/srv/irclogs.ubuntu.com/2014/11/28/#juju.txt

bradmanyone about who can help with a problem deploying something in juju?  I'm getting an odd traceback when I try to add a service using juju deployer00:50
LinStatSDRWhat is the error bradm01:17
bradmLinStatSDR: http://pastebin.ubuntu.com/9276609/, using a juju deployer config01:19
lamontI say juju upgrade-charm and the bundle it delivers is the _old_ contents of the charm directory.. (juju 1.16.5)  - thoughts?02:19
captineHi all.  Can anyone point me to a write up (if available) of using Juju and MAAS in a corporate environment.  My company currently has an IBM pureflex running Hyper-V on all nodes and VM's on them.  All is managed as if the machines were physical e.g. no automated provisioning etc.  I am just trying to see if Juju is more for dev type people or if there is a usecase for it in a corporate where vm's dont chane much.04:14
=== CyberJacob|Away is now known as CyberJacob
=== urulama_ is now known as urulama
=== erkules_ is now known as erkules
=== CyberJacob is now known as CyberJacob|Away
=== liam_ is now known as Guest93453
=== rogpeppe1 is now known as rogpeppe
mgzgnuoy: how busy are you today?11:57
gnuoymgz, that seems like a loaded question...11:57
gnuoymgz, I'm working on adding a feature so I can take a pause11:57
mgzso, I was looking on the train at the 'right' way of doing devel tools with juju and simplestreams11:58
mgzI think I have all the bits down now11:58
mgzso, if you want to retry the windows workloads tools part the right way, we could have a quick bash at that11:59
gnuoyok, I have a call in 1 min, then I was hoping to grab some lunch but it'd be great to catch up about that this afternoon if taht's ok?11:59
mgzthat works for me, poke when available11:59
gnuoymgz my world is running behind, I'm heading to lunch now13:37
hazmatbradm, do you have a pastebin for the traceback?14:05
hazmatbradm, what version of juju?14:05
hazmatbradm, do you have a service 'infra' in your deployer config?14:06
=== tdc_ is now known as tdc
gnuoymgz, I'm champing at the bit14:17
mgzgnuoy: okay, I'm back from lunch too14:45
gnuoymgz, ok, hit me14:47
mgzso, rough plan14:49
mgzmake tools tarballs for a trunk juju version for trusty and windows14:49
mgzgenerate tools streams14:49
mgzbootstrap with --metadata-source pointing at that directory14:50
gnuoymgzAre you suggesting I bootstrap with 1.20.12 tools?14:52
mgzgnuoy: no14:55
mgzwe bootstrap with the devel, we just need to give bootstrap the path to our carefully constructed simplestreams version14:56
gnuoyok14:57
=== roadmr is now known as roadmr_afk
=== scuttle|afk is now known as scuttlemonkey
mgzgnuoy: do you want to ssh into a box I have to poke things? or some other means to pair on this?15:02
gnuoymgz, I need to disappear for 20mins but I'll be back after that. I'd like to get you access to the lab I'm working in tbh15:03
mgzah, I should check if I have the vlan stuff set up on here15:03
=== scuttlemonkey is now known as scuttle|afk
gnuoymgz, do you have vpn access to the qalab ?15:31
gnuoymgzare you happy with juju-1.21-beta3-trusty-amd64.tgz juju-1.21-beta4-win2012hvr2-amd64.tg being the tools?15:32
mgzgnuoy: they need to be the same beta15:37
=== xerxas_ is now known as xerxas
gnuoymgz so there's a trusty beta 3 but no windows and a windows beta 4 but no trusty, right ?15:40
mgzgnuoy: there are both, it's just a question of putting in the same versions15:42
mgzsec, I just need to restore all my sessions (X login had a bit of a fit)15:43
gnuoymgz, Are you saying that there is trusty beta 4 out there somewhere ?15:43
=== roadmr_afk is now known as roadmr
mgzthere is trunk 1.21 which reports as the upcoming beta415:43
gnuoymgz, I'm looking at https://streams.canonical.com/juju/tools/devel/ fwiw15:44
mgzgnuoy: actually, let's just use tools from this job: <http://reports.vapour.ws/releases/2121>15:44
gnuoymgz, Build Artifacts  empty  <- on the few I've tried15:47
mgzgnuoy: `wget http://data.vapour.ws/juju-ci/products/version-2121/win-client-build-installer/build-1325/juju-1.21.0-win2012-amd64.tgz`15:50
mgzgnuoy: `wget http://data.vapour.ws/juju-ci/products/version-2121/publish-revision/build-1237/juju-core_1.21.0-0ubuntu1~14.04.1~juju1_amd64.deb`15:51
mgzthen `dpkg-deb -x juju-core_1.22-alpha1-0ubuntu1~14.04.1~juju1_amd64.deb extracted-bin15:51
mgzand get the jujud binary from in there for the trusty/amd64 combo15:52
mgzgnuoy: then my instructions from earlier has `tar -cf tools/devel/juju-`~/go/bin/juju version`.tgz -C ~/go/bin jujud` - but this is going to be different for these two tools15:53
mgzthen we put the two tarballs in tools/devel/ under our working dir15:54
mgzand run `juju-metadata --debug generate-tools --clean --stream devel -d .`15:54
mgzcheck that the streams data generated has both tools15:55
gnuoymgz ok so far: http://paste.ubuntu.com/9284701/16:00
gnuoylet me redo with the devel dir16:03
mgzgnuoy: okay, do releases rather than devel (pretty much the same, just different environments.yaml setting fun)16:03
mgzreleases is fine16:03
mgzI did devel mostly because it seemed more fun16:04
gnuoymgz happy for me to: juju bootstrap --metadata-source /var/lib/jenkins/.juju/tools  ?16:04
mgzgnuoy: next step is bootstrap with that `juju --debug bootstrap --metadata-source . -e $ENV`16:05
mgzgnuoy: I think not with the tools, it's the dir containing the tools16:05
gnuoyack16:05
mgzI'd use a big buffer or tee out/err somewhere16:06
mgzbecause you need to read a lot of simplestreams junk if something's not right16:06
mgzafter that it's add-machine with da windows16:07
mgzgnuoy: how it going?16:25
mgzI'll need to reboot for standup ina sec so will be off irc briefly16:25
gnuoymgz one explosion down to the tgz not really being z16:25
gnuoyrebootstrapping now16:25
mgzyeah, I did .tar.gz first time around... which tar did z for me, but juju metadata refused to acknowledge16:28
gnuoymgz, bootstrap done.Happy for me to go on to the windows deploy ?16:29
gnuoyme goes for it16:32
mgzgo for it16:33
gnuoyarggh, I missed a v out of the windows tools name16:33
mgzgnuoy: whoops16:34
mgzI'll be back in ~10 or so, tell me how you get on16:34
mgz(and yes, this streams assembly stuff is all very error prone... does juju-metadata validate-tools help at all?16:35
mgz)16:35
gnuoymgz http://paste.ubuntu.com/9285206/16:46
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
mgzgnuoy: how goes?17:30
gnuoymgz, do you see my pastebin?17:31
gnuoy http://paste.ubuntu.com/9285206/17:31
=== kadams54 is now known as kadams54-away
mgzgnuoy: looking now17:48
mgzgnuoy: can you kill that machine, do set-env with the debug log config (we should have supplied on bootstrap really..) and look at machine-0.log17:50
gnuoymgz debug was set in the environments.yaml17:51
mgzokay, ace, then just look at machine-0.log for the provisioner bit that says "no matching tools available"17:52
gnuoymgz I've popped the log on chinstrap17:54
mgzyou're liam on chinstrap? not gnuoy?17:56
mgz2014-11-28 16:45:46 DEBUG juju.environs.simplestreams simplestreams.go:428 read metadata index at "https://streams.canonical.com/juju/tools/streams/v1/index2.json"17:58
mgz2014-11-28 16:45:46 DEBUG juju.environs.simplestreams simplestreams.go:436 index file has no data for product name(s) ["com.ubuntu.juju:win2012hvr2:amd64" "com.ubuntu.juju:win2012hvr2:i386" "com.ubuntu.juju:win2012hvr2:armhf" "com.ubuntu.juju:win2012hvr2:arm64" "com.ubuntu.juju:win2012hvr2:ppc64el"]17:58
mgzgraaaaa17:59
=== kadams54-away is now known as kadams54
themonklazyPower, hi19:43
themonki am getting a strange error after updating juju19:43
themonkfew hours back19:44
themonkthis is the error: WARNING discarding API open error: unable to connect to "wss://172......:17070/environment/4aaa9a83............/api" ERROR Unable to connect to environment "amazon". Please check your credentials or use 'juju bootstrap' to create a new environment.19:44
themonkcredentials are ok19:44
=== scuttle|afk is now known as scuttlemonkey
=== kadams54 is now known as kadams54-away
=== roadmr is now known as roadmr_afk
=== roadmr_afk is now known as roadmr
lkraiderhello, we are looking into extending juju to notify charm relations when their machines restart (right now only config-changed is called when the machine boots). Any pointers?22:23
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
lkraiderwe want to call relation-changed when a machine reboots22:39
lkraideris this possible?22:39
sarnoldlkraider: i'm just a spectator, but that feels like it'd introduce a huge amount of overhead when machines reboot... running scripts to take that unit out of service in all N relations that know about it might take longer than the machine rebooting will take..22:40
sarnoldlkraider: I suspect providing a unit-reboot hook would let charms that care about it handle it and let other charms ignore it without the overhead..22:41
lkraider@sarnold I mainly want to update the old relations with new IP when the machine reboots22:43
sarnoldlkraider: aha :)22:44
lkraidersarnold: am I right in that there's no provision in Juju right now for that?22:46
lkraidersarnold: this is my understanding of the hooks as they are now: http://stackoverflow.com/a/25980368/32473122:47
sarnoldlkraider: sorry, I'm too much of a bystander for that -- I wouldn't be surprised if semi-stable IPs are assumed though, and teardown / re-provision in the case of new unit IP addresses..22:47
sarnoldlkraider: nice graph :)22:48
lkraidersarnold: yep, I found the docs confusing so I made it from what I gathered22:51
lkraidersarnold: not sure if its 100% accurate tho22:51
lkraidersarnold: thanks for your help, I'll try asking sometime later to the folks here again22:54
sarnoldlkraider: good luck :)22:54
=== kadams54 is now known as kadams54-away
=== kadams54 is now known as kadams54-away

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!