This way the runner can be activated for all projects in Argo.

Add usefull options to lease/appliance

See merge request !12

Our CI playbook requires a vault pass. Add an option to have ansible on
the frontend side to ask for this vault pass.

Note that the output asking for the pass doesn't appear on stdout, but
it still works.

Chameleon is able to send email reminders before a lease ends. Add an
option defaulting to False to activate those.

[fix] Force update on argo dependencies

See merge request !11

The base image we are using contains some of these packages already, but
at a terrible version. Forcing them to latest ensure the test/install
work properly.

[refactor] Isolate Popen, no recursive ansible

See merge request !10

Recursive ansible was causing all kinds of problems, especially with IO.
Instead, we use ssh to launch a second round of ansible.

Instead of duplicating the popen handling, we then move it to a new
function.

[fix] Use metadata to map instances to lease

See merge request !9

The lease id recently disappeared from the availability zone info in
servers. It broke the configure part of an appliance, as we were using
this info to create an ansible inventory for the stack. Unfortunately,
after an exchange with Chameleon staff, it became clear that
this "feature" wasn't intended.

We now add metadata to our appliance template, allowing us to add the
arbitrary info we need to the server info. This way we can filter as we
want. This should make the script more future-proof.

[feature] Add nodeos-config role

See merge request !8

Add Prototype Spack repository

See merge request !7

Technically doesn't work, as we need setuid on the binary.

Can install the library, but crashes with --test. Will do for now.

Pretty straightforward. Also added as a dependency for the nrm.

Working spack repository and aml package. Will work on adding to it.

Improve playbooks

See merge request !6

Also fix a couple of bugs identified from this playbook.

Includes msr-safe and libmsr, based on comments from @tpatki.

[feature] add umap CI/install role

See merge request !5

Add playbook role to install or use CI with umap.

Ci support

See merge request !4

Add role to activate ci/install on chameleon.

I discovered that CI runners could be manually activated for multiple
projects. It means I don't need to add a config section for each runner,
and can instead have a global one.

Playbook to use with ./chi-appliance configure to setup a CI
infrastructure on top of Chameleon nodes.

This playbook:
 - installs gitlab-runner
 - adds role to install or run ci on aml

I'm reluctant to add CI tokens in plaintext inside the infra repo.
Instead, ansible-vault is used to keep them encrypted.

The openstack client libraries bury the actual error message reported by
the openstack servers inside a Requests.Response object. This patch
makes sure we retrieve this message, as it is more useful than the top
level one.

We don't have a use for a appliance-local ssh key for now, so let's not
add that trouble to our setup.

Just enough tasks and templates to end up with an idle gitlab CI runner
installed and running on the node.

It should make it easier to organize tasks, and give us easy access to
"become" for an entire group of tasks.

[fix] enforce region for blazar client

See merge request !3

Since Chameleon changed to a multi-region setup the blazar client is
acting up. It looks like the current upstream doesn't support that
feature by default.

In theory, the session already contains the region info, but since the
client creation code doesn't use it by default, we force it. This is
adapted from the Chameleon-recommended client library.

Ansible improvements

See merge request !2

Until we figure out a way to add host keys to the config without
trouble, disable host key checking when calling ansible.

Not doing so could result in blocked calls, as ansible was asking
questions during the run.

Usefull for users that want to try a different set of roles.

Ansible allows us to wait for the node to become available, which should
allow us to launch the `configure` command as soon as `create --wait`
completes.

Uses default wait_for_connection module, which should poll for 10
minutes.

Requires that we disable gather_fact, and reactivate it after the
connection succeeds.

Stack create and delete take an option to wait for the operation to
complete. It doesn't actually wait for the operation to complete, just
for the Openstack side of it to be done. For creation for exemple, the
nodes might still be booting.

Ansible recommend a specific directory layout to deal with complex
playbooks. As we expect this configuration to become trickier, let's
adopt good practices right away.

Previous code was blocking on stdout after subprocess completed with
success, as `poll()` would return 0, and `not 0` is true.

Region support

See merge request !1