How to install CLI under DC/OS On-Premises
This article mainly introduces how to install CLI under DC/OS On-Premises, has a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, the following let the editor take you to understand.
# Environment
OS:CentOS 7.2 64bit Kernel:4.3.3IP: DCOSBootstrap 172.30.250.175 DCOSmaster1 172.30.250.210 DCOSmaster2 172.30.250.211 DCOSmaster3 172.30.250.178DCOSnode1 172.30.250.18 DCOSnode2 172 .30.250.181DCOSnode3 172.30.250.182
Local platform only supports centos and coreos, other operating systems do not support, I use centos7.2, I upgrade the 4.3.3 kernel, the default 3.10 kernel is also possible, need to support the kernel of overlay module. The seven machines are divided into three types:
Bootstrap: for DC/OS installation master: run DC/OSnode: run service
There are three modes of installation, GUI,CLI and advanced mode, which are installed using CLI on the virtual machine.
# start the installation
# # step 1: configure the boot node ssh to be password-free to all nodes
1. All nodes generate ssh keys
$ssh-genkey
two。 Execute the following command on the boot node to enable password-free ssh to the remote node
$ssh-copy-id-I ~ / .ssh/id_rsa.pub $remote-host$ssh $remote-host
# # step 2: boot the node to install docker
1. Upgrade the kernel, turn off the firewall, install dependency packages, add user groups
$sudo yum update $sudo systemctl stop firewalld & & sudo systemctl disable firewalld$sudo yum install-y tar xz unzip curl ipset$sudo sed-is / SELINUX=enforcing/SELINUX=permissive/g / etc/selinux/config $sudo groupadd nogroup
two。 Generate three files, namely, open overlay, configure SYSTEMD, and add Docker repository
$sudo tee / etc/modules-load.d/overlay.conf STAGE install_prereqs==== > OUTPUT FOR install_prereqs==== > END install_prereqs with returncode: 0 SUMMARY FOR install_prereqs6 out of 6 hosts successfully completed install_prereqs stage.==== > END OF SUMMARY FOR install_prereqs
The above command can add the-v parameter to show the installation process, and you can see the following information:
# / bin/sh# setenforce is in this pathPATH=$PATH:/sbindist=$ (cat / etc/*-release | sed-n's @ ^ ID = "\ (. *\)" $@\ 1roomp') if ([x$dist! = 'xrhel'] & & [x$dist! =' xcentos']); then echo "$dist is not supported. Only RHEL and CentOS are supported "> & 2 exit 0fiversionmakers $(cat / etc/*-release | sed-n's @ ^ version _ ID="\ (. *\) "$@\ 1fiversion7] if [$version-lt 7]; then echo" $version is not supported. Only > = 7 version is supported "> & 2 exit 0fisudo setenforce 0 & & sudo sed-I's / ^ SELINUX =. * / SELINUX=disabled/g' / etc/sysconfig/selinuxsudo tee / etc/yum.repos.d/docker.repo STAGE preflight==== > STAGE preflight_cleanup==== > STAGE preflight==== > STAGE preflight_cleanup==== > OUTPUT FOR run_preflight==== > END run_preflight with returncode: zero cycles = > SUMMARY FOR run_preflight6 out of 6 hosts successfully completed run_preflight stage.==== > END OF SUMMARY FOR run_preflight
6. Install DC/OS to all nodes
¥sudo bash dcos_generate_config.sh-deployRunning mesosphere/dcos-genconf docker with BUILD_DIR set to / root/genconf==== > EXECUTING DC/OS INSTALLATION==== > START install_dcos==== > STAGE deploy==== > STAGE deploy_cleanup==== > STAGE deploy==== > STAGE deploy==== > STAGE deploy_cleanup==== > STAGE deploy_cleanup==== > STAGE deploy==== > STAGE deploy_cleanup==== > OUTPUT FOR install_dcos==== > END install_dcos with returncode: 0mm cake = > SUMMARY FOR install_dcos6 out of 6 hosts successfully completed install_dcos stage.==== > END OF SUMMARY FOR install_dcos
7. Confirm that the service starts properly
Running mesosphere/dcos-genconf docker with BUILD_DIR set to / home/centos/genconf==== > 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_cleanup==== > dcos_installer.action_lib.prettyprint:: = > STAGE postflight_cleanup==== > dcos_installer.action_lib.prettyprint:: = = > END run_postflight with returncode: 0 out of hosts successfully completed run_postflight stage = > dcos_installer.action_lib.prettyprint:: = > SUMMARY==== > dcos_installer.action_lib.prettyprint:: 6 out of 6 hosts successfully completed run_postflight stage.
# # finally, log in to # the ip of any master node can be logged in to the monitoring and management page of zookeeper, address: http://183.131.54.89:8181/exhibitor/v1/ui/index.html
# choose the ip of any master node in the login page of DC/OS. For example, the user name and password of http://183.131.54.89, is configured in config.yaml, and the page after login
Tip:183.131.54.89 is the public network ip # # port of node 172.30.250.177 description:
Port 80 mesos-uiport 53 mesos-dnsport 15055 dcos-historyport 5050 mesos-master port 2181 zookeeperport 8080 marathonport 3888 zookeeperport 8181 exhibitorport 8123 mesos-dns thank you for reading this article carefully. I hope the article "how to install CLI under DC/OS On-Premises" shared by the editor will be helpful to you. At the same time, I also hope that you will support and pay attention to the industry information channel. More related knowledge is waiting for you to learn!
