Important: Upgrades are not supported with this installation method.

Transcription

1 CLI DC/OS Installation Guide The automated CLI installer provides a guided installation of DC/OS from the command line. With this method you can choose from the complete set of DC/OS configuration options. This installation method uses a bootstrap node to administer the DC/OS installation across your cluster. The bootstrap node uses an SSH key to connect to each node in your cluster to automate the DC/OS installation. Important: Upgrades are not supported with this installation method. The DC/OS installation creates these folders: Folder /opt/mesosph ere /etc/systemd /system/dcos. target.wants /etc/systemd /system/dcos. <units> /var/lib/dco s/exhibitor/z Description Contains all the DC/OS binaries, libraries, cluster configuration. Do not modify. Contains the systemd services which start the things that make up systemd. They must live outside of /opt/ mesosphere because of systemd constraints. Contains copies of the units in /etc/systemd/system/ dcos.target.wants. They must be at the top folder as well as inside dcos.target.wants. Contains the ZooKeeper data.

2 ookeeper /var/lib/doc ker /var/lib/dco s /var/lib/mes os Contains the Docker data. Contains the DC/OS data. Contains the Mesos data. Important: Changes to /opt/mesosphere are unsupported. They can lead to unpredictable behavior in DC/OS and prevent upgrades. Prerequisites Your cluster must meet the software and hardware requirements. Configure your cluster 1. Create a directory named genconf on your bootstrap node and navigate to it. mkdir -p genconf 2. Create an ip-detect script. In this step, an IP detect script is created. This script reports the IP address of each node across the cluster. Each node in a DC/OS cluster

3 has a unique IP address that is used to communicate between nodes in the cluster. The IP detect script prints the unique IPv4 address of a node to STDOUT each time DC/OS is started on the node. Important: The IP address of a node must not change after DC/OS is installed on the node. For example, the IP address should not change when a node is rebooted or if the DHCP lease is renewed. If the IP address of a node does change, the node must be wiped and reinstalled. The script must return the same IP address as specified in the config.yaml. For example, if the private master IP is specified as in the config.yaml, your script should return this same value when run on the master. Create an IP detect script for your environment and save as genconf/ip -detect. This script needs to be UTF-8 encoded and have a valid shebang line. You can use the examples below. Use the AWS Metadata Server This method uses the AWS Metadata service to get the IP address: #!/bin/sh # Example ip-detect script using an external authority # Uses the AWS Metadata Service to get the node's internal # ipv4 address curl -fssl Use the GCE Metadata Server This method uses the GCE Metadata Server to get the IP address:

4 #!/bin/sh # Example ip-detect script using an external authority # Uses the GCE metadata server to get the node's internal # ipv4 address curl -fssl -H "Metadata-Flavor: Google" Use the IP address of an existing interface This method discovers the IP address of a particular interface of the node. If you have multiple generations of hardware with different internals, the interface names can change between hosts. The IP detect script must account for the interface name changes. The example script could also be confused if you attach multiple IP addresses to a single interface, or do complex Linux networking, etc. #!/usr/bin/env bash set -o nounset -o errexit export PATH=/usr/sbin:/usr/bin: /usr/sbin:/usr/bin:$path echo $(ip addr show eth0 grep -Eo '[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\ Use the network route to the Mesos master This method uses the route to a Mesos master to find the source IP address to then communicate with that node. In this example, we assume that the Mesos master has an IP address of You can use any language for this script. Your

5 Shebang line must be pointed at the correct environment for the language used and the output must be the correct IP address. #!/usr/bin/env bash set -o nounset -o errexit -o pipefail export PATH=/sbin:/usr/sbin:/bin:/usr/bin: /sbin:/usr/sbin:/bin:/usr/bin:$path MASTER_IP=$( $(dig +short master.mesos true) MASTER_IP=${MASTER_IP: } INTERFACE_IP=$( $(ip r g ${MASTER_IP} \ awk -v master_ip=${master_ip} ' BEGIN { ec = 1 } { } if($1 == master_ip) { print $7 ec = 0 } else if($1 == "local") { print $6 ec = 0 } if (ec == 0) exit; END { exit ec } ') echo $INTERFACE_IP 3. Create a configuration file and save as genconf/config.yaml. In this step you create a YAML configuration file that is customized for your environment. DC/OS uses this configuration file during installation to generate your cluster installation files. You can use this template to get started. This template specifies 3 masters, 5 private agents, 1 public agent, a custom proxy, and SSH configuration specified. If your servers are installed with a domain name in your /etc/resolv.conf, you should add dns_search to your conf ig.yaml file. For parameters descriptions and configuration examples, see the documentation. Tips:

