- All Ceph instances now communicate using public subnet and
additionally OSDs communicate with each other using private cluster
subnet
- Workaround for
https://github.com/vagrant-libvirt/vagrant-libvirt/issues/645
- Fix for #952 to avoid concatenated MAC addresses caused by
vagrant-libvirt bug.
This enables running multiple clusters concurrently in the same Linode
account. Linode does not allow machines to have the same label.
Signed-off-by: Patrick Donnelly <pdonnell@redhat.com>
Other things of note:
o You can now set the ceph branch to test against in
vagrant_variables.yml.
o You can now set the ceph_conf_overrides in vagrant_variables.yml.
This commit depends on an open PR:
https://github.com/displague/vagrant-linode/pull/66
Until that is merged, you must copy the changed file to your copy
of the vagrant-linode plugin, e.g.:
cp lib/vagrant-linode/actions/create.rb ~/.vagrant.d/gems/gems/vagrant-linode-0.2.7/lib/vagrant-linode/actions/create.rb
Signed-off-by: Patrick Donnelly <pdonnell@redhat.com>
use the activation scenario instead of the full ceph_disk one, we
already have a task to prepare osds so we just need to activate the
device.
working for me using vagrant :)
Signed-off-by: Sébastien Han <seb@redhat.com>
There is no need to run the actions from
roles/ceph-mon/tasks/docker/create_configs.yml
on the first monitor only since the monitor deployment happens
**serially**.
Moreover with Vagrant it's useful to allow the auto creation of the
cluster fsid, so enabling the option. If this is not desired you can
still set `fsid: 9c9c0448-0551-401d-b55b-e5b3a42bae42` for example.
Signed-off-by: Sébastien Han <seb@redhat.com>
Ceph has the ability to export it's filesystem via NFS using Ganesha.
Add a ceph-nfs role that will start Ganesha and export the Ceph
filesystems.
Note that, although support is going in to export RGW via NFS, this is
not working yet.
Signed-off-by: Daniel Gryniewicz <dang@redhat.com>
Vagrant has the ability to download images from an arbitraty URL. Add
this support to the Vagrantfile and vagrant_varables.yml
Signed-off-by: Daniel Gryniewicz <dang@redhat.com>
When running via Vagrant, rather than always starting RESTAPI on each
monitor, make it optional via a configuration option in
vagrant_variables.yml.
Signed-off-by: Daniel Gryniewicz <dang@redhat.com>
now with vagrant, you can either enable ceph_stable or ceph_dev
depending on what you're looking to test.
Signed-off-by: Sébastien Han <seb@redhat.com>
run containerized daemons in virtual machines.
to enable it simply do:
`cp site-docker.yml.sample site-docker.yml`
and set `docker: true` in `vagrant_variables.yml`
Signed-off-by: Sébastien Han <seb@redhat.com>
We want to force the user to only enable the options they need. Thus
they shouldn't have to enable one option and then disable another.
Signed-off-by: leseb <seb@redhat.com>
Now we don't need to activate the services through a variable. If the
role is activated in the inventory, actions will occur automatically.
Fixing the repo creation for red hat storage too.
Signed-off-by: leseb <seb@redhat.com>
* fix the Vagrantfile ruby check
* fix the variable positions
Bring more mandatory variables and try to separate Vagrant vars from the
playbook vars.
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
The box can be configured thanks to a new var, look at vagrant_variables
and select your box.
Handy to test several distros deployment.
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
This is really handy when we are testing code since we don't need to
modify the Vagrantfile, which is tracked by git.
The next commit will ignore the vagrant_variables.yml file.
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
When enabling radosgw virtual machines, we also need to enable the
radosgw variable. Same thing goes with the mds.
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>
The recently added Trusty box was build with a Controller named
"SATAController", we must reuse the same name while adding our devices.
Signed-off-by: Sébastien Han <sebastien.han@enovance.com>