In some environments it may not be desirable to modify the sudoers
configuration. This change makes this part of bootstrap-servers
optional, based on the create_kolla_user_sudoers variable.
Change-Id: I653403bfc5431741807edef57df58e05e679900b
This makes the bootstrap-servers command more idempotent, since without
the append argument set the kolla user will be removed from the docker
group before being added to it again in a later task.
TrivialFix
Change-Id: Iab0f6b5e18a103e9140631ee3ebbbb48c490bc24
In I86bf5e1df3d6568c4f1ca6f4757f08a3dd22754d, creation of the kolla user
was moved to after package installation to ensure the sudo package is
installed when required. This change does not work when python
dependencies are installed in a virtual environment however - when the
virtualenv variable is set.
This change moves the ownership change of the virtualenv to after the
kolla user has been created. It also uses the kolla_user and kolla_group
variables to set the user and group appropriately.
Change-Id: I320e5d611099ad162945a98d5505a79606da0eba
TrivialFix
Kolla Ironic reference point out enable booting via iPXE by setting
"enable_ironic_ipxe" to "true" in "/etc/kolla/globals.yml", but there
is no enable_ironic_ipxe option exists in globals.yml.
Change-Id: I5794fc5a7d236f7f486011f53366a5b3f4c59731
Other lists of servers have the postfix _servers. To be consistent
this change uses the same format for Kafka.
Change-Id: Ia595f2ab485904e76fb76211f6715a7c019886ea
Partially-Implements: blueprint monasca-roles
Skydive recently splitted the OpenStack configuration:
one for the authentication - on the analyzer - 'auth.keystone'
and an other one for the Neutron probe on the agent
'agent.topology.neutron'.
Change-Id: Idce277d30f01e7a36499b1aee24c54779c54a807
It is not always convenient to use the the given
admin project and admin user; especially when some clouds
use different user and project for there keystone 'admin'
This allows setting the variables for these users to something
else, and defaults them to there current values of 'admin'.
Change-Id: I22b79a30f01c90a92ecc0974886edf3791518f2f
By default, kolla configure docker to use an insecure connection
with the private registry. If we want to use SSL verification we need
to add an option.
Change-Id: Id1805c9cfeb499da9bb56c70028f14c6f8bb20b6
To destroy a kolla-ansible environment a confirmation string should be passed
along with kolla-ansible command: kolla-ansible destroy -i ~/multinode \
--yes-i-really-really-mean-it
However, this string is not evaluated right and just putting --y starts destroy
process: ./kolla-ansible destroy -i ~/multinode --y
Change-Id: I5983f9c7fd3859d60741dfd23ad10dfd91872eeb
Closes-Bug: #1701313
As reported in the bug, these can grow to 10s to 100s of GB
in a month. To reduce the chance of filling the disk and
bringing down the control plane this change defines
an expiry time.
Closes-Bug: 1720113
Change-Id: I508aad1f515d5108a3d08c90318b70d0a918908c
This reverts commit f8fd06011aed5cd9028a8c1e206762a78e137df7.
Based on the code, overall uses service_credentials, but looks like a
few parts is using keystonemiddleware.auth_*
Closes-Bug: #1775956
Change-Id: I766a5624737cae892fe77fa8151b20e0972ed5b2
Both the driver and the enabled_drivers options are being removed
this week. Stop setting them to avoid breakages.
Change-Id: I0e0bf851424b8f5839b159ef83f1cc65c30e2fb3
