get_started:release_and_maintenance
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Last revision Both sides next revision | ||
|
get_started:release_and_maintenance [2015/05/06 14:56] Frank Brockners created |
get_started:release_and_maintenance [2015/05/06 15:25] Tim Rozet |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Terminology discussion: "Release", "Latest", etc. ====== | ====== Terminology discussion: "Release", "Latest", etc. ====== | ||
| - | * **Release** | + | * "**Release**" |
| * OPNFV defined fixed set of objects and artifacts. All objects and artifacts are **specifically versioned**: Using the versions it must be possible to reproduce the "release" for as long as the "release" is supported by OPNFV (i.e. not deprecated). | * OPNFV defined fixed set of objects and artifacts. All objects and artifacts are **specifically versioned**: Using the versions it must be possible to reproduce the "release" for as long as the "release" is supported by OPNFV (i.e. not deprecated). | ||
| * The "release" successfully deploys on a set of reference hardware/infrastructure (see below for "reference hardware"). Successful deployment means that all tests defined for a particular release pass. | * The "release" successfully deploys on a set of reference hardware/infrastructure (see below for "reference hardware"). Successful deployment means that all tests defined for a particular release pass. | ||
| Line 8: | Line 8: | ||
| * Bootable disk image (ISO) to install the jump host | * Bootable disk image (ISO) to install the jump host | ||
| * Build script which allows the creation of the above mentioned ISO | * Build script which allows the creation of the above mentioned ISO | ||
| - | * Option: Deploy script which creates an equivalent installation of what the bootable disk image (ISO) creates. | + | * Deploy script which creates an equivalent installation of what the bootable disk image (ISO) creates as well as deploys OPNFV Target System. |
| * Description of the reference hardware and its configuration that the code was tested on | * Description of the reference hardware and its configuration that the code was tested on | ||
| * Description of all components/artifacts used in the release, including their individual versions (and if applicable, a reference to where these artifacts are sourced from). | * Description of all components/artifacts used in the release, including their individual versions (and if applicable, a reference to where these artifacts are sourced from). | ||
| Line 16: | Line 16: | ||
| * Community supported: Collections of bug-fixes etc. will be supplied as a "maintenance release" (see below), which has the same qualities as a "release". | * Community supported: Collections of bug-fixes etc. will be supplied as a "maintenance release" (see below), which has the same qualities as a "release". | ||
| - | * **Maintenance release** | + | * "**Maintenance release**" |
| * Fixed set of objects and artifacts defined by a specific existing (i.e. already released) OPNFV release. | * Fixed set of objects and artifacts defined by a specific existing (i.e. already released) OPNFV release. | ||
| * The "maintenance release" successfully deploys on a set of reference hardware/infrastructure (see below for "reference hardware"). Successful deployment means that all tests defined for a particular release pass. | * The "maintenance release" successfully deploys on a set of reference hardware/infrastructure (see below for "reference hardware"). Successful deployment means that all tests defined for a particular release pass. | ||
| * "Maintenance release" content is the same as that of a "release". | * "Maintenance release" content is the same as that of a "release". | ||
| - | * **Latest** | + | * "**Latest**" |
| * Fixed set of objects and artifacts defined by a specific OPNFV release (existing //or// planned). Rather than using a specific version of a particular component, the latest available components (could be binary artifacts or sources) from upstream repositories are used. | * Fixed set of objects and artifacts defined by a specific OPNFV release (existing //or// planned). Rather than using a specific version of a particular component, the latest available components (could be binary artifacts or sources) from upstream repositories are used. | ||
| - | * The "latest" successfully deploys on a set of reference hardware/infrastructure (see below for "reference hardware"). Successful deployment means that all tests defined for the particular release (existing or planned) pass. | + | * The "latest" successfully deploys on a set of reference hardware/infrastructure (see below for "reference hardware"). Successful deployment means that all tests defined for the particular release (existing or planned) pass. Main objective of "latest" is to give developers and testers immediate feedback at system level. |
| * OPNFV defined set of scenario tests associated with the release | * OPNFV defined set of scenario tests associated with the release | ||
| * "Latest" does not imply a “supported” release, rather is the “latest” working merge working towards the next target ‘release’ (future or maintenance) from OPNFV. | * "Latest" does not imply a “supported” release, rather is the “latest” working merge working towards the next target ‘release’ (future or maintenance) from OPNFV. | ||
| * Does not imply anything more than Jenkins smoke-test and may/may not work (Users should be aware) | * Does not imply anything more than Jenkins smoke-test and may/may not work (Users should be aware) | ||
| - | * **Reference hardware/infrastructure** | + | * "**Reference hardware/infrastructure**" |
| * Set of infrastructure to deploy an OPNFV release on (used for validation purposes) | * Set of infrastructure to deploy an OPNFV release on (used for validation purposes) | ||
| * Documentation of | * Documentation of | ||
get_started/release_and_maintenance.txt · Last modified: 2015/05/06 17:57 by Daniel Smith
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
