Kuryr need etcd on each compute node to store
network data.
Etcd is only deployed in controller nodes at this moment.
Also this change remove and useless bootstrap tasks.
Depends-On: I9c6c876773288c2f951966498db0ff8af090ac20
Change-Id: I8a84334e831fb15f6cbdd3bc34d2159638df6b85
Closes-Bug: #1697699
- Updated Ubuntu image to use 16.04.
- VirtualBox provider to use centos/7 image + vagrant-vbguest plugin.
- Improved docs so it is clear that vagrant-vbguest plugin is only
required with VirtualBox.
- Clarified comment and made it independent of the release.
- Refactored the kolla and kolla-ansible paths to be based on the
username used by Vagrant, that can change depending on the image.
Change-Id: I23d84dcc3297c43eb12eff9c443d282281fc6c82
With the following configuration in globals.yml:
enable_ceilometer="no"
enable_designate="no"
enable_searchlight="yes"
neutron.conf is generated like following:
[oslo_messaging_notifications]
driver = messagingv2
topics =
=> topics value is missing.
This patch fix it.
Closes-Bug: #1671940
Change-Id: I28ab60c61882caaba823bab84f30f77e270f29b4
With the following configuration in globals.yml
enable_ceilometer="no"
enable_designate="no"
enable_searchlight="yes"
nova.conf is generated like following:
[oslo_messaging_notifications]
driver = messagingv2
topics =
topics value is missing.
Change-Id: I27145c0da8b864b2614091933c33d83bdec8b9be
Closes-Bug: #1671935
Co-Authored-By: Jeffrey Zhang <jeffrey.zhang@99cloud.net>
The default value of default_boot_option configuration will
change eventually from "netboot" to "local".
It is recommended to set an explicit value for it during the
transition period
Change-Id: Ic42b84e82d4ad27e371536ad9915b5a32118012d
Closes-Bug: #1696636
The 's' command wasn't closed properly. This was fixed in kolla repo
before it was decided that the dev env should go in kolla-ansible.
Change-Id: Ia1434ebb276f0fc76bf88fe386b8e9527133ce4d
Updated the package with correct one and got the command working
for ubuntu 16.04
Closes-Bug: #1696044
Change-Id: I643d36459ed563965fe95e57a47117be926a8d49
If we don't use cirros image, ``image_ssh_user = cirros`` is wrong,
so we should make it be variable.
Change-Id: I0a1d6999d1dbc8ce319f4bd504455dfd1fb5fceb
Closes-Bug: #1696088
Normally chronyd will cause the system to gradually correct any time offset, by slowing down or speeding up the clock as required.
In certain situations, the system clock might be so far adrift
that this slewing process would take a very long time to correct the system clock
Change-Id: I939b6aae1dbeb133203085ec68bdb9f7936ee9ef
Closes-Bug: #1696056
This patch introduces the ansible materials to deploy
the skydive service, that can be used to monitor and
troubleshoot networking in an openstack deployment.
Implements: blueprint skydive-service
Co-Authored-By: Nicolas Bouron <nicolas.bouron@gmail.com>
Signed-off-by: Mathieu Rohon <mathieu.rohon@gmail.com>
Change-Id: I53051a1b0c85380416288e17040a398b6efb62c0
gnocchi have archive policy rule feature, which can control metric's
archive_policy. gnocchi also have a default archive policy rule which
is using low archive policy.
On the other hand, archive_policy is marked as deprecated and will be
removed in the feature in ceilometer[0].
So should better remove archive_policy ceilometer.conf.
[0] https://review.openstack.org/#/c/448586/
Change-Id: I0aa726f6420d628bda3fb4c4eba86b55fe1e2699
Closes-Bug: #1696038
This patches changes deploy_gate quite a bit so in reality all
deployments will now assume multinode (even if it's single node). After
that we will refactor it even further to enable easy addition of new
scenerios.
Change-Id: I1faada46e6a7aa026128b2f01d77eabb04759439
Actually Openstack services configuration can be overriden using many
files:
- /etc/kolla/config/<< service name >>/<< config file >>
- /etc/kolla/config/<< service name >>/<<host>>/<< config file >>
- /etc/kolla/config/global.conf
- /etc/kolla/config/database.conf
- /etc/kolla/config/messaging.conf
Only per-service configuration is actually documented here:
https://github.com/openstack/kolla-ansible/blob/master/doc/advanced-configuration.rst#L164
Allowing to globally modify service configuration can be perform too,
but it can be done in 3 different manners:
- /etc/kolla/config/global.conf
- /etc/kolla/config/database.conf
- /etc/kolla/config/messaging.conf
database.conf and messaging.conf seems redundant with global.conf.
In order to simplify codebase it seems logical to deprecate them.
Change-Id: Ia632c207e4b0237ea813fcf53b44504b97a204e7