summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNarinder Gupta <narinder.gupta@canonical.com>2018-04-25 10:16:48 -0500
committerNarinder Gupta <narinder.gupta@canonical.com>2018-04-25 15:15:25 -0500
commite00115a7a5ea27030cc4f36efdc298b6145cdb02 (patch)
tree3b765aa925abd92b0b5e096141ea4525daa5a8c6
parent6345ba5917f720c00b165530916436578bd4c327 (diff)
document update for Fraser release.
Change-Id: Iab88d244a8a39b78c84aa11550cee2c04f81ab0f Signed-off-by: Narinder Gupta <narinder.gupta@canonical.com>
-rw-r--r--docs/release/configguide/configguide.rst12
-rw-r--r--docs/release/configguide/installerconfig.rst10
-rw-r--r--docs/release/configguide/postinstall.rst2
-rw-r--r--docs/release/installation/installation_baremetal.rst20
-rw-r--r--docs/release/installation/introduction.rst2
-rw-r--r--docs/release/installation/postinstall.rst2
-rw-r--r--docs/release/release-notes/release-notes.rst34
-rw-r--r--docs/release/scenarios/k8-canal-lb-noha/index.rst16
-rw-r--r--docs/release/scenarios/k8-canal-lb-noha/release-notes.rst173
-rw-r--r--docs/release/scenarios/k8-nosdn-lb-noha/release-notes.rst18
-rw-r--r--docs/release/scenarios/k8-nosdn-lb_ceph-noha/index.rst16
-rw-r--r--docs/release/scenarios/k8-nosdn-lb_ceph-noha/release-notes.rst174
-rw-r--r--docs/release/scenarios/k8-nosdn-nofeature-noha/release-notes.rst18
-rw-r--r--docs/release/scenarios/k8-ovn-lb-noha/release-notes.rst4
-rw-r--r--docs/release/scenarios/os-nosdn-lxd-ha/release-notes.rst30
-rw-r--r--docs/release/scenarios/os-nosdn-lxd-noha/release-notes.rst30
-rw-r--r--docs/release/scenarios/os-nosdn-nofeature-ha/release-notes.rst30
-rw-r--r--docs/release/scenarios/os-nosdn-nofeature-noha/release-notes.rst30
-rw-r--r--docs/release/scenarios/os-nosdn-openbaton-ha/release-notes.rst12
-rw-r--r--docs/release/userguide/userguide.rst12
20 files changed, 522 insertions, 123 deletions
diff --git a/docs/release/configguide/configguide.rst b/docs/release/configguide/configguide.rst
index 209f6cb..9db0ab3 100644
--- a/docs/release/configguide/configguide.rst
+++ b/docs/release/configguide/configguide.rst
@@ -24,4 +24,14 @@ Scenario 4: Kubernetes with OVN
Scenario 5: Openstack with Opencontrail
---------------------------------------
-*./deploy.sh -o ocata -s ocl -t ha -l custom -f none -d xenial -m openstack*
+*./deploy.sh -o pike -s ocl -t ha -l custom -f none -d xenial -m openstack*
+
+Scenario 6: Kubernetes Load Balancer with Canal CNI
+---------------------------------------------------
+
+*./deploy.sh -s canal -l custom -f lb -m kubernetes*
+
+Scenario 7: Kubernetes Load Balancer with Ceph
+----------------------------------------------
+
+*./deploy.sh -l custom -f lb,ceph -m kubernetes*
diff --git a/docs/release/configguide/installerconfig.rst b/docs/release/configguide/installerconfig.rst
index aee4ce2..86e3309 100644
--- a/docs/release/configguide/installerconfig.rst
+++ b/docs/release/configguide/installerconfig.rst
@@ -189,7 +189,7 @@ opnfv:
release: d
distro: xenial
type: noha
- openstack: newton
+ openstack: pike
sdncontroller:
- type: nosdn
storage:
@@ -244,10 +244,10 @@ When it's done, you should be able to view MAAS webpage (http://<MAAS IP>/MAAS)
OPNFV Install
-------------
-| ``   ./deploy.sh -o newton -s nosdn -t noha -l custom -f none -d xenial -m openstack``
+| ``   ./deploy.sh -o pike -s nosdn -t noha -l custom -f none -d xenial -m openstack``
| ``   ``
-./deploy.sh -o newton -s nosdn -t noha -l custom -f none -d xenial -m openstack
+./deploy.sh -o pike -s nosdn -t noha -l custom -f none -d xenial -m openstack
NOTE: Possible options are as follows:
@@ -263,9 +263,9 @@ Mode of Openstack deployed.
ha: HA mode of openstack.
Wihch version of Openstack deployed.
- [-o|--openstack <ocata|newton>]
+ [-o|--openstack <pike|ocata>]
+ pike: Pike version of openstack.
Ocata: Ocata version of openstack.
- Newton: Newton version of openstack.
Where to deploy
[-l|--lab <custom | default>] etc...
diff --git a/docs/release/configguide/postinstall.rst b/docs/release/configguide/postinstall.rst
index 49388b1..519eb4f 100644
--- a/docs/release/configguide/postinstall.rst
+++ b/docs/release/configguide/postinstall.rst
@@ -6,7 +6,7 @@ Configure OpenStack
openstack.sh under joid/ci used to configure the openstack after deployment
-./openstack.sh <nosdn> custom xenial newton
+./openstack.sh <nosdn> custom xenial pike
Below commands are used to setup domain in heat.
juju run-action heat/0 domain-setup
diff --git a/docs/release/installation/installation_baremetal.rst b/docs/release/installation/installation_baremetal.rst
index 3b7d0cc..567ab64 100644
--- a/docs/release/installation/installation_baremetal.rst
+++ b/docs/release/installation/installation_baremetal.rst
@@ -117,7 +117,7 @@ home directory.
::
- git clone -b stable/danube https://gerrit.opnfv.org/gerrit/p/joid.git
+ git clone -b stable/fraser https://gerrit.opnfv.org/gerrit/p/joid.git
Create a directory in ``joid/labconfig/<company_name>/<pod_number>/`` and
create or copy a ``labconfig.yaml`` configuration file to that directory.
@@ -221,7 +221,7 @@ Example ``labconfig.yaml`` configuration file:
release: d
distro: xenial
type: noha
- openstack: ocata
+ openstack: pike
sdncontroller:
- type: nosdn
storage:
@@ -323,7 +323,7 @@ This section will guide you through the Juju an OPNFV deployment. This is the
second of two JOID deployment steps.
JOID allows you to deploy different combinations of OpenStack and SDN solutions
-in HA or no-HA mode. For OpenStack, it supports Newton and Ocata. For SDN, it
+in HA or no-HA mode. For OpenStack, it supports Pike and Ocata. For SDN, it
supports Open vSwitch, OpenContrail, OpenDaylight and ONOS (Open Network
Operating System). In addition to HA or no-HA mode, it also supports deploying
the latest from the development tree (tip).
@@ -334,10 +334,10 @@ script. For example:
::
# in joid/ci directory
- ./deploy.sh -d xenial -m openstack -o ocata -s nosdn -f none -t noha -l custom
+ ./deploy.sh -d xenial -m openstack -o pike -s nosdn -f none -t noha -l custom
The above command starts an OPNFV deployment with Ubuntu Xenial (16.04) distro,
-OpenStack model, Ocata version of OpenStack, Open vSwitch (and no other SDN),
+OpenStack model, Pike version of OpenStack, Open vSwitch (and no other SDN),
no special features, no-HA OpenStack mode and with custom labconfig. I.e. this
corresponds to the ``os-nosdn-nofeature-noha`` OPNFV deployment scenario.
@@ -373,20 +373,21 @@ corresponds to the ``os-nosdn-nofeature-noha`` OPNFV deployment scenario.
**Version of Openstack deployed**
::
- [-o <newton|mitaka>]
+ [-o <pike|ocata>]
- - ``newton``: Newton version of OpenStack.
+ - ``pike``: Pike version of OpenStack.
- ``ocata``: Ocata version of OpenStack.
**SDN controller**
::
- [-s <nosdn|odl|opencontrail|onos>]
+ [-s <nosdn|odl|opencontrail|onos|canal>]
- ``nosdn``: Open vSwitch only and no other SDN.
- ``odl``: OpenDayLight Boron version.
- ``opencontrail``: OpenContrail SDN.
- ``onos``: ONOS framework as SDN.
+ - ``cana;``: canal CNI plugin for kubernetes.
**Feature to deploy** (comma separated list)
::
@@ -400,6 +401,7 @@ corresponds to the ``os-nosdn-nofeature-noha`` OPNFV deployment scenario.
- ``dpdk``: Will enable DPDK feature.
- ``sfc``: Will enable sfc feature only supported with ONOS deployment.
- ``lb``: Load balancing in case of Kubernetes will be enabled.
+ - ``ceph``: Ceph storage Kubernetes will be enabled.
**Mode of Openstack deployed**
::
@@ -553,7 +555,7 @@ The following are the common issues we have collected from the community:
::
- ./deploy.sh -o newton -s nosdn -t ha -l custom -f none
+ ./deploy.sh -o pike -s nosdn -t ha -l custom -f none
- If you have not setup MAAS with ``03-maasdeploy.sh`` then the
``./clean.sh`` command could hang, the ``juju status`` command may hang
diff --git a/docs/release/installation/introduction.rst b/docs/release/installation/introduction.rst
index 52e04f2..846792c 100644
--- a/docs/release/installation/introduction.rst
+++ b/docs/release/installation/introduction.rst
@@ -5,7 +5,7 @@ JOID in brief
-------------
JOID as *Juju OPNFV Infrastructure Deployer* allows you to deploy different
combinations of OpenStack release and SDN solution in HA or non-HA mode. For
-OpenStack, JOID currently supports Newton and Ocata. For SDN, it supports
+OpenStack, JOID currently supports Ocata and Pike. For SDN, it supports
Openvswitch, OpenContrail, OpenDayLight, and ONOS. In addition to HA or non-HA
mode, it also supports deploying from the latest development tree.
diff --git a/docs/release/installation/postinstall.rst b/docs/release/installation/postinstall.rst
index 750ea4a..3320ba0 100644
--- a/docs/release/installation/postinstall.rst
+++ b/docs/release/installation/postinstall.rst
@@ -67,7 +67,7 @@ OpenStack after deployment.
::
- ./openstack.sh <nosdn> custom xenial newton
+ ./openstack.sh <nosdn> custom xenial pike
Below commands are used to setup domain in heat.
diff --git a/docs/release/release-notes/release-notes.rst b/docs/release/release-notes/release-notes.rst
index e86521b..5c1f1c1 100644
--- a/docs/release/release-notes/release-notes.rst
+++ b/docs/release/release-notes/release-notes.rst
@@ -1,4 +1,4 @@
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+/. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) <optionally add copywriters name>
@@ -26,17 +26,17 @@ Summary
=======
The Fraser release with the JOID deployment toolchain will establish an OPNFV target system on a Pharos compliant lab infrastructure.
-The current definition of an OPNFV target system is and OpenStack Newton combined with OpenDaylight Boron.
+The current definition of an OPNFV target system is and OpenStack Pike combined with OpenDaylight Boron.
The system is deployed with OpenStack High Availability (HA) for most OpenStack services.
Ceph storage is used as Cinder backend, and is the only supported storage for Fraser. Ceph is setup as 3 OSDs and 3 Monitors, one radosgw.
User has following choices to make to do the deployment.
- - Openstack -- Newton
+ - Openstack -- Pike
- Type -- HA, nonHA, tip (stable git branch of respective openstack)
- - SDN controller -- OpenDaylight, nosdn(Openvswitch), Onos, OpenContrail
- - Feature -- IPV6, DVR(distributed virtual routing), SFC(service function chaining odl only), BGPVPN(odl only), LB(Load Balancer for Kubernetes)
+ - SDN controller -- nosdn(Openvswitch), Onos, OpenContrail, Canal(k8), OVN (K8)
+ - Feature -- IPV6, DVR(distributed virtual routing), ceph(Kubernetes storage), LB(Load Balancer for Kubernetes)
- Distro -- Xenial
- Model -- Openstack, Kubernetes
@@ -54,15 +54,15 @@ Release Data
| | |
+--------------------------------------+--------------------------------------+
| **Repo/tag** | gerrit.opnfv.org/gerrit/joid.git |
-| | stable/fraser |
+| | opnfv-6.0.0 |
+--------------------------------------+--------------------------------------+
-| **Release designation** | Fraser release |
+| **Release designation** | Fraser release |
| | |
+--------------------------------------+--------------------------------------+
-| **Release date** | December 15 2017 |
+| **Release date** | April 27 2018 |
| | |
+--------------------------------------+--------------------------------------+
-| **Purpose of the delivery** | Fraser release |
+| **Purpose of the delivery** | Fraser release |
| | |
+--------------------------------------+--------------------------------------+
@@ -87,7 +87,7 @@ Version change
Module version change
~~~~~~~~~~~~~~~~~~~~~
- Fraser release with the JOID deployment toolchain.
- - OpenStack (Ocata release)
+ - OpenStack (Pike release)
- Kubernetes 1.8
- Ubuntu 16.04 LTS
@@ -116,7 +116,7 @@ Feature additions
+--------------------------------------+--------------------------------------+
| JIRA: JOID-106 | Kubernetes on Baremetal |
+--------------------------------------+--------------------------------------+
-| JIRA: JOID-102 | Enable OpenStack Ocata |
+| JIRA: | Enable OpenStack Pike |
+--------------------------------------+--------------------------------------+
| | Enable OpenContrail |
+--------------------------------------+--------------------------------------+
@@ -203,6 +203,14 @@ Name: joid-os-ocl-nofeature-noha
Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-ocl-nofeature-noha-baremetal-daily-fraser/
Notes:
+Name: joid-k8-canal-lb-noha
+Test Link: https://build.opnfv.org/ci/view/joid/job/joid-k8-canal-lb-noha-baremetal-daily-fraser/
+Notes:
+
+Name: joid-k8-nosdn-lb_ceph-noha
+Test Link: https://build.opnfv.org/ci/view/joid/job/joid-k8-nosdn-lb_ceph-noha-baremetal-daily-fraser/
+Notes:
+
References
==========
For more information on the OPNFV Fraser release, please visit
@@ -221,12 +229,12 @@ MAAS
JOID
----
- `OPNFV JOID wiki <https://wiki.opnfv.org/joid>`_
-- `OPNFV Release Notes <http://docs.opnfv.org/en/stable-danube/submodules/joid/docs/release/release-notes/release-notes.html>`_
+- `OPNFV Release Notes <http://docs.opnfv.org/en/stable-fraser/submodules/joid/docs/release/release-notes/release-notes.html>`_
- `OPNFV JOID Install Guide <http://docs.opnfv.org/en/latest/submodules/joid/docs/release/installation/index.html>`_
OpenStack
---------
-- `OpenStack Newton Release artifacts <http://www.openstack.org/software/ocata>`_
+- `OpenStack Pike Release artifacts <http://www.openstack.org/software/pike>`_
- `OpenStack documentation <http://docs.openstack.org>`_
OpenDaylight
diff --git a/docs/release/scenarios/k8-canal-lb-noha/index.rst b/docs/release/scenarios/k8-canal-lb-noha/index.rst
new file mode 100644
index 0000000..ff273d4
--- /dev/null
+++ b/docs/release/scenarios/k8-canal-lb-noha/index.rst
@@ -0,0 +1,16 @@
+.. _k8-canal-lb-noha:
+
+.. This work is licensed under a Creative Commons Attribution 4.0 International Licence.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) <optionally add copywriters name>
+
+=============================
+JOID Kubernetes Release Notes
+=============================
+
+.. toctree::
+ :numbered:
+ :maxdepth: 4
+
+ release-notes.rst
+
diff --git a/docs/release/scenarios/k8-canal-lb-noha/release-notes.rst b/docs/release/scenarios/k8-canal-lb-noha/release-notes.rst
new file mode 100644
index 0000000..1248cf1
--- /dev/null
+++ b/docs/release/scenarios/k8-canal-lb-noha/release-notes.rst
@@ -0,0 +1,173 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) <optionally add copywriters name>
+
+
+Abstract
+========
+
+This document compiles the release notes for the Fraser release of
+OPNFV when using JOID as a deployment tool for Kubernetes with cancal CNI.
+
+Introduction
+============
+
+These notes provides release information for the use of joid as deployment
+tool for the Fraser release of OPNFV for Kubernetes scenario.
+
+The goal of the Fraser release and this JOID based deployment process is
+to establish a lab ready platform accelerating further development
+of the OPNFV infrastructure for docker based workloads.
+
+Carefully follow the installation-instructions which guides a user to deploy
+OPNFV using JOID which is based on MAAS and Juju.
+
+Summary
+=======
+
+Kubernetes is an open-source system for automating deployment, scaling, and
+management of containerized applications.
+
+This is a Kubernetes cluster that includes logging, monitoring, and operational
+knowledge. It is comprised of the following components and features:
+
+Kubernetes (automated deployment, operations, and scaling)
+ TLS used for communication between nodes for security.
+ A CNI plugin (e.g., Canal)
+ Optional Ingress Controller (on worker)
+ Optional Dashboard addon (on master) including Heapster for cluster monitoring
+
+EasyRSA
+ Performs the role of a certificate authority serving self signed certificates
+ to the requesting units of the cluster.
+
+Etcd (distributed key value store)
+ Minimum Three node cluster for reliability.
+
+Fraser release with the JOID deployment with Kubernetes will establish an
+OPNFV target system on a Pharos compliant lab infrastructure.
+
+NOTE: Detailed information on how to install in your lab can be find in installation guide
+command to deploy lxd feature is:
+
+#Kubernetes deployment
+./deploy.sh -m kubernetes -f lb -l custom -s canal
+
+Using Kubernetes after Deployment
+=================================
+
+Once you have finished installinf the JOID with Kubernetes you can use the
+following command to test the deployment.
+
+To deploy 5 replicas of the microbot web application inside the Kubernetes
+cluster run the following command:
+
+juju run-action kubernetes-worker/0 microbot replicas=5
+
+This action performs the following steps:
+
+It creates a deployment titled 'microbots' comprised of 5 replicas defined
+during the run of the action. It also creates a service named 'microbots'
+which binds an 'endpoint', using all 5 of the 'microbots' pods.
+Finally, it will create an ingress resource, which points at a
+xip.io domain to simulate a proper DNS service.
+
+Running the packaged example
+
+You can run a Juju action to create an example microbot web application:
+
+$ juju run-action kubernetes-worker/0 microbot replicas=3
+Action queued with id: db7cc72b-5f35-4a4d-877c-284c4b776eb8
+
+$ juju show-action-output db7cc72b-5f35-4a4d-877c-284c4b776eb8
+results:
+ address: microbot.104.198.77.197.xip.io
+status: completed
+timing:
+ completed: 2016-09-26 20:42:42 +0000 UTC
+ enqueued: 2016-09-26 20:42:39 +0000 UTC
+ started: 2016-09-26 20:42:41 +0000 UTC
+Note: Your FQDN will be different and contain the address of the cloud
+instance.
+At this point, you can inspect the cluster to observe the workload coming
+online.
+
+Mor einformation on using Canonical distribution of kubernetes can be found
+at https://jujucharms.com/canonical-kubernetes/
+
+Release Data
+============
+
++--------------------------------------+--------------------------------------+
+| **Project** | JOID |
+| | |
++--------------------------------------+--------------------------------------+
+| **Repo/tag** | gerrit.opnfv.org/gerrit/joid.git |
+| | opnfv-6.0.0 |
++--------------------------------------+--------------------------------------+
+| **Release designation** | Fraser release |
+| | |
++--------------------------------------+--------------------------------------+
+| **Release date** | April 27 2018 |
+| | |
++--------------------------------------+--------------------------------------+
+| **Purpose of the delivery** | Fraser release |
+| | |
++--------------------------------------+--------------------------------------+
+
+Deliverables
+------------
+
+Software deliverables
+~~~~~~~~~~~~~~~~~~~~~
+`JOID based installer script files <https://gerrit.opnfv.org/gerrit/gitweb?p=joid.git>`_
+
+Known Limitations, Issues and Workarounds
+=========================================
+
+Known issues
+------------
+
+**JIRA TICKETS:**
+
++--------------------------------------+--------------------------------------+
+| **JIRA REFERENCE** | **SLOGAN** |
+| | |
++--------------------------------------+--------------------------------------+
+| JIRA: | No support for yardstick and functest|
+| | for Kubernetes scenarios (OPNFV) |
++--------------------------------------+--------------------------------------+
+| JIRA: | |
++--------------------------------------+--------------------------------------+
+
+
+Scenario Releases
+=================
+Name: joid-k8-canal-lb-noha
+Test Link: https://build.opnfv.org/ci/user/narindergupta/my-views/view/joid/job/joid-k8-canal-lb-noha-baremetal-daily-fraser/
+Notes:
+
+References
+==========
+
+Juju
+----
+- `Juju Charm store <https://jujucharms.com/>`_
+- `Juju documents <https://jujucharms.com/docs/stable/getting-started>`_
+- `Canonical Distibuytion of Kubernetes <https://jujucharms.com/canonical-kubernetes/>`_
+
+MAAS
+----
+- `Bare metal management (Metal-As-A-Service) <http://maas.io/get-started>`_
+- `MAAS API documents <http://maas.ubuntu.com/docs/>`_
+
+JOID
+----
+- `OPNFV JOID wiki <https://wiki.opnfv.org/joid>`_
+- `OPNFV JOID Get Started <https://wiki.opnfv.org/display/joid/JOID+Get+Started>`_
+
+Kubernetes
+----------
+- `Kubernetes Release artifacts <https://get.k8s.io/>`_
+- `Kubernetes documentation <https://kubernetes.io/>`_
+
diff --git a/docs/release/scenarios/k8-nosdn-lb-noha/release-notes.rst b/docs/release/scenarios/k8-nosdn-lb-noha/release-notes.rst
index a5ebd32..6d49a3c 100644
--- a/docs/release/scenarios/k8-nosdn-lb-noha/release-notes.rst
+++ b/docs/release/scenarios/k8-nosdn-lb-noha/release-notes.rst
@@ -6,17 +6,17 @@
Abstract
========
-This document compiles the release notes for the Danube release of
+This document compiles the release notes for the Fraser release of
OPNFV when using JOID as a deployment tool for Kubernets and load balancer.
Introduction
============
These notes provides release information for the use of joid as deployment
-tool for the Danube release of OPNFV for Kubernets and load balancer
+tool for the Fraser release of OPNFV for Kubernets and load balancer
scenario.
-The goal of the Danube release and this JOID based deployment process is
+The goal of the Fraser release and this JOID based deployment process is
to establish a lab ready platform accelerating further development
of the OPNFV infrastructure for docker based workloads.
@@ -46,7 +46,7 @@ EasyRSA
Etcd (distributed key value store)
Minimum Three node cluster for reliability.
-Danube release with the JOID deployment with Kubernetes with load balancer will establish an
+Fraser release with the JOID deployment with Kubernetes with load balancer will establish an
OPNFV target system on a Pharos compliant lab infrastructure.
NOTE: Detailed information on how to install in your lab can be find in installation guide
@@ -105,15 +105,15 @@ Release Data
| | |
+--------------------------------------+--------------------------------------+
| **Repo/tag** | gerrit.opnfv.org/gerrit/joid.git |
-| | stable/danube |
+| | opnfv-6.0.0 |
+--------------------------------------+--------------------------------------+
-| **Release designation** | Danube release |
+| **Release designation** | Fraser release |
| | |
+--------------------------------------+--------------------------------------+
-| **Release date** | March 31 2017 |
+| **Release date** | April 27 2018 |
| | |
+--------------------------------------+--------------------------------------+
-| **Purpose of the delivery** | Danube release |
+| **Purpose of the delivery** | Fraser release |
| | |
+--------------------------------------+--------------------------------------+
@@ -146,7 +146,7 @@ Known issues
Scenario Releases
=================
Name: joid-k8-nosdn-lb-noha
-Test Link: https://build.opnfv.org/ci/view/joid/job/joid-k8-nosdn-lb-noha-baremetal-daily-danube/
+Test Link: https://build.opnfv.org/ci/view/joid/job/joid-k8-nosdn-lb-noha-baremetal-daily-fraser/
Notes:
References
diff --git a/docs/release/scenarios/k8-nosdn-lb_ceph-noha/index.rst b/docs/release/scenarios/k8-nosdn-lb_ceph-noha/index.rst
new file mode 100644
index 0000000..b17b628
--- /dev/null
+++ b/docs/release/scenarios/k8-nosdn-lb_ceph-noha/index.rst
@@ -0,0 +1,16 @@
+.. _k8-nosdn-lb_ceph-noha:
+
+.. This work is licensed under a Creative Commons Attribution 4.0 International Licence.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) <optionally add copywriters name>
+
+=============================
+JOID Kubernetes Release Notes
+=============================
+
+.. toctree::
+ :numbered:
+ :maxdepth: 4
+
+ release-notes.rst
+
diff --git a/docs/release/scenarios/k8-nosdn-lb_ceph-noha/release-notes.rst b/docs/release/scenarios/k8-nosdn-lb_ceph-noha/release-notes.rst
new file mode 100644
index 0000000..2d1c791
--- /dev/null
+++ b/docs/release/scenarios/k8-nosdn-lb_ceph-noha/release-notes.rst
@@ -0,0 +1,174 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) <optionally add copywriters name>
+
+
+Abstract
+========
+
+This document compiles the release notes for the Fraser release of
+OPNFV when using JOID as a deployment tool for Kubernetes with cancal CNI.
+
+Introduction
+============
+
+These notes provides release information for the use of joid as deployment
+tool for the Fraser release of OPNFV for Kubernetes scenario.
+
+The goal of the Fraser release and this JOID based deployment process is
+to establish a lab ready platform accelerating further development
+of the OPNFV infrastructure for docker based workloads.
+
+Carefully follow the installation-instructions which guides a user to deploy
+OPNFV using JOID which is based on MAAS and Juju.
+
+Summary
+=======
+
+Kubernetes is an open-source system for automating deployment, scaling, and
+management of containerized applications.
+
+This is a Kubernetes cluster that includes logging, monitoring, and operational
+knowledge. It is comprised of the following components and features:
+
+Kubernetes (automated deployment, operations, and scaling)
+ TLS used for communication between nodes for security.
+ A CNI plugin (e.g., Canal)
+ Ceph based storage solution ( LXD container)
+ Optional Ingress Controller (on worker)
+ Optional Dashboard addon (on master) including Heapster for cluster monitoring
+
+EasyRSA
+ Performs the role of a certificate authority serving self signed certificates
+ to the requesting units of the cluster.
+
+Etcd (distributed key value store)
+ Minimum Three node cluster for reliability.
+
+Fraser release with the JOID deployment with Kubernetes will establish an
+OPNFV target system on a Pharos compliant lab infrastructure.
+
+NOTE: Detailed information on how to install in your lab can be find in installation guide
+command to deploy lxd feature is:
+
+#Kubernetes deployment
+./deploy.sh -m kubernetes -f lb,ceph -l custom
+
+Using Kubernetes after Deployment
+=================================
+
+Once you have finished installinf the JOID with Kubernetes you can use the
+following command to test the deployment.
+
+To deploy 5 replicas of the microbot web application inside the Kubernetes
+cluster run the following command:
+
+juju run-action kubernetes-worker/0 microbot replicas=5
+
+This action performs the following steps:
+
+It creates a deployment titled 'microbots' comprised of 5 replicas defined
+during the run of the action. It also creates a service named 'microbots'
+which binds an 'endpoint', using all 5 of the 'microbots' pods.
+Finally, it will create an ingress resource, which points at a
+xip.io domain to simulate a proper DNS service.
+
+Running the packaged example
+
+You can run a Juju action to create an example microbot web application:
+
+$ juju run-action kubernetes-worker/0 microbot replicas=3
+Action queued with id: db7cc72b-5f35-4a4d-877c-284c4b776eb8
+
+$ juju show-action-output db7cc72b-5f35-4a4d-877c-284c4b776eb8
+results:
+ address: microbot.104.198.77.197.xip.io
+status: completed
+timing:
+ completed: 2016-09-26 20:42:42 +0000 UTC
+ enqueued: 2016-09-26 20:42:39 +0000 UTC
+ started: 2016-09-26 20:42:41 +0000 UTC
+Note: Your FQDN will be different and contain the address of the cloud
+instance.
+At this point, you can inspect the cluster to observe the workload coming
+online.
+
+Mor einformation on using Canonical distribution of kubernetes can be found
+at https://jujucharms.com/canonical-kubernetes/
+
+Release Data
+============
+
++--------------------------------------+--------------------------------------+
+| **Project** | JOID |
+| | |
++--------------------------------------+--------------------------------------+
+| **Repo/tag** | gerrit.opnfv.org/gerrit/joid.git |
+| | opnfv-6.0.0 |
++--------------------------------------+--------------------------------------+
+| **Release designation** | Fraser release |
+| | |
++--------------------------------------+--------------------------------------+
+| **Release date** | April 27 2018 |
+| | |
++--------------------------------------+--------------------------------------+
+| **Purpose of the delivery** | Fraser release |
+| | |
++--------------------------------------+--------------------------------------+
+
+Deliverables
+------------
+
+Software deliverables
+~~~~~~~~~~~~~~~~~~~~~
+`JOID based installer script files <https://gerrit.opnfv.org/gerrit/gitweb?p=joid.git>`_
+
+Known Limitations, Issues and Workarounds
+=========================================
+
+Known issues
+------------
+
+**JIRA TICKETS:**
+
++--------------------------------------+--------------------------------------+
+| **JIRA REFERENCE** | **SLOGAN** |
+| | |
++--------------------------------------+--------------------------------------+
+| JIRA: | No support for yardstick and functest|
+| | for Kubernetes scenarios (OPNFV) |
++--------------------------------------+--------------------------------------+
+| JIRA: | |
++--------------------------------------+--------------------------------------+
+
+
+Scenario Releases
+=================
+Name: joid-k8-nosdn-lb_ceph-noha
+Test Link: https://build.opnfv.org/ci/user/narindergupta/my-views/view/joid/job/joid-k8-nosdn-lb_ceph-noha-baremetal-daily-fraser/
+Notes:
+
+References
+==========
+
+Juju
+----
+- `Juju Charm store <https://jujucharms.com/>`_
+- `Juju documents <https://jujucharms.com/docs/stable/getting-started>`_
+- `Canonical Distibuytion of Kubernetes <https://jujucharms.com/canonical-kubernetes/>`_
+
+MAAS
+----
+- `Bare metal management (Metal-As-A-Service) <http://maas.io/get-started>`_
+- `MAAS API documents <http://maas.ubuntu.com/docs/>`_
+
+JOID
+----
+- `OPNFV JOID wiki <https://wiki.opnfv.org/joid>`_
+- `OPNFV JOID Get Started <https://wiki.opnfv.org/display/joid/JOID+Get+Started>`_
+
+Kubernetes
+----------
+- `Kubernetes Release artifacts <https://get.k8s.io/>`_
+- `Kubernetes documentation <https://kubernetes.io/>`_
+
diff --git a/docs/release/scenarios/k8-nosdn-nofeature-noha/release-notes.rst b/docs/release/scenarios/k8-nosdn-nofeature-noha/release-notes.rst
index c9ad436..ad35634 100644
--- a/docs/release/scenarios/k8-nosdn-nofeature-noha/release-notes.rst
+++ b/docs/release/scenarios/k8-nosdn-nofeature-noha/release-notes.rst
@@ -6,16 +6,16 @@
Abstract
========
-This document compiles the release notes for the Danube release of
+This document compiles the release notes for the Fraser release of
OPNFV when using JOID as a deployment tool for Kubernetes.
Introduction
============
These notes provides release information for the use of joid as deployment
-tool for the Danube release of OPNFV for Kubernetes scenario.
+tool for the Fraser release of OPNFV for Kubernetes scenario.
-The goal of the Danube release and this JOID based deployment process is
+The goal of the Fraser release and this JOID based deployment process is
to establish a lab ready platform accelerating further development
of the OPNFV infrastructure for docker based workloads.
@@ -44,7 +44,7 @@ EasyRSA
Etcd (distributed key value store)
Minimum Three node cluster for reliability.
-Danube release with the JOID deployment with Kubernetes will establish an
+Fraser release with the JOID deployment with Kubernetes will establish an
OPNFV target system on a Pharos compliant lab infrastructure.
NOTE: Detailed information on how to install in your lab can be find in installation guide
@@ -103,15 +103,15 @@ Release Data
| | |
+--------------------------------------+--------------------------------------+
| **Repo/tag** | gerrit.opnfv.org/gerrit/joid.git |
-| | stable/danube |
+| | opnfv-6.0.0 |
+--------------------------------------+--------------------------------------+
-| **Release designation** | Danube release |
+| **Release designation** | Fraser release |
| | |
+--------------------------------------+--------------------------------------+
-| **Release date** | March 31 2017 |
+| **Release date** | April 27 2018 |
| | |
+--------------------------------------+--------------------------------------+
-| **Purpose of the delivery** | Danube release |
+| **Purpose of the delivery** | Fraser release |
| | |
+--------------------------------------+--------------------------------------+
@@ -144,7 +144,7 @@ Known issues
Scenario Releases
=================
Name: joid-k8-nosdn-nofeature-noha
-Test Link: https://build.opnfv.org/ci/view/joid/job/joid-k8-nosdn-nofeature-noha-baremetal-daily-danube/
+Test Link: https://build.opnfv.org/ci/view/joid/job/joid-k8-nosdn-nofeature-noha-baremetal-daily-fraser/
Notes:
References
diff --git a/docs/release/scenarios/k8-ovn-lb-noha/release-notes.rst b/docs/release/scenarios/k8-ovn-lb-noha/release-notes.rst
index 0a9938e..2a0ba98 100644
--- a/docs/release/scenarios/k8-ovn-lb-noha/release-notes.rst
+++ b/docs/release/scenarios/k8-ovn-lb-noha/release-notes.rst
@@ -105,12 +105,12 @@ Release Data
| | |
+--------------------------------------+--------------------------------------+
| **Repo/tag** | gerrit.opnfv.org/gerrit/joid.git |
-| | stable/fraser |
+| | opnfv-6.0.0 |
+--------------------------------------+--------------------------------------+
| **Release designation** | Fraser release |
| | |
+--------------------------------------+--------------------------------------+
-| **Release date** | March 31 2018 |
+| **Release date** | April 27 2018 |
| | |
+--------------------------------------+--------------------------------------+
| **Purpose of the delivery** | Fraser release |
diff --git a/docs/release/scenarios/os-nosdn-lxd-ha/release-notes.rst b/docs/release/scenarios/os-nosdn-lxd-ha/release-notes.rst
index 96afbec..7bfdc6d 100644
--- a/docs/release/scenarios/os-nosdn-lxd-ha/release-notes.rst
+++ b/docs/release/scenarios/os-nosdn-lxd-ha/release-notes.rst
@@ -6,17 +6,17 @@
Abstract
========
-This document compiles the release notes for the Danube release of
+This document compiles the release notes for the Fraser release of
OPNFV when using JOID as a deployment tool with LXD container hypervisor.
Introduction
============
These notes provides release information for the use of joid as deployment
-tool for the Danube release of OPNFV with LXD hypervisor for containers
+tool for the Fraser release of OPNFV with LXD hypervisor for containers
scenario.
-The goal of the Danube release and this JOID based deployment process is
+The goal of the Fraser release and this JOID based deployment process is
to establish a lab ready platform accelerating further development
of the OPNFV infrastructure.
@@ -32,16 +32,16 @@ the container will look and feel like a regular VM – but will act like a
container. LXD uses the same container technology found in the Linux kernel
(cgroups, namespaces, LSM, etc).
-Danube release with the JOID deployment with LXD hypervisor will establish an
+Fraser release with the JOID deployment with LXD hypervisor will establish an
OPNFV target system on a Pharos compliant lab infrastructure.
-The current definition of an OPNFV target system is and OpenStack Newton combined
+The current definition of an OPNFV target system is and OpenStack Pike combined
with LXD Hypervisor.
The system is deployed with OpenStack High Availability (HA) for most OpenStack services.
User has following choices to make to do the deployment.
- - Openstack -- Newton
+ - Openstack -- Pike
- Type -- HA, nonHA, tip (stable git branch of respective openstack)
- Feature -- LXD (container hypervisor)
@@ -49,10 +49,10 @@ NOTE: Detailed information on how to install in your lab can be find in installa
command to deploy lxd feature is:
#LXD deployment with HA Openstack
-./deploy.sh -o newton -f lxd -t ha -l custom -s nosdn
+./deploy.sh -o pike -f lxd -t ha -l custom -s nosdn
#LXD deployment with no HA Openstack
-./deploy.sh -o newton -f lxd -t noha -l custom -s nosdn
+./deploy.sh -o pike -f lxd -t noha -l custom -s nosdn
Using LXD with Openstack
========================
@@ -79,15 +79,15 @@ Release Data
| | |
+--------------------------------------+--------------------------------------+
| **Repo/tag** | gerrit.opnfv.org/gerrit/joid.git |
-| | stable/danube |
+| | opnfv-6.0.0 |
+--------------------------------------+--------------------------------------+
-| **Release designation** | Danube release |
+| **Release designation** | Fraser release |
| | |
+--------------------------------------+--------------------------------------+
-| **Release date** | April 01 2017 |
+| **Release date** | April 27 2018 |
| | |
+--------------------------------------+--------------------------------------+
-| **Purpose of the delivery** | Danube release |
+| **Purpose of the delivery** | Fraser release |
| | |
+--------------------------------------+--------------------------------------+
@@ -120,11 +120,11 @@ Known issues
Scenario Releases
=================
Name: joid-os-nosdn-lxd-ha
-Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-nosdn-lxd-ha-baremetal-daily-danube/
+Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-nosdn-lxd-ha-baremetal-daily-fraser/
Notes:
Name: joid-os-nosdn-lxd-noha
-Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-nosdn-lxd-noha-baremetal-daily-danube/
+Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-nosdn-lxd-noha-baremetal-daily-fraser/
Notes:
References
@@ -152,6 +152,6 @@ JOID
OpenStack
---------
-- `OpenStack Newton Release artifacts <http://www.openstack.org/software/newton>`_
+- `OpenStack Pike Release artifacts <http://www.openstack.org/software/pike>`_
- `OpenStack documentation <http://docs.openstack.org>`_
diff --git a/docs/release/scenarios/os-nosdn-lxd-noha/release-notes.rst b/docs/release/scenarios/os-nosdn-lxd-noha/release-notes.rst
index 96afbec..327736b 100644
--- a/docs/release/scenarios/os-nosdn-lxd-noha/release-notes.rst
+++ b/docs/release/scenarios/os-nosdn-lxd-noha/release-notes.rst
@@ -6,17 +6,17 @@
Abstract
========
-This document compiles the release notes for the Danube release of
+This document compiles the release notes for the Fraser release of
OPNFV when using JOID as a deployment tool with LXD container hypervisor.
Introduction
============
These notes provides release information for the use of joid as deployment
-tool for the Danube release of OPNFV with LXD hypervisor for containers
+tool for the Fraser release of OPNFV with LXD hypervisor for containers
scenario.
-The goal of the Danube release and this JOID based deployment process is
+The goal of the Fraser release and this JOID based deployment process is
to establish a lab ready platform accelerating further development
of the OPNFV infrastructure.
@@ -32,16 +32,16 @@ the container will look and feel like a regular VM – but will act like a
container. LXD uses the same container technology found in the Linux kernel
(cgroups, namespaces, LSM, etc).
-Danube release with the JOID deployment with LXD hypervisor will establish an
+Fraser release with the JOID deployment with LXD hypervisor will establish an
OPNFV target system on a Pharos compliant lab infrastructure.
-The current definition of an OPNFV target system is and OpenStack Newton combined
+The current definition of an OPNFV target system is and OpenStack Pike combined
with LXD Hypervisor.
The system is deployed with OpenStack High Availability (HA) for most OpenStack services.
User has following choices to make to do the deployment.
- - Openstack -- Newton
+ - Openstack -- Pike
- Type -- HA, nonHA, tip (stable git branch of respective openstack)
- Feature -- LXD (container hypervisor)
@@ -49,10 +49,10 @@ NOTE: Detailed information on how to install in your lab can be find in installa
command to deploy lxd feature is:
#LXD deployment with HA Openstack
-./deploy.sh -o newton -f lxd -t ha -l custom -s nosdn
+./deploy.sh -o pike -f lxd -t ha -l custom -s nosdn
#LXD deployment with no HA Openstack
-./deploy.sh -o newton -f lxd -t noha -l custom -s nosdn
+./deploy.sh -o pike -f lxd -t noha -l custom -s nosdn
Using LXD with Openstack
========================
@@ -79,15 +79,15 @@ Release Data
| | |
+--------------------------------------+--------------------------------------+
| **Repo/tag** | gerrit.opnfv.org/gerrit/joid.git |
-| | stable/danube |
+| | opnfv-6.0.0 |
+--------------------------------------+--------------------------------------+
-| **Release designation** | Danube release |
+| **Release designation** | Fraser release |
| | |
+--------------------------------------+--------------------------------------+
-| **Release date** | April 01 2017 |
+| **Release date** | April 30 2019 |
| | |
+--------------------------------------+--------------------------------------+
-| **Purpose of the delivery** | Danube release |
+| **Purpose of the delivery** | Fraser release |
| | |
+--------------------------------------+--------------------------------------+
@@ -120,11 +120,11 @@ Known issues
Scenario Releases
=================
Name: joid-os-nosdn-lxd-ha
-Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-nosdn-lxd-ha-baremetal-daily-danube/
+Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-nosdn-lxd-ha-baremetal-daily-fraser/
Notes:
Name: joid-os-nosdn-lxd-noha
-Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-nosdn-lxd-noha-baremetal-daily-danube/
+Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-nosdn-lxd-noha-baremetal-daily-fraser/
Notes:
References
@@ -152,6 +152,6 @@ JOID
OpenStack
---------
-- `OpenStack Newton Release artifacts <http://www.openstack.org/software/newton>`_
+- `OpenStack Pike Release artifacts <http://www.openstack.org/software/pike>`_
- `OpenStack documentation <http://docs.openstack.org>`_
diff --git a/docs/release/scenarios/os-nosdn-nofeature-ha/release-notes.rst b/docs/release/scenarios/os-nosdn-nofeature-ha/release-notes.rst
index 974b798..a13397e 100644
--- a/docs/release/scenarios/os-nosdn-nofeature-ha/release-notes.rst
+++ b/docs/release/scenarios/os-nosdn-nofeature-ha/release-notes.rst
@@ -6,17 +6,17 @@
Abstract
========
-This document compiles the release notes for the Danube release of
+This document compiles the release notes for the Fraser release of
OPNFV when using JOID as a deployment tool with KVM hypervisor.
Introduction
============
These notes provides release information for the use of joid as deployment
-tool for the Danube release of OPNFV with KVM hypervisor for containers
+tool for the Fraser release of OPNFV with KVM hypervisor for containers
scenario.
-The goal of the Danube release and this JOID based deployment process is
+The goal of the Fraser release and this JOID based deployment process is
to establish a lab ready platform accelerating further development
of the OPNFV infrastructure.
@@ -31,16 +31,16 @@ for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-
It consists of a loadable kernel module, kvm.ko, that provides the core
virtualization infrastructure and a processor specific module, kvm-intel.ko or kvm-amd.ko.
-Danube release with the JOID deployment with KVM hypervisor will establish an
+Fraser release with the JOID deployment with KVM hypervisor will establish an
OPNFV target system on a Pharos compliant lab infrastructure.
-The current definition of an OPNFV target system is and OpenStack Newton.
+The current definition of an OPNFV target system is and OpenStack Pike.
The system is deployed with OpenStack High Availability (HA) for most OpenStack services.
User has following choices to make to do the deployment.
- - Openstack -- Newton
+ - Openstack -- Pike
- Type -- HA, nonHA, tip (stable git branch of respective openstack)
- Feature -- KVM (hypervisor)
@@ -48,10 +48,10 @@ NOTE: Detailed information on how to install in your lab can be find in installa
command to deploy lxd feature is:
#KVM deployment with HA Openstack
-./deploy.sh -o newton -f none -t ha -l custom -s nosdn
+./deploy.sh -o pike -f none -t ha -l custom -s nosdn
#LXD deployment with no HA Openstack
-./deploy.sh -o newton -f none -t noha -l custom -s nosdn
+./deploy.sh -o pike -f none -t noha -l custom -s nosdn
Using Openstack
===============
@@ -68,15 +68,15 @@ Release Data
| | |
+--------------------------------------+--------------------------------------+
| **Repo/tag** | gerrit.opnfv.org/gerrit/joid.git |
-| | stable/danube |
+| | opnfv-6.0.0 |
+--------------------------------------+--------------------------------------+
-| **Release designation** | Danube release |
+| **Release designation** | Fraser release |
| | |
+--------------------------------------+--------------------------------------+
-| **Release date** | April 01 2017 |
+| **Release date** | April 27 2018 |
| | |
+--------------------------------------+--------------------------------------+
-| **Purpose of the delivery** | Danube release |
+| **Purpose of the delivery** | Fraser release |
| | |
+--------------------------------------+--------------------------------------+
@@ -106,11 +106,11 @@ Known issues
Scenario Releases
=================
Name: joid-os-nosdn-lxd-ha
-Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-nosdn-lxd-ha-baremetal-daily-danube/
+Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-nosdn-lxd-ha-baremetal-daily-fraser/
Notes:
Name: joid-os-nosdn-lxd-noha
-Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-nosdn-lxd-noha-baremetal-daily-danube/
+Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-nosdn-lxd-noha-baremetal-daily-fraser/
Notes:
References
@@ -137,6 +137,6 @@ JOID
OpenStack
---------
-- `OpenStack Newton Release artifacts <http://www.openstack.org/software/newton>`_
+- `OpenStack Pike Release artifacts <http://www.openstack.org/software/pike>`_
- `OpenStack documentation <http://docs.openstack.org>`_
diff --git a/docs/release/scenarios/os-nosdn-nofeature-noha/release-notes.rst b/docs/release/scenarios/os-nosdn-nofeature-noha/release-notes.rst
index 974b798..a13397e 100644
--- a/docs/release/scenarios/os-nosdn-nofeature-noha/release-notes.rst
+++ b/docs/release/scenarios/os-nosdn-nofeature-noha/release-notes.rst
@@ -6,17 +6,17 @@
Abstract
========
-This document compiles the release notes for the Danube release of
+This document compiles the release notes for the Fraser release of
OPNFV when using JOID as a deployment tool with KVM hypervisor.
Introduction
============
These notes provides release information for the use of joid as deployment
-tool for the Danube release of OPNFV with KVM hypervisor for containers
+tool for the Fraser release of OPNFV with KVM hypervisor for containers
scenario.
-The goal of the Danube release and this JOID based deployment process is
+The goal of the Fraser release and this JOID based deployment process is
to establish a lab ready platform accelerating further development
of the OPNFV infrastructure.
@@ -31,16 +31,16 @@ for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-
It consists of a loadable kernel module, kvm.ko, that provides the core
virtualization infrastructure and a processor specific module, kvm-intel.ko or kvm-amd.ko.
-Danube release with the JOID deployment with KVM hypervisor will establish an
+Fraser release with the JOID deployment with KVM hypervisor will establish an
OPNFV target system on a Pharos compliant lab infrastructure.
-The current definition of an OPNFV target system is and OpenStack Newton.
+The current definition of an OPNFV target system is and OpenStack Pike.
The system is deployed with OpenStack High Availability (HA) for most OpenStack services.
User has following choices to make to do the deployment.
- - Openstack -- Newton
+ - Openstack -- Pike
- Type -- HA, nonHA, tip (stable git branch of respective openstack)
- Feature -- KVM (hypervisor)
@@ -48,10 +48,10 @@ NOTE: Detailed information on how to install in your lab can be find in installa
command to deploy lxd feature is:
#KVM deployment with HA Openstack
-./deploy.sh -o newton -f none -t ha -l custom -s nosdn
+./deploy.sh -o pike -f none -t ha -l custom -s nosdn
#LXD deployment with no HA Openstack
-./deploy.sh -o newton -f none -t noha -l custom -s nosdn
+./deploy.sh -o pike -f none -t noha -l custom -s nosdn
Using Openstack
===============
@@ -68,15 +68,15 @@ Release Data
| | |
+--------------------------------------+--------------------------------------+
| **Repo/tag** | gerrit.opnfv.org/gerrit/joid.git |
-| | stable/danube |
+| | opnfv-6.0.0 |
+--------------------------------------+--------------------------------------+
-| **Release designation** | Danube release |
+| **Release designation** | Fraser release |
| | |
+--------------------------------------+--------------------------------------+
-| **Release date** | April 01 2017 |
+| **Release date** | April 27 2018 |
| | |
+--------------------------------------+--------------------------------------+
-| **Purpose of the delivery** | Danube release |
+| **Purpose of the delivery** | Fraser release |
| | |
+--------------------------------------+--------------------------------------+
@@ -106,11 +106,11 @@ Known issues
Scenario Releases
=================
Name: joid-os-nosdn-lxd-ha
-Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-nosdn-lxd-ha-baremetal-daily-danube/
+Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-nosdn-lxd-ha-baremetal-daily-fraser/
Notes:
Name: joid-os-nosdn-lxd-noha
-Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-nosdn-lxd-noha-baremetal-daily-danube/
+Test Link: https://build.opnfv.org/ci/view/joid/job/joid-os-nosdn-lxd-noha-baremetal-daily-fraser/
Notes:
References
@@ -137,6 +137,6 @@ JOID
OpenStack
---------
-- `OpenStack Newton Release artifacts <http://www.openstack.org/software/newton>`_
+- `OpenStack Pike Release artifacts <http://www.openstack.org/software/pike>`_
- `OpenStack documentation <http://docs.openstack.org>`_
diff --git a/docs/release/scenarios/os-nosdn-openbaton-ha/release-notes.rst b/docs/release/scenarios/os-nosdn-openbaton-ha/release-notes.rst
index 51ea0de..30de597 100644
--- a/docs/release/scenarios/os-nosdn-openbaton-ha/release-notes.rst
+++ b/docs/release/scenarios/os-nosdn-openbaton-ha/release-notes.rst
@@ -35,13 +35,13 @@ heterogeneous NFV Infrastructures.
Fraser release with the JOID deployment enables deployment of orchestra
on a Pharos compliant lab infrastructure.
-The current definition of an OPNFV target system is based on OpenStack Ocata.
+The current definition of an OPNFV target system is based on OpenStack Pike.
The system is deployed with OpenStack High Availability (HA) for most OpenStack services.
User has following choices to make to do the deployment.
- - Openstack -- Ocata
+ - Openstack -- Pike
- Type -- HA, nonHA, tip (stable git branch of respective openstack)
- Feature -- Open Baton (NFV MANO framework)
@@ -49,10 +49,10 @@ NOTE: Detailed information on how to install in your lab can be find in installa
command to deploy orchestra feature is:
#Orchestra deployment with no HA Openstack
-./deploy.sh -o ocata -m openstack -f openbaton -s nosdn -t nonha
+./deploy.sh -o pike -m openstack -f openbaton -s nosdn -t nonha
#Orchestra deployment with no HA Openstack
-./deploy.sh -o ocata -m openstack -f openbaton -s nosdn -t ha
+./deploy.sh -o pike -m openstack -f openbaton -s nosdn -t ha
Using Openstack
@@ -81,7 +81,7 @@ Release Data
| **Release designation** | Fraser release |
| | |
+--------------------------------------+--------------------------------------+
-| **Release date** | March 31 2018 |
+| **Release date** | April 27 2018 |
| | |
+--------------------------------------+--------------------------------------+
| **Purpose of the delivery** | Fraser release |
@@ -142,7 +142,7 @@ JOID
OpenStack
---------
-- `OpenStack Newton Release artifacts <http://www.openstack.org/software/newton>`_
+- `OpenStack Release artifacts <http://www.openstack.org/software/pike>`_
- `OpenStack documentation <http://docs.openstack.org>`_
Orchestra
diff --git a/docs/release/userguide/userguide.rst b/docs/release/userguide/userguide.rst
index 4ef228f..5b829f0 100644
--- a/docs/release/userguide/userguide.rst
+++ b/docs/release/userguide/userguide.rst
@@ -172,7 +172,7 @@ opnfv:
release: d
distro: xenial
type: noha
- openstack: newton
+ openstack: pike
sdncontroller:
- type: nosdn
storage:
@@ -227,11 +227,11 @@ HA or non-HA mode. For OpenStack, it supports Juno and Liberty. For SDN, it supp
vSwitch, OpenContrail, OpenDaylight and ONOS (Open Network Operating System). In addition
to HA or non-HA mode, it also supports deploying the latest from the development tree (tip).
-The deploy.sh script in the joid/ci directoy will do all the work for you. For example, the following deploys OpenStack Newton with OpenvSwitch in a HA mode.
+The deploy.sh script in the joid/ci directoy will do all the work for you. For example, the following deploys OpenStack Pike with OpenvSwitch in a HA mode.
::
- ~/joid/ci$ ./deploy.sh -o newton -s nosdn -t ha -l custom -f none -m openstack
+ ~/joid/ci$ ./deploy.sh -o pike -s nosdn -t ha -l custom -f none -m openstack
The deploy.sh script in the joid/ci directoy will do all the work for you. For example, the following deploys Kubernetes with Load balancer on the pod.
@@ -251,8 +251,8 @@ Take a look at the deploy.sh script. You will find we support the following for
ha: HA mode of OpenStack.
tip: The tip of the development.
[-o]
- mitak: OpenStack Mitaka version.
- newton: OpenStack Newton version.
+ ocata: OpenStack Ocata version.
+ pike: OpenStack Pike version.
[-l]
default: For virtual deployment where installation will be done on KVM created using ./03-maasdeploy.sh
custom: Install on bare metal OPNFV defined by labconfig.yaml
@@ -417,7 +417,7 @@ The following are the common issues we have collected from the community:
::
- ./deploy.sh -o newton -s nosdn -t ha -l custom -f none
+ ./deploy.sh -o pike -s nosdn -t ha -l custom -f none
- If you have setup maas not with 03-maasdeploy.sh then the ./clean.sh command could hang,
the juju status command may hang because the correct MAAS API keys are not mentioned in