openstack/kolla.git/ansible/roles/prechecks/tasks/service_checks.yml, branch master

Remove Ansible from Kolla

2016-11-16T04:34:17+00:00

Change-Id: I5396e4b9927d3e65b6aa4185238a43a4765a996b

fixed kestone fernet prechecks for multinode deployments

2016-10-03T10:14:04+00:00

command fails since it is a compound command. Changed to a single awk command instead. Closes-Bug: #1629206 Change-Id: Id7963b15c3321eca6f891a625b1ba140dc57aa22

run_once Checking mongodb backend for ceilometer

2016-09-19T19:07:44+00:00

TrivialFix Change-Id: I54151df7f869e0a7915ce6361eda8dfefe5d1870

Checking valid fernet expiry only need to run once

2016-09-19T15:21:57+00:00

TrivialFix Change-Id: I4e84ac4e51a976ad132aa78b175855bed1d4bb20

Check volume group exists for Cinder in prechecks

2016-09-13T15:39:56+00:00

Add a service check for Cinder when using iscsi/LVM, that the appropriate volume group exists. TrivialFix Change-Id: I54e01911709db73549334760498b4246fe6271d7 Co-Authored-By: Vladislav Belogrudov

Allow mysql to be used as a database for Ceilometer

2016-09-12T11:41:35+00:00

MongoDB is still default. Refer to http://docs.openstack.org/developer/ceilometer/install/dbreco.html for more info on Ceilometer database backends. Closes-Bug: #1622532 Change-Id: Iaf84f9efe0537f42797f4bb7ba2a3611835cc84e

Add precheck for ceilometer backend

2016-09-01T15:23:28+00:00

Currently when set enable_ceilometer: true and enable_mongodb: no, the deploy will fail with ceilometer database creating error. Add a precheck to avoid this situation in both prechecks and bootstrap. Change-Id: I2d46ef9adeb8e028f3c18e6bc2d3752cc39bcb29 Closes-bug: #1605522

Add option to support dhcp/l3 agent ha

2016-08-31T08:31:07+00:00

New option enable_neutron_agent_ha added to enable/disable dhcp/l3 agent high availability, dhcp_agents_per_network is default to 2 and it's configurable. Implement blueprint: support-network-ha Change-Id: Id4742aa67c80584634b923195545bf2b654172f3

Add full support for fernet

2016-08-25T10:08:22+00:00

This addresses the ansible aspects of fernet key bootstrapping as well as distributed key rotation. - Bootstrapping is handled in the same way as keystone bootstrap. - A new keystone-fernet and keystone-ssh container is created to allow the nodes to communicate with each other (taken from nova-ssh). - The keystone-fernet is a keystone container with crontab installed. This will handle key rotations through keystone-manage and trigger an rsync to push new tokens to other nodes. - Key rotation is setup to be balanced across the keystone nodes using a round-robbin style. This ensures that any node failures will not stop the keys from rotating. This is configured by a desired token expiration time which then determines the cron scheduling for each node as well as the number of fernet tokens in rotation. - Ability for recovered node to resync with the cluster. When a node starts it will run sanity checks to ensure that its fernet tokens are not stale. If they are it will rsync with other nodes to ensure its tokens are up to date. The Docker component is implemented in: https://review.openstack.org/#/c/349366 Change-Id: I15052c25a1d1149d364236f10ced2e2346119738 Implements: blueprint keystone-fernet-token

add baremetal role to install kolla deps.

2016-08-10T16:03:08+00:00

Change-Id: Ie70db1b18a73528b1194e4fbcf53d09fed20f4a0 Implements: blueprint kolla-host