Re: public-address and dns of nodes are IPs instead of hostnames

This was introduced a while ago, not sure if on 1.25.5, but it also changed the behavior on AWS, where you used to get ec2-ip-address-here.country.availabilityzone.amazonaws.com, and now you get the public IP address. Someone else, maybe from the core team, may be able to give you a little bit

public-address and dns of nodes are IPs instead of hostnames

Hi everyone, I'm hitting an issue on one of my deployments. $ juju stat shows IP of a node as its public-address and dns that instead should have the hostname. I'm using juju version 1.25.5 and MAAS version 1.9.3 If i run $ maas nodes list it outputs the correct hostnames so I'm guessing there's

Juju plugins should start juju-

Landing in the next beta of Juju 2.0, plugins will not only have to start 'juju-' but the next character must be [a-zA-Z]. For details see: If you've written your own juju plugin, make sure it's named something that starts with a letter rather

Re: grabbing resources when deploying via api Application.Deploy

There is also a open bug about the inconsistency between the 'resources' facade and all other facades https://launchpad.net/bugs/1597519 On Wed, Jun 29, 2016 at 4:56 PM, Katherine Cox-Buday < katherine.cox-bu...@canonical.com> wrote: > > So just to follow up on our conversation in IRC: > > -

Re: grabbing resources when deploying via api Application.Deploy

So just to follow up on our conversation in IRC: - You do need to upload resource metadata prior to deploying a charm. You can do so via the "resources" facade, version 1. Call "AddPendingResources". - This will give you a list of IDs back; associate these in a map of resource-name -> id, and