Fix keystone to manage the OSM users/projects 61/14461/7
authorvegall <lvega@whitestack.com>
Tue, 2 Jul 2024 15:30:30 +0000 (15:30 +0000)
committergarciadeblas <gerardo.garciadeblas@telefonica.com>
Thu, 24 Oct 2024 15:04:15 +0000 (17:04 +0200)
commit7badcae198d10e8dc0777f013f0176b81ebe5e68
treed5b955ca156ee30e7e9522f07ec2904ccbda6c04
parent36a2a79de653143011c2d5ef50ee213d581537f1
Fix keystone to manage the OSM users/projects

Keystone was not used by default by OSM NBI. Instead, internal
authentication is used.

When NBI is configured to use Keystone as auth backend, we found that it
didn't bootstrap properly because there were no data in the MySQL DB
used by Keystone. The initilization of DB was supposed to be done by the
Keystone containers in keystone-deployment. However, those container
were not able to initialize the DB because they were running as regular
users instead of root users.

Keystone is thought as an infra solution, not as an application
solution. The community behind Keystone development agreed on that
behaviour.

Based on that, Keystone containers were adapted to run as root.

In addition, we decided to disable Keystone and MySQL as part of the
default values for OSM helm chart.

Change-Id: I0e7078b809abe858a69323d6e3e493e862d6e6ab
Signed-off-by: vegall <lvega@whitestack.com>
.gitignore
docker/Keystone/Dockerfile
docker/Keystone/scripts/start.sh
installers/helm/osm/templates/keystone/keystone-configmap.yaml
installers/helm/osm/templates/keystone/keystone-deployment.yaml
installers/helm/osm/templates/keystone/keystone-service.yaml
installers/helm/osm/templates/nbi/nbi-configmap.yaml
installers/helm/osm/values.yaml