Re: Juju Openstack - Blocked

[Junaid Ali]

Hi James,

Have you checked neutron-server.log in neutron-api and nova-scheduler.log
in nova-cloud-controller?


--
Junaid

On Thu, Feb 15, 2018 at 1:21 AM, James Beedy  wrote:

> Hello,
>
> I am experiencing some issues with a base-openstack deploy.
>
> I can get a base-openstack to deploy legitimately using MAAS with no
> apparent errors from Juju's perspective. Following some init ops and the
> launching of an instance, I find myself stuck with errors I'm unsure how to
> diagnose. I upload an image, create my networks, flavors, and launch an
> instance, and see the instance erring out with a "host not found" error
> when I try to launch them.
>
> My nova/ceph node and neutron node interface configuration [0] all have a
> single flat 1G mgmt-net interface configured via MAAS, and vlans trunked in
> on enp4s0f0 (untracked by maas).
>
>
> Looking to the nova logs, I find [1] [2]
>
>
> The bundle I'm using [3] is lightly modified version of the openstack base
> bundle [4] with modifications to match my machine tags and mac addresses
> for my machines.
>
> I've gone back and forth with network and charm config trying different
> combinations in hope this error is caused by some misconfiguration on my
> end, but I am now convinced this is something outside of my scope as an
> operator, and am hoping for some insight from the greater community.
>
> I seem to be able to reproduce this consistently (using both Juju < 2.3.2
> and 2.3.2).
>
> Not even sure if I should create a bug somewhere as I'm not 100% sure this
> isn't my fault. Let me know if additional info is needed.
>
>
> Thanks,
>
>
> James
>
>
>
> [0] https://imgur.com/a/x62m9
> [1] cat /var/log/nova/nova-api-metadata.log |
> http://paste.ubuntu.com/p/cTSjjRnHQ8/
> [2] cat /var/log/nova/nova-compute.log | http://paste.ubuntu.com/p/YFnM
> s93xhG/
> [3] https://paste.ubuntu.com/p/8hsQnmFYh4/
> [4] https://github.com/openstack-charmers/openstack-bundles/blob
> /master/stable/openstack-base/bundle.yaml
>
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/listinfo/juju-dev
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Juju Openstack - Blocked

[Junaid Ali]

Hi James,

Have you checked neutron-server.log in neutron-api and nova-scheduler.log
in nova-cloud-controller?


--
Junaid

On Thu, Feb 15, 2018 at 1:21 AM, James Beedy  wrote:

> Hello,
>
> I am experiencing some issues with a base-openstack deploy.
>
> I can get a base-openstack to deploy legitimately using MAAS with no
> apparent errors from Juju's perspective. Following some init ops and the
> launching of an instance, I find myself stuck with errors I'm unsure how to
> diagnose. I upload an image, create my networks, flavors, and launch an
> instance, and see the instance erring out with a "host not found" error
> when I try to launch them.
>
> My nova/ceph node and neutron node interface configuration [0] all have a
> single flat 1G mgmt-net interface configured via MAAS, and vlans trunked in
> on enp4s0f0 (untracked by maas).
>
>
> Looking to the nova logs, I find [1] [2]
>
>
> The bundle I'm using [3] is lightly modified version of the openstack base
> bundle [4] with modifications to match my machine tags and mac addresses
> for my machines.
>
> I've gone back and forth with network and charm config trying different
> combinations in hope this error is caused by some misconfiguration on my
> end, but I am now convinced this is something outside of my scope as an
> operator, and am hoping for some insight from the greater community.
>
> I seem to be able to reproduce this consistently (using both Juju < 2.3.2
> and 2.3.2).
>
> Not even sure if I should create a bug somewhere as I'm not 100% sure this
> isn't my fault. Let me know if additional info is needed.
>
>
> Thanks,
>
>
> James
>
>
>
> [0] https://imgur.com/a/x62m9
> [1] cat /var/log/nova/nova-api-metadata.log |
> http://paste.ubuntu.com/p/cTSjjRnHQ8/
> [2] cat /var/log/nova/nova-compute.log | http://paste.ubuntu.com/p/YFnM
> s93xhG/
> [3] https://paste.ubuntu.com/p/8hsQnmFYh4/
> [4] https://github.com/openstack-charmers/openstack-bundles/blob
> /master/stable/openstack-base/bundle.yaml
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/listinfo/juju-dev
>
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Juju 2.3 beta2 is here!

[Junaid Ali]

Good to see the much-awaited bundle specific changes. A big thumbs up to
Juju Dev team!


On Thu, Nov 2, 2017 at 9:56 AM, Chris Lee  wrote:

