releases:c
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
releases:c [2016/03/03 22:19] Debra Scott |
releases:c [2016/03/21 16:06] (current) Frank Brockners |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | "C" Release Page | + | ====== Colorado Release ====== |
| Need to add pages around release planning, projects involved, infrastructure, reporting & share relevant information here. | Need to add pages around release planning, projects involved, infrastructure, reporting & share relevant information here. | ||
| Line 9: | Line 10: | ||
| * Functest R2 C wiki | * Functest R2 C wiki | ||
| * Latest results of C builds | * Latest results of C builds | ||
| + | |||
| + | |||
| ===== Overview ===== | ===== Overview ===== | ||
| - | The C release will consist of a common deployment which may be extended by feature and development projects. | + | The Colorado release will be framed around scenarios. Within OPNFV a scenario is a "deployment of a set of components and their configuration". Colorado will include all scenarios which are available and ready by the Colorado time frame. |
| + | {{:releases:opnfv_release_and_scenario_releases.pdf|Overview presentation of scenario releases.}} | ||
| - | ==== FAQ ==== | + | ==== FAQ (needs updating!) ==== |
| - | === How are different features/functions enabled for a C installation? === | + | === How are different features/functions enabled for a Colorado installation? === |
| From the Brahmaputra release onwards, a user can choose the features to be installed for a particular installation. Feature selection and the associated configuration of the features is done via a set of configuration files which are common for all installers (“install.yaml” – for general configuration and feature selection, “feature_x.yaml” – for configuration specific to a “feature_x”, like for example a SDN-controller like OpenDaylight). Note that not all features/functions are install-time features. Installers only take care of install-time features. Note that installers only install a particular feature or component, i.e. they don’t take any responsibility for the appropriate operation of a feature, component, or function. | From the Brahmaputra release onwards, a user can choose the features to be installed for a particular installation. Feature selection and the associated configuration of the features is done via a set of configuration files which are common for all installers (“install.yaml” – for general configuration and feature selection, “feature_x.yaml” – for configuration specific to a “feature_x”, like for example a SDN-controller like OpenDaylight). Note that not all features/functions are install-time features. Installers only take care of install-time features. Note that installers only install a particular feature or component, i.e. they don’t take any responsibility for the appropriate operation of a feature, component, or function. | ||
| === Several projects require specific components installed. How are their needs being met? === | === Several projects require specific components installed. How are their needs being met? === | ||
| - | === What is the role of testing and test-documentation for the C release? === | + | === What is the role of testing and test-documentation for the Colorado release? === |
| - | Test projects (i.e. Functest, Yardstick, etc.) supply a set of tests for C. C testing adds to the existing test suites available in the OPNFV Brahmaputra release. Tests which are to be run on an installation are defined by a set of test-configuration scripts. | + | Test projects (i.e. Functest, Yardstick, etc.) supply a set of tests for Colorado. Colorado testing adds to the existing test suites available in the OPNFV Brahmaputra release. Tests which are to be run on an installation are defined by a set of test-configuration scripts. |
| - | === What constitutes the C release? === | + | === What constitutes the Colorado release? === |
| A release is constituted through a set of deployments (defined by the configuration files), the associated tests (defined by the test configuration) and the corresponding test results. Note that the set of combinations tested follows interest: For a release not all possible feature/component and deployment configurations will be tested. Testing will follow the interest (and associated invested effort) of the projects participating, rather than try to test any possible combination. | A release is constituted through a set of deployments (defined by the configuration files), the associated tests (defined by the test configuration) and the corresponding test results. Note that the set of combinations tested follows interest: For a release not all possible feature/component and deployment configurations will be tested. Testing will follow the interest (and associated invested effort) of the projects participating, rather than try to test any possible combination. | ||
| - | === How will the C release be maintained? Will there be specific service releases? === | + | === How will the Colorado release be maintained? Will there be specific service releases? === |
| - | === How will C be installed? === | + | === How will Colorado be installed? === |
releases/c.1457043551.txt.gz · Last modified: 2016/03/03 22:19 by Debra Scott
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
