Skip to content

Latest commit

 

History

History
74 lines (56 loc) · 3.6 KB

README.md

File metadata and controls

74 lines (56 loc) · 3.6 KB
Raw

Summary - vagrant-puppet-scaleio

This repository houses a Vagrantfile and Puppet configuration files that allow you to deploy and scale-up/out a ScaleIO storage environment. It makes use of the puppet-scaleio module to perform all of the configuration and Vagrant to deploy a Puppet Master, configure Puppet with ScaleIO module, and then deploy additional defined ScaleIO nodes.

With this Vagrantfile, it is possible to deploy pre-defined ScaleIO clusters. Further, the ScaleIO puppet module allows you to deploy massive descriptive ScaleIO clusters across any environment, physical or virtual in minutes.

ScaleIO Downloads A new feature of this Vagrantfile is to download the latest ScaleIO RPM's automatically. This is done automatically and can be disabled by editing the Vagrantfile and commenting out download_scaleio.

Instructions

  • git clone -b docker_1.7rc3_experimental_rexray https://github.com/emccode/vagrant-puppet-scaleio.git
  • cd vagrant-puppet-scaleio
  • vagrant up
  • vagrant ssh mdm1
  • sudo su
  • rexray get-instance
  • rexray new-volume --volumename=testing1 --size=8 (test rexray with new-volume)
  • docker run --volume-driver=rexray -ti -v newvol:/newvol busybox (create another volume directly from docker)
  • touch /newvol/test
  • exit (exit from container)
  • exit (exit from mdm1)
  • vagrant ssh mdm2
  • sudo su
  • docker run --volume-driver=rexray -ti -v newvol:/newvol busybox (attach volume to anther OS and container)
  • ls /newvol (look for test file)

Puppet Module Repository

For reference you can review the Puppet module repos at Github and Puppet Forge.

Puppet Module Features

  • Puppet Agent installs proper RPMs for components
  • Configures firewall settings
  • Sets required OS kernel SHM settings
  • Sets /dev/shm temporary fs size
  • Multiple component types per node (Tie-Breaker, MDM, SDS, SDC, GW, LIA, Call-Home)
  • Configures MDM cluster services
  • Configure multiple Protection Domains with Storage Pools
  • Configure Storage Pools
  • Multiple devices per SDS with per node definition of device paths, device size, storage pool
  • Add Devices to SDSs
  • Add Volumes
  • Map Volumes to SDCs

Documentation
Read The Docs

Contributors/Sources

  • Eoghan Kelleher
  • Jonas Rosland
  • Clint Kitson

Contributing
We encourage the community to actively contribute to this module.

  • Fork the repository
  • Clone
  • Add original repository as upstream
  • Checkout new branch
  • Commit changes
  • Push to your repository
  • Issue pull request

Licensing
Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Support
Please file bugs and issues at the Github issues page. For more general discussions you can contact the EMC Code team at Google Groups. The code and documentation are released with no warranties or SLAs and are intended to be supported through a community driven process.