> A new development release of Juju is here, 2.3-beta2.
>
> ## New and Improved
>
> * Deploying bundles now supports --dry-run
>
> With --dry-run, no changes are made to the model, but what would be done
> is output. The new machine numbers and unit numbers take into account the
> current model. The --dry-run flag can also be used to apply changes made to
> a bundle since it had been deployed.
>
> * Deploying bundles can now target existing machines
>
> When deploying bundles, machines specified in the bundle are added to the
> model as new machines. In order to use the existing machines in the model
> rather than create new machines, the --use-existing-machines flag can be
> used. To specify a particular machine, the --bundle-machine flag can be
> used to specify a specific machine for  a particular machine in the bundle.
> These flags can be combined with the --bundle-machine flag taking
> precidence. For example, if there was a bundle that specified machines 1,
> 2, and 3, and the model had machines 1, 2, 3 and 4, the following
> deployment of the bundle would use machines 1 and 2 in the model for
> machines 1 and 2 in the bundle and use machine 4 in the model for the
> bundle machine 3.
>
>juju deploy some-bundle --use-existing-machines --bundle-machine 3=4
>
> * OpenStack Cinder storage provider now supports “volume-type”
>
> https://bugs.launchpad.net/juju/+bug/1719323
>
> The “cinder” storage provider now supports a “volume-type” pool
> configuration. You can create a pool using “juju create-storage-pool”,
> specifying the name of an OpenStack Cinder volume type.
>
> * Cross model relations now supports nagios in its own [controller:]model
>
> The nagios and nrpe charms are updated to be cross model relations aware.
> This means they work in either a single model or cross model scenario. For
> now, the charms are available at cs:~wallyworld but will be published to
> the store soon.
>
> juju bootstrap aws
>
> juju switch controller
>
> juju deploy cs:~wallyworld/nagios
>
> juju expose nagios
>
> juju offer nagios:monitors
>
> juju switch default
>
> juju deploy ubuntu
>
> juju deploy cs:~wallyworld/nrpe
>
> juju add-relation ubuntu nrpe
>
> juju add-relation nrpe:monitors controller.nagios
>
> - get the public IP of nagios and load it in the browser
>
> - username is nagiosadmin
>
> - password can be found by this command on the nagios model:
>
> juju ssh nagios/0 sudo cat /var/lib/juju/nagios.passwd
>
> * open_port and close_port hook tools now support ICMP
>
> The open_port and close_port hook tools now support opening firewall
> access for ICMP. The syntax is:
>
> open_port icmp
>
> This was needed for the (new) nrpe charm when used in a cross model
> scenario, so that the remote nagios application could access the nrpe
> subordinate in another model.
>
> The necessary charm helpers change has not yet landed upstream - it is for
> now just contained in the cs:~wallyworld/nrpe charm. But the Juju support
> is there so charms can shell out to call open_port directly if needed,
> until charm helpers is updated.
>
> * Cross model relations now supports prometheus in its own
> [controller:]model
>
> The prometheus and telegraf charms are updated to be cross model aware.
> This means they work in either a single model or cross model scenario. For
> now, the charms are available at cs:~rharding but will be published to the
> store soon.
>
> juju bootstrap google bigbrother
>
> juju bootstrap aws monitorme
>
> juju switch bigbrother
>
> juju deploy cs:~rharding/prometheus-0
>
> juju expose prometheus
>
> juju offer prometheus:target offerprom
>
> juju switch monitorme
>
> juju deploy ubuntu
>
> juju deploy cs:~rharding/telegraf-0
>
> juju relate ubuntu:juju-info telegraf
>
> juju consume bigbrother:/admin/default.offerprom promed
>
> juju relate telegraf:prometheus-client promed:target
>
> juju switch bigbrother
>
> juju show-machine 0
>
> - get the public IP of prometheus and load it in the browser :9090
>
> - open the status->targets list and make sure you see the CMR with the
> public IP address of the telegraf unit in AWS
>
> * Cross model relations over private networks
>
> The algorithm used to select the ingress address to advertise across a
> cross model relation is tweaked to better support the case where both
> applications are on a private subnet.
>
> If the offered endpoint is bound to a space, select an ingress address in
> that space.
>
> If the offered endpoint is not bound to a space, attempt to select a
> public address on the machine, and fallback to a cloud local address if
> necessary.
>
> The deployer of the application being offered thus gets to decide how they
> want the offer to be accessed when they deploy the application. Not all
> scenarios are covered since they are not yet modelled, eg bind to a private
> 

Re: using the new bundle features in Juju 2.2.3

[Junaid Ali]

>
> I  think the big thing as you note is that it's charm.key=value to hit the
> right place. And since you can do things like change unit/constriants/etc
> it's a much more complicated syntax.


Makes sense. Keeping it simple is a good approach at the moment.


--
Junaid

On Mon, Sep 18, 2017 at 7:27 PM, Rick Harding <rick.hard...@canonical.com>
wrote:

>
>
> On Sun, Sep 17, 2017 at 12:59 AM Junaid Ali <junaid...@xgrid.co> wrote:
>
>>
>> It would be great if we can pass a single value as well e.g juju deploy
>> ./bundle.yaml test-charm.admin-ip=172.31.81.203
>>
>
> Hmm, I wonder if the --bundle-config can be either a file or a k=v pairing
> like we do with the charm deploy where you can use both. I  think the big
> thing as you note is that it's charm.key=value to hit the right place. And
> since you can do things like change unit/constriants/etc it's a much more
> complicated syntax.
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: using the new bundle features in Juju 2.2.3

[Junaid Ali]

I used to go with yaml 'anchors' like Giuseppe. +1 for bundle-config flag
since that is a cleaner approach IMO.
It would be great if we can pass a single value as well e.g juju deploy
./bundle.yaml test-charm.admin-ip=172.31.81.203


--
Junaid

On Sat, Sep 16, 2017 at 12:22 PM, Patrizio Bassi 
wrote:

> +1 from my side.
>
> At the moment i have 3 bundles, dev, qa and prod which differ only by IPs
> and unit number
> It would be great to have a dynamic filled bundle :)
>
> Patrizio
>
> 2017-09-16 9:02 GMT+02:00 Giuseppe Attardi :
>
>>
>> > On 15 set 2017, at 16:46, Rick Harding 
>> wrote:
>> >
>> > On Fri, Sep 15, 2017 at 10:33 AM Giuseppe Attardi <
>> giuseppe.atta...@garr.it> wrote:
>> > Is it possible to use variables in the bundle defined in the
>> bundle-config?
>> >
>> > Not currently no, there's no string substitution in there. Are you
>> looking for model specific data to make it in? Or some other input?
>>
>> What we do in our bundles is this:
>>
>> variables:
>>   network-space-pub: _space_pub  space-pub
>>   …
>>
>> services:
>>   keystone:
>> bindings:
>>   public: *network_space_pub
>>  …
>>   openstack-dashboard:
>> bindings:
>>   shared-db: *network_space_os_mgmt
>>   cluster: *network_space_os_mgmt
>>   website: *network_space_pub
>>
>> It would be nice to place these variable definitions in the bundle-config
>> file.
>>
>> —
>>
>>
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/juju
>>
>
>
>
> --
>
> Patrizio Bassi
> www.patriziobassi.it
> http://piazzadelpopolo.patriziobassi.it
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Can we do bundle within a bundle?

