Currently, when users try to navigate through horizon
panels or use the command-line interface that contains
calls to /api/glance/metadefs it will pop up insufficient
permission errors due to the fact we are disabling [1]
the metadef APIs in glance addressing OSSN-0088 [2].
As a side effect on how we address the OSSN, all API calls
to metadefs will be forbidden for any user, which is not recommended
in production environments. However, we have the current
recommendation of the OSSN which allows CRUD of metadef to
admin only and provide read access to all users.
[1] aab5ee7711
[2] https://wiki.openstack.org/wiki/OSSN/OSSN-0088
Story: 2008761
Task: 42128
Change-Id: Ib1415cadbbfab874a8d44ac6b5c6fba3c7502242
With stein in extended maintenance, this change updates the check
and gate jobs to run train and up, as well as updating some jobs
to use train. Moved stein to periodic.
Change-Id: Icd516f25140ebd479b49da101e4f84326f341274
Chart upgrading was failing due to some immutable fields are needed to upgrade before the jobs can be upgraded. For solving this issue, we
have added the helm.sh/hook annotations with post-install and post-upgrade values.
As for hook-weight annotations, we have added these to control the flow of the jobs with hook creation as the jobs are dependent. Like,
db-init jobs need to run before db-sync and so on.
Change-Id: I28dec6d082b95b448752e741e7694d32b2740cfa
Chart upgrading was failing due to some immutable fields are needed to upgrade before the jobs can be upgraded. For solving this issue, we
have added the helm.sh/hook annotations with post-install and post-upgrade values.
As for hook-weight annotations, we have added these to control the flow of the jobs with hook creation as the jobs are dependent. Like,
db-init jobs need to run before db-sync and so on.
Change-Id: Ia8eebf87a646aa0e25f89721ebda0e237dcf23af
Chart upgrading was failing due to some immutable fields are needed to upgrade before the jobs can be upgraded. For solving this issue, we
have added the helm.sh/hook annotations with post-install and post-upgrade values.
As for hook-weight annotations, we have added these to control the flow of the jobs with hook creation as the jobs are dependent. Like,
db-init jobs need to run before db-sync and so on.
Change-Id: Idca6ee2422769ccb5c8a87812b4fb564b283d44b
Chart upgrading was failing due to some immutable fields are needed to upgrade before the jobs can be upgraded. For solving this issue, we
have added the helm.sh/hook annotations with post-install and post-upgrade values.
As for hook-weight annotations, we have added these to control the flow of the jobs with hook creation as the jobs are dependent. Like,
db-init jobs need to run before db-sync and so on.
Change-Id: I2c0f9468371a60d875fd0267b3d916b286f8ce7b
Chart upgrading was failing due to some immutable fields are needed to upgrade before the jobs can be upgraded. For solving this issue, we
have added the helm.sh/hook annotations with post-install and post-upgrade values.
As for hook-weight annotations, we have added these to control the flow of the jobs with hook creation as the jobs are dependent. Like,
db-init jobs need to run before db-sync and so on.
Change-Id: I0905be3d1708e5226ccd41b84b409a290c89f826
Chart upgrading was failing due to some immutable fields are needed to upgrade before the jobs can be upgraded. For solving this issue, we
have added the helm.sh/hook annotations with post-install and post-upgrade values.
As for hook-weight annotations, we have added these to control the flow of the jobs with hook creation as the jobs are dependent. Like,
db-init jobs need to run before db-sync and so on.
Change-Id: I5facecb2885f0373e986c62e97abad822f4047dc
Chart upgrading was failing due to some immutable fields in job are needed to upgrade. So, we thought using the post-install and post-upgrade
helm hook for job to force the job resource to execute after all resources are created. And as some jobs are dependent on each other i.e.
some jobs needs to run in order for helm hook to be successful. For that we used hook-weight to control resource creation order.
Change-Id: I26881324d101a986b7367d4682e9adcd07a24b13
About helm-toolkit chart, you should to path <HELM_CHART_ROOT_PATH> run the script when build helm-toolkit, not here.Otherwise, the old code will not work here.
Change-Id: Ic3ee9209742a74153935faa7de20411461eabef8
Without this "make",It can lead to not being found <helm-toolkit> when running this script.
Closes-Bug: #1917849
Change-Id: I453a87c4d38e2db59fcbacc5c38e7bf68491914c
Without this "make",It can lead to not being found <helm-toolkit> when running this script.
Closes-Bug: #1917852
Change-Id: Iba4be77bd278e156c56fe35c79b1b87d84a7a5f9
It is possible than an interface has multiple IP addresses, for
simplicity of this change, use the first one so that the service
can start.
We can look later into improving it to accept some sort of index
for the IP address.
Change-Id: Ie856f54331d689a51bfd6de45db5820b765797ef
There was an issue with the metadef APIs in glance, detailed in
the latest OSSN[0] that they have the potential to leak resources.
This change updates the default policy for the metadef APIs to
be disabled by default.
[0] https://wiki.openstack.org/wiki/OSSN/OSSN-0088
Change-Id: I7377b3a2f3784fe7da78bdd7aba146328cc0f406
