Tuesday, 2014-08-19

*** sankarshan_away is now known as sankarshan00:00
*** sankarshan is now known as sankarshan_away00:00
*** seizadi has quit IRC00:01
*** eguz has joined #openstack-meeting-300:04
*** hinnant has quit IRC00:07
*** eghobo has quit IRC00:08
*** eghobo has joined #openstack-meeting-300:12
*** eguz has quit IRC00:16
*** hinnant has joined #openstack-meeting-300:17
*** hinnant has quit IRC00:17
*** yamahata has joined #openstack-meeting-300:18
*** eghobo has quit IRC00:19
*** eghobo has joined #openstack-meeting-300:19
*** SridharRamaswamy has quit IRC00:22
*** otherwiseguy has joined #openstack-meeting-300:22
*** rudrarug_ has quit IRC00:34
*** cjellick has quit IRC00:41
*** cjellick has joined #openstack-meeting-300:42
*** cjellick has quit IRC00:46
*** armax has quit IRC00:50
*** terryw has joined #openstack-meeting-300:51
*** shwetaap has joined #openstack-meeting-300:52
*** otherwiseguy has quit IRC00:54
*** otherwiseguy has joined #openstack-meeting-300:59
*** SumitNaiksatam has joined #openstack-meeting-301:01
*** terryw has quit IRC01:02
*** eghobo has quit IRC01:14
*** eguz has joined #openstack-meeting-301:14
*** stanzgy has joined #openstack-meeting-301:18
*** hinnant has joined #openstack-meeting-301:23
*** eguz has quit IRC01:27
*** eghobo has joined #openstack-meeting-301:27
*** eguz has joined #openstack-meeting-301:28
*** eghobo has quit IRC01:28
*** eguz has quit IRC01:31
*** eghobo has joined #openstack-meeting-301:31
*** hinnant has quit IRC01:32
*** shakamunyi has joined #openstack-meeting-301:34
*** otherwiseguy has quit IRC01:44
*** stanzgy has quit IRC01:48
*** seizadi has joined #openstack-meeting-301:50
*** seizadi has quit IRC01:56
*** stanzgy has joined #openstack-meeting-301:57
*** otherwiseguy has joined #openstack-meeting-301:59
*** shwetaap has quit IRC02:01
*** seizadi has joined #openstack-meeting-302:04
*** eguz has joined #openstack-meeting-302:05
*** eguz has quit IRC02:05
*** eghobo has quit IRC02:08
*** alexpilotti has quit IRC02:09
*** mwagner_lap has joined #openstack-meeting-302:10
*** carl_baldwin has joined #openstack-meeting-302:14
*** seizadi has quit IRC02:37
*** amotoki_ has quit IRC02:37
*** otherwiseguy has quit IRC02:41
*** shwetaap has joined #openstack-meeting-302:57
*** aleksandr_null has quit IRC03:06
*** aleksandr_null has joined #openstack-meeting-303:06
*** shakamunyi has quit IRC03:09
*** vkmc has quit IRC03:21
*** markmcclain has quit IRC03:24
*** Sukhdev has joined #openstack-meeting-303:27
*** amotoki has joined #openstack-meeting-303:33
*** rudrarugge has joined #openstack-meeting-303:43
*** rudrarugge has quit IRC03:43
*** rudrarugge has joined #openstack-meeting-303:44
*** SumitNaiksatam has quit IRC03:47
*** SumitNaiksatam has joined #openstack-meeting-303:48
*** seizadi has joined #openstack-meeting-303:53
*** shakamunyi has joined #openstack-meeting-304:07
*** shwetaap has quit IRC04:09
*** shwetaap has joined #openstack-meeting-304:10
*** otherwiseguy has joined #openstack-meeting-304:13
*** rudrarugge has quit IRC04:14
*** rudrarugge has joined #openstack-meeting-304:16
*** otherwiseguy has quit IRC04:24
*** flaviof_zzz is now known as flaviof04:30
*** s3wong has joined #openstack-meeting-304:36
*** rudrarugge has quit IRC04:38
*** eghobo has joined #openstack-meeting-304:40
*** banix has joined #openstack-meeting-304:53
*** natarajk has joined #openstack-meeting-304:58
*** natarajk has left #openstack-meeting-305:05
*** shakamunyi has quit IRC05:13
*** eghobo has quit IRC05:13
*** eghobo has joined #openstack-meeting-305:14
*** ctracey has quit IRC05:16
*** chuckC_ has joined #openstack-meeting-305:16
*** sandr8 has quit IRC05:16
*** hinnant has joined #openstack-meeting-305:19
*** ctracey has joined #openstack-meeting-305:20
*** seizadi has quit IRC05:23
*** Sukhdev has quit IRC05:27
*** s3wong has quit IRC05:27
*** banix has quit IRC05:30
*** banix has joined #openstack-meeting-305:31
*** sandr8 has joined #openstack-meeting-305:32
*** chuckC_ has quit IRC05:32
*** banix has quit IRC05:34
*** k4n0 has joined #openstack-meeting-305:36
*** reed has quit IRC05:42
*** shwetaap has quit IRC05:45
*** tmazur has joined #openstack-meeting-305:52
*** carl_baldwin has quit IRC05:56
*** baohua has joined #openstack-meeting-306:07
*** hinnant has quit IRC06:12
*** baohua_ has joined #openstack-meeting-306:29
*** baohua has quit IRC06:32
*** tmazur has quit IRC06:33
*** flaper87|afk is now known as flaper8706:46
*** tmazur has joined #openstack-meeting-306:46
*** MaxV has joined #openstack-meeting-306:54
*** pkoniszewski has joined #openstack-meeting-307:05
*** MaxV has quit IRC07:11
*** mwagner_lap has quit IRC07:13
*** Longgeek has joined #openstack-meeting-307:26
*** jcoufal has joined #openstack-meeting-307:26
*** jtomasek has joined #openstack-meeting-307:29
*** MaxV has joined #openstack-meeting-307:44
*** eghobo has quit IRC07:50
*** jcoufal has quit IRC07:51
*** jcoufal has joined #openstack-meeting-308:03
*** Longgeek has quit IRC08:04
*** Longgeek has joined #openstack-meeting-308:05
*** Longgeek has quit IRC08:06
*** Longgeek has joined #openstack-meeting-308:06
*** igordcard has joined #openstack-meeting-308:33
*** Longgeek has quit IRC08:42
*** Longgeek has joined #openstack-meeting-308:43
*** overlayer has joined #openstack-meeting-308:47
*** igordcard has quit IRC08:47
*** Longgeek has quit IRC08:47
*** Longgeek has joined #openstack-meeting-308:49
*** yamahata has quit IRC08:57
*** baohua_ has quit IRC09:31
*** kashyap is now known as kashyapc09:34
*** alexpilotti has joined #openstack-meeting-309:45
*** tsufiev has left #openstack-meeting-309:50
*** MaxV has quit IRC10:03
*** overlayer has quit IRC10:09
*** Longgeek has quit IRC10:24
*** MaxV has joined #openstack-meeting-310:44
*** Longgeek has joined #openstack-meeting-310:53
*** overlayer has joined #openstack-meeting-311:10
*** jab has joined #openstack-meeting-311:25
*** jab has quit IRC11:25
*** jab has joined #openstack-meeting-311:25
*** Longgeek has quit IRC11:26
*** Longgeek has joined #openstack-meeting-311:26
*** overlayer has quit IRC11:41
*** vkmc has joined #openstack-meeting-311:43
*** vkmc has quit IRC11:43
*** vkmc has joined #openstack-meeting-311:43
*** salv-orlando_ has joined #openstack-meeting-311:43
*** salv-orlando has quit IRC11:43
*** salv-orlando_ is now known as salv-orlando11:43
*** SumitNaiksatam_ has joined #openstack-meeting-311:48
*** baohua has joined #openstack-meeting-311:49
*** SumitNaiksatam has quit IRC11:49
*** SumitNaiksatam_ has quit IRC11:49
*** salv-orlando has quit IRC11:49
*** SumitNaiksatam has joined #openstack-meeting-311:49
*** salv-orlando has joined #openstack-meeting-311:55
*** sdague has joined #openstack-meeting-312:04
*** kashyapc is now known as kashyap12:10
*** kashyap is now known as kashyapc12:16
*** jab is now known as bradjones12:27
*** seizadi has joined #openstack-meeting-312:38
*** julim has joined #openstack-meeting-312:42
*** julim has quit IRC12:43
*** stanzgy has quit IRC12:53
*** amotoki has quit IRC13:03
*** julim has joined #openstack-meeting-313:03
*** mfer has joined #openstack-meeting-313:16
*** jpomero has quit IRC13:19
*** peristeri has joined #openstack-meeting-313:23
*** jaypipes has joined #openstack-meeting-313:29
*** jpomero has joined #openstack-meeting-313:38
*** thomasem has joined #openstack-meeting-313:42
*** jcoufal has quit IRC13:45
*** jcoufal has joined #openstack-meeting-313:46
*** HenryG_ has joined #openstack-meeting-313:46
*** HenryG has quit IRC13:47
*** shwetaap has joined #openstack-meeting-313:48
*** danpb has joined #openstack-meeting-313:49
*** lblanchard has joined #openstack-meeting-314:05
*** HenryG_ is now known as HenryG14:07
*** markmcclain has joined #openstack-meeting-314:07
*** amotoki has joined #openstack-meeting-314:12
*** nelsnelson has joined #openstack-meeting-314:16
*** shakamunyi has joined #openstack-meeting-314:16
*** thangp has joined #openstack-meeting-314:21
*** mfer has quit IRC14:23
*** david-lyle has joined #openstack-meeting-314:24
*** reed has joined #openstack-meeting-314:26
*** celttechie has joined #openstack-meeting-314:30
*** jpich has joined #openstack-meeting-314:31
*** shakamunyi has quit IRC14:32
*** seizadi has quit IRC14:34
*** carl_baldwin has joined #openstack-meeting-314:37
*** mestery_afk is now known as mestery14:39
*** celttechie has quit IRC14:45
*** kashyapc is now known as kashyap14:45
*** shakamunyi has joined #openstack-meeting-314:47
*** kashyap is now known as kashyapc14:48
*** kashyapc is now known as kashyap14:49
*** apmelton has joined #openstack-meeting-314:51
*** markmcclain has quit IRC14:52
*** rcleere has joined #openstack-meeting-314:53
*** markmcclain has joined #openstack-meeting-314:53
*** mfer has joined #openstack-meeting-314:54
*** mtesauro has joined #openstack-meeting-314:54
*** sew has joined #openstack-meeting-314:57
*** celttechie has joined #openstack-meeting-314:57
*** julim has quit IRC14:59
danpb#startmeeting libvirt15:00
openstackMeeting started Tue Aug 19 15:00:45 2014 UTC and is due to finish in 60 minutes.  The chair is danpb. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: libvirt)"15:00
openstackThe meeting name has been set to 'libvirt'15:00
danpb..if anyone is here & wants to talk about libvirt issues make yourselves known...15:01
sewo/15:01
*** mestery is now known as mestery_afk15:01
thomasemo/15:02
*** bauzas has joined #openstack-meeting-315:02
apmeltono/15:02
mtesauroo/15:02
rcleereo/15:02
nelsnelsono/15:02
*** lsmola2 has joined #openstack-meeting-315:03
*** seizadi has joined #openstack-meeting-315:03
danpbwelcome folks, so the only item added to the etherpad is from rcleere15:04
danpb#topic Libvirt ulimit patch15:04
*** openstack changes topic to "Libvirt ulimit patch (Meeting topic: libvirt)"15:04
danpbrcleere: ..your turn :-)15:04
*** s1rp has joined #openstack-meeting-315:04
rcleereok15:04
rcleereSo, when we boot containers the container inherits ulimits from the libvirt_lxc process15:04
rcleereone of those being no_file (max file descriptors a process can have)15:05
danpbok, standard unix inheritance which is probably quite unhelpful here :-)15:05
rcleerethis introduces xml to set it in the instance XML that would get applied when executing the init process of the container.15:05
*** seizadi has quit IRC15:06
danpbrcleere: what is your end goal here - is it to simply avoiding inheriting a possibly stupid limit from libvirt_lxc15:06
sewwith this patch, eventually we could apply flavor specific open file limits15:06
rcleereThe other hacky way I was doing it was to have a shell wrapper around libvirt_lxc that set it then passed all args to the real libvirt_lxc15:06
danpbrcleere: or is to to use this for some kind of explicit resource control polocy15:06
rcleereexplicit resource control.15:07
rcleereI should mention we are using user namespace, so as root in the container you cannot increase the no_file only decrease it15:07
danpbhmm, so that raises questions of just how the mechanism works, particularly wrt user namespaces15:08
danpbah, that's what i was going to ask - does user namespace give you compete unrestricted control over the ulimits15:08
rcleerenope15:08
rcleerejust decrease15:08
danpbso semantically is the num files limit of the container a global limit that will apply to the sum of all child processes it starts15:09
rcleereso as it is in our environment the kernel sets a soft limit of 1024 and a hard limit of 4096. we dont change those in our running environment. libvirt_lxc inherits that so does container init.15:09
rcleereunfortunatly not15:09
rcleereit is the max open files per process.15:09
danpbi recall previously seeing discussions about whether  ulimits needed to be mapped into cgroups to apply to an entire process set15:09
rcleerethey really should be mapped to cgroups and/or namespaces15:09
thomasemSeems like it'd make more sense that way15:10
danpbyeah so if it is per-process it isn't very useful as a resource limiting mechanism15:10
danpbas you can just spawn more processes to escape the limit15:10
rcleereThere had been some talk on the kernel mailing and some patches but none have made it in.15:10
sewi like that ulimit inside the container reports correct limits with rcleere's approach15:10
danpbgiven that current impl, why would be not simply set the container init to have  (hard_limit == soft_limit) ==  hard limit of libvirt-lxc ?15:11
rcleeredanpb: true it is not a real limit on the container, BUT it does allow things like mysql, ngingx, haproxy to set higher limits for incoming tcp connections that it needs.15:11
danpbit isn't offering any resource control - so only useful thing we can do is avoid the accidental capping of the soft limit15:11
rcleeredanpb: not sure I understand your question15:11
danpbso say libvirt_lxc has soft=1024, hard=819215:12
danpbwhy would we not simply set  the init process to have  hard=8192, soft=8192 and avoid any XML confijg15:12
rcleereit already does.15:12
*** markmcclain has quit IRC15:12
danpbthe XML config doesn't seem to add any real value here  until we can set  num_files liimits against the cgroup so they actually work as a global cap on the container15:13
sewwe'd eventually like to customize the number of open files value based on flavor15:13
sewand having an XML directive seemed to be a good place to define it15:13
rcleereBut I dont want to blindly set ALL containers an arbitrarally high no_files limit if they dont need it.15:13
danpbsew: sure i understand that, but it feels like that needs the cgroups integration for ulimits15:14
rcleerelike the haproxy example. if we were going to use that as a LB, then I would probably want the no_files limit to 10000+ but I dont really want that for all of my containers.15:14
apmeltonthe idea behind this change is to allow good processes to work properly, not to disallow bad processes from behaving badly15:15
thomasem(which they could anyway)15:15
rcleereapmelton: very good point15:15
mtesauro+1 on amelton's pont15:15
danpbapmelton: yep, but my concern is around the long term implications of  a short term decision15:16
*** akrivoka has joined #openstack-meeting-315:16
danpbapmelton: eg if we add config setting for the current per-process ulimit vs later  per-container ulimit15:16
danpband whether it makes sense to support both approaches in the long term or not15:17
apmeltondanpb: why not both once they're available15:17
apmeltonah15:17
apmeltonso, being able to set ulimit and have it appear correctly in a container will be useful for processes that aren't cgroup aware15:17
danpbi guess you could say that if you had a per-container ulimit of  100,000 files15:17
*** alexpilotti has quit IRC15:18
danpbwould it still make sense to be able to say that the init process only had 8192 per-process limit15:18
*** flaper87 is now known as flaper87|afk15:19
danpbdoes anyone know what limits a real pid1 will get from the kenrel15:19
rcleere1024/409615:19
danpbbut pid1 still has the ability to raise its own hard limit i guess15:20
danpbwhich we do not have in containers even with user namespace15:20
rcleereas root any process can raise its hard limit15:20
danpbany process with CAP_SYS_RESOURCE i guess15:21
rcleerethat I dont know15:21
danpboh well, i guess I'd say you should make a patch proposal to the libvirt list and we can discuss the finer details there15:22
rcleereok15:23
danpb#topic qemu-nbd mounting15:26
*** openstack changes topic to "qemu-nbd mounting (Meeting topic: libvirt)"15:26
danpbs1rp: ^^15:26
nelsnelsonHowdy danpb.  s1rp and I were trying to get libvirt-lxc working with a simple tempest test in devstack over the past few days...15:27
s1rpyeah, so just started digging into that at the end of the day yesterday; but i don't think it's a 'bug' in libvirt per se; just the fact that AMIs + qemu-nbd + mount aren't work off the bat15:27
s1rpwe've been using LVM for a few months, so qemu-nbd stuff is very unfamiliar, so not even sure if i can ask the right questions at the moment :-)15:28
*** cjellick has joined #openstack-meeting-315:29
nelsnelsonThe effect is basically that the rootfs filesystem on the disk seems to fail to pupulate correctly.  Correct, s1rp?15:29
danpbthe idea behiind the qemu-nbd stuff is simply that it lets us use  qcow2 files directly without having to flatten them into raw files15:29
nelsnelsonpopulate*15:29
danpbassuming qemu-nbd is not buggy, you aren't supposed to notice any difference vs plain raw files15:29
apmeltondoes qemu-nbd/qemu-img even support ami?15:30
*** baohua has quit IRC15:30
s1rpdanpb: yeah the qcow2 part does work fine...15:30
danpbapmelton: oh, wait, what do you mean by 'ami' here ?15:31
s1rpso we're using the cirros image from devstack15:31
apmeltondanpb: I'm wondering the same thing, s1rp, what AMI are you talking about?15:31
danpbthis isn't just a plain disk image in raw or qcow2 format ?15:31
danpbi thought AMI was just a term to refer to the 3 files (kernel, initrd, disk image)15:31
*** lcheng has joined #openstack-meeting-315:32
danpbmust admit i've not looked at cirros in any great detail though15:32
s1rpdanpb: right, which is why it's not going to work... we're just going to need to use a different image for the LXC tempest tests15:32
danpbso you can't just boot a regular cirros disk image without the  kernel/initrd part being used15:34
danpbnaively i'd hope the cirros disk image would just let you run the init inside it15:34
apmeltons1rp: does tempest not use the normal cirros image that comes with devstack?15:34
s1rpdanpb: yeah so we're attempting that, but it's not working off the bat... still digging into figure out exactly why.... sorry not too many more details i can offer15:34
s1rpwe end of with an empty filesystem mounted to rootfs right now15:35
danpbyeah, i'd be interested in hearing what you find out15:35
apmeltonI could have sworn I got it to at least start a cirros container15:35
thomasemthere are two cirros images in devstack15:35
s1rpapmelton: yeah i vaguely recall that as well, but i'm not sure what's different this go around15:35
*** pkoniszewski has quit IRC15:35
thomasemone being raw format for libvirt-lxc15:35
s1rpdid we have to recompile qemu-nbd15:35
s1rp?15:35
apmeltons1rp: nope15:36
s1rphmm15:36
apmeltonthe only thing I ever had to do was modprobe nbd15:36
apmeltonfor some reason devstack won't load it when running lxc15:36
thomasemapmelton: I also got it running containers, but that was months ago.15:36
s1rpyeah, the module is loaded15:36
thomasembut they consistently worked fine in Devstack15:36
danpbohhh, hang on,the cirros image is wierd15:37
s1rpoh really?15:37
s1rpso when i try to qemu-nbd/mount it, i just end of w/ 'lost+found'15:37
danpbso the disk image  just looks like an empty ext3 filesystem15:37
s1rpi'd expect a full filesystem15:37
s1rpyeah that's what im seeing15:37
danpbi wonder if all the real data is in the initrd cpio file15:38
danpband just gets copied into this empty filesystem by the initrd15:38
s1rpso that's what i was starting to think...15:38
s1rphaven't gotten to confirm that though15:38
s1rpso if that's the case, how did we get cirros working before?15:38
danpbperhaps we'll just have to make devstack able to convert the default cirros image into a normal filesystem when it sees it is configured for libvirt LXC15:38
s1rpapmelton ^^^15:38
s1rpdanpb: yeah a shim shouldn't be too hard to write, i hope15:39
apmeltons1rp: must be something new, I know I had cirros working at least to the point where I could virsh console into it15:39
*** mestery_afk has quit IRC15:39
apmeltoni might still have the devstack vm around that I can poke in15:40
danpbyeah wonder if the cirros upstream changed15:40
s1rpyeah, so im going to look in the initrd to see what's hiding in there15:40
s1rphopefully that answers it, and we can just do a copy into the rootfs, and then mount for lxc15:40
s1rpwould really like the gate to use 'cirros' image though15:41
s1rpthat way we're literally just flipping virt_type from qemu -> lxc15:41
*** kgriffs|afk is now known as kgriffs15:41
s1rpeven if behind the scenes we're doing some hacky stuff to make that work15:42
*** kgriffs has left #openstack-meeting-315:42
thomasems1rp, nelsnelson: may I see the local.conf for your devstack?15:42
s1rpyou mean locarc?15:43
s1rp*localrc?15:43
thomasems1rp: Sure, it's local.conf now15:43
thomasemhttp://devstack.org/15:44
thomasemlocalrc is the old way15:44
apmeltons1rp: danpb: cirros image from july 16th devstack contains a single rootfs image15:44
s1rpah right, so i'm just using the prompts to generate .local.auto15:44
thomasemhttps://github.com/openstack-dev/devstack/blob/a6a45467c412476b2cddb8526a97e421b0b74db7/stackrc#L354-L35615:44
apmeltons1rp: when you switched to lxc, did you just flip the config, or did you rebuild?15:44
apmeltonthomasem: ah ha15:45
s1rpapmelton: just flipped the config15:45
s1rpthomasem: ahhh15:45
*** dulek has joined #openstack-meeting-315:45
s1rpthomasem: well that's the answer, thanks!15:46
thomasemmy pleasure!15:46
s1rptempest tests, one step closer, 999 more to go15:46
thomasem:P15:46
danpbapmelton: the image i looked at is from just a day or two ago15:48
danpbanyway, this doesn't sound like it is a libvirt problem per se, rather a cirros problem15:48
apmeltondanpb: there are two different images devstack will pull down, the uec style or rootfs style15:48
danpbah,15:48
thomasemfinally my 2 months in devstack hell pay off15:48
thomasem:)15:48
nelsnelson:)15:49
thomasemWell, they did back then too. Now it's just icing.15:49
danpblol15:49
danpb#topic idmap15:49
*** openstack changes topic to "idmap (Meeting topic: libvirt)"15:49
sewso i know we discussed the idmap and block devices issue a while back, but i was curious if there are any new thoughts?15:50
danpbsew: can you refresh my mind ?15:50
danpbis the problem that we need to find a way to mount the block dev before we run id remaping ?15:50
sewyes, i think so15:50
sewwhen using lvm with idmap for example15:51
danpbyeah, guess that does make sense really15:51
sewi would imagine anyone attempting to run containers with user namespaces enabled and block backed filesystems would be hitting this15:51
danpbhmm, oh,  type=block is only used when we boot from cinder volume, right ?15:52
sewcinder would be block device15:53
sewbut we're seeing this problem with just local logical volumes15:53
apmeltondanpb: we'd like to move to type=block for lvm images as well15:53
danpbright now though, for non-volume based instances we're always mounting the image (whether lvm, raw or qcow2) in the host and then using  type=mount so idmap can run without trouble15:54
s1rpit's be nice to be able to start VMs using libvirt, rather than have to nova mount the drive, then start the guest15:54
sewreboot inside the container also fails under the mounted approach15:55
danpbif we change so that libvirt is responsible for all the mounting, then we'll face this problem for all types of root disk,  lvm., raw, qcow215:55
*** armax has joined #openstack-meeting-315:55
*** sdague has quit IRC15:55
apmeltondanpb: moving the responsibility to libvirt would allow the removal of a bunch of extra lxc code paths in nova15:55
danpbit seems that somewhere in the guest startup process we will always need to mount the images or volumes in the host, run the idmap, and then unmount again and handoff to libvirt15:55
danpbapmelton: yeah, i'd like to see that happen15:56
apmeltondanpb: this isn't idmapshift15:56
apmeltondanpb: this is the setting up of the actual user namespace15:56
danpboh, you mean  libvirt itself is broken with type=block and user namespaces15:56
apmeltonit appears that the mounting of the block device is done from within the user namespace15:56
apmeltondanpb: yup15:56
sewyes15:56
danpbsorry, ok, now i see15:57
danpbguess someone will need to poke around in the code to see how we might fix it - presumably we need to chown the block device before starting the user namespace , or possibly even mount it before hand ?15:57
*** TravT has joined #openstack-meeting-315:58
sewi played with changing device ownership a bit , but didn't find a winning combo15:58
danpbafraid we're out of time here today15:59
danpbhave to make way for the next meeting to use this channel15:59
*** emagana has joined #openstack-meeting-315:59
sewsounds good.  thx danpb15:59
danpbbest take this to the mailing list or bug tracker15:59
*** tzumainn has joined #openstack-meeting-315:59
danpb#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Tue Aug 19 15:59:52 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-08-19-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-08-19-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-08-19-15.00.log.html15:59
david-lyle#startmeeting Horizon16:00
apmeltontake care everyone!16:00
openstackMeeting started Tue Aug 19 16:00:15 2014 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** otherwiseguy has joined #openstack-meeting-316:00
*** openstack changes topic to " (Meeting topic: Horizon)"16:00
*** MarkAtwood has joined #openstack-meeting-316:00
openstackThe meeting name has been set to 'horizon'16:00
thomasemthanks everyone! Take it easy!16:00
*** apmelton has left #openstack-meeting-316:00
david-lyleHello16:00
akrivokahello!16:00
*** pawels has joined #openstack-meeting-316:00
akrivoka\o16:00
jpichHello16:00
*** gary-smith has joined #openstack-meeting-316:00
tzumainnhiya!16:00
gary-smithhi16:00
TravT0/16:00
pawelshi16:01
bradjoneshi16:01
*** danpb has left #openstack-meeting-316:01
*** nlahouti has joined #openstack-meeting-316:01
*** rbertram has joined #openstack-meeting-316:01
*** tsufiev has joined #openstack-meeting-316:01
jristo/16:02
david-lylelet's start with https://launchpad.net/horizon/+milestone/juno-316:02
*** jgravel has joined #openstack-meeting-316:02
*** celttechie has quit IRC16:02
lchenghello16:02
david-lyleBlueprints:16:02
david-lyle1 Unknown, 7 Started, 4 Slow progress, 6 Good progress, 1 Beta Available, 35 Needs Code Review, 8 Implemented16:02
david-lylewe're making progress, but lots up for review16:02
*** seizadi has joined #openstack-meeting-316:03
david-lyleI think https://blueprints.launchpad.net/horizon/+spec/remove-javascript-bundling is almost ready with a couple caveats16:03
gugl2hi16:03
jpichThat's my understanding as well16:03
david-lyleI don't see radomir online16:03
amotokihi16:03
*** sdague has joined #openstack-meeting-316:03
*** dickson.freenode.net changes topic to "qemu-nbd mounting (Meeting topic: libvirt)"16:03
jpichThere'll be follow-up patches but the biggest part is ready to merge16:03
*** mxu has joined #openstack-meeting-316:04
david-lylethat's great, I'd even be ok tracking the remaining pieces as high priority bugs16:04
jpichSounds like a good idea16:04
*** alexpilotti has joined #openstack-meeting-316:04
david-lylethe other high bp open is https://blueprints.launchpad.net/horizon/+spec/launch-instance-ux-enhancement16:05
*** clu_ has joined #openstack-meeting-316:05
david-lyleMaxV: do you have a better feel for if that is a Juno or Kilo target?16:05
*** alexpilotti has quit IRC16:06
*** alexpilotti has joined #openstack-meeting-316:06
david-lylemy feel is that won't make it, but I want to give MaxV a chance to give an update16:06
david-lyleso I'll ping him separately16:06
MaxVdavid-lyle: I do the max but it seems that it will be for Kilo, I have made some refactoring and patches, I will have the best look on friday16:07
david-lyleMaxV: ok thanks for the update, I'm going to move it to Kilo, if you can get it ready, I'll move it back into Juno, just want to set expectations at this point16:08
*** harrisonkelly has joined #openstack-meeting-316:08
*** doug-fish has joined #openstack-meeting-316:08
rbertramMaxV: I'm still available to help, if I can16:09
MaxVrbertram: https://review.openstack.org/#/c/115321/116:09
*** rdopieralski has joined #openstack-meeting-316:09
rbertramMaxV: ok, cool16:09
rdopieralskiI'm sorry for being late16:10
david-lyleMaxV, rbertram, keep me updated16:10
david-lylerdopieralski: we discussed the js separation bp a bit16:10
MaxVrbertram: If you have a good understanding of angular, there is the flavor to implement following this16:11
rdopieralskidavid-lyle: I will read the log16:11
*** emagana has quit IRC16:11
david-lyleseems like the majority is ready to go and there will be a couple of patches for straggling patches in requirements16:11
david-lylewe can track those with bugs16:11
rdopieralskidavid-lyle: yes, I actually removed the struggling ones from the one mega-patch16:11
*** emagana has joined #openstack-meeting-316:12
*** mfer has quit IRC16:12
rdopieralskidavid-lyle: so that it will finally merge16:12
*** jacalcat has joined #openstack-meeting-316:12
david-lylerdopieralski: sounds great, thank you16:12
*** emagana has quit IRC16:12
david-lyleI'll try out the updated patch after this16:12
rdopieralskiI should have made a separate patch for each of them from the beginning16:12
*** emagana has joined #openstack-meeting-316:12
david-lyleshouldn't be this hard16:12
* david-lyle should know that it is16:12
david-lylethere are a few medium bps that are in slow progress16:13
david-lylethese will likely be bumped16:14
david-lyleOn the plus side, lots of things to review16:14
rdopieralskiyay16:14
david-lylemany opportunities to exercise your code review skills16:15
david-lyleall help is appreciated16:15
david-lyleI think that covers Juno-316:15
david-lylekeep up the great work everyone16:16
*** SridharRamaswamy has joined #openstack-meeting-316:16
david-lyleOnly one topic on the agenda for today16:16
david-lyle#topic modified js library and packaging issue (pawels)16:16
*** openstack changes topic to "modified js library and packaging issue (pawels) (Meeting topic: Horizon)"16:16
TravThey david-lyle16:16
*** yinzuo has joined #openstack-meeting-316:16
david-lyle#link https://review.openstack.org/#/c/10495616:16
TravTlet me introduce it16:16
TravTwe have a high priority Glance feature called the Metadata Definitions Catalog that will land in Juno #link: https://blueprints.launchpad.net/glance/+spec/metadata-schema-catalog16:17
TravTit is going through final Glance code review now.16:17
TravTwe have several related horizon patches that we've had some code review on16:17
*** dulek has quit IRC16:17
TravTwe'd love more eyes on them soon, but today we have a specific question on how to handle a js library16:17
TravTas david-lyle mentioned the question relates to #link: https://review.openstack.org/10495616:17
TravTwe used a 3rd party angular tree widget as the basis for the code and then customized it quite a bit to fit in with horizon and for our use case16:17
*** lsmola2 has quit IRC16:17
TravTit has an MIT license and is hosted on git hub16:17
TravTso basically, our question is if we can just directly include the code (as we've done) or if we need to fork this on git hub and package?16:18
*** SridharRamaswamy has quit IRC16:18
*** MaxV has quit IRC16:18
pawelswe have already "removed" AngularJS update from the patch16:18
*** MaxV has joined #openstack-meeting-316:18
pawelsand this is understood16:18
*** SridharRamaswamy has joined #openstack-meeting-316:18
pawelsbut now we have library https://github.com/nickperkinslondon/angular-bootstrap-nav-tree modified as a part of patch16:19
david-lyleGenerally, it's best to fix issues with upstream projects, upstream, but this sounds like a significant fork16:19
pawelsyeap, this is a fork16:19
pawelsit's not a fix of original library16:19
david-lyleand this is behavior the original library would not want to include?16:20
rdopieralskiin the perfect world, you would make a patch for the original library and they would include what you need as options16:20
pawelsI believe it is more  Horizon Metadata feature changes16:20
*** harrisonkelly has quit IRC16:21
pawelsbut I would guess they may not be willing to include "a feature specyfic changes"16:21
TravTyes, the changes are mostly horizon / glance metadata definition specific16:21
pawelsin mainstream16:21
rdopieralskipawels: you might try asking, you never know16:21
rdopieralskiI mean, they could be generalized to be useful for the general population16:21
rdopieralskipawels: do you have an example of such change?16:22
pawelsthere is a change: https://review.openstack.org/#/c/104956/1..52/horizon/static/horizon/js/angular/directives/abn_tree_directive.js16:22
pawelse.g.:16:22
pawels module.directive('abnTree', [67    '$timeout', function($timeout) {    '$timeout', 'capabilitiesService', function($timeout, capabilitiesService) {16:22
pawelswhere a "capabilitiesService" is like Horizon Metadata code16:22
*** lsmola2 has joined #openstack-meeting-316:23
pawelsangular.forEach(capabilitiesService.metadata, function(item){16:23
*** MaxV has quit IRC16:23
pawelsthat kind of change16:23
rdopieralskilooks like you are mixing library with the model16:23
*** rudrarugge has joined #openstack-meeting-316:23
rdopieralskithere is no cleaner way of doing that?16:24
*** johnma has joined #openstack-meeting-316:25
TravTi'm not sure about that, but the widget on github is a simple tree, like a folder structure.16:25
pawelsso it doesn;t fit our need16:25
TravTit provides a good bases16:25
TravTbut as it stands, it definitely does not fit our needs16:26
*** eghobo has joined #openstack-meeting-316:26
TravTrdopieralski: we'd be happy to demonstrate it to you16:26
*** julim has joined #openstack-meeting-316:27
TravTour changes are very specific to the new Glance service and managing metadata on openstack.16:28
rdopieralskiTravT: what I'm wondering about is whether the special additional features that you need could be added to the original library in a way that is not horizon-specific16:28
gary-smithand also preferably not glance-specific, so they could be re-used within horizon16:29
rdopieralskiI know it's easier to just modify it like this16:29
rdopieralskibut not very useful in the long term16:29
TravThmm... not sure why it isn't very useful in the long term.16:30
TravTit isn't glance specific.16:30
TravTthe data it gets comes from Glance16:30
TravTbut there are four dependent uses of it that make it work with flavors, aggregates, and volumes16:30
david-lyleso why wouldn't the upstream library be in favor of the changes if they are not glance specific?16:31
TravTwell, we can always ask.16:31
david-lylethat's the preferred path16:31
david-lyletry to work with the library maintainer to get the generalized feature supported in that library16:32
david-lyleif/when it becomes clear that the maintainer doesn't want to support your use case, then we talk about bringing in a fork and taking on the maintenance burden for that16:33
TravTokay, so we can take a look at that and reach out.16:33
TravTTBH16:33
*** Radu_ has joined #openstack-meeting-316:33
TravTI feel it may become a bigger maintenance burden to not bring it in.16:33
*** markmcclain has joined #openstack-meeting-316:34
david-lylemultiply bringing it in times 100+16:34
david-lylethat's our number of dependencies, roughly estimated16:34
TravTAhh, what's one more! ;-)16:35
TravTSo, we'll look at it and see if we can get it in the external library16:35
TravTif they accept, what's the path from there?16:35
david-lyleexcellent16:35
TravTIf the don't accept, what's the path from there?16:35
david-lylebuild an xstatic copy of the library - add it to the global requirements - add to horizon16:36
* david-lyle remembers he owes the mailing list an email regarding this subject16:36
*** SumitNaiksatam has quit IRC16:36
*** dconde has joined #openstack-meeting-316:36
TravTAnd if they don't accept?16:37
TravTit hasn't been touched since April.16:37
david-lyle#action david-lyle send dev mailing list new approval process for JavaScript libraries in Horizon16:37
*** SumitNaiksatam has joined #openstack-meeting-316:37
clu_david-lyle: +1 would like to learn about the process16:37
*** tqtran has joined #openstack-meeting-316:37
david-lylehasn't been touched because it hasn't had your input :)16:37
david-lyleif no progress on the upstream, we can look to fork, then follow the rest of the same steps16:38
TravTok16:38
pawelsthanks16:38
rdopieralskibut even if forked, it should be a general-purpose library, not horizon-specific16:38
rdopieralskiI think16:39
david-lyle+116:39
pawelsrdopieralski: sure16:39
david-lyleanother approach, try to just get an extensibility point into the upstream library and then create a horizon specific js file to leverage that extensibility point16:40
david-lylenot sure how to accomplish that in angular16:40
david-lylebut something to consider16:40
pawelswill try and go back to you ;()16:40
david-lylethanks16:40
jpich+116:40
david-lyle#topic Open Discussion16:41
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"16:41
bradjonesI have a question regarding https://bugs.launchpad.net/horizon/+bug/128848416:41
*** eghobo has quit IRC16:41
bradjonesit talks about moving rickshaw graphs to d3 to support axis titles16:42
bradjonesIt seems to me that there should be a standard graphing library for horizon (maybe d3)16:42
bradjonesis there a reason this is not the case?16:42
*** seizadi has quit IRC16:43
david-lyled3 was chosen as the standard, rickshaw builds on top of that and was included to avoid reinventing16:43
*** seizadi has joined #openstack-meeting-316:43
bradjonesok so for the bug in question it is not asking to rewrite the graphs in d3?16:44
lsmolabradjones: rickshaw is using D316:44
*** ultimate has joined #openstack-meeting-316:44
lsmolabradjones: it's framework around d3 for timeseries data16:44
*** thinrichs has joined #openstack-meeting-316:44
david-lylethe bug is essentially, we can't label axis16:44
lsmolabradjones: what are exactly axis titles?16:45
*** seizadi has quit IRC16:45
david-lylebeyond that, the rest is conjecture16:45
*** seizadi1 has joined #openstack-meeting-316:45
david-lylelabels I assume16:45
bradjonesyeah labels sorry16:45
lsmoladavid-lyle: like with values? or with name?16:45
*** SumitNaiksatam has quit IRC16:45
david-lyley and x for example16:45
david-lyleheight and width16:45
david-lylenames16:46
bradjonesi took it to mean names16:46
david-lyleclu_: insight?16:46
david-lyleor clarification16:46
lsmoladavid-lyle: right16:46
*** pballand has joined #openstack-meeting-316:46
clu_david-lyle: yes, the x-y labels16:46
*** SumitNaiksatam has joined #openstack-meeting-316:46
lsmolabradjones: well we can always add something like that to rickshaw :-)16:46
bradjoneslsmola: I think that sounds like a good approach, will look into this16:47
lsmolabradjones: but there was no need for us, as you can display that detail on chart hover16:47
lsmolabradjones: so it says 10%CPU at date xy16:47
lsmolabradjones: e.g.16:47
*** harrisonkelly has joined #openstack-meeting-316:47
bradjonesyup I will continue to look into this thanks all for the clarification16:48
tqtranwhile we're on this subject, anyone know how why we decided on d3 as oppose to other graphing libs like flot?16:48
lsmolabradjones: we are actually using it for timeseries data only, so one axis is always time, the other is title of the chart16:49
tqtranthe zuul gate check jobs are using flot graphs, just curious why we decided to go with d316:49
*** markmcclain has quit IRC16:49
lsmolatqtran: no idea, that came before me, we used rickshaw, because there was already d3 :-)16:50
david-lylethat choice was made back at the Havana summit by the past PTL, but d3 provides more than just graphs16:50
lsmolatqtran: but on the other hand, d3 is very good library for data related charting16:50
david-lylewell maybe the largest sense of graphs16:50
tqtranlsmola: yes agree, but flot is easier to use and has a built in grammar (without requiring richshaw)16:51
lsmoladavid-lyle: yeah there is liek the neutron topology, heat topology, etc.16:51
lsmolatqtran: Attractive JavaScript plotting for jQuery16:51
lsmolatqtran: since we are slowly dropping Jquery, it might not be the best :-)16:52
tqtranlsmola: oh we are?16:52
david-lylebut it does add "Attractive"16:52
lsmolatqtran: yeah there is very slow transformation to angular :-)16:52
david-lyleso there's that reason16:52
tqtranlsmola: but angular uses jquery =P16:53
david-lyletqtran: a subset16:53
lsmolatqtran: it's very slow because there is not enough people :-)16:53
lsmolatqtran: I don't think it does, it has it's own querying16:53
lsmolatqtran: but I am no angular wizard yet :-D so I just think16:54
*** sarob_ has joined #openstack-meeting-316:54
tqtranlsmola: =P16:54
*** harrisonkelly_ has joined #openstack-meeting-316:55
david-lyletqtran: at some point a decision has to be made to make progress, there's no guarantee any decision will stand the test of time or make everyone happy.  If there is a compelling reason to reevaluate, we can. Otherwise, we just thrash.16:55
*** markmcclain has joined #openstack-meeting-316:55
*** emagana has quit IRC16:56
*** amotoki has quit IRC16:56
*** harrisonkelly has quit IRC16:56
*** harrisonkelly_ is now known as harrisonkelly16:56
david-lyleBut that doesn't mean we shouldn't question the decisions16:56
lsmolatqtran: for now we are stuck in d3, cause there is a lot of things implemented in it :-)16:56
*** amotoki has joined #openstack-meeting-316:56
*** emagana has joined #openstack-meeting-316:56
tqtrandavid: yep, that sounds good. last summit, i didnt get a chance to show you some of my slides. i have a couple of ideas that could potentially make life easier if we switch to flot16:56
*** rdopieralski has quit IRC16:57
david-lyleslides!16:57
david-lyle:)16:57
tqtrandavid: hhahahaha16:57
tqtrandavid: and demos too16:57
lsmolatqtran: hehe, I would like to see that :-)16:57
tqtranlsmola: =) ok, i'll put it in the mailing list16:58
lsmolatqtran: I see it is using html 5 canvas vs SVG with d316:58
lsmolatqtran: ok, thanks16:59
tqtranlsmola: its canvas-based, but can also render in svg and even html elements16:59
lsmolatqtran: ah, ok16:59
david-lyleTime's up. Thanks everyone.  Have a great week and do some reviews for your fellow developer.16:59
david-lyle#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Tue Aug 19 17:00:00 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
*** rbertram has left #openstack-meeting-317:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-08-19-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-08-19-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-08-19-16.00.log.html17:00
*** gary-smith has left #openstack-meeting-317:00
*** nlahouti has left #openstack-meeting-317:00
akrivokathanks all, see you next week17:00
jpichThanks everyone17:00
*** jpich has left #openstack-meeting-317:00
bradjonesthanks17:00
*** rajdeep has joined #openstack-meeting-317:00
*** emagana has quit IRC17:01
pballandhello everyone17:01
pballand#startmeeting CongressTeamMeeting17:01
openstackMeeting started Tue Aug 19 17:01:09 2014 UTC and is due to finish in 60 minutes.  The chair is pballand. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
sarob_Morning17:01
*** openstack changes topic to " (Meeting topic: CongressTeamMeeting)"17:01
*** mxu has quit IRC17:01
openstackThe meeting name has been set to 'congressteammeeting'17:01
thinrichsHi all17:01
*** tzumainn has left #openstack-meeting-317:01
*** skn_ has joined #openstack-meeting-317:01
*** johnma has left #openstack-meeting-317:01
*** jgravel has left #openstack-meeting-317:01
*** sew has left #openstack-meeting-317:01
*** akrivoka has left #openstack-meeting-317:01
rajdeephi17:01
*** alexsyip has joined #openstack-meeting-317:01
*** doug-fish has left #openstack-meeting-317:01
pballandItems to discuss today: Alpha release progress, policy summit, open discussion17:02
pballandthinrichs: would you mind starting with an update on the alpha release?17:02
skn_Hi Guys, sorry couldn't make it last week17:02
*** pawels has left #openstack-meeting-317:02
pballandhi skn_, no worries, glad you could make it today17:02
thinrichsSure.17:03
*** eghobo has joined #openstack-meeting-317:03
thinrichsWe're targeting our first release Friday.17:03
*** mtesauro has left #openstack-meeting-317:03
*** apviera has joined #openstack-meeting-317:03
thinrichsThe goal is to have basic monitoring in place and Nova/Neutron datasource drivers.17:03
*** SumitNaiksatam has quit IRC17:03
*** LouisF has joined #openstack-meeting-317:03
skn_Yeah, got pulled into something for a couple of weeks, will resume Congress work from this week17:03
thinrichsAPI support as well.17:03
thinrichsThat is, curl API support.17:03
*** SridharRamaswamy has quit IRC17:04
thinrichsLast Friday we were supposed to be code complete, which we mainly succeeded at.17:04
LouisFis this congress meeting?17:04
thinrichsThis week we're testing, fixing minor things, improving documentation.17:04
*** kudva has joined #openstack-meeting-317:04
thinrichsLouisF: yep17:04
kudvahi17:04
LouisFhi17:04
thinrichsYesterday I had a completely successful API test.17:05
thinrichsSo everything seems to be working as we'd expect.17:05
pballandawesome17:05
thinrichsThe hope is that we'll have all the small code bits merged into master by Thurs morning.17:05
*** ivar-lazzaro has joined #openstack-meeting-317:05
kudvathinrichs: does that mean the tests will run now?17:06
skn_Great stuff, thinrichs!17:06
thinrichsOn Thurs, if everyone could help by testing out the install instructions and the API, that would be great!17:06
thinrichskudva: tests should run with tox -epy2717:06
skn_I'd love to17:06
*** lsmola2 has quit IRC17:06
kudvathinrichs: great! can't wait to get the tests working again...17:07
thinrichsOr ./run_tests.sh but without -N so that it creates a virtual env.17:07
thinrichscongress/README.rst should be up to date.17:07
*** apviera has quit IRC17:07
pballandI’ve been able to run the tests with ./run_tests.sh -N once all of the test dependencies are in17:07
kudvapballand: okay, will try it asap17:07
thinrichspballand: I had an issue where once I installed with devstack then installed test dependencies, my devstack install broke.17:07
thinrichsBut I haven't tried it for a while—I understand there was a bug in infra that I kept hitting.17:08
pballandwe have a couple of ways people are running congress, so the more people we have trying it out and reporting issues/solutions the better17:08
kudvapballand: I am running it without devstack, just clone and install congress from git.17:08
rajdeeptests seems to be working fine17:09
thinrichsThere are just a few outstanding changes in review that need to be merged.17:09
rajdeepi checked our code coverage also it is around 57%17:09
*** apviera has joined #openstack-meeting-317:09
thinrichsrajdeep: what do you mean by 'code coverage', and where did 57% come from?17:09
sarob_57.3%17:09
pballandrajdeep: thanks for doing that - code coverage is somethign we haven’t been tracking so far, but it’s a reasonable time to start doing so17:09
pballandrajdeep: any notable code paths missing coverage?17:10
*** ivar-lazzaro has quit IRC17:10
*** johnthetubaguy is now known as zz_johnthetubagu17:10
*** ivar-lazzaro has joined #openstack-meeting-317:10
rajdeepplexxi code17:10
rajdeepand the runtime17:10
rajdeepare two areas where we could add more tests17:11
thinrichsrajdeep: we're only exposing a fraction of the functionality of runtime in the API.17:11
*** igordcard has joined #openstack-meeting-317:11
pballandrajdeep: ok, no surprises there - we’ve been working on those slowly but surely17:12
sarob_Rajdeep: so where does the number come from?17:12
rajdeepyeah so we need to add unit test cases there17:12
rajdeepyou can run coverage command for tox17:12
rajdeeptox -e cover17:12
*** tqtran has left #openstack-meeting-317:12
sarob_Rajdeep: thx17:12
pballandthinrichs: I think your doc patch went in as well, right?17:13
thinrichspballand: yes—but ayip is making another editing pass.17:13
rajdeepi added a few new tests for webservice17:13
thinrichsApparently there are several large holes I can't see.17:13
pballandgreat!  it would also be great to have more eyes on the docs to help newbies as much as possible17:13
*** jacalcat has quit IRC17:14
Radu_The  new doc's readme for a fresh install seems to be going well. Installing devstack on a new vm now.17:14
thinrichsI'd love to have people try out the install on a bunch of different distros/versions.17:14
thinrichsMaybe it's worth putting a list of the distros we've had success with somewhere in the README.17:15
sarob_Thinrichs: good idea17:15
pballandthinrichs: I like that idea17:15
pballandI have a short list of instructions I follow for ubunu 12.04, so I can add those17:15
rajdeepi checked it on ubuntu 13.1017:16
rajdeepseesm to work fine17:16
*** gokul has joined #openstack-meeting-317:16
pballandrajdeep: thanks for adding the tests - I think they need to be reabased though17:16
rajdeeppballand -- will do that17:16
thinrichsI'll try to send out a reminder on Thur morning to the ML asking people to test the install/API/docs.17:17
pballandrajdeep: actually, nevermind - I refactored the code I was thinking of in test_webservice out :-P17:17
bauzashi Congress team, I'm just reviewing your code but I'm having some concerns about the design you made with WSGI natively, do you plan to work in the future with Pecan or Flask ?17:17
pballandhi bauzas - I can speak to that in a minute17:18
bauzaspballand: sure17:19
pballandthinrichs, rajdeep: any other updates?17:19
thinrichsThat's it for me.17:19
*** keith` has joined #openstack-meeting-317:19
rajdeepi made some changes in README but ran into rebase problems -- need to look into it17:19
rajdeephttps://review.openstack.org/#/c/114896/1/README.rst17:20
pballandkudva: any updates on the builtins?17:20
*** tmazur has quit IRC17:21
pballandin paralle, skn_ - are you still working on your use case?17:21
skn_Hi pballand17:21
skn_Yeah, I have something written up as well as some progress in the code17:22
skn_Where do you guys put the specs?17:22
skn_I'd like to put that in so that you can take a look17:22
kudvapballand: yes, I added code to do syntax checking. It works. need to run the new tests and I'll check in17:22
kudvapballand: I have finished the coding, was having problems running the tests17:23
pballandskn_: https://wiki.openstack.org/wiki/Congress#How_To_Create_a_Blueprint17:23
pballandskn_: we started putting the specs in the code repo, but are trying to get a spec repo done17:23
pballandsarob: can you update us on the specs repo?17:23
sarob_Pballand: sure17:24
*** emagana has joined #openstack-meeting-317:24
pballandkudva: great - are there any particular blockers to discuss here, or is it something to work out over email?17:24
sarob_Pballand: the infra code is finally working17:24
*** markmcclain has quit IRC17:25
sarob_Pballand: I'm working through the req of the specs doc test17:25
*** markmcclain has joined #openstack-meeting-317:25
sarob_Pballand: should be done tomorrow17:25
pballandsarob_: is it fair for people to follow the instructions on the wiki, and you will update it when the new repo is ready?17:26
sarob_Pballand: I'm leaving for linuxcon17:26
skn_pballand: so after we have the spec repo, that's where I should upload, right?17:26
kudvapballand: It's going well. I will check in the syntax checking asap, and then move forward17:26
sarob_Pballand: sure. I'll move when repo is ready17:26
pballandkudva: great, thanks!17:26
*** eghobo has quit IRC17:26
*** eghobo has joined #openstack-meeting-317:27
pballandI want to talk a bit about the policy summit17:27
pballandbauzas: I haven’t forgot about your question17:27
sarob_Shirley17:27
pballand#link https://etherpad.openstack.org/p/juno-midcycle-policy-summit17:27
bauzaspballand: no worries, it's more likely an open question about the level of integration you have17:27
*** ivar-lazzaro has quit IRC17:28
pballandwe’ve been getting some good feedback and signups for the policy summit in Sept17:28
*** apviera has quit IRC17:28
pballandcurrently, the agenda is fairly open17:28
pballandwe have some ideas (there is more than enough to discuss), but want to give the community time to participate in the planning17:29
pballandif there is something in particular people want to discuss, please addi it to the etherpad, so we can discuss17:29
sarob_Mmcclain, mikal should have something on the agenda17:30
pballandwe’ll be calling on community leaders for each section17:30
sarob_I'll work with them over this week to add17:30
pballanddoes that make sense / are there any questions or comments about the summit?17:30
pballand#topic Open Discussion17:31
*** openstack changes topic to "Open Discussion (Meeting topic: CongressTeamMeeting)"17:31
rajdeepwhat is the agenda for day 2 post lunch17:32
skn_sarob/pballand: day 2 is for use cases?17:32
sarob_Skn_ that's correct17:33
pballandskn_: the high level idea was to spend day one getting familiar with various projects policy strategy and goals, and day two would be spent applying what we leared to use cases17:33
skn_Got it!  I am hoping I could do a talk on the security use cases17:33
*** emagana has quit IRC17:34
pballandskn_: that would be great - can you pencil that in under “proposed overviews” on the etherpad?  Then we will schedule it17:35
*** emagana has joined #openstack-meeting-317:35
skn_pballand: Oh ok, great, let me add it now17:35
pballandLouisF: I didn’t get a chane to welcome you to the meeting - are you new to congress?17:35
LouisFpballand: yes, currently in gbp17:36
LouisFpballand: looking forward to sept summit17:37
sarob_Thinrichs, arosen: how's the demo?17:37
skn_pballand: I added this to the proposed overviews, it would make sense for day 2, I guess17:37
sarob_We have slot for next weeks ops summit17:38
thinrichssarob_: there are many details about the alpha release earlier in the meeting notes.  But in short, it's looking good for a Friday release.17:38
pballandsarob_: cool - I’ll be ready to give a demo - how long is the slot?17:38
sarob_40 min17:39
pballandI’ve booked my travel to SA - sarob_ and I will be at the Ops Summit to talk about policy17:39
*** shakamunyi has quit IRC17:39
pballandsarob_: perfect!17:39
sarob_Pballand: good17:39
sarob_Ness17:39
*** emagana has quit IRC17:39
sarob_I'm on the way to linuxcon17:40
sarob_Before ops summit17:40
pballandbauzas: The short answer on the API framework is that the design came from work I’ve done previously, was was done before we started pusing openstack compatibility17:40
sarob_Mestery and other odl people there17:40
bauzaspballand: thanks for your answer17:40
pballandbauzas: we’re currently focused on getting the code where others can pick up congress and integrate policy across openstack projects17:41
sarob_Anything you guys are wanting to ask these guys?17:41
bauzaspballand: by reading your bps, I can't see where you plan to integrate with common Openstack guidelines17:41
*** eghobo has quit IRC17:41
bauzaspballand: on the other hand, I can see you're pretty interested in being incubated one day or later17:41
pballandbauzas: code compatability and reuse is important, but the mechanics of the API are not a focus area right now17:41
pballandfrom a look-and-feel perspective, we definitely aim to follow REST best practices17:42
bauzaspballand: sounds reasonable, but I'm just wondering when you guys plan to work on that17:42
bauzaspballand: I can see you have specs ?17:42
pballandthe implementation can certainly change, but I don’t see it as urgent unless there are problems17:42
thinrichsbauzas: have a pointer to the OS guidelines handy?17:43
bauzasthinrichs: wish I would have :)17:43
bauzasthinrichs: that's mostly coming from other projects readability17:43
pballandbauzas: we’ve started following the specs process, but don’t yet have specs for everything17:43
pballand(still getting the specs repo up :) )17:43
bauzaspballand: ok, so, meaning that we can propose without that ?17:44
thinrichsSo there's no doc describing OS guidelines/best-practices?17:44
pballandbauzas: we have a process for proposing specs, if that’s what you’re asking17:44
pballandbauzas: https://wiki.openstack.org/wiki/Congress#How_To_Create_a_Blueprint17:44
bauzasthinrichs: well, each project has their own rules17:44
sarob_Bauzas I wasn't aware pecan had become a standard17:45
*** emagana has joined #openstack-meeting-317:45
bauzassarob_:  Pecan is not a standard but a good opportunity for starting projects17:45
sarob_Bauzas it's an interesting option for reuse though17:45
*** banix has joined #openstack-meeting-317:45
sarob_Bauzas okay got it17:46
bauzassarob_: it was discussed during Icehouse and Juno summits, and I know that's something that can be considered17:46
bauzasdo you have any design docs in the wiki or elsewhere?17:46
bauzasbecause I can't see if you plan to integrate with a messaging queue or so17:46
*** pballand has left #openstack-meeting-317:46
bauzasI identified you made up the Keystone middleware auth17:47
*** pballand has joined #openstack-meeting-317:47
bauzasbut IIRC, the engine is called thru a python lib ?17:47
thinrichsbauzas: design doc (linked from wiki): https://docs.google.com/a/vmware.com/document/d/1f2xokl9Tc47aV67KEua0PBRz4jsdSDLXth7dYe-jz6Q/edit17:47
pballandsorry, got dropped from the channel for a second..17:47
bauzasthinrichs: awesome, thanks17:47
sarob_Bauzas its important to get critical feedback17:48
pballandbauzas: from the API perspecive, we’ve focused on the consuption aspects17:48
thinrichsbauzas: That design doc is concerned with functionality, not implementation.17:48
bauzaspballand: ok17:48
bauzaspballand: ok, I need to look further and see your API model17:49
pballandthe framework also is designed to keep developers from falling in to the trap of tightly-coupling the API to the application17:49
bauzaspballand: what do you mean ? you still need input validation on the API ?17:49
pballandbauzas: yes, there is a bp for that17:49
bauzaspballand: k17:50
bauzaspballand: got it17:50
*** otherwiseguy has quit IRC17:50
bauzaspballand: ok, thanks for your feedback, greatly appreciated17:50
pballandbauzas: the goal is that those writing to congress don’t have to touch the REST API (they just write to a data-source interface, and their info is exposed by the framework)17:50
pballandthose writing APIs follow a simple model class, and the framework offloads validation, etc for them17:51
bauzaspballand: mmm ok I see what you mean17:51
bauzaspballand: ok, will see what I can do then17:51
pballandand those working in the API framework, have to understand the details - which is where using existing frameworks has advantanges17:51
*** otherwiseguy has joined #openstack-meeting-317:52
bauzasok, will go further17:52
pballandthe api framework is the 3rd tier of interaction (by developer time), however, so that is why it is not the top priority17:52
bauzask thanks17:52
pballandwith that said, we’d be (very) happy to consider blueprints and contributions that bring us closer :)17:53
bauzasJuno-3 is closing :)17:53
thinrichsTime check: 5 min remaining17:54
pballandanything else people want to bring up before we close?17:54
sarob_Opendaylight17:55
sarob_Anything you guys want me to discuss with17:55
skn_What about ODL?17:55
sarob_At linuxcon17:55
pballandsarob: details?17:56
sarob_odl track at linuxcon17:57
*** jpomero has quit IRC17:57
sarob_I'm going to listen mostly17:57
sarob_Anything to discuss from this group?17:58
sarob_Around policy17:58
skn_ODL group policy project working with Congress, you mean17:58
sarob_Along those lines, sure17:59
skn_That's one of the relevant things of interest for Congress, for sure17:59
pballandsarob_: I don’t have anythin in particular to discuss, but it would be good to listen for areas of collaboration17:59
sarob_Ping me on the ML if you think of something17:59
sarob_Yup will do17:59
*** mfer has joined #openstack-meeting-318:00
*** thomasem_ has joined #openstack-meeting-318:00
pballandok, that’s it on time18:00
pballandthanks everyone!18:00
sarob_Thx18:01
skn_Bye everyone18:01
pballand#endmeeting18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
openstackMeeting ended Tue Aug 19 18:01:07 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-08-19-17.01.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-08-19-17.01.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-08-19-17.01.log.html18:01
*** skn_ has quit IRC18:01
*** thinrichs has left #openstack-meeting-318:01
*** gokul has quit IRC18:01
*** thomasem has quit IRC18:01
*** keith` has left #openstack-meeting-318:02
*** jpomero has joined #openstack-meeting-318:02
*** chuckC_ has joined #openstack-meeting-318:02
*** rajdeep has quit IRC18:03
*** sarob_ has quit IRC18:04
*** garyduan has joined #openstack-meeting-318:07
*** lcheng has quit IRC18:07
*** gduan has quit IRC18:08
*** apviera has joined #openstack-meeting-318:10
*** shakamunyi has joined #openstack-meeting-318:11
*** LouisF has quit IRC18:13
*** emagana has quit IRC18:17
*** emagana has joined #openstack-meeting-318:17
*** rudrarug_ has joined #openstack-meeting-318:18
*** banix has quit IRC18:20
*** rudrarugge has quit IRC18:21
*** emagana_ has joined #openstack-meeting-318:21
*** emagana has quit IRC18:21
*** SridharRamaswamy has joined #openstack-meeting-318:24
*** shakamunyi has quit IRC18:30
*** jpomero has quit IRC18:36
*** harrisonkelly has quit IRC18:41
*** shakamunyi has joined #openstack-meeting-318:44
*** harrisonkelly has joined #openstack-meeting-318:46
*** Sukhdev has joined #openstack-meeting-318:48
*** harrisonkelly has left #openstack-meeting-318:49
*** emagana_ has quit IRC18:50
*** david-ly_ has joined #openstack-meeting-318:50
*** stevelle has joined #openstack-meeting-318:50
*** david-lyle has quit IRC18:51
*** SumitNaiksatam has joined #openstack-meeting-318:52
*** emagana has joined #openstack-meeting-318:53
*** terrylhowe has joined #openstack-meeting-318:56
*** briancurtin has joined #openstack-meeting-318:59
briancurtin#startmeeting python-openstacksdk19:00
openstackMeeting started Tue Aug 19 19:00:25 2014 UTC and is due to finish in 60 minutes.  The chair is briancurtin. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: python-openstacksdk)"19:00
openstackThe meeting name has been set to 'python_openstacksdk'19:00
*** apviera has quit IRC19:00
briancurtinif you're here for the python-openstacksdk meeting, say hi19:01
terrylhoweTerry Howe, HP19:01
briancurtinBrian Curtin, Rackspace19:01
*** ultimate has quit IRC19:01
stevelleSteve Lewis, Rackspace19:02
jamielennoxJamie Lennox, Red Hat19:02
*** TravT|2 has joined #openstack-meeting-319:03
*** jpomero has joined #openstack-meeting-319:03
briancurtini don't have a ton to talk about other than thinking about these more complex resources that we're hitting now (that's basically all the agenda has: https://wiki.openstack.org/wiki/Meetings/PythonOpenStackSDK#Agenda_for_2014-08-12_1900_UTC)19:03
briancurtini have started a scratch pad of ideas for updating openstack-dev, but want to have some of these things more fleshed out when we go to ask about people's input on higher level views19:04
terrylhoweI marked that ServerInterface review WIP because I realized I didn’t have any tests19:04
*** TravT has quit IRC19:06
*** Longgeek has quit IRC19:06
terrylhoweServerInterface has the path_args in it19:06
briancurtinterrylhowe: now that we're on to needing extra info like in that ServerInterface change, it feels like it's going to be a hassle to build on top of while targeting a simple command line script19:07
briancurtinbut i guess that's a consequence of the spot we're in19:07
*** asahlin has quit IRC19:07
briancurtineverything works relatively nicely right now running stuff out of the examples dir, which is cool19:08
jamielennoxso what is the complex resource you are hitting and what do we need to solve?19:08
terrylhoweyeh, it is kind of complicated.  It may be better to try it with an Idnetity example19:08
terrylhowehttps://review.openstack.org/#/c/115047/19:08
*** TravT|2 has quit IRC19:08
terrylhoweI put together an implementation and *then* realized I didn’t have it available to functional test19:09
terrylhoweInstead of path_args, maybe there should be some sort of url args or url builder19:10
jamielennoxthe identity one i know is a user and role are top level concepts, but a user has roles ie /user/X/roles/Y and IMO that should be a role object19:10
stevelleI'm beginning to block on similar issues with ceilometer meter samples and alarm history19:11
terrylhoweYeh, I’d have access to that at least19:11
briancurtinterrylhowe: i kind of just wish a lot of this stuff wasn't classmethods. would make some of the url building easier19:13
*** david-ly_ is now known as david-lyle19:13
jamielennoxbriancurtin: we talked about this and it's probably a good idea to make it so19:14
* briancurtin forgot to mention - i need to leave this meeting in roughly 35 min for a doctor appointment19:14
terrylhowestevelle: since most of the oddball ceilomter calls don’t have full crud, maybe they could just be methods of the related resource19:15
briancurtinjamielennox: yeah. maybe i'll take a hack at that next, because i wasn't liking the way i was working with swift objects (after i un-hardcoded a bunch of stuff, hah)19:16
jamielennoxbriancurtin: i was thinking about it, and i don't know how yet but our objects should be just containers for data19:17
*** markmcclain has quit IRC19:17
stevelleterrylhowe:  the properties of samples and alarm are very different from the resources they are nested under, they need to be a different model, trying to make that work.19:17
jamielennoxi don't know if there should be any inbuilt knowledge of how you get that data19:18
terrylhowestevelle: maybe a one off like ServerIP19:18
jamielennoxso in my previous example a Role (something consistent with the format) at any sub-url should be a role object19:18
stevelleterrylhowe: that was the model I was working on today19:19
terrylhowestevelle: that is probably a good approach on those19:20
stevelleterrylhowe: I suspect it will look funny but we can bring it to review19:21
briancurtinjamielennox: yeah i bounce back and forth between containers and having some knowledge. i flip back and forth enough times i think i just need to hack a few different ways instead of thinking so much19:21
jamielennoxbriancurtin: yea, i know exactly what you mean, there is definitely an argument for both19:22
terrylhoweas far as the path_args thing, does anyone have any other ideas on that?  should there be a get_path class method for resources for example?19:22
jamielennoxthe idea was to be kind of sqlalchemy-ish but i don't think the mappings are as 1-to-1 here19:22
*** emagana has quit IRC19:24
*** emagana has joined #openstack-meeting-319:24
*** emagana has quit IRC19:25
terrylhowewell, maybe implementing Role will help with ideas19:25
briancurtinterrylhowe: i dont really have a great suggestion yet. it just feels wrong, but i dont have enough experience working on top of it to say exactly how to change it. kind of a half-assed response19:25
jamielennoxbriancurtin: a part of my concern here is that if we do need a layer above the resource objects, then that's getting close to managers and i've wasted a lot of people's time by advocating away from them19:25
*** dconde has quit IRC19:25
briancurtinjamielennox: i think a potential layer above would mostly solve having to pass in a session to every call, and maybe that's where we bridge together these nested resources. or something19:26
briancurtini imagine it being fairly thin19:26
*** dconde has joined #openstack-meeting-319:27
terrylhoweAs Dean would say, we need a strawman to beat on for that19:28
terrylhoweOnce we have something on that though, it might resemble a real product19:28
*** dtroyer has joined #openstack-meeting-319:29
terrylhowejamielennox: dod you have anything in the works with identity?19:29
jamielennoxterrylhowe: not as yet, i got started last week as you saw but didn't get futher than that19:30
jamielennoxterrylhowe: have been meaning to get back and just keep adding a few a week19:30
terrylhowewell, as long as it is okay with you, maybe I’ll try Role later in the week then19:31
jamielennoxterrylhowe: sure19:31
terrylhowecool19:31
terrylhoweback to higher level stuff, are there any baby steps we can take for that?19:31
briancurtinterrylhowe: i dont know if its a good idea or not, but i kind of want to just write a thin layer for swift and then back it out into something perhaps more generic, and see what it looks like19:33
briancurtinthat'll let me see how to get the container into the object class from that higher level19:33
briancurtinand whatever other niceties we may get out of that higher level view19:34
*** emagana has joined #openstack-meeting-319:34
terrylhowedoesn’t seem like a baby step, but I have no better ideas19:35
*** rockyg has joined #openstack-meeting-319:36
terrylhoweI don’t think it will that bad though19:36
briancurtinfwiw, i'm at the CloudOpen conference this week so i wont have a ton of time, but i'll try to hack a bit19:37
briancurtini have to take off in a few minutes, but does anyone have anything else? sorry for this not being super productive, i guess we just have to try a bunch of stuff and see where it goes19:42
terrylhowenothing here19:42
jamielennoxi'm good19:44
stevellenothing more19:44
briancurtincool, thanks everyone. i'll still keep an eye on reviews while i'm at this conf and try to sneak in some hacking19:44
briancurtin#endmeeting19:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:45
openstackMeeting ended Tue Aug 19 19:45:04 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-08-19-19.00.html19:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-08-19-19.00.txt19:45
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-08-19-19.00.log.html19:45
*** stevelle has left #openstack-meeting-319:45
*** briancurtin has left #openstack-meeting-319:45
*** Radu_ has left #openstack-meeting-319:46
*** dtroyer has left #openstack-meeting-319:47
*** kudva has quit IRC19:49
*** markmcclain has joined #openstack-meeting-319:50
*** asahlin has joined #openstack-meeting-319:50
*** terrylhowe has left #openstack-meeting-319:52
*** jamielennox has left #openstack-meeting-319:54
*** dconde has quit IRC19:56
*** SridharR_ has joined #openstack-meeting-320:04
*** dconde has joined #openstack-meeting-320:05
*** SridharRamaswamy has quit IRC20:06
*** dconde has quit IRC20:06
*** dconde has joined #openstack-meeting-320:07
*** peristeri has quit IRC20:11
*** peristeri has joined #openstack-meeting-320:16
*** MaxV has joined #openstack-meeting-320:23
*** yinzuo has quit IRC20:28
*** peristeri has quit IRC20:29
*** eghobo has joined #openstack-meeting-320:34
*** eghobo has quit IRC20:35
*** emagana has quit IRC20:44
*** Youcef has quit IRC20:44
*** emagana has joined #openstack-meeting-320:45
*** shakamunyi has quit IRC20:46
*** seizadi has joined #openstack-meeting-320:47
*** seizadi1 has quit IRC20:47
*** Sukhdev has quit IRC20:48
*** mestery has joined #openstack-meeting-320:49
*** emagana has quit IRC20:49
*** mestery has quit IRC20:49
*** mestery has joined #openstack-meeting-320:50
*** SridharR_ has quit IRC20:51
*** SridharRamaswamy has joined #openstack-meeting-320:52
*** seizadi1 has joined #openstack-meeting-320:56
*** seizadi has quit IRC20:56
*** jtomasek has quit IRC20:57
*** emagana has joined #openstack-meeting-321:02
*** cbader has joined #openstack-meeting-321:09
*** cbader has quit IRC21:10
*** cbader has joined #openstack-meeting-321:10
*** Sukhdev has joined #openstack-meeting-321:11
*** julim has quit IRC21:11
*** lblanchard has quit IRC21:13
*** thangp has quit IRC21:17
*** mfer has quit IRC21:20
*** celttechie has joined #openstack-meeting-321:34
*** thomasem_ has quit IRC21:34
*** mestery_ has joined #openstack-meeting-321:36
*** mestery has quit IRC21:37
*** mestery_ is now known as mestery21:40
*** emagana has quit IRC21:43
*** emagana has joined #openstack-meeting-321:44
*** mestery has quit IRC21:45
*** mestery has joined #openstack-meeting-321:46
*** emagana_ has joined #openstack-meeting-321:46
*** emagana has quit IRC21:46
*** alexsyip has quit IRC21:59
*** mestery has quit IRC22:01
*** otherwiseguy has quit IRC22:03
*** SridharR_ has joined #openstack-meeting-322:03
*** SridharRamaswamy has quit IRC22:04
*** alexsyip has joined #openstack-meeting-322:04
*** banix has joined #openstack-meeting-322:06
*** rockyg has quit IRC22:06
*** jpomero has quit IRC22:08
*** rcleere has quit IRC22:11
*** seizadi1 has quit IRC22:11
*** MaxV has quit IRC22:12
*** ivar-lazzaro1 has joined #openstack-meeting-322:16
*** HenryG_ has joined #openstack-meeting-322:17
*** banix has quit IRC22:19
*** HenryG has quit IRC22:19
*** banix has joined #openstack-meeting-322:19
*** otherwiseguy has joined #openstack-meeting-322:20
*** banix has quit IRC22:24
*** markmcclain has quit IRC22:26
*** jpomero has joined #openstack-meeting-322:26
*** jpomero has quit IRC22:27
*** jpomero has joined #openstack-meeting-322:28
*** shwetaap has quit IRC22:30
*** SridharR_ has quit IRC22:39
*** mestery has joined #openstack-meeting-322:53
*** dconde has quit IRC22:54
*** cbader has quit IRC22:54
*** SridharRamaswamy has joined #openstack-meeting-322:54
*** shakamunyi has joined #openstack-meeting-323:02
*** mestery_ has joined #openstack-meeting-323:02
*** mestery has quit IRC23:02
*** mestery_ has quit IRC23:07
*** seizadi has joined #openstack-meeting-323:07
*** mestery has joined #openstack-meeting-323:07
*** otherwiseguy has quit IRC23:09
*** otherwiseguy has joined #openstack-meeting-323:09
*** seizadi has quit IRC23:10
*** Sukhdev has quit IRC23:11
*** seizadi has joined #openstack-meeting-323:12
*** mestery has quit IRC23:12
*** mestery has joined #openstack-meeting-323:13
*** seizadi has quit IRC23:13
*** shakamunyi has quit IRC23:18
*** banix has joined #openstack-meeting-323:20
*** emagana_ has quit IRC23:25
*** banix has quit IRC23:25
*** emagana has joined #openstack-meeting-323:25
*** emagana has quit IRC23:27
*** emagana has joined #openstack-meeting-323:28
*** SridharRamaswamy has quit IRC23:30
*** shakamunyi has joined #openstack-meeting-323:33
*** celttechie_ has joined #openstack-meeting-323:34
*** rudrarugge has joined #openstack-meeting-323:34
*** igordcard has quit IRC23:35
*** rudrarug_ has quit IRC23:36
*** celttechie has quit IRC23:36
*** alexsyip has quit IRC23:40
*** SridharRamaswamy has joined #openstack-meeting-323:41
*** SridharRamaswamy has quit IRC23:41
*** mestery has quit IRC23:41
*** SridharRamaswamy has joined #openstack-meeting-323:42
*** HenryG_ is now known as HenryG23:42
*** dconde has joined #openstack-meeting-323:43
*** mestery has joined #openstack-meeting-323:44
*** david-lyle has quit IRC23:44
*** david-lyle has joined #openstack-meeting-323:45
*** david-lyle has quit IRC23:45
*** mestery has quit IRC23:45
*** dconde has quit IRC23:45
*** alexsyip has joined #openstack-meeting-323:53
*** celttechie_ has quit IRC23:53
*** carl_baldwin has quit IRC23:53
*** yamahata has joined #openstack-meeting-323:53
*** zehicle has quit IRC23:55
*** banix has joined #openstack-meeting-323:57

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