[00:15] <Volka> hi
[00:16] <Volka> does it have anything to do with juju island?
[00:20] <jcw4> Volka: no
[00:39] <Volka> too bad
[00:39] <Volka> juju island is great
[00:39] <jcw4> hehe
[00:39] <Volka> have you been?
[00:39] <jcw4> no.  sounds great though.
[00:40] <Volka> https://en.wikipedia.org/wiki/Jeju_Province
[11:35] <dweaver`> I have a problem with juju bootstrap: fails with invalid SSH key, using the same key as I have uploaded to Launchpad.  Used to work, but now fails on EC2 and HPCloud both tested and both fail with the same error.
[11:35] <dweaver`> lazyPower, ping^
[11:36] <lazyPower> dweaver`: juju uses the sshkeys in ~/.juju/ssh - can you juju ssh into the unit in question?
[11:37] <lazyPower> oh wait, bootstrap?
[11:37] <lazyPower> hang on let me get some coffee
[11:40] <dweaver`> juju-core version 1.18.1
[11:43] <lazyPower> dweaver`: can you show me the output from a bootstrap with debug output? Juju bootstrap --debug
[11:44] <lazyPower> Make sure you scrub any keys, it may output sensitive info
[11:48] <dweaver`> Aha!  Actually when using juju bootstrap --debug it reports that the SSH key is invalid, but then completes, but without debug it fails.
[11:50] <dweaver`> I can work around it using --debug then
[11:53] <lazyPower> thats... strange
[11:53] <dweaver`> http://pastebin.ubuntu.com/7607387/
[11:53] <lazyPower> dweaver`: can you file a bug on this?
[11:53] <dweaver`> Shows the beginning of the output where it states invalid SSH key.
[11:54] <lazyPower> I see the line complaining : 2014-06-07 11:44:53 WARNING juju.utils.ssh authorisedkeys.go:310
[11:55] <dweaver`> Yes, I can file a bug on Monday when I am back at my desk, just trying to get the demos running for some presentations here at Tadhack
[11:55] <lazyPower> brilliant
[11:55] <lazyPower> Hows that going?
[12:49] <dweaver`> lazyPower, going OK, just setting up orange box demo and EC2 and openstack demos of telco apps, still debugging, but we are getting there.
[13:44] <lazyPower> dweaver`: are you going to be trying to get the metaswitch charms up on orangebox today?
[13:45] <dweaver`> lazyPower, yes, going to try it when the guys here have finished the bundle.
[13:45] <lazyPower> if so, you're in for a rough time. The clearwater- prefix charms all call from the magic IP in AWS for metadata. I just ran into this on my MAAS cluster. You may need to ping matt to slime whaver values he's expecting from the AWS metadata.
[13:46] <dweaver`> lazyPower, we are also seeing some issues with Juju defaulting to i386 on EC2
[13:46] <dweaver`> But we are specifying amd64 as a constraint to get round it
[13:47] <lazyPower> dweaver`: constraints: "arch=amd64"
[13:47] <lazyPower> yeah, thats the proper method to get 64 bit hosts.
[13:48] <dweaver`> has this behaviour changed recently, I thought the default was 64 bit
[13:49] <lazyPower> not sure. I know its possible to set as an environment constraint so you dont have to specify it on every charm ever.
[14:00] <dweaver`> lazyPower, which version were you using to test, Matt reckons that issue was fixed last night, but if you deploy with the bundle specifying versions, it would have pulled the older version of the charm
[14:01] <dweaver`> The latest bundle should be deploying the latest charm versions.
[14:01] <lazyPower> dweaver`: I haven't used any of their bundles - it's with revision 4 from ~matt-williams-x branch
[14:01] <lazyPower> specifically on clearwater-sprout
[14:02] <dweaver`> He is just checking it
[14:02] <lazyPower> if he wants additional eyes on it have him join #juju and i'll run through some test scenarios with him. I'm testing the latest release of DNSAAS that i just cut
[14:03] <dweaver`> We haven't had any issues with DNSaaS, I found it deployed OK on both the OB and on EC2
[14:03] <lazyPower> \o/
[14:03] <dweaver`> Nice charm too.
[14:04] <lazyPower> it had some issues on Thursday with zonefile corruption
[14:04] <lazyPower> I've since resolved those and made it more fault tolerant
[14:04] <lazyPower> + backups! - atomic file rewriting is scary
[14:05] <lazyPower> thanks for the +1 dweaver`
[14:07] <dweaver`> Matt's going to join the channel.
[14:42] <dweaver`> lazyPower, We ran out of time and didn't get it working for the OB, but we got everything working on EC2 so we are good for now.
[14:42] <dweaver`> And Matt had to leave for his flight home
[14:44] <haxx0r> www.anon.fm
[22:24] <designated> jamespage, for the ceph charm, I can see functions getting defined in host.py (def list_nics(nic_type)).  but I don't see this function being called anywhere else in the charm.  from what I understand when building relationships, the charm will just use the first NIC it finds.  How can I just statically assign this to a variable somewhere?