releases:brahmaputra:release_artifacts_discussion
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
releases:brahmaputra:release_artifacts_discussion [2015/09/21 10:46] Christopher Price |
releases:brahmaputra:release_artifacts_discussion [2015/12/09 12:35] (current) julien zhang |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Stack of Brahmaputra ====== | ||
| + | |||
| + | ^ Stack ^ OS ^^ | ||
| + | ^ ::: ^ Ubuntu ^ CentOS ^ | ||
| + | | Openstack | Kilo | Kiko | | ||
| + | | Kernel | 3.14? | | | ||
| + | | OVS | 2.3.0 | | | ||
| + | | Qemu | 2.3.0 | | | ||
| + | | KVM | | | | ||
| + | | Libvirt | 1.2.13 | | | ||
| + | | ODL | Lithium SR2 | | | ||
| + | | Onos | | | | ||
| + | |||
| + | |||
| ====== Discussion: Release Artifacts for Brahmaputra ====== | ====== Discussion: Release Artifacts for Brahmaputra ====== | ||
| Line 16: | Line 30: | ||
| Summary of options discussed: | Summary of options discussed: | ||
| - | ^ Identifier ^ Option title ^ | + | ^ Identifier ^ Option title ^ |
| - | | A.1a | Bootable disk image per installer | | + | | A.1a | Bootable disk image per installer | |
| - | | A.1b | Self-contained bootable disk image per installer | | + | | A.1b | Self-contained bootable disk image per installer | |
| - | | A.1c | Single bootable disk image covering all installers | | + | | A.1c | Single bootable disk image covering all installers | |
| - | | A.2a | Install script per installer | | + | | A.2a | Install-documentation only per installer | |
| - | | A.2b | Single install script covering all installers | | + | | A.2b | Install script per installer | |
| + | | A.2c | Single install script covering all installers | | ||
| + | |||
| Note: For OPNFV Arno: | Note: For OPNFV Arno: | ||
| - | * A.1a was required | + | * A.1b was required |
| - | * A.1b and A.2a were optional | + | * A.1a and A.2b were optional |
| + | |||
| + | Note: For OPNFV Brahmaputra : | ||
| + | * A.2b is required | ||
| + | |||
| + | TSC decision : http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-10-06-13.59.html | ||
| + | VOTE: Voted on "Preference on minimum requirements on release artifacts?" Results are, A2b: 7, abstain: 1, A1b: 1 (ChrisPriceAB, 14:49:18) | ||
| + | |||
| ==== Option A.1a: Bootable disk image per installer ==== | ==== Option A.1a: Bootable disk image per installer ==== | ||
| Line 49: | Line 74: | ||
| * documentation / release notes | * documentation / release notes | ||
| - | ==== Option A.2a: Install script per installer ==== | + | ==== Option A.2a: Install-documentation only per installer ==== |
| + | |||
| + | A release is comprised of: | ||
| + | |||
| + | * documentation / release notes on installing OPNFV from the tagged Git repository corresponding to the release | ||
| + | |||
| + | ==== Option A.2b: Install script per installer ==== | ||
| A release is comprised of: | A release is comprised of: | ||
| Line 57: | Line 88: | ||
| - | ==== Option A.2b: Single install script covering all installers ==== | + | ==== Option A.2c: Single install script covering all installers ==== |
| A release is comprised of: | A release is comprised of: | ||
| Line 75: | Line 106: | ||
| ^ Identifier ^ Approach title ^ | ^ Identifier ^ Approach title ^ | ||
| | M.1 | Latest only | | | M.1 | Latest only | | ||
| - | | M.2 | Latest plus Service Releases for "Latest-1" | | + | | M.2a | Latest and stable branch maintenance | |
| - | | M.3 | Latest plus Service Releases for "Latest-n" (n=1,2...) | | + | | M.2b | Latest plus Service Releases for "Latest-1/stable" | |
| + | | M.3a | Latest and branch maintenance for the last k releases (k>1) | | ||
| + | | M.3b | Latest plus Service Releases for "Latest-n" (n=1,2..m) | | ||
| - | Note: For OPNFV Arno approach "M.2" is used. | + | Note: For OPNFV Arno approach "M.2b" is used. |
| ==== Option M.1: Latest only ==== | ==== Option M.1: Latest only ==== | ||
| Line 88: | Line 121: | ||
| * Bug fixes and new features are provided in a continous way. | * Bug fixes and new features are provided in a continous way. | ||
| - | ==== Option M.2: Latest plus Service Releases for "Latest-1" ==== | + | ==== Option M.2a: Latest and stable branch maintenance ==== |
| + | |||
| + | Release definition and maintenance: | ||
| + | |||
| + | * "Releases" are defined by labeling in git. | ||
| + | * A release is maintained and bug-fixes are applied to a release. I.e. there are always two active branches in OPNFV: | ||
| + | * "latest" - artifacts that will become the next release | ||
| + | * "stable" - the current release plus fixes on top of the most recent release (i.e. on top of the labeled artifacts of the most recent release). | ||
| + | * The "stable" branch will be available and stable at all times after the release until the next release. | ||
| + | * Requires higher validation settings on stable for all changes | ||
| + | |||
| + | Example for this option: | ||
| + | * Brahmaputra released - Brahmaputra would be the "stable" release, C-River would become "latest" | ||
| + | * Fixes for Brahmaputra would be done and committed to "stable" | ||
| + | * No further maintenance for Arno would be done | ||
| + | |||
| + | ==== Option M.2b: Latest plus Service Releases for "Latest-1/stable" ==== | ||
| Release definition and maintenance: | Release definition and maintenance: | ||
| Line 98: | Line 147: | ||
| * Snapshots of the "stable" branch will be released at regular intervals as "service releases" using labels. | * Snapshots of the "stable" branch will be released at regular intervals as "service releases" using labels. | ||
| - | ==== Option M.3: Latest plus Service Releases for "Latest-n" (n=1,2...) ==== | + | Example for this option: |
| + | * Brahmaputra released - Brahmaputra would be the "stable" release, C-River would become "latest" | ||
| + | * Fixes for Brahmaputra would be done and committed to "stable" | ||
| + | * At regular intervals service releases of Brahmaputra would be created | ||
| + | * No further maintenance for Arno would be done | ||
| + | |||
| + | ==== Option M.3a: Latest and branch maintenance for the last k releases (k>1) ==== | ||
| + | |||
| + | Release definition and maintenance: | ||
| + | |||
| + | * "Releases" are defined by labeling in git. | ||
| + | * The last k releases are maintained and bug-fixes are applied to the last k releases. I.e. there are k+1 active branches in OPNFV: | ||
| + | * "latest" - artifacts that will become the next release | ||
| + | * "stable" - the current release plus fixes on top of the most recent release (i.e. on top of the labeled artifacts of the most recent release). | ||
| + | * ... | ||
| + | * "stable - (k-1)" - the release which is (k-1) versions older than the most recent release plus fixes on top of the most recent release. | ||
| + | * The "stable ..." branches will be available and stable at all times. | ||
| + | * "k" would be a value defined by the TSC | ||
| + | |||
| + | Example for this option - with k=2: | ||
| + | * Brahmaputra released: Brahmaputra would be the "stable" release, C-River would become "latest", Arno would be "stable-1" | ||
| + | * Fixes for Brahmaputra would be done and committed to "stable" | ||
| + | * Fixes for Arno would be done and committed to "stable-1" | ||
| + | * Once C-River would be released, maintenance for Arno would stop. | ||
| + | |||
| + | ==== Option M.3b: Latest plus Service Releases for "Latest-n" (n=1,2...) ==== | ||
| Release definition and maintenance: | Release definition and maintenance: | ||
| Line 108: | Line 182: | ||
| * "stable release n-1" - the release prior to the current release plus fixes on top of the released (i.e. labeled) artifacts. | * "stable release n-1" - the release prior to the current release plus fixes on top of the released (i.e. labeled) artifacts. | ||
| * ... | * ... | ||
| - | * "stable release 1" - Arno release plus fixes on top of the released artifacts. | + | * "stable release m" - Release m (in case m=1, this would be Arno) plus fixes on top of the released artifacts. |
| * Snapshots of the "stable" branches will be released at regular intervals as "service releases" using labels. | * Snapshots of the "stable" branches will be released at regular intervals as "service releases" using labels. | ||
| + | * "m" would be a value defined by the TSC | ||
releases/brahmaputra/release_artifacts_discussion.1442832398.txt.gz · Last modified: 2015/09/21 10:46 by Christopher Price
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
