I've used the manual provider in Juju 1.x, and that functionality was
working at the moment. This is one of the bundles that was working:
https://raw.githubusercontent.com/IBCNServices/tengu-charms/master/bundles/streaming/bundle.yaml
(ignore the "annotations" of the machines)
2016-12-29 20:16 G
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 & following
> the online in
Hi Daniel
On Tue, 3 Jan 2017 at 03:58 Daniel Bidwell wrote:
I started out installing openstack-base and then went back to add more
disks to be used for block storage. The default was /dev/sdb. I added
/dev/sda, /dev/sdc, and /dev/sdd via the juju gui, saved and deployed.
Nothing happened.
I
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
m
Hi all
When releasing my charm I get the following error:
charm release cs:~tengu-team/jupiter-notebook-spark-0
ERROR cannot release charm or bundle: cannot publish charm or bundle:
cannot update base entity for "cs:~tengu-team/jupiter-notebook-spark-0":
Field name duplication not allowed with m
Has juju expose been run on the applications? The charm can declare that
these ports are the ones that are opened if exposed, it's not actually set
until the operator runs the juju expose command on the application.
On Sun, Jan 1, 2017 at 2:58 AM Mac Lin wrote:
>
> Hi,
>
> I'm running CORD maste
Interesting. Thanks for the report.
That's an error I don't think we've seen before, and I can't reproduce
the problem immediately
on one of my own charms.
Do you see the same issue if you try and publish and release the same
charm in the
staging charmstore (set
JUJU_CHARMSTORE=https://api.stagin
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 modifiers
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
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 mod
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 15:0
Is there any work currently being done out there for a kub provider? Has anyone
looked into this yet?
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
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 this yet?
> --
> Juju m
Wikipedia entry for Juju needs update
https://en.m.wikipedia.org/wiki/Juju_(software)
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
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-...@lists.ubuntu.com
>
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, 20
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
provider
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 02:23,
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 th
19 matches
Mail list logo
