/srv/irclogs.ubuntu.com/2014/10/01/#juju-gui.txt

hatchhey huwshimi00:19
huwshimiHey00:20
huwshimihatch: How's things?00:21
hatchgoing good - just trying to get everything done before next week00:21
hatchseems these things always happen a week too early haha00:22
huwshimi:)00:22
=== uru_ is now known as urulama
=== urulama is now known as urulama-afk
=== urulama-afk is now known as urulama
rick_h_morning party people11:01
rick_h_frankban: how goes this morning?11:05
frankbanrick_h_: I was going to send you an email11:06
frankbanrick_h_: I was able to give internet access to nodes, by doing the following:11:06
frankban- add a default 10.0.0.1 gateway to the MAAS network;11:06
frankban- fix the POSTROUTING netfilter rule in the host, i.e.11:06
frankban  iptables -t nat -A POSTROUTING -s 10.0.0.0/24 -j MASQUERADE11:06
rick_h_cool, yea that's what I was just looking at in some google searches11:07
frankbanrick_h_: Next error was related to juju tools: "cannot execute binary file: Exec format error”.11:07
frankbanSee https://bugs.launchpad.net/juju-core/+bug/132596811:07
frankbanso the fix seems t be --constraints arch=i38611:07
rick_h_ugh11:08
frankbanrick_h_: with that constraint, juju finally bootstrapped!11:08
rick_h_yay!11:08
frankbanrick_h_: so now I am testing quickstart with and without the constraints flag11:08
rick_h_frankban: <3 ok very cool. Glad you're unblocked enough. Thanks for helping throgh all this fun stuff11:09
rick_h_frankban: let's make sure we add notes to that maas doc so that we can make sure this works out as the hope is we'll have a maas lab going forward11:09
frankbanrick_h_: yeah it was ages since my last iptables command ;-)11:09
rick_h_no kidding, I got that far last night and took that as a sign I was done :)11:10
rick_h_iptables and multiple glasses of wine never mix lol11:10
frankban:-)11:10
frankbanrick_h_:  now running ".venv/bin/python juju-quickstart --constraints arch=i386" fingers crossed11:11
rick_h_frankban: cool, maybe did I install i386 ubuntu on the maas controller?11:12
frankbanrick_h_: unrelated, but ssh always disconnects me after a few minutes with a broken pipe11:12
frankbanrick_h_: the kernel is 64 bit11:12
rick_h_frankban: yea, I wonder if I've got a network thing going on. It kept doing that to me ssh'ing out on my laptop last night11:12
rick_h_frankban: but my desktop stayed connected the whole time, so it's strange11:12
frankbanrick_h_: the nodes are i386, and that's where tools are used11:13
rick_h_frankban: ic, but the nodes can be anything right? We can set them as amd64 in maas and it should install the right images from it's list of images?11:13
frankbanrick_h_: in theory yes, in theory...11:13
rick_h_lol11:13
rick_h_frankban: ok, so you ssh'd in and verified they were running i386 images?11:14
* rick_h_ is trying to phrase a reply to the bug and if we can dupe it we should work with juju core on it11:14
frankbanrick_h_: no I have not but in the edit node page i see "i386/generic" arch11:14
rick_h_frankban: oh? oooh, ok. 11:15
rick_h_I was looking at nuc2 which is amd6411:15
rick_h_so maybe it's my failing to setup maas correctly11:16
rick_h_frankban: when you're test is done let me know and we'll edit the node and try to recomission it11:16
frankbanrick_h_: ok11:16
rick_h_and see if we can get updated software on it11:16
rick_h_and then make it work sans constraint :)11:16
frankbanrick_h_: woot, all's good for now: http://pastebin.ubuntu.com/8472118/11:17
rick_h_yay!11:17
rick_h_so now the other thing to document is sshuttle into the 10.0 network on there so you can get at the gui11:18
frankbanrick_h_: quickstart has not finished yet11:18
* rick_h_ really doesn't want to redo this setup but wonders if trying to put all the nodes on the public network would be best11:18
frankbanrick_h_: so, GUI deployed, but then quickstart exited with an error: juju-quickstart: error: unable to connect to the Juju API server on wss://nuc1.maas:443/ws: [Errno -2] Name or service not known11:19
frankbanso, dns is not working11:20
rick_h_hmm, yea11:20
rick_h_so maas is setup and supposed to manage dns, but I bet it's because I set the dns on the hosts to google or something vs itself11:21
* rick_h_ looks up format of dig commands11:22
rick_h_dig nuc1.maas @10.0.0.111:23
rick_h_works so cool11:23
rick_h_frankban: ok, updated resolv.conf and the nameserver for the 10.x interface and just a normal cli "dig nuc1.maas" returns now11:24
frankbanrick_h_: cool, so, I'll re-run quickstart on the bootstrapped environment and this time it should be able to connect to the gui server11:26
rick_h_frankban: rgr11:27
frankbanrick_h_: done, quickstart completed successfully: http://pastebin.ubuntu.com/8472146/11:27
frankban\o/11:27
rick_h_woooooooo!11:27
rick_h_it's early...but a happy dance it is11:27
frankbanrick_h_: destroying the environment11:28
rick_h_hold on if you can11:28
frankbanops11:28
rick_h_ok, np11:28
frankbanrick_h_: another thing I noted, when destroying an environment the node is left to Releasing failed status, and you need a manual "release" fot it to be back in ready state11:28
rick_h_frankban: yea11:29
frankbanrick_h_: but I guess it's not our problem11:29
rick_h_frankban: ok so sshuttle -v -D -r ubuntu@maas.jujugui.org 10.0.0.0/2411:29
rick_h_let's me load up maas on http://10.0.0.1/MAAS11:29
frankbanrick_h_: cool, should wer try to switch nuc1 to amd64?11:29
rick_h_frankban: so the hope is that line will let us load up the gui and environment stuff once it's brought up11:30
rick_h_frankban: yea, let's do that11:30
rick_h_frankban: ok switched and comissioning11:30
frankbanrick_h_: cool thanks11:30
* rick_h_ wishes he had all the kvm stuff setup to watch it and make sure it's going...doesn't trust maas enough yet11:31
rick_h_frankban: yea, on the release node stuff, it's new and we've got some issues from the experimental branch11:31
rick_h_frankban: you'll be happy to know our big problem before was lack of the amt control tools package installed11:31
rick_h_frankban: the new software shows the error while before I assumed maas handled that bit11:31
frankbanrick_h_: yay for experimental maas11:32
rick_h_definitely, so maas was never powering on/off our machines as hoped11:32
frankbanic11:32
frankbanrick_h_: one confusing bit is that nuc1 pretends to have 10.0.0.151 addr, but when it starts it's on 10.0.0.10011:33
rick_h_frankban: yea, I'm not sure what's up with that to be honest. 11:34
frankbanrick_h_: ok the node is ready11:35
frankbanrick_h_: running quickstart without constraints11:35
rick_h_frankban: rgr11:35
frankbanrick_h_: at least we now my branch with maas support works and generates a reasonable configuration11:36
rick_h_frankban: :)11:38
rick_h_frankban: yea, I had hoped it would be very little different other than generating the proper environments.yaml11:39
frankbanrick_h_: yeah, it's basically just it11:39
rick_h_and then 3 days of getting maas and juju happy lol11:39
rick_h_across timezones 11:39
frankbanlol11:39
rick_h_hmm, it's green and says deployed?11:40
frankbanrick_h_: yeah, qucikstart still bootstrapping11:40
rick_h_cool11:40
frankbanrick_h_: and now it's deploying11:41
frankbanrick_h_: so bootstrap succeeded without constraints11:41
rick_h_woot11:41
rick_h_lol, every change one step closer...and closer...and closer11:41
frankbanwaiting for the new shiny cs:trusty/juju-gui-9 unit to be deployed11:41
frankbanrick_h_: done! quickstart is ready11:42
rick_h_sweet, so with the shuttle command can you load the gui in your local browser now?11:42
frankbantrying11:42
rick_h_it works here https://10.0.0.100/login/11:45
frankbanrick_h_: it works!11:45
rick_h_woot!11:45
rick_h_jujugui we have a maas ! rock on frankban 11:45
frankbanrick_h_: password is 109b105fe8b699f4b0a255556350233111:45
rick_h_hah, /me wants to deploy something!11:46
frankbanrick_h_: machine view shows 0-state service 4xGHz, 8.0GB,11:46
frankban\o/11:46
rick_h_nice!11:46
frankbanwe might want to strip the final comma there ;-)11:46
rick_h_and with machine view we can container on that thing and deploy crazy stuff11:46
rick_h_lol11:46
urulamarick_h_, frankban: did anyone tried juju-gui on manual? i can play with that tonight before going to bed as I wanted to test using mongo shards and multi CS units11:47
frankbanrick_h_: ghost charm on the bootstrap node?11:47
rick_h_frankban: yea, should work11:47
rick_h_urulama: 'juju-gui on manual'?11:48
frankbanrick_h_: in a container?11:48
urulamarick_h_: manual environment11:48
rick_h_urulama: oh hmm, not sure. 11:48
rick_h_frankban: yea, lxc it up11:48
urulamarick_h_: ok, i'll let you know11:48
rick_h_frankban: my understanding is that the lxc container will get a root 10.0.0.xx ip from dhcp11:48
rick_h_frankban: and be able to be exposed at the root network level11:48
rick_h_urulama: I think with machine view now you could bring up the machines, add them, and they'd show up in machine view11:49
rick_h_urulama: and then you could deploy to them directly11:49
rick_h_urulama: but you'd have to add them and such via cli/manual stuff first? 11:49
rick_h_ok, bringing up elasticsearch on nuc2 hopefully11:50
frankbanrick_h_: nuc2 is pending, 0/lxc/0 is pending. man, this GUI thing seems to work just fine11:52
rick_h_frankban: <311:52
rick_h_frankban: sometimes, we do damn good work :)11:52
urulamarick_h_: yes, adding will have to be done by add-machine unless there is code in GUI that makes this "add-machine" call. 11:52
rick_h_urulama: right, it makes an add-machine call but I think in manual you have to provide extra info to that call as to where the machine to add is located11:53
rick_h_urulama: and the gui doesn't do that11:53
frankbanrick_h_: http://10.0.0.155:2368/ \o/11:53
urulamarick_h_: ok.11:53
rick_h_frankban: woot, ghost looks green and exposed11:53
rick_h_haha! 11:53
* rick_h_ does another round of happy dance and notices son is up...time to prepare for day bare biab11:54
rick_h_frankban: you rock thanks again for the pita work on this!11:54
* rick_h_ goes afk for a little bit11:54
frankbanand it's not "Just a blogging platform.". it's more "just a blogging platform deployed via a GUI which manages juju on top of a maas controller"11:54
urulamarick_h_, frankban: did you try deploying openstack? :P11:54
frankbanurulama: I don't even know where to start to do that. but for our scope, ghost is as good as openstack ;-)11:56
* frankban lunches11:59
urulamafrankban: https://jujucharms.com/bundle/~james-page/openstack-on-openstack/25/openstack/?text=openstack12:00
rick_h_frankban: urulama http://marcoceppi.com/2014/06/deploying-openstack-with-just-two-machines/ :P12:06
urulamarick_h_: even better :)12:06
rick_h_frankban: urulama so I think I'll end up getting a 3rd nuc so we can easily test out bundles on two empty nodes and maybe then we can get openstack on them :P12:06
rick_h_oh boo, elasticsearch failed12:07
rick_h_oh, it can't reach out to the internet12:08
rick_h_no, it did reach out ok. It just got a forbidden for some reason ok12:09
frankbanguihelp: is anyone available for taking a look at https://codereview.appspot.com/151200043 (quickstart/python)? thanks!13:49
frankbanrick_h_: thanks for the nice email13:50
rick_h_frankban: <313:51
bacfrankban: i can look13:53
frankbanbac: thanks13:53
bacah, i've missed rietveld.13:54
hatchlike honestly?13:54
baccompared to reviews on github, yeah.14:00
frankban+114:00
hatchthe only difference I can see is that you can queue up review comments14:00
hatchbut you can also do that on github wtihout clicking 'submit'14:01
bachatch: so you keep each comment in limbo and then submit them all at once?14:01
hatchno because queuing up the comments doesn't really bother me :) 14:02
hatchbut it is possible14:02
bachatch: i also don't like how it collapses and hides your comments when a new revision is pushed.  i find it very hard to follow the review and determine if everything has been addressed.14:02
frankbanhatch: there are other little things that I miss. For instance, better handling of long lines (when reviewing go code it is useful), ability to comment unchanged code and above all, a way to review patches and follow the review discussion that doesn't drive me crazy14:02
hatchreitveld frequently 'forgets' comments when saving so it's really a catch 2214:03
bacno, it is a toss up.  it is definitely not a catch 22.  :)14:03
hatchlol right14:03
hatchmaybe if reitveld wasn't so ugly I'd like it more14:04
hatchgota get some designers up in that house14:04
* rick_h_ changes location back to the house. afk14:05
bacsee, when doing the review i made a comment about some user-facing text but when i did the QA i saw my comment was bogus.  deleted it.  approved the review. no noise from premature comment sent out.14:08
bacfrankban: +114:08
hatchlol14:08
hatchhey luca__14:08
luca__hi hatch 14:09
frankbanbac: thanks14:09
bacfrankban: amazing that it was so simple!14:09
bacrick_h_: you need to add a photo of your MAAS to that document14:12
hatchluca__: sent an email to ya regarding the commit summary14:16
bacrick_h_: i tried to ssh to the maas but cannot connect.  did you do an ssh-import-id for all of us?14:16
luca__hatch: I haven’t seen any email...14:18
luca__hatch: I just got an email14:18
hatch:)14:19
luca__hatch: I didn’t know this feature was coming!14:24
hatchyeah we like to keep you on your toes :P14:24
luca__hatch: haha14:25
hatchI'm going to land this as is but would be nice to tweak it a bit for the next release14:25
luca__hatch: maybe we should schedule a call so you can talk me through it, it seems pretty straight forward.14:25
luca__hatch: do we have to land it?14:25
hatchwell if I don't the code could go stale 14:26
luca__ok14:26
hatchI'm pretty much free whenever14:26
luca__ok14:26
hatchwith the exception of the standup in 4514:26
hatcher 3014:26
kadams54guihelp: am I correct in thinking that a revived model (from a LazyModelList) should fire change events automatically?14:27
hatchkadams54: yes14:27
kadams54hatch: *sigh*14:27
hatchlol why?14:27
hatchthat sounds like a good thing14:27
hatchand pretty much the only reason to revive :P14:27
kadams54hatch: it would be a good thing… if that's what I actually saw happening.14:28
kadams54hatch: http://pastie.org/private/kndmzbqg3syfm9zgeh21pg14:28
hatchlooking14:28
kadams54That's the change I made. But now my onChange handler function isn't being called at all.14:28
hatchand you're sure the revive is being called?14:29
kadams54Yeah, got a breakpoint on it14:29
hatchand what's the event handler?14:29
hatchjust the registration part14:30
kadams54I'll double-check though. I'm also wondering if something is breaking in event propagation.14:30
hatchI'm guessing that there is something wrong with your event registration14:30
frankbanbac: I can add your keys, what pait are you using? I see four in your lp page14:30
frankbanpair even14:31
kadams54this.addEvent(db.machines.after('*:change', this._onMachineChange, this));14:31
kadams54hatch: ^14:31
bacfrankban: just run 'ssh-import-id bac', if it hasn't been done14:31
frankbanbac: cool14:31
hatchkadams54: yeah that won't work14:31
bacfrankban: i should probably prune what i've got on LP14:31
frankbanbac: done14:32
bacfrankban: and i'm in.  thanks.14:32
hatchkadams54: lazy model list doesn't have a change event for attribute changes14:32
hatchkadams54: and unfortunately reviving doesn't add the lml as a bubble target14:33
kadams54The previous approach, of manually firing the change event, was buggy because the event object wasn't populated with the same info that a change would have in a ModelList.14:34
hatchahh14:34
hatchwell you can fire a custom event facade 14:34
hatchthe second param of fire() 14:34
hatchnbd just another YUI bug that'll never get fixed now ;)14:35
rick_h_bac: woot welcome to maas :)14:36
kadams54hatch: yeah, I know I can fire a custom event facade, but that means trying to populate it with the same info that YUI does for changes in a ModelList… and I'd like to avoid that.14:36
hatchwell you only have to populate it with the information that your handlers expect14:36
hatchwhich shouldn't be too much14:36
bacrick_h_: so you have some poor man's maas?  no orange box?14:37
rick_h_bac: yea, I've got a 'rick bought 3 nucs, a switch, and a internet plan with static ips' maas14:37
bacrick_h_: nuc-nuc-nuc14:37
rick_h_bac: so it took months to come up vs an orange box taking 10min14:37
kadams54hatch: the whole point of an event architecture is to decouple so that the code firing the event doesn't have to know about the code subscribed to the event.14:37
kadams54hatch: I mean, if that's what I have to do, I'll do it. I'm just hoping there's a better way.14:38
bacyou should name them larry, moe, and curly14:38
rick_h_bac: hah!14:38
hatchnot without patching lazymodellist14:38
rick_h_bac: .95 manual focus lens just arrived wheeee!14:38
hatchrick_h_: can't you just turn off auto focus to get a manual focus? ;)14:39
bacrick_h_: which one?14:39
rick_h_bac: voightlander 17.5mm for m4/314:40
bacthat'll be a real challenge to focus i would think14:40
rick_h_bac: so m4/3 focus peaking ftw14:40
rick_h_it'll take some practice for sure14:40
rick_h_but focus peaking should hopefully help14:40
rick_h_the hard part is I'm used to setting aperture priority and hitting go14:41
bacbeing that wide, you've got some leeway14:41
rick_h_so now it's more set aperture on the lens, focus with peaking, adjust shutter speed to get desired exposure manually14:41
rick_h_but .95 is wiiiide open14:41
bacwait, can't you leave it in AP and let the camera set shutter speed?14:42
rick_h_it doesn't know the aperture since it's done on lens14:42
rick_h_it has no contacts to talk to the camera14:42
rick_h_the camera thinks there's no lense there14:42
bacrick_h_: no, but it has a meter.14:42
bacrick_h_: no different from my rangefinder14:42
* rick_h_ will have to check it out and try14:43
baca step in the right luddite direction for sure14:43
rick_h_bac: ah cool. So the aperture shows 0.0, but it does adjust SS for me when I hit go14:43
bacrick_h_: but your exif data will be hosed!14:44
rick_h_yes, no exif data :/14:44
bacmine guesses based on having two out of three data points14:45
rick_h_gotcha14:45
bacit writes to a different exif field showing that it is not sure14:45
hatchI just use my cell phone14:48
frankbanrick_h_: are you available for a quick second review of https://codereview.appspot.com/151200043 ?14:48
hatch< --- professional14:48
rick_h_frankban: already looking14:49
frankbanthanks14:49
rick_h_frankban: done, thanks for the changes. The goal will be to work on the release and completing the FFE bugs in the package for utopic after this please.14:52
rick_h_bac: now that's shallow https://www.flickr.com/photos/7508761@N03/15411328085/ :)14:53
bacrick_h_: 40414:54
rick_h_doh, perms14:54
rick_h_reload14:54
frankbanrick_h_: cool thanks, I'll work on a 1.4.4 release after landing this14:55
rick_h_frankban: awesome. 14:55
hatchrick_h_: that's some seriously shallow dof14:55
hatchwhat;s that, 1"?14:56
rick_h_hatch: 5 or 614:56
MakyoOooh.  Jealous.14:57
rick_h_jujugui call in 414:58
rick_h_kanban it up please14:58
bacso is my mic not working?15:12
rick_h_bac: yea, mic fail15:18
rick_h_camera fail15:18
bacrogpeppe: under "Mailing List" do you have an Unsubscribe button?15:18
rogpeppebac: yup15:18
rick_h_rogpeppe: filter or spam catch it?15:18
bacrogpeppe: nm, https://launchpad.net/~juju-gui-peeps/+mailing-list-subscribers15:18
rogpepperick_h_: i'm looking in Spam15:18
bacyou are on it.15:18
rick_h_"gui maas now available...pretty much" is the exact title15:19
rogpepperick_h_: i don't think so. when did you send the mail?15:19
bacrick_h_: does everyone really have access?  frankban had to manually add me15:19
rick_h_bac: no, I need to go through and import ssh keys15:19
rick_h_bac: but you me and frankban can now add that in15:19
rogpepperick_h_: i'm guessing it might just be delayed15:19
bacrick_h_: okey doke15:19
rick_h_bac: I'll try to run through everyone's LP ids at lunch15:20
rick_h_rogpeppe: shared the doc with you and included the email contents in the share notice15:21
rogpepperick_h_: thanks15:21
rogpepperick_h_: when did you send the email? was it today?15:21
rogpepperick_h_: i've got that. i wonder what happened to the mailing list message.15:23
* rogpeppe is concerned that he may have missed lots more15:23
hatchMakyo: did you forget to mark this one as committed? https://bugs.launchpad.net/juju-gui/+bug/136526015:26
rick_h_rogpeppe: whoa, you're not on yellow in LP strange15:29
rogpepperick_h_: hmm. i am in ~juju-gui-peeps though.15:30
rick_h_rogpeppe: added you, should hopefully be all set, not sure on the peeps list but at least on the team wise15:30
rick_h_rogpeppe: yea15:30
rogpepperick_h_: no archives, i'm guessing15:30
rick_h_rogpeppe: no, nothing much that you'd be interested yet I don't think15:30
rogpepperick_h_: cool15:31
rick_h_rogpeppe: it's been very gui/machine view focused so far though it's starting to warm up with storefront stuff15:31
rick_h_it's handy as the UX team is also on that list, and a few core folks like ramm, kapil, etc15:31
rick_h_I'll try to remember to check next time I see something go across15:32
rick_h_jujugui ok added ssh keys for the LP users  fabricematrat evarlast jcsackett hatch kadams54 makyo uros-jovanovic martin-hilton rogpeppe to the maas server15:32
rick_h_jujugui so if you're not on the list or can't get in let me know15:33
rick_h_bac: thanks for the prod15:33
kadams54rick_h_: sweet… will check it out in a bit.15:33
hatchrick_h_: so what "can't" we deploy here? Does MAAS create vm's ? So it'll look to us like a bunch of machines? Or does it still only look like 2 machines?15:37
rick_h_hatch: it's two machines and you can lxc at will15:37
rick_h_so can install most anything you want but bundles of 5 machines can't work15:37
hatchahh so is that where openstack comes in? to create vm's?15:37
rick_h_hatch: yes, thought without juju can you bring up a node with bare ubuntu image15:39
hatchso MAAS is really the hardware layer then openstack is the vm layer then juju is the orchestration layer15:39
hatchwe got this stack!15:39
=== uru_ is now known as urulama
Makyohatch, sorry, bio break.  I'll mark it as committed.15:48
MakyoActually, should be released15:48
hatchahh yes15:49
jcsackettjujugui: i need two reviews and a pretty serious (requires real env) QA of https://github.com/juju/juju-gui/pull/60016:15
hatchjcsackett: I can get on it once I'm finished mine but I'm running into some testing oddities that are being less than awesome16:16
hatchwant to get this finished first16:16
rick_h_jujugui ok break time for lunch afk16:18
kadams54Also lunching.16:40
hatchrick_h_: luca brings up a good point in his email re the conflict blocking - should I bench this branch until we can come to an agreement on a real plan?16:44
rick_h_hatch: well, I think we should leave the notification for now. 16:53
rick_h_hatch: at least it's visible and non-blocking16:53
rick_h_hatch: and it's more info that we have today (no hidden config issues) 16:53
rick_h_hatch: and we can work out the blocking path16:53
hatchrick_h_: ok so remove the blocking of the commit?16:56
rick_h_hatch: that's my idea atm, how does that sound?16:56
hatchworks for me16:58
hatchI'll respond to the email with luca16:58
rick_h_hatch: k16:58
hatchjcsackett: lol nice typod bug17:05
hatchcontainser all the things!!!17:05
hatchour minimum wage just went up to $10.20/hr 17:07
hatchand there goes the cost of living by the same increase 17:07
hatchlol17:07
hatchjujugui does anyone know why the inspector breaks when the gui loses connection to its server? Anyone looked into this in their spare time? 17:15
hatchjujugui I need reviews and qa https://github.com/juju/juju-gui/pull/59917:45
hatchjcsackett: still need reviews and all that?17:45
=== uru_ is now known as urulama
jcsacketthatch: i do. looking to trade?17:51
hatchshitty trade but ok17:52
hatch:P 17:52
rick_h_bwuahahahha17:52
rick_h_jujugui I've put the two big bugs into the urgent lane for next steps. They're big enough I'd like to do another release once we get those in. 17:53
hatchcool17:55
hatchrick_h_: well there goes Ember from the list https://twitter.com/jdalton/status/51737099053249740917:57
hatch:)17:57
rick_h_hello17:59
rick_h_bah17:59
* rick_h_ test17:59
* rick_h_ never thought ember was on the list17:59
rick_h_hmm, why did that not go out 3 times in a row :/17:59
hatcheverything is on the list :) I'm being open minded!!!17:59
kadams54hatch: is there any way to set e.target when firing an event? I tried: list.fire('change', {foo: 'bar', target: model}) and the target that came through on the other side was still list (and not model).18:10
kadams54hatch: Right now I'm considering, as a hack, something like this: http://pastie.org/private/cp1wjtfuigw4bsdxfhhynw18:15
kadams54(with comments, of course)18:15
jcsackettrick_h_: just letting you know i was able to successfully get onto the maas stuff.18:32
hatchkadams54: looking18:33
hatchkadams54: so it won't let you set the target?18:34
kadams54hatch: doesn't seem to.18:34
hatchkadams54: http://yuilibrary.com/yui/docs/api/classes/EventTarget.html#method_fire18:35
hatchyeah looks like it will18:35
hatchsee the arguments definition18:35
kadams54Yeah, I know, which is why I though my first approach would work. But that's not the story told in the debugger.18:36
hatchwell no, the change event has a facade set18:37
hatchso it'll overwrite what you're trying to pass18:37
hatchkadams54: I think your approach in that pastie is acceptable with comments as per why it's there and where it's coming from18:38
hatchkadams54: there are other psudo appropriate ways to do it - setting a custom facade for the event...but no, that's even harder to reason about :)18:44
hatchjust fyi :)18:44
hatchjcsackett: your branch qa's well on sandbox - I'm going to take lunch then will qa the real env18:47
bic2kwhich is the preferred place to file bugs/feature requests: launchpad or github?19:10
rick_h_bic2k: launchpad19:14
rick_h_I think issues is disabled in github19:14
rick_h_jujugui running away for the day. jcsackett if you don't get a second review I'll try to look at it tonight after 19:17
urulamarick_h_: have fun19:17
rick_h_urulama: get out of here :P I can't EOD before you TZ law19:18
urulama:D19:18
* urulama goes *puf*19:18
hatchjcsackett: +120:37
jcsacketthatch: whoo! thanks.20:37
jcsackettso glad to be closing in on landing that mofo.20:37
jcsackettthat db.reset call and 'var db =' thing in the tests were total PITAs to track down.20:38
hatchyeah I bet20:38
hatchjcsackett: I can't reproduce #1376353 nor does the var in question exist20:42
hatchare you sure you didn't have some local branch with a typo?20:42
jcsacketthatch: you mean the one about not switching back to services that i filed?20:43
hatchyeah20:43
hatchhttps://bugs.launchpad.net/juju-gui/+bug/137635320:43
hatchlazyPower: ping20:43
lazyPowerpong20:43
hatchI'm looking at your bug here https://bugs.launchpad.net/juju-gui/+bug/137525120:44
hatchwhat do you mean by 'environment clone' ?20:44
lazyPoweri copied the same entry in environments.yaml (its a manual clone provider, read: DO)20:44
lazyPowerand deployed a "fresh environment" - with fresh vms and saw the same behavior20:44
hatchoh ok so you upgraded from 7 to 8 in the new env and it was the same issue?20:45
hatchand you say switching to machine view at any time clears the xy coords? This is very odd - I've never seen that before20:46
hatchI wonder if this is a DO specific issue20:46
jcsacketthatch: what do you mean the var in question doesn't exist?20:46
jrwrenjcsackett: was it you that fixed the mysterious jenkins crashing spawned process bug?20:46
hatchjcsackett: this._containserHeader is undefined20:47
jcsackettjrwren: i think so? you mean the fact that the dev server wouldn't stay up?20:47
jcsacketthatch: right, that it's undefined is the problem.20:47
jrwrenjcsackett: yes. Was there anything other than BUILD_ID=dontkillme environment variable?20:48
jcsackettjrwren: nope, that's all it took.20:48
lazyPowerhatch: actually on the new env it was a straight deployment of 820:48
jrwrenjcsackett: thanks.20:48
jcsackettjrwren: yw.20:48
lazyPowerhatch: and yes, switching to machine view at any time clears x/y coords. :(20:49
lazyPowerhatch: i can run a sample deployment and hand over creds if you want to inspect20:49
hatchjcsackett: right but do you see the var name? It doesn't exist in the app20:49
hatchlazyPower: ok this must be a DO only issue because I know of a few others using the mv on ec2 without issue in a prod env20:49
hatchdid you use the DO plugin?20:49
hatchor just manually assign the machines?20:50
lazyPoweri use the DO plugin20:50
jcsacketthatch: i don't know what you mean. the line exists in the code, and is coming up undefined. 20:50
jcsacketthatch: i do indeed see this._containersHeader20:50
hatchjcsackett: oh so the bug has a typo?20:51
hatchlazyPower: ok I'll install the plugin and such and give it a try20:51
hatchalthough I'm guessing the issue is DO specific 20:52
jcsacketthatch: yup, bug has a typo, i've updated.20:52
hatchok so just tried on develop and alls well20:52
hatchin fact I qa'd your branch with it and no issues20:52
jcsacketthatch: there is indeed no containers header in my personal env.20:58
hatchso possible that yours is broken?20:58
jcsacketthatch: how?20:58
hatchwell I just had a fresh env on ec2 running on develop and it worked as expected20:59
hatchI can try again 20:59
jcsacketthatch: where do we do the whole "provider has these sorts of containers" thing?20:59
jcsacketthatch: it may also be a charm upgrade issue.20:59
hatch environments.providerFeatures = {21:00
hatchgo.js 218521:00
rick_h_jcsackett: to force headers/etc add :flags:/containers21:01
rick_h_jcsackett: it overrides the normal provider settings21:01
jcsackettrick_h_, hatch: right, my env is manual, we have nothing for that.21:02
jcsackettwhich i think means anyone trying to use our stuff with the digital ocean plugin is going to have issues too, since iirc that's just a wrapper around manual.21:02
rick_h_jcsackett: ok, seems like manual provider is something we might have to check out. Sounds like both your bug and lazyPower's here is causing us issues?21:02
hatchyeah this sounds like a manual provider issue21:03
hatchI'm in the process of setting up the DO plugin to give this all a try21:03
rick_h_ok, so in our list of providers/featuers we offer is manual in that list?21:03
jcsackettrick_h_: no.21:03
rick_h_I bet that's the issue. We've got the list of features per provider and we're missing one now21:03
hatchnegative21:03
jcsacketti suspect adding it to that with no allowed containers we'll work.21:03
jcsacketts/we'll/will21:03
hatchoh waitasecond21:03
jcsackettwe should probably have a sane fallback.21:03
rick_h_jcsackett: rgr21:04
jcsacketthatch: ??21:04
hatchthese are all named off the env name?21:04
rick_h_hatch: off the provider juju tells us we're using21:04
hatchohh ok *phew*21:04
rick_h_hatch: but we didn't include 'manual' I bet and that's blowing up21:04
hatchyeah - and what does manual support? nothing?21:05
rick_h_:/ no idea21:05
rick_h_I'd say to fix the bug we start with nothing21:05
hatchhaha sounds good21:05
rick_h_and land that for the updated release EOW21:05
hatchhazmat: any idea if manual provider supports containers?21:05
rick_h_and then we can explore making it nicer going forward.21:05
jcsackettrick_h_: manual supports nothing, b/c it'll have the same no bridging issue as ec2.21:05
hatchahh ok21:05
hatchthat makes sense21:05
rick_h_hatch: jcsackett right, with manual it could be any platform, we can't tell if lxc or kvm will work/etc21:05
rick_h_it could just be my old laptops in a row in a closet21:06
lazyPowerhatch: manual supports --to lxc:#21:06
hatchhmmm21:06
jcsackettlazyPower, hatch: technically, so does ec2.21:06
hatchheh true21:06
jcsackettwe say "nope" to containers b/c while you can deploy, you can't then properly use those services without going into the server and mucking with the lxc bridge.21:06
rick_h_lazyPower: if you deploy wordpess in an lxc on ec2 and expose it...no worky21:07
lazyPowerwell none of the networking works in terms of --to containers21:07
rick_h_lazyPower: so we've cut back that in the GUI to help prevent a lot of bug reports around that until juju supports routing those network connections21:07
lazyPowerbut you can still do it. you're just expected to handle the routing yourself.21:07
rick_h_lazyPower: it does in maas :) and juju will support ec2 around end of cycle21:07
lazyPowerooo21:07
lazyPowerfantastic21:07
rick_h_lazyPower: rgr, so we have :flags:/containers to enable it anyway21:08
jcsackettrick_h_: confirmed, :flags:/containers makes everything work. i'm updating the bug in case someone else encounters this before EoW.21:08
rick_h_jcsackett: rgr21:08
rick_h_jcsackett: ty much21:08
jcsackettrick_h_: hey, happy to help with my own bug. :p21:09
jcsacketti love being an actual user of the thing i work on.21:09
hatch:D21:10
hatchlazyPower: what are you saying in your video? "ssh (tack) keygen" ?21:11
hatchyour DO video21:11
lazyPoweryep21:12
lazyPowertack = -21:13
hatchisn't that a dash? 21:13
lazyPowerits a 'tack' when i say it21:13
hatchlol ok21:13
lazyPowerbut i can see why you'd think its a dash21:13
hatch- = en dash — = em dash21:13
hatchcould that be why? :P21:13
lazyPoweryou've forgotten a very distinct dialect21:14
lazyPower- = sysadmin 'tack'21:14
hatchohh - tbh I've never heard it called a tack before21:14
lazyPowerhack at -21:15
lazyPowersee what i did there?21:15
hatchhaha21:15
hazmathatch, definitely does21:16
hazmatre containers21:16
hazmathatch, and with the rudder/flannel charm they can talk across hosts21:16
hazmatthough that makes things work across hosts in any provider21:16
lazyPowerwait21:18
hatchhazmat: right but juju doesn't support the routing so If I created two lxc containers using manual provider and installed wordpress in one and mysql in the other - I couldn't relate them21:18
lazyPowerwe have phaux networking charms that solve this?21:18
hazmathatch, on the same host it would just work21:18
lazyPowerhazmat: why are we not talking about this more prominently?21:18
hatchrick_h_: ^21:18
hazmathatch, across hosts you need one of my container sdn charms21:18
hazmathatch, currently its published as rudder21:19
hazmatbut upstreamed changed names 21:19
hatchohh so if I had two machines the units couldn't communicate21:19
hazmathatch, let me dig you up the readme21:19
hatchI think I'll still set it as disabled in the GUI for now :)21:19
hazmatno21:19
hazmathatch, so this charm does the magic sdn across hosts http://bazaar.launchpad.net/~hazmat/charms/trusty/rudder/trunk/view/head:/readme.txt21:19
lazyPowerand suddenly hazmat just gave birth to the most amazing thing I've heard all day21:20
hazmathatch, it should be a configuration option on gui21:20
hatchright but joe user won't know that relations won't "just work" which = GUI bugs which aren't our fault21:20
hazmatlazyPower, your right it deserves talking about it21:20
hazmathatch, make it an option21:20
hatchyou can enable container support using the 'container' flag in the gui21:20
hazmatlazyPower, i'm hoping to bring it up at brussels as we should do this or weave as our default sdn, 21:21
hazmatas opposed to the broken by default on providers, let's do a works on all providers by default21:21
lazyPowerI'll give ita go - when you sent the rudder email to the list, it was only 10k feet over my head21:21
lazyPowernow that you've just put it out there in plain english, i want to blog about this as well21:21
hazmatie. we do the opposite for security groups/firewalls.. we should have universal iptables and then provider specific customization around implementation21:22
hazmatas an optimization21:22
lazyPowerman, we've had this for what, over a month now?21:22
* hazmat hides21:22
hazmatgotta run EOD family time21:22
lazyPowero/ tc hazmat21:22
hatchcya thanks hazmat21:22
rick_h_Makyo: hatch do you guys think we could crank out https://bugs.launchpad.net/juju-gui/+bug/1376464 in one day during sprints?21:56
hatchoo fancy21:57
hatchwhere would it go? :)21:57
rick_h_no, simple, in the drop down menu in the upper right21:57
rick_h_under help and feedback21:57
rick_h_or maybe even on the keyboard shortcut menu would be good21:58
hatchso that might cause some issues because the flags ususally need to be set pre-init21:58
rick_h_hatch: yea, maybe we even go so far as to do a page reload on save21:58
hatchso maybe the dropdown could modify the config file21:58
hatchthen reload21:58
hatchyeah21:58
rick_h_hatch: meh, I'm thinking straight localstorage21:58
hatchahh that would also work nicely21:58
rick_h_and then on load read the key or don't at all the config points21:58
hatchyeha that would be a cool project21:59
MakyoYeah21:59
MakyoThat sounds good.21:59
rick_h_hatch: Makyo ok, goal is to do that monday and show it in a lightning talk. 21:59
rick_h_hatch: Makyo feel free to hack during flights :P21:59
MakyoHahah22:00
MakyoSounds good.22:00
rick_h_I like the idea of putting the checkboxes/etc in the keyboard help22:00
rick_h_because people don't know that's there either and it's out of the way regardless of what happens to the header later in life22:00
hatchyeah the flag code would need a minor addition to check localstorage22:01
rick_h_hatch: right22:01
hatchbut should be straight forward22:01
MakyoYeah, exactly.22:01
rick_h_ok, noted to the bug22:01
rick_h_thanks guys22:01
hatchrick_h_: maybe in the dropdown a link to open the 'developer tools' for the gui22:04
hatchwould give us a place to put random dev type things22:04
rick_h_hatch: yea, I'm worried about that moving around 22:04
rick_h_hatch: longer term22:04
rick_h_hatch: but yea, we can find a home22:04
bic2kthis one is a feature request: https://bugs.launchpad.net/juju-gui/+bug/137648722:38
hatchoh nice one :)22:40
hatchbic2k: question - would you want that zoom level saved only on your machine? Or cross the environment?22:40
hatchcross env might make for some....interesting...results for differing screen sizes :)22:40
bic2kthats why I suggest localStore for it22:41
bic2kchances are if you are accessing juju-gui from different machines they will have different browser sizes. That being said, you could store the top x,y offset for all viewers and the zoom locally for maximum effect22:42
bic2kbut really, per device probably makes the most sense22:42
bic2kits easiest to do, dumb in the right ways22:42
hatchbest kind of enhancements :P22:44
rick_h_hatch: is your blog post up?22:57
bic2kblog post for?22:57
rick_h_hatch: or is tumblr hating still?22:57
bic2kACK, never mind me22:58
rick_h_bic2k: machine view post he had prepped but never made it public22:58
bic2krick_h_ thanks ;-) I thought I was in a different window when I read that23:01
rick_h_:)23:01
hatch rick_h_ still having issues I'll get it up tonight no matter what23:01
rick_h_hatch: gotcha23:01
rick_h_huwshimi: morning23:01
huwshimiMorning23:01
* rick_h_ heads off to coffee shop, biab23:01

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