| commit | dd188395efbacb657e93d6bf7681dc4a0e1cf1ad | [log] [tgz] |
|---|---|---|
| author | nauman <nauman.yaseen@est.tech> | Mon Feb 21 08:47:25 2022 +0000 |
| committer | nauman <nauman.yaseen@est.tech> | Mon Feb 21 14:30:13 2022 +0000 |
| tree | 61b50d8aee405ceb514e757885ce4e025cff462b | |
| parent | 6253131af31d3593d92bd53ae3967fda833b4034 [diff] |
Change nginx offline install config using default nginx.conf add enine config in sites-enabled Change-Id: Icbb18bd3a3ab6f87de0840fa182495f907bdf0af
The Cloud Infra Engine is created based on OPNFV Cross Community CI (XCI) project in order to automate the deployment and testing of various cloud infra scenarios. [1]
The supported scenarios are based on
technologies and they can be deployed and tested using different types of resources such as
The possibility of using one of the resources listed above highly depends on the scenario the users want to deploy, test, and use. More information is available in corresponding sections.
Cloud Infra Engine lets users to deploy the scenario of their choosing on to their workstations. Minimum requirements for the host where the Cloud Infra Engine is executed are
Recommended requirements are
The engine currently only supports Ubuntu16.04.
Apart from having sufficient performance and capacity on the host, few packages need to be installed on the host before executing the engine
The user that is executing the engine should also have passwordless sudo enabled.
Cloud Infra Engine is version controlled on Nordix Gerrit so its repository needs to be cloned.
git clone https://gerrit.nordix.org/infra/engine.git
Cloud Infra Engine expects the ssh keys to be created in advance. If you don't have ssh keypair already, you can do that by executing below command.
ssh-keygen -t rsa
Once the keypair is generated, the main script deploy.sh can be executed in order to start deployment of the default scenario on virtual machines that are created by the engine.
cd engine/engine ./deploy.sh -h # get help ./deploy.sh -c
Once the script execution starts, it will prepare the environment, create libvirt resources, provision libvirt vms and install the selected scenario on them. The overall process takes about 40 minutes to complete if ramdisk and deployment images are created in advance.
Please note, in the default / embeded pdf / idf files, we have specified two disks for each vms we are going to create. If you are going to provide pdf / idf files yourself with mulitple disks, please note the current deployment script will not work when the disks have the same size as we specify the bootable disk based on size.
TBD
TBD
TBD
TBD