Develop and update official OVP web portal
For OVP Web development, currently the source code is included in Dovetail repo. The github link is can be found in github https://github.com/opnfv/dovetail/tree/master/cvp-webportal.
The web portal is composed by 3 5 different Docker containers and the corresponding Docker images are,
- opnfv/testapi:cvp.0.35.0opnfv/dovetail
- mongo:web3.ovp2.1.1.0
- jwilder/nginx-proxy
- opnfv/dovetail-webportal-web:latest
- opnfv/dovetail-webportal-api:latestapi.ovp.1.1.0
The first testapi Docker image is a basic image 3 Docker images are basic images and has no relationship with Dovetail dovetail-webportal repo. So in order to update the web, it only needs to update the last 2 Docker images.
Here using Dovetail Docker hub for these 2 Docker images and distinguish them with different image tags. These 2 images need to will be rebuilt manually automatically when there are new patched merged . Also the Dovetail docker build job can be used to build them with a little modifications.
...
to repo dovetail-webportal.
Tag the repo
...
(e.g.
...
- DOCKER_DIR: cvp/docker
- COMMIT_ID: one commit id that merged no earlier than the OVP web patch
- GERRIT_REFNAME: the tag name you want to tag the Docker image (e.g. api.ovp.1.1.0)
- DOCKERFILE: Dockerfile
...
2.0.0), then it will build 2 docker images with that tag, and they can be used for updating official OVP web portal.
After the Docker images have been successfully pushed to Dovetail Docker hub, contact Trevor Bramwell to use the new Docker images to update the Web.
Test web portal locally
Before updating the official web, it needs to test locally.
Pull the dovetail-webportal source code and download the 5 docker images mentioned before.
Go to dovetail-webportal/docker, refer to file README.rst to edit config.env and vhost.env.
Run all containers with docker-compose.yml. (exec cmd: docker-compose up -d)
Use the local IP and port (default is 8000) to access the local web.