Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Full and comprehensive VNF/Software Application(VF), and service design, which includes, not limited to:
    • Onboarding VNF/VF
    • Workflow design
      • lifecycle flows
      • change management flows
      • Discovery of available workflow actions (related to Micro Services and discovery)

    • Close loop design
    • policy design
    • Service function chaining Design
    • VNF/VF License Design
    • VF/VNF deployment flavor design
  • Collaborative design
    • versioning
    • Design Lifecycle
  • VNF/VF/SERVICE testing and certification
  • Distribution to ONAP
    • TOSCA parser
  • External API- for VNF/VF and  service 
  • Image management
  • Identify the usecase in the Release 1

    • VoLTE usecase 
      • Service and VNF design
      • Workflow design
      • SFC design
  • Test
  • Integration with BSS / Customer ordering 

  • Describe the functionality to be provided by the project.  Please provide the full intended scope of the project; not just what is intended for the project's first release.
  • Specify any interface/API specification proposed,
  • Identity a list of features and functionality will be developed.
  • Identify what is in or out of scope. During the development phase, it helps reduce discussion.


Architecture Alignment

  • An alignment between the below projects should be agreed on

    • CLAMP is showing “Designing the Control Loop

    • ICE – there is a link with onboarding

    • Modelling – we intend to provide modelling for A&AI in SDC
    • Network Function Change Management is showing “This project provides users with the ability to design workflows
    • Policy Framework Project Proposal is showing “Policy Design GUI - work with SDC project to integrate the Policy Design GUI
    • VNF SDK – there is a link with onboarding
    How the existing functionality is going to align in ONAP
    • How it will integrate with:
    • VNF-SDK
    • ICE (VNF certification)
    • Modeling
  • What kind of dependency other projects will have with SDC, e.g SO modeling?
  • How will multi VIM project influence on the input/ output we have for SDC?
  • How to align to standards like ETSI VNF packaging?

...

Repo name: SDC and SDC/sdc-destribution-client
Lifecycle State: 
Primary Contact: Michael Lando, Tal Halfon
Project Lead: Michael Lando (AT&T), Avi Ziv (amdocs)
mailing list tag sdc 
Committers:


Avi Ziv

amdocs

Avi.Ziv@amdocs.com

...

Raanana, Israel. GMT +3

 Ziv Levy

 amdocs

 Ziv.Levy@amdocs.com

Raanana, Israel. GMT +3

Shalom BermanamdocsSHALOMB@Amdocs.com

...

Raanana, Israel. GMT +3
Shrikant AwacharamdocsShrikant.Awachar@amdocs.comPune, India. GMT +5.5
Vitaliy EmporopuloamdocsVitaliy.Emporopulo@amdocs.comRaanana, Israel. GMT +3
Halfon TalamdocsHalfon.Tal@amdocs.comRaanana, Israel. GMT +3
Zhaoxing Meng

...

...

...

LvZTEv

...

...

...


An HoHuawei

an.ho@huawei.com


Kang XiHuawei

kang.xi@huawei.com


Chong LiHuawei

chong.li@huawei.com


Rene RobertOrange

rene.robert@orange.com




*Link to TSC approval: 
Link to approval of additional submitters: