You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 8, 2018. It is now read-only.
Blimpy's OpenStack support was developed against an "Essex" cluster, and thus far is only know to work against that release of OpenStack.
Using
In order to spin up a machine on the OpenStack cluster, you need to use the :openstack argument when invoking fleet.add, e.g.:
# vim: ft=ruby# Blimpfile created on 2012-05-07 14:05:41 -0700Blimpy.fleetdo |f|
f.add(:openstack)do |ship|
ship.name="blimpy-dev"ship.region='test'# name of the 'tenant' to useship.image_id='ebd0b126-c841-4a78-ae68-f3690a4b8b7e'# preciseship.flavor='m1.small'ship.livery=Blimpy::Livery::Puppetendend
Notes
Blimpy will allocate and associate a floating IP address for every machine it spins up. When the machine is destroyed, Blimpy will disassociate and release the floating IP.
Blimpy will use the "native" Nova API, it will not use the openstack-ec2 style API.