JOID Kubernetes Release Notes¶
1. Abstract¶
This document compiles the release notes for the Danube release of OPNFV when using JOID as a deployment tool for Kubernetes.
2. Introduction¶
These notes provides release information for the use of joid as deployment tool for the Danube release of OPNFV for Kubernetes scenario.
The goal of the Danube 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.
3. 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., Flannel) 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.
Danube 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 none -l custom -s nosdn
4. 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/
5. Release Data¶
| Project | JOID |
| Repo/tag | gerrit.opnfv.org/gerrit/joid.git stable/danube |
| Release designation | Danube release |
| Release date | March 31 2017 |
| Purpose of the delivery | Danube release |
6. Known Limitations, Issues and Workarounds¶
6.1. Known issues¶
JIRA TICKETS:
| JIRA REFERENCE | SLOGAN |
| JIRA: | No support for yardstick and functest for Kubernetes scenarios (OPNFV) |
| JIRA: |
7. 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/ Notes:
