Monday, 2017-03-06

*** bobmel has joined #openstack-meeting-400:05
*** sp_ has quit IRC00:05
*** bobmel has quit IRC00:10
*** sp_ has joined #openstack-meeting-400:19
*** amotoki has joined #openstack-meeting-400:27
*** limao has joined #openstack-meeting-400:32
*** tonytan_brb has joined #openstack-meeting-400:36
*** tonytan4ever has quit IRC00:39
*** yifei has joined #openstack-meeting-400:53
*** salv-orlando has joined #openstack-meeting-400:53
*** salv-orlando has quit IRC00:54
*** salv-orlando has joined #openstack-meeting-400:54
*** salv-orl_ has quit IRC00:55
*** markvoelker has joined #openstack-meeting-400:56
*** dave-mccowan has joined #openstack-meeting-401:00
*** SerenaFeng has joined #openstack-meeting-401:01
*** tovin07 has joined #openstack-meeting-401:08
*** yamamoto_ has joined #openstack-meeting-401:10
*** zhurong has joined #openstack-meeting-401:15
*** yamamoto_ has quit IRC01:21
*** yamamoto_ has joined #openstack-meeting-401:25
*** yfauser has joined #openstack-meeting-401:26
*** yamamoto_ has quit IRC01:29
*** yamamoto_ has joined #openstack-meeting-401:29
*** yfauser has quit IRC01:31
*** yamamoto_ has quit IRC01:39
*** dave-mccowan has quit IRC01:40
*** woodard has joined #openstack-meeting-401:43
*** julim_ has quit IRC01:45
*** woodard has quit IRC01:47
*** gongysh has joined #openstack-meeting-402:05
*** zhurong has quit IRC02:15
*** zhurong has joined #openstack-meeting-402:19
*** dave-mccowan has joined #openstack-meeting-402:29
*** yfauser has joined #openstack-meeting-402:31
*** lei-zh has joined #openstack-meeting-402:32
*** yfauser has quit IRC02:35
*** yamamoto_ has joined #openstack-meeting-402:36
*** necuser__ has quit IRC02:38
*** chigang has joined #openstack-meeting-402:42
*** woodard has joined #openstack-meeting-402:43
*** woodard has quit IRC02:48
*** necuser__ has joined #openstack-meeting-402:50
*** bobmel has joined #openstack-meeting-403:05
*** janonymous has joined #openstack-meeting-403:06
*** thorst has quit IRC03:08
*** bobmel has quit IRC03:10
*** huangtianhua has joined #openstack-meeting-403:17
*** chatter29 has joined #openstack-meeting-403:19
*** chatter29 has quit IRC03:19
*** tiantian has quit IRC03:20
*** sp_ has quit IRC03:23
*** yfauser has joined #openstack-meeting-403:32
*** sp_ has joined #openstack-meeting-403:36
*** yfauser has quit IRC03:37
*** yfauser has joined #openstack-meeting-403:48
*** SerenaFeng has quit IRC03:51
*** yfauser has quit IRC03:53
*** dave-mccowan has quit IRC04:03
*** spotz_zzz is now known as spotz04:13
*** markvoelker has quit IRC04:23
*** thorst has joined #openstack-meeting-404:28
*** thorst has quit IRC04:28
*** SerenaFeng has joined #openstack-meeting-404:36
*** woodard has joined #openstack-meeting-404:45
*** chigang has quit IRC04:49
*** psachin has joined #openstack-meeting-404:49
*** woodard has quit IRC04:49
*** SerenaFeng has quit IRC05:04
*** limao has quit IRC05:15
*** limao has joined #openstack-meeting-405:15
*** markvoelker has joined #openstack-meeting-405:24
*** SerenaFeng has joined #openstack-meeting-405:27
*** SerenaFeng has quit IRC05:28
*** markvoelker has quit IRC05:29
*** thorst has joined #openstack-meeting-405:29
*** bobmel has joined #openstack-meeting-405:32
*** thorst has quit IRC05:34
*** bobmel has quit IRC05:37
*** amotoki_ has joined #openstack-meeting-405:42
*** psachin has quit IRC05:42
*** amotoki has quit IRC05:46
*** woodard has joined #openstack-meeting-405:47
*** yfauser has joined #openstack-meeting-405:50
*** tonytan_brb has quit IRC05:51
*** woodard has quit IRC05:51
*** yfauser has quit IRC05:57
*** yfauser has joined #openstack-meeting-406:07
*** yfauser has quit IRC06:11
*** mohankumar has joined #openstack-meeting-406:16
*** SerenaFeng has joined #openstack-meeting-406:22
*** alexchadin has joined #openstack-meeting-406:26
*** SerenaFeng has quit IRC06:27
*** yfauser has joined #openstack-meeting-406:29
*** thorst has joined #openstack-meeting-406:30
*** thorst has quit IRC06:34
*** nkrinner_afk is now known as nkrinner06:36
*** SerenaFeng has joined #openstack-meeting-406:38
*** markvoelker has joined #openstack-meeting-406:44
*** unicell has joined #openstack-meeting-406:45
*** woodard has joined #openstack-meeting-406:47
*** janki has joined #openstack-meeting-406:48
*** woodard has quit IRC06:51
*** salv-orl_ has joined #openstack-meeting-406:53
*** salv-orlando has quit IRC06:56
*** pcaruana has joined #openstack-meeting-406:58
*** pcaruana has quit IRC07:05
*** pcaruana has joined #openstack-meeting-407:06
*** 7GHAAG5MM is now known as irenab_07:30
*** ltomasbo|away is now known as ltomasbo07:31
*** ralonsoh has joined #openstack-meeting-407:40
*** woodard has joined #openstack-meeting-407:48
*** unicell has quit IRC07:51
*** woodard has quit IRC07:53
*** alexchadin has quit IRC07:59
*** alexchadin has joined #openstack-meeting-408:00
*** tovin07 has quit IRC08:12
*** tovin07 has joined #openstack-meeting-408:12
*** karthiks has joined #openstack-meeting-408:16
*** gibi has joined #openstack-meeting-408:17
*** thorst has joined #openstack-meeting-408:32
*** bauwser is now known as bauzas08:34
*** thorst has quit IRC08:36
*** woodard has joined #openstack-meeting-408:49
*** markvoelker_ has joined #openstack-meeting-408:51
*** woodard has quit IRC08:53
*** markvoelker has quit IRC08:54
oanson#startmeeting Dragonflow09:00
openstackMeeting started Mon Mar  6 09:00:17 2017 UTC and is due to finish in 60 minutes.  The chair is oanson. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: Dragonflow)"09:00
openstackThe meeting name has been set to 'dragonflow'09:00
*** yamamoto_ has quit IRC09:00
*** nick-ma has joined #openstack-meeting-409:00
xiaohhuihello09:00
nick-maHello09:00
oansonnick-ma, xiaohhui, hi09:00
lihiHi09:00
dimakHello09:00
oansonWe'll wait another minute to let everyone join09:01
irenab_hi09:01
*** ishafran has joined #openstack-meeting-409:02
* yuvalb observes quietly09:02
oansonAll right. I guess we can start09:02
oanson#info xiaohhui nick-ma lihi dimak irenab ishafran in meeting09:03
oanson#info yuvalb observing meeting09:03
oanson#topic Roadmap09:03
*** openstack changes topic to "Roadmap (Meeting topic: Dragonflow)"09:03
oansonWe have a few lay-overs from Ocata into Pike. Actually it's all the big stuff09:03
*** itamaro has joined #openstack-meeting-409:04
oansonIPv6 - lihi, I understand that we're just missing the fullstack test and we're go?09:04
lihiyes, The ping pong and the rest of the test are almost done. Will be up today09:04
oansonGreat!09:05
lihi(however be prepared for another 300~ seconds test to the ci)09:05
oansonWe'll have to see. If it is getting too long, maybe we'll split the gate jobs - one for flow based, and one for end-to-end based tests09:05
oansonBut that's a long way ahead.09:05
oansonNB refactor - It is almost complete. We have also started porting models over.09:06
oansonGive me a second to find the right etherpad :)09:06
dimakI have some reservations on tests that check flows are there09:06
dimakhttps://etherpad.openstack.org/p/df-refactor-models09:06
dimakoanson, ^^09:06
oanson#link Model porting status https://etherpad.openstack.org/p/df-refactor-models09:07
xiaohhuiIt is free to pick the porting job, right? I would like to play with one or two models.09:07
oansonSo Chassis was already ported.09:07
oansonYes09:07
xiaohhuiGreat!09:08
oansonxiaohhui, I think the router stuff is free.09:08
oansonNote that lport relies on lswitch, subnet, and secgroups09:08
xiaohhuiI will check the router.09:08
oansonI did most of the work on lswitch and subnet, and I want to assign secgroups to lihi09:09
lihiSure09:09
oansonlihi mentioned that she wants to review the sg app, so it would work well together09:09
oansonPlease add yourselves to the list.09:09
*** nick-ma has quit IRC09:09
xiaohhuiDone09:10
oansonThanks09:10
lihialso done09:10
oansonsNAT - there is a patch up. It looks ready for review. I tested an earlier version and it seems to work09:10
oanson#link snat patch https://review.openstack.org/#/c/431422/09:11
ishafranAll comments are addressed, including fulstack test09:11
oansonishafran, cool. Thanks!09:11
irenab_oanson, once I verify, will post +109:11
oansonirenab_, great. Thanks!09:12
oansonChassis/Service health - rajivk informed me that he was pulled from Dragonflow, so someone has to take over that one09:12
oansonIt's interesting for the feature itself, and for the Service base class09:12
oansonDo we have any volunteers?09:12
xiaohhuiI think I can take it09:12
oansonxiaohhui, great. Thanks!09:13
oanson#link Added support for service status reporting https://review.openstack.org/#/c/415997/09:13
xiaohhuiGot it.09:13
oansonTAPaaS is frozen for now. Since it's not a major feature, I suggest we put it on hold.09:13
oansonUnless there are objections?09:13
oansonAll right.09:14
*** d0ugal has quit IRC09:14
oansonRegarding API, once the migration to new NB models is partly complete, we can start testing the autogenerated API.09:15
oansonirenab_, this one is on you?09:15
*** joedborg has joined #openstack-meeting-409:15
irenab_irenab, ok09:15
irenab_oanson, ok09:15
oansonCool. Thanks!09:15
oansonNew features for Pike:09:16
oansonVLAN over VMs - I'm taking this one. I uploaded a WIP patch, but it relies on the migration of lport to NB models.09:16
irenab_oanson, when do you think it will be possible to experiment with this?09:17
oansonirenab_, I am hoping in 2 weeks.09:17
oansonIt mostly depends on how well the migration goes.09:17
irenab_cool, thanks09:17
dimakoanson, s/over/aware/09:17
oansondimak, sorry?09:18
oansondimak, Yes.09:18
oansonVLAN *aware* VMs.09:18
oansonRPM packaging - I have met with the packaging people in the PTG. Their very nice. They told me where to start and what to do09:18
oansondimak, you're taking this, right?09:19
dimakYes09:19
dimakI've started tinkering with it a bit but it'll take some time until I have some progress to show09:19
oansondimak, sure.09:19
oansonThere's also the SFC on you, so no rush.09:20
oansonNext is puppet deployment, which will also be used for TripleO deployment. lihi, this one is on you, right?09:20
lihiYes.09:20
oansonWe should also have a multinode gate test. I spoke with infra about that too. It doesn't seem to complex, but it will need a carrier.09:21
*** neiljerram has joined #openstack-meeting-409:22
oansonWe should also have a get for the ansible deployment. But the ansible deployment is broken :(.09:22
oansonOnce the ansible deployment works again, it shouldn't be a problem to add the gate to our list09:22
oansonThere are also goals for LBaaS and documentation, but I think we're out of hands at the moment, so let's wait with those until we cleared the queue a bit.09:23
oansonI'll make an etherpad with a summary of all this, and publish it in the channel and next meeting (and add it to the agenda)09:23
oansonThis is acceptable to everyone? Anything that should be pushed forwards and isn't?09:24
*** nick-ma has joined #openstack-meeting-409:24
dimakYou missed the SFC part :P09:24
oansonbtw LBaaS hopefully will be a collaboration effort with octavia team.09:24
dimakIts getting quite ready, so I'd love some input09:24
oansondimak, sure09:24
irenab_oanson, please also update on interop09:25
itamaroI'd like to discuss the idea of making the ICMP and TTL mgmt as a sparate app09:25
oansonirenab_, I don't have all the information of the top of my head. If someone can fill in, that would be great.09:25
irenab_oanson, maybe some summary later based on the info you got during PTG09:26
oansonSure. I'll put it in the channel09:26
*** d0ugal has joined #openstack-meeting-409:26
*** d0ugal has quit IRC09:26
*** d0ugal has joined #openstack-meeting-409:26
oansonitamaro, sure, go ahead09:26
itamaroI mainly think that DNAT should only do DNAT09:27
itamaroand all L3 related functions such as ICMP and TTL moved to a dediicated application09:28
xiaohhuiWhat if user don't add l3 app, how will the dedicated application work?09:29
itamarodependecy.09:30
itamaroIt should depend on the ecistence of either DNAT/L309:30
itamaroit also can depend on exiting flows in a dedicated table09:31
oansonitamaro, will the ICMP/TTL app behave the same under a different L3/dNAT/sNAT implementation?09:31
dimakMaybe it can be something installable like an arp responder?09:32
*** joedborg has quit IRC09:32
itamaroIt should, but need to investigate in order to provide a common functionality09:32
xiaohhuiThe message generation should be the same, but details should be different.09:32
itamarodimak -> yes09:32
*** thorst has joined #openstack-meeting-409:33
itamaroagree09:33
itamarowith xiaohhui09:33
oansonThe ICMP generation is already in a library09:33
dimakHave an app that monitors packet_in from a specific table, then add installable redirector09:33
oansonMaybe just move the ICMP inner-NATting code to the library as well?09:33
oansondimak, applications already register to packet-in from a specific table09:34
xiaohhuiresponder might not be feasible. The packet construction is too complex for a rule in OpenFlow.09:34
dimakNo I meant that you have a ttl responder app09:34
dimakand ttl responder redirector that route ttl=0 packets to app's table with some reg to note what app did it09:35
itamaroI agree with both dimak's suggestions09:35
*** joedborg has joined #openstack-meeting-409:35
oansondimak, OVS sends a packet-in message automatically if the TTL hits 0. This way we don't have to detect it manually09:35
oansonWe can add code to detect the event and move it to a specified application, rather than by table number09:36
oanson(Like the code that exists today in L3)09:36
dimakWe'll need to figure it out, maybe match on ttl=1 prematurely09:36
dimakThats also a possibility09:37
*** nick-ma_ has joined #openstack-meeting-409:37
oansonI think letting OVS do the filtering for us is better - less error-prone.09:37
*** thorst has quit IRC09:37
xiaohhuiit looks like ryu doesn't provide ttl match, thought it is supported in ovs09:37
dimakI think if we decide to tackle it we can come up with a way to consolidate all the treatment into a designated app09:37
xiaohhuithought -> though09:37
itamaroxiao, dimak would u like to take it together with me09:38
dimakitamaro, sure09:38
xiaohhuisure, I will review the code, if it comes up.09:39
oansonitamaro, dimak, xiaohhui, in your solution, please try to use OVS's automatic TTL expiry detection method. I'd rather not maintain a heuristic for something that OVS gives us for free09:39
dimak+109:39
*** SerenaFeng has quit IRC09:39
oansonAnd this way we don't need ryu's missing ttl matching support09:40
oansonitamaro, this one's on you :)09:40
*** nick-ma__ has joined #openstack-meeting-409:40
itamarook09:40
xiaohhuiI agree with oanson, that is also an feature described in openflow 1.3 spec. We should use it.09:40
*** nick-ma has quit IRC09:40
oansonGreat.09:41
oansonAnything else for roadmap?09:41
*** nick-ma_ has quit IRC09:41
oanson#topic Open Discussion09:42
*** openstack changes topic to "Open Discussion (Meeting topic: Dragonflow)"09:42
itamaroI wanted to talk about the app  tag feature09:42
oansonitamaro, sure, go ahead09:42
itamaroI have tried to do a full stack test. but it looks rather compilcated09:43
itamaroas the test does not share the same memory as the apps09:43
nick-ma__Sorry, I am in the train.  my network is not stable. I didn't get most of the discussion. I will quit and check the log. g09:44
oansonnick-ma__, we just started this topic09:44
itamaroas it is a debug feature which is based on well tested cockie manipulation  mechnism09:44
itamaromaybe a unit test will suffice09:44
oansonitamaro, it will at least need a unit test09:44
*** nick-ma__ has quit IRC09:44
itamaroyes09:45
oansonSince nick-ma brought up the fullstack test issue, I would like to get an OK from him that a unit test is enough09:45
oansonLet's wait a minute till he returns and continue this one.09:46
oansonAny other items, in the meantime?09:46
oansonAny reviews you feel should get special attention?09:47
dimakUmmm09:47
dimakI came across skydive this morning09:47
xiaohhuiI have one09:47
dimakIts a network monitoring tool that integrates with neutron09:47
oansondimak, link?09:48
xiaohhuihttps://review.openstack.org/#/c/440946/09:48
dimakhttps://github.com/skydive-project/skydive09:48
irenab_dimak, I checked this project a while ago09:48
*** lei-zh has quit IRC09:48
oansonxiaohhui, sure. I'll look at it09:48
dimakI've tried to deploy it in my devstack and it went OK, but there are some things that I failed to do, like pinging between ports09:49
xiaohhuiThanks!09:49
dimakThey say they are SDN agnostic though provide drivers for various neutron implementations09:49
dimakMaybe its worthwhile adding some support for dragonflow09:49
irenab_dimak, +109:49
oansonxiaohhui, done. +WFed09:50
*** woodard has joined #openstack-meeting-409:50
xiaohhuiThanks!09:50
irenab_according to the project irc, links are: Skydive is hosted on http://softwarefactory-project. Github: https://github.com/redhat-cip/skydive09:50
oansondimak, yes. Troubleshooting features are very important, and a pain point for providers09:50
dimakI still haven't looked into it too much, but it looks quite nice09:52
oansondimak, so what were you thinking? Add a Dragonflow driver? Add documentation on how to integrate?09:53
dimakoanson, well, first figure out what's missing09:53
dimakMaybe both09:53
*** mohankumar has quit IRC09:53
irenab_dimak, I think it already supports ODL as SDN backend09:54
*** woodard has quit IRC09:54
oansonitamaro, it looks like nick-ma isn't coming back. Please contact him offline09:55
itamarook09:55
oansondimak, sounds like a plan. Do you have time to take it?09:55
dimakI wanted to check it out in context of SFC testing09:56
oansonSounds cool09:56
dimakI'll see how much effort it requires and report back09:56
oansonSure. Sounds good.09:56
oansonAnything other items?09:57
oansonGreat.09:58
oansonThanks everyone!09:58
oanson#endmeeting09:58
*** openstack changes topic to " (Meeting topic: ironic_neutron)"09:58
openstackMeeting ended Mon Mar  6 09:58:52 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-03-06-09.00.html09:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-03-06-09.00.txt09:58
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-03-06-09.00.log.html09:58
*** limao has quit IRC10:01
*** alexchadin has quit IRC10:11
*** pbourke has quit IRC10:17
*** pbourke has joined #openstack-meeting-410:18
*** sdague has joined #openstack-meeting-410:25
*** Gk-1wm-su has joined #openstack-meeting-410:31
*** thorst has joined #openstack-meeting-410:34
*** joedborg_ has joined #openstack-meeting-410:34
*** Gk-1wm-su has quit IRC10:35
*** joedborg has quit IRC10:37
*** thorst has quit IRC10:38
*** joedborg_ has quit IRC10:39
*** joedborg has joined #openstack-meeting-410:39
*** amotoki_ has quit IRC10:40
*** alexchadin has joined #openstack-meeting-410:48
*** woodard has joined #openstack-meeting-410:50
*** woodard has quit IRC10:55
*** sambetts|afk is now known as sambetts10:58
*** sdague has quit IRC11:13
*** sdague_ has joined #openstack-meeting-411:14
*** sdague has joined #openstack-meeting-411:14
*** sdague has quit IRC11:16
*** sdague_ is now known as sdague11:16
*** gongysh has quit IRC11:21
*** itamaro has quit IRC11:27
*** alexchadin has quit IRC11:28
*** alexchadin has joined #openstack-meeting-411:44
*** woodard has joined #openstack-meeting-411:51
*** woodard has quit IRC11:56
*** zhurong has quit IRC11:58
*** amotoki has joined #openstack-meeting-412:01
*** dave-mccowan has joined #openstack-meeting-412:09
*** alexchadin has quit IRC12:17
*** rfolco has joined #openstack-meeting-412:17
*** alexchadin has joined #openstack-meeting-412:21
*** rwallner has joined #openstack-meeting-412:24
*** ishafran has quit IRC12:29
*** mohankumar has joined #openstack-meeting-412:37
*** thorst has joined #openstack-meeting-412:44
*** rfolco has quit IRC12:52
*** salv-orlando has joined #openstack-meeting-412:53
*** rfolco has joined #openstack-meeting-412:54
*** salv-orl_ has quit IRC12:56
*** lei-zh has joined #openstack-meeting-412:57
*** rwallner has quit IRC12:58
*** kylek3h_ has quit IRC13:01
*** rwallner has joined #openstack-meeting-413:01
*** rwallner_ has joined #openstack-meeting-413:02
*** mohankumar has quit IRC13:04
*** rwallner has quit IRC13:06
*** mohankumar has joined #openstack-meeting-413:07
*** mohankumar has quit IRC13:18
*** cleong has joined #openstack-meeting-413:26
*** limao has joined #openstack-meeting-413:35
*** bobmel has joined #openstack-meeting-413:37
*** kylek3h has joined #openstack-meeting-413:37
*** sshnaidm has joined #openstack-meeting-413:38
*** vikasc has joined #openstack-meeting-413:41
*** klamath has joined #openstack-meeting-413:43
*** klamath has quit IRC13:45
*** klamath has joined #openstack-meeting-413:45
*** baoli has joined #openstack-meeting-413:47
*** baoli has quit IRC13:48
*** baoli has joined #openstack-meeting-413:49
*** bauzas has left #openstack-meeting-413:50
*** baoli has quit IRC13:50
*** baoli_ has joined #openstack-meeting-413:50
*** baoli_ has quit IRC13:51
*** woodard has joined #openstack-meeting-413:53
*** mchiappero has joined #openstack-meeting-413:54
*** bauzas has joined #openstack-meeting-413:55
*** alraddarla has joined #openstack-meeting-413:57
*** woodard has quit IRC13:57
*** julim has joined #openstack-meeting-413:58
*** baoli has joined #openstack-meeting-413:59
*** yedongcan has joined #openstack-meeting-414:00
*** hongbin has joined #openstack-meeting-414:00
apuimedo#startmeeting kuryr14:01
openstackMeeting started Mon Mar  6 14:01:00 2017 UTC and is due to finish in 60 minutes.  The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: kuryr)"14:01
openstackThe meeting name has been set to 'kuryr'14:01
apuimedoHello everybody14:01
ltomasboo/14:01
alraddarlao/14:01
vikasco/14:01
hongbino/14:01
mchiapperoo/14:01
yedongcano/14:01
limaoo/14:01
apuimedowelcome to the first official Pike cycle weekly irc meeting14:01
*** garyloug has joined #openstack-meeting-414:02
apuimedo#topic VTG14:02
*** openstack changes topic to "VTG (Meeting topic: kuryr)"14:02
garylougo/14:03
janonymouso/14:03
irenabhi14:03
apuimedoI have to say I enjoyed the Virtual Team Gathering. I hope it was not too strenuous to follow and join14:03
apuimedoand that the recordings and boards were helpful14:03
*** ivc_ has joined #openstack-meeting-414:03
irenabapuimedo: I agree with you, my experience was positive too14:04
ltomasboit was my first one, but I liked it too!14:04
ivc_o/14:04
apuimedoltomasbo: it was the first one for everybody14:04
apuimedo:P14:04
apuimedoI'd like to propose a meeting tomorrow at 14utc to go over the action items14:04
ltomasbo:D14:04
apuimedodoes that time work?14:05
janonymous+114:05
mchiappero+114:05
irenabcan we shift 30 mins earlier?14:05
vikasc+1 irenab14:05
apuimedoirenab: fine for me14:05
vikascwill prefer 30 mins earlier14:06
apuimedomchiappero: janonymous: ivc_: does that work for you 13:30utc tomorrow?14:06
janonymous+114:06
mchiapperook14:06
ltomasbook14:06
*** amotoki has quit IRC14:06
irenab+114:06
*** amotoki has joined #openstack-meeting-414:06
apuimedo#info March 7th 13:30 utc VTG Action Item sorting session.14:07
vikascthanks!14:07
apuimedo#action apuimedo to send the VTG Action Item sorting session to the mailing list14:07
apuimedoAnything else about the VTG?14:07
ivc_apuimedo as long as it is an hour long, i'm ok with that14:07
apuimedoit is14:07
irenabapuimedo: please share the list before, so we can check what to pick before the meeting14:08
*** cathrichardson has joined #openstack-meeting-414:08
apuimedoirenab: it will be in the email to the ml14:08
apuimedo:-)14:08
irenabthanks14:08
apuimedo#topic fuxi14:08
*** openstack changes topic to "fuxi (Meeting topic: kuryr)"14:08
apuimedo#chair hongbin14:08
openstackCurrent chairs: apuimedo hongbin14:08
alraddarlasorry, i actually have to step away. will catch up in a bit14:08
hongbinhi14:09
apuimedoalraddarla: very well, if there is any question reach out on the ml14:09
apuimedoor irc14:09
apuimedohongbin: any fuxi updates?14:09
hongbinfor fuxi, there are several patches landed last week14:09
hongbinand we are proposing the first release14:09
hongbin#link https://review.openstack.org/#/c/441522/14:09
apuimedo:-)14:10
hongbinthat would be a good first relase for fuxi14:10
apuimedoThat's really good news14:10
hongbinapuimedo: that is all from me14:10
*** cathrich_ has quit IRC14:10
apuimedo#info A first fuxi release, 0.1.0 has been proposed14:10
*** gongysh has joined #openstack-meeting-414:11
apuimedohongbin: At some point we should define what 1.0.0 should be14:11
apuimedoand if that should be in the Pike cycle14:11
hongbinapuimedo: work for me14:11
*** janki has quit IRC14:11
apuimedothanks14:11
apuimedoanybody else has some question about fuxi?14:11
*** pc_m has joined #openstack-meeting-414:12
apuimedo#topic kuryr-libnetwork14:12
*** openstack changes topic to "kuryr-libnetwork (Meeting topic: kuryr)"14:12
apuimedoWe had a very nice series of contributions this week14:13
apuimedofixing bugs and adding blueprints14:13
apuimedo:-)14:13
irenabregarding IPv6 support https://blueprints.launchpad.net/kuryr-libnetwork/+spec/ipv6-subnet14:13
apuimedo#info oslo debug bugfix in https://review.openstack.org/43652314:14
apuimedo#info gateway ip retrieval fix https://review.openstack.org/43670514:14
apuimedo#info mac address setting fix https://review.openstack.org/43277714:14
apuimedoirenab: please go ahead14:15
irenabI suggest to address IPv6 support as a whole14:15
*** amotoki has quit IRC14:15
irenabcurrently there some ptches to add support for existing IPv6 subnetpools14:15
apuimedoI'm fine with delaying 1.0.0 for ipv6 support14:15
apuimedoin fact, I propose we do just that14:15
irenabsounds reasonable to me14:16
apuimedoat the very least, I want the support for dual stack networking that hongbin has been pushing14:16
irenabapuimedo: but this is fragmental, isn’t it?14:16
apuimedoirenab: I also saw your comment to hongbin's https://review.openstack.org/#/c/426595/14:16
apuimedoirenab: sort of. It only enables dual stack14:17
apuimedobut not pure ipv614:17
hongbinirenab: it looks the support of existing ipv6 and kuryr-created ipv6 will be very different14:17
irenabapuimedo: dual stack only if its neutron created subnet14:18
apuimedoirenab: yes14:18
hongbinit is more like a bug fix than a new feature (i think)14:18
apuimedoI think that what hongbin proposes in regard to the change of semantics for specifying the subnetpool makes sense. Because it is consistent with what we do for specifying networks14:18
irenabI think IPv6 never have been a priority till now14:18
irenabapuimedo: I will revisit my comment, ned to recheck14:19
irenabas long as there are no users, I guess we can change the API semantics, but in general I prefer to avoid it14:20
apuimedoI know14:20
apuimedoI'll take a second look14:20
apuimedobut the consistency is important reaching 1.0.014:21
irenabso supporting container on existing IPv6 subnet will be included in 1.00?14:21
apuimedoyes14:21
irenabbut no docker driver IPv6 subnet14:21
apuimedoand I'd like also on creating new one14:21
irenabapuimedo: what is the expected timeline for 1.0.0?14:22
apuimedoyedongcan: hongbin: limao: is creating on new ipv6 something either of you want to work on?14:22
apuimedoirenab: asap14:22
apuimedoas soon as we support ipv6 we cut the release14:22
hongbinapuimedo: yes, i saw yedongcan took the bp, i can work with him for this14:22
apuimedoperfect14:23
apuimedohongbin: yedongcan: I love the collaboration you have14:23
apuimedo:-)14:23
yedongcanapuimedo, hongbin: thanks, will do that.14:23
limaoapuimedo: It is ok for me IPv6 not in 1.0.014:23
irenabapuimedo: to cut 1.0.0, what is DoD criteria?14:23
irenabFull stack tests?14:24
apuimedoirenab: I'm sorry. But since I was a teenager... DoD only means "Day of Defeat" to me14:24
irenab:-)14:24
apuimedoirenab: could you remind me what it means?14:24
irenabDefinition of Done14:24
apuimedoah, right14:24
apuimedoI know remember it's not the first time I ask you this14:24
apuimedosorry about that14:24
apuimedoirenab: IPv6 with full stack tests for dual stack and IPv614:25
apuimedolimao: would you prefer 1.0.0 be cut before?14:25
irenabI asked yedongcan to list work items at the bp14:25
apuimedoI ask because if it is helpful we can consider it for before14:25
limaoapuimedo: depend on what's the time line we can fix ipv6, maybe we can check the ipv6 patch status next weekly, to see if we include ipv6 in 1.0.014:26
apuimedolimao: agreed14:27
hongbinlimao: +114:27
apuimedoLet's try to have code either merged or almost ready14:27
apuimedoso that in next week we only miss the fullstack tests14:27
yedongcanI will work on the base code and unit test this week.14:28
*** makowals has quit IRC14:28
apuimedoyedongcan: thanks a lot!14:28
apuimedo#info We will revisit IPv6 creation inclusion on 1.0.0 release on the next weekly14:28
apuimedoanything else on kuryr-libnetwork?14:29
limaoapuimedo: one more14:29
apuimedogo ahead14:29
limaoabout the kuryr-libnetwork docker image14:29
limaoWill we create an offical image to upload to docker hub?14:30
*** makowals has joined #openstack-meeting-414:30
limao(Maybe as a part of 1.0.0 release?)14:30
apuimedolimao: there was some discussion on the PTG about the OpenStack container registry14:30
apuimedodan prince said he'd help with the puppet to deploy it14:31
limaoapuimedo: oh, cool, thanks for the info.14:31
*** cdelatte has joined #openstack-meeting-414:31
apuimedolimao: before that, we can only have unofficial container, that I can publish again14:31
apuimedo#topic kuryr-kubernetes14:32
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)"14:32
apuimedoltomasbo: how is the work going on the resource management after the VTG discussion?14:32
ltomasboI'm modifying the already existing patches14:33
*** hongbin has quit IRC14:33
apuimedoirenab: vikasc: we should be merging https://review.openstack.org/#/c/440248/1 as we did in the other repos14:33
ltomasboto increase the isolation between VIF and PortsPool drivers14:33
apuimedogood14:33
ltomasboI already did for the baremetal one14:33
apuimedoltomasbo: is there anything you need?14:33
ltomasboand working right now in the nested one14:33
apuimedo(from reviewers)14:34
ltomasboit would be really nice to have some reviews on these:14:34
irenabapuimedo: why is this one manula update?14:34
ltomasbohttps://review.openstack.org/#/c/43687514:34
ltomasbohttps://review.openstack.org/#/c/436876/14:34
ltomasbohttps://review.openstack.org/#/c/436877/14:34
ltomasboand I will submit the ones for nested probably today14:34
ltomasboand hopefully update the devref tomorrow14:34
irenabltomasbo: will check them by tomorrow14:35
apuimedohttps://bugs.launchpad.net/openstack-requirements/+bug/166884814:35
openstackLaunchpad bug 1668848 in tacker "PBR 2.0.0 will break projects not using constraints" [High,In progress] - Assigned to yong sheng gong (gongysh)14:35
ltomasbothen I will work on the kuryr-controller reboot (discovering the already created ports)14:35
apuimedoI thought there was an email on the ml about it too14:35
apuimedobut I can't find it now14:35
ltomasboirenab, great, thanks14:35
apuimedothanks ltomasbo14:35
ltomasboapuimedo, about what?14:35
ltomasbo(not the thanks but the ml thing)14:36
ltomasbo:d14:36
apuimedoltomasbo: about the pbr thing I pointed irenab towards14:36
ivc_apuimedo we have that pbr patch https://review.openstack.org/#/c/439321/14:36
ltomasboahh, ok14:36
apuimedogaryloug: mchiappero: I see irenab also posted some comments to https://review.openstack.org/#/c/440669/14:36
ivc_apuimedo since it passes gates it seems it does not break anything14:36
apuimedokeep up to good work14:37
apuimedoivc_: it may break us on indirect dependencies, but you are right, for kuryr-k8s it doesn't break us for now14:37
mchiapperoapuimedo: the main concern is actually the potential race you pointed out14:37
apuimedomchiappero: yeah... That's a tough onw14:38
apuimedo*one14:38
apuimedo:-)14:38
irenabapuimedo: so about the prb patch, which one do you want to merge?14:38
apuimedomchiappero: did you get any inspiration for that?14:38
irenabpbr14:38
mchiapperoapuimedo: other than a "allowed_address_pairs" lock?14:38
mchiapperono14:38
apuimedoirenab: I'll dig around14:39
mchiapperoI'm afraid that Neutron has nothing to offer, and on the dispatcher side I'm not sure whether there is something we can do (e.g. use a threaded controller in this config)14:39
irenabok14:39
irenabmchiappero: what is the problem you are dealing with?14:40
apuimedomchiappero: irenab: Do you think there is any chance the address pairs Neutron API could be enhanced?14:40
mchiapperoirenab: the possibility that two threads might be updating the "allowed_address_pairs" on the parent port at the same time14:40
apuimedoSo instead of being a replacement we get additions?14:40
mchiapperoapuimedo: it should probably work as the openstack client14:41
mchiapperoget/set14:41
mchiapperoeach with a commit approach14:41
irenabmchiappero: on kuryr side?14:41
mchiapperoshort term, maybe locking on the kuryr side14:41
*** amotoki has joined #openstack-meeting-414:41
apuimedoivc_: the problem here is we'd probably need the dispatcher to be able to grouping events into green threads according to a driver as well14:42
*** cathrichardson has left #openstack-meeting-414:42
apuimedomchiappero: that would get rid of needing a lock14:42
mchiapperoapuimedo: yes, that the other approach I was talking about14:42
apuimedofor example, for the current macvlan driver, we'd just group events for scheduled node14:42
mchiapperoI need to check though, or get feedback from any of you familiar with the dispatching code14:42
ivc_apuimedo yup. but lets stay away from that for now. i'm still hoping for a generalised actor model that would solve those issues14:42
apuimedoivc_: any hint on how it would solve it? Without giving up pod creation concurrency14:43
ivc_apuimedo mchiappero i'm probably ok with locking as a short-term workaround just for that14:43
mchiapperoapuimedo: long term if the nested port support for macvlan/ipvlan based on trunks will be accepted in Neutron we are ok14:43
ltomasboso, neutorn.update_port_address_pairs just replace the current set, instead of adding into it?14:43
ivc_apuimedo you'll have an actor for 'update address pairs'14:43
apuimedoirenab: well, the problem for the approach garyloug and mchiappero patch pushes14:44
apuimedoexactly what ltomasbo said14:44
apuimedo:P14:44
ltomasbosounds to me that the right place to fix it is on the neutron side then14:44
apuimedoso the same we do for trunk ports can't be done14:44
apuimedoas it's buying tickets for the hot potato game14:44
apuimedoltomasbo: I agree that it would be the nicest outcome14:44
apuimedoltomasbo: but that may not be a tractable problem14:45
ltomasbo:(14:45
irenabneutron works on API request basis, so every request should be served autonomously, isn’t it?14:45
ivc_ltomasbo 'just replace' could race and loose some calls14:45
mchiapperoltomasbo: agree, I'm not sure though how willing they are to change a public API14:45
apuimedo#action apuimedo to reach out to Neutron folks about a non-replacing API for allowed address ports14:46
ltomasboI'm not in favor of replacing ivc_, rather the oposite14:46
ivc_apuimedo ltomasbo or are we discussing 'commit' on neutron side. if so, i'd be agains that14:46
irenabI am not sure I unnderstand what API change you propose for neutron14:47
mchiapperoas I said I think an 'openstack' client like API would be nice14:47
apuimedomchiappero: I don't understand what that means14:47
mchiapperoso atomic adds and removes rather a full replace14:47
ivc_irenab i think they mean making 'allowed address pairs' a sub-resource so it can support add/remove instead of replace14:47
mchiapperoapuimedo: like add one or more pair14:48
irenabivc_: thanks for clarification14:48
mchiapperoso that you do not need to per form the Read-Modify-Update14:48
apuimedoivc_: yes, that's what I meant14:48
apuimedoit's a REST change14:49
apuimedoso I think it's unlikely14:49
ivc_apuimedo in that case it does make sense, tho super unlikely to get that change in reasonable amount of time14:49
irenabapuimedo: I tend to agree; unless itis addition and not replacement to the existing API14:49
apuimedoagreed14:49
apuimedoI can't see it happening unless it is a service plugin14:50
mchiappero:D I'm not following you anymore14:50
apuimedoor some other sort of extension14:50
ivc_irenab apuimedo addition would mean neutron would provide 2 api's for the same function, which is kinda ugly14:50
apuimedomchiappero: discussing neutron api/maintenance/politics14:50
mchiapperoapuimedo: ok14:50
irenabapuimedo: worth to check anyway, maybe same issues came from other use cases14:51
ivc_apuimedo i'd say serialising updates on kuryr side is more realistic approach. so locks for now and actors later14:51
*** makowals has quit IRC14:52
*** limao_ has joined #openstack-meeting-414:52
apuimedoivc_: I'll just ask if a plugin could make sense. If possible I prefer to lock in Neutron14:52
irenabivc_: so lock on call neutron to update port with address pairs?14:52
mchiapperook, so, to recap: 1) macvlan specific lock on allowed_address_pairs updates 2) attempt Neutron API extension 3)improve the dispatching logic14:52
apuimedoirenab: I guess just lock on a per port basis14:52
mchiapperois this ok in terms of priority?14:52
*** limao has quit IRC14:53
apuimedowhen doing the address pairs update14:53
apuimedoas you say14:53
apuimedomchiappero: that's right14:53
ivc_irenab lock per 'update_address_pair' call is the easiest, but could be narrowed down to per-port lock14:53
mchiapperook, let's try in that order and update according to the progress14:53
*** woodard has joined #openstack-meeting-414:54
apuimedoirenab: https://review.openstack.org/#/c/438367/114:54
apuimedowhen you have a moment14:54
irenabapuimedo: done14:54
ivc_apuimedo irenab that one could have some better wording, but ok :)14:55
apuimedoas ivc_ says. per port when doing the update_address_pair14:55
*** git-harry has joined #openstack-meeting-414:55
apuimedoivc_: I'm just glad I didn't have to write it :P14:55
irenablets follow up on the patch14:55
apuimedodocumentation patches warm my heart14:55
*** makowals has joined #openstack-meeting-414:56
apuimedoanything else on kuryr-k8s?14:56
ivc_apuimedo i was lazy when documenting the function and that devref patch just copied that :)14:56
apuimedoivc_: we need to document better in this cycle. I had a diagram bug as well14:56
apuimedoand we should start making release note patches to catch up to what we have14:57
apuimedowith reno14:57
ivc_apuimedo add another action item for tmoroz meeting :P14:57
irenabapuimedo: I think we shoudl ahve a list what should be included for every added feature14:57
apuimedoivc_: That's a very good point14:58
apuimedoI will14:58
apuimedoirenab: even better point14:58
apuimedoa checklist14:58
*** woodard has quit IRC14:58
apuimedothanks irenab!14:58
irenabI can add some feature DoD list to the devref14:58
*** thomasem has joined #openstack-meeting-414:58
*** limao_ has quit IRC14:58
apuimedoirenab: that would be super great!14:59
ivc_trello? or i remember there was some openstack-hosted todo list...14:59
*** limao has joined #openstack-meeting-414:59
apuimedoivc_: I think more like have a devref of: Things to check for when submitting a feature14:59
apuimedolike people can use it for their own checklist14:59
irenabI just though to add some rst into the devref , like kuryr feature addition plolicy or something like this14:59
apuimedoivc_: the action items from the VTG will end up on a trello most likely14:59
apuimedoirenab: sounds perfect15:00
apuimedolet me know if I can help you with that15:00
apuimedoit's an excellent idea15:00
irenabapuimedo: add AI for me please15:00
apuimedo(especially for forgetful people like me15:00
apuimedo)15:00
ivc_apuimedo i'll try to find that openstack-hosted tool (to keep things under the same umbrella if possible)15:00
irenabso I won’t forget :-)15:00
apuimedo#action irenab to draft the feature contributor checklist15:00
apuimedoivc_: openstack stories15:00
apuimedostoryboard15:00
apuimedoor something like that15:01
apuimedoirenab: we really need those checklists15:01
apuimedo:P15:01
apuimedoanyways. Out of time15:01
apuimedothank you all for joining!15:01
ivc_apuimedo right, storyboard it is :)15:01
apuimedotalk to you tomorrow15:01
apuimedoivc_: I'm proud I remembered it15:01
apuimedo#endmeeting15:01
*** openstack changes topic to " (Meeting topic: ironic_neutron)"15:01
openstackMeeting ended Mon Mar  6 15:01:45 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-03-06-14.01.html15:01
irenabbye15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-03-06-14.01.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-03-06-14.01.log.html15:01
*** alexchadin has quit IRC15:01
jimbaker#startmeeting craton15:01
openstackMeeting started Mon Mar  6 15:01:54 2017 UTC and is due to finish in 60 minutes.  The chair is jimbaker. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
jimbaker#chair sigmavirus sulo jimbaker thomasem15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
jimbaker#link https://etherpad.openstack.org/p/craton-meetings15:01
*** openstack changes topic to " (Meeting topic: craton)"15:01
openstackThe meeting name has been set to 'craton'15:01
jimbaker#topic Roll Call15:02
openstackCurrent chairs: jimbaker sigmavirus sulo thomasem15:02
*** openstack changes topic to "Roll Call (Meeting topic: craton)"15:02
thomasemAh, beat me to it15:02
fsaado/15:02
thomasemo/15:02
sigmaviruso/15:02
jimbakero/15:02
jimbakerthomasem, :)15:02
sigmavirusthomasem: looks like jimbaker wants to chair this meeting ;)15:02
thomasemYep.15:02
* thomasem passes torch15:02
*** alraddarla has left #openstack-meeting-415:02
* thomasem kids15:02
*** garyloug has left #openstack-meeting-415:02
jimbakeroh i'm so sure you want me to chair...15:02
suloo/15:02
* sigmavirus sets bridge on fire using torch15:02
thomasem#topic Action Items from Last Meeting15:03
thomasem#link http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-02-27-15.04.html15:03
*** cjloader has joined #openstack-meeting-415:03
*** openstack changes topic to "Action Items from Last Meeting (Meeting topic: craton)"15:03
thomasemACTION: thomasem to write BP regarding deployment as a starting point for iterating on a suggested deployment model15:03
thomasem#action thomasem to write BP regarding deployment as a starting point for iterating on a suggested deployment model15:04
thomasemACTION: jimbaker to map Dusty's requirements to work or existing features of Craton, especially with respect to short-term deliverable15:04
jimbakerdefer...15:04
thomasem#action jimbaker to map Dusty's requirements to work or existing features of Craton, especially with respect to short-term deliverable15:04
jimbakerthx15:04
thomasemACTION: sigmavirus finish up client/cli testing15:04
jimbakerso is this something we can ever say is done?15:04
jimbakerseems to me that sigmavirus did a lot of work on this15:05
thomasemYeah.15:05
thomasemIt can be done.. up to us.15:05
thomasem;)15:05
jimbakerlet's just rewind context here, and i think it was something along the lines of15:05
thomasemProbably not enough detail in the noted item.. yeah15:05
jimbakerthe client/CLI need better testing in this way, because of inconsistency in column ordering etc15:06
sigmavirusI still have more testing to do15:06
sigmavirusI have yet to set up tests that actually talk to a craton server15:06
jimbakersigmavirus, sure, so how about the following action item for you15:06
sigmavirusWe can split it up into multiple items15:06
jimbakersigmavirus will work out testing plan15:06
jimbakersuch as assurance testing15:06
jimbakerand present back to us15:06
*** yedongcan has left #openstack-meeting-415:07
sigmavirusyep15:07
jimbakerwhat we don't want a mega action item that's just a recurring standing task. better code! better testing! more customers! :)15:07
sigmavirusI mean15:07
sigmavirusI have a plan15:07
sigmavirusbut =P15:07
thomasem#action sigmavirus to detail a testing plan for python-cratonclient for the team15:08
jimbaker+115:08
*** pc_m has left #openstack-meeting-415:09
thomasemThen we can generate bugs/BPs from said plan for any things that need to be done.15:09
sigmavirusI'll spec it out in python-cratonclient repo15:09
thomasem+115:09
jimbaker+115:09
thomasem#undo15:09
openstackRemoving item from minutes: #action sigmavirus to detail a testing plan for python-cratonclient for the team15:09
thomasem#action sigmavirus to spec out a testing plan for python-cratonclient in python-cratonclient repo15:09
*** limao has quit IRC15:09
thomasem#topic Stand-up15:10
thomasem#info each team member briefly describes what they are working on this week, and describes blockers (if there are any)15:10
*** openstack changes topic to "Stand-up (Meeting topic: craton)"15:10
*** limao has joined #openstack-meeting-415:10
thomasem#topic Stand Up :: thomasem15:10
*** openstack changes topic to "Stand Up :: thomasem (Meeting topic: craton)"15:10
thomasemFinishing up CLI vars patch, code reviews, and taking the next highest priority item after the CLI vars patch is done15:11
thomasempatches*15:12
thomasemdone15:12
thomasem#topic Stand Up :: fsaad15:12
*** openstack changes topic to "Stand Up :: fsaad (Meeting topic: craton)"15:12
fsaadnot much from my end, got the demo box (ajaxterm) playbook going in case it's useful15:13
fsaadcloudnull mentioned he's starting work on a deploy playbook, in case it's useful https://github.com/os-cloud/craton/blob/master/tools/craton-deploy/deploy-craton.yml15:13
fsaadplans on converting to role for OSA15:13
fsaaddone15:13
cloudnull++ I should have that done today15:14
thomasem#topic Stand Up :: sigmavirus15:14
*** openstack changes topic to "Stand Up :: sigmavirus (Meeting topic: craton)"15:14
*** makowals has quit IRC15:14
sigmavirusI am currently standing up15:14
sigmavirusEr, wait, that's not what you wanted15:14
thomasemIt is, actually. Thank you for sharing.15:14
sigmavirus/fin15:14
thomasemI am sitting down.15:14
jimbakeri too stand up if possible in an irc meeting15:14
sigmavirusIn reality, I did a bunch of refactoring on the cratonclient shell nonsense15:15
*** baoli has quit IRC15:15
sigmavirusMade the column ordering deterministic and seem to have annoyed sulo into making a quick patch :)15:15
sigmavirusI'm going to work on the spec as soon as the meeting is done15:15
sigmavirus/fin-for-real15:15
thomasem#topic Stand Up :: jimbaker15:15
*** openstack changes topic to "Stand Up :: jimbaker (Meeting topic: craton)"15:15
jimbakerReview outstanding code, especially vars support in client (hopefully finalize and get in this morning)15:15
jimbakerImplement testing for the var search query filter so we can get in15:15
jimbakerTriage bugs (one critical is left without in progress: https://bugs.launchpad.net/craton/+bug/1666536)15:16
openstackLaunchpad bug 1666536 in craton "Cyclical hierarchies using parent_id" [Critical,New] - Assigned to Jim Baker (jimbaker)15:16
jimbakerWork on Dusty's requirements - especially production-oriented aspects - this should translate into a spec as well15:16
jimbakerBack to RBAC later this week15:16
jimbakerdone15:16
thomasem#topic Stand Up :: sulo15:16
*** openstack changes topic to "Stand Up :: sulo (Meeting topic: craton)"15:16
*** alexchadin has joined #openstack-meeting-415:16
sulohola, mostly testing the patches right now for the demo and making some minor changes in the process15:17
jimbaker+10015:17
thomasem#topic This Week's Priorities15:17
*** openstack changes topic to "This Week's Priorities (Meeting topic: craton)"15:17
sulodone15:17
thomasem#undo15:17
openstackRemoving item from minutes: #topic This Week's Priorities15:17
thomasem#topic This Week's Priorities15:17
*** openstack changes topic to "This Week's Priorities (Meeting topic: craton)"15:17
jimbakerobviously today's demo15:18
thomasemFinishing up CLI vars support15:18
*** makowals has joined #openstack-meeting-415:18
jimbakerlet me suggest that for tues meeting we use that meeting time as a retrospective15:18
jimbaker(at least in part)15:18
thomasemOkay. Please add retrospective topics to the Etherpad.15:18
sulowould be good to look at the bug to add --resolved-vars =false to show command15:19
* sulo goes to find the lp link15:19
sulohttps://bugs.launchpad.net/python-cratonclient/+bug/166950815:19
openstackLaunchpad bug 1669508 in Craton's Python Client "Resource GET calls need to allow filtering" [Undecided,New]15:19
sigmavirusjimbaker: should we tag a release this afternoon in craton/cratonclient?15:19
jimbaker#action jimbaker plan retrospective meeting for tues mar 7 with appropriate topics15:19
jimbakersigmavirus, the cmdb milestone? so long as we get this alembic stuff in15:20
*** david-lyle has quit IRC15:20
thomasemDistilling it down:15:20
sigmavirusjimbaker: I mean a tag in the repo15:20
sigmavirusWe can call it 0.1.0 or whatever15:21
sigmavirusjust gives the tiger team something to use15:21
jimbakersigmavirus, +115:21
sigmavirus(rather than HEAD)15:21
sulosigmavirus: +115:21
*** limao has quit IRC15:21
jimbakeri think stating that says something about today's demo15:21
thomasemYeah, finalize that and backport for any things we want to get in there before the next release?15:21
*** limao has joined #openstack-meeting-415:21
sigmavirusthomasem: backport?15:22
jimbakerhaving said that, would like alembic in, because otherwise we have some possible unnecessary pain, https://review.openstack.org/#/c/441644/15:22
jimbakerso just needs some reviews15:22
sigmavirusjimbaker: will review15:22
jimbakerthanks15:22
thomasemsigmavirus: Posing the question of discriminating new patches to HEAD and whether we want to also get some of them into the 0.1.0 tag as well?15:23
sigmavirusthomasem: ah, so nothing has tagged yet. When i think of backporting, I think of having a separate branch that we cherry-pick commits to15:23
sigmavirusWe can do that15:23
thomasemIn which case a branch may be better.15:23
sigmavirusbut I think we should be releasing from head frequently15:23
jimbakerbasically anything that sulo demos15:23
thomasemOkay15:23
jimbakertoday should go in 0.1.015:23
*** gongysh has quit IRC15:24
sigmavirusthomasem: I think we should create separate branches *when* we want to support old releases for a while15:24
thomasemSure, sounds good. I just don't know if everything will get in, if history tells.15:24
thomasemGot it15:24
*** tonytan4ever has joined #openstack-meeting-415:24
thomasemeverything will get in *today*15:24
thomasemI mean to say15:24
jimbakervar search query is a good example15:24
sigmavirusthomasem: we don't have to do 0.1.0 today15:24
sigmaviruswe can do it tomorrow15:24
sigmavirusbut15:24
sigmaviruswe should do it *soon*15:24
jimbakerright15:24
thomasemI agree.15:25
thomasemOkay, so, let's distill this down15:25
thomasem1. demo today15:25
thomasem2. CLI vars patch15:25
jimbakerthere's one outstanding bug that was marked critical, and therefore supposed to be in the cmdb milestone, https://bugs.launchpad.net/craton/+bug/166653615:25
openstackLaunchpad bug 1666536 in craton "Cyclical hierarchies using parent_id" [Critical,New] - Assigned to Jim Baker (jimbaker)15:25
thomasem3. Alembic changes15:25
*** limao has quit IRC15:26
thomasemjimbaker: where does that fit in this week's priorities?15:26
jimbaker(i can unassign it to me if anyone has free cycles)15:26
jimbakerthomasem, so this is a data corruption bug15:26
*** cathrichardson has joined #openstack-meeting-415:27
jimbakerif one creates such a cycle, the db is corrupted from the standpoint of subsequent queries against devices15:27
thomasemWhat about not assigning until you're ready to work on it?15:27
jimbakerthomasem, yep, sounds like a better plan15:27
thomasemThat way there never has to be the question if someone else wants to pick it up and work on it.15:27
jimbakeri will unassign myself now15:27
thomasem+115:28
sigmavirusthomasem: yeah, I think we have people on the team who just assign themselves to things they intend to work on at some point in the vague future15:28
*** cjloader has quit IRC15:28
sigmavirusIt's incredibly unhelpful15:28
sigmavirusAnd it's not just jim15:28
sigmavirusalso, the openstack infra bot will assign you once you submit a review15:28
jimbakernice to know15:28
sigmavirusso unless you anticipate it taking days or longer, best to just let it auto-assign you15:28
thomasemYep. That bot takes care of a lot of stuff for you.15:28
* sigmavirus nods15:29
thomasemIt'll set the bug to in progress, it'll auto-assign you, it'll link the review.15:29
thomasemAll you have to do is tag the bug in the commit message15:29
suloneed more bots to unassign15:29
thomasemLol15:29
sulobot = "you are taking too long ... "15:29
jimbakerso best coordinate interest in our meetings, or on #craton. but don't sit on an assignment15:29
thomasemCorrect. I don't imagine we're territorial people, but it does have that effect sometimes.15:30
sigmavirussulo: I think launchpad can do stuff like that for you15:30
sigmavirusthere's a concept of a Launchpad Janitor15:30
*** cathrichardson has left #openstack-meeting-415:30
sigmavirusit also cleans up stale bug reports if you want15:30
sulosigmavirus: cool :)15:30
jimbakergreat retrospective topics btw15:30
thomasemYep15:30
sigmavirus"How to bring development progress to a halt > Assign all the bugs to yourself"15:31
thomasemYep. So, we're drifting a bit.15:31
sulothis is like the age of bots15:31
thomasemBasically, priorities are in order of priority in LP for cmdb v0.1.0 milestone in both repositories.15:31
sulolets write some bot to do more things15:31
thomasemdemo is a big deal. Other than that, any in-flight code reviews for critical priority items in LP need eyes.15:32
jimbakeryeah, anything else we need to cover?15:32
thomasemDoes that make sense and resonate with everyone?15:32
jimbakerotherwise, let's just postpone discussion until tomorrow15:33
thomasemOpen Discussion, you mean?15:33
jimbakerand this meeting as well15:33
thomasemCool.15:33
*** amotoki has quit IRC15:33
thomasemAlright, let's get back to it!15:34
jimbakerawesome, thanks!15:34
fsaady'all want to do a demo dry-run ?15:34
thomasem#endmeeting15:34
fsaad:)15:34
*** openstack changes topic to " (Meeting topic: ironic_neutron)"15:34
openstackMeeting ended Mon Mar  6 15:34:09 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-03-06-15.01.html15:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-03-06-15.01.txt15:34
openstackLog:            http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-03-06-15.01.log.html15:34
fsaadok back to #craton15:34
*** alexchadin has quit IRC15:34
*** git-harry has left #openstack-meeting-415:34
*** tojuvone has joined #openstack-meeting-415:35
*** galstrom_zzz is now known as galstrom15:39
*** lei-zh has quit IRC15:40
*** makowals_ has joined #openstack-meeting-415:42
*** makowals has quit IRC15:43
*** Syed__ has joined #openstack-meeting-415:44
*** reedip_1 has joined #openstack-meeting-415:51
*** bobmel has quit IRC15:54
*** woodard has joined #openstack-meeting-415:55
*** woodard has quit IRC15:59
*** trinaths1 has joined #openstack-meeting-416:00
*** Jeffrey4l has quit IRC16:02
*** yamahata has joined #openstack-meeting-416:02
*** emagana has joined #openstack-meeting-416:03
*** hongbin has joined #openstack-meeting-416:03
*** reedip_1 has left #openstack-meeting-416:04
*** cjloader has joined #openstack-meeting-416:12
*** Jeffrey4l has joined #openstack-meeting-416:15
*** baoli has joined #openstack-meeting-416:16
*** david-lyle has joined #openstack-meeting-416:17
*** baoli has quit IRC16:20
*** david-lyle has quit IRC16:22
*** mjturek has joined #openstack-meeting-416:31
*** mjturek has left #openstack-meeting-416:31
*** revon has joined #openstack-meeting-416:32
*** nkrinner is now known as nkrinner_afk16:33
*** amotoki has joined #openstack-meeting-416:34
*** ativelkov has quit IRC16:38
*** hippiepete has quit IRC16:38
*** amotoki has quit IRC16:39
*** ativelkov has joined #openstack-meeting-416:40
*** niedbalski has joined #openstack-meeting-416:41
*** salv-orlando has quit IRC16:41
*** freyes has joined #openstack-meeting-416:43
*** hippiepete has joined #openstack-meeting-416:45
*** uck has joined #openstack-meeting-416:49
*** ivc_ has left #openstack-meeting-416:50
*** woodard has joined #openstack-meeting-416:55
*** sshnaidm is now known as sshnaidm|afk16:58
thedaco/16:59
cargonzao/16:59
wolseno/16:59
iceyo/16:59
niedbalskio/16:59
*** cholcombe has joined #openstack-meeting-416:59
*** woodard has quit IRC16:59
joedborgo/17:00
thedacWaiting just another minute to allow a few more stragglers17:01
coreycbo/17:01
*** vds has joined #openstack-meeting-417:01
thedac#startmeeting charms17:02
openstackMeeting started Mon Mar  6 17:02:01 2017 UTC and is due to finish in 60 minutes.  The chair is thedac. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: charms)"17:02
openstackThe meeting name has been set to 'charms'17:02
thedacWelcome everyone.17:02
*** jamespage has joined #openstack-meeting-417:02
jamespageo/17:02
vdso/17:02
thedacAppologies for canceling our previous meeting as we were in the middle of release week17:02
thedacWe'll jump right in17:02
thedac#topic Review ACTION points from previous meeting17:02
jamespageawesome-o17:02
*** openstack changes topic to "Review ACTION points from previous meeting (Meeting topic: charms)"17:02
thedacCopied over some out of date previous actions.17:03
thedacACTION: jamespage    talk py27 retirement with tc as ptl17:03
thedacjamespage: any word or can that be closed out?17:03
jamespageI've still not really broached that subject; however I do feel the requirement for py27 is broadly not applicable in our use case17:04
jamespageI don't think we need to continue to track it specifically17:04
thedacOK17:04
thedacACTION: cholcombe    close out bugs against ceph-fs17:04
thedaccholcombe: any status ^^17:04
jamespagedone17:04
jamespagewe released it :-)17:04
thedac\o/17:04
wolsen\o/17:04
thedac#topic State of Development for next Charm Release17:05
*** mgagne_ has quit IRC17:05
*** mgagne_ has joined #openstack-meeting-417:05
*** openstack changes topic to "State of Development for next Charm Release (Meeting topic: charms)"17:05
cholcombe:D17:05
thedac17.02 is out the door17:05
jamespagecongrats all17:05
jamespageit was nice todo the release with most people in the same room for a change!17:05
thedacagreed17:05
thedacWe do have some follow up work regarding ocata amulet tests. That work is in progress17:06
iceywoot17:06
thedacAny other items for State of Development17:06
thedacgoing once?17:07
thedacMoving on17:07
jamespage+117:07
thedac#topic Discussion: service discovery vs modeling17:07
*** openstack changes topic to "Discussion: service discovery vs modeling (Meeting topic: charms)"17:07
thedacjamespage: wolsen niedbalski I believe you are all on for this ^^^17:08
jamespageoh strait into the interesting stuff this evening!17:08
wolsenthedac indeed17:08
jamespageok so the context for this is charms that need to enable features based on knowledge of whats been deployed as part of the cloud17:08
jamespagespecific examples - enabling notifications for ceilometer when ceilometer is deployed17:08
jamespageenabling designate notifcations when designate is deployed17:08
jamespageceilometer knowing to use the radosgw support when the object-storage is radosgw17:09
*** dosaboy_ is now known as dosaboy17:09
jamespagewe've seen a few approaches proposed for this - niedbalski - thanks for your proposal for cinder btw17:09
jamespageniedbalski's approach involves quering the service catalog during charm hook execution to determine which services are enabled or not.17:10
jamespageI have a few reservations about that approach as its a little point in time - ceilometer might get added to the deployment after the initial deployment, but notifications might not get turned on correctly taking this approach17:11
cholcombei was thinking the same thing17:11
jamespageso we have to model this by using relations and relation data in some fashion17:11
jamespagethat's my take at least - this may mean adding a 'requires:ceilometer-service' relation to service that need to optionally enable notifications of this type17:12
jamespagethen the charm categorically knows there is something in the deployment providing ceilometer, so notifications can be enabled17:12
jamespagethat's fairly coarse in application17:12
jamespageits either there or not17:13
jamespagewe have other finer grained requirements - I really don't like the way we have to turn on dashboard features using config for example17:13
jamespagethat should just be part of service discovery of some description17:13
jamespageanyone else have any opinions here?17:13
thedacI agree relations is the only way we can manage the race conditions during deploy time. We could do actions post-deploy but that is not an elegant solution.17:14
* jamespage shivers a litte17:14
jamespageagreed thedac17:14
jamespagethis is a great example of a 'smart' charm use-case17:14
thedacWith relations the charms can then set workload status if a service is not avaialable. Informing the end user17:15
*** tojuvone has left #openstack-meeting-417:15
jamespagewhere juju deploy openstack actually deploys a charm, which then deploys the rest of openstack and knows what's been deployed and can toggle config flags17:15
jamespagebut that's a bit of a pipe dream right now17:15
thedac:)17:15
cholcombeconsul is specifically built for this use case17:16
jamespagethedac: I did also have a crazy idea about a general capability to register services and features17:16
cholcombeand i believe it's charmed?17:16
jamespagecholcombe: what might that add? I'm not familiar with consul17:16
cholcombecharms would have to talk to consul to register themselves and what they provide17:16
cholcombei'm not entirely sure it adds anything17:16
thedacHow would that be different than the keystone catalog?17:17
jamespagethedac: I was just thinking that17:17
* jamespage ponders this17:17
cholcombeit's prob not any different so long as keystone can handle scaling up and taking the load of lots of clients asking it for things17:17
jamespageif API endpoints provided features as well as the service type, the keystone charm could have a relation where it echos out a consolidated set of service discovery information to any charm that wants to consume it17:17
*** ntpttr has joined #openstack-meeting-417:17
*** david-lyle has joined #openstack-meeting-417:18
cholcombeas long as it's reliable i don't see any reason not to use it :)17:18
jamespagecholcombe: thedac: does that make some sort of sense?17:18
cholcombeyeah i believe so17:18
niedbalskijamespage, agreed, that'd solve my case.17:19
cholcombei'm a radosgw i provide x, y and z17:19
thedacyeah, that might work. The consuming charm can wait until the service it needs shows up.17:19
*** delattec has joined #openstack-meeting-417:19
jamespageschema might look like17:19
jamespagetype: metering17:20
jamespage   hmm not sure we'll get to this right now17:20
jamespagethedac: can you action me to draft an initial proposal?17:21
jamespageunless someone else would like to take a first pass?17:21
*** cdelatte has quit IRC17:21
thedac#action jamespage Draft initial proposal for service discovery17:21
jamespagehappy to standback from this one if someone else wants to take point17:21
thedacShall we move on then? Any more discussion for this meeting on this topic?17:22
thedacOk, moving on17:23
niedbalskithe suggested approach looks fine to me17:23
thedacgreat17:23
thedac#topic High Priority Bugs17:23
*** openstack changes topic to "High Priority Bugs (Meeting topic: charms)"17:23
thedac#link https://bugs.launchpad.net/openstack-charms17:23
*** david-lyle has quit IRC17:24
* jamespage waves17:24
jamespagehigh level stats17:24
jamespage1 critical bug open still17:24
jamespage59 high priority ones17:24
jamespagehttps://bugs.launchpad.net/charm-hacluster/+bug/147898017:24
openstackLaunchpad bug 1478980 in OpenStack hacluster charm "If the principle updates a resource parameter of an already configured resource hacluster ignores it" [Critical,In progress] - Assigned to Liam Young (gnuoy)17:24
jamespageis the high priority one17:24
thedacok17:25
jamespageand a bit of a tricky one to solve methings17:25
jamespagehigh/critical priority one17:25
thedacI would also like to highlight jamespage's great work consolidating all charms under one project so that bugs are now easier to find and create.17:26
jamespageta - it should make things much easier to track17:26
thedacThat is an understatement17:26
thedacAny other high priority bugs to highlight?17:26
* jamespage is glad his migration script dtrt :-)17:27
thedacMoving on17:27
thedac#topic Openstack Events17:27
*** openstack changes topic to "Openstack Events (Meeting topic: charms)"17:27
thedacWe just came from the ptg17:27
thedac#link https://etherpad.openstack.org/p/openstack-charms-ptg-pike17:27
thedacAny upcoming events to highlight?17:28
jamespageops meetup next week - I won't be attending but I think some folk are going along17:28
jamespage...17:29
jamespage(that was for gnuoy)17:29
thedacODS in Boston in May17:29
thedac#link https://www.openstack.org/summit/boston-2017/17:29
cargonzaBoston DevOps Meetup during ODS Boston in May also... still planning...17:30
*** david-lyle has joined #openstack-meeting-417:30
thedacAny other events?17:30
thedac#topic Open Discussion17:31
*** openstack changes topic to "Open Discussion (Meeting topic: charms)"17:31
thedacOpen discussion time. Does anyone have anything to bring up?17:31
jamespagenot this week17:31
thedacGoing once?17:31
wolsennot from me17:32
wolsenwell17:32
wolsendoes this - https://etherpad.openstack.org/p/openstack-charms-ptg-pike capture the discussions at the PTG adequately17:32
wolsenany additional comments on it for those of us that didn't attend17:32
thedacI think it gives the highlights and the actions that came out of the discussion. Feel free to ping me on any points of interest17:33
wolsenthedac ack17:33
thedacok closing out17:33
thedac#endmeeting17:33
*** openstack changes topic to " (Meeting topic: ironic_neutron)"17:33
openstackMeeting ended Mon Mar  6 17:33:45 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-03-06-17.02.html17:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-03-06-17.02.txt17:33
openstackLog:            http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-03-06-17.02.log.html17:33
thedacThanks all17:33
iceythanks thedac !17:34
joedborgditto, thanks thedac17:34
*** cholcombe has left #openstack-meeting-417:35
*** freyes has left #openstack-meeting-417:37
*** jovon has joined #openstack-meeting-417:44
*** tobberydberg_ has joined #openstack-meeting-417:45
*** armax has joined #openstack-meeting-417:45
*** trinaths1 has quit IRC17:46
*** thomasem has left #openstack-meeting-417:47
*** tobberydberg_ has quit IRC17:50
*** ltomasbo is now known as ltomasbo|away17:52
*** ralonsoh has quit IRC17:55
*** beekneemech is now known as bnemec17:56
*** woodard has joined #openstack-meeting-417:56
*** delatte has joined #openstack-meeting-417:58
*** delattec has quit IRC18:00
*** woodard has quit IRC18:01
*** iyamahat has joined #openstack-meeting-418:03
*** sambetts is now known as sambetts|afk18:07
*** neiljerram has quit IRC18:12
*** unicell has joined #openstack-meeting-418:16
*** vishnoianil has quit IRC18:21
*** joedborg has quit IRC18:22
*** uck_ has joined #openstack-meeting-418:25
*** uck has quit IRC18:25
*** liangy has joined #openstack-meeting-418:32
*** baoli has joined #openstack-meeting-418:34
*** amotoki has joined #openstack-meeting-418:36
*** amotoki has quit IRC18:41
*** spotz is now known as spotz_zzz18:42
*** spotz_zzz is now known as spotz18:43
*** ntpttr_ has joined #openstack-meeting-418:48
*** ntpttr has quit IRC18:48
*** unicell has quit IRC18:50
*** unicell has joined #openstack-meeting-418:50
*** liangy has quit IRC18:51
*** baoli has quit IRC18:58
*** britthouser has quit IRC18:59
*** britthouser has joined #openstack-meeting-418:59
*** FrankZhang has joined #openstack-meeting-419:02
*** s3wong has joined #openstack-meeting-419:02
*** pcaruana has quit IRC19:04
*** baoli has joined #openstack-meeting-419:09
*** bobmel has joined #openstack-meeting-419:14
*** tobberydberg_ has joined #openstack-meeting-419:15
*** pcaruana has joined #openstack-meeting-419:15
*** tobberydberg_ has quit IRC19:18
*** vishnoianil has joined #openstack-meeting-419:19
*** bobmel has quit IRC19:20
*** salv-orlando has joined #openstack-meeting-419:24
*** ntpttr_ is now known as ntpttr19:26
*** basilAB_ has joined #openstack-meeting-419:26
*** baoli has quit IRC19:29
*** uck_ has quit IRC19:31
*** liangy has joined #openstack-meeting-419:36
*** markvoelker_ has quit IRC19:47
*** Rockyg has joined #openstack-meeting-419:50
*** baoli has joined #openstack-meeting-419:50
*** baoli has quit IRC19:50
*** galstrom is now known as galstrom_zzz19:54
*** tobberydberg_ has joined #openstack-meeting-419:57
*** woodard has joined #openstack-meeting-419:58
*** salv-orlando has quit IRC19:58
*** tobberydberg_ has quit IRC20:00
*** bobmel has joined #openstack-meeting-420:01
*** woodard has quit IRC20:02
*** bobmel has quit IRC20:06
*** bobmel has joined #openstack-meeting-420:07
*** galstrom_zzz is now known as galstrom20:11
*** markvoelker has joined #openstack-meeting-420:24
*** yfauser has quit IRC20:29
*** uck has joined #openstack-meeting-420:31
*** rwallner_ has quit IRC20:34
*** rwallner has joined #openstack-meeting-420:35
*** uck has quit IRC20:36
*** amotoki has joined #openstack-meeting-420:37
*** tonytan4ever has quit IRC20:37
*** tonytan4ever has joined #openstack-meeting-420:38
*** rwallner has quit IRC20:40
*** amotoki has quit IRC20:42
*** hippiepete has quit IRC20:42
*** tonytan4ever has quit IRC20:42
*** MeganR has joined #openstack-meeting-420:45
*** bobmel has quit IRC20:50
*** bobmel has joined #openstack-meeting-420:50
*** yamahata has quit IRC20:52
*** iyamahat has quit IRC20:52
*** salv-orlando has joined #openstack-meeting-420:53
*** iyamahat has joined #openstack-meeting-420:56
*** woodard has joined #openstack-meeting-420:59
*** rfolco has quit IRC21:01
*** TxGirlGeek has joined #openstack-meeting-421:02
*** woodard has quit IRC21:03
*** rfolco has joined #openstack-meeting-421:04
*** rfolco has quit IRC21:04
*** yamahata has joined #openstack-meeting-421:06
*** ntpttr has quit IRC21:11
*** pcaruana has quit IRC21:13
*** iyamahat has quit IRC21:17
*** yamahata has quit IRC21:19
*** julim has quit IRC21:19
*** TxGirlGeek has quit IRC21:21
*** hoangcx has joined #openstack-meeting-421:25
*** ntpttr has joined #openstack-meeting-421:25
*** TxGirlGeek has joined #openstack-meeting-421:29
*** yfauser has joined #openstack-meeting-421:30
*** iyamahat has joined #openstack-meeting-421:30
*** rwallner has joined #openstack-meeting-421:31
*** stream10 has joined #openstack-meeting-421:32
*** baoli has joined #openstack-meeting-421:33
*** TxGirlGeek has quit IRC21:34
*** Jeffrey4l has quit IRC21:35
*** yfauser has quit IRC21:35
*** Jeffrey4l has joined #openstack-meeting-421:35
*** rwallner has quit IRC21:35
*** TxGirlGeek has joined #openstack-meeting-421:36
*** TxGirlGeek has quit IRC21:39
*** TxGirlGeek has joined #openstack-meeting-421:39
*** TxGirlGeek has quit IRC21:43
*** TxGirlGeek has joined #openstack-meeting-421:43
*** TxGirlGeek has quit IRC21:45
*** TxGirlGeek has joined #openstack-meeting-421:46
*** cleong has quit IRC21:48
*** yamahata has joined #openstack-meeting-421:48
*** TxGirlGeek has quit IRC21:49
*** uck has joined #openstack-meeting-421:49
*** tonytan4ever has joined #openstack-meeting-421:50
*** jovon has quit IRC21:52
*** yfauser has joined #openstack-meeting-421:59
*** bobmel has quit IRC22:00
*** MeganR has quit IRC22:01
*** thorst has quit IRC22:04
*** thorst has joined #openstack-meeting-422:05
*** thorst has quit IRC22:09
*** kylek3h has quit IRC22:16
*** dave-mccowan has quit IRC22:17
*** cjloader_ has joined #openstack-meeting-422:23
*** baoli has quit IRC22:23
*** FrankZhang has quit IRC22:25
*** limao has joined #openstack-meeting-422:25
*** cjloader has quit IRC22:26
*** s3wong has quit IRC22:27
*** limao_ has joined #openstack-meeting-422:27
*** cjloader_ has quit IRC22:28
*** stream10 has quit IRC22:28
*** limao has quit IRC22:30
*** limao_ has quit IRC22:37
*** limao has joined #openstack-meeting-422:38
*** amotoki has joined #openstack-meeting-422:38
*** amotoki has quit IRC22:42
*** limao_ has joined #openstack-meeting-422:48
*** tonytan4ever has quit IRC22:49
*** gongysh has joined #openstack-meeting-422:50
*** limao has quit IRC22:51
*** stanchan has joined #openstack-meeting-422:57
*** woodard has joined #openstack-meeting-423:00
*** woodard has quit IRC23:04
*** ntpttr_ has joined #openstack-meeting-423:08
*** ntpttr has quit IRC23:08
*** yfauser has quit IRC23:08
*** woodard has joined #openstack-meeting-423:16
*** woodard has quit IRC23:17
*** woodard has joined #openstack-meeting-423:17
*** galstrom is now known as galstrom_zzz23:21
*** hoangcx has quit IRC23:27
*** limao_ has quit IRC23:28
*** woodard has quit IRC23:32
*** woodard has joined #openstack-meeting-423:32
*** klamath has quit IRC23:34
*** woodard has quit IRC23:35
*** salv-orlando has quit IRC23:46
*** gongysh has quit IRC23:57

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