Re: juju 2.0.2 picking a random ip address from maas

You might want to track https://bugs.launchpad.net/juju/+bug/1680100 On Thu, Apr 27, 2017 at 11:45 AM Patrizio Bassi wrote: > Hi John, > > i'm writing you again after long time i didn't check juju deploys for a > while. > > Basically the dns-name (what juju status

Re: juju 2.0.2 picking a random ip address from maas

Hi John, i'm writing you again after long time i didn't check juju deploys for a while. Basically the dns-name (what juju status shows in Public address column) is still wrong juju show-machine 0 model: openstack machines: "0": juju-status: current: started since: 27 Apr 2017

Re: juju 2.0.2 picking a random ip address from maas

Good morning John, I tested it, i destroyed the controller and rebuilt from scratch. after juju bootstrap i got "No packaged binary found, preparing local Juju agent binary" because it could not find 2.1.2 version in the repos, which is great. with $ juju deploy ceph-osd --bind The unit

Re: juju 2.0.2 picking a random ip address from maas

Ok! I'll test tomorrow, but i need a xenial build as i'm on 16.04 release Patrizio Il 09/mar/2017 07:29 PM, "John Meinel" ha scritto: > http://data.vapour.ws/juju-ci/products/version-4977/build- > binary-trusty-amd64/build-2159/juju-core_2.1.2-0ubuntu1~ >

Re: juju 2.0.2 picking a random ip address from maas

My snap is pending review. In the meantime you can try with: https://launchpad.net/~ivoks/+archive/ubuntu/ppa On Thu, Mar 9, 2017 at 6:38 PM John Meinel wrote: > We should as soon as I have it landed in the 2.1 branch and CI starts to > run we can use it's deb. > > John

Re: juju 2.0.2 picking a random ip address from maas

We should as soon as I have it landed in the 2.1 branch and CI starts to run we can use it's deb. John =:-> On Mar 9, 2017 09:48, "Patrizio Bassi" wrote: > Fantastic job John! > > do you have a .deb i can already test on my environment? > > Patrizio > > 2017-03-09

Re: juju 2.0.2 picking a random ip address from maas

Fantastic job John! do you have a .deb i can already test on my environment? Patrizio 2017-03-09 16:24 GMT+01:00 John Meinel : > I do have a fix up for review: > https://github.com/juju/juju/pull/7081 > And I have tested it live against a local maas, though my maas

Re: juju 2.0.2 picking a random ip address from maas

I do have a fix up for review: https://github.com/juju/juju/pull/7081 And I have tested it live against a local maas, though my maas doesn't have multiple interfaces, I can see the bindings get requested appropriately and not fail with the "empty binding name" failure. I'm pushing to get a

Re: juju 2.0.2 picking a random ip address from maas

@John great. i'm using juju 2.1.1 and maas 2.1.3. Regarding the workaround...it's not a matter of a particular charm, it's a matter of all (i will deploy openstack-telemetry charm with some modifications), because when we allocate a machine with juju i would like it to pick a public (dns) name,

Re: juju 2.0.2 picking a random ip address from maas

Where do we find which bindings a charm has so they can be specified directly? According to the docs on the metadata ( https://jujucharms.com/docs/stable/authors-charm-metadata) there's a section called extra-bindings but that only seems to be used in some charms. -- Sandor Zeestraten On Thu,

Re: juju 2.0.2 picking a random ip address from maas

In the meantime, you can work around it by specifying the bindings directly: so in the case of mysql that would be: juju deploy mysql --bind "db=db-space monitors=db-space ha=db-space ..." John =:-> On Thu, Mar 9, 2017 at 7:25 AM, John Meinel wrote: > "juju deploy

Re: juju 2.0.2 picking a random ip address from maas

"juju deploy mysql --bind db-space" is exactly the syntax that should be working, and I'm seeing it failing now. I will work to fix that and make sure we don't regress here. We certainly should have caught that before release. John =:-> On Thu, Mar 9, 2017 at 1:47 AM, Patrizio Bassi

Re: juju 2.0.2 picking a random ip address from maas

What version of MAAS? Just in case the problem is a mismatch with all the tests I've been doing so far. John =:-> On Mar 9, 2017 07:05, wrote: We intentionally use "" to mean the default value for everything else, which is why I need to understand where we are actually getting the error. I'll

Re: juju 2.0.2 picking a random ip address from maas

We intentionally use "" to mean the default value for everything else, which is why I need to understand where we are actually getting the error. I'll try to reproduce it today. John =:-> On Mar 9, 2017 01:28, "Patrizio Bassi" wrote: > Hi John, > > i simply would like

Re: juju 2.0.2 picking a random ip address from maas

Hi All, after some debugging i found in juju /application /deploy.go func (c *DeployCommand) parseBind() { case

Re: juju 2.0.2 picking a random ip address from maas

Hi Patrizio, this is exactly what I saw yesterday too, unrelated to this thread. What you could do is: juju deploy mysql --constraints spaces=db-space Let me know if the constraints workaround works for you. On Thu, Mar 9, 2017 at 8:28 AM Patrizio Bassi wrote: > Hi

Re: juju 2.0.2 picking a random ip address from maas

Hi John, i simply would like to do what's written in https://jujucharms.com/docs/2.1/charms-deploying "When deploying an application to a target with multiple spaces, the operator must specify which space to use because ambiguous bindings will result in a provisioning failure." This is exactly

Re: juju 2.0.2 picking a random ip address from maas

So without bindings, I would expect the behavior, the question is why you would be seeing: "cannot run instances: cannot run instance: interface bindings cannot have empty names" Can you open a bug on https://bugs.launchpad.net/juju/+filebug and include some more information like the logs from

Re: juju 2.0.2 picking a random ip address from maas

Is it possible for you to test with Juju 2.1? I haven't seen that particular bug with binding, but I have done a lot more testing with 2.1. I didn't think we changed the particular "empty space" differences. The other possibility is to try and explicitly list the endpoints: juju deploy

Re: juju 2.0.2 picking a random ip address from maas

i just upgraded to 2.1.1-xenial-amd64, same behaviour unfortunately. As i'm going to deploy openstack services (now i'm using ceph-osd just to test, than my binding should be global for a local bundle charm) i would like to say: all juju endpoint (bare metal/lxd containers) just get a 10.xxx

Re: juju 2.0.2 picking a random ip address from maas

It looks like it's not working $ juju deploy ceph-osd --bind "management" $ juju show-machine 0 shows "message: 'failed to start instance (cannot run instances: cannot run instance: interface bindings cannot have empty names), retrying in 10s (3 more attempts)' ...than after some seconds

Re: juju 2.0.2 picking a random ip address from maas

You should be using "juju deploy application --bind space" to declare which set of addresses you want the applications to use. Does that not work? John =:-> On Wed, Mar 8, 2017 at 4:44 AM, Patrizio Bassi wrote: > Hi All, > > I'm quite new the juju and it's charms.

juju 2.0.2 picking a random ip address from maas

Hi All, I'm quite new the juju and it's charms. On ubuntu 16.04 LTS I have juju 2.0.2 using maas (2.1.3) cloud as provider. In maas I have configured (ready status) some machines, each one has 2 eth ports, one with a public ip (same as juju client/controller 10.x.x.x) which resolves to machine