Page tree
Skip to end of metadata
Go to start of metadata

This page shows planned work for the Models project.

Euphrates

Deliverables:

  • MODELS-46: Installer scripts for VNFN/NFVO projects as used in the Models use case tests
  • MODELS-23: Models use case tests for various smoketest (Hello World) and simple/medium-complexity VNFs
  • MODELS-25: Functest integration of use case tests for as many installers as possible: JOID, Apex, Fuel, Compass
  • Reference VNF/blueprint library

Danube

Deliverables:

  • MODELS-29MODELS-30: Baseline TOSCA model for VNFs, based upon best examples of VNFs that are deployable on the OPNFV Colorado/Danube system
  • MODELS-46: Installer scripts for VNFN/NFVO projects as used in the Models use case tests
  • MODELS-23: Models use case tests for various smoketest (Hello World) and simple/medium-complexity VNFs
  • MODELS-25: Functest integration of use case tests for as many installers as possible: JOID, Apex, Fuel, Compass
  • Broader goals for VNF modeling, e.g. support of a modeled-object method for service orchestrator integration with infrastructure providers
  • Analysis of the goals and solutions for modeling-related aspects of the VNF/service lifecycle
    • Development
      • Developer tools
        • VNF topology and lifecycle
        • Application control
      • VNF package preparation
      • VNF package upload to ingestion
    • Onboarding
      • VNF package ingestion
      • Testing
      • Augmentation
      • Incorporation into Services
      • Cataloging
    • Production
      • Deployment
      • Lifecycle event handling
      • Application control
      • Telemetry
  • Analysis of capabilities and variation of current NFVO/VNFM solutions focused on in the Danube release
  • Role of standards, formats, tools etc in the above, e.g. TOSCA, YANG, application-specific logic design tools, etc
  • Upstream feedback recommendations
    • SDOs: key gaps needing closure
    • Open source projects: possible blueprints
  • Reference VNF/blueprint library

Project plan per the milestones described at Danube.

MilestoneStatus/PlanNotes
(MS0) Open Intent to ParticipateDone (9/27/16) 
(MS1) Planning complete (scenarios or deliverables defined)10/25/16See "Deliverables" above.
(MS2) Detailed test case descriptions communicated to test project teams11/22/16 
(MS3) Installer integration with OpenStack completed11/30/16 
(MS4) Infrastructure updates completed12/6/16 
(MS5) Scenario integration and Feature Freeze completed1/13/17 
(MS6) Test cases implemented, preliminary documentation completed, and stable branch open1/26/17 
(MS7) Stable branch window close3/10/17 
(MS8) Formal test execution completed3/20/17 
(MS9) JIRA issues assigned to release closed or deferred3/22/17 
(MS10) Documentation completed3/24/17 
(MS11) Release Danube 1.0
3/27/17 
(MS12) Release Danube 2.0
5/4/17 
(MS13) Release Danube 3.06/8/17 

 

Colorado

Following were project plans for the Models project per the C release planning page.

Milestone expectations

MS0 : Project planning

  • Activities to be performed during this phase:
    • State your intention to participate in the C-Release: YES
    • establish release plan wiki: Models release plan
    • Define impacts on other projects;
      • installers: no impacts at this time
        • Models is not expected to result (by itself) in the addition of new components to the OPNFV reference platform. Rather, as needed components may be used in the FuncTest process similar to the use of Cloudify for the vIMS tests.
      • test projects
        • Functest: tests are expected to be contributed to the Functest library
        • Dovetail: use cases are expected to be contributed to the Dovetail library
      • documentation: normal support by documentation toolchain
      • Infrastructure (pharos/CI)
        • Models is expected to add additional tests to the CI/CD pipeline.
    • Include estimated time and resource plans

Task

Estimated time/week

Contributors

Outreach to SDOs, Open Source projects, OPNFV projects

2 hrs

Bryan

Model research/analysis

2 hrs

Dan

Tools research/analysis (including MANO components)

2 hrs

Dan

Use case development/testing

2 hrs

Bryan

 

  • Project plans in place in Jira (at the story level and cross project)

 

key summary type created updated due assignee reporter priority status resolution

JIRA project doesn't exist or you don't have permission to view it.

View these issues in JIRA

MS1 : Planning complete

  • Project must
    • Have coordinated schedules with other projects and captured cross project dependencies in Jira
    • Have a concrete project time plan in place that accommodates dependencies and resource availability
    • Dependencies must include upstream dependencies impacting ability to execute on future milestones
  • Activities to be performed after this milestone
    • Development of feature code
    • Integration in, or establishment of, scenario's
    • Test case development
      MS2 : Feature Code freeze
  • Feature project must
    • Be code complete.
    • Have completed unit test case development
    • Have documentation in place for pre-release verification
  • Activities to be performed after this milestone
    • Begin release readiness activities and verification.
      • Stable branch labels can be applied from here (project to decide when to pull the stable branch).
        MS3: Installation Code freeze:
  • Installers code complete / code freeze
  • Features successfully deploy expected deliverables on a pharos lab
  • Feature/component installs with target installer(s), i.e. plugins or similar for the installers are ready.

MS4: Test Code freeze

  • Test infra and Test cases for system level testing of features available and code complete.

MS5: Integration ready:

  • Combination of components in scenarios work "as designed".

MS6 : Release

  • Project must
    • All frozen features and scenario's have achieved release readiness.
    • All stable branch labels in place, release labels available on the branch.
  • Activities to be performed after this milestone
    • Clear plans for release support according to the release stable processes

Planned Tasks for C Release

Slogan

Jira issue

Use Cases

MODELS-1

Testbed

MODELS-2

Tests

MODELS-3

Release Notes

MODELS-4

Requirements Gap Analysis

MODELS-5

Draft Blueprints

MODELS-6

Project Box

Must-Have Reqs

At-Risk Reqs

Use Cases

 

Testbed

 

Tests

 

Release Notes

 

Working Plan Reqs

Outplan Reqs

Requirements Gap Analysis

 

Draft Blueprints

 

Dependencies on other OPNFV Projects

Criticality

Project

Dependency Description

Must-Have

FuncTest

Incorporation of Models test scenarios C release functional tests, either as part of automated post-install tests, or as an on-demand test set.

Working Plan

TBD

Establishment of model-based feature priorities within the scope of OPNFV project.

Dependencies on Upstream Projects

Criticality

Project

Dependency Description

Must-Have

OpenStack

Latest stable release version, as basis for adding TBD components and testing

Must-Have

OpenDaylight

Latest stable release version, as basis for adding TBD components and testing

  • No labels