| commit | 5f34c2a712d8f97a6c6b71bc5a80fd85cb98c609 | [log] [tgz] |
|---|---|---|
| author | Wenqing Gu <wenqing.gu@gmail.com> | Fri Mar 15 15:44:53 2019 +0100 |
| committer | Wenqing Gu <wenqing.gu@gmail.com> | Mon Mar 18 21:54:17 2019 +0000 |
| tree | ca85347e5768625d71a3782d0ac168ab42122042 | |
| parent | 5dff1c0966c6690c2ea3b4ba7159ccc9998f0c11 [diff] |
[INF-63] Fix dns configuration In the OS image, systemd-resolved is used as local dns manager, therefore in this commit we config the DNS via the corresponding configuration file: /etc/systemd/resolved.conf Removed the changes to network interfaces file as this dns manager will not respect that. Removed also to the changes to resolve.conf as the file will be managed by the dns manager. At the same time, restore the idf back to support multiple dns servers as a list. Also, to make the host server be less resource demanding, modified the pdf file with reduced hard disk and memory. Change-Id: I0ce7beb644bb5e2757bb62da46aca6d3f4e86e1f
The Cloud Infra Engine is created based on OPNFV Cross Community CI (XCI) project in order to automate deployment of various cloud infra scenarios. [1]
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.