The Juju Show #3 - what you missed

Check out the recording of the show in case you missed it. https://www.youtube.com/watch?v=n86tRu4xpYU I want to thank everyone that joined us for the show this week. We talked about the great new things we hope folks build on top of libjuju, our favorite less famous Juju commands, come see us at

Re: errors in my juju deploy of canonical distribution of kubernetes

I just wanted to circle back on this thread that we took corrective action yesterday and it should make it into the next bump of the bundle. Thanks for reporting and following up fellas :) https://github.com/juju-solutions/bundle-canonical-kubernetes/pull/170 Charles Butler - Juju Charmer Come

Re: Charm release fails with "cannot update base entity for..."

Ok, thanks! This might be a bug in `charm build`. It merges the "series" array of multiple layers' metadata.yaml. 2017-01-04 18:18 GMT+01:00 roger peppe : > OK, I've found the issue. Your metadata.yaml specifies "trusty" twice > in the "series" attribute. > Specifying it only once should allow

Re: Charm release fails with "cannot update base entity for..."

OK, I've found the issue. Your metadata.yaml specifies "trusty" twice in the "series" attribute. Specifying it only once should allow you to release. We should produce a better error message for this case (or just de-duplicate series). cheers, rog. On 3 January 2017 at 12:17, Merlijn Sebre

Re: errors in my juju deploy of canonical distribution of kubernetes

I've got a pending pull request in the upstream documentation that makes this more clear, and lists some other limitations that we've discovered, for example if you set up ipv6 in LXD then conjure-up won't work. I filed a bug on this before the break so that we do a smarter job of getting it workin

Re: using a bundle with manually added machines (redux)

On 4 January 2017 at 15:34, roger peppe wrote: > a dep option I meant to say "a deploy option" here. -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju

Re: using a bundle with manually added machines (redux)

On 4 January 2017 at 14:35, Vance Morris wrote: > It's worse than a waste: it managed to confused the hell out of me. I had no > idea that there even was a thing called "juju-deployer" that was separate > from "juju deploy". > > Seems to me that if a model already has machines 0 and 1 deployed,

Re: using a bundle with manually added machines (redux)

It's worse than a waste: it managed to confused the hell out of me. I had no idea that there even was a thing called "juju-deployer" that was separate from "juju deploy". Seems to me that if a model already has machines 0 and 1 deployed, and a bundle is deployed that refers to machines 0, 1 and

Re: Charm release fails with "cannot update base entity for..."

Ah, sorry, I misread above - I thought that "jupyter" was the incorrect spelling. Will look again. On 4 January 2017 at 10:49, Merlijn Sebrechts wrote: > Correct. In the staging charm store I only used the (correct) name > jupyter-notebook-spark. It's in the normal charm store that I used the > i

Re: master/CiaB: Wait for juju services to have open ports - Timeout when waiting for services

This is the content of juju-bad.log, result of "juju status" on my server. Or please let me know what command should I gave. It's difficult for me to try them out in ansible playbook. *sigh* environment: manual machines: "0": agent-state: started agent-state-info: (started) agent-ve

Re: master/CiaB: Wait for juju services to have open ports - Timeout when waiting for services

Can you paste the relations part of the juju status output that shows those relations in place? Perhaps there's an issue with the charm logic and breaking and re-adding the relations might kick it into gear? On Wed, Jan 4, 2017 at 2:48 AM Mac Lin wrote: > Really appreciate for the help. Have b

Re: Charm release fails with "cannot update base entity for..."

Correct. In the staging charm store I only used the (correct) name jupyter-notebook-spark. It's in the normal charm store that I used the incorrect jupiter-notebook-spark. 2017-01-04 11:04 GMT+01:00 roger peppe : > On 3 January 2017 at 13:05, Merlijn Sebrechts > wrote: > > I have the same issue

Re: Charm release fails with "cannot update base entity for..."

On 3 January 2017 at 13:05, Merlijn Sebrechts wrote: > I have the same issue in the staging charm store. > > > charm release cs:~tengu-team/jupyter-notebook-spark-0 > ERROR cannot release charm or bundle: cannot publish charm or bundle: cannot > update base entity for "cs:~tengu-team/jupyter-note

Re: using a bundle with manually added machines (redux)

On 04/01/17 10:55, Stuart Bishop wrote: > > > On 3 January 2017 at 19:07, Rick Harding > wrote: > > I'm looking into this. The bundle deploy feature in Juju 2.0 does > not allow referring to existing machines because it breaks the > reusability of the

Re: using a bundle with manually added machines (redux)

On 3 January 2017 at 19:07, Rick Harding wrote: > I'm looking into this. The bundle deploy feature in Juju 2.0 does not > allow referring to existing machines because it breaks the reusability of > the bundle. > It would be great if Juju started supporting non-reusable bundles too. Its a waste h