Difference between revisions of "Meetings/ServiceFunctionChainingMeeting"
< Meetings
(→Topics for Next Meeting) |
(→Agenda for the next Networking - Service Function Chaining Meeting) |
||
| Line 5: | Line 5: | ||
== Agenda for the next Networking - Service Function Chaining Meeting == | == Agenda for the next Networking - Service Function Chaining Meeting == | ||
| − | + | * Follow-up on previous meeting discussion: Tacker to call networking-sfc API and then our driver model delegates out to whichever SDN controller mech driver is appropriate | |
| − | |||
| − | |||
| − | * Follow up on previous meeting discussion: Tacker to call networking-sfc API and then our driver model delegates out to whichever SDN controller mech driver is appropriate | ||
* Patch update progress | * Patch update progress | ||
* Patch dependency issue and how we avoid cross damage to other patches due to change of one patch | * Patch dependency issue and how we avoid cross damage to other patches due to change of one patch | ||
Revision as of 21:57, 18 November 2015
Weekly Neutron Service Function Chaining Meeting Info
Weekly on Thursday at 1700 UTC in #openstack-meeting-4 (IRC webclient) Chair (to contact for more information): Cathy Hong Zhang (cathy-h-zhang), Louis Fourie (louis-fourie) Logs from past meetings: http://eavesdrop.openstack.org/meetings/service_chaining/2015/
Agenda for the next Networking - Service Function Chaining Meeting
- Follow-up on previous meeting discussion: Tacker to call networking-sfc API and then our driver model delegates out to whichever SDN controller mech driver is appropriate
- Patch update progress
- Patch dependency issue and how we avoid cross damage to other patches due to change of one patch
