Closed swiftgist closed 5 years ago
If everyone agrees on the change to policy.cfg and this overall direction, I'll look to complete the calls to the network parts of the DeepSeaGlobal class.
An example policy.cfg
role-master: admin*
role-admin: mon*
role-igw: igw*
role-rgw: rgw*
role-mon: mon*
role-mds: mds*
role-mgr: mon*
rgw:
role-red: rgw*
role-blue: rgw*
ganesha:
role-alpha: ganesha1*
role-beta: ganesha2*
role-client-cephfs: client1*
role-client-radosgw: client1*
role-client-iscsi: client1*
role-client-nfs: client1*
role-benchmark-rbd: client2*
role-benchmark-blockdev: client2*
role-benchmark-fs: client2*
If everyone agrees on the change to policy.cfg and this overall direction, I'll look to complete the calls to the network parts of the DeepSeaGlobal class.
This sounds like the right direction to me!
This sounds like the right direction to me!
Likewise :-)
besides the linter complaints, shall we merge this and #1728 together?
Fine with me... the last couple of linter complaints I was undecided on.
I fear we have to rebase here
okay.... give me a bit... still resolving some other issues.
rebased... we need to chat about Salt config vs. Ceph config
The original configuration uses stack.py and supports individual minion customizations. With a default and user pillar directory tree, this led to confusion for many more than once.
This strategy abandons using stack.py and the custom trees. Instead of file globbing, values of policy.cfg become Salt targets. The roles are generated the same without the intermittent files. Lastly, the global.yml moves out of the stack directory and is only initialized. The global.yml is still a user maintained file.
Signed-off-by: Eric Jackson ejackson@suse.com
Fixes #
Description:
Checklist: