[11:13] <jam> mgz, dimitern: /wave, just figured I'd stop by before heading out again, and see how things are going
[11:13] <mgz> hey
[11:13] <dimitern> jam: hey :)
[11:14] <dimitern> jam: I'm working on the openstack client for go right now
[11:18] <jam> dimitern: sounds reasonable, certainly worth getting familiar with how everything hooks together.
[11:19] <jam> You might try looking at some of the code mgz and I landed in goose trunk
[11:19] <jam> see if you can pull any of the Auth code into your client work.
[11:19] <jam> mgz, dimitern: anyway, I'm off to go do errands, but have a great weekend.
[11:21] <mgz> have a good weekend!
[11:21] <lifeless> goose ?
[11:22] <mgz> lifeless: go openstack... had to make a silly name
[11:22] <lifeless> ah
[11:23] <lifeless> you guys should post to the openstack lists about that :)
[11:23] <lifeless> I'm positive they'd love to hear :)
[11:23] <mgz> maybe when we actually start working on it, also monty trolls enough already
[11:24] <mgz> it'll just be the small amount of client code juju needs to talk to openstack that's currently in the juju.providers.openstack.client module
[11:25] <mgz> unfortunately python-novaclient is neither sufficient, nor stable or reusable enough anyway
[11:26] <mgz> (I have got some code that uses it directly, but you have to be very careful about which version of the client you run against which openstack deployments due to api changes which is more than a little annoying)
[11:26] <mgz> I should recheck if HP have updated their volume stuff yet
[11:30] <dimitern> jam: ok, same to you :)
[20:57] <jtv> matsubara, smoser: I see that the Quantal version doesn't import Quantal boot images, only Precise ones...  That seems to have been fixed in trunk, but how does the import script succeed on trunk given that maas-import-squashfs 404's on the Quantal image!?
[20:59] <matsubara> jtv, you mean the integration tests?
[21:00] <matsubara> I added a workaround to not download the squashfs images
[21:00] <jtv> But that blows up in production, right?
[21:01] <matsubara> don't know what you mean by production but yes, maas-import-pxe-files is broken and there's a bug filed for it: bug 1074167
[21:01] <matsubara> jtv, ^
[21:01] <jtv> AFAICT support for Quantal nodes is blocked on that.
[21:02] <jtv> Thanks for the bug number — I'll annotate the other bug I'm looking into.
[21:02] <matsubara> jtv, according to rvba, not downloading the squashfs only makes things slower but shouldn't break anythign
[21:04] <jtv> Right.  It's an optimization, and I think it's slated to be replaced by some other approach.
[21:05] <jtv> Now, I've been assuming that the quantal version was supposed to support quantal nodes.  Do you know if that's the case?  Or is lack of quantal support a known limitation?
[21:08] <matsubara> jtv, last I tried quantal did work for nodes so not sure what you're referring to
[21:09] <jtv> But the import scripts don't import Quantal boot images.
[21:10] <jtv> In the Quantal version, that is.  They do in trunk.
[21:10] <jtv> So two different problems:
[21:10] <jtv> 1. The Quantal version doesn't import Quantal boot images.
[21:10] <jtv> 2. Importing Quantal boot images fails at the maas-import-squashfs stage.
[21:32] <matsubara> jtv, I see what you mean