[Junaid Ali]

Fengxia,
juju-deployer 
could be helpful here to incorporate multiple bundles. Charm-testing repo

can help you in using juju-deployer supported bundles e.g check this bundle

.


--
Junaid

On Fri, Apr 21, 2017 at 12:38 AM, Tom Barber  wrote:

> Currently bundles are pretty dumb and nested bundles don't exist.
>
> Tom
>
> On 20 Apr 2017 20:29, "fengxia"  wrote:
>
>> We have a design that calls for tree structure of entities, each will be
>> mapped to a charm/bundle. So how to bundle a list of bundles?
>>
>> --
>> Feng xia
>> Engineer
>> Lenovo USA
>>
>> Phone: 5088011794
>> fx...@lenovo.com
>>
>> Lenovo.com
>> Twitter | Facebook | Instagram | Blogs | Forums
>>
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/juju
>>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: How to add openstack cloud to juju 2.1.2-xenial

[Junaid Ali]

 0x2d, 0x4e, 0xf3, 0xe6, 0xd,
> > > 0x80,
> > > 0x20, 0x5e, 0xd1, 0x22, 0xa9, 0xc9, 0x70, 0x54, 0x4, 0xd0, 0x43,
> > > 0xc,
> > > 0x50, 0x2, 0xbe, 0xc2, 0xdf, 0x6f, 0x5, 0xb0, 0x4c, 0xf9, 0x4,
> > > 0xe5,
> > > 0x88, 0xf8, 0x88, 0x78, 0x18, 0xb1, 0xd7, 0x0, 0xa6, 0xc, 0xd5,
> > > 0x67,
> > > 0x5a, 0x50, 0x5f, 0x7a, 0xd, 0x30, 0x81, 0xe9, 0x33, 0x87, 0x45,
> > > 0x88,
> > > 0xf8, 0x53, 0x93, 0xd0, 0x7a, 0x70, 0x6a, 0x72, 0xda, 0xd7, 0x1c,
> > > 0xbd,
> > > 0x52, 0x82, 0x58, 0x44, 0x79, 0xbd, 0xd5, 0x2f, 0xc8, 0xb3, 0xea,
> > > 0x48,
> > > 0xfe, 0x2a, 0x32, 0x17, 0x13, 0x11, 0x7, 0x4d, 0x96, 0xa6, 0x80,
> > > 0xc2,
> > > 0x19, 0x8, 0x42, 0x40, 0xb, 0xaf, 0xc1, 0xad, 0x43, 0x88, 0xf, 0xb,
> > > 0x7f, 0x7d, 0xaf, 0xe0, 0x2b, 0xe7, 0xd7, 0xbf, 0x38, 0xf5, 0xa2,
> > > 0xa0,
> > > 0xc5, 0xdd, 0xd7, 0xe4, 0x32, 0x1e, 0x45, 0x6c, 0x72, 0x1d, 0x60,
> > > 0xfd,
> > > 0x6, 0x7f, 0x74, 0xfd, 0x3b, 0x21, 0x0, 0x5a, 0xe0, 0xa7, 0x6f,
> > > 0xaa,
> > > 0xa7, 0xd8, 0x30, 0x7c, 0x84, 0x7a, 0x3c, 0x5, 0x88, 0x40, 0x37,
> > > 0x45,
> > > 0xdf, 0x84, 0xf4, 0xdf, 0x9d, 0xbe, 0x4b, 0x7, 0xbb, 0x77, 0x10,
> > > 0x91,
> > > 0x50, 0xe2, 0xa1, 0x67, 0x7e, 0xe1, 0xcd, 0xbd, 0x7f, 0x34, 0xb3,
> > > 0xac,
> > > 0x21, 0x5, 0xe8, 0x67, 0x98, 0xc, 0x5d, 0x4a, 0x39, 0xe3, 0x5,
> > > 0xcc,
> > > 0x1f, 0x8f, 0xfb, 0x37, 0x88, 0xe6, 0x6, 0x6b, 0x54, 0x17, 0x16,
> > > 0xb4,
> > > 0xcc, 0x59, 0x23, 0x5c, 0x1, 0xd4, 0x8, 0x8f, 0xb5, 0xf4, 0x31,
> > > 0xbd,
> > > 0x5b, 0x9e, 0x5f, 0xd0, 0x87, 0xcf, 0xc7, 0xb0, 0x16, 0x30, 0xff,
> > > 0xb4,
> > > 0xf3, 0xfb, 0x1a, 0xa4, 0x34, 0xcf, 0xaf, 0x77, 0xb3, 0x56, 0x4b,
> > > 0x4d,
> > > 0xfc, 0x6e, 0xe6, 0x69, 0x19, 0x7e, 0xb5, 0x59, 0xe9, 0x3f, 0x80,
> > > 0xce,
> > > 0xd8, 0x47, 0x8d, 0x95, 0x52, 0x2f, 0xf9, 0x3d, 0x87, 0x8c, 0x55,
> > > 0xfe,
> > > 0x10, 0xf0, 0xa2, 0x6c, 0x9a, 0x4a, 0x60, 0x86, 0x86, 0xa0, 0x74,
> > > 0x4b,
> > > 0xc2, 0xcb, 0x7a, 0xcb, 0x22, 0xd4, 0x8c, 0xd0, 0xbd, 0xc8, 0x2e,
> > > 0x64,
> > > 0x51, 0xe3, 0x62, 0x91, 0x0, 0x4b, 0x1e, 0xd1, 0x2, 0xdf, 0x90,
> > > 0x2f,
> > > 0x24, 0xe8, 0xfa, 0xc9, 0xb8, 0x39, 0x28, 0x18, 0x4, 0x5a, 0xfd,
> > > 0x1b,
> > > 0xc9, 0xab, 0x1b, 0x1c, 0x77, 0xaf, 0x9e, 0xa4, 0x37, 0xdb, 0x89,
> > > 0x66,
> > > 0x6a, 0xa3, 0xc6, 0xad, 0x99, 0x13, 0x67, 0x7f, 0xba, 0x10, 0xa3,
> > > 0xaf,
> > > 0xef, 0xe6, 0xfa, 0xaa, 0x14, 0xf, 0x16, 0xcc, 0xa7, 0xe, 0x3c,
> > > 0x57,
> > > 0xc7, 0x44, 0x34, 0x15, 0xb9, 0x33, 0x4e, 0x26, 0xa8, 0xb0, 0xfc,
> > > 0x53,
> > > 0xfc, 0x21, 0x45, 0xe6, 0xc1, 0xc8, 0xd1, 0x92, 0x5d, 0xe5, 0xb7,
> > > 0x31,
> > > 0x5e, 0x5e, 0x5d, 0xf9, 0xd6, 0x47, 0xb, 0xd9, 0x35, 0xf0, 0xfc,
> > > 0x10,
> > > 0xa9, 0x23, 0xc9, 0x50, 0xa7, 0x99, 0x1a, 0xda, 0xee, 0xfc, 0xb0,
> > > 0x31,
> > > 0xdf, 0x25, 0xe5, 0xa5, 0x77, 0x3d, 0x66, 0xd3, 0x8b, 0x57, 0xad,
> > > 0xb1,
> > > 0xaa, 0x8f, 0xb7, 0x1b, 0x98, 0xe7, 0x3d, 0xd5, 0x57, 0xd4, 0xf6,
> > > 0xc9,
> > > 0x99, 0x3b, 0xce, 0xa1, 0xda, 0x62, 0x3a, 0xee, 0xc, 0xca, 0x25,
> > > 0x52,
> > > 0x44, 0x6b, 0x2b, 0xa7, 0x76, 0xf7, 0xb6, 0xee, 0x24, 0xa6, 0x7c,
> > > 0xdd,
> > > 0xe0, 0xd9, 0x7a, 0x74, 0x74, 0x49, 0x94, 0xb0, 0x70, 0xbf, 0x6f,
> > > 0x2f,
> > > 0x95, 0x59, 0x95, 0xe, 0xd2, 0x4b, 0xca, 0xe6, 0xc7, 0x20, 0x74,
> > > 0xfa,
> > > 0x1b, 0x53, 0x26, 0x3, 0xbf, 0xdf, 0x35, 0x7b, 0x46, 0xbc, 0xae,
> > > 0xf4,
> > > 0x9d, 0x34, 0x47, 0x49, 0xe5, 0xaf, 0xec, 0x4b, 0x65, 0x9c, 0x9d,
> > > 0xf7,
> > > 0xb4, 0x27, 0x99, 0x7d, 0x43, 0xa6, 0xea, 0xc2, 0x91, 0xb2, 0xd9,
> > > 0xc9,
> > > 0x6d, 0xaf, 0x91, 0x19, 0x86, 0xc7, 0xa9, 0x8a, 0xad, 0x85, 0x2a,
> > > 0x2d,
> > > 0x7b, 0xf1, 0x69, 0x92, 0xad, 0xed, 0x2e, 0xc1, 0xca, 0xe4, 0x5,
> > > 0x87,
> > > 0xd2, 0xa4, 0xcb, 0xd4, 0x38, 0x89, 0xd5, 0x75, 0x2f, 0x74, 0xd8,
> > > 0xfc,
> > > 0x3d, 0xdc, 0xbe, 0x39, 0x6d, 0x32, 0x8f, 0xfa, 0xe8, 0xc0, 0x47,
> > > 0xe5,
> > > 0xdb, 0x2d, 0x49, 0x6e, 0x1f, 0x4c, 0xfd, 0x50, 0x56, 0xdb, 0xf,
> > > 0x6b,
> > > 0xae, 0x4b, 0xeb, 0xe4, 0xe4, 0x4, 0x8a, 0x1d, 0xe7, 0x62, 0xbb,
> > > 0x6b,
> > > 0xf7, 0xa3, 0x5d, 0xac, 0x19, 0x98, 0xca, 0x3, 0x63, 0xe4, 0xee,
> > > 0xdf,
> > > 0xd4, 0x48, 0x42, 0x12, 0xdc, 0x5d, 0x76, 0xf6, 0xfb, 0x34, 0xeb,
> > > 0xe6,
> 

