| === kadams54-away is now known as kadams54 | ||
| === kadams54 is now known as kadams54-away | ||
| === kadams54-away is now known as kadams54 | ||
| === kadams54 is now known as kadams54-away | ||
| === kadams54-away is now known as kadams54 | ||
| === kadams54 is now known as kadams54-away | ||
| === kadams54 is now known as kadams54-away | ||
| === kadams54 is now known as kadams54-away | ||
| gnuoy | jamespage, I'm guessing you don't have anytime today but if you do I'd love to get https://code.launchpad.net/~gnuoy/charm-helpers/current-dc-leader/+merge/259123 reviewed | 08:32 |
|---|---|---|
| jamespage | gnuoy, aside for a constant for 'DC' lgtm | 08:39 |
| apuimedo | jamespage: ping | 08:42 |
| jamespage | apuimedo, hello | 09:36 |
| apuimedo | jamespage: I am making the changes to neutron-api so that it installs the right repos and it uses the neutron credentials from identityservicecontext ;-) | 09:40 |
| jamespage | apuimedo, +1 | 09:44 |
| === liam_ is now known as Guest15928 | ||
| === Murali_ is now known as Murali | ||
| tvansteenburgh | stub: you are ready for the new trusty/cassandra charm to enter the charm store correct? double-checking before i do it | 15:00 |
| === kadams54 is now known as kadams54-away | ||
| === kadams54-away is now known as kadams54 | ||
| === kadams54 is now known as kadams54-away | ||
| elurkki | Is it possible to configure juju to use specific maas zone for auto selected nodes ? | 19:03 |
| lazyPower | maas tagging should give you that | 19:32 |
| lazyPower | constraints="tag=zone" | 19:32 |
| lazyPower | as an example | 19:32 |
| lazyPower | there may be another tag thats more specific to the zoning integration... | 19:33 |
| lazyPower | natefinch: ericsnow ^ any ideas on this? I'm pretty sure that tags are the only maas specific constraint supported... | 19:33 |
| natefinch | hmm | 19:39 |
| natefinch | you can do juju deploy some_charm --to zone=foo | 19:40 |
| natefinch | There's no way to set up a default zone right now, though | 19:42 |
| lazyPower | perfect, thanks natefinch | 19:53 |
| lazyPower | elurkki: ^ | 19:53 |
| elurkki | lazyPower: Ahaa, ok. Thanks a lot | 19:54 |
| elurkki | Will try this. Currently juju bootstrap errors on mongodb. Wrestling with that first | 19:56 |
| lazyPower | elurkki: whats teh stacktrace? | 19:58 |
| elurkki | The last error I get is : "ERROR juju.cmd supercommand.go:430 cannot initiate replica set: cannot get replica set status: can't get local.system.replset config from self or any seed (EMPTYCONFIG)" | 19:58 |
| elurkki | Not sure if this is from stacktrace | 19:58 |
| lazyPower | i just recently encountered that | 19:59 |
| lazyPower | what my problem was, is it used the public interface that was firewalled and unable to initate itself. let me fish up teh bug i commented on | 19:59 |
| elurkki | Not sure if this is related to fact that DNS can not resolve the node name | 19:59 |
| lazyPower | this was however in an AWS VPC | 19:59 |
| lazyPower | yeah, if its using the nodename that will be it | 19:59 |
| elurkki | lazyPower: I am totally newbie with maas & juju (second day here) | 20:00 |
| elurkki | lazyPower: Not sure even if I have to manually add the DNS entry for DHCP reserved node | 20:00 |
| lazyPower | if you're using maas you shouldn't have to | 20:01 |
| lazyPower | it should be communciating with your region-server, and getting dns info w/ resolveable config back from that | 20:01 |
| elurkki | lazyPower: That is what I thought. I am using Maas yep | 20:01 |
| lazyPower | unless you're using external dns | 20:02 |
| elurkki | MaaS DNS is used | 20:02 |
| lazyPower | ok, yeah it should all be peachy | 20:02 |
| elurkki | lazyPower: Ok. I will check system logs for possible problems | 20:02 |
| lazyPower | https://bugs.launchpad.net/juju-core/+bug/1340663 | 20:03 |
| mup | Bug #1340663: bootstrap issue with replicasets on 1.20.1 with VM on MAAS provider <bootstrap> <landscape> <maas-provider> <mongodb> <juju-core:Invalid> <https://launchpad.net/bugs/1340663> | 20:03 |
| elurkki | lazyPower: Ok, that looks a bit different than mine here. I will compare these a bit. Thanks a lot for pointer | 20:04 |
| lazyPower | np | 20:04 |
| === kadams54-away is now known as kadams54 | ||
| === kadams54 is now known as kadams54-away | ||
| Argon] | it feels like I'm asking a pretty stupid question, but I just don't get it. where does juju search for jujud when bootstrapping with --upload-tools? | 21:22 |
| perrito666 | Argon]: your path | 22:11 |
| Argon] | perrito666: $PATH? and there it's searching for the appropriate tgz? hm, then I have to double check it again, the files are in my path | 22:12 |
| perrito666 | Argon]: i believe it looks for jujud bin in your path | 22:13 |
| perrito666 | in my case /home/hduran/gocode/bin/jujud | 22:13 |
| marcoceppi | in mine it's /usr/lib/juju-1.24-beta2/bin/jujud | 22:13 |
| perrito666 | so I just go install github.com/juju/juju/... and then run the upgrade | 22:13 |
| perrito666 | marcoceppi: showoff | 22:13 |
| marcoceppi | ;) | 22:14 |
| marcoceppi | perrito666: you're the one running from source, I'm just using the stable/devel ppas | 22:14 |
| Argon] | :/ both, jujud and the tarball are in my path but "no matching tools available" | 22:15 |
| perrito666 | marcoceppi: there is no good reason for using upload tools if you are not running from source | 22:15 |
| perrito666 | Argon]: what command are you running? | 22:15 |
| marcoceppi | perrito666: true, I'm just saying | 22:15 |
| Argon] | juju bootstrap --environment amazon --constraints "cpu-power=10 cpu-cores=1 mem=768M" --upload-tools | 22:15 |
| Argon] | and I loaded an appropriate jujud from http://streams.canonical.com/juju/tools/devel | 22:16 |
| Argon] | (this is supposed to be a test, going to use a different jujud later on) | 22:16 |
| perrito666 | throw a --debug in there and paste the result in a pastebin | 22:17 |
| Argon] | oh there's debug? I wondered why -v doesn't work | 22:18 |
| perrito666 | there is --show-logs and --debug which are in turn like -v and -vv | 22:19 |
| Argon] | https://gist.github.com/Argon-/a74263ba5a9309a0a5b4 | 22:20 |
| Argon] | I should run it without --upload-tools to see what's "new", I guess | 22:21 |
| === kadams54 is now known as kadams54-away | ||
| perrito666 | Argon]: it is not working actually | 22:24 |
| perrito666 | you should see 2015-05-15 22:23:12 DEBUG juju.environs.sync sync.go:304 Building tools | 22:24 |
| perrito666 | try having constraints as the last param | 22:24 |
| Argon] | I don't want to build them, though. just pass a already built binary. at least who I understood it: https://github.com/juju/juju/blob/master/cmd/juju/upgradejuju.go#L56 | 22:25 |
| Argon] | ok | 22:25 |
| Argon] | *that's how | 22:25 |
| perrito666 | Argon]: I think build refers to the targz | 22:25 |
| perrito666 | I know for a fact that what I just ran did not actually built it or it would have failed since my code does not compile right now | 22:26 |
| Argon] | nope, no "Building tools", errors out with "no matching tools available" even without --constraints | 22:28 |
| Argon] | (the debug output is exactly the same) | 22:30 |
| perrito666 | :| | 22:31 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!