[11:38] hello everybody [11:38] can somebody help me with adding win2012r2 to this dropbox menu and making it work? http://postimg.org/image/to2m0mtpn/ [11:38] I'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#L158 [11:40] however 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 steps [12:26] hi bogdanteleaga [12:26] looking [12:33] bogdanteleaga: I confirm that's the place to be updated to add more choices to the series drop down when uploading a local charm archive [12:34] frankban: so what other steps should I do to get it up? [12:34] frankban: as I said, I tried modifying that repackaging the archive and deploying the local charm [12:35] bogdanteleaga: do you need that now or can you wait a couple of days for a new gui release (including the charm)? [12:35] bogdanteleaga: or do you just need a temporary hack to get those choices in your environment? [12:36] frankban: 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 complicated [12:36] bogdanteleaga: 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:38] frankban: we'd like to demonstrate the steps for the gui deployment, it is windows after all :P [12:38] frankban: I could just deploy from the CLI and show the gui result [12:38] frankban: oh, I misunderstood, sorry [12:38] frankban: the second one [12:39] bogdanteleaga: so you can hack in the GUI unit before starting the demo, correct? [12:39] frankban: yup [12:40] cool, 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 you [12:41] frankban: cool, thanks [12:41] bogdanteleaga: 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 box [12:42] frankban: that'd be awesome as well [12:42] bogdanteleaga: but if this does not happen, let's try to hack the new series in [12:42] frankban: https://github.com/juju/juju/blob/master/version/supportedseries.go#L77 [12:42] bogdanteleaga: cool thanks [12:42] frankban: you should toss centos7 in there :) [12:43] frankban: arch is CLI only at this point [12:44] bogdanteleaga: so, assuming you have an environment with the juju-gui in it [12:44] we might need only win2012r2 and win2012hvr2 I'll get back to you with that one [12:44] yes [12:44] bogdanteleaga: fir step is to "juju set juju-gui juju-gui-debug=true" so that the GUI is served via its non-minified version [12:48] bogdanteleaga: 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:49] (replace nano with a textual editor of your choice) [12:49] bogdanteleaga: 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 archive [12:53] bogdanteleaga: I'll ping you when we have a new GUI release including this fix [12:54] hmm [12:54] frankban: it seems it was already there when I tried editing the file [12:54] frankban: and now it's in the browser as well [12:55] frankban: I could swear it wasn't there after I deployed it [12:55] bogdanteleaga: is this your customized local charm? [12:55] frankban: yeah the one where I unpacked, modified and repacked [12:55] frankban: could it be the debug flag that did it or am I just tired? :) [12:56] bogdanteleaga: it can be, anyway, my instructions work from scratch, without the need to deploy a local charm [12:56] frankban: yup, that's true [12:56] bogdanteleaga: you are basically editing the files served by the GUI server running in the unit [12:57] frankban: thanks a lot :) [12:57] frankban: I'll get back to you later with the series that should get in [12:57] bogdanteleaga: that's ugly but hopefully you won;t need it by the eow [12:57] frankban: I have a feeling we only want the CLI on win8, 8.1 and 7 [12:57] bogdanteleaga: I am planning about adding all the series listed in juju-core, except for centos and arch, is that ok? [12:58] bogdanteleaga: so basically series: [ [12:58] 'precise', 'quantal', 'raring', 'saucy', 'trusty', 'utopic', 'vivid', [12:58] 'win2012hvr2', 'win2012hv', 'win2012r2', 'win2012', 'win7', 'win8', [12:58] 'win81'], [12:59] bogdanteleaga: dont forget Win10 [12:59] and win2016 [12:59] alexpilotti, frankban: yes, we should get those in core soon [12:59] win10 now, as it’s publicly awailable [12:59] alexpilotti: but only the server versions are for charms right? [13:00] not really, VDI woks on client too [13:00] AD, SQL Server, SP, etc only server of course [13:00] bogdanteleaga: for now, I'd keep wily and win10 out of the GUI if they are not in core yet [13:00] alexpilotti: hmm, we should have some guards then somewhere to prevent faulty deployment [13:00] bogdanteleaga: is your demo ok with the list above? [13:00] frankban: yes [13:00] but win2016 and win2016hv are out now in TP2 [13:00] cool [13:01] so we should get them in now already IMO [13:01] alexpilotti: you guys have charms for win2016* already? we can include those series in new charmstore release this week if needed [13:01] alexpilotti: we need to get them in core before gui I think [13:02] urulama: there shouldn't be anything preventing the current ones from working [13:02] urulama: yep, we run tests on them, especially hyper-v [13:02] bogdanteleaga: just asking if we need to add the win2016* and win10 to "unblock" you [13:03] alexpilotti, bogdanteleaga: so, just to verify: new series are win10, win2016 and win2016hv? [13:04] there’s also: win2016nano [13:04] alexpilotti: what's that? :) the IoT thingy? [13:04] that’s the NanoServer, Windows Server on a 300-400MB image [13:04] hah, ok [13:04] we tested the Juju agent quite some time ago, but we need to run more tests [13:05] consider that this stuff is getting rolled out publicly via technical previews (we have TP2 in April) [13:05] and will get a final release next year [15:09] frankban: rick_h_: That JujuGui stacktrace is back again about websocket closed - http://paste.ubuntu.com/12048618/ [15:09] i'm getting this consistently in CI across 2 substrates, GCE and AWS [15:11] lazyPower: on call, I'll look, at first sight this is something I cannot dupe on ec2. juju quickstart and juju versions? [15:12] frankban: pulling more details now, 1 sec [15:17] frankban: juju-1.24.3, juju-quickstart 2.2.0 [15:21] lazyPower: is the error intermittent? [15:21] i've triggered it twice, running a third time to capture the output [15:22] lazyPower: dpkg -l python-websocket ? [15:22] ii python-websocket 0.18.0-0ubuntu0 all WebSocket client library for python [15:23] lazyPower: I have 0.18.0-2 which should be basically the same [15:24] so for some reason juju-core closes the ws connection [15:24] lazyPower: what's the output if you pass --debug to quickstart? [15:25] http://drone.dasroot.net/github.com/chuckbutler/kubernetes-juju-builder/master/c6b3dbd3e0a8f2e792bbd926eb4d4fb981398b94 [15:25] not sure, but if you want to follow along at home - threaten it with developer debugging goggles, maybe it'll behave and stop stacktracing at me [15:27] its going to hand off to quickstart momentarily [15:30] if you opened your browser, it appears to have been the magic sauce to get it to behave [15:30] it just bootstrapped and completed without stacktracing me :-| [15:30] silly intermittant issues [15:32] lazyPower: yeah, no errors now [15:33] i'm calling schenanigans on juju [15:34] lazyPower: 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 disconnections [15:34] i think 1.24 had this issue in an earlier revision [15:34] it might have been a cached image problem running an older juju [15:34] lazyPower: that sounds like a great explanation ;-) [15:35] weird that i pulled the updated image and it still tanked, but again, its probably a caching problem [15:35] 90% of my issues are due to something being old hanging around w/ my aggressive caching strategy === arosales_ is now known as arosales