Re: How to add openstack cloud to juju 2.1.2-xenial

[Junaid Ali]

Hi Daniel,
Can you run juju bootstrap command with --debug flag? It should provide a
more detailed output.


--
Junaid

On Wed, Apr 12, 2017 at 10:23 PM, Daniel Bidwell 
wrote:

> I have followed the new howto-privatecloud down to the juju boostrap
> command of:
>
> juju bootstrap acauits --config image-metadata-url=http://10.20.9.139:8
> 0/swift/v1
>
> and it returns:
>
> Creating Juju controller "acauits-RegionOne" on acauits/RegionOne
> Looking for packaged Juju agent version 2.1.2 for amd64
> Launching controller instance(s) on acauits/RegionOne...
> ERROR failed to bootstrap model: cannot start bootstrap instance:
> cannot run instance: failed to run a server with
> nova.RunServerOpts{Name:"juju-8344e6-controller-0", FlavorId:"115c7b33-
> 901b-4431-bca4-040cfc91567b", ImageId:"xenial", UserData:[]uint8{0x1f,
> 0x8b, 0x8, 0x0, 0x0, 0x9, 0x6e, 0x88, 0x0, 0xff, 0x9c, 0x54, 0xfd,
> 0x8f, 0xb2, 0x46, 0x10, 0xfe, 0xfd, 0xfe, 0x8a, 0x4d, 0x9a, 0xc6, 0x36,
> 0x86, 0x43, 0x1, 0x95, 0x33, 0xb9, 0xa6, 0xa8, 0xdc, 0x89, 0xdf, 0x8,
> 0xea, 0x61, 0xdb, 0x34, 0xb, 0x2c, 0xb0, 0x7c, 0xec, 0x22, 0xbb, 0x88,
> 0x9a, 0xf7, 0x8f, 0x2f, 0xe8, 0xbd, 0xe9, 0x47, 0xd2, 0x26, 0x7d, 0xfd,
> 0xc1, 0x9d, 0x9d, 0x9d, 0x7d, 0xe6, 0xd9, 0x99, 0x67, 0xf8, 0xce, 0x4b,
> 0x69, 0xe9, 0xb, 0x1e, 0x25, 0x1, 0xe, 0x9f, 0x68, 0xc9, 0xf3, 0x92,
> 0xf, 0x9f, 0x0, 0x80, 0x69, 0x3a, 0x4, 0xad, 0x2f, 0x80, 0x23, 0x4,
> 0x4, 0x8, 0xc4, 0x33, 0x2c, 0xc4, 0x94, 0x86, 0xe2, 0x23, 0x1c, 0x13,
> 0xcc, 0x85, 0x47, 0xf0, 0x73, 0xed, 0x6d, 0x3d, 0x15, 0x25, 0xf1, 0x32,
> 0x7f, 0xf8, 0x24, 0x0, 0x86, 0x38, 0x10, 0x2e, 0xa8, 0xb6, 0x30, 0x61,
> 0xbc, 0x86, 0x1, 0xc2, 0x4, 0x8, 0x19, 0xe8, 0x2b, 0xa, 0x10, 0x7d,
> 0x74, 0x16, 0x49, 0x59, 0xfb, 0x5a, 0x22, 0xe2, 0x9e, 0xc8, 0xae, 0x8c,
> 0xa3, 0xcc, 0xff, 0x5c, 0xc5, 0xb8, 0x8c, 0x4b, 0xc1, 0x4b, 0x11, 0x24,
> 0x2, 0x8b, 0x4a, 0xee, 0xd3, 0x8a, 0x3c, 0x33, 0x54, 0x9c, 0xb1, 0x87,
> 0x5a, 0x35, 0xde, 0x17, 0xa1, 0xe6, 0x95, 0x17, 0x98, 0xf0, 0x0, 0xb4,
> 0xbe, 0x67, 0xbf, 0x92, 0x16, 0x68, 0xd5, 0x9e, 0x5f, 0x76, 0x35, 0x99,
> 0xdf, 0x6a, 0x63, 0x82, 0x98, 0x57, 0xe0, 0x9c, 0x63, 0x4a, 0x5e, 0x2d,
> 0x4e, 0xf3, 0xe6, 0xd, 0x80, 0x20, 0x5e, 0xd1, 0x22, 0xa9, 0xc9, 0x70,
> 0x54, 0x4, 0xd0, 0x43, 0xc, 0x50, 0x2, 0xbe, 0xc2, 0xdf, 0x6f, 0x5,
> 0xb0, 0x4c, 0xf9, 0x4, 0xe5, 0x88, 0xf8, 0x88, 0x78, 0x18, 0xb1, 0xd7,
> 0x0, 0xa6, 0xc, 0xd5, 0x67, 0x5a, 0x50, 0x5f, 0x7a, 0xd, 0x30, 0x81,
> 0xe9, 0x33, 0x87, 0x45, 0x88, 0xf8, 0x53, 0x93, 0xd0, 0x7a, 0x70, 0x6a,
> 0x72, 0xda, 0xd7, 0x1c, 0xbd, 0x52, 0x82, 0x58, 0x44, 0x79, 0xbd, 0xd5,
> 0x2f, 0xc8, 0xb3, 0xea, 0x48, 0xfe, 0x2a, 0x32, 0x17, 0x13, 0x11, 0x7,
> 0x4d, 0x96, 0xa6, 0x80, 0xc2, 0x19, 0x8, 0x42, 0x40, 0xb, 0xaf, 0xc1,
> 0xad, 0x43, 0x88, 0xf, 0xb, 0x7f, 0x7d, 0xaf, 0xe0, 0x2b, 0xe7, 0xd7,
> 0xbf, 0x38, 0xf5, 0xa2, 0xa0, 0xc5, 0xdd, 0xd7, 0xe4, 0x32, 0x1e, 0x45,
> 0x6c, 0x72, 0x1d, 0x60, 0xfd, 0x6, 0x7f, 0x74, 0xfd, 0x3b, 0x21, 0x0,
> 0x5a, 0xe0, 0xa7, 0x6f, 0xaa, 0xa7, 0xd8, 0x30, 0x7c, 0x84, 0x7a, 0x3c,
> 0x5, 0x88, 0x40, 0x37, 0x45, 0xdf, 0x84, 0xf4, 0xdf, 0x9d, 0xbe, 0x4b,
> 0x7, 0xbb, 0x77, 0x10, 0x91, 0x50, 0xe2, 0xa1, 0x67, 0x7e, 0xe1, 0xcd,
> 0xbd, 0x7f, 0x34, 0xb3, 0xac, 0x21, 0x5, 0xe8, 0x67, 0x98, 0xc, 0x5d,
> 0x4a, 0x39, 0xe3, 0x5, 0xcc, 0x1f, 0x8f, 0xfb, 0x37, 0x88, 0xe6, 0x6,
> 0x6b, 0x54, 0x17, 0x16, 0xb4, 0xcc, 0x59, 0x23, 0x5c, 0x1, 0xd4, 0x8,
> 0x8f, 0xb5, 0xf4, 0x31, 0xbd, 0x5b, 0x9e, 0x5f, 0xd0, 0x87, 0xcf, 0xc7,
> 0xb0, 0x16, 0x30, 0xff, 0xb4, 0xf3, 0xfb, 0x1a, 0xa4, 0x34, 0xcf, 0xaf,
> 0x77, 0xb3, 0x56, 0x4b, 0x4d, 0xfc, 0x6e, 0xe6, 0x69, 0x19, 0x7e, 0xb5,
> 0x59, 0xe9, 0x3f, 0x80, 0xce, 0xd8, 0x47, 0x8d, 0x95, 0x52, 0x2f, 0xf9,
> 0x3d, 0x87, 0x8c, 0x55, 0xfe, 0x10, 0xf0, 0xa2, 0x6c, 0x9a, 0x4a, 0x60,
> 0x86, 0x86, 0xa0, 0x74, 0x4b, 0xc2, 0xcb, 0x7a, 0xcb, 0x22, 0xd4, 0x8c,
> 0xd0, 0xbd, 0xc8, 0x2e, 0x64, 0x51, 0xe3, 0x62, 0x91, 0x0, 0x4b, 0x1e,
> 0xd1, 0x2, 0xdf, 0x90, 0x2f, 0x24, 0xe8, 0xfa, 0xc9, 0xb8, 0x39, 0x28,
> 0x18, 0x4, 0x5a, 0xfd, 0x1b, 0xc9, 0xab, 0x1b, 0x1c, 0x77, 0xaf, 0x9e,
> 0xa4, 0x37, 0xdb, 0x89, 0x66, 0x6a, 0xa3, 0xc6, 0xad, 0x99, 0x13, 0x67,
> 0x7f, 0xba, 0x10, 0xa3, 0xaf, 0xef, 0xe6, 0xfa, 0xaa, 0x14, 0xf, 0x16,
> 0xcc, 0xa7, 0xe, 0x3c, 0x57, 0xc7, 0x44, 0x34, 0x15, 0xb9, 0x33, 0x4e,
> 0x26, 0xa8, 0xb0, 0xfc, 0x53, 0xfc, 0x21, 0x45, 0xe6, 0xc1, 0xc8, 0xd1,
> 0x92, 0x5d, 0xe5, 0xb7, 0x31, 0x5e, 0x5e, 0x5d, 0xf9, 0xd6, 0x47, 0xb,
> 0xd9, 0x35, 0xf0, 0xfc, 0x10, 0xa9, 0x23, 0xc9, 0x50, 0xa7, 0x99, 0x1a,
> 0xda, 0xee, 0xfc, 0xb0, 0x31, 0xdf, 0x25, 0xe5, 0xa5, 0x77, 0x3d, 0x66,
> 0xd3, 0x8b, 0x57, 0xad, 0xb1, 0xaa, 0x8f, 0xb7, 0x1b, 0x98, 0xe7, 0x3d,
> 0xd5, 0x57, 0xd4, 0xf6, 0xc9, 0x99, 0x3b, 0xce, 0xa1, 0xda, 0x62, 0x3a,
> 0xee, 0xc, 0xca, 0x25, 0x52, 0x44, 0x6b, 0x2b, 0xa7, 0x76, 0xf7, 0xb6,
> 0xee, 0x24, 0xa6, 0x7c, 0xdd, 0xe0, 0xd9, 0x7a, 0x74, 0x74, 0x49, 0x94,
> 0xb0, 0x70, 0xbf, 0x6f, 0x2f, 0x95, 0x59, 0x95, 0xe, 0xd2, 0x4b, 0xca,
> 0xe6, 0xc7, 0x20, 0x74, 0xfa, 0x1b, 0x53, 0x26, 0x3, 0xbf, 

Re:

[Junaid Ali]

Hi Shweta,
can you remove all lines after the "endpoint: https://192.168.
100.2:5000/v2.0" line, re-add the cloud and source adminrc file in the
terminal. Then run:
$ juju autoload-credentials

and try bootstrapping again.


--
Junaid

On Mon, Feb 13, 2017 at 9:00 AM, Shweta Shotu 
wrote:

> Hii,
>
> I installed juju on ubuntu 14.04, I am trying to add a private cloud to
> juju.This private cloud is an openstack setup on my local network.
>
> The commands are as follows:
>
> using this command, i got to know about that there no such cloud
>
> *~$ juju list-clouds*
> CloudRegions  DefaultTypeDescription
> aws   11  us-east-1  ec2 Amazon Web Services
> aws-china  1  cn-north-1 ec2 Amazon China
> aws-gov1  us-gov-west-1  ec2 Amazon (USA Government)
> azure 18  centralus  azure   Microsoft Azure
> azure-china2  chinaeast  azure   Microsoft Azure China
> cloudsigma 5  hnlcloudsigma  CloudSigma Cloud
> google 6  us-east1   gce Google Cloud Platform
> joyent 6  eu-ams-1   joyent  Joyent Cloud
> rackspace  6  dfwrackspace   Rackspace Cloud
> localhost  1  localhost  lxd LXD Container Hypervisor
>
> So, I added  openstack to the list of clouds using:
> ~$ juju add-cloud mystack openstack.yaml
> --
> *openstack.yaml :*
>
>  mystack:
>   type: openstack
>   auth-types: [userpass]
>   regions:
> RegionOne:
>   endpoint: https://192.168.100.2:5000/v2.0
>   auth-mode: userpass
>   auth-url: http://192.168.100.2:5000/v2.0
>   default-series: trusty
>   password: password
>   region: RegionOne
>   tenant-name: admin
>   username: admin
> 
> *~$ juju list-clouds*
> CloudRegions  DefaultTypeDescription
> aws   11  us-east-1  ec2 Amazon Web Services
> aws-china  1  cn-north-1 ec2 Amazon China
> aws-gov1  us-gov-west-1  ec2 Amazon (USA Government)
> azure 18  centralus  azure   Microsoft Azure
> azure-china2  chinaeast  azure   Microsoft Azure China
> cloudsigma 5  hnlcloudsigma  CloudSigma Cloud
> google 6  us-east1   gce Google Cloud Platform
> joyent 6  eu-ams-1   joyent  Joyent Cloud
> rackspace  6  dfwrackspace   Rackspace Cloud
> localhost  1  localhost  lxd LXD Container Hypervisor
> *mystack1  RegionOne  openstack   Openstack Cloud*
>
>
> After adding it, I tried to bootstrap but I encounter authentication
> failed error.
>
> ~$ juju bootstrap -v
> Clouds
> aws
> aws-china
> aws-gov
> azure
> azure-china
> cloudsigma
> google
> joyent
> localhost
> mystack
> openstack
> rackspace
>
> Select a cloud [localhost]: mystack
>
> Enter a name for the Controller [mystack-RegionOne]:
>
> *ERROR authentication failed.*
>
> *Please ensure the credentials are correct*. A common mistake is
> to specify the wrong tenant. Use the OpenStack "project" name
> for tenant-name in your model configuration.
>
>
> I have checked google a lot but found no solution for this. So, Can anyone
> help me out regarding all this
>
>
> Regards,
> Shweta
> Tata Consultancy Services,
> Gurgaon
> Mailto: shwe...@tcs.com
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/listinfo/juju-dev
>
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: juju openstack-base guide is not clear

[Junaid Ali]

Hi Yinon,

I would suggest you to read https://jujucharms.com/do
cs/stable/getting-started
and
https://docs.ubuntu.com/maas/2.1/en/


Question: Does this mean I have to provision the 4 nodes using MAAS prior
> to deploying openstack with juju? Or will juju provision them?
>
MAAS will provision the nodes. If you check the bundle.yaml file, it has a
machine section in it where Juju has specified some machines to be
provisioned by MAAS. You should probably look for Juju constraints


Question: I understand eth0 is used for internal APIs (keystone, nova,
> neutron etc.), and eth1 for external connectivity for VMs. Does this mean
> eth0 is the management network, and the internal API uses the same network?
> What about a PXE network for provisioning the nodes? Which NIC is that and
> what VLAN?

Yes, PXE, management are mapped onto the same network (eth0). You can
use network
spaces  feature of Juju
to use different APIs on different networks but I think the commands in the
shared link need update.

Question: Where is the step that is supposed to actually deploy the cloud
> (something like "juju deploy ...")?

You can deploy the cloud using bundle.yaml by simply running:
$ juju deploy bundle.yaml

Question: Where do I specify the IPs of the target hosts, or the MAAS
> server, for juju to know where to deploy?

Machines will be provisioned by MAAS using the constraints (and series)
specified in bundle.yaml. Juju makes use of machine IDs (check machine
section in bundle.yaml) to deploy service/s to a specific machine.


I hope it will help you a bit.

Thanks,
Junaid



On Wed, Feb 8, 2017 at 3:11 AM, Yinon  wrote:

>
> Hello,
>
> I am following the guide: https://jujucharms.com/openstack-base/ in order
> to install openstack using juju.
> Some steps are not clear to me.
>
> The guide: "This bundle is designed to run on bare metal using Juju with
> MAAS  (Metal-as-a-Service); you will need to
> have setup a MAAS  deployment with a minimum
> of 4 physical servers prior to using this bundle."
> Question: Does this mean I have to provision the 4 nodes using MAAS prior
> to deploying openstack with juju? Or will juju provision them?
>
> The guide: "Two cabled network ports on eth0 and eth1"
> Question: I understand eth0 is used for internal APIs (keystone, nova,
> neutron etc.), and eth1 for external connectivity for VMs. Does this mean
> eth0 is the management network, and the internal API uses the same network?
> What about a PXE network for provisioning the nodes? Which NIC is that and
> what VLAN?
>
> Question: Where is the step that is supposed to actually deploy the cloud
> (something like "juju deploy ...")?
>
> Question: Where do I specify the IPs of the target hosts, or the MAAS
> server, for juju to know where to deploy?
>
> Thanks,
> Yinon
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Create Juju Charms from your browser!

[Junaid Ali]

Great. Thanks Merlijn for sharing.
-- Junaid-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Best way to put images in a Charm's readme?

[Junaid Ali]

Merlijin,
In your readme.md, can you specify URL for the images like L17 in this
readme
<http://bazaar.launchpad.net/~ya-bo-ng/landscape-charm/readme-with-image/view/head:/README.md>
file? It will work in your case.

Thanks,
- Junaid

On Fri, Dec 9, 2016 at 12:01 PM, Junaid Ali <junaid...@plumgrid.com> wrote:

> Merlijin,
> It seems that readme in charm store expects images to be in
> https://jujucharms.com/u///files/documentation/.
> I'm also not sure how to add that.
>
> Thanks,
> - Junaid
>
> On Fri, Dec 9, 2016 at 8:06 AM, Merlijn Sebrechts <
> merlijn.sebrec...@gmail.com> wrote:
>
>> Hi all
>>
>>
>> I have this beautiful picture tutorial in the README of my openvpn charm.
>> The images are stored as part of the Charm. This looks great on github
>> <https://github.com/IBCNServices/tengu-charms/tree/openvpn/charms/builds/openvpn#connecting-to-the-vpn>,
>> where relative urls work. But this is completely broken in the charm
>> store <https://jujucharms.com/u/tengu-bot/openvpn/5>.
>>
>> What's the best way to include pictures in a Charm's readme?
>>
>>
>>
>> Kind regards
>> Merlijn
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/juju
>>
>>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Best way to put images in a Charm's readme?

[Junaid Ali]

Merlijin,
It seems that readme in charm store expects images to be in
https://jujucharms.com/u///files/documentation/. I'm
also not sure how to add that.

Thanks,
- Junaid

On Fri, Dec 9, 2016 at 8:06 AM, Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:

> Hi all
>
>
> I have this beautiful picture tutorial in the README of my openvpn charm.
> The images are stored as part of the Charm. This looks great on github
> ,
> where relative urls work. But this is completely broken in the charm store
> .
>
> What's the best way to include pictures in a Charm's readme?
>
>
>
> Kind regards
> Merlijn
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: MAAS Commissioning Failed timed out after 0:20:00

[Junaid Ali]

Hi Parbakaran,

Make sure you have passwordless ssh-access from maas-user to the infra node.
I would suggest running these commands on maas-controller and try to
commission again:

$ sudo chsh -s /bin/bash maas
$ sudo su - maas
$ ssh-keygen -t rsa
$ ssh-copy-id @
$ exit
$ ssh-keygen -t rsa

Thanks,
Junaid

On Mon, Oct 10, 2016 at 12:27 PM, Prabakaran Chandrasekaran <
praba...@in.ibm.com> wrote:

> Hello Team,
>
> I have installed MAAS and tried to setup MAAS. I am setting up virtual
> machines to use as nodes with MAAS, and I have selected the power type as
> virsh. After manually adding the machine(node), within few minutes of
> commissioning process got failed stating “'Commissioning' timed out after
> 0:20:00”. Below is maas log link *http://pastebin.ubuntu.com/23301741/*
> 
>
> I tried few methods of troubleshooting but no luck. Below are the
> troubleshooting steps which I have tried.
>
> 1, sudo dpkg-reconfigure maas-region-controller
>
> 2, sudo dpkg-reconfigure maas-cluster-controller
>
> Please advise me on this issue.
>
> Posted this query in here also: http://askubuntu.com/questions
> /835087/maas-commissioning-failed-timed-out-after-02000
>
> Thanks
> Prabakaran Chandrasekaran
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

juju status stucking

[Junaid Ali]

Hi everyone,

I'm having an issue on juju status command. It stucks when I run the
command for a service e.g

juju status nova-cloud-controller

although
$ juju status
 and
$ juju status --format tabular
works fine.

Version of juju that I'm using is 1.25.6. Let me know please if any
workaround available for this issue or what logs to share if this is a bug.

Thanks and Regards,
Junaid
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: [ANN] New juju-deployer-0.9.0, python-jujuclient-0.53.1

[Junaid Ali]

Thanks Tim.
It is working well for me as well except for local charms and charms at
launchpad. It gives out error "juju deploy -m ctr-trusty:neutron_plugin
--config /tmp/tmpciQAqA --series trusty trusty/neutron-api neutron-api".

Regards,
Junaid

On Thu, Aug 4, 2016 at 6:38 PM, Pete Vander Giessen <
pete.vandergies...@canonical.com> wrote:

> Hi Tim,
>
> I've been using the latest Juju beta, along with updated deployer and
> amulet built from master, and it is all working smoothly. Thank you very
> much for putting in the work to get everything updated. :-)
>
> ~ PeteVG
>
> On Wed, Aug 3, 2016 at 1:41 PM Charles Butler <
> charles.but...@canonical.com> wrote:
>
>> With quick turn around this is now available for immediate testing in the
>> charmbox:devel flavor of images
>>
>> docker pull jujusolutions/charmbox:devel
>>
>> You can get started right away with some volume mounts to bring in your
>> charm's and $JUJU_DATA location. We on the ~containers team have a bash
>> alias to make this somewhat trivial:
>>
>> I apologize in advance for the number of flags to make this feasible,
>> however its a vanilla juju workspace on every invocation.
>>
>> docker run --rm \
>>   -ti  \
>>   -h charmbox.juju.solutions \
>>   -v $HOME/.juju-work:/home/ubuntu/.local/share/juju \
>>   -v $HOME/projects/work/interfaces:/home/ubuntu/interfaces \
>>   -v $HOME/projects/work/layers:/home/ubuntu/layers \
>>   -v $HOME/projects/work/builds:/home/ubuntu/builds \
>>   -v $HOME/projects/work/bundles:/home/ubuntu/bundles \
>>   -v $PWD:/home/ubuntu/pwd \
>>   jujusolutions/charmbox:devel
>>
>> From here you should be able to enter into any charm/bundle directory and
>> kick off a test against a boostrapped juju2 controller:
>>
>> juju bootstrap amazon aws
>> bundletester -F -l DEBUG -v
>>
>> If you encounter any issues, let us know on the issue tracker:
>>
>> https://github.com/juju-solutions/charmbox/issues
>>
>> Thanks and happy testing!
>>
>> On Wed, Aug 3, 2016 at 11:01 AM Tim Van Steenburgh <
>> tim.van.steenbu...@canonical.com> wrote:
>>
>>> These new releases work with the latest juju-2.0 betas while maintaining
>>> compatibility with juju-1.25.
>>>
>>> They are currently available on PyPI and in ppa:tvansteenburgh/ppa, and
>>> will likely be copied to ppa:juju/stable in the near future.
>>>
>>> Find bugs? File here:
>>> https://bugs.launchpad.net/python-jujuclient
>>> https://bugs.launchpad.net/juju-deployer
>>>
>>>
>>> Bundletester (https://github.com/juju-solutions/bundletester) works
>>> with the latest juju-2.0 betas if the latest versions of juju-deployer and
>>> python-jujuclient are installed.
>>>
>>> The Amulet charm testing library (http://pythonhosted.org/amulet/) has
>>> juju-2.0 support in master, but is awaiting a release that contains that
>>> support. Watch this space for an announcement of that release.
>>> --
>>> Juju mailing list
>>> Juju@lists.ubuntu.com
>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>>> an/listinfo/juju
>>>
>> --
>> Juju Charmer
>> Canonical Group Ltd.
>> Ubuntu - Linux for human beings | www.ubuntu.com
>> Juju - The fastest way to model your service | www.jujucharms.com
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/juju
>>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

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

[Junaid Ali]

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 something wrong on
juju side.  Also if i ssh into a node and check the hostname, the node has
the correct hostname.

Here is the output of
$ juju stat --format tabular
http://paste.ubuntu.com/18145396/

Can you anyone please help me in debugging this issue?

Thanks,
- Junaid
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju