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>

In case Kolla's users want to deploy with both of
binary and source image, we should have a variable
install type that define install type for each project.

We also add specific image tag for each Openstack project.

This commit is implemented for Neutron, Nova,
Octavia project and Openvswitch as well.

Change-Id: I04d3a17231b607795bbddb85cd940fa725ff7a61
Implements: blueprint mixing-binary-and-source-image

OSprofile allows user/devs trace OpenStack requests.

Implements: blueprint enable-osprofiler
Co-Authored-By: Bertrand Lallau <bertrand.lallau@gmail.com>
Change-Id: I82ea85d726011ef6cbf99380f395452d6d7f8053

Remove option vnc_enabled from group default.
Add option enabled in group vnc.

Change-Id: Ia48b335fd9d160b53bc2ec98b7e3bc5b89b9c553
Closes-Bug: #1695181

Recent code updates[1][2] broke the support for nova fake drivers.
in [1], nova_services dict is introduce but the change is not refected
in nova.conf.j2[3] when dealing with its elements.
in [2], two typos make neutron handlers to fail.

[1]: https://review.openstack.org/#/c/407416/
[2]: https://review.openstack.org/#/c/424504/
[3]:
https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/nova/templates/nova.conf.j2#L35

Change-Id: Ie32c76c4c902f1d95a1b4c97f8cbdb7ab101e48b
Closes-bug: #1695218

Many of the templates use 600, remove unnecessary permission
on these templates to bring them in line with the others.

Change-Id: I30fe1b3822b9c7bb6ab98729fc519dc1d603db27

Useful api_interface_address variable has been define here:
https://github.com/openstack/kolla-ansible/blob/master/ansible/group_vars/all.yml#L57
In order to simplify codebase we must use it as much as possible.

Change-Id: I18fec19bf69e05a22a4142a9cd1165eccd022455

In someplace in the code admin user, project and domain name
are hardcoded.

This change use the correct variable defined at:
https://github.com/openstack/kolla-ansible/blob/master/ansible/group_vars/all.yml#L278

Change-Id: I3a4c78d81733bf7a2f3c67d259ec5c5f5bb38d3f

Option "notify_on_state_change" from group "DEFAULT" is deprecated. Use
option "notify_on_state_change" from group “notifications".

refer to
https://docs.openstack.org/ocata/config-reference/compute/config-options.html

Change-Id: I18e80ccd5981b81bfd597b94717ed77b13c05222
Closes-Bug: #1690494

wait_for module waits 300 seconds for the port started or stopped.  This
is meaningless and useless in precheck. This patch change timeout to 1
seconds.

Change-Id: I9b251ec4ba17ce446655917e8ef5e152ef947298
Closes-Bug: #1688152

With nova cells_v2 at least one compute node is required in
inventory to deploy nova.

This change add prechecks to ensure at least 1 compute is present.

Change-Id: I242518ad3bd149ad245515299301777f6b3bdd08
Closes-Bug: #1686410

If used external ceph for nova,the ceph storage not enable cephx.
So ceph keyring file not does not exist.
Task throw error of check ceph keyring files.

Change-Id: I6257c107b94abf4d363e854229aaab8301d1d694
Closes-Bug: #1684522

Simple_cell_setup is not recomended to use.
Is better create map_cell0 manually, create base
cell for non cell deployments and run discover_hosts.

This PS migrate actual config to make use of described
workflow at [1]. We our actual workflow we're running
into the issue that services are not mapped until cells
are present, breaking deployment waiting for compute
services to appear.

[1] https://docs.openstack.org/developer/nova/cells.html#fresh-install

Change-Id: Id061e8039e72de77a04c51657705457193da2d0f
Closes-Bug: #1682060

Some roles made a bad usage of the 'node_config_directory' variable.

As described here:
https://github.com/openstack/kolla-ansible/blob/master/ansible/group_vars/all.yml#L16

'node_config_directory' is the directory to store the config files on
the destination node.

This variable MUST be changed to 'node_custom_config'.
Futhermore this will unified all roles.

Closes-Bug: #1682445
Change-Id: Id8d8a1268c79befac8938c1e0396267314b40301

Change-Id: I6c725efd9d08a079ced2abca5be188b6ceac55c2
Closes-bug: #1682000

Nova service-list is returning empty registered service
when in database they are. Because of this, simple_cell_setup
is not executed and deploy stucks waiting for nova-compute.

This change temporaly checks the database for existing nova services
instead of openstack compute service list.

This change will need to be reverted once the command is fixed.

Change-Id: Ic508eb3ff03b5f233186353fc7697305cc792d14

Option "secure_proxy_ssl_header" from group "DEFAULT"  has been
deprecated in the N release and has been removed in the O release.

Use wsgi.secure_proxy_ssl_header configuration instead.

see
https://docs.openstack.org/ocata/config-reference/compute/config-options.html
https://docs.openstack.org/newton/config-reference/tables/conf-changes/nova.html
https://docs.openstack.org/mitaka/config-reference/compute/config-options.html

Change-Id: Icf3eea66f4ac281641ba22e8194aa113b57f6ce8

If disable cinder in openstack environment.
Cinder of configuration items do not need to configure in nova.conf

Change-Id: Ie346dfe45f8c2d3fd383095d0c64f8e9421100ff

The following WARN logs always appears in nova-api.log:
- Option "firewall_driver" from group "DEFAULT" is deprecated for removal.
- Option "linuxnet_interface_driver" from group "DEFAULT" is deprecated
for removal.

These 2 options can be removed for the following reasons:
- nova-network will be deprecated
- moreover Kolla doesn't configure nova-network

Options deprecation notes is here:
https://github.com/openstack/nova/blob/master/releasenotes/notes/deprecate-more-nova-network-opts-a9f87c79f7d26438.yaml#L8
https://github.com/openstack/nova/blob/master/releasenotes/notes/deprecate-more-nova-network-opts-a9f87c79f7d26438.yaml#L37

Change-Id: I12f80a02b9d27f2bdbb8926eb648ea4f6e6dd945

Change-Id: Ide78ed1de89a9904db48f08fcff3c247ee650317

Heka has been removed and replaced by fluentd.
Refer to https://review.openstack.org/#/c/437874/

Change-Id: Id9f95cbefcd4b1089e2a00a92dc66f387c27f09b

Closes-Bug: #1671862
Change-Id: I6b77773238cd65a3cc009d8d9a38bdbea0035212

The presence of heka_socket:/var/lib/kolla/heka with
containers that log to /dev/log, such as nova-ssh cause a
wedge on starting as /var/lib/kolla/heka/log is never
created due to the removal of heka.

This means that ssh data, such as config and keys are never
sync'd and sshd is never started.

Change-Id: Ia561526e6caf82eebd18c6e31cbeb1738b9ff602
Closes-Bug: #1672207
Signed-off-by: Dave Walker (Daviey) <email@daviey.com>

* Ironic do not support multi glance ips.
* Write the nova-compute-ironic binary log to nova-compute-ironic.log
file

Change-Id: I87359c47a5845c4d7a6ab9daaefcc94a51c92eb0
Closes-Bug: #1671989

This reverts commit 6cb45072.

Change-Id: I33a0b8ba4ca69e5e34edb11248fb614a5a913f65

Add support for basic multiple regions, that is to say, many OpenStack
with a shared Keystone (same users) and Horizon. The shared Keystone
and Horizon are deployed into one region, for instance RegionOne.
Services of other regions have an access to this Keystone. This
support assumes that the operator knows the name of all OpenStack
regions in advance, and considers as many Kolla runs as there are
regions.

The new variable, multiple_regions_names, contains the name of
regions. It is needed by the region that includes Keystone and
Horizon. In register.yml, it specifies to create as many Keystone
endpoints as there are regiones, so that services of other regions can
connect to Keystone. In local_settings.j2, it changes the render to
support multiple regions in Horizon. The multi-regions.rst explains
how to perform a multiple regions deployment.

Implements: blueprint multi-kolla-config
Change-Id: Icab2aebfc4de0e3bc609950956e0af397705f403

Nova external ceph task have a type which break deployment.
State module not present, the module used should be stat.

Change-Id: Ie8a0b30f44fc35a597334383a85353d324e765cd
Closes-Bug: #1671526

Add a new subcommand 'check' to kolla-ansible, used to run the
smoke/sanity checks.

Add stub files to all services that don't currently have checks.

Change-Id: I9f661c5fc51fd5b9b266f23f6c524884613dee48
Partially-implements: blueprint sanity-check-container

cell0 is already setup in Ocata, when upgrading to Pike
is not anymore necessary to create.
All nova DBs (nova_api, nova and nova_cell0) are already
created in Ocata too. Only bootstrap_service is needed
while upgrading.

Change-Id: Idc4941334faf91feee868472155a8c8ea0eba436

It is unnecessary and a waste to run nova-compute-ironic on a single
node, change the host name field in nova-compute-ironic could ensure
nova-compute and nova-compute-ironic run on the same node.

Change-Id: If2acbf25caab0570da444472003599b9e0f2a1ff
Closes-Bug: #1671103

Booting from volume require cinder's ceph client secret now. Move cinder
before nova in site.yml, because nova depends on cinder ceph client key
now.

Change-Id: I01c9ed80843d98305b8963894c4917c21a35d3ac
Closes-Bug: #1670676

Libvirt 2.5 (latest version in cloud archive) seems to have changed
behavior of dynamic_ownership.

Change-Id: Icf9592c2f82f0f4a35074b9b13a51643a32631e9
Closes-bug: #1668654

Change-Id: Ie26b20bb4012d35bfbcd43440d32c9eac7a471d6
Closes-Bug: #1670673

* Move the tasks to the role
* Skip the task when container is already running

Change-Id: I1990d4dd2a02efa2b3766329000aa23419e0ff17
Closes-Bug: #1670286

In some case, public interface may not reachable in internal.

Change-Id: Ibcdef571a6814e6626216fe33028e5e69889b4f2
Closes-Bug: #1670259

retries only works with until.

Change-Id: I350ee69b0eca7a1763bb7eab34f874d7e22c1340
Closes-bug: #1668023

Change-Id: Ic3cbf89b135a1902fa57a8d1df8c858cd6398097

nova-compute will try to connect nova-conductor when upgrade.level is
auto. So nova-conductor need run more earlier. Otherwise, nova-compute
will failed to connect nova-conductor through message queue.

Closes-Bug: #1665836
Change-Id: If6296a84305bc283fb071b9650e629c6b1b71e61

In kolla-kubernetes, nova-compute-ironic is ran with a separate virtual
interface with a different hostname. So it is OK to run nova-compute and
nova-compute-ironic on the same node.

Change-Id: I3b0f12f128af8210bc97502dbc01469f619dd1ac

Change-Id: Ied1af4c8ab3012fc5893905795590b53227fb26e
Closes-Bug: #1666123