=== gianr_ is now known as gianr === wedgwood_away is now known as wedgwood === wedgwood is now known as wedgwood_away [06:09] Hey guys, how's the status on the HA juju charms for grizzly openstack going? Last time I tested it out, there were a couple things I had to change to get grizzly a-workin for a certain packages, but they worked very well ;) [06:09] s/a certain/a few/ [07:43] juju, dnsmasq and `.localdomain` | http://askubuntu.com/q/281628 [08:29] Juju not seeing the MaaS slaves... at least not after some time? | http://askubuntu.com/q/281640 === edamato is now known as ed-afk [11:13] Hey , maybe some of you could help. Thanks in advance http://askubuntu.com/questions/281640/juju-not-seeing-the-maas-slaves-at-least-not-after-some-time [12:36] Hey , maybe some of you could help. Thanks in advance http://askubuntu.com/questions/281640/juju-not-seeing-the-maas-slaves-at-least-not-after-some-time === defunctzombie_zz is now known as defunctzombie === defunctzombie is now known as defunctzombie_zz [13:27] hazmat: environment snapshot alternative? === defunctzombie_zz is now known as defunctzombie === wedgwood_away is now known as wedgwood [14:03] is the openstack provider expected to be working in juju-core? [14:10] I ask because I get an error when I try to bootstrap: 'error: secret-key: expected nothing, got ""' [16:21] mramm: is the openstack provider working in juju-core? [16:22] wedgwood: The basic openstack support is in, so you can deploy charms, add relationships, etc [16:23] mramm: when I try to bootstrap: 'error: secret-key: expected nothing, got ""' [16:23] I've copied over my (working) config from pyju [16:23] the config file has changed somewhat [16:23] and go juju does not accept some of the python keys [16:24] ah ok. I spit out the example, but I'm not sure I see where to plug in some of the values [16:25] ok [16:25] did you spit it out with juju generate-config -w [16:25] wedgwood: for this particular case, your issue is probably that keypair auth isn't in yet [16:25] you can use userpass auth for now [16:26] mgz: do you know if juju-core has been used against canonistack? [16:27] wedgwood: yes, it has [16:27] that was the first testing platform [16:27] there are some issues with not having available public IP addresses there [16:28] wedgwood: last i heard it still requires a public ip address per machine, which makes it unusable with canonistack [16:28] there is a workaround [16:28] wedgwood, there is a funny glitch in the parsing that will give you an error for supplying the key value, even if you choose "userpass" [16:29] mramm: perhaps avoiding expose? [16:29] it is more than that, since juju core actually communicates between the agent and the server on the public ip addresses [16:30] anyone have notes? I'd like to give it a try. === beuno_ is now known as beuno [16:31] if AWS is a path of less resistence, I can get started there, but I'd like to start trying things out in openstack === gianr_ is now known as gianr === gianr_ is now known as gianr [17:33] Trying to deploy wordpress. /var/lib/juju/units/wordpress-1/charm/hooks/config-changed failed with exit code 1. The output of hook scripts get logged anywhere? [17:40] I think `unit-get private-address` is failing. Anyone know how I can lookup the CLIENT_ID so I can run `unit-get` from within the container? [17:41] Erik_: check /var/log/juju -- iirc, there are logs in there.. [18:46] is there a known issue with pyjuju where it forever sits with "instance-id: pending" without actually creating an instance in openstack (lcy01)? [18:46] It seems no matter how many times I try to create a three node cassandra cluster, this happens for third node. This wasn't always the case, though. [18:47] and there it is: ProviderInteractionError: Unexpected 413: '{"overLimit": {"message": "SecurityGroupLimitExceeded: Quota exceeded, too many security groups.", "code": 413}}' [18:47] apols, clearly that's on my end [19:02] ev: indeed, but i think the failure mode could be improved. i also had similar issues where i had api quota exceeded or some other error that caused the instance to end up in ERROR state but show as pending in pyjuju. [19:03] sidnei: *nods* [19:03] by api quota exceeded i mean openstack's api rate limiting, where if you do too many api calls in sequence it forces you to back off [19:05] oh interesting. I wasn't even aware that existed. [19:06] I've always associated the error state with the canonistack node running out of free memory :) [19:08] if you're a light user you might notice it, but if you do add-unit -n 15 or something more abusive. ;) [19:18] heh [19:19] canonistack tends to fall over long before I approach 15 units. It's great fun trying to run lp:error-tracker-deployment (~12 units). [19:19] lol === wedgwood is now known as wedgwood_away