Create CSAR with Helm chart as an artifact
We need to attach a tgz file to heat template package.
The basic package consists of an environment file, base_dummy.yaml file (for the sake of example) and MANIFEST.json and the tar.gz file. We need to zip all of these files before onboarding. One thing to pay much attention to is VNF project dictates the naming convention; which must be followed while making the zip of all these files.
NOTE: The Naming convention is for the helm chart zip file.
Naming convention follows the format:
<free format string>_cloudtech_<technology>_<subtype>.extension
- Cloudtech is a fixed pattern and should not be changed if not necessary
- Technology: k8s, azure, aws, ….
- Subtype: charts, day0, configtemplate, ...
- Extension: zip, tgz, csar, …”
Listed below is an example of the contents inside a heat template package
vfw_k8s_demo.zip file is a zip of the 4 other files(manifest.json, base_dummy.env, base_dummy.yaml,vfw_cloudtech_jus.charts) gets on boarded onto SDC.
$ vfw-k8s/package$ ls |
NOTE:
The .tgz file must be a tgz created from the top level helm chart folder. I.e a folder that contains a Chart.yaml file in it.
MANIFEST.json
Key thing is note the addition of cloud artifact
type: "CLOUD_TECHNOLOGY_SPECIFIC_ARTIFACTS"
{ |
Base_dummy.yaml
Designed to be minimal HEAT template.
# #==================LICENSE_START========================================== |
Base_dummy.env
parameters: |
Onboard the CSAR
For onboarding instructions please refer to steps 4-9 from the document here.
REGISTER KUD CLOUD REGION with K8s-Plugin
API to support Reachability for Kubernetes Cloud
The command to POST Connectivity Info
{ |
This is a multipart upload and here is how you do the POST for this.
#Using a json file (eg: post.json) containing content as above;
curl -i -F "metadata=<post.json;type=application/json" -F file=@ /home/ad_kkkamine/.kube/config -X POST http://MSB_NODE_IP:30280/api/multicloud-k8s/v1/v1/connectivity-info |
Command to GET Connectivity Info
curl -i -X GET http://MSB_NODE_IP:30280/api/multicloud-k8s/v1/v1/connectivity-info/{name} |
Command to DELETE Connectivity Info
curl -i -X DELETE http://MSB_NODE_IP:30280/api/multicloud-k8s/v1/v1/connectivity-info/{name} |
Command to UPDATE/PUT Connectivity Info
curl -i -d @update.json -X PUT http://MSB_NODE_IP:30280/api/multicloud-k8s/v1/v1/connectivity-info |
Register KUD Cloud region with AAI
With k8s cloud region, we need to add a tenant to the k8s cloud region. The 'easy' way is to have the ESR information (in step 1 of cloud registration) point to a real OpenStack tenant (e.g. the OOF tenant in the lab where we tested).
This will cause multicloud to add the tenant to the k8s cloud region and then, similar to #10 in the documentation here , the service-subscription can be added to that object.
NOTE: use same name cloud-region and cloud-owner name
Example is shown below for K8s cloud but following the steps 1,2,3 from here. The sample input below is for k8s cloud type.
Step 1 - Cloud Registration/ Create a cloud region to represent the instance.
Note: highlighted part of the body refers to an existing openstack tenant (OOF in this case). Has nothing to do with the K8s cloud region we are adding.
PUT https://{{AAI1_PUB_IP}}:{{AAI1_PUB_PORT}}/aai/v13/cloud-infrastructure/cloud-regions/cloud-region/k8scloudowner4/k8sregionfour |
Step 2 – add a complex to the cloud
Note: just adding one that exists already
PUT https://{{AAI1_PUB_IP}}:{{AAI1_PUB_PORT}}/aai/v13/cloud-infrastructure/cloud-regions/cloud-region/k8scloudowner4/k8sregionfour/relationship-list/relationship |
Step 3 - Trigger the Muticloud plugin registration process
This registers the K8S cloud with Multicloud – it also reaches out and adds tenant information to the cloud (see example below – you’ll see all kinds of flavor, image information that is associated with the OOF tenant).
If we had not done it this way, then we’d have to go in to AAI at this point and manually add a tenant to the cloud region. The first time I tried this (k8s region one), I just made up some random tenant id and put it in.)
The tenant is there so you can add the service-subscription to it:
Making a Service Type:
PUT https://{{AAI1_PUB_IP}}:{{AAI1_PUB_PORT}}/aai/v13/service-design-and-creation/services/service/vfw-k8s |
Add subscription to service type to the customer (Demonstration in this case – which was already created by running the robot demo scripts)
PUT https://{{AAI1_PUB_IP}}:{{AAI1_PUB_PORT}}/aai/v16/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vfw-k8s |
Add Service-Subscription to the tenant (resource-version changes based on actual value at the time):
PUT https://{{AAI1_PUB_IP}}:{{AAI1_PUB_PORT}}/aai/v16/cloud-infrastructure/cloud-regions/cloud-region/k8scloudowner4/k8sregionfour/tenants/tenant/6bbd2981b210461dbc8fe846df1a7808?resource-version=1559345527327 |
Distribute the CSAR
Onboard a service it gets stored in SDC final action is distributed. SO and other services are notified sdc listener in the multicloud sidecar. When distribution happens it takes tar.gz file and uploads to k8s plugin.
Create Profile Manually
K8s-plugin artifacts start in the form of Definitions. These are nothing but Helm Charts wrapped with some metadata about the chart itself. Once the Definitions are created, we are ready to create some profiles so that we can customize that definition and instantiate it in Kubernetes.
A profile contains the following:
- manifest.yaml
- Contains the details for the profile and everything contained within
- A HELM values override yaml file.
- It can have any name as long as it matches the corresponding entry in the manifest.yaml
- Any number of files organized in a folder structure
- All these files should have a corresponding entry in manifest.yaml file
Sample Definition found here
Creating a Profile Artifact
> cd multicloud-k8s/kud/tests/vnfs/testrb/helm/profile |
The manifest file contains the following
--- |
Note: values: "values_override.yaml" can be empty file if you are creating a dummy profile
Note: A dummy profile does not need any customization. The following is optional in the manifest file.
configresource: |
With this information, we are ready to upload the profile with the following JSON data
{ |
Command to create (POST) Profile
curl -i -d @create_rbprofile.json -X POST http://MSB_NODE_IP:30280/api/multicloud-k8s/v1/v1/rb/definition/test-rbdef/v1/profile |
Command to UPLOAD artifact for Profile
curl -i --data-binary @profile.tar.gz -X POST http://MSB_NODE_IP:30280/api/multicloud-k8s/v1/v1/rb/definition/test-rbdef/v1/profile/p1/content |
Command to GET Profiles
# Get all Profiles |
Command to DELETE Profile
curl -i -X DELETE http://MSB_NODE_IP:30280/api/multicloud-k8s/v1/v1/rb/definition/test-rbdef/v1/profile/p1 |
Instantiation
Instantiation is done by SO. SO then talks to Multi Cloud-broker via MSB and that in turn looks up the cloud region in AAI to find the endpoint. If k8sregion one is registered with AAI and SO makes a call with that, then the broker will know that it needs to talk to k8s-plugin based on the type of the registration.
Instantiate the created Profile via the following REST API
Using the following JSON:
{ |
NOTE: Make sure that the namespace is already created before instantiation.
Instantiate the profile with the ID provided above
Command to Instantiate a Profile
curl -d @create_rbinstance.json http://MSB_NODE_IP:30280/api/multicloud-k8s/v1/v1/instance |
The command returns the following JSON
{ |
Delete Instantiated Kubernetes resources
The id field from the returned JSON can be used to DELETE the resources created in the previous step. This executes a Delete operation using the Kubernetes API.
GET Instantiated Kubernetes resources
The id field from the returned JSON can be used to GET the resources created in the previous step. This executes a get operation using the Kubernetes API.
https://github.com/onap/oom/blob/master/kubernetes/multicloud/resources/config/provider-plugin.json
Create User parameters
We need to create parameters that ultimately get translated as:
"user_directives": { |