copper:planning
Table of Contents
Copper Project Planning
This page shows planned work for Copper.
Current R2 C-Milestone Status
(draft in progress)
| Criteria | Copper Status |
|---|---|
| 1. Project name | Copper |
| 2. Project status indicator for milestone C readiness: Green/Yellow/Red; GREEN = on track; YELLOW = working minor issues to get back on track; RED = offtrack with major issues | Green |
| 3.Name of person providing status | Bryan Sullivan |
| 4.a link to your Jira tasks (filtered on R2) | Copper R2 Jira tasks |
| 5.a link to your Jira dashboard | Copper Jira Dashboard |
| 6.a statement of your progress at linking cross project dependencies in Jira | Complete: see Genesis-54, Functest input |
| 7.a statement of your readiness (detailed planning complete & in Jira) for your first sprint or first development cycle (if not agile) | First development cycle is underway. |
| 8.a statement of your readiness (high level planning complete & in Jira) for future sprints | We do not plan to organize around sprints. |
| 9.a statement about any issues you have | Complexity of getting lab resources; steep/long learning curve on fundamentals of creating workloads and virtual network environments under OpenStack and OpenDaylight; |
| 10.how & when you will finish getting your tasks & dependencies into Jira if not complete | Jira is complete. |
| 11.how and when you will get ready to start development for Brahmaputra if not ready now | Development for Brahmaputra is underway. |
| 12.a statement summarizing your project risk analysis & planning status | Detailed risk management planning has not been attempted. Overall nature or risks and dependencies is clear, e.g. see issues above. No obvious solutions to these issues other than additional resources. We will do our best. |
Copper Project Box
| Must-Have Req's | At-Risk Req's |
|---|---|
| Config PolicyTestbed | |
| Config Policy Use Cases | |
| Config Policy Tests |
| Working Plan Reqs | Outplan Req's |
|---|---|
| Requirements Gap Analysis | |
| Draft Blueprints |
Copper Dependencies on other OPNFV Projects
| Criticality | Project | Dependency Description |
|---|---|---|
| Must-Have | FuncTest | Incorporation of OpenStack Congress into B release functional tests, either as part of automated post-install tests, or as an on-demand test set. |
| Working Plan | Genesis | Incorporation of OpenStack Congress into B release CI build and smoke test processes. Alternately, prepare tools for post-install OPNFV platform augmentation with Congress. |
| Working Plan | SFC | ODL-based service chaining and group policy as a means to establish network resource configurations for services. |
| Working Plan | SFC, Promise | Incorporation of upstream projects as emulators / test drivers (at least) for VNFM/NFVO functionality. |
Copper Dependencies on Upstream Projects
| Criticality | Project | Dependency Description |
|---|---|---|
| Must-Have | OpenStack Kilo | Stable release version, as basis for adding Congress, Heat, etc. |
| Must-Have | OpenStack Congress | Config policy violation detection for OpenStack-managed resources. |
| Working Plan | OpenDaylight Lithium | Stable release version, as basis for adding SFC, GBP, etc. |
| Working Plan | OpenDaylight SFC | ODL-based service chaining as a means to establish network resource configurations for services. |
| Working Plan | OpenDaylight GBP | ODL-based endpoint group policy management as a means to establish network resource configurations for services. |
| Working Plan | OpenStack Heat | Template-based resource configuration for VNFs. |
copper/planning.txt · Last modified: 2015/09/24 18:57 by Bryan Sullivan
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
