This wiki page is explicitly set up as a scratch-pad of feedback that the ONAP TSC Members will use to identify, and collate initial feedback to ONAP project proposals as we all prepare for the first set of Project Creation Reviews starting on June 8th and 9th 2107.
...
APPC Project Proposal (5/12/17
(Phil Robb pjr) SAMPLE COMMENT
...
(Stephen Terrill)
- While obvious, it would be good to state in the project description and scope that this produces the APP-C module. E.g. This purpose of this project is to create the Application controller module.
- In the project description, it states the "APPC model will be based on ONAP TOSCA, YANG, ...". I assume this will have a dependency on the modeling project. Can we call out specifically what this project will contribute with the models vs uses. i.e. I was looking for whether this project felt it was responsible for a model, in alignment with the modeling project, Or would it use the models defined by the modeling project?
- The project description could go into more of what the project is about. e.g. To produce an application controller that : ...."
- In the scope, where it states that it "provides Generic LCM commands" it would be good to work in that this is an API that is the responsibility of this project.
- There is some text such as "Manage the VNF operational state including Blocking, Sequencing and Session Throttling" where the project is not really doing, but the model the project produces does, small but could be clearer. e.g. "APP-C will: bullet points.
- In the text for "how does this align with external standards/specification", I thought it also used YANG for the components of the southbound? (question, not a statement).
- General: Is there dependencies on the common controller framework that hasn't been called out? Either state the dependencies, or state how that is to be handled in the scope.
- General: There is the discussion around the alignment or relation to the VF-C, however I do agree that leaving this out for now until this is clearer in the architecture is fine.
- I think it would be good to call out the interfaces defined and used by the project. Note as there are interfaces common to all controllers, maybe the definition of the interfaces could be under the common controller framework project??? note: we need to ensure that this is done in such a way that the capabilities of one controller, or release, does not hold back the capabilities of other controlers.
- My view on the resources, committers is that this is ok (4 committers, 3 companies, a number of interested resources).
...
Service Orchestrator (5/14/17)
(Alla, Andrei)
- Closed Loop management and orchestration: applying Event/Model/Policy approach causing service re-plan
(Stephen)
- Scope is rather clear. It would be good to state which APIs the project feels it is responsible for defining (it states later which it feels it uses).
- JIRA prefix: I suggest we drop MSO now as I understood its decided as SO.
...
- Potential Overlap with VNF SDK for VNF validation tooling or testing framework.
- Need clarificatin with the overlap between modeling and this project regarding the VNF template (HEAT and TOSCA).
ICE
(Alla, Andrei)
- VNF package validation, VNF testing based on agreed KPI's;
- Supporting ETSI NFV standards and TOSCA specifications;
- VNF store/market place;
- VNF certification;
- Leveraging SDC platform and SDC/ONAP Portal
(Jason Hunt)
- I believe I understand the difference between ICE and VNF SDK, as it appears that VNF SDK will provide all the tooling to implement the validation program, but the ICE/VNF Validation Program will establish the community and processes for validation. Is this correct? Because of the tight synergies of these projects, would you consider merging them? Perhaps VNF SDK and VNF Requirements could be subprojects under the VNF Validation Program?
- (CJD) The skillsets (and interests) of the committers are different. Some people have experience with code, others with writing guidelines, and others with developing certification/compliance programs. While there will be a relationship between the projects, we think that this separation makes sense from a committer and governance perspective.
(Roberto Kung)
- VNF SDK and ICE should be merged. VNF-SDK starts almost from scratch, so it would be easy. Some links to be made do OPNFV (Dovetail, Program CVP).
- Will depends very much on technical decisions from other projects that may impact VNF guidelines.
- (CJD) VNF SDK is part of the OPEN-O Mercury release (not from scratch). Note that we made changes from the original project proposals - code development (tools) will occur in VNF SDK and validation program development (governance) will occur in ICE.
...
(Chris) We discussed this at length between the VNF SDK/ICE teams. ICE/Verification will focus on the verification program. VNF SDK will focus on the tools (including the ICE tools) and will align with SDC.
VNF-SDK
(Alla, Andrei)
- VNF package onboarding;
- Supporting ETSI NFV standards and TOSCA specifications;
- Leveraging SDC platform and SDC/ONAP Portal
(Jason Hunt)
- I believe I understand the difference between ICE and VNF SDK, as it appears that VNF SDK will provide all the tooling to implement the validation program, but the ICE/VNF Validation Program will establish the community and processes for validation. Is this correct? Because of the tight synergies of these projects, would you consider merging them? Perhaps VNF SDK and VNF Requirements could be subprojects under the VNF Validation Program? Or are there other uses of VNF SDK outside of the validation program?
- Can you clarify how this tooling will be provided? Will it be another running component of ONAP, accessible from the ONAP portal?
- Can you clarify the role of the network function repository? Is the thought for this to be run separately by a third party? If not, and it is part of an ONAP installation, how is it different from the existing catalog of onboarded functions?
...
- Could the proposal clarify the unified model-driven approach? How are the data models used by AAI, APIs, or blueprints updated?
- Include in scope: Modeling and Design (concept for multiple projects: CLAMP, SDC, AAI, Network Functions Change Management, External API Framework, External System Registry
- Include in Scope: Application Modeling (VNF modeling) (e.g. YAML based) for managed VNF's as supported by APP-C that leverages Closed Loop management including application management
- Small: the text uses OPEN-O and OpenECOMP. As the project description should survive the first release, perhaps look at wording to avoid referring to those terms as they should be deprecated in ONAP. e.g. "The project will produce unified and consolidated data models".
- Under "scope" The reference to R1 may better be removed. It may imply that the data model will be designed to address these use cases only and ignore the rest, which I am sure was not the intention. This information should go into the release planning, not project definition.
- Question: What about backwards compatibility for ECOMP and Open-O data models? Will there be a new model to replace both? If so, is ONAP expected to support only the unified model? Or support the new as well as the two old ones?
...
- Could the proposal clarify the unified model-driven approach? How are the data models used by AAI, APIs, or blueprints updated?
(Alla, Andrei)
- Include in scope: Modeling and Design (concept for multiple projects: CLAMP, SDC, AAI, Network Functions Change Management, External API Framework, External System Registry);
- Include in Scope: Application Modeling (VNF modeling) (e.g. YAML based) for managed VNF's as supported by APP-C that leverages Closed Loop management including application management
(Stephen)
- Small: the text uses OPEN-O and OpenECOMP. As the project description should survive the first release, perhaps look at wording to avoid referring to those terms as they should be deprecated in ONAP. e.g. "The project will produce unified and consolidated data models".
- During the release planning, it would be good to have the plan of when to deliver what models for the needs of other projects to use.
- I understand that the deliverables are both models, as well as code in the form of tools. Should they be in the same repo, or different repos (question, not a statement). consider separating tooling from models in repos
- The number of committers is very high, perhaps 1-2 per company
- Be clear on the tools to be as a deliverable, and the APIs. e.g. a model passer .
...
Reasonable and Well defined Scope:
- Scope seems rather large. Not clear on what is for the first release, and interactions/dependencies with DCAE, policy, SO, Controllers. .....
- More detail on what test is
- could be clear on what deliverables are required to support the use cases.
- What is the scope of the catalog module
Identification of SW modules and APIs being developed and delivered to other components
- It would be great to be clear on the modules delivered by this project
- The connections to other projects should be clarified clearly.
- Are there APIs that the project feels it is responsible for, or does it use the APIs defined by others?
Follow project and LF guidelines for contributors/committers
- Perhaps 1-2 committers per company
Identification of dependences and assumptions on other components and open source
...
Intentional and unintentional overlap
- Any relation to ICE?
overlap with external opensource efforts
...
Could the proposal describe the scope of the catalog module?
(Alla, Andrei)
- SDC should be an umbrella for all Design time parts from other Projects (CLAM, Policy, Converged ICE & VNF SD-K);
- SDC is a platform for all the modeling and design in ONAP and provides the interactive tool for design and automation for on-boarding.
(Stephen)
- It would be great to be clear on the modules delivered by this project.
- The connections to other projects should be clarified clearly.
- Are there APIs that the project feels it is responsible for, or does it use the APIs defined by others?
- Perhaps 1-2 committers per company
- More detail on what test is.
- Scope seems rather large. Not clear on what is for the first release, and interactions/dependencies with DCAE, policy, SO, Controllers. ......
- Not clear what deliverables are required to support the usecases
(Zhaoxing)
- Could this project proposal clarify how to support the Telcom use case(VoLTE), for example, how to onboarding TOSCA based VNF and use it as building block for service design?
- Could this project proposal clarify its relationship/dependency with ICE? It seems that the ICE project will provide guideline/process definition for certification and this project will provide tools to support ICE?
...
Sound technical solution solving a real need.
...
(Stephen)
- Scope: could be a little clearer by way of example..
...