/srv/irclogs.ubuntu.com/2015/08/10/#juju-gui.txt

bogdanteleagahello everybody11:38
bogdanteleagacan somebody help me with adding win2012r2 to this dropbox menu and making it work? http://postimg.org/image/to2m0mtpn/11:38
bogdanteleagaI've tried downloading the charm-zip, untarring the archive in releases/ and modifying https://github.com/juju/juju-gui/blob/develop/app/store/env/go.js#L15811:38
bogdanteleagahowever I'm not sure whether: a) that's the correct place to update, b) that archiving it back and deploying it would actually create that change without going through some make steps11:40
frankbanhi bogdanteleaga 12:26
frankbanlooking12:26
frankbanbogdanteleaga: I confirm that's the place to be updated to add more choices to the series drop down when uploading a local charm archive12:33
bogdanteleagafrankban: so what other steps should I do to get it up?12:34
bogdanteleagafrankban: as I said, I tried modifying that repackaging the archive and deploying the local charm12:34
frankbanbogdanteleaga: do you need that now or can you wait a couple of days for a new gui release (including the charm)?12:35
frankbanbogdanteleaga: or do you just need a temporary hack to get those choices in your environment?12:35
bogdanteleagafrankban: we've got a demo at the end of the week, I'd like to at least try it out if it's not that complicated12:36
frankbanbogdanteleaga: in this demo, do you demonstrate the GUI deployment or do you just need an initial environment with the GUI already there and the choices for new series?12:36
bogdanteleagafrankban: we'd like to demonstrate the steps for the gui deployment, it is windows after all :P12:38
bogdanteleagafrankban: I could just deploy from the CLI and show the gui result12:38
bogdanteleagafrankban: oh, I misunderstood, sorry12:38
bogdanteleagafrankban: the second one12:38
frankbanbogdanteleaga: so you can hack in the GUI unit before starting the demo, correct?12:39
bogdanteleagafrankban: yup12:39
frankbancool, so I have an idea bogdanteleaga, I am setting up a local env with quickstart right now, so that I can try while I expose it to you12:40
bogdanteleagafrankban: cool, thanks12:41
frankbanbogdanteleaga: before we start, I'll try to get someone to update that list and I hope to be able to do a GUI release this week, so it's possible that at the end of the week you'll have a GUI with the new series out of the box12:41
bogdanteleagafrankban: that'd be awesome as well12:42
frankbanbogdanteleaga: but if this does not happen, let's try to hack the new series in12:42
bogdanteleagafrankban: https://github.com/juju/juju/blob/master/version/supportedseries.go#L7712:42
frankbanbogdanteleaga: cool thanks12:42
bogdanteleagafrankban: you should toss centos7 in there :)12:42
bogdanteleagafrankban: arch is CLI only at this point12:43
frankbanbogdanteleaga: so, assuming you have an environment with the juju-gui in it12:44
bogdanteleagawe might need only win2012r2 and win2012hvr2 I'll get back to you with that one12:44
bogdanteleagayes12:44
frankbanbogdanteleaga: fir step is to "juju set juju-gui juju-gui-debug=true" so that the GUI is served via its non-minified version12:44
frankbanbogdanteleaga: then we can proceed and change the file you already found in the GUI unit: "juju ssh juju-gui/0 sudo nano /var/lib/juju-gui/juju-gui/build-debug/juju-ui/store/env/go.js"12:48
frankban(replace nano with a textual editor of your choice)12:49
frankbanbogdanteleaga: then refresh the GUI page very well in your browser (shift+ctrl+r usually works) and the new series should be available when dragging and dropping a zip archive12:49
frankbanbogdanteleaga: I'll ping you when we have a new GUI release including this fix12:53
bogdanteleagahmm12:54
bogdanteleagafrankban: it seems it was already there when I tried editing the file12:54
bogdanteleagafrankban: and now it's in the browser as well12:54
bogdanteleagafrankban: I could swear it wasn't there after I deployed it12:55
frankbanbogdanteleaga: is this your customized local charm?12:55
bogdanteleagafrankban: yeah the one where I unpacked, modified and repacked12:55
bogdanteleagafrankban: could it be the debug flag that did it or am I just tired? :)12:55
frankbanbogdanteleaga: it can be, anyway, my instructions work from scratch, without the need to deploy a local charm12:56
bogdanteleagafrankban: yup, that's true12:56
frankbanbogdanteleaga: you are basically editing the files served by the GUI server running in the unit12:56
bogdanteleagafrankban: thanks a lot :)12:57
bogdanteleagafrankban: I'll get back to you later with the series that should get in12:57
frankbanbogdanteleaga: that's ugly but hopefully you won;t need it by the eow12:57
bogdanteleagafrankban: I have a feeling we only want the CLI on win8, 8.1 and 712:57
frankbanbogdanteleaga: I am planning about adding all the series listed in juju-core, except for centos and arch, is that ok?12:57
frankbanbogdanteleaga: so basically series: [12:58
frankban      'precise', 'quantal', 'raring', 'saucy', 'trusty', 'utopic', 'vivid',12:58
frankban      'win2012hvr2', 'win2012hv', 'win2012r2', 'win2012', 'win7', 'win8',12:58
frankban      'win81'],12:58
alexpilottibogdanteleaga: dont forget Win1012:59
alexpilottiand win201612:59
bogdanteleagaalexpilotti, frankban: yes, we should get those in core soon12:59
alexpilottiwin10 now, as it’s publicly awailable12:59
bogdanteleagaalexpilotti: but only the server versions are for charms right?12:59
alexpilottinot really, VDI woks on client too13:00
alexpilottiAD, SQL Server, SP, etc only server of course13:00
frankbanbogdanteleaga: for now, I'd keep wily and win10 out of the GUI if they are not in core yet13:00
bogdanteleagaalexpilotti: hmm, we should have some guards then somewhere to prevent faulty deployment13:00
frankbanbogdanteleaga: is your demo ok with the list above?13:00
bogdanteleagafrankban: yes13:00
alexpilottibut win2016 and win2016hv are out now in TP213:00
frankbancool13:00
alexpilottiso we should get them in now already IMO13:01
urulamaalexpilotti: you guys have charms for win2016* already? we can include those series in new charmstore release this week if needed13:01
bogdanteleagaalexpilotti: we need to get them in core before gui I think13:01
bogdanteleagaurulama: there shouldn't be anything preventing the current ones from working13:02
alexpilottiurulama: yep, we run tests on them, especially hyper-v13:02
urulamabogdanteleaga: just asking if we need to add the win2016* and win10 to "unblock" you13:02
urulamaalexpilotti, bogdanteleaga: so, just to verify: new series are win10, win2016 and win2016hv?13:03
alexpilottithere’s also: win2016nano13:04
urulamaalexpilotti: what's that? :) the IoT thingy?13:04
alexpilottithat’s the NanoServer, Windows Server on a 300-400MB image13:04
urulamahah, ok13:04
alexpilottiwe tested the Juju agent quite some time ago, but we need to run more tests13:04
alexpilotticonsider that this stuff is getting rolled out publicly via technical previews (we have TP2 in April)13:05
alexpilottiand will get a final release next year13:05
lazyPowerfrankban: rick_h_: That JujuGui stacktrace is back again about websocket closed - http://paste.ubuntu.com/12048618/15:09
lazyPoweri'm getting this consistently in CI across 2 substrates, GCE and AWS15:09
frankbanlazyPower: on call, I'll look, at first sight this is something I cannot dupe on ec2. juju quickstart and juju versions?15:11
lazyPowerfrankban: pulling more details now, 1 sec15:12
lazyPowerfrankban: juju-1.24.3, juju-quickstart 2.2.015:17
frankbanlazyPower: is the error intermittent?15:21
lazyPoweri've triggered it twice, running a third time to capture the output15:21
frankbanlazyPower: dpkg -l python-websocket ?15:22
lazyPowerii  python-websocket     0.18.0-0ubuntu0 all             WebSocket client library for python15:22
frankbanlazyPower: I have 0.18.0-2 which should be basically the same15:23
frankbanso for some reason juju-core closes the ws connection15:24
frankbanlazyPower: what's the output if you pass --debug to quickstart?15:24
lazyPowerhttp://drone.dasroot.net/github.com/chuckbutler/kubernetes-juju-builder/master/c6b3dbd3e0a8f2e792bbd926eb4d4fb981398b9415:25
lazyPowernot sure, but if you want to follow along at home - threaten it with developer debugging goggles, maybe it'll behave and stop stacktracing at me15:25
lazyPowerits going to hand off to quickstart momentarily15:27
lazyPowerif you opened your browser, it appears to have been the magic sauce to get it to behave15:30
lazyPowerit just bootstrapped and completed without stacktracing me :-|15:30
lazyPowersilly intermittant issues15:30
frankbanlazyPower: yeah, no errors now15:32
lazyPoweri'm calling schenanigans on juju15:33
frankbanlazyPower: if you can add --debug to your script then maybe the next time we have more info. looking at that tracebakc, it could be anything from juju-core oddities to python-websocket issues to network disconnections15:34
lazyPoweri think 1.24 had this issue in an earlier revision15:34
lazyPowerit might have been a cached image problem running an older juju15:34
frankbanlazyPower: that sounds like a great explanation ;-)15:34
lazyPowerweird that i pulled the updated image and it still tanked, but again, its probably a caching problem15:35
lazyPower90% of my issues are due to something being old hanging around w/ my aggressive caching strategy15:35
=== arosales_ is now known as arosales

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