please add transcode-cluster bundle to the charm store

Bug #1342847 reported by Dustin Kirkland  on 2014-07-16
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juju Charms Collection
Undecided
Unassigned

Bug Description

This is related to LP: #1342843.

Please add the bundle to the charm store.

Charles Butler (lazypower) wrote :

Dustin,

This bundle is great work! I love how its got a cloud / orange box deployment strategy. However, it appears our tooling is not aware of some of the features you've stuffed in here (that it appears deployer understands)

When running charm proof on the bundle:

W: transcode: charm URL should include a revision
W: transcode: charm URL should include a revision
E: orange-box/nfs: unsupported constraints: tags
E: orange-box/transcode: unsupported constraints: tags

And as I'm sure you know the bundle should be updated with the charm-store flavor of the charm once its been accepted. I'll be keeping my eyes on this bundle as it continues to grow.

Thank you for the submission, and pending resolution of the above tooling output - I'll follow up with additional information regarding this bundle's acceptance.

Charles Butler (lazypower) wrote :

Greetings again,

It appears the tooling output is unaware of the constraints - and that's not a blocker. However the personal branch of the charm is used, and does not specify a revision. This is currently a blocker for charm-store inclusion - but can live on in your personal namespace.

Once the transcoder charm has been promulgated, I urge you to update this bundle to target the charm-store verison, and resubmit for a review at which time it will be reviewed for charm-store inclusion. At which time, move the bug from incomplete to fix-committed.

Thank you for your patience during the review cycle process Dustin!

If you have any questions/comments/concerns about the review contact us in #juju on irc.freenode.net or email the mailing list <email address hidden>, or ask a question tagged with "juju" on http://askubuntu.com.

Changed in charms:
status: New → Incomplete
Charles Butler (lazypower) wrote :

Dustin,

Thank you for the Transcode charm submission. I've validated the charm, and it appears you've addressed Tim's feedback based on the open-port(80) block in the start hook of the charm.

I see no apparent blockers for this charm's inclusion in the charm store, and have started the promulgation now. Please note I've included a quick commit to add the caveats outlined above to the charm's readme, that you may need to backport to your local branch for future updates to prevent branch divergence.

You can find the project page for your charm in the juju charm store here: https://launchpad.net/~charmers/charms/precise/transcode/trunk

with the bug tracker, here:
https://bugs.launchpad.net/charms/precise/+source/transcode

We appreciate your patience during the review cycle, and thank you for a great submission.

If you have any questions/comments/concerns about the review contact us in #juju on irc.freenode.net or email the mailing list <email address hidden>, or ask a question tagged with "juju" on http://askubuntu.com.

Changed in charms:
status: Incomplete → Fix Released
Charles Butler (lazypower) wrote :

And since i Just realized I posted the transcode charm review on the bundle... lets address the bundle properly.

Thanks for the submission Dustin! Everything deployed as was expected in my testing.

The bundle has been promulgated, but it was modified to use the CS: resource instead of LP Branches. The bundle as it exists for orange box deployment using the LP urls may live on in your personal namespace. Anything targeting the recommended charm store should reference a cs: url.

We appreciate your patience during the review cycle, and thank you for a great submission.

If you have any questions/comments/concerns about the review contact us in #juju on irc.freenode.net or email the mailing list <email address hidden>, or ask a question tagged with "juju" on http://askubuntu.com.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers