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

Really appreciate for the help. Have been stuck here for weeks. AFAIK, no. I attached two result of "juju status" on CloudLab(good) and my server (bad). It's supposed to work without expose the ports. And I just noticed that on my server, most of the services are in blocked status. But it seems

Re: juju bootstrap complaining about "no registered provider for"

That sounds like the juju client knows about the provider but the agent it is installing (jujud) doesn't. You may need to change the version of the client so it guarantees it tries to install the developer build of the agent rather than an official released agent. John =:-> On Jan 4, 2017

Re: juju bootstrap complaining about "no registered provider for"

That sounds like the juju client knows about the provider but the agent it is installing (jujud) doesn't. You may need to change the version of the client so it guarantees it tries to install the developer build of the agent rather than an official released agent. John =:-> On Jan 4, 2017

Re: juju bootstrap complaining about "no registered provider for"

Hi juju Team, Lenovo team is trying to write a new provider with their xclarity product. Currently they are experimenting it mock-provider and did some coding and trying to bootstrap the nodes and facing few issues. Do you think we can give Lenovo team some guidance on how to write a new

Re: using a bundle with manually added machines

FWIW, I think this *could* work, but it may be that we just haven't coded it up. Just as *juju deploy mysql -n 4* will use existing clean machines in the model where appropriate, deploying a bundle should as well (presuming the existing machines match constraints etc as usual). On Tue, Jan 3,

Re: Juju Wikipedia Needs Update

Thanks for the heads up. I'll take a look at it. I've wanted to write for wikipedia sometime. On Tue, Jan 3, 2017 at 12:55 PM James Beedy wrote: > Wikipedia entry for Juju needs update > https://en.m.wikipedia.org/wiki/Juju_(software) > > -- > Juju-dev mailing list >

Juju Wikipedia Needs Update

Wikipedia entry for Juju needs update https://en.m.wikipedia.org/wiki/Juju_(software) -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Kubernetes Provider

Same question got asked yesterday(lxd on kub). Marks answer was it's not roadmapped but make it great and someone will make it happen. On 3 Jan 2017 17:18, "James Beedy" wrote: > Is there any work currently being done out there for a kub provider? Has > anyone looked into

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

This is it: https://jujucharms.com/u/tengu-team/jupiter-notebook-spark/0 Strangely, only the jup*i*ter-notebook-spark charm is visible, the jup*y*ter-notebook charm isn't even though it has the right permissions. perm: Read: - tengu-team - everyone Write: - tengu-team 2017-01-03

Re: using a bundle with manually added machines

Hi Vance, you can deploy a bundle that uses existing machines in the model with the juju-deployer [1] tool. The built in juju deploy method is the first stage in a generic tool and does not allow pointing at existing machines because it means the bundles are not sharable and that you need your

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

Is this charm or bundle somewhere we can look at? On Tue, Jan 3, 2017 at 8:06 AM Merlijn Sebrechts < merlijn.sebrec...@gmail.com> 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

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

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-notebook-spark-0": Field name duplication not allowed with

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

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. However, the manual provider is a bit unique in that it's how you get machines into the system. The bundle deployment should work to pick up

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

It might be a good idea to state in the README that you need to use conjure-up for local clouds. These kind of things can indeed be confusing for people new to this. 2017-01-02 15:36 GMT+01:00 brian mullan : > Thx Marco... my concern was more for folks new to Canonical &