=== ant_ is now known as Guest28866
=== urulama__ is now known as urulama
=== perrito667 is now known as perrito666
=== kwmonroe_ is now known as kwmonroe
=== urulama is now known as urulama__
[20:51] <cory_fu> Hey, question about charm2 upload and bundles for the uiteam.  I've been told that `charm2 upload` should just work with bundles, but I get a message about about it being unable to open metadata.yaml, which obviously the bundle doesn't have
[20:51] <cory_fu> Is this the correct command form?  charm2 upload ~bigdata-dev/bundles/apache-core-batch-processing
[20:51] <rick_h_> cory_fu: shouldn't need the /bundles part of the url
[20:51] <bac> cory_fu: you need to give it a path
[20:51] <rick_h_> ?
[20:52] <bac> cory_fu: so if you're in the bundle, use a . after the upload command
[20:52] <bac> cory_fu: but i've never used upload with a bundle, just charms
[20:52] <cory_fu> bac: How does it know where to upload it into the store?
[20:52] <cory_fu> Also, `charm2 upload --help` says to use `charm upload ~bob/bundle/django`
[20:53] <bac> cory_fu: the help says that the directory of where the bundle lives is optional and the final argument is the charmstore namespace
[20:53] <cory_fu> Hrm.  Using that form (bundle, singular) says it can't find my local path.  I think I need to use "bundle" locally as well
[20:53] <cory_fu> Ah, I see
[20:53] <bac> cory_fu: so if you don't give a local path it assumes it is in your JUJU_REPOSITORY directory
[20:54] <cory_fu> Perfect.  That worked.  Thanks!
[20:54] <rick_h_> cory_fu: so try charm2 upload . cs:~bigdata-dev/apache-core-batch-processing
[20:54] <bac> cory_fu: that is why when uploading charms i always have my cwd to be the directory and use .
[20:54] <rick_h_> cory_fu: ok coolio
[20:55] <rick_h_> cory_fu: did you need the /bundle in the url or did you drop that?
[20:55] <bac> cory_fu: yeah, could you paste the command that worked?
[20:55] <cory_fu> I will also update my local path convention to use "bundle" instead of "bundles" so that it matches the command's expectations
[20:55] <cory_fu> Yes, I did
[20:55] <cory_fu> charm2 upload . ~bigdata-dev/bundle/apache-core-batch-processing
[20:55] <rick_h_> hmm, :( that the bundle was there
[20:56] <cory_fu> Leaving it out complains about metadata.yaml, so it must be assuming it's a charm
[20:56] <rick_h_> gotcha, yea that's :(
[20:56] <rick_h_> we'll have to work on that
[20:56] <bac> cory_fu: i also like to use the 'cs:' prefix so it is obvious.  also it prevents ~ expansion if your local username is the same.
[20:56] <bac> but clearly not a problem with your example
[20:57] <cory_fu> bac: Good advice.  Seems like it'd be good to update the --help examples to use cs:
[20:57] <bac> cory_fu: i thought i had.
[20:57] <rick_h_> cory_fu: it is, but in trunk and not in the release
[20:57] <bac> ah
[20:57] <rick_h_> bac: you did, but we've not released a new charm2 lately
[20:57] <bac> we should do that.  :)
[20:58] <rick_h_> +1, hoping that we get that worked out and updated. the /bundle should be skipable as well.
[20:58]  * rick_h_ files a bug
[21:12] <cory_fu> Are we going to get a new release of the GUI soon with the title updates to jujusvg?
[21:19] <rick_h_> cory_fu: soon, the title updates are in bjt needs a charmstore release
[21:20] <cory_fu> Also, the X and Y values for placement... Are those for the top-left corner?  I notice that the circles for subordinates are smaller than normal services, so it makes calculating the placement a bit harder.
[21:23] <hatch> cory_fu: don't calculate the placement, do it in the GUI then export the bundle
[21:23] <hatch> much easier
[21:23] <hatch> and less error prone for typos :)
[21:27] <cory_fu> hatch: Any support for grid-snapping in the GUI?
[21:28] <hatch> nope
[21:28] <cory_fu> Would be nice to have.  :)
[21:28] <hatch> yeah it's been on the roadmap for 3 years
[21:29] <hatch> but to much else to do :)
[21:29] <hatch> but honestly building bundles in the gui and then exporting it saves so much time than trying to write it by hand
[21:29] <hatch> even if to just get it close