6 If Google DNS is not available in your country, you can replace the Google DNS servers and with your local DNS servers. If you specify master_discovery: static, you must also create a script to map internal IPs to public IPs on your bootstrap node (e.g., / genconf/ip-detect-public ). This script is then referenced in ip_de tect_public_filename: <path-to-ip-script>. --- agent_list: - <agent-private-ip-1> - <agent-private-ip-2> - <agent-private-ip-3> - <agent-private-ip-4> - <agent-private-ip-5> # Use this bootstrap_url value unless you have moved the DC/OS installer as bootstrap_url: file:///opt/dcos_install_tmp cluster_name: <cluster-name> exhibitor_storage_backend: static master_discovery: static ip_detect_public_filename: <path-to-ip-script> master_list: - <master-private-ip-1> - <master-private-ip-2> - <master-private-ip-3> public_agent_list: - <public-agent-private-ip> resolvers: ssh_port: 22 ssh_user: <username> use_proxy: 'true' http_proxy: https_proxy: no_proxy: - 'foo.bar.com' - '.baz.com' 4. Copy your private SSH key to genconf/ssh_key. For more information,

7 see the ssh_key_path parameter. cp <path-to-key> genconf/ssh_key && chmod 0600 genconf/ssh_key Install DC/OS In this step you create a custom DC/OS build file on your bootstrap node and then install DC/OS across your cluster nodes with SSH. With this installation method you create a bootstrap server that uses your SSH key and connects to every node to automate the deployment. Important: Do not install DC/OS until you have these items working: ip-detect script, DNS, and NTP everywhere. For help with troubleshooting, see the documentation. If something goes wrong and you want to rerun your setup, use these cluster cleanup instructions. To install DC/OS: 1. Download the DC/OS installer to your root directory. curl -O 2. From your home directory, run the DC/OS installer shell script on your bootstrapping master nodes to generate a customized DC/OS build. The

8 setup script extracts a Docker container that uses the generic DC/OS install files to create customized DC/OS build files for your cluster. The build files are output to./genconf/serve/. Tip: You can view all of the automated command line installer options with the dcos_generate_config.sh --help flag. sudo bash dcos_generate_config.sh --genconf Here is an example of the output. Extracting image from this script and loading into docker daemon, this step dcos-genconf.e060aa49ac4ab62d5e-1e14856f55e5d5d07b.tar Running mesosphere/dcos-genconf docker with BUILD_DIR set to /home/centos/g ==== ==> EXECUTING CONFIGURATION GENERATION... At this point your directory structure should resemble: dcos-genconf.<hash>.tar dcos_generate_config.sh genconf cluster_packages.json config.yaml ip-detect serve ssh_key state 3. Install the cluster prerequisites, including system updates, compression utilities (UnZip, GNU tar, and XZ Utils), and cluster permissions. For a full

9 list of cluster prerequisites, see this documentation. sudo bash dcos_generate_config.sh --install-prereqs Here is an example of the output. Running mesosphere/dcos-genconf docker with BUILD_DIR set to /home/centos/g ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> EXECUTING INSTALL PRERE ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> START install_prereqs ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> STAGE install_prereqs ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> STAGE install_prereqs ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> END install_prereqs wit ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> SUMMARY ==== ==> dcos_installer.action_lib.prettyprint:: 2 out of 2 hosts successfully 4. Run a preflight script to validate that your cluster is installable. sudo bash dcos_generate_config.sh --preflight Here is an example of the output. Running mesosphere/dcos-genconf docker with BUILD_DIR set to /home/centos/g ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> EXECUTING PREFLIGHT ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> START run_preflight ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> STAGE preflight ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> STAGE preflight ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> STAGE preflight_cleanup ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> STAGE preflight_cleanup ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> END run_preflight with ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> SUMMARY

10 ==== ==> dcos_installer.action_lib.prettyprint:: 2 out of 2 hosts successfully Tip: For a detailed view, you can append log level debug ( -v ) to your command. For example sudo bash dcos_generate_config.sh --pref light -v. 5. Install DC/OS on your cluster. sudo bash dcos_generate_config.sh --deploy Here is an example of the output. Running mesosphere/dcos-genconf docker with BUILD_DIR set to /home/centos/g ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> EXECUTING DC/OS INSTALL ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> START deploy_master ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> STAGE deploy_master ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> STAGE deploy_master_cle ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> END deploy_master with ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> SUMMARY ==== ==> dcos_installer.action_lib.prettyprint:: 1 out of 1 hosts successfully ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> START deploy_agent ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> STAGE deploy_agent ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> STAGE deploy_agent_clea ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> END deploy_agent with r ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> SUMMARY ==== ==> dcos_installer.action_lib.prettyprint:: 1 out of 1 hosts successfully 6. Run the DC/OS diagnostic script to verify that services are up and running.

11 sudo bash dcos_generate_config.sh --postflight Here is an example of the output. Running mesosphere/dcos-genconf docker with BUILD_DIR set to /home/centos/g ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> EXECUTING POSTFLIGHT ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> START run_postflight ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> STAGE postflight ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> STAGE postflight ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> STAGE postflight_cleanu ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> STAGE postflight_cleanu ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> END run_postflight with ==== ==> dcos_installer.action_lib.prettyprint:: ==== ==> SUMMARY ==== ==> dcos_installer.action_lib.prettyprint:: 2 out of 2 hosts successfully 7. Monitor Exhibitor and wait for it to converge at -ip>:8181/exhibitor/v1/ui/index.html. Tip: If you encounter errors such as Time is marked as bad, adjtim ex, or Time not in sync during Post-Flight, verify that Network Time Protocol (NTP) is enabled on all nodes. For more information, see the system requirements.

12 When the status icons are green, you can access the DC/OS web interface. 8. Launch the DC/OS web interface at and login. If this doesn t work, take a look at the troubleshooting docs

13 You are done!

14 (Optional) Backup your DC/OS installer files It is recommended that you save your DC/OS installer file immediately after installation completes and before you start using DC/OS. These installer files can be used to add more agent nodes to your cluster, including the public agent node. 1. From your bootstrap node, navigate to the genconf/serve directory

15 and package the contents as dcos-install.tar : # <Ctrl-C> to exit installer cd genconf/serve sudo tar cf dcos-install.tar * 2. Copy the dcos-install.tar file to another location for backup. For example, you can use Secure Copy (scp) to copy dcos-install.tar to your home directory: exit scp -i $username@$node-ip:~/genconf/serve/dcos-install.tar ~ Next Steps Add users to your cluster Add a public agent post-installation Install the DC/OS Command-Line Interface (CLI) Troubleshooting DC/OS installation Uninstalling DC/OS Add more agent nodes After DC/OS is installed and deployed across your cluster, you can add more agent nodes. Prerequisite:

16 The agent nodes must meet the hardware and software prerequisites. 1. Update the config.yaml file with the additional agent nodes. For parameters descriptions and configuration examples, see the documentation. 2. Run the installation steps beginning with installing the cluster prerequisites: sudo bash dcos_generate_config.sh --install-prereqs Important: You can ignore the errors that are shown. For example, during the --preflight you may see this error: 18:17:14:: Found an existing DC/OS installation. To reinstall DC/ 18:17:14:: first uninstall DC/OS then run dcos_install.sh. To uni 18:17:14:: documentation provided with DC/OS. 18:17:14:: 18:17:14:: 18:17:14:: ==== ==> :22 FAILED