This PS adds role which installs docker
Change-Id: Icf8e33f36dfc72327255b9949f0efd9f5f5f8b55
Signed-off-by: Sreejith Punnapuzha <sreejith.punnapuzha@outlook.com>
These roles will allow to get logs and resource definitions from
remote host to zuul, will ease debugging process.
Change-Id: I1876ff59fc99d2a605a45e3ecc1abb46bac677a6
This role is only needed during local development, if developer is
using remote machine to deploy environment on. Role will copy local
repository to remote ansible host, his repository will be then used
to build airshipctl binary and to create bundle with airship docs
Change-Id: I742d89656830d02a8e998bbef6041a5b0231d132
in this commit we are removing dhcp from the networks, fixing vnc
listen ip addresses, and console log output directories
Change-Id: I61a77baa343720583b1ebfb2e4519803f1f32676
This PS removes privilege escalation from the roles so that these roles
can be used in a developer environment
Change-Id: I44ddc18532ee75b0d398896d470ecf949ad4496a
Role will allow to easily serve static content over http.
python simple http server wrapped into systemd unit
Change-Id: I7726b973ad77ab3a58819ff48033a74095ed3ea0
airship-libvirt-gate role is designed to build a fully functioning
all-in-one type infrastructure for development, testing or gating
purpose on top of libvirt + qemu. It has concept of `Flavor` which
would allow users to pick fingerprint (size of the env). In this
commit only flavor called `small` is introduced. In near future we
will add other flavors.
For default usecases please see examples/playbooks/gate directory.
Change-Id: Ifefd299592b91ce2810794eb29050874977397f2
Please note, in near future we will remove escalation where ever
we can to make sure that we can securely build not only gates
but also development environment
Change-Id: I38045b45607b519699b232b35dd5e1f48a88febc
This commit adds simple roles to manage:
- libvirt service, domains, volumes, networks and pools.
- redfish-emulator role installs sushy-tools from pip, together
with support packages
Please note, that libvirt roles are not meant to be completely
idempotent, their main job is deploy temporary resources that for
ci and gating purposes, to be tore down afterwards. Roles are
specifically made to be simple to debug, and don't contain any
complex logic to make them portable, flexible or idempotent.
Change-Id: I2ff0138b5c95bea3445e242a2e5061651498f1ab