Monday, 2016-07-11

*** banix has quit IRC00:00
*** shaohe_feng has quit IRC00:00
*** ddieterly has joined #openstack-meeting-400:00
*** shaohe_feng has joined #openstack-meeting-400:00
*** sdake has joined #openstack-meeting-400:09
*** itisha has quit IRC00:10
*** shaohe_feng has quit IRC00:10
*** shaohe_feng has joined #openstack-meeting-400:10
*** sdake_ has quit IRC00:11
*** banix has joined #openstack-meeting-400:11
*** spzala has joined #openstack-meeting-400:12
*** ddieterly has quit IRC00:13
*** woodard has joined #openstack-meeting-400:14
*** spzala_ has joined #openstack-meeting-400:19
*** shaohe_feng has quit IRC00:20
*** shaohe_feng has joined #openstack-meeting-400:21
*** spzala has quit IRC00:22
*** banix has quit IRC00:26
*** sdake_ has joined #openstack-meeting-400:26
*** sdake has quit IRC00:29
*** shaohe_feng has quit IRC00:31
*** woodard has quit IRC00:31
*** shaohe_feng has joined #openstack-meeting-400:31
*** woodard has joined #openstack-meeting-400:32
*** bobh has joined #openstack-meeting-400:32
*** limao has joined #openstack-meeting-400:32
*** thorst has joined #openstack-meeting-400:33
*** zeih has joined #openstack-meeting-400:33
*** thorst has quit IRC00:35
*** coolsvap has joined #openstack-meeting-400:35
*** thorst has joined #openstack-meeting-400:36
*** zeih has quit IRC00:38
*** shaohe_feng has quit IRC00:41
*** shaohe_feng has joined #openstack-meeting-400:42
*** spzala_ has quit IRC00:43
*** thorst has quit IRC00:44
*** gongysh has joined #openstack-meeting-400:48
*** shaohe_feng has quit IRC00:51
*** shaohe_feng has joined #openstack-meeting-400:52
*** May-meimei has quit IRC00:59
*** zhurong has joined #openstack-meeting-401:01
*** shaohe_feng has quit IRC01:01
*** shaohe_feng has joined #openstack-meeting-401:02
*** shaohe_feng has quit IRC01:12
*** shz has quit IRC01:12
*** shaohe_feng has joined #openstack-meeting-401:12
*** shz has joined #openstack-meeting-401:13
*** May-meimei has joined #openstack-meeting-401:13
*** zhurong has quit IRC01:14
*** zhurong has joined #openstack-meeting-401:17
*** iceyao has joined #openstack-meeting-401:18
*** shaohe_feng has quit IRC01:22
*** shaohe_feng has joined #openstack-meeting-401:25
*** thorst has joined #openstack-meeting-401:27
*** thorst has quit IRC01:27
*** azbiswas has joined #openstack-meeting-401:28
*** shaohe_feng has quit IRC01:32
*** limao has quit IRC01:32
*** shaohe_feng has joined #openstack-meeting-401:33
*** limao has joined #openstack-meeting-401:33
*** azbiswas has quit IRC01:33
*** zeih has joined #openstack-meeting-401:34
*** zeih has quit IRC01:38
*** ddieterly has joined #openstack-meeting-401:41
*** shaohe_feng has quit IRC01:42
*** shaohe_feng has joined #openstack-meeting-401:43
*** shaohe_feng has quit IRC01:53
*** shaohe_feng has joined #openstack-meeting-401:54
*** ddieterly has quit IRC01:56
*** oanson has joined #openstack-meeting-402:00
*** shaohe_feng has quit IRC02:03
*** shaohe_feng has joined #openstack-meeting-402:03
*** bobh has quit IRC02:06
*** shaohe_feng has quit IRC02:13
*** shaohe_feng has joined #openstack-meeting-402:14
*** shaohe_feng has quit IRC02:23
*** shaohe_feng has joined #openstack-meeting-402:24
*** baoli has joined #openstack-meeting-402:26
*** ddieterly has joined #openstack-meeting-402:26
*** ddieterly has quit IRC02:31
*** shaohe_feng has quit IRC02:34
*** zeih has joined #openstack-meeting-402:35
*** shaohe_feng has joined #openstack-meeting-402:35
*** sdake_ is now known as sdake02:35
*** zeih has quit IRC02:39
*** britthouser has joined #openstack-meeting-402:42
*** shaohe_feng has quit IRC02:44
*** shaohe_feng has joined #openstack-meeting-402:44
*** azbiswas has joined #openstack-meeting-402:49
*** shaohe_feng has quit IRC02:54
*** shaohe_feng has joined #openstack-meeting-402:55
*** britthouser has quit IRC02:56
*** azbiswas has quit IRC03:00
*** coolsvap has quit IRC03:04
*** shaohe_feng has quit IRC03:04
*** shaohe_feng has joined #openstack-meeting-403:05
*** bobh has joined #openstack-meeting-403:07
*** brad_pokorny has joined #openstack-meeting-403:12
*** bobh has quit IRC03:12
*** limao has quit IRC03:13
*** brad_pokorny has quit IRC03:14
*** brad_pokorny has joined #openstack-meeting-403:14
*** shaohe_feng has quit IRC03:15
*** shaohe_feng has joined #openstack-meeting-403:15
*** coolsvap has joined #openstack-meeting-403:17
*** lelouch_ has joined #openstack-meeting-403:20
*** julim has quit IRC03:22
*** yamamot__ has joined #openstack-meeting-403:24
*** baoli has quit IRC03:25
*** shaohe_feng has quit IRC03:25
*** rstarmer has quit IRC03:26
*** shaohe_feng has joined #openstack-meeting-403:26
*** scsnow_ has joined #openstack-meeting-403:31
*** scsnow has quit IRC03:31
*** wxy has joined #openstack-meeting-403:34
*** shaohe_feng has quit IRC03:35
*** zeih has joined #openstack-meeting-403:35
*** shaohe_feng has joined #openstack-meeting-403:36
*** baoli has joined #openstack-meeting-403:37
*** brad_pokorny has quit IRC03:38
*** zeih has quit IRC03:40
*** JRobinson__ is now known as JRobinson__afk03:40
*** lelouch_ has quit IRC03:44
*** shaohe_feng has quit IRC03:45
*** shaohe_feng has joined #openstack-meeting-403:46
*** Sukhdev has joined #openstack-meeting-403:53
*** rstarmer has joined #openstack-meeting-403:54
*** shaohe_feng has quit IRC03:56
*** shaohe_feng has joined #openstack-meeting-403:56
*** azbiswas has joined #openstack-meeting-404:01
*** azbiswas has quit IRC04:02
*** limao has joined #openstack-meeting-404:05
*** shaohe_feng has quit IRC04:06
*** shaohe_feng has joined #openstack-meeting-404:07
*** bobh has joined #openstack-meeting-404:08
*** brad_pokorny has joined #openstack-meeting-404:10
*** dims has quit IRC04:11
*** azbiswas has joined #openstack-meeting-404:12
*** azbiswas has quit IRC04:12
*** amotoki has joined #openstack-meeting-404:13
*** bobh has quit IRC04:14
*** shaohe_feng has quit IRC04:16
*** shaohe_feng has joined #openstack-meeting-404:16
*** jmccrory is now known as jmccrory_away_th04:20
*** jmccrory_away_th is now known as jmccrory_away04:20
*** shaohe_feng has quit IRC04:26
*** shaohe_feng has joined #openstack-meeting-404:27
*** GB21 has joined #openstack-meeting-404:33
*** vikasc has joined #openstack-meeting-404:36
*** zeih has joined #openstack-meeting-404:36
*** shaohe_feng has quit IRC04:37
*** shaohe_feng has joined #openstack-meeting-404:37
*** gongysh has quit IRC04:37
*** TaylorH has joined #openstack-meeting-404:38
*** woodard has quit IRC04:40
*** woodard has joined #openstack-meeting-404:40
*** zeih has quit IRC04:40
*** TaylorHuang has quit IRC04:42
*** sdake has quit IRC04:43
*** woodard has quit IRC04:45
*** shaohe_feng has quit IRC04:47
*** shaohe_feng has joined #openstack-meeting-404:47
*** azbiswas has joined #openstack-meeting-404:50
*** yamamot__ has quit IRC04:51
*** baoli has quit IRC04:52
*** reedip has joined #openstack-meeting-404:55
*** shaohe_feng has quit IRC04:57
*** shaohe_feng has joined #openstack-meeting-404:57
*** irenab has quit IRC04:58
*** vishwanathj has joined #openstack-meeting-405:02
*** vishwanathj has quit IRC05:03
*** azbiswas has joined #openstack-meeting-405:04
*** brad_pokorny has quit IRC05:06
*** shaohe_feng has quit IRC05:07
*** shaohe_feng has joined #openstack-meeting-405:08
*** anilvenkata has joined #openstack-meeting-405:09
*** bobh has joined #openstack-meeting-405:10
*** baoli has joined #openstack-meeting-405:13
*** bobh has quit IRC05:15
*** pcaruana has quit IRC05:17
*** baoli has quit IRC05:17
*** gongysh has joined #openstack-meeting-405:18
*** shaohe_feng has quit IRC05:18
*** shaohe_feng has joined #openstack-meeting-405:19
*** numans has joined #openstack-meeting-405:20
*** dims has joined #openstack-meeting-405:26
*** azbiswas has quit IRC05:26
*** shaohe_feng has quit IRC05:28
*** shaohe_feng has joined #openstack-meeting-405:29
*** sdake has joined #openstack-meeting-405:31
*** sdake has quit IRC05:33
*** zeih has joined #openstack-meeting-405:37
*** shaohe_feng has quit IRC05:38
*** shaohe_feng has joined #openstack-meeting-405:39
*** yamamot__ has joined #openstack-meeting-405:40
*** woodard has joined #openstack-meeting-405:41
*** Sukhdev has quit IRC05:42
*** zeih has quit IRC05:42
*** spzala has joined #openstack-meeting-405:43
*** baoli has joined #openstack-meeting-405:44
*** woodard has quit IRC05:46
*** irenab has joined #openstack-meeting-405:47
*** spzala has quit IRC05:47
*** baoli has quit IRC05:48
*** shaohe_feng has quit IRC05:48
*** shaohe_feng has joined #openstack-meeting-405:49
*** irenab has quit IRC05:55
*** irenab has joined #openstack-meeting-405:57
*** shaohe_feng has quit IRC05:59
*** shaohe_feng has joined #openstack-meeting-405:59
*** rstarmer_ has joined #openstack-meeting-406:02
*** baoli has joined #openstack-meeting-406:05
*** rstarmer has quit IRC06:05
*** oshidoshi has joined #openstack-meeting-406:06
*** rstarmer_ has quit IRC06:07
*** shaohe_feng has quit IRC06:09
*** shaohe_feng has joined #openstack-meeting-406:09
*** baoli has quit IRC06:09
*** reedip has quit IRC06:12
*** javeriak has joined #openstack-meeting-406:12
*** lelouch_ has joined #openstack-meeting-406:16
*** lelouch_ has quit IRC06:18
*** reedip has joined #openstack-meeting-406:19
*** shaohe_feng has quit IRC06:19
*** lelouch_ has joined #openstack-meeting-406:20
*** shaohe_feng has joined #openstack-meeting-406:20
*** JRobinson__afk is now known as JRobinson__06:26
*** lelouch_ has quit IRC06:28
*** shaohe_feng has quit IRC06:29
*** shaohe_feng has joined #openstack-meeting-406:30
*** bobh has joined #openstack-meeting-406:34
*** gongysh has quit IRC06:37
*** zeih has joined #openstack-meeting-406:38
*** bobh has quit IRC06:38
*** shaohe_feng has quit IRC06:40
*** shaohe_feng has joined #openstack-meeting-406:43
*** zeih has quit IRC06:43
*** shaohe_feng has quit IRC06:50
*** woodard has joined #openstack-meeting-406:50
*** shaohe_feng has joined #openstack-meeting-406:51
*** pcaruana has joined #openstack-meeting-406:51
*** woodard has quit IRC06:55
*** shaohe_feng has quit IRC07:00
*** shaohe_feng has joined #openstack-meeting-407:01
*** baoli has joined #openstack-meeting-407:02
*** limao has quit IRC07:02
*** limao has joined #openstack-meeting-407:03
*** coolsvap has quit IRC07:05
*** alexchadin has joined #openstack-meeting-407:05
*** coolsvap has joined #openstack-meeting-407:06
*** nkrinner_afk is now known as nkrinner07:07
*** baoli has quit IRC07:07
*** shaohe_feng has quit IRC07:10
*** shaohe_feng has joined #openstack-meeting-407:11
*** lelouch_ has joined #openstack-meeting-407:17
*** gongysh has joined #openstack-meeting-407:17
*** shaohe_feng has quit IRC07:21
*** shaohe_feng has joined #openstack-meeting-407:21
*** azbiswas has joined #openstack-meeting-407:27
*** GB21 has quit IRC07:29
*** dtardivel has joined #openstack-meeting-407:30
*** shaohe_feng has quit IRC07:31
*** shaohe_feng has joined #openstack-meeting-407:32
*** azbiswas has quit IRC07:32
*** shz has quit IRC07:33
*** shihanzhang has joined #openstack-meeting-407:34
*** bobh has joined #openstack-meeting-407:35
*** zeih has joined #openstack-meeting-407:39
*** bobh has quit IRC07:39
*** shaohe_feng has quit IRC07:41
*** zeih has quit IRC07:44
*** shaohe_feng has joined #openstack-meeting-407:44
*** coolsvap has quit IRC07:49
*** shaohe_feng has quit IRC07:51
*** GB21 has joined #openstack-meeting-407:51
*** shaohe_feng has joined #openstack-meeting-407:52
*** alexchadin has quit IRC07:54
*** alexchadin has joined #openstack-meeting-407:55
*** mfedosin has joined #openstack-meeting-407:56
*** coolsvap has joined #openstack-meeting-408:00
*** shaohe_feng has quit IRC08:02
*** shaohe_feng has joined #openstack-meeting-408:02
*** vikasc has quit IRC08:05
*** shaohe_feng has quit IRC08:12
*** shaohe_feng has joined #openstack-meeting-408:12
*** sshnaidm|afk is now known as sshnaidm08:16
*** JRobinson__ has quit IRC08:16
*** alexchadin has quit IRC08:19
*** alexchadin has joined #openstack-meeting-408:20
*** shaohe_feng has quit IRC08:22
*** shaohe_feng has joined #openstack-meeting-408:23
*** shaohe_feng has quit IRC08:32
*** shaohe_feng has joined #openstack-meeting-408:33
*** vikasc has joined #openstack-meeting-408:33
*** zeih has joined #openstack-meeting-408:40
*** javeriak has quit IRC08:42
*** shaohe_feng has quit IRC08:43
*** Wang_jian has joined #openstack-meeting-408:44
*** zeih has quit IRC08:45
*** shaohe_feng has joined #openstack-meeting-408:45
*** nkrinner_ has joined #openstack-meeting-408:50
*** DuanKebo has joined #openstack-meeting-408:51
*** alexchadin has quit IRC08:52
*** nkrinner has quit IRC08:53
*** shaohe_feng has quit IRC08:53
*** shaohe_feng has joined #openstack-meeting-408:53
*** dshakhray has joined #openstack-meeting-408:54
*** gsagie has joined #openstack-meeting-408:57
*** yuli_s has joined #openstack-meeting-408:59
*** bauwser is now known as bauzas09:00
gsagieoanson?09:02
gsagieanyone here for Dragonflow IRC meeting?09:02
nick-maI'm here09:03
DuanKeboI'm here09:03
oansonHi09:03
oansonSorry I'm late09:03
*** shaohe_feng has quit IRC09:03
oanson#startmeeting Dragonflow09:03
openstackMeeting started Mon Jul 11 09:03:46 2016 UTC and is due to finish in 60 minutes.  The chair is oanson. Information about MeetBot at http://wiki.debian.org/MeetBot.09:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:03
*** openstack changes topic to " (Meeting topic: Dragonflow)"09:03
openstackThe meeting name has been set to 'dragonflow'09:03
*** shaohe_feng has joined #openstack-meeting-409:03
*** yuanwei has joined #openstack-meeting-409:04
*** alexchadin has joined #openstack-meeting-409:04
oanson#info gsagie, nick-ma, DuanKebo is in the meeting.09:04
oansonIs anyone else here for the Dragonflow meeting?09:04
oansonAll right, then let's get started09:05
oanson#topic Roadmap09:05
*** openstack changes topic to "Roadmap (Meeting topic: Dragonflow)"09:05
oansonReminder, the Newton roadmap link is here: https://etherpad.openstack.org/p/dragonflow-newton09:05
oanson#link https://etherpad.openstack.org/p/dragonflow-newton09:05
oansonI'll start with my update about packaging and distribution: Sadly I wasn't able to make much progress.09:06
oansonI am in China this week for openstack days china and collaborating with DuanKebo and team, so I probably won't have it ready for next week either.09:06
*** javeriak has joined #openstack-meeting-409:08
*** ricolin has joined #openstack-meeting-409:08
oansonI'm waiting a second for the others to join. Then we can talk about DB synchronisation, ML2, and VLAN.09:08
oansonIf anyone wants to take the floor, it's available09:08
*** hshan has joined #openstack-meeting-409:08
*** nkrinner_ is now known as nkrinner09:08
oansonhujie, wangyongben, liuhaixia, are you here?09:09
oansonhujie says he commited a patch. The link is: https://review.openstack.org/33637709:11
oansonHe'd be happy for reviews.09:12
oansonliuhaxia also made the ML2 patch smaller. It contains only L2 for ML2. It is available here: https://review.openstack.org/#/c/334798/09:12
oansonPatches for vxlan, vlan, and flat networks will come later. vlan and flat will depend on vxlan, so they may come after it is merged (or at least passes a few review cycles)09:13
*** shaohe_feng has quit IRC09:13
*** jed56 has joined #openstack-meeting-409:14
*** feipeng1 has joined #openstack-meeting-409:14
oansonwangyongben uploaded the L3 plugin to here: https://review.openstack.org/#/c/316785/ . It also needs reviews.09:14
hshanhshan is online, there are not only omer himself having meeting :)09:14
*** shaohe_feng has joined #openstack-meeting-409:14
oanson#link https://review.openstack.org/#/c/316785/09:15
oanson#link https://review.openstack.org/#/c/334798/09:15
oanson#link https://review.openstack.org/33637709:15
oansonAny other updates someone wants to share?09:15
gsagienot here09:16
oansonAll right.09:16
oanson#topic Barcelona Summit09:16
*** openstack changes topic to "Barcelona Summit (Meeting topic: Dragonflow)"09:16
oansonThe call for presentations end this week09:17
oansonIf you want to submit a talk, you need to prepare your title and abstract as soon as possible09:17
*** hujie has joined #openstack-meeting-409:17
oansonIt is highly recommended to go if possible. We can meet and attract new people to work on dragonflow.09:17
oansonI guess the talks might be interesting as well :)09:18
oansonAnyone has anything to add on this topic?09:18
nick-maI was thinking of the talks, not sure about which topics can cover the whole 40 minutes.09:19
nick-main the last summit, we did one for general introduction.09:19
oansonnick-ma: Each of the talks I'm submitting is comprised from 3 smaller titles that I tied together.09:20
*** barmaley has joined #openstack-meeting-409:20
oansonnick-ma: I think oshidoshi may have a few ideas that are still missing submitters.09:22
gsagiei think we can take this offline09:22
nick-mayes.09:22
oansonagreed.09:22
oansonAnything else here?09:23
oanson#topic Performance Testing09:23
*** openstack changes topic to "Performance Testing (Meeting topic: Dragonflow)"09:23
oansonyuli_s: I understand you have done some work here?09:23
gsagienot sure he is here09:24
*** shaohe_feng has quit IRC09:24
gsagieahh yes09:24
gsagiehe is09:24
*** shaohe_feng has joined #openstack-meeting-409:24
oansonHis user is here09:24
gsagieyuli_s is working on implementing end-to-end enviorments09:24
gsagieto test both control and data plane performance09:25
gsagieso instead of only testing the DB backends we can tests it all09:25
oansonHow is he setting up the environments?09:25
gsagiehe is checking ansible/vagrant now to do the env installation09:25
gsagiewith your project09:25
gsagieor with openstack-ansible09:26
oansonThat's great. I'll sit with him and collaborate when I get back.09:26
oansonThe best solution would be to use both - my project to set up VMs using vagrant, and openstack-ansible for installation.09:27
oansonThis will push the deployment project forwards as well.09:27
DuanKeboIf we want to do the large scale test, we need lots of servers09:27
oansonDuanKebo: openstack-ansible should be usable on both virtual and physical servers09:28
nick-macan be simulated?09:28
oansonHowever, we need these physical servers somewhere.09:28
hujieIn the discussion last time, we said we will have 20 servers for redis db cluster, not for the local controller server, it that enough??09:28
hujiefor simulation09:29
oansonhujie: I think it's enough for a start. Enough to test the deployment and get initial results.09:29
hujiegood :)09:29
oansonBut the best thing would be as many servers as possible to run a real test, and be able to prove we scale to as many nodes we say we scale.09:29
DuanKeboI'm not sure, but i think simulated ways may be more viable for large scale test.09:30
DuanKebothinking about how to test DC with 10,000 servers.09:31
nick-ma:-)09:31
oansonDuanKebo: That's where ansible comes in - it should allow us to provision the servers from a single location.09:31
*** gongysh has quit IRC09:32
hujiethe deployment is not bottleneck for DC with 10,000 servers.09:32
oansonhujie: So wher's the bottleneck?09:32
DuanKeboproblem is we can deploy so many servers.09:33
nick-maso you have 10,000 real servers in single location for testbed?09:33
DuanKebo* can not09:33
oansonDuanKebo, hujie, the deployment is or is not the bottleneck?09:33
DuanKeboisn't09:34
oansonIf we have a deployment solution, is there anything else that's blocking us (provided we have the servers)09:34
*** coolsvap has quit IRC09:34
gsagieoanson: i think what hujie and DuanKebo are saying the deployment tool is not a problem09:34
gsagieits only physical resources09:34
*** shaohe_feng has quit IRC09:34
hujiethe test method and the control and data plane performance is more important I think :)09:34
*** shaohe_feng has joined #openstack-meeting-409:34
oansonThis is something yuli_s and Shlomo_N are working on.09:35
hujieyes, the deployment tool is good itself and for dragonflow :)09:35
*** coolsvap has joined #openstack-meeting-409:35
gsagiehujie: for data plane performance we dont need many servers09:35
oansonShlomo_N has a patch here: https://review.openstack.org/#/c/304470/09:35
gsagiefor control plane testing we will do a simulated tests09:35
gsagiewe will of course try to squeeze as much "local controllers" as possible in one server09:35
oansonyuli_s has a control plane test here: https://review.openstack.org/#/c/309948/09:35
DuanKebowe haven't so many servers. So we have calculate the control plane and data plane traffic, and simulate it.09:35
*** bobh has joined #openstack-meeting-409:35
gsagieusually its best to run them 1 per core so we wont get into scheduling problems09:35
DuanKeboYes, Gal09:36
gsagieDuanKebo: lets start with what we have09:36
gsagiewe dont need to start with 10,00009:36
*** igordcard has joined #openstack-meeting-409:36
gsagiehow many do we have?09:36
hujieI think for DC with 10,000 servers, deployment is necessary and good thing, but it's not what we truely worried :)09:37
gsagieincluding your servers09:37
*** barmaley has quit IRC09:37
oansonobviously. As I said, the 20 servers is definitely enough for a start09:37
yuanweiDuanKebo: If we have 20 servers?09:37
DuanKeboYes, we have09:37
gsagiearound how many cores each?09:37
gsagie12, 14?09:37
DuanKebo16 maybe09:37
gsagieok so thats 320 local controllers09:38
gsagiethat we can run on them09:38
oansongsagie: Some of them should be compute nodes09:38
gsagielets say less09:38
oansonIf we want to test end-to-end and not just controll plane09:38
gsagieso we have around 20009:38
oansonSome should also be database.09:38
oansonI think perhaps we should construct a testing plan, and then decide how many nodes of each we need.09:39
DuanKeboYes, I worry about db and pub/sub performance09:39
oansonWe can say that we have 320 simulated servers for now, but I don't think it's that important.09:39
oansonLet's get the testing framework and deployment finished first.09:39
nick-maif the computing resource is containers we can save much resource.09:40
DuanKeboOmer, we are working on the test plan09:40
hujieOK, we can move on to do the deployment work and design the test plan :)09:40
oansonI'll step on deployment it next week. I'll also help yuli_s to get the testing framework finished as soon as possible.09:40
*** bobh has quit IRC09:40
oansonnick-ma: I think that's the direction yuli_s is taking.09:40
gsagiethe problem with containers is OVS09:40
oansonDuanKebo: Great. I'd be happy to see it after the meeting.09:41
gsagiewe will need to do work to "simulate" the kernel module09:41
gsagiesince it will be shared09:41
*** zeih has joined #openstack-meeting-409:41
oansongsagie: Can be worked around, maybe with a OVS bridge per container.09:41
DuanKeboIt's not ready yes.^o^09:41
DuanKebonot ready yet09:41
oansonDuanKebo: Sorry. I'm enthusiastic :)09:42
oansongsagie: Can the OVS+container be worked around with an OVS bridge per container?09:42
nick-maok, get it.09:42
gsagieoanson: we need to think about it, because we will need something that creates the ports and connect them to each container09:42
gsagieand simulate the OVSDB events09:43
gsagieso it can work but it need some work09:43
oansongsagie: So we'll do the work :)09:43
DuanKebomaybe we need kuryr to do this ?09:43
gsagieit might be faster to just use user space OVS part and not use the kernel module as we only checking the control plane09:43
gsagieyuli_s is suppose to check it09:44
gsagiesoon09:44
*** spzala has joined #openstack-meeting-409:44
gsagieDuanKebo: we will need kuryr09:44
gsagiefor this09:44
*** mfedosin has quit IRC09:44
gsagieif we use Docker09:44
oansongsagie: I thought we're checking end to end.09:44
*** shaohe_feng has quit IRC09:44
*** shaohe_feng has joined #openstack-meeting-409:45
gsagieoanson: "end-to-end" as in using Dragonflow controller full code, but we can still ignore the part that install flows to OVS given that can help09:45
*** zeih has quit IRC09:45
gsagiebut again yuli_s will check it09:45
gsagieand hopefully provide some insights next week09:45
*** alexchadin has quit IRC09:46
oansonAll right, let's wait till next week. We'll also figure out what end-to-end means once the test plan is ready :)09:46
oansonAnything else in this topic?09:46
oanson#topic Bugsw09:46
*** openstack changes topic to "Bugsw (Meeting topic: Dragonflow)"09:46
oanson#topic Bugs09:46
*** openstack changes topic to "Bugs (Meeting topic: Dragonflow)"09:46
gsagiethe meaning is not end-to-end as in test the entire system but test the controller instead of just the DB09:46
gsagiewhich is what was done till now09:47
*** zenoway has joined #openstack-meeting-409:47
oansonAll right.09:47
*** lelouch_ has quit IRC09:48
nick-mathe fullstack is.failed due to arpresponder.test.simple.response. but it really works in my local machine.09:48
*** spzala has quit IRC09:48
oansonnick-ma: Yes. It works locally for me as well.09:48
nick-maalso the ryu 4.409:48
*** GB21 has quit IRC09:48
nick-maryu breaks secgroup.09:49
oansonAbout ryu09:49
oansonyamamoto and iwamoto say that the change should be reverted in ryu09:49
*** igordcard has quit IRC09:49
oansonThey brought this up in their mailing list, but I didn't see any progress yet.09:49
*** igordcard has joined #openstack-meeting-409:49
nick-mai suggest we first revert to 4.3 if.possible. and wait for the upstream change09:49
oansonWe can't revert, because we are locked to the openstack requirements09:50
nick-magot it.09:50
oansonI though of aligning ourselves, and reverting if the upstream changes.09:50
oansonIt's more work for us, but at least our code will work.09:50
oansonand I don't know if and when the upstream will change.09:50
nick-mathat is the problem09:50
oansonI will try and catch Yamamoto offline and discuss it. See what he thinks, what our chances are, and what is the expected change in ryu.09:51
oansonbecause any change will either break ryu 4.4, or keep <=4.3 broken.09:51
oansonDue to the API changes they have made.09:52
nick-maok.09:53
oansonnick-ma: I see you opened a bug about the ARP responder test.09:53
nick-mai am trying to figure out why. we didn't change any codes related09:53
nick-mato it09:53
oansonI suspect the gate test will have to be debugged.09:54
nick-mayes.09:54
*** shaohe_feng has quit IRC09:54
oansonAny other items here?09:55
nick-maby the way, suggest we clean up the bug list of launchpad, lots of them are out of date.09:55
oansonYes. Each bug should be verified, and marked invalid if appropriate.09:56
DuanKeboYes, nick09:56
nick-mai went through most of them, but lots of.them are assigned, so not sure the progress09:56
oansonI suggest that everyone go over the bugs they are assigned, and verify them.09:57
oansonBugs that haven't been updated in a while, or owners that have been inactive for a while should be pinged.09:57
nick-maafaik, lots of.them are invalid due to testing09:57
*** shihanzhang has quit IRC09:58
oansonI see also that there are many undecided importance bugs.09:59
oansonyuli_s, as our bugmaster: Will you rate them?09:59
*** shihanzhang has joined #openstack-meeting-409:59
oansonHe might still not be here.09:59
oansonAll right. That's our time.10:01
oansonThanks everyone.10:01
oanson#endmeeting10:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"10:01
openstackMeeting ended Mon Jul 11 10:01:34 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:01
*** shaohe_feng has joined #openstack-meeting-410:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-07-11-09.03.html10:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-07-11-09.03.txt10:01
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-07-11-09.03.log.html10:01
*** Wang_jian has quit IRC10:01
DuanKebothanks, bye!10:01
nick-mabye10:01
*** muneeb has joined #openstack-meeting-410:04
*** GB21 has joined #openstack-meeting-410:04
*** shaohe_feng has quit IRC10:05
*** shaohe_feng has joined #openstack-meeting-410:06
*** javeriak has quit IRC10:09
*** shaohe_feng has quit IRC10:15
*** shaohe_feng has joined #openstack-meeting-410:16
*** vikasc has quit IRC10:17
*** zeih has joined #openstack-meeting-410:17
*** vishnoianil has joined #openstack-meeting-410:18
*** GB21 has quit IRC10:19
*** zhurong has quit IRC10:24
*** shaohe_feng has quit IRC10:25
*** shaohe_feng has joined #openstack-meeting-410:26
*** iceyao has quit IRC10:27
*** limao has quit IRC10:28
*** alexchadin has joined #openstack-meeting-410:33
*** javeriak has joined #openstack-meeting-410:33
*** gsagie has left #openstack-meeting-410:33
*** vikasc has joined #openstack-meeting-410:35
*** shaohe_feng has quit IRC10:35
*** shaohe_feng has joined #openstack-meeting-410:36
*** bobh has joined #openstack-meeting-410:36
*** stanchan has quit IRC10:39
*** bobh has quit IRC10:41
*** kzaitsev_mb has joined #openstack-meeting-410:43
*** shaohe_feng has quit IRC10:46
*** shaohe_feng has joined #openstack-meeting-410:46
*** thorst has joined #openstack-meeting-410:46
*** thorst has quit IRC10:47
*** thorst has joined #openstack-meeting-410:47
*** vikasc has quit IRC10:49
*** thorst_ has joined #openstack-meeting-410:50
*** thorst has quit IRC10:52
*** lelouch_ has joined #openstack-meeting-410:54
*** GB21 has joined #openstack-meeting-410:54
*** shaohe_feng has quit IRC10:56
*** shaohe_feng has joined #openstack-meeting-410:56
*** cdelatte has joined #openstack-meeting-410:59
*** ricolin has quit IRC11:05
*** shaohe_feng has quit IRC11:06
*** shaohe_feng has joined #openstack-meeting-411:07
*** vikasc has joined #openstack-meeting-411:13
*** pbourke_ has joined #openstack-meeting-411:14
*** sigmavirus_away is now known as sigmavirus11:14
*** pbourke- has joined #openstack-meeting-411:14
*** shaohe_feng has quit IRC11:16
*** shaohe_feng has joined #openstack-meeting-411:17
*** sdake has joined #openstack-meeting-411:19
*** xiaohhui has quit IRC11:21
*** muneeb has quit IRC11:21
*** xiaohhui has joined #openstack-meeting-411:21
*** TaylorH has quit IRC11:22
*** TaylorH has joined #openstack-meeting-411:22
*** pbourke_ has quit IRC11:23
*** muneeb has joined #openstack-meeting-411:23
*** shaohe_feng has quit IRC11:27
*** shaohe_feng has joined #openstack-meeting-411:27
*** Jeffrey4l has joined #openstack-meeting-411:27
*** vikasc has quit IRC11:29
*** azbiswas has joined #openstack-meeting-411:30
*** azbiswas has quit IRC11:35
*** jed56 has quit IRC11:35
*** shaohe_feng has quit IRC11:37
*** shaohe_feng has joined #openstack-meeting-411:38
*** pbourke_ has joined #openstack-meeting-411:39
*** baoli has joined #openstack-meeting-411:40
*** hujie has left #openstack-meeting-411:40
*** mfedosin has joined #openstack-meeting-411:40
*** banix has joined #openstack-meeting-411:41
*** pbourke| has joined #openstack-meeting-411:44
*** baoli has quit IRC11:44
*** banix has quit IRC11:44
*** iceyao has joined #openstack-meeting-411:45
*** shaohe_feng has quit IRC11:47
*** sdake has quit IRC11:48
*** shaohe_feng has joined #openstack-meeting-411:48
*** pbourke^ has joined #openstack-meeting-411:49
*** pbourke- has quit IRC11:49
*** muneeb has quit IRC11:49
*** pbourke_ has quit IRC11:50
*** pbourke| has quit IRC11:50
*** dmburmistrov has quit IRC11:52
*** pbourke^ has quit IRC11:55
*** shaohe_feng has quit IRC11:57
*** shaohe_feng has joined #openstack-meeting-411:58
*** ddieterly has joined #openstack-meeting-411:58
*** woodard has joined #openstack-meeting-411:58
*** ddieterly has quit IRC12:03
*** banix has joined #openstack-meeting-412:07
*** iurygregory has joined #openstack-meeting-412:08
*** shaohe_feng has quit IRC12:08
*** shaohe_feng has joined #openstack-meeting-412:08
*** coolsvap has quit IRC12:18
*** shaohe_feng has quit IRC12:18
*** shaohe_feng has joined #openstack-meeting-412:18
*** banix has quit IRC12:20
*** woodard has quit IRC12:27
*** shaohe_feng has quit IRC12:28
*** shaohe_feng has joined #openstack-meeting-412:29
*** sshnaidm is now known as sshnaidm|afk12:29
*** gampel has joined #openstack-meeting-412:34
*** GB21 has quit IRC12:37
*** shaohe_feng has quit IRC12:38
*** shaohe_feng has joined #openstack-meeting-412:39
*** automagically has joined #openstack-meeting-412:40
*** ddieterly has joined #openstack-meeting-412:41
*** spzala has joined #openstack-meeting-412:42
*** zhurong has joined #openstack-meeting-412:42
*** gampel has quit IRC12:42
*** uck has joined #openstack-meeting-412:45
*** spzala has quit IRC12:46
*** ddieterly has quit IRC12:46
*** shaohe_feng has quit IRC12:49
*** shaohe_feng has joined #openstack-meeting-412:49
*** cbits has joined #openstack-meeting-412:54
*** ddieterly has joined #openstack-meeting-412:59
*** shaohe_feng has quit IRC12:59
*** shaohe_feng has joined #openstack-meeting-412:59
*** bobh has joined #openstack-meeting-413:00
*** itisha has joined #openstack-meeting-413:03
*** klamath has joined #openstack-meeting-413:05
*** klamath has quit IRC13:05
*** klamath has joined #openstack-meeting-413:06
*** sshnaidm|afk is now known as sshnaidm13:06
*** javeriak has quit IRC13:07
*** markvoelker has joined #openstack-meeting-413:08
*** shaohe_feng has quit IRC13:09
*** shaohe_feng has joined #openstack-meeting-413:10
*** ddieterly is now known as ddieterly[away]13:12
*** ddieterly[away] has quit IRC13:12
*** julim has joined #openstack-meeting-413:13
*** spzala has joined #openstack-meeting-413:14
*** david-lyle has quit IRC13:15
*** cleong has joined #openstack-meeting-413:19
*** shaohe_feng has quit IRC13:19
*** shaohe_feng has joined #openstack-meeting-413:20
*** automagically has left #openstack-meeting-413:21
*** jcook has quit IRC13:26
*** markvoelker has quit IRC13:27
*** irenab has quit IRC13:27
*** shaohe_feng has quit IRC13:30
*** alexchadin has quit IRC13:30
*** stanchan has joined #openstack-meeting-413:30
*** alexchadin has joined #openstack-meeting-413:30
*** shaohe_feng has joined #openstack-meeting-413:30
*** marst has joined #openstack-meeting-413:36
*** luis5tb has quit IRC13:37
*** singlethink has joined #openstack-meeting-413:38
*** woodster_ has joined #openstack-meeting-413:39
*** shaohe_feng has quit IRC13:40
*** shaohe_feng has joined #openstack-meeting-413:40
*** jcook has joined #openstack-meeting-413:45
*** ddieterly has joined #openstack-meeting-413:47
*** sdake has joined #openstack-meeting-413:48
*** alexchadin has quit IRC13:48
*** sdake_ has joined #openstack-meeting-413:49
*** sarob has joined #openstack-meeting-413:49
*** sdake has quit IRC13:49
*** ddieterly is now known as ddieterly[away]13:50
*** ddieterly[away] is now known as ddieterly13:50
*** shaohe_feng has quit IRC13:50
*** shaohe_feng has joined #openstack-meeting-413:50
*** anilvenkata has quit IRC13:51
*** vishwanathj has joined #openstack-meeting-413:52
*** banix has joined #openstack-meeting-413:54
*** banix has quit IRC13:54
*** cartik has joined #openstack-meeting-413:55
*** banix has joined #openstack-meeting-413:55
*** shaohe_feng has quit IRC14:00
*** shaohe_feng has joined #openstack-meeting-414:01
*** ddieterly is now known as ddieterly[away]14:01
*** markvoelker has joined #openstack-meeting-414:02
*** dasanind has joined #openstack-meeting-414:05
*** jcook has quit IRC14:06
*** tonytan4ever has joined #openstack-meeting-414:07
*** markvoelker has quit IRC14:07
*** zhurong has quit IRC14:08
*** dasanind has quit IRC14:09
*** dasanind has joined #openstack-meeting-414:09
*** yamamot__ has quit IRC14:10
*** shaohe_feng has quit IRC14:11
*** sarob has quit IRC14:11
*** shaohe_feng has joined #openstack-meeting-414:11
*** sarob has joined #openstack-meeting-414:12
*** uxdanielle has joined #openstack-meeting-414:12
*** marst has quit IRC14:12
*** marst has joined #openstack-meeting-414:12
*** spotz_zzz is now known as spotz14:13
*** ddieterly[away] is now known as ddieterly14:14
*** rbak_ has quit IRC14:15
*** banix has quit IRC14:16
*** markvoelker has joined #openstack-meeting-414:17
*** cartik has quit IRC14:17
*** shaohe_feng has quit IRC14:21
*** banix has joined #openstack-meeting-414:22
*** jcook has joined #openstack-meeting-414:22
*** markvoelker has quit IRC14:23
*** uck has quit IRC14:23
*** shaohe_feng has joined #openstack-meeting-414:24
*** shaohe_feng has quit IRC14:31
*** shaohe_feng has joined #openstack-meeting-414:32
*** oshidoshi has quit IRC14:32
*** daneyon has joined #openstack-meeting-414:33
*** baoli has joined #openstack-meeting-414:34
*** yuli_s has quit IRC14:35
*** baoli has quit IRC14:38
*** shaohe_feng has quit IRC14:41
*** oshidoshi has joined #openstack-meeting-414:42
*** shaohe_feng has joined #openstack-meeting-414:42
*** piet has joined #openstack-meeting-414:43
*** oshidoshi has quit IRC14:44
*** daneyon has quit IRC14:44
*** oshidoshi1 has joined #openstack-meeting-414:44
*** sarob has quit IRC14:45
*** bobh has quit IRC14:46
*** yuli_s has joined #openstack-meeting-414:47
*** sdake_ has quit IRC14:47
*** markvoelker has joined #openstack-meeting-414:48
*** daneyon has joined #openstack-meeting-414:48
*** alexchadin has joined #openstack-meeting-414:49
*** alexchadin has quit IRC14:52
*** shaohe_feng has quit IRC14:52
*** shaohe_feng has joined #openstack-meeting-414:52
*** hvprash has joined #openstack-meeting-414:55
*** nkrinner is now known as nkrinner_afk14:57
*** piet has quit IRC14:58
*** rbak has joined #openstack-meeting-414:58
jimbaker#startmeeting craton14:59
openstackMeeting started Mon Jul 11 14:59:05 2016 UTC and is due to finish in 60 minutes.  The chair is jimbaker. Information about MeetBot at http://wiki.debian.org/MeetBot.14:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:59
*** openstack changes topic to " (Meeting topic: craton)"14:59
openstackThe meeting name has been set to 'craton'14:59
*** yuli_s1 has joined #openstack-meeting-414:59
jimbakertoday's agenda can be found here: https://etherpad.openstack.org/p/craton-meetings14:59
*** oshidoshi1 has quit IRC14:59
jimbakersulo, hi14:59
jimbakersarob cannot make it15:00
suloo/15:00
jimbakero/15:00
*** daneyon has quit IRC15:00
sigmaviruso/15:00
*** yuli_s has quit IRC15:00
*** piet has joined #openstack-meeting-415:01
*** oshidoshi has joined #openstack-meeting-415:01
jimbaker#topic user stories15:01
*** nkrinner_afk is now known as nkrinner15:01
*** openstack changes topic to "user stories (Meeting topic: craton)"15:01
jimbakerwe have been working against the user stories: https://specs.openstack.org/openstack/openstack-user-stories/user-stories/proposed/fleet-management.html15:02
*** shaohe_feng has quit IRC15:02
*** turvey has joined #openstack-meeting-415:02
*** shaohe_feng has joined #openstack-meeting-415:03
jimbakerkencjohnston and KrishR have curated these stories, and we have agreed they are broadly applicable to fleet management and craton specifically15:03
*** yuli_s1 has quit IRC15:03
*** woodard has joined #openstack-meeting-415:04
*** cmspence has joined #openstack-meeting-415:04
jimbakerbecause the stories are high level, to make them actionable i believe we need to focus on representative stories; define acceptance criteria; and build out accordingly15:04
jimbakerturvey, o/15:04
jimbakercmspence, o/15:04
cmspenceo/15:04
turveyo/15:05
jimbakerthe specific story that seems to be most straightforward for us to work on is FLT00515:05
jimbakerFLT005 - As a cloud operator, I need to check my deployed physical resources against a set of policies and rules, so that I can meet security, availability and other requirements15:06
jimbakeri believe auditing with the OSA security role lets us go deep. also we can work with mhayden on it15:06
*** david-lyle has joined #openstack-meeting-415:07
*** nkrinner is now known as nkrinner_afk15:07
jimbakersulo, we are pretty close to having OSA container modeling working against craton inventory, right?15:07
suloyeah15:07
*** dharinic_ has joined #openstack-meeting-415:07
suloso that .. and in general a model to allow network devices too15:08
suloso we can do things that are raised here :https://docs.google.com/document/d/1N3f_H3bjZ1a08wkxRLCMt5ANXRGmFAOEUZ_mtI3BYxw/edit15:08
suloi.e being able to use switches / cabs15:09
*** yamamoto has joined #openstack-meeting-415:09
sulothat is useful for osa as well btw15:09
jimbakersulo, so your PR re device hierarchies is essential for this to happen?15:09
suloyes15:09
jimbakerwith respect to OSA containers?15:09
jimbakerack15:09
sulojimbaker: so like i was discussing with you in #craton15:10
sulothe question is: do we want to model each of these as separate models vs doing how i did in that par .. with a column tracking host_type15:10
jimbakersulo, my questions for you and the team, and not necessarily something we can decide on now15:10
jimbakersulo, yeah, that's an additional question to mine then :)15:11
sulojimbaker: yeah .. we can resume that discussion in craton15:11
sulojimbaker: my point is as soon as we agree on a model . . i think we can solve for both those items15:11
jimbakerno worries, we just want to publicly capture these questions15:11
jimbakeri would add: 1) do we fully capture as a DAG?15:11
jimbaker2) do variables inherit in this hierarchy?15:12
*** shaohe_feng has quit IRC15:12
jimbaker(if we model as a DAG, we get much closer to oneops core modeling, which will help convergence there)15:12
jimbakeranyway, i think we should resolve these questions this week15:13
jimbakerso that seems like an action item to me15:13
*** shaohe_feng has joined #openstack-meeting-415:13
suloso DAG model is close to what we are trying to do through devices like the pr right now ?15:14
*** yamamoto has quit IRC15:14
jimbakersulo, yes15:14
*** pcaruana has quit IRC15:15
sulojimbaker: so what does fully capturing DAG involve ?15:15
sulojust trying to understand really15:15
suloare we missing something on that .. ?15:16
jimbakersulo, sure - you just need a src, dest associative table15:16
*** yuli_s1 has joined #openstack-meeting-415:16
*** numans has quit IRC15:16
jimbakerand outside of the db you need to support computing things like transitive closure15:16
jimbakerand ensuring it's actually acyclic15:16
sulook15:17
sulojimbaker: but we also need variable hierarchy right ? so i guess we do both ?15:17
jimbakerit seems more complicated if we want to have variable overrides participate in the DAG, so my question of whether we need that modeling power15:17
jimbakersulo, right, we are obviously thinking of similar things :)15:18
jimbakerso i don't know the answers. just want to ask the questions to we can model the things we care about15:18
jimbakeranyway, two action items here15:19
jimbaker#action define acceptance criteria for FLT00515:19
jimbaker#action jimbaker define acceptance criteria for FLT00515:19
jimbaker#action jimbaker sulo finalize modeling of device hierarchy, considering DAG, variables15:20
jimbakerlook good?15:20
*** Gerald__ has joined #openstack-meeting-415:20
suloyes15:20
jimbaker#topic inventory fabric15:21
*** openstack changes topic to "inventory fabric (Meeting topic: craton)"15:21
*** iceyao has quit IRC15:22
jimbakersulo, this is a term i started using to explain to stakeholders what craton is trying to do in terms of managing sources of truth for inventory15:22
*** alexchadin has joined #openstack-meeting-415:22
*** shaohe_feng has quit IRC15:22
sulojimbaker: heh, cool15:22
jimbakerit's not trying to do everything... but perhaps it can integrate with arbitrary other systems, via plugins15:23
sulojimbaker: so i've had a few meetings with osa folks last week on how we can achieve this15:23
*** shaohe_feng has joined #openstack-meeting-415:23
sulothere is a good discussion going on here also :https://github.com/rackerlabs/craton/issues/1215:24
jimbakerso if we have a network inventory system like arista; or nova is managing the scheduling of VMs to hosts... that's the role of the fabric15:24
jimbakerand presumably virtualized variables15:24
jimbakerhttps://github.com/rackerlabs/craton/issues/10915:24
*** dasanind has quit IRC15:24
jimbakersulo, so any updates from OSA on this from that email thread?15:25
jimbaker(it15:25
sulowell lots of feedback during my meeting .. and on that issue i posted above15:25
jimbakersure, just wanted a summary here15:26
sulobut the main point to start with is : being able to support config data such that we can generate a ansible inventory to run a playbook15:26
*** beisner has joined #openstack-meeting-415:26
suloand to do that we need to address quite a few issues15:26
*** alexchadin has quit IRC15:27
*** david-lyle has quit IRC15:27
sulolike 1. this should be templated enough that inital variable generation15:27
suloand host and group generation is super easy15:27
*** dasanind has joined #openstack-meeting-415:27
sulo2. we support variable override in the way you have captured in various issues already15:27
sulo3. we support containers and deives as in my pr15:28
suloso we are moving towards it15:28
sulobut there is some more work to be done .. mostly on config/variables side15:28
*** Gerald__ has quit IRC15:28
suloso the plan is for us to get the base set working15:28
sulothen demo to them and go from there15:29
jimbakersulo, yeah. it seems to me this will start impacting OSA, with respect to templating15:29
sulooh yeah .. and 4. support handling secrets ;)15:29
*** yamamoto has joined #openstack-meeting-415:30
jimbakerseems reasonable. i think handling secrets should not be so bad, we can adopt a vault-style model15:30
jimbaker(ansible vault)15:31
jimbakerbut definitely details there to get right15:31
suloyeah15:31
*** azbiswas has joined #openstack-meeting-415:31
jimbakeron my side, i spent some time on the variable refactoring. it should work, and it almost does, but i'm missing something on the sqlalchemy side in terms of how relationships get converted to the appropriate collection type15:32
jimbakeranyway, i'm sure it will be easy enough to fix15:33
*** shaohe_feng has quit IRC15:33
sulojimbaker: does that include variables blame support ?15:33
jimbakersulo, yeah, that would just work once i have it refactored15:33
sulocool15:33
jimbakeri'm just trying to preserve k,v access through a dict mapping, as opposed to seeing a list of variables15:34
*** shaohe_feng has joined #openstack-meeting-415:34
*** armax has joined #openstack-meeting-415:34
jimbakeranyway, i know much more about sqlalchemy at this point :)15:34
jimbakerlet's move on15:35
jimbaker#topic audit workflows15:36
*** openstack changes topic to "audit workflows (Meeting topic: craton)"15:36
*** azbiswas has quit IRC15:36
jimbakersulo, so the OSA work is a good complement here, since it enables the actual FLT005 stuff with OSA security role15:37
sulojimbaker: yeah, so i did test this a little bit15:37
jimbakerat this point, we need to take gus' work on taskflow integration15:37
jimbakerand really start building it out15:37
sulowe need to discuss the architecture a bit more detail in one of the dev meeting15:37
jimbakersulo, sounds good to me15:38
jimbakeri know gus looked into TF's jobboard, and that seems the right approach for scale; but i'm more concerned about task generation/scheduling15:39
jimbakersince we only have this as TODOs so far15:39
jimbakershould we just have that as the focus of this thurs dev meeting, with research this week?15:40
sulo+115:40
jimbakercmspence, sigmavirus, turvey - any thoughts?15:41
*** brad_pokorny has joined #openstack-meeting-415:41
*** brad_pokorny has quit IRC15:41
jimbaker#topic integrations15:41
*** openstack changes topic to "integrations (Meeting topic: craton)"15:41
*** brad_pokorny has joined #openstack-meeting-415:42
cmspencejimbaker: +115:42
jimbakeri talked with mike tamayo from OSIC/intel15:42
turveyWorks for me15:42
*** bobh has joined #openstack-meeting-415:42
jimbaker(sounds good!)15:42
jimbakerand he will be committing resources to help on horizon integration, which will be optional for operators15:42
jimbakerbut certainly useful for all sorts of use cases, even if many operators will often want to use the CLI or python client15:43
*** shaohe_feng has quit IRC15:43
sigmavirussorry jimbaker, got stuck in another meeting15:43
*** shaohe_feng has joined #openstack-meeting-415:43
jimbakersigmavirus, no worries15:43
*** piet has quit IRC15:43
jimbakerso we are looking at wireframes by july 2315:43
sulojimbaker: details on this integration work ? is this going upstream etc ?15:44
jimbakerre oneops integration, after a good meeting with walmart labs on june 28, we are waiting to follow up. sarob will help organize15:45
sulowhat are we expecting on horizon end?15:45
jimbakersulo, it should be a horizon plugin that can consume craton's REST APIs15:45
sulook15:46
sigmavirusI really think that should be put off until we have a stable API15:46
suloyeah agree15:46
jimbakersigmavirus, i understand your concern, however we are getting stakeholder feedback to do this earlier than later15:46
turveyWe'll make sure that those implementing understand the API is still in flux15:47
jimbakerturvey, +115:47
sulojimbaker: so even if we use the current api what is horizon going to show ? basically a UI for inventory to start with ?15:47
jimbakersulo, yes, and then augment with say being able to use the workflow APIs, as we develop those15:48
jimbakerso being able to inspect the environment, config vars, etc; then as we add workflows, kick those off15:48
suloright, yeah in general sound good, given it takes UI work away from this team ;)15:49
jimbakerinteresting points here is that we will need to consider how to show say audit results - what convention/config makes it possible to flag things15:49
jimbakersulo, correct, we want this work done15:49
jimbakerand it is a separate team of resources :)15:49
jimbakerhaving good APIs is our responsibility regardless15:50
turveyIt also gives is an early consumer of the API, which could be useful.15:50
jimbakergoing back to FLT005 - this will help in completeness on that story. also on demoable things for barcelona :)15:50
jimbakerturvey, +115:51
jimbakertime to move on!15:51
jimbaker#topic admin15:51
*** openstack changes topic to "admin (Meeting topic: craton)"15:51
jimbakerwe need to reschedule the dev meeting on thurs15:51
jimbakersulo cannot make it at all, and i believe it would be best to accommodate gus by my doing a 1:1 with him15:52
jimbakercmspence, sigmavirus, sulo, turvey - i'm proposing something around 1600 UTC, no earlier than 1530 UTC on thursdays15:53
sulosounds good to me15:53
*** Gbothello has joined #openstack-meeting-415:53
*** shaohe_feng has quit IRC15:53
jimbakeri will send out a doodle poll on the list to get specific times. but would this basically work for all of you?15:53
*** dasanind_ has joined #openstack-meeting-415:53
*** sukhdev has joined #openstack-meeting-415:53
turveySure15:54
cmspenceya, that should be fine15:54
*** shaohe_feng has joined #openstack-meeting-415:54
*** hshiina has joined #openstack-meeting-415:54
jimbakersigmavirus, ?15:54
jimbakerthe other item here is that sarob has basically completed the project patch15:55
jimbakerwe need to do a final review15:55
sulooh its not complete .. i just https://review.openstack.org/#/c/332470/415:55
sigmavirusjimbaker: I have a weekly meeting Thursday mornings, I probably won't make that either15:55
*** dasanind has quit IRC15:55
suloi was going to ping him on that15:55
*** Sukhdev_ has joined #openstack-meeting-415:55
*** dasanind_ has quit IRC15:55
jimbakersigmavirus, then we need to figure a time to make it work for you15:55
sigmavirusjimbaker: meh15:55
sulojimbaker: sigmavirus: different day ?15:55
sigmavirusI'm not on the project full time for more months15:55
sigmaviruswe can shift if necessary then15:56
jimbakersigmavirus, yeah, i just want to make sure that you, sulo, cmspence, turvey and me can make it15:56
sulojimbaker: sigmavirus: as long as its not very late UTC time i am fine with any date btw.15:56
*** galstrom_zzz is now known as galstrom15:57
jimbakersulo, thanks for being flexible!15:57
jimbakerwe just didn't want to push it too much15:57
sigmavirusLet's go with thursday for now. I'm doing mental utc math15:57
suloheh15:57
*** dharinic_ has quit IRC15:57
jimbakersigmavirus, so i am making it work with jason c's meeting15:57
*** Jeffrey4l has quit IRC15:58
jimbakerwe should be in our staff meeting :)15:58
*** mjturek1 has joined #openstack-meeting-415:58
sigmavirusjimbaker: I'm not in your staff meeting though =P15:58
jimbakerok, then it's just sulo and i have to be there15:58
jimbakerbut regardless, let's find a time over on #craton, then put it out there on the mailing list to finalize15:58
sulowe are running out of time here .. move this to #craton ?15:58
jimbakeryes, time to end meeting15:59
jimbaker#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Mon Jul 11 15:59:07 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-07-11-14.59.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-07-11-14.59.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-07-11-14.59.log.html15:59
*** cmspence has left #openstack-meeting-415:59
Sukhdev_Folks, time for Ironic-neutron meeting16:00
mjturek1hey o/16:01
Sukhdev_#startmeeting ironic_neutron16:01
openstackMeeting started Mon Jul 11 16:01:19 2016 UTC and is due to finish in 60 minutes.  The chair is Sukhdev_. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
TheJuliao/16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
davidlenwello/16:01
*** openstack changes topic to " (Meeting topic: ironic_neutron)"16:01
openstackThe meeting name has been set to 'ironic_neutron'16:01
hshiinao/16:01
Sukhdev_We'll for a minute to give others time to join in16:01
*** Gbothello has quit IRC16:02
Sukhdev_jroll sambetts devananda: are you here?16:02
Sukhdev_#topic: Agenda16:03
*** openstack changes topic to ": Agenda (Meeting topic: ironic_neutron)"16:03
Sukhdev_#link: https://wiki.openstack.org/wiki/Meetings/Ironic-neutron#Meeting_July_11.2C_201616:03
Sukhdev_I kept the previous agenda - as we did not have a meeting last week16:03
*** shaohe_feng has quit IRC16:03
sambettso/16:04
TheJuliajroll is not available today16:04
*** shaohe_feng has joined #openstack-meeting-416:04
Sukhdev_If anybody wants to add to the agenda, feel free to add16:04
Sukhdev_TheJulia : thanks for update16:04
Sukhdev_lets keep going in that case16:05
Sukhdev_#topic: Announcements16:05
devanandao/16:05
*** openstack changes topic to ": Announcements (Meeting topic: ironic_neutron)"16:05
*** bryan_att has joined #openstack-meeting-416:05
Sukhdev_We skipped last week's meeting and I missed the previous week's16:05
sambettsI think the biggest Annoucement of all is we missed the nova FF with a major patch to get the networking stuff done16:06
TheJulia297895?16:06
Sukhdev_sambetts : I noticed that16:06
*** stanchan has quit IRC16:06
sambettsTheJulia: yup16:06
Sukhdev_sambetts : what happened? I thought it was going to go in -16:06
*** bobh has quit IRC16:07
TheJuliaIt seems like ironic can navigate around the issue though, since essentially there is already a bug in the behavior that wouldn't change nova setup/configuration in a production deployment.  I think ironic just needs to see if the port already exists, delete it in neutron, and then re-create it as part of the deployment process.16:07
mjturek1I thought it was said during mid-cycle that we weren't aiming for nova feature freeze anymore? sorry if I misunderstood16:08
sambettsmjturek1: we thought we didn't have any patches that would affect the current work, but it seems like we missed one :(16:08
mjturek1dang :(16:09
TheJuliavisibility was not raised until last week :(16:09
*** turvey has left #openstack-meeting-416:09
*** azbiswas has joined #openstack-meeting-416:09
sambettsMy concern is that I'm not sure if the code already merged in nova might cause us problems too, because the code already merged is actually incorrect now too16:10
Sukhdev_and, I take it nova does not allow exceptions16:10
*** azbiswas_ has joined #openstack-meeting-416:10
sambettsSukhdev_: they wouldn't give us one because we didn't have the Ironic stuff merged16:10
sambettsas I understand it16:10
TheJuliasambetts: good point, but I thought it was minimal, I'm likely wrong though16:11
devanandasambetts: can you elaborate on "the code already merged is actually incorrect" ?16:11
sambettsdevananda: we already have code in Nova that expects the network_provider field, and none instead of network_interface and flat16:12
sambettsdevananda: https://review.openstack.org/#/c/297895/3/nova/virt/ironic/driver.py16:12
sambettsits a update patch16:12
sambetts:/16:12
*** uck has joined #openstack-meeting-416:12
TheJuliais it just network_binding_host_id ?16:13
*** david-lyle has joined #openstack-meeting-416:13
Sukhdev_sambetts: I do not believe that is incorrect code, is it?16:13
*** shaohe_feng has quit IRC16:14
*** azbiswas has quit IRC16:14
sambettsit might be safe, because of the getattr, but its looking for a field name that doesn't exist anymore16:14
*** shaohe_feng has joined #openstack-meeting-416:14
*** dharinic_ has joined #openstack-meeting-416:15
Sukhdev_I do not see that patch merged though - did it merge as a part of different patch?16:15
*** jcook has quit IRC16:16
TheJuliahttps://github.com/openstack/nova/commit/0e6e28aed74e8029e394bb16298436a239c7192e is where initial support went in to nova16:17
TheJuliaJust that link to provide the diff view16:17
*** jcook has joined #openstack-meeting-416:18
*** david-lyle has quit IRC16:19
Sukhdev_TheJulia : yes - that is the correct one -16:19
*** oshidoshi has quit IRC16:19
*** brad_pokorny has quit IRC16:20
Sukhdev_the one sambetts pointed out modifies this merged code - and, I have tested it - but, I do not believe it is merged16:21
devanandais the problem that, in ironic, it was decided to use a different field name inthe API, since that patch merged in Nova? (or have I misunderstood the issue?)16:21
devanandas/network_provider/network_interface/ ?16:21
TheJuliadevananda: pretty much, plus ironic is coded to expect no network to possibly be attached, correct or not, upon the beginning of deployment16:22
sambettsdevananda: right, a different field name in the API and a different stevedore name for the network interface that represents the existing network support16:22
sambettss/none/flat16:22
lazy_princeo/16:23
*** zenoway has quit IRC16:23
Sukhdev_sambetts : so, I tested everything with this patch - did not test without patch - so, perhaps, it may be problematic16:23
*** shaohe_feng has quit IRC16:24
*** iyamahat has joined #openstack-meeting-416:24
Sukhdev_so, I wonder if we merge ironic patches and go back to nova folks for exception on the basis that the merged code may be broken, we may be able to get one -16:24
*** spotz is now known as spotz_zzz16:24
Sukhdev_jroll is guy I rely on for nova communications - wish he was here to answer16:24
*** shaohe_feng has joined #openstack-meeting-416:25
sambettsTBH as the orignal patch is merged, and its all our code is designed to be backwards compatible (as far as I can see) with the getattr etc I don't see why we shouldn't be allowed to merge it with the Ironic side changes, (although that puts us in the same situation as before in regards to thinks might change)16:25
*** rainya has joined #openstack-meeting-416:25
lazy_princesambetts: which patch has merged..?16:26
Sukhdev_lazy_prince: the link posted by TheJulia16:26
sambettslazy_prince: https://github.com/openstack/nova/commit/0e6e28aed74e8029e394bb16298436a239c7192e16:27
lazy_princeaha..16:27
Sukhdev_sambetts : so, I think we may have a shot, if we can get ironic stuff merged -16:27
sambettsjroll is going the nova midcycle on the 19th of July, so I think we might need to work hard to get the ironic side merged to give him the best shot to convice them to give us a FFE16:28
Sukhdev_that leads me to next point - how come we did not merge the ironic patches ?16:28
*** alexchadin has joined #openstack-meeting-416:28
Sukhdev_sambetts : right that gives us a week to get ironic stuff merged -16:29
*** brad_pokorny has joined #openstack-meeting-416:29
lazy_princeyeah.. i have the same question.. whats taking so long for the patches.. its almost three cycles..16:29
*** jcook has quit IRC16:29
Sukhdev_what is barrier to get ironic patches merged - they have gone through so many revs16:29
sambettsSo there was a couple of things that delays the patches again, the first was that we've changed the Ironic port model a little to support this logic better, Ironic ports now have an internal_info field to hold the data about ports created by Ironic, that merged pretty fast16:30
lazy_princeis there anything else..?16:31
sambettsthere is currently some contention on the patch adding network_interfaces because of how it plays with the driver reform Ironic is currently working on16:31
TheJuliaThat is an agenda itemf or the next ironic meeting16:31
sambettsFor reference: https://review.openstack.org/#/c/285852/63/ironic/common/driver_factory.py16:31
sambetts#link https://review.openstack.org/#/c/285852/63/ironic/common/driver_factory.py16:31
*** dasanind has joined #openstack-meeting-416:31
*** britthouser has joined #openstack-meeting-416:31
*** baoli has joined #openstack-meeting-416:33
Sukhdev_so, folks how do converge on these? - we have really gone through these so many times - we should not keep holding and keep making changes -16:33
sambettsother delays include the problems highlighted when trying to run this new code in Ironic standalone mode, which I hope are resolved now, and that Ironic wanted to have grenade upgrade testing before merging any of this code16:33
*** alexchadin has quit IRC16:33
sambettswhich is done too16:34
*** shaohe_feng has quit IRC16:34
Sukhdev_TheJulia: are you planning on discussing the plan to merge these patches in ironic meeting?16:34
TheJuliaAFAIK we are16:35
*** dasanind has quit IRC16:35
Sukhdev_sambetts : as you had suggested once, perhaps we can set up a chat session for people to dial in and go over these to get merged?16:36
*** unicell has quit IRC16:37
*** dasanind has joined #openstack-meeting-416:37
*** shaohe_feng has joined #openstack-meeting-416:37
*** yamahata has joined #openstack-meeting-416:37
*** baoli has quit IRC16:37
sambettsYeah I think it might be worth trying to organise a time and place to sync and push these in16:38
sambettsby place I mean the Jitsi audio call thing16:38
TheJuliaagreed16:38
Sukhdev_right - if that makes things move...16:38
*** lelouch_ has quit IRC16:38
Sukhdev_we have to do it this week16:39
TheJuliaIt should, we just need to come to a consensus, and land what we have, and iterrate from there16:39
Sukhdev_TheJulia : +116:40
sambetts+1 the only think out of all of it thats hard to interate on is the API16:40
sambettsthing*16:40
*** woodard has quit IRC16:41
Sukhdev_sambetts : what is the contention over api?16:41
TheJuliasambetts: Agreed, in the next meeting, lets discuss identifying a time to get on a call in the next day or two to work through the items16:41
sambettsright now there is contention over whether network_interfaces should be known as network_interfaces or not which affects how its represented in the API16:42
*** dasanind has quit IRC16:43
sambettsbecause we have a new concept of *_interfaces coming, which is why we wanted to call them network_interfaces in the first place, but there are some new interactions between *_interfaces and the concept of a hardware_type we're adding which don't fit very well for the network_interfaces16:43
*** shaohe_feng has quit IRC16:44
*** dasanind has joined #openstack-meeting-416:45
Sukhdev_network will be always needed - so, the contention is to call it network_interface or something else?16:45
*** shaohe_feng has joined #openstack-meeting-416:45
sambettsthe main one being that hardware_type have vendor specified defaults for each of the *_interfaces (power/managemnt) etc but network_interfaces are very environment specific and only in some cases (e.g. my out of tree driver) hardware specific16:45
*** jcook has joined #openstack-meeting-416:46
devanandasambetts: huh. also, network interface doesn't depend on the server's OOB management device in the same way that, say, power, RAID, etc do16:47
sambettsdevananda: my out of tree one will but I'm special16:47
devanandanetwork_interface could vary by server, but is logically decoupled from the physical server (expcet special cases where it isn't)16:47
sambettsexactly16:47
Sukhdev_exceptions do not set the rules - I believe we will always need network16:48
*** rbak has quit IRC16:48
sambettsSukhdev_: its not that we won't always need network, its that vendors can not set sane defaults on a hardware_type because its dependant on the environment its deployed in16:48
Sukhdev_I see these two as orthogonal items - (perhaps I am missing something)16:49
sambettsand for all the other *_interfaces vendors set a sane/recomended default interfaces which is using unless overridden by the operator using Ironic16:49
*** sarob has joined #openstack-meeting-416:50
sambetts(sorry that was terrible english)...16:50
*** thiagop has joined #openstack-meeting-416:50
*** thiagop has left #openstack-meeting-416:50
TheJuliaThat won't be quite true with storage/boot from volume so there are some in which it makes sense, and some it does not, and it seems like we've already discussed that being the case16:50
*** sarob has quit IRC16:50
TheJulia(sorry for being slow responding, was on a call until a moment ago)16:50
devanandaTheJulia: good point. this affects more than just network_interface16:51
sambetts:'(16:51
* Sukhdev_ time check 8 min16:52
* devananda notices that the meeting topic is still "announcements"16:52
*** gnuoy has joined #openstack-meeting-416:53
Sukhdev_devananda : oppss...my fault - too late now :-)16:53
Sukhdev_TheJulia : is the ironic meeting right after this meeting?16:55
*** shaohe_feng has quit IRC16:55
*** sarob has joined #openstack-meeting-416:55
sambettsYup, in openstack-meeting316:55
*** sarob has quit IRC16:55
sambettsHopefully we can unsick this in the main Ironic meeting16:55
*** sarob has joined #openstack-meeting-416:55
*** shaohe_feng has joined #openstack-meeting-416:55
Sukhdev_Yup I will stick around16:55
Sukhdev_#topic Open Discussion16:56
*** openstack changes topic to "Open Discussion (Meeting topic: ironic_neutron)"16:56
*** sarob has quit IRC16:56
Sukhdev_devananda : ha ha I changed the topic :-)16:56
sambettsI believe this problem (no easy sane default) is the origial reason we it so network_interfaces had to be set on node create, and there was no default16:56
sambettswe made it so*16:56
*** sarob has joined #openstack-meeting-416:56
*** rbak has joined #openstack-meeting-416:58
*** rainya has quit IRC16:59
Sukhdev_didn't we used to have flat network as default?16:59
lazy_princeor the default from config file...?16:59
* devananda goes over to the other room to get ready for hte next meeting17:00
*** thedac has joined #openstack-meeting-417:00
sambettsI believe that we ended up with flat if you used an old client if I remember correctly17:00
Sukhdev_time is up for this meeting - lets move over to other room17:00
sambetts++17:00
*** tinwood has joined #openstack-meeting-417:00
Sukhdev_thanks for attending this meeting17:00
Sukhdev_bye17:00
sambettso/17:00
Sukhdev_#endmeeting17:00
*** Swami has joined #openstack-meeting-417:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:01
openstackMeeting ended Mon Jul 11 17:00:59 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-07-11-16.01.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-07-11-16.01.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-07-11-16.01.log.html17:01
*** daneyon has joined #openstack-meeting-417:01
gnuoy#startmeeting charms17:01
openstackMeeting started Mon Jul 11 17:01:51 2016 UTC and is due to finish in 60 minutes.  The chair is gnuoy. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: charms)"17:01
openstackThe meeting name has been set to 'charms'17:01
gnuoy\o17:02
beisnero/17:02
thedaco/17:02
tinwoodo/17:02
gnuoy#topic Review ACTION points from previous meeting17:02
*** openstack changes topic to "Review ACTION points from previous meeting (Meeting topic: charms)"17:02
gnuoy#subtopic gnuoy move meeting to openstack-meeting channel17:02
beisnerWoot17:02
gnuoyWell, I did \o/17:02
tinwoodyay17:02
thedac\o/17:02
gnuoyhurray for me.17:02
beisneryes :-)17:02
gnuoy#topic State of Development for next Charm Release17:02
*** openstack changes topic to "State of Development for next Charm Release (Meeting topic: charms)"17:02
gnuoySo...*Thursday*17:03
gnuoyWe need to be finishing features off or punting them for three weeks17:03
gnuoyDesignate should be up for review tomorrow PM17:03
gnuoyI think Barbican should be done soonish too17:04
*** rainya has joined #openstack-meeting-417:04
gnuoyAnyone got any big changes up their sleeves that they want to come clean about?17:04
tinwoodBarbican will hopefully be ready by Wednesday inc. some func tests.17:04
gnuoykk17:04
gnuoy#topic High Priority Bugs17:04
*** openstack changes topic to "High Priority Bugs (Meeting topic: charms)"17:04
gnuoyRabbit and Percona are the two big ones that have come up recently17:05
*** xenogear has quit IRC17:05
*** shaohe_feng has quit IRC17:05
gnuoyI believe thedac has crushed the percona one17:05
gnuoyI will grab that review17:05
beisnerwe do need to refactor the percona-cluster amulet tests to cover more than just trusty-icehouse17:05
tinwoodnice thedac :)17:05
gnuoyand jamespage has fixed the rabbit one17:05
thedac#link https://review.openstack.org/#/c/339823/17:05
beisneryes big thx thedac17:06
*** daneyon has quit IRC17:06
*** shaohe_feng has joined #openstack-meeting-417:06
gnuoybeisner, shall we try and do that real-soon-now or in a few weeks?17:06
*** jamespage has joined #openstack-meeting-417:06
*** coreycb has joined #openstack-meeting-417:06
jamespageo/17:06
coreycbo/17:06
thedacI verified jamespage's rabbit fix. It is good.17:06
beisnernot sure if we can squeeze that in for 16.07 (pxc) ... i know i don't have bandwidth atm to take that on.  but it does need to happen, sooner the better17:06
gnuoybeisner, ack, lets push it out then17:07
jamespagebeisner, test for xenial?17:07
beisnerjamespage, ack17:07
jamespageI might be able todo that - assign me the bug17:07
*** cholcombe has joined #openstack-meeting-417:07
gnuoyjamespage, general refactor17:07
gnuoybut xenial is defo needed17:07
beisnerref:  https://bugs.launchpad.net/charms/+source/percona-cluster/+bug/154657717:08
openstackLaunchpad bug 1546577 in percona-cluster (Juju Charms Collection) "pxc charm needs amulet test coverage refactor" [High,Confirmed]17:08
gnuoy#action jamespage add xenial tests to percona-cluster17:08
*** icey has joined #openstack-meeting-417:08
beisnerer um17:08
beisner#link https://bugs.launchpad.net/charms/+source/percona-cluster/+bug/154657717:08
jamespagegot it17:08
gnuoyta17:08
gnuoymoving on ...17:08
gnuoy#topic Tox target for layers17:09
*** openstack changes topic to "Tox target for layers (Meeting topic: charms)"17:09
gnuoyjamespage, beisner Ithink you said you were going to defer a discussion to here on that ?17:09
*** cargonza has joined #openstack-meeting-417:09
gnuoyor am I imagining that?17:09
jamespage oh yes - that's right17:09
jamespageso this came up because the layer jobs are currently configured to run a build target as part of check/gate17:10
beisnerok, so do we want to require all layer repos to (a) have a build tox target; and (b) expect success in building ?17:10
gnuoyWhat does the build do ?17:10
*** dasanind has quit IRC17:10
jamespagegnuoy, pulls the layer + its dependencies together17:10
gnuoyassemble the lower layers?17:10
gnuoyack17:10
tinwoodwhy would a layer have a build target?17:10
jamespageso if someone stuff in a bad interface or layer, this would gate that17:10
jamespageI think ideally we've have this are part of a layer lint tool17:11
gnuoyI feel a bit shruggy about it but I don't object17:11
jamespagelayer proof or siuchlike17:11
beisnertinwood, that's the nature of the convo.  i was also surprised by it.  but jamespage pointed out that it is potentially a valuable test (to build it).17:11
jamespagebut right now, the only way todo this is to 'build' the layer (and then throw it away)17:11
beisneraiui, the "src charm" is the only thing we'll ever build, deploy-test and publish, right?17:11
jamespageack17:11
gnuoyyep, I think so17:12
jamespageso - build target in layers (to be superceeded by lint later)17:12
gnuoyok, unless anyone objects lets go with a build target to check dependancies can be assembled17:12
jamespageis that agreed?17:12
jamespage+117:12
gnuoy+117:12
thedac+117:12
*** ddieterly is now known as ddieterly[away]17:12
beisneri'm good with that - please do document it somehow, perhaps a tox.ini #comment17:13
gnuoykk. I'll take silence from others as 017:13
beisnermy only holdback here is that a non-openstacker gets ahold of a layer repo, sees a build target, builds it, tries to deploy it, fails, etc.17:13
gnuoybeisner, agreed, lets spew out a comment/warning17:13
jamespagesure17:14
beisneror ... perhaps more confusingly ... an openstacker tries to create a layer which can be both a built charm AND a layer to consume.17:14
beisneri'm just looking for good ways to make it crystal clear.17:14
jamespagewe're trying to avoid that situation :-)17:14
beisneri sniff the desire to do just that with the ceph-*s.17:15
*** unicell has joined #openstack-meeting-417:15
jamespagehmm17:15
* jamespage ponders this a bit longer17:15
*** shaohe_feng has quit IRC17:15
tinwoodI thought that had been quashed and a thin src charm was the idea for the ceph-*17:15
beisneri think that is the right answer tinwood - while they layer "could" be a layer or a charm, it "shouldn't"17:16
*** brad_pokorny has quit IRC17:16
tinwoodmaybe 'quashed' isn't the right word for it.17:16
*** shaohe_feng has joined #openstack-meeting-417:16
thedacpolitely suggested?17:16
tinwoodindeed.17:16
*** brad_pokorny has joined #openstack-meeting-417:16
beisnerneed to make sure everyone's in line with:   for every layered charm we produce, there shall be a src charm.   and, solved.  :)17:16
iceymy understanding is the same as tinwood, src charm that has a built layer on top of it17:16
iceythe top layer for (for example) ceph-mon would be a layer that just includes the ceph-mon layer17:17
gnuoykk17:17
tinwoodcan it be 'enforced' though?  Only in the publish step, i would say?17:17
beisnerwhere charm-ceph-mon is a src charm and charm-layer-ceph-mon is just a layer.  beautiful.17:17
thedacWe might want to disucss naming conventions. Ceph-mon layer vrs src charm should'b both be named ceph-mon17:18
jamespagetinwood, basically if you don't comply with the 'interface' which is to have src, your charm/layer won't work with the CI17:18
iceybeisner: I think it'd just be charm-ceph-mon uses layer-ceph-mon17:18
icey?17:18
jamespagewe have to prefix due to a single openstack namespace17:18
beisnercharm-layer-ceph-mon should be the namespace aiui17:18
tinwoodjamespage, that is very sensible.17:18
jamespageok - so build is OK17:19
gnuoyok, I think we are in agreement17:19
jamespagethis is not unchangeable btw17:19
tinwoodyes, I've come around to the idea :)17:19
gnuoyok, lets move on17:19
jamespageif we all hate it in two weeks time that ok17:19
gnuoy#topic 2 x +217:19
*** openstack changes topic to "2 x +2 (Meeting topic: charms)"17:19
jamespageyeah ok17:19
gnuoyanother of jamespages17:19
jamespageso this came up in the governance review for project status17:19
gnuoy#link https://review.openstack.org/#/c/224797/17:19
jamespagemost openstack projects operate 2 x  +2's prior to workflow +117:19
jamespagewe're not operating that currently - just a single +2 is required for workflow +117:20
jamespageI *think* that we should do the 2x +2, but it will have a small overhead on throughput of changes17:20
tinwoodIs it a blocker then?17:20
*** degorenko is now known as _degorenko|afk17:21
jamespageno its not a blocker as far as we can tell17:21
thedacjamespage: Does +1 and then a +2 make more sense? Or does it have to be 2 x +2?17:21
tinwoodah, okay, so it's up to us.17:21
beisneri'm actually good with a single +2 given the size of our group17:21
*** brad_pokorny has quit IRC17:21
beisneradditional +1s or +2s are always a good thing though17:22
gnuoyI'm leaning towards beisners view until the core reviewer base is bigger17:22
jamespageagreed - and maybe we do this on a per change basis - if its something contentious or a config flags or relation data change we do 2x17:22
beisneryah i think we've effectively done that, asking for cross-reviews for hairy changes.17:23
gnuoykk, but its something we should keep an eye on17:23
thedacthat makes sense and we have basically been doing that. Waiting for a second opinion on complex changes17:23
beisnerindeed.  we could sure do 2 x +2s if it's a thing or desired.17:23
jamespageI think that is fair as well - if/when we get a more diverse reviewer base, then this will be more powerful, ensuring that no single person could drive a change objective not aligned to the project17:23
cholcombei agree, single +2 is enough for us.  The reviewer base is too small17:23
gnuoyyep, that makes sense17:23
jamespageok17:23
gnuoyok, onwards and upwards17:23
gnuoy#topic Openstack talk submissions for ODS17:23
*** openstack changes topic to "Openstack talk submissions for ODS (Meeting topic: charms)"17:23
gnuoyWhen was that deadline again?17:24
jamespagethis week17:24
jamespagethursday I think17:24
gnuoyack, ta17:24
beisner#link  https://www.openstack.org/summit/barcelona-2016/call-for-presentations/17:24
* beisner quotes: JULY 13, 2016 AT 11:59PM PDT (JULY 14 6:59 UTC) IS THE DEADLINE TO SUBMIT A TALK.17:24
gnuoyThanks beisner17:25
jamespagethat's wednesday to be clear17:25
gnuoyyep17:25
*** shaohe_feng has quit IRC17:25
gnuoyGet your thinking caps on17:26
gnuoy#topic Open Events17:26
*** openstack changes topic to "Open Events (Meeting topic: charms)"17:26
gnuoyAny other Openstack and/or charm events coming up?17:26
*** javeriak has joined #openstack-meeting-417:26
*** uck has quit IRC17:26
gnuoyOk, moving on17:27
gnuoy#topic Open Discussion17:27
*** openstack changes topic to "Open Discussion (Meeting topic: charms)"17:27
*** shaohe_feng has joined #openstack-meeting-417:28
gnuoyGoing Once17:28
*** brad_pokorny has joined #openstack-meeting-417:28
*** iyamahat has quit IRC17:28
gnuoyGoing Twice17:28
beisnerSold!   thanks, gnuoy17:29
gnuoy#topic Announce next meeting date, time and chair17:29
*** openstack changes topic to "Announce next meeting date, time and chair (Meeting topic: charms)"17:29
gnuoyTwo weeks time, on Monday at 17:00 UTC17:29
gnuoySame place17:29
gnuoychair thedac I believe17:29
thedacI am up17:29
gnuoy#endmeeting17:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:29
openstackMeeting ended Mon Jul 11 17:29:42 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-07-11-17.01.html17:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-07-11-17.01.txt17:29
openstackLog:            http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-07-11-17.01.log.html17:29
tinwoodthanks gnuoy17:29
thedacthanks gnuoy17:29
jamespagethanks gnuoy17:29
gnuoyyw17:29
*** yamahata has quit IRC17:30
*** coreycb has quit IRC17:31
*** brad_pok_ has joined #openstack-meeting-417:31
*** coreycb has joined #openstack-meeting-417:31
*** fawadkhaliq has joined #openstack-meeting-417:32
*** unicell1 has joined #openstack-meeting-417:33
*** unicell has quit IRC17:33
*** brad_pokorny has quit IRC17:35
*** brad_pok_ has quit IRC17:36
*** sshnaidm is now known as sshnaidm|afk17:36
*** shaohe_feng has quit IRC17:36
*** shaohe_feng has joined #openstack-meeting-417:36
*** javeriak_ has joined #openstack-meeting-417:38
*** amotoki has quit IRC17:38
*** javeriak has quit IRC17:38
*** pcaruana has joined #openstack-meeting-417:39
*** brad_pokorny has joined #openstack-meeting-417:40
*** dharinic_ has quit IRC17:41
*** shaohe_feng has quit IRC17:46
*** shaohe_feng has joined #openstack-meeting-417:46
*** muneeb has joined #openstack-meeting-417:47
*** iyamahat has joined #openstack-meeting-417:49
*** pvaneck has joined #openstack-meeting-417:51
*** yamahata has joined #openstack-meeting-417:51
*** s3wong has joined #openstack-meeting-417:52
*** spotz_zzz is now known as spotz17:54
*** fawadkhaliq has quit IRC17:55
*** kzaitsev_mb has quit IRC17:55
*** shaohe_feng has quit IRC17:56
*** shaohe_feng has joined #openstack-meeting-417:56
*** Sukhdev_ has quit IRC17:56
*** lelouch_ has joined #openstack-meeting-418:01
*** muneeb has quit IRC18:01
*** muneeb has joined #openstack-meeting-418:01
*** brad_pokorny has quit IRC18:03
*** yamamoto has quit IRC18:03
*** yamamoto has joined #openstack-meeting-418:04
*** shaohe_feng has quit IRC18:06
*** yamamoto has quit IRC18:09
*** shaohe_feng has joined #openstack-meeting-418:09
*** uck has joined #openstack-meeting-418:10
*** dshakhray has quit IRC18:10
*** david-lyle has joined #openstack-meeting-418:12
*** ddieterly[away] has quit IRC18:13
*** shaohe_feng has quit IRC18:17
*** david-lyle has quit IRC18:17
*** shaohe_feng has joined #openstack-meeting-418:17
*** jcook has quit IRC18:18
*** ddieterly has joined #openstack-meeting-418:23
*** hshiina has quit IRC18:24
*** muneeb has quit IRC18:26
*** muneeb has joined #openstack-meeting-418:27
*** shaohe_feng has quit IRC18:27
*** muneeb has quit IRC18:27
*** automagically has joined #openstack-meeting-418:27
*** shaohe_feng has joined #openstack-meeting-418:29
*** dasanind has joined #openstack-meeting-418:33
*** shaohe_feng has quit IRC18:37
*** shaohe_feng has joined #openstack-meeting-418:37
*** mfedosin has quit IRC18:38
*** dasanind has quit IRC18:39
*** rainya has quit IRC18:40
*** dasanind has joined #openstack-meeting-418:41
*** woodard has joined #openstack-meeting-418:46
*** woodard has quit IRC18:46
*** vishwanathj has quit IRC18:47
*** woodard has joined #openstack-meeting-418:47
*** shaohe_feng has quit IRC18:47
*** rainya has joined #openstack-meeting-418:48
*** shaohe_feng has joined #openstack-meeting-418:48
*** lelouch_ has quit IRC18:49
*** brad_pokorny has joined #openstack-meeting-418:52
*** Rockyg has joined #openstack-meeting-418:52
*** shaohe_feng has quit IRC18:58
*** shaohe_feng has joined #openstack-meeting-418:58
*** rbak_ has joined #openstack-meeting-418:58
*** rbak has quit IRC18:59
*** alexchadin has joined #openstack-meeting-419:01
*** yamamoto has joined #openstack-meeting-419:02
*** alexchadin has quit IRC19:02
*** sarob has quit IRC19:07
*** shaohe_feng has quit IRC19:08
*** sarob has joined #openstack-meeting-419:08
*** shaohe_feng has joined #openstack-meeting-419:09
*** dasanind has quit IRC19:09
*** _sarob has joined #openstack-meeting-419:10
*** fawadkhaliq has joined #openstack-meeting-419:10
*** tonytan4ever has quit IRC19:10
*** rbak_ has quit IRC19:11
*** rbak has joined #openstack-meeting-419:12
*** mfisch has joined #openstack-meeting-419:13
*** mfisch has quit IRC19:13
*** mfisch has joined #openstack-meeting-419:13
*** dshakhray has joined #openstack-meeting-419:13
*** sarob has quit IRC19:14
*** ddieterly is now known as ddieterly[away]19:15
*** jcook has joined #openstack-meeting-419:15
*** dharinic_ has joined #openstack-meeting-419:17
*** shaohe_feng has quit IRC19:18
*** shaohe_feng has joined #openstack-meeting-419:19
*** brad_pokorny is now known as bpokorny19:19
*** dshakhray has quit IRC19:24
*** Sukhdev_ has joined #openstack-meeting-419:26
*** sdake has joined #openstack-meeting-419:26
*** sdake has quit IRC19:26
*** shaohe_feng has quit IRC19:28
*** shaohe_feng has joined #openstack-meeting-419:29
*** sdake has joined #openstack-meeting-419:32
*** sdake has quit IRC19:32
*** sukhdev has quit IRC19:33
*** ddieterly[away] is now known as ddieterly19:37
*** dtardivel has quit IRC19:37
*** shaohe_feng has quit IRC19:39
*** ajmiller has joined #openstack-meeting-419:41
*** shaohe_feng has joined #openstack-meeting-419:41
*** lelouch_ has joined #openstack-meeting-419:42
*** ajmiller_ has quit IRC19:44
*** _ody has joined #openstack-meeting-419:45
*** javeriak_ has quit IRC19:47
*** shaohe_feng has quit IRC19:49
*** shaohe_feng has joined #openstack-meeting-419:50
*** trozet has quit IRC19:54
*** ajmiller has quit IRC19:54
*** ajmiller has joined #openstack-meeting-419:55
*** yamamoto has quit IRC19:55
*** jcook has quit IRC19:55
*** yamamoto has joined #openstack-meeting-419:55
*** yamamoto has quit IRC19:57
*** yamamoto has joined #openstack-meeting-419:57
*** spotz is now known as spotz_zzz19:57
*** woodard has quit IRC19:57
*** vishwanathj has joined #openstack-meeting-419:58
*** shaohe_feng has quit IRC19:59
*** ajmiller has quit IRC19:59
*** yamamoto has quit IRC20:00
*** ajmiller has joined #openstack-meeting-420:00
*** shaohe_feng has joined #openstack-meeting-420:00
*** yamamoto has joined #openstack-meeting-420:00
*** kzaitsev_mb has joined #openstack-meeting-420:02
*** jcook has joined #openstack-meeting-420:03
*** vishwanathj has quit IRC20:04
*** yamamoto has quit IRC20:05
*** vishwanathj has joined #openstack-meeting-420:05
*** banix has quit IRC20:08
*** trozet has joined #openstack-meeting-420:09
*** shaohe_feng has quit IRC20:09
*** shaohe_feng has joined #openstack-meeting-420:10
*** bpokorny has quit IRC20:11
*** dshakhray has joined #openstack-meeting-420:14
*** _sarob has quit IRC20:16
*** pcaruana has quit IRC20:17
*** sambetts is now known as sambetts|afk20:17
*** bpokorny has joined #openstack-meeting-420:18
*** shaohe_feng has quit IRC20:20
*** shaohe_feng has joined #openstack-meeting-420:21
*** spotz_zzz is now known as spotz20:21
*** sarob has joined #openstack-meeting-420:22
*** julim has quit IRC20:27
*** shaohe_feng has quit IRC20:30
*** julim has joined #openstack-meeting-420:32
*** sarob has quit IRC20:32
*** shaohe_feng has joined #openstack-meeting-420:33
*** spotz is now known as spotz_zzz20:34
*** sarob has joined #openstack-meeting-420:36
*** fawadkhaliq has quit IRC20:36
*** julim has quit IRC20:37
*** shaohe_feng has quit IRC20:40
*** shaohe_feng has joined #openstack-meeting-420:41
*** dharinic_ has quit IRC20:41
*** ddieterly is now known as ddieterly[away]20:43
*** ajmiller has quit IRC20:44
*** ajmiller has joined #openstack-meeting-420:44
*** dharinic_ has joined #openstack-meeting-420:48
*** sarob has quit IRC20:49
*** sarob has joined #openstack-meeting-420:50
*** shaohe_feng has quit IRC20:50
*** shaohe_feng has joined #openstack-meeting-420:51
*** sarob has quit IRC20:54
*** spotz_zzz is now known as spotz20:55
*** thorst_ has quit IRC20:56
*** thorst_ has joined #openstack-meeting-420:57
*** boden has joined #openstack-meeting-420:57
*** boden has left #openstack-meeting-420:57
*** galstrom is now known as galstrom_zzz20:59
*** itisha has quit IRC21:00
*** shaohe_feng has quit IRC21:01
*** thorst_ has quit IRC21:02
*** shaohe_feng has joined #openstack-meeting-421:02
*** yamamoto has joined #openstack-meeting-421:02
*** alexchadin has joined #openstack-meeting-421:02
*** sarob has joined #openstack-meeting-421:03
*** thorst_ has joined #openstack-meeting-421:03
*** alexchadin has quit IRC21:05
*** thorst_ has quit IRC21:07
*** sarob has quit IRC21:07
*** shaohe_feng has quit IRC21:11
*** shaohe_feng has joined #openstack-meeting-421:11
*** lelouch_ has quit IRC21:12
*** TaylorHuang has joined #openstack-meeting-421:16
*** dasanind has joined #openstack-meeting-421:16
*** yamamoto has quit IRC21:18
*** TaylorH has quit IRC21:19
*** ddieterly[away] is now known as ddieterly21:19
*** dasanind has quit IRC21:21
*** dasanind has joined #openstack-meeting-421:21
*** shaohe_feng has quit IRC21:21
*** david-lyle has joined #openstack-meeting-421:22
*** cleong has quit IRC21:22
*** shaohe_feng has joined #openstack-meeting-421:22
*** blahRus has joined #openstack-meeting-421:26
*** hvprash has quit IRC21:28
*** britthouser has quit IRC21:29
*** david-lyle has quit IRC21:30
*** shaohe_feng has quit IRC21:31
*** shaohe_feng has joined #openstack-meeting-421:32
*** spzala has quit IRC21:32
*** marst has quit IRC21:32
*** spzala has joined #openstack-meeting-421:33
*** spzala has quit IRC21:38
*** mbound has joined #openstack-meeting-421:41
*** shaohe_feng has quit IRC21:42
*** shaohe_feng has joined #openstack-meeting-421:42
*** yamamoto has joined #openstack-meeting-421:45
*** ddieterly is now known as ddieterly[away]21:45
*** cdelatte has quit IRC21:50
*** david-lyle has joined #openstack-meeting-421:52
*** shaohe_feng has quit IRC21:52
*** thorst_ has joined #openstack-meeting-421:52
*** trozet has quit IRC21:52
*** shaohe_feng has joined #openstack-meeting-421:52
*** v1k0d3n has joined #openstack-meeting-421:54
*** ddieterly[away] is now known as ddieterly21:54
*** thorst_ has quit IRC21:57
*** TaylorH has joined #openstack-meeting-421:59
*** prithiv has joined #openstack-meeting-422:00
*** vishwanathj has quit IRC22:00
*** TaylorHuang has quit IRC22:01
*** spotz is now known as spotz_zzz22:02
*** david-lyle has quit IRC22:02
*** shaohe_feng has quit IRC22:02
*** shaohe_feng has joined #openstack-meeting-422:03
*** dasanind has quit IRC22:03
*** piet has joined #openstack-meeting-422:06
*** dshakhray has quit IRC22:07
*** shaohe_feng has quit IRC22:12
*** shaohe_feng has joined #openstack-meeting-422:13
*** JRobinson__ has joined #openstack-meeting-422:15
*** spotz_zzz is now known as spotz22:22
*** shaohe_feng has quit IRC22:23
*** shaohe_feng has joined #openstack-meeting-422:23
*** spzala has joined #openstack-meeting-422:24
*** dasanind has joined #openstack-meeting-422:26
*** spzala has quit IRC22:30
*** thorst has joined #openstack-meeting-422:31
*** shaohe_feng has quit IRC22:33
*** shaohe_feng has joined #openstack-meeting-422:33
*** thorst has quit IRC22:34
*** spzala has joined #openstack-meeting-422:34
*** thorst has joined #openstack-meeting-422:35
*** spzala has quit IRC22:35
*** spzala has joined #openstack-meeting-422:35
*** singlethink has quit IRC22:35
*** dasanind has quit IRC22:39
*** thorst has quit IRC22:39
*** krtaylor has quit IRC22:41
*** spotz is now known as spotz_zzz22:42
*** shaohe_feng has quit IRC22:43
*** shaohe_feng has joined #openstack-meeting-422:44
*** dharinic_ has quit IRC22:44
*** yamahata has quit IRC22:45
*** bpokorny has quit IRC22:47
*** ddieterly has quit IRC22:51
*** Jeffrey4l has joined #openstack-meeting-422:53
*** mbound has quit IRC22:53
*** Jeffrey4l has quit IRC22:53
*** shaohe_feng has quit IRC22:53
*** shaohe_feng has joined #openstack-meeting-422:54
*** limao has joined #openstack-meeting-422:55
*** rbak has quit IRC22:58
*** shaohe_feng has quit IRC23:04
*** limao has quit IRC23:05
*** limao has joined #openstack-meeting-423:05
*** shaohe_feng has joined #openstack-meeting-423:06
*** yamahata has joined #openstack-meeting-423:11
*** bpokorny has joined #openstack-meeting-423:12
*** itisha has joined #openstack-meeting-423:13
*** shaohe_feng has quit IRC23:14
*** shaohe_feng has joined #openstack-meeting-423:15
*** bobh has joined #openstack-meeting-423:24
*** shaohe_feng has quit IRC23:24
*** shaohe_feng has joined #openstack-meeting-423:27
*** uxdanielle has quit IRC23:34
*** shaohe_feng has quit IRC23:34
*** shaohe_feng has joined #openstack-meeting-423:35
*** limao has quit IRC23:40
*** shaohe_feng has quit IRC23:45
*** shaohe_feng has joined #openstack-meeting-423:46
*** markvoelker has quit IRC23:49
*** woodster_ has quit IRC23:49
*** bobh has quit IRC23:49
*** azbiswas_ has quit IRC23:50
*** julim has joined #openstack-meeting-423:55
*** shaohe_feng has quit IRC23:55
*** shaohe_feng has joined #openstack-meeting-423:56
*** kzaitsev_mb has quit IRC23:58

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