OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|2 months ago|
|deployment_scripts/puppet||3 years ago|
|doc||3 years ago|
|repositories||3 years ago|
|specs||3 years ago|
|test||3 years ago|
|wip||3 years ago|
|.gitignore||3 years ago|
|.gitreview||2 months ago|
|LICENSE||3 years ago|
|README.md||3 years ago|
|environment_config.yaml||3 years ago|
|metadata.yaml||3 years ago|
|pre_build_hook||3 years ago|
|tasks.yaml||3 years ago|
This is an working implementation for a plugin that will install calamari console for ceph on a os-base node with fuel.
The =fuel-camari-plugin= installs the following packages:
A simple install script tested with the default values of the virtualbox script is available once the plugin is installed. It requires a clean environment with at least 4 unallocated nodes.
Run with the following:
cd /var/www/nailgun/plugins/fuel-plugin-calamari-1.0/test/ ./simple-install
The following commands may be helpful:
# On the controllers and ceph-osd nodes puppet apply --debug \ --modulepath=/etc/fuel/plugins/fuel-plugin-calamari-1.0/puppet/modules:/etc/puppet/modules \ /etc/fuel/plugins/fuel-plugin-calamari-1.0/puppet/manifests/calamari-agent.pp # On the calamari node puppet apply /etc/puppet/modules/osnailyfacter/modular/netconfig/netconfig.pp puppet apply --debug \ --modulepath=/etc/fuel/plugins/fuel-plugin-calamari-1.0/puppet/modules:/etc/puppet/modules \ /etc/fuel/plugins/fuel-plugin-calamari-1.0/puppet/manifests/calamari-server.pp
Here is the diff in /etc:
diff --git a/ceph/ceph.conf b/ceph/ceph.conf index 17c676a..cf2f502 100644 --- a/ceph/ceph.conf +++ b/ceph/ceph.conf @@ -1,4 +1,5 @@ [global] +osd crush location hook = /usr/bin/calamari-crush-location fsid = 783fcc91-e95d-4ce3-b9c2-0a414a4751d3 mon_initial_members = node-1 mon_host = 192.168.0.3 diff --git a/default/diamond b/default/diamond index deda518..c936044 100644 --- a/default/diamond +++ b/default/diamond @@ -9,4 +9,4 @@ # Additional options that are passed to the Daemon. ENABLE_DIAMOND="yes" DIAMOND_PID="/var/run/diamond.pid" -DIAMOND_USER="diamond" +DIAMOND_USER="root"
Do the conf changes will step over puppet? How can we manage salt and puppet to not step on each other?
Figure out how to do proper testing and CI (we do not have hardware resources for this)
Reproducible build of the packages included in the plugin.
UI: Does make sense to enable the plugin only if there is some ceph depoyed?
What happens in case of node ceph node addition? What happens in case of node ceph node removal?
The puppet code is executed in the new node. But not on the calamari server. This blueprint addressed the problem: