| Note | ||
|---|---|---|
| ||
As of the Dublin release, the web components of VVP are deprecated and no longer maintained. The associated repositories in VVP have been locked, but they remain available for reference and historical purposes. OOM support has been removed in Dublin, but the Casablanca version still supports the Casablanca version of VVP. |
Installation
Deployment
Installation is performed by OOM - see http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_user_guide.html#user-guide-label for instructions. This guide assumes you are using a kubernetes cluster w/ rancher to deploy OOM.
In the instructions/examples below, I am using the following infrastructure:
rancher node: 10 1.662.353.704
kubernetes master node: 10 1.662.353.685
kubernetes slave node 1: 10 1.662.353.676
kubernetes slave node 0: 10.66.35.69: 1.2.3.7
After Infrastructure is deployed, install VVP w/ OOM:
# clone oom repo
# update kubernetes/onap/values.yaml to enable/disable components.
# make sure VVP is enabled.
cd kubernetes
helm init --upgrade
helm serve &
helm repo add local http://127.0.0.1:8879
make all
helm install local/onap --name dev --namespace onaproot@rancher:~#
...
kubectl
...
get
...
pods
...
NAME READY STATUS RESTARTS AGE
dev-ci-uwsgi-688f759846-dcm5t 1/1 Running 0 54m
dev-cms-uwsgi-564b5b5d86-mpgkl 1/1 Running 0 54m
dev-em-645d6bf559-h9tdq 1/1 Running 0 54m
dev-ext-haproxy-6597f77789-ql5vn 1/1 Running 0 54m
dev-imagescanner-54fb84dfb8-6hwx6 3/3 Running 2 54m
dev-int-haproxy-57945994cf-rj2pr 1/1 Running 0 54m
dev-vvp-79b59c4f55-g84r2 1/1 Running 0 54m
dev-vvp-gitlab-5f48c7cf6c-nmbrf 1/1 Running 0 54m
dev-vvp-jenkins-69758c6dc8-cbm99 1/1 Running 0 54m
dev-vvp-postgres-d9bf9fd55-9vb4g 1/1 Running 0 54m
dev-vvp-redis-7c7448c5f4-5ls98 1/1 Running 0 54m...
After deployment has been initiated, it will take ~10 minutes for the containers to come up and become functional.
To access the portal, you will need to login to the kubernetes dashboard and figure out what port is being used by the ext-haproxy pod mapped to internal port 80.
Once you have the port, access the portal by navigating in a web browser to http://101.662.353.695:31601 .
To create an account
...
Once you create an engagement from the portal, a corresponding git repository will be created in the vvp-gitlab pod. To access the gitlab dashboard, you need to figure out what port is mapped for it. To do this, perform the same exercise as for the ext-haproxy pod, except instead now find the vvp-gitlab external port.
Navigate to http://101.662.353.695:<gitlab port> in your web browser. The root password is stored in the gitlab configmap and is base64 encoded. You should change the password as soon as possible.
...
After updating the checklist, jenkins pod will clone and run the validation-scripts against the heat templates. This The results will be reported back in to the jenkins log on the portal.
Once satisfied, move engagement to completed
...