Monday, 2017-02-13

*** bobh has quit IRC00:00
*** rwallner has joined #openstack-meeting-400:08
*** thorst_ has joined #openstack-meeting-400:10
*** thorst_ has quit IRC00:12
*** rwallner has quit IRC00:12
*** Julien-zte has joined #openstack-meeting-400:13
*** bobh has joined #openstack-meeting-400:18
*** rwallner has joined #openstack-meeting-400:21
*** baoli has joined #openstack-meeting-400:22
*** baoli has quit IRC00:23
*** baoli has joined #openstack-meeting-400:23
*** rwallner has quit IRC00:25
*** baoli has quit IRC00:38
*** SerenaFeng has joined #openstack-meeting-400:55
*** julim has quit IRC00:55
*** mattmceuen has quit IRC01:05
*** mattmceuen has joined #openstack-meeting-401:06
*** hshan has quit IRC01:17
*** zz_ja has quit IRC01:19
*** iurygregory has quit IRC01:19
*** v1k0d3n has quit IRC01:19
*** thorst_ has joined #openstack-meeting-401:19
*** thorst_ has quit IRC01:19
*** iurygregory has joined #openstack-meeting-401:19
*** iberezovskiy_ has quit IRC01:20
*** iberezovskiy has joined #openstack-meeting-401:21
*** zz_ja has joined #openstack-meeting-401:22
*** v1k0d3n has joined #openstack-meeting-401:22
*** salv-orlando has joined #openstack-meeting-401:23
*** salv-orlando has quit IRC01:27
*** gongysh has joined #openstack-meeting-401:41
*** mattmceuen has quit IRC01:42
*** thorst_ has joined #openstack-meeting-401:45
*** thorst_ has quit IRC01:45
*** hongbin_ has joined #openstack-meeting-401:57
*** baoli has joined #openstack-meeting-402:04
*** SerenaFeng has quit IRC02:05
*** julim has joined #openstack-meeting-402:10
*** v1k0d3n has quit IRC02:14
*** thorst_ has joined #openstack-meeting-402:19
*** thorst_ has quit IRC02:19
*** v1k0d3n has joined #openstack-meeting-402:19
*** woodard has joined #openstack-meeting-402:20
*** rwallner has joined #openstack-meeting-402:20
*** lei-zh has joined #openstack-meeting-402:21
*** rwallner has quit IRC02:24
*** SerenaFeng has joined #openstack-meeting-402:24
*** woodard has quit IRC02:25
*** baoli has quit IRC02:33
*** sdake has joined #openstack-meeting-402:34
*** armax has joined #openstack-meeting-402:35
*** sdake_ has joined #openstack-meeting-402:40
*** sdake has quit IRC02:43
*** SerenaFeng has quit IRC02:49
*** xiaohhui has quit IRC02:50
*** SerenaFeng has joined #openstack-meeting-402:51
*** SerenaFe_ has joined #openstack-meeting-402:54
*** SerenaFeng has quit IRC02:54
*** tovin07 has joined #openstack-meeting-402:55
*** anilvenkata has joined #openstack-meeting-402:55
*** chandanc_ has joined #openstack-meeting-402:55
*** tovin07_ has joined #openstack-meeting-402:57
*** liuyulong has joined #openstack-meeting-403:05
*** sdake has joined #openstack-meeting-403:17
*** sdake_ has quit IRC03:18
*** rwallner has joined #openstack-meeting-403:19
*** thorst_ has joined #openstack-meeting-403:20
*** armax has quit IRC03:21
*** rwallner has quit IRC03:24
*** salv-orlando has joined #openstack-meeting-403:24
*** thorst_ has quit IRC03:25
*** bobh has quit IRC03:28
*** salv-orlando has quit IRC03:28
*** bobh has joined #openstack-meeting-403:34
*** bobh has quit IRC03:38
*** bobh has joined #openstack-meeting-403:39
*** gongysh has quit IRC03:39
*** bobh has quit IRC03:43
*** bobh has joined #openstack-meeting-403:46
*** sdake has quit IRC03:49
*** SerenaFe_ has quit IRC03:51
*** julim has quit IRC03:55
*** julim has joined #openstack-meeting-403:57
*** janki has joined #openstack-meeting-403:59
*** julim has quit IRC04:01
*** julim has joined #openstack-meeting-404:04
*** bobh has quit IRC04:07
*** Julien-zte has quit IRC04:09
*** Julien-z_ has joined #openstack-meeting-404:10
*** psachin has joined #openstack-meeting-404:10
*** Julien-z_ has quit IRC04:15
*** Julien-zte has joined #openstack-meeting-404:15
*** thorst_ has joined #openstack-meeting-404:21
*** thorst_ has quit IRC04:26
*** SerenaFeng has joined #openstack-meeting-404:38
*** SerenaFeng has quit IRC04:46
*** rwallner has joined #openstack-meeting-404:53
*** salv-orlando has joined #openstack-meeting-404:54
*** rwallner has quit IRC04:57
*** salv-orlando has quit IRC04:59
*** adisky_ has joined #openstack-meeting-405:00
*** unicell has joined #openstack-meeting-405:03
*** unicell has quit IRC05:11
*** mtreinish has quit IRC05:20
*** hongbin_ has quit IRC05:21
*** rwallner has joined #openstack-meeting-405:22
*** rwallner has quit IRC05:27
*** mtreinish has joined #openstack-meeting-405:31
*** Rockyg has quit IRC05:32
*** amotoki has joined #openstack-meeting-405:33
*** amotoki has quit IRC05:36
*** trinaths has joined #openstack-meeting-405:39
*** SerenaFeng has joined #openstack-meeting-405:46
*** amotoki has joined #openstack-meeting-405:48
*** janki has quit IRC05:50
*** trinaths has left #openstack-meeting-405:55
*** salv-orlando has joined #openstack-meeting-405:55
*** salv-orlando has quit IRC06:00
*** janki has joined #openstack-meeting-406:00
*** l4yerffeJ__ has joined #openstack-meeting-406:00
*** Jeffrey4l__ has joined #openstack-meeting-406:01
*** Jeffrey4l_ has quit IRC06:04
*** l4yerffeJ_ has quit IRC06:04
*** jrist has joined #openstack-meeting-406:04
*** amotoki has quit IRC06:10
*** thorst_ has joined #openstack-meeting-406:22
*** amotoki has joined #openstack-meeting-406:23
*** thorst_ has quit IRC06:26
*** psachin has quit IRC06:33
*** abhishekk has left #openstack-meeting-406:38
*** itisha has quit IRC06:42
*** salv-orlando has joined #openstack-meeting-406:43
*** psachin has joined #openstack-meeting-406:50
*** psachin has quit IRC06:54
*** psachin has joined #openstack-meeting-406:54
*** salv-orl_ has joined #openstack-meeting-407:00
*** liuyulong_ has joined #openstack-meeting-407:00
*** liuyulong has quit IRC07:03
*** salv-orlando has quit IRC07:03
*** nkrinner_afk is now known as nkrinner07:12
*** yamamoto has quit IRC07:34
*** ralonsoh has joined #openstack-meeting-407:46
*** pcaruana has joined #openstack-meeting-407:49
*** xiaohhui has joined #openstack-meeting-408:13
*** matrohon has joined #openstack-meeting-408:14
*** hwoarang has quit IRC08:16
*** yamamoto has joined #openstack-meeting-408:17
*** yamamoto has quit IRC08:17
*** yamamoto has joined #openstack-meeting-408:18
*** thorst_ has joined #openstack-meeting-408:22
*** ltomasbo|away is now known as ltomasbo08:25
*** thorst_ has quit IRC08:27
*** liuyulong_ is now known as liuyulong08:37
*** rwallner has joined #openstack-meeting-408:43
*** hughhalf has quit IRC08:46
*** duankebo has joined #openstack-meeting-408:47
*** hughhalf has joined #openstack-meeting-408:47
*** rwallner has quit IRC08:48
*** mfedosin has joined #openstack-meeting-408:50
*** nick_ma has joined #openstack-meeting-408:51
*** ishafran has joined #openstack-meeting-408:57
*** itamaro has joined #openstack-meeting-408:57
itamaroHi all08:57
oanson#startmeeting Dragonflow09:00
openstackMeeting started Mon Feb 13 09:00:06 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
oansonitamaro, hi09:00
*** openstack changes topic to " (Meeting topic: Dragonflow)"09:00
openstackThe meeting name has been set to 'dragonflow'09:00
dimakHello all09:00
xiaohhuihi09:00
oansondimak, xiaohhui, hi09:00
irenabhi09:00
oansonirenab, hi09:00
oansonWe'll wait another minute, and then start09:00
nick_mahi all09:01
dimakI see we branched Ocata, 🎉09:01
oansonnick_ma, hi09:01
oansondimak, don't ruin the surprise! :)09:01
oanson#info itamaro dimak xiaohhui irenab nick_ma are in meeting09:02
oanson#topic Announcements09:02
*** openstack changes topic to "Announcements (Meeting topic: Dragonflow)"09:02
*** sshnaidm|off is now known as sshnaidm09:02
oansonFirst off, a big welcome to xiaohhui, who should now be a core09:02
oansonI say should, because I am not sure I updated the correct list :)09:02
nick_maconglats!!~~09:03
oansonSo xiaohhui, if your core powers are activated, let me know09:03
dimakCongratulations!09:03
ishafranHi09:03
xiaohhuiThanks guys!09:03
oansonWith great power comes great responsibility, so please try not to delete the project :)09:03
xiaohhuiIt seems not work now.09:03
itamarocongrats09:03
xiaohhuiI will try...09:04
*** joedborg has joined #openstack-meeting-409:04
xiaohhuitry not..09:04
irenabxiaohhui, congrats!09:04
oansonI updated the list about 10 minutes ago. If withing 24 hours it isn't working, I'll contact the infra guys for help09:04
oansonwithin*09:04
xiaohhuiThanks irenab09:04
nick_maxiaohhui: i checked the dragonflow-core list, you are there.09:05
oansonSecond item is, like dimak said, the new tag (3.0.0) and branch (stable/ocata) for Dragonflow is out09:05
xiaohhuiOK, thanks nick_ma09:05
xiaohhuiDoes that mean we need to cherry-pick patches to ocata branch?09:06
oansonThere are some things that I think should be backported: lihi's ipv6 work, itamaro's l2 refactor (I was contacted and asked to have it backported)09:06
oansonYes. Patches that were merged and we want in ocata should be cherry picked09:06
nick_maok.09:07
oansonThe branch mainly exists for 2 reasons: The Openstack-Ansible deployment patch was merged, and I wanted to make sure the matching Dragonflow version was tagged09:07
oansonThe second reason is that I want to start merging dimak's NB refactor, including migration, and I wanted to have a stable version without it09:07
dimakI see one of the patches is already in09:08
dimakHooray09:08
oansonThe tag took place about 24 hours ago, with commit tag: Add rate limiter to icmp handler(DNAT)09:09
nick_mathat's reasonable. currently there are too many big patches there.09:09
irenaboanson, what feature are included?09:09
oansonirenab, anything that was merged till yesterday :)09:09
dimakAre we going to have release notes?09:10
*** gongysh has joined #openstack-meeting-409:10
oansondimak, only if someone writes them.09:11
oansonWe should start keeping track from this point on09:11
oansonThat is, any patch that changes API, adds a feature, or changes deployment, should have a release not09:11
oansonnick_ma added the reno framework, so it should be easy to do that from now on09:12
irenabnote?09:12
nick_mayes09:12
oansonirenab, sorry?09:12
xiaohhuiThat could be applied to the review process, right?09:12
irenabnver mind, was not sure if you mean not ore note09:12
oansonxiaohhui, yes09:13
oansonirenab, yes, 'note'09:13
oansonAnything else here?09:14
oanson#topic Roadmap09:14
*** openstack changes topic to "Roadmap (Meeting topic: Dragonflow)"09:15
oansonIPv6 - lihi uploaded a WIP here: https://review.openstack.org/#/c/431566/ . She's out this week, and next week is the PTG, so I don't think she'll be able to update it again soon09:15
oansonExcept that she updated it this morning :)09:15
oansonSo I guess she is updating it09:16
*** acabot has joined #openstack-meeting-409:16
oansonThe patch adds IPv6 support to the security groups, which (I think) is the last big obstacle for IPv6 support09:16
irenaboanson, is it for review already?09:16
oansonIt fails py35, so only if you have time09:16
irenabok09:17
oansonNB refactor - dimak, you want to take this one?09:17
dimakI see that you took the first framework patch09:18
dimakI'm working mainly on SFC while using the framework as basis to weed out more issues09:18
*** rwallner has joined #openstack-meeting-409:18
dimakbut I didn't come across anything I hadn't fixed yet09:18
oansonThat's good09:18
dimakSo for now I'm waiting for more feedback09:19
dimakAnd keep focusing on SFC09:19
oansonYou also want to take this chance to talk about SFC?09:19
dimakI got it to work last week on a single node09:19
dimakWithout treating most of the edge cases09:19
irenabI have one comment about NB refactor09:19
oansonirenab, shoot09:20
dimakAnd I'm writing some tests now before I proceed with tackling the apps09:20
irenabone more patch is needed to add dev doc guide for adding new models09:20
dimakI'll draft one up :)09:21
irenabthanks09:21
oansonthanks09:21
*** hujie has joined #openstack-meeting-409:21
oansondimak, re sfc, what service functions are you testing?09:21
dimakI am working with a fullstack testing framework so I built something simple by using policy09:22
dimakits enough for now09:22
oansonCool09:22
dimakSimple packet modification and return to the next hop09:22
dimakor SF09:22
dimakI'll upload the tests sometime today, everyone can take a look09:23
*** rwallner has quit IRC09:23
oansonVery cool!09:23
oansonAnything else for NB refactor and SFC?09:23
dimakNothing for now09:23
oansonAll right.09:24
oansonAs far as I know, there is no update regarding TaaS and chassis/service health09:24
oansonAnonymous/distributed snat - ishafran, you want to take this?09:24
ishafranok09:24
ishafranI have 2 ongoing code reviews09:25
ishafranone is in more mature state09:25
ishafranhttps://review.openstack.org/#/c/431422/09:25
ishafranI need to make small functional changes hopefully today for both patches09:25
ishafranAnd I will be ready for next review cicle09:26
ishafranquestions ? :)09:26
dimakI'll take another look at the patches today09:27
oansonSounds good09:27
*** rfolco has joined #openstack-meeting-409:27
irenabregarding the https://review.openstack.org/#/c/431423/09:27
oansonishafran, if you're respinning, could you also add a release note?09:27
ishafrannote in commit itself ?09:28
irenabWe discussed the approach at the previous patch, but my concern is still present. I do not think that the sNAT change should be reflected durectly in the ml2 mech_driver09:28
oansonishafran, using 'reno', you can create a release note file. I want it to mention the new feature, as well as that it requires OVS 2.609:29
ishafranirenab: yes I remember this. We need a time to talk about it09:29
oansonbut this can be done in another patch, so as not to delay this one09:29
irenabanother concern is about modifing the port object with port profile stuff that is not present in neutron, but sent to DF09:29
irenabishafran, great. Lets chat after the meeting09:30
irenabjust wanted to see if there are more opinions on this09:30
ishafranirenab: for the profile change. its DF specific feature so I don't see a problem there09:30
irenabishafran, consider the case where we need to align DF DB with neutron one09:31
*** neiljerram has joined #openstack-meeting-409:31
ishafranthis is a very long shot :)09:32
irenabit may happen due to some cases where DF DB is out of sync, and we could use sync DB utility to align both, but adding neutron side applicative logic, will make it difficult09:32
oansonishafran, I don't think it's such a long shot09:33
oansonAnd being able to do so adds stability to our system09:33
ishafranupdating neutron DB cause kind of recursive update ... lets talk about it09:34
oansonSure. We can take it offline09:34
irenabishafran, I would prefer not changing port object at all09:34
irenabsure, let discuss offile09:35
oansonThat gets us to the API feature09:35
nick_maimo, if we don't check the port object, it should be no problem.09:35
nick_mas/check/change09:35
oansonYes. That info has to be placed somewhere, but I agree the port object shouldn't be modified09:37
oansonirenab, you want to talk about the API?09:37
irenaboanson, yes09:37
irenabnothing to update actually. The spec is up to review. I added few clarifications based on the recent reviews09:38
oansonNote, the spec is here: https://review.openstack.org/#/c/418842/09:38
irenabPlease check if there are some missing requirements that to be added09:38
oansonirenab, will the api be pending migration to the new NB? i.e. change the models like in the 'chassis' case?09:39
irenaboanson, yes09:39
*** yuli_s has joined #openstack-meeting-409:40
yuli_shello09:40
irenabit does not make sense to base on the previous modesl. json models can be helpful for the automation of the API processing09:40
oansonyuli_s, hi09:40
oansonirenab, all right09:40
oansonWe should get an etherpad up with the modules that have to be migrated.09:41
oansonOnce someone takes a model, put your name next to it. Once it is merged, we'll strike-through the model name09:41
dimakThats a good idea09:41
nick_magood idea.09:41
irenab+1\09:41
oansondimak, you want to create the etherpad?09:41
dimakSure, I'll do that today09:42
oansonGreat. Post a link in the channel once you have a link, so it'll be recorded somewhere09:42
oansonyuli_s, you arrived just in time. Want to talk about TaaS?09:42
dimakOk09:42
yuli_sI created a very simple plugin09:43
yuli_sthat receives taas events09:43
yuli_sI started to port it to use the new API that Dima is working09:43
yuli_son09:44
oansonThat's a good idea.09:44
yuli_sbesides I was working a new performance test project09:44
irenabyuli_s, new plugin on the neutron or DF side?09:45
*** Julien-zte has quit IRC09:45
yuli_sit should work in both cases09:46
irenabon neutron I believe it should be new driver for the TaaS plugin09:46
yuli_sthe one that receives messages should push them to db using new API09:46
yuli_sand the implementation part that applies the rules09:47
irenabyuli_s, link to the patch?09:47
yuli_srunning as part of df process09:47
yuli_sit is will not ready09:47
yuli_sas I had to switch to performance test project09:47
*** hwoarang has joined #openstack-meeting-409:47
irenabok, got it09:48
yuli_si found and fixed a number of small issues in multi-node deployment09:48
oansonThat reminds me, we need to see if we can set up a multinode gate09:48
dimakoanson, maybe we can use ODAD09:49
*** neiljerram has quit IRC09:49
dimakOSAD09:49
yuli_s2 patches had been merged already09:49
oansondimak, you're gonna have to give me more than an acronym :)09:49
dimakansible09:49
oansondimak, yes. That's one option that will definitely be added. I want to make sure we don't break the ansible deployment on our end as well09:50
irenabOSAD?09:50
oansonThat we don't cause a degradation, that is. Shouldd't be too difficult, as openstack-ansible already have a gate job running for us on openstack-ansible-os_neutron09:50
oansonOpen-Stack Ansible Deployment?09:51
dimakyes09:51
oansonIn any case, I am also thinking of taking up TripleO this cycle. This should allow us to test provider nets as well.09:51
irenaboanson, can you elaborate on TripleO?09:53
oansonMy understanding is that it's for running openstack on openstack09:53
irenabyes, it is. So what is your plan with regards to DF?09:54
oansonWe'll use the lower openstack deployment (it has a name, but I forgot it now) to set up the network for the upper openstack deployment (also has a name). The upper openstack deployment will be Dragonflow. The lower deployment will provide the network needed to have provider net (flat and vlan), VxLAN, and maybe dNAT and  sNAT.09:54
oansonYes, this took longer to write than I expected :)09:55
nick_mait can help you deploy neutron with dragonflow and check whether it is working for undercloud networking.09:55
oansonThat's also an interesting use case. I haven't thought of that09:55
oansonundercloud and overcloud. Those are the names :)09:56
nick_ma:-)09:56
*** lei-zh has quit IRC09:56
*** noops has joined #openstack-meeting-409:57
oansonOne more item, before we break off to dinner - next week there will be no meeting due to the PTG09:57
irenabthe undercloud can be DF network too09:57
oansonirenab, yes, that's what nick suggested.09:57
oansonThat would be a 2-in-1 testing environment :)09:57
irenaboanson, any update on VLAN aware VMs?09:57
oansonirenab, none as of yet. I'll try contacting rajivk offline. I didn't see him around lately09:57
noopsHey tomorrow ...do we have meeting?09:57
oansonThat means our next meeting is on the 27th of Feb., two weeks from now09:58
oansonI'll also send a reminder in the mailing list towards the end of the week09:59
*** amotoki has quit IRC09:59
oansonAll right, that's our time.09:59
oansonAnything last-minute?09:59
nick_maok.09:59
oansonGreat! Thanks, everyone!10:00
oanson#endmeeting10:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"10:00
openstackMeeting ended Mon Feb 13 10:00:09 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-02-13-09.00.html10:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-02-13-09.00.txt10:00
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-02-13-09.00.log.html10:00
*** nick_ma has quit IRC10:00
*** noops has quit IRC10:01
*** amotoki has joined #openstack-meeting-410:01
*** jamespage has joined #openstack-meeting-410:01
jamespageo/10:01
gnuoyo/10:02
jamespage#startmeeting charms10:02
openstackMeeting started Mon Feb 13 10:02:17 2017 UTC and is due to finish in 60 minutes.  The chair is jamespage. Information about MeetBot at http://wiki.debian.org/MeetBot.10:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.10:02
*** openstack changes topic to " (Meeting topic: charms)"10:02
openstackThe meeting name has been set to 'charms'10:02
jamespage#topic Review action points from previous meeting10:03
*** openstack changes topic to "Review action points from previous meeting (Meeting topic: charms)"10:03
jamespagejamespage    talk py27 retirement with tc as ptl10:03
jamespagenot done yet - will raise at PTG I think10:03
jamespagecholcombe    close out bugs against ceph-fs10:03
jamespagemostly done10:03
jamespagehowever the ceph-base layer needs work still prior to release10:03
jamespageceph-fs is a bit of a frankencharm atm10:03
jamespage#action cholcombe resolve ceph-fs/ceph-base layer usage overloading10:04
jamespagejamespage to send out etherpad link to list for charms planning for mon/tues10:04
jamespagedone10:04
jamespagehttps://etherpad.openstack.org/p/openstack-charms-ptg-pike10:04
jamespage#url https://etherpad.openstack.org/p/openstack-charms-ptg-pike10:04
jamespageall - brainstorm ideas so we can come up with a scheduler and objectives for the PTG10:04
jamespagethat needs some work still - I'd like to finalize the topic list by friday at the latest10:05
jamespagegnuoy, feels like just you and me here today :-)10:05
jamespageanyway10:05
jamespage#topic State of Development for next Charm Release10:05
gnuoyhaha, maybe10:05
*** openstack changes topic to "State of Development for next Charm Release (Meeting topic: charms)"10:05
jamespagefreeze was last thursday - a few features with exceptions are still in landing10:05
jamespagespecifically the cephx groups work (which has the widest impacT)10:06
*** tovin07 has quit IRC10:06
jamespagemost other things inflight are bug fixes10:06
jamespageso we'll aim to get in a ch-sync early this week10:06
jamespageworking towards 23rd February still for release10:06
jamespagebut nice to have everything baked this week so we can focus on the next cycle at the PTG10:06
gnuoyagreed10:06
jamespage#topic High Priority Bugs10:07
*** openstack changes topic to "High Priority Bugs (Meeting topic: charms)"10:07
*** ishafran has quit IRC10:07
jamespagewe currently have 8 critical and 72 high bugs open10:07
jamespagewe should aim to nail the critical ones for this release10:07
gnuoyyep10:08
jamespageok10:08
jamespageso moving on10:08
jamespage#topic Openstack Events10:08
*** openstack changes topic to "Openstack Events (Meeting topic: charms)"10:08
jamespagePTG next week - see most of you there (apart from gnuoy of course)10:08
* gnuoy sniff10:08
jamespageif you happen to be in Manchester, there is a meetup on Wednesday evening - despite being relatively local I can't make it due to other commitments10:09
jamespageI think that just about covers it - hope everyone that submitted talks for the summit in boston gets them accepted!10:10
jamespage#topic Open Discussion10:10
*** openstack changes topic to "Open Discussion (Meeting topic: charms)"10:10
jamespageanything else?10:10
gnuoyMaybe send out a reminder about this meeting?10:10
jamespageyeah good idea10:10
jamespageI think it would be wise to send a reminder on the friday before each meeting that its happening and at what time10:10
gnuoy+110:10
jamespage#action jamespage update meeting chair guidelines to send out notices for meetings10:11
jamespagegnuoy, anything else/10:11
jamespage?10:11
gnuoynot from me10:11
*** neiljerram has joined #openstack-meeting-410:12
jamespage#endmeeting10:14
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"10:14
openstackMeeting ended Mon Feb 13 10:14:32 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:14
*** rwallner has joined #openstack-meeting-410:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-02-13-10.02.html10:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-02-13-10.02.txt10:14
openstackLog:            http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-02-13-10.02.log.html10:14
gnuoythanks jamespage10:14
jamespagethanks all - until next week10:14
*** dims_ has quit IRC10:16
*** rwallner_ has joined #openstack-meeting-410:17
*** sdake has joined #openstack-meeting-410:18
*** rwallner has quit IRC10:19
*** rwallner_ has quit IRC10:21
*** jamespage has left #openstack-meeting-410:22
*** dims has joined #openstack-meeting-410:23
*** thorst_ has joined #openstack-meeting-410:23
*** salv-orl_ has quit IRC10:24
*** salv-orlando has joined #openstack-meeting-410:25
*** karthiks has joined #openstack-meeting-410:27
*** thorst_ has quit IRC10:28
*** ralonsoh_ has joined #openstack-meeting-410:30
*** ralonsoh_ has quit IRC10:32
*** ralonsoh_ has joined #openstack-meeting-410:32
*** ralonsoh has quit IRC10:33
*** chandanc__ has joined #openstack-meeting-410:39
*** chandanc_ has quit IRC10:42
*** portdirect_ has quit IRC10:53
*** rwallner has joined #openstack-meeting-410:58
*** sambetts|afk is now known as sambetts10:58
*** portdirect is now known as portdirect_10:58
*** portdirect_ is now known as portdirec10:59
*** portdirec is now known as portdirect_10:59
*** portdirect_ is now known as portdirect10:59
*** portdirect has joined #openstack-meeting-411:00
*** rwallner has quit IRC11:02
*** psachin has quit IRC11:08
*** chandanc__ has quit IRC11:08
*** hughhalf has quit IRC11:16
*** hughhalf has joined #openstack-meeting-411:18
*** sdague has joined #openstack-meeting-411:19
*** Julien-zte has joined #openstack-meeting-411:25
*** psachin has joined #openstack-meeting-411:25
*** penfold has joined #openstack-meeting-411:35
*** psachin has quit IRC11:39
*** hujie has quit IRC11:43
*** gongysh has quit IRC11:52
*** ralonsoh__ has joined #openstack-meeting-411:52
*** ralonsoh_ has quit IRC11:55
*** janki has quit IRC11:56
*** penfold has quit IRC11:57
*** penfold has joined #openstack-meeting-411:57
*** dave-mccowan has joined #openstack-meeting-412:05
*** pbourke has quit IRC12:08
*** pbourke has joined #openstack-meeting-412:09
*** psachin has joined #openstack-meeting-412:12
*** penfold has quit IRC12:13
*** rwallner has joined #openstack-meeting-412:20
*** dims has quit IRC12:23
*** rwallner has quit IRC12:25
*** SerenaFeng has quit IRC12:27
*** dave-mcc_ has joined #openstack-meeting-412:28
*** dave-mccowan has quit IRC12:30
*** sdake_ has joined #openstack-meeting-412:36
*** sdake has quit IRC12:39
*** sdake_ is now known as sdake12:48
*** thorst_ has joined #openstack-meeting-412:48
*** limao has joined #openstack-meeting-413:02
*** bobh has joined #openstack-meeting-413:05
*** bobh has quit IRC13:05
*** bobh has joined #openstack-meeting-413:05
*** armax has joined #openstack-meeting-413:08
*** rfolco has quit IRC13:18
*** dims has joined #openstack-meeting-413:20
*** rwallner has joined #openstack-meeting-413:21
*** klamath has joined #openstack-meeting-413:24
*** klamath has quit IRC13:24
*** klamath has joined #openstack-meeting-413:25
*** rwallner has quit IRC13:27
*** rwallner has joined #openstack-meeting-413:28
*** salv-orlando has quit IRC13:29
*** rosmaita_ has joined #openstack-meeting-413:30
*** bobh has quit IRC13:31
*** dolphm has quit IRC13:32
*** kevinbenton has quit IRC13:32
*** rosmaita has quit IRC13:32
*** dolphm_ has joined #openstack-meeting-413:32
*** rfolco has joined #openstack-meeting-413:32
*** dolphm_ is now known as dolphm13:33
*** rosmaita_ is now known as rosmaita13:34
*** kevinbenton has joined #openstack-meeting-413:35
*** yamamoto has quit IRC13:39
*** yamamoto has joined #openstack-meeting-413:41
*** dims_ has joined #openstack-meeting-413:43
*** dims has quit IRC13:45
*** yamamoto has quit IRC13:47
*** salv-orlando has joined #openstack-meeting-413:49
*** kylek3h has joined #openstack-meeting-413:55
*** yedongcan has joined #openstack-meeting-413:56
*** uck has joined #openstack-meeting-413:56
*** ralonsoh__ is now known as ralonsoh13:57
*** alraddarla has joined #openstack-meeting-413:59
*** amotoki has quit IRC13:59
*** garyloug has joined #openstack-meeting-414:00
*** gongysh has joined #openstack-meeting-414:00
apuimedo#startmeeting kuryr14:02
openstackMeeting started Mon Feb 13 14:02:20 2017 UTC and is due to finish in 60 minutes.  The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: kuryr)"14:02
openstackThe meeting name has been set to 'kuryr'14:02
apuimedoHello everybody and welcome to the weekly IRC kuryr meeting14:02
irenabhi14:02
apuimedoWho's here?14:03
mchiapperoo/14:03
alraddarlao/14:03
yedongcano/14:03
ltomasboo/14:03
garylougo/14:03
limao0/14:03
*** dave-mcc_ has quit IRC14:03
apuimedoWelcome :-)14:04
apuimedo#topic kuryr-libnetwork14:04
*** openstack changes topic to "kuryr-libnetwork (Meeting topic: kuryr)"14:04
*** beagles is now known as beagles-mtg14:05
apuimedo#info This week there continued to be improvements on the kuryr-libnetwork front and I think that we could release after the tagging situation is solved14:06
ltomasbohttps://review.openstack.org/#/c/42577214:06
ltomasbothis already have the +2s, missing W14:06
*** dave-mcc_ has joined #openstack-meeting-414:06
irenabapuimedo: want to take a look to approve?14:07
apuimedoah, good14:07
* apuimedo taking a fast look14:07
ltomasbo:D14:08
*** amotoki has joined #openstack-meeting-414:08
apuimedoltomasbo: irenab: so this patch gets rid of DEVICE_OWNER tag for kuryr-libnetwork altogether14:10
apuimedo?14:10
ltomasboactually, it leaves it14:10
ltomasbobut it does not use it later one14:10
irenabit keeps the owner, but uses tag to for filtering14:10
*** bobh has joined #openstack-meeting-414:10
ltomasbojust use tagging to find the nsubnets to be deleted after pod deletion14:10
apuimedoit keeps it or does it still set it as well14:11
apuimedo?14:11
ltomasbosets it14:11
apuimedook14:11
irenabset to compute:kuryr to be aligned with convention14:11
ltomasboas it was before this patch14:11
apuimedothen I think we can take this14:11
apuimedomerging14:11
apuimedoalright14:11
ltomasbothe compute:kuryr is in the kuryr-lib part14:11
ltomasbohttps://review.openstack.org/#/c/431091/14:12
apuimedoltomasbo: that means that we should also cut a new kuryr-lib release14:12
irenaband bump the requirements on kuryr-libnetworks14:13
apuimedoright14:13
*** cathrich_ has joined #openstack-meeting-414:13
ltomasboif you agree on changing the device_owner value...14:13
*** bobh has quit IRC14:13
apuimedoI do14:13
*** bobh has joined #openstack-meeting-414:13
apuimedothe problem is14:13
ltomasboit will work on kuryr-libnetworks regardless of the change anyway14:13
irenabright, its just alignment with naming convention14:14
apuimedofor people that upgrade, the filtering will be broken for already 'device_owner' marked resources14:14
apuimedosince we were before 1.0, I think we can live with this14:14
apuimedobut it's the last time14:14
apuimedonext times we'll have to do legacy checks14:15
irenabsince there is nothing that counts on the device owner name any more,it should not be a problem\14:15
irenabapuimedo: even more important to fix it now14:15
ltomasboright14:15
apuimedoalright. Let's set wednesday as freeze day for kuryr-lib and kuryr-libnework14:15
apuimedoand then we cut the release14:15
apuimedoagreed?14:15
irenab+114:15
*** cathrichardson has quit IRC14:15
apuimedolimao: yedongcan: hongbin ^^14:16
limao(if neutron do not support tag-ext, we still use device owner for filter port)14:16
apuimedoI'll request a 1.0.014:16
limao+114:16
yedongcan+114:16
apuimedoso that means that it's the first supported release14:16
ltomasbothe tag-ext patch was merged last week14:16
apuimedoltomasbo: also the backport?14:17
ltomasbothat I don't know14:17
irenablimao: maybe we need to check for ‘kuryr’ presence in OWNER field14:17
yedongcanbackport in neutron stable branch14:17
apuimedoif there are patches that you feel should be in. Please, bother the cores about getting them in by Wednesday 20:00utc14:17
apuimedoirenab: that's a very good point14:17
apuimedoltomasbo: can you patch that?14:17
limaoltomasbo: yes, I mean if user use kuryr in an openstack environment not support tag-ext14:17
ltomasbolimao, it should work the same way, there is an extra check in those cases14:18
irenabltomasbo: lets just make sure there is a test that covers the case14:19
*** hongbin_ has joined #openstack-meeting-414:19
apuimedolimao: please, check if you think https://review.openstack.org/#/c/432777/ should get into the release14:19
hongbin_o/14:19
ltomasboirenab, I've included unit test with and without tag-ext support14:19
irenabltomasbo: I mean the case limao raised14:20
apuimedohi hongbin_14:20
ltomasboirenab, https://review.openstack.org/#/c/425772/8/kuryr_libnetwork/tests/unit/test_kuryr_ipam.py14:20
apuimedowe were saying that we'll cut a 1.0.0 release of kuryr-libnetwork14:20
irenabltomasbo: great14:20
limaoapuimedo: ok, I will check14:20
ltomasboirenab, let me know if you were thinking about some extra tests14:20
apuimedo#info kuryr-libnetwork 1.0.0 freeze active Wednesday 20:00utc14:20
apuimedohongbin_: ^^14:21
irenabltomasbo: sure14:21
hongbin_apuimedo: ack14:21
*** cdelatte has joined #openstack-meeting-414:21
apuimedohongbin_: I know you have some patches, so please work with the cores to try and get those that should make the release in14:22
hongbin_apuimedo: i will try that14:22
apuimedo@all: remember that we are release independent, so we are flexible. But we should patch for critical issues at least the previous released version14:23
apuimedoso we can't get too crazy with the amount of releases14:23
apuimedoAnything else on kuryr-libnetwork?14:23
*** cathrich_ has left #openstack-meeting-414:23
limaoapuimedo: https://hub.docker.com/r/kuryr/libnetwork/14:24
limaoyour Source Repository has not updated for some time, will we plan to maintain this docker image?14:25
*** hongbin__ has joined #openstack-meeting-414:25
irenablimao: apuimedo : maybe we should consider hosting the image in some more ‘official’ repo?14:26
apuimedolimao: we need to for the 1.0.0 release. yes14:26
apuimedo#action apuimedo to fix https://hub.docker.com/r/kuryr/libnetwork for the release14:26
apuimedoirenab: not possible yet. Infra does not have its own repository14:26
limaoapuimedo: irenab: I think toni want to use the auto build on hub.docker14:27
apuimedobut I would love it14:27
irenabok, the docker hub seems a good option for now14:27
apuimedolimao: yes. I like the auto build. It makes it immediate for people to see how things were built14:27
limaoapuimedo: agree, nothing more about kuryr-libnetwork from me now14:28
apuimedovery well14:28
apuimedothanks a lot for bringing it up limao!14:28
*** hongbin_ has quit IRC14:29
apuimedo#topic fuxi14:29
*** openstack changes topic to "fuxi (Meeting topic: kuryr)"14:29
hongbin__o/14:29
apuimedo#chair hongbin14:29
openstackCurrent chairs: apuimedo hongbin14:29
apuimedogo ahead14:29
apuimedo;-)14:29
hongbin__i don't have too much to update this week14:29
hongbin__if you have any topic to discuss, please feel free to bring it up14:29
*** gongysh has quit IRC14:29
*** beagles-mtg has quit IRC14:30
apuimedohongbin__: please review https://review.openstack.org/#/c/430658/114:30
hongbin__apuimedo: ack14:31
hongbin__#action hongbin review https://review.openstack.org/#/c/430658/114:31
apuimedoand https://review.openstack.org/#/c/431085/14:31
hongbin__done14:31
apuimedothanks hongbin__14:31
apuimedohongbin__: I would also like to ask you to lead the VTG session on Fuxi14:32
hongbin__apuimedo: sure, i can do that14:32
apuimedoit will be about fuxi, fuxi-kubernetes and plans for release14:32
apuimedothanks hongbin14:32
apuimedo#topic kuryr-kubernetes14:32
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)"14:32
hongbin__my pleasure14:32
* apuimedo updating document14:33
*** tonytan4ever has joined #openstack-meeting-414:34
apuimedo#info ivc_'s patch that improves the handling of resourceVersion conflicts was taken in14:35
apuimedo#info A videoconf meeting about resource management took place last thursday: https://www.youtube.com/watch?v=3698DBV-Ng414:35
apuimedo#info In the resource management meeting it was agreed to work on feature parity between baremetal (by reusing both ports and veths) and nested (reusing just ports)14:37
apuimedoltomasbo is leading the way14:37
apuimedoltomasbo: did you get around to trying it with nested?14:37
ltomasboI committed a newer version last friday14:37
ltomasbowith the min and max number of ports at the pool14:37
*** amotoki has quit IRC14:37
ltomasboas we were discussing14:37
ltomasboas well as reusing created ports, by reseting the security-group and the name to the default one14:38
apuimedo#info vikasc has demonstrated ivc's service patches to work with pods-in-VMs. A demo will be shared by the end of the week on the mailing list14:38
ltomasboI also updated the nested version, but I still need a decent server to test it and measure the performance for the nested case14:38
apuimedomore info: the max number of ports is about limiting the amount of ports that are kept in the pool. So if you have the pool full, you delete the resource instead of pooling it14:39
apuimedoltomasbo: very well14:39
*** Guest69121 has joined #openstack-meeting-414:39
ltomasboyes, you define a max number of ports14:39
ltomasboper pool14:39
ltomasboand then, if the pool is already full, then the port gets deleted instead of returned to the pool14:40
irenabltomasbo: apuimedo what about the spec we discussed?14:40
ltomasboalso, there is a batch variable, to create ports/subports in batches, as it is more efficient14:40
irenabto capture the oevrall plan and steps14:40
apuimedoirenab: you mean the spec about the pool namespace?14:41
apuimedosorry14:41
apuimedobp14:41
irenabyes, bp14:41
apuimedo#action apuimedo to submit the blueprint for resource management14:41
irenabit will be helpful to see the overal plan and various steps to achive performance goals14:41
apuimedoindeed14:42
*** yamamoto has joined #openstack-meeting-414:44
apuimedogood14:44
*** uck has quit IRC14:44
apuimedoanything else on kuryr-kubernetes?14:45
*** cathrichardson has joined #openstack-meeting-414:45
apuimedoalraddarla: you are on the devref moving, right?14:45
*** galstrom is now known as galstrom_zzz14:45
alraddarlaapuimedo, yes.14:45
alraddarlasorry for the delay...my laptop got messed up and had to wipe it and put a new OS on it. I can get that push up today14:46
apuimedono worries14:46
*** HenryG has quit IRC14:46
apuimedojust following-up in case you had any further doubts on the parts that needed to be ported and merged14:46
janonymouso/14:46
apuimedoand those that had to be dropped14:46
* janonymous got a bit late14:46
alraddarlaI will let you knwo if I have more questions once I actually move everything around14:47
apuimedojanonymous: you can ask after going over the logs in the channel if you have questions ;-)14:48
apuimedoperfect alraddarla14:48
apuimedo#topic general14:48
*** openstack changes topic to "general (Meeting topic: kuryr)"14:48
*** kylek3h has quit IRC14:48
apuimedo#info I updated the VTG schedule and sessions https://etherpad.openstack.org/p/kuryr_virtual_gathering_2017h114:49
*** yamamoto has quit IRC14:49
apuimedo#action apuimedo to move it to the wiki14:49
*** HenryG has joined #openstack-meeting-414:49
apuimedoThere's still some orphan sessions14:50
apuimedobut I'll be contacting some of you to ask for session steering14:50
apuimedo;-)14:50
*** pcaruana has quit IRC14:50
apuimedoplease, let me know about important time conflicts14:50
apuimedoIs anybody going to atlanta?14:51
apuimedothere will be a session about tripleo/kolla integration on Wednesday14:51
apuimedolet me hunt for the time14:51
apuimedo#info There will be a PTG meeting in Atlanta about Kolla/Tripleo + kuryr http://lists.openstack.org/pipermail/openstack-dev/2017-February/111950.html14:53
apuimedo#link https://ethercalc.openstack.org/Pike-PTG-Discussion-Rooms14:53
*** baoli has joined #openstack-meeting-414:53
apuimedoanything else anybody?14:54
yedongcanapuimedo: please see these patch: https://review.openstack.org/#/c/429432/14:54
yedongcanhttps://review.openstack.org/#/c/429329/14:55
yedongcanhttps://review.openstack.org/#/c/431844/14:55
yedongcanhttps://review.openstack.org/#/c/431312/14:55
apuimedo#action apuimedo to review https://review.openstack.org/#/c/429432/ https://review.openstack.org/#/c/429329/ https://review.openstack.org/#/c/431844/ https://review.openstack.org/#/c/431312/14:55
*** pcaruana has joined #openstack-meeting-414:55
yedongcanI just sort these, and think it can merged before we released.14:55
apuimedothanks yedongcan. I will!14:56
apuimedoalright14:56
apuimedoclosing the meeting!14:56
apuimedoTHank you all for joining14:56
apuimedo#endmeeting14:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:56
openstackMeeting ended Mon Feb 13 14:56:33 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-02-13-14.02.html14:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-02-13-14.02.txt14:56
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-02-13-14.02.log.html14:56
*** zerick_ is now known as zerick14:56
*** dave-mcc_ has quit IRC14:57
*** alraddarla has left #openstack-meeting-414:58
*** mfedosin has quit IRC14:59
*** chandanc__ has joined #openstack-meeting-414:59
*** limao has quit IRC14:59
sigmavirus#startmeeting craton15:00
openstackMeeting started Mon Feb 13 15:00:09 2017 UTC and is due to finish in 60 minutes.  The chair is sigmavirus. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: craton)"15:00
openstackThe meeting name has been set to 'craton'15:00
sigmavirus#chair jimbaker sulo15:00
openstackCurrent chairs: jimbaker sigmavirus sulo15:00
*** thomasem has joined #openstack-meeting-415:00
*** limao has joined #openstack-meeting-415:00
*** jose-phillips has joined #openstack-meeting-415:00
*** rbak has joined #openstack-meeting-415:00
*** anilvenkata has quit IRC15:00
*** mfedosin has joined #openstack-meeting-415:00
sigmavirus#info There is no agenda for this meeting this week15:00
thomasemo/15:00
sigmavirus    #link https://etherpad.openstack.org/p/craton-meetings15:01
sigmavirusdamnit15:01
*** garyloug has left #openstack-meeting-415:01
sigmavirus#link https://etherpad.openstack.org/p/craton-meetings15:01
sigmavirus#topic Roll Call15:01
*** openstack changes topic to "Roll Call (Meeting topic: craton)"15:01
jimbakersigmavirus, properly, there is no unique agenda for this meeting15:01
sigmavirus(now you should wave thomasem)15:01
jimbakero/15:01
thomasemo/ o/15:01
sigmavirusjimbaker: most teams will have a basic format which people add items to15:01
sigmavirusHence creating a semi-unique agenda15:01
* sigmavirus shugs15:01
sigmavirusWe're barely a team though15:01
jimbakerworking on it15:02
sigmavirussulo: git-harry?15:02
thomasemI think sulo's out15:03
jimbakerthat was sulo's communication from earlier today - he is out for the entire week15:03
*** cjloader_ has joined #openstack-meeting-415:03
*** cathrichardson has left #openstack-meeting-415:03
sigmavirusAh, I did not receive that email15:03
* sigmavirus assumes it was an email15:03
*** kylek3h has joined #openstack-meeting-415:04
jimbakerit was on irc15:04
sigmavirusAh. Okay. (Still haven't read this morning's scrollback either)15:04
jimbakerand folks if you are going to be out, i would like to know about it15:04
jimbakerit does help on the planning15:04
jimbakeryour manager knows. i do not know15:04
*** FrankZhang has joined #openstack-meeting-415:04
*** git-harry has joined #openstack-meeting-415:05
sigmaviruso/ git-harry15:05
git-harryapologies all, I lost track of time.15:05
jimbakergit-harry, must be in flow15:05
sigmavirus#info We should all treat jimbaker as our manager and inform him of all time off taken15:05
sigmavirussecondary manager?15:06
sigmavirusassistant to the regional manager?15:06
thomasemAssistant to the regional manager15:06
thomasemAH!15:06
thomasemsigmavirus!15:06
sigmavirusjinx15:06
jimbakersomething like that :)15:06
git-harrywe have a calendar for that internally15:06
jimbakerfarid will be joining us end of month, at which point he can take on that responsibility15:06
sigmavirusgit-harry: so while our corporate diversity is currently quite poor, that won't work for long15:07
jimbakergit-harry, also awesome, i have never seen that calendar15:07
sigmavirusMoving along15:08
*** beekneemech is now known as bnemec15:08
jimbakeranyway, it's atypical for me to kvetch15:08
sigmavirus#topic Action Items From Last Monday's Meeting15:08
*** openstack changes topic to "Action Items From Last Monday's Meeting (Meeting topic: craton)"15:08
sigmavirus#link http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-02-06-15.00.html15:08
sigmavirusjimbaker: should we carry forward the doc -> etherpad task?15:09
*** cgoncalves has quit IRC15:09
jimbakersigmavirus, yes, this got caught up in the best process of doing so15:09
sigmavirus#action jimbaker to turn dusty's doc into an etherpad15:09
sigmavirus#action jimbaker once the etherpad is created, add reviewing it as a standing item to our meeting template15:09
sigmavirusgit-harry: thomasem did either of you decide who should write the spec we discussed last week?15:10
*** cgoncalves has joined #openstack-meeting-415:10
thomasemyes. I will.15:10
jimbakeretherpad. launchpad. waffle. back to launchpad. how to split15:10
*** anilvenkata has joined #openstack-meeting-415:10
sigmavirus#action thomasem to write the spec discussed in last Monday's meeting15:10
sigmavirusI'm still working on my action item, so I'll carry that forward15:10
sigmavirus#action sigmavirus to update pagination API work to add functional tests now that sulo's work has landed15:10
thomasemI'd like to discuss that, jimbaker, in open discussion.15:10
sigmavirus#action sigmavirus to finish up testing on cli15:10
jimbakerthomasem, +115:10
sigmavirusthomasem: add it to the agenda? https://etherpad.openstack.org/p/craton-meetings15:11
thomasemon it15:11
*** salv-orlando has quit IRC15:11
*** dave-mccowan has joined #openstack-meeting-415:11
sigmavirusthomasem: did you get around to making a blueprint for the deployment docs?15:11
*** salv-orlando has joined #openstack-meeting-415:11
*** Guest69121 is now known as beagles15:11
jimbakersigmavirus, i would like to discuss the CLI testing later in today's meeting15:11
thomasemI did not, I'm afraid. Can we carry that forward?15:12
sigmavirus#action thomasem to create BP, with initial thoughts, regarding suggested production deployment documentation15:12
sigmavirusthomasem: everything is carry-forwardable ;)15:12
sigmavirusjimbaker: add it to the agenda?15:12
thomasemExcellent15:12
sigmavirusNote, this is why we review those items :)15:12
jimbakersigmavirus, +1 to agenda add, if that works for you15:12
sigmavirusjimbaker: gopherit15:12
jimbakerindeed, we can all edit :)15:12
sigmavirus#link http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-02-09-17.02.html15:13
sigmavirusThere were no action items added on Thursday15:13
sigmavirusSo, moving along15:13
sigmavirus#topic Stand-Up15:13
*** openstack changes topic to "Stand-Up (Meeting topic: craton)"15:13
sigmavirus#info each team member briefly describes what they are working on this week, and describes blockers (if there are any)15:14
sigmavirus#topic Stand-Up :: git-harry15:14
*** openstack changes topic to "Stand-Up :: git-harry (Meeting topic: craton)"15:14
*** yedongcan has quit IRC15:15
git-harrycurrently the only task I have for the week is https://bugs.launchpad.net/craton/+bug/166249615:15
openstackLaunchpad bug 1662496 in craton "Host response is missing parent_id property" [High,New] - Assigned to git-harry (git-harry)15:15
sigmavirus#link https://bugs.launchpad.net/craton/+bug/166249615:15
sigmavirusgit-harry: any blockers?15:15
git-harryThis was something sulo asked me to pick up while he's off.15:15
git-harryNope15:15
git-harryDone15:15
jimbakergit-harry, +115:15
sigmavirus#topic Stand-Up :: thomasem15:16
*** openstack changes topic to "Stand-Up :: thomasem (Meeting topic: craton)"15:16
thomasemFixing up Project vars patch (almost done) to work with jimbaker's fix for variable delete15:16
thomasemThen the CLI changes are awaiting jimbaker's patch for get/set vars for other resources15:16
*** jose-phillips has quit IRC15:16
thomasemworking on adding cloud resource, which will also have vars support and such15:17
*** hongbin__ has quit IRC15:17
thomasemand continuing to mosy through the review queue in between things15:17
thomasemdone15:17
*** jose-phi_ has joined #openstack-meeting-415:17
sigmavirus#topic Stand-Up :: jimbaker15:17
*** openstack changes topic to "Stand-Up :: jimbaker (Meeting topic: craton)"15:17
jimbakerunblock thomasem. this includes finalizing variable delete change, which thomasem likes, except for some overly strong tests. so we will negotiate on exactly what those are after this meeting15:18
jimbakeralong with finalizing the get/set/delete vars client/CLI work15:19
*** Syed__ has joined #openstack-meeting-415:19
jimbakerrefactor alembic is next; then finally start getting rbac going to WIP15:19
jimbakerand in general, hope to see us having a useful project state done in the next 2 weeks so we can work with antonym and team when they are back15:20
jimbakerdone15:20
sigmavirus#topic Stand-Up :: sigmavirus15:20
*** openstack changes topic to "Stand-Up :: sigmavirus (Meeting topic: craton)"15:20
sigmavirusStill hacking on tests round-robin when I get time between other tasks.15:20
sigmavirusI'm blocked by not being able to get some things off my plate =P15:21
sigmavirusLooking into cloudnull's cruton rewrite to see if there's anything to learn from that15:21
sigmavirusDone.15:21
cloudnull:)15:21
cloudnullo/15:21
sigmavirus#topic This Week's Priorities15:21
*** openstack changes topic to "This Week's Priorities (Meeting topic: craton)"15:21
Syed__o/15:21
sigmavirusWelcome Syed__15:22
sigmavirus#undo15:22
openstackRemoving item from minutes: #topic This Week's Priorities15:22
sigmavirus#topic Stand-Up :: Syed__15:22
*** openstack changes topic to "Stand-Up :: Syed__ (Meeting topic: craton)"15:22
jimbakercruton? love it15:22
Syed__Haha15:22
cloudnullhttps://github.com/cloudnull/cruton yw15:23
Syed__well i have been working over some patches which are in reviews, need to add functional testing for Craton Projects and Users update calls15:23
Syed__apart from that, will be taking over few more things this week from launchpad15:23
Syed__thats all from my side :)15:24
sigmavirusI don't see Jovon, so I'll move on to the next topic15:25
sigmavirus#topic This Week's Priorities15:25
*** openstack changes topic to "This Week's Priorities (Meeting topic: craton)"15:25
Syed__thanks ian15:25
sigmavirusLet's try to figure out what we as a group of developers want to prioritize to get done this week15:25
sigmavirusYou're welcome Syed__. I'm sorry I didn't see you sneak in :)15:25
jimbakerso toan has challenged us a team to see if we are ready for what the rackspace tiger team needs in terms of tooling15:26
jimbakerin one corner, craton15:26
jimbakerin the other corner, cruton15:26
Syed__cruton and craton are two diff things :/15:27
sigmavirusWell that makes it the 10th rewrite of the thing Rackers call CORE then ;)15:27
Syed__need to look into cruton, will do that after meeting15:27
git-harryjimbaker: what does that mean in practise?15:27
jimbakerwhy it wasn't named crouton, cloudnull would have to explain15:27
jimbakergit-harry, in practice it means for craton15:28
cloudnullthere's a project called crouton already for chrome books15:28
jimbakercloudnull, yep15:28
jimbakerback to git-harry15:28
cloudnullso i used cruton which is crouton from urban dictionary15:28
jimbakerfor craton: does our stuff actually work as advertised? so full client support of what is in the schema, including parent-child support15:29
cloudnullhttp://www.urbandictionary.com/define.php?term=cruton&defid=482011015:29
cloudnullanyway.15:29
*** dave-mccowan has quit IRC15:29
*** farid has joined #openstack-meeting-415:30
* cloudnull goes back doing something else15:30
jimbakerthe second definition for cruton works better15:30
cloudnullhttp://www.urbandictionary.com/define.php?term=cruton&defid=137165215:30
jimbakerurban dictionary just keeps on going, doesn't it?15:31
cloudnullit does15:31
thomasemsec15:31
cloudnullok, done for real15:31
jimbakerok, i don't see this discussion as a high priority item15:31
jimbakereven though it's infinitely amusing15:31
git-harryjimbaker: when does that need to be done?15:32
jimbakergit-harry, we have 2 weeks15:32
git-harryof the bugs in launchpad, are all the required ones currently marked high priority or tagged in someway?15:33
jimbakerand we are going to go against dusty's requirements, plus the modeling that cloudnull out together15:33
*** dave-mccowan has joined #openstack-meeting-415:33
jimbakergit-harry, that would be an awesome thing to do15:33
jimbakerand i encourage everyone to put some time in doing so15:34
sigmavirusjimbaker: into marking the required ones in some way?15:34
jimbakersigmavirus, yes15:34
sigmavirusBecause, I have no visibility into that besides what would end up in launchpad15:34
git-harryokay, so would it be fair to say that as it stands we don't know the scope of the remaining work?15:34
jimbakersigmavirus, so i will put dusty's doc in launchpad15:34
thomasemgit-harry: I think so.15:35
jimbakergit-harry, did you get dusty's doc?15:35
thomasemWe have a general idea, but not concrete steps.15:35
jimbakerthomasem, that is understandable15:35
git-harryYes, but I don't find it particularly helpful in determining what's left.15:35
jimbakergit-harry, and more of the same15:36
git-harryassuming we're talking about the doc from last year.15:36
jimbakergit-harry, a simplified version was distributed last week and discussed on tues iirc15:36
thomasemFurthermore, the doc in question has some things outside of the scope of Craton identified.15:36
thomasemAnd other things that we talked about being out-of-scope for this 2 week timeframe being referred to, but none of that is documented anyway, afaict.15:37
thomasems/anyway/anywhere/15:37
git-harryjimbaker: that was probably done in one of the last minute meetings15:37
jimbakerso our chance to do just that15:37
thomasemSo, I'd say the actual scope is pretty vlurry15:37
thomasemblurry*15:37
jimbakerthomasem, i wish i had the magic sharpener15:37
thomasemLol, yep15:37
jimbakerbut i don't15:37
*** galstrom_zzz is now known as galstrom15:38
sigmavirusjimbaker: can you at least zoom and enhance for us? =P15:38
jimbakersigmavirus, let's go back to the demo we had two weeks ago. if we deliver that without sharp edges, i think we are good15:38
jimbakerand project -> cloud -> region15:39
jimbaker...15:39
sigmavirusWhich demo? The one I wasn't invited to or the one I wasn't invited to?15:39
thomasemShared devices sounds out of scope15:39
sigmavirusWere either of them recorded at least?15:39
jimbakerthomasem, yes15:39
jimbakersigmavirus, the first was held in the vidyo meeting we have every tues15:39
jimbakertojuvone for example attended that meeting15:40
thomasemI do suspect we'll have more trouble getting patches landed with sulo out, btw.15:40
sigmavirusRight, I had a different meeting during that one and didn't make it :/15:40
jimbakerthomasem, i may have to +2 my own stuff. it's ok15:40
sigmavirusjimbaker: link me to priority stuff and I'll prioritize that over testing15:41
* thomasem didn't hear that15:41
*** kylek3h has quit IRC15:41
jimbakerthomasem, yep. but i also didn't know about sulo's being out until this morning15:41
sigmavirusthomasem: i'm glad. This is IRC, it shouldn't be talking to you =P15:41
*** kylek3h has joined #openstack-meeting-415:42
thomasemsigmavirus: now you know my secret15:42
*** galstrom is now known as galstrom_zzz15:42
thomasemjimbaker: understood15:42
thomasemsame here15:42
thomasemAnyway, not trying to be Debbie Downer. Wanting to be sure we keep our expectations grounded.15:43
jimbakerthomasem, yes, i was thinking about the same thing just now15:43
*** Jeffrey4l__ is now known as Jeffrey4l15:44
*** psachin has quit IRC15:44
jimbakerso that's my emphasis - if we show what we demoed, and it works as expected, i think we are good15:44
*** kylek3h_ has joined #openstack-meeting-415:44
jimbakerplus the parent-child stuff15:44
thomasemAlright, so, to enumerate:15:45
jimbakerbut that's just a matter of properly exposing what's already there15:45
thomasem1. parent-child stuff in working state15:45
thomasemWhich the remaining thing is what's on git-harry's plate?15:45
git-harry^ I've picked that up with https://bugs.launchpad.net/craton/+bug/166249615:45
openstackLaunchpad bug 1662496 in craton "Host response is missing parent_id property" [High,New] - Assigned to git-harry (git-harry)15:45
git-harryyep15:46
thomasemsweet15:46
thomasem2. adding cloud resource and project variables15:46
thomasemlet's break those apart15:46
*** kylek3h has quit IRC15:46
thomasem2. adding project variables15:46
thomasem3. adding cloud resource15:46
jimbakerand ideally it's a bit more than making parent_id visible - it should be ergonomic as well15:46
thomasemBoth #2 and #3 require CLI support as well.15:46
jimbakerand exposed to the python client/CLI15:47
thomasemOkay, all of these assume support in API and CLI15:47
jimbakerit's cleaned up. json works15:47
thomasemand 4. polish15:47
jimbakerespecially #415:47
git-harry5. spit15:47
thomasemSo, taking some time toa audit the calls weknow should work15:47
jimbakeryes15:47
thomasemto audit*15:47
thomasemand filing bugs for what doesn't work15:47
* thomasem crosses fingers15:48
Syed__+!15:48
Syed__+1 for filing bugs15:48
jimbakerif we get that done, we are good15:48
jimbakerpolish and spit, simple enough15:48
thomasemFeels do-able, though I fear Hofstadter's will bite us.15:48
thomasemLet's see what happens!15:49
jimbakeryep, that's what we have been experiencing for a month or so15:49
thomasemjimbaker: when you say especially #4, are you suggesting we ought to prioritize polish over the others?15:49
jimbakerthomasem, so #4 is prioritized over stuff like device sharing or rbac15:49
*** cjloader_ has quit IRC15:49
thomasemOkay, but not the ones before it (1-3)?15:50
*** sneti_ has joined #openstack-meeting-415:50
jimbakerwe have to the basic functionality :)15:50
jimbakerhave to have15:50
thomasemSo, then, would it be safe to say my enumeration above is reflective of the priorities we wanted to get out of this topic?15:50
*** cjloader_ has joined #openstack-meeting-415:50
*** sneti_ has quit IRC15:50
thomasemin the correct order15:50
*** anilvenkata has quit IRC15:50
git-harryWhat about the pagination stuff, is that a priority for the next two weeks?15:50
jimbakerthomasem, i agree with this enumeration15:50
thomasemExcellent15:50
jimbakergit-harry, no. it's super important work15:51
jimbakerbut it has NOT come up in these discussions15:51
*** marst has quit IRC15:51
jimbakereveryone expects that we are the long term solution15:51
jimbakerthe question is: can we be the short term solution as well15:51
jimbaker?15:51
sigmavirusjimbaker: we can't be everything to everyone15:52
thomasemThe goal being to get actual runtime with this thing and have real use-cases from organic use driving our continued development15:52
thomasemis my understanding15:52
jimbakersigmavirus, i agree. we but we can be something for someone15:52
jimbakerthese are modest tasks15:52
jimbakerand they will ensure we actually walk before we run, by putting us in a real customer usage15:52
jimbakerevery project should be so lucky15:53
sigmavirusjimbaker: I'm not sure "real customer usage" is a thing we'll see from the tiger team15:53
*** jason77 has joined #openstack-meeting-415:53
sigmavirusMost of the customers I know of are far too afraid to adopt new technologies15:53
*** salv-orlando has quit IRC15:54
jimbakerbut it will get us closer to being not so new15:54
jimbakeragain, nothing here is derailing our longterm plans15:54
sigmavirusRight, I agree that none of that derails long term plans15:54
jimbakerinserting a cloud in the resource hierarchy, that's a good thing15:54
jimbakergetting our client/CLI completely usable - and tested! - awesome stuff15:55
jimbakeri would also add docs to that spit & polish15:55
jimbakerso the good thing is, we are almost there. i hope everyone can see that. that's why i mentioned the tues demo we did, because that showed we could do things people cared about15:56
*** jose-phi_ has quit IRC15:56
jimbakereven though it's a fraction of what we are trying to build :)15:56
jimbakerok, so this is no st crispin's day speech15:57
jimbakerbut hopefully that gives you all what we are trying to aim at15:58
jimbakerso a few things left on our agenda15:59
jimbaker:)15:59
*** yamahata has joined #openstack-meeting-415:59
jimbakerbut time is running short15:59
jimbaker#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Mon Feb 13 15:59:46 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-02-13-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-02-13-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/craton/2017/craton.2017-02-13-15.00.log.html15:59
*** git-harry has left #openstack-meeting-416:00
*** marst has joined #openstack-meeting-416:01
*** jason77 has quit IRC16:03
*** chandanc__ has quit IRC16:03
*** jason77 has joined #openstack-meeting-416:05
*** dandruta has joined #openstack-meeting-416:07
*** galstrom_zzz is now known as galstrom16:07
*** Julien-z_ has joined #openstack-meeting-416:11
*** Julien-zte has quit IRC16:12
*** spzala has joined #openstack-meeting-416:13
*** dims_ has quit IRC16:19
*** pcaruana has quit IRC16:20
*** armax has quit IRC16:21
*** iyamahat has joined #openstack-meeting-416:23
*** dims has joined #openstack-meeting-416:24
*** v1k0d3n has quit IRC16:25
*** spzala has quit IRC16:26
*** v1k0d3n has joined #openstack-meeting-416:28
*** matrohon has quit IRC16:32
*** pcaruana has joined #openstack-meeting-416:34
*** dims has quit IRC16:51
*** spzala has joined #openstack-meeting-416:54
*** sdake_ has joined #openstack-meeting-416:55
*** dims has joined #openstack-meeting-416:55
*** sdake__ has joined #openstack-meeting-416:57
*** ltomasbo is now known as ltomasbo|away16:57
*** pcaruana has quit IRC16:58
*** pcaruana has joined #openstack-meeting-416:58
*** sdake has quit IRC16:59
*** sdake_ has quit IRC17:00
*** gibi has quit IRC17:01
*** mgoddard has joined #openstack-meeting-417:01
*** mgoddard has quit IRC17:01
*** gibi has joined #openstack-meeting-417:02
*** mgoddard has joined #openstack-meeting-417:02
*** mgoddard has left #openstack-meeting-417:03
*** dims_ has joined #openstack-meeting-417:06
*** dims has quit IRC17:07
*** rwallner has quit IRC17:10
*** rwallner has joined #openstack-meeting-417:10
*** yfauser has joined #openstack-meeting-417:12
*** jovon has joined #openstack-meeting-417:13
*** ltomasbo|away is now known as ltomasbo17:15
*** nkrinner is now known as nkrinner_afk17:18
*** bnemec has quit IRC17:20
*** bnemec has joined #openstack-meeting-417:24
*** ltomasbo is now known as ltomasbo|away17:28
*** baoli has quit IRC17:44
*** pcaruana has quit IRC17:44
*** baoli has joined #openstack-meeting-417:45
*** baoli has quit IRC17:45
*** iyamahat has quit IRC17:45
*** yamahata has quit IRC17:45
*** armax has joined #openstack-meeting-417:51
*** salv-orlando has joined #openstack-meeting-417:55
*** ralonsoh has quit IRC17:56
*** david-lyle has joined #openstack-meeting-417:58
*** armax has quit IRC17:59
*** armax has joined #openstack-meeting-418:00
*** spzala has quit IRC18:01
*** armax has quit IRC18:02
*** iyamahat has joined #openstack-meeting-418:05
*** Swami has joined #openstack-meeting-418:06
*** david-lyle_ has joined #openstack-meeting-418:08
*** david-lyle has quit IRC18:09
*** david-lyle_ is now known as david-lyle18:12
*** bobh has quit IRC18:12
*** unicell has joined #openstack-meeting-418:13
*** bobh has joined #openstack-meeting-418:13
*** jason77 has quit IRC18:13
*** FrankZhang has quit IRC18:17
*** dandruta has quit IRC18:20
*** baoli has joined #openstack-meeting-418:24
*** baoli has quit IRC18:25
*** yamahata has joined #openstack-meeting-418:25
*** baoli has joined #openstack-meeting-418:25
*** joedborg has quit IRC18:26
*** FrankZhang has joined #openstack-meeting-418:35
*** s3wong has joined #openstack-meeting-418:39
*** vishnoianil has quit IRC18:40
*** sdake has joined #openstack-meeting-418:42
*** sdake__ has quit IRC18:43
*** sdake has quit IRC18:45
*** sdake has joined #openstack-meeting-418:46
*** sdake has quit IRC18:47
*** baoli has quit IRC18:48
*** baoli has joined #openstack-meeting-418:48
*** zz_ja has quit IRC18:49
*** Sukhdev has joined #openstack-meeting-418:51
*** zz_ja has joined #openstack-meeting-418:54
*** emagana has joined #openstack-meeting-418:54
*** yfauser has quit IRC18:56
*** yfauser has joined #openstack-meeting-418:57
*** cjloader_ has quit IRC18:57
*** cjloader_ has joined #openstack-meeting-418:58
*** cjloader_ has quit IRC19:00
*** salv-orl_ has joined #openstack-meeting-419:00
*** cjloader_ has joined #openstack-meeting-419:00
*** yfauser has quit IRC19:01
*** salv-orlando has quit IRC19:03
*** revon has joined #openstack-meeting-419:12
*** hemanthm is now known as hemanthm|lunch19:14
*** dharinic is now known as dharinic|lunch19:19
*** salv-orl_ has quit IRC19:20
*** salv-orlando has joined #openstack-meeting-419:21
*** matrohon has joined #openstack-meeting-419:41
*** klamath has quit IRC19:43
*** rfolco has quit IRC19:44
*** kylek3h_ has quit IRC19:47
*** baoli has quit IRC19:50
*** baoli has joined #openstack-meeting-419:51
*** kylek3h has joined #openstack-meeting-419:54
*** salv-orlando has quit IRC19:57
*** dharinic|lunch is now known as dharinic19:57
*** galstrom is now known as galstrom_zzz20:04
*** galstrom_zzz is now known as galstrom20:05
*** armax has joined #openstack-meeting-420:07
*** hemanthm|lunch is now known as hemanthm20:08
*** spzala has joined #openstack-meeting-420:09
*** mfedosin has quit IRC20:13
*** csun has joined #openstack-meeting-420:13
*** csun has quit IRC20:13
*** rfolco has joined #openstack-meeting-420:29
*** rfolco has quit IRC20:29
*** kylek3h has quit IRC20:30
*** kylek3h has joined #openstack-meeting-420:33
*** galstrom is now known as galstrom_zzz20:33
*** tonytan4ever has quit IRC20:36
*** tonytan4ever has joined #openstack-meeting-420:36
*** rfolco has joined #openstack-meeting-420:38
*** rfolco has quit IRC20:38
*** sdake has joined #openstack-meeting-420:41
*** vishnoianil has joined #openstack-meeting-420:53
*** Syed__ has quit IRC20:55
*** klamath has joined #openstack-meeting-420:55
*** Swami has quit IRC20:55
*** Sukhdev has quit IRC20:56
*** Swami has joined #openstack-meeting-420:56
*** galstrom_zzz is now known as galstrom20:58
*** yamamoto has joined #openstack-meeting-421:12
*** sambetts is now known as sambetts|afk21:14
*** adisky_ has quit IRC21:19
*** iyamahat has quit IRC21:22
*** yamamoto has quit IRC21:27
*** julim has quit IRC21:29
*** julim has joined #openstack-meeting-421:30
*** yfauser has joined #openstack-meeting-421:34
*** l4yerffeJ has joined #openstack-meeting-421:34
*** l4yerffeJ__ has quit IRC21:35
*** Jeffrey4l has quit IRC21:36
*** Jeffrey4l_ has joined #openstack-meeting-421:36
*** dave-mccowan has quit IRC21:36
*** yfauser has quit IRC21:40
*** rwallner has quit IRC21:45
*** salv-orlando has joined #openstack-meeting-421:46
*** sshnaidm is now known as sshnaidm|off21:51
*** jovon has quit IRC22:02
*** thorst_ has quit IRC22:03
*** yamamoto has joined #openstack-meeting-422:12
*** cjloader_ has quit IRC22:14
*** cjloader_ has joined #openstack-meeting-422:14
*** cjloader_ has quit IRC22:16
*** FrankZhang has quit IRC22:17
*** yfauser has joined #openstack-meeting-422:29
*** matrohon has quit IRC22:30
*** thorst_ has joined #openstack-meeting-422:33
*** farid has left #openstack-meeting-422:37
*** thorst_ has quit IRC22:38
*** yfauser has quit IRC22:38
*** kylek3h has quit IRC22:44
*** tonytan4ever has quit IRC22:46
*** salv-orlando has quit IRC22:49
*** bobh has quit IRC22:58
*** thorst_ has joined #openstack-meeting-423:01
*** gk--1wm- has joined #openstack-meeting-423:01
*** gk--1wm- has left #openstack-meeting-423:01
*** dhellmann has quit IRC23:05
*** dhellmann has joined #openstack-meeting-423:06
*** marst has quit IRC23:11
*** marst has joined #openstack-meeting-423:11
*** limao has left #openstack-meeting-423:11
*** limao has joined #openstack-meeting-423:12
*** limao has quit IRC23:13
*** galstrom is now known as galstrom_zzz23:17
*** iyamahat has joined #openstack-meeting-423:18
*** marst has quit IRC23:21
*** spzala has quit IRC23:22
*** edleafe has quit IRC23:30
*** edleafe has joined #openstack-meeting-423:30
*** edleafe has quit IRC23:34
*** Swami has quit IRC23:36
*** edleafe has joined #openstack-meeting-423:40
*** rerobot is now known as redrobot23:43
*** Swami has joined #openstack-meeting-423:49
*** spzala has joined #openstack-meeting-423:52
*** Julien-z_ has quit IRC23:53
*** edleafe has quit IRC23:54
*** spzala has quit IRC23:56
*** edleafe has joined #openstack-meeting-423:57
*** rbak has quit IRC23:57

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