| commit | f16580a226a01eb8bd0503f31e27693b62b1fdad | [log] [tgz] |
|---|---|---|
| author | Fatih Degirmenci <fdegir@gmail.com> | Tue Mar 19 13:37:38 2019 +0000 |
| committer | Fatih Degirmenci <fdegir@gmail.com> | Tue Mar 19 14:33:20 2019 +0000 |
| tree | a4ca8456754e47cc409c6f628d250cc1fdb11e63 | |
| parent | 5f34c2a712d8f97a6c6b71bc5a80fd85cb98c609 [diff] |
Install ironic components using pip Installing ironic and the other ironic components from source is something that comes from OPNFV XCI as we provided feedback to OpenStack community by testing stuff from source. In our case, we are not providing feedback so using pip should be sufficient. This obviously makes us a bit vulnerable since there is no way to pin ironic stuff in bifrost but at the same time, this is not the only situation we will be open to this type of issues. Apart from that, there is no way to install ironic using pip so we still install ironic from source by pinning it so this should provide some kind of protection. Finally, we also stop using upper-constraints as it is not necessary in our context and let bifrost itself handle it. Change-Id: Ibc89c67d684379ad99cd19de55431848e97cc9ab
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.