configuration/environments_scripts/build_server/setup-hudson-server.sh
... ...
@@ -7,11 +7,7 @@
7 7
# of the instance you just launched in AWS as only argument. This will then
8 8
# turn the instance into an application server for the SAP Sailing Analytics
9 9
# application. When the script is done you may log in to look around and check
10
-# things. When done, shut down the instance (Stop, not Terminate) and create
11
-# an image off of it, naming it, e.g., "SAP Sailing Analytics 2.0" and
12
-# also tagging its root volume snapshot as, e.g., "SAP Sailing Analytics 2.0 (Root)".
13
-# If you want to use the resulting image in production, also tag it with
14
-# tag key "image-type" and tag value "sailing-analytics-server".
10
+# things.
15 11
if [ $# != 0 ]; then
16 12
SERVER=$1
17 13
$(dirname $0)/../sailing_server/setup-sailing-server.sh ${SERVER}
... ...
@@ -73,6 +69,8 @@ EOF
73 69
sudo systemctl start sailing.service
74 70
sudo systemctl stop sailing.service
75 71
sudo mount -a
72
+ echo "Now follow the instructions on the wiki for creating-ec2-image-for-hudson-from-scratch.md. It explains how to mount"
73
+ echo "the hudson volume and setup the aws + ssh keys."
76 74
else
77 75
echo "Not running on an AWS instance; refusing to run setup!" >&2
78 76
echo "To prepare an instance running in AWS, provide its external IP as argument to this script." >&2
wiki/info/landscape/creating-ec2-image-for-hudson-from-scratch.md
... ...
@@ -27,7 +27,11 @@ To find out ``{the-UUID-of-the-partition-to-mount}``, use ``blkid``.
27 27
```
28 28
* If you'd like to keep in sync with the latest version of a still running live Hudson environment, keep copying its ``/home/hudson`` contents with ``rsync -av root@dev.internal.sapsailing.com:/home/hudson/ /home/hudson/`` until you switch
29 29
* Ensure you have EC2 / EBS snapshot backups for the volumes by tagging them as follows: ``WeeklySailingInfrastructureBackup=Yes`` for ``/`` and ``/home/hudson``.
30
-
30
+* Then run the following to correctly configure the aws keys and ssh keys.
31
+```
32
+. imageupgrade_functions.sh
33
+setup_keys -p build_server # -p preserves existing ownerships and permissions.
34
+```
31 35
## In-Place Start-Up
32 36
33 37
You can then either use the instance right away by starting the two essential services, as follows: