Cloudify 3 is a major milestone for Gigaspaces. It tightens our integration with Openstack and steer the product architecture to closely match the Openstack architecture stack. There are several ways to get started with Cloudify 3 on Openstack; You may use an Openstack public cloud such as HP Cloud, your can use your organization own Openstack private cloud. There is an option to download a vagrant box that will let you bootstrap Cloudify inside a single VM. Finally, there is an option to run Devstack and use it as your own private cloud for bootstrapping Cloudify 3. Setting up and running Devstack is pretty straight forward and you can use the official quick guide as your reference: http://devstack.org/ You need to ensure that the computer running devstack has enough resources for the Devstack + 3 additional VMs running inside it (16GB ram is highly recommended, but 8 GB should work too) Please add an Ubuntu image (12.04 LTS is recommended) from the Ubuntu official cloud images (http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img ) to your new DevStack environment. Once devstack is installed, I recommend signing into it web UI and spawning a small Ubuntu instance as a validation that the installation was indeed successful. Next, go to the Cloudify web site at: http://getcloudify.org/downloads/get_cloudify_3x.html Choose the relevant Debian package (either 32 or 64 bit). Install the package:
dpkg –I ./ cloudify-cli_3.0.0-ga-b6_amd64.deb Next we will need to configure Cloudify to use its Openstack plugin for bootstrapping. It is recommended to do it in a dedicated folder:
mkdir cloudify_work cd Cloudify_work cfy init openstack Follow the steps on the Cloudify quickstart-openstack guide at http://getcloudify.org/guide/3.0/quickstart-openstack.html Devstack defaults for the cloudify-config.yaml: Next we will follow quick start guide steps. To verify the the bootstrapping succeeded after you ran the cty bootstrap command, you may run cfy status and get the IP of the Cloudify management node and a list of the running services on it. Before executing the blueprint upload step in the guide,there are a couple of environment changes to the blueprint.yaml to match our Devstack environment: Once you are done with the steps in the quick guide, you can view the node-cellar deployment also from you Devstack horizon UI. You will see there the two VMs that were provisioned in addition to the Cloudify management VM.
There we are, Node-cellar is deployed and you can use it as a reference to building and running your own blueprints.
Transmissions for sa… on GigaSpaces Cloudify & Open…