Skip to main content

DC/OS 2.2 Production Installation on Linux | DC/OS Unistallation

DC/OS 2.2 Production installation on Linux:

Make certain to refer Before Installation

01. Download DCOS V2.2 installation file -dcos_generate_config.sh from
https://docs.d2iq.com/mesosphere/dcos/2.0/release-notes/2.0.2/ for Open source
02. Save it locally on laptop or desktop.
03. Move it to Bootstrap node /dcos/dcos_software
04. Make directory /dcos/dcos_software/genconf
05. Create file /dcos/dcos_software/genconf/config.yaml

bootstrap_url: http://<BootStrapNode_IP>:80
cluster_name: 'dcoscluster'
exhibitor_storage_backend: static
master_discovery: static
master_list:
- <IP_Address_Master>
resolvers:
- 10.86.1.1
- 10.86.2.1
- 10.1.1.1
security: disabled
oauth_enabled: 'false'
use_proxy: 'false'

06. Execute #ifconfig and find out ens32 attached with ip address of the host
07. Create genconf directory on bootstrap node.
08. Create genconf/ip-detect script
09. Create file /dcos/dcos_software/genconf/ip-detect and include following. Make sure to get actual ip address when you execute file

#!/usr/bin/bash
set -o nounset -o errexit
export PATH=/usr/sbin:/usr/bin:$PATH
echo $(ip addr show ens32 | grep -Eo '[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}' | head -1)

10. Execute /dcos/dcos_software/dcos_generate_config.sh
# ./dcos_generate_config.sh
Extracting image from this script and loading into docker daemon, this step can take a few minutes
dcos-genconf.236d4cef2fdf0fe613-50baa2ec85af8be41c.tar
Loaded image: mesosphere/dcos-genconf:236d4cef2fdf0fe613-50baa2ec85af8be41c
====> EXECUTING CONFIGURATION GENERATION
Generating configuration files...
Options for dcos_generate_config.sh:
 ./dcos_generate_config.sh --help
usage: dcos_generate_config.sh [-h] [--hash-password [password]]
                               [--generate-node-upgrade-script [installed_cluster_version]]
                               [-v] [--version] [--web] [--genconf]
                               [--aws-cloudformation]
DC/OS Install and Configuration Utility
optional arguments:
  -h, --help            show this help message and exit
  --hash-password [password]
                        Hash a password and print the results to copy into a config.yaml.
  --generate-node-upgrade-script [installed_cluster_version]
                        Generate a script that upgrades DC/OS nodes running
                        installed_cluster_version
  -v, --verbose  Verbose log output (DEBUG).
  --version        Print the DC/OS version
  --web             Run the web interface
  --genconf       Create DC/OS install files customized according to genconf/config.yaml.
  --aws-cloudformation  Generate AWS Advanced AWS CloudFormation templates
                        using the provided config
11. dcos_generate_config.sh 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/

 Directory structure should looks like as follows

12. Enable overlay for Docker in /etc/modules-load.d/overlay.conf
Following command will create file - overlay.conf at /etc/modules-load/ and add line overlay in it
# tee /etc/modules-load.d/overlay.conf <<-'EOF'
overlay
EOF
13. Run nginx docker container
# docker run -d -p 80:80 -v ${PWD}/genconf/serve:/usr/share/nginx/html:ro nginx
14.On dcos each master execute following to get dcos_install.sh file
curl -O http://<BootstrapNode_IP>:<Port_NoOfConfigFile>/dcos_install.sh15.On dcos agent execute following to get dcos_install.sh file
curl -O http://<BootstrapNode_IP:<Port_NoOfConfigFile>/dcos_install.sh

16. Execute ./dcos_install.sh master on DCOS master.
17. Execute ./dcos_install.sh master on DCOS slave_public to install DCOS public slave
DCOS has Bootstrap node, master node, public slave node, private slave node
18. Launch DC/OS web interface at http://<master_node_IP>. If this does not work
visit - https://dcos.io/ and refer troubleshooting section .
19. To unistall DC/OS download dcos_uninstall.sh script and execute on host from where you want uninstall DC/OS

Explore System Requirement -
https://docs.d2iq.com/mesosphere/dcos/1.11/installing/production/system-requirements/#port-and-protocol

Ref.:
https://docs.d2iq.com/mesosphere/dcos/1.11/installing/production/deploying-dcos/installation/

Labels

Labels:
Location: San Francisco, CA, USA

Comments

Post a Comment

Popular posts from this blog

MySQL InnoDB cluster troubleshooting | commands

Cluster Validation: select * from performance_schema.replication_group_members; All members should be online. select instance_name, mysql_server_uuid, addresses from  mysql_innodb_cluster_metadata.instances; All instances should return same value for mysql_server_uuid SELECT @@GTID_EXECUTED; All nodes should return same value Frequently use commands: mysql> SET SQL_LOG_BIN = 0;  mysql> stop group_replication; mysql> set global super_read_only=0; mysql> drop database mysql_innodb_cluster_metadata; mysql> RESET MASTER; mysql> RESET SLAVE ALL; JS > var cluster = dba.getCluster() JS > var cluster = dba.getCluster("<Cluster_name>") JS > var cluster = dba.createCluster('name') JS > cluster.removeInstance('root@<IP_Address>:<Port_No>',{force: true}) JS > cluster.addInstance('root@<IP add>,:<port>') JS > cluster.addInstance('root@ <IP add>,:<port> ') JS > dba.getC...
Post a Comment
Read more

InnoDB cluster Remove Instance Force | Add InnoDB instance

InnoDB cluster environment UUID is different on node: To fix it stop group replication, remove instance (use force if require), add instance back Identify the node which is not in sync: Execute following SQL statement on each node and identify the node has different UUID on all nodes. mysql> select * from mysql_innodb_cluster_metadata.instances; Stop group replication: Stop group replication on the node which does not have same UUID on all nodes. mysql > stop GROUP_REPLICATION; Remove instances from cluster: Remove all secondary node from the cluster and add them back if require. $mysqlsh JS >\c root@<IP_Address>:<Port_No> JS > dba.getCluster().status() JS > dba.getCluster () <Cluster:cluster_name> JS > var cluster = dba.getCluster("cluster_name"); JS >  cluster.removeInstance('root@<IP_Address>:<Port_No>'); If you get "Cluster.removeInstance: Timeout reached waiting......" JS > cluster.removeInstance(...
2 comments
Read more

Oracle E-Business Suite Online Patch Phases executing adop

Following description about Oracle E-Business Suite is high level and from documentation https://docs.oracle.com/cd/E26401_01/doc.122/e22954/T202991T531062.htm#5281339 for in depth and detail description refer it. The online patching cycle phases: Prepare Apply Finalize Cutover Cleanup Prepare phase: Start a new online patching cycle, Prepares the environment for patching. $ adop phase=prepare Apply phase: Applies the specified patches to the environment. Apply one or more patches to the patch edition. $ adop phase=apply patches=123456,789101 workers=8 Finalize phase: Performs any final steps required to make the system ready for cutover. Perform the final patching operations that can be executed while the application is still online. $ adop phase=finalize Cutover phase: Shuts down application tier services, makes the patch edition the new run edition, and then restarts application tier services. This is the only phase that involves a brief ...
Post a Comment
Read more