| commit | 231f7cc158bd5a299bd81867fae97b461da766fd | [log] [tgz] |
|---|---|---|
| author | Fatih Degirmenci <fdegir@gmail.com> | Tue Apr 23 21:52:37 2019 +0200 |
| committer | Fatih Degirmenci <fdegir@gmail.com> | Thu Apr 25 08:30:45 2019 +0200 |
| tree | e23b7a5cf670f79ac37897e8c31956fef9bdae1c | |
| parent | ef37f738c9c907f555368f9e61592c4b66e90142 [diff] |
Bump kubespray in order to bring k8s v1.14.0
This change bumps kubespray sha to 05dc2b3 in order to bring k8s
v1.14.0.
Previous attempt failed due to the task that makes k8s admin.conf
available on jumphost. It looks like k8s v1.14.0 kubeadm behavior
changed, resulting in inclusion of erroneous stdout line in the
file, causing failures when kubectl is attempted to be used or
during testing with functest and yardstick. [1]
[kubeconfig] Writing "admin.conf" kubeconfig file
apiVersion: v1
clusters:
- cluster:
...
In order to accommodate this error, a task in engine post-deployment
role is created as a workaround.
[1] https://github.com/kubernetes-sigs/kubespray/blob/master/roles/kubernetes/client/tasks/main.yml#L78
Change-Id: I1238806983ecb763037f05d38bf2af2b4ae698f4
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.