releases:arno:releasereadiness
This is an old revision of the document!
Release Readiness for Arno: Status and Plan
Time to release readiness: max{TEST.READY, SYS.READY} + max{SYS.AUTOMATED,TEST.EXEC} + SYS.RELEASE + DOCS.READY
Status and plan as of Apr/22:
| Category | Task | Fuel deployment approach | Foreman deployment approach | Project | Effort to complete: estimate | Dependencies |
|---|---|---|---|---|---|---|
| LAB | LF lab state stable and configuration documented and up to date | Pharos | ||||
| LAB | Field labs state stable and documented and up to date in Pharos | Pharos | ||||
| LAB | Pharos specification | Pharos | ||||
| LAB | System Usernames | yes (wiki) | yes (wiki) | Pharos | ||
| LAB | LF infrastructure - hardware | yes (wiki) | yes (wiki) | Pharos | ||
| LAB | LF infrastructure - admin | yes (wiki) | yes (wiki) | Pharos | ||
| LAB | LF infrastructure - access | yes (wiki) | yes (wiki) | Pharos | ||
| LAB | LF infrastructure - physical diagram (wiki) | yes (wiki) | yes (wiki) | Pharos | ||
| LAB | LF infrastructure - logical topology diagram (wiki) | yes (wiki) | yes (wiki) | Pharos | ||
| LAB | LF infrastructure - LO network | yes (wiki) | yes (wiki) | Pharos | ||
| LAB | LF infrastructure - Networks | draft (wiki) | draft (wiki) | Pharos | ||
| LAB | LF infrastructure - IPs | draft (wiki) | draft (wiki) | Pharos | ||
| SYS.READY | Bootable ISO disk image for Jumphost installation available | yes | yes | BGS | done | |
| SYS.READY | Bootable ISO disk image for Jumphost installation tested by 3rd-party | no | in progress | BGS | 2 days | |
| SYS.READY | Final system state fully documented target system state wiki | BGS | 1 day | |||
| SYS.READY | LF Hardware available and fully configured (POD1 and POD2) | no | Available, starting install 4/20/15 | BGS | 1 day | |
| LF Hardware PODSs configured the same (VLANs/users/etc. the same across across POD1 and POD2) | no | no | BGS | 1 day (once both installers work on their PODs) | ||
| SYS.AUTOMATED | Jump servers operational with Jenkins connectivity (POD1 and POD2) | yes - verification pending | yes - verification pending | Octopus | ||
| SYS.READY | Manual deploy to development lab fully functional | yes (Ericsson lab) | yes (Intel lab) | BGS | done | |
| SYS.READY | Validate that install works on "any lab" - not just the original development lab: Manual deploy to generic Pharos-lab (i.e. LF HW as target) fully functional (Deploy.sh is executed and deploys the install/jumphost automatically and then provisions OpenStack with HA + ODL to baremetal) | no | no | BGS | undetermined (pending resolution of current tech. issues) | TEST.READY |
| SYS.READY | Manual validation that install to "any lab" is operational: Manual base validation of install on generic Pharos-lab (i.e. LF HW as target) ( manually connect to the system, performs basic openstack operations) | no | no | BGS | 1 day | TEST.READY |
| SYS.AUTOMATED | Automated deploy (Jenkins triggered) to LF Hardware fully functional | no | no | Octopus | 1 day | SYS.READY, TEST.EXEC |
| SYS.RELEASE | All tests relevant to Arno pass. Any required fixes in please | no | no | BGS | undetermined (depends on test outcome) | SYS.AUTOMATED, TEST.EXEC |
| SYS.DOCS | Release notes document available in repo | yes - 1st draft | 1st draft in gerrit | BGS | 2 days | |
| SYS.DOCS | User/installation guide available in repo | yes - 1st draft | in progress, estimate 4/21/15 | BGS | 2 days | |
| SYS.DOCS | License information on components used | 1st draft in gerrit | BGS | 1 day | ||
| TEST.READY | Defined and documented set of test cases (Tempest/Rally and Robot) for Arno | Functest | 2 days | |||
| TEST.READY | Robot test cases for Arno created (scripts available) | Functest | 1 day | |||
| TEST.READY | Rally/Tempest scenario test for Arno created (scripts available) | Functest | ||||
| TEST.READY | Robot framework operational on LF HW Jumphosts of POD1 and POD2 | Functest | 1 day | |||
| TEST.READY | Rally/Tempest operational on LF HW Jumphosts of POD1 and POD2 | Functest | 1 day | |||
| TEST.READY | Sample VNFs for testing available | Functest | ||||
| TEST.DOCS | Functional Testing User-Guide for Robot (in .rst) | Functest | ||||
| TEST.DOCS | Functional Testing User-Guide for Rally/Tempest (in .rst) | Functest | ||||
| TEST.DOCS | Functional Testing Release notes for Robot (in .rst) | Functest | 1 day | |||
| TEST.DOCS | Functional Testing Release notes for Rally/Tempest (in .rst) | Functest | ||||
| TEST.EXEC | Successful manual execution of Robot test scripts on field labs HW | Functest | ||||
| TEST.EXEC | Successful manual execution of Robot test scripts on LF HW | Functest | ||||
| TEST.EXEC | Successful manual execution of Tempest test scripts on field labs HW | Functest | ||||
| TEST.EXEC | Successful manual execution of Tempest test scripts on LF HW | Functest | ||||
| TEST.EXEC | Successful manual execution of vIMS test scripts on field labs HW | Functest | ||||
| TEST.EXEC | Successful manual execution of vIMS test scripts on field labs HW | Functest | ||||
| TEST.AUTOMATED | Automated validation (functest, autodeploy & test flow) executed on deployed platform | no | no | Octopus | 1 day | TEST.EXEC |
| TEST.AUTOMATED | Automated validation (functest, autodeploy & test flow) executed on LF deployed platform | no | no | Octopus | 1 day | TEST.EXEC |
| DOCS.INFRA | Documentation tool-chain installed and operational in OPNFV infra | yes | yes | opnfvdocs | ||
| DOCS.INFRA | Documentation processes documented, including methodology | yes | yes | opnfvdocs | ||
| DOCS.INFRA | Documentation templates available | yes | yes | opnfvdocs | ||
| DOCS.INFRA | Documentation integrated into Gerrit/Jenkins and publishing artefacts | yes | yes | opnfvdocs | ||
| DOCS.INFRA | List of all required docs across all projects | no | no | opnfvdocs | ||
| DOCS.READY | User guide documentation prepared | no | no | opnfvdocs | 2 days | |
| DOCS.READY | Arno release description prepared | no | no | opnfvdocs | 2 days | |
| DOCS.READY | Documentation consolidated and reviewed for final publishing | no | no | opnfvdocs | 3 days | |
| RELEASE.READY | All artifacts (docs, code) packaged up and available to customers (web) | no | no | all | 2 days | DOCS.READY,TEST.EXEC,SYS.DOCS, SYS.RELEASE, LAB |
Additional details:
- For Pharos Pharos release planning
releases/arno/releasereadiness.1429783603.txt.gz · Last modified: 2015/04/23 10:06 by Frank Brockners
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
