[09:08] <wedgwood> marcoceppi: do you know if a "best practices" document has been put together yet, perhaps in the new docs?
[13:18] <marcoceppi> wedgwood: not yet
[14:36] <AskUbuntu> How do I build juju-core from source? | http://askubuntu.com/q/301107
[15:09] <jcastro> Daviey: so maas sru is well on it's way
[15:09] <jcastro> what shall we do about juju?
[15:40] <Daviey> jcastro: for precise?
[15:44] <jcastro> yeah
[15:45] <jcastro> Daviey: pretend only the LTS exists when I talk about juju and maas. :)
[15:47] <Daviey> heh
[15:47] <Daviey> jcastro: Okay, well - there needs to be an SRU for the co-installable of juju binary (update-alternatives), stolen from Raring
[15:48] <jcastro> Daviey: ok, do we know who is assigned to that?
[15:49] <Daviey> jcastro: Yes
[15:49] <Daviey> jcastro: Jorge is handling that :)
[15:50] <FunnyLookinHat> Hey guys - last I checked Rackspace Openstack wasn't compliant with Juju - what were the exact features that were missing?  I believe they're running the openstack API now
[15:51] <jcastro> Daviey: I mean engineering-wise
[15:51] <jcastro> FunnyLookinHat: if you know they are instead of believe then it should Just Work.
[15:51] <jcastro> did they update recently?
[15:51] <jcastro> because if they did that would be awesome.
[15:53] <FunnyLookinHat> jcastro, well, not 100% sure, but according to their guys in #rackspace , they're nearly identical to trunk at this point... so they're not sure what would be missing.
[15:53] <FunnyLookinHat> In fact, they're closer to it than AWS  :)
[15:54] <jcastro> http://askubuntu.com/questions/132411/how-can-i-configure-juju-for-deployment-on-openstack
[15:54] <jcastro> give it a shot
[15:54] <FunnyLookinHat> will do - thx
[15:54] <jcastro> and lmk if it works, if it does then I will tell the world
[15:54] <jcastro> sorry I'm in the middle of something otherwise I'd try it myself
[15:55] <Daviey> jcastro: There isn't currently an owner.. I'd love to review mgz or Mimms doing it :)
[15:55] <jcastro> Daviey: you tell me what you need, you need mgz/mims to work on it I can work that
[15:56] <Daviey> jcastro: an SRU of the current juju package to support co-installabiltiy
[15:57] <jcastro> ack.
[16:03] <jcastro> FunnyLookinHat: did rax do an announcement or anything?
[16:04] <FunnyLookinHat> jcastro, not that I'm aware, but I'm building a config right now to see what happens
[16:24] <FunnyLookinHat> OS_USERNAME and OS_PASSWORD - for an openstack config - these will be machine usernames/passwords?  or these are the credentials for my openstack account for keystone ?
[16:28] <FunnyLookinHat> well - I'm guessing that isn't the issue, because I was able to get "ERROR 'object-store'"
[16:31] <jcastro> mgz is usually on top of the openstack provider stuff, but he's not around
[16:32] <jcastro> I'll ask him to check on RAX though
[16:33] <FunnyLookinHat> jcastro, well I think I'm nearly there actually - have you seen this error before? http://pastebin.com/puJ9ruVy
[16:33] <FunnyLookinHat> I went ahead and manually created the container in storage to match the yaml and it seemed to work
[16:34] <jcastro> I hadn't even tried it
[16:34] <jcastro> I was assuming they would announce when it all landed
[16:34] <marcoceppi> FunnyLookinHat: that's an odd looking pyjuju error. It probably has something to do with constraints
[16:35] <FunnyLookinHat> marcoceppi, Do tell :)
[16:36] <FunnyLookinHat> constraints = something I can change in my yaml ?
[16:36] <FunnyLookinHat> jcastro, yeah I don't know - they seem fairly open to fixing things, but not to testing necessarily
[16:36] <marcoceppi> I don't know how to fix it, just speculating that it's something juju is trying to consume. So constraints are --constraints and it gives you things like controlling mem, cpu, instance-type, etc
[16:37] <marcoceppi> FunnyLookinHat: do you have juju-core installed? It might be worth testing with that
[16:37] <FunnyLookinHat> Right right -
[16:37] <FunnyLookinHat> marcoceppi, well I tested juju locally ( lxc ) and it worked fine
[16:37] <FunnyLookinHat> Could it have something to do with their machine IDs being single digit numbers?
[16:37] <FunnyLookinHat> err - instance-type IDs
[16:38] <marcoceppi> FunnyLookinHat: that shouldn't affect anything, HP cloud uses numerics for their instances as well
[16:38] <FunnyLookinHat> testing with juju-core now
[16:59] <FunnyLookinHat> marcoceppi, ok - I wasn't aware of juju-core.... with it installed I had to change a few params but got a bit further.  Does this make any sense to you ? http://pastebin.com/raw.php?i=qweMjW4z
[17:08] <FunnyLookinHat> RS guys are guessing it requires content-length
[17:08] <FunnyLookinHat> header, that is.
[18:03] <FunnyLookinHat> Is there a way to enable verbose request logging with juju-core ?
[19:22] <hazmat> FunnyLookinHat, re rackspace.. no network security options
[19:23] <hazmat> i've gotten it farther than that, but that was a little while ago that i was testing
[19:23] <FunnyLookinHat> hazmat, that's why Juju doesn't currently support it?  Or why that single request failed ?
[19:23] <FunnyLookinHat> Ah
[19:23] <FunnyLookinHat> What network security, specifically?
[19:23] <hazmat> i added rax auth support for pyjuju, but its not much use without the rest.
[19:23] <hazmat> FunnyLookinHat, rackspace does do nova sec groups or quantum sec groups
[19:23] <hazmat> ie. no net security at an iaas level
[19:23] <FunnyLookinHat> Ah
[19:24] <hazmat> currently juju assumes that capability.. we could do a noop for it to make it work with rackspace.. capabilities detection against nova and keystone (for quantum)
[19:24] <FunnyLookinHat> Yeah - I'm not sure the loss of that feature would be missed if you could deploy on RS
[19:25] <FunnyLookinHat> I wouldn't miss it at least...  :)
[19:29] <FunnyLookinHat> hazmat, assuming either a no-security option was implemented, or rackspace implemented it, would juju "Just work" at that point?
[19:29] <FunnyLookinHat> I'm only concerned about juju-core btw
[19:29] <FunnyLookinHat> which I believe means... newer?
[19:55] <hazmat> FunnyLookinHat, pretty much
[19:55] <FunnyLookinHat> Ok - good to know.
[19:55] <hazmat> re sec.. re jcore yes newer, its a reimplementation in golang
[20:00] <FunnyLookinHat> Ah ok yeah - that's what I had thought.  :)
[20:38] <hazmat> FunnyLookinHat, re the second error after container creation.. you need to spec a valid image id there as 'default-image-id' in environments.yaml
[20:54] <AskUbuntu> How to preserve custom configurations across reboots when using juju and maas? | http://askubuntu.com/q/301241
[20:54] <AskUbuntu> Juju deploy issue : Connection was refused by other side | http://askubuntu.com/q/301243
[22:59] <_mup_> Bug #1185198 was filed: ERROR 'ServiceRelationState' object has no attribute 'role' <juju:New> <https://launchpad.net/bugs/1185198>
[23:00] <sidnei> hazmat: ^
[23:13] <hazmat> interesting
[23:20] <hazmat> sidnei, finally.. a bug static compilation would have found.. thats a client side error?
[23:22] <hazmat> there's only ref to that in the upgrade_charm