*** yifei has quit IRC | 00:00 | |
*** yifei has joined #openstack-meeting-4 | 00:03 | |
*** thorst_ has joined #openstack-meeting-4 | 00:38 | |
*** yamahata has joined #openstack-meeting-4 | 00:40 | |
*** bobmel has quit IRC | 00:42 | |
*** thorst_ has quit IRC | 00:43 | |
*** tovin07 has joined #openstack-meeting-4 | 01:00 | |
*** limao has joined #openstack-meeting-4 | 01:01 | |
*** limao has quit IRC | 01:02 | |
*** limao has joined #openstack-meeting-4 | 01:02 | |
*** bobh has joined #openstack-meeting-4 | 01:25 | |
*** amotoki has joined #openstack-meeting-4 | 01:25 | |
*** zhurong has joined #openstack-meeting-4 | 01:26 | |
*** bobh has quit IRC | 01:30 | |
*** zhurong has quit IRC | 01:34 | |
*** zhurong has joined #openstack-meeting-4 | 01:34 | |
*** amotoki has quit IRC | 01:34 | |
*** amotoki has joined #openstack-meeting-4 | 01:35 | |
*** amotoki has quit IRC | 01:47 | |
*** amotoki has joined #openstack-meeting-4 | 01:51 | |
*** amotoki has quit IRC | 01:53 | |
*** amotoki has joined #openstack-meeting-4 | 01:55 | |
*** bobh has joined #openstack-meeting-4 | 02:01 | |
*** amotoki has quit IRC | 02:03 | |
*** bobh has quit IRC | 02:05 | |
*** sdake has quit IRC | 02:08 | |
*** tovin07 is now known as tovin07_ | 02:08 | |
*** tovin07 has joined #openstack-meeting-4 | 02:09 | |
*** tovin07_ has quit IRC | 02:10 | |
*** tovin07 has quit IRC | 02:10 | |
*** tovin07 has joined #openstack-meeting-4 | 02:11 | |
*** tovin07_ has joined #openstack-meeting-4 | 02:11 | |
*** sdake has joined #openstack-meeting-4 | 02:12 | |
*** thorst_ has joined #openstack-meeting-4 | 02:12 | |
*** gongysh has joined #openstack-meeting-4 | 02:12 | |
*** tovin07__ has joined #openstack-meeting-4 | 02:12 | |
*** tovin07__ has quit IRC | 02:13 | |
*** tovin07_ has quit IRC | 02:13 | |
*** tovin07_ has joined #openstack-meeting-4 | 02:13 | |
*** tovin07__ has joined #openstack-meeting-4 | 02:13 | |
*** tovin07__ has quit IRC | 02:13 | |
*** tovin07_ has quit IRC | 02:13 | |
*** tovin07_ has joined #openstack-meeting-4 | 02:14 | |
*** tovin07_ has quit IRC | 02:15 | |
*** tovin07_ has joined #openstack-meeting-4 | 02:16 | |
*** tovin07 has quit IRC | 02:16 | |
*** tovin07_ is now known as tovin07 | 02:16 | |
*** thorst_ has quit IRC | 02:17 | |
*** tovin07 is now known as tovin07_ | 02:17 | |
*** thorst_ has joined #openstack-meeting-4 | 02:17 | |
*** tovin07_ is now known as tovin07 | 02:18 | |
*** tovin07 has quit IRC | 02:18 | |
*** tovin07 has joined #openstack-meeting-4 | 02:18 | |
*** tovin07_ has joined #openstack-meeting-4 | 02:19 | |
*** amotoki has joined #openstack-meeting-4 | 02:23 | |
*** baoli has quit IRC | 02:25 | |
*** baoli has joined #openstack-meeting-4 | 02:26 | |
*** thorst_ has quit IRC | 02:28 | |
*** baoli has quit IRC | 02:28 | |
*** baoli has joined #openstack-meeting-4 | 02:28 | |
*** thorst_ has joined #openstack-meeting-4 | 02:28 | |
*** armax has quit IRC | 02:33 | |
*** baoli has quit IRC | 02:37 | |
*** thorst_ has quit IRC | 02:37 | |
*** bobh has joined #openstack-meeting-4 | 02:38 | |
*** baoli has joined #openstack-meeting-4 | 02:39 | |
*** tonytan4ever has quit IRC | 02:39 | |
*** armax has joined #openstack-meeting-4 | 02:49 | |
*** bobmel has joined #openstack-meeting-4 | 02:54 | |
*** armax has quit IRC | 02:55 | |
*** bobmel has quit IRC | 02:58 | |
*** baoli has quit IRC | 03:01 | |
*** bobh has quit IRC | 03:03 | |
*** bobh has joined #openstack-meeting-4 | 03:05 | |
*** bobh has quit IRC | 03:06 | |
*** dave-mccowan has quit IRC | 03:09 | |
*** julim_ has joined #openstack-meeting-4 | 03:26 | |
*** thorst_ has joined #openstack-meeting-4 | 03:26 | |
*** julim has quit IRC | 03:28 | |
*** thorst_ has quit IRC | 03:28 | |
*** thorst_ has joined #openstack-meeting-4 | 03:28 | |
*** amotoki has quit IRC | 03:30 | |
*** gongysh has quit IRC | 03:36 | |
*** thorst_ has quit IRC | 03:37 | |
*** amotoki has joined #openstack-meeting-4 | 03:40 | |
*** links has joined #openstack-meeting-4 | 03:55 | |
*** coolsvap has joined #openstack-meeting-4 | 04:10 | |
*** sdake has quit IRC | 04:21 | |
*** baoli has joined #openstack-meeting-4 | 04:25 | |
*** baoli has quit IRC | 04:30 | |
*** thorst_ has joined #openstack-meeting-4 | 04:35 | |
*** thorst_ has quit IRC | 04:42 | |
*** prateek has joined #openstack-meeting-4 | 04:54 | |
*** prateek has quit IRC | 04:54 | |
*** GB21 has joined #openstack-meeting-4 | 05:03 | |
*** limao has quit IRC | 05:13 | |
*** limao has joined #openstack-meeting-4 | 05:13 | |
*** Jeffrey4l has joined #openstack-meeting-4 | 05:21 | |
*** GB21 has quit IRC | 05:25 | |
*** GB21 has joined #openstack-meeting-4 | 05:37 | |
*** thorst_ has joined #openstack-meeting-4 | 05:40 | |
*** janki has joined #openstack-meeting-4 | 05:43 | |
*** anilvenkata has joined #openstack-meeting-4 | 05:44 | |
*** thorst_ has quit IRC | 05:47 | |
*** trinaths has joined #openstack-meeting-4 | 05:48 | |
*** armax has joined #openstack-meeting-4 | 05:53 | |
*** bobmel has joined #openstack-meeting-4 | 05:54 | |
*** mohankumar has joined #openstack-meeting-4 | 05:57 | |
*** armax has quit IRC | 05:58 | |
*** bobmel has quit IRC | 05:58 | |
*** numans has joined #openstack-meeting-4 | 06:01 | |
*** xuao has joined #openstack-meeting-4 | 06:02 | |
*** amotoki has quit IRC | 06:03 | |
*** xuao has quit IRC | 06:06 | |
*** yfauser has joined #openstack-meeting-4 | 06:09 | |
*** eyalb has joined #openstack-meeting-4 | 06:16 | |
*** yfauser has quit IRC | 06:32 | |
*** thorst_ has joined #openstack-meeting-4 | 06:46 | |
*** thorst_ has quit IRC | 06:53 | |
*** amotoki has joined #openstack-meeting-4 | 06:53 | |
*** armax has joined #openstack-meeting-4 | 06:55 | |
*** irenab has joined #openstack-meeting-4 | 06:56 | |
*** trinaths has left #openstack-meeting-4 | 06:57 | |
*** armax has quit IRC | 07:00 | |
*** berendt has joined #openstack-meeting-4 | 07:00 | |
*** berendt has quit IRC | 07:00 | |
*** berendt has joined #openstack-meeting-4 | 07:01 | |
*** amotoki has quit IRC | 07:08 | |
*** gongysh has joined #openstack-meeting-4 | 07:12 | |
*** pcaruana has joined #openstack-meeting-4 | 07:17 | |
*** Jeffrey4l has quit IRC | 07:18 | |
*** limao has quit IRC | 07:19 | |
*** amotoki has joined #openstack-meeting-4 | 07:21 | |
*** amotoki has quit IRC | 07:22 | |
*** amotoki has joined #openstack-meeting-4 | 07:22 | |
*** limao has joined #openstack-meeting-4 | 07:25 | |
*** mohankumar has quit IRC | 07:43 | |
*** GB21 has quit IRC | 07:45 | |
*** belmoreira has joined #openstack-meeting-4 | 07:46 | |
*** thorst_ has joined #openstack-meeting-4 | 07:50 | |
*** ad_rien_ has joined #openstack-meeting-4 | 07:55 | |
*** armax has joined #openstack-meeting-4 | 07:56 | |
*** thorst_ has quit IRC | 07:57 | |
*** armax has quit IRC | 08:00 | |
*** Julien-zte has joined #openstack-meeting-4 | 08:00 | |
*** Julien-zte has quit IRC | 08:01 | |
*** Julien-zte has joined #openstack-meeting-4 | 08:01 | |
*** ad_rien_ has quit IRC | 08:09 | |
*** dtardivel has joined #openstack-meeting-4 | 08:12 | |
*** Jeffrey4l has joined #openstack-meeting-4 | 08:17 | |
*** baoli has joined #openstack-meeting-4 | 08:18 | |
*** bobmel has joined #openstack-meeting-4 | 08:21 | |
*** matrohon has joined #openstack-meeting-4 | 08:22 | |
*** baoli has quit IRC | 08:23 | |
*** bobmel has quit IRC | 08:25 | |
*** ddellav has quit IRC | 08:28 | |
*** shaohe_feng has quit IRC | 08:29 | |
*** ddellav has joined #openstack-meeting-4 | 08:29 | |
*** shaohe_feng has joined #openstack-meeting-4 | 08:30 | |
*** alex_xu has quit IRC | 08:30 | |
*** mohankumar has joined #openstack-meeting-4 | 08:32 | |
*** betherly has joined #openstack-meeting-4 | 08:34 | |
*** myatsenko has joined #openstack-meeting-4 | 08:36 | |
*** alex_xu has joined #openstack-meeting-4 | 08:37 | |
*** rajivk has joined #openstack-meeting-4 | 08:46 | |
*** ddellav has quit IRC | 08:48 | |
*** mohankumar has quit IRC | 08:49 | |
*** ddellav has joined #openstack-meeting-4 | 08:49 | |
*** GB21 has joined #openstack-meeting-4 | 08:53 | |
*** thorst_ has joined #openstack-meeting-4 | 08:55 | |
*** jingting has left #openstack-meeting-4 | 08:56 | |
*** xiaohhui has joined #openstack-meeting-4 | 08:56 | |
*** armax has joined #openstack-meeting-4 | 08:57 | |
*** zenoway has joined #openstack-meeting-4 | 08:59 | |
*** lihi has joined #openstack-meeting-4 | 08:59 | |
*** oanson has joined #openstack-meeting-4 | 09:00 | |
oanson | #startmeeting Dragonflow | 09:00 |
---|---|---|
openstack | Meeting started Mon Nov 7 09:00:44 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 09:00 |
*** openstack changes topic to " (Meeting topic: Dragonflow)" | 09:00 | |
openstack | The meeting name has been set to 'dragonflow' | 09:00 |
oanson | Hello. Who's here for the meeting? | 09:00 |
lihi | Hi | 09:00 |
xiaohhui | hello, | 09:01 |
rajivk | Hi | 09:01 |
*** dimak has joined #openstack-meeting-4 | 09:01 | |
oanson | Let's wait another minute, maybe nick-ma and yuli will also join. | 09:01 |
dimak | Hello | 09:01 |
nick-ma_ | hi all | 09:01 |
*** armax has quit IRC | 09:02 | |
*** thorst_ has quit IRC | 09:02 | |
*** yuli_s has joined #openstack-meeting-4 | 09:02 | |
yuli_s | hello | 09:02 |
oanson | All right. We can begin | 09:02 |
oanson | #topic Ocata Roadmap | 09:02 |
*** openstack changes topic to "Ocata Roadmap (Meeting topic: Dragonflow)" | 09:02 | |
oanson | Let's start with a very quick status update. | 09:03 |
oanson | Openstack-ansible deployment is coming along nicely. You can see it here: https://review.openstack.org/#/c/391524/ | 09:03 |
oanson | Great thanks to the openstack-ansible guys who practically wrote all of it (I only stitched it together) | 09:04 |
*** yuval has joined #openstack-meeting-4 | 09:04 | |
xiaohhui | Good to know that | 09:04 |
yuval | hey | 09:04 |
oanson | About the other items I suggest to wait for next week. | 09:04 |
*** Julien-zte has quit IRC | 09:04 | |
oanson | I would be happy if anyone working on new features would upload a spec in time for next week's meeting, so that it could be discussed. | 09:05 |
oanson | According to the relase timetable, we are supposed to have specs up by the end of next week. | 09:05 |
oanson | (I hope we can make it (: ) | 09:05 |
oanson | release* | 09:05 |
dimak | I will have SFC spec up for review today | 09:05 |
oanson | Great. Thanks! | 09:05 |
*** ntr0py has joined #openstack-meeting-4 | 09:06 | |
nick-ma_ | about the release, dragonflow releases independently. do we need to release a version for N cycle? | 09:06 |
oanson | nick-ma_, I thought I have. I released version 2.0.0. | 09:07 |
nick-ma_ | oho, got it. | 09:07 |
oanson | If it didn't register as N cycle release, I'll have to go back and fix it | 09:07 |
oanson | Additionally, I plan to move us to the Openstack release cycle | 09:07 |
*** jingting has joined #openstack-meeting-4 | 09:07 | |
nick-ma_ | i see the tags, but not branch. | 09:07 |
oanson | I want to see how this and next week go, before I finalise it | 09:07 |
*** oshidoshi has joined #openstack-meeting-4 | 09:07 | |
oanson | nick-ma_, then I'll look into it | 09:08 |
oanson | #action oanson Branch out N cycle version from tag 2.0.0 | 09:08 |
oanson | Next on the roadmap talk is the a couple of blueprints: Controller HA, Services' status, and monitoring and notification | 09:08 |
nick-ma_ | it is a big change and we will have a fixed cycle. | 09:08 |
oanson | Yes | 09:08 |
nick-ma_ | if we follow the openstack. | 09:08 |
oanson | I think the project is mature enough to manage | 09:09 |
oanson | Unless there are objections | 09:09 |
oanson | In fact, if there are objections, now would be a good time to bring them up and discuss. If this may be a bad idea, I would like to know :) | 09:10 |
nick-ma_ | there is a bp about chassis status report. what about service status? health check? maybe we need to make them together to prevent from duplicate work? | 09:10 |
*** hujie has joined #openstack-meeting-4 | 09:11 | |
oanson | Yes. That's a good idea. | 09:11 |
xiaohhui | The chassis status report spec is here https://review.openstack.org/#/c/385719/ | 09:12 |
nick-ma_ | yes. | 09:12 |
oanson | #link Chassis status report spec patch https://review.openstack.org/#/c/385719 | 09:12 |
rajivk | oanson: notification and monitoring, i would like to know more. | 09:12 |
oanson | rajivk, actually I was hoping you'd share your ideas :) | 09:12 |
rajivk | okay, i just wanted to say that notification is not in the scope of dragonflow | 09:13 |
oanson | In general, Dragonflow should monitor its artifacts, e.g. service health, statistics, etc., and pass that information on (e.g. to ceilometer). | 09:13 |
rajivk | however monitoring can be used for internal scheduling etc. | 09:13 |
oanson | rajivk, yes. My understanding is that notification is handled in project aodh, | 09:13 |
oanson | which takes its info from ceilometer | 09:14 |
oanson | But I assume we have to provide ceilometer with the relevant data | 09:14 |
rajivk | okay, i think, i misunderstood by notification | 09:14 |
rajivk | i thought notification means notifying user or admin as per our earlier discussion | 09:14 |
oanson | rajivk, yes. I thought so too... | 09:14 |
nick-ma_ | notify metrics of virtual network. | 09:15 |
rajivk | notification to other components like ceilometer, congress etc should be there | 09:15 |
*** ralonsoh has joined #openstack-meeting-4 | 09:15 | |
*** ruriryan has joined #openstack-meeting-4 | 09:15 | |
rajivk | I agree on notification for openstack component | 09:15 |
oanson | Maybe we should start over :) | 09:16 |
rajivk | Help from other component team might be required, in some scenario's. | 09:16 |
rajivk | yes | 09:16 |
oanson | My understanding is the ceilometer exists to receive monitor information from components. In dragonflow's case: services' health, statistics, etc. | 09:16 |
oanson | Aodh exists to raise alarms, which could be used to take actions, or notify other components or users and admins | 09:17 |
nick-ma_ | neutron will send basic notifications in its api worker. | 09:17 |
oanson | So far, am I correct? | 09:17 |
oanson | nick-ma_, to whom? | 09:17 |
nick-ma_ | ceilometer | 09:17 |
rajivk | okay, may be we can think, about integration with congress as well. | 09:18 |
nick-ma_ | like starting to create router, create router success/failure. | 09:18 |
oanson | rajivk, sure. | 09:18 |
rajivk | May be congress allow to provide some policy for neutron | 09:19 |
rajivk | we will have to provide some mechanism to do the same in Dragonflow. | 09:19 |
oanson | Congress probably pushes policy using the Neutron API. | 09:20 |
oanson | So that should natively reach Dragonflow | 09:20 |
oanson | (Unless I am wrong) | 09:20 |
rajivk | Sorry, no idea about internal working of congress :( | 09:20 |
nick-ma_ | i have no idea about how the congress works. | 09:20 |
nick-ma_ | me too~ | 09:20 |
oanson | From a quick look at their documentation, there is a Neutron Policy Engine. But I don't know how it works internally wither | 09:21 |
oanson | rajivk, could you do the research? | 09:21 |
rajivk | I know some who can help me | 09:21 |
rajivk | from congress community | 09:21 |
oanson | That would be great! | 09:21 |
oanson | I suggest you also work with xiaohhui about the service monitor ideas you mentioned the other day. See if you can collaborate on the work he is doing on the chassis status. | 09:22 |
rajivk | ok, i will work with him. | 09:23 |
xiaohhui | :) | 09:23 |
oanson | Would you like to talk about controller HA? | 09:23 |
rajivk | yes | 09:23 |
oanson | The floor is yours! :) | 09:24 |
rajivk | Currently, if local controller goes down on a compute node than no flows will be added and removed | 09:24 |
rajivk | As per discussion with oanson, we can take two approaches to avoid this problem | 09:25 |
rajivk | 1) Add a watch dog, that keeps on monitoring local controller and if it goes down than it tries to restart it. | 09:25 |
rajivk | It try a few times(configurable), if it fails everytime then some other node's controller can be notified and from that point ownward | 09:26 |
rajivk | remote controller takes care of it's own flows as well as failed node's flows. | 09:26 |
hujie | what about deploy two df controllers, master and slave? | 09:27 |
rajivk | You mean on the same node. | 09:27 |
nick-ma_ | that doesn't make sense to deploy two same process on the same node. | 09:27 |
rajivk | hujie, usually if a service fails on one machine then there must be some external factor, which affected it from continuing | 09:28 |
rajivk | therefore slave will most probably fail | 09:28 |
oanson | This is also why the watchdog solution may not be enough | 09:28 |
nick-ma_ | in production, we use watchdog. | 09:28 |
hujie | indeed we may not consider the HA in full-distributed SDN solution, if the df goes down, the server is also down, but if you consider df goes down and the server works well you can consider deploy two role df controllers | 09:29 |
*** karthiks has joined #openstack-meeting-4 | 09:29 | |
yuval | Sorry to pop in, but if the controller is deployed using kubernetes (kolla-kubernetes?) with health check, why is there a need for a watchdog? | 09:29 |
oanson | yuval, the watchdog is there to verify the process is still running and behaving correctly. If k8s' health check does that, then that is a watchdog implementation. | 09:30 |
rajivk | yuval, you are right. In that it might not be required. | 09:31 |
oanson | But not all deployments use k8s | 09:31 |
oanson | w.g. OSA use lxc | 09:31 |
oanson | e.g.* | 09:31 |
yuval | sounds like watchdog is a deployment issue not specific to dragonflow | 09:31 |
*** markvoelker has quit IRC | 09:32 | |
rajivk | watchdog is solve the issue of a short misbehaviour of service. | 09:32 |
oanson | Possibly. We need to know what solutions exist before writing our own | 09:32 |
oanson | But the point is what to do if the process fails, and the watchdog can't bring it back up. | 09:32 |
rajivk | In that case, we can notify other node's controller to take over and do all the tasks remotely it possible.(Not sure about, whether possible or not) | 09:33 |
oanson | In theory, currently, is should be possible, since both ovsdb and the OVS ofproto interface can be connected over the net. | 09:34 |
*** zhurong_ has joined #openstack-meeting-4 | 09:34 | |
rajivk | okay, is there any major challenges to implement it? | 09:34 |
rajivk | can you see anything, that can stop us from doing it?(i am new to Dragonflow therefore does not know internal details) | 09:35 |
*** zhurong has quit IRC | 09:35 | |
xiaohhui | How would other node's controller get the vm of current node? Besides vm, I think other resources don't need to migrate | 09:35 |
oanson | I suspect the whole thing is a challenge :). But I don't see a technological problem. | 09:36 |
yuli_s | may be we will consider one df controller to implement all rules on all cns ? | 09:36 |
yuli_s | computer nodes | 09:36 |
oanson | yuli_s, that goes against the dragonflow design. We want to be fully distributed, not migrate back to a central control unit | 09:36 |
yuli_s | with a failover in this case | 09:36 |
oanson | this is only for failover, in case local solutions (e.g. watchdog) fail | 09:36 |
*** neiljerram has joined #openstack-meeting-4 | 09:36 | |
hujie | yuli_s: we are full distributed SDN solution:) | 09:37 |
oanson | xiaohhui, I think all the necessary information is stored in the OVSDB. If it is still running, the event should be received | 09:37 |
oanson | We don't even need to know about the vm. Just how to connect the southbound (OVS/OVSDB) port to the northbound (Neutron DB) port | 09:38 |
oanson | And as far as I know, that information is stored in OVSDB. | 09:38 |
yuli_s | i remember seeing a patch to update the chases table periodically. it can be used for this | 09:38 |
yuli_s | (to detect failed controller) | 09:39 |
hujie | if other df to manage remote ovs, it is in-band flow, the OM and data plane is shared, | 09:39 |
oanson | We can also try adding a plug-vif driver to nova, which would help when we want to extend beyond vms and beyond ovs. But I don't think we'll make it for Ocata. | 09:39 |
nick-ma_ | when the remote controller takes over the work, it also needs to update its local cache for all the remote topology | 09:39 |
oanson | And tell apart items that belong to the local compute node, and to the HAed compute node | 09:40 |
rajivk | nick-ma_: can you elaborate | 09:40 |
nick-ma_ | rajivk: i can help discuss and review. :-) | 09:42 |
rajivk | I think, it is good feature. | 09:42 |
hujie | if df could manage remote ovs, it seems dragonflow is a high distributed ODL\floodlight\onos\ryu..., not full distributed | 09:42 |
*** admcleod_ has joined #openstack-meeting-4 | 09:42 | |
rajivk | nick-ma_: i would a lot of help and discussion. Thanks. | 09:43 |
xiaohhui | I agree with hujie | 09:43 |
oanson | rajivk, the local DF controller holds an in-memory cache of the database objects. We try to have it as small as possible. In case of HA, we need to read the information of the other compute node into the cache | 09:43 |
oanson | hujie, xiaohhui, this feature is for fallback only. There should be a dragonflow local controller on every node. | 09:43 |
*** admcleod has quit IRC | 09:43 | |
rajivk | what about supporting distributed cache as well like memcache? | 09:43 |
nick-ma_ | yes, HA is an exception for centralization. we can run HA for all the compute nodes, but that doesn't make sense to deploy in production. | 09:43 |
oanson | But it is possible it will crash, and it might be possible that the watchdog won't be able to raise it again. | 09:43 |
*** betherly has quit IRC | 09:44 | |
nick-ma_ | we do have a distributed data store. | 09:44 |
oanson | The local cache is just to speed up reads from that data store. | 09:44 |
nick-ma_ | if we need distributed cache, we just remove the local cache layer. that's all. | 09:44 |
nick-ma_ | every read will go to db layer. | 09:45 |
rajivk | hmm, i got it. | 09:45 |
oanson | rajivk, additionally, the data store layer is fully pluggable. If we want to use specifically memcache, a driver can be written | 09:46 |
rajivk | i just said it for caching remote machine's info. | 09:46 |
rajivk | But i think, i did not understand that much about Dragonflow. May be i will discuss about it later on. | 09:47 |
oanson | No worries. I was just showing off our pluggability :) | 09:47 |
oanson | rajivk, sure. | 09:47 |
oanson | I am always available (if not in IRC, then by mail) | 09:47 |
rajivk | oanson, okay thanks. | 09:48 |
oanson | I would ask that you let me know what you want to implement, and that you upload a spec so that we'll have it organised. | 09:48 |
oanson | But that can be done later | 09:48 |
rajivk | okay, i will discuss and let you know on IRC. | 09:49 |
oanson | Great. Thanks! | 09:49 |
oanson | Anything else for roadmap? | 09:49 |
rajivk | I have created a bp | 09:50 |
rajivk | it is not a feature but now other components are also centerlizing configurations | 09:50 |
rajivk | that's it from my side. | 09:50 |
yuli_s | oanson, u wnat to talk about ml2 and dumping plugin ? | 09:51 |
yuli_s | oanson, you want to talk about ml2 and dumping plugin.py ? | 09:51 |
*** tovin07 has quit IRC | 09:51 | |
oanson | rajivk, I brushed over the spec. Seems like a good idea. I think nick-ma_ started working on something like. | 09:51 |
oanson | Using oslo config generation | 09:52 |
oanson | yuli_s, not sure what you mean. Could you please explain? | 09:52 |
nick-ma_ | yes, that was done. centralized configuration is also welcomed. please share the spec link here. i can catch up. | 09:53 |
oanson | rajivk, done in this patch: https://review.openstack.org/#/c/373796/ | 09:53 |
yuli_s | for the Ocata release do we want to swithc completely to ml2 and dump old plugin support | 09:53 |
oanson | #link Centralised configuration blueprint https://blueprints.launchpad.net/dragonflow/+spec/centralize-config-options | 09:53 |
yuli_s | ? | 09:53 |
oanson | yuli_s, yes. | 09:53 |
*** tovin07_ has quit IRC | 09:53 | |
oanson | It is not urgent, but it should be done within the 4-6 weeks. | 09:53 |
yuli_s | ok,\ | 09:54 |
oanson | I can do that, seeing as it's just deleting a couple of files | 09:54 |
xiaohhui | I have this work https://bugs.launchpad.net/dragonflow/+bug/1618792 which might similar to dumping plugin.py | 09:54 |
openstack | Launchpad bug 1618792 in DragonFlow "RFE: Use ml2 as default option for devstack" [Wishlist,In progress] - Assigned to Hong Hui Xiao (xiaohhui) | 09:54 |
*** bogdando has quit IRC | 09:54 | |
oanson | xiaohhui, this is an important step in the way. Yes. | 09:55 |
*** sdake has joined #openstack-meeting-4 | 09:55 | |
oanson | But it looks like it's merged :) | 09:55 |
xiaohhui | I plan to add more code for it, | 09:55 |
xiaohhui | currently it is just update the sample local.conf files | 09:56 |
oanson | You want dragonflow's plugin.sh to set the variables by default? | 09:56 |
xiaohhui | yes, | 09:56 |
oanson | xiaohhui, sounds good! | 09:56 |
yuli_s | good idea | 09:56 |
oanson | I also want to discuss https://bugs.launchpad.net/dragonflow/+bug/1638151 . jingting: I added a comment to the bug, could you please reply? | 09:56 |
openstack | Launchpad bug 1638151 in DragonFlow "Router schedule error in L3 router plugin as there are multi-external network" [High,New] - Assigned to rajiv (rajiv-kumar) | 09:56 |
oanson | It is the only high priority bug that isn't marked 'in progress'. | 09:57 |
rajivk | I went through the details for this bug. | 09:57 |
*** armax has joined #openstack-meeting-4 | 09:57 | |
rajivk | I it seems like, during update of the router at neutron side it fails. | 09:58 |
xiaohhui | This is actually the issue that dragonflow don't support multi-external network now. | 09:58 |
nick-ma_ | it uses router scheduler but it failed to do it in dragonflow. | 09:58 |
xiaohhui | If br-ex is configured in neutron, the same exception will report | 09:58 |
oanson | We are running out of time. | 09:59 |
oanson | If you all could share your information on the bug, we could take it from there | 09:59 |
rajivk | let's discuss it on IRC channel of Dragonflow | 09:59 |
oanson | #link https://bugs.launchpad.net/dragonflow/+bug/1638151 | 09:59 |
openstack | Launchpad bug 1638151 in DragonFlow "Router schedule error in L3 router plugin as there are multi-external network" [High,New] - Assigned to rajiv (rajiv-kumar) | 09:59 |
oanson | rajivk, Sure. | 09:59 |
xiaohhui | I want to bring this review out https://review.openstack.org/#/c/339975/ | 10:00 |
*** sdake_ has joined #openstack-meeting-4 | 10:00 | |
oanson | Thanks everyone for coming. We can continue in #openstack-dragonflow . | 10:00 |
*** thorst_ has joined #openstack-meeting-4 | 10:00 | |
xiaohhui | It is legacy from N release | 10:00 |
xiaohhui | OK | 10:00 |
oanson | xiaohhui, one we have a Newton branch (I'll take care of is ASAP), we can back port important patches | 10:01 |
oanson | I suggest we'll discuss it once the patch is merged into master | 10:01 |
oanson | Thanks again | 10:01 |
oanson | #endmeeting | 10:01 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 10:01 | |
openstack | Meeting ended Mon Nov 7 10:01:36 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 10:01 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-11-07-09.00.html | 10:01 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-11-07-09.00.txt | 10:01 |
openstack | Log: http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-11-07-09.00.log.html | 10:01 |
*** qwebirc53104 has joined #openstack-meeting-4 | 10:01 | |
*** qwebirc53104 has quit IRC | 10:02 | |
*** armax has quit IRC | 10:02 | |
*** sdake has quit IRC | 10:03 | |
*** bauwser is now known as bauzas | 10:03 | |
*** asettle has joined #openstack-meeting-4 | 10:05 | |
*** zhurong_ has quit IRC | 10:05 | |
*** thorst_ has quit IRC | 10:07 | |
*** yuval has left #openstack-meeting-4 | 10:10 | |
*** asettle has quit IRC | 10:11 | |
*** asettle has joined #openstack-meeting-4 | 10:11 | |
*** yamahata has quit IRC | 10:11 | |
*** sambetts|afk is now known as sambetts | 10:12 | |
*** gongysh has quit IRC | 10:13 | |
*** sdake_ is now known as sdake | 10:25 | |
*** limao has quit IRC | 10:38 | |
*** hujie has left #openstack-meeting-4 | 10:39 | |
*** irenab has quit IRC | 10:43 | |
*** eyalb has quit IRC | 10:44 | |
*** bobmel has joined #openstack-meeting-4 | 10:48 | |
*** bobmel has quit IRC | 10:53 | |
*** eyalb has joined #openstack-meeting-4 | 10:59 | |
*** thorst_ has joined #openstack-meeting-4 | 11:05 | |
*** ad_rien_ has joined #openstack-meeting-4 | 11:12 | |
*** thorst_ has quit IRC | 11:12 | |
*** ad_rien_ has quit IRC | 11:13 | |
*** ad_rien_ has joined #openstack-meeting-4 | 11:13 | |
*** ad_rien_1 has joined #openstack-meeting-4 | 11:18 | |
*** ad_rien_ has quit IRC | 11:18 | |
*** _degorenko|afk is now known as degorenko | 11:20 | |
*** markvoelker has joined #openstack-meeting-4 | 11:32 | |
*** caowei has joined #openstack-meeting-4 | 11:33 | |
*** irenab has joined #openstack-meeting-4 | 11:36 | |
*** markvoelker has quit IRC | 11:38 | |
*** eyalb has quit IRC | 11:47 | |
*** dimak has quit IRC | 11:53 | |
*** mohankumar has joined #openstack-meeting-4 | 11:54 | |
*** rtheis has joined #openstack-meeting-4 | 12:09 | |
*** thorst_ has joined #openstack-meeting-4 | 12:10 | |
*** qwebirc34710 has joined #openstack-meeting-4 | 12:13 | |
*** thorst_ has quit IRC | 12:17 | |
*** qwebirc34710 has quit IRC | 12:19 | |
*** zhurong has joined #openstack-meeting-4 | 12:25 | |
*** ad_rien_1 has quit IRC | 12:27 | |
*** ad_rien_ has joined #openstack-meeting-4 | 12:28 | |
*** janonymous has joined #openstack-meeting-4 | 12:31 | |
*** yfauser has joined #openstack-meeting-4 | 12:40 | |
*** sdake has quit IRC | 12:40 | |
*** sdake has joined #openstack-meeting-4 | 12:40 | |
*** tinwood has quit IRC | 12:41 | |
*** berendt has quit IRC | 12:41 | |
*** tinwood has joined #openstack-meeting-4 | 12:44 | |
*** GB21 has quit IRC | 12:46 | |
*** leo_wang has quit IRC | 12:46 | |
*** Kevin_Zheng has quit IRC | 12:47 | |
*** leo_wang has joined #openstack-meeting-4 | 12:48 | |
*** Kevin_Zheng has joined #openstack-meeting-4 | 12:48 | |
*** yuli_s has quit IRC | 12:48 | |
*** limao has joined #openstack-meeting-4 | 12:49 | |
*** thorst_ has joined #openstack-meeting-4 | 12:50 | |
*** thorst_ has quit IRC | 12:50 | |
*** thorst_ has joined #openstack-meeting-4 | 12:52 | |
*** limao has quit IRC | 12:53 | |
*** kylek3h has quit IRC | 12:57 | |
*** bobh has joined #openstack-meeting-4 | 12:59 | |
*** bobh has quit IRC | 12:59 | |
*** bobh has joined #openstack-meeting-4 | 13:00 | |
*** woodard has joined #openstack-meeting-4 | 13:02 | |
*** janki has quit IRC | 13:02 | |
*** limao has joined #openstack-meeting-4 | 13:15 | |
*** limao_ has joined #openstack-meeting-4 | 13:16 | |
*** limao has quit IRC | 13:19 | |
*** markvoelker has joined #openstack-meeting-4 | 13:21 | |
*** dave-mccowan has joined #openstack-meeting-4 | 13:23 | |
*** ddellav has quit IRC | 13:26 | |
*** bobh has quit IRC | 13:26 | |
*** ddellav has joined #openstack-meeting-4 | 13:27 | |
*** kylek3h has joined #openstack-meeting-4 | 13:30 | |
*** kylek3h has quit IRC | 13:30 | |
*** kylek3h has joined #openstack-meeting-4 | 13:30 | |
*** mchiappero has joined #openstack-meeting-4 | 13:31 | |
*** bobh has joined #openstack-meeting-4 | 13:32 | |
*** links has quit IRC | 13:40 | |
*** reedip_ has joined #openstack-meeting-4 | 13:42 | |
*** vikasc has joined #openstack-meeting-4 | 13:44 | |
*** bobh has quit IRC | 13:45 | |
*** julim_ has quit IRC | 13:47 | |
*** sdake has quit IRC | 13:48 | |
*** mohankumar has quit IRC | 13:51 | |
*** yedongcan has joined #openstack-meeting-4 | 13:55 | |
*** uck has joined #openstack-meeting-4 | 13:55 | |
*** sshnaidm is now known as sshnaidm|afk | 13:57 | |
*** amotoki has quit IRC | 13:58 | |
*** ivc_ has joined #openstack-meeting-4 | 13:58 | |
*** lmdaly has joined #openstack-meeting-4 | 13:59 | |
*** apuimedo has joined #openstack-meeting-4 | 13:59 | |
*** Julien-zte has joined #openstack-meeting-4 | 14:00 | |
*** pc_m has joined #openstack-meeting-4 | 14:01 | |
*** klamath has joined #openstack-meeting-4 | 14:01 | |
*** klamath has quit IRC | 14:01 | |
*** garyloug has joined #openstack-meeting-4 | 14:01 | |
*** caowei has quit IRC | 14:01 | |
*** klamath has joined #openstack-meeting-4 | 14:01 | |
apuimedo | #startmeeting kuryr | 14:02 |
openstack | Meeting started Mon Nov 7 14:02:11 2016 UTC and is due to finish in 60 minutes. The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:02 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:02 |
*** openstack changes topic to " (Meeting topic: kuryr)" | 14:02 | |
openstack | The meeting name has been set to 'kuryr' | 14:02 |
*** lserpietri has joined #openstack-meeting-4 | 14:02 | |
apuimedo | Hello everybody and welcome to another Kuryr weekly IRC meeting | 14:02 |
apuimedo | who's here to chat? | 14:02 |
vikasc | o/ | 14:02 |
garyloug | o/ | 14:02 |
lmdaly | o/ | 14:02 |
limao_ | o/ | 14:02 |
yedongcan | o/ | 14:02 |
ivc_ | o/ | 14:02 |
*** Drago1 has joined #openstack-meeting-4 | 14:03 | |
* pc_m lurking | 14:03 | |
Drago1 | o/ | 14:03 |
*** Drago1 is now known as Drago | 14:03 | |
*** caowei has joined #openstack-meeting-4 | 14:03 | |
apuimedo | Welcome everybody! | 14:03 |
ltomasbo | o/ | 14:03 |
*** baoli has joined #openstack-meeting-4 | 14:03 | |
apuimedo | #topic kuryr-lib | 14:03 |
*** openstack changes topic to "kuryr-lib (Meeting topic: kuryr)" | 14:03 | |
apuimedo | Today I'll be pushing the new version of the kuryr-lib CNI driver | 14:04 |
apuimedo | missing still the OVO binding :/ | 14:04 |
mchiappero | o/ | 14:05 |
apuimedo | anything else on kuryr-lib? | 14:05 |
apuimedo | #topic kuryr-libnetwork | 14:06 |
*** tonytan4ever has joined #openstack-meeting-4 | 14:06 | |
*** openstack changes topic to "kuryr-libnetwork (Meeting topic: kuryr)" | 14:06 | |
*** oanson has quit IRC | 14:06 | |
apuimedo | #info mchiappero and lmdaly reported a bug in how we handle the creation and deletion of interfaces in libnetwork that impacts us specially when working in container-in-vm mode | 14:07 |
irenab | sorry for joining late | 14:07 |
*** cleong has joined #openstack-meeting-4 | 14:07 | |
*** zhurong has quit IRC | 14:07 | |
apuimedo | The issue is about when we delete and create the virtual devices for the container | 14:07 |
apuimedo | they report that libnetwork expects deletion on deleteendpoint, whereas we were doing it in 'leave' | 14:08 |
irenab | apuimedo, link? | 14:08 |
apuimedo | sure | 14:08 |
mchiappero | maybe bug is a misleading term | 14:08 |
*** amotoki has joined #openstack-meeting-4 | 14:09 | |
mchiappero | if you have good contacts with any folk in docker let's check with them | 14:09 |
apuimedo | darn, can't find the link now | 14:09 |
apuimedo | mchiappero: banix does, but he didn't join today | 14:09 |
mchiappero | https://github.com/docker/libnetwork/issues/1520 | 14:09 |
limao_ | https://bugs.launchpad.net/neutron/+bug/1639186 | 14:09 |
openstack | Launchpad bug 1639186 in neutron "qos max bandwidth rules not working for neutron trunk ports" [Low,Confirmed] - Assigned to Luis Tomas Bolivar (ltomasbo) | 14:09 |
apuimedo | limao_: that's a different one :P | 14:09 |
apuimedo | plenty of bugs to go around | 14:10 |
apuimedo | :P | 14:10 |
apuimedo | we | 14:10 |
limao_ | yeah.. | 14:10 |
apuimedo | we'll get to it | 14:10 |
limao_ | just find.. | 14:10 |
apuimedo | anyway. I'll find it later | 14:10 |
mchiappero | I tried once again to ping someone in #docker-network | 14:10 |
*** beekneemech is now known as bnemec | 14:10 | |
mchiappero | without success | 14:10 |
mchiappero | tried pinging mrjana | 14:10 |
mchiappero | nothing | 14:10 |
apuimedo | the fact of the matter is that libnetwork attempts to move the device after the 'leave'. Which is good because we are supposed to delete the ipvlan/macvlan devices | 14:10 |
apuimedo | and for that they have to be in the host namespace (so we find them) | 14:11 |
apuimedo | with veths we do not have the problem | 14:11 |
apuimedo | due to the fact that if we delete teh host side veth | 14:11 |
apuimedo | the other one gets removed as well | 14:11 |
apuimedo | so we got a pass with doing things earlier | 14:11 |
janonymous | o/ | 14:11 |
janonymous | sorry got late | 14:12 |
apuimedo | I believe that mchiappero and lmdaly have a patch in the works for solving this | 14:12 |
apuimedo | janonymous: no worries | 14:12 |
apuimedo | so I wait eagerly to get it in ;-) | 14:12 |
mchiappero | we'll be pushing shortly | 14:13 |
apuimedo | #action mchiappero lmdaly to push the libnetwork fix for container device deletion ordering | 14:13 |
mchiappero | the missing piece is the doc change | 14:13 |
apuimedo | mchiappero: you can definitely put that on a follow up patch | 14:13 |
apuimedo | now, on to the bug limao mentioned | 14:13 |
*** amotoki has quit IRC | 14:13 | |
apuimedo | #link https://bugs.launchpad.net/neutron/+bug/1639186 | 14:13 |
openstack | Launchpad bug 1639186 in neutron "qos max bandwidth rules not working for neutron trunk ports" [Low,Confirmed] - Assigned to Luis Tomas Bolivar (ltomasbo) | 14:13 |
*** bobmel has joined #openstack-meeting-4 | 14:14 | |
apuimedo | #info ltomasbo has been checking the vlan-aware-vms neutron reference implementation for completeness | 14:14 |
apuimedo | #info ltomasbo has found out that Neutron QoS does not get applied to the container subports | 14:14 |
*** syed_ has joined #openstack-meeting-4 | 14:14 | |
ltomasbo | yep, and find out that QoS cannot be applied on trunk ports | 14:14 |
ltomasbo | neither parent not subports | 14:14 |
irenab | DSCP marking as well? | 14:15 |
apuimedo | ltomasbo: I'd rather say 'cannot be applied on trunk ports with the current plumbing' | 14:15 |
apuimedo | :P | 14:15 |
ltomasbo | didn't try, but perhaps that will work | 14:15 |
apuimedo | irenab: that will only affect real hw, won't it? | 14:15 |
irenab | I just think saying QoS cannot be applied to trunk ports is too generic | 14:16 |
apuimedo | (and possibly customized tc rules at the host's egress, of coure) | 14:16 |
apuimedo | irenab: I agree with that sentiment | 14:16 |
apuimedo | :-) | 14:16 |
apuimedo | ltomasbo is looking at other ways to enable it | 14:16 |
irenab | apuimedo, seems its in neutron domain to fix, right? | 14:16 |
apuimedo | so subports and parent ports get the same level of QoS | 14:16 |
apuimedo | irenab: it is | 14:16 |
apuimedo | ltomasbo works on both sides ;-) | 14:16 |
ltomasbo | yep, it is in vlan-aware-vm part | 14:17 |
irenab | great, thanks | 14:17 |
apuimedo | ltomasbo: maybe you can explain a bit the two ways that you are looking at (container per vlan and networking per vlan) | 14:17 |
ltomasbo | apuimedo: actually it is not that they get the same QoS | 14:17 |
apuimedo | s/networking/network/ | 14:17 |
ltomasbo | is that it is not enforce at all | 14:17 |
ltomasbo | due to the way the VMs are connected to the br-int when in vlan-aware-vm mode | 14:18 |
apuimedo | ltomasbo: I meant that they should get the get QoS applied as if they were unrelated ports | 14:18 |
irenab | apuimedo, can you please give a quick update on the nested case progress? | 14:18 |
apuimedo | s/get QoS/QoS/ | 14:18 |
*** tonytan4ever has quit IRC | 14:19 | |
ltomasbo | and yes, I can explain what I've been trying for the containers in vlan-aware-vms | 14:19 |
apuimedo | irenab: that is what we are doing. ltomasbo will now explain a bit about his experiments | 14:19 |
apuimedo | for kuryr-libnetwork we covered the bug in interface deletion earlier | 14:19 |
*** tonytan4ever has joined #openstack-meeting-4 | 14:19 | |
ltomasbo | yep, I've been trying two different ways of providing vlan networks to nested containers | 14:19 |
apuimedo | when serving the container-in-vm case | 14:19 |
ltomasbo | the first scenario is when we have one subport (one vlan) per container | 14:20 |
ltomasbo | independently of if they are on the same neutron network or not | 14:20 |
irenab | ltomasbo, vlan maps to the network of type vlan? | 14:20 |
irenab | or just vlan for Container separation on host? | 14:21 |
apuimedo | this means that connectivity between containers on the same machine always goes down to br-int on the host. So security groups are applied, QoS may get applied there as well once it is fixed, but you can only have 4096 container on the host | 14:21 |
ltomasbo | it is vlan just up to the trunk port | 14:21 |
ltomasbo | trunk bridge, sorry | 14:21 |
apuimedo | well, less than that, but in the ballpark | 14:22 |
apuimedo | :P | 14:22 |
ltomasbo | and then it will be encapsulated as the neutron network (vlan, vxlan, ...) | 14:22 |
apuimedo | irenab: vlan to separate inside the VM | 14:22 |
irenab | ltomasbo, got it, thanks | 14:22 |
ltomasbo | the other way is also using ipvlan | 14:22 |
ltomasbo | and have one subport per network | 14:22 |
apuimedo | irenab: in the previous way, you basically have the VM eth0 and kuryr createds eth.X vlan devices and moves them into the containers | 14:23 |
*** bobh has joined #openstack-meeting-4 | 14:23 | |
ltomasbo | and then, inside the VM, all the container belonging to the same network, will get connected through the same subport | 14:23 |
ltomasbo | but they need to create a port and include it into the allowed address pair, as in the current ipvlan implementation | 14:24 |
apuimedo | so there's two calls to do to neutron. Create a port and make it a subport of the VM trunk port | 14:24 |
apuimedo | (in the previous way) | 14:24 |
*** Drago has quit IRC | 14:24 | |
ltomasbo | apuimedo: yes | 14:25 |
irenab | apuimedo, so the kuryr part that does it is already wip? | 14:25 |
ltomasbo | and in the second case, there is one to get the port and one to include it into the allowed pairs of the subport | 14:25 |
apuimedo | in this other way (one vlan per network used for containers in the VM), there's also two calls. One to create the port to reserve the IP in the subnet, the other to update the port that is actually a subport of the VM so that it has the new IP as an allowed one | 14:25 |
apuimedo | right | 14:25 |
vikasc | https://review.openstack.org/#/c/361993/ | 14:25 |
apuimedo | vikasc: :-) | 14:26 |
vikasc | apuimedo, irenab i started this part :) | 14:26 |
irenab | vikasc, cool! | 14:26 |
apuimedo | vikasc: we'd need to make it configurable for the two modes | 14:26 |
vikasc | apuimedo, yeah makes sense, for ipval as well | 14:26 |
vikasc | *ipvlan | 14:27 |
irenab | so back to the QoS problem | 14:27 |
apuimedo | :-) | 14:27 |
irenab | what is the use case, any libnetwork API or more looking forward case? | 14:27 |
apuimedo | #action vikasc to work with ltomasbo to put the vlan management in sync with the two ways ltomasbo is experimenting with | 14:27 |
apuimedo | irenab: well, it's mostly for when k8s adds QoS support | 14:28 |
apuimedo | so we can map it to Neutron | 14:28 |
irenab | apuimedo, is it planned for 1.6? | 14:28 |
apuimedo | as part of the work to check that vlan aware VMs are 'ready' â„¢ | 14:28 |
apuimedo | haven't checked | 14:28 |
irenab | I see, so more checking if it works as expected | 14:29 |
apuimedo | so it is more of a priority for Neutron to get this fixed than for us :P | 14:29 |
vikasc | apuimedo, was wondering what pros vlan has ipvlan, cons is lower limit of 4096? | 14:29 |
apuimedo | we have time | 14:29 |
*** makowals has quit IRC | 14:29 | |
irenab | there is also proposal for CoS support (vlan prio) | 14:29 |
apuimedo | vikasc: the pros of using vlan per container are that you are getting full neutron networking to the containers, including SG | 14:30 |
apuimedo | for Container network per vlan | 14:30 |
vikasc | apuimedo, ahh , got it. thanks | 14:30 |
apuimedo | the advantage is that you are not limited to <4095 containers on the VM | 14:30 |
vikasc | apuimedo, scalibility vs control | 14:31 |
apuimedo | the disadvantage is that if you wanted to have different security/policy applied to containers of the same container network | 14:31 |
apuimedo | you would not be able to let Neutron on the host handle it | 14:31 |
apuimedo | vikasc: that's a way to put it | 14:31 |
apuimedo | ;-) | 14:31 |
vikasc | apuimedo, makes sense | 14:31 |
*** sshnaidm|afk is now known as sshnaidm | 14:32 | |
apuimedo | #info limao has been working on revamping the rally tests, to test the cost we incur on container creation going to neutron | 14:32 |
apuimedo | it will probably get merged this week | 14:32 |
*** makowals has joined #openstack-meeting-4 | 14:32 | |
apuimedo | so we'll have better data to take into account when deciding default networking modes | 14:33 |
apuimedo | (and we can track perf regressions hopefully) | 14:33 |
irenab | apuimedo, short question regarding k8s implementation | 14:35 |
apuimedo | irenab: let's move over to the topic then | 14:35 |
apuimedo | :-) | 14:35 |
apuimedo | #topic kuryr-kubernetes | 14:35 |
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)" | 14:35 | |
apuimedo | irenab: go ahead! | 14:35 |
apuimedo | :-) | 14:35 |
irenab | is there any list of working items, trello board to track the work you , vikasc and ivc_ currently doing? | 14:36 |
* apuimedo is ashamed | 14:36 | |
apuimedo | I have the trello board | 14:36 |
apuimedo | but I have not updated it since the week before the summit | 14:37 |
apuimedo | I'll put it up to date again today | 14:37 |
apuimedo | let me put the link | 14:37 |
* vikasc was a bit idle for some time and will be catching up on reviewing ivc_ patches | 14:37 | |
irenab | thanks a lot! it will be very helpful for reviews | 14:37 |
ivc_ | too late vikasc, toni already merged those :P | 14:37 |
vikasc | ivc_, :D | 14:38 |
ivc_ | but i've got 2-3 more on the way, just need the cni driver in kuryr-lib | 14:38 |
vikasc | ivc_, will try out merged code then | 14:38 |
apuimedo | #link https://trello.com/b/1Ij919E8/networking | 14:39 |
apuimedo | if anybody is missing access, let me know and I'll add you | 14:39 |
apuimedo | ivc_: you need to rebase the handler patch | 14:39 |
apuimedo | https://review.openstack.org/#/c/391329/ | 14:40 |
ivc_ | apuimedo, you mean namespace? | 14:40 |
apuimedo | yup | 14:40 |
ivc_ | oh we wont need it for some time now | 14:40 |
apuimedo | but IIRC it also needs other changes | 14:40 |
ivc_ | it will just lurk there with 'wip' status | 14:40 |
apuimedo | since you changed the approach of having watcher per namespace resource to the one of the prototype (one watcher per resource, and let the handlers care, if necessary, abou the namespaces) | 14:41 |
*** yfauser has quit IRC | 14:41 | |
apuimedo | ivc_: got it | 14:41 |
apuimedo | anybody can feel free to take items from that board | 14:41 |
ivc_ | yup. it will get used once we get to sec-groups/network per namespace | 14:42 |
apuimedo | but if there's already somebody on it, do talk to each other | 14:42 |
apuimedo | ivc_: right | 14:42 |
*** makowals has quit IRC | 14:42 | |
apuimedo | irenab: did you have some other question on the k8s front? | 14:42 |
apuimedo | the summary is, ivc_ is waiting for my kuryr-lib CNI patch | 14:42 |
apuimedo | and in the meantime we can prepare the WIP of the other handlers | 14:43 |
irenab | I just wanted to see the plan, since had silly questions on the patch ivc_ posted last week :-) | 14:43 |
apuimedo | and prototype the cluster membership, since it is quite orthogonal | 14:43 |
irenab | I will check the board | 14:43 |
*** banix has joined #openstack-meeting-4 | 14:43 | |
apuimedo | there's rarely silly questions | 14:43 |
*** jlvill-travel is now known as jlvillal | 14:43 | |
apuimedo | except whether salmiak is better than chocolate. That would be silly | 14:44 |
irenab | :-) | 14:44 |
vikasc | there is a saying.. questions are never silly, answers can be :) | 14:44 |
apuimedo | :-) | 14:44 |
ivc_ | apuimedo, what other handlers do we expect besides podport and service? | 14:44 |
irenab | endpoints? | 14:44 |
apuimedo | ivc_: I was implicitly referring to the service one (which we read from endpoints) | 14:45 |
ivc_ | irenab, thats service | 14:45 |
irenab | network policy | 14:45 |
apuimedo | I think it can be put as WIP more or less like the namespaces one is | 14:45 |
apuimedo | irenab: also | 14:45 |
ivc_ | network policy we'll probably need to handle in podport mostly | 14:45 |
apuimedo | I'd suggest that whoever wants to do that, take a look at how the ovn k8s implementation did it, so that we can have some reference | 14:46 |
ivc_ | https://review.openstack.org/#/c/376045/ | 14:46 |
ivc_ | ^ service/endpoints | 14:46 |
apuimedo | ivc_: we will need to watch the policy objects | 14:46 |
*** Drago has joined #openstack-meeting-4 | 14:46 | |
irenab | apuimedo, do you have a reference to ovn? | 14:46 |
apuimedo | sure | 14:46 |
ivc_ | apuimedo, yes, but my point is that we prolly cant start on policies before we finish port bindings | 14:47 |
apuimedo | irenab: https://github.com/openvswitch/ovn-kubernetes | 14:47 |
irenab | ivc_, agree | 14:47 |
irenab | apuimedo, thanks | 14:47 |
*** hongbin has joined #openstack-meeting-4 | 14:47 | |
*** yfauser has joined #openstack-meeting-4 | 14:47 | |
apuimedo | ivc_: it can't be tested. But one can start checking how others mapped it | 14:47 |
apuimedo | and start prototyping | 14:47 |
apuimedo | or at least breaking down things to do in the trello board | 14:48 |
irenab | sorry, have to leave. Will catch up on meeting log | 14:48 |
apuimedo | irenab: do you think you could take up the checking part? | 14:48 |
apuimedo | ok irenab | 14:48 |
apuimedo | thanks for joining | 14:48 |
irenab | apuimedo, will check if I have cycles to spend on it | 14:48 |
apuimedo | ivc_: thanks for the link to the services patch, it escaped my eye | 14:48 |
apuimedo | thanks irenab | 14:48 |
apuimedo | any other topic on k8s? | 14:49 |
apuimedo | ivc_: | 14:49 |
*** reedip_ has quit IRC | 14:49 | |
ivc_ | got some ideas about net.policies and labels, that we can have a sec.group per label | 14:49 |
ivc_ | i.e. multiple labels -> multiple sec.groups | 14:50 |
ivc_ | but need to experiment with that | 14:50 |
apuimedo | same here | 14:50 |
apuimedo | I have some ideas, but need to check if it will work out with the selectors | 14:51 |
apuimedo | #topic open discussion | 14:52 |
*** openstack changes topic to "open discussion (Meeting topic: kuryr)" | 14:52 | |
apuimedo | anybody else has other topics? | 14:52 |
*** julim has joined #openstack-meeting-4 | 14:52 | |
apuimedo | #action apuimedo to update the trello board | 14:53 |
apuimedo | alrigth then. Thank you all for joining! | 14:54 |
apuimedo | #endmeeting | 14:54 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 14:54 | |
openstack | Meeting ended Mon Nov 7 14:54:05 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:54 |
mchiappero | thank you | 14:54 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-11-07-14.02.html | 14:54 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-11-07-14.02.txt | 14:54 |
openstack | Log: http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-11-07-14.02.log.html | 14:54 |
vikasc | bbye | 14:54 |
*** Drago has left #openstack-meeting-4 | 14:54 | |
ltomasbo | bye | 14:54 |
mchiappero | bye | 14:54 |
*** pc_m has left #openstack-meeting-4 | 14:54 | |
*** yedongcan has left #openstack-meeting-4 | 14:57 | |
*** makowals has joined #openstack-meeting-4 | 14:58 | |
*** caowei has quit IRC | 14:59 | |
*** lmdaly has left #openstack-meeting-4 | 14:59 | |
sigmavirus | #startmeeting craton | 15:00 |
openstack | Meeting started Mon Nov 7 15:00:07 2016 UTC and is due to finish in 60 minutes. The chair is sigmavirus. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
*** openstack changes topic to " (Meeting topic: craton)" | 15:00 | |
openstack | The meeting name has been set to 'craton' | 15:00 |
sulo | o/ | 15:00 |
sigmavirus | #help | 15:00 |
sigmavirus | #topic roll call | 15:01 |
*** openstack changes topic to "roll call (Meeting topic: craton)" | 15:01 | |
sigmavirus | #link https://etherpad.openstack.org/p/craton-meetings | 15:01 |
sulo | o/ again | 15:01 |
sigmavirus | ^ Today's agenda | 15:01 |
sigmavirus | (although there's nothing there for today) | 15:01 |
*** shananigans has joined #openstack-meeting-4 | 15:01 | |
sigmavirus | #chair sulo | 15:01 |
openstack | Current chairs: sigmavirus sulo | 15:01 |
*** reedip_ has joined #openstack-meeting-4 | 15:01 | |
* sigmavirus couldn't remember the octothorpe command | 15:01 | |
sigmavirus | #chair jimbaker | 15:01 |
openstack | Current chairs: jimbaker sigmavirus sulo | 15:01 |
*** jerms has quit IRC | 15:02 | |
sigmavirus | #link http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-10-31-15.00.txt | 15:02 |
sigmavirus | Last week's summary | 15:02 |
sigmavirus | Since jimbaker still seems to be on PTO, let's just run down the action items from last week | 15:02 |
sulo | right i dont have the writeup yet | 15:02 |
sigmavirus | #topic Review action items | 15:02 |
*** openstack changes topic to "Review action items (Meeting topic: craton)" | 15:02 | |
sigmavirus | #info We'll carry forward the action item for jimbaker and sulo to do a summary/write-up for the summit meetings | 15:03 |
*** uck has quit IRC | 15:03 | |
sulo | cool sounds good | 15:03 |
sigmavirus | #action jimbaker to send summary to openstack-dev with [craton] tag from what happened in Barcelona | 15:03 |
sigmavirus | #action sulo to send summary to openstack-dev with [craton] tag from what happened in Barcelona | 15:03 |
sigmavirus | (It only assigned the action item to jim last week so, adding two distinct ones) | 15:03 |
sulo | ok | 15:03 |
sigmavirus | #topic updates | 15:04 |
*** openstack changes topic to "updates (Meeting topic: craton)" | 15:04 | |
sigmavirus | Any updates on your end sulo? | 15:04 |
*** chrisspencer has joined #openstack-meeting-4 | 15:04 | |
sulo | so looks like participation is thin today .. | 15:04 |
sulo | yes | 15:04 |
chrisspencer | o/ | 15:04 |
sulo | hi chrisspencer | 15:04 |
sigmavirus | And now we're 3 :) | 15:04 |
sulo | so i am working on few work items, namely search by variables | 15:04 |
chrisspencer | who decided it was a good idea to change the clocks? | 15:04 |
chrisspencer | we just keep them the same here in AZ :) | 15:05 |
sulo | there is a small bug in get /data | 15:05 |
sulo | and getting create calls to allow variables | 15:05 |
sulo | chrisspencer: yeah i hear you | 15:06 |
*** banix_ has joined #openstack-meeting-4 | 15:06 | |
sulo | expect PR's for all of it today | 15:06 |
sigmavirus | chrisspencer: it's supposed to help farmers and save energy but it does neither ;) | 15:06 |
sigmavirus | sulo: that sounds ominous | 15:06 |
sigmavirus | ;) | 15:06 |
*** banix has quit IRC | 15:07 | |
*** banix_ is now known as banix | 15:07 | |
*** mchiappero has left #openstack-meeting-4 | 15:07 | |
sulo | heh | 15:07 |
*** apuimedo has left #openstack-meeting-4 | 15:07 | |
sulo | mostly simple changes .. shouldnt break too much ;) | 15:07 |
sulo | i am going to start some work on workflow as well this week | 15:08 |
sigmavirus | awesome | 15:09 |
sulo | we can discuss more tomorrow during the dev vidyo meeting | 15:09 |
sigmavirus | That sounds good to me | 15:09 |
sigmavirus | Anything else sulo? | 15:09 |
sulo | i think thats all from my side | 15:09 |
*** ivc_ has left #openstack-meeting-4 | 15:09 | |
sigmavirus | chrisspencer: since you're the only other one here, do you have any updates? | 15:10 |
*** amotoki has joined #openstack-meeting-4 | 15:10 | |
chrisspencer | I don't, haven't really spent any significant time on craton other than code reviews | 15:11 |
sigmavirus | Your reviews have been sincerely appreciated, chrisspencer | 15:11 |
sigmavirus | As for me, I'm just doing more work on our tests. Still pondering a solution to remove all the duplicated code between each of the shells commands | 15:12 |
*** tuan_luong has joined #openstack-meeting-4 | 15:12 | |
sigmavirus | #topic Patches needing code review | 15:13 |
*** openstack changes topic to "Patches needing code review (Meeting topic: craton)" | 15:13 | |
sigmavirus | If anyone has something they need reviewed, feel free to drop it here preceded by `#link ` | 15:13 |
*** spotz_zzz is now known as spotz | 15:13 | |
sulo | looks like nothing from me .. i need to fix the one that i have pending | 15:13 |
sigmavirus | #link https://review.openstack.org/393910 | 15:13 |
sigmavirus | That's nothing urgent, but it's simple | 15:14 |
sigmavirus | Just making it match the other shells unit tests that we have | 15:14 |
*** lserpietri has left #openstack-meeting-4 | 15:14 | |
sulo | ah cool | 15:15 |
sigmavirus | #topic Q&A / Wrap up / Idle chatter | 15:15 |
*** openstack changes topic to "Q&A / Wrap up / Idle chatter (Meeting topic: craton)" | 15:15 | |
sigmavirus | Anything else from anyone? | 15:15 |
sigmavirus | With only three of us, we can probably wrap this up 45 minutes earlier than expected :P | 15:16 |
sulo | :) | 15:16 |
*** irenab has quit IRC | 15:16 | |
sulo | ok lets end it .. see you guys later | 15:17 |
*** woodard has quit IRC | 15:17 | |
chrisspencer | later | 15:17 |
*** shananigans has left #openstack-meeting-4 | 15:17 | |
sigmavirus | #topic End meeting | 15:17 |
*** openstack changes topic to "End meeting (Meeting topic: craton)" | 15:17 | |
sigmavirus | #info Only 3 of us showed up so we're ending early this week | 15:18 |
sigmavirus | #endmeeting | 15:18 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:18 | |
openstack | Meeting ended Mon Nov 7 15:18:09 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:18 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-11-07-15.00.html | 15:18 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-11-07-15.00.txt | 15:18 |
openstack | Log: http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-11-07-15.00.log.html | 15:18 |
*** chrisspencer has left #openstack-meeting-4 | 15:18 | |
*** oanson has joined #openstack-meeting-4 | 15:19 | |
*** rbak has joined #openstack-meeting-4 | 15:20 | |
*** oshidoshi has quit IRC | 15:29 | |
*** galstrom_zzz is now known as galstrom | 15:32 | |
*** yamahata has joined #openstack-meeting-4 | 15:33 | |
*** links has joined #openstack-meeting-4 | 15:35 | |
*** automagically has left #openstack-meeting-4 | 15:36 | |
*** numans has quit IRC | 15:36 | |
*** dtardivel has quit IRC | 15:41 | |
*** serverascode has quit IRC | 15:41 | |
*** sripriya has quit IRC | 15:41 | |
*** coolsvap has quit IRC | 15:42 | |
*** izaakk has quit IRC | 15:42 | |
*** carl_baldwin has quit IRC | 15:42 | |
*** johnsom has quit IRC | 15:42 | |
*** cloudnull has quit IRC | 15:42 | |
*** ChrisPriceAB has quit IRC | 15:42 | |
*** ChrisPriceAB has joined #openstack-meeting-4 | 15:42 | |
*** vdrok has quit IRC | 15:42 | |
*** MarkAtwood has quit IRC | 15:42 | |
*** alanmeadows has quit IRC | 15:42 | |
*** dpyzhov has quit IRC | 15:42 | |
*** uli-k has quit IRC | 15:42 | |
*** skath has quit IRC | 15:42 | |
*** csatari has quit IRC | 15:42 | |
*** masteinhauser has quit IRC | 15:42 | |
*** cargonza has quit IRC | 15:42 | |
*** ashtokolov has quit IRC | 15:42 | |
*** nikhil has quit IRC | 15:42 | |
*** qwang has quit IRC | 15:42 | |
*** wolsen has quit IRC | 15:42 | |
*** sweston has quit IRC | 15:42 | |
*** kozhukalov has quit IRC | 15:42 | |
*** amit213 has quit IRC | 15:42 | |
*** margaret has quit IRC | 15:42 | |
*** alex_didenko has quit IRC | 15:42 | |
*** dougwig has quit IRC | 15:42 | |
*** zhiyan has quit IRC | 15:42 | |
*** Kevin_Zheng has quit IRC | 15:42 | |
*** raddaoui has quit IRC | 15:42 | |
*** RaginBajin has quit IRC | 15:42 | |
*** zeestrat has quit IRC | 15:42 | |
*** raginbaj- is now known as raginbajin | 15:42 | |
*** yfauser has quit IRC | 15:43 | |
*** nkrinner_afk has quit IRC | 15:43 | |
*** dasanind_ has quit IRC | 15:43 | |
*** erikmwilson has quit IRC | 15:43 | |
*** cjloader has quit IRC | 15:43 | |
*** fungi has quit IRC | 15:43 | |
*** odyssey4me has quit IRC | 15:43 | |
*** FrankZhang has quit IRC | 15:43 | |
*** toan has quit IRC | 15:43 | |
*** dtardivel has joined #openstack-meeting-4 | 15:44 | |
*** ashtokolov has joined #openstack-meeting-4 | 15:44 | |
*** wolsen has joined #openstack-meeting-4 | 15:44 | |
*** zhiyan has joined #openstack-meeting-4 | 15:45 | |
*** dpyzhov has joined #openstack-meeting-4 | 15:45 | |
*** Kevin_Zheng has joined #openstack-meeting-4 | 15:45 | |
*** csatari has joined #openstack-meeting-4 | 15:45 | |
*** izaakk has joined #openstack-meeting-4 | 15:45 | |
*** coolsvap has joined #openstack-meeting-4 | 15:45 | |
*** nikhil has joined #openstack-meeting-4 | 15:45 | |
*** dougwig has joined #openstack-meeting-4 | 15:45 | |
*** sripriya has joined #openstack-meeting-4 | 15:45 | |
*** trinaths has joined #openstack-meeting-4 | 15:46 | |
*** sweston has joined #openstack-meeting-4 | 15:46 | |
*** vdrok has joined #openstack-meeting-4 | 15:46 | |
*** johnsom has joined #openstack-meeting-4 | 15:46 | |
*** qwang has joined #openstack-meeting-4 | 15:46 | |
*** skath has joined #openstack-meeting-4 | 15:46 | |
*** cargonza has joined #openstack-meeting-4 | 15:46 | |
*** alex_didenko has joined #openstack-meeting-4 | 15:47 | |
*** toan has joined #openstack-meeting-4 | 15:47 | |
*** margaret has joined #openstack-meeting-4 | 15:47 | |
*** amit213 has joined #openstack-meeting-4 | 15:47 | |
*** alanmeadows has joined #openstack-meeting-4 | 15:48 | |
*** zeestrat has joined #openstack-meeting-4 | 15:48 | |
*** RaginBajin_ has joined #openstack-meeting-4 | 15:48 | |
*** kozhukalov has joined #openstack-meeting-4 | 15:48 | |
*** serverascode has joined #openstack-meeting-4 | 15:48 | |
*** carl_baldwin has joined #openstack-meeting-4 | 15:48 | |
*** cloader89 has joined #openstack-meeting-4 | 15:48 | |
*** odyssey4me has joined #openstack-meeting-4 | 15:48 | |
*** erikmwilson has joined #openstack-meeting-4 | 15:48 | |
*** cloader89 is now known as cjloader | 15:48 | |
*** FrankZhang has joined #openstack-meeting-4 | 15:49 | |
*** raddaoui has joined #openstack-meeting-4 | 15:49 | |
*** cloudnull has joined #openstack-meeting-4 | 15:50 | |
*** makowals has quit IRC | 15:51 | |
*** MarkAtwood has joined #openstack-meeting-4 | 15:52 | |
*** masteinhauser has joined #openstack-meeting-4 | 15:52 | |
*** dave-mccowan has quit IRC | 15:53 | |
*** dasanind_ has joined #openstack-meeting-4 | 15:54 | |
*** nkrinner_afk has joined #openstack-meeting-4 | 15:54 | |
*** fungi has joined #openstack-meeting-4 | 15:55 | |
*** spzala has joined #openstack-meeting-4 | 15:55 | |
*** uli-k has joined #openstack-meeting-4 | 15:56 | |
*** hshiina has joined #openstack-meeting-4 | 15:57 | |
*** banix has quit IRC | 15:57 | |
*** tuan_luong has quit IRC | 15:58 | |
*** Sukhdev has joined #openstack-meeting-4 | 16:00 | |
Sukhdev | Folks, time for Ironic-neutron integration meeting | 16:01 |
sambetts | o/ | 16:01 |
hshiina | o/ | 16:01 |
trinaths | o/ | 16:01 |
Sukhdev | #startmeeting ironic_neutron | 16:01 |
openstack | Meeting started Mon Nov 7 16:01:57 2016 UTC and is due to finish in 60 minutes. The chair is Sukhdev. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:01 |
*** openstack changes topic to " (Meeting topic: ironic_neutron)" | 16:01 | |
openstack | The meeting name has been set to 'ironic_neutron' | 16:02 |
jroll | \o | 16:02 |
*** zenoway has quit IRC | 16:02 | |
Sukhdev | #topic: Agenda | 16:02 |
*** openstack changes topic to ": Agenda (Meeting topic: ironic_neutron)" | 16:02 | |
Sukhdev | #link: https://wiki.openstack.org/wiki/Meetings/Ironic-neutron#Meeting_November_7.2C_2016 | 16:02 |
*** zenoway has joined #openstack-meeting-4 | 16:02 | |
Sukhdev | Welcome to first meeting after the summit | 16:02 |
Sukhdev | Hope everybody is fully recovered from travels by now | 16:02 |
Sukhdev | #topic: Announcements | 16:03 |
*** openstack changes topic to ": Announcements (Meeting topic: ironic_neutron)" | 16:03 | |
Sukhdev | Anybody has any announcements? | 16:03 |
sambetts | Port groups API patch merged | 16:03 |
*** makowals has joined #openstack-meeting-4 | 16:03 | |
Sukhdev | yup - that is good news | 16:04 |
Sukhdev | I updated it on the agenda | 16:04 |
Sukhdev | lets dive into the agenda | 16:04 |
hshiina | nova schedule was announced http://lists.openstack.org/pipermail/openstack-dev/2016-October/106423.html | 16:04 |
jroll | ^^ | 16:04 |
hshiina | spec freeze is o-1, nov 17 | 16:04 |
jroll | need to get that nova portgroups spec merged | 16:04 |
hshiina | it's important | 16:05 |
sambetts | Nova team accepted attach/detach BP but we need to review/merge the Ironic RFE/spec first | 16:05 |
*** dave-mccowan has joined #openstack-meeting-4 | 16:06 | |
*** yamahata has quit IRC | 16:06 | |
sambetts | wow thats 1 week away.. . | 16:06 |
*** zenoway has quit IRC | 16:06 | |
Sukhdev | yup - its almost upon us | 16:07 |
Sukhdev | lets quickly go through the agenda items | 16:08 |
Sukhdev | #topic Security Groups | 16:08 |
*** openstack changes topic to "Security Groups (Meeting topic: ironic_neutron)" | 16:08 | |
Sukhdev | I posted the documentation patch for this | 16:09 |
Sukhdev | #link: https://review.openstack.org/#/c/393962/ | 16:09 |
Sukhdev | when ever you have a moment, please have a look at it | 16:10 |
Sukhdev | for the patch - https://review.openstack.org/#/c/361451 | 16:10 |
Sukhdev | sambetts and I had a brief discussion on Friday regarding the flag security_group_enabled | 16:11 |
Sukhdev | i.e. if the security_group_enabled flag False, and SGs are configured, how to deal with this | 16:11 |
Sukhdev | I checked on the neutron and nova side as to how this is handled. | 16:12 |
*** pcaruana has quit IRC | 16:12 | |
Sukhdev | basically, if this flag is set to false and somebody tries to set security groups at the time of nova boot - the instance fails | 16:13 |
Sukhdev | in our case it is slightly different - as everything is being set/done during the init | 16:14 |
Sukhdev | for tenant networks, it will have the same behavior - however, how do we want to deal with it when this happens for provisioning or cleaning networks | 16:14 |
Sukhdev | we can take two approaches - | 16:15 |
Sukhdev | 1 ) Since all of these operations are managed by admin, we should simply document it | 16:15 |
Sukhdev | 2) we fail the operation | 16:16 |
Sukhdev | or may be both actullay | 16:16 |
*** sdake has joined #openstack-meeting-4 | 16:16 | |
Sukhdev | any thoughts? | 16:16 |
jroll | both seems right to me | 16:17 |
jroll | if someone has configured some security group, they expect that port to be locked down, we shouldn't allow a port to be up that isn't locked down the way they expect | 16:17 |
jroll | if that makes sense | 16:17 |
*** berendt has joined #openstack-meeting-4 | 16:18 | |
*** lserpietri has joined #openstack-meeting-4 | 16:19 | |
*** lserpietri has left #openstack-meeting-4 | 16:19 | |
Sukhdev | the way the SG patch is written, it will behave like that - i.e. port_create() will fail and log the exception | 16:19 |
*** sdake has quit IRC | 16:20 | |
Sukhdev | l just noticed sambetts comment about it on the patch - | 16:21 |
sambetts | Sorry for being slow to respond, I was in another call, I put a more detailed https://review.openstack.org/#/c/361451/14/ironic/common/neutron.py | 16:21 |
Sukhdev | I think option 2 in your comment - i.e. misconfiguration seems more appropriate | 16:21 |
jroll | +1 | 16:22 |
sambetts | the only reason I prefer option 1 is that port security can be enabled and disabled at will in the neutron API, however the secuirty groups in the ironic configuration can only be disabled by editing the ironic config file and restarting ironic, so it the admin wants to debug something and turns off port secuirty it'll prevent all ironic deployments | 16:23 |
jroll | sambetts: as an operator, I never want to be surprised with something less secure than I expect | 16:24 |
jroll | is why I'm on the option 2 side | 16:24 |
Sukhdev | sambetts : that scenario is not really applicable in this case - it is the same operator who is adding both options | 16:24 |
*** sdake has joined #openstack-meeting-4 | 16:25 | |
sambetts | I'm talking about post having Ironic running, I don't want to have to restart ironic once its running to do something which in other cases can simply be enabled/disable via an API | 16:25 |
jroll | yeah, I get it, but I think it can put someone in a "dangerous" position | 16:26 |
Sukhdev | sambetts : i chatted with both nova and neutron PTLs about this on Friday after our discussion - it is used to fail the instance - in case somebody tries to specify SG, when they should not be | 16:27 |
sambetts | yeah they changed it in mitaka to just not apply the SG right? | 16:28 |
Sukhdev | in our case, these operations are managed by the admin | 16:28 |
*** tonytan4ever has quit IRC | 16:29 | |
Sukhdev | I mean to say is that the net effect of this mis-configuration is that the instance is faied | 16:29 |
*** tonytan4ever has joined #openstack-meeting-4 | 16:30 | |
* sambetts wonders if this is the sort of check we should have on the neutron network driver validate() function | 16:30 | |
*** belmoreira has quit IRC | 16:30 | |
*** admin0 has left #openstack-meeting-4 | 16:30 | |
Sukhdev | I am of the openion that we update the documentation - where we talk about the provisioning/cleaning network creation | 16:32 |
Sukhdev | actually, the patch that I pushed for documentation - I should add text to describe this | 16:32 |
*** krtaylor has quit IRC | 16:33 | |
*** limao_ has quit IRC | 16:33 | |
*** garyloug has quit IRC | 16:34 | |
Sukhdev | thoughts? | 16:34 |
*** garyloug has joined #openstack-meeting-4 | 16:35 | |
jroll | yes, agree | 16:35 |
sambetts | I think we should definatly document it, but I wonder if we should fail earlier in the process if the network has port security disabled | 16:35 |
jroll | yeah, I wouldn't be opposed to checking in validate | 16:36 |
Sukhdev | sambetts : failing earlier does not really help - as you pointed out earlier - if somebody changes the network properties after everything is running | 16:37 |
sambetts | e.g. make the nodes configured the neutron network interface fail validation or have an explict check so that we don't fire off N port creates even though we know they are going to fail | 16:37 |
*** ruriryan has left #openstack-meeting-4 | 16:38 | |
*** iyamahat has joined #openstack-meeting-4 | 16:38 | |
Sukhdev | so, this is really a weird scenario - I can see the usefulness if there are multiple operators | 16:39 |
*** spzala has quit IRC | 16:39 | |
Sukhdev | failing earlier helps if someone creates networks and SGs and also sets this flag to false - which is kind of weird :-) | 16:39 |
*** spotz is now known as spotz_zzz | 16:40 | |
*** spzala has joined #openstack-meeting-4 | 16:40 | |
*** vishwanathj has joined #openstack-meeting-4 | 16:40 | |
sambetts | Sukhdev: nova runs node validation has part of its resource discovering process and will prevent nova scheduling instances on the node if they are misconfigured | 16:40 |
*** berendt has quit IRC | 16:41 | |
jroll | sambetts: no, validation happens post-schedule | 16:41 |
jroll | but agree, it will save some time/resources | 16:41 |
Sukhdev | see here - https://github.com/openstack/nova/blob/14.0.1/nova/network/neutronv2/api.py#L783 | 16:42 |
sambetts | jroll: ? really?! I'm sure nodes that fail validation don't show up as available to nova? | 16:42 |
*** spotz_zzz is now known as spotz | 16:42 | |
Sukhdev | this is where this is checked | 16:42 |
jroll | sambetts: yeah, it happens here https://github.com/openstack/nova/blob/master/nova/virt/ironic/driver.py#L763 | 16:42 |
*** trinaths has left #openstack-meeting-4 | 16:43 | |
jroll | sambetts: it also happens between enroll and manageable, so you're partially right | 16:43 |
*** berendt has joined #openstack-meeting-4 | 16:44 | |
*** spzala has quit IRC | 16:44 | |
Sukhdev | nova only checks this flag at the time of port create | 16:44 |
*** reedip_ has quit IRC | 16:45 | |
Sukhdev | sambetts : even if we go with the idea of checking this flag - what would you see the end-result? - not fail the operation? | 16:46 |
sambetts | No fail it, but we'd fail here: https://github.com/openstack/nova/blob/master/nova/virt/ironic/driver.py#L763 | 16:47 |
sambetts | before we've even starting deployment | 16:47 |
*** spzala has joined #openstack-meeting-4 | 16:47 | |
sambetts | but this is something we can always expand on later | 16:47 |
*** shaohe_feng_ has joined #openstack-meeting-4 | 16:48 | |
Sukhdev | hmm... | 16:48 |
*** lihi has quit IRC | 16:48 | |
*** shaohe_f- has joined #openstack-meeting-4 | 16:48 | |
Sukhdev | I really believe this is an issue of misconfiguration - and, we can come back and this check here if it becomes an issue - | 16:50 |
Sukhdev | I mean add this check here | 16:50 |
*** shaohe_feng has quit IRC | 16:50 | |
jroll | I mean... we agreed to add a check. why not add it sooner in the deploy process? | 16:50 |
sambetts | jroll: we technically don't need the check right now, it'll just catch the failure like any other port create error right now | 16:51 |
jroll | s/add a check/have it fail/ | 16:51 |
*** spzala has quit IRC | 16:51 | |
jroll | :) | 16:51 |
*** shaohe_feng has joined #openstack-meeting-4 | 16:52 | |
Sukhdev | +1 | 16:52 |
*** shaohe_feng_ has quit IRC | 16:52 | |
jroll | so, agree to fail early in validate()? | 16:52 |
sambetts | I guess the only potential arguement might be to do with validate being syncronous and making an external call */me ducks* | 16:52 |
*** shaohe_f- has quit IRC | 16:52 | |
jroll | sambetts: it already hits the bmc, if neutron ever gets slower than a bmc we have bigger problems :) | 16:53 |
*** spzala has joined #openstack-meeting-4 | 16:53 | |
jroll | net-show, anyway | 16:53 |
sambetts | true true | 16:53 |
sambetts | does validate hit the BMC? | 16:53 |
jroll | yes | 16:53 |
sambetts | for power or something? | 16:54 |
persia | Some folk talk about running neutron on fairly low-spec switch hardware. Some BMCs have fairly high-clock cores. Take care with assumptions. | 16:54 |
jroll | oh wait, apparently we do not: https://github.com/openstack/ironic/blob/master/ironic/drivers/modules/ipmitool.py#L774 | 16:54 |
jroll | :/ | 16:54 |
jroll | persia: fair point | 16:54 |
* Sukhdev time check - 5 min | 16:55 | |
Sukhdev | lets draw some conclusions | 16:55 |
sambetts | I'm happy with the patch as it is today if we're happy for it to be a misconfiguration | 16:56 |
*** sdake has quit IRC | 16:56 | |
*** jerms has joined #openstack-meeting-4 | 16:56 | |
sambetts | I've removed my -1 | 16:56 |
jroll | I'm still happiest with doing this in validate(), but okay with current status quo too | 16:56 |
Sukhdev | I think we can come back with a new patch to address it | 16:57 |
*** berendt has quit IRC | 16:57 | |
*** spzala has quit IRC | 16:57 | |
Sukhdev | I will push an update to the documentation patch to describe this misconfiguration patch | 16:57 |
* Sukhdev 2 min left | 16:58 | |
Sukhdev | anything critical to discuss? | 16:58 |
sambetts | nothing from me as far as I can remember | 16:59 |
Sukhdev | Thanks folks, this was a very good discussion - | 16:59 |
Sukhdev | see ya'll next week when US will have new president :-) | 16:59 |
Sukhdev | bye | 17:00 |
sambetts | :/ | 17:00 |
*** shaohe_feng has quit IRC | 17:00 | |
sambetts | cya o/ | 17:00 |
Sukhdev | #endmeeting | 17:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 17:00 | |
openstack | Meeting ended Mon Nov 7 17:00:18 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-11-07-16.01.html | 17:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-11-07-16.01.txt | 17:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-11-07-16.01.log.html | 17:00 |
*** shaohe_feng has joined #openstack-meeting-4 | 17:01 | |
*** shaohe_f- has joined #openstack-meeting-4 | 17:02 | |
*** shaohe_f| has joined #openstack-meeting-4 | 17:02 | |
*** vishwanathj has quit IRC | 17:03 | |
*** krtaylor has joined #openstack-meeting-4 | 17:03 | |
*** shaohe_f- has quit IRC | 17:04 | |
*** krtaylor has quit IRC | 17:05 | |
*** iyamahat has quit IRC | 17:05 | |
*** shaohe_feng has quit IRC | 17:06 | |
*** shaohe_f| has quit IRC | 17:06 | |
*** woodard has joined #openstack-meeting-4 | 17:07 | |
*** ppiela_ has joined #openstack-meeting-4 | 17:07 | |
*** matrohon has quit IRC | 17:09 | |
*** jovon has joined #openstack-meeting-4 | 17:09 | |
*** krtaylor has joined #openstack-meeting-4 | 17:11 | |
*** shaohe_feng has joined #openstack-meeting-4 | 17:13 | |
*** caboucha has joined #openstack-meeting-4 | 17:17 | |
*** shaohe_feng has quit IRC | 17:18 | |
*** links has quit IRC | 17:20 | |
*** berendt has joined #openstack-meeting-4 | 17:22 | |
*** banix has joined #openstack-meeting-4 | 17:22 | |
*** shaohe_feng has joined #openstack-meeting-4 | 17:22 | |
*** unicell1 has quit IRC | 17:23 | |
*** shaohe_feng_ has joined #openstack-meeting-4 | 17:25 | |
*** shaohe_feng has quit IRC | 17:26 | |
*** shaohe_feng has joined #openstack-meeting-4 | 17:26 | |
*** anilvenkata has quit IRC | 17:26 | |
*** numans has joined #openstack-meeting-4 | 17:28 | |
*** shaohe_feng_ has quit IRC | 17:30 | |
*** Sukhdev has quit IRC | 17:30 | |
*** shaohe_feng has quit IRC | 17:30 | |
*** asettle has quit IRC | 17:33 | |
*** ppiela_ has quit IRC | 17:37 | |
*** shaohe_feng_ has joined #openstack-meeting-4 | 17:37 | |
*** shaohe_feng_ has quit IRC | 17:40 | |
*** iyamahat has joined #openstack-meeting-4 | 17:41 | |
*** shaohe_feng has joined #openstack-meeting-4 | 17:42 | |
*** iyamahat has quit IRC | 17:45 | |
*** shaohe_feng_ has joined #openstack-meeting-4 | 17:46 | |
*** shaohe_feng_ has quit IRC | 17:46 | |
*** shaohe_feng_ has joined #openstack-meeting-4 | 17:47 | |
*** shaohe_feng has quit IRC | 17:49 | |
*** hemanthm|away is now known as hemanth | 17:49 | |
*** shaohe_feng_ has quit IRC | 17:51 | |
*** shaohe_feng has joined #openstack-meeting-4 | 17:51 | |
*** shaohe_feng_ has joined #openstack-meeting-4 | 17:53 | |
*** automagically has joined #openstack-meeting-4 | 17:53 | |
*** cdelatte has joined #openstack-meeting-4 | 17:54 | |
*** hshiina has left #openstack-meeting-4 | 17:54 | |
*** shaohe_f- has joined #openstack-meeting-4 | 17:55 | |
*** ad_rien_ has quit IRC | 17:55 | |
*** shaohe_feng has quit IRC | 17:56 | |
*** shaohe_feng has joined #openstack-meeting-4 | 17:57 | |
*** shaohe_feng_ has quit IRC | 17:58 | |
*** ralonsoh has quit IRC | 17:58 | |
*** shaohe_f- has quit IRC | 17:59 | |
*** shaohe_feng has quit IRC | 18:00 | |
*** degorenko is now known as _degorenko|afk | 18:00 | |
*** unicell has joined #openstack-meeting-4 | 18:05 | |
*** garyloug has quit IRC | 18:05 | |
*** neiljerram has quit IRC | 18:06 | |
*** dave-mccowan has quit IRC | 18:06 | |
*** yamahata has joined #openstack-meeting-4 | 18:06 | |
*** dave-mccowan has joined #openstack-meeting-4 | 18:11 | |
*** shaohe_feng has joined #openstack-meeting-4 | 18:12 | |
*** shaohe_feng has quit IRC | 18:14 | |
*** shaohe_feng has joined #openstack-meeting-4 | 18:14 | |
*** shaohe_feng_ has joined #openstack-meeting-4 | 18:18 | |
*** shaohe_feng has quit IRC | 18:18 | |
*** shaohe_feng_ is now known as shaohe_feng | 18:18 | |
*** yamahata has quit IRC | 18:19 | |
*** ad_rien_ has joined #openstack-meeting-4 | 18:20 | |
*** yamahata has joined #openstack-meeting-4 | 18:22 | |
*** sshnaidm is now known as sshnaidm|brb | 18:26 | |
*** yamahata has quit IRC | 18:31 | |
*** iyamahat has joined #openstack-meeting-4 | 18:32 | |
*** dtardivel has quit IRC | 18:34 | |
*** ad_rien_ has quit IRC | 18:39 | |
*** armax has joined #openstack-meeting-4 | 18:39 | |
*** spzala has joined #openstack-meeting-4 | 18:54 | |
*** markvoelker_ has joined #openstack-meeting-4 | 18:54 | |
*** Sukhdev has joined #openstack-meeting-4 | 18:55 | |
*** markvoelker has quit IRC | 18:56 | |
*** markvoelker has joined #openstack-meeting-4 | 18:57 | |
*** s3wong has joined #openstack-meeting-4 | 18:58 | |
*** hemanth is now known as hemanth|lunch | 18:59 | |
*** markvoelker_ has quit IRC | 18:59 | |
*** sambetts is now known as sambetts|afk | 18:59 | |
*** iyamahat has quit IRC | 19:07 | |
*** d0ugal has quit IRC | 19:30 | |
*** d0ugal has joined #openstack-meeting-4 | 19:31 | |
*** d0ugal has quit IRC | 19:31 | |
*** d0ugal has joined #openstack-meeting-4 | 19:31 | |
*** hemanth|lunch is now known as hemanth | 19:31 | |
*** anilvenkata has joined #openstack-meeting-4 | 19:31 | |
*** dave-mccowan has quit IRC | 19:39 | |
*** yamahata has joined #openstack-meeting-4 | 19:39 | |
*** armax has quit IRC | 19:44 | |
*** ad_rien_ has joined #openstack-meeting-4 | 19:50 | |
*** sshnaidm|brb is now known as sshnaidm | 19:52 | |
*** dave-mccowan has joined #openstack-meeting-4 | 19:53 | |
*** yamahata has quit IRC | 19:54 | |
*** woodster_ has joined #openstack-meeting-4 | 19:56 | |
*** spotz is now known as spotz_zzz | 19:57 | |
*** ad_rien_ has quit IRC | 20:09 | |
*** uxdanielle has joined #openstack-meeting-4 | 20:15 | |
*** yifei has quit IRC | 20:23 | |
*** yifei has joined #openstack-meeting-4 | 20:23 | |
*** jmccrory has quit IRC | 20:24 | |
*** jmccrory has joined #openstack-meeting-4 | 20:25 | |
*** d0ugal has quit IRC | 20:26 | |
*** wirehead_ has left #openstack-meeting-4 | 20:26 | |
*** d0ugal has joined #openstack-meeting-4 | 20:27 | |
*** d0ugal has quit IRC | 20:27 | |
*** d0ugal has joined #openstack-meeting-4 | 20:27 | |
*** uxdanielle has quit IRC | 20:28 | |
*** spotz_zzz is now known as spotz | 20:39 | |
*** spzala has quit IRC | 20:40 | |
*** revon has joined #openstack-meeting-4 | 20:40 | |
*** oanson has quit IRC | 20:41 | |
*** matrohon has joined #openstack-meeting-4 | 20:41 | |
*** iyamahat has joined #openstack-meeting-4 | 20:45 | |
*** armax has joined #openstack-meeting-4 | 20:47 | |
*** automagically has left #openstack-meeting-4 | 20:48 | |
*** banix_ has joined #openstack-meeting-4 | 20:53 | |
*** banix__ has joined #openstack-meeting-4 | 20:54 | |
*** banix has quit IRC | 20:55 | |
*** banix__ is now known as banix | 20:55 | |
*** banix_ has quit IRC | 20:57 | |
*** anilvenkata has quit IRC | 20:58 | |
*** MeganR has joined #openstack-meeting-4 | 21:00 | |
*** Rockyg has joined #openstack-meeting-4 | 21:00 | |
*** mriedem has joined #openstack-meeting-4 | 21:00 | |
*** julim has quit IRC | 21:17 | |
*** uck has joined #openstack-meeting-4 | 21:21 | |
*** spzala has joined #openstack-meeting-4 | 21:22 | |
*** spzala has quit IRC | 21:27 | |
*** yfauser has joined #openstack-meeting-4 | 21:28 | |
*** mriedem has left #openstack-meeting-4 | 21:30 | |
*** Jeffrey4l has quit IRC | 21:35 | |
*** spzala has joined #openstack-meeting-4 | 21:35 | |
*** cleong has quit IRC | 21:38 | |
*** yamahata has joined #openstack-meeting-4 | 21:41 | |
*** myatsenko has quit IRC | 21:43 | |
*** iyamahat has quit IRC | 21:44 | |
*** banix has quit IRC | 21:45 | |
*** baoli has quit IRC | 21:45 | |
*** rtheis has quit IRC | 21:51 | |
*** bobmel has quit IRC | 22:00 | |
*** MeganR has quit IRC | 22:00 | |
*** armax has quit IRC | 22:01 | |
*** yamahata has quit IRC | 22:06 | |
*** caboucha has quit IRC | 22:07 | |
*** woodard has quit IRC | 22:10 | |
*** thorst_ has quit IRC | 22:10 | |
*** iyamahat has joined #openstack-meeting-4 | 22:14 | |
*** krtaylor has quit IRC | 22:22 | |
*** tonytan4ever has quit IRC | 22:23 | |
*** iyamahat has quit IRC | 22:29 | |
*** jcdfr has joined #openstack-meeting-4 | 22:30 | |
*** matrohon has quit IRC | 22:31 | |
*** jcdfr has quit IRC | 22:31 | |
*** iyamahat has joined #openstack-meeting-4 | 22:39 | |
*** uxdanielle has joined #openstack-meeting-4 | 22:46 | |
*** bobmel has joined #openstack-meeting-4 | 22:47 | |
*** kylek3h has quit IRC | 22:51 | |
*** limao has joined #openstack-meeting-4 | 22:56 | |
*** limao_ has joined #openstack-meeting-4 | 22:58 | |
*** yfauser_ has joined #openstack-meeting-4 | 22:59 | |
*** yfauser has quit IRC | 22:59 | |
*** limao has quit IRC | 23:01 | |
*** spotz is now known as spotz_zzz | 23:06 | |
*** spotz_zzz is now known as spotz | 23:06 | |
*** jovon has quit IRC | 23:07 | |
*** bobh has quit IRC | 23:10 | |
*** baoli has joined #openstack-meeting-4 | 23:11 | |
*** galstrom is now known as galstrom_zzz | 23:11 | |
*** rbak has quit IRC | 23:28 | |
*** Jeffrey4l has joined #openstack-meeting-4 | 23:31 | |
*** Julien-zte has quit IRC | 23:32 | |
*** cdelatte has quit IRC | 23:33 | |
*** armax has joined #openstack-meeting-4 | 23:36 | |
*** limao_ has quit IRC | 23:46 | |
*** thorst_ has joined #openstack-meeting-4 | 23:47 | |
*** sshnaidm is now known as sshnaidm|away | 23:53 | |
*** gibi_ has quit IRC | 23:56 | |
*** gibi has joined #openstack-meeting-4 | 23:56 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!