Implementing jump VM create via ansible

This patch reimplements the creation of the jump VM as ansible
playbook. The advantage of this approach is a more deterministic
behavior and the ability to render configuration files using
templates based on the pdf and idf.

Moreover, this patch allows to overwrite the VENDOR variable.
This is necessary to allow deployment in different labs via
CI.

The BMRA configuration has not yet been transformed to ansible
template and needs to follow in subsequent patches.

Signed-off-by: Georg Kunz <georg.kunz@est.tech>
Signed-off-by: Victor Morales <v.morales@samsung.com>
Change-Id: I2cde41dcecec7480bddf71ed864f06244a89f1f3
Reviewed-on: https://gerrit.opnfv.org/gerrit/c/kuberef/+/70882
Tested-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
Reviewed-by: Victor Morales <chipahuac@hotmail.com>

1 files changed, 13 insertions, 0 deletions

diff --git a/playbooks/roles/jump-vm/templates/user-data.j2 b/playbooks/roles/jump-vm/templates/user-data.j2
new file mode 100644
index 0000000..648f8d1
--- /dev/null
+++ b/playbooks/roles/jump-vm/templates/user-data.j2
@@ -0,0 +1,13 @@
+    #cloud-config
+    users:
+      - name: ubuntu
+        ssh-authorized-keys:
+          - {{ lookup('file', pub_key ) }}
+        sudo: ['ALL=(ALL) NOPASSWD:ALL']
+        groups: sudo
+        shell: /bin/bash
+    runcmd:
+        # this is requried in labs where the PXE network is different from
+        # the public network. Without internet connectivity, the installation
+        # of BMRA fails
+        - [ iptables, -t, nat, -A, POSTROUTING, -o, ens3, -j, MASQUERADE ]