| commit | b71ed0f9bda63a9b2ba0c90b50c675bb9befad52 | [log] [tgz] |
|---|---|---|
| author | Fatih Degirmenci <fdegir@gmail.com> | Thu Apr 18 13:40:17 2019 +0000 |
| committer | Fatih Degirmenci <fdegir@gmail.com> | Tue Apr 23 07:25:05 2019 +0000 |
| tree | 741c1406144c17a5714047ae3143dcf1aea398d3 | |
| parent | c49d8d71c8a161e1dd846f46f12d2e898585e9b9 [diff] |
Create and use ansible.cfg for engine ansible.cfg lets us configure various options such as ssh and others and it makes sense to ship this together with engine rather than asking users to modify ~/.ssh/config files or configure Jenkins slaves in advance. Created ansible.cfg file is taken from kubespray as it already ships its own ansible.cfg. By default, Ansible looks at various places for ansible.cfg so we place engine ansible.cfg into root of engine repo and run all the playbooks from there. It also helps us to get rid of StrictHostKeyChecking by moving it to ansible.cfg. Created ansible.cfg is only used for engine itself as other tools might come with their own ansible.cfg as it can be seen for kubespray. Change-Id: Ida201e0815858401f5adc23cc0936e23c6edaf87
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.
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.