With pod disruption budget set it is not possible to drain nodes
and perform other expected operations. This PS changes the default
value to 0, restoring the typically expected operation of pods.
Change-Id: I43ef35638c98caee2cf567487173399157000ada
Allow glance to use the "pvc" method, this was previously called file
but has been renamed for clarity.
We now require Kubernetes 1.6 or later; remove the storage annotation
in favor of storageClassName.
Change-Id: I315eaf68937f91b56c1a26954072bda53767c606
Addresses consistency issues that appear with autoincrement fields in
the existing chart, as demonstrated in [1]. It should allow automatic
recovery of 2 out of the 3 (default) cluster members.
It does not address automatic recovery of a complete shutdown of all
cluster nodes.
[1] https://review.openstack.org/#/c/465977/
Change-Id: I84c86e1862f03a6d381bf219b821ea3636049f0b
This PS adds a default pod disruption budget for glance-api and
glance-registry to ensure at least one replica of each is running.
Change-Id: I06364bc2bb816fd4877353857b1adfb13a35a0a7
Now ceph.enabled property in values.yaml file is not used anywhere
and almost all configuration about ceph is moved under conf property.
In addition, default values.yaml file has no ceph.glance_user property
and still the property is used in templetes.
It looks it's time to move remained ceph properties under conf tree
and remove ceph tree.
Closes-Bug: #1691011
Change-Id: I98f7a85eef517ab806432a7342aa3601e8183e0b
This PS makes the PV used for the file backend flexible, allowing
operators to specify the annotation and size used/allocated.
Change-Id: I6d153143f9cc268c4c543e392ddf115e5db67a57
The default bootstrap image for glance was Ubuntu 16.04, which was a
>200Mb download, and is not sutiable for testing in low memory
environments. This moves to the Cirros image which is suited to
this sort of usage.
Change-Id: I3c22f961c43ee68c24e23eb6b483c165540337bd
This commit moves Glance to use the configuration methods from Heat,
Nova, Neutron and Keystone.
It includes a _values-mvp.yaml that applies values suitable for using
a file backend, including the auto creation of a PVC.
Change-Id: I55a96982a7d0adbc118492aff4b56adf127b2cd1
* Add resources limits and requests for each chart
* Refactor the resources limits and requests to follow a patern
* Fix some coding issues
* fix issues resulting from feedback on the resources PR
* Reset some variables to a static value in the neutron chart.
* Substituting variable entrypoint by dependency_check in the concerned files
* Few adjustments
* Update deploy-region.yaml
* Update deployment.yaml
* Add resources limits and requests for each chart
Squah all commits in one.
* Add resources limits and requests for some charts
* cleaning
* Fix indendation issue
* Update deployment.yaml
* Update daemonset-ovs-vswitchd.yaml
two templates, because i don't how to pass two variables to template.
PR also adjust layout of configuration files in Nova.
Signed-off-by: DTadrzak <daniel.tadrzak@intel.com>
This introduces changes across several charts, for consistent
endpoint lookup routines. Today, only the internal endpoints
are defined (and copied to admin and public). This can later
be expanded to handle unique public and admin endpoints.
This ensures the catalog is populated with consistent URLs
for all services.
* imagePullPolicy requirements for init-containers in 1.5
* dependency tree specified mariadb-init, when there is only a
mariadb-seed job to depend on
* the requirements.yaml should not include any chart in this
repository other then common as that severely complicates
removing charts as all dependent elements are removed with it
* the post.sh.yaml has HOME set to /tmp which will not read
/home/ansible configuration. It was unclear if this was by
design, but /home/ansible seems like an important part of the
kolla toolbox
* the post.sh.yaml file had quoting typos, but even when they are
fixed the job/glance-post will not run to completion, complaining
of a missing kolla_keystone_service module
