How to get private-address in juju status output?

[Martin Packman]

On 27/11/2013, Andreas Hasenack <andreas at canonical.com> wrote:
> Hi,
>
> I have an instance on openstack (canonistack) that got a floating ip, and
> that address is now showing as public-address. I guess that's ok.

As discussed on IRC, this is the expected behaviour, though with the
limited details juju currently exposes it is surprising. For clouds
that do not hand out public ip addresses by default, juju falls back
to using a private 10. address or whatever is available. When you add
the floating ip, it realises that is in fact a public address and
starts returning that instead.

> Except it's not reachable via ssh anymore (nor juju ssh). For some reason
> (bug? deployment issue?) public addresses are not routeable from within
> that cloud itself. You have to use the private address.

That does seem like a bug, either in the cloud or possibly your ssh config.

> So, how do I get the private address in the juju status output?

Some changes still need to land to make that possible. The internal
model now understands machines can have a variety of addresses
associated, and tracks information about them beyond the rather
artifical public/private split. The tricky part is we need to get that
information into `juju status` without breaking existing tools that
expect the current forms or bloating the output too much.

Martin