Clarifying the concept of bindings in charms

Hi all, The new network requirements in Juju 2.1.x where operators must explicitly specifying which bindings to use are confusing me a bit. Just to clarify, where do I find which bindings/endpoints are available for each charm? The charm store does not seem to display these without looking in the

Re: Juju GUI handling of empty config breaks promulgated charms

Hi All, Just a quick follow-up on this: both the gui and python-libjuju now use the "config-yaml" rather than the "config" parameter when deploying a bundle, which addresses the issue (provided you have an updated GUI or libjuju wherever you're performing the deploy, of course). ~ PeteVG On Thu,

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~ > 14.04.1~juju1_amd64.deb > > Should have

Re: juju 2.0.2 picking a random ip address from maas

http://data.vapour.ws/juju-ci/products/version-4977/build-binary-trusty-amd64/build-2159/juju-core_2.1.2-0ubuntu1~14.04.1~juju1_amd64.deb Should have the fix for empty binding names. John =:-> On Thu, Mar 9, 2017 at 11:43 AM, Ante Karamatić < ante.karama...@canonical.com> wrote: > My snap is p

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 > =:-> > > On Mar 9, 201

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 16:24 GMT+01:00 John Meinel :

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 doesn't > have multiple int

Re: juju 2.0.2 picking a random ip address from maas

Hi John I'll give this a shot today. Thank you! On Thu, Mar 9, 2017 at 4:25 PM John Meinel wrote: > 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 bindin

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 2.1.2

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, th

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, Mar

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 mysql --bind db-space" is ex

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 wrote: > H

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 tr

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 to do what's written in ht

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