ONAP on VMware Integrated OpenStack - Container Orchestration
Table of Contents
VMware VIO 4.1 Kubernetes Architecture
VMware VIO supports Container Orchestration. Container Orchestration can be used a product or as a service. This page captures the information and steps to deploy ONAP using OOM on VI0 4.1 with Kubernetes using 'OpenStack' as the Cloud Provider.
Prerequisites
VMware Integrated OpenStack 4.1.
VMware Integrated OpenStack 4.1 with Kubernetes.
A SSH Client - (Example: MobaXTerm - Download).
Software Requirements
OOM Software Requirements
Release | Kubernetes | Helm | Kubectl | Docker |
|---|---|---|---|---|
Amsterdam | 1.7.x | 2.3.x | 1.7.x | 1.12.x |
Beijing/Master | 1.8.5 | 2.7.x | 1.8.5 | 1.12.x |
Minimum Hardware Configuration
OOM Hardware Requirements
RAM | HD | vCores | Ports |
|---|---|---|---|
128 GB | 160 GB | 16 | 0.0.0.0/0 (All Open) |
Procedure
Step 1: Login to VMware Intergrated OpenStack 4.1 with Kubernetes
Go to your web browser (Firefox/Chrome Recommended).
Visit https://FQDN/login or https://VIO_K8s_IP_Address/login
Step 2: Create a Cloud Provider
Go to Cloud Provider and click on Deploy New Provider.
If you have a JSON File with all the configurations, then click on Choose File and upload the JSON.
Otherwise, click Next.Give a Provider name and select OpenStack as the Provider type, then click Next.
We need to provide OpenStack Authentication now to add it as the Cloud Provider.
Give the Keystone Public URL, Username, Password, Project name, Region name, Domain name and upload the CA Certificate.
(CA Certificate is an important step for successful OpenStack Authentication, you can found more details about the certificate on the Page 34 of this PDF.)
Click Next.Now, we need to select the Image which will be used to deploy the Kubernetes Master and Worker Nodes.
We are selecting Ubuntu 16.04 as the image for our deployment.
Give the Image username and Select an image from the list.
(This list will be fetched from your VMware Integrated Openstack deployment post successful authentication.)Now, we need to select the Flavor which will be used to deploy the Kubernetes Master and Worker Nodes.
We are selecting m1.oom as the flavor for our deployment. This is a custom flavor created on VMware Integrated OpenStack 4.1.
(It is recommended to create a flavor which meets the minimum hardware configurations as described above in this document.)
Select a flavor from the list. (This list will be fetched from your VMware Integrated Openstack deployment post successful authentication.)
Click Next.If you are not using NSX-T, then you can click Next.
If you are using NSX-T, then give then Manager address, Username, Password, Tier 0 Router and Transport zone.Now, we need to select the Security Group which will be applied to all the cluster nodes. All the security groups created by you will be listed here.
Select security group(s) has a list of groups with their names, select them as per your requirements.
Click Next.Now, we need to select the External Network which will used to expose Kubernetes Cluster API and also for external services. All the external networks created by you will be listed here.
Select external network has a list of external network with their names, select the external network as per your requirement.
(Please make sure that at least two floating IPs are available.)
Click Next.Now, we need to select the Internal Network, it should be connected to the External Network via a router and should have atleast one subnet. All the internal networks created by you will be listed here.
Select internal network and Select a subnet has a list of internal networks and subnets with their names, select the internal network and subnet as per your requirement.
Click Next.Now, check the Configuration Summary and verify the information.
If you wish to download the JSON of your configurations, click on Download Provider JSON.
Click Finish to add the Cloud Provider.The addition of Cloud Provider is pretty quick and it should be added instantly as soon you click Finish. If not then kindly wait for few minutes.
You can check your Cloud Provider on the page.
It should show the state as ACTIVE, denoting successful addition of Cloud Provider.You can get additional information regarding a Cloud Provider by clicking on it's name.