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
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
Tested the scripts in the Atlanta Lab and ran into issues
with 'max_shipyard_count' and 'shipyard_query_time' variables
as we will need to export them as environment variables as well.
This patch set is meant to correct the problem.
Change-Id: I0ae407adac3df6a0cbe027a70940ee65904a7854
We will make use of common functions across the deploy_site,
update_site and redeploy_server script.
This will help to reduce common and repetitive codes across
the scripts.
Note that the Shipyard CLI needs to be installed before we
can use these scripts.
Change-Id: I31e5c8723346666a592951f59856008ccb64128b
Jiří Suchomel