diff options
Diffstat (limited to 'docs/release')
5 files changed, 49 insertions, 16 deletions
diff --git a/docs/release/installation/installation.instruction.rst b/docs/release/installation/installation.instruction.rst index acf4aac4b..5d4c2cbd7 100644 --- a/docs/release/installation/installation.instruction.rst +++ b/docs/release/installation/installation.instruction.rst @@ -392,7 +392,7 @@ These steps are common both for virtual and baremetal deploys. .. code-block:: bash - $ git checkout opnfv-6.0.0 + $ git checkout opnfv-6.1.0 #. Start the deploy script diff --git a/docs/release/release-notes/release-notes.rst b/docs/release/release-notes/release-notes.rst index 5ee3bc0ff..7a2d60923 100644 --- a/docs/release/release-notes/release-notes.rst +++ b/docs/release/release-notes/release-notes.rst @@ -61,13 +61,13 @@ Release Data | **Project** | fuel/armband | | | | +--------------------------------------+--------------------------------------+ -| **Repo/tag** | opnfv-6.0.0 | +| **Repo/tag** | opnfv-6.1.0 | | | | +--------------------------------------+--------------------------------------+ -| **Release designation** | Fraser 6.0 | +| **Release designation** | Fraser 6.1 | | | | +--------------------------------------+--------------------------------------+ -| **Release date** | April 27 2018 | +| **Release date** | May 25 2018 | | | | +--------------------------------------+--------------------------------------+ | **Purpose of the delivery** | Fraser alignment to Released | @@ -85,7 +85,7 @@ Version Change Module Version Changes ---------------------- -This is the Fraser 6.0 release. +This is the Fraser 6.1 release. It is based on following upstream versions: - MCP Base Release @@ -96,7 +96,7 @@ It is based on following upstream versions: Document Changes ---------------- -This is the Fraser 6.0 release. +This is the Fraser 6.1 release. It comes with the following documentation: - :ref:`fuel-release-installation-label` @@ -112,14 +112,14 @@ Feature Additions ----------------- **JIRA TICKETS:** -`Fraser 6.0 new features <https://jira.opnfv.org/issues/?filter=12302>`_ +`Fraser 6.1 new features <https://jira.opnfv.org/issues/?filter=12306>`_ Bug Corrections --------------- **JIRA TICKETS:** -`Fraser 6.0 bug fixes <https://jira.opnfv.org/issues/?filter=12303>`_ +`Fraser 6.1 bug fixes <https://jira.opnfv.org/issues/?filter=12307>`_ (Also See respective Integrated feature project's bug tracking) @@ -163,7 +163,7 @@ Known Issues **JIRA TICKETS:** -`Known issues <https://jira.opnfv.org/issues/?filter=12304>`_ +`Known issues <https://jira.opnfv.org/issues/?filter=12308>`_ (Also See respective Integrated feature project's bug tracking) @@ -172,20 +172,20 @@ Workarounds **JIRA TICKETS:** -- +`Workarounds <https://jira.opnfv.org/issues/?filter=12309>`_ (Also See respective Integrated feature project's bug tracking) ============ Test Results ============ -The Fraser 6.0 release with the Fuel deployment tool has undergone QA test +The Fraser 6.1 release with the Fuel deployment tool has undergone QA test runs, see separate test results. ========== References ========== -For more information on the OPNFV Fraser 6.0 release, please see: +For more information on the OPNFV Fraser 6.1 release, please see: OPNFV ===== diff --git a/docs/release/scenarios/os-nosdn-ovs-ha/os-nosdn-ovs-ha.rst b/docs/release/scenarios/os-nosdn-ovs-ha/os-nosdn-ovs-ha.rst index c51a5f5b8..3a8b82b6d 100644 --- a/docs/release/scenarios/os-nosdn-ovs-ha/os-nosdn-ovs-ha.rst +++ b/docs/release/scenarios/os-nosdn-ovs-ha/os-nosdn-ovs-ha.rst @@ -2,7 +2,7 @@ .. http://creativecommons.org/licenses/by/4.0 .. (c)2017 Mirantis Inc., Enea Software AB and others -This document provides scenario level details for Fraser 6.0 of +This document provides scenario level details for Fraser 6.1 of deployment with no SDN controller and no extra features enabled. ============ diff --git a/docs/release/scenarios/os-nosdn-ovs-noha/os-nosdn-ovs-noha.rst b/docs/release/scenarios/os-nosdn-ovs-noha/os-nosdn-ovs-noha.rst index 99c4de041..5049db0c2 100644 --- a/docs/release/scenarios/os-nosdn-ovs-noha/os-nosdn-ovs-noha.rst +++ b/docs/release/scenarios/os-nosdn-ovs-noha/os-nosdn-ovs-noha.rst @@ -2,7 +2,7 @@ .. http://creativecommons.org/licenses/by/4.0 .. (c) 2017 Mirantis Inc., Enea Software AB and others -This document provides scenario level details for Fraser 6.0 of +This document provides scenario level details for Fraser 6.1 of deployment with no SDN controller and no extra features enabled. ============ diff --git a/docs/release/userguide/userguide.rst b/docs/release/userguide/userguide.rst index fd9dfa736..584948f15 100644 --- a/docs/release/userguide/userguide.rst +++ b/docs/release/userguide/userguide.rst @@ -250,9 +250,9 @@ UEFI-images for the guests: +------------------+-------------------+------------------+ | Ubuntu 14.04 | untested | Full support | +------------------+-------------------+------------------+ -| Fedora atomic 27 | untested | Not supported | +| Fedora atomic 27 | untested | Full support | +------------------+-------------------+------------------+ -| Fedora cloud 27 | untested | Not supported | +| Fedora cloud 27 | untested | Full support | +------------------+-------------------+------------------+ | Debian | untested | Full support | +------------------+-------------------+------------------+ @@ -270,6 +270,37 @@ to make. The images for the above operating systems can be found in their respective websites. + +================= +OpenStack Storage +================= + +OpenStack Cinder is the project behind block storage in OpenStack and Fuel@OPNFV supports LVM out of the box. +By default x86 supports 2 additional block storage devices and ARMBand supports only one. +More devices can be supported if the OS-image created has additional properties allowing block storage devices +to be spawned as SCSI drives. To do this, add the properties below to the server: + + .. code-block:: bash + + openstack image set --property hw_disk_bus='scsi' --property hw_scsi_model='virtio-scsi' <image> + +The choice regarding which bus to use for the storage drives is an important one. Virtio-blk is the default +choice for Fuel@OPNFV which attaches the drives in /dev/vdX. However, since we want to be able to attach a +larger number of volumes to the virtual machines, we recommend the switch to SCSI drives which are attached +in /dev/sdX instead. Virtio-scsi is a little worse in terms of performance but the ability to add a larger +number of drives combined with added features like ZFS, Ceph et al, leads us to suggest the use of virtio-scsi in Fuel@OPNFV for both architectures. + +More details regarding the differences and performance of virtio-blk vs virtio-scsi are beyond the scope +of this manual but can be easily found in other sources online like `4`_ or `5`_. + +.. _4: https://mpolednik.github.io/2017/01/23/virtio-blk-vs-virtio-scsi/ + +.. _5 : https://www.ovirt.org/develop/release-management/features/storage/virtio-scsi/ + +Additional configuration for configuring images in openstack can be found in the OpenStack Glance documentation. + + + =================== Openstack Endpoints =================== @@ -372,3 +403,5 @@ References 1) :ref:`fuel-release-installation-label` 2) `Saltstack Documentation <https://docs.saltstack.com/en/latest/topics>`_ 3) `Saltstack Formulas <http://salt-formulas.readthedocs.io/en/latest/>`_ +4) `Virtio performance <https://mpolednik.github.io/2017/01/23/virtio-blk-vs-virtio-scsi/>`_ +5) `Virtio SCSI <https://www.ovirt.org/develop/release-management/features/storage/virtio-scsi/>`_ |