https://wiki.openstack.org/w/api.php?action=feedcontributions&user=Ogawa.yasufumi&feedformat=atom
OpenStack - User contributions [en]
2024-03-28T12:10:32Z
User contributions
MediaWiki 1.28.2
https://wiki.openstack.org/w/index.php?title=Forum/Vancouver2023&diff=183939
Forum/Vancouver2023
2023-11-22T07:24:25Z
<p>Ogawa.yasufumi: </p>
<hr />
<div>=Room 9=<br />
==Tuesday, June 13==<br />
* [https://etherpad.opendev.org/p/collaboration-wo-boundaries-vancouver-forum-2023 Collaborating without boundaries]<br />
* Meet the Open Infrastructure Foundation's Board of Directors - Informal meet and greet mixer, ergo no etherpad<br />
* [https://etherpad.opendev.org/p/vancouver-june2023-neutron Neutron meet and greet: Operators feedback session ]<br />
* [https://etherpad.opendev.org/p/YVR23-kolla-user-forum Kolla User Forum]<br />
* [https://etherpad.opendev.org/p/rbac-operator-feedback-vancouver2023 OpenStack RBAC: updates & operators feedback]<br />
* [https://etherpad.opendev.org/p/nova-vancouver2023-meet-and-greet Nova community meet&greet (2nd take) ]<br />
<br />
==Wednesday, June 14==<br />
* [https://etherpad.opendev.org/p/octavia-forum-vancouver2023 OpenStack Octavia Forum Session ]<br />
* [https://etherpad.opendev.org/p/oscsdk-vancouver-forum-2023 Managing OSC and SDK as multi-project deliverables]<br />
* [https://etherpad.opendev.org/p/vancouver23-ironic-forum Ironic: Our Future starts Now! ]<br />
* [https://etherpad.opendev.org/p/manila-vancouver-forum-2023 Operational concerns with OpenStack Manila - High Availability ]<br />
* [https://etherpad.opendev.org/p/cinder-vancouver-forum-2023 Cinder- the OpenStack Block Storage service ... how are we doing? ]<br />
* [https://etherpad.opendev.org/p/vancouver-2023-em How do we end the Extended Maintenance "experiment"?]<br />
* Observe All Openstack: expose metrics from OpenStack services<br />
* [https://etherpad.opendev.org/p/ois-vancouver-unite SDKs of all languages- unite!]<br />
* [https://etherpad.opendev.org/p/vancouver-june2023-upgrades-rebuilds-forum Upgrading hypervisors- live-migration and related fun]<br />
<br />
==Thursday, June 15==<br />
* [https://etherpad.opendev.org/p/publiccloud-vancouver-forum-2023 Public Cloud Certification]<br />
* [https://etherpad.opendev.org/p/tacker-forum-feedback-for-etsi-nfv-usecases Future requirements for Tacker's ETSI-NFV/O-RAN usecases]<br />
* [https://etherpad.opendev.org/p/vancouver-june2023-os-ansible OpenStack-Ansible - Project Onboarding]<br />
* [https://etherpad.opendev.org/p/vancouver-2023-i18n-forum Is it time to stop providing OpenStack translations?]<br />
* [https://etherpad.opendev.org/p/Summit23-kata-fb-session Kata Containers Feedback Forum]<br />
<br />
=Room 10=<br />
==Tuesday June 13==<br />
* [https://etherpad.opendev.org/p/tc-leaders-interaction-2023-vancouver The OpenStack Technical Committee + Community Leaders interaction]<br />
* [https://etherpad.opendev.org/p/vancouver-june2023-interop Improve Interop Testing]<br />
* [https://etherpad.opendev.org/p/diversity-survey-vancouver-forum-2023 Diversity Survey Feedback Session]<br />
<br />
==Wednesday June 14==<br />
* [https://etherpad.opendev.org/p/openinfra_ecg_forum_2023 So we talked a lot about edge computing. Can we get practical now?]<br />
* [https://etherpad.opendev.org/p/community_blueprint_forum_2023 So you know what open source is. Or do you?!]<br />
* [https://etherpad.opendev.org/p/challenges-largescale Challenges & Lessons from Operating OpenStack at Scale]<br />
<br />
==Thursday, June15==<br />
* [https://etherpad.opendev.org/p/openinfra-2023-kubernetes-on-openstack Kubernetes on OpenStack]</div>
Ogawa.yasufumi
https://wiki.openstack.org/w/index.php?title=Tacker/Installation&diff=178625
Tacker/Installation
2021-06-01T04:48:03Z
<p>Ogawa.yasufumi: /* Tacker Usage Guide */</p>
<hr />
<div>== Tacker Installation Guide ==<br />
<br />
For Tacker to work, the system consists of two parts, one is tacker system and another is VIM systems. Tacker system can be installed (here just some ways are listed):<br />
<br />
via Devstack, which is usually used by developers: https://docs.openstack.org/tacker/latest/install/devstack.html<br />
<br />
via Tacker source code manually: https://docs.openstack.org/tacker/latest/install/manual_installation.html<br />
<br />
via Kolla installation: https://docs.openstack.org/tacker/latest/install/kolla.html<br />
<br />
== Tacker Usage Guide ==<br />
<br />
1) Sample TOSCA YAML files are placed in https://opendev.org/openstack/tacker/src/branch/master/samples <br />
<br />
The NFV-orchestration cli-reference is available at https://docs.openstack.org/ocata/cli-reference/tacker.html<br />
<br />
2) Tacker using Horizon (NFV left menu entry)</div>
Ogawa.yasufumi
https://wiki.openstack.org/w/index.php?title=Tacker&diff=178623
Tacker
2021-06-01T04:41:06Z
<p>Ogawa.yasufumi: /* Repos */</p>
<hr />
<div>__NOTOC__<br />
<br />
= Tacker - OpenStack NFV Orchestration =<br />
<br />
Tacker is an official OpenStack project building a Generic VNF Manager (VNFM) and an NFV Orchestrator (NFVO) to deploy and operate Network Services and Virtual Network Functions (VNFs) on an NFV infrastructure platform like OpenStack. It is based on ETSI MANO Architectural Framework and provides a functional stack to Orchestrate Network Services end-to-end using VNFs. <br />
<br />
[[File:Tacker_Architecture.png]]<br />
<br />
= High-Level Architecture =<br />
<br />
<br />
== NFV Catalog ==<br />
<br />
# VNF Descriptors <br />
# Network Services Descriptors<br />
# VNF Forwarding Graph Descriptors<br />
<br />
== VNFM ==<br />
<br />
# Basic life-cycle of VNF (create/update/delete)<br />
# Enhanced platform-aware (EPA) placement of high-performance NFV workloads <br />
# Health monitoring of deployed VNFs<br />
# Auto Healing / Auto Scaling VNFs based on Policy<br />
# Facilitate initial configuration of VNF<br />
<br />
== NFVO ==<br />
<br />
# Templatized end-to-end Network Service deployment using decomposed VNFs<br />
# VNF placement policy – ensure efficient placement of VNFs <br />
# VNFs connected using an SFC - described in a VNF Forwarding Graph Descriptor<br />
# VIM Resource Checks and Resource Allocation<br />
# Ability to orchestrate VNFs across Multiple VIMs and Multiple Sites (POPs)<br />
<br />
<br />
= Documentation =<br />
<br />
https://docs.openstack.org/tacker/<br />
<br />
== Install Guide ==<br />
<br />
https://docs.openstack.org/tacker/latest/install/index.html<br />
<br />
= Use Cases =<br />
<br />
=== vCE ===<br />
<br />
Tacker API can be used by SP's OSS / BSS or an NFV Orchestrator to deploy VNFs in SP's network to deliver agile network services for remote Customer networks<br />
<br />
=== vCPE ===<br />
<br />
Tacker API can be used by SP's OSS / BSS or an NFV Orchestrator to manage OpenStack enabled remote CPE devices to deploy VNFs to provide locally network services at the customer site.<br />
<br />
=== vPE ===<br />
<br />
Tacker API can be used by SP's OSS / BSS or an NFV Orchestrator to deploy VNFs within SP's network to virtualize existing network services into a Virtual Function.<br />
<br />
=== Telecom operator's expectations ===<br />
[[Tacker/UseCase|What Tacker solves ?]]<br />
<br />
= ETSI NFV SPECS =<br />
[http://www.etsi.org/standards-search#page=1&search=&title=1&etsiNumber=1&content=0&version=0&onApproval=1&published=1&historical=0&startDate=1988-01-15&endDate=2017-02-03&harmonized=0&keyword=&TB=789,,832,,831,,795,,796,,800,,798,,799,,797&stdType=&frequency=&mandate=&sort=1 ETSI NFV SPECS]<br />
<br />
= TOSCA for NFV =<br />
<br />
Tacker uses TOSCA for VNF meta-data definition. Within TOSCA Tacker used NFV profile schema.<br />
* TOSCA YAML<br />
** YAML Simple Profile: http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/csprd02/TOSCA-Simple-Profile-YAML-v1.1-csprd02.html<br />
* TOSCA NFV Profile:<br />
** Latest spec is available here: https://www.oasis-open.org/committees/document.php?document_id=56577&wg_abbrev=tosca<br />
** Current latest (as of Oct 2015) is: https://www.oasis-open.org/committees/download.php/56577/tosca-nfv-v1.0-wd02-rev03.doc<br />
<br />
= Tacker + SFC (Service Function Chaining) =<br />
<br />
The proposal to enable SFC for Tacker is captured in these slides,<br />
<br />
https://docs.google.com/presentation/d/18AGaiysVgHOd_fIHVpObMO7zUkMjJGOQ98CUwkxU1xo/edit?usp=sharing<br />
<br />
= Weekly Meetings and Mailing List =<br />
<br />
<br />
'''IRC Channel:''' <code><nowiki>#tacker</nowiki></code><br />
<br />
'''Meetings:''' Tuesday 08:00 UTC [Weekly] @ <code><nowiki>#openstack-meeting</nowiki></code><br />
<br />
'''Tags:''' [NFV] [Tacker]<br /><br />
<br />
= Meeting Minutes =<br />
<br />
http://eavesdrop.openstack.org/meetings/tacker/<br />
<br />
= Repos =<br />
{| class="wikitable"<br />
|-<br />
! colspan="2"| Git <br />
|-<br />
| Tacker || https://opendev.org/openstack/tacker/<br />
|-<br />
| Tacker Specs || https://opendev.org/openstack/tacker-specs/<br />
|-<br />
| Tacker Python Client || https://opendev.org/openstack/python-tackerclient/<br />
|-<br />
| Tacker Horizon || https://opendev.org/openstack/tacker-horizon/<br />
|-<br />
! colspan="2" | Gerrit<br />
|-<br />
| Tacker || https://review.openstack.org/#/q/status:open+project:openstack/tacker,n,z<br />
|-<br />
| Tacker Specs || https://review.openstack.org/#/q/status:open+project:openstack/tacker-specs,n,z<br />
|-<br />
| Tacker Python client || https://review.openstack.org/#/q/status:open+project:openstack/python-tackerclient,n,z<br />
|-<br />
| Tacker Horizon || https://review.openstack.org/#/q/status:open+project:openstack/tacker-horizon,n,z<br />
|-<br />
|}<br />
<br />
= Reviews =<br />
<br />
[https://review.openstack.org/#/q/project:openstack/tacker+OR+project:openstack/python-tackerclient+OR+project:openstack/tacker-horizon+OR+project:openstack/tacker-specs,n,z Tacker Code and Spec Reviews ]<br />
<br />
[https://review.openstack.org/#/q/(project:openstack/tacker+OR+project:openstack/python-tackerclient+OR+project:openstack/tacker-horizon+OR+project:openstack/tacker-specs)+AND+status:open,n,z Tacker Open Code and Spec Reviews]<br />
<br />
= Bugs =<br />
<br />
https://bugs.launchpad.net/tacker<br />
<br />
[https://bugs.launchpad.net/tacker/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search Unassigned Bugs]<br />
= Points of contact =<br />
<br />
* Launchpad project page: https://launchpad.net/tacker<br />
* IRC meeting information: https://wiki.openstack.org/wiki/Meetings/Tacker<br />
* IRC channel on OFTC: <code><nowiki>#tacker</nowiki></code><br />
<br />
= Quick Links =<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| OpenStack Summit Tacker Talks || https://www.openstack.org/videos/search?search=Tacker<br />
|-<br />
| Team || [https://wiki.openstack.org/wiki/Tacker/Incubation#Team_Members Team Members ]<br />
|-<br />
| Tacker API doc || https://developer.openstack.org/api-ref/nfv-orchestration/<br />
|-<br />
| Tacker Client doc || https://docs.openstack.org/ocata/cli-reference/tacker.html<br />
|-<br />
| Tacker Installation || https://wiki.openstack.org/wiki/Tacker/Installation<br />
|- <br />
|}<br />
<br />
= Wiki Pages =<br />
{{Special:PrefixIndex/ServiceVM}}</div>
Ogawa.yasufumi
https://wiki.openstack.org/w/index.php?title=Tacker&diff=178622
Tacker
2021-06-01T04:36:30Z
<p>Ogawa.yasufumi: /* Points of contact */</p>
<hr />
<div>__NOTOC__<br />
<br />
= Tacker - OpenStack NFV Orchestration =<br />
<br />
Tacker is an official OpenStack project building a Generic VNF Manager (VNFM) and an NFV Orchestrator (NFVO) to deploy and operate Network Services and Virtual Network Functions (VNFs) on an NFV infrastructure platform like OpenStack. It is based on ETSI MANO Architectural Framework and provides a functional stack to Orchestrate Network Services end-to-end using VNFs. <br />
<br />
[[File:Tacker_Architecture.png]]<br />
<br />
= High-Level Architecture =<br />
<br />
<br />
== NFV Catalog ==<br />
<br />
# VNF Descriptors <br />
# Network Services Descriptors<br />
# VNF Forwarding Graph Descriptors<br />
<br />
== VNFM ==<br />
<br />
# Basic life-cycle of VNF (create/update/delete)<br />
# Enhanced platform-aware (EPA) placement of high-performance NFV workloads <br />
# Health monitoring of deployed VNFs<br />
# Auto Healing / Auto Scaling VNFs based on Policy<br />
# Facilitate initial configuration of VNF<br />
<br />
== NFVO ==<br />
<br />
# Templatized end-to-end Network Service deployment using decomposed VNFs<br />
# VNF placement policy – ensure efficient placement of VNFs <br />
# VNFs connected using an SFC - described in a VNF Forwarding Graph Descriptor<br />
# VIM Resource Checks and Resource Allocation<br />
# Ability to orchestrate VNFs across Multiple VIMs and Multiple Sites (POPs)<br />
<br />
<br />
= Documentation =<br />
<br />
https://docs.openstack.org/tacker/<br />
<br />
== Install Guide ==<br />
<br />
https://docs.openstack.org/tacker/latest/install/index.html<br />
<br />
= Use Cases =<br />
<br />
=== vCE ===<br />
<br />
Tacker API can be used by SP's OSS / BSS or an NFV Orchestrator to deploy VNFs in SP's network to deliver agile network services for remote Customer networks<br />
<br />
=== vCPE ===<br />
<br />
Tacker API can be used by SP's OSS / BSS or an NFV Orchestrator to manage OpenStack enabled remote CPE devices to deploy VNFs to provide locally network services at the customer site.<br />
<br />
=== vPE ===<br />
<br />
Tacker API can be used by SP's OSS / BSS or an NFV Orchestrator to deploy VNFs within SP's network to virtualize existing network services into a Virtual Function.<br />
<br />
=== Telecom operator's expectations ===<br />
[[Tacker/UseCase|What Tacker solves ?]]<br />
<br />
= ETSI NFV SPECS =<br />
[http://www.etsi.org/standards-search#page=1&search=&title=1&etsiNumber=1&content=0&version=0&onApproval=1&published=1&historical=0&startDate=1988-01-15&endDate=2017-02-03&harmonized=0&keyword=&TB=789,,832,,831,,795,,796,,800,,798,,799,,797&stdType=&frequency=&mandate=&sort=1 ETSI NFV SPECS]<br />
<br />
= TOSCA for NFV =<br />
<br />
Tacker uses TOSCA for VNF meta-data definition. Within TOSCA Tacker used NFV profile schema.<br />
* TOSCA YAML<br />
** YAML Simple Profile: http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/csprd02/TOSCA-Simple-Profile-YAML-v1.1-csprd02.html<br />
* TOSCA NFV Profile:<br />
** Latest spec is available here: https://www.oasis-open.org/committees/document.php?document_id=56577&wg_abbrev=tosca<br />
** Current latest (as of Oct 2015) is: https://www.oasis-open.org/committees/download.php/56577/tosca-nfv-v1.0-wd02-rev03.doc<br />
<br />
= Tacker + SFC (Service Function Chaining) =<br />
<br />
The proposal to enable SFC for Tacker is captured in these slides,<br />
<br />
https://docs.google.com/presentation/d/18AGaiysVgHOd_fIHVpObMO7zUkMjJGOQ98CUwkxU1xo/edit?usp=sharing<br />
<br />
= Weekly Meetings and Mailing List =<br />
<br />
<br />
'''IRC Channel:''' <code><nowiki>#tacker</nowiki></code><br />
<br />
'''Meetings:''' Tuesday 08:00 UTC [Weekly] @ <code><nowiki>#openstack-meeting</nowiki></code><br />
<br />
'''Tags:''' [NFV] [Tacker]<br /><br />
<br />
= Meeting Minutes =<br />
<br />
http://eavesdrop.openstack.org/meetings/tacker/<br />
<br />
= Repos =<br />
{| class="wikitable"<br />
|-<br />
! colspan="2"| Git <br />
|-<br />
| Tacker || https://git.openstack.org/cgit/openstack/tacker/<br />
|-<br />
| Tacker Specs || https://git.openstack.org/cgit/openstack/tacker-specs/<br />
|-<br />
| Tacker Python Client || https://git.openstack.org/cgit/openstack/python-tackerclient/<br />
|-<br />
| Tacker Horizon || https://git.openstack.org/cgit/openstack/tacker-horizon/<br />
|-<br />
! colspan="2" | Gerrit<br />
|-<br />
| Tacker || https://review.openstack.org/#/q/status:open+project:openstack/tacker,n,z<br />
|-<br />
| Tacker Specs || https://review.openstack.org/#/q/status:open+project:openstack/tacker-specs,n,z<br />
|-<br />
| Tacker Python client || https://review.openstack.org/#/q/status:open+project:openstack/python-tackerclient,n,z<br />
|-<br />
| Tacker Horizon || https://review.openstack.org/#/q/status:open+project:openstack/tacker-horizon,n,z<br />
|-<br />
|}<br />
<br />
= Reviews =<br />
<br />
[https://review.openstack.org/#/q/project:openstack/tacker+OR+project:openstack/python-tackerclient+OR+project:openstack/tacker-horizon+OR+project:openstack/tacker-specs,n,z Tacker Code and Spec Reviews ]<br />
<br />
[https://review.openstack.org/#/q/(project:openstack/tacker+OR+project:openstack/python-tackerclient+OR+project:openstack/tacker-horizon+OR+project:openstack/tacker-specs)+AND+status:open,n,z Tacker Open Code and Spec Reviews]<br />
<br />
= Bugs =<br />
<br />
https://bugs.launchpad.net/tacker<br />
<br />
[https://bugs.launchpad.net/tacker/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search Unassigned Bugs]<br />
= Points of contact =<br />
<br />
* Launchpad project page: https://launchpad.net/tacker<br />
* IRC meeting information: https://wiki.openstack.org/wiki/Meetings/Tacker<br />
* IRC channel on OFTC: <code><nowiki>#tacker</nowiki></code><br />
<br />
= Quick Links =<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| OpenStack Summit Tacker Talks || https://www.openstack.org/videos/search?search=Tacker<br />
|-<br />
| Team || [https://wiki.openstack.org/wiki/Tacker/Incubation#Team_Members Team Members ]<br />
|-<br />
| Tacker API doc || https://developer.openstack.org/api-ref/nfv-orchestration/<br />
|-<br />
| Tacker Client doc || https://docs.openstack.org/ocata/cli-reference/tacker.html<br />
|-<br />
| Tacker Installation || https://wiki.openstack.org/wiki/Tacker/Installation<br />
|- <br />
|}<br />
<br />
= Wiki Pages =<br />
{{Special:PrefixIndex/ServiceVM}}</div>
Ogawa.yasufumi
https://wiki.openstack.org/w/index.php?title=Tacker&diff=175659
Tacker
2020-07-20T06:44:59Z
<p>Ogawa.yasufumi: /* Install Guide */</p>
<hr />
<div>__NOTOC__<br />
<br />
= Tacker - OpenStack NFV Orchestration =<br />
<br />
Tacker is an official OpenStack project building a Generic VNF Manager (VNFM) and an NFV Orchestrator (NFVO) to deploy and operate Network Services and Virtual Network Functions (VNFs) on an NFV infrastructure platform like OpenStack. It is based on ETSI MANO Architectural Framework and provides a functional stack to Orchestrate Network Services end-to-end using VNFs. <br />
<br />
[[File:Tacker_Architecture.png]]<br />
<br />
= High-Level Architecture =<br />
<br />
<br />
== NFV Catalog ==<br />
<br />
# VNF Descriptors <br />
# Network Services Descriptors<br />
# VNF Forwarding Graph Descriptors<br />
<br />
== VNFM ==<br />
<br />
# Basic life-cycle of VNF (create/update/delete)<br />
# Enhanced platform-aware (EPA) placement of high-performance NFV workloads <br />
# Health monitoring of deployed VNFs<br />
# Auto Healing / Auto Scaling VNFs based on Policy<br />
# Facilitate initial configuration of VNF<br />
<br />
== NFVO ==<br />
<br />
# Templatized end-to-end Network Service deployment using decomposed VNFs<br />
# VNF placement policy – ensure efficient placement of VNFs <br />
# VNFs connected using an SFC - described in a VNF Forwarding Graph Descriptor<br />
# VIM Resource Checks and Resource Allocation<br />
# Ability to orchestrate VNFs across Multiple VIMs and Multiple Sites (POPs)<br />
<br />
<br />
= Documentation =<br />
<br />
https://docs.openstack.org/tacker/<br />
<br />
== Install Guide ==<br />
<br />
https://docs.openstack.org/tacker/latest/install/index.html<br />
<br />
= Use Cases =<br />
<br />
=== vCE ===<br />
<br />
Tacker API can be used by SP's OSS / BSS or an NFV Orchestrator to deploy VNFs in SP's network to deliver agile network services for remote Customer networks<br />
<br />
=== vCPE ===<br />
<br />
Tacker API can be used by SP's OSS / BSS or an NFV Orchestrator to manage OpenStack enabled remote CPE devices to deploy VNFs to provide locally network services at the customer site.<br />
<br />
=== vPE ===<br />
<br />
Tacker API can be used by SP's OSS / BSS or an NFV Orchestrator to deploy VNFs within SP's network to virtualize existing network services into a Virtual Function.<br />
<br />
=== Telecom operator's expectations ===<br />
[[Tacker/UseCase|What Tacker solves ?]]<br />
<br />
= ETSI NFV SPECS =<br />
[http://www.etsi.org/standards-search#page=1&search=&title=1&etsiNumber=1&content=0&version=0&onApproval=1&published=1&historical=0&startDate=1988-01-15&endDate=2017-02-03&harmonized=0&keyword=&TB=789,,832,,831,,795,,796,,800,,798,,799,,797&stdType=&frequency=&mandate=&sort=1 ETSI NFV SPECS]<br />
<br />
= TOSCA for NFV =<br />
<br />
Tacker uses TOSCA for VNF meta-data definition. Within TOSCA Tacker used NFV profile schema.<br />
* TOSCA YAML<br />
** YAML Simple Profile: http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/csprd02/TOSCA-Simple-Profile-YAML-v1.1-csprd02.html<br />
* TOSCA NFV Profile:<br />
** Latest spec is available here: https://www.oasis-open.org/committees/document.php?document_id=56577&wg_abbrev=tosca<br />
** Current latest (as of Oct 2015) is: https://www.oasis-open.org/committees/download.php/56577/tosca-nfv-v1.0-wd02-rev03.doc<br />
<br />
= Tacker + SFC (Service Function Chaining) =<br />
<br />
The proposal to enable SFC for Tacker is captured in these slides,<br />
<br />
https://docs.google.com/presentation/d/18AGaiysVgHOd_fIHVpObMO7zUkMjJGOQ98CUwkxU1xo/edit?usp=sharing<br />
<br />
= Weekly Meetings and Mailing List =<br />
<br />
<br />
'''IRC Channel:''' <code><nowiki>#tacker</nowiki></code><br />
<br />
'''Meetings:''' Tuesday 08:00 UTC [Weekly] @ <code><nowiki>#openstack-meeting</nowiki></code><br />
<br />
'''Tags:''' [NFV] [Tacker]<br /><br />
<br />
= Meeting Minutes =<br />
<br />
http://eavesdrop.openstack.org/meetings/tacker/<br />
<br />
= Repos =<br />
{| class="wikitable"<br />
|-<br />
! colspan="2"| Git <br />
|-<br />
| Tacker || https://git.openstack.org/cgit/openstack/tacker/<br />
|-<br />
| Tacker Specs || https://git.openstack.org/cgit/openstack/tacker-specs/<br />
|-<br />
| Tacker Python Client || https://git.openstack.org/cgit/openstack/python-tackerclient/<br />
|-<br />
| Tacker Horizon || https://git.openstack.org/cgit/openstack/tacker-horizon/<br />
|-<br />
! colspan="2" | Gerrit<br />
|-<br />
| Tacker || https://review.openstack.org/#/q/status:open+project:openstack/tacker,n,z<br />
|-<br />
| Tacker Specs || https://review.openstack.org/#/q/status:open+project:openstack/tacker-specs,n,z<br />
|-<br />
| Tacker Python client || https://review.openstack.org/#/q/status:open+project:openstack/python-tackerclient,n,z<br />
|-<br />
| Tacker Horizon || https://review.openstack.org/#/q/status:open+project:openstack/tacker-horizon,n,z<br />
|-<br />
|}<br />
<br />
= Reviews =<br />
<br />
[https://review.openstack.org/#/q/project:openstack/tacker+OR+project:openstack/python-tackerclient+OR+project:openstack/tacker-horizon+OR+project:openstack/tacker-specs,n,z Tacker Code and Spec Reviews ]<br />
<br />
[https://review.openstack.org/#/q/(project:openstack/tacker+OR+project:openstack/python-tackerclient+OR+project:openstack/tacker-horizon+OR+project:openstack/tacker-specs)+AND+status:open,n,z Tacker Open Code and Spec Reviews]<br />
<br />
= Bugs =<br />
<br />
https://bugs.launchpad.net/tacker<br />
<br />
[https://bugs.launchpad.net/tacker/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search Unassigned Bugs]<br />
= Points of contact =<br />
<br />
* Launchpad project page: https://launchpad.net/tacker<br />
* IRC meeting information: https://wiki.openstack.org/wiki/Meetings/Tacker<br />
* IRC channel on Freenode: <code><nowiki>#tacker</nowiki></code><br />
<br />
<br />
= Quick Links =<br />
<br />
{| class="wikitable"<br />
<br />
|-<br />
| OpenStack Summit Tacker Talks || https://www.openstack.org/videos/search?search=Tacker<br />
|-<br />
| Team || [https://wiki.openstack.org/wiki/Tacker/Incubation#Team_Members Team Members ]<br />
|-<br />
| Tacker API doc || https://developer.openstack.org/api-ref/nfv-orchestration/<br />
|-<br />
| Tacker Client doc || https://docs.openstack.org/ocata/cli-reference/tacker.html<br />
|-<br />
| Tacker Installation || https://wiki.openstack.org/wiki/Tacker/Installation<br />
|- <br />
|}<br />
<br />
= Wiki Pages =<br />
{{Special:PrefixIndex/ServiceVM}}</div>
Ogawa.yasufumi
https://wiki.openstack.org/w/index.php?title=Tacker/Incubation&diff=175467
Tacker/Incubation
2020-06-30T08:42:00Z
<p>Ogawa.yasufumi: /* Team Members */</p>
<hr />
<div>'''This page is Draft under review'''<br />
<br />
== Project codename ==<br />
Tacker<br />
<br />
== Trademarks ==<br />
(Does this project name, codename or contents use any trademarks, and if so, who owns them? List the codenames or other marks for which a trademark search should occur.)<br />
<br />
No known trademarks.<br />
<br />
<br />
== Summary ==<br />
Tacker is an OpenStack service for NFV Orchestration with a general purpose VNF Manager to deploy and operate Virtual Network Functions (VNFs) and Network Services on an NFV Platform. It is based on ETSI MANO Architectural Framework.<br />
<br />
== Parent Program name and PTL ==<br />
Neutron networking/Kyle Mestery<br />
<br />
<br />
== Mission statement ==<br />
Provide common framework/groundwork for lifecycle management of<br />
VNFs and virtual/physical services which conforms ETSI NFV.<br />
<br />
<br />
=== Mission ===<br />
Establish/encourage ecosystem of virtual/physical appliance on<br />
OpenStack.<br />
To make it easy for appliance providers to integrate their<br />
appliances (services implemented in virtual machines/container-based VNFs or physical hardware) with OpenStack by<br />
providing a unified interface for lifecycle management of<br />
VNFs which is capable of multiple service/vendor.<br />
<br />
== Detailed Description ==<br />
(Background: this project is spin-out project from Neutron)<br />
<br />
It is a quite common requirement to run services in virtual<br />
machines aka ServiceVM. So far each OpenStack<br />
service(Especially Neutron case) implemented their own life<br />
cycle management of ServiceVMs/services and<br />
hardware. Preparing/pooling/scheduling VMs/services and so on.<br />
It resulted in duplicated work and rises the bar for appliance<br />
provide to integrate appliances with OpenStack.<br />
<br />
This project introduces a new service for managing<br />
servicevm/device. Its responsibility is to:<br />
# manage VMs/devices/services<br />
# control the allocation of processing capacity in such devices As such the servicevm/device manager mainly serves other projects. Another natural responsibility of this service would be to keep track of and store the physical topology that the devices are part of.<br />
# pluggable for each VMs/physical devices/services<br />
<br />
<br />
As ETSI NFV is an important use case, NFV conformance is in the scope of this project.<br />
This project services as some components of NFV MANO architecture.<br />
http://www.ietf.org/proceedings/89/slides/slides-89-opsawg-7.pdf<br />
<br />
* corresponding component:<br />
** VNFM(VNF Manager)<br />
<br />
* corresponding interfaces:<br />
** VNF lifecycle management interface<br />
** VNF lifecycle changes notifications interface<br />
** VNF configuration interface<br />
<br />
<br />
The relationship of NFV team and this project:<br />
<br />
This project serves as (sub)component(s) necessary for NFV in openstack. The team will cooperate with NFV team.<br />
<br />
* links to NFV team<br />
** https://wiki.openstack.org/wiki/Meetings/NFV<br />
** https://etherpad.openstack.org/p/juno-nfv-bof<br />
<br />
== Basic roadmap for the project ==<br />
from Near term to middle term<br />
(Note: Addressing missing features for Neutron/Nova: some features are missing in Neutron/Nova. Those features can be addressed independently of this project.)<br />
Design/patch review process will follow Neutron style as this project spun out of Neutron.<br />
<br />
* terminology conversion. including NFV conformance/nomenclature<br />
* produce a minimul working code as an independent service(out of Neutron. So far there were two implementations within Neutron). merge floating around multiple implementations.<br />
* design review process: gerrit, wiki, google-doc<br />
* API/data model design<br />
* Actual coding(server, python client)<br />
* establish testing<br />
* Corporate with Neutron driver for Network service in VM (e.g. router vm, firewall vm) that interacts with Tacker<br />
* make use of currently missing Neutron feature like service insertion<br />
At first temporal shim code will be needed in Neutron for service<br />
insertion, traffic steering and so on. At this moment those features<br />
are under development. Once such features are stabilized and <br />
public RestAPI is provided, convert the implmentation to use RestAPI<br />
and remove the temporal shim code.<br />
* consider generic VM/service scheduling<br />
<br />
== Location of project source code ==<br />
Tacker: http://git.openstack.org/cgit/openstack/tacker/<br />
Tacker Specs: http://specs.openstack.org/openstack/tacker-specs/<br />
Tacker Python Client: http://git.openstack.org/cgit/openstack/python-tackerclient/<br />
<br />
== Programming language, and required technology dependencies ==<br />
Language: Python.<br />
Dependencies: alembic, eventlet, sqlalchemy, pbr, pecan, jsonschema, ...<br />
<br />
== Is project currently open sourced? What license? ==<br />
Yes and Apache 2.0<br />
<br />
== Level of maturity of software and team ==<br />
=== Software ===<br />
TODO(to be written)<br />
<br />
= Team =<br />
The team has worked for more than 3 months as Neutron subteam.<br />
It as independent project out of Neutron started to work since<br />
May 2014.<br />
From three(XXX) differenct companies(Cisco, Midokura, Intel. XXX)<br />
<br />
== Team Members ==<br />
<br />
<tt style="color: blue"> We are growing! Add your name and details here if you are planning to contribute or simply be kept in the loop :) </tt><br />
=== Bob Melander ===<br />
Status : Core Developer <br/><br />
IRC handle: bmelande<br/><br />
Email: bob.melander@gmail.com<br/><br />
Affiliation: Cisco<br />
<br />
=== Stephen Wong ===<br />
Status : Core Developer<br/><br />
IRC handle: s3wong<br/><br />
Email: <br/><br />
Affiliation: - <br />
<br />
=== Hareesh Puthalath ===<br />
Status : Developer<br/><br />
IRC handle: hareeshp<br/><br />
Email: hareesh.puthalath@gmail.com<br/><br />
Affiliation: Cisco<br />
<br />
<br />
=== Sridar Kandaswamy ===<br />
Status : Developer<br/><br />
IRC handle: SridarK<br/><br />
Email: skandasw@cisco.com<br/><br />
Affiliation: Cisco<br />
<br />
===Yong sheng gong ===<br />
Status : Core Developer<br/><br />
IRC handle: gongysh<br/><br />
Email: gong_ys2004@aliyun.com <br/><br />
Affiliation: 99cloud<br />
<br />
=== Karthik Natarajan ===<br />
Status : Developer<br/><br />
IRC handle: natarajk<br/><br />
Email: <br/><br />
Affiliation: Brocade<br />
<br />
=== Kyle Mestery ===<br />
Status : Developer<br/><br />
IRC handle: mestery<br/><br />
Email: <br/><br />
Affiliation: HP<br />
<br />
=== Balaji Padnala ===<br />
Status : Developer<br/><br />
IRC handle: balajip<br/><br />
Email: <br/><br />
Affiliation: FreeScale<br />
<br />
===Sridhar Ramaswamy ===<br />
Status : Developer<br/><br />
IRC handle: SridharRamaswamy<br/><br />
Email: <br/><br />
Affiliation: Brocade<br />
<br />
===Sripriya Seetharam ===<br />
Status : Developer<br/><br />
IRC handle: sripriya<br/><br />
Email: <br/><br />
Affiliation: Brocade<br />
<br />
===Vishwanath Jayaraman ===<br />
Status : Developer<br/><br />
IRC handle: vishwanathj<br/><br />
Email: vishwanathj@hotmail.com<br/><br />
Affiliation: Brocade<br />
<br />
===Vikash Kumar===<br />
Status: Developer<br/><br />
IRC handle: vks<br/><br />
Email: vikash.kumar@oneconvergence.com<br />
<br />
===Prakash Ramchandran===<br />
Status : Core Developer <br/><br />
IRC handle: rprakash<br/><br />
Email: pramchan@yahoo.com<br/><br />
Affiliation: Futurewei Inc.<br />
<br />
===Bob Haddleton===<br />
Status: Developer<br/><br />
IRC handle: bobh<br/><br />
Email: bob.haddleton@alcatel-lucent.com<br/><br />
Affiliation: Alcatel-Lucent<br />
<br />
===Ahmed El-Khouly===<br />
Status: Developer<br/><br />
IRC handle: ahelkhou<br/><br />
Email: Ahmed.h.elkhouly@gmail.com<br/><br />
Affiliation: Nokia<br />
<br />
===Ashok Pachaiappan===<br />
Status: Comcast Lead<br/><br />
IRC handle: apachia<br/><br />
Email: ashok_pachaiappan@cable.comcast.com<br/><br />
Affiliation: Comcast<br />
<br />
===Rajkumar Kuppuraj===<br />
Status: Developer<br/><br />
IRC handle: rajkumar_kuppuraj<br/><br />
Email: Rajkumar_Kuppuraj@cable.comcast.com<br/><br />
Affiliation: Comcast<br />
<br />
===Shrinath Suresh===<br />
Status: Developer<br/><br />
IRC handle: Shrinath_Suresh<br/><br />
Email: Shrinath_Suresh@cable.comcast.com<br/><br />
Affiliation: Comcast<br />
<br />
===Bharath Thiruveedula===<br />
Status: Developer<br/><br />
IRC handle: tbh<br/><br />
Email: bharath_ves@hotmail.com<br/><br />
Affiliation:<br />
<br />
===Denis Makogon===<br />
Status: Developer<br/><br />
IRC handle: denismakogon<br/><br />
Email: lildee1991@gmail.com<br/><br />
<br />
===Martin Oemke===<br />
Status : Developer<br/><br />
IRC handle: zeih<br/><br />
Email: zeih@zeih.eu<br/><br />
Affiliation: Deutsche Telekom<br />
<br />
===Ravi Chunduru===<br />
Status: Developer<br/><br />
IRC handle: rsun<br/><br />
Email: ravivsn@gmail.com<br/><br />
Affiliation: ClearPath Networks<br />
<br />
===Steve Wilkerson===<br />
Status: Developer<br/><br />
IRC handle: srwilkers<br/><br />
Email: wilkers.steve@gmail.com<br/><br />
Affiliation: AT&T<br />
<br />
===Manikantha Srinivas Tadi===<br />
Status: Developer<br/><br />
IRC handle: manikanta_tadi<br/><br />
Email: manikantha.tadi@gmail.com<br/><br />
Affiliation:<br />
<br />
=== Dharmendra Kushwaha ===<br />
Status : Developer <br/><br />
IRC handle: dkhuswaha<br/><br />
Email: dharmendra.kushwaha@nectechnologies.in<br/><br />
Affiliation: NEC<br />
<br />
=== VenkataMahesh Kotha ===<br />
Status : Developer <br/><br />
IRC handle: kvmahesh<br/><br />
Email: Venkata.Kotha@infinite.com<br/><br />
Affiliation: Infinite<br />
<br />
=== Janki Chhatbar ===<br />
Status : Developer <br/><br />
IRC handle: janki<br/><br />
Email: jankihchhatbar@gmail.com<br/><br />
Affiliation: RedHat<br />
<br />
=== Tung Doan ===<br />
Status : Developer <br/><br />
IRC handle: tung_doan<br/><br />
Email: doantungbk.203@gmail.com<br/><br />
Affiliation: K-ONE<br />
<br />
=== Nguyen Hai ===<br />
Status : Developer <br/><br />
IRC handle: nguyenhai<br/><br />
Email: nguyentrihai93@gmail.com<br/><br />
Affiliation: Soongsil University<br />
<br />
=== Trinh Nguyen ===<br />
Status : Developer <br/><br />
IRC handle: dangtrinhnt<br/><br />
Email: dangtrinhnt@gmail.com<br/><br />
<br />
=== Abdel Rabi ===<br />
Status : NFV & SDN Architect<br/><br />
Email: abdel.rabi@vodafone.com<br/><br />
Affiliation: Vodafone Group<br />
<br />
=== Yasufumi Ogawa ===<br />
Status : Core Developer<br/><br />
IRC handle: yasufum<br/><br />
Email: yasufum.o@gmail.com<br/><br />
Affiliation: NTT<br />
<br />
=== Hyunsik Yang ===<br />
Status : Developer<br/><br />
IRC handle: hyunsikyang<br/><br />
Email: yangun@dcn.ssu.ac.kr<br/><br />
Affiliation: IISTRC<br />
<br />
== Infrastructure requirements (testing, etc) ==<br />
No additional requirements to the current OpenStack Infrastructure<br />
<br />
== Have all current contributors agreed to the OpenStack CLA? ==<br />
Yes</div>
Ogawa.yasufumi
https://wiki.openstack.org/w/index.php?title=Tacker/Incubation&diff=174903
Tacker/Incubation
2020-05-20T17:01:54Z
<p>Ogawa.yasufumi: /* Team Members */ Add yasufum</p>
<hr />
<div>'''This page is Draft under review'''<br />
<br />
== Project codename ==<br />
Tacker<br />
<br />
== Trademarks ==<br />
(Does this project name, codename or contents use any trademarks, and if so, who owns them? List the codenames or other marks for which a trademark search should occur.)<br />
<br />
No known trademarks.<br />
<br />
<br />
== Summary ==<br />
Tacker is an OpenStack service for NFV Orchestration with a general purpose VNF Manager to deploy and operate Virtual Network Functions (VNFs) and Network Services on an NFV Platform. It is based on ETSI MANO Architectural Framework.<br />
<br />
== Parent Program name and PTL ==<br />
Neutron networking/Kyle Mestery<br />
<br />
<br />
== Mission statement ==<br />
Provide common framework/groundwork for lifecycle management of<br />
VNFs and virtual/physical services which conforms ETSI NFV.<br />
<br />
<br />
=== Mission ===<br />
Establish/encourage ecosystem of virtual/physical appliance on<br />
OpenStack.<br />
To make it easy for appliance providers to integrate their<br />
appliances (services implemented in virtual machines/container-based VNFs or physical hardware) with OpenStack by<br />
providing a unified interface for lifecycle management of<br />
VNFs which is capable of multiple service/vendor.<br />
<br />
== Detailed Description ==<br />
(Background: this project is spin-out project from Neutron)<br />
<br />
It is a quite common requirement to run services in virtual<br />
machines aka ServiceVM. So far each OpenStack<br />
service(Especially Neutron case) implemented their own life<br />
cycle management of ServiceVMs/services and<br />
hardware. Preparing/pooling/scheduling VMs/services and so on.<br />
It resulted in duplicated work and rises the bar for appliance<br />
provide to integrate appliances with OpenStack.<br />
<br />
This project introduces a new service for managing<br />
servicevm/device. Its responsibility is to:<br />
# manage VMs/devices/services<br />
# control the allocation of processing capacity in such devices As such the servicevm/device manager mainly serves other projects. Another natural responsibility of this service would be to keep track of and store the physical topology that the devices are part of.<br />
# pluggable for each VMs/physical devices/services<br />
<br />
<br />
As ETSI NFV is an important use case, NFV conformance is in the scope of this project.<br />
This project services as some components of NFV MANO architecture.<br />
http://www.ietf.org/proceedings/89/slides/slides-89-opsawg-7.pdf<br />
<br />
* corresponding component:<br />
** VNFM(VNF Manager)<br />
<br />
* corresponding interfaces:<br />
** VNF lifecycle management interface<br />
** VNF lifecycle changes notifications interface<br />
** VNF configuration interface<br />
<br />
<br />
The relationship of NFV team and this project:<br />
<br />
This project serves as (sub)component(s) necessary for NFV in openstack. The team will cooperate with NFV team.<br />
<br />
* links to NFV team<br />
** https://wiki.openstack.org/wiki/Meetings/NFV<br />
** https://etherpad.openstack.org/p/juno-nfv-bof<br />
<br />
== Basic roadmap for the project ==<br />
from Near term to middle term<br />
(Note: Addressing missing features for Neutron/Nova: some features are missing in Neutron/Nova. Those features can be addressed independently of this project.)<br />
Design/patch review process will follow Neutron style as this project spun out of Neutron.<br />
<br />
* terminology conversion. including NFV conformance/nomenclature<br />
* produce a minimul working code as an independent service(out of Neutron. So far there were two implementations within Neutron). merge floating around multiple implementations.<br />
* design review process: gerrit, wiki, google-doc<br />
* API/data model design<br />
* Actual coding(server, python client)<br />
* establish testing<br />
* Corporate with Neutron driver for Network service in VM (e.g. router vm, firewall vm) that interacts with Tacker<br />
* make use of currently missing Neutron feature like service insertion<br />
At first temporal shim code will be needed in Neutron for service<br />
insertion, traffic steering and so on. At this moment those features<br />
are under development. Once such features are stabilized and <br />
public RestAPI is provided, convert the implmentation to use RestAPI<br />
and remove the temporal shim code.<br />
* consider generic VM/service scheduling<br />
<br />
== Location of project source code ==<br />
Tacker: http://git.openstack.org/cgit/openstack/tacker/<br />
Tacker Specs: http://specs.openstack.org/openstack/tacker-specs/<br />
Tacker Python Client: http://git.openstack.org/cgit/openstack/python-tackerclient/<br />
<br />
== Programming language, and required technology dependencies ==<br />
Language: Python.<br />
Dependencies: alembic, eventlet, sqlalchemy, pbr, pecan, jsonschema, ...<br />
<br />
== Is project currently open sourced? What license? ==<br />
Yes and Apache 2.0<br />
<br />
== Level of maturity of software and team ==<br />
=== Software ===<br />
TODO(to be written)<br />
<br />
= Team =<br />
The team has worked for more than 3 months as Neutron subteam.<br />
It as independent project out of Neutron started to work since<br />
May 2014.<br />
From three(XXX) differenct companies(Cisco, Midokura, Intel. XXX)<br />
<br />
== Team Members ==<br />
<br />
<tt style="color: blue"> We are growing! Add your name and details here if you are planning to contribute or simply be kept in the loop :) </tt><br />
=== Bob Melander ===<br />
Status : Core Developer <br/><br />
IRC handle: bmelande<br/><br />
Email: bob.melander@gmail.com<br/><br />
Affiliation: Cisco<br />
<br />
=== Stephen Wong ===<br />
Status : Core Developer<br/><br />
IRC handle: s3wong<br/><br />
Email: <br/><br />
Affiliation: - <br />
<br />
=== Hareesh Puthalath ===<br />
Status : Developer<br/><br />
IRC handle: hareeshp<br/><br />
Email: hareesh.puthalath@gmail.com<br/><br />
Affiliation: Cisco<br />
<br />
<br />
=== Sridar Kandaswamy ===<br />
Status : Developer<br/><br />
IRC handle: SridarK<br/><br />
Email: skandasw@cisco.com<br/><br />
Affiliation: Cisco<br />
<br />
===Yong sheng gong ===<br />
Status : Core Developer<br/><br />
IRC handle: gongysh<br/><br />
Email: gong_ys2004@aliyun.com <br/><br />
Affiliation: 99cloud<br />
<br />
=== Karthik Natarajan ===<br />
Status : Developer<br/><br />
IRC handle: natarajk<br/><br />
Email: <br/><br />
Affiliation: Brocade<br />
<br />
=== Kyle Mestery ===<br />
Status : Developer<br/><br />
IRC handle: mestery<br/><br />
Email: <br/><br />
Affiliation: HP<br />
<br />
=== Balaji Padnala ===<br />
Status : Developer<br/><br />
IRC handle: balajip<br/><br />
Email: <br/><br />
Affiliation: FreeScale<br />
<br />
===Sridhar Ramaswamy ===<br />
Status : Developer<br/><br />
IRC handle: SridharRamaswamy<br/><br />
Email: <br/><br />
Affiliation: Brocade<br />
<br />
===Sripriya Seetharam ===<br />
Status : Developer<br/><br />
IRC handle: sripriya<br/><br />
Email: <br/><br />
Affiliation: Brocade<br />
<br />
===Vishwanath Jayaraman ===<br />
Status : Developer<br/><br />
IRC handle: vishwanathj<br/><br />
Email: vishwanathj@hotmail.com<br/><br />
Affiliation: Brocade<br />
<br />
===Vikash Kumar===<br />
Status: Developer<br/><br />
IRC handle: vks<br/><br />
Email: vikash.kumar@oneconvergence.com<br />
<br />
===Prakash Ramchandran===<br />
Status : Core Developer <br/><br />
IRC handle: rprakash<br/><br />
Email: pramchan@yahoo.com<br/><br />
Affiliation: Futurewei Inc.<br />
<br />
===Bob Haddleton===<br />
Status: Developer<br/><br />
IRC handle: bobh<br/><br />
Email: bob.haddleton@alcatel-lucent.com<br/><br />
Affiliation: Alcatel-Lucent<br />
<br />
===Ahmed El-Khouly===<br />
Status: Developer<br/><br />
IRC handle: ahelkhou<br/><br />
Email: Ahmed.h.elkhouly@gmail.com<br/><br />
Affiliation: Nokia<br />
<br />
===Ashok Pachaiappan===<br />
Status: Comcast Lead<br/><br />
IRC handle: apachia<br/><br />
Email: ashok_pachaiappan@cable.comcast.com<br/><br />
Affiliation: Comcast<br />
<br />
===Rajkumar Kuppuraj===<br />
Status: Developer<br/><br />
IRC handle: rajkumar_kuppuraj<br/><br />
Email: Rajkumar_Kuppuraj@cable.comcast.com<br/><br />
Affiliation: Comcast<br />
<br />
===Shrinath Suresh===<br />
Status: Developer<br/><br />
IRC handle: Shrinath_Suresh<br/><br />
Email: Shrinath_Suresh@cable.comcast.com<br/><br />
Affiliation: Comcast<br />
<br />
===Bharath Thiruveedula===<br />
Status: Developer<br/><br />
IRC handle: tbh<br/><br />
Email: bharath_ves@hotmail.com<br/><br />
Affiliation:<br />
<br />
===Denis Makogon===<br />
Status: Developer<br/><br />
IRC handle: denismakogon<br/><br />
Email: lildee1991@gmail.com<br/><br />
<br />
===Martin Oemke===<br />
Status : Developer<br/><br />
IRC handle: zeih<br/><br />
Email: zeih@zeih.eu<br/><br />
Affiliation: Deutsche Telekom<br />
<br />
===Ravi Chunduru===<br />
Status: Developer<br/><br />
IRC handle: rsun<br/><br />
Email: ravivsn@gmail.com<br/><br />
Affiliation: ClearPath Networks<br />
<br />
===Steve Wilkerson===<br />
Status: Developer<br/><br />
IRC handle: srwilkers<br/><br />
Email: wilkers.steve@gmail.com<br/><br />
Affiliation: AT&T<br />
<br />
===Manikantha Srinivas Tadi===<br />
Status: Developer<br/><br />
IRC handle: manikanta_tadi<br/><br />
Email: manikantha.tadi@gmail.com<br/><br />
Affiliation:<br />
<br />
=== Dharmendra Kushwaha ===<br />
Status : Developer <br/><br />
IRC handle: dkhuswaha<br/><br />
Email: dharmendra.kushwaha@nectechnologies.in<br/><br />
Affiliation: NEC<br />
<br />
=== VenkataMahesh Kotha ===<br />
Status : Developer <br/><br />
IRC handle: kvmahesh<br/><br />
Email: Venkata.Kotha@infinite.com<br/><br />
Affiliation: Infinite<br />
<br />
=== Janki Chhatbar ===<br />
Status : Developer <br/><br />
IRC handle: janki<br/><br />
Email: jankihchhatbar@gmail.com<br/><br />
Affiliation: RedHat<br />
<br />
=== Tung Doan ===<br />
Status : Developer <br/><br />
IRC handle: tung_doan<br/><br />
Email: doantungbk.203@gmail.com<br/><br />
Affiliation: K-ONE<br />
<br />
=== Nguyen Hai ===<br />
Status : Developer <br/><br />
IRC handle: nguyenhai<br/><br />
Email: nguyentrihai93@gmail.com<br/><br />
Affiliation: Soongsil University<br />
<br />
=== Trinh Nguyen ===<br />
Status : Developer <br/><br />
IRC handle: dangtrinhnt<br/><br />
Email: dangtrinhnt@gmail.com<br/><br />
<br />
=== Abdel Rabi ===<br />
Status : NFV & SDN Architect<br/><br />
Email: abdel.rabi@vodafone.com<br/><br />
Affiliation: Vodafone Group<br />
<br />
=== Yasufumi Ogawa ===<br />
Status : Core Developer<br/><br />
IRC handle: yasufum<br/><br />
Email: yasufum.o@gmail.com<br/><br />
Affiliation: NTT<br />
<br />
== Infrastructure requirements (testing, etc) ==<br />
No additional requirements to the current OpenStack Infrastructure<br />
<br />
== Have all current contributors agreed to the OpenStack CLA? ==<br />
Yes</div>
Ogawa.yasufumi
https://wiki.openstack.org/w/index.php?title=Meetings/Tacker&diff=174888
Meetings/Tacker
2020-05-19T09:57:37Z
<p>Ogawa.yasufumi: /* Previous Meeting Logs */</p>
<hr />
<div><br />
=Tacker=<br />
<br />
* project page: https://wiki.openstack.org/wiki/Tacker<br />
* meeting log:<br />
** http://eavesdrop.openstack.org/meetings/tacker/<br />
* long term discussion: https://etherpad.opendev.org/p/tacker-meeting<br />
<br />
== Meeting Information==<br />
* Weekly Tuesday 08:00 UTC: 60 mins<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
<br />
=Agenda=<br />
==Meeting May 26th 2020 (next)==<br />
* develop/patches status<br />
* other discussions<br />
<br />
==Meeting May 19th 2020==<br />
* networking-sfc maintainance<br />
* victoria vPTG pre-discussion<br />
<br />
==Meeting May 12th 2020==<br />
* about networking-sfc<br />
* Update wiki<br />
* develop/patches status<br />
* victoria vPTG<br />
<br />
==Meeting May 5th 2020 (skip)==<br />
<br />
==Meeting Apr. 28th, 2020==<br />
* Victoria vPTG Schedule<br />
* Other discussions<br />
<br />
= Past Meeting Agenda =<br />
[[Meetings/Tacker/PastMeetingAgenda]]<br />
<br />
= Previous Meeting Logs =<br />
<br />
** http://eavesdrop.openstack.org/meetings/tacker/2019/<br />
** http://eavesdrop.openstack.org/meetings/tacker/2018/<br />
** http://eavesdrop.openstack.org/meetings/tacker/2017/<br />
** http://eavesdrop.openstack.org/meetings/tacker/2016/<br />
** http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2015/<br />
** http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/<br />
*** http://eavesdrop.openstack.org/meetings/neutron_servicevm/<br />
*** http://eavesdrop.openstack.org/meetings/neutron_servicevm/2014/</div>
Ogawa.yasufumi
https://wiki.openstack.org/w/index.php?title=Meetings/Tacker&diff=174887
Meetings/Tacker
2020-05-19T09:55:57Z
<p>Ogawa.yasufumi: /* Agenda */ Update meeting schedule</p>
<hr />
<div><br />
=Tacker=<br />
<br />
* project page: https://wiki.openstack.org/wiki/Tacker<br />
* meeting log:<br />
** http://eavesdrop.openstack.org/meetings/tacker/<br />
* long term discussion: https://etherpad.opendev.org/p/tacker-meeting<br />
<br />
== Meeting Information==<br />
* Weekly Tuesday 08:00 UTC: 60 mins<br />
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code><br />
<br />
=Agenda=<br />
==Meeting May 26th 2020 (next)==<br />
* develop/patches status<br />
* other discussions<br />
<br />
==Meeting May 19th 2020==<br />
* networking-sfc maintainance<br />
* victoria vPTG pre-discussion<br />
<br />
==Meeting May 12th 2020==<br />
* about networking-sfc<br />
* Update wiki<br />
* develop/patches status<br />
* victoria vPTG<br />
<br />
==Meeting May 5th 2020 (skip)==<br />
<br />
==Meeting Apr. 28th, 2020==<br />
* Victoria vPTG Schedule<br />
* Other discussions<br />
<br />
= Past Meeting Agenda =<br />
[[Meetings/Tacker/PastMeetingAgenda]]<br />
<br />
= Previous Meeting Logs =<br />
<br />
** http://eavesdrop.openstack.org/meetings/tacker/2017/<br />
** http://eavesdrop.openstack.org/meetings/tacker/2016/<br />
** http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2015/<br />
** http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/<br />
*** http://eavesdrop.openstack.org/meetings/neutron_servicevm/<br />
*** http://eavesdrop.openstack.org/meetings/neutron_servicevm/2014/</div>
Ogawa.yasufumi