Re: Deploying Juju charms from Github

[Mark Shuttleworth]

On 15/04/15 11:51, Robert Day wrote:
> I agree that not having juju-deployer handle the Git side of things, and just 
> working locally from a Git checkout, would be simpler – but I don’t think 
> that sort of bundle would work in the Juju GUI, because the extra steps 
> needed mean that you can’t drag-and-drop it. Have I understood correctly?

There's a current limitation with bundles in the GUI, because they are
actually deployed server-side, which makes the drag-and-drop interaction
awkward. However, I just saw a lighting talk demo of client-side bundle
handling, so drag-and-drop will work with any bundle, including bundles
that reference local charms managed on Github :)

Would expect that to show up relatively soon, based on the demo!

Mark

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Review/Re-review of charms submitted by ibmcharmers

[Antonio Rosales]

On Wed, Apr 15, 2015 at 7:33 PM, Johnny Shieh  wrote:
> Please review the following submitted charms:

Hello, and thanks for you contributions to the Juju Charm community in
the xCAT charm and following up on the WebSphere MQ charm.
Encapsulating your team's IBM software expertise into these charms is
valuable to the Juju Ecosystem as well the IBM ecosystem. Looking
forward to see the solutions Juju users put together with MQ, xCAT,
and GPFS now that they are in the Charm store.

>
> IBM MQ (formerly known as WebSphere MQ)
> https://bugs.launchpad.net/charms/+bug/1432489

A commented added. The readme looks to be updated with the feedback
given, but we are still coordinating binaries for testing. For review
we are leveraging the 90 day trail, but we also need to investigate
longer term binaries for Charm CI testing.

>
> This has been commented by the charm team.  A response and change has been
> provided.
> Asking for re-review.
>
> GPFS
> https://bugs.launchpad.net/charms/+bug/1431045

Comment added to the bug. Outstanding item is coordinating the binary
for deployment verification.

>
> This has been commented by the charm team.  A response and change has been
> provided.
> Asking for re-review.
>
> xCAT
> https://bugs.launchpad.net/charms/+bug/1441622

Comment added to the bug. Error on downloading the .deb needs to be
resolved as well as some minor fixes.

-thanks,

Antonio
>
>
>
>
>
> 
> Johnny Shieh
> CTO Office - Software Defined Systems
> jsh...@us.ibm.com
> Mobile: 512-680-1375
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Review/Re-review of charms submitted by ibmcharmers

[Johnny Shieh]

Please review the following submitted charms:

IBM MQ (formerly known as WebSphere MQ)
https://bugs.launchpad.net/charms/+bug/1432489

This has been commented by the charm team.  A response and change has been
provided.
Asking for re-review.

GPFS
https://bugs.launchpad.net/charms/+bug/1431045

This has been commented by the charm team.  A response and change has been
provided.
Asking for re-review.

xCAT
https://bugs.launchpad.net/charms/+bug/1441622






Johnny Shieh
CTO Office - Software Defined Systems
jsh...@us.ibm.com
Mobile: 512-680-1375-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Reminder: Juju Office Hours, 16 April (tomorrow)

[Jorge O. Castro]

Hello everyone!

Just a reminder that we have Juju office hours tomorrow. This is a
live Google Hangout where we talk about Juju, answer questions, and in
general get everyone up to speed on what's going with Juju. Classroom
instruction can be provided to anyone who wants to participate, in
general we'd like to see the audience drive the topic.

Here's the info:

#juju on Freenode
http://ubuntuonair.com to listen in.

I'll paste in the Google Hangout link in IRC when we start if people
want to join in and ask questions.

1300 (1pm) PDT
1600 (4pm) EDT
2000 (8pm) UTC

-- 
Jorge Castro
Canonical Ltd.
http://juju.ubuntu.com/ - Automate your Cloud Infrastructure

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

RE: Deploying Juju charms from Github

[Robert Day]

Hi Kapil,

I agree that not having juju-deployer handle the Git side of things, and just 
working locally from a Git checkout, would be simpler – but I don’t think that 
sort of bundle would work in the Juju GUI, because the extra steps needed mean 
that you can’t drag-and-drop it. Have I understood correctly?

On the syntax for bundle files, one thing I might want to do is take my five 
charms (all hosted in one Git repository) and bundle them together with several 
charms from someone else (which might all be hosted in the same repository). I 
can’t quite see how the syntax you suggest (one Git repository per bundle) 
would allow that. Something like:

> clearwater:
>  services:
>"clearwater-bono":
>  charm: "clearwater-bono"
>  branch: 
> "https://github.com/Metaswitch/clearwater-juju@46785ea8368a47c4351a516bb9a76763f6d4a952";
>  charms_subdirectory: "charms/precise/clearwater-bono"
>"clearwater-sprout":
>  charm: "clearwater-sprout"
>  branch: 
> "https://github.com/Metaswitch/clearwater-juju@46785ea8368a47c4351a516bb9a76763f6d4a952";
>  charms_subdirectory: "charms/precise/clearwater-sprout"
>"somethingElse":
>  charm: "somethingElse"
>  branch: "https://github.com/someoneElse/somethingElse@abcde";
>  charms_subdirectory: "contrib/juju-charms"
Does that seem OK to you, or do you still prefer the single charm_repository 
option?

Thanks,
Rob

From: Kapil Thangavelu [mailto:kap...@gmail.com]
Sent: 14 April 2015 13:26
To: Robert Day
Cc: juju@lists.ubuntu.com
Subject: Re: Deploying Juju charms from Github

On Tue, Apr 14, 2015 at 6:09 AM, Robert Day 
mailto:robert@metaswitch.com>> wrote:
Thanks for the response! I’ve:
* found https://code.launchpad.net/~whitmo/juju-deployer/git-clone-fix and 
applied those changes to my local copy of juju-deployer
* removed the “--depth 1” from vcs.py
* corrected my bundle to the below

>  services:
>"clearwater-bono":
>  charm: "clearwater-bono"
>  branch: 
> "https://github.com/Metaswitch/clearwater-juju@46785ea8368a47c4351a516bb9a76763f6d4a952";

I then get this error:

2015-04-14 09:33:21 Using deployment clearwater
2015-04-14 09:33:21 Starting deployment of clearwater
2015-04-14 09:33:21 Invalid config charm clearwater-bono zone=clearwater.local
2015-04-14 09:33:21 Deployment stopped. run time: 0.52



I’m pretty sure that this is because juju-deployer expects the charm’s 
metadata.yaml file (or config.yaml, etc.) to be in 
precise/clearwater-bono/metadata.yaml, whereas due to the way my Git repository 
is laid out, it’s actually in 
precise/clearwater-bono/charms/precise/clearwater-bono/metadata.yaml (the Git 
repository is checked out correctly to precise/clearwater-bono, but my charms 
are all in the charms/precise subdirectory of that repository – it’s at 
https://github.com/Metaswitch/clearwater-juju if you want to see what I mean).

specifically the error is referencing the key 'zone' is not found in the 
charms's config.yaml. if you have a single directory of charms in vcs, its a 
bit easier to not have deployer do vcs, ie. checkout, set JUJU_REPOSITORY env 
var to root of checkout dir, omit vcs info from the bundle config, and then 
just juju-deployer. Granted that has the downside of requiring additional 
instructions when sharing.


I think I could correct this by having one repository per charm, but I’d like 
to keep all my charms in the same repository if possible – there are six or 
seven of them and they’re quite closely related. It feels like having an option 
in the bundle to say “the charm files are in this subdirectory of the Git 
repository” would be useful – I might try and put that patch together, unless 
there are reasons why that wouldn’t be a good idea (or unless something similar 
already exists). Something like:

> clearwater:
>  services:
>"clearwater-bono":
>  charm: "clearwater-bono"
>  branch: 
> "https://github.com/Metaswitch/clearwater-juju@46785ea8368a47c4351a516bb9a76763f6d4a952";
>  charms_subdirectory: "charms/precise/clearwater-bono"
>"clearwater-sprout":
>  charm: "clearwater-sprout"
>  branch: 
> "https://github.com/Metaswitch/clearwater-juju@46785ea8368a47c4351a516bb9a76763f6d4a952";
>  charms_subdirectory: "charms/precise/clearwater-sprout"

actually i think a different syntax would be nice.

clearwater:
   charm_repository: https://github.com/Metaswitch/clearwater@987132asdf
   services:
  charm: clearwater-bono

that repo directory would get checked out, and set as the JUJU_REPOSITORY for 
the rest of the services, ie. propagate for all local charms automatically, but 
they could override as needed.  patches welcome.

cheers,

Kapil


Thanks,
Rob


From: Kapil Thangavelu [mailto:kap...@gmail.com]
Sent: 14 April 2015 05:57
To: Robert Day
Cc: juju@lists.ubuntu.com
Subject: Re: Deploying Juju charms from Github


There's a few things going on. The charm key in the bundle shou