orchestrate-devstack: Copy controller ceph.conf and keyrings to subnode
This change introduces a basic role to copy the contents of /etc/ceph between the controller and subnodes during orchestrate-devstack allowing a multinode ceph job to be introduced by I9ffdff44a3ad42ebdf26ab72e24dfe3b12b1ef8b. Note that this role is only used when devstack-plugin-ceph is enabled. Change-Id: I324c0f35db34f8540ca164bf8c6e3dea67c5b1b4
This commit is contained in:
parent
aef50ed18c
commit
e11d367d8e
@ -18,6 +18,11 @@
|
|||||||
name: sync-devstack-data
|
name: sync-devstack-data
|
||||||
when: devstack_services['tls-proxy']|default(false)
|
when: devstack_services['tls-proxy']|default(false)
|
||||||
|
|
||||||
|
- name: Sync controller ceph.conf and key rings to subnode
|
||||||
|
include_role:
|
||||||
|
name: sync-controller-ceph-conf-and-keys
|
||||||
|
when: devstack_plugins is defined and 'devstack-plugin-ceph' in devstack_plugins
|
||||||
|
|
||||||
- name: Run devstack on the sub-nodes
|
- name: Run devstack on the sub-nodes
|
||||||
include_role:
|
include_role:
|
||||||
name: run-devstack
|
name: run-devstack
|
||||||
|
3
roles/sync-controller-ceph-conf-and-keys/README.rst
Normal file
3
roles/sync-controller-ceph-conf-and-keys/README.rst
Normal file
@ -0,0 +1,3 @@
|
|||||||
|
Sync ceph config and keys between controller and subnodes
|
||||||
|
|
||||||
|
Simply copy the contents of /etc/ceph on the controller to subnodes.
|
15
roles/sync-controller-ceph-conf-and-keys/tasks/main.yaml
Normal file
15
roles/sync-controller-ceph-conf-and-keys/tasks/main.yaml
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
- name: Ensure /etc/ceph exists on subnode
|
||||||
|
become: true
|
||||||
|
file:
|
||||||
|
path: /etc/ceph
|
||||||
|
state: directory
|
||||||
|
|
||||||
|
- name: Copy /etc/ceph from controller to subnode
|
||||||
|
become: true
|
||||||
|
synchronize:
|
||||||
|
owner: yes
|
||||||
|
group: yes
|
||||||
|
perms: yes
|
||||||
|
src: /etc/ceph/
|
||||||
|
dest: /etc/ceph/
|
||||||
|
delegate_to: controller
|
Loading…
Reference in New Issue
Block a user