Difference between revisions of "Meetings/taas"
< Meetings
(→Agenda (2016-01-20)) |
|||
| Line 11: | Line 11: | ||
* (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS? | * (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS? | ||
* (kaz) Update for https://review.openstack.org/#/c/248043/ | * (kaz) Update for https://review.openstack.org/#/c/248043/ | ||
| − | |||
| − | |||
| − | |||
| − | |||
== Agenda (2015-12-16) == | == Agenda (2015-12-16) == | ||
Revision as of 06:47, 20 January 2016
Contents
Neutron Tap as a Service (TaaS) Meeting
http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting
Agenda (2016-01-20)
- (reedip) Specification https://review.openstack.org/#/c/256210/ needs to be revived.Will drop a mail today on ML as a call to Neutron Core to review
- (reedip) Re-propose https://review.openstack.org/#/c/229869/ with the above Spec request.
- (reedip, vyadav) Work to begin on L2 Extension. Need to work with https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion
- (reedip) Is an IRC channel needed for TaaS?
- (reedip) Core reviewers needed for TaaS, so that two +2 rule can be followed
- (vyadav, reedip ) Is Blueprints required in the Launchpad for TaaS?
- (kaz) Update for https://review.openstack.org/#/c/248043/
Agenda (2015-12-16)
- (yamamoto) end of year and new year holidays?
- (yamamoto) let's revive spec discussion https://review.openstack.org/#/c/256210/
- (yamamoto) we ought to maintain "two +2s to merge" rule
- currently we are doing "one +2 to merge"
- (yamamoto) have a dedicated irc channel?
- (soichi, kaz) neutron ovs-agent deletes taas flows (cont.)
- (yamamoto) we ought to fill https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion
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)
