From e00115a7a5ea27030cc4f36efdc298b6145cdb02 Mon Sep 17 00:00:00 2001 From: Narinder Gupta Date: Wed, 25 Apr 2018 10:16:48 -0500 Subject: document update for Fraser release. Change-Id: Iab88d244a8a39b78c84aa11550cee2c04f81ab0f Signed-off-by: Narinder Gupta --- docs/release/scenarios/k8-canal-lb-noha/index.rst | 16 ++ .../scenarios/k8-canal-lb-noha/release-notes.rst | 173 ++++++++++++++++++++ .../scenarios/k8-nosdn-lb-noha/release-notes.rst | 18 +-- .../scenarios/k8-nosdn-lb_ceph-noha/index.rst | 16 ++ .../k8-nosdn-lb_ceph-noha/release-notes.rst | 174 +++++++++++++++++++++ .../k8-nosdn-nofeature-noha/release-notes.rst | 18 +-- .../scenarios/k8-ovn-lb-noha/release-notes.rst | 4 +- .../scenarios/os-nosdn-lxd-ha/release-notes.rst | 30 ++-- .../scenarios/os-nosdn-lxd-noha/release-notes.rst | 30 ++-- .../os-nosdn-nofeature-ha/release-notes.rst | 30 ++-- .../os-nosdn-nofeature-noha/release-notes.rst | 30 ++-- .../os-nosdn-openbaton-ha/release-notes.rst | 12 +- 12 files changed, 465 insertions(+), 86 deletions(-) create mode 100644 docs/release/scenarios/k8-canal-lb-noha/index.rst create mode 100644 docs/release/scenarios/k8-canal-lb-noha/release-notes.rst create mode 100644 docs/release/scenarios/k8-nosdn-lb_ceph-noha/index.rst create mode 100644 docs/release/scenarios/k8-nosdn-lb_ceph-noha/release-notes.rst (limited to 'docs/release/scenarios') 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 00000000..ff273d4a --- /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) + +============================= +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 00000000..1248cf1c --- /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) + + +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 `_ + +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 `_ +- `Juju documents `_ +- `Canonical Distibuytion of Kubernetes `_ + +MAAS +---- +- `Bare metal management (Metal-As-A-Service) `_ +- `MAAS API documents `_ + +JOID +---- +- `OPNFV JOID wiki `_ +- `OPNFV JOID Get Started `_ + +Kubernetes +---------- +- `Kubernetes Release artifacts `_ +- `Kubernetes documentation `_ + 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 a5ebd32d..6d49a3c6 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 00000000..b17b6282 --- /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) + +============================= +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 00000000..2d1c7913 --- /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) + + +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 `_ + +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 `_ +- `Juju documents `_ +- `Canonical Distibuytion of Kubernetes `_ + +MAAS +---- +- `Bare metal management (Metal-As-A-Service) `_ +- `MAAS API documents `_ + +JOID +---- +- `OPNFV JOID wiki `_ +- `OPNFV JOID Get Started `_ + +Kubernetes +---------- +- `Kubernetes Release artifacts `_ +- `Kubernetes documentation `_ + 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 c9ad4364..ad356342 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 0a9938e5..2a0ba98f 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 96afbec0..7bfdc6dc 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 `_ +- `OpenStack Pike Release artifacts `_ - `OpenStack documentation `_ 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 96afbec0..327736b9 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 `_ +- `OpenStack Pike Release artifacts `_ - `OpenStack documentation `_ 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 974b7981..a13397e9 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 `_ +- `OpenStack Pike Release artifacts `_ - `OpenStack documentation `_ 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 974b7981..a13397e9 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 `_ +- `OpenStack Pike Release artifacts `_ - `OpenStack documentation `_ 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 51ea0ded..30de5976 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 `_ +- `OpenStack Release artifacts `_ - `OpenStack documentation `_ Orchestra -- cgit 1.2.3-korg