Implement ansible role to deploy designate
and dependencies. The backend used is bind9.
Co-Authored-By: zhubingbing <zhubingbing10@gmail.com>
Co-Authored-By: Eduardo Gonzalez <dabarren@gmail.com>
Depends-On: 6d0dc3e0f931c7c50b64a4659900cc50b0d860a2
Implements: blueprint ansible-designate
Change-Id: I34d8126e0cd8d71d5ced9b62f3776cc354fbb549
* the roles field is lost when implementing. This patch adds the field
* add enable_octavia example in globas.yml file
Change-Id: I94c33f78afafc903779c9f3bdb051fca39206211
Implements: blueprint octavia-ansible-role
If an operator wants to deploy a single node (e.g. add an additional
compute), they may want to use the --limit feature of Ansible to avoid
waiting for every play across every node.
The problem with this is that --limit will gather facts for that node
only, causing template errors such as the infamous ('dict object' has no
attribute u'ansible_eth0'").
Ansible has catered to this problem to an extent with it's
"delegate_facts" mechanism. The only problem is that in the default 'all
nodes' case, we end up with a storm of SSHs as each node SSHs to every
other. I'm solving this with a separate task to only use this mechanism
when a subset of nodes has been specified (see ansible_play_batch).
Useful links on this subject:
- https://medium.com/@george.shuklin/perfecting-forced-fact-gathering-in-ansible-1611f9c8d0d5#.tr5zs3e7x
- http://docs.ansible.com/ansible/playbooks_delegation.html#delegated-facts
Change-Id: Ibb691eae15cacd9e5129ae9280fd296f5ba95940
Closes-Bug: 1642004
Searchlight is an Openstack search and index service, this patch
implements the ansible role for searchlight.
Implement blueprint: support-searchlight-deployment
Change-Id: Ibf42d5b259a6740d6596041f896e1009657b7388
nova-ironic-compute will try to connect ironic-api service. So ironic
should be started first.
TrivialFix
Change-Id: I23ba5724d86e3b7a06f7f7d112ee1ac84a2cda03
In cf0c25c37 [0] a play was added to run the common role against all
hosts. This ends up being redundant since every role includes the common
role as a dependancy. The reasoning behind this change as pointed out by
the author in the review comments [1] was so that an operator could run
with '--tags common' and just have the common role applied.
To avoid redundancy, the common play has been removed and tags have been
added to the common role. This allows for just the common role to run
when another role is including it while reducing redundancy.
A side affect of removing the common playbook which runs against all
hosts is that not all facts on all hosts are gathered at the beginning
of the site.yml. This breaks the haproxy role since it relies heavily on
facts to build out the haproxy.cfg file.
Previously, the haproxy role would include several hosts purely for fact
gathering purposes as pointed out in c68c9d95 [2] and a guard was put in
place so that the tasks would only run against the 'haproxy' group. In
423e3f3f [3] these hosts were removed. After reading the review [4],
this seems to have been done without fully understanding why the hosts
were there in the first place.
This change did not break anything however since the common role that
ran on all hosts mentioned previously would gather all of the facts
necessary.
To fix this fact gathering issue replace the common role play with a
play that will simply gather facts with an 'always' tag to ensure it is
run regardless of what might be passed in the '--tags' argument by the
operator.
Kudos to Paul Bourke for helping identify many of these issues.
[0] cf0c25c37d
[1] https://review.openstack.org/#/c/369212/
[2] c68c9d95fc
[3] 423e3f3fdf
[4] https://review.openstack.org/#/c/355861
TrivialFix
Closes-Bug: #1628472
Change-Id: Ia94146579e743935501f1ff4b4c1bf6cb7c43aa3
By having serial in site.yml for these roles will mean (particularly
during an upgrade) that tasks can be executed out of the intended
order across hosts, leading to unexpected results.
Change-Id: I44f0c66c445d853a2e4af69119562f13b4424936
Closes-Bug: #1626096
Currently Cinder enables iscsid service only when LVM is choosen as
backend. This fix will allow to specify external iSCSI storage via
configuration add-on and to run iscsid independently of LVM settings.
Change-Id: Iaae0f8025534e5ab1c5f9d5e812a7d41129915ef
Closes-Bug: 1614125
* add serial for reconfigure
* set playbook serial by using variable
* fix serial for barbican, influxdb and vmtp
Closes-Bug: #1624607
Change-Id: I66530c7736e1673a592eddbde75637825d12d9e2
Added ansible role to deploy telegraf
Roll out telegraf to all nodes
Introduce parameter to toggle deployment of performance monitoring
Co-Authored-By: zhubingbing <zhubingbing10@gmail.com>
Change-Id: Ia09b20ce65bf557c1a1030eda99df5cc88debd01
Partially-Implements: Blueprint performance-monitoring
Add vmtp ansible role to kolla.
Co-Authored-By: Larry Rensing <lr699s@att.com>
Co-Authored-By: Tin Lam <tinlam@gmail.com>
Partially implements: bp vmtp-container
Change-Id: Ib3945e0a94cca9f3a8c4f55953b40674c88ac8e4
Added ansible role to deploy grafana
Added host group for grafana deployment
Co-Authored-By: zhubingbing <zhubingbing10@gmail.com>
Change-Id: I3dec4e8586b6f65fa7de66a48506d1c79de2fe1e
Partially-Implements: Blueprint performance-monitoring
We use hosts detective in wrong. No need add the other hosts we do not
need in the role.
TrivialFix
Change-Id: I2d228704cd76fc59f590497e33e1b89f397c0e3c
Signed-off-by: Jeffrey Zhang <zhang.lei.fly@gmail.com>
Useful for upgrade etc., which is preferablly done serially.
Example usage: tools/kolla-ansible deploy OR tools/kolla-ansible upgrade
Closes-Bug: #1576708
DocImpact
Change-Id: I34b2e16f8ce53e472a4682a4738c4ac0f5abf00c
Collectd-ceilometer-plugin is essential for further
more detailed metrics collection, smarter scheduling and service
assurance.
Change-Id: I8da572980de370517ec120d745ad1d36e316b465
Implements: blueprint collectd-ceilometer-plugin
