consistent private/public ip accessors (thanks abecc)

[geemus]

for instance AWS servers have private_ip_address and ip_address

but Rackspace servers have addresses['public'] and addresses['private'](which are arrays)

array vs single value may need to be reconciled and naming should be unified

private_ip_address and public_ip_address would probably be good as the accessors

So other stuff will need to be updated and/or deprecated as appropriate to allow for this

You may want to talk to geemus before tackling this, because it could be a bit hairy. Otherwise I'll get to it eventually.

[geemus]

This shouldn't be too crazy I don't think.

For each server model we just want to have #public_ip_address and #private_ip_address.

If there happens to be more than one just return the primary one, or the first one if there is no clear primary one. If for some reason there is no ip address for one option or the other this call should simply return nil.

Shared server tests should also be updated to ensure that the model responds_to both of the previously mentioned methods.

[joakimk]

I'd like to see this, but I also want it to allocate IP's when needed.

For Brightbox there is no public IP by default, so you have to create or reuse an existing cloud_ip with a few additional API calls.

What I would want is essentially this:
compute = Fog::Compute.new({ ... any provider conf ...})
server = compute.servers.create({ .. })
ssh(server.public_ip, ...)

(How I do this now: https://github.com/joakimk/testbot_cloud/blob/master/lib/server/brightbox.rb).

[geemus]

I can definitely see how that would be useful. But I think it is outside of scope for this particular ticket. It would make sense to have this functionality as a part of the 'bootstrap' command though, I think.

[geemus]

[compute] consolidate ip accessors

closed by 9a40a17