MAAS provider returns the hostname to juju

[Diogo Matsubara]

MAAS returns the hostname to juju and when you run juju status you get a message like:

$ juju status
2012-08-31 12:12:38,425 INFO Connecting to environment...
2012-08-31 12:12:44,211 ERROR Invalid host for SSH forwarding: ssh: Could not resolve hostname node-00e081ddd10b.local: Name or service not known

It could instead return the IP address of the node.

For reference, the juju bug to fix this issue is bug 945505.

[Julian Edwards (julian-edwards)]

Before we land this change, that bug needs to be fixed. It has had a pending merge proposal since 2012-08-10 which need to be released.

However, it's fairly horrible to just fix this bug and release because it will break older juju clients that need a hostname. Needs some more thought.

[Jeroen T. Vermeulen (jtv)]

There are several problems to be solved: the "acquire" API call returns a Node. We'd need to add an IP-address field to that, and then I guess the juju machine provider will have to decide when to use the hostname and when to use an IP address. ("An" because a node may have several). We can't just always use IP addresses because we won't know the IP address if we're not managing DHCP.

It may not be desirable to add the IP addresses to all representations of Nodes returned by the API, because it involves querying extra tables. So we'd have to do something unusual like: create a JSON representation of the node that's similar to what the API would return, but add an IP field ourselves.

[Julian Edwards (julian-edwards)]

As discussed with Francis, won't-fix since there are too many problems surrounding this proposal.