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
The authtoken config variable delay_auth_decision must be set to True.
The default is False, but that breaks public access, StaticWeb, FormPost,
TempURL, and authenticated capabilities requests (using Discoverability).
Change-Id: I420a95f5f9fda3321a4acfc5846e40294a8bd588
Closes-Bug: #1768795
User can use custom directory for nova instance.
For example using a shared file system as backend.
Change-Id: I11fe4891719a2e2a34888d8b798df5602e294e4f
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
As of the Queens release, Keystone solely implements the Identity
API v3. Support for Identity API v2.0 has been removed since Queens
in favor of the Identity API v3.
Change-Id: If65b26935e8bd1e6655d84259499f4013762e4e3
Closes-Bug: #1778846
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
1. Add the role enabled check for some projects
2. adjust the file created positon for keystone to keep
consistence with others
Change-Id: Id2b893ba546b3adf41d97927f8d20dca403a0457
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
Kolla-ansible supports the deployment with specified tags,
"--tags, -t <tags> Only run plays and tasks tagged with
these values".
However, when specifying a tag, if the tag of the task
is not "always" or different from the specified tag,
it will not be run.
This task "Gather facts for all hosts (if using --limit)"
is not executed when the --limit parameter is added and
deployment with specified tag.
Closes-bug: #1711266
Change-Id: If50db2718b765f1d65b5d79eb042b0d95775bafc
Provide support for kolla dev mode in blazar. When
'kolla_dev_mode' or 'blazar_dev_mode' variables are
enabled, source code of blazar project will be cloned
and mounted automatically
Partially implements: blueprint mount-sources
Change-Id: I50c5eb97be1123b76b1d42fbb25a0ecbaa2c1a44
