Monday, 2017-07-10

*** thorst has joined #openstack-meeting-400:02
*** thorst has quit IRC00:08
*** woodard has joined #openstack-meeting-400:09
*** gmann has quit IRC00:11
*** gmann has joined #openstack-meeting-400:11
*** limao has joined #openstack-meeting-400:33
*** thorst has joined #openstack-meeting-400:36
*** thorst has quit IRC00:36
*** yujunz_ has joined #openstack-meeting-400:37
*** yujunz_ has quit IRC00:39
*** yujunz_ has joined #openstack-meeting-400:41
*** yujunz_ is now known as yujunz-zte00:42
*** yifei has joined #openstack-meeting-400:46
*** zhurong has joined #openstack-meeting-400:47
*** lei-zh has joined #openstack-meeting-400:55
*** dixiaoli has joined #openstack-meeting-401:04
*** julim has joined #openstack-meeting-401:27
*** galstrom_zzz is now known as galstrom01:28
*** dave-mccowan has joined #openstack-meeting-401:33
*** hongbin has joined #openstack-meeting-401:36
*** thorst has joined #openstack-meeting-401:52
*** galstrom is now known as galstrom_zzz01:54
*** thorst has quit IRC01:56
*** bobh has joined #openstack-meeting-402:10
*** kevzha01 has joined #openstack-meeting-402:10
*** kevzha01 is now known as kevinz02:15
*** julim has quit IRC02:17
*** baoli has joined #openstack-meeting-402:21
*** baoli has quit IRC02:28
*** julim has joined #openstack-meeting-402:29
*** limao has quit IRC02:33
*** julim has quit IRC02:34
*** limao has joined #openstack-meeting-402:34
*** limao_ has joined #openstack-meeting-402:35
*** limao has quit IRC02:38
*** zhurong has quit IRC02:43
*** woodard has quit IRC02:43
*** woodard has joined #openstack-meeting-402:44
*** woodard has quit IRC02:48
*** limao_ has quit IRC02:57
*** limao has joined #openstack-meeting-402:57
*** limao has quit IRC03:02
*** bobh has quit IRC03:13
*** reedip has quit IRC03:13
*** bobh has joined #openstack-meeting-403:17
*** bobh has quit IRC03:21
*** reedip has joined #openstack-meeting-403:25
*** yamamoto has joined #openstack-meeting-403:47
*** slaweq has joined #openstack-meeting-403:47
*** slaweq has quit IRC03:52
*** thorst has joined #openstack-meeting-403:53
*** psachin has joined #openstack-meeting-403:56
*** thorst has quit IRC03:57
*** hongbin has quit IRC03:58
*** julim has joined #openstack-meeting-403:59
*** woodard has joined #openstack-meeting-404:00
*** dave-mccowan has quit IRC04:05
*** adisky__ has joined #openstack-meeting-404:07
*** bobh has joined #openstack-meeting-404:17
*** zhurong has joined #openstack-meeting-404:46
*** trinaths has joined #openstack-meeting-404:48
*** trinaths has quit IRC05:04
*** trinaths has joined #openstack-meeting-405:08
*** janki has joined #openstack-meeting-405:08
*** aavraham has joined #openstack-meeting-405:14
*** unicell has quit IRC05:23
*** unicell has joined #openstack-meeting-405:23
*** yujunz-zte has quit IRC05:36
*** thorst has joined #openstack-meeting-405:54
*** thorst has quit IRC05:59
*** kzaitsev_ws has joined #openstack-meeting-406:17
*** dixiaoli has quit IRC06:18
*** dixiaoli has joined #openstack-meeting-406:18
*** vds has joined #openstack-meeting-406:22
*** alexchadin has joined #openstack-meeting-406:27
*** janki has quit IRC06:38
*** coolsvap has joined #openstack-meeting-406:47
*** belmoreira has joined #openstack-meeting-406:54
*** lei-zh has quit IRC07:06
*** lei-zh has joined #openstack-meeting-407:07
*** amotoki_away is now known as amotoki07:11
*** harlowja has quit IRC07:11
*** bogdando has joined #openstack-meeting-407:23
*** yujunz-zte has joined #openstack-meeting-407:25
*** egonzalez has joined #openstack-meeting-407:38
*** kkxue has joined #openstack-meeting-407:39
*** dixiaoli has quit IRC07:45
*** dixiaoli has joined #openstack-meeting-407:46
*** sambetts is now known as sambetts|afk07:47
*** thorst has joined #openstack-meeting-407:54
*** sambetts|afk is now known as sambetts07:57
*** thorst has quit IRC08:00
*** kkxue has quit IRC08:13
*** kural has quit IRC08:13
*** kkxue has joined #openstack-meeting-408:13
*** kkxue has quit IRC08:16
*** kkxue has joined #openstack-meeting-408:16
*** hieulq has quit IRC08:39
*** ralonsoh has joined #openstack-meeting-408:51
*** anilvenkata has joined #openstack-meeting-408:51
oanson#startmeeting Dragonflow09:00
openstackMeeting started Mon Jul 10 09:00:33 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
dimakHey09:00
leyalHi09:00
lihiHi09:00
oansonHello. Who is here for the Dragonflow weekly?09:00
oansonLet's wait another minute, and then we'll start.09:01
* yamamoto peeping09:01
oansonAll right. Let's start.09:01
oanson#info dimak leyal lihi in meeting09:01
oanson#info yamamoto peeping :)09:01
oansonFirst, some announcements:09:02
oansonI changed the teimslot for the Dragonflow weekly.09:02
itamaroין09:02
oanson#link Meeting time change https://review.openstack.org/#/c/482034/09:02
oanson#info itamaro also in meeting09:02
itamarohi09:02
dimakIt was already merged?09:03
oansonYes09:03
dimakNo time to appeal :P09:03
dimak?09:03
irenabhi09:03
oansonThis means that next week we start an hour earlier, and the week after we meet at 1900 UTC09:03
oansondimak, the time was voted on last week and was accepted, but we can always submit a second patch09:03
oansonThierry just didn't waste any time :)09:04
oanson#info irenab also in meeting09:04
oanson(Hi)09:04
*** yujunz-zte has left #openstack-meeting-409:04
oansonIt is also possible I got it wrong, and next week we start in the evening, and the week after we move an hour earlier :)09:04
oansonI guess the wiki will be updated soon, and I'll verify09:05
irenaboanson, maybe worth to add on the DF wiki the date and time for few following weeks09:05
oansonSure09:05
oansonI'll also send an email to the mailing list09:05
oansonAnything else for announcements?09:06
oanson#topic Roadmap09:07
*** openstack changes topic to "Roadmap (Meeting topic: Dragonflow)"09:07
oansonSo, SFC09:07
oansondimak, any comments?09:08
dimakI'll upload a newer version soon with more tests, there are some python3 issues I found09:08
dimakbut I its nothing major09:08
oansonAll right. ping lihi and me once you do, and we'll push it in. I think it's in a fairly advanced state09:08
oansonLBaaS - sadly no progress :(09:09
dimakoanson, alright, will do09:09
oansonThanks.09:09
oansonL3 flavour - dimak, you're up again.09:09
dimakI didn't get to revise the spec yet09:09
oansonSure09:10
oansonetcd publisher - lihi?09:10
lihiI have some issues with python-etcd. I'm missing some an important feature from etcd's regular API09:10
lihiI'm testing if we can use pyton-etcd3 instead09:11
oansonrequirements project has an etcd3 package already in - is this what you're testing?09:11
lihiNo, I want to replace our driver to use etcd3 package instead of etcd09:12
oanson#link etcd3 https://python-etcd3.readthedocs.io/en/latest/09:12
oansonThe question is - are you using something already in requirements (like the link I just posted)09:13
lihiI'm sorry I don't understand your question09:14
oansonThe requirements project unifies all the python requirements used in openstack. They do that for  licensing issues and to make sure no stale packages are used09:14
*** hieulq has joined #openstack-meeting-409:15
oanson#link Requirements Project https://github.com/openstack/requirements09:15
lihiI'm trying to get our DB driver to work with the package, and then build our subscriber on top of it09:15
oansonI see. And you are using the etcd3 python library, from here: https://python-etcd3.readthedocs.io/en/latest/ ?09:15
lihiOh09:15
lihiYes this is the one09:15
oansonAll right. Just wanted to make sure :)09:16
oansonDo you have an ETA?09:16
oansonlihi, ?09:18
lihiAiming for this week (even though this is was I say last week :|)09:18
oansonIt's all right. It's not a hard limit :)09:18
oansonRPM packaging - I started looking into this. I hope to have a patch up by end of week09:19
dimakCool09:19
oansonSkydive has no carrier - so I'll skip it unless someone volunteers?09:19
oansonAnd Ironic support - leyal ?09:19
dimakoanson, I want to get to it eventually09:20
irenaboanson, can you please post the link to the roadmap items list?09:20
leyalI started to read about09:20
oansondimak, doesn't look like anyone is rushing to it, so... :)09:20
leyalIronic09:20
oansonirenab, agenda is here: https://wiki.openstack.org/wiki/Meetings/Dragonflow09:20
oanson#link Agenda https://wiki.openstack.org/wiki/Meetings/Dragonflow09:20
irenabthanks09:20
oansonleyal, yes09:20
leyalIt's looks that it's HAd 2 modes : 1. flat-networks09:21
leyal2. sperated the tenant networks from the provisioning networks09:21
oansonWhat do you mean by 2.?09:22
oansonAnd what about virtual services, e.g. dhcp, metadata, NATs? Do they mention that?09:22
*** thorst has joined #openstack-meeting-409:23
leyalIt's the second mode - use one network for provision (boot - DHCP - TFTP etc .. )09:23
irenableyal, maybe it will be helpful if you can provide some draft for the Ironic support09:24
leyalAnd other network for regular usage after  vm boot from disk ..09:24
leyali didn't saw that they mention anything about virtual-services..09:25
oansonI see09:25
oansonI think irenab has the right idea. Writing up a draft would be all right?09:25
kkxue+109:25
oansonleyal, ?09:26
leyalwriting draft about what?09:26
oansonAbout ironic, and its integration with Dragonflow09:26
oansonIt doesn't have to be a spec. A whitepaper or blog post can also do09:27
leyal+1 , but i think that i need to get better understanding of Ironic before that ...09:27
oansonOf course.09:27
oansonThe idea is to synthesize the information that is relevant for the cross-project synergy, and put it somewhere where it's accessible09:28
*** thorst has quit IRC09:28
oansonAnything else for roadmap?09:29
leyalsure , will do when i will be prepared ..09:30
irenaboanson, the spec itamaro posted09:30
oanson1 sec. Let me find it09:30
oansonYou mean this one? https://review.openstack.org/#/c/481887/09:31
dimakPosted some comments ther09:31
dimake09:31
oansondimak, I see your main concern is snat09:32
itamaro yes. In my opinion it is best to have a patch identified by the connecting briges for simplicity.09:32
dimaksnat and provider are the primary users of patches09:32
itamarosnat issues can be managed by providing higher priority09:33
dimakThen we have coupling09:33
itamaroeg SNAT_CLASS_PRIO = 30009:33
oansonIn general the snat API is lacking. It is configuration based, not in line with Neutron networks, and doesn't have a logical port on which other applications can operate if needed09:33
oanson(which in theory breaks the API and General Order of Things we are constructing)09:34
oansonLike dnat relies on provider networks, maybe make snat do the same09:34
oansonGive snat a port (e.g. like a fip, but for snat not dnat), and let it do its thing from there09:35
itamaroI think that ant connectivity with the physical underlay must go through  provider networks09:35
dimakWho will allocate those ports?09:35
oansonprovider networks - they will be responsible for the mapping of network to bridge. Any other apps just sends packets to networks09:35
oansonIn case of snat and dnat, also natting the packets in the process.09:36
itamaroyes09:36
oansonAnd then only provider networks need to handle patch ports. In general, we only need a library for software engineering reasons. provider app should be the only user09:36
dimakoanson, my question still stands09:36
oansonLet me think a second09:37
oanson(Or someone else suggest something (: )09:37
*** karthiks has joined #openstack-meeting-409:38
dimakSome one needs to allocate ports for 'snat' ports and delete them when hosts die09:38
oansonAs step 1 - we can do the quick and dirty fix of giving snat higher priority. As step 2 - we give snat a specialised fip or fip network09:38
irenabI need to catch up on the spec. Can we have a discussion later09:38
dimakOr don't have any ports on chassis09:38
dimakI think its more relevant to snat rather than patch ports09:38
itamaro if I understand your concern. it is that snap flows may no be considered because of higher prio match.09:39
oansonirenab, it's not a long spec. Basically it says, let's have an external library for patch ports. Have a single patch-port-pair between br-int and any external bridge. And let provider networks app manage the patch ports. itamaro, dimak, did I miss anything?09:39
dimakYes09:39
itamarocorrect09:39
dimakI'm just not sure what problem we try to solve if snat works differently09:39
irenaboanson, this sounds reasonable approach09:40
oansondimak, one example is an API. If the api is configuration file, you need to restart the controller to change configuration.09:41
oansonSecondly, we *have* issues of multiple patch ports and multiple apps trying to reach networks (the dnat problem). I'm hoping this will solve that as well09:41
itamarosnat can be solved by having it's own priorities in the global constants  prefixed with SNAT_PRIO, and keep them higher than the higest prio09:41
dimakOk, but bridge mapping to physical network is configuration anyway09:41
*** lei-zh has quit IRC09:41
oansonYes09:42
oansonBut snat -> physical network doesn't have to be09:42
dimakitamaro, I don't like this solution, because it creates overlap in table=0 for both apps, I'd very much like to avoid that09:43
itamaroit's logical mapping. we shall map the mapped (physical: flat/valn) networks names to the patch port09:43
oansonThe rationale is that if you change the network <-> bridge mapping, there's a hardware change involved. Otherwise, everything is software defined.09:43
oansondimak, in the second phase, only provider app will have a mapping in table=0. snat (like dnat) will take the packet from provider.09:43
oansonitamaro, please confirm09:44
dimakoanson, what if I want to NAT to another network?09:44
itamaroyes, that should be the plan.09:44
dimakCurrent implementation does not restrict you to neutron networks09:44
oansondimak, then the snat app should be extended. If snat is already network based, it should be easy.09:44
oansondimak, that's not a good thing09:44
itamaroyou will have a mapping  like <name>:bridge09:44
oanson(I think it isn't, at least)09:45
itamaroname is network name09:45
dimakoanson, I can argue otherwise09:45
dimakIts an extra flexibility we allow at the moment09:45
oansonYes, extra flexibility means more complex api.09:45
itamarothe bridge must be handelded by the providers networks app, which prodes the access to the physical infra09:46
oansonCurrently, there is no way to control it except going to the node, changing the configuration, and restarting the service09:46
dimakAt the moment its zero API, egress through the address your host got from the DHCP09:46
oansonIf you want an API, which can be validated and verified, you need to lay down some ground rules. This also helps the applications "play nice" with each other - there is a limit to what they are allowed to do09:46
irenabI think we are mixing the api (usability) part with the implementation part09:46
dimakBut same for mapping, I see it on the same level09:46
oansonyes, definitely09:47
irenabmaybe worth to keep discussion on implementation first?09:47
oansonAs I said, the mapping assumes a physical backend. That's why I want things to be network based, not bridge based.09:47
irenaboanson, phy network?09:48
oansonirenab, I thought that's what we're doing?09:48
irenaboanson, just seemed to me 2 parallel discussions, sorry09:48
oansonirenab, yes. But that still goes through mapping, which is handled by provider network and hidden for everything else09:48
oansonI would be happiest with a solution that let's us phase into it, without breaking too much on the way, and allows us to get things working09:49
dimakWe can have a provider network based SNAT, and it won't need extra patches. But that's not what chassis SNAT does at the moment.09:49
*** rwallner has quit IRC09:49
itamarodimak is right that apps need to play nice with each other09:50
dimakWe can decide that we drop it but that's something else09:50
irenabdrop what?09:50
oansondimak, sure. That's a good way to do it09:50
dimakchassis snat in favor of neutron managed snat09:50
dimakmanages as in IPAM and port creation and deletion09:51
oansonSure09:51
oansonBut if chassis snat works ad-hoc, it's going to be difficult to get it to play nice with other apps09:52
oansone.g. provider networks09:52
itamaroi think a full snat solution should include a physical  network/interface mapping  and  even reachability checks,09:52
oansonUnless you have another suggestion09:52
oansonitamaro, yes to the second, not sure about the first. A more flexible approach will just let you nat between networks09:52
dimakoanson, it is super simple, each gets its own patch port09:52
itamarowe can use pkt marks09:53
*** Dua has joined #openstack-meeting-409:53
oansonThen you can have snat have a patch-port, ignoring that provider app already has one as well09:53
dimakThat way SNAT can communicate with provider ports as well09:53
oansonPossibly, but probably not the only way.09:54
dimak(No need for loopback if both apps classify on same patch port in table=0)09:54
itamaropkt-marks09:54
dimakShould work both ways, external bridge will flood and learn09:55
oansonitamaro, there is only so much you can cover with 'pkt-marks'. :)09:55
oansonPlease at least explain how to use them?09:55
itamaropkt marks can emulate patch port..09:55
oansonthat moves the logic to the external bridges.09:56
itamaroone can tag snat traffic with it'a mark, so you match on it09:57
oansonThat might not be too good, since the external bridges might be regular bridges (i.e. not OVS/OpenFlow)09:57
oansonnormal bridges*09:57
dimakI think we're almost out of time09:58
oansonYes09:58
oansonI am not convinced either way.09:58
oansondimak, itamaro, please discuss offline and come up with a design everyone is happy, which will support better snat/dnat implementations in the future (as discussed here)09:59
oansonAnd post for us a spec, if possible.09:59
oansonThat's all our time for today,09:59
dimak+109:59
oansonThanks everyone for coming.09:59
dimakBye09:59
oanson#endmeeting09:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:59
itamaroI think that snat should be given some extra thought. But even if ot requires it's own patch it can be handled intimately by the snat.09:59
openstackMeeting ended Mon Jul 10 09:59:55 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-07-10-09.00.html09:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-07-10-09.00.txt10:00
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-07-10-09.00.log.html10:00
oansonitamaro, yes10:00
*** kevinz has quit IRC10:16
*** sdague has joined #openstack-meeting-410:21
*** hieulq has quit IRC10:57
*** pbourke has quit IRC10:57
*** pbourke has joined #openstack-meeting-410:59
*** Dua has left #openstack-meeting-410:59
*** dixiaoli has quit IRC11:00
*** alexchadin has quit IRC11:10
*** hieulq has joined #openstack-meeting-411:12
*** rwallner has joined #openstack-meeting-411:13
*** shukixxxx has joined #openstack-meeting-411:14
*** shukixxxx has quit IRC11:14
*** rwallner_ has joined #openstack-meeting-411:15
*** rwallne__ has joined #openstack-meeting-411:16
*** rwallner has quit IRC11:17
*** rwallner_ has quit IRC11:20
*** julim has quit IRC11:30
*** trinaths has left #openstack-meeting-411:40
*** aavraham has quit IRC11:46
*** aavraham has joined #openstack-meeting-411:48
*** thorst has joined #openstack-meeting-411:53
*** dave-mccowan has joined #openstack-meeting-411:55
*** janki has joined #openstack-meeting-411:56
*** hieulq has quit IRC12:04
*** d0ugal has joined #openstack-meeting-412:04
*** d0ugal has quit IRC12:04
*** d0ugal has joined #openstack-meeting-412:04
*** kevinz has joined #openstack-meeting-412:05
*** kevzha01_ has joined #openstack-meeting-412:08
*** d0ugal has quit IRC12:12
*** kevinz has quit IRC12:12
*** krtaylor_ has joined #openstack-meeting-412:19
*** hieulq has joined #openstack-meeting-412:19
*** krtaylor has quit IRC12:20
*** cartik has joined #openstack-meeting-412:22
*** baoli has joined #openstack-meeting-412:25
*** alexchadin has joined #openstack-meeting-412:25
*** baoli has quit IRC12:27
*** baoli has joined #openstack-meeting-412:28
*** bobh has quit IRC12:28
*** bobh has joined #openstack-meeting-412:28
*** cartik has quit IRC12:30
*** iurygregory has quit IRC12:31
*** kkxue has quit IRC12:31
*** kkxue has joined #openstack-meeting-412:31
*** zhurong has quit IRC12:36
*** sambetts has quit IRC12:38
*** itamaro has quit IRC12:41
*** iurygregory has joined #openstack-meeting-412:41
*** bobh has quit IRC12:41
*** sambetts has joined #openstack-meeting-412:42
*** lyan has joined #openstack-meeting-412:44
*** Guest9640 is now known as beagles12:47
*** rwallne__ has quit IRC12:50
*** rwallner_ has joined #openstack-meeting-412:53
*** kkxue has quit IRC12:53
*** d0ugal has joined #openstack-meeting-412:54
*** d0ugal has quit IRC12:54
*** d0ugal has joined #openstack-meeting-412:54
*** woodard has quit IRC12:58
*** woodard has joined #openstack-meeting-412:58
*** d0ugal has quit IRC12:59
*** baoli has quit IRC13:00
*** woodard_ has joined #openstack-meeting-413:01
*** woodard_ has quit IRC13:01
*** woodard_ has joined #openstack-meeting-413:02
*** woodard has quit IRC13:03
*** hieulq has quit IRC13:16
*** trozet has joined #openstack-meeting-413:17
*** bobh has joined #openstack-meeting-413:22
*** sdague has quit IRC13:30
*** belmorei_ has joined #openstack-meeting-413:32
*** belmoreira has quit IRC13:32
*** sdague has joined #openstack-meeting-413:33
*** hieulq has joined #openstack-meeting-413:36
*** klamath has joined #openstack-meeting-413:46
*** klamath has quit IRC13:46
*** klamath has joined #openstack-meeting-413:46
*** rwallner_ has quit IRC13:50
*** rwallner has joined #openstack-meeting-413:52
*** rwallner has quit IRC13:53
*** rwallner_ has joined #openstack-meeting-413:54
*** woodard_ has quit IRC13:59
*** garyloug has joined #openstack-meeting-414:00
*** pbourke has quit IRC14:01
*** anilvenkata has quit IRC14:01
*** kural has joined #openstack-meeting-414:01
*** superdan is now known as dansmith14:02
apuimedo#startmeeting kuryr14:03
openstackMeeting started Mon Jul 10 14:03:00 2017 UTC and is due to finish in 60 minutes.  The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
*** openstack changes topic to " (Meeting topic: kuryr)"14:03
openstackThe meeting name has been set to 'kuryr'14:03
apuimedoHello and welcome to the weekly Kuryr IRC meeting14:03
apuimedowho's here for the show?14:03
ltomasboo/14:03
kzaitsev_wso/14:03
garylougo/14:03
irenabhi14:03
kzaitsev_wswill be connecting from my phone shortly as I need to go14:03
mchiappero o/14:04
apuimedokzaitsev_ws: I did the whole meeting last week in the car while my wife was driving14:04
kuralo/14:04
apuimedoI got so darned dizzy14:04
apuimedodo not ride and read14:04
ltomasbo:D14:05
*** baoli has joined #openstack-meeting-414:05
apuimedo#topic kuryr-libnetwork14:05
*** openstack changes topic to "kuryr-libnetwork (Meeting topic: kuryr)"14:05
apuimedokzaitsev_ws: do we have the doc fixed?14:06
apuimedoI saw your oslosphinx patches merged14:06
kzaitsev_ws#link https://docs.google.com/document/d/1GNZbmVxE2n5j07YRlkx4zP-XbFSPI9UEcVifX1MRXyY/edit14:06
kzaitsev_wsoh not that doc14:07
kzaitsev_ws=)14:07
kzaitsev_wsyeah14:07
kzaitsev_ws#link https://docs.openstack.org/kuryr-libnetwork/latest/14:07
apuimedoperfect14:07
apuimedothanks14:07
apuimedoSo that was all that happened this week in kuryr-libnetwork land14:08
apuimedoAnybody's got anything else on that?14:08
apuimedoalright14:09
apuimedomoving on14:09
apuimedo#topic kuryr-kubernetes14:09
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)"14:09
*** kzaitsev_ has joined #openstack-meeting-414:09
*** vishnoianil has quit IRC14:09
*** zengchen1 has joined #openstack-meeting-414:10
*** kzaitsev_ws has quit IRC14:10
apuimedo#info From 12-13h utc today we held a videoconference meeting about multiple networks. In it the community worked towards converging in the approach we adopt based on Network TPR/CRD and Pod network annotations and OIR for SRIOV (and possibly DPDK) bookkeeping14:11
apuimedo#info kzaitsev_ started a document for the SR-IOV Network object usage pros/cons https://docs.google.com/document/d/1GNZbmVxE2n5j07YRlkx4zP-XbFSPI9UEcVifX1MRXyY/14:11
ltomasbonice14:12
ltomasboI got some questions/request at my meetings last week for being able to specify the networks where the pods are to be plugged14:12
kural+114:12
apuimedoltomasbo: dmellado: I'll send you the link to the recording later14:12
apuimedoIf I forget, ping me14:12
ltomasboapuimedo, great! thanks!14:13
apuimedoif anybody else wants it, ping me as well ;-)14:13
apuimedoltomasbo: cool14:13
apuimedoso the recording should help with that14:13
irenabapuimedo: maybe you can put a link on kuryr wiki?14:13
apuimedowe'll add the agreements to vikasc' patch14:13
*** janki has quit IRC14:13
apuimedoirenab: you know I prefer to edit it first14:13
apuimedo:-)14:13
irenabapuimedo: sure14:14
*** hongbin has joined #openstack-meeting-414:14
apuimedootherwise it's full of silences14:14
ltomasboso, the idea is to polish vikasc spec?14:14
apuimedoI have pto tomorrow, wednesday and Friday14:14
apuimedoso I'll probably put the link on Thursday or Monday14:14
ltomasboand then make the modifications (considering the current SRIOV efforts)14:14
apuimedoltomasbo: yes, it will veer towards something more similar to what the community is doing14:15
kzaitsev_there is a short analysis of what can be moved to network objs. and only focuses on my sriov stuff. feel free to suggest/edit14:15
apuimedoand provide a way for the SRIOV to do it (probably as kzaitsev_'s current patches, we can make it simpler afterwards)14:15
kzaitsev_yeah. probably network objs is the way k8s will handle things14:15
kzaitsev_so no reason not to adopt it ahead of time14:15
hongbino/14:15
*** limao has joined #openstack-meeting-414:16
ltomasbosure, I like the idea and happy to collaborate!14:16
apuimedo#action apuimedo to try again to deploy the network addon14:16
apuimedohongbin: hi!14:16
kuralCurrently k8s network objs agreed to have only plugin in network spec, rest of args will be part of annotation..14:16
apuimedo#link https://docs.google.com/presentation/d/1-2UVtWSsiMdzO1xUpsPsKjXcX3mOHb5zHI-xEPHi7v4/edit?usp=sharing14:17
irenabI think we should try to be aligned with what is agreed at k8s-net-sig14:17
apuimedoltomasbo: this are the slides I showed14:17
apuimedokural: righr14:17
apuimedo*right14:17
kuralOnce k8s community agreed on proposal, we can change the args from annotation.. Will provide more information in the doc14:17
apuimedoand I think it's a good thing that the rest be annotation tbf14:18
ltomasbook, thanks!14:18
apuimedoit will prevent people wanting to put spec for CIDR in network objects14:18
apuimedowhich IMHO is a good thing14:18
kzaitsev_so where does the networkid go then?14:18
*** pbourke has joined #openstack-meeting-414:18
apuimedokzaitsev_: annotation14:18
kuralannotation14:18
kzaitsev_pod annotation?14:18
apuimedoeither annotation or label14:18
kuralnetwork annotation14:19
kzaitsev_oh. ok makes sense14:19
kuralpod annotation is only for network obj name14:19
apuimedokzaitsev_: if you mean the subnetid, on the network annotation14:19
apuimedoright14:19
apuimedokural: and it is namespace specific!)14:19
kuralCR or TPR don't support namespace14:19
irenabnetwork is namespace specific?14:19
kuralit support only default namespace14:19
apuimedooh true14:19
apuimedoI'm dumb14:20
apuimedoxD14:20
* apuimedo scratches the bruise on top of his head14:20
kzaitsev_we'll have to work with that then :/14:20
kuraloriginal K8s Multi-net PoC, puts them out of scope14:20
apuimedokural: no, no. It makes sense14:20
kuralbut it open new windows of complexity14:20
*** limao_ has joined #openstack-meeting-414:20
apuimedoindeed14:21
apuimedokural: it basically means networks are operational things14:21
*** limao has quit IRC14:21
apuimedopossibly not to be created by users :P14:21
apuimedobut we'll see how it plays out14:21
kuralnetwork obj is created by operator, pod spec network is by users14:21
apuimedoright14:21
*** beekneemech is now known as bnemec14:22
kzaitsev_I'll be working on a multi-network poc this week. will see if i can incorporate discussion results there14:22
kuraluser can only select the network, operator has privilege to update/create network obj14:22
apuimedo#info janonymous has been advancing his work on the CNI Daemon split14:22
apuimedo#link https://review.openstack.org/#/c/480028/14:22
apuimedokzaitsev_: irenab: ltomasbo: please review ^^14:23
apuimedoIt is tight for Pike, but it would be nice to have it asap14:24
irenabits still WIP14:24
apuimedoirenab: right, just to check the direction14:24
kzaitsev_would be grateful if you add me manually to the review :)14:24
ltomasboapuimedo, ok14:24
irenabapuimedo: cool, will check it asap14:24
apuimedokzaitsev_: I will!14:24
kzaitsev_hard to do on the go :)14:24
apuimedokzaitsev_: done14:24
apuimedo#action apuimedo irenab ltomasbo kural to review SRIOV patches14:25
*** alexchadin has quit IRC14:25
apuimedo#link https://review.openstack.org/#/q/status:open+project:openstack/kuryr-kubernetes+branch:master+topic:bp/kuryr-kubernetes-sriov-support14:25
apuimedoI've already looked into them14:26
apuimedobut we should add some comments ;-)14:26
kuralGary and me will work..14:26
irenabapuimedo: I did partially, will follow-up14:26
*** kzaitsev_ has quit IRC14:27
apuimedo#action janonymous to address comments from kzaitsev_ in https://review.openstack.org/#/c/454555/14:27
apuimedoperfect14:27
*** kzaitsev_ has joined #openstack-meeting-414:27
apuimedoalright. Anybody's got anything else on kuryr-k8s?14:27
garylougyes14:27
*** galstrom_zzz is now known as galstrom14:28
garylougI've added a BP for DPDK: https://blueprints.launchpad.net/kuryr-kubernetes/+spec/nested-dpdk-support14:28
apuimedoon my side, I'm struggling moving to the separate devstack-container-plugin14:28
apuimedogaryloug: OH! Didn't see it14:28
apuimedosorry14:28
mchiapperohow will the daemon split deal with the config file?14:28
garylougI just uploaded :)14:28
*** galstrom is now known as galstrom_zzz14:28
*** psachin has quit IRC14:28
apuimedo#action review https://blueprints.launchpad.net/kuryr-kubernetes/+spec/nested-dpdk-support14:28
*** galstrom_zzz is now known as galstrom14:28
apuimedoah14:28
apuimedomchiappero: well, the conf file will be for the daemon14:28
mchiapperoso will it keep the default network information?14:29
apuimedothe small kubelet called executable will only know which unix domain socket to talk to14:29
*** zhurong has joined #openstack-meeting-414:29
apuimedomchiappero: I hadn't thought it like htat. I expected that to be known by the controller only14:30
mchiapperook :)14:30
*** cartik has joined #openstack-meeting-414:30
irenabI think we try to preserve the asumption that the only info CNI gets is the VIF related stuff driven by controller14:31
apuimedogaryloug: alright. I'll get back to you on Thursday about the blueprint14:31
apuimedoright14:31
apuimedoirenab: just as you said. As much as possible without getting to stubborn about it14:31
mchiapperosounds good :) I was just curious14:32
apuimedo:-)14:32
apuimedoAnything else before we move on to fuxi14:32
*** dixiaoli has joined #openstack-meeting-414:33
*** dixiaoli has quit IRC14:33
*** kzaitsev_68 has joined #openstack-meeting-414:34
apuimedoalright, moving on14:34
apuimedo#topic fuxi14:34
*** openstack changes topic to "fuxi (Meeting topic: kuryr)"14:34
hongbinhi all14:34
apuimedo#chair hongbin14:34
openstackCurrent chairs: apuimedo hongbin14:34
hongbinin last week, the major things are the patches proposed by zengchen114:34
hongbinzengchen1: could you give an update about that14:35
zengchen1yes14:35
*** kzaitsev_ has quit IRC14:35
zengchen1for the past week, I finished the flexvolume driver of cinder and have tested it on the real environment14:35
zengchen1that is all.14:36
hongbini believe a few patches were merged last week, thanks for the kuryr team for reviewing them14:37
hongbinthere are a few patches that is under active reviews14:37
zengchen1yes, they gave many valume comments.14:37
zengchen1s/valume/valuable14:37
apuimedocool14:37
apuimedozengchen1: ping us any time we slow down14:37
apuimedosometimes it happens :/14:37
zengchen1ok14:37
*** vishnoianil has joined #openstack-meeting-414:38
hongbinapuimedo: that is all from my side :)14:38
apuimedovery well14:38
apuimedo#topic general14:38
*** openstack changes topic to "general (Meeting topic: kuryr)"14:38
*** kzaitsev_ has joined #openstack-meeting-414:39
apuimedoI wanted to propose dates for the VTG14:39
apuimedoSeptember 19th, 20th and 21st14:39
apuimedoI will not be attending the PTG this time, btw14:40
*** kzaitsev_68 has quit IRC14:40
irenabapuimedo: I think it may be the holidays for me14:40
kzaitsev_Are we doing it virtually or do we plan to pursue that Brno idea? :)14:40
apuimedowe could maybe do it the week before the ptg instead, this time14:41
apuimedokzaitsev_: it would depend on how easy it is for all the folks to attend14:41
irenaba week before is better14:41
*** woodard has joined #openstack-meeting-414:41
ltomasbobefore PTG? that is the first week of September?14:41
*** belmorei_ has quit IRC14:41
kzaitsev_I'll try my best to not attend the PTG too :)14:41
ltomasboxD14:41
apuimedoltomasbo: 6, 7 and 8th is before I think14:42
*** belmoreira has joined #openstack-meeting-414:42
irenabapuimedo: just checked September 20-22 are holidays over here14:42
kzaitsev_a doodle might help14:43
irenabapuimedo: 5,6, 7 ?14:43
irenabno Sundays and Fridays :-)14:43
apuimedoirenab: that's right14:43
*** jamesbenson has joined #openstack-meeting-414:44
*** kzaitsev_ has quit IRC14:45
*** woodard has quit IRC14:45
*** woodard_ has joined #openstack-meeting-414:45
apuimedoalright. That was all from me. Does anybody have anything else?14:45
*** kzaitsev_ has joined #openstack-meeting-414:45
*** woodard_ has quit IRC14:45
*** woodard has joined #openstack-meeting-414:46
mchiapperothis is likely my last kuryr-meeting, I just wanted to say it's been nice working with you14:46
mchiapperoyou're great people :)14:46
*** belmoreira has quit IRC14:46
irenabmchiappero: good luck with your next projects. It was a pleasure working with you14:47
ltomasboohh, bad to hear it!14:47
kzaitsev_oh that's sad :(. please come by to say hello :)14:47
ltomasbogood luck in the next challenge!14:47
mchiapperoI will still be around somehow :)14:47
mchiapperobest of luck to you guys14:48
*** chyka has joined #openstack-meeting-414:48
apuimedothanks a lot mchiappero!14:48
*** chyka has quit IRC14:48
apuimedoand good luck14:48
apuimedoThanks to you all for joining today, specially after the long bluejeans meeting we had just before14:49
apuimedoI really appreciate it14:49
apuimedo#endmeeting14:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:49
openstackMeeting ended Mon Jul 10 14:49:26 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-07-10-14.03.html14:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-07-10-14.03.txt14:49
*** chyka has joined #openstack-meeting-414:49
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-07-10-14.03.log.html14:49
*** hieulq has quit IRC14:51
*** cholcombe has joined #openstack-meeting-414:52
*** kzaitsev_ has quit IRC14:54
*** zhurong has quit IRC14:56
*** zengchen1 has quit IRC14:56
*** yamahata has quit IRC14:59
*** yamahata has joined #openstack-meeting-415:00
*** kevzha01__ has joined #openstack-meeting-415:01
*** kevzha01_ has quit IRC15:05
*** limao_ has quit IRC15:05
*** kevzha01__ has quit IRC15:06
*** limao has joined #openstack-meeting-415:06
*** cartik has quit IRC15:06
*** hieulq has joined #openstack-meeting-415:09
*** limao_ has joined #openstack-meeting-415:12
*** limao has quit IRC15:14
*** lkoranda has quit IRC15:19
*** d0ugal has joined #openstack-meeting-415:20
*** d0ugal has quit IRC15:20
*** d0ugal has joined #openstack-meeting-415:20
*** unicell1 has joined #openstack-meeting-415:21
*** unicell has quit IRC15:23
*** lkoranda has joined #openstack-meeting-415:25
*** hieulq has quit IRC15:28
*** hieulq has joined #openstack-meeting-415:43
*** gongysh has joined #openstack-meeting-415:51
*** baoli has quit IRC15:55
*** d0ugal has quit IRC15:56
*** baoli has joined #openstack-meeting-415:56
*** unicell1 has quit IRC15:57
*** cathrichardson has joined #openstack-meeting-415:59
*** cathrich_ has quit IRC16:02
*** egonzalez has quit IRC16:03
*** Julien-zte has quit IRC16:04
*** Julien-zte has joined #openstack-meeting-416:05
*** Julien-zte has quit IRC16:05
*** Julien-zte has joined #openstack-meeting-416:06
*** Julien-zte has quit IRC16:06
*** Julien-zte has joined #openstack-meeting-416:07
*** Julien-zte has joined #openstack-meeting-416:07
*** Julien-zte has joined #openstack-meeting-416:08
*** Julien-zte has quit IRC16:08
*** Julien-zte has joined #openstack-meeting-416:09
*** Julien-zte has quit IRC16:09
*** bogdando has quit IRC16:11
*** gongysh has quit IRC16:15
*** coolsvap has quit IRC16:16
*** limao_ has quit IRC16:20
*** baoli has quit IRC16:23
*** cshen has joined #openstack-meeting-416:34
*** hieulq has quit IRC16:36
*** harlowja has joined #openstack-meeting-416:37
*** julim has joined #openstack-meeting-416:39
*** slaweq has joined #openstack-meeting-416:48
*** hieulq has joined #openstack-meeting-416:51
*** slaweq has quit IRC16:54
*** thedac has joined #openstack-meeting-416:57
*** hieulq has quit IRC16:59
*** garyloug has quit IRC17:00
joedborg#startmeeting charms17:00
openstackMeeting started Mon Jul 10 17:00:03 2017 UTC and is due to finish in 60 minutes.  The chair is joedborg. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: charms)"17:00
openstackThe meeting name has been set to 'charms'17:00
joedborgo/17:00
tinwoodo/17:00
thedaco/17:00
jamespageo/17:00
joedborg#topic Review ACTION points from previous meeting17:00
*** openstack changes topic to "Review ACTION points from previous meeting (Meeting topic: charms)"17:00
wolseno/17:01
joedborgcholcombe to generate spec for glusterfs charm work17:01
cholcombejoedborg: yeah i'm working on that today.  it's almost finished17:01
joedborgawesome, thanks cholcombe17:01
joedborgjamespage to organise weekly bug triage rota for the team (also on ODD meeting actions)17:01
jamespagebah that's a fail again - I keep getting distracted - please carry over17:02
* jamespage makes a note to sort that out this week17:02
joedborgno worries, thanks jamespage17:02
joedborg#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
joedborgAny updates for the Gnocchi charm?17:03
jamespageyup17:03
jamespagehmm is my collaborator here?17:03
jamespageit would appear not17:03
jamespageanyway17:03
jamespagehttps://github.com/openstack-charmers/charm-gnocchi17:03
jamespagetesting at the moment; functionally things appear to work - using ceph for storage, with mysql for indexing the memcached for coordination (required for HA deployments)17:04
jamespagesome changes into the rest of the charms - specifically ceilometer and keystone reviews up17:04
jamespagehttps://review.openstack.org/#/q/topic:gnocchi-charm17:04
wolsenthe keystone one should be landed I think17:05
jamespagemost of the existing notifications configuration in the charms appears to work - I'm validating and will update for deprecations as I go along17:05
*** iyamahat has joined #openstack-meeting-417:05
jamespagewolsen: yeah - thankyou!17:05
wolsenjamespage: np, I'll look at the ceilometer one this afternoon17:05
tinwoodjamespage, does any dictionary data go over the relationship from gnocchi to keystone?17:05
jamespageI'm also poking at grafana -> gnocchi for reporting17:05
jamespagetinwood: no - but I think I'm seeing that bug in the hacluster sub relation17:06
tinwoodright.17:06
jamespagesome considerations for gnocchi - as soon as you configure ceilometer to use gnocchi, it turns its API off...17:07
tinwoodI'm wondering if it's something we can 'fix' in charms.openstack.  serialisation helper or something.17:07
jamespagebasically its redundant at that point17:07
jamespagetinwood: +1 sounds good17:07
jamespageanyway things progress - I'm pretty optimistic about having that ready for the august release17:07
tinwoodI'll take a poke at it.  joedborg action for me17:07
coreycbo/17:08
jamespagethe charm template helped alot, but its bit-rotted against best practice a bit so we need to refresh17:08
joedborg#action tinwood helper for Gnocchi in charms.openstack (serialisation)17:09
joedborganything else on Gnocchi?17:10
jamespagejoedborg: can you action a refresh of the charm templates as well please17:10
joedborgis that to be actioned by you?17:10
jamespageyeah why not17:10
joedborg:)17:10
joedborg#action jamespage refresh of charm templates17:11
joedborgOkay, next topic is Snaps integration into Charms17:11
thedaccoreycb et al have done great work getting the snaps ready in the snap store. \o/17:12
thedacStill working on keystone PoC as we have moved from classic back to jail mode but it is close.17:12
thedacThe helpers are ready for some more eyes on https://code.launchpad.net/~thedac/charm-helpers/os-snaps/+merge/32570217:12
coreycbthedac: i'll take a look at that17:12
thedacthanks17:12
joedborgAnything more to add on Snaps?17:14
thedacthat is it from me17:14
coreycbjoedborg: i don't think so, not for this meeting at least17:14
joedborgsweet, thanks coreycb and thedac17:15
joedborg#topic High Priority Bugs17:15
*** openstack changes topic to "High Priority Bugs (Meeting topic: charms)"17:15
joedborghttps://bugs.launchpad.net/openstack-charms/+bugs17:15
joedborgDoes anyone want to raise anything bug related?17:16
jamespagewe should try to address the two critical bugs that are not fix committed17:16
jamespagehttps://bugs.launchpad.net/charm-ceph-osd/+bug/167518617:16
openstackLaunchpad bug 1675186 in OpenStack ceph-osd charm "ceph-osd storage-attached hook fails" [Critical,Triaged] - Assigned to Chris Holcombe (xfactor973)17:16
jamespageand17:16
jamespagehttps://bugs.launchpad.net/charm-hacluster/+bug/147898017:16
openstackLaunchpad bug 1478980 in OpenStack hacluster charm "If the principle updates a resource parameter of an already configured resource hacluster ignores it" [Critical,Triaged]17:16
jamespageany takers?17:16
jamespagethat second one is non-trivial17:16
jamespageoh cholcombe already has that first one - please can you review!17:17
cholcombejamespage: sure17:17
thedacI'll see if I can get to the hacluster one17:17
wolsenI can look at the hacluster one as well17:18
wolsenI'm getting a ping from someone who needs that at the moment17:18
thedacgreat17:18
wolsenI'll assign it to myself right now17:18
jamespageta17:18
thedacwolsen: feel free to ping me for reviews then17:18
wolsenthedac: will do17:19
*** yamamoto has quit IRC17:19
joedborgAny more bugs?17:20
jamespagenope17:20
*** slaweq has joined #openstack-meeting-417:20
jamespagewell there are always bugs but not for today I think!17:20
joedborghaha, yeah i thought that when I sent it17:20
tinwoodindeed.17:20
joedborg#topic Openstack Events17:21
*** openstack changes topic to "Openstack Events (Meeting topic: charms)"17:21
joedborgAccording to the notes, there is a PTG in September17:21
joedborgAnything to add?17:21
thedacYes, and I believe there a couple of days left for OpenStack Summit proposals17:21
jamespageoh yes - good reminder!17:22
thedacI am not sure how many of us will make it to Sydney17:22
jamespagetis along way!17:22
wolsenand short at 3 days17:23
tinwoodtis a very long way17:23
jamespageI'm also speaking at the openstack uk day in london at the end of september17:23
jamespageftr17:23
jamespagetopic tbc17:23
tinwoodcongrats!17:24
*** slaweq has quit IRC17:24
jamespagetinwood: ta17:24
*** slaweq has joined #openstack-meeting-417:24
joedborgAnyone else?17:25
tinwoodnope, I'm good.17:25
wolsenall good on events here17:25
jamespage...17:25
joedborg#topic Open Discussion17:26
*** openstack changes topic to "Open Discussion (Meeting topic: charms)"17:26
jamespage(that was for gnuoy)17:26
thedac:)17:26
wolsenheh17:26
tinwood:)17:26
joedborgHave we anything else to be raised today?17:27
wolsenI've been thinking about the openstack charmhelpers stuff17:27
wolsenit would be fairly nice to have the contrib.openstack in its own repo at times17:27
* tinwood perks up in interest17:27
tinwoodwolsen, yes, and some sort of long term merger with charms.openstack would be cool.17:28
tinwoodOr at least more code sharing.17:28
wolsentinwood: +100017:28
wolsenyeah17:28
jamespageI'd support that move17:28
wolsenmaybe we can start thinking about it for next cycle17:29
jamespagehowever we do need a way to deal with classic style charms in that model17:29
jamespagesure that figurable-outable17:29
*** slaweq has quit IRC17:29
wolsencorrect17:29
tinwoodagreed17:29
wolsens/correct/agreed17:29
wolsenso maybe I can chat with tinwood about this idea more as we get near the next cycle17:30
jamespage+1 great17:30
tinwoodsounds good; I'm up for that.17:30
* jamespage has to drop - need to be somewhere else17:30
tinwoodwe should take an action as a reminder.17:30
tinwoodbye jamespage17:31
joedborgciao jamespage17:31
wolsenI think an action would be good17:31
joedborgwhat shall i call it tinwood wolsen ?17:31
joedborgand who should i assign it to?17:31
tinwoodhow about: "tinwood wolsen to discus contrib.openstack and charms.openstack roadmap"17:31
wolsenperfect17:31
joedborghaha that simple17:32
tinwoodIt's a placeholder, but useful.17:32
joedborg#action tinwood wolsen discus contrib.openstack and charms.openstack roadmap17:32
joedborgAnything else?17:33
tinwoodNope, I'm good.17:33
thedacRelated to that we might want an update on the attempts to move charmhelpers to github. I think there were problems with commit attribution history17:33
tinwoodthedac, I'm sure james is all over that17:33
tinwood(at least he was)17:33
*** Kevin_Zheng has quit IRC17:33
wolsenyeah, I recently had a short discussion with jamespage on that17:33
thedacok17:33
tinwoodBut, we should keep it on a card or something17:34
wolsenhe was working on it and I think it was a matter of rewriting emails or something - there's a lot of commits so it takes more time17:34
joedborgshall i add an action wolsen / thedac ?17:35
thedacjoedborg: jamespage ;)17:35
joedborg#action jamespage moving charmhelpers to github17:36
wolsenboy james has a lot of actions17:36
tinwoodactions in absence - the ideal of a meeting17:36
tinwood:)17:36
wolsen"he didn't say no"17:36
thedacAgreed, we can figure out redistribution offline17:36
joedborgAnything else?17:37
wolsenI'm good17:38
thedacAll done17:38
tinwoodall done too17:38
joedborg#topic Next Chair17:38
*** openstack changes topic to "Next Chair (Meeting topic: charms)"17:38
joedborgI'm not sure if this goes back the beisner?17:39
tinwoodnah, just rotate to the next one (which is probably me)17:39
joedborgIt's Dmitrii-Sh17:39
tinwoodwe have a winner!17:39
wolsenhaha17:39
thedacDo we need to remove Dmitrii-Sh? Is he likely to be available?17:40
*** hieulq has joined #openstack-meeting-417:40
joedborgIt's a bit uncertain with all of us FEs (we can talk about it after)17:40
thedacok17:40
joedborgSo it'll either be Dmitrii-Sh or tinwood :)17:40
tinwoodyay17:41
joedborg#endmeeting17:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:41
openstackMeeting ended Mon Jul 10 17:41:19 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:41
joedborgThanks all17:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-07-10-17.00.html17:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-07-10-17.00.txt17:41
openstackLog:            http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-07-10-17.00.log.html17:41
tinwoodthanks joedborg17:41
wolsenthanks joedborg o/17:41
thedacThanks, joedborg17:41
*** julim has quit IRC17:41
*** hieulq has quit IRC17:43
*** ralonsoh has quit IRC17:44
*** yamahata has quit IRC17:49
*** iyamahat has quit IRC17:49
*** slaweq has joined #openstack-meeting-417:51
*** hieulq has joined #openstack-meeting-417:58
*** emagana has joined #openstack-meeting-418:00
*** dmellado has quit IRC18:02
*** dmellado has joined #openstack-meeting-418:02
*** aavraham has quit IRC18:04
*** iyamahat has joined #openstack-meeting-418:05
*** sambetts is now known as sambetts|afk18:05
*** makowals has quit IRC18:07
*** kylek3h has joined #openstack-meeting-418:11
*** cathrichardson has left #openstack-meeting-418:17
*** yamamoto has joined #openstack-meeting-418:19
*** bobmel has joined #openstack-meeting-418:20
*** makowals has joined #openstack-meeting-418:22
*** Sukhdev has joined #openstack-meeting-418:24
*** yamahata has joined #openstack-meeting-418:24
*** vishnoianil has quit IRC18:26
*** yamamoto has quit IRC18:27
*** unicell has joined #openstack-meeting-418:29
*** baoli has joined #openstack-meeting-418:31
*** makowals has quit IRC18:39
*** rwallner_ has quit IRC18:52
*** rwallner has joined #openstack-meeting-418:59
*** galstrom is now known as galstrom_zzz19:01
*** rwallner has quit IRC19:04
*** kural has quit IRC19:09
*** makowals has joined #openstack-meeting-419:14
*** vishnoianil has joined #openstack-meeting-419:14
*** hieulq has quit IRC19:38
*** cathrichardson has joined #openstack-meeting-419:49
*** trozet has quit IRC19:51
*** d0ugal has joined #openstack-meeting-419:57
*** cshen has quit IRC20:02
*** trozet has joined #openstack-meeting-420:04
*** cshen has joined #openstack-meeting-420:06
*** makowals has quit IRC20:38
*** thorst has quit IRC20:42
*** thorst has joined #openstack-meeting-420:45
*** thorst has quit IRC20:49
*** d0ugal has quit IRC20:52
*** galstrom_zzz is now known as galstrom20:52
*** rockyg has joined #openstack-meeting-420:54
*** MeganR has joined #openstack-meeting-420:55
*** hoangcx has joined #openstack-meeting-420:56
*** thorst has joined #openstack-meeting-421:00
*** cshen has quit IRC21:14
*** dklyle has joined #openstack-meeting-421:18
*** david-lyle has quit IRC21:19
*** tonytan4ever has joined #openstack-meeting-421:19
*** makowals has joined #openstack-meeting-421:20
*** leyal has quit IRC21:26
*** leyal has joined #openstack-meeting-421:27
*** oanson has quit IRC21:28
*** oanson has joined #openstack-meeting-421:29
*** trozet has quit IRC21:33
*** baoli has quit IRC21:36
*** baoli has joined #openstack-meeting-421:37
*** gongysh has joined #openstack-meeting-421:47
*** woodard_ has joined #openstack-meeting-421:48
*** jamesbenson has quit IRC21:51
*** woodard has quit IRC21:52
*** vishwanathj has joined #openstack-meeting-421:52
*** woodard_ has quit IRC21:52
*** jamesbenson has joined #openstack-meeting-421:53
*** hieulq has joined #openstack-meeting-421:54
*** slaweq has quit IRC21:55
*** slaweq has joined #openstack-meeting-421:55
*** makowals has quit IRC21:57
*** jamesbenson has quit IRC21:58
*** kural has joined #openstack-meeting-421:59
*** slaweq has quit IRC21:59
*** kylek3h has quit IRC22:00
*** slaweq has joined #openstack-meeting-422:00
*** MeganR has quit IRC22:02
*** thorst has quit IRC22:02
*** makowals has joined #openstack-meeting-422:09
*** galstrom is now known as galstrom_zzz22:10
*** hieulq has quit IRC22:12
*** deep-book-gk_ has joined #openstack-meeting-422:15
*** slaweq has quit IRC22:16
*** deep-book-gk_ has left #openstack-meeting-422:17
*** kural has quit IRC22:20
*** lyan has quit IRC22:20
*** kural has joined #openstack-meeting-422:21
*** makowals has quit IRC22:24
*** bobh has quit IRC22:27
*** hieulq has joined #openstack-meeting-422:27
*** kural_ has joined #openstack-meeting-422:28
*** kural has quit IRC22:28
*** emagana has quit IRC22:36
*** slaweq has joined #openstack-meeting-422:37
*** kural_ has quit IRC22:37
*** emagana has joined #openstack-meeting-422:37
*** kural_ has joined #openstack-meeting-422:37
*** slaweq has quit IRC22:41
*** emagana has quit IRC22:42
*** kural has joined #openstack-meeting-422:42
*** kural_ has quit IRC22:42
*** Julien-zte has joined #openstack-meeting-422:43
*** makowals has joined #openstack-meeting-422:48
*** makowals has quit IRC22:52
*** Julien-zte has quit IRC23:04
*** Julien-zte has joined #openstack-meeting-423:06
*** rockyg has quit IRC23:08
*** hoangcx__ has joined #openstack-meeting-423:09
*** hoangcx has quit IRC23:09
*** thorst has joined #openstack-meeting-423:17
*** makowals has joined #openstack-meeting-423:18
*** woodard has joined #openstack-meeting-423:20
*** thorst has quit IRC23:21
*** bobh has joined #openstack-meeting-423:24
*** bobh has quit IRC23:27
*** bobh has joined #openstack-meeting-423:34
*** bobh has quit IRC23:35
*** hoangcx__ has quit IRC23:35
*** hoangcx has joined #openstack-meeting-423:36
*** bobh has joined #openstack-meeting-423:39
*** hongbin has quit IRC23:42
*** bobh has quit IRC23:43
*** amotoki is now known as amotoki_away23:43
*** hoangcx has quit IRC23:45
*** bobh has joined #openstack-meeting-423:50
*** chyka has quit IRC23:54
*** chyka has joined #openstack-meeting-423:55
*** irenab has quit IRC23:56
*** irenab has joined #openstack-meeting-423:56
*** lihi has quit IRC23:56
*** thorst has joined #openstack-meeting-423:57
*** dimak has quit IRC23:58
*** leyal has quit IRC23:58
*** oanson has quit IRC23:59
*** dimak has joined #openstack-meeting-423:59
*** chyka has quit IRC23:59

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