Since build env is setup for building images, it makes more sense to
have all build jobs in that environment.

We do not run merge request pipeline, so no need to check for it

Closes rc/hpc-factory#181

Defining a network can be optional when a port is already defined when
deploying a VM.

This commit adds flexibility where you can either use --port or
--network options to define a network during the deployment.

Alternatively, you can define both but the port cannot be from the same
network you used in the --network option. Otherwise, you will have two
ips from the same network which will cause network reachability issues.

Closes rc/hpc-factory#203

Download group_vars/knightly or group_vars/prod for knightly or prod
environments respectively.
Note: For all other environments like dev or staging just use the
default values from group_vars/all

Closes rc/hpc-factory#176

Eesaan Atluri authored 5 months ago and Bo-Chun Chen committed 5 months ago

Because compute and login nodes are basically the same except login node
does not need slurmd and we don't use compute image anywhere. So use it
to build login image and change its references in CI script

Parse the target dir where the external repo will be cloned, from the
value of EXT_REPO_DIR var. Use this var to replace all instances where
the repo name is hardcoded.

This will let you define the branch name for the PR you want to test
from the src repo and target branch to merge into, in the target repo

This will enable us to define the upstream and downstream repos hosted
external to gitlab (For eg. Github)

Define Floating IPs as a list so that we can assign multiple
whenever needed like in prod