Difference between revisions of "Meetings/taas"
< Meetings
(→Agenda (2015-12-09)) |
|||
| Line 2: | Line 2: | ||
http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting | http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting | ||
| + | |||
| + | == Apologies for Absence == | ||
| + | |||
| + | * yamamoto will be absent from 2015-12-23 to 2016-01-10 | ||
| + | |||
| + | == Agenda (2015-12-16) == | ||
| + | * end of year and new year holidays? | ||
| + | * let's revive spec discussion https://review.openstack.org/#/c/256210/ | ||
== Agenda (2015-12-09) == | == Agenda (2015-12-09) == | ||
Revision as of 04:49, 11 December 2015
Contents
Neutron Tap as a Service (TaaS) Meeting
http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting
Apologies for Absence
- yamamoto will be absent from 2015-12-23 to 2016-01-10
Agenda (2015-12-16)
- end of year and new year holidays?
- let's revive spec discussion https://review.openstack.org/#/c/256210/
Agenda (2015-12-09)
- neutron ovs-agent deletes taas flows
- gate-tempest-dsvm-tap-as-a-service is now voting
Agenda (2015-12-02)
- finish usecase and API discussion
- have a subproject spec?
- What do you say to adding +1 for creating dashboard repository for neutron subprojects?
- port security setting
Agenda (2015-11-25)
- leftovers from the previous agenda
- More Core Reviewers needed
- Isolation of production and mirrored traffics. Media: TrafficIsolation_20151116-01.pdf (cont.)
- Media: Response_Anil's_Comments (Response_Soichi's_Proposal).pdf
- We submitted our source code.
- Current implementation has several restrictions:
- Multiple monitoring VMs are not supported.
- IP addresses of underlay networks are hard-coded. (It should be read from a configuration file.)
- Current implementation has several restrictions:
Agenda (2015-11-18)
- Isolation of production and mirrored traffics. Media: TrafficIsolation_20151116-01.pdf
- Supporting operations from the dashboard. Media: OperationsFromGUI_20151116-01.pdf
- More Core Reviewers needed
Agenda (2015-11-11)
- Short introduction - participants, their position and interest in TaaS
- Current status of the project
- Blueprint clarifications + reviving the blueprint (?)
- The Neutron big tent - the missing parts from being part of it and division of tasks
Meetbot commands
- #startmeeting taas
- "taas" part is used for the log URL
- #endmeeting
- To end the meeting officially (as a result, meetbot will perform all of the necessary logging and archiving of the text from #startmeeting to #endmeeting)
