Tuesday, 2014-05-27

*** xuhanp has joined #openstack-meeting-300:05
*** HenryG has quit IRC00:11
*** nati_ueno has joined #openstack-meeting-300:12
*** xuhanp has quit IRC00:16
*** kenhui has joined #openstack-meeting-300:16
*** nati_ueno has quit IRC00:17
*** nati_uen_ has joined #openstack-meeting-300:22
*** nati_ue__ has joined #openstack-meeting-300:27
*** banix has quit IRC00:29
*** nati_uen_ has quit IRC00:30
*** nati_ue__ has quit IRC00:32
*** nati_uen_ has joined #openstack-meeting-300:35
*** xuhanp has joined #openstack-meeting-300:36
*** banix has joined #openstack-meeting-300:37
*** nati_uen_ has quit IRC00:39
*** tomoe_ has quit IRC00:47
*** xuhanp has quit IRC00:49
*** nati_uen_ has joined #openstack-meeting-300:52
*** nati_ue__ has joined #openstack-meeting-300:54
*** nati_uen_ has quit IRC00:57
*** nati_ueno has joined #openstack-meeting-300:57
*** nati_ue__ has quit IRC00:59
*** nati_ueno has quit IRC00:59
*** nati_ueno has joined #openstack-meeting-301:00
*** carl_baldwin_m has quit IRC01:03
*** carl_baldwin_m has joined #openstack-meeting-301:03
*** nati_ueno has quit IRC01:04
*** peristeri has quit IRC01:06
*** carl_baldwin_m has quit IRC01:07
*** nati_ueno has joined #openstack-meeting-301:09
*** david-lyle has quit IRC01:30
*** kenhui has quit IRC01:31
*** nati_ueno has quit IRC01:33
*** yamahata has joined #openstack-meeting-301:37
*** nati_ueno has joined #openstack-meeting-302:00
*** persia has quit IRC02:01
*** persia_ has joined #openstack-meeting-302:03
*** persia_ is now known as Guest7785002:04
*** persia has joined #openstack-meeting-302:04
*** persia is now known as Guest997502:04
*** Guest9975 has joined #openstack-meeting-302:04
*** Guest9975 is now known as persia02:04
*** nati_ueno has quit IRC02:10
*** tomoe_ has joined #openstack-meeting-302:12
*** nati_ueno has joined #openstack-meeting-302:19
*** nati_ueno has quit IRC02:25
*** david-lyle has joined #openstack-meeting-302:31
*** nati_ueno has joined #openstack-meeting-302:33
*** david-lyle has quit IRC02:35
*** lcheng_ has joined #openstack-meeting-302:35
*** HenryG has joined #openstack-meeting-302:37
*** kenhui has joined #openstack-meeting-302:59
*** coolsvap|afk is now known as coolsvap03:06
*** kenhui has quit IRC03:08
*** kenhui has joined #openstack-meeting-303:09
*** kenhui has quit IRC03:23
*** yamamoto_ has joined #openstack-meeting-303:27
*** eghobo has joined #openstack-meeting-303:30
*** david-lyle has joined #openstack-meeting-303:32
*** david-lyle has quit IRC03:36
*** david-lyle has joined #openstack-meeting-303:38
*** david-lyle has quit IRC03:43
*** banix has quit IRC04:18
*** david-lyle has joined #openstack-meeting-304:24
*** nati_ueno has quit IRC04:31
*** nati_ueno has joined #openstack-meeting-304:32
*** TravT has joined #openstack-meeting-304:33
*** coolsvap is now known as coolsvap|afk04:54
*** lcheng_ has quit IRC05:01
*** TravT has quit IRC05:33
*** lcheng_ has joined #openstack-meeting-305:43
*** eghobo has quit IRC05:44
*** coolsvap|afk is now known as coolsvap05:50
*** lcheng_ has quit IRC05:52
*** mrunge has joined #openstack-meeting-306:03
*** mrunge has quit IRC06:43
*** jtomasek has joined #openstack-meeting-306:52
*** david-lyle has quit IRC06:54
*** boris-42 has quit IRC07:03
*** boris-42 has joined #openstack-meeting-307:11
*** jtomasek has quit IRC07:15
*** jtomasek has joined #openstack-meeting-307:15
*** jcoufal has joined #openstack-meeting-307:17
*** nati_ueno has quit IRC07:18
*** nati_ueno has joined #openstack-meeting-307:19
*** markmcclain has joined #openstack-meeting-307:23
*** nati_ueno has quit IRC07:23
*** yamamoto_ has quit IRC07:24
*** d0ugal_ has quit IRC07:25
*** jtomasek has quit IRC07:29
*** ttrifonov_zZzz is now known as ttrifonov07:30
*** markmcclain has quit IRC07:35
*** amotoki has joined #openstack-meeting-307:49
*** nati_ueno has joined #openstack-meeting-307:50
*** nati_ueno has quit IRC07:54
*** safchain has joined #openstack-meeting-307:54
*** nacim has joined #openstack-meeting-308:02
*** coolsvap is now known as coolsvap|afk08:34
*** jamielennox is now known as jamielennox|away08:40
*** coolsvap|afk is now known as coolsvap08:45
*** nati_ueno has joined #openstack-meeting-308:50
*** mrunge has joined #openstack-meeting-308:52
*** nati_ueno has quit IRC08:55
*** nelsnelson has joined #openstack-meeting-309:07
*** igordcard has joined #openstack-meeting-309:10
*** jtomasek has joined #openstack-meeting-309:14
*** keshavahp has joined #openstack-meeting-309:20
keshavahpHi09:21
keshavahpHi This is Test in IRC Meeting09:21
*** amotoki has quit IRC09:22
*** ttrifonov is now known as ttrifonov_zZzz09:22
*** sahid has quit IRC09:26
*** ttrifonov_zZzz is now known as ttrifonov09:30
*** ttrifonov is now known as ttrifonov_zZzz09:46
*** nacim has quit IRC09:47
*** gangs-hp has joined #openstack-meeting-309:49
gangs-hpTest IRC connection09:49
*** nati_ueno has joined #openstack-meeting-309:51
*** ttrifonov_zZzz is now known as ttrifonov09:54
*** nati_ueno has quit IRC09:55
*** ttrifonov is now known as ttrifonov_zZzz09:59
*** ttrifonov_zZzz is now known as ttrifonov09:59
*** coolsvap is now known as coolsvap|afk10:00
*** nacim has joined #openstack-meeting-310:01
*** ttrifonov is now known as ttrifonov_zZzz10:02
*** nacim has quit IRC10:03
*** ttrifonov_zZzz is now known as ttrifonov10:03
*** nacim has joined #openstack-meeting-310:04
*** nacim_ has joined #openstack-meeting-310:31
*** nacim has quit IRC10:33
*** tomoe_ has quit IRC10:34
*** keshavahp has quit IRC10:43
*** nati_ueno has joined #openstack-meeting-310:52
*** nati_ueno has quit IRC10:56
*** tomoe_ has joined #openstack-meeting-311:01
*** tomoe_ has joined #openstack-meeting-311:02
*** igordcard has quit IRC11:02
*** gangs-hp has quit IRC11:06
*** tomoe_ has quit IRC11:10
*** safchain has quit IRC11:31
*** safchain has joined #openstack-meeting-311:36
*** yamahata has quit IRC11:36
*** nati_uen_ has joined #openstack-meeting-311:55
*** nati_uen_ has quit IRC11:59
*** ttrifonov is now known as ttrifonov_zZzz12:06
*** mwagner_lap has quit IRC12:08
*** ttrifonov_zZzz is now known as ttrifonov12:10
*** vinay_yadhav has joined #openstack-meeting-312:15
*** vinay_yadhav has quit IRC12:18
*** thomasem has joined #openstack-meeting-312:35
*** yamahata has joined #openstack-meeting-312:42
*** yamahata has quit IRC12:45
*** yamahata has joined #openstack-meeting-312:46
*** jamie_h has joined #openstack-meeting-312:53
*** nati_ueno has joined #openstack-meeting-312:55
*** nati_ueno has quit IRC13:00
*** carl_baldwin_m has joined #openstack-meeting-313:02
*** julim has joined #openstack-meeting-313:05
*** lenrow has joined #openstack-meeting-313:05
*** thomasem has quit IRC13:07
*** jcoufal has quit IRC13:07
*** jcoufal_ has joined #openstack-meeting-313:07
*** carl_baldwin_m has quit IRC13:07
*** carl_baldwin_m has joined #openstack-meeting-313:07
*** xuhanp has joined #openstack-meeting-313:13
*** banix has joined #openstack-meeting-313:14
*** lblanchard has joined #openstack-meeting-313:16
*** thomasem has joined #openstack-meeting-313:17
*** tomoe_ has joined #openstack-meeting-313:21
*** carl_baldwin_m has quit IRC13:22
*** carl_baldwin_m has joined #openstack-meeting-313:22
*** jaypipes has joined #openstack-meeting-313:22
*** carl_baldwin_m has quit IRC13:23
*** kenhui has joined #openstack-meeting-313:27
*** jpomero has quit IRC13:35
*** peristeri has joined #openstack-meeting-313:36
*** sballe_ has joined #openstack-meeting-313:37
*** sballe has quit IRC13:39
*** sballe_ has quit IRC13:42
*** danpb has joined #openstack-meeting-313:42
*** peristeri has quit IRC13:46
*** peristeri has joined #openstack-meeting-313:46
*** cody-somerville has left #openstack-meeting-313:47
*** jcoufal has joined #openstack-meeting-313:49
*** jcoufal_ has quit IRC13:52
*** nati_ueno has joined #openstack-meeting-313:56
*** nati_ueno has quit IRC14:00
*** tomoe_ has quit IRC14:01
*** lcheng_ has joined #openstack-meeting-314:06
*** jpomero has joined #openstack-meeting-314:16
*** ttrifonov is now known as ttrifonov_zZzz14:16
*** dlenrow has joined #openstack-meeting-314:22
*** lcheng_ has quit IRC14:22
*** lcheng_ has joined #openstack-meeting-314:24
*** lenrow has quit IRC14:25
*** busterswt has quit IRC14:28
*** david-lyle has joined #openstack-meeting-314:30
*** otherwiseguy has joined #openstack-meeting-314:36
*** TravT has joined #openstack-meeting-314:39
*** busterswt has joined #openstack-meeting-314:41
*** zul has joined #openstack-meeting-314:45
*** sew has joined #openstack-meeting-314:47
*** gcb has joined #openstack-meeting-314:52
*** apmelton has joined #openstack-meeting-314:55
*** hallyn has joined #openstack-meeting-314:56
*** nati_ueno has joined #openstack-meeting-314:57
*** otherwiseguy has quit IRC14:57
*** vladikr has joined #openstack-meeting-314:57
*** otherwiseguy has joined #openstack-meeting-314:58
*** gcb has quit IRC14:58
*** s1rp__ has joined #openstack-meeting-314:59
*** s1rp__ is now known as s1rp15:00
*** bauzas has joined #openstack-meeting-315:00
danpb#startmeeting libvirt15:01
openstackMeeting started Tue May 27 15:01:01 2014 UTC and is due to finish in 60 minutes.  The chair is danpb. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: libvirt)"15:01
openstackThe meeting name has been set to 'libvirt'15:01
*** jgrimm has joined #openstack-meeting-315:01
lparth_hello15:01
apmeltono/15:01
*** nati_ueno has quit IRC15:01
*** mspreitz has joined #openstack-meeting-315:01
jgrimmo/15:01
*** mspreitz has left #openstack-meeting-315:01
danpbah, great, some people added some agenda items15:01
thomasemo/15:02
*** garyk has joined #openstack-meeting-315:02
*** rkukura has joined #openstack-meeting-315:02
thomasemYeah, wouldn't want crickets chirping, now would we?15:02
sewo/15:02
danpblets be traditional and begin at the beginning15:02
danpb#topic LXC boot from block device15:02
*** openstack changes topic to "LXC boot from block device (Meeting topic: libvirt)"15:02
danpbvladikr: you added this item ....anything you want to say15:02
*** sgordon has joined #openstack-meeting-315:03
vladikrdanpb, thank you for the help with this15:03
vladikrI'm a bit confused with what should actually be done regarding your last comment15:03
s1rpo/15:04
danpbi think that all we need is a bit more description about some of the supported scenarios15:04
vladikron checking the number of partitions in the volume15:04
vladikrand shouldn't we do the same for images, in this case?15:04
danpbie say that the change is only intended to work with the case of an unpartitioned block dev15:04
danpband describe the security considerations inherent in mounting untrusted filesystems15:05
danpbvladikr: yes most of the comments there apply just as well to images15:05
danpbso you're spec is really just going to be describing the status quo15:06
vladikrdanpb, ah, I see, it's not about the actual implementation? they don't expect us to mount the device and look into how many partitions are there?15:06
danpbno, no, definitely not15:06
danpbjust document what scenarios you intend to support with your change15:06
vladikrdanpb, ok :) thanks, I got it.15:07
danpbok cool15:07
*** jpich has joined #openstack-meeting-315:07
danpb#topic IPv6 Guest Configuration15:07
*** openstack changes topic to "IPv6 Guest Configuration (Meeting topic: libvirt)"15:07
danpbthomasem: ^^15:07
thomasemSo, s1rp and myself were messing around with IP configurations in the guest. Pretty much the scenario is the /etc/network/interfaces file is generated for the guest, and then cloud-init uses that.15:08
thomasemWe found that IPv6 was failing to get configured since, when it used an inet6 static configuration in the interfaces file, the upstart job was trying to change the following value via sysctl: net.ipv6.conf.eth0.autoconf=015:09
thomasemit appeared to be the case outlined in this bug: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/964882 from a couple years ago15:09
danpbhmmm, ok, interesting problem15:09
thomasemLibvirt mounts /proc/sys as readonly15:09
thomasemSo, I'm wondering15:10
danpbso the mounting of /proc/sys readonly is mostly considered security-through-obscurity - it only ever really prevented accidental changes15:10
*** terryw has joined #openstack-meeting-315:10
thomasemhmm okay15:10
danpbreal security requried that SELinux/AppArmour prevent the changes, or for user namespaces to be active15:11
s1rpright, so we made a change that just made /proc/sys/net RW, but left everything else RO15:11
thomasemSo, that's what I'm wondering... with the appropriate documentation, could we change that and assume that if you want that security, you'll use namespaces?15:11
thomasembased on the documented way to secure containers :)15:11
*** otherwiseguy has quit IRC15:11
thomasemI found that when I changed the host value, it wasn't reflected in the guest, so the guest seems to have its own set of values, at least in /proc/sys/net.15:12
danpbso the problem is that some stuff in /proc/sys/net is host-global while some stuff is namespace-local15:12
*** akrivoka has joined #openstack-meeting-315:12
thomasemoh15:12
*** carl_baldwin_ has joined #openstack-meeting-315:12
danpbwhen user namespaces are active we'd need to figure out how to allow access - presumably we'd have the chown the files we need to grant acess for15:12
danpbthomasem: oh, hmm, i thought that only the tunables related to network interfaces were made local, but perhaps the kernel does more than i thought15:13
danpbin any case, doing a read-write mount is easy enough in libvirt for the non-userns case15:14
thomasemdanpb: I didn't test thoroughly, or anything, I just know that the value it was trying to set when configuring IPv6 wasn't the shared between host and guest.15:14
thomasems/the//15:14
danpbwe'll need to check what we can do in the user-namespace case  - hopefully chown would work15:14
danpbthis is probably something we should just take to the upstream libvirt mailing list, since i think any fix belongs in the libvirt layer15:15
thomasemagreed15:15
thomasemI'll do that15:15
hallynand any place where chown does not suffice might require kernel fix (i.e. s/capable/ns_capable in sysctl handler)15:15
danpbhallyn: yep, good point15:16
thomasem+115:17
thomasemOkay, I'll write up an e-mail when I get a chance with some gists and what-not to help the discussion and fire off to the libvirt upstream ML15:17
danpbok, great15:17
*** rkukura has left #openstack-meeting-315:17
danpb#topic Config drive with LXC15:18
*** openstack changes topic to "Config drive with LXC (Meeting topic: libvirt)"15:18
s1rpyeah, so we want to be able to pass info into the guests, just like the hypervisor case15:18
danpbyep, use case totally makes sense15:18
s1rpseems like there are two possible approaches, blockstyle and fs-style15:18
s1rpi've already done fs-style, using a plain-old directory that gets bind mounted15:19
s1rpbut for the upstream patch, i'm thinking that block-style would be more 'harmonious' with the other hypervisors15:19
s1rpsince it doesn't introduce another config-drive backend15:19
danpbhmmm, i could see that fs-style is more convenient for containers though15:19
s1rpit really is15:19
s1rpand it's a very small patch15:19
danpbbecause if your container image is a single app binary that is launched as init15:20
*** directxman12 has joined #openstack-meeting-315:20
danpbthen you don't need to worry about having a shell wrapper script to mount the config drive and so forth15:20
danpbopenstack just takes care of making it immediately accessible to the app15:20
danpbFWIW,  a FS style approach is not totally unreasonable for hypervisors too15:21
*** sew has quit IRC15:21
danpbKVM has 9p filesystem passthrough from the host, and vmware has a shared filesystem capability too15:21
thomasems1rp: Maybe we should toss that patch upstream and see where it goes?15:21
danpbso I think it is pretty reasonable for openstack to support both FS-style and block-style config drives15:22
s1rpdanpb: good poiints15:22
s1rpthomasem: yeah, can do15:22
s1rpi can toss up the patch, wonder if i need to retroactively create a spec15:22
danpbi think FS style approach would probably appeal to docker people too15:22
s1rpit's so simple, i hope not15:22
thomasemIt's like 3 lines of code, lol.15:22
thomasempretty awesome, imo.15:22
danpbi think you do need to have a spec15:23
*** sew has joined #openstack-meeting-315:23
danpbif only to let us bikeshed about the "best" mount point for the config drive15:23
*** lblanchard has quit IRC15:23
*** sew has quit IRC15:23
thomasemHaha, well by default cloud-init looks in /var/lib/cloud/seed/config_drive15:23
danpband to allow us to explain why it is conceptually useful for multiple hypervisors, even if we don't intend to implement fs-approach for others15:23
s1rpyeah have it hard coded to config-drive's preferred dest, but could make it configurable15:24
danpbthomasem: ah, well that's something to say in the spec :-)15:24
s1rpwith cloud-init the option's default15:24
*** sew has joined #openstack-meeting-315:24
thomasemdefinitely15:24
thomasemcool cool, s1rp, I'll work with you on that15:25
danpbgood, sounds like a plan15:26
danpb#topic Any other business ?15:26
*** openstack changes topic to "Any other business ? (Meeting topic: libvirt)"15:26
danpb....we're out of agenda items now... so speak up if you've anything else to add15:26
s1rpso remove-fakelibvirt turned out to be pretty contraversial15:26
s1rpbusy at the moment, so holding off for a bit, hope to get to it later in the cycle15:27
danpblol, yeah15:27
danpbit isn't really blocking anything on critical path, so no particular rush15:27
s1rpyeah exactly, just sort of a nice-to-have15:27
s1rpbut johannes had a good point about trying to figure out what's expected across hypervisors testing-wise15:28
s1rpright not it's very ad hoc, some integration tests, some unit, etc15:28
thomasemHow're they going to figure that out?15:28
thomasemor we, rather... not sure what all's involved there. :)15:28
danpbyeah, its kind of fuzzy15:29
s1rpguessing we just need a ML thread to hash it out15:29
thomasemGotcha15:29
danpbi was always rather under the impression that its primarily unit testing15:29
s1rpso i think it's mostly integration tests under the guise of unit-tests15:29
danpbbut that we need the real libvirt module around, so we can access module constants & the like15:29
s1rpi think we have very few true unit-tests15:29
s1rpbut that's a whole can-of-worms :)15:29
*** abramley has joined #openstack-meeting-315:30
*** emagana has joined #openstack-meeting-315:30
danpbs1rp: the stuff in nova/tests/virt/libvirt  isn't actually making changes against the real hypervisors though is it ?15:30
thomasemYeah...15:30
apmeltons1rp: true unit tests turn out to have tons of @patch's in nova >_>15:30
thomasemLol! Boy, do they.15:30
danpbi mean it might connect to the hypervisor, but its stubbing out the real interesting APIs to avoid hitting the host15:30
*** directxman12 has quit IRC15:30
*** lenrow has joined #openstack-meeting-315:30
s1rpdanpb: yeah, we're not hitting the real hypervisor, but we're making very high-level calls and then asserting stuff at a very low-level (via fakelibvirt or fakexenapi), so we're testing multiple 'units'15:31
danpbok, right, i see what you mean15:31
danpbi guess i was still thinking of that as unit testing but I see why you might call it integration testing15:32
*** sew has quit IRC15:32
s1rpyeah consistent terminology is probably half-the-battle15:32
s1rpso many of the discussions about this, we end up talking past each other15:33
danpbyeah, i can imagine15:33
*** dlenrow has quit IRC15:33
danpbanyhow, I guess we can end this meeting now15:34
*** kenhui has quit IRC15:34
danpbthanks to all for coming, see you same time / place next week15:34
apmeltono/15:34
vladikrthanks15:34
thomasemThanks! o/15:34
lparth_thanks15:34
*** thomasem has left #openstack-meeting-315:34
danpb#endmeeting15:34
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:34
openstackMeeting ended Tue May 27 15:34:58 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-05-27-15.01.html15:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-05-27-15.01.txt15:35
openstackLog:            http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-05-27-15.01.log.html15:35
s1rpthanks all!15:35
*** lparth_ has left #openstack-meeting-315:36
*** hallyn has left #openstack-meeting-315:36
*** lblanchard has joined #openstack-meeting-315:37
*** sgordon has left #openstack-meeting-315:38
*** jgrimm has quit IRC15:39
*** sew has joined #openstack-meeting-315:40
*** sew has quit IRC15:41
*** ericpeterson has joined #openstack-meeting-315:41
*** sew has joined #openstack-meeting-315:41
*** eghobo has joined #openstack-meeting-315:43
*** nlahouti_ has joined #openstack-meeting-315:47
*** xuhanp has quit IRC15:49
*** jgrimm has joined #openstack-meeting-315:52
*** zul has left #openstack-meeting-315:55
*** shakamunyi has joined #openstack-meeting-315:56
*** xuhanp has joined #openstack-meeting-315:57
*** santib has joined #openstack-meeting-315:57
*** devlaps has joined #openstack-meeting-315:58
*** tqtran has joined #openstack-meeting-315:58
*** vladikr has left #openstack-meeting-315:58
*** apmelton has left #openstack-meeting-315:58
*** doug-fish has joined #openstack-meeting-315:58
*** alexpilotti has joined #openstack-meeting-315:59
*** tzumainn has joined #openstack-meeting-315:59
*** gary-smith has joined #openstack-meeting-315:59
david-lyle#startmeeting Horizon15:59
openstackMeeting started Tue May 27 15:59:55 2014 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.15:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:59
*** openstack changes topic to " (Meeting topic: Horizon)"15:59
openstackThe meeting name has been set to 'horizon'15:59
david-lyleHello everyone!16:00
lsmolahello16:00
gary-smithhi16:00
akrivokahi everyone16:00
jcoufalo/16:00
devlapshi all!16:00
doug-fishhello!16:00
jpichHello16:00
santibhi all16:00
jristwhat do we call many Horizon-ers16:00
jristhorizonites?16:00
jristo/16:00
*** jthopkin has joined #openstack-meeting-316:00
jristhorizonizers16:00
jristhorizinians16:00
jtomasekhi16:01
*** xuhanp has quit IRC16:01
tzumainnhiya!16:01
*** johnma has joined #openstack-meeting-316:01
david-lyleWe'll we've almost hit Juno-1, surprise16:01
david-lyleJune 12 is the date for Juno-116:02
david-lylefirst one always sneaks up on me16:02
david-lylehttps://launchpad.net/horizon/+milestone/juno-116:02
*** clu_ has joined #openstack-meeting-316:02
jcoufaldoug-fish: that was fast16:02
jcoufaldoug-fish: sorry :)16:02
david-lyleis not cleaned up yet and I have to put together 2 and 316:02
david-lylewill work on that this week16:02
david-lyleanyway, just a heads up on that16:03
*** vkmc has joined #openstack-meeting-316:03
david-lyleSecond general item, I attended the TC meeting last week and we discussed the integration gap analysis for Horizon16:03
david-lylehttps://etherpad.openstack.org/p/horizon-gap-analysis16:04
david-lyleThis is a process to make sure that Horizon meets the current criteria for exiting incubation to become part of openstack, so that new projects are not being asked to achieve something above and beyond what integrated projects have done16:05
david-lyleWe have just a few issues to address16:05
david-lylethe first and most glaring is a mission statement16:05
david-lyleWe do UI   wasn't enough16:05
doug-fishlol16:06
jcoufallol16:06
jcoufalnice :)16:06
david-lyleSo I'm putting together a plan to address the rest of the short-comings and will present that to the TC today16:06
jrist"A unified user interface that exposes most of the OpenStack infrastructure to users and operators"?16:06
lsmoladavid-lyle: I would say it was enough :-D16:07
jcoufaljrist: where is that?16:07
jristjcoufal: I just made it up16:07
jristshould I add a TM ?16:07
jrist:)16:07
lsmolajrist: you forgot graphical16:07
jristlsmola: or I purposefully omitted it!16:08
lsmolajrist: user interface can be also like command line, bananas, etc.16:08
jcoufaljrist: why OpenStack infrastructure?16:08
tzumainn"bananas"?16:08
lsmolatzumainn: you know, for monkeys..16:08
jristjcoufal: what is another way to put it16:08
david-lyleTo provide an extensible unified web based user interface for all integrated OpenStack services.16:08
jristdavid-lyle++16:08
ericpetersonyep, remove infrastructure16:08
david-lylewas my attempt16:08
jcoufaldavid-lyle: +116:08
doug-fishyeah that's us  +116:09
jtomasek+116:09
lsmoladavid-lyle: sounds good16:09
david-lyleextensibility is a core value of Horizon and should be in there16:09
jpich+1 to to a mission statement that includes supporting integrated projects and extensibility as goals16:09
santibdavid-lyle: +116:09
david-lylejpich: should there be more?16:09
tqtranim thinking something along of the line of managing stuff....16:10
david-lyleI think quality and usability should be implied from the core values16:10
jrist+116:10
jristagreed to that16:10
*** jamie_h has quit IRC16:10
david-lylenot explicitly stated16:10
ericpetersoncould add the tagline :  now with 20% more quality ?16:10
jcoufaldavid-lyle: that sounds reasonable16:10
*** crobertsrh has joined #openstack-meeting-316:10
david-lyle20% seems high16:10
david-lylemaybe 12.5%16:11
jpichdavid-lyle: Your proposal sounds good to me16:11
jristNow with approximately 12% more quality!16:11
doug-fishnow with nearly 20% more quality16:11
*** sew has quit IRC16:11
ericpetersonfloating point -    11.9999999999%16:11
jpichIs it a pain to tweak / update the mission statement if we find the Perfect Way To Phrase It later?16:11
tqtranlol !!! +1 doug16:11
david-lylejpich: I don't believe so, it just lives in https://github.com/openstack/governance/blob/master/reference/programs.yaml16:12
jristoh man16:12
lsmolalol16:12
david-lyleso a patch and vote by TC is all it takes16:12
*** danpb has left #openstack-meeting-316:13
* doug-fish is way off track testing out mission statement generators.16:13
* david-lyle fearful of results16:13
jpichdavid-lyle: Ok thank you16:13
doug-fish"To enthusiastically supply viral methods to allow us to continue to competently integrate graphical interface materials while maintaining the highest standards."  (slightly edited)16:13
david-lyleother items were around integration testing and the upcoming repo split16:14
*** nati_ueno has joined #openstack-meeting-316:14
david-lyleno real red flags just questions about timelines and goals16:14
doug-fishdavid-lyle - is integration testing a new topic, or part of the TC needs?16:14
david-lylefor projects integrating it is a graduation requirement to have tempest integration16:15
david-lylewe have 1 test16:15
david-lylenot a banner effort16:15
ericpetersonI found an issue to consider around repo split...   the APIBaseResource type classes..... might want to consider moving those into a horizon location ?????16:15
lsmoladoug-fish: I miss like web>2.0, drag & drop and look & feel in that statement :-)16:15
*** jgravel has joined #openstack-meeting-316:15
doug-fish:-)  Drag & Drop present accessibility challenges.  I left it out on purpose!16:16
jcoufallsmola: and nicely colored unicorns :)16:17
lsmolaoh yeah and those16:17
doug-fishdavid-lyle - I talked with ... the PTL for Tempest (name?) ... about UI integration testing at the summit.  It seems that it is explicitly kept very light in tempest because its hard to coordinate intentional changes to the UI with changes to the tests.  I know the test architecture jpich has started on helps with that16:17
*** amotoki has joined #openstack-meeting-316:17
jpichYup, the page object pattern with separate pages and tests should take care of that. dkorn should get the credit :)16:18
doug-fishwell thought out dkorn!16:18
jpichMore exciting reading on the page object pattern: https://wiki.openstack.org/wiki/Horizon/Testing/UI#Page_Object_Pattern_.28Selected_Approach.2916:18
david-lyleI didn't have any more general items16:19
david-lyle#topic Open Discussion16:19
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"16:19
doug-fishI'm on integrations tests still - is it required that we keep our integration tests in tempest?16:20
david-lyledoug-fish: no16:20
nlahouti_how can we find a horizon BP is approved for juno-1?16:20
david-lylenlahouti_: link?16:21
jpichdoug-fish: It'd be a nice end goal but we're starting them in our own repo till we figure it all out and see if it makes sense to merge them back into Tempest16:21
nlahouti_david-lyle: link to BP?16:21
david-lyleyes, please16:21
doug-fishI'd suggest keeping the tests in our project if we can then.  its not hard to image we'll have refactors that change the page a particular function should be performed on16:21
nlahouti_david-lyle: https://blueprints.launchpad.net/horizon/+spec/horizon-cisco-dfa-support16:21
clu_is there a way to test if the layout "looks" right - like if there is text overflowing out of a div, or something...16:22
ericpetersontqtran and I have some ajax table stuff to share: https://blueprints.launchpad.net/horizon/+spec/table-client-rendering   too16:22
doug-fish clu_:  do you mean as part of the integration test?16:23
clu_yes16:23
doug-fishno16:23
doug-fishI don't know of a framework that does that sort of testing in an automated basis -- do you know of one?16:23
tqtranclu_: i think it will be hard to test those kind of stuff, human eye?16:24
jpichdoug-fish: Most projects have their tests in Tempest, it'd give us the advantage that they'd be automatically part of every project's gate so breaking changes would be caught before they get to us. Though once we have a stable integration gate we could also see if it can be run for the other projects but that'll be later either way16:24
clu_doug-fish, tqtran: don't know any framework like that... only the "human eye" test16:24
doug-fishjpich - right.  I understand we need the UI driven integration tests to gate the other projects one day.  I just doing think UI tests seem very much like the other tempest stuff - which is very stable/API driven.16:25
doug-fishs/I just doing think UI tests seem/I just doing think UI tests doesn't seem16:25
doug-fishwow16:25
doug-fishcan't type today anymore can I16:26
tqtranlol16:26
doug-fishUI != API16:26
jpichdoug-fish: I suspect these tests are not as stable as one might expect :-) but yeah I get your point, we can rediscuss later either way, it's very much "future" discussion16:26
doug-fishjpich - agreed this is a future discussion.  I'd rather get some written first then decide what to do with them16:27
jcoufalOne quick announcement: Next week on Monday (June 2) there is going to be the first UX meeting at 1700 UTC (#openstack-meeting-3). Everybody is welcome and if you plan to join, please, fill yourself into this etheprad: https://etherpad.openstack.org/p/ux-meetings so we can arrange meeting times for the most convenient time slot for everyone.16:27
jpichdoug-fish: Yup!16:27
david-lylenlahouti_: so re: your bp, I'm trying to get a better handle on how we can effectively support 3rd party extensions, the current model of a flag per setting/device is not scalable16:28
jpichWoohoo UX meetings \o/ I can't make the first one but hope to attend in the future, thanks for setting these up jcoufal16:28
*** jackib has joined #openstack-meeting-316:28
amotokijpich: doug-fish: in the neutron summit session there is a siimlar discussion about having functional tests in its own repo for better testing coverage.16:28
amotoki imo cross-project testing requiring API calls to backend projects (nvoa, cinder, ..) is better to be in tempest.16:29
clu_jcoufal: nice!16:29
david-lylethe benefit of Horizon tests is exercising the python-*clients so they don't break us and heat as they change16:29
nlahouti_david-lyle: I replied to comments in the review. For instance for avoiding the flag... There is existing api (list_extensions()) that can be used instead of flag16:30
david-lylenlahouti_: that's new in Juno?16:30
nlahouti_david-lyle: The API exists in api/neutron.py16:30
david-lyledoes neutronclient support it?16:31
nlahouti_david-lyle: yes.16:31
nlahouti_david-lyle: Basically it returns all the supported exstension.16:31
david-lylenlahouti_: that is a much better way to approach the problem. We should be triggering off that16:31
jpichamotoki: I agree, and I think people get annoyed when Horizon requires yet again Special Snowflake treatment, but either way we can revisit the conversation when we have a stable and stronger suite of integration tests actually implemented16:31
nlahouti_david-lyle: I think security group using it If I'm not mistaken.16:31
*** jcoufal has quit IRC16:32
nlahouti_david-lyle: But again, using the list_extension API we still need to have if...else in the code in workflow, forms... to display a vendor specific options in the GUI16:32
amotokijpich: agree. (i am catching up with the meeting log now)16:33
david-lylenlahouti_: let's use that in your patch rather than the settings flag, and I think we'll have a workable solution16:33
jpichamotoki: No worries! Your input from a consistency-across-projects perspective is definitely appreciated :)16:33
*** lsmola2 has joined #openstack-meeting-316:33
david-lyleericpeterson: you had a table on the table?16:34
nlahouti_david-lyle: Ok, I'll update the patch based on this solution and post it for review.16:34
*** bauzas has left #openstack-meeting-316:34
ericpetersonyep... tqtran and I have a method to add json versions of data tables16:34
ericpetersonhttps://review.openstack.org/#/c/94706/6/openstack_dashboard/dashboards/project/instances/views.py   see line 50  for how to plug this into a view16:34
amotokidavid-lyle: nlahouti_: related to cisco DFA bp, the correponsing neturon feature is proposed for juno too and not implemented yet.16:34
amotokidavid-lyle: nlahouti_: is it better to wait horizon patch unitl neutron feature is implemented?16:35
david-lyleamotoki: that would change things :)16:35
nlahouti_amotoki: what feature?16:35
*** mwagner_lap has joined #openstack-meeting-316:35
amotokinlahouti_: i think DFA feature is not implemeted yet. am i wrong?16:36
amotokinlahouti_:  *in neutron16:36
ericpetersonand that table mixin.... adds the ability to get a json-ified table   via https://review.openstack.org/#/c/94706/6/horizon/tables/views.py .   this stuff is WIP very clearly.... but am wondering the interest level of the more web 2.0 version of table rendering16:36
*** terryw is now known as otherwiseguy16:36
david-lyleOSAPIJSONEncoder not the best camel case name :)16:36
nlahouti_amotoki: Yes. It is not implemented. But what I'm referring to is the list_extensions() in neutron API which exist today.16:36
ericpetersonyeah, tqtran and I really like capital letters16:37
david-lylenlahouti_: the concern is turning on support for a feature in Horizon, cfa that is not yet supported in neutron16:37
david-lylefor many reasons, it may change, it may not make it, it may make it in K16:38
amotokinlahouti_: ok... what i have in my mind is a feature depedency between hroizon and backend project. horizon team needs to consider merge timing even if the bp is approved.16:38
david-lylethat leaves broken/dead code in Horizon16:38
nlahouti_david-lyle: It won't cause any issue as  the extensions does not return the dfa.16:38
david-lylewhich we're not excited to bring in16:38
jpichI agree with amotoki and david-lyle, in general it's better to wait for the Neutron (or whatever project's) code to be merged before the Neutron feature is implemented. At least make sure to mark the Horizon code as Work In Progress16:38
david-lylenlahouti_: but it's code you can't exercise16:38
doug-fishnlahouti_  dead code creates issues16:38
nlahouti_david-lyle: so code is not gtting exercise.16:39
david-lyleand thus not necessary until neutron integrates16:39
nlahouti_david-lyle: only the if ... statement is executed.16:39
jpichnlahouti_: and the Neutron implementation may change before it gets merged making the horizon part broken16:39
doug-fishdead code creates extra work for translators, unnecessary work for reviews, and confusion among new developers16:39
david-lylenlahouti_: we will not merge before neutron does16:39
*** kenhui has joined #openstack-meeting-316:39
david-lyleend of story16:39
*** jtomasek has quit IRC16:39
*** lsmola3 has joined #openstack-meeting-316:40
jpichlsmola is multiplying...16:40
nlahouti_david-lyle: so first the feature has to be implemented in neutron?16:40
david-lyleyes16:40
amotokinlahouti_: of course it is no problem that horizon patch is upload for review even before merging neutron feature (in parallel). we are just talking about the merge timing. no worries.16:41
david-lyleyes the patch can progress, just not merge16:41
amotokibut we need to have a clear criteria to merge features into hoirzon repo.16:41
lsmola3jpich, hehe16:41
doug-fishlike a working integration test!16:41
david-lyleericpeterson, how are actions handled with the client side rendering?16:42
*** lsmola2 has quit IRC16:42
*** nacim_ has quit IRC16:42
david-lyledo action classes in the table view need to be rewritten, or used as is?16:42
nlahouti_david-lyle: david-lyle, amotoki: yes it is merge timing. In my case the feautre in neutron is related to changes in horizon and they are related together.16:42
*** safchain has quit IRC16:42
david-lylenlahouti_: neutron does not depend on Horizon16:42
ericpetersonI am working on the actions right now..... those should get encoded to json as well..... so you will have something like actions : [  {type: link, href: 'http://..."}   ]16:43
ericpetersonso actions will be in the json.... and those will be at both the table level and the row level..... just like what we have right now16:43
david-lyleand where does allowed come into play, whether it gets added to the JSON to ship to the client16:43
david-lyle?16:43
ericpetersonthose get eval'd on the server16:43
ericpetersontable.get_row_actions(datum)16:44
nlahouti_david-lyle: I understand. I wasn't clear. I was refering the whole solution.16:44
ericpetersonI think that should do that for me16:44
nlahouti_david-lyle: anyhow, I'll update the patch to get comment on the implementaion. not to use flag ...16:45
*** lsmola3 has quit IRC16:45
ericpetersonthe approach with the json stuff is the continue using the horzion table classes / constructs..... and have a quick switch to add, to add the json version of your table16:45
david-lylenlahouti_: I understand, let's keep iterating on the patch in Horizon get it ready to merge, once the feature support goes into neutron the horizon patch can quickly follow16:45
*** lsmola2 has joined #openstack-meeting-316:45
ericpetersonand stuff should continue to work in the same way16:46
nlahouti_david-lyle: Sure.16:46
nlahouti_david-lyle: will do that.16:46
*** sjcazzol has joined #openstack-meeting-316:46
tqtranyep, its basically an alternative way to render your table data.16:46
*** beyounn_1 has joined #openstack-meeting-316:46
david-lyleericpeterson, I need to take a closer look, but I think the idea seems sound16:47
*** vinay_yadhav has joined #openstack-meeting-316:47
tqtranit will work alongside the current implementation nicely16:47
ericpetersonthere is some cross repo dependency stuff like we have a horizon/tables/ import of openstack_dashboard/api stuff..... that is wonky.... which is why I brought that up with repo split16:48
david-lylethat is very wonky16:48
lsmola2:-016:49
ericpetersonthat json encoder thing needs to know if it is dealing with an APIBaseResource type class, that's why16:49
david-lylethe APIBaseResources are particular to the implementation (openstack_dashboard) and don't belong in the toolkit side16:49
ericpetersonyeah.... I could move that jsonecoder code out to the openstack_dashboard section then..... and have a base implementation to override16:50
david-lyleUnfortunately, I have to end 10 minutes early today due to a conflict, please carry on in #openstack-horizon  See everyone next week!16:51
david-lyle#endmeeting16:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:51
openstackMeeting ended Tue May 27 16:51:24 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-05-27-15.59.html16:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-05-27-15.59.txt16:51
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-05-27-15.59.log.html16:51
*** ericpeterson has left #openstack-meeting-316:51
tzumainnthanks all!16:51
jpichYay to short meetings, thanks everyone!16:51
jristo/16:51
jpich*shorter16:51
*** johnma has left #openstack-meeting-316:51
*** david-lyle has quit IRC16:51
*** gary-smith has left #openstack-meeting-316:51
*** tzumainn has left #openstack-meeting-316:52
lsmola2thanks, goodbye16:52
*** david-lyle has joined #openstack-meeting-316:52
*** david-lyle has quit IRC16:52
lblanchardthanks all!16:53
santibthanks16:53
*** santib has left #openstack-meeting-316:53
*** nati_ueno has quit IRC16:53
akrivokabye16:54
*** jgravel has left #openstack-meeting-316:54
*** lsmola2 has quit IRC16:54
*** SumitNaiksatam has quit IRC16:54
*** akrivoka has quit IRC16:54
*** jpich has left #openstack-meeting-316:54
*** doug-fish has left #openstack-meeting-316:55
*** yamahata has quit IRC16:55
*** jackib has quit IRC16:55
*** nati_ueno has joined #openstack-meeting-316:56
*** rajdeep has joined #openstack-meeting-316:58
*** thinrichs has joined #openstack-meeting-316:59
thinrichsHi all.  Anyone here for Congress?17:01
*** tqtran has left #openstack-meeting-317:01
thinrichsAlso making sure I have the right room, unlike last week.17:01
rajdeephi17:01
*** iben has joined #openstack-meeting-317:01
thinrichsHi rajdeep17:01
banixhi17:01
thinrichsHi banix—good to “see” you here.17:01
rajdeepi guess this is the one17:01
*** skn_ has joined #openstack-meeting-317:02
*** pballand has joined #openstack-meeting-317:02
banixthinrichs: thanks. I will be a bit slow catching up :)17:02
sjcazzolhi17:02
thinrichsbanix: no worries—we’ll do what we can to help.17:02
pballandsorry I’m late17:02
thinrichssjcazzol: hi—glad you could make it.17:02
skn_thinrichs: were you able to see my name/id?17:03
ibenthis is the congress meeting, right?17:03
thinrichsiben: yes—this is congress.17:03
thinrichsskn_: not yet.17:03
*** mspreitz has joined #openstack-meeting-317:03
thinrichsLet’s get this started officially.17:03
thinrichs#startmeeting CongressTeamMeeting17:03
openstackMeeting started Tue May 27 17:03:25 2014 UTC and is due to finish in 60 minutes.  The chair is thinrichs. Information about MeetBot at http://wiki.debian.org/MeetBot.17:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:03
*** openstack changes topic to " (Meeting topic: CongressTeamMeeting)"17:03
openstackThe meeting name has been set to 'congressteammeeting'17:03
skn_Its weird.  I used launchpad to create the id17:03
*** vinay_yadhav has quit IRC17:04
thinrichsskn_: I don’t know how to get your name to show up on review.openstack as a potential reviewer.17:04
thinrichsIf anyone knows a quick-fix, let us know.  Otherwise we’ll do that offline.17:04
skn_Yup.  Let me know too.17:04
thinrichsLet’s do our usual thing of going over action items from last week, briefly.17:05
thinrichssarob: are you here?17:05
ibenhe's not signed on now17:05
thinrichsHmm.. doesn’t look like it.  Let’s hope he joins later.17:05
thinrichsWe had a couple of new use cases that were supposed to go up on the wiki.17:05
thinrichsskn_: how’d you do with yours?17:06
skn_I have some write up, but I’ll have to first figure out out where to put17:06
banixis there a link?17:06
skn_where to put it, i mean17:06
thinrichshttps://wiki.openstack.org/wiki/Congress#Use_Cases17:07
skn_Oh ok17:07
thinrichsWe have a list with brief descriptions at the URL.17:07
banixthinrichs: thanks17:07
skn_But these are like one liners17:07
thinrichsbanix (and all other newcomers): the wiki *should* have links to all the resources.  So that’s the one-stop shop.17:07
skn_I thought we’d have a lil more descriptive17:07
thinrichsskn_: We don’t yet have a doc with longer descriptions.  Want to start one?17:08
skn_HI banix, what’s your name?17:08
skn_I think so, we should have a doc17:08
banixMohammad Banikazemi17:08
banixskn_: Hi ^^^17:08
*** sarob has joined #openstack-meeting-317:09
thinrichsskn: sounds good.  Can we use your writeup to seed that doc?17:09
thinrichspballand: where should we host the doc?17:09
skn_Yes, I will17:09
pballandthinrichs: doc for use cases?17:09
skn_Hi Mohammad.  Are you from IBM, who presented the neutron group policy?17:09
thinrichspballand: yes17:09
banixwe use google docs17:10
banixskn_: Yes that’s me :)17:10
pballandI’d go with google docs, or in the repo17:10
*** sarob_ has joined #openstack-meeting-317:10
sarob_Halo17:10
skn_Oh, cool.  This is Susanta from Symantec.  We chatted a lil bit after your talk at OpenStack, remember?17:10
skn_Hey sarob17:10
pballandif we don’t expct many comments, checking them in near the specs sounds good to me17:10
sarob_Yup17:11
thinrichssarob: glad you could make it.17:11
banixskn_: Ahhh yes. great to see you here :)17:11
skn_Good to see all you guys made it today17:11
thinrichssarob: we were just discussing the use case writeups we talked about last week.17:11
sarob_Board stuff bleeding over17:11
thinrichssarob: We’re going to either put them in the repo or on a google doc.  Sound good?17:11
sarob_Got it17:12
*** crobertsrh has left #openstack-meeting-317:12
sarob_Yup17:12
skn_So we create a google doc for the use cases and put it where?17:12
*** igordcard has joined #openstack-meeting-317:12
pballanddoes anyone have any preference?17:12
thinrichsA google doc might make it easier for non-coders to add use cases.17:12
thinrichsI’m leaning toward a google doc.17:13
skn_May be we can just link it from those one liners in Congress wiki17:13
thinrichsskn: yep.17:13
*** sarob has quit IRC17:13
pballandhttps://docs.google.com/document/d/1ExDmT06vDZjzOPePYBqojMRfXodvsk0R8nRkX-zrkSw/edit?usp=sharing17:13
sarob_Gdoc will be easier for the non git gerrit people17:13
rajdeepgoogle docs is easier unless the doc becomes large17:13
rajdeepor we need to maintain history17:13
pballandI’ll link from the wiki17:14
thinrichspballand: no need for even an action item for that, it seems.  Nice.  :)17:14
skn_Thanks pballand17:14
thinrichsskn_: when you copy your description in there, let us all know so we can take a look.17:15
thinrichssarob: any progress on your use case?17:15
skn_We should have at least one paragraph for each of the use cases17:15
skn_sarob: I have something written,  I’ll try to clean it up and put it in the doc today or tomorrow when I get time17:15
sarob_No sorry. I was slammed last week17:16
sarob_I have some time today17:16
*** nlahouti_ has quit IRC17:16
thinrichssarob: no worries.  Let us know if we can help.17:16
sarob_I'll post to the gdoc for collaboration and such17:17
thinrichssarob: sounds good.17:17
thinrichsEspecially for you newcomers, if you have use cases you’re interested in, put them in the doc and drop us a note so we can take a look.17:17
skn_pballand: is the gdoc open to edit for everyone?17:17
pballandit should be editable by anyone with the link17:18
thinrichsI just edited it.17:18
sjcazzolgood, we are developing some new scenarios that could be addressed17:18
pballandI can lock it down to emails I have17:18
thinrichssjcazzol: great!  Love to see them.17:18
thinrichspballand: let’s leave it open to the world.17:18
ibenHow many use cases are we shooting for to start with?17:19
ibenwill they be prioritized based on effort?17:19
banixyeah open to the world will be better17:19
thinrichsiben: I think we want to know what people are interested in and then yes, prioritized.17:19
ibenwould security be one <— as an example?17:20
thinrichsiben: meant to say we’ll prioritize them17:20
thinrichsiben: I think we’d want something more specific than “security”.17:20
skn_iben: Yes, I am working on a security use case17:20
skn_IDS use case17:20
thinrichsWhat data sources are needed?  What’s the concrete policy?  ETc.17:20
ibensure - of course - but as a general category - okay - gotcha!17:20
pballandiben: we would like to highlight cross-component uses17:21
skn_I think we’ll need some discussion on the policy caching etc, after we make some progress with the use cases17:22
thinrichsThere’s for sure lots to discuss.17:23
sarob_Acls being applied as set will be critical17:23
thinrichsWe are hoping to get an alpha release out in the next couple of weeks.  People are starting to ask for it.17:23
*** amotoki has quit IRC17:23
skn_Cant folks just download from the stackforge?17:24
thinrichssarob: good to know.  Let’s get it up on that google doc so we can start prioritizing dev effort.17:24
thinrichsskn: They can get the code, but they won’t be able to do much with it right now.17:24
thinrichsThe policy engine and data sources don’t talk to each other.17:24
thinrichsI’m working on that currently.  I’m hoping to have significant time this week to devote.17:25
*** mspreitz has quit IRC17:25
thinrichsBut I’ve also got jury duty.  Fun.17:25
skn_thinrichs: Oh, ok, got it.  Do we have a readme there?17:25
thinrichsThe file is there, but I doubt it says anything interesting since the code isn’t yet functional.17:25
skn_I see17:26
thinrichsI forgot to record action items for sarob and skn_.17:26
thinrichs#action sarob, skn_ will put their use cases on the use case google doc linked from the wiki17:26
sjcazzolthinrichs: which are the main features that are missing for the alpha?17:26
thinrichs#action thinrichs will continue working on policy/datasource integration17:27
skn_Is it already linked from wiki?17:27
pballandskn_: yes17:27
thinrichssjcazzol: mainly the integration I mentioned and the API implementation17:27
*** rajdeep_ has joined #openstack-meeting-317:27
thinrichspballand is working on the API17:27
thinrichsI’m hoping to have something in review by end of week.17:27
sjcazzolthinrichs: ok, nice17:27
skn_pballand: where is the link in the wiki?17:27
*** emagana has quit IRC17:27
thinrichspballand: an eta on the API?17:28
*** rajdeep has quit IRC17:28
thinrichsskn: refresh your web page and you’ll see it at the top.17:28
pballandskn_: search for “use cases"17:28
skn_pballand: https://wiki.openstack.org/wiki/Congress#Use_Cases is where I am looking at, but I dont see the link17:29
pballandthinrichs: I keep hoping for some serious time to devote - at the risk of sounding like a broken record, I think this week is reasonable17:29
thinrichskudva, who I don’t see here today, is also working on adding builtins to the policy language.17:29
thinrichsBuiltins are things like addition, subtraction, string manipulation.17:30
*** emagana has joined #openstack-meeting-317:30
thinrichsBuiltins aren’t strictly necessary for the alpha, but it would be nice to have them.17:30
thinrichsrajdeep: are you still here?  I saw you signed off.17:31
rajdeep_yes17:31
pballandskn_: I had linked at the top, but added a link to that section as well17:31
rajdeep_i am there17:31
*** nati_ueno has quit IRC17:31
thinrichsI saw your unit tests for Nova were merged.17:31
skn_pballand: Thanks!  Now I see it :)17:32
rajdeep_thanks - those were first set of test cases17:32
thinrichsNewcomers: rajdeep has been working on writing thing wrappers around Nova/Neutron so that we can write policy over the data they expose.17:32
rajdeep_which test conversion of dictionary into tuples17:32
banixrajdeep_: nice17:33
*** kudva has joined #openstack-meeting-317:33
kudvaHi Kudva joining, sorry for the delay17:33
rajdeep_it will be great to take a look at the drivers for neutron and nova and provide feedback on amount of data coming in17:33
sjcazzolrajdeep_: great17:33
thinrichskudva: glad you could join us.17:34
sjcazzolrajdeep_: are you targeting other components too?17:34
rajdeep_yes once i have the unit tests completed17:34
rajdeep_nova and neutron were critical which are done17:34
rajdeep_next is cinder and keystone17:34
thinrichssjcazzol: any components you’re specifically interested in?17:35
rajdeep_- we should prioritize17:35
thinrichsWe were focused on integrating those necessary for one of our use cases.17:35
sjcazzolthinrichs: for now just nova17:35
skn_thinrichs, rajdeep: is the wrapper for enforcement of the policies?17:35
sjcazzolthinrichs: but we are waiting for new scenarios17:35
skn_or both?17:35
rajdeep_enforcement is the next step ..17:36
thinrichssjcazzol, rajdeep: Maybe you and rajdeep should connect offline to check that we have enough Nova support to handle what you need.  I don’t believe we have full Nova integration.17:36
sjcazzolthinrichs: perfect17:36
rajdeep_sjcazzol you can send me email at rajdeepd at vmware.com17:37
thinrichsskn: I didn’t understand your question17:37
sjcazzolrajdeep_: ok, I'll do17:37
skn_thinrics: the nova/neutron wrapper is meant to enforce the policy?17:37
ibeni would expect a policy wrapper to be like able to log or enforce17:38
ibenthere should be a learning mode option17:38
ibenand an enforcement option17:38
thinrichsThe datasource wrapper just makes Nova/Neutron data look like it’s represented as tables.17:38
thinrichsEventually the datasource wrapper will also execute API calls on Nova/Neutron.17:38
thinrichsBut the policy engine is responsible for monitoring policy and choosing which API calls to execute (i.e. how to enforce policy).17:39
*** alexpilotti has quit IRC17:39
banixsorry if this question is not relevant; iignore if that is the case: Is  a policy like “all passwords in servers of this group need to be at leat this long” something being considered?17:39
skn_thinrichs: that’s what i wanted to know.  So, currently its only about modifying the data so that can be ingested by Congress data source17:39
thinrichsskn: yes.17:39
skn_Got it, thanks.17:39
thinrichsbanix: that’s possible to express/enforce IF there are datasources that allow Congress to do it.17:40
thinrichsSay we have an ActiveDirectory integration that exposes the min-length for passwords.17:40
thinrichsThen we could write policy in Congress saying what the min-length must be.17:40
banixthinrichs: sure. makes sense.17:41
*** alexpilotti has joined #openstack-meeting-317:41
thinrichsiben: what did you mean by “learning mode"17:41
thinrichs?17:41
*** eghobo has quit IRC17:41
skn_thinrichs: So this wrapper will eventually be responsible for making API calls into Nova/Neutron?17:41
ibennever mind - you guys answered it17:42
*** eghobo has joined #openstack-meeting-317:42
thinrichsGreat.17:42
ibenthe existing functions will need to be wrapped17:42
ibenthis wrapped data goes into a policy engine17:42
*** nati_ueno has joined #openstack-meeting-317:42
ibenwhere rules can be run17:42
ibenthese rules can do various things17:42
thinrichsiben: sounds like we’re on the same page.17:42
ibenlearning or analytics is one of the actions17:43
pballandCongress needs to both get data from the components in a standard form (tables) _and_ can work with the components to enforce policy.  We are focused on the first part (which enables monitoring/logging) initially17:43
ibenbut of course policy enforcement would be possible too17:43
skn_iben: by learning you mean monitoring?17:43
thinrichsWe’re planning to look into pushing policy down to other policy-aware components (like Neutron’s GBP) so that enforcement is done more proactively.17:44
sjcazzolpballand: do you plan to add policies enforcement for the beta?17:44
ibeni'm just thinking of a simple firewall use case - it's important not to disrupt existing traffic patterns so many vendors offer a learning mode or discover period where the sample initial rule sets get created17:45
ibenthen you can decide to enable these auto generated rules (or policies)17:45
pballandsjcazzol: I don’t know when we will tag ‘beta’, but I do envision some enforcement support comming shortly after monitoring is working17:46
skn_iben: got it17:46
ibenthe rules can be enabled in blocking (enforcing) mode or in logging only - watching17:46
thinrichsiben: we’re definitely not aiming to auto-generate policy.17:46
sjcazzolpballand: ok, thanks17:46
thinrichslogging-only makes sense for sure.17:46
ibenthis allows us to experiment and see the results of any policy changes without impacting production traffic.17:46
banixiben: well i gues that could happen in parallel with what congress does17:46
banixwhat thinrichs said17:47
thinrichsBut no auto-gen b/c unlike a firewall Congress doesn’t know much about the services it is monitoring.17:47
ibencoolio!  this is really great.17:47
pballandiben: your example makes sense, but in some cases monitoring (logging) will be the final desired action (not a compromise)17:47
thinrichsWe’re sensitive to customers not trusting basically anything for a while, and trying to slowly earn their trust over time.17:48
thinrichsBefore we run out of time, let’s get to an update from kudva too.17:48
thinrichskudva: how are the builtins progressing?17:48
rajdeep_you could write a driver for firewall - which could convert congress actions into firewall configuration17:48
kudvaI tried to push into gerrit.17:48
thinrichsDid it work?17:49
thinrichsI didn’t see a request for review for me.17:49
kudvaseems to have. I created a new branch. I have tested the builtin directory code itself. That is working fine17:49
kudvaLet me try again then. I pushed on saturday, and got an email saying jenkins test failed.17:49
thinrichsDon’t worry about the Jenkins test for now.17:50
skn_rajdeep_: agreed.  That’s the right way, because Congress should not try to understand the concepts like firewalling, or for that matter anything else17:50
kudvaThe runtime.py with Tim's recommended changes was also pushed, but all my code was commented out. I need some feedback on that section17:50
thinrichsAdd at least me as a reviewer (Tim Hinrichs), and we can iterate.17:50
kudvaokay, will do that. The builtin directory that manages the objects for the builtin are testing. The hook to runtime.py is about 10-20 lines of code which I need some help with since17:51
kudvaI am not completely clear on the TopDownTheory data structure17:51
kudvaSo, I will push again17:51
thinrichskudva: I’ll definitely help out.17:51
kudvaWondering how I can have review on the runtime.py code17:51
kudvairc?17:51
banixkudva: do you have a link from your push?17:51
kudvahttp://logs.openstack.org/40/95340/1/check/gate-congress-pep8/178c99b17:52
kudvahttp://logs.openstack.org/40/95340/1/check/gate-congress-python27/7a3e74c17:52
*** davlaps has joined #openstack-meeting-317:52
banix#link https://review.openstack.org/#/c/95340/17:53
kudvathe first link says failure, the second one says success17:53
thinrichskudva: there’s probably just some formatting that needs fixing.17:53
rajdeep_you need to fix the pep warnings17:53
banixkudva: no worries; mainly white space you need to clean up.17:54
rajdeep_white spaces etc17:54
thinrichsYou can add me as a reviewer by typing in Tim Hinrichs next to the button “Add Reviewer”17:54
banixkudva: https://review.openstack.org/#/c/95340/1/congress/builtin/congressbuiltin.py17:54
kudvagot it, will clean up and push again17:55
thinrichsI’ll write comments, and you should get an email saying that I’ve posted those comments.17:55
thinrichsI think that covers all our action items from last week.17:55
thinrichsLet’s open it up for discussion.17:55
kudvaokay, grat thanks17:55
thinrichs#topic open discussion17:55
*** openstack changes topic to "open discussion (Meeting topic: CongressTeamMeeting)"17:55
thinrichsIf no one has anything specific, maybe the newcomers can tell us why they’re interested in Congress.17:56
sjcazzolthinrichs: ok17:57
banixLet me say a few words: The Neutron group poliy is getting to a point that we may have some code merged this cycle17:57
skn_BTW, it would be nice if the newcomers can tell their names too17:57
sjcazzolwe are working on a POC to add SLA to openstack17:57
sjcazzolSergio Cazzolato17:57
banixwould be great to see how it can get used by other policy engines like Congress17:57
sjcazzolI work at Intel17:57
*** kudva has quit IRC17:57
skn_sjcazzol: Awesome17:58
ibenI've heard a lot about the need for policy to enable standard security practices across a disparate infrastrcuture. <— Iben Rodriguez - cloud security architect - leveraging my background in vmware environments to being openstack to the enterprise17:58
skn_SLA for availability or performance?17:58
thinrichsbanix: That’s been on our agenda for a long while.17:58
sjcazzolSLA for both17:58
*** pballand has quit IRC17:59
sjcazzolalso we are considering other scenarios17:59
thinrichssjcazzol: SLAs sound interesting.  I’m looking forward to the details for your use cases.17:59
*** jpomero has quit IRC17:59
banixthinrichs: yes looks like we may be getting closer to the goal :)17:59
skn_Got to leave, running out of time.  Thanks folks17:59
*** skn_ has left #openstack-meeting-317:59
thinrichsskn: thanks!17:59
ibenbye everyone!17:59
sjcazzolthanks folks17:59
thinrichsiben: cool—glad to have you.17:59
thinrichsAnd yes it seems we’re out of time.  Follow up to the ML if it can’t wait til next week!18:00
thinrichsThanks all!18:00
banixbye everybody18:00
thinrichs#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Tue May 27 18:00:22 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-05-27-17.03.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-05-27-17.03.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-05-27-17.03.log.html18:00
*** sjcazzol has left #openstack-meeting-318:00
*** emaganap has joined #openstack-meeting-318:02
*** rajdeep_ has quit IRC18:02
*** alexpilotti has quit IRC18:03
*** emagana has quit IRC18:03
*** jpomero has joined #openstack-meeting-318:03
*** thinrichs has quit IRC18:04
*** david-lyle has joined #openstack-meeting-318:05
*** jamielennox|away is now known as jamielennox18:05
*** mrunge has quit IRC18:07
*** sarob_ has quit IRC18:07
*** pballand has joined #openstack-meeting-318:11
*** nati_ueno has quit IRC18:13
*** nati_ueno has joined #openstack-meeting-318:14
*** Youcef has joined #openstack-meeting-318:14
*** clu_ has left #openstack-meeting-318:24
*** pballand has quit IRC18:31
*** emaganap has quit IRC18:36
*** chuckC has quit IRC18:38
*** emagana has joined #openstack-meeting-318:43
*** emagana has quit IRC18:44
*** emaganap has joined #openstack-meeting-318:45
*** chuckC has joined #openstack-meeting-318:46
*** jpomero_ has joined #openstack-meeting-318:52
*** jpomero has quit IRC18:54
*** lsmola2 has joined #openstack-meeting-318:56
*** Alex_Gaynor has joined #openstack-meeting-318:56
*** nati_ueno has quit IRC18:58
*** nati_ueno has joined #openstack-meeting-318:59
briancurtin#startmeeting python-openstacksdk19:01
openstackMeeting started Tue May 27 19:01:17 2014 UTC and is due to finish in 60 minutes.  The chair is briancurtin. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: python-openstacksdk)"19:01
openstackThe meeting name has been set to 'python_openstacksdk'19:01
*** bknudson has joined #openstack-meeting-319:01
briancurtinif you're here for the python-openstacksdk meeting, there's a little agenda at https://wiki.openstack.org/wiki/Meetings/PythonOpenStackSDK#Agenda_for_2014-05-27_1900_UTC - it's just the open reviews to talk about so we can move on, if you need the links19:02
briancurtinand with that, who's here?19:03
briancurtinBrian Curtin, Rackspace19:03
edleafeEd Leafe, Rackspace19:03
bknudsonBrant Knudson, IBM19:03
jamielennoxJamie Lennox, Red Hat19:03
Alex_GaynorAlex Gaynor, Rackspace19:03
briancurtin#topic https://review.openstack.org/#/c/91889/ -- Authentication from keystoneclient19:05
*** openstack changes topic to "https://review.openstack.org/#/c/91889/ -- Authentication from keystoneclient (Meeting topic: python-openstacksdk)"19:05
briancurtinhas anyone looked at the big auth review and have any comments? terry made a bunch of changes, and i have a few small comments on the last set, but anyone else?19:05
briancurtinjamie had some comments, most of which were addressed, but a few things potentially outstanding (the factory functions are one off the top of my head)19:06
jamielennoxregarding the _factory for plugins, the reason i made it private in keystoneclient and advocate for it's removal here is that we should expect that there are going to be way more plugins and that loading them manually from a factory like that won't work19:06
jamielennoxyou should never be in the position that you have a bunch of arguments and you need to figure out which plugin to use - the plugin should always be explicit19:07
Alex_Gaynor+119:07
*** rockyg has joined #openstack-meeting-319:07
*** lcheng_ has quit IRC19:08
*** lcheng_ has joined #openstack-meeting-319:08
*** terrylhowe has joined #openstack-meeting-319:09
terrylhoweTerry Howe HP running late19:09
briancurtinyep, agreed there19:09
briancurtinoutside of the factories, anything else going on in the change that people like/dont like?19:12
*** ericpete_ has joined #openstack-meeting-319:13
jamielennoxjust looking auth/service.py has been removed - how does that affect get_token etc19:13
terrylhoweI renamed it service_filter19:13
terrylhoweI think there is some doc cleanup that needs to happen in other files19:14
terrylhowesome things I'm reluctant to change because of other outstanding changes in the pipeline19:14
*** ericpete_ has quit IRC19:14
*** vkmc has quit IRC19:15
*** ericpeterson has joined #openstack-meeting-319:15
*** ericpeterson has left #openstack-meeting-319:15
briancurtinterrylhowe: overall i'm good with this, and i think we can go back and change things if we need, in the interest of just moving on so we can build something19:17
briancurtindoes anyone have anything with this change that is a hard blocker?19:18
terrylhoweI'd definitely like some feedback on it from jamielennox19:18
*** jamielennox_ has joined #openstack-meeting-319:18
briancurtincertainly19:18
jamielennox_stupid vpn19:18
*** jamielennox_ has quit IRC19:19
*** dlenrow has joined #openstack-meeting-319:19
jamielennoxterrylhowe: i'm ok with coming back to fix things19:20
jamielennoxi would like the factories gone up front though19:20
terrylhowecool, that'll work19:20
jamielennoxpeople tend to look at them and assume that's how you should be creating things otherwise19:20
terrylhoweokay19:20
briancurtinif anyone else who hasn't reviewed can try to give it a look after this, that would be great, and then we'll be rolling on19:21
*** lenrow has quit IRC19:22
briancurtin#action remove factory methods, should be good to go19:22
briancurtin#topic https://review.openstack.org/#/c/94887 -- Clean up transport stuff out of the resource class19:22
*** openstack changes topic to "https://review.openstack.org/#/c/94887 -- Clean up transport stuff out of the resource class (Meeting topic: python-openstacksdk)"19:22
terrylhowedtroyer needs to look at that, is he afk?19:23
briancurtini thought this looked fine and +2'ed, could use another look19:23
briancurtinand yeah, from dtroyer19:23
briancurtinnot sure if he's around, but i just added him as a reviewer on the change19:24
*** kenhui has quit IRC19:24
terrylhoweI think I've minimized the changes and Dean might be able to live with it based on offline discussions I've had with him19:25
briancurtinsounds good19:26
briancurtin#action needs a dtroyer review, seems like it should be workable given minimized changes19:26
briancurtin#topic https://review.openstack.org/#/c/94707 -- Add command structure to example code19:27
*** openstack changes topic to "https://review.openstack.org/#/c/94707 -- Add command structure to example code (Meeting topic: python-openstacksdk)"19:27
briancurtinthis one is really small19:27
*** muralia has joined #openstack-meeting-319:28
*** muralia has left #openstack-meeting-319:28
jamielennoxsure, that's fine19:28
jamielennoxso long as no-one ever thinks it should be pulled out and make into a proper CLI tool :)19:29
terrylhoweit is hill billy, but it should do19:29
briancurtin#topic what's next?19:31
*** openstack changes topic to "what's next? (Meeting topic: python-openstacksdk)"19:31
briancurtinso if we think the auth change is basically good to go, what do we want our next step to be?19:31
terrylhoweI'd like to implement some resource class and get a feel for everything19:32
*** nati_ueno has quit IRC19:33
jamielennoxterrylhowe: i agree, i had a play with some resource classes a while ago and i think there will be some pain points to get through, but i don't think we'll know what they are until we try it19:33
briancurtinis there any particularly good starting point on that? edleafe - from having implemented a lot of them via pyrax, any thought there?19:34
edleafeNot sure given the reverse nature of the current design19:35
*** dlenrow has quit IRC19:36
edleafeif you have endpoints, you need a way to create the desired URLs for retrieving objects. Pyrax created them from the JSON response, but you've indicated that you want to pre-define the attributes, so that's another sticking point.19:36
terrylhoweI was kind of thinking with starting with something simple like some basic glance thing and then pick a complicated one after that19:39
Alex_Gaynorsounds good19:40
*** lsmola2 has quit IRC19:40
briancurtini'll be traveling for a bit to pittsburgh and russia, but i guess i know the most about swift of anything, so maybe looking there myself19:42
*** ericpete_ has joined #openstack-meeting-319:43
terrylhoweswift would be a good one to try early since it is a bit oddball19:43
*** SumitNaiksatam has joined #openstack-meeting-319:44
*** nelsnelson has quit IRC19:44
*** nelsnelson has joined #openstack-meeting-319:45
jamielennoxi'll try to have a crack at a few of the basic keystone classes, a little swamped currently though19:45
briancurtinbesides starting to play with those, is there anything else to talk about? 15 minutes left, and it seems like we're slowing down19:46
terrylhowemore example code19:47
*** ericpete_ has left #openstack-meeting-319:47
*** lcheng_ has quit IRC19:47
briancurtinshould start making docs a hard requirement at this point as well19:48
briancurtin(touched on that at the summit, havent had it come up though)19:49
terrylhowedocs would be especially useful on the resource implementations19:49
*** nati_ueno has joined #openstack-meeting-319:50
terrylhoweif users are using it at that level19:50
jamielennoxare we ok to have those docs inline or should they be in a folder?19:50
*** lcheng_ has joined #openstack-meeting-319:50
jamielennoxinline as in docstrings19:51
Alex_GaynorDocstrings and the docs/ dir are for different things IMO19:51
edleafe+1 on not relying on docstrings19:51
Alex_Gaynordocs/ dir is for prose, for anyone using the public API for the SDK. docstrings are reference material (not always prose) for someone who is (usually) reading the code itself19:51
edleafePeople working on the SDK use the docstrings. Developers *using* the SDK need higher-level docs19:52
terrylhowesounds good19:52
jamielennoxok19:52
briancurtinagreed. i think we need to be on top of both, and make sure we're starting to build up user docs as we're developing19:52
edleafeYou should probably write the usability docs *before* implementing the SDK19:53
briancurtini sketch things out locally like that from time to time, but i dont particularly care about doc driven as a process or anything like that19:56
edleafeI just mean figure out how you would expect an SDK to work, and then implement it that way19:57
edleafeIt's too easy for technical folks to get tied up in the details of the implementation19:57
edleafeAnd forget how devs need this to work19:57
briancurtintwo minutes left, anything to squeeze in?19:59
briancurtin#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue May 27 20:00:28 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-05-27-19.01.html20:00
*** nati_ueno has quit IRC20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-05-27-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-05-27-19.01.log.html20:00
*** markmcclain has joined #openstack-meeting-320:00
*** terrylhowe has left #openstack-meeting-320:04
*** Alex_Gaynor has left #openstack-meeting-320:06
*** jgrimm has left #openstack-meeting-320:08
*** nati_ueno has joined #openstack-meeting-320:12
*** chuckC has quit IRC20:13
*** otherwiseguy has quit IRC20:19
*** boris-42 has quit IRC20:21
*** boris-42 has joined #openstack-meeting-320:21
*** jpomero_ has quit IRC20:33
*** vkmc has joined #openstack-meeting-320:37
*** rm_work|away is now known as rm_work20:38
*** otherwiseguy has joined #openstack-meeting-320:41
*** jtomasek has joined #openstack-meeting-320:41
*** gduan has quit IRC20:49
*** garyduan has joined #openstack-meeting-320:49
*** lcheng_ has quit IRC20:50
*** gduan has joined #openstack-meeting-320:52
*** garyduan has quit IRC20:54
*** julim has quit IRC21:01
*** alexpilotti has joined #openstack-meeting-321:01
*** chuckC has joined #openstack-meeting-321:07
*** jpomero has joined #openstack-meeting-321:07
*** nati_ueno has quit IRC21:08
*** nati_ueno has joined #openstack-meeting-321:11
*** lblanchard has quit IRC21:11
*** jtomasek has quit IRC21:12
*** lcheng_ has joined #openstack-meeting-321:13
*** rockyg has quit IRC21:15
*** markmcclain has quit IRC21:21
-openstackstatus- NOTICE: Zuul is offline due to an operational issue; ETA 2200 UTC.21:33
*** ChanServ changes topic to "Zuul is offline due to an operational issue; ETA 2200 UTC."21:33
*** nati_ueno has quit IRC21:37
*** davidlenwell_ has joined #openstack-meeting-321:40
*** nati_ueno has joined #openstack-meeting-321:43
*** SumitNaiksatam has quit IRC21:43
*** davidlenwell_ has quit IRC21:44
*** SumitNaiksatam has joined #openstack-meeting-321:45
*** davidlenwell has quit IRC21:45
*** davidlenwell has joined #openstack-meeting-321:47
*** mwagner_lap has quit IRC21:52
*** emaganap has quit IRC21:54
*** peristeri has quit IRC21:55
*** emagana has joined #openstack-meeting-321:55
*** shakamunyi has quit IRC22:03
*** nati_ueno has quit IRC22:05
*** otherwiseguy has quit IRC22:06
*** yamahata has joined #openstack-meeting-322:07
*** rgbkrk has joined #openstack-meeting-322:07
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:10
-openstackstatus- NOTICE: Zuul is started and processing changes that were in the queue when it was stopped. Changes uploaded or approved since then will need to be re-approved or rechecked.22:10
*** briancurtin has left #openstack-meeting-322:10
*** shakamunyi has joined #openstack-meeting-322:10
*** jthopkin has quit IRC22:11
*** tomoe_ has joined #openstack-meeting-322:16
*** SumitNaiksatam has quit IRC22:19
*** SumitNaiksatam has joined #openstack-meeting-322:23
*** emagana has quit IRC22:30
*** nati_ueno has joined #openstack-meeting-322:32
*** Sukhdev has joined #openstack-meeting-322:38
*** nati_uen_ has joined #openstack-meeting-322:42
*** nati_ueno has quit IRC22:42
*** beyounn_1 has quit IRC23:06
*** mwagner_lap has joined #openstack-meeting-323:08
*** beyounn_1 has joined #openstack-meeting-323:08
*** yamahata has quit IRC23:16
*** SumitNaiksatam has quit IRC23:23
*** otherwiseguy has joined #openstack-meeting-323:23
*** SumitNaiksatam has joined #openstack-meeting-323:24
*** david-lyle has quit IRC23:25
*** igordcard has quit IRC23:29
*** davlaps has quit IRC23:33
*** devlaps has quit IRC23:33
*** TravT has quit IRC23:35
*** eguz has joined #openstack-meeting-323:51
*** carl_baldwin_ has quit IRC23:52
*** eghobo has quit IRC23:55
*** lcheng_ has quit IRC23:58

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