Tuesday, 2014-06-03

*** jackib has joined #openstack-meeting-300:00
*** jackib has quit IRC00:00
*** jackib has joined #openstack-meeting-300:01
*** pballand has joined #openstack-meeting-300:01
*** jackib has quit IRC00:01
*** jackib has joined #openstack-meeting-300:01
*** jackib has quit IRC00:02
*** jackib has joined #openstack-meeting-300:03
*** jackib has quit IRC00:03
*** jackib has joined #openstack-meeting-300:03
*** jackib has quit IRC00:04
*** jackib has joined #openstack-meeting-300:04
*** jackib has quit IRC00:05
*** jackib has joined #openstack-meeting-300:05
*** jackib has quit IRC00:06
*** jackib has joined #openstack-meeting-300:06
*** jackib has quit IRC00:07
*** jackib has joined #openstack-meeting-300:07
*** jackib has quit IRC00:08
*** jackib has joined #openstack-meeting-300:08
*** jackib has quit IRC00:09
*** jackib has joined #openstack-meeting-300:10
*** jackib has quit IRC00:11
*** jackib has joined #openstack-meeting-300:11
*** jackib has quit IRC00:12
*** jackib has joined #openstack-meeting-300:12
*** jackib has quit IRC00:13
*** jackib has joined #openstack-meeting-300:13
*** jackib has quit IRC00:14
*** jackib has joined #openstack-meeting-300:14
*** jackib has quit IRC00:15
*** jackib has joined #openstack-meeting-300:15
*** jackib has quit IRC00:16
*** jackib has joined #openstack-meeting-300:16
*** nati_uen_ has quit IRC00:16
*** jackib has quit IRC00:16
*** nati_ueno has joined #openstack-meeting-300:17
*** jackib has joined #openstack-meeting-300:17
*** jackib has quit IRC00:17
*** TravT has quit IRC00:18
*** jackib has joined #openstack-meeting-300:18
*** SumitNaiksatam has quit IRC00:18
*** jackib has quit IRC00:18
*** jackib has joined #openstack-meeting-300:19
*** jackib has quit IRC00:19
*** jackib has joined #openstack-meeting-300:20
*** jackib has quit IRC00:20
*** jackib has joined #openstack-meeting-300:21
*** nati_ueno has quit IRC00:21
*** jackib has quit IRC00:21
*** jackib has joined #openstack-meeting-300:22
*** safchain_ has quit IRC00:22
*** jackib has quit IRC00:23
*** jackib has joined #openstack-meeting-300:23
*** jackib has quit IRC00:23
*** jackib has joined #openstack-meeting-300:24
*** thomasem has quit IRC00:24
*** pballand has quit IRC00:24
*** jackib has quit IRC00:24
*** jackib has joined #openstack-meeting-300:25
*** jackib has quit IRC00:25
*** jackib has joined #openstack-meeting-300:26
*** jackib has quit IRC00:26
*** jackib has joined #openstack-meeting-300:26
*** jackib has quit IRC00:27
*** jackib has joined #openstack-meeting-300:27
*** jackib has quit IRC00:28
*** jackib has joined #openstack-meeting-300:28
*** nati_ueno has joined #openstack-meeting-300:32
*** cjellick has quit IRC00:33
*** jackib has quit IRC00:33
*** cjellick has joined #openstack-meeting-300:34
*** chuckC has quit IRC00:34
*** cjellick has quit IRC00:38
*** otherwiseguy has quit IRC00:45
*** nati_ueno has quit IRC00:46
*** nati_ueno has joined #openstack-meeting-300:47
*** chuckC has joined #openstack-meeting-300:50
*** nati_ueno has quit IRC00:51
*** SumitNaiksatam has joined #openstack-meeting-300:54
*** banix has joined #openstack-meeting-300:55
*** jaypipes has joined #openstack-meeting-301:00
*** nati_ueno has joined #openstack-meeting-301:07
*** jaypipes has quit IRC01:09
*** otherwiseguy has joined #openstack-meeting-301:18
*** nati_ueno has quit IRC01:23
*** nati_ueno has joined #openstack-meeting-301:24
*** nati_ueno has quit IRC01:24
*** nati_ueno has joined #openstack-meeting-301:25
*** nati_uen_ has joined #openstack-meeting-301:26
*** nati_uen_ has quit IRC01:26
*** nati_uen_ has joined #openstack-meeting-301:26
*** nati_uen_ has quit IRC01:26
*** nati_ueno has quit IRC01:29
*** nelsnels_ has joined #openstack-meeting-301:39
*** nelsnelson has quit IRC01:42
*** Sukhdev has joined #openstack-meeting-301:51
*** tomoe_ has quit IRC01:51
*** tomoe_ has joined #openstack-meeting-301:54
*** thomasem has joined #openstack-meeting-301:59
*** yamahata has joined #openstack-meeting-302:02
*** thomasem has quit IRC02:04
*** devlaps has quit IRC02:16
*** davlaps has quit IRC02:16
*** Sukhdev has quit IRC02:17
*** jackib has joined #openstack-meeting-302:17
*** jackib has quit IRC02:22
*** shakamunyi has quit IRC02:31
*** jackib has joined #openstack-meeting-302:45
*** coolsvap|afk is now known as coolsvap03:13
*** tomoe_ has quit IRC03:27
*** eghobo has quit IRC03:47
*** jackib has quit IRC03:48
*** banix has quit IRC03:50
*** emagana has joined #openstack-meeting-303:51
*** zehicle has joined #openstack-meeting-303:53
*** otherwiseguy has quit IRC04:08
*** emagana has quit IRC04:15
*** emaganap has joined #openstack-meeting-304:19
*** tomoe_ has joined #openstack-meeting-304:20
*** kenhui has joined #openstack-meeting-304:20
*** emaganap has quit IRC04:30
*** emagana has joined #openstack-meeting-304:30
*** lcheng_ has joined #openstack-meeting-304:33
*** emagana has quit IRC04:35
*** eghobo has joined #openstack-meeting-304:42
*** SumitNaiksatam has left #openstack-meeting-304:51
*** dolphm has quit IRC05:03
*** dolphm has joined #openstack-meeting-305:04
*** emagana has joined #openstack-meeting-305:20
*** emagana has quit IRC05:23
*** Youcef has joined #openstack-meeting-305:34
*** jcoufal has joined #openstack-meeting-305:41
*** yamamoto_ has joined #openstack-meeting-305:41
*** mrunge has joined #openstack-meeting-305:45
*** mrunge has quit IRC05:45
*** mrunge has joined #openstack-meeting-305:45
*** coolsvap is now known as coolsvap|afk05:56
*** coolsvap|afk is now known as coolsvap06:01
*** lcheng_ has quit IRC06:06
*** kenhui has quit IRC06:17
*** kevinbenton has quit IRC06:19
*** lcheng_ has joined #openstack-meeting-306:24
*** lcheng_ has quit IRC06:30
*** ttrifonov is now known as ttrifonov_zZzz06:32
*** lcheng_ has joined #openstack-meeting-306:37
*** nati_ueno has joined #openstack-meeting-306:38
*** coolsvap is now known as coolsvap|afk06:57
*** coolsvap|afk is now known as coolsvap07:02
*** ttrifonov_zZzz is now known as ttrifonov07:13
*** eghobo has quit IRC07:18
*** lcheng_ has quit IRC07:21
*** jtomasek has joined #openstack-meeting-307:23
*** nacim has quit IRC07:43
*** nacim has joined #openstack-meeting-307:43
*** MaxV has joined #openstack-meeting-307:46
*** yamamoto_ has quit IRC08:00
*** safchain has joined #openstack-meeting-308:05
*** nati_ueno has quit IRC08:21
*** coolsvap is now known as coolsvap|afk08:24
*** coolsvap|afk is now known as coolsvap08:46
*** zehicle has quit IRC08:56
*** zehicle has joined #openstack-meeting-308:56
*** igordcard has joined #openstack-meeting-309:09
*** armax has joined #openstack-meeting-309:30
*** tomoe_ has quit IRC09:41
*** armax has quit IRC09:52
*** amotoki has joined #openstack-meeting-309:57
*** coolsvap is now known as coolsvap|afk10:24
*** banix has joined #openstack-meeting-310:45
*** yamahata has quit IRC10:52
*** tomoe_ has joined #openstack-meeting-311:11
*** banix has quit IRC11:22
*** nacim has quit IRC11:36
*** safchain has quit IRC11:37
*** yamahata has joined #openstack-meeting-311:39
*** nacim has joined #openstack-meeting-311:46
*** mwagner_lap has quit IRC11:53
*** sankarshan has joined #openstack-meeting-311:54
*** safchain has joined #openstack-meeting-311:54
*** tomoe_ has quit IRC11:59
*** sankarshan is now known as sankarshan_away12:01
*** tomoe_ has joined #openstack-meeting-312:01
*** jamie_h has joined #openstack-meeting-312:04
*** amotoki has quit IRC12:05
*** mrunge has quit IRC12:22
*** thomasem has joined #openstack-meeting-312:28
*** thomasem has quit IRC12:29
*** thomasem has joined #openstack-meeting-312:29
*** jackib has joined #openstack-meeting-312:35
*** julim has joined #openstack-meeting-312:46
*** lblanchard has joined #openstack-meeting-312:49
*** jcoufal has quit IRC12:52
*** jcoufal has joined #openstack-meeting-312:53
*** jackib has quit IRC12:53
*** jackib has joined #openstack-meeting-312:54
*** jackib has quit IRC12:54
*** akrivoka has joined #openstack-meeting-312:58
*** nacim has quit IRC13:02
*** jaypipes has joined #openstack-meeting-313:03
*** armax has joined #openstack-meeting-313:09
*** banix has joined #openstack-meeting-313:12
*** alexpilotti has joined #openstack-meeting-313:24
*** nacim has joined #openstack-meeting-313:27
*** mfer has joined #openstack-meeting-313:28
*** nati_ueno has joined #openstack-meeting-313:29
*** nelsnels_ has quit IRC13:39
*** nelsnelson has joined #openstack-meeting-313:39
*** otherwiseguy has joined #openstack-meeting-313:43
*** MaxV has quit IRC13:48
*** zehicle has quit IRC13:48
*** armax has quit IRC13:48
*** JingYuan has joined #openstack-meeting-313:50
*** MaxV has joined #openstack-meeting-313:51
*** shakamunyi has joined #openstack-meeting-313:51
*** peristeri has joined #openstack-meeting-313:58
*** armax has joined #openstack-meeting-314:01
*** jcoufal has quit IRC14:03
*** mwagner_lap has joined #openstack-meeting-314:21
*** nati_ueno has quit IRC14:29
*** pballand has joined #openstack-meeting-314:32
*** tomoe_ has quit IRC14:38
*** TravT has joined #openstack-meeting-314:39
*** bauzas has joined #openstack-meeting-314:40
*** jackib has joined #openstack-meeting-314:49
*** lcheng_ has joined #openstack-meeting-314:50
*** emagana has joined #openstack-meeting-314:51
*** dgenin has joined #openstack-meeting-314:53
*** devlaps has joined #openstack-meeting-314:55
*** emagana has quit IRC14:56
*** apmelton has joined #openstack-meeting-314:56
*** igordcard has quit IRC14:56
*** emagana has joined #openstack-meeting-314:56
*** jpich has joined #openstack-meeting-314:57
*** danpb has joined #openstack-meeting-314:58
*** vladikr has joined #openstack-meeting-314:59
*** lparth has joined #openstack-meeting-315:00
danpb#startmeeting libvirt15:00
openstackMeeting started Tue Jun  3 15:00:17 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
*** ndipanov has joined #openstack-meeting-315:00
openstackThe meeting name has been set to 'libvirt'15:00
thomasemo/15:00
ndipanov\o15:00
s1rpo/15:00
vladikro/15:00
* bauzas lurking15:00
danpbgreetings team !15:00
thomasem'ello!15:00
lparthhello15:01
*** aloga has joined #openstack-meeting-315:01
danpbreminder that the agenda for today is in - seems quite short currently https://etherpad.openstack.org/p/nova-libvirt-meeting-agenda15:01
thomasemYep, haven't had time to look into the IPv6 stuff any further (like checking for what's shared between host and guest) :(15:01
apmeltono/15:01
danpblets give a couple of  mins grace for anyone else to join before getting into it15:01
*** hallyn_ has joined #openstack-meeting-315:02
*** alaski has joined #openstack-meeting-315:02
*** jcoufal has joined #openstack-meeting-315:02
*** jcoufal has quit IRC15:03
*** lcheng_ has quit IRC15:03
*** jcoufal has joined #openstack-meeting-315:03
*** safchain has quit IRC15:03
*** carl_baldwin has joined #openstack-meeting-315:03
danpb#topic Security contact15:04
*** openstack changes topic to "Security contact (Meeting topic: libvirt)"15:04
danpbso it seems the openstack security team want some contacts for libvirt driver issues15:04
*** safchain has joined #openstack-meeting-315:04
* danpb will throw himself under that bus, but anyone else who's got a strong understanding of the driver can also volunteer15:05
ndipanovI've done it for a few bugs in I15:05
*** jgrimm has joined #openstack-meeting-315:05
ndipanovso I guess write me down unless I am THE SOLE poc...15:05
danpbideally we'd probably want ~3 official points of contact to give coverage  when folks are away15:05
vladikrI think I can help on that as well15:06
*** emagana has quit IRC15:07
danpbFYI, I expect you'll be required to respect any agreed embargo for non-public issues15:07
*** jackib has left #openstack-meeting-315:08
danpb#action danpb, ndipanov and vladikr  volunteered as security contacts15:08
danpb#topic USB Passthrough15:09
*** openstack changes topic to "USB Passthrough (Meeting topic: libvirt)"15:09
danpbis Jing Yuan here ?15:09
JingYuanhi15:09
JingYuanI'm here15:09
danpbgreat - anything you wanted to talk about for this topic ?15:09
JingYuanI have implemented a demo about pass-through host's usb device15:09
JingYuanI want to share some key information about hypervisor(libvirt,qemu) i met when implemented the demo15:10
danpbok15:10
JingYuanDo you think i need to repeat the use cases in the first?15:10
JingYuanIf not i will share the key information directly15:11
danpbpersonally I'm fine with the use cases15:11
danpbso just go straight to the info you have15:11
JingYuanok15:12
JingYuanThe example xml of pass-through a usb device is as follow:<hostdev mode='subsystem' type='usb'> <source>  <vendor id='0x136b'/>  <product id='0x0003'/>  <address bus='2' device='3'/> </source> </hostdev>15:12
JingYuan1. How to distinguish a usb device of a host?  I want to use bus+device to distinguish a usb device, but found that device number will change every time unplug/plug usb device from/to the host.  Vmware and some other software implement this function by pass-through usb port but not usb device. Libvirt doesn't support pass-through usb port. Users have a little inconvenient to use this function15:12
JingYuan2. This feature is strong correlation with guest os type. Win7 with default 'uhci controller' the usb device is in abnormal status, but with 'ehci controller' it is normal. Winxp sp3 is opposed with win7. Both 'uhci' and 'ehci' are ok in centos 6.5.15:13
JingYuanSo i think it is better let end user optionally choose usb controller type15:13
JingYuan3. usb 2.0 and 3.0 controller may improve guest performance as compared to usb 1.1 controller when using usb tablet in windows guest os. I have a statistics about it.15:13
JingYuan4. Some other server actions inlude start, stop, reboot, pause/unpause, suspend/resume, rebuild are not affected by this new feature15:13
JingYuan5. The actions of resize and live migrate may be affected by this new feature15:13
*** chris_hunt has joined #openstack-meeting-315:14
danpb1.  this sounds like a valid RFE to send to  libvirt upstream for specification of host USB devices based on port number15:14
danpb2. yes, we already allow for  hw_scsi image property to choose scsi controller type, so no reason why we can't allow choice of usb controller model with a image property15:15
*** emagana has joined #openstack-meeting-315:15
danpbanother idea we have is to integrate with libosinfo - so you just specify the os_id in the image property and then nova would query libosinfo to find the best USB controller model to use15:16
danpbthat all said, if Win7 can't use  uhci, it could well be a QEMU bug - try reporting the problem to the qemu mailing list and see if they know about it / fix it15:17
danpb3. we should consider whether we enable usb 2 or 3 by default for guests  so we get good performance out of the box15:17
JingYuanI have found a bug about uhci with win7, it was reported in a few years ago, but have no progress by now15:18
*** jbernard has joined #openstack-meeting-315:18
danpbok try just reminding qemu-devel about it - in particular Gerd Hoffmann <kraxel@redhat.com>  is a good person to CC on the mail about USB in QEMU ,since he's active maintainer of this code15:19
JingYuanok, i will connect him15:19
danpb4/5.  libvirt will usually report an error if the virDomainMigrate command is used when the guest config won't migrate. so might want to catch that error and make sure it propagates back to the Nova API in a nice way15:19
danpbJingYuan: thanks for  the info on USB progress15:21
JingYuanThank you very much for your suggestion.15:21
JingYuanI will modify spec and hope you can review them too15:22
*** davlaps has joined #openstack-meeting-315:22
danpbFYI, while reviews will continue, no specs will be approved until Juno-1 snapshot is released15:22
danpbsince we've want a focus on code reviews for next 1+1/2 weeks15:22
danpb#topic Bug Triage15:23
*** openstack changes topic to "Bug Triage (Meeting topic: libvirt)"15:23
danpbnot sure who added this agenda item ?  kashyap was it yours  ?15:23
kashyapdanpb, Hi, yes,15:24
danpbanything you want to say, or were you just reminding us that there are alot of open bugs :-)15:24
kashyapI don't have anything significant to report, I just started triaging this morning again15:24
thomasemWasn't there a suggestion for a triage day each month or something?15:25
kashyapdanpb, I just opened the etherpad, and didn't realize I added it :-)15:25
kashyapthomasem, Tomorrow is Nova bug triage day15:25
*** mrunge has joined #openstack-meeting-315:25
kashyapin #openstack-bugday15:25
thomasemah, gotcha15:25
thomasemneat :)15:26
*** cjellick has joined #openstack-meeting-315:26
danpbok, so guess that's all the agenda items15:26
kashyapThis supposedly "high" bug is15:26
kashyaplanguishing for 8 months - https://bugs.launchpad.net/nova/+bug/122198515:26
kashyapI'm sure we'll have many such I guess, and it's not worth discussing spending time here in this meeting15:26
thomasemkk15:27
*** emagana has quit IRC15:27
*** MaxV has quit IRC15:27
danpb#topic Open Forum15:27
*** openstack changes topic to "Open Forum (Meeting topic: libvirt)"15:27
danpb....any other things people want to raise before we end the meeting...15:27
apmeltonso, I had a quick question about the idmap tool I've been working on15:27
*** emagana has joined #openstack-meeting-315:28
*** MaxV has joined #openstack-meeting-315:28
danpbapmelton: sure, go for it15:28
apmeltonI was planning on just listing it in pypi, and getting it included in nova's requirements, but I'm wondering if it should just be included as a nova util15:28
apmeltonI personally feel that it's useful for more than just nova (or openstack) so pypi might be the best place15:28
danpbi'm fairly ambivalent - going the pypi route is more work for you, but if you want todo that, then go for it15:29
thomasemWhat all's involved there?15:30
danpbi can see how it could be useful for others doing container stuff15:30
thomasemout of curiosity15:30
danpbthomasem: you mean, what does the tool do ?15:30
apmeltonI've already got it in it's own repo, with travis-ci hooked up for tests, just need to get everything set up to get it in pypi15:31
thomasemOh, sorry, no. I'm referring to what's the trouble with going to PyPI :)15:31
thomasemcompared to having it as a nova util15:31
thomasemdanpb ^^15:31
danpbthomasem: well nova util means you just drop one file into the existing git repo15:31
*** tmazur has joined #openstack-meeting-315:31
apmeltongetting it in pypi, getting it approved for our requirements.txt, maintaining it, tagging, etc15:31
danpbpypi means you have to create a new git repo, setup setuptools script, etc, etc15:31
thomasemGotcha15:32
danpbnothing really hard, its just a bit more work15:32
thomasemOkay, I wasn't sure if there was something else. :)15:32
vladikrJust a quick question.. is there a blueprint about integrating with libosinfo? I didn't find any15:32
*** emagana has quit IRC15:32
danpbvladikr: no, nothing beyond what's in my head15:32
thomasemThanks for the explanation15:32
vladikr:)15:32
apmeltonalright, I'm gonna go with the pypi route15:32
danpbshould probably write one at some point :-)15:33
danpbbecause the number of image properties is getting quite large and tedious for users to deal with15:33
alogai've a small question regarding disk drivers and xen15:34
danpbok15:36
alogahttps://github.com/openstack/nova/blob/master/nova/virt/libvirt/utils.py#L45015:37
alogacurrently the disk driver is being selected regarding on the version of the hypervisor15:37
aloga(i'm talking about xen)15:37
alogasince blktap was deprecated in 4.0.0 and blktap2 was the replacement15:37
danpbyes15:38
alogabut it seems that the preferred driver is qdisk (qemu)  http://lists.xen.org/archives/html/xen-devel/2013-08/msg02633.html15:38
alogaand to complete the mess, it seems that libxl is able to select the best driver http://xenbits.xen.org/docs/unstable/misc/xl-disk-configuration.txt15:38
*** tomoe_ has joined #openstack-meeting-315:39
danpbok, so you'd need to find out what version of Xen supports  'qdisk' and also check if libvirt supports use of qdisk with xen driver15:39
alogadanpb: yep, the problem is with the xen management stack15:40
alogaxend (xm) was deprecated in 4.215:40
danpbif qdisk is current recommended driver, then we should be using it in poenstacak15:40
danpbsure, libvirt uses the libxl driver for Xen >= 4.215:40
alogadanpb: but what if the admin selects xm a the toolstack15:41
alogausing xen >= 4.215:41
aloga?15:41
alogais there any way of knowing if the stack being used is xl or xm from libvirt?15:42
danpblibvirt does the right thing15:42
alogadanpb: great then15:42
thomasemI've got to drop off, folks. I'll catch y'all next week! Hopefully I'll have time to poke around the IPv6 issues with LXC. :)15:42
alogai will submit a patch for this asap15:42
alogadanpb: thanks15:42
danpbyou can query libvirt for the driver name - xenlight vs xen15:43
danpbso I think we can wrap up this meeting - thanks for coming everyone. same time/place next week...15:43
danpb#endmeeting15:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:43
openstackMeeting ended Tue Jun  3 15:43:55 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-06-03-15.00.html15:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-06-03-15.00.txt15:43
openstackLog:            http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-06-03-15.00.log.html15:44
*** eghobo has joined #openstack-meeting-315:44
*** lparth has left #openstack-meeting-315:44
*** chris_hunt has left #openstack-meeting-315:45
*** dgenin has left #openstack-meeting-315:45
*** lcheng_ has joined #openstack-meeting-315:46
*** rdopiera has joined #openstack-meeting-315:47
*** nati_ueno has joined #openstack-meeting-315:47
*** JingYuan has quit IRC15:48
*** nati_uen_ has joined #openstack-meeting-315:52
*** jbernard has left #openstack-meeting-315:53
*** nati_ue__ has joined #openstack-meeting-315:53
*** nati_ue__ has quit IRC15:53
*** nati_ue__ has joined #openstack-meeting-315:54
*** nati_ueno has quit IRC15:55
*** Openstack1 has joined #openstack-meeting-315:56
*** nati_uen_ has quit IRC15:57
*** hallyn_ has left #openstack-meeting-315:57
*** santib has joined #openstack-meeting-315:57
*** gary-smith has joined #openstack-meeting-315:57
*** tzumainn has joined #openstack-meeting-315:58
*** thomasem has quit IRC15:58
*** crobertsrh has joined #openstack-meeting-315:58
*** doug-fish has joined #openstack-meeting-315:59
*** nlahouti has joined #openstack-meeting-315:59
*** tqtran has joined #openstack-meeting-315:59
*** amotoki has joined #openstack-meeting-316:00
*** vkmc has joined #openstack-meeting-316:00
*** nlahouti has quit IRC16:01
mrunge#startmeeting16:02
*** Milton has joined #openstack-meeting-316:02
openstackmrunge: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'16:02
mrunge#startmeeting Horizon16:02
openstackMeeting started Tue Jun  3 16:02:07 2014 UTC and is due to finish in 60 minutes.  The chair is mrunge. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: Horizon)"16:02
openstackThe meeting name has been set to 'horizon'16:02
*** nlahouti has joined #openstack-meeting-316:02
mrungegood afternoon16:02
rdopierahello16:02
tzumainnhiya!16:02
tmazurhello everyone o/16:02
davlapso/16:02
akrivokahey16:02
gary-smithhi16:02
lblanchardhi all16:02
santibhi!!16:02
akrivokaeveryone :)16:02
doug-fishhello all16:02
jomarahi16:02
Openstack1hello16:02
*** julim has quit IRC16:02
amotokihi16:02
jcoufalo/16:02
mrungedavid lyle is currently on pto, so I'll chair the meeting16:02
crobertsrhhi16:02
mrungehttps://wiki.openstack.org/wiki/Meetings/Horizon16:03
*** johnma has joined #openstack-meeting-316:03
*** jackib has joined #openstack-meeting-316:03
mrunge#topic project news16:03
*** openstack changes topic to "project news (Meeting topic: Horizon)"16:03
mrungeany news to share?16:03
jrist-afko/16:03
*** jrist-afk is now known as jrist16:04
*** clu_ has joined #openstack-meeting-316:04
*** danpb has left #openstack-meeting-316:04
rdopierathe pyscss patch for global-requirements has been merged :)16:04
doug-fishThe nova guys have been asking a lot about the default quota stuff they took out in icehouse.16:04
mrungehooray rdopiera16:04
doug-fishThey must be getting a lot of grief about it, and it seems that its going back in16:05
rdopieradoug-fish: I've seen a patch that is supposed to restore some views, is that it?16:05
mrungegood news as well16:05
jomarardopiera: nice16:05
doug-fishof course this has led to questions like "Why don't you have better integration tests, so we can know this earlier?"16:05
doug-fish(I think this is where jpich is supposed to post the link to the horizon integration test wiki)16:06
*** hurgleburgler has joined #openstack-meeting-316:06
*** Openstack1 has quit IRC16:06
mrungedoug-fish, I assume you answered: known issue; we're working on this ;-)16:06
crobertsrhI'm still working on the sahara merge.  Next-up is adding some tests for each of the panels.16:06
doug-fishyep16:06
jpichdoug-fish: :)16:07
*** ttrifonov is now known as ttrifonov_zZzz16:07
*** tmazur has quit IRC16:07
mrungecrobertsrh, yes, you have a lot of patches up for review, progress with reviews is still a bit slow16:07
*** clu__ has joined #openstack-meeting-316:08
crobertsrhYes, reviews have been a bit slow to trickle in, but those that we have got have been helpful.16:08
*** clu_ has quit IRC16:08
*** clu__ is now known as clu_16:08
mrungelet's move to the next topic16:09
amotokianother kind of news about stable update.16:09
amotokistable icehouse update is now soft freeze. if any important backport, please send a mail to stable-maint.16:09
mrungeoh yes16:09
amotokilet's move on.16:09
mrunge#topic Horizon split16:10
*** openstack changes topic to "Horizon split (Meeting topic: Horizon)"16:10
mrungerdopiera, I assume, you brought this up?16:10
rdopierayes16:10
mrungehttps://etherpad.openstack.org/p/horizon-split-plan is the linked document16:10
rdopieraI just wanted to mention again that the plan is on the etherpad, at https://etherpad.openstack.org/p/horizon-split-plan16:10
rdopieraand that anybody is free to add to it16:11
rdopieraor raise concerns, etc.16:11
rdopieraanother thing that we have to do before the split, is decide on the name16:11
rdopierait has been raised on the mailing list that django_horizon is not the best choice16:11
mrungeIMHO we should reach out to the mailing list for proposals16:11
rdopieraI wonder what the most effective method of picking the name would be16:11
mrungeI agree here16:12
rdopieraso, an etherpad with the names, and people putting their names next to the ones they like?16:12
mrungecall for proposals? make a list of 3-5 names?16:12
clu_we could have some an online poll after we get some name proposals?16:13
rdopieraand a week from now we count them, and if there are ties, we just pick randomly?16:13
tqtrani highly doubt there will be a tie16:13
*** vladikr has left #openstack-meeting-316:13
mrungeI assume, we could make a poll? does anyone know, how other projects decided about a name?16:13
rdopieratqtran: just in case, to make it quicker :)16:13
mrungeneutron folks here?16:13
tqtranif there is, we can have david flip a coin16:13
*** tmazur has joined #openstack-meeting-316:13
rdopieratqtran: exactly what I meant16:13
amotokimrunge: ?16:14
mrungeamotoki, how was the name change to neutron decided?16:14
akrivokathen we will potentially need a n-sided coin :)16:14
rdopieraI would hate to waste a week for gathering the proposals, and another for voting16:14
mrungequantum - (something I forgot) -> neutron16:14
amotokiwe voted a couple of candidates.16:14
rdopiera2 days for proposals, and until the next meeting for voting, maybe?16:15
amotokionly core member voted at that time.16:15
mrungerdopiera, could you send a mail to the list about name proposals?16:15
tmazurI suggest "mirokolitsa". No one uses this name before, that's win-win! ^^16:16
rdopieramrunge: should we collect them on an etherpad or wiki? because tracking them on e-mails would be error prone16:16
mrunge#todo rdopiera to send a mail to the mailing list, asking for naming proposals16:16
clu_do we want other openstack projects to vote on the name too?16:16
tqtrantmazur: lol what does it mean?16:16
mrungerdopiera, etherpad or wiki: works both for me16:16
gary-smithsorry for the noob question, where to subscribe to the mailing list? I looked around and couldn't find it16:16
*** yamahata has quit IRC16:16
tmazurThat's "horizon" in fake proto slavic :)16:17
amotokiAFAIK, in neutron cases, we have candidate names without copyright problem.16:17
tqtrantmazur: i like! haha16:17
amotokiwhat i am not sure is do we need to check copyright issue before name vote.16:17
tzumainngary-smith, http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev16:17
jpichgary-smith: You can find more information over there -> https://wiki.openstack.org/wiki/MailingLists#Future_Development16:17
rdopieraamotoki: you mean trademark16:17
mrungegary-smith, http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev16:17
amotokiah.... right.16:18
gary-smiththanks, got it16:18
rdopieraamotoki: do you know how one would go about it?16:18
rdopieraamotoki: does openstack have any lawyers who would help?16:18
jpichthe foundation does16:18
amotokirdopiera: i am not sure. markmcclain, former neutron ptl, is the right contact.16:19
amotokiIf you need it, I can send a mail to ask.16:19
rdopieraotoh, if we use something like "horizon-lib", we can be pretty cofident it's safe16:19
rdopieraamotoki: that would be awesome16:19
amotokirdopiera: sure.16:20
mrungeon the other side, it doesn't need to have horizon in the name16:20
rdopieramrunge: right16:20
mrungeas it should be more generic and consumable from the outside, totally unrelated to openstack16:20
rdopieraI just like boring names16:20
mrungesomething like django-generic (or so) ;-)16:20
rdopiera"skyline" is taken already, unfortunately :(16:21
tzumainn"firmament"16:21
*** thomasem has joined #openstack-meeting-316:21
gary-smithwhat's beneath a horizon? an ocean or seabed16:21
rdopieranadir16:21
mrungeproposals to the wiki or etherpad16:21
rdopierayup16:21
rdopieraI will send the e-mail shortly16:22
rdopieraI think we are done with that16:22
mrungeok, then we could start a poll next week?16:22
tqtran"sunrise" or something along the line of horizon?16:22
rdopieramrunge: I wuld want to start it before the weekend16:22
rdopieramrunge: and have the name decided on the next meetings16:22
mrungerdopiera, start the poll before next weekend?16:22
rdopierabut maybe that's unrealistic16:22
mrungemight be a bit tight16:23
rdopierayeah16:23
rdopieraok16:23
rdopieraso poll next week16:23
mrungeyes16:23
rdopierawhich brings me to the next topic16:23
rdopieradates for the split16:23
mrungeyes please16:23
jristskywave?16:23
jrist:)16:23
mrungej-1 will  be cut on june 12th16:23
rdopieraI'm still waiting for some patches to merge, and we will have to depend on some more patches for the requirements16:24
mrungeI think we should do the split shortly after16:24
*** markmcclain has joined #openstack-meeting-316:24
rdopieramrunge: I'm not sure we will be ready16:24
rdopieramrunge: also, how long in advance do we need to set the date for the freeze?16:25
rdopieraand what is the latest date when it still makes sense16:25
rdopieraby June 12 we still won't have the name, for example16:25
mrungerdopiera, not putting any pressure, but j-3 would be too late (imho)16:25
rdopieramrunge: when is that?16:26
mrungerdopiera, good question16:26
mrungeanyone?16:26
*** msundara has joined #openstack-meeting-316:27
jcoufalhttps://wiki.openstack.org/wiki/Juno_Release_Schedule16:27
mrungearound Sept 4th16:27
rdopierathanks16:28
rdopieraok, so we have to do it before that16:28
johnmacan someone explain the process of how this split works. For example, once this split happens how do we coordinate the changes that are still in review that depend on the old code structure?16:29
mrungeyes16:29
rdopierajohnma: the patch queue stays with the current openstack_dashboard16:30
rdopierajohnma: so any changes that touch the current horizon part will become invalid16:30
rdopierajohnma: and will have to be broken up and re-submitted16:30
mrungein fact, most patches in the past have been for openstack-dashboard16:30
rdopierathe /horizon part is mostly a library16:31
rdopieraso the changes there are more general and "global"16:31
mrungerdopiera, do we have an overview on what needs to get merged before?16:31
rdopierait makes sense to make them separately16:31
johnmaaah ok. Thanks for clarifying that.16:31
rdopieramrunge: I will add links to patches to the plan, good idea16:32
*** tomoe_ has quit IRC16:32
mrungegreat, thank you16:32
amotokiperhaps we need to clarfiy the detail process on etherpad and review it in the meeting.16:32
mrungeamotoki, good idea16:33
mrungeanything else to add?16:33
lcheng_does it make sense to have a separate launchpad project too?16:33
mrungehmm, I don't think so16:33
mrungethoughts?16:34
rdopieramrunge: if it will be used by other projects, they will want to report bugs and stuff16:34
mrungea person from the outside can't know, which component is failing/causing issues16:34
lcheng_framework vs content related?  Right now, we do have a separate project for openstack_auth.16:34
rdopieraI think it may make sense to have separate launchpad16:35
rdopierafor the library/framework16:35
mrungewould a tag work as well?16:35
*** alaski has left #openstack-meeting-316:35
mrungea tag #framework or #ui ?16:35
rdopieraor name-of-the-project-that-we-will-come-up-with16:36
mrungeI mean, that would avoid copying bugs from there to there16:37
amotokifor launchpad we can migrate to a separate launchpad project gradually. At first most reports should be from openstack-dashboard.16:37
lcheng_mrunge got a point... From user perspective, it does make it confusing figuring out which project to log the bug or request.16:37
johnmaI second the idea of using a tag with the new name as the tag name16:37
johnmaits easier that way to track bugs and bp16:38
tqtrani also think it might be hard if a bug spans both projects16:38
tqtranthen where do you report it? two different reports? thats confusing....16:38
lcheng_we don't really get bugs logged in openstack_auth right now, mostly bugs comes in horizon project and moved to openstack_auth after triage.16:38
mrungethat's the reason, why we're moving away from launchpad16:39
jpichtqtran: Launchpad lets you open tasks so you can say a bug affects 2 projects within the same report16:39
amotokitqtran: we can add multiple projects for one bug.16:39
tqtranoh right....16:39
amotokiit is a common way to track a bug across multiple projects in openstack.16:39
*** tmazur has quit IRC16:39
mrungecan we move to the next topic?16:40
mrunge#topic django-angular.js16:40
*** openstack changes topic to "django-angular.js (Meeting topic: Horizon)"16:40
mrungewho brought this up?16:41
tqtrani think eric did, but hes not here....16:41
tqtrani'll speak on his behalf =)16:41
mrungethanks16:42
tqtranso the current plan is to provide an alternative way for rendering, mainly client-side using angular16:42
tqtranit will hook nicely into the current django implementation16:42
tqtranand overtime, we can have people jump in to retrofit the django version wth the angular version16:42
tqtraneventually, we end up with everything rendering on client-side, then we can go back and clean out the django rendering logic16:43
mrungethat's about: why we're investigating angular, right?16:43
jpichLink to the current discussion on list as well, started by Veronica Musso: http://lists.openstack.org/pipermail/openstack-dev/2014-June/036488.html16:44
mrungehow comes django-angular into the game?16:44
tqtranthe question is, does this make sense? or are people oppose to removing the django implementation over time? or do we want to keep 2 rendering path for new developers?16:44
rdopieratqtran: I brought it up, because I've seen the discussion on the ML16:44
rdopierabut I don't really have anything to say about it16:45
rdopierasorry16:45
tqtranah...=)16:45
*** julim has joined #openstack-meeting-316:45
rdopieraI thought it might just be good to compare notes16:45
rdopieraand agree where we stand16:45
*** nati_ue__ has quit IRC16:46
mrungeso, this topic is about django-angular (the python package), right?16:46
* jrist is sitting16:46
*** ericpeterson has joined #openstack-meeting-316:46
mrungeso tqtran any thoughts about that?16:46
ericpetersonsorry, late comming16:46
tqtrani would have to read more about it16:48
ericpetersonI am not sure django-angular is critical, but would likely be a good first thing to use.   just having a json centric web layer would be helpful.... no matter if it's angular or something else16:48
mrungeyes, that is my impression as well16:48
ericpetersonand angular seems to have a lot of support among current devs too, which never hurts16:49
mrungesorry guys, I need to run out right now!16:49
*** mrunge has quit IRC16:49
ericpetersonthanks mrunge!16:49
ericpetersonanything else I could help on the subject?  (apologies for the late arrival) ?16:50
jpichLooks like the conclusion on django-angular is "more reading required"? Was there any other items on the agenda?16:50
jpichericpeterson: Did you see the discussion on list? Your input would likely be appreciated there as well16:51
jpichhttp://lists.openstack.org/pipermail/openstack-dev/2014-June/036488.html16:51
jpich#topic Open discussion16:51
amotokiI see "Use mock?" in the agenda. Anything to discuss?16:52
jpichNope, not working. I think only the chair will be able to end the meeting too16:52
*** MaxV has quit IRC16:52
rdopieraamotoki: yes, that's me too16:52
jpichamotoki: I think it was a question about the current status which I believe is "feel free to use mock in future tests, no need to rewrite all the current ones, mox3 should work with python 3 in the future"...?16:52
rdopierathe thing is, mock is not added to requirements.txt in Horizon16:52
rdopieraso can we add it?16:53
rdopierajpich: it is like that in Nova16:53
jpichrdopiera: I guess so? I don't know where the current OpenStack direction is documented16:53
rdopierajpich: but not sure about Horizon16:53
amotokiIMO it is better to avoid two mocking methods in a single project.16:53
*** tmazur has joined #openstack-meeting-316:53
rdopierathe thing is, mox is not really suitable for unit tests16:53
jpichamotoki: mox is confusing enough on its own alright16:54
rdopieramore for acceptance testing and bigger stuff16:54
rdopierait forces you to check everything16:54
rdopierawhile with mock, you can just check the things you care about16:54
rdopieraand not lock the implementation16:54
doug-fishI assume mock is something we'd add to test-requirements.txt right?  and not necessarily require it for production deploys16:54
rdopieradoug-fish: yes16:54
doug-fishsuper16:54
amotokijpich: rdopiera: totally agree with you.  I have experince both.16:55
rdopierait's also in the stdlib in recent pythons16:55
jpichDoes someone fancy starting the discussion the list again, asking for the current status for mocking frameworks in the wider project and where we are documenting this?16:55
jpich*where it is documented16:55
rdopierajpich: ok, I will do that tomorrow16:55
amotokigood idea.16:55
jpichrdopiera: Thank you16:55
*** s3wong has joined #openstack-meeting-316:55
jpichAnything else?16:56
rdopierais there anything we should talk about?16:56
doug-fishJust a minor issue - I think we had discussed using a "docimpact" tag at some point in the past16:57
doug-fishbut I don't think we have been16:57
doug-fishand I can't recall exactly how we were supposed to use it16:57
doug-fishanyone of a link to a wiki describing what we intend?16:57
jpichRight... We should summarise what was discussed in a wiki page16:57
amotokihttps://wiki.openstack.org/wiki/Documentation/DocImpact16:58
jpichThere is the generic page here: https://wiki.openstack.org/wiki/Documentation/DocImpact16:58
jpichThanks amotoki16:58
doug-fishand we need more info about how we are using it in Horizon?16:58
amotokicommits which affect documentation team should have DocImpact flag.16:58
amotokiIMO commits which only affects developer docs don't need DocImpact flag.16:59
jpichamotoki: Because nearly every commit affects the UI in some way it's unclear what requires a DocImpact tag and what doesn't16:59
jpichWe document settings in the dev docs that really should probably belong to the wider project documentation, it is useful to deployers16:59
*** kudva has joined #openstack-meeting-316:59
amotokiit is different from what other projects do.17:00
*** thinrichs has joined #openstack-meeting-317:00
amotokiour time is over...17:00
jpichOk, tbc on that one, I'm not 100% clear on what is appropriate to flag or not either, I would need to reread the logs - I think annegentle had popped up to clarify a few things during that meeting17:00
jpichRight17:00
jpich#endmeeting17:00
rdopierabye17:00
tzumainnthanks all17:00
lblanchardbye all!17:00
jpichfungi: We lost the chair, any chance someone in infra could help us force-end the meeting?17:00
*** gary-smith has left #openstack-meeting-317:00
*** rdopiera has quit IRC17:00
akrivokabye everyone17:00
*** sjcazzol has joined #openstack-meeting-317:00
davlapsbye all!17:00
amotokiI am afraid that only chair can send *endmeeting*.....17:00
*** ericpeterson has left #openstack-meeting-317:00
jristo/17:01
*** skn__ has joined #openstack-meeting-317:01
jristamotoki: try it :)17:01
jcoufalbye bye17:01
tmazurbye all!17:01
*** johnma has left #openstack-meeting-317:01
clu_bye17:01
thinrichsAnyone here for Congress?17:01
*** santib has left #openstack-meeting-317:01
kudvahi this is kudva17:01
skn__Hi thinrichs17:02
banixi here :)17:02
thinrichskudva, skn, banix: hi!17:02
*** tqtran has left #openstack-meeting-317:02
s3wongwe are still in Horizon meeting topic17:02
skn__where is pballand17:02
thinrichs#startmeeting CongressTeamMeeting17:02
pballandhi17:02
openstackthinrichs: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.17:02
fungijpich: it will be endable after an hour17:02
*** sarob has joined #openstack-meeting-317:02
fungiwhich is right about now17:02
fungi#endmeeting17:02
skn__#endmeeting17:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:02
openstackMeeting ended Tue Jun  3 17:02:55 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-06-03-16.02.html17:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-06-03-16.02.txt17:02
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-06-03-16.02.log.html17:03
skn__Oops!17:03
s3wongcool :-)17:03
skn__Soory17:03
fungibetter?17:03
*** tzumainn has left #openstack-meeting-317:03
thinrichsfungi: thanks]17:03
*** rajdeep has joined #openstack-meeting-317:03
fungiyw17:03
*** tmazur has quit IRC17:03
jpichfungi: Thank you!17:03
fungianyone can #endmeeting after an hour of the meeting running17:03
thinrichsfungi: good to know.  Thanks.17:03
*** Milton has quit IRC17:03
thinrichs#startmeeting CongressTeamMeeting17:03
openstackMeeting started Tue Jun  3 17:03:51 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
*** jpich has quit IRC17:04
thinrichslet’s start with last week’s action items.17:04
thinrichsI saw some use cases published to the gdoc.17:04
skn__Yeah, I added a few17:04
thinrichsBut I didn’t get a chance to look at them.17:04
skn__but I have not put them in the main page though17:05
thinrichs#link https://docs.google.com/document/d/1ExDmT06vDZjzOPePYBqojMRfXodvsk0R8nRkX-zrkSw/edit#17:05
*** akrivoka has quit IRC17:05
sarobHere17:06
sarobAdded use cases as well17:06
*** lcheng_ has quit IRC17:06
pballandI’m hoping we can prioritize these somehow17:06
sarobNeed more meat17:06
pballandat least mark some first-priority targets17:06
*** ericpete_ has joined #openstack-meeting-317:07
thinrichsIt might help if for each use case we added some more info.17:07
sarobMy ideas are priority17:07
sarobSolved your problem ;)17:07
thinrichssarob: :)17:07
skn__How many do we have to cover for the initial demo?17:07
thinrichsSuch as (i) what the policy is in Datalog, (ii) what datasources it depends on.17:07
sjcazzolfolks we have define our use case, it is called "Automatic Evacuation on Host Failure"17:08
pballandthinrichs: +117:08
skn__Or, rather want to cover17:08
thinrichsThen we can see if it fits into the policy language and if we have datasource wrappers to cover it.17:08
thinrichssjcazzol: I see the title but not the desc.17:09
sjcazzolI am working on this17:09
sjcazzoltoday I'll complete this17:09
*** hurgleburgler has quit IRC17:09
thinrichssjcazzol: good—just wanted to make sure I wasn’t missing it somewhere.17:09
sjcazzolthinrichs: :)17:09
thinrichsWe should work with sjcazzol to fill in the policy and datasource details I mentioned.17:09
thinrichsAny volunteers?17:10
kudvaSo are you monitoring host condition with Ceilometer17:10
* sarob hand up17:10
thinrichsFor that matter, skn and sarob, would you like help writing Datalog policies too?17:10
sjcazzolkudva: yes17:10
kudvaI can work with you on that17:10
skn__thinrichs: you mean the real policy statements?17:10
thinrichssarob: thanks.17:10
sjcazzolkudva: great17:10
thinrichsskn: yep or at least something close17:10
sarobHmm, what would a datalog policy be?17:11
skn__Got it, yeah I can do some of that17:11
thinrichsLet me find a policy example to point you all at.  Hang on.17:11
sarobI'll keep editing the use case gdoc17:11
kudvathe network example in the congress directory is a good one. but it doesn't connect to monitoring data yet I think17:12
sarobFor prioritization17:12
skn__But I am missing the biger picture, what’s the plan?17:12
sarobWe have two audiences17:12
sarobThe other projects like neutron17:12
skn__sarob: I could work with for priotizing stuffs17:12
sarobAnd the operators17:12
sjcazzolkudva: good, I'll take a look17:13
thinrichskudva is right: congress/examples/private_public_network.classify17:13
sarobWhat's important is going to be diff17:13
thinrichsis a good example of policy17:13
*** jackib has quit IRC17:13
sarobIf incubation is the release cycle goal17:14
*** jackib has joined #openstack-meeting-317:14
sarobThen we need to meet other project needs before operators17:14
skn__thinrichs: the issue is we have to integrate with neutron/nova/etc, and we need some of that capability demo'ed17:15
thinrichsskn: yes.  sarob is articulating what the principles are for prioritizing use cases.17:15
sarobProject policy Interop as the priority17:15
thinrichsI’d imagine the top-priority use cases will make it into the demo.17:15
skn__sarob: agreed17:16
sarobBetter way of saying it17:16
thinrichsOf course, limited by our ability to build those use cases without boiling the ocean17:16
sarobThe gdoc is a good place to boil17:16
thinrichsDo we know which of the use cases in the doc are important for other projects?17:16
sarobNot sure yet17:17
kudvaI think the host evacuation from sjcazzol is simple yet important I think17:17
sarobWe need more water to boil17:17
pballandadding the list of data necessary for each use case will help17:17
kudvaBut needs ceilometer integration17:17
thinrichsI know adrian_otto, who I have yet to track down, added a use case for Solum17:17
sarob I will get Michael still to review the gdoc17:18
skn__I think we should show one of the security use cases combined with neutron17:18
sarobImportant from the source17:18
thinrichsOne way to convince other projects that Congress is useful is to demonstrate use cases where their projects are central to the use case.17:18
sarobAnd Mestery17:18
*** jackib has quit IRC17:19
* mestery is lurking.17:19
sarobSweet17:19
mesteryI'm a fan of Congress. What do you guys need from me?17:19
thinrichsWe need to understand if there are use cases you’d like to see us deliver.17:19
*** emagana has joined #openstack-meeting-317:20
mesterythinrichs: OK, that makes sense.17:20
thinrichsWe’ve been focused on policies that span different OS components, e.g. nova and neutron.17:20
sarobMestery: #link https://goo.gl/RM3W6W17:20
skn__mestery: We have a use case gdoc, if you could take a look at it17:20
*** jackib has joined #openstack-meeting-317:20
mesterysarob thinrichs skn__: Will have a look.17:20
thinrichsmestery: Thanks—any feedback would be great!17:21
banixs3wong: still here?17:21
*** markmcclain has quit IRC17:21
mesterythinrichs: Sure!17:21
s3wongbanix: yes, just lurking though :-)17:21
banixs3wong: mestery I think for Neutron the group policy work may be coming a bit later; we may want to focus on non gp stuff to begin with?17:22
mesterybanix: It's possible, yes, with the goal of having Congress use GBP eventually.17:22
s3wongbanix: oh? is congress moving ahead this quickly? they are ahead of Neutron GP now?17:23
thinrichsbanix: we definitely don’t want to confuse GBP with Congress (that happens a lot).17:23
banixmestery: yes of course that would be the goal but if congress wants to showcase something this cycle that may be a bit difficult17:23
thinrichsI’d say that initially we should focus on non-GBP use cases so people can understand the diff.17:23
banixthinrichs: agree; that should be a good start17:24
*** shakamunyi has quit IRC17:24
skn__mestery, banix: by non group stuffs in Neutron, do you mean generic networking capabilities?17:24
s3wongthinrichs: agreed. a quick glance into your use cases, seems to encompass Nova and Neutron, thus no yet in scope of GBP17:24
banixskn__: yes17:24
skn__banix: ok, thanks17:24
thinrichss3wong: that was part of the goal—to highlight the things Congress does that are diff from gbp and the nova policy work17:25
s3wongthinrichs: great!17:25
thinrichsIf no one has anything else on this, we should move on.  I’ll leave an action item to continue soliciting feedback about how to prioritize use cases wrt OS projects for incubation.17:25
pballandwe also want the use cases to start out using simple, well-understood primitives, and grow over time17:25
skn__thinrichs: agreed17:26
thinrichs#action Everyone will contribute use cases and we will solicit other OS projects’ interest so as to prioritize.17:26
sarobAgreed17:26
* sarob exceelent17:26
skn__so, sarob, thinrichs, and me can work on priotizing?17:26
skn__prioritizing?17:26
sarobGdoc boiling ocean of ideas17:27
skn__oh ok17:27
thinrichsYep17:27
thinrichsMoving on…17:27
thinrichskudva: you’ve been working on builtins for the alpha release.  How’s it going?17:28
thinrichs#link https://review.openstack.org/#/c/95340/17:28
kudvaYou I completed some unit tests which passed, and jenkins as well passed17:28
kudvahttps://review.openstack.org/9708117:28
kudvalatest17:28
kudvathe unit test is called test_builtin.py17:28
kudvahave some tests there, will add more with time (and features added)17:29
kudvaMade all the changes17:29
kudvathat Tim recommended to the congressbuiltin code17:29
thinrichsSounds good.  I’ll follow up via gerrit comments.  I’ve been slammed the last few days.17:29
kudvaokay17:29
kudvahttps://review.openstack.org/9706517:30
kudvaactually that's the last commit17:30
thinrichskudva: thanks for the update17:30
rajdeepkudva it might be easier to update the CL17:30
kudvarajdeep: ok will do17:31
rajdeepwith the changes using --amend17:31
*** ericpete_ has left #openstack-meeting-317:31
thinrichsrajdeep: I saw you added some more tests.  Everything working out there?17:31
skn__thinrichs: do we want to put together some working version withwhatever we have today for alpha? is that the plan?17:31
rajdeepyes ..added test cases for neutron17:32
thinrichsI’ve started looking into mock instead of fakes (as banix mentioned in a review).17:32
rajdeepsome minor pep8 issues but otherwise we have good coverage on both nova and neutron drivers17:32
thinrichsWhat’s the concensus on mock vs. fakes in OS?17:32
rajdeepi used mocks for neutron17:32
sjcazzolmock I think17:33
sjcazzolat least in nova17:33
rajdeepbut stuck to fakes for nova17:33
rajdeepdriver17:33
rajdeepwill eventually move to mocks  i guess17:33
thinrichsrajdeep: sounds like a plan.  I think mocks are better, and it should be easy to port.17:33
thinrichssjcazzol and rajdeep: did you sync up about our Nova coverage?17:34
rajdeepyes, it was easy enough to use them17:34
thinrichsDo we have enough coverage for sjcazzol’s use cases?17:34
rajdeepnot yet17:34
thinrichsMaybe once we get the use case on the gdoc, you two can chat about the details.17:34
rajdeepsjcazzol : it will be great if you can look at the nova driver17:34
rajdeepand give feedback17:35
sjcazzolrajdeep: of course17:35
thinrichsrajdeep: to make that easier, maybe we can describe what data we are currently pulling out of Nova.17:35
thinrichsReading the code for how to convert JSON into tables might be too difficult.17:35
sjcazzolrajdeep: I am delayed because we just define the full scope for the use case17:36
thinrichsNot on IRC—but maybe in a doc17:36
*** nati_ueno has joined #openstack-meeting-317:36
thinrichssjcazzol: a use case hot off the pressess—I like it!17:36
rajdeepok, i will document and send across the doc17:36
thinrichsSounds good.17:37
kudvasjcazzol: would like to see the plan for host evacuation on google doc with dependencies on both nova and monitoring/notifications17:37
thinrichs#action rajdeep will document info exported from nova and touch base with sjcazzol17:37
sjcazzolkudva: yes!17:37
rajdeepsjcazzol what is the best way to contact you offline17:38
*** hurgleburgler has joined #openstack-meeting-317:38
*** sarob has quit IRC17:38
sjcazzolsergio.j.cazzolato@intel.com17:38
skn__What about neutron? Do we already have the data exported from neutron somewhere?17:38
*** eghobo has quit IRC17:39
thinrichsThe code that exports data from neutron is there.  No docs, though.17:39
skn__thinrichs: oh okay.17:40
*** SumitNaiksatam has joined #openstack-meeting-317:40
*** MaxV has joined #openstack-meeting-317:40
thinrichsrajdeep: want to add Neutron to the doc if you have spare cycles?17:40
skn__yeah that would be helpful17:40
*** rajdeep_ has joined #openstack-meeting-317:41
thinrichs(While waiting to hear from rajdeep…) Just a reminder there’s a nova-spec like blueprint avail for everyone to critique.17:42
thinrichshttps://review.openstack.org/#/c/94692/17:42
thinrichsThe plan is to get in the habit of writing these.17:42
rajdeep_sorry got disconnected17:42
*** rajdeep has quit IRC17:42
thinrichsrajdeep: I just asked if you could add Neutron to the doc if you have spare cycles.17:42
rajdeep_which doc?17:43
thinrichsThe one about the datasources we’re exporting that you’re sending to sjcazzol17:43
rajdeep_neutron is already documented https://docs.google.com/document/d/1K9RkQuBSPN7Z2TmKfok7mw3E24otEGo8Pnsemxd5544/edit17:44
rajdeep_i will update this with nova17:44
rajdeep_do you want this in rst format?17:44
thinrichsNot sure I ever saw that before—great!17:45
*** safchain has quit IRC17:46
thinrichsI guess we’ll eventually want it in RST, so we can publish it to users.  Maybe it makes sense to start that now so we don’t dig ourselves into a hole of RST debt?17:47
skn__Yeah, I wanted to see this one, thanks.17:47
thinrichsBut priority 1 is getting it documented so you and sjcazzol can talk17:47
rajdeep_ok sounds good17:48
thinrichsTime check: about 12 min left.17:48
thinrichspballand: you’ve been working on the API, right?  How’s it going?17:48
pballandI’ve got the eventlet wsgi server and DSE (deep6) code running together17:48
pballandthere are some architectural issues there to iron out17:49
pballandno code for review yet17:49
pballandstill working against the spect at https://docs.google.com/document/d/14hM7-GSm3CcyohPT2Q7GalyrQRohVcx77hxEx4AO4Bk/edit#17:49
*** otherwiseguy has quit IRC17:49
pballandonly one comment was to add arbitrary table metadata - if anyone has thoughts on that, it would be helpful to hear17:49
pballandthats about all I have to report17:51
*** emaganap has joined #openstack-meeting-317:51
thinrichsMetadata about cols/tables is sensible.  It’s lower priority than the rest though.17:52
thinrichsrajdeep might have some idea what metadata we would want since the metadata would be useful to people trying to understand what the tables contain.17:53
*** emagana has quit IRC17:53
thinrichspballand: great that we’re making progress here!17:54
pballandI think the proposal was to allow the user to input _anything_17:54
thinrichsShort on time…17:54
pballandso it would be more like an extension17:54
pballandthis can be addressed later17:54
thinrichspballand: not sure if it should be a formal extension or just a change we make after we get the basics in.17:54
thinrichsI’ve been working on integrating DSE, data sources, and the policy engine.17:55
thinrichsHere are some interesting changesets, if anyone is interested...17:55
thinrichsStill works in progress.17:55
thinrichshttps://review.openstack.org/#/c/93143/  (basic integration)17:55
thinrichshttps://review.openstack.org/#/c/96978/  (make datasources poll -- unfinished)17:55
thinrichshttps://review.openstack.org/#/c/95966/  (toplevel integration -- unfinished)17:55
skn__thinrichs: thanks.17:55
skn__when do we target to tentatively have an alpha?17:56
thinrichsI’ve got a few other changes in review.  The changes above are all dependent on those.17:56
thinrichsskn: as soon as we can manage to get the pieces all put together.17:56
thinrichsSpeaking of which, we don’t have plans for a python-client.  Anyone think that’s important for the alpha?17:56
skn__thinrichs: oh ok, its ASAP then :)17:57
thinrichsOr I should say important enough to delay the alpha?17:57
thinrichsAnd since we’re rapidly running out of time, chime in with other issues we haven’t covered yet.17:57
banixif no cient, then rest api is the interface only?17:57
skn__may be dicuss about this python client in the next meeting17:58
thinrichsskn__: good suggestion17:58
thinrichsbanix: the “alpha” is just something that people can use to kick the tires.17:58
thinrichsWe want early feedback on this to see what real users actually want.17:58
banixthinrichs: ok but how will they use it?17:59
thinrichsbanix: the REST interface — wget or whatever17:59
*** mrunge has joined #openstack-meeting-317:59
banixthinrichs: ok thx17:59
*** rajdeep_ has quit IRC17:59
*** skn__ has left #openstack-meeting-318:00
thinrichsTimes up for this week.18:00
banixbye18:00
thinrichsThis was a good meeting!  See you all next week (or on gerritt/email)!18:00
thinrichs#endmeeting18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
openstackMeeting ended Tue Jun  3 18:01:02 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-06-03-17.03.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-06-03-17.03.txt18:01
sjcazzolbye18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-06-03-17.03.log.html18:01
*** emaganap has quit IRC18:01
*** sjcazzol has left #openstack-meeting-318:02
*** nati_ueno has quit IRC18:02
*** nati_uen_ has joined #openstack-meeting-318:02
*** emagana has joined #openstack-meeting-318:03
*** nlahouti has quit IRC18:03
*** ndipanov has quit IRC18:04
*** thinrichs has quit IRC18:04
*** julim has quit IRC18:05
*** kudva has quit IRC18:07
*** julim has joined #openstack-meeting-318:07
*** Sukhdev has joined #openstack-meeting-318:22
*** emagana has quit IRC18:28
*** emagana has joined #openstack-meeting-318:28
*** SumitNaiksatam has quit IRC18:31
*** mrunge has quit IRC18:34
*** nati_uen_ has quit IRC18:39
*** nati_ueno has joined #openstack-meeting-318:39
*** Youcef has quit IRC18:41
*** msundara has quit IRC18:43
*** krotscheck has quit IRC18:45
*** krotscheck has joined #openstack-meeting-318:46
*** pballand has quit IRC18:48
*** nati_ueno has quit IRC18:53
*** otherwiseguy has joined #openstack-meeting-318:54
*** nati_uen_ has joined #openstack-meeting-318:55
*** otherwiseguy has quit IRC18:59
*** pballand has joined #openstack-meeting-319:00
*** bauzas has quit IRC19:01
*** Alex_Gaynor has joined #openstack-meeting-319:01
*** otherwiseguy has joined #openstack-meeting-319:01
Alex_GaynorHi all.19:01
Alex_Gaynorbriancurtin can't make today's meeting, so I'll take over for him, except I don't know how to work the bot :-)19:02
*** emagana has quit IRC19:02
*** terrylhowe has joined #openstack-meeting-319:02
Alex_Gaynor#startmeeting python-openstacksdk19:02
openstackMeeting started Tue Jun  3 19:02:36 2014 UTC and is due to finish in 60 minutes.  The chair is Alex_Gaynor. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: python-openstacksdk)"19:02
openstackThe meeting name has been set to 'python_openstacksdk'19:02
Alex_GaynorOk, I guess we'll do roll call to get started :-)19:03
Alex_GaynorAlex Gaynor, Rackspace (filling in for briancurtin today)19:03
*** alexpilotti has quit IRC19:03
*** alexpilotti has joined #openstack-meeting-319:03
terrylhoweTerry Howe HP19:03
Alex_GaynorAnyone else? Bueller?19:04
jamielennoxJamie Lennox - Red Hat19:04
Alex_GaynorOk, we'll give it a minute to see if anyone else tickles in19:05
*** otherwiseguy has quit IRC19:05
Alex_GaynorOkey doke, I guess we'll just go short handed.19:07
Alex_GaynorI dont' have a particular agenda for today, we got a few PRs, including teh auth one, landed last week, so that's pretty great.19:07
edleafeEd Leafe, Rackspace (running late)19:07
Alex_Gaynorterrylhowe: Do you want to walk us through the remaining outstanding CRs?19:08
terrylhowehttps://review.openstack.org/#/c/94887/19:09
Alex_Gaynor#link https://review.openstack.org/#/c/94887/19:09
terrylhowethe most important outstanding one I guess, waiting on Dean, but I think he is AFK most of this week19:09
*** emagana has joined #openstack-meeting-319:10
terrylhoweI agree with jamielennox comment, but waiting on Dean19:11
*** hurgleburgler has quit IRC19:11
Alex_GaynorDoes that make us totally blocked until Dean returns?19:11
jamielennoxterrylhowe: i think if you make my change, then we pass it without him19:11
jamielennoxhe can come back through and fix it later19:11
*** alexpilotti has quit IRC19:11
terrylhowethat would unblock some others19:12
jamielennox++19:12
Alex_GaynorUnblocking sounds good :-)19:12
terrylhoweI wanted to throw exceptions on 4xxs etc though, not sure how everyone felt about that19:13
Alex_GaynorI'm +1 on defaulting to exceptions on non-{2xx,3xx} responses19:14
Alex_GaynorA nickel for every ValueError: malformed JSON because I tried to parse an HTML 500 :-)19:14
jamielennoxterrylhowe: i agree, though in my case i had to add a raise_exc=True param by default to make it optional19:14
*** emagana has quit IRC19:14
jamielennoxhopefully we shouldn't need it here19:15
terrylhoweokay19:15
terrylhowe#link https://review.openstack.org/#/c/96436/19:16
terrylhoweI don’t think anyone disagrees19:16
Alex_GaynorLooks like it needs to be rebased, because of a merge conflict19:16
*** bauzas has joined #openstack-meeting-319:17
Alex_GaynorI'm happy to +A it once it is19:17
*** emagana has joined #openstack-meeting-319:18
terrylhowe#link https://review.openstack.org/#/c/96437/19:18
terrylhoweis next19:18
Alex_GaynorHow does this affect the "root" identity service?19:18
terrylhowealso needs rebasing19:19
terrylhoweI’ve had the auth stuff working without using base_url19:19
jamielennoxAlex_Gaynor: once there is an auth plugin you just get the url from there19:19
terrylhoweI was going to check in some example code later today or tomorrow19:19
Alex_GaynorOk, cool19:20
jamielennoxkeystone is in the service catalog as well19:20
terrylhowe#link https://review.openstack.org/#/c/96604/19:21
jamielennoxthat was failing because of the setuptools bug19:22
Alex_GaynorStraightforward +2. I only didn't because all  tests were failing, will +A now19:22
jamielennoxshould be able to be rechecked now19:22
Alex_GaynorAll of zuul is having a bad time now, but that's a different issue19:22
jamielennoxAlex_Gaynor: right, this is the most backed up i think i've seen it19:23
terrylhowe#link https://review.openstack.org/#/c/96513/19:24
terrylhoweSession docs, needs probably more careful consideration edleafe maybe?19:24
edleafeterrylhowe: I've been pulled in other directions the last few weeks, so haven't had time to do many reviews19:26
*** otherwiseguy has joined #openstack-meeting-319:26
terrylhoweyeh, I figued so19:27
*** s3wong_ has joined #openstack-meeting-319:27
terrylhoweanyway, session docs aren’t so important19:27
*** s3wong_ has quit IRC19:27
*** s3wong has quit IRC19:29
terrylhoweIf we are all done with that for now19:30
terrylhowe#link https://review.openstack.org/#/c/96516/19:30
terrylhoweThat was a test authenticator19:30
*** otherwiseguy has quit IRC19:30
terrylhoweI have some reswizzling I wanted to do in the example code that is going to follow this19:31
terrylhowewhere each component would have their own test file to avoid conflicts19:31
terrylhowetransport, session, authenticate, …19:31
terrylhowethat is next though19:32
*** otherwiseguy has joined #openstack-meeting-319:32
jamielennoxany reason to have the test authenticator run via env variables?19:33
jamielennoxisn't it easier to just have a basic one that takes those params on __init__19:33
terrylhoweyeh, that might be better jamielennox the only reason I added was inspiration from the session docs19:34
jamielennoxjust thinking if you want to use that from elsewhere (other examples) you then need to mess with envs19:35
*** otherwiseguy has quit IRC19:36
Alex_Gaynorseems reasonable to me19:36
terrylhowewell, feel free to -1 that one and I’ll come up with something better19:39
jamielennoxdone19:40
terrylhoweAlex_Gaynor: that is it for me19:40
Alex_GaynorThank you.19:40
jamielennox#link https://review.openstack.org/#/c/9625319:40
jamielennoxis Alex's19:40
*** MaxV has quit IRC19:41
terrylhowePetr is technically correct, not sure if I care though19:41
jamielennoxkind of agree you shouldn't put that requirements change in there - but not fussed19:41
jamielennox:)19:41
Alex_GaynorI can move that to a seperate PR.19:41
Alex_GaynorAnyone know where the babel thing came from?19:41
*** MaxV has joined #openstack-meeting-319:41
*** jackib has quit IRC19:41
Alex_GaynorI know what babel is, but we don't use it anywhere as far as I know19:41
jamielennoxit's in everything19:41
terrylhoweno idea here19:41
jamielennoxi assume we probably got it from boilerplate19:42
Alex_Gaynorah, from cookiecutter19:42
terrylhowejust approve it and be done I think19:43
jamielennoxyea, i'm ok19:43
jamielennoxactually you can edit commit messages from gerrit now19:44
*** otherwiseguy has joined #openstack-meeting-319:44
jamielennoxso tag on 'Remove babel - wtf' and we'll just do it19:44
Alex_Gaynordone19:45
jamielennoxand done19:46
*** MaxV has quit IRC19:47
*** MaxV has joined #openstack-meeting-319:47
*** otherwiseguy has quit IRC19:48
*** emaganap has joined #openstack-meeting-319:48
Alex_GaynorOk, I don't have any other outstanding business. ANyone else have stuff they want to bring up?19:49
jamielennoxin case it's useful to others i added this to bookmarks toolbar, so hopefully keep on top of reviews a bit better now19:49
jamielennoxhttps://review.openstack.org/#/q/project:stackforge/python-openstacksdk+label:Code-Review%253D0%252Cuser%253Dself+is:open+NOT+owner:self,n,z19:49
*** emagana has quit IRC19:50
jamielennoxbut otherwise, nice work terrylhowe19:51
terrylhowethanks19:52
terrylhoweI have nothing else19:52
Alex_GaynorCheers then, I guess we're done a few minutes early.19:52
Alex_GaynorThanks for coming everyone!19:52
*** jackib has joined #openstack-meeting-319:53
edleafeAlex_Gaynor: don't forget #endmeeting19:53
Alex_Gaynoredleafe: thanks19:53
Alex_Gaynor#endmeeting19:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:54
openstackMeeting ended Tue Jun  3 19:54:00 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-06-03-19.02.html19:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-06-03-19.02.txt19:54
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-06-03-19.02.log.html19:54
*** jamielennox has left #openstack-meeting-319:54
*** Alex_Gaynor has left #openstack-meeting-319:55
*** zehicle_at_dell has joined #openstack-meeting-319:56
*** otherwiseguy has joined #openstack-meeting-319:58
*** otherwiseguy has quit IRC20:02
*** davlaps has quit IRC20:03
*** devlaps has quit IRC20:03
*** jtomasek has quit IRC20:03
*** otherwiseguy has joined #openstack-meeting-320:06
*** sarob has joined #openstack-meeting-320:07
*** otherwiseguy has quit IRC20:11
*** lblanchard has quit IRC20:12
*** pballand has quit IRC20:14
*** jcoufal has quit IRC20:15
*** MaxV_ has joined #openstack-meeting-320:15
*** alexpilotti has joined #openstack-meeting-320:15
*** hurgleburgler has joined #openstack-meeting-320:17
*** devlaps has joined #openstack-meeting-320:17
*** davlaps has joined #openstack-meeting-320:17
*** terrylhowe has left #openstack-meeting-320:17
*** MaxV has quit IRC20:18
*** lcheng_ has joined #openstack-meeting-320:21
*** Sukhdev has quit IRC20:22
*** nati_uen_ has quit IRC20:28
*** otherwiseguy has joined #openstack-meeting-320:32
*** apmelton has left #openstack-meeting-320:34
*** otherwiseguy has quit IRC20:36
*** julim has quit IRC20:37
*** crobertsrh has left #openstack-meeting-320:41
*** mrunge has joined #openstack-meeting-320:45
*** nati_ueno has joined #openstack-meeting-320:47
*** jackib has quit IRC20:49
*** otherwiseguy has joined #openstack-meeting-320:49
*** otherwiseguy has quit IRC20:53
*** nati_uen_ has joined #openstack-meeting-321:00
*** nati_ueno has quit IRC21:00
*** igordcard has joined #openstack-meeting-321:03
*** dhellmann has quit IRC21:11
*** otherwiseguy has joined #openstack-meeting-321:12
*** dhellmann has joined #openstack-meeting-321:13
*** armax_ has joined #openstack-meeting-321:15
*** armax has quit IRC21:15
*** armax_ is now known as armax21:15
*** otherwiseguy has quit IRC21:16
*** otherwiseguy has joined #openstack-meeting-321:19
*** otherwiseguy has quit IRC21:23
*** jamie_h has quit IRC21:25
*** safchain has joined #openstack-meeting-321:25
*** mrunge has quit IRC21:27
*** mfer has quit IRC21:35
*** emaganap has quit IRC21:39
*** emagana has joined #openstack-meeting-321:42
*** otherwiseguy has joined #openstack-meeting-321:49
*** zehicle_at_dell has quit IRC21:52
*** nati_uen_ has quit IRC21:54
*** armax has left #openstack-meeting-321:57
*** mwagner_lap has quit IRC22:02
*** nati_ueno has joined #openstack-meeting-322:02
*** sarob has quit IRC22:04
*** sarob has joined #openstack-meeting-322:06
*** emagana has quit IRC22:06
*** emagana has joined #openstack-meeting-322:06
*** emaganap has joined #openstack-meeting-322:07
*** sarob has quit IRC22:10
*** emagana has quit IRC22:10
*** alexpilotti has quit IRC22:12
*** doug-fish has left #openstack-meeting-322:15
*** emaganap has quit IRC22:16
*** SumitNaiksatam has joined #openstack-meeting-322:20
*** nati_ueno has quit IRC22:24
*** bauzas has quit IRC22:25
*** sarob has joined #openstack-meeting-322:29
*** thomasem has quit IRC22:30
*** nati_ueno has joined #openstack-meeting-322:32
*** zehicle_at_dell has joined #openstack-meeting-322:39
*** jgrimm has quit IRC22:44
*** nati_uen_ has joined #openstack-meeting-322:47
*** nati_ueno has quit IRC22:50
*** peristeri has quit IRC22:59
*** carl_baldwin has quit IRC22:59
*** TravT has quit IRC22:59
*** igordcard has quit IRC23:11
*** tomoe_ has joined #openstack-meeting-323:16
*** banix has quit IRC23:18
*** safchain has quit IRC23:19
*** DinaBelova2 has joined #openstack-meeting-323:20
*** ruhe has quit IRC23:20
*** DinaBelova has quit IRC23:20
*** DinaBelova2 is now known as DinaBelova23:20
*** rossella_s has quit IRC23:20
*** ruhe2 has joined #openstack-meeting-323:20
*** rossella has joined #openstack-meeting-323:20
*** rossella is now known as rossella_s23:20
*** ruhe2 is now known as ruhe23:20
*** devlaps1 has joined #openstack-meeting-323:47
*** devlaps has quit IRC23:49
*** devlaps1 has quit IRC23:50
*** davlaps has quit IRC23:50
*** otherwiseguy has quit IRC23:51
*** devlaps has joined #openstack-meeting-323:51
*** devlaps1 has joined #openstack-meeting-323:51
*** MaxV_ has quit IRC23:55
*** devlaps2 has joined #openstack-meeting-323:58

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