- May 16, 2018
-
-
Kevin Tibi authored
Previous change[1] of config for grafana introduced new bugs. [1]https://review.openstack.org/#/c/548291/ Change-Id: Ib62f0670003612073ff08f702febe81c753b72e5
-
Zuul authored
-
Zuul authored
-
- May 15, 2018
- May 14, 2018
-
-
Zuul authored
-
ZhijunWei authored
Now, the ceilometer use [service_credentials] to get credentials[0][1], remove the unused [keystone_authtoken] [0]: https://github.com/openstack/ceilometer/blob/master/devstack/plugin.sh#L294 [1]: https://docs.openstack.org/ceilometer/latest/configuration/index.html Change-Id: Ic92f9ecb1a43c11311f2a428611e78c0986f02cf
-
caoyuan authored
when run creating Magnum trustee user role task, the domain parameter must be domain id[0]. so kolla-ansible need to register the result of Creating Magnum trustee domain task, and use the domain id when creating Magnum trustee user role. [0]: https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/magnum/tasks/register.yml#L59 Co-Authored-By:
ZhijunWei <wzj334965317@outlook.com> Change-Id: I57cdd011b7fc863133f9e3b43ae783cd1486e644 Closes-Bug: #1766410
-
- May 12, 2018
-
-
wu.chunyang authored
keep consistent with other projects Change-Id: I3eae5efbc148a87dea44ce1fe727f6314a437e98
-
- May 11, 2018
-
-
Zuul authored
-
Jorge Niedbalski authored
This patch enables 3 new configuration options for haproxy.cfg global section. - haproxy_processes: number of haproxy processes (default:1). - haproxy_max_connections: number of concurrent connections (default:4000) - haproxy_process_cpu_map: enforces 1:1 mapping/affinity between process and core. (default: no). Closes-Bug: #1770060 Change-Id: I33fc499b083c7bcc548133498e44406a479389f1 Signed-off-by:
Jorge Niedbalski <jorge.niedbalski@linaro.org>
-
Zuul authored
-
Zuul authored
-
Jeffrey Zhang authored
- rename action and serial to kolla_ansible and kolla_serial - use become instead of "sudo <command>" in shell - Remove quota for failed_when and changed_when in rabbitmq tasks Change-Id: I78cb60168aaa40bb6439198283546b7faf33917c Implements: blueprint migrate-to-ansible-2-2-0
-
Zuul authored
-
Zuul authored
-
- May 10, 2018
- May 09, 2018
-
-
Mohamed El Gindi authored
In trove-taskmanager.conf a typo has been introduced for nova_proxy_admin_tenant_name option. It currently is: "nova_proxy_admin_tenant_name = services" But should be: "nova_proxy_admin_tenant_name = service" Change-Id: I7b5d0ca4c6c994b6dd3c5de3f0a79637fda88177 Closes-Bug: #1770262
-
Mark Giles authored
The kolla-ansible certificates command creates a self-signed certificate and corresponding private key. This change sets the file mode on the files that contain the private key so that they are not world readable. Change-Id: I7bfba5975af8d230e5d00c2ce801a914fbbf2d4e
-
Zuul authored
-
Zuul authored
-
Duong Ha-Quang authored
Apply Glance database upgrade procedure: https://docs.openstack.org/glance/latest/admin/zero-downtime-db-upgrade.html Rolling upgrade in Glance requires that glance-registry is not deployed and run Depends-On: https://review.openstack.org/532128 Depends-On: https://review.openstack.org/566804 Change-Id: Ia5d0cee2385facefda9d423051b74ab51d075f13 Implements: blueprint apply-service-upgrade-procedure
-
wu.chunyang authored
Since the version of ceph bump to L, the output should be updated. Change-Id: I4c05b9b7423369a43dcb5855a2f0ef016ddbe488
-
wu.chunyang authored
By default, the workers for gnocchi_metricd is 5[0], it's too small for production environment, this PS to make it configurable, in this way, user can change it according to actual needs. [0]: https://github.com/openstack/kolla-ansible/blob/master/ansible/group_vars/all.yml#L356 Change-Id: Ibf4dec793f02c407547c77963cc13799d044b90f
-
Jorge Niedbalski authored
This commit adds the --by-service flag in the discover_hosts command of the nova cell subsystem, using this flag, hosts are mapped based on the existing nova-compute services instead of using the compute node reference. In this way, we can ensure that the host mappings exists for this new host (and create it if not) preventing the HostMappingNotFound exception to loop over and over. Bug: #1768094 Change-Id: I948004031bc3e125f929ed3e6c670aea11e73a31 Signed-off-by:
Jorge Niedbalski <jorge.niedbalski@linaro.org>
-
chenxing authored
Following by https://docs.openstack.org/image-guide/obtain-images.html#cirros-test Change-Id: Ide3508b3af6923a06e63242dc730b2742147ce37
-
Mark Goddard authored
Change I0c1328237d2109b1d1d5dcb40f331fff1ab10257 recently prevented running kolla deployment CI jobs against changes to some files, including requirements.txt. This change reinstates testing of changes to requirements.txt, since this can have an effect on the operation of kolla ansible. Change-Id: I3d839de9aed60cddebea7d1140f618d3261cca2a
-
Zuul authored
-
ghanshyam authored
While fixing test-requirement.txt, I found that check pipeline can be more optimized in term of selecting the jobs to run based on file change. - https://review.openstack.org/#/c/567083/ kolla main jobs are not needed to be run on check pipeline for test-requirements.txt, releasenotes/* etc. This commit skip those jobs when only above files are changed in patch. This is will save time as well as infra resource also. Change-Id: I0c1328237d2109b1d1d5dcb40f331fff1ab10257
-
ghanshyam authored
hacking is not capped in g-r and it is in blacklist for requirement as hacking new version can break the gate jobs. Hacking can break gate jobs because of various reasons: - There might be new rule addition in hacking - Some rules becomes default from non-default - Updates in pycodestyle etc That was the main reason it was not added in g-r auto sync also. Most of the project maintained the compatible and cap the hacking version in test-requirements.txt and update to new version when project is ready. Bumping new version might need code fix also on project side depends on what new in that version. If project does not have cap the hacking version then, there is possibility of gate failure whenever new hacking version is released by QA team. Example of such failure in recent release of hacking 1.1.0 - http://lists.openstack.org/pipermail/openstack-dev/2018-May/130282.html Change-Id: I05790c5f946a4127fe6c8d9867cc618cb83d67fb
-
- May 08, 2018
-
-
Zuul authored
-
Duong Ha-Quang authored
As described in [1], [2], glance-registry was deprecated from Queens and will be removed in S, so we should disable glance registry in Queens but keep the image and deploy logic if user need this (but it's low chance due to glance-registry almost do nothing currently). This patch only disable glance registry microservice. [1]: http://specs.openstack.org/openstack/glance-specs/specs/newton/approved/glance/deprecate-registry.html [2]: https://blueprints.launchpad.net/glance/+spec/deprecate-registry Change-Id: I6667325711d1c54cf5233ad6973d89ea396a46b5 Closes-bug: #1769837
-
Zuul authored
-
- May 07, 2018
-
-
Jorge Niedbalski authored
This patch enforces the removal of the container network namespace when the environment is destroyed. Closes-Bug: #1769651 Change-Id: I9b0bbbb5a59e6067a745635c555051ef97b79f9a Signed-off-by:
Jorge Niedbalski <jorge.niedbalski@linaro.org>
-
Zuul authored
-