Skip to main content

Mesosphere DC/OS Concept

Mesosphere DC/OS Concept:
  • DC/OS stands for Data Center Operating System
  • It is a distributed operating system, abstracts the cluster hardware, software resources, and provides container orchestration,package management, networking, logging and metrics, storage and volumes, and identity management.
  • DC/OS has system space / kernel space and user space.
  • System space is a protected area, not accessible to users, which involves low-level operations such as resource allocation, security, and process isolation
  • User space includes user applications, jobs, and services.
  • Built-in package manager can be used to install services into user space.
  • Each DC/OS node also has a host operating system which manages the underlying machine
  • Made up of many components - distributed systems kernel and a container orchestration engine Marathon.
  • DC/OS runs on a cluster of nodes, instead of a single machine.
  • The kernel of DC/OS is based on Apache Mesos distributed system kernel
  • A cluster manager, a container platform, and an operating system
  • Group of agent nodes, coordinated by a group of master nodes
  • It provides platform to containerized task such as Docker images.
  • Mesosphere DC/OS Enterprise may include closed-source components and multi-tenancy, fine-grained permissions secrets management, and end-to-end encryption.
  • Agent nodes provides resources to the cluster --> Resources are then bundled into resource offers made available to registered schedulers --> Schedulers accepts these offers and allocate resources to specific tasks by placing tasks on specific agent nodes --> The agent nodes then spawn executors to manage each task type and the executors run and manage the tasks assigned to them.
  • You can manage multiple machines as they are single computer.
  • Automates resource management, schedules process placement, facilitates inter-process communication,and simplifies the installation and management of distributed services.
  • Manages both resources and tasks running on the agent nodes.
  • DC/OS runs in the cluster and manages the life cycle of the tasks it launches.
  • There are two options available to interact with DC/OS, using them you can remotely manage and monitor cluster and cluster services web interface and command-line interface (CLI) facilitate
Ref.: https://docs.d2iq.com/mesosphere/dcos/2.0/overview/what-is-dcos/

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