Monday, 2016-11-14

*** sdake_ has quit IRC00:10
*** thorst has joined #openstack-meeting-400:19
*** yfauser has joined #openstack-meeting-400:21
*** yfauser has quit IRC00:26
*** thorst has quit IRC00:26
*** Julien-zte has joined #openstack-meeting-400:34
*** bobh has joined #openstack-meeting-400:36
*** limao has joined #openstack-meeting-400:48
*** sdake has joined #openstack-meeting-400:48
*** bobmel has quit IRC00:58
*** bobmel has joined #openstack-meeting-401:00
*** bobmel has quit IRC01:04
*** neiljerram has joined #openstack-meeting-401:05
*** tovin07_ has joined #openstack-meeting-401:11
*** markvoelker has joined #openstack-meeting-401:19
*** yfauser has joined #openstack-meeting-401:22
*** markvoelker has quit IRC01:23
*** thorst has joined #openstack-meeting-401:25
*** yfauser has quit IRC01:27
*** zhurong has joined #openstack-meeting-401:30
*** sdake has quit IRC01:30
*** limao has quit IRC01:31
*** limao has joined #openstack-meeting-401:31
*** limao has quit IRC01:32
*** sdake has joined #openstack-meeting-401:32
*** limao has joined #openstack-meeting-401:32
*** thorst has quit IRC01:32
*** sdake has quit IRC01:33
*** Julien-zte has quit IRC01:34
*** yfauser has joined #openstack-meeting-401:44
*** Julien-zte has joined #openstack-meeting-401:46
*** yfauser has quit IRC01:49
*** thorst has joined #openstack-meeting-401:51
*** thorst has quit IRC01:56
*** thorst has joined #openstack-meeting-401:57
*** bobmel has joined #openstack-meeting-402:01
*** thorst has quit IRC02:05
*** bobmel has quit IRC02:05
*** bobh has quit IRC02:21
*** vishnoianil has quit IRC02:22
*** lei-zh has joined #openstack-meeting-402:22
*** vishnoianil has joined #openstack-meeting-402:35
*** dims has quit IRC02:43
*** yfauser has joined #openstack-meeting-402:45
*** yfauser has quit IRC02:49
*** janonymous has joined #openstack-meeting-403:09
*** markvoelker has joined #openstack-meeting-403:20
*** bobh has joined #openstack-meeting-403:22
*** markvoelker has quit IRC03:24
*** bobh has quit IRC03:26
*** yamamot__ has joined #openstack-meeting-403:26
*** yfauser has joined #openstack-meeting-403:46
*** neiljerram has quit IRC03:47
*** limao has quit IRC03:47
*** yfauser has quit IRC03:50
*** bobmel has joined #openstack-meeting-404:02
*** thorst has joined #openstack-meeting-404:03
*** lei-zh has quit IRC04:04
*** psachin has joined #openstack-meeting-404:04
*** psachin has quit IRC04:05
*** bobmel has quit IRC04:06
*** thorst has quit IRC04:10
*** psachin has joined #openstack-meeting-404:11
*** psachin has quit IRC04:12
*** psachin has joined #openstack-meeting-404:13
*** links has joined #openstack-meeting-404:15
*** limao has joined #openstack-meeting-404:27
*** limao has quit IRC04:34
*** zhurong has quit IRC04:37
*** janki has joined #openstack-meeting-404:49
*** limao has joined #openstack-meeting-404:50
*** GB21 has joined #openstack-meeting-404:58
*** yfauser has joined #openstack-meeting-405:08
*** thorst has joined #openstack-meeting-405:08
*** reedip has quit IRC05:12
*** yfauser has quit IRC05:12
*** thorst has quit IRC05:15
*** lei-zh has joined #openstack-meeting-405:16
*** markvoelker has joined #openstack-meeting-405:21
*** bobh has joined #openstack-meeting-405:23
*** coolsvap has joined #openstack-meeting-405:23
*** markvoelker has quit IRC05:25
*** bobh has quit IRC05:28
*** amotoki has joined #openstack-meeting-405:31
*** prateek has joined #openstack-meeting-405:31
*** zhurong has joined #openstack-meeting-405:33
*** yfauser has joined #openstack-meeting-405:40
*** reedip has joined #openstack-meeting-405:40
*** yfauser has quit IRC05:44
*** yamamot__ has quit IRC05:45
*** bobmel has joined #openstack-meeting-405:50
*** gongysh has joined #openstack-meeting-405:53
*** bobmel has quit IRC05:55
*** yfauser has joined #openstack-meeting-406:08
*** yfauser has quit IRC06:12
*** thorst has joined #openstack-meeting-406:15
*** irenab has joined #openstack-meeting-406:18
*** thorst has quit IRC06:20
*** yfauser has joined #openstack-meeting-406:22
*** xiaohhui has quit IRC06:26
*** yfauser has quit IRC06:26
*** yfauser has joined #openstack-meeting-406:31
*** anilvenkata has joined #openstack-meeting-406:31
*** yfauser has quit IRC06:31
*** yfauser has joined #openstack-meeting-406:32
*** yamamot__ has joined #openstack-meeting-406:35
*** cartik has joined #openstack-meeting-406:38
*** belmoreira has joined #openstack-meeting-406:45
*** oshidoshi has joined #openstack-meeting-406:48
*** bobmel has joined #openstack-meeting-406:51
*** bobmel has quit IRC06:58
*** JRobinson__ has quit IRC07:06
*** yamamot__ has quit IRC07:08
*** yamamot__ has joined #openstack-meeting-407:11
*** thorst has joined #openstack-meeting-407:19
*** bobh has joined #openstack-meeting-407:25
*** thorst has quit IRC07:25
*** bobh has quit IRC07:30
*** frickler has quit IRC07:34
*** yamamot__ has quit IRC07:36
*** korzen has joined #openstack-meeting-407:42
*** yamamot__ has joined #openstack-meeting-407:42
*** dtardivel has joined #openstack-meeting-407:42
*** korzen has quit IRC07:43
*** korzen has joined #openstack-meeting-407:43
*** unicell has joined #openstack-meeting-407:45
*** unicell1 has quit IRC07:46
*** GB21 has quit IRC07:49
*** yamamot__ has quit IRC07:55
*** yamamot__ has joined #openstack-meeting-407:56
*** pcaruana has joined #openstack-meeting-407:57
*** ralonsoh has joined #openstack-meeting-408:03
*** alexchadin has joined #openstack-meeting-408:04
*** dimak has joined #openstack-meeting-408:05
*** sdake has joined #openstack-meeting-408:07
*** GB21 has joined #openstack-meeting-408:11
*** unicell has quit IRC08:11
*** unicell has joined #openstack-meeting-408:13
*** iurygregory has quit IRC08:13
*** eyalb has joined #openstack-meeting-408:15
*** myatsenko has joined #openstack-meeting-408:15
*** matrohon has joined #openstack-meeting-408:17
*** vishnoianil has quit IRC08:19
*** thorst has joined #openstack-meeting-408:22
*** yuval has joined #openstack-meeting-408:24
*** lei-zh has quit IRC08:28
*** vishnoianil has joined #openstack-meeting-408:30
*** thorst has quit IRC08:30
*** yuli_s has joined #openstack-meeting-408:42
*** d0ugal has joined #openstack-meeting-408:42
*** lei-zh has joined #openstack-meeting-408:42
*** cartik has quit IRC08:50
*** bobmel has joined #openstack-meeting-408:54
*** lihi has joined #openstack-meeting-408:57
*** xiaohhui has joined #openstack-meeting-408:57
*** bobmel has quit IRC08:58
*** oanson has joined #openstack-meeting-408:59
yuli_shello09:00
*** rajivk has joined #openstack-meeting-409:00
oanson#startmeeting Dragonflow09:00
openstackMeeting started Mon Nov 14 09:00:19 2016 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
oansonHello.09:00
dimakGood morning09:00
oansonWelcome to Dragonflow weekly.09:00
lihiHi09:00
*** ruriryan has joined #openstack-meeting-409:00
rajivkHi09:00
oansonReminder, the agenda is posted here: https://wiki.openstack.org/wiki/Meetings/Dragonflow09:00
xiaohhuihello09:00
*** irenab_ has joined #openstack-meeting-409:00
oansonI doubt we will cover everything, but here's hoping09:01
oanson#info yuli_s dimak lihi rajivk xiaohhui In meeting09:01
oansonAll right. Let's start.09:02
oanson#topic Ocata Roadmap09:02
*** openstack changes topic to "Ocata Roadmap (Meeting topic: Dragonflow)"09:02
oansonThere are some specs that were uploaded this week09:02
*** irenab has quit IRC09:02
*** irenaber has joined #openstack-meeting-409:02
oansonI think they need to be merged by Thursday to make the first milestone09:02
oansonLet's start with IPv609:03
oanson#link IPv6 spec https://review.openstack.org/#/c/396226/09:03
*** cartik has joined #openstack-meeting-409:03
oansonlihi, I take it you fixed the previous comments on the spec?09:04
oansonAnyone, if you have any open questions about it, this is the time09:04
yuvalhey all :)09:04
lihiYes. I've upload an update to the spec a few minutes ago.09:04
oansonAll right. No questions are good questions :)09:05
oansonNext up is SFC.09:05
oanson#link Service Function Chaining (SFC) spec https://review.openstack.org/#/c/396226/09:05
oanson#link Service Function Chaining (SFC) spec https://review.openstack.org/#/c/394498/09:05
*** sdake has quit IRC09:05
oansonWrong copy-paste buffer.09:05
dimakI'm waiting for more comments on the spec09:05
oansonAll right. I should be able to go over all the specs today.09:06
dimakI've addressed all the comments and uploaded an new patchset yesterday09:06
*** irenab_ has quit IRC09:06
oansonYes. It looks like there are no new comments yet.09:06
dimakI'd love to see the lbaas spec to see if I can use it for load balancing between sfcs09:06
dimakSFs*09:06
xiaohhuiis there a lbaas spec?09:07
oansonI received a draft of the LB spec.09:07
oansonThe author will upload it today.09:07
xiaohhuiOK09:07
dimakother than that, I hope the spec is extensive enough09:08
oansonLooks like no one has any complaints :)09:09
dimakthats all for me then09:09
oansonNext up is chassis health/service health report09:09
xiaohhuiI have reply comments in the spec and hope rajivk can give some input based on that09:10
oanson#link Is chassis alive support https://review.openstack.org/#/c/385719/09:10
oansonxiaohhui, rajivk, maybe you'd like to take this chance for the discussion?09:10
xiaohhuiSure09:11
oansonWe may be able to close any loose ends quickly in this format09:11
rajivkxiaohhui, can you share your thought?09:11
rajivki could not check my mail today on gmail09:11
rajivkit is banned in my organization.09:11
rajivkWhat do you think, should we do it together or separately?09:12
xiaohhuiI added comments at https://review.openstack.org/#/c/385719/7/doc/source/specs/support_check_chassis_alive.rst@3909:12
*** berendt has joined #openstack-meeting-409:12
xiaohhuito add my thought about service monitor09:12
oansonxiaohhui, I see you mostly recommend using Neutron's ProcessManager?09:13
xiaohhuiYeah, I think that will be simpler09:13
oansonCan we use that for the DF local controller too?09:13
xiaohhuiI don't think so, df local controller should act as the controller to other service.09:14
oansonI also saw it has some accuracy issues. Is that something you ran into? (Or was that only in my setup)09:14
rajivkwhat do you think about each service reporting it's own status?09:14
xiaohhuioanson: what do you mean by accuracy issues?09:15
oansonSometimes is shows that agents which have failed that they are still alive09:15
xiaohhuirajivk: I think that is ok too, but what's the purpose for that?09:15
oansonAnd shows agents that are still alive as failed09:15
xiaohhuiYou mean the neutron agent status, right?09:16
*** admin0 has left #openstack-meeting-409:16
oansonWith Neutron's ProcessManager, my understanding is that each process sends a heartbeat, and you have a monitor reporting that heartbeats are missing. xiaohhui, is that correct?09:16
xiaohhuiNeutron's ProcessManager run in one process, and in that process, the process will be checked, if the process dies, the monitored process will be restarted09:17
xiaohhuiFor example the metadata-ns-proxy in neutron-l3-agent09:18
xiaohhuineutron-l3-agent manages  metadata-ns-proxy by using ProcessManager, to keep it always alive.09:18
oansonAnd metadata-ns-proxy updates the Neutron database with a heartbeat_timestamp? This way the l3 agent knows the ns-proxy service is alive?09:19
xiaohhuino, l3 agent check  metadata-ns-proxy's aliveness by checking its pid file09:20
*** limao has quit IRC09:20
xiaohhuino hearbeat is required for metadata-ns-proxy09:20
oansonI'm a little confused.09:21
oansonYou recommend that local controller verifies health of other services (metadata, l3-agent, publisher) by checking their PID.09:21
oansonAnd reporting at intervals to the database for itself?09:22
oansonAnd have the publisher on the Neutron server be called via the ProcessManager? Where health-check is managed automatically?09:22
xiaohhuiyeah, that is the model of neutron agents for now. agents report to neutron db periodly, however, sub-process will be managed by ProcessManager09:23
oansonI see.09:23
xiaohhuipublisher can be managed by neutron server, as it only needs to work with neutron server(maybe not need to live with neutron server)09:24
*** limao has joined #openstack-meeting-409:24
oansonWe could maintain that model. Have the local controller monitor other df services. When it reports to the database, it will report the health of all services. The only issue is that these services are started outside of the controller.09:24
oansonThe publisher has to live with the neutron server, since the communicate over IPC. Currently, it is started externally (But obviously this can be changed)09:25
oansonI think it is started externally to avoid the q-svc forking issue.09:25
xiaohhuiIf we decided to go that way, some changes need to be made for starting process09:25
oansonYes.09:26
oansonGood thing this is the start of the cycle :)09:26
oansonThe metadata service can be started from the DF metadata app.09:27
xiaohhuiI am thinking adding more information to chassis, we can definitely add the status of sub-process to chassis too.09:27
oansonWe can write a centralised snat app to maintain df-l3-agent.09:27
xiaohhuiyeah, so that if user don't add the metadata app, the metadata proxy service don't need to be started09:27
*** thorst has joined #openstack-meeting-409:28
oansonI need to review the Neutron code, but I'm sure we can find the correct place to add the publisher service startup code09:28
oansonxiaohhui, yes. Same for the l3 agent.09:28
xiaohhuiwe can wait for the distributed snat and then remove df-l3-agent, right?09:28
oansonThat's the plan09:28
oansonBut with this change, centralised snat can still be used, as a DF app.09:28
*** Julien-zte has quit IRC09:28
oansonWhich is more in-line with our global design09:29
xiaohhuiI guess that is something can be implemented.09:29
oansonSounds like we're in agreement. rajivk, any comments?09:29
rajivki am still going through your dicussion09:30
rajivk:)09:30
rajivkYou can continue09:30
oansonAll right. We can take a second to breathe :)09:30
xiaohhuiWe can continue our discussion in the spec, if we miss something here.09:30
*** gongysh has quit IRC09:30
oansonSounds like a plan09:30
rajivkNo, it is ok, you carry on with the meeting.09:30
rajivkI will need extra effort to understand, what you mean :)09:31
oansonrajivk, no worries. We're here for any follow-ups.09:31
rajivkoanson, thanks :)09:31
oansonI'll skip ahead for a bit:09:32
oansonLBaaS, as I said, the spec should be up today.09:32
oansonI also received a draft for sNAT. I can't promise it will be up today, but I hope by tomorrow.09:32
irenaberoanson, to support V2 apis?09:32
oansonYes09:32
irenaberfor LBaaS09:32
oansonV1 has been removed in Newton, so supporting it is a bit...09:33
oansonLet's move on to Tap as a service.09:34
*** zhurong has quit IRC09:34
*** thorst has quit IRC09:34
oanson#link Tap as a service (TAPaaS) spec https://review.openstack.org/#/c/396307/09:34
oansonyamamoto added some comments about the TAP location.09:35
oansonyuli_s, would you like to discuss the two TODO items?09:35
oansonno. 1 (TAP destination port on different compute nodes) should be easy to tackle.09:36
yuli_syes, sure09:36
oansonWe already have everything in place. Just need to update the correct parameters, and send to the table that handles tunneling.09:36
*** yamamot__ has quit IRC09:36
yuli_si got a comments from Yamamoto09:36
*** yamamoto has joined #openstack-meeting-409:36
yuli_sthat the packets should be intercepted after the SG09:37
oansonYes. He mentions that security groups should be taken into account.09:37
oansonCould you please verify and update the spec?09:37
yuli_sso, I need to update the spec with his comments09:37
oansonYes09:37
*** yamamoto has quit IRC09:38
yuli_sI will review the rules and release a new version today09:38
yuli_sos the spec09:38
yuli_sof the spec09:38
oansonGreat.09:38
*** bogdando has quit IRC09:38
oansonAbout TAP of a TAP. Do you have any thoughts?09:38
yuli_sregarding the second item09:38
yuli_syes, tap of the tap09:38
oansonAny thoughts?09:39
yuli_si think I need additional time09:39
yuli_sto research this09:39
oansonSure.09:39
yuli_sbecause dimak suggested that it can create a loop09:40
oansonSure. Worst comes to worst, we can leave it as a limitation in Ocata.09:40
yuli_sok, great09:40
*** yuelongguang has joined #openstack-meeting-409:40
yuli_sI would like to get oppinion of all the experts09:41
oansonBut that will have to be written in the spec. And if you can make it after all, that would be better09:41
oansonAlso don't forget to treat dimak 's comments about router ports and dhcp ports.09:41
yuli_sif the target VM ( the one that should receive the intercepted traffic)09:41
yuli_shas seurity group in place09:41
yuli_sshould we filter that traffic of other hosts as well ?09:41
*** asettle has joined #openstack-meeting-409:43
*** Wang__Jian has joined #openstack-meeting-409:43
yuli_sok, I will write this in spec and we will see other people opinon09:43
oansonyuli_s, could you explain a bit more?09:43
oansonI'm not sure I understand the question09:43
yuli_sas I understand the comments from Yamamoto, it is not clear if we need to filter traffic 2 times09:44
yuli_sones when the traffic leaves the source vm09:44
yuli_sand another when it received by target VM09:44
yuli_s(I am talking here about tapped traffic)09:45
yuli_sI will write to Yamamoto to get his comments,09:46
oansonI think it would be best to understand how TAPaaS should work with SG09:46
yuli_slets continue09:46
oansonThe above is already an implementation question, but I would like to understand the requirement.09:46
oansonyuli_s, please do. I think this needs clearing up.09:46
oansonAll right, this is all for roadmap.09:46
oansonIs there a spec, blueprint, or feature I missed?09:47
oansonRemember, to meet the Ocata milestones, we need these merged by the end of the week.09:47
oansonI think we're in good shape!09:47
oanson#topic bugs09:48
*** openstack changes topic to "bugs (Meeting topic: Dragonflow)"09:48
oansonStatus hasn't changed since last week. There is still one High priority bug with no progress09:48
oansonBug 163815109:48
openstackbug 1638151 in DragonFlow "Router schedule error in L3 router plugin as there are multi-external network" [High,New] https://launchpad.net/bugs/1638151 - Assigned to rajiv (rajiv-kumar)09:48
xiaohhuiI think I can give a look to it from neutron side,09:49
xiaohhuiAfter another thought, I think it might be a neutron issue, but I need more investigation09:49
*** zenoway has joined #openstack-meeting-409:50
oansonCurrently its assigned to rajivk, so make sure you guys aren't stepping on each others' toes09:50
rajivkI will abondon it09:50
xiaohhuisorry, I didn't notice that it has owner09:50
rajivkI know, it is high priority09:50
oansonxiaohhui, that's all right. That;s why we are discussing it :)09:50
rajivkand xiaohhui can do it better than me09:50
oansonMy question is, is it really high priority? Are there any functional issues, except the thrown error?09:51
oanson(I asked this also on the bug)09:51
xiaohhuiif we don't eager to support mult-external network, I think it is ok09:51
xiaohhuidon't -> aren't09:52
oansonAll right. Then I'll reduce it to medium09:53
oansonI think everything else is under control. I want to concentrate on specs this weekl09:53
*** iberezovskiy|off is now known as iberezovskiy09:53
rajivkI have removed myself from assignee09:53
oansonweek*09:53
oansonAnything else for bugs?09:53
oanson#topic Open Discussion09:54
*** openstack changes topic to "Open Discussion (Meeting topic: Dragonflow)"09:54
oansonThe floor is for the taking09:54
xiaohhuiIf you guys have extra time09:54
xiaohhuiI would like to you to review this https://review.openstack.org/#/c/339975/09:54
oansonI'll try and get to it today/tomorrow09:55
xiaohhuiit is in merge conflict now, but it will be updated soon09:55
xiaohhuithanks09:55
oansonIt's not in merge conflict...09:55
xiaohhuimy eyes go wrong...09:56
*** neiljerram has joined #openstack-meeting-409:56
oansonYou mean patch: "add active detection app for allowed address pairs"09:56
oanson?09:56
xiaohhuiyeah09:56
oansonSure. I'll look at it today/tomorrow :)09:57
xiaohhuiit is in merge conflict, I give it another glance...09:57
xiaohhuianyway, thanks09:57
oansonSure.09:57
oansonAnything else?09:57
xiaohhuinothing from me...09:57
oansonGreat. Then we can go to eat :)09:58
oansonThanks everyone for coming!09:58
oanson#endmeeting09:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:58
openstackMeeting ended Mon Nov 14 09:58:30 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-11-14-09.00.html09:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-11-14-09.00.txt09:58
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-11-14-09.00.log.html09:58
*** Wang__Jian has quit IRC09:59
*** alexchadin has quit IRC10:01
*** tovin07_ has quit IRC10:03
*** sambetts|afk is now known as sambetts10:03
*** limao has quit IRC10:04
*** aarefiev has joined #openstack-meeting-410:06
*** alexchadin has joined #openstack-meeting-410:07
*** numans has joined #openstack-meeting-410:11
*** aarefiev has quit IRC10:22
*** alexchadin has quit IRC10:22
*** alexchadin has joined #openstack-meeting-410:23
*** thorst has joined #openstack-meeting-410:32
*** lei-zh has quit IRC10:34
*** nkrinner_afk has quit IRC10:35
*** aarefiev has joined #openstack-meeting-410:37
*** khushbu has joined #openstack-meeting-410:38
*** thorst has quit IRC10:40
*** liuyulong has joined #openstack-meeting-410:46
*** baoli has joined #openstack-meeting-410:46
*** nkrinner_afk has joined #openstack-meeting-410:47
*** baoli has quit IRC10:50
*** bogdando has joined #openstack-meeting-410:52
*** bobmel has joined #openstack-meeting-410:55
*** d0ugal has quit IRC10:56
*** GB21 has quit IRC10:59
*** bobmel has quit IRC10:59
*** d0ugal has joined #openstack-meeting-411:04
*** xiaohhui has quit IRC11:07
*** limao has joined #openstack-meeting-411:28
*** yfauser has quit IRC11:28
*** yamamoto has joined #openstack-meeting-411:31
*** limao_ has joined #openstack-meeting-411:32
*** limao has quit IRC11:35
*** zhurong has joined #openstack-meeting-411:35
*** thorst has joined #openstack-meeting-411:37
*** gongysh has joined #openstack-meeting-411:39
*** zhurong has quit IRC11:42
*** thorst has quit IRC11:45
*** khushbu has quit IRC11:47
*** dave-mccowan has joined #openstack-meeting-412:01
*** julim has joined #openstack-meeting-412:05
*** zhurong has joined #openstack-meeting-412:16
*** rtheis has joined #openstack-meeting-412:17
*** zhurong has quit IRC12:19
*** GB21 has joined #openstack-meeting-412:19
*** zhurong has joined #openstack-meeting-412:21
*** cartik has quit IRC12:24
*** yuval has left #openstack-meeting-412:31
*** alexchadin has quit IRC12:46
*** alexchadin has joined #openstack-meeting-412:47
*** thorst has joined #openstack-meeting-412:50
*** julim has quit IRC12:51
*** thorst_ has joined #openstack-meeting-412:54
*** thorst has quit IRC12:54
*** bobmel has joined #openstack-meeting-412:55
*** makowals has quit IRC12:57
*** makowals has joined #openstack-meeting-412:59
*** belmorei_ has joined #openstack-meeting-413:00
*** kylek3h has quit IRC13:00
*** bobh has joined #openstack-meeting-413:00
*** bobmel has quit IRC13:00
*** bobh has quit IRC13:00
*** alexchadin has quit IRC13:01
*** bobh has joined #openstack-meeting-413:01
*** alexchadin has joined #openstack-meeting-413:01
*** belmoreira has quit IRC13:01
*** alexchadin has quit IRC13:05
*** alexchadin has joined #openstack-meeting-413:05
*** zaneb has joined #openstack-meeting-413:07
*** neiljerram has quit IRC13:15
*** makowals has quit IRC13:16
*** janki has quit IRC13:16
*** _degorenko|afk is now known as degorenko13:19
*** yfauser has joined #openstack-meeting-413:20
*** lamt has joined #openstack-meeting-413:21
*** janki has joined #openstack-meeting-413:21
*** lamt has quit IRC13:22
*** irenaber has quit IRC13:23
*** lamt has joined #openstack-meeting-413:23
*** sdake has joined #openstack-meeting-413:24
*** haleyb_ has joined #openstack-meeting-413:24
*** bobh has quit IRC13:28
*** figleaf is now known as edleafe13:29
*** makowals has joined #openstack-meeting-413:30
*** dims has joined #openstack-meeting-413:35
*** woodard has joined #openstack-meeting-413:35
*** woodard has quit IRC13:36
*** woodard has joined #openstack-meeting-413:36
*** alraddarla_ has joined #openstack-meeting-413:39
*** baoli has joined #openstack-meeting-413:41
*** baoli has quit IRC13:42
*** markvoelker has joined #openstack-meeting-413:46
*** Julien-zte has joined #openstack-meeting-413:49
*** uck has joined #openstack-meeting-413:50
*** kylek3h has joined #openstack-meeting-413:51
*** irenab has joined #openstack-meeting-413:54
*** irenab_ has joined #openstack-meeting-413:55
*** psachin has quit IRC13:55
*** ivc_ has joined #openstack-meeting-413:56
*** gongysh has quit IRC13:56
*** mchiappero has joined #openstack-meeting-414:00
*** lmdaly has joined #openstack-meeting-414:01
*** yfauser has quit IRC14:02
*** pc_m has joined #openstack-meeting-414:02
*** klamath has joined #openstack-meeting-414:03
*** klamath has quit IRC14:03
*** klamath has joined #openstack-meeting-414:04
*** oanson has quit IRC14:05
*** alexchadin has quit IRC14:06
*** julim has joined #openstack-meeting-414:07
*** bobh has joined #openstack-meeting-414:07
*** yamamoto has quit IRC14:08
*** yamamoto has joined #openstack-meeting-414:08
*** zhurong has quit IRC14:08
*** lmdaly has quit IRC14:11
vikasc#startmeeting kuryr14:11
openstackMeeting started Mon Nov 14 14:11:49 2016 UTC and is due to finish in 60 minutes.  The chair is vikasc. Information about MeetBot at http://wiki.debian.org/MeetBot.14:11
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:11
*** openstack changes topic to " (Meeting topic: kuryr)"14:11
openstackThe meeting name has been set to 'kuryr'14:11
vikascHello everybody and welcome to another Kuryr weekly IRC meeting14:12
ivc_o/14:12
irenab_hi14:12
*** Julien-zte has quit IRC14:12
vikascwho's here to chat?14:12
* pc_m lurking again14:12
*** lmdaly has joined #openstack-meeting-414:12
limao_o/14:12
alraddarla_o/14:12
lmdalyo/14:12
*** Julien-zte has joined #openstack-meeting-414:12
*** Julien-zte has quit IRC14:13
vikasc#info ivc_ irenab vikasc alraddarla_ lmdaly  joined the meeting14:13
*** Julien-zte has joined #openstack-meeting-414:13
mchiapperoo/14:13
vikasc#topic kuryr-libnetwork14:13
*** openstack changes topic to "kuryr-libnetwork (Meeting topic: kuryr)"14:13
*** Julien-zte has quit IRC14:13
*** Julien-zte has joined #openstack-meeting-414:14
*** baoli has joined #openstack-meeting-414:14
*** irenab_ has quit IRC14:14
*** Julien-zte has quit IRC14:14
vikasc#link https://review.openstack.org/#/c/394547/14:14
*** tuan_luong has joined #openstack-meeting-414:14
*** Julien-zte has joined #openstack-meeting-414:15
irenabthere are jenkins failures14:15
mchiapperoyes14:15
mchiapperoI'm updating the unit test files14:15
*** Julien-zte has quit IRC14:15
vikasclmdaly has a WIP patch for moving binding from join to create_endpoint14:15
mchiapperoI hope to finish today or tomorrow14:15
vikascthanks mchiappero14:15
*** Julien-zte has joined #openstack-meeting-414:15
*** Julien-zte has quit IRC14:16
*** Julien-zte has joined #openstack-meeting-414:16
*** pcaruana has quit IRC14:16
*** Julien-zte has quit IRC14:17
vikascI observed that currently kuryr-libnetwork is missing neutron call for updating port with --allowed-address-pair incase ipvlan driver is used in nested container case14:17
*** Julien-zte has joined #openstack-meeting-414:17
irenabvikasc, link to bug?14:17
*** Julien-zte has quit IRC14:17
mchiapperoyes, that's because there is a patch missing14:17
mchiapperobeing worked on14:18
lmdalyWe are working on a patch to create a driver based model for libnetwork to do this14:18
*** makowals has quit IRC14:18
vikascirenab, no bug report yet14:18
vikascirenab, just an random observation14:18
irenabguys, please report bugs once you observe them14:18
vikascirenab, sure, i was planning to raise after discussion14:18
vikascthanks lmdaly and mchiappero for the update!!14:19
*** tonytan4ever has joined #openstack-meeting-414:19
irenablmdaly, can you please elaborate on driver based model?14:19
lmdalynot concrete on the idea yet, but thinking much like the model introduced in kuryr-lib14:20
mchiapperothere is actually another open point regarding IPVLAN14:21
lmdalywith a config file option and different implementations based on the driver14:21
mchiapperothe fact is that libnetwork seems to assign the MAC address, but the IPVLAN driver doesn't have such capability14:21
mchiapperoso it fails14:22
lmdalywill push a WIP patch as soon as possible to get feedback on the structure14:22
irenablmdaly, got it, thanks. sounds as a good approach to keep code base better separated14:22
mchiapperodo we have any contact we can leverage in docker?14:22
mchiapperoalso the libnetwork specs are confusing at times, we need clarifications there14:22
vikascmay be banix would have helped14:22
irenabI am not aware of any, probably mailing list option14:23
mchiapperoif you know someone personaly let us know14:23
*** makowals has joined #openstack-meeting-414:23
mchiapperook, thanks14:23
vikasci messed up the order :P14:23
vikasc#topic kuryr-lib14:23
*** openstack changes topic to "kuryr-lib (Meeting topic: kuryr)"14:23
vikasc#link https://review.openstack.org/#/c/397057/14:24
irenabvikasc, unit testing is missing14:24
vikasci pushed a small fix in ipvlan/macvlan driver ip assignment14:24
mchiapperoI'm not too sure I understand this patch14:25
mchiapperothe previous behaviour seemed to be correct to me14:25
vikascmchiappero, would you mind please adding your comments to patch14:26
vikascirenab, will add if fix is valid :)14:26
mchiapperoI will, but I need to find some time to better review and maybe test it :)14:27
limao_in utils._configure_container_iface, it add ip onto the macvlan/ipvlan device, the ip should be not is vm-port14:27
vikascmchiappero, np, we can still discuss offline. i will ping you14:27
limao_the ip should be not is vm-port -> the ip should not be vm-port fixed ip14:27
lmdalyfor the demo I passed in port as vm-port and nested_port as dangling neutron port with the container_ip14:28
irenabmaybe the name is confusing, I thought nested port is the container port14:28
mchiapperoit is/should br14:28
mchiappero*be14:28
vikascirenab, nested_port seems to be vm_port to me14:28
vikascirenab, because in veth driver, this is not being even used14:29
lmdalyI would have thought the same as irenab14:29
irenabthen it should be nesting_port :-)14:29
limao_I was thought it is vm-port...14:29
vikasci will take a look again14:29
mchiapperome too14:29
lmdalyseems we need a name change :)14:30
vikascrequest everbody to please review the same14:30
limao_since nowhere actually use this param now..14:30
irenabif its not in  use, better to remove it14:30
vikasc#link https://review.openstack.org/#/c/361993/14:30
lmdalyit will be used for the driver patch we introduce for libnetwork14:31
vikascirenab, it will be used in trunk port case14:31
irenabthen lets just improve the name14:31
vikascirenab, +114:31
vikasc#link https://review.openstack.org/#/c/361993/14:31
vikascWIP patch for adding vlan driver support14:32
irenabvikasc, I posted few comments14:32
*** garyloug has joined #openstack-meeting-414:32
vikascthanks irenab, i will go through them14:33
vikascintention is to leverage neutron trunk ports14:33
limao_a quick question, in which use case we need to use local vlan? I see local vlan manage in that patch14:34
limao_I mean : https://review.openstack.org/#/c/361993/11/kuryr/lib/segmentation_type_drivers/vlan.py14:35
vikasclimao_, for the isolation of traffic from containers14:35
vikasclimao_, on  the vm only14:35
irenablimao_, vlan is to identify the container14:35
limao_you mean in vm-nested case with subport trunk port?14:35
vikasclimao_, yes14:36
irenabyes14:36
limao_In my currently understanding, the vlan in vm should not be local vlan, it should be same vlan as subport14:36
vikasclimao_, vlan of subport menas?14:37
limao_(I'm not sure if I miss something here since I has not actually tried trunk port now)14:37
vikasclimao_, sorry, can you please reword your question14:38
limao_The VM should be trunk port, in case it using vlan 100,20014:38
limao_then the container on this vm should just use eth0.100, eth0.200, right?14:38
irenablimao_, I think the idea is to use trunk port neutron APIs to get something similar to what OVN did:  http://docs.openstack.org/developer/networking-ovn/containers.html14:39
*** isq has quit IRC14:39
limao_oh... let me check offline, thanks for the info , irenab, vikasc14:39
ivc_limao_, irenab, we are we talking about vlan-aware-vms or ipvlan-based trunk ports?14:40
*** neiljerram has joined #openstack-meeting-414:40
*** isq has joined #openstack-meeting-414:40
limao_I think it should be vlan-aware-vms14:40
irenabvikasc, may I raise one question that ks more related to the open discussion part, just need to drop in 5 mins14:40
irenabivc_, vlan aware vms14:41
vikascirenab, sure, please go ahead14:41
irenabthere is a design summit in February14:41
irenabI didn't see kuryr in the list of confirmed projects, I wonder if anyone plans to attend14:41
limao_PTG?14:42
irenabyes14:42
limao_I do not see it on list too14:42
*** syed__ has joined #openstack-meeting-414:42
vikasc#action need to confirm with Toni on PTG.14:42
*** haleyb__ has joined #openstack-meeting-414:43
irenabvikasc, thanks. Please keep going according to the usual route14:43
vikascirenab, thanks :)14:43
limao_thanks irenab14:43
vikascivc_, yes vlan aware vms14:43
*** haley__ has joined #openstack-meeting-414:44
vikasclimao_, as per my understanding scope of vlans(vlan-per-container) will be local to vm only14:44
*** haleyb has quit IRC14:44
*** haleyb_ has quit IRC14:44
limao_ivc_ , vikasc: I was thought we do not need manage local vlan in kuryr, just use the vlan of the subport14:44
vikasclimao_, i could not get chance to have a look at ovn way yet14:44
*** _fortis has joined #openstack-meeting-414:45
*** woodard has quit IRC14:45
ivc_limao_, vikasc, we need to manage vlans for subports14:45
vikasclimao_, i think i got your point14:45
ivc_because when you create sub-port in neutron we either specify the vid, or let neutron set it14:46
ivc_but we need to coordinate subports (on neutron) with the ethX.Y inside the vm14:46
vikascivc_, +114:46
limao_Is this info can be get when container create? or we need to cache it in kuryr?14:47
vikascivc_, we are talking about this https://review.openstack.org/#/c/361993/14:47
*** apuimedo has joined #openstack-meeting-414:47
apuimedo\o/14:47
vikasclimao_, we will have to manage in kuryr14:48
vikascapuimedo, hello14:48
*** rbak has joined #openstack-meeting-414:48
limao_apuimedo :-) you get released ?14:48
vikaschandover to you apuimedo14:48
vikascand many many congrats14:48
irenabhave to leave, will catch up on the log14:48
vikasc:)14:48
apuimedoyup14:49
apuimedowe're all home14:49
mchiappero:)14:49
apuimedosorry I couldn't make it 50min earlier14:49
mchiapperodoing well?14:49
ivc_apuimedo, congrats on your daughter release !14:49
*** eyalb has quit IRC14:49
apuimedothanks!14:49
lmdalycongrats! :)14:49
apuimedoit was a hard fork!14:49
vikascsweets...........14:49
vikascapuimedo, laddu14:49
vikasc:)14:49
apuimedobut the new process is running strong and consuming a lot of resources14:49
apuimedoas it should14:49
apuimedothank you all14:50
mchiappero:)14:50
apuimedoare we in kuryr-kubernetes part or in open discussion already?14:50
vikascjust starting14:50
ivc_neither14:50
vikasc#topic kuryr-kubernetes14:50
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)"14:50
ivc_#link https://review.openstack.org/#/c/376044/2/kuryr_kubernetes/controller/handlers/vif.py@7114:51
apuimedoonly 9min remaining14:51
* vikasc feeling sorry for poor time-management14:51
apuimedosorry, it's because my email was not sent properly14:51
ivc_polling for neutron port activation seems to be a hot topic14:51
*** hemanth|away is now known as hemanth14:51
ivc_but i've checked and it is the same in kuryr-libnetwork14:51
ivc_#link https://github.com/openstack/kuryr-libnetwork/blob/master/kuryr_libnetwork/controllers.py#L342-L36014:52
apuimedo#action apuimedo to address vikasc comments to https://review.openstack.org/#/c/396113/14:52
apuimedoivc_: yes, that was a relatively recent addition from banix14:52
ivc_so i was thinking if it is worth adding some notification-based mechanism for both projects to check for port activation14:52
apuimedoonly for ovs, iirc14:53
apuimedowell, we have an open door to do it in neutron for both14:53
apuimedojust as it does for nova14:53
apuimedoso that's the long term solution I'd like14:53
apuimedoor the one that I think is more doable14:53
apuimedoivc_: did you see https://review.openstack.org/#/c/396113/ ? I think it addresses the loopback requirement you noted to me14:54
*** bobh has quit IRC14:54
*** git-harry has joined #openstack-meeting-414:54
ivc_apuimedo, yes, but need to test it (the cni binary is 'lo' instead of 'loopback')14:54
apuimedoyeah... I need to test it too14:55
apuimedoI had to run to the hospital just after writing it xD14:55
mchiappero:D14:56
apuimedoalmost literally14:56
vikasc:D14:56
apuimedoalso14:56
mchiapperomaybe the code was ready too14:56
apuimedoI want to add to devstack to set kubectl config14:56
mchiappero:P14:56
apuimedo:D14:56
*** matrohon has quit IRC14:56
limao_apuimedo: you will get more sleepless night now14:56
apuimedoto make development easier14:56
*** bobmel has joined #openstack-meeting-414:56
apuimedolimao_: yeah, more time for coding14:56
limao_:)14:56
apuimedoone eye on the baby and one on the screen, like a chameleon14:57
vikascapuimedo, height of optimism14:57
apuimedoindeed14:57
apuimedoanyway. I will be working part time for a few weeks now14:58
apuimedoI still should be able to finish cni and do these devstack improvements :-)14:58
limao_home is always first :)14:58
vikasclimao_, +114:58
apuimedovery true limao_14:58
apuimedoanything else about kuryr-kubernetes before we close?14:58
apuimedoI'd appreciate that people try the devstack and start to play with the environment and review ivc_'s code if they haven't started already14:59
ivc_apuimedo, well we could discuss the cni-daemon idea next week14:59
ivc_since its a long-term idea anyway15:00
apuimedoivc_: good point15:00
apuimedoivc_: we can even do an extraordinary irc meeting some time in the week in #openstack-kuryr15:00
apuimedovikasc: we must close the meeting now and move to #openstack-kuryr15:00
jimbakerapuimedo, thanks15:00
apuimedoI'm sure there's people waiting to take the room :P15:01
vikascsure15:01
ivc_apuimedo, sure15:01
*** bobmel has quit IRC15:01
vikasc#end-meeting15:01
jimbaker#startmeeting craton15:01
openstackjimbaker: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.15:01
jimbakervikasc, ^^^15:01
apuimedovikasc: endmeeting15:01
apuimedonot end-meeting15:01
vikasc#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:01
openstackMeeting ended Mon Nov 14 15:01:52 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-11-14-14.11.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-11-14-14.11.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-11-14-14.11.log.html15:01
apuimedo;-)15:01
jimbaker#startmeeting craton15:02
openstackMeeting started Mon Nov 14 15:02:00 2016 UTC and is due to finish in 60 minutes.  The chair is jimbaker. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
vikascsorry jimbaker15:02
*** openstack changes topic to " (Meeting topic: craton)"15:02
openstackThe meeting name has been set to 'craton'15:02
*** alraddarla_ has left #openstack-meeting-415:02
jimbakervikasc, np15:02
sigmavirusGood morning, all!15:02
palendaeo/15:02
jimbakersigmavirus, hi, thanks for a good conversation on #craton about cachine15:02
jimbakercaching15:02
*** lmdaly has left #openstack-meeting-415:03
jimbakerwe can spend a few minutes this morning on this discussion, although it's of course fairly openended from the server perspective15:03
*** haleyb_ has joined #openstack-meeting-415:03
jimbakerbut from the client, it's straightforward15:03
*** garyloug has left #openstack-meeting-415:03
palendaeLooks like. Invalidating will be the biggest concern now, but that's easy ;)15:04
jimbakerpalendae, thanks for joining!15:04
*** ivc_ has left #openstack-meeting-415:04
jimbakerpalendae, it's only one of the so-called hardest problems in computer science15:05
palendaejimbaker: ;)15:05
sigmaviruspalendae: so, i'm going to work on adding caching headers to the server15:05
jimbakerpalendae, http://martinfowler.com/bliki/TwoHardThings.html15:05
palendaejimbaker: I know, I was making a joke15:05
sigmavirusCacheControl will then be used on the client side and will take care of invalidating thing sintelligently (as it does)15:05
*** haleyb__ has quit IRC15:05
palendaesigmavirus: Ok, cool15:05
jimbakeryeah, i love the joke. especially the off by one part15:06
jimbakerbut, hey, i am sort of in this field a bit too deep ;)15:06
jimbakerit's rubbed off15:06
jimbakersulo, around?15:07
jimbakersyed__, hi15:07
suloo/15:07
sulohi everyone15:07
jimbakerok, looks like we have our quorum15:07
syed__Hi  guys15:07
*** uck has quit IRC15:08
sulohi syed__15:08
jimbakerfirst, it's good to be back. i guess i have missed the last 3 of these meetings, between travel and vacation15:08
*** lakerzhou has joined #openstack-meeting-415:09
*** apuimedo has left #openstack-meeting-415:09
*** bobmel has joined #openstack-meeting-415:09
*** janki has quit IRC15:09
jimbakerso let's get started with a quick standup of what we plan to be working on this week; and especially review progress15:09
jimbakersigmavirus, you want to go first?15:10
sigmavirusSure15:10
sigmavirusI'm going to having Flask provide proper cache-control headers to users, once that's in place, I'll rework my existing client work to rely on the much better (and more appropriate) cachecontrol library15:10
sigmavirusI'll start a review to add that library to global-requirements now so that we can maybe have that resolved by the time the client work is ready to be done15:10
sigmavirus</update>15:11
jimbakersigmavirus, +1. what specific logic are you planning for the server side - just expiry time for the time being?15:11
sigmavirusjimbaker: no, thinking of providing ETags15:13
*** watanabe_isao has joined #openstack-meeting-415:13
sigmavirusThose are more reliable in my experience15:13
suloprobably add mod time15:13
sigmavirussulo: you mean, "Last-Modified" so we can use "If-Modified-Since"?15:13
*** GB21 has quit IRC15:13
*** bobmel has quit IRC15:13
suloyeah15:13
*** links has quit IRC15:13
suloetag woudl be difficult to do/ more server work ?15:14
jimbakersigmavirus, sure, i think we would certainly prefer etags. just a concern of whether we can get quick/easy versioning out of what we have already15:14
jimbakervs something simple like TTL based approaches15:14
suloprobalby the best etag would be to add some sort of hash but then we'd have to compue that ...15:15
sulottl bases sutff probably would be bad ?15:15
sigmaviruswe can start with Last-Modified, if that's what you all want15:16
jimbakersulo, i started looking at a range of options that exist, such as NDB and its memcached support - supposedly we do get a version, not certain what it would mean for making it easy going forward15:16
sigmavirusSo, to be clear, I'm not doing caching between the DB and the API15:16
sulosigmavirus: +115:16
sigmavirusThat's far more work than is necessary here15:16
jimbakersigmavirus, yeah, agreed here15:16
sigmavirusI'm only providing cache-control headers as defined in the RFC to the clients15:16
suloyeah that should be something different15:16
suloyeah agreed15:16
*** coolsvap has quit IRC15:17
jimbakerwe want to get the client to follow the server's direction - we can improve the server for its consistency with the database over time - a number of options15:17
jimbakersigmavirus, ok, so that sounds great15:17
palendaeFrom my perspective, I'm not too concerned about the underlying implementation, just that there are fewer roundtrips15:17
*** watanabe_isao has quit IRC15:17
jimbakerpalendae, agreed - we should not get too worked up about server performance just yet :)15:18
jimbakerthere are so many things we can do to improve that, and we can take advantage of a variety of approaches for a specific setup15:18
jimbakersulo, what is this week looking like for you?15:19
suloSo i just started looking at functional testing15:20
suloi have a bunch of reviews in place (i need to update the filter pr .. which i will do later today)15:20
sulobut will probalby get the functional testing going this week15:20
jimbakersulo, sounds good about the filter update. i think that's pretty much ironed out in those comments, in terms of removing in support + using ?vars=x:y15:21
suloyeah, i think this makes sense15:21
jimbakersulo, i expect we we will want to use some variant on jsonpath for the equiv of the in operator; and probably just pass complex queries in the request15:22
jimbakerbut deferring means we can figure that out :)15:22
suloyeah agreed, we can do that as impovement work ..15:22
*** cleong has joined #openstack-meeting-415:23
jimbakersulo, re functional testing - so this will be using docker-py?15:23
suloyeah i think15:23
suloi think so15:23
*** oanson has joined #openstack-meeting-415:23
*** prateek has quit IRC15:23
jimbakersulo, ack, follows what we have been doing manually, so it seems to make sense15:23
suloi have a question15:24
jimbakersulo, did you write up your barcelona observations for openstack-dev? (i still need to do mine, although i did speak about it for an OSIC meeting)15:24
jimbakersulo, ?15:24
sulosigmavirus might know .. what happens on infra side if we choose to use docker based tests15:24
sulojimbaker: i have not15:25
suloi can do that if required15:25
syed__Just a general question15:25
syed__Dont we need tempest aswell? Since eventually this gets integrated in openstack15:25
jimbakersulo, no worries, it was in the action items from last week that sigmavirus assigned you - but why don't i take responsibility for writing that email for us jointly15:25
jimbakersort of my job :)15:25
jimbakersyed__, it's a great question - our perspective has been no, because we are not exactly like other openstack services15:26
sulosyed__: i dont think so ...but i am pinging someone to find out15:26
sigmavirussulo: I don't know what happens on the infra side, but I think you have to do most of the orchestration yourself15:26
sulosigmavirus: something like 3party thing ?15:27
sigmavirussyed__: so tempest is also a test framework, we can use tempest's libraries to craft our own tempest like tests, and that wouldn't be a bad idea15:27
sigmavirussulo: no, more like running specific commands to run the functional tests on a VM provided by infra15:27
sulosigmavirus: ah that we can do15:27
jimbakersigmavirus, thanks for that clarification15:27
sulosigmavirus: our vm is container here ..15:27
sulosigmavirus: do they allow for us to sipin up docker during out test ?15:28
sigmavirussulo: I think, yes15:28
sulosigmavirus: cool, thx15:28
jimbakersulo, which should be quite lightweight - just really requires that docker daemon is available15:28
suloyeah15:28
sulopretty much thats all our req is for that15:28
syed__Thanks sigmavirus15:28
*** spotz_zzz is now known as spotz15:29
palendaesulo: They definitely allow spinning up lxc containers, so Docker's probably allow15:30
palendaeallowed*15:30
jimbakersyed__, the one piece where we see integration with openstack that we should test explicitly here: maybe testing against AIO builds with ansible (but that's really integration testing); and perhaps testing against some prebuilt nova setup when we implement virtualized variables15:30
sulopalendae: cool thats good to know15:30
sigmavirusIdk how kolla would test on openstack CI otherwise15:30
palendaeGuessing Kolla spins up docker instances too15:30
sulosigmavirus: palendae: yeah good point15:30
jimbakeryeah, this is pretty essential for actually testing openstack type stuff. one would think :)15:30
sigmavirusjimbaker: docker? yeah, no15:31
sigmavirusCraton is the only project that has a dockerfile and uses it as part of development afaik15:31
jimbakerjust a question of how flexible the specifics are, and then how much we can abuse :)15:31
*** woodard has joined #openstack-meeting-415:31
jimbakersigmavirus, so that's the abuse part15:31
jimbakeranyway, we will find out more. i'm not terribly worried about getting a docker daemon setup, given that we should be able to get a VM in the testing process. it just might be easier15:32
*** vhoward has joined #openstack-meeting-415:33
jimbakerand something we can just build oin15:33
jimbakeron15:33
*** numans has quit IRC15:33
*** makowals has quit IRC15:33
sulojimbaker: what15:33
sulowhich vm ?15:33
jimbakersulo, with respect to running our tests on openstack infra15:33
*** anilvenkata has quit IRC15:33
jimbakersulo, please ignore these concerns for now - i don't see any impact on what we are trying to do in terms of a dockerized way to do functional testing15:34
*** spotz is now known as spotz_zzz15:34
jimbakersulo, sound good?15:35
suloyes15:35
sulothats all from my side15:35
*** spotz_zzz is now known as spotz15:36
jimbakersulo, thanks!15:36
jimbakerpalendae, good meeting with the OSA team last week in terms of figuring out OSA integration. anything more you want to discuss about what you plan to be working on this week?15:36
palendaejimbaker: I'm going to try to push forward on our refactorings and high level APIs15:37
jimbakerwhich means being able to put in some db backend in, like craton15:37
palendaeYeah, I think we'll need to get further along with the separations, but we're close15:38
*** matrohon has joined #openstack-meeting-415:38
palendaeThere are some reviews from stevelle up now that are putting our existing implementations behind our agreed APIs15:38
jimbakerit seems like the merge approach means that it's really easy for craton as it is now15:38
*** pc_m has left #openstack-meeting-415:39
jimbakerwe will find out shortly enough, which is good15:39
*** oanson has quit IRC15:39
jimbakersulo, quick question - what's the status of being able to get at containers in the rest api? i would assume this is just using the host api, right? (since addressable)15:40
suloyep15:40
sulodevice_type=container15:40
jimbakercool, just wanted to verify that assumption, and yeah, device_type15:41
jimbakerdocs anyone? ;)15:41
jimbakerwe will get there15:41
sulothis reminds me15:41
sulowe dont verify device_type .. perhaps we should15:41
sulowhat i mean is .. you can put device_type=<anything>15:41
jimbakersulo, in terms of a defined set of device_types?15:42
suloyeah15:42
jimbakermaybe this should be a config option15:42
jimbakercould have a separate db table, seems more than what we need15:42
jimbakerdon't want to hardcode however15:42
suloi mean this could be as siimple as validating it to few predefined string15:43
jimbakerright, but it would be enumerated in the craton config15:43
sulojimbaker: it can be in jsonschema vlidation schema15:43
sulojimbaker: yeah can do that15:43
jimbakersulo, jsonschema seems too hardcoded to me15:43
jimbakerjsonschema should just know it's a string15:44
sulojimbaker: how do you mean, the schema is hardcoded15:44
*** makowals has joined #openstack-meeting-415:44
suloanyway .. its not too important how we do it15:44
jimbakersulo, because it seems like a valid config option for users15:44
suloyeah15:44
sulowe can make it a config option15:45
jimbakersulo, cool15:45
sulolets create isuue for this for now15:45
sulowe can disscuss more when we get to it15:45
jimbaker#action sulo add issue for device_type configuration15:45
*** tuan_luong has quit IRC15:46
jimbakersyed__, what are plans for this week?15:46
jimbakeryour plans?15:46
syed__So i will be working on crud devices to users, plus working on writing appropriate test and schema entries in client as per our current schema for regions, cells, hosts etc15:46
*** woodard has quit IRC15:46
jimbakersyed__, +115:47
jimbakerwe will also follow up on RBAC this week15:47
syed__sure, looking forward towards that15:47
*** woodard has joined #openstack-meeting-415:47
jimbakerme: work on blueprints (including RBAC with syed__); and finalize the resolution_order branch that's almost ready on my laptop15:48
jimbakeralso i promised harlowja a fix on listener support in taskflow, so i will get that in15:48
jimbakeras time: revisit the taskflow stuff i did prior to the summit15:48
jimbakeralmost got that working, but ran out of time15:49
*** Sukhdev has joined #openstack-meeting-415:49
jimbakerso that was a nice discussion for the week. we will check in with jovon when he get in the office15:50
syed__Sounds good to me15:50
jimbakerpalendae, sigmavirus, sulo, syed__, any other topics we should cover for today?15:50
sulohttps://blueprints.launchpad.net/craton/+spec/craton-notifications15:51
sulojust going to drop that here for everyone to looksee15:51
suloin case someone wants to pick it up and run with it15:51
jimbakersulo, ahh interesting. what are your thoughts on this implementation? it's very much related to RBAC given governance15:51
jimbakeri do see this as a separable task from say following the db's write ahead log15:52
*** bobmel has joined #openstack-meeting-415:53
suloyeah .. need to check if there is already a notification thing in oslo15:53
jimbakersulo, there's also the governance concern that we discussed last week re keeping variable versions around15:53
suloah yes15:53
sulothats a separate bp i need to create15:53
jimbakersulo, i think we can do that in the context of the blame system15:53
suloyeah .. the versioning could be15:54
jimbakerbtw, in my branch, i move blame such that it's a method on anything that mixes in variables15:54
*** logan- has quit IRC15:54
jimbakerso could readily add a parameter to the method to get old versions, etc15:55
sulosounds good to me15:55
*** dgonzalez is now known as dgonzalez__15:55
*** dgonzalez__ is now known as dgonzalez15:55
jimbakersulo, re notification - assuming everything goes through the python api, vs directly against the db, this should be straightforward. maybe a mixin or just an addition to the craton base?15:56
jimbakermuch like create, modified timestamp support15:57
jimbakeranyway we should certainly see if there's something preexisting in oslo that could support.\15:57
*** yamahata has quit IRC15:57
jimbakerok, time to wrap up the meeting15:58
jimbakerany other questions?15:58
*** tonytan4ever has quit IRC15:58
jimbakerconcerns?15:58
syed__i am good15:58
syed__thanks jimbaker15:58
*** yamahata has joined #openstack-meeting-415:58
*** tonytan4ever has joined #openstack-meeting-415:58
jimbakercool, let's just move over to #craton15:58
jimbakerthanks everyone!15:58
jimbaker#endmeeting15:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:58
openstackMeeting ended Mon Nov 14 15:58:54 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-11-14-15.02.html15:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-11-14-15.02.txt15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-11-14-15.02.log.html15:58
*** git-harry has left #openstack-meeting-415:59
SukhdevFolks, time for Ironic-neutron meeting16:00
*** hshiina has joined #openstack-meeting-416:00
*** limao_ has quit IRC16:01
*** logan- has joined #openstack-meeting-416:01
Sukhdevwho is here  ?16:01
sambettso/16:02
*** korzen has quit IRC16:02
Sukhdevlets get started16:02
jroll\o16:02
Sukhdev#startmeeting ironic_neutron16:02
openstackMeeting started Mon Nov 14 16:02:32 2016 UTC and is due to finish in 60 minutes.  The chair is Sukhdev. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: ironic_neutron)"16:02
openstackThe meeting name has been set to 'ironic_neutron'16:02
Sukhdev#topic: Agenda16:02
*** openstack changes topic to ": Agenda (Meeting topic: ironic_neutron)"16:02
Sukhdev#link: https://wiki.openstack.org/wiki/Meetings/Ironic-neutron#Meeting_November_14.2C_201616:02
Sukhdevanybody wants anything added to the agenda?16:03
Sukhdev#topic: Announcements16:03
*** openstack changes topic to ": Announcements (Meeting topic: ironic_neutron)"16:03
Sukhdevany announcements?16:04
*** rbak has quit IRC16:04
sambettsAttach/Detach VIF spec landed16:04
sambettsso those patches need updating and reviewing16:04
*** haleyb_ has quit IRC16:04
*** rbak has joined #openstack-meeting-416:04
Sukhdevcool16:05
sambettsvasyl is helping me update the client side patch because the API design changed at the last minute16:05
*** lihi has quit IRC16:05
sambettsI'm nearly done updating the Ironic side16:05
Sukhdevsambetts : thanks16:06
SukhdevI spent some time last weekend organizing the wiki to reflect all the correct patches16:07
*** zenoway has quit IRC16:07
jroll\o/16:07
SukhdevI should not call these patches POC code anymore :-)16:08
*** zenoway has joined #openstack-meeting-416:08
Sukhdevmake sure all the patches are listed there - it is easier to keep track of them16:08
*** haleyb_ has joined #openstack-meeting-416:08
Sukhdev#topic: Security Groups16:09
*** openstack changes topic to ": Security Groups (Meeting topic: ironic_neutron)"16:09
*** dimak has quit IRC16:09
jrollthis one is close16:09
SukhdevI noticed last week there were lot of reviews of the SG patches16:09
jrolljust missing some test cases16:09
Sukhdevjroll : I am confused about the test cases that are needed16:10
jrollSukhdev: what's confusing?16:10
Sukhdevjroll : about the neutron client setup for SG16:10
Sukhdevfor the verification16:11
jrollnot sure what you mean16:11
jrollmy comments say what is missing16:11
*** corey_ has joined #openstack-meeting-416:11
*** belmorei_ has quit IRC16:11
*** makowals has quit IRC16:11
*** zenoway has quit IRC16:12
Sukhdevjroll : not about what is missing - how to go about part - let me ping you offline16:12
jrollSukhdev: sure, sounds good16:12
*** reedip_outofmemo has joined #openstack-meeting-416:12
Sukhdevother than that this is pretty much good to go16:13
*** belmoreira has joined #openstack-meeting-416:13
*** cleong has quit IRC16:13
SukhdevI will try to add tests for verification part and upload it16:13
Sukhdevany body else has any question about it other than test?16:14
Sukhdev#topic: Port Groups16:14
*** openstack changes topic to ": Port Groups (Meeting topic: ironic_neutron)"16:14
SukhdevPort Groups is also looking good16:14
SukhdevIronic patches are merged -16:15
jrollthere's still a few ironic patches https://review.openstack.org/#/q/topic:bug/161875416:15
jrollbut yeah, we're getting there16:16
jrollonly one is code, the rest are docs/tests16:16
Sukhdevright16:16
Sukhdevnova side16:17
Sukhdevnova side is sitting with -ve votes16:18
jrollnova spec is looking good, hoping it'll get some eyes this week https://review.openstack.org/#/c/387534/16:18
jrollnova spec freeze is thursday16:18
Sukhdevwe have few days - hopefully, this go16:19
jrollya :)16:19
*** m-greene has quit IRC16:19
*** makowals has joined #openstack-meeting-416:20
Sukhdevanything else on PG?16:21
Sukhdev#topoic: Vlan Aware Servers16:21
*** alij has joined #openstack-meeting-416:21
sambettsI don't think that worked :-p16:22
jrollhonestly I don't expect to see this make progress until late ocata or pike16:22
jrollgotta finish attach/detach and portgroups first16:22
jrollsambetts: agree?16:23
sambettsYeah, they are certainly higher priority and we aren't going to get the nova spec for the configdrive in before freeze16:23
*** unicell has quit IRC16:24
*** pcaruana has joined #openstack-meeting-416:24
sambettsother than that part everything else should be Ironic side16:25
jrollyep16:25
Sukhdevthat naturally leads to the next topic -16:26
Sukhdev#topic: Attach/detach API16:26
*** openstack changes topic to ": Attach/detach API (Meeting topic: ironic_neutron)"16:26
Sukhdevas sambetts pointed out - the spec is now approved16:26
jrollas well as the nova blueprint16:27
jrollso time to get moving on code :D16:27
Sukhdevsambetts : I listed three patches on the wiki (nova, ironic, client)16:27
jrollwe also decided nova portgroups depends on this, it will make it much simpler to implement16:27
*** haley__ is now known as haley16:28
sambettsYeah and that was a question I had, do you want my attach/detach spec API patch to Ironic to include the portgroups mapping logic and the port mapping logic or just the port part with portgroups in a follow up16:28
sambettss/spec//16:28
jrollsambetts: not sure, I suspect the latter, just for smaller patches16:29
sambettsyeah thats what I was thinking16:29
Sukhdevwe need it for both though16:31
*** haleyb_ has quit IRC16:31
jrollnobody disagrees :)16:31
sambettsCool, the status of the patches are: Ironic one is nearly finished being updated16:32
sambettsIronic Client one Vasyl was going to update for me16:32
*** jovon has joined #openstack-meeting-416:32
jrollnice16:32
sambettsand Nova one will need updating once client functions are laided out16:33
*** haley is now known as haleyb16:33
*** belmoreira has quit IRC16:33
*** Jeffrey4l has quit IRC16:33
Sukhdevsounds reasonable - anything else on this?16:35
sambettsNothing else from me16:35
sambettsjust pushing on with it16:35
jrollditto16:36
Sukhdevwith my change in job, I am trying to set up the BM environment so that I can test all of this16:36
SukhdevI lost my setup when I left Arista :-)16:36
Sukhdev#topic: Open Discussion16:36
*** openstack changes topic to ": Open Discussion (Meeting topic: ironic_neutron)"16:37
* sambetts is also working to build a new test environment after mine was aquired by another team :( 16:37
Sukhdevsambetts : ha ha - it can be painful16:37
sambettsyeah16:38
Sukhdevanybody wants to discuss anything else networking related?16:38
sambettsbtw what are the plans/goals for 3rd party CI of the network drivers + ml2 supprt?16:38
sambettshave we laid out any rules for that?16:39
*** vhoward has quit IRC16:39
sambettss/rules/goals16:39
*** amotoki has quit IRC16:39
jrollwe haven't16:39
jrollit really shouldn't differ based on driver, right?16:39
*** beekneemech is now known as bnemec16:40
sambettsno, jsut different local_link_connection info to be passed for different vendors16:40
Sukhdevsambetts : that is part of the CI test setup16:41
sambettsthe unit tests?16:41
jrollsambetts: hrm, those vendors don't have code in ironic, so seems like it'd be weird to ask them for CI16:41
SukhdevI can give you example of how we did at Arista16:42
sambettsjroll: yeah :/ its more of a cross project ml2 driver repo X ironic CI I guess, like how nova CI's ironic16:42
sambettsso networking-cisco should proably CI Ironic or the other way around16:43
jrollya16:43
Sukhdevsambetts : you do not need ironic specific CI - unless you want to test the internals of ironic through CI16:43
jrollthe first, I think16:43
sambettsyeah that seems to make the most sense, to make sure nothing that merges into net-cisco breaks the intergration with ironic16:44
Sukhdevyup - so, there are two parts to it sambetts16:45
Sukhdev1) the merges into networking-cisco - those are your local unit tests16:45
Sukhdev2) the CI to catch the issues with upstream - i.e at the API integration level16:45
Sukhdevthat is the way I had setup for Arista - it works very effectively16:46
Sukhdevunless, you want an overkill :-):-)16:46
sambettsyeah, I'll have to play around and see what extra equipment I can squeeze into my CI environment :)16:47
sambettsthats all I had today16:50
Sukhdevanything else - anybody?16:50
jrollnope :)16:50
Sukhdevcool - we are done16:50
Sukhdevthanks16:50
jrollthanks Sukhdev16:50
Sukhdev#endmeeting16:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:51
openstackMeeting ended Mon Nov 14 16:50:59 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:51
sambettso/16:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-11-14-16.02.html16:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-11-14-16.02.txt16:51
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-11-14-16.02.log.html16:51
*** alij has quit IRC16:51
*** m-greene has joined #openstack-meeting-416:52
*** alij has joined #openstack-meeting-416:55
*** alij has quit IRC17:00
thedaco/17:00
gnuoy\o17:00
thedacI'll wait for a few more people before starting the meeting.17:00
*** asettle__ has joined #openstack-meeting-417:00
iceyheh17:00
*** vsaienk0 has joined #openstack-meeting-417:01
*** mjturek1 has joined #openstack-meeting-417:01
thedacWell we should probably get started anyway17:01
thedac#startmeeting charms17:01
openstackMeeting started Mon Nov 14 17:01:48 2016 UTC and is due to finish in 60 minutes.  The chair is thedac. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: charms)"17:01
openstackThe meeting name has been set to 'charms'17:01
*** vsaienk0 has left #openstack-meeting-417:01
thedacWelcome everyone17:02
thedac#topic Review ACTION points from previous meeting17:02
*** openstack changes topic to "Review ACTION points from previous meeting (Meeting topic: charms)"17:02
iceyo/17:02
thedacLooking at the meeting notes ...17:02
thedacACTION: beisner regular upgrade tests17:02
jamespageo/17:02
thedacbeisner: around? ^^17:02
gnuoyI think that ones supposed to be closed17:02
thedacok next17:02
*** matrohon has quit IRC17:03
thedacACTION: jamespage to identity alternate week slot and get scheduled (carried forward)17:03
*** asettle has quit IRC17:03
* jamespage hangs head in shame17:03
jamespageplease carry that forward17:03
thedacheh17:03
thedacwill do17:03
jamespageI'm not doing a great job at that I am17:03
thedacACTION: all to read through the charm specs: http://specs.openstack.org/openstack/charm-specs/17:03
*** mjturek1 is now known as mjturek17:03
thedacNow I am holding my head in shame. I'll do that today17:03
thedacShould we carry that forward as well?17:04
icey+117:04
tinwood+117:04
coreycbo/17:04
thedacok17:04
*** hshiina has left #openstack-meeting-417:04
thedaclast one17:04
thedacACTION: jamespage allocate days in month for bug squashing.17:04
*** Sukhdev has quit IRC17:04
jamespagecarry pls17:04
thedacwill do17:05
*** cholcombe has joined #openstack-meeting-417:05
thedac#topic State of Development for next Charm Release17:05
*** openstack changes topic to "State of Development for next Charm Release (Meeting topic: charms)"17:05
*** mjturek has left #openstack-meeting-417:05
thedacjamespage and gnuoy any comments from the last couple of weeks?17:05
gnuoyInput on https://review.openstack.org/#/c/397241/ would be much appreciated17:05
beisnero/ apologies, was tied up.  hi all.17:05
thedachey beisner17:05
*** uck has joined #openstack-meeting-417:06
*** asettle__ is now known as asettle17:06
jamespageok so focus should be on specs right now17:06
jamespagewe have a few already approved17:06
jamespageI have gnuoy's lb spec on my list to  review tomorrow17:06
jamespagespecs only required for new features17:06
thedacok, I'll take a read through the LB spec as well to see how it has evolved since my last conversation with gnuoy on the topic17:07
thedacAny other comments on the state of development?17:07
beisnerre: regular upgrade tests;  we do run the single-hop upgrades now (L:M or M:N).  but, we've got that on the list for doing multi-step L:K:M type upgrades.  no cycles to move forward on that so far.17:07
*** vmorris has joined #openstack-meeting-417:07
gnuoythedac, tinwood has a charm inbound I believe17:08
gnuoyM-something17:08
beisnerha!17:08
gnuoyManilla!17:08
tinwoodmanila, manila-generic17:08
tinwood:)17:08
thedac\o/17:08
gnuoyMurano, Manilla, Mistral it blurs17:08
tinwoodindeed.17:08
thedacbeisner: got it. Should that remain on this list of actions? Or due to its long running nature be tracked somwhere else?17:08
thedacAll the Ms17:08
cargonzao/17:08
thedacOk, moving forward17:09
thedac#topic High Priority Bugs17:09
beisnerthedac, not sure.  it will likely not be resolved before the next meeting.17:09
*** openstack changes topic to "High Priority Bugs (Meeting topic: charms)"17:09
thedacOpenStack bugs at: https://bugs.launchpad.net/openstack-charms17:09
thedacAnything to highlight?17:09
gnuoyHow are the rabbits?17:09
thedacI think we quashed the DNS short hostname bug.17:09
*** sdake has quit IRC17:10
gnuoykk17:10
thedacThat is out in the wild and I have not heard complaints yet17:10
beisner🐇🐇🐇17:10
thedacfeedback welcome of course17:10
thedacothers?17:10
thedacMoving on ...17:10
thedac#topic Openstack Events17:11
*** openstack changes topic to "Openstack Events (Meeting topic: charms)"17:11
thedacWhat is coming up?17:11
thedacbeisner: you mentioned some deadlines recently can you post those here?17:11
beisnerah, yes.  juju charmer summit proposals + config mgmt camp proposals.  one sec, links inbound.17:12
thedacthank you17:12
*** sdake has joined #openstack-meeting-417:13
beisnerfosdem:  deadline is today Nov 14 - https://fosdem.org/2017/news/2016-07-20-call-for-participation/17:13
jamespageurgh17:13
jamespageI though it wsa end of the week17:13
beisnercfg mgmt camp:  https://docs.google.com/forms/d/e/1FAIpQLSeAMyDhrz4Z-xcSvCIroDoA1EKy-FhWIRwg8CEwjB1Lt9GM_g/viewform?c=0&w=1   (not sure of deadline but i believe it is this wk)17:14
beisnerjuju charmer summit:  http://summit.juju.solutions/17:14
thedacthanks, beisner17:14
jamespageyah 18th17:14
*** m-greene has left #openstack-meeting-417:14
thedacAlso Project Teams Gathering is in February in Atlanta, correct?17:14
thedac#link https://www.openstack.org/ptg/17:15
thedacany others?17:15
beisner#link http://summit.juju.solutions/17:15
beisner#link https://fosdem.org/2017/news/2016-07-20-call-for-participation/17:15
beisnerforgat about that fancy meet bot stuff17:15
thedac:)17:15
thedacmoving forward ...17:15
thedac#topic Open Discussion17:15
*** openstack changes topic to "Open Discussion (Meeting topic: charms)"17:15
thedacRelease the orangutans!17:16
gnuoydo we need to charm up any more ceilometer fragments17:16
gnuoy?17:16
gnuoyI'm just going to pick random words17:16
gnuoygnochi ?17:16
thedacgnuoy: is gnochi in Ocata? I suspect we will need to17:17
gnuoynot sure tbh17:18
gnuoythedac, action me with taking a look17:18
beisnerwas panko a new thing spinning out of/around ceilo?17:19
thedac#action gnuoy determine which openstack release gnochi will be in17:19
coreycbyeah i think we need to get an understanding of which pieces of ceilometer we need, also affects getting packages into main17:19
gnuoycoreycb, agreed17:20
gnuoyas beisner says panko is definitely a thing too17:20
thedacgnuoy: can I update that action item to be ceilometer micro services17:20
gnuoy+117:20
thedacok17:20
thedacAny other open discussion items?17:20
jamespageo/17:20
jamespageyeah sorry doing two things at once does not work17:21
jamespagere the PTG17:21
thedacyes17:21
jamespagewe can have a room for the event, but I only think that's worth doing if we get some wider attendees17:21
jamespageso I was going to ping the devs who expressed interest in barcelona in becoming official projects as part of charms17:22
thedacOK17:22
thedacOne more call for open discussion17:22
thedacAlright thanks everyone17:23
thedac#endmeeting17:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:23
openstackMeeting ended Mon Nov 14 17:23:04 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-11-14-17.01.html17:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-11-14-17.01.txt17:23
openstackLog:            http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-11-14-17.01.log.html17:23
tinwoodthedac: thanks!17:23
gnuoythanks thedac17:23
iceythanks thedac17:23
*** alij has joined #openstack-meeting-417:25
thedacicey: fyi, you are up next for chair17:25
iceyI saw thedac :-/17:26
*** alij has quit IRC17:30
*** vmorris has left #openstack-meeting-417:30
*** yfauser has joined #openstack-meeting-417:32
*** uck has quit IRC17:32
*** m-greene_ has joined #openstack-meeting-417:32
*** uck has joined #openstack-meeting-417:33
*** m-greene_ is now known as m-greene17:33
*** iberezovskiy is now known as iberezovskiy|off17:33
*** m-greene has quit IRC17:34
*** sdake_ has joined #openstack-meeting-417:34
*** sdake has quit IRC17:37
*** lakerzhou has quit IRC17:40
*** alij has joined #openstack-meeting-417:42
*** alij has quit IRC17:46
*** armax has joined #openstack-meeting-417:49
*** yamahata has quit IRC17:50
*** liuyulong has quit IRC17:52
*** devananda|away is now known as devananda17:52
*** liuyulong has joined #openstack-meeting-417:52
*** mbirru has joined #openstack-meeting-417:57
*** sambetts is now known as sambetts|afk18:01
*** reedip_outofmemo has quit IRC18:02
*** ralonsoh has quit IRC18:02
*** GB21 has joined #openstack-meeting-418:06
*** reedip_outofmemo has joined #openstack-meeting-418:06
*** haleyb_ has joined #openstack-meeting-418:07
*** pbourke has quit IRC18:07
*** pbourke has joined #openstack-meeting-418:09
*** yfauser has quit IRC18:15
*** s3wong has joined #openstack-meeting-418:20
*** bobh has joined #openstack-meeting-418:24
*** cartik has joined #openstack-meeting-418:24
*** anilvenkata has joined #openstack-meeting-418:25
*** Jeffrey4l has joined #openstack-meeting-418:31
*** alij has joined #openstack-meeting-418:32
*** alij has quit IRC18:37
*** unicell1 has joined #openstack-meeting-418:41
*** oshidoshi has quit IRC18:48
*** cwolferh has quit IRC18:49
*** cwolferh has joined #openstack-meeting-418:50
*** asettle has quit IRC18:52
*** GB21 has quit IRC18:52
*** m-greene has joined #openstack-meeting-418:59
*** bobh has quit IRC19:02
*** Sukhdev has joined #openstack-meeting-419:12
*** hemanth is now known as hemanth|lunch19:15
*** haleyb_ has quit IRC19:17
*** yuelongguang has quit IRC19:20
*** yamamoto has quit IRC19:20
*** yuelongguang has joined #openstack-meeting-419:21
*** belmoreira has joined #openstack-meeting-419:23
*** belmoreira has quit IRC19:27
*** Swami has joined #openstack-meeting-419:30
*** hongbin has joined #openstack-meeting-419:45
*** cartik has quit IRC19:56
*** woodster_ has joined #openstack-meeting-420:01
*** bobmel_ has joined #openstack-meeting-420:02
*** hemanth|lunch is now known as hemanth20:02
*** cwolferh has quit IRC20:03
*** bobmel has quit IRC20:05
*** uck_ has joined #openstack-meeting-420:06
*** uck has quit IRC20:06
*** cartik has joined #openstack-meeting-420:07
*** iyamahat has joined #openstack-meeting-420:08
*** cwolferh has joined #openstack-meeting-420:10
*** sdake_ is now known as sdake20:11
*** kylek3h is now known as kylek3h_away20:12
*** haleyb_ has joined #openstack-meeting-420:14
*** dtardivel has quit IRC20:14
*** haleyb_ has quit IRC20:18
*** yamamoto has joined #openstack-meeting-420:21
*** yamamoto has quit IRC20:25
*** cartik has quit IRC20:29
*** kylek3h_away is now known as kylek3h20:30
*** anilvenkata has quit IRC20:38
*** vhoward has joined #openstack-meeting-420:40
*** pcaruana has quit IRC20:45
*** yamahata has joined #openstack-meeting-420:50
*** yamahata has quit IRC20:50
*** yamahata has joined #openstack-meeting-420:53
*** rtheis has quit IRC20:56
*** MeganR has joined #openstack-meeting-420:57
*** slaweq_ has joined #openstack-meeting-421:03
*** vishnoianil has quit IRC21:04
*** Rockyg has joined #openstack-meeting-421:04
*** galstrom_zzz is now known as galstrom21:04
*** alij has joined #openstack-meeting-421:13
*** uxdanielle has joined #openstack-meeting-421:15
*** spzala has joined #openstack-meeting-421:15
*** m-greene has quit IRC21:15
*** julim has quit IRC21:16
*** m-greene has joined #openstack-meeting-421:17
*** alij has quit IRC21:17
*** Julien-zte has joined #openstack-meeting-421:25
*** uxdanielle has quit IRC21:28
*** Jeffrey4l has quit IRC21:34
*** tonytan4ever has quit IRC21:45
*** uxdanielle has joined #openstack-meeting-421:49
*** rainya has joined #openstack-meeting-421:53
*** liangy has joined #openstack-meeting-421:55
*** corey_ has quit IRC21:56
*** berendt has quit IRC21:57
*** galstrom is now known as galstrom_zzz21:58
*** slaweq_ has left #openstack-meeting-421:59
*** Swami has quit IRC22:00
*** woodard_ has joined #openstack-meeting-422:01
*** woodard_ has quit IRC22:03
*** MeganR has quit IRC22:03
*** woodard_ has joined #openstack-meeting-422:03
*** woodard has quit IRC22:04
*** woodard_ has quit IRC22:05
*** woodard has joined #openstack-meeting-422:05
*** vhoward has quit IRC22:09
*** woodard has quit IRC22:10
*** haleyb_ has joined #openstack-meeting-422:15
*** jovon has quit IRC22:17
*** haleyb_ has quit IRC22:20
*** kylek3h has quit IRC22:23
*** jovon has joined #openstack-meeting-422:26
*** thorst_ has quit IRC22:30
*** JRobinson__ has joined #openstack-meeting-422:35
*** dave-mccowan has quit IRC22:38
*** baoli has quit IRC22:40
*** klamath has quit IRC22:45
*** klamath has joined #openstack-meeting-422:46
*** klamath is now known as klamath_22:46
*** Swami has joined #openstack-meeting-422:46
*** Swami has quit IRC22:46
*** spotz is now known as spotz_zzz22:47
*** Swami has joined #openstack-meeting-422:47
*** Swami_ has joined #openstack-meeting-422:47
*** uxdanielle has quit IRC22:51
*** rainya has quit IRC22:52
*** thorst has joined #openstack-meeting-422:53
*** kylek3h has joined #openstack-meeting-422:56
*** spzala has quit IRC22:56
*** kylek3h has quit IRC22:56
*** neiljerram has quit IRC22:57
*** kylek3h has joined #openstack-meeting-422:57
*** woodard has joined #openstack-meeting-422:57
*** thorst has quit IRC22:57
*** yfauser has joined #openstack-meeting-422:59
*** s3wong_ has joined #openstack-meeting-423:02
*** uck_ has quit IRC23:02
*** galstrom_zzz is now known as galstrom23:02
*** uck has joined #openstack-meeting-423:03
*** s3wong has quit IRC23:05
*** lamt has quit IRC23:05
*** hongbin has quit IRC23:05
*** kylek3h_ has joined #openstack-meeting-423:13
*** kylek3h has quit IRC23:13
*** kylek3h_ has quit IRC23:16
*** kylek3h has joined #openstack-meeting-423:16
*** myatsenko has quit IRC23:16
*** yamamoto_ has joined #openstack-meeting-423:24
*** kylek3h is now known as kylek3h_away23:27
*** galstrom is now known as galstrom_zzz23:28
*** Jeffrey4l has joined #openstack-meeting-423:31
*** irenab has quit IRC23:36
*** Julien-zte has quit IRC23:37
*** yamamoto_ has quit IRC23:50
*** yfauser has quit IRC23:55

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