[11:05] <lazyPower> http://askubuntu.com/questions/597826/difference-between-deploying-bundle-with-quickstart-or-juju-deployer/597835#597835 - needs citation/approval from UX team 
[11:31] <rick_h_> lazyPower: rgr will do ty
[11:33] <lazyPower> if its totally wrong - i blame hatch.
[11:33]  * lazyPower sips coffee and awates flame-on mode when hatch shows up
[11:33] <lazyPower> *awaits
[11:34] <rick_h_> hah
[11:53] <rick_h_> lazyPower: ok, edits in, let me know what you think
[11:54] <rick_h_> lazyPower: I know that the question was quickstart vs deployer, but I wanted to try to pull out that quickstart was designed/built for that single command to get started with juju, vs just another bundle deployment tool. 
[11:54] <rick_h_> lazyPower: http://askubuntu.com/review/suggested-edits/390134
[12:03] <lazyPower> rick_h_: approved!
[12:03] <lazyPower> ta
[12:03] <rick_h_> lazyPower: feel free to edit back and such as I've not had coffee yet
[12:04] <lazyPower> this is why i made sure to follow up - let the UX peeps shine
[12:04] <rick_h_> hah, ty for catching the question
[12:04] <rick_h_> I have a SO email but it's too much junk I end up auto deleting. I guess I've not set one up for AU
[12:04] <lazyPower> i listen for mup
[12:04] <lazyPower> or the ask bot - i forget which drops in #juju with the links
[12:05] <rick_h_> ah right, yea I've caught that sometimes but don't watch them overnight/etc
[12:05] <lazyPower> highlights are amazing for channel scanning :D
[12:05] <lazyPower> but i'm maybe 1/4 as popular as you are
[12:05] <lazyPower> so it may not be  agood method for you
[12:06] <rick_h_> heh, /me ducks and hides in a corner
[12:11] <lazyPower> :)
[13:33] <beisner> good morning.  bug 1413654 is marked fix-released, but i'm still seeing the issue as of cs:trusty/juju-gui-21.   is there a known work-around, or alternate branch that includes the fix?
[13:33] <mup> Bug #1413654: Bundle Export link broken in Juju-Gui 16+ <juju-gui:Fix Released by hatch> <https://launchpad.net/bugs/1413654>
[13:36] <beisner> fyi hatch ^
[13:39] <rick_h_> beisner: is this a deployed gui or the demo?
[13:40] <rick_h_> beisner: and what is the stack you've got you're exporting? 
[13:40] <beisner> rick_h_, deployed.
[13:40] <rick_h_> beisner: a quick test on the demo site with one deployed charm works so might be something in one of the charms is having a hard time getting serialized
[13:40] <rick_h_> beisner: would love to have a screenshot or details on what's in the stack there to reproduce
[13:41] <beisner> rick_h_, it's a full stack openstack bundle that i'm validating in prep for charm store
[13:41] <beisner> i'll link you to it shortly.
[13:41] <rick_h_> beisner: ty
[13:42] <rick_h_> beisner: yea, going to guess the "to" error is around placement 
[13:42] <rick_h_> beisner: so some bug specific to the placement of the services in your bundle we'll have to replicate/trace down
[13:45] <beisner> rick_h_, here are the juju stats  http://paste.ubuntu.com/10615355/
[13:46] <rick_h_> beisner: ok yea the direct placement stuff is still in progress as we update the deployer and have to update the gui export once that lands. It shouldn't traceback at you though for sure while we get that working
[13:48] <beisner> rick_h_, ok i see - something is in-flight.   let me know if there's more i can do to help on the bug.
[13:49] <rick_h_> beisner: np, ty for the report and prod on it. 
[13:50] <beisner> rick_h_, it's really not critical, i was going to use it mostly for x/y coords instead of thinking hard about those coords.  ;-)
[13:51] <beisner> rick_h_, i think it will gather add'l heat though, as we come up with additional openstack bundles for the charm store.   holler back if you need to to throw something at it.
[13:52] <rick_h_> beisner: ok to use your pastebin in the new bug report?
[13:52] <beisner> rick_h_, ha!  just posted it.
[13:53] <rick_h_> beisner: ok, I'm going to move it to a new bug around the placement directive stuff
[13:53] <rick_h_> beisner: just to split it as it's a different line of work/issue
[13:53] <beisner> rick_h_, ok thank you
[13:56] <rick_h_> beisner: https://bugs.launchpad.net/juju-gui/+bug/1433096 is the new bug and https://code.launchpad.net/~makyo/juju-deployer/machines-and-placement/+merge/251857 is the WIP on the deployer side to let us export stuff that has machine placement stuff in it
[13:56] <mup> Bug #1433096: bundle export link fails when placement is involved <juju-gui:Triaged> <https://launchpad.net/bugs/1433096>
[13:57] <beisner> rick_h_, great, thanks again.
[14:38] <beisner> rick_h_, the jujucharms.com authors page advises "Refer to the Bundles page for instructions on how to create bundles of charms and submit them to the store."   But the link is broken (https://jujucharms.com/docs/charms-bundles.html).  Do I need to raise a bug somewhere?
[14:38] <beisner> Not sure which channel/team to ask.
[14:40] <beisner> Referring page = https://jujucharms.com/docs/authors-charm-store
[14:40] <rick_h_> beisner: sec looking. 
[14:40] <rick_h_> beisner: yea, it's in the nav link as well, and only that page seems to not route
[14:41] <rick_h_> but does exist in the docs so filing a bug for us to inviestigate and if it's docs related we'll move the bug to the docs
[14:41] <rick_h_> beisner: we've also got a release we're working on getting out that fixing some routing so might be fix on the way but will verify
[14:41] <rick_h_> beisner: https://github.com/CanonicalLtd/jujucharms.com/issues/58
[14:41] <beisner> rick_h_, is there a working (perhaps not-yet-linked) url for the bundles page?
[14:41] <rick_h_> fabrice: can you peek at https://github.com/CanonicalLtd/jujucharms.com/issues/58 and chase that please?
[14:42] <rick_h_> beisner: it should be https://github.com/juju/docs/blob/master/src/en/charms-bundles.md
[14:42] <beisner> rick_h_, ack, thanks again!
[14:42] <rick_h_> np
[14:43] <rick_h_> beisner: yea, looks like it's working on our QA site http://qa.storefront.theblues.io:6543/docs/1.20/charms-bundles so that fix is probably on the way in the deployment
[14:43] <beisner> sweet
[14:45] <fabrice> rick_h_: so I have nothing to look at :)
[14:45] <rick_h_> fabrice: yea, looks like not sorry
[14:46] <fabrice> rick_h_: I like it 
[15:32] <marcoceppi> How do you look up bundles in v4 api?
[15:33] <hatch> marcoceppi: just query for bundle
[15:33] <rick_h_> marcoceppi: type=bundle
[15:33] <hatch> oh woops sorry heh the api not the website :)
[15:33] <rick_h_> https://api.jujucharms.com/v4/search?type=bundle&limit=1000
[15:33] <marcoceppi> so, how does that look in the URL? https://api.jujucharms.com/v4/mediawiki-scalable ?
[15:33] <rick_h_> marcoceppi: ^
[15:33]  * hatch goes away
[15:34] <marcoceppi> yeah, but if I wanted to get the bundle.yaml file for a bundle
[15:34] <marcoceppi> I'd need to know it's address, right?
[15:34] <rick_h_> https://api.jujucharms.com/v4/bundle/mediawiki-scalable-9/archive/bundle.yaml and https://api.jujucharms.com/v4/bundle/mediawiki-scalable-9/archive/bundles.yaml.orig
[15:35] <marcoceppi> ah, so the whole not found message for bundle/mediawiki-scalable-9 is because I didn't give it a query?
[15:35] <rick_h_> marcoceppi: https://api.jujucharms.com/v4/bundle/mediawiki-scalable/meta/any for just checking if it exists
[15:35] <rick_h_> marcoceppi: right, you need to ask for something
[15:35] <marcoceppi> there we go, thank you
[15:35] <rick_h_> https://api.jujucharms.com/v4/bundle/mediawiki-scalable/meta/id for instance
[15:36] <rick_h_> np
[15:36] <rick_h_> marcoceppi: and jcsackett is working today on pulling the python lib out so hopefully be end of week we'll have the open source client in the juju org
[15:36] <marcoceppi> rick_h_: I finally got around to doing that jujusvg as a webservice, just adding some finishing touches
[15:36] <rick_h_> marcoceppi: ah nice
[15:37]  * rick_h_ will be eager to check it out
[15:37] <marcoceppi> <3 the jujusvg code btw frankban
[15:37] <rick_h_> that's Makyo 
[15:37] <rick_h_> ^
[15:37] <marcoceppi> fuuuu
[15:37] <marcoceppi> w/e all those who hath made it
[15:37] <hatch> I reviewed a branch of it once...
[15:37] <rick_h_> well his baby
[15:37] <hatch> yay me!!
[15:37] <rick_h_> hah!
[15:38] <hatch> haha
[15:38] <rick_h_> hatch: photo bombs the credit reel on jujusvg
[15:38] <hatch> lol bingo
[15:38] <rick_h_> jcsackett: so let's keep marcoceppi in the loop on the progress and pr and such when we get things pulled apart ^
[15:39] <marcoceppi> yes pls, righ tnow I'm just hitting endpoints but having the API library would be boss
[15:39] <jcsackett> rick_h_: ack
[15:39] <rick_h_> jcsackett: <3
[15:39] <marcoceppi> also I can start moving our tools over
[15:39] <jcsackett> marcoceppi: we should be able to help you out real soon. 
[15:39] <marcoceppi> \o/
[15:40] <jcsackett> And I look forwards to people outside our team using it. 
[18:46] <marcoceppi> Does the v4 api give a status code other than the json Message/Code?
[18:46] <marcoceppi> nvm, yes it does
[18:51] <hatch> :)
[20:05] <aisrael> This may already be a known issue (and I opened a bug in case it's not), but this page is a 404: https://jujucharms.com/docs/tools-charm-tools/
[20:24] <jcastro> aisrael, where do you see that link referenced?
[20:25] <jcastro> oh, in the sidebar
[20:25] <jcastro> https://jujucharms.com/docs/tools-amulet/ is also busted
[20:25] <rick_h_> aisrael: yep, we're working on getting a deployment that has that fix in for some routing issues with trailing slashes and such http://qa.storefront.theblues.io:6543/docs/1.20/tools-charm-tools
[20:25] <aisrael> jcastro: https://jujucharms.com/docs/, http://pythonhosted.org/charmhelpers/getting-started.html#installing-charm-tools
[20:25] <rick_h_> jcastro: aisrael yep, hit it with the bundle one as well
[20:25] <aisrael> rick_h_: awesome, thanks
[20:25] <jcastro> rick_h_, do we have a way of just spitting out everything with a 404?
[20:26] <rick_h_> jcastro: not yet
[20:26] <rick_h_> jcastro: we've got the sitemap stuff and once we have that we want to start link crawling and referencing that against the sitemap which would bring up the 404s
[20:26] <jcastro> I found a few yesterday I fixed by hand
[20:27] <rick_h_> k
[20:27] <rick_h_> yea, we need to toss a link crawler at the site but waiting on the current fixes + the sitemap stuff
[20:27] <jcastro> after we sort it it would be nice to just have the docs builder or whatever autofile a bug on new 404's
[20:27] <rick_h_> rgr