Release notes for Fuel@OPNFV

1. Abstract

This document compiles the release notes for the Colorado 2.0 release of OPNFV when using Fuel as a deployment tool.

2. Important notes

These notes provides release information for the use of Fuel as deployment tool for the Colorado 2.0 release of OPNFV.

The goal of the Colorado release and this Fuel-based deployment process is to establish a lab ready platform accelerating further development of the OPNFV infrastructure.

Carefully follow the installation-instructions provided in Reference 13.

3. Summary

For Colorado, the typical use of Fuel as an OpenStack installer is supplemented with OPNFV unique components such as:

As well as OPNFV-unique configurations of the Hardware- and Software stack.

This Colorado artifact provides Fuel as the deployment stage tool in the OPNFV CI pipeline including:

  • Documentation built by Jenkins
    • overall OPNFV documentation
    • this document (release notes)
    • installation instructions
    • build-instructions
  • The Colorado Fuel installer image (.iso) built by Jenkins
  • Automated deployment of Colorado with running on bare metal or a nested hypervisor environment (KVM)
  • Automated validation of the Colorado deployment

4. Release Data

Project fuel
Repo/tag colorado.2.0
Release designation Colorado 2.0 follow-up release
Release date November 10 2016
Purpose of the delivery Colorado alignment to Released Fuel 9.0 baseline + features and bug-fixes for the following feaures: - NFV Hypervisors-KVM - Open vSwitch for NFV - OpenDaylight - ONOS - SDN distributed routing and VPN - Service function chaining - Promise - Parser - Doctor - Tacker

4.1. Version change

4.1.1. Module version changes

This is the Colorado 2.0 follow-up release. It is based on following upstream versions:

  • Fuel 9.0 Base release
  • OpenStack Mitaka release
  • OpenDaylight Boron release [1]
  • ONOS Drake release

4.1.2. Document changes

This is the Colorado 2.0 follow-up release. It comes with the following documentation:

  • Installation instructions - Reference 13 - Changed
  • Build instructions - Reference 14 - Changed
  • Release notes - Reference 15 - Changed (This document)

4.2. Reason for version

4.2.1. Feature additions

JIRA TICKETS:

4.2.2. Bug corrections

JIRA TICKETS:

Colorado 2.0 bug fixes ‘https://jira.opnfv.org/issues/?filter=11203‘

(Also See respective Integrated feature project’s bug tracking)

4.3. Deliverables

4.3.1. Software deliverables

Fuel-based installer iso file found in Reference 2

4.3.2. Documentation deliverables

  • Installation instructions - Reference 13
  • Build instructions - Reference 14
  • Release notes - Reference 15 (This document)

5. Known Limitations, Issues and Workarounds

5.1. System Limitations

  • Max number of blades: 1 Fuel master, 3 Controllers, 20 Compute blades
  • Min number of blades: 1 Fuel master, 1 Controller, 1 Compute blade
  • Storage: Ceph is the only supported storage configuration
  • Max number of networks: 65k

5.2. Known issues

JIRA TICKETS:

Known issues ‘https://jira.opnfv.org/issues/?filter=11205‘

(Also See respective Integrated feature project’s bug tracking)

5.3. Workarounds

JIRA TICKETS:

Workarounds ‘https://jira.opnfv.org/issues/?filter=11204‘

(Also See respective Integrated feature project’s bug tracking)

6. Test results

The Colorado 2.0 release with the Fuel deployment tool has undergone QA test runs, see separate test results.

7. References

For more information on the OPNFV Colorado 2.0 release, please see: