Monday, 2017-03-20

*** reedip has joined #openstack-meeting-400:09
*** dave-mccowan has joined #openstack-meeting-400:13
*** baoli has quit IRC00:18
*** baoli has joined #openstack-meeting-400:22
*** bobh has joined #openstack-meeting-400:24
*** bobh has quit IRC00:27
*** limao has joined #openstack-meeting-400:33
*** reedip has quit IRC00:38
*** yamamoto has joined #openstack-meeting-400:41
*** yamamoto has quit IRC00:45
*** hippiepete has quit IRC00:50
*** hippiepete has joined #openstack-meeting-400:51
*** tovin07_ has joined #openstack-meeting-400:55
*** yifei has joined #openstack-meeting-400:57
*** Julien-zte has joined #openstack-meeting-401:01
*** bobmel has joined #openstack-meeting-401:04
*** baoli has quit IRC01:04
*** leo_wang has quit IRC01:06
*** bobmel has quit IRC01:09
*** yamamoto has joined #openstack-meeting-401:11
*** yamamoto has quit IRC01:15
*** gongysh has joined #openstack-meeting-401:16
*** julim has quit IRC01:21
*** julim has joined #openstack-meeting-401:23
*** rfolco has joined #openstack-meeting-401:23
*** rfolco has quit IRC01:23
*** bobh has joined #openstack-meeting-401:28
*** yamamoto has joined #openstack-meeting-401:28
*** yamamoto has quit IRC01:28
*** baoli has joined #openstack-meeting-401:30
*** reedip has joined #openstack-meeting-401:30
*** bobh has quit IRC01:32
*** Julien-zte has quit IRC01:34
*** yamamoto has joined #openstack-meeting-401:36
*** rfolco has joined #openstack-meeting-401:39
*** rfolco has quit IRC01:39
*** yamamoto has quit IRC01:41
*** markvoelker has joined #openstack-meeting-401:45
*** markvoelker has quit IRC01:49
*** rfolco has joined #openstack-meeting-401:54
*** rfolco has quit IRC01:54
*** lei-zh has joined #openstack-meeting-401:59
*** rfolco has joined #openstack-meeting-402:00
*** rfolco has quit IRC02:00
*** yamamoto has joined #openstack-meeting-402:19
*** yamamoto has quit IRC02:19
*** yamamoto has joined #openstack-meeting-402:31
*** lei-zh has quit IRC02:39
*** lei-zh has joined #openstack-meeting-402:39
*** hippiepete has quit IRC03:03
*** bobmel has joined #openstack-meeting-403:05
*** lei-zh has quit IRC03:07
*** lei-zh has joined #openstack-meeting-403:07
*** bobmel has quit IRC03:11
*** lei-zh has quit IRC03:11
*** lei-zh has joined #openstack-meeting-403:11
*** janonymous has joined #openstack-meeting-403:13
*** baoli has quit IRC03:14
*** dave-mccowan has quit IRC03:20
*** hippiepete has joined #openstack-meeting-403:20
*** zhurong has joined #openstack-meeting-403:25
*** lei-zh has quit IRC03:27
*** lei-zh has joined #openstack-meeting-403:27
*** lei-zh has quit IRC03:29
*** yamamoto has quit IRC03:50
*** yamamoto has joined #openstack-meeting-403:57
*** yamamoto has quit IRC03:59
*** yamamoto has joined #openstack-meeting-404:00
*** yamamoto has quit IRC04:00
*** psachin has joined #openstack-meeting-404:09
*** zhurong has quit IRC04:16
*** gongysh has quit IRC04:18
*** links has joined #openstack-meeting-404:20
*** SerenaFeng has joined #openstack-meeting-404:44
*** unicell1 has joined #openstack-meeting-404:53
*** unicell has quit IRC04:54
*** yamamoto has joined #openstack-meeting-404:55
*** zhurong has joined #openstack-meeting-404:59
*** yamamoto has quit IRC05:00
*** gongysh has joined #openstack-meeting-405:04
*** janki has joined #openstack-meeting-405:04
*** zhurong has quit IRC05:14
*** vks1 has joined #openstack-meeting-405:16
*** adisky_ has joined #openstack-meeting-405:23
*** anilvenkata has joined #openstack-meeting-405:26
*** Julien-zte has joined #openstack-meeting-405:28
*** bobh has joined #openstack-meeting-405:31
*** cartik has joined #openstack-meeting-405:31
*** bobh has quit IRC05:36
*** vks1 has quit IRC05:39
*** cartik has quit IRC05:42
*** ntpttr_ has joined #openstack-meeting-405:53
*** vks1 has joined #openstack-meeting-405:55
*** bobmel has joined #openstack-meeting-405:57
*** ntpttr_ has quit IRC05:58
*** gongysh has quit IRC05:58
*** bobmel has quit IRC06:01
*** Sukhdev has joined #openstack-meeting-406:07
*** gongysh has joined #openstack-meeting-406:10
*** yamamoto has joined #openstack-meeting-406:11
*** yamamoto has quit IRC06:18
*** yamahata has joined #openstack-meeting-406:29
*** lei-zh has joined #openstack-meeting-406:30
*** bobh has joined #openstack-meeting-406:32
*** bobh has quit IRC06:36
*** Sukhdev has quit IRC06:48
*** karthiks_afk has joined #openstack-meeting-406:57
*** nkrinner_afk is now known as nkrinner07:03
*** alexchadin has joined #openstack-meeting-407:19
*** bogdando has joined #openstack-meeting-407:22
*** Jeffrey4l__ has quit IRC07:33
*** Jeffrey4l__ has joined #openstack-meeting-407:36
*** makowals has joined #openstack-meeting-407:37
*** lionelze has joined #openstack-meeting-407:42
*** karthiks_afk is now known as karthiks07:43
*** lei-zh has quit IRC07:44
*** lei-zh has joined #openstack-meeting-407:44
*** ralonsoh has joined #openstack-meeting-407:51
*** bobmel has joined #openstack-meeting-407:58
*** matrohon has joined #openstack-meeting-408:00
*** bobmel has quit IRC08:02
*** armax has quit IRC08:05
*** sshnaidm|off is now known as sshnaidm08:09
*** bobmel has joined #openstack-meeting-408:10
*** neiljerram has quit IRC08:11
*** pcaruana has joined #openstack-meeting-408:14
*** xiaohhui has joined #openstack-meeting-408:18
*** yamamoto has joined #openstack-meeting-408:22
*** matrohon has quit IRC08:32
*** bobh has joined #openstack-meeting-408:33
*** bobh has quit IRC08:38
*** bobmel_ has joined #openstack-meeting-408:42
*** bobmel has quit IRC08:45
*** sshnaidm is now known as sshnaidm|afk08:47
*** joedborg has joined #openstack-meeting-408:48
*** ishafran has joined #openstack-meeting-408:50
*** nick-ma has joined #openstack-meeting-408:51
*** nick-ma_ has joined #openstack-meeting-408:55
*** nick-ma has quit IRC08:58
*** bobmel has joined #openstack-meeting-408:59
*** ishafran has quit IRC09:00
oanson#startmeeting Dragonflow09:00
openstackMeeting started Mon Mar 20 09:00:17 2017 UTC and is due to finish in 60 minutes.  The chair is oanson. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: Dragonflow)"09:00
openstackThe meeting name has been set to 'dragonflow'09:00
*** ishafran has joined #openstack-meeting-409:00
nick-ma_Hi09:00
dimakhello09:00
*** itamaro has joined #openstack-meeting-409:00
oansonWe'll wait another minute. Then we'll start09:01
lihiHi09:01
ishafranHi09:01
itamarohi09:01
*** oshidoshi has joined #openstack-meeting-409:01
oanson#info nick-ma_ dimak lihi ishafran itamaro in meeting09:01
oansonxiaohhui, are you here too?09:01
xiaohhuiyeah,09:02
oanson#info xiaohhui also in meeting09:02
oansonGreat! Let's start.09:02
oanson#topic Roadmap09:02
*** bobmel_ has quit IRC09:02
*** openstack changes topic to "Roadmap (Meeting topic: Dragonflow)"09:02
oansonlihi, hit us with the IPv6 stuff09:02
lihiThe SG is almost done. I need to make a small fix to the tests09:03
oansonGreat!09:04
oansonDo you have an ETA?09:04
*** yamamoto has quit IRC09:04
lihitomorrow probably. After I'll finish with the migration09:04
oansonSure!09:04
oansondimak, SFC?09:05
dimakHaven't made a lot of progress due to many small things I had to take care of09:05
*** hshan has joined #openstack-meeting-409:05
dimakBut I am testing now mpls unaware port pairs09:05
oansonCool09:06
dimakOther than that I have some comments to fix09:06
oansonAll right09:06
oansonChassis health - I don't know if we discussed this previously. But this needs a carrier for the last mile.09:06
oansonIf there are no volunteers, I can take this next week. If anyone's free, it would be nice to get this to the finish line09:07
oanson(Or did someone already volunteer and I forgot?)09:07
xiaohhuiI said I would take this in previous meeting09:08
xiaohhuibut I am not free recently09:08
oansonxiaohhui, I heard. Congratulations.09:08
xiaohhuiIf you would like take it, that would be good from my point of view.09:08
oansonIf you can't get to it, I can take it.09:08
xiaohhuithanks,09:08
oansonSure. Summary: I took it. Will do it next week :)09:09
oansonsNAT - the patch is waiting for review. ishafran, anything to say on this?09:09
ishafranall comments are closed09:09
ishafranactually I'm waiting for merge :)09:10
oansonAll right. We'll try to get to it as soon as we can.09:10
ishafrangreat09:10
oansonNB API refactor09:10
oansonWork is coming along. QoS and LSwitch are ready for review: https://review.openstack.org/#/c/441950/09:11
oansonSG and lport are WIP here: https://review.openstack.org/#/c/445548 and https://review.openstack.org/#/c/44736609:12
oansonI think SG will be done today, hopefully lport tomorrow.09:12
xiaohhuiAnd loudos-review.huawei.com/#/q/dragonflow09:12
xiaohhuicloudos-review.huawei.com/#/q/dragonflow09:12
oansonThen VLAN aware VMs will be rebased on top of that and can be tested manually (I hope)09:13
xiaohhuisorry, don't know what happened09:13
xiaohhuihttps://review.openstack.org/#/c/443648/09:13
xiaohhuiThis is the migration for lrouter and lrouter port, I will reshape it these days.09:14
*** reedip has quit IRC09:14
oansonYes. Sorry - LRouter and LRouterPort is also WIP in the link above09:14
oansonAnything else for roadmap?09:14
oansonThen let's move on09:15
oanson#topic Open Discussion09:15
*** openstack changes topic to "Open Discussion (Meeting topic: Dragonflow)"09:15
oansonnick-ma_, I understood last week you were interested in the iovisor work09:16
oansonI invited the person working on this today, but he couldn't make it. I will send you his contact details off-line09:16
oansonActually, he says he will join momentarily.09:16
lionelzeHi09:17
nick-ma_Ok, thanks09:18
lionelzeThe first step for IOVisor is to check if it's worth to work on it.09:18
lionelzeWhat can bring an implementation based on it in place of ovs09:19
oansonlionelze, you mean test it performance-wise?09:20
nick-ma_Yes, I researched some day, and thought it is a huge work.09:21
*** lei-zh has quit IRC09:21
lionelzeI'd like to compare performance between OVS and IOVisor without hardware help.09:21
oansonCurrently our DF applications are heavily based on OVS/OpenFlow. We will have to find a less hard-coded solution.09:21
nick-ma_I tested plumgrid and discussed with the team on the technology. The performance is outstanding.09:22
nick-ma_9g per physical port on vxlan tunneling09:22
oansonNice!09:23
lionelzeNice, Do you test small UDP packets?09:23
nick-ma_I think I have the report. Will find it.09:23
nick-ma_The control plane is not open source.09:24
lionelzeIf we consider that it worth to work on it, the design stage will begin.09:25
nick-ma_The documents I think is not sufficient. To implement a full functionality of switch, lots of work needs to be done. s to09:26
lionelzeYou can check this project to see what can be done: https://github.com/iovisor/iovisor-ovn09:26
nick-ma_Cool, I dont know ovn is starting working on it.09:27
*** alexchadin has quit IRC09:27
lionelzeI know that the work can be huge but it can worth it.09:27
nick-ma_Yes, I think so.09:27
oansonAll right. Anything more on this?09:28
oansonThen I guess the floor is free.09:29
oansonAnyone wants to bring anything up for discussion?09:29
oansonAll right.09:31
oansonThanks everyone for coming.09:31
oanson#endmeeting09:31
*** openstack changes topic to " (Meeting topic: ironic_neutron)"09:31
openstackMeeting ended Mon Mar 20 09:31:19 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-03-20-09.00.html09:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-03-20-09.00.txt09:31
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-03-20-09.00.log.html09:31
*** itamaro has quit IRC09:33
*** Julien-zte has quit IRC09:35
*** ishafran has quit IRC09:35
*** neiljerram has joined #openstack-meeting-409:35
*** nick-ma_ has quit IRC09:37
*** qwebirc50898 has joined #openstack-meeting-409:40
*** SerenaFeng has quit IRC09:44
*** neil_ has joined #openstack-meeting-409:45
*** neil_ has quit IRC09:46
*** salmankhan has joined #openstack-meeting-409:47
*** yamahata has quit IRC09:48
*** reedip has joined #openstack-meeting-409:53
*** alexchadin has joined #openstack-meeting-409:58
*** lei-zh has joined #openstack-meeting-410:00
*** yamamoto has joined #openstack-meeting-410:03
*** limao has quit IRC10:06
*** pbourke has quit IRC10:07
*** pbourke has joined #openstack-meeting-410:07
*** yamamoto has quit IRC10:07
*** sshnaidm|afk is now known as sshnaidm10:09
*** lei-zh has quit IRC10:12
*** vks1 has quit IRC10:14
*** tovin07_ has quit IRC10:16
*** yamamoto has joined #openstack-meeting-410:21
*** yamamoto has quit IRC10:21
*** vks1 has joined #openstack-meeting-410:34
*** bobh has joined #openstack-meeting-410:35
*** bobh has quit IRC10:39
*** hshan has quit IRC10:40
*** matrohon has joined #openstack-meeting-410:54
*** alexchadin has quit IRC11:04
*** psachin has quit IRC11:05
*** rwallner has joined #openstack-meeting-411:10
*** matrohon has quit IRC11:12
*** aarefiev_afk is now known as aarefiev11:15
*** zhurong has joined #openstack-meeting-411:17
*** matrohon has joined #openstack-meeting-411:18
*** yamamoto has joined #openstack-meeting-411:22
*** chigang has joined #openstack-meeting-411:25
*** yamamoto has quit IRC11:30
*** alexchadin has joined #openstack-meeting-411:33
*** Jeffrey4l_ has joined #openstack-meeting-411:34
*** bobh has joined #openstack-meeting-411:35
*** Jeffrey4l__ has quit IRC11:36
*** zhurong has quit IRC11:37
*** bobh has quit IRC11:40
*** yamamoto has joined #openstack-meeting-411:41
*** anilvenkata has quit IRC11:42
*** psachin has joined #openstack-meeting-411:42
*** anilvenkata has joined #openstack-meeting-411:48
*** kylek3h has quit IRC11:55
*** gongysh has quit IRC12:06
*** alexchadin has quit IRC12:07
*** vks1 has quit IRC12:07
*** dave-mccowan has joined #openstack-meeting-412:07
*** rfolco has joined #openstack-meeting-412:11
*** alexchadin has joined #openstack-meeting-412:12
*** julim has quit IRC12:15
*** julim has joined #openstack-meeting-412:15
*** bobh has joined #openstack-meeting-412:15
*** bobh has quit IRC12:20
*** matrohon has quit IRC12:28
*** yfauser has joined #openstack-meeting-412:30
*** matrohon has joined #openstack-meeting-412:31
*** ralonsoh_ has joined #openstack-meeting-412:34
*** kylek3h has joined #openstack-meeting-412:37
*** liangy has joined #openstack-meeting-412:42
*** cleong has joined #openstack-meeting-412:51
*** woodard has joined #openstack-meeting-412:52
*** yuvalb has quit IRC12:53
*** yuvalb has joined #openstack-meeting-412:54
*** yamamoto has quit IRC12:55
*** uck has joined #openstack-meeting-412:55
*** gongysh has joined #openstack-meeting-412:58
*** bcafarel has quit IRC12:59
*** bcafarel has joined #openstack-meeting-413:00
*** markvoelker has joined #openstack-meeting-413:01
*** salmankhan has quit IRC13:01
*** salmankhan has joined #openstack-meeting-413:02
*** haleyb has joined #openstack-meeting-413:09
*** limao has joined #openstack-meeting-413:11
*** links has quit IRC13:11
*** Julien-zte has joined #openstack-meeting-413:14
*** Sukhdev has joined #openstack-meeting-413:25
*** cathrichardson has joined #openstack-meeting-413:26
*** cathrich_ has quit IRC13:28
*** baoli has joined #openstack-meeting-413:37
*** Sukhdev has quit IRC13:39
*** Sukhdev has joined #openstack-meeting-413:39
*** julim has quit IRC13:40
*** ralonsoh_ has quit IRC13:40
*** kzaitsev_ws has joined #openstack-meeting-413:44
*** edleafe- is now known as edleafe13:45
*** klamath has joined #openstack-meeting-413:45
*** galstrom_zzz is now known as galstrom13:45
*** klamath has quit IRC13:45
*** galstrom is now known as galstrom_zzz13:46
*** klamath has joined #openstack-meeting-413:46
*** hongbin has joined #openstack-meeting-413:47
*** xiaohhui has quit IRC13:50
*** armax has joined #openstack-meeting-413:53
*** FrankZhang has joined #openstack-meeting-413:55
*** yamamoto has joined #openstack-meeting-413:55
*** vks1 has joined #openstack-meeting-413:56
*** yedongcan has joined #openstack-meeting-413:56
*** ivc_ has joined #openstack-meeting-413:59
*** alraddarla has joined #openstack-meeting-414:00
apuimedo#startmeeting kuryr14:01
openstackMeeting started Mon Mar 20 14:01:04 2017 UTC and is due to finish in 60 minutes.  The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: kuryr)"14:01
openstackThe meeting name has been set to 'kuryr'14:01
apuimedoHello everybody and welcome to the weekly IRC meeting14:01
apuimedowho's here today?14:01
alraddarlao/14:01
yedongcano/14:01
limaoo/14:01
*** irenab_ has joined #openstack-meeting-414:01
apuimedoirenab: hongbin: ltomasbo|away:14:02
hongbino/14:02
irenab_hi14:02
apuimedo#topic kuryr-libnetwork14:03
*** openstack changes topic to "kuryr-libnetwork (Meeting topic: kuryr)"14:03
*** hemanthm|pto is now known as hemanthm14:03
*** yamamoto has quit IRC14:04
apuimedoI think we are practically at the point of being able to cut a release14:04
hongbin+114:04
yedongcanyes14:05
limao+114:05
irenab_+114:05
apuimedovery well14:05
apuimedoI'm merging https://review.openstack.org/#/c/444661/614:05
apuimedoCause having more fullstack tests is always good14:05
apuimedoAlso https://review.openstack.org/#/c/446891/314:06
apuimedoso people can make easily vagrant machines of the release14:06
hongbini will submit another revision for this one soon: https://review.openstack.org/#/c/445683/ , i think it would be good to have this fix in the release as well14:07
*** woodard has quit IRC14:07
yedongcanThanks, hongbin.14:07
apuimedohongbin: I'd like to merge https://review.openstack.org/#/c/446706/3 too. But it needs to reference the blueprint for IPv6 as janonymous said14:08
hongbinapuimedo: ack14:08
apuimedohongbin: agreed on https://review.openstack.org/#/c/445683/14:08
apuimedoDo we all agree to cut the release when https://review.openstack.org/#/c/445683/ gets merged?14:09
irenab_yes14:09
yedongcan+114:09
limao+114:09
apuimedo+114:09
apuimedohongbin:14:10
hongbinapuimedo: +114:10
apuimedovery well then14:10
apuimedo#info Kuryr-libnetwork will cut a release when https://review.openstack.org/#/c/445683/ is merged14:10
apuimedoalright. Final part of this topic14:11
apuimedoDo we want to set up some goals for making a Pike release?14:11
*** thomasem has joined #openstack-meeting-414:12
irenab_Can we add this topic for next weekly to think till then?14:13
apuimedo#action apuimedo bring up to the mailing list the question of having a Pike release for kuryr-libnetwork14:13
apuimedoirenab_: oops. we wrote at the same time14:13
apuimedo:P14:13
apuimedolet's take it to the ML14:13
irenab_+1 on email14:13
apuimedoand vote next week14:13
irenab_agreed14:13
apuimedo#info Next weekly meeting will see a vote on kuryr-libnetwork pike release14:14
apuimedoIt's between keeping fully async releases only or having async releases + some OSt joint releases14:14
apuimedo#topic kuryr-lib14:14
*** openstack changes topic to "kuryr-lib (Meeting topic: kuryr)"14:14
apuimedoI would like to propose to cut a 0.3.1 release for kuryr-lib14:15
apuimedoso that it includes the nested vlan shuffling and device_owner fixes14:16
irenab_+114:16
yedongcan+114:16
irenab_apuimedo: what is still pending review ?14:17
apuimedolimao: hongbin14:17
apuimedoirenab_: afaik only requirements14:17
apuimedowhich I don't want to touch14:17
apuimedobefore a release14:17
limao+114:17
apuimedovery well14:17
*** salmankhan has quit IRC14:17
apuimedo#action apuimedo to send patch for 0.3.1 kuryr-lib release14:17
*** yfauser has quit IRC14:18
apuimedo#info I've been working on rpm packages for kuryr-kubernetes. I'll be adding kuryr-lib as well (package name python-kuryr)14:18
apuimedoanything else on kuryr-lib?14:18
apuimedovery well, moving on14:20
apuimedo#topic fuxi14:20
*** openstack changes topic to "fuxi (Meeting topic: kuryr)"14:20
hongbinhi14:20
apuimedo#chair hongbin14:20
openstackCurrent chairs: apuimedo hongbin14:20
hongbinlast week, this patch got merged https://review.openstack.org/#/c/438292/ , which is the first step for setting up the ci for manila provider14:20
hongbinbesides that, there are other fixed proposed: https://review.openstack.org/#/c/445788/ https://review.openstack.org/#/c/447305/ https://review.openstack.org/#/c/429484/14:21
hongbinthat is for fuxi, i didn't receive a update from fuxi-kubernetes side this week14:21
hongbini will try to give an update next week on that14:21
apuimedothanks hongbin14:21
hongbinapuimedo: that is all from my side14:21
apuimedovery well14:22
apuimedoI'm merging those changes14:22
apuimedo#topic kuryr-kubernetes14:22
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)"14:22
hongbinapuimedo: thx14:22
apuimedoWe have a few blueprints to vote on14:23
*** julim has joined #openstack-meeting-414:23
apuimedohttps://blueprints.launchpad.net/kuryr-kubernetes/+spec/kuryr-k8s-contrail-integration14:23
alraddarla+1 ;)14:23
apuimedo+114:24
apuimedoivc delegated a +1 vote on me14:24
irenab_+114:24
apuimedovery well then. I'll merge the spec and approve the blueprint14:25
apuimedo#info Kuryr-kubernetes contrail integration bp https://blueprints.launchpad.net/kuryr-kubernetes/+spec/kuryr-k8s-contrail-integration approved14:25
alraddarlaThanks all14:25
*** cathrichardson has quit IRC14:26
*** cathrichardson has joined #openstack-meeting-414:26
apuimedosecond14:26
apuimedoI submitted this blueprint https://blueprints.launchpad.net/kuryr-kubernetes/+spec/use-ovsdbapp14:26
apuimedomuch like we use pyroute2 instead of "ip link", it would make us use ovsdbapp instead of "ovs-vsctl14:27
apuimedo"14:27
apuimedoThe code is the same production ready code that used to live in openstack/neutron14:28
apuimedoI helped Neutron's otherwiseguy split it in the Atlanta PTG14:28
apuimedoand the idea is that os-vif will end up using it as well14:28
*** cathrichardson has left #openstack-meeting-414:28
irenab_apuimedo: just use lib instead of wrapping commands on kuryr side?14:29
apuimedoexactly14:29
apuimedoit's native14:29
irenab_+114:29
apuimedoyedongcan: limao: hongbin: maybe it would be a good idea to implement this for a Pike release in kuryr-libnetwork too14:29
yedongcan+114:29
limao+114:29
janonymouso/14:29
hongbin+114:29
apuimedoVery well then14:29
apuimedo#info ovsdbapp usage is approved. It will wait merging for the first release of ovsdbapp14:30
apuimedoI would also like to bring for discussion https://blueprints.launchpad.net/kuryr-kubernetes/+spec/driver-handler-opt-loading14:31
apuimedoirenab_: do you think we need a spec for this one?14:32
irenab_apuimedo: similar to the neutron ml2/services drivers?14:32
apuimedoright14:32
irenab_apuimedo: I donot think we need spec, can be later added into devref to guide on adding new driver14:33
apuimedojanonymous: could you update https://blueprints.launchpad.net/kuryr-kubernetes/+spec/client-migration to reflect the discussion in the VTG ?14:33
*** iyamahat has joined #openstack-meeting-414:33
apuimedoso we can approve it soon and start using it14:33
janonymousapuimdeo: yes , sure i will14:33
apuimedoirenab_: very well. Thanks14:33
apuimedojanonymous: thanks!14:33
apuimedoirenab_: Let's vote on that one over ml14:33
apuimedo#action apuimedo to bring https://blueprints.launchpad.net/kuryr-kubernetes/+spec/driver-handler-opt-loading for ml voting14:34
apuimedojanonymous: I saw you submitted another one https://blueprints.launchpad.net/kuryr-kubernetes/+spec/oslo-gmr14:34
irenab_apuimedo: I think it makes sense, not sure needs ml to confirm, but up to you14:34
apuimedoirenab_: to be on the safe side14:34
apuimedo:-)14:34
janonymousapuimedo: yes i will complete it this week14:35
apuimedojanonymous: very well14:35
apuimedo#action janonymous to complete https://blueprints.launchpad.net/kuryr-kubernetes/+spec/oslo-gmr and ping cores about it so we can vote next weekly IRC meeting14:35
*** salmankhan has joined #openstack-meeting-414:36
apuimedoyedongcan: thanks for https://review.openstack.org/#/c/447385/14:37
apuimedomerging it14:37
apuimedo:-)14:37
apuimedoand thanks janonymous for the report that led to the fix14:37
apuimedoPlease, all of you, rebase your patches after this one14:38
apuimedoso that we don't get false -1s14:38
apuimedoSorry. I got to go. Please ping me on #openstack-kuryr for more discussion. Thank you all for joining14:38
apuimedo#endmeeting14:38
*** openstack changes topic to " (Meeting topic: ironic_neutron)"14:38
openstackMeeting ended Mon Mar 20 14:38:55 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-03-20-14.01.html14:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-03-20-14.01.txt14:38
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-03-20-14.01.log.html14:39
*** alraddarla has left #openstack-meeting-414:40
*** isq has quit IRC14:40
*** yedongcan has left #openstack-meeting-414:41
*** irenab_ has quit IRC14:45
*** galstrom_zzz is now known as galstrom14:46
*** yamahata has joined #openstack-meeting-414:47
*** marst has quit IRC14:48
*** limao has quit IRC14:48
*** armax has quit IRC14:53
*** woodard has joined #openstack-meeting-414:55
*** limao has joined #openstack-meeting-414:55
*** marst has joined #openstack-meeting-414:56
*** marst has quit IRC14:56
*** marst has joined #openstack-meeting-414:56
*** janki has quit IRC14:58
*** bobh has joined #openstack-meeting-414:59
thomasem#startmeeting craton14:59
thomasem#chair sigmavirus sulo jimbaker thomasem14:59
openstackMeeting started Mon Mar 20 14:59:59 2017 UTC and is due to finish in 60 minutes.  The chair is thomasem. Information about MeetBot at http://wiki.debian.org/MeetBot.14:59
thomasem#link https://etherpad.openstack.org/p/craton-meetings15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
thomasem#topic Roll Call15:00
*** openstack changes topic to " (Meeting topic: craton)"15:00
openstackThe meeting name has been set to 'craton'15:00
openstackCurrent chairs: jimbaker sigmavirus sulo thomasem15:00
*** openstack changes topic to "Roll Call (Meeting topic: craton)"15:00
thomasemo/15:00
suloo/15:00
*** ivc_ has left #openstack-meeting-415:00
*** woodard has quit IRC15:00
thomasemjimbaker, sigmavirus, and fsaad said they'll be a little late.15:01
*** anonymike has joined #openstack-meeting-415:01
*** woodard has joined #openstack-meeting-415:01
thomasemo/ anonymike15:01
anonymike\o thomasem15:01
antonymo/15:01
thomasem#topic Action Items from Last Meeting15:01
thomasem#link  http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-03-13-15.00.html15:01
*** openstack changes topic to "Action Items from Last Meeting (Meeting topic: craton)"15:01
thomasemACTION: thomasem to write BP regarding deployment as a starting point for iterating on a suggested deployment model15:02
thomasemHigher priority things in play, will be punting this again. I do think I can get something up this week, though!15:02
thomasem#action thomasem to write BP regarding deployment as a starting point for iterating on a suggested deployment model15:03
thomasemACTION: jimbaker to map Dusty's requirements to work or existing features of Craton, especially with respect to short-term deliverable15:03
thomasemNot sure how relevant this is anymore, will hear jimbaker's thoughts when he gets in (probably in Open Discussion or prioritizing).15:03
thomasem#topic Stand-up15:03
thomasem#info each team member briefly describes what they are working on this week, and describes blockers (if there are any)15:03
*** openstack changes topic to "Stand-up (Meeting topic: craton)"15:03
thomasem#topic Stand Up :: thomasem15:03
*** openstack changes topic to "Stand Up :: thomasem (Meeting topic: craton)"15:03
*** tojuvone has joined #openstack-meeting-415:03
tojuvonehi15:04
*** alexchadin has quit IRC15:04
thomasemCleaning up MySQL 5.7 patch today by updating documentation according to some testing in Ubuntu 16.04, CentOS 7, and Fedora 25 and being sure the documented install works, and noting the requirement of MySQL 5.7 for nested variable searching. Also have several reviews I want to go through today.15:05
thomasemStarted work on functional tests for nested variable search... trying to do it in a way that affords for testing all resources the same way, so we're not copy/pasting everywhere and possibly introducing inconsistencies. Working through some snags there.15:06
thomasemThe patch, however, can be pulled down and run as long as you're using MySQL 5.715:06
thomasem#link https://review.openstack.org/44394115:07
thomasemdone15:07
thomasem#topic Stand Up :: sulo15:07
*** openstack changes topic to "Stand Up :: sulo (Meeting topic: craton)"15:07
suloworking on a few issues re: users cretion, found some more issues that needs fixing .. after that i might poke that device sharing15:08
sulodone15:08
thomasem#topic Stand Up :: anonymike15:08
*** openstack changes topic to "Stand Up :: anonymike (Meeting topic: craton)"15:08
anonymikeHello all. My name is Michael, I'm a developer at Rackspace and I just started on the Craton team today. I'm working on transferring some internal accounts  and getting my dev environment setup.15:09
anonymikedone15:09
*** adisky_ has quit IRC15:09
thomasem#topic Stand Up :: antonym15:09
*** openstack changes topic to "Stand Up :: antonym (Meeting topic: craton)"15:09
antonymtesting out thomasem's patch for searching on a list of mac's which works well after switching to mysql 5.7, also got together a dev playbook for setting up the stack on a server w/o docker, done15:11
thomasem(YAY!)15:11
antonymit's here for right now: https://github.com/antonym/ecopoiesis/blob/master/roles/ecopoiesis/tasks/craton_install.yml15:11
antonymprobably need to pull it out into a role15:11
thomasem#link https://github.com/antonym/ecopoiesis/blob/master/roles/ecopoiesis/tasks/craton_install.yml15:11
thomasem#topic This Week's Priorities15:12
*** yfauser has joined #openstack-meeting-415:12
*** openstack changes topic to "This Week's Priorities (Meeting topic: craton)"15:12
jimbakero/15:12
suloantonym: nice!15:12
thomasemPriorities (tentative):15:13
thomasem1. https://review.openstack.org/44164415:13
thomasem(Alembic)15:13
*** rhedlind has joined #openstack-meeting-415:14
jimbakerthomasem, thanks, yes, i will be finalizing this. i don't anticipate anything blocking that work15:14
thomasem2. https://review.openstack.org/446972 and https://review.openstack.org/446938 (Issue with creating users)15:14
*** rhedlind has left #openstack-meeting-415:14
thomasem3. https://review.openstack.org/440929 (Resolved Variable Search)15:14
thomasem4. https://review.openstack.org/443186 (MySQL 5.7 and SQLAlchemy 1.1.6)15:15
thomasem5. https://review.openstack.org/443941 (Nested variable search)15:15
thomasemDo folks agree with those priorities?15:15
jimbakerthomasem, these look good as our most important priorities15:15
*** limao has quit IRC15:15
thomasem#2 is how project_id was not being honored in user creation, so it's a big deal.15:16
jimbakeragreed about this being a big deal15:16
jimbakerit effectively means we are not multitenant until we get this done15:16
jimbaker(was hidden until recently because we were using mysql directly. don't do that :)15:17
thomasemOther than that, we have some integration test stuff up for craton client, which has been a gap for a while.15:17
thomasemand we have some documentation that sigmavirus shored up.. so several in-flight reviews that could use some eyes.15:17
sigmavirussorry for being late. I think some of the leftovers I ate yesterday went bad15:17
sigmavirusYep, I'll be working on more documentation to get some stuff at the least started15:17
thomasemExcellent! Thanks for doing that, sigmavirus!15:18
jimbakersigmavirus, thanks! important stuff for the project15:18
sigmavirusI'll be working on doing some reveiws too15:18
jimbakermuch as we saw how getting tox -e functional made a huge diff15:18
thomasemAlright, assuming that's smiles all around, let's move into open discussion.15:19
jimbaker:) :) :)15:19
thomasem#topic Open Discussion15:19
*** openstack changes topic to "Open Discussion (Meeting topic: craton)"15:19
thomasemWe have several topics today15:19
thomasemfrom sulo: Review process (proposing that we require at least 2 +2 before a +1, so atleast 2 ppl review before merge)15:19
*** uck has quit IRC15:20
jimbakermakes sense15:20
anonymikeI agree15:20
jimbakerlet's be clear, there are several valid review processes in open source15:20
thomasems/people/cores/15:21
jimbakerbut given team size, openstack standards, and current project goals, we should be good15:21
thomasems/people/ppl/15:21
thomasem:)15:21
jimbakerthomasem, yep, implied by gerrit :)15:21
thomasemHaha, indeed15:21
jimbakerobviously we were in an expedited mode in 0.1.015:22
jimbakerand that was a good thing15:22
jimbakerbut we need to go to normal mode now15:22
thomasemSo, yeah, during the time we needed to move fast and cores were out, we saw a need to afford for cores to self-merge high value things. We tended to favor some +1s at least. But, yeah, now that we're towards the end of that short-term workstream, it definitely makes sense to tighten back up.15:22
thomasemRight15:22
thomasemsulo: anything to add?15:23
sulothomasem: nothing on the review, process, looks like we all agree15:24
thomasemAwesome15:24
jimbakeragreement all around15:24
thomasemfrom sulo: Do we want to support, transfer of resouces between projects, see Ian's comment on: https://review.openstack.org/#/c/44693815:24
jimbakerthomasem, so sounds like an #agreed item15:24
thomasemOh, sorry. Didn't know that was a command.15:25
sigmavirusthomasem:  it s15:25
sigmavirususually happens after a #vote though15:25
sigmavirus=P15:25
jimbakersigmavirus, thanks for the process help15:25
thomasem#agreed require at least 2 +2 before a +1 workflow, so at least 2 cores review before merge15:25
thomasemlol, gotcha15:26
jimbakerthanks. we will do a formal vote next time. but we do an informal canvassing15:26
jimbakerwe *did* do15:26
thomasemEither/or. As long as #agreed works the same ultimately.15:26
thomasemimo15:26
jimbakerjust want to doc in minutes appropriately at the very least15:26
jimbakeryep15:26
jimbakercool, next topic?15:27
thomasemYep, noted it above ^^15:27
thomasem"from sulo: Do we want to support, transfer of resouces between projects, see Ian's comment on: https://review.openstack.org/#/c/446938"15:27
thomasemI think sigmavirus and sulo were discussing this earlier15:27
jimbakerahh, this is a very interesting problem15:27
sigmavirusRight, I'm not certain we do15:27
sigmavirusBut I'm also not certain others won't want it15:28
sigmavirusSo I'm not saying we should support it now15:28
thomasemThis also has some implications here: https://bugs.launchpad.net/craton/+bug/1666699 (able to create unexpected relationships via API)15:28
openstackLaunchpad bug 1666699 in craton "able to create unexpected relationships via API" [Undecided,New]15:28
jimbakerthomasem, agreed with that15:28
*** baoli has quit IRC15:28
jimbakeri think the following should hold15:28
jimbakerwe should not require the user to work with our denormalized data model15:28
jimbakerthat to me is an implementation detail15:28
jimbakerthat should not be exposed15:29
jimbakerthat it in fact is exposed (poorly) is causing that bug15:29
jimbakermentioned above15:29
jimbakerso what does this mean in practice?15:30
*** yfauser has quit IRC15:30
jimbakerif creating a cell, just specify its region_id15:30
*** tonytan4ever has joined #openstack-meeting-415:30
*** baoli has joined #openstack-meeting-415:30
jimbakeri think the way it sneaked in here is the optional cell part15:30
thomasemI think some audit of the exposure is important here. Does one not need to specify all parents of, say, a device that's being created?15:31
jimbakerthomasem, that's the net of it. only specify the parent15:32
*** beekneemech is now known as bnemec15:32
thomasemRight15:32
jimbakeri suppose we could allow for overspecification15:32
jimbakerbut only the parent counts, and if the overspecification is wrong, then an error is returned15:32
thomasemRight, so why have it in the first place?15:32
jimbakerthomasem, i think it makes sense from a data model perspective15:33
jimbakerdenormalization is a valid approach15:33
*** armax has joined #openstack-meeting-415:33
jimbakerbut again, impl detail15:33
jimbakerthat the client should not have to be aware of15:33
jimbakerhaving said that: i'm absolutely fine with us re-opening and looking at consequences15:33
thomasemI have some concerns with that being the only approach, but until I have something concrete to suggest, I'd prefer not rabbit hole on it.15:34
jimbakerthomasem, yep. this is entirely valid refactoring15:34
thomasemYeah. It's on my to-do list to pull in some data modeling folks and see what options might suit our needs and improve our data integrity constraints at the DB rather than having to code around it.15:34
jimbakerthomasem, we can always benefit from a review15:34
thomasemBut, ultimately the problem is it's exposed to the user as a bug now, so yep.15:35
thomasemAnd, bringing it back to the original topic, if we afford for moving resources between projects, we have to be sure we maintain that integrity along the way.15:35
jimbakerright, let's get rid of this bug by 1) requiring only parent; 2) possibly allow overspecification (and that also is backwards compatible...)15:35
*** baoli has quit IRC15:36
jimbakerthomasem, agreed15:36
jimbakera database is of little use if it's corrupted15:36
thomasemSo, the original question was: do we want to allow for that?15:36
thomasemSpot on15:36
thomasemWhat are some use-cases for allowing us to move resources between projects? And what resources?15:36
jimbakerin principle, i see it as being reasonable. however, it may make the multisource replication more challenging15:37
thomasemOh, yeah... also if we can move between projects, why not clouds, regions, cells, etc.?15:37
thomasemI can see a case for, say, rebalancing hosts between cells15:38
*** baoli has joined #openstack-meeting-415:38
jimbakerwithin a project, it makes perfect sense15:38
thomasemRight15:38
thomasemSo, is this a question we want to address now or later? Do we have concrete use-cases?15:38
jimbakeracross a project, i think this gets more complicated, because we implicitly (!) been assuming that project could be used for partitioning15:39
jimbaker(from a sharded perspective, or direct customer placement)15:39
*** ntpttr_ has joined #openstack-meeting-415:39
jimbakerthomasem, my feeling is that we punt for now15:40
thomasemMine, too.15:40
thomasemsulo, sigmavirus?15:40
sigmavirusYeah, like I said, no need to fix this now15:40
jimbakerlet's look at the standard answer for distributed file systems. we actually copy/delete when we say "move"15:40
thomasemCool, so we'll discuss this again when it comes up as a use-case we wish to support?15:41
jimbakeragreed15:41
thomasemExcellent. Anything else folks wish to talk about>?15:41
jimbakerand again we can support this at least 2 ways15:41
thomasemYeah15:42
jimbaker(i think the copy/delete paradigm works best... even if this means IDs are remapped. which is a good thing for multisource)15:42
thomasemAnd it means we need to do nothing to support it. :P15:42
jimbakeryes :)15:42
jimbakerbulk export out of a project; bulk import into a new project; done15:43
thomasemIf there's nothing else, we can get a whole 17 minutes of our lives back.15:43
thomasem:D15:43
thomasemjimbaker: yep!15:43
thomasemAlrightyo, closing in..15:43
thomasem3...15:44
thomasem2...15:44
thomasem1...15:44
thomasem#endmeeting15:44
*** openstack changes topic to " (Meeting topic: ironic_neutron)"15:44
openstackMeeting ended Mon Mar 20 15:44:08 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-03-20-14.59.html15:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-03-20-14.59.txt15:44
jimbakerthanks!15:44
openstackLog:            http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-03-20-14.59.log.html15:44
thomasemCheers!15:44
*** thomasem has left #openstack-meeting-415:44
*** matrohon has quit IRC15:46
*** matrohon has joined #openstack-meeting-415:50
*** gongysh has quit IRC15:50
*** links has joined #openstack-meeting-415:51
*** psachin has quit IRC15:51
*** links has quit IRC15:55
*** links has joined #openstack-meeting-415:56
*** bobmel has quit IRC15:58
*** kaifeng has joined #openstack-meeting-415:59
*** Syed__ has joined #openstack-meeting-416:02
*** vks1 has quit IRC16:05
*** armax has quit IRC16:05
*** links has quit IRC16:05
*** liangy has quit IRC16:08
*** Sukhdev has quit IRC16:16
*** Sukhdev_ has joined #openstack-meeting-416:16
*** tojuvone has left #openstack-meeting-416:17
*** uck has joined #openstack-meeting-416:18
*** julim_ has joined #openstack-meeting-416:26
*** nkrinner is now known as nkrinner_afk16:27
*** pcaruana has quit IRC16:27
*** julim has quit IRC16:28
*** chigang has quit IRC16:29
*** Sukhdev has joined #openstack-meeting-416:29
*** yamahata has quit IRC16:31
*** iyamahat has quit IRC16:33
*** uck has quit IRC16:38
*** uck has joined #openstack-meeting-416:38
*** Julien-zte has quit IRC16:48
*** bobmel has joined #openstack-meeting-416:51
*** hoangcx has joined #openstack-meeting-416:52
*** oshidoshi has quit IRC16:53
*** bobmel_ has joined #openstack-meeting-416:55
*** bobmel has quit IRC16:56
*** iyamahat has joined #openstack-meeting-416:59
tinwoodo/ charmers16:59
*** liangy has joined #openstack-meeting-416:59
*** unicell1 has quit IRC17:00
iceyo/ tinwood17:00
*** freyes has joined #openstack-meeting-417:00
tinwood\o17:00
*** Sukhdev has quit IRC17:01
*** Sukhdev_ is now known as Sukhdev17:01
coreycbo/17:01
*** liangy has quit IRC17:01
tinwoodhave we got some people for a meeting?17:01
tinwoodokay, kicking off ...17:02
*** kzaitsev_ws has quit IRC17:02
tinwood#startmeeting charms17:02
openstackMeeting started Mon Mar 20 17:02:17 2017 UTC and is due to finish in 60 minutes.  The chair is tinwood. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: charms)"17:02
openstackThe meeting name has been set to 'charms'17:02
tinwoodHello all.  Welcome to the openstack charms meeting.17:02
tinwoodroll call, so I know who's here :)17:02
*** sparkiegeek has joined #openstack-meeting-417:03
tinwoodhello?17:03
*** anonymike has left #openstack-meeting-417:03
iceyHi :)17:03
beisnero/17:03
* sparkiegeek waves17:03
tinwoodOkay, lets get started.17:03
tinwood#topic Review ACTION points from previous meeting17:04
*** openstack changes topic to "Review ACTION points from previous meeting (Meeting topic: charms)"17:04
jamespageo/17:04
coreycbo/17:04
tinwoodThe only one we have is: ACTION: jamespage Draft initial proposal for service discovery17:04
tinwoodo/ jamespage17:04
jamespagedone17:04
tinwoodexcellent!17:05
jamespagehmm - but I think I need to write that up as a spec still17:05
tinwoodIs there a link?17:05
*** cholcombe has joined #openstack-meeting-417:05
jamespagehttps://etherpad.openstack.org/p/charms-service-discovery17:05
cholcombeo/17:05
tinwoodta17:05
tinwoodOkay, next topic:17:06
tinwood#topic State of Development for next Charm Release17:06
*** openstack changes topic to "State of Development for next Charm Release (Meeting topic: charms)"17:06
tinwoodwe're early in the cycle.17:06
tinwoodI'm still switching on some of the tests for automated testing.17:07
tinwoodAnyone want to comment on this?17:07
tinwood(topic)17:07
* beisner thanks tinwood and thedac ;-)17:07
beisneri have a question on this topic17:07
beisnerpike is next17:07
beisneri'd like to see us have a definitive checkpoint where we aim to have preliminary bits landed and sync'd in ahead of charm freeze.17:08
tinwooddo you mean like the bits I'm doing now?17:08
beisnerre: c-h version tables, c-h amulet helpers, amulet test definitions, etc.17:08
beisneryes17:08
tinwoodIs there a reason we do them afterwards?  (e.g. they're not going to work beforehand)17:09
beisnerit doesn't have to be / shouldn't be flipped on as gating at that checkpoint, but we should have all of the series/codename bits flipped and landed so people can do a `func27-dev` and get those to run.17:09
beisnertinwood, no reason other than 'its hard'(tm) when upstream bits are still flying in the days/weeks leading up to it.17:10
tinwoodthat's a good reason :)17:10
*** anilvenkata has quit IRC17:10
* sparkiegeek hands beisner a ™17:10
beisnerit is a bit chicken/egg.  in order for us to know where we stand, we need to have a certain baseline of things landed to make the mechanics of testing work.17:10
beisnerwithout that, we can't even deploy the next thing™17:11
*** Swami has quit IRC17:11
tinwoodokay, beisner would you like an action to suggest a process that might work?  i.e. what sort of timeatable would work, etc.17:11
beisnerso i'd like to be able to deploy the next thing™ earlier this, and every cycle.,17:11
beisnereven if it's not known-good.17:11
* beisner thanks sparkiegeek too17:11
jamespagebeisner: so like enabling xenial-pike now rather than later?17:11
beisnertinwood, curious if there are thoughts already on this among those in the room17:11
beisnerjamespage, exactly.17:12
jamespagebeisner: but as part of dev first rather than gate17:12
beisneror at some pre-determined checkpoint, such as R-N17:12
beisnerjamespage, exactly x 217:12
coreycbnot amulet related, but we do have a to-do to enable CI from master branch PPAs for pike17:12
tinwoodcould they be non-voting?17:12
beisnercoreycb, this is a prereq for that.17:12
tinwoodi.e. run automatically.17:12
icey+1 for non voting early CI17:12
jamespagebeisner: its a shame we can't split up our full amulet run to report back individual results for each check/gate17:12
jamespagethen we could have a non-voting check on the development release stuff early in cycle17:13
beisnerjamespage, we can and we plan to.  ie. define each test in the project-config bits, rather than wildcard them in tox.17:13
jamespageawesome17:13
jamespageso dev vs gate is the current method for that right?17:13
beisneryep17:13
beisnerdev-*17:13
jamespageok17:13
jamespage+117:13
beisnera'ight thanks y'all17:14
tinwoodsounds good +117:14
tinwoodso, any action out of that?17:14
jamespagebtw I did write the spec17:14
jamespagehttp://specs.openstack.org/openstack/charm-specs/specs/pike/approved/service-discovery.html17:14
*** matrohon has quit IRC17:14
jamespagerrd-brain17:14
beisnertinwood, action would be to do what thedac's batch is doing now for ocata, but for pike immediately after.17:14
coreycbbeisner, not following the pre-req bit but i don't know if it's important17:14
beisnercoreycb, in order to test pike deploys from master pkg builds, the charms have to be pike-aware.17:15
tinwoodthis feels bigger than a simple action. maybe we could open a bug to track it?17:15
coreycbbeisner, right but not necessarily amulet pike aware, although that would be nice17:15
* sparkiegeek 's eyes twitch at "alot" in service-discover spec17:16
beisnercoreycb, correct, the two are not technically coupled.  but it makes sense to enable the dev-* amulets in the same batch, as there is no expectation that they pass or be gating.17:16
beisnertinwood, this is really a routine issue, which we need to formulate and just-do each cycle.,17:17
beisnerand my trailing commas are due to a bandaid on my finger btw ;-)17:17
tinwoodbeisner, I agree, but the initial work needs to be tracked somewhere, wouldn't you agree (i.e. to make sure it happens!)17:17
coreycbbeisner, that's true if we want to enable pike tests early in the cycle but i didn't think that was the plan17:17
*** yamahata has joined #openstack-meeting-417:17
beisnertinwood, yep, wherever we track the "open the next version for development" list-o-stuff ™ to do.17:17
tinwoodokay, then I will leave it with you :) Any thing more on this topic before we move on?17:18
beisnercoreycb, depends on who's driving the batches.  if i'm driving, i'm flipping the bits in one pass vs two or three.17:18
coreycbbeisner, my point is that we want to do CI on a daily basis for pike starting soonish.  but will amulet tests be part of that for pike?17:19
beisnertinwood, but i'm not convinced we have such a list-o-stuff list, so let's add an action to document the dev-cycle-opening task list?17:19
beisnercoreycb, fear not.  the CI daily won't be dependent on the amulet dev actually passing.  it'll be a blind bitflip so that people "can" exercise it.  whereas right now they "cannot."17:20
tinwood#action beisner list-o-stuff™ concerning/documenting the dev-cycle-opening task list.17:20
beisnerthen, at freeze or before it, hopefully pike has stabilized enough, and there is someone ready and available to go make sure they pass.17:20
coreycbbeisner, cool, i'd be +1 for non-voting pike enablement of amulet tests17:20
* tinwood hopes the ™ didn't break the action bot17:20
beisner:-)17:20
tinwoodOkay, next up:17:21
beisnerthanks guys and gals17:21
tinwood#topic Discussion: service discovery vs modeling17:21
*** openstack changes topic to "Discussion: service discovery vs modeling (Meeting topic: charms)"17:21
tinwoodjamespage, the floor ...17:21
jamespageoh that's an old item - we already talked bout that17:21
jamespageoutcome was:17:21
jamespagehttp://specs.openstack.org/openstack/charm-specs/specs/pike/approved/service-discovery.html17:21
*** isq has joined #openstack-meeting-417:21
tinwoodokay, wasn't sure whether it was a post spec discussion.  All is good :)17:22
tinwoodthanks17:22
jamespagecrufty agenda methings17:22
tinwood#topic High Priority Bugs17:22
*** openstack changes topic to "High Priority Bugs (Meeting topic: charms)"17:22
tinwoodOpenStack bugs at: https://bugs.launchpad.net/openstack-charms17:22
tinwoodcritical/high = 69 bugs17:23
jamespageits about 15% of total bugs17:24
jamespage(453)17:24
jamespagegosh did that in my head17:24
tinwood10 reported in the last year that are still open.17:24
sparkiegeekin the last year = > 365 days old, or reported in 2016 ?17:25
jamespageI think its worth everyone using their bug time to focus in on those bugs17:25
tinwood(actually it may be more than that, due to sorting not working!)17:25
jamespageit may be they are not classified correctly; or that they do need fixing17:25
*** liangy has joined #openstack-meeting-417:25
jamespageI'd encourage folk to leave 4hrs or so a week to bug triage17:26
tinwoodwe have regular bug squash days.17:26
tinwoodjamespage, can I triage yet?17:26
jamespagewe have the monthly bug squash days as well17:26
jamespagetinwood: you should be able to17:26
tinwoodokay, I will check17:26
jamespagetinwood: yes you're in the right team17:26
tinwoodany bugs we want to discuss before moving on.  (we have 3 minutes)17:27
jamespagenope17:27
jamespageoh actually17:27
jamespageI wanted to mention17:27
jamespagehttps://docs.openstack.org/developer/charm-guide/1702.html#ceph-based-cinder-storage-backends17:27
*** unicell has joined #openstack-meeting-417:27
jamespagethat was resolved as a post 17.02 stable update17:27
* jamespage looks at sparkiegeek17:28
*** vishnoianil has quit IRC17:28
jamespageI did raise this to dpb last week - just want to make sure one of our downstream projects is aware of that requirement for ocata17:28
sparkiegeekjamespage: noted, thanks17:28
jamespageyw17:28
tinwood#topic Openstack Events17:28
*** openstack changes topic to "Openstack Events (Meeting topic: charms)"17:28
tinwoodany comments on this?17:29
tinwoodif not:17:29
tinwood#topic Open Discussion17:29
*** openstack changes topic to "Open Discussion (Meeting topic: charms)"17:29
tinwoodfloors anybody's17:29
iceytime to clear the floor?17:30
sparkiegeekdid my suggestion of updating/composing release notes as we go get anywhere?17:30
tinwoodis that relnote or similar?17:30
tinwoodbecause something got mentioned at the ptg17:31
jamespagesparkiegeek: the reno stuf?17:31
jamespagesparkiegeek: that's the intent but I think we're lacking an assignee atm17:31
sparkiegeekjamespage: tinwood: ... maybe?17:31
* tinwood thanks sparkiegeek 17:31
tinwoodyes, I'll take a look.17:31
sparkiegeekI didn't read notes from PTG (are they up somewhere?)17:31
jamespagechanges would land with the associated releasenote and we then generate them all17:31
tinwood#action tinwood to look at reno17:32
jamespagesparkiegeek: https://etherpad.openstack.org/p/openstack-charms-ptg-pike17:32
sparkiegeekjamespage: thankns17:32
tinwoodanything else?17:32
tinwoodokay, thanks everybody.17:33
tinwood#endmeeting17:33
*** openstack changes topic to " (Meeting topic: ironic_neutron)"17:33
openstackMeeting ended Mon Mar 20 17:33:25 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-03-20-17.02.html17:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-03-20-17.02.txt17:33
openstackLog:            http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-03-20-17.02.log.html17:33
coreycb thanks tinwood17:34
sparkiegeekthanks tinwood17:34
* sparkiegeek notes ™ survived logging17:34
jamespagethanks tinwood17:34
tinwood:)17:35
*** sparkiegeek has left #openstack-meeting-417:36
*** lazyPwr is now known as lazyPower17:37
*** lazyPower has quit IRC17:38
*** lazyPower has joined #openstack-meeting-417:38
*** baoli has quit IRC17:40
*** baoli has joined #openstack-meeting-417:42
*** baoli has quit IRC17:42
*** baoli has joined #openstack-meeting-417:46
*** neiljerram has quit IRC17:47
*** hoangcx has quit IRC17:51
*** hoangcx has joined #openstack-meeting-418:02
*** ralonsoh has quit IRC18:02
*** aarefiev is now known as aarefiev_pto18:06
*** salmankhan has quit IRC18:10
*** baoli has quit IRC18:10
*** baoli has joined #openstack-meeting-418:11
*** joedborg has quit IRC18:14
*** baoli has quit IRC18:16
*** vishnoianil has joined #openstack-meeting-418:17
*** armax has joined #openstack-meeting-418:18
*** sneti_ has joined #openstack-meeting-418:25
*** bogdando has quit IRC18:26
*** dharinic is now known as dharinic|lunch18:26
*** baoli has joined #openstack-meeting-418:28
*** kaifeng has quit IRC18:31
*** bobmel_ has quit IRC18:31
*** sneti_ has quit IRC18:32
*** baoli has quit IRC18:32
*** baoli has joined #openstack-meeting-418:38
*** freyes has left #openstack-meeting-418:42
*** uck has quit IRC18:42
*** uck has joined #openstack-meeting-418:42
*** baoli has quit IRC18:44
*** anonymike has joined #openstack-meeting-418:50
*** david-lyle_ has joined #openstack-meeting-418:52
*** david-lyle has quit IRC18:52
*** david-lyle_ is now known as david-lyle18:53
*** armax has quit IRC19:01
*** baoli has joined #openstack-meeting-419:07
*** sneti_ has joined #openstack-meeting-419:12
*** dharinic|lunch is now known as dharinic19:13
*** baoli has quit IRC19:14
*** Swami has joined #openstack-meeting-419:16
*** baoli has joined #openstack-meeting-419:25
*** salmankhan has joined #openstack-meeting-419:37
*** salmankhan has quit IRC19:41
*** krtaylor has quit IRC19:43
*** cathrichardson has joined #openstack-meeting-419:46
*** cathrich_ has joined #openstack-meeting-419:48
*** uck has quit IRC19:48
*** uck has joined #openstack-meeting-419:49
*** cathrichardson has quit IRC19:51
*** rockyg has joined #openstack-meeting-419:53
*** hemanthm is now known as hemanthm|afk19:55
*** cathrich_ has quit IRC19:55
*** cathrichardson has joined #openstack-meeting-419:56
*** baoli has quit IRC20:01
*** baoli has joined #openstack-meeting-420:01
*** baoli has quit IRC20:02
*** rockyg has quit IRC20:06
*** rockyg has joined #openstack-meeting-420:06
*** cathrichardson has left #openstack-meeting-420:11
*** baoli has joined #openstack-meeting-420:12
*** julim_ has quit IRC20:12
*** matrohon has joined #openstack-meeting-420:12
*** dave-mcc_ has joined #openstack-meeting-420:15
*** abramley_ has joined #openstack-meeting-420:15
*** anonymike_ has joined #openstack-meeting-420:16
*** pbourke_ has joined #openstack-meeting-420:16
*** Sukhdev_ has joined #openstack-meeting-420:17
*** anonymike has quit IRC20:18
*** anonymike_ is now known as anonymike20:18
*** hemanthm1afk has joined #openstack-meeting-420:19
*** makowals_ has joined #openstack-meeting-420:20
*** vsaienk01 has joined #openstack-meeting-420:20
*** rosmaita_ has joined #openstack-meeting-420:20
*** tinwood_ has joined #openstack-meeting-420:21
*** krtaylor has joined #openstack-meeting-420:21
*** palendae_ has joined #openstack-meeting-420:22
*** jmccrory_ has joined #openstack-meeting-420:22
*** irenab_ has joined #openstack-meeting-420:22
*** palendae_ is now known as palebndae20:23
*** baoli has quit IRC20:23
*** sdake_ has joined #openstack-meeting-420:24
*** sdake_ has quit IRC20:24
*** sdake_ has joined #openstack-meeting-420:24
*** Sukhdev__ has joined #openstack-meeting-420:25
*** armax has joined #openstack-meeting-420:26
*** lkoranda_ has joined #openstack-meeting-420:27
*** Sukhdev has quit IRC20:29
*** dave-mccowan has quit IRC20:29
*** pbourke has quit IRC20:29
*** makowals has quit IRC20:29
*** irenab has quit IRC20:29
*** tinwood has quit IRC20:29
*** sdague has quit IRC20:29
*** shasha_t_ has quit IRC20:29
*** vsaienk0 has quit IRC20:29
*** sdake has quit IRC20:29
*** jmccrory has quit IRC20:29
*** palendae has quit IRC20:29
*** hemanthm|afk has quit IRC20:29
*** abramley has quit IRC20:29
*** lkoranda has quit IRC20:29
*** rosmaita has quit IRC20:29
*** lkoranda_ is now known as lkoranda20:29
*** irenab_ is now known as irenab20:29
*** jmccrory_ is now known as jmccrory20:29
*** abramley_ is now known as abramley20:29
*** Sukhdev__ is now known as Sukhdev20:29
*** palebndae is now known as palendae_20:29
*** dave-mcc_ is now known as dave-mccowan20:33
*** sdague has joined #openstack-meeting-420:36
*** sdague has quit IRC20:37
*** baoli has joined #openstack-meeting-420:37
*** sdague has joined #openstack-meeting-420:45
*** unicell1 has joined #openstack-meeting-420:51
*** sdague has quit IRC20:51
*** cleong has quit IRC20:51
*** sdague__ has joined #openstack-meeting-420:52
*** unicell has quit IRC20:52
*** uck has quit IRC20:56
*** s3wong has joined #openstack-meeting-420:57
*** woodard has quit IRC21:00
*** woodard has joined #openstack-meeting-421:00
*** uck has joined #openstack-meeting-421:03
*** woodard has quit IRC21:03
*** baoli has quit IRC21:09
*** Swami has quit IRC21:09
*** baoli has joined #openstack-meeting-421:11
*** baoli has quit IRC21:11
*** baoli has joined #openstack-meeting-421:11
*** s3wong has quit IRC21:13
*** s3wong has joined #openstack-meeting-421:14
*** amotoki has joined #openstack-meeting-421:23
*** baoli has quit IRC21:24
*** cholcombe has left #openstack-meeting-421:28
*** FrankZhang has quit IRC21:31
*** baoli has joined #openstack-meeting-421:32
*** baoli has quit IRC21:33
*** s3wong_ has joined #openstack-meeting-421:33
*** Jeffrey4l_ has quit IRC21:35
*** s3wong has quit IRC21:35
*** Jeffrey4l_ has joined #openstack-meeting-421:38
*** matrohon has quit IRC21:49
*** rwallner has quit IRC21:56
*** kylek3h has quit IRC21:58
*** haleyb has quit IRC22:01
*** baoli has joined #openstack-meeting-422:01
*** baoli has quit IRC22:06
*** sdake_ is now known as sdake22:07
*** bobh has quit IRC22:10
*** rfolco has quit IRC22:10
*** dave-mccowan has quit IRC22:12
*** salmankhan has joined #openstack-meeting-422:22
*** rockyg has quit IRC22:22
*** galstrom is now known as galstrom_zzz22:24
*** neiljerram has joined #openstack-meeting-422:30
*** amotoki has quit IRC22:41
*** krtaylor has quit IRC22:45
*** marst has quit IRC22:58
*** s3wong__ has joined #openstack-meeting-423:01
*** s3wong_ has quit IRC23:01
*** rwallner has joined #openstack-meeting-423:03
*** rwallner has quit IRC23:08
*** marst has joined #openstack-meeting-423:10
*** s3wong__ has quit IRC23:10
*** s3wong has joined #openstack-meeting-423:12
*** sneti_ has quit IRC23:17
*** s3wong has quit IRC23:21
*** s3wong has joined #openstack-meeting-423:23
*** hoangcx has quit IRC23:25
*** Sukhdev has quit IRC23:26
*** s3wong has quit IRC23:34
*** s3wong has joined #openstack-meeting-423:35
*** uck_ has joined #openstack-meeting-423:36
*** uck has quit IRC23:36
*** dave-mccowan has joined #openstack-meeting-423:43
*** gongysh has joined #openstack-meeting-423:55
*** liangy has quit IRC23:55
*** salmankhan has quit IRC23:56

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