Add hosts range “192.168.124.[81:83] ansible_ssh_user=root” to the
If you are really lazy, add “[Default] // host_key_checking = False” to your “~/.ansible.cfg” file
now ping the hosts, “ansible all -m ping”
pat yourself on the back, you’re done.
to show off:
touch all machines “ansible all -a “/bin/echo hello”
look at types of Linux “ansible all -a “uname -a”
Further integration work can make this even more powerful.
I’d like to see OpenCrowbar generate the Ansible inventory file from the discovery data and to map Ansible groups from deployments. Crowbar could also call Ansible directly to use playbooks or even do a direct hand-off to Tower to complete an install without user intervention.
RAID – Automatically set RAID configuration parameters depending on how the system will be used.
Support for LSI controllers
Single and Dual RAID configuration
BIOS – Automatically set BIOS settings depending on how the system will be used.
Configuration setting for Dell PE series systems
Out of Band Support- Configure and manage systems via their OOB interface
Support for IPMI and WSMan
RPM Installation (it riseth again!) – Install OpenCrowbar via a standard RPM instead of a Docker container
SaltStack integration – OpenCrowbar can install SaltStack as a configuration tool to take over after “Ready State”
Chef Provisioning (was Chef Metal) – OpenCrowbar driver allows Chef to build clusters on bare metal using the Crowbar API.
Automated smoke test and code coverage analysis for all pull requests.
And…v2.1 is the first release with commercial support!
RackN (rackn.com) offers consulting and support for the OpenCrowbar v2.1 release. The company was started by Crowbar founders Greg Althaus, Scott Jensen, Dan Choquette, and myself specifically to productize and extend Crowbar.
I had a question about moving barclamps between solutions. Since Victor just changed the barclamp build to create a tar for each barclamp (with the debs/rpms), I thought it was the perfect time to explain the new feature.
You can find the barclamps on the Crowbar ISO under “/dell/barclamps” and you can install the TAR onto a Crowbar system using “./barclamp_install foo.tar.gz” where foo is the name of your barclamp.
Here’s a video of how to find and install barclamp tars:
Note: while you can install OpenStack into a Hadoop system, that combination is NOT tested. We only test OpenStack on Ubuntu 10.10 and Hadoop on RHEL 5.7. Community help in expanding support is always welcome!
Since some of you cannot make it to the show and see the demo in person, we’ve captured it as a video for your enjoyment. The OpenStack deployment is available in our open source distribution. We are currently in QA for the overall solution so expect additional refinement as we progress towards our next OpenStack solution release.
REMINDER: Dell Hardware is NOT required to use Crowbar for OpenStack. The open source version has everything you need – the BIOS and RAID barclamps are optional (but handy).
These Crowbar videos are the first two in a series of how to setup and use your own local Crowbar dev environment (here’s more info & the ISO). I used VMware Workstation, but any virtual hosts that support Ubuntu 10.10 will work fine. We use ESX, KVM and Xen for testing too.
Creating this environment is the basis for learning Crowbar, experimenting with OpenStack and creating your own barclamps. It’s also a handy way to play with Opscode Chef since it includes a stand alone Chef server.
Some items from the install video that I want to re-emphasize:
The admin server REQUIRES >1 GB of RAM (more is better)
All other nodes REQUIRE > 512 MB of RAM (more depending on what you install)
At least TWO NICS are required.
You must disable DHCP on the virtual network because Crowbar has a DHCP server and they will conflict.
The login for the Crowbar admin server is openstack/openstack. You must “sudo -i” before you run the install script.