In case users have OS_PASSWORD set for a different cloud, it may
have sense to use different variable just for shiyard user's password.
Change-Id: I709df849e1109582917453c9fcec8bed565c2814
By default, all sudo commands are logged to auth.log with their
full command line. Previously, Shipyard scripts called 'sudo docker'
with -e OS_PASSWORD=foo, resulting in the password value appearing
in auth.log in plaintext. This change adds -E to the sudo command
to pass the user's environment through, and removes the value from
-e OS_PASSWORD which tells Docker to use the environment value
directly. This prevents the password value from being logged.
Change-Id: Ifcf7f6525876144a609ff42be42da57a3f7f6f60
Updates the Shipyard/Airflow workflow for deploy_site and
update_site to use the deployment group/deployment strategy
information from the design.
This allows for baremetal nodes to be deployed in a design-
specified order, with criticality and success criteria driving
the success and failure of deployment.
Includes refactoring of service endpoints to reduce the need
for so much data passing.
Change-Id: Ib5e9fca535ca74d1819fe46959695acfed5b65c2
- Don't change directory so that the volume mounted in the
container at /home/shipayard/host is predictable
- Update image default to point at airshipit repo
Change-Id: If8b0988925921d7b54ec74ac73e12289d89d392e
We will move away from installation of shipyard CLI/client
binaries and will make use of the shipyard docker container
instead for our CI/CD integration environment.
Change-Id: I253cbc1e2f9310b9c11195e1c68b97ee8d0efead
We will no longer need to manually update the '/etc/hosts' file
for 'in-cluster' scenario with the bug fix in [0]. This patch set
is meant to update the scripts in the tools directory to reflect
that change.
Note that user will still need to ensure that the DNS is set up or
'/etc/hosts' file is properly updated if he/she is executing the
workflow from outside the cluster, e.g. via jump server
[0] https://review.gerrithub.io/#/c/398739/
Change-Id: I0580cfc473b0f1b0ed824a578d3e6c89dd6f1443
[0] allows namespace specific ingress controllers and a
cluster wide ingress controller that acts as the external
front door to the cluster.
As the codes in OSH have been merged, we are removing the
workaround that was previously put in place for UCP namespace.
[0] https://review.openstack.org/#/c/533271/
Change-Id: Ia1c3e85e55678d62a4eb8506841dffc547012ef0
Installing the Shipyard CLI on the Genesis host will introduce
large number of packages on the host machine and is not the
desired approach. Hence we will want to use a docker container
to execute Shipyard CLI whenever possible. However, it is
troublesome to pass all the required parameters everytime
when we execute the Shipyard CLI with docker command.
This patch set attempts to create a thin wrapper script to make
it easier for user.
Change-Id: I06235399cc7c9a22169f39edf948dc5e573652c5
Jiří Suchomel