rtyler / blimpy Goto Github PK

We'll need this in the "future" to verify that the machine we SSH into is the right machine

The :puppet livery should bootstrap Puppet onto the machine and provide the same workspace copying that the :cwd currently does.

This will probably require some amount of thought on how to properly configure liveries

I think the Fleet object should become the manager coordinator of multiple ships, etc

Instead of running one machine after the other, we should start the provisions in parallel

We're not ignoring host key validation on the rsync for a :cwd livery, which can break on openstack

"The Blimpfile is invalid!" Fuck you, what's wrong with it?

Currently an Blimpy::InvalidBlimpFileError is raised :(

To make the blimpy ssh command as seamless as possible. Whenever a blimpy start is called, and new hosts are created, we should generate a new key pair for the machines in ever region there are machines

Basically a file with a bunch of rsync ignores for things that don't need to be sent to the machine

To make the blimpy ssh command as seamless as possible. Whenever a blimpy start is called, and new hosts are created, we should generate a new key pair for the machines in ever region there are machines

There's no need for the Fleet to have that level of access

Whoops

For puppet specifically, being able to overwrite the manifest file and the module path would be handy

FreeBSD images default to root logins and don't have sudo installed by default.

SMOOTH MOVE FERGUSON

I can see it making sense to have something like this in your Blimpfile:

Blimpy.fleet do |f|
  f.add do |s|
    s.cloud :aws
    s.name 'amazon'
  end
  f.add do |s|
    s.cloud :openstack
    s.name 'private'
  end
end

We're tagging machines, but we're not storing it in ./.blimpy.d/.

We probably should, then we may be able to use that to help validate management parts

This naming scheme is getting silly

Currently failing in BuildHive due to this issue.

Over SSH naturally!

Doesn't generate the right calls to invoke an AWS box, regression since #17

Having something like:

fleet.add do |ship|
  ship.open_ports [22, 80]
end

Instead of requiring a security group to be set up by default would be handy

Since symbols (:cwd) are deprecated, they should fail the Blimpfile at validation instead of inside of #bootstrap_livery

This one's going to hurt.

Despite the setting theoretically being us-west-2

On FreeBSD hosts they do not have rsync installed by default, rats.

Fucking AWS, how does it work

Hi,

I'm using blimpy with Ruby 1.9 and when I run blimpy start after adding a new ship, I get this:

Resuming: ,/usr/local/lib/ruby/gems/1.9/gems/blimpy-0.4.3/lib/blimpy/fleet.rb:61:in block in resume': undefined methodresume' for nil:NilClass (NoMethodError)

Is this a ruby 1.9 issue or a more general bug?

Thanks,
Steve

Note to self

fail

It'd be useful to know what VMs will come online when the blimpy start command is invoked