Apache Mesos

The full text of this page is only available to our customers.

Please login or sign up. You may also need to provide your support ID if you have not already done so.

Discover with BMC Discovery
download

This product can be discovered by Enterprise version of BMC Discovery, but you can still Download our free Community Edition to discover other products !

What is this?
This is a product information page, containing details of the information that BMC Discovery gathers about a product and how it is obtained.
Product Name
Mesos
Publisher Page
Apache
Category
Workload Scheduling and Automation Software
Release
TKU 2017-July-1
Change History
Apache Mesos - Change History
Reports & Attributes
Apache Mesos - Reports & Attributes
Publisher Link
Apache

Product Description

Mesos is built using the same principles as the Linux kernel, only at a different level of abstraction. The Mesos kernel runs on every machine and provides applications (e.g., Hadoop, Spark, Kafka, Elasticsearch) with API’s for
resource management and scheduling across entire datacenter and cloud environments. In other words - Apache Mesos is an open source cluster manager that simplifies running applications on a scalable cluster of servers

Architecture

Known Versions

  • 0.12
  • 0.13
  • 0.14
  • 0.15
  • 0.16
  • 0.17
  • 0.18
  • 0.19
  • 0.20
  • 0.21
  • 0.22
  • 0.23
  • 0.24
  • 0.25
  • 0.26
  • 0.27
  • 0.28
  • 1.0
  • 1.1
  • 1.2

Software pattern summary

Product componentOS typeVersioningPattern Depth
MesosMasterUNIXActive/PackageInstance-Based
MesosAgentUNIXActive/PackageInstance-Based
MesosClusterUNIXNo versioningInstance-Based

Platforms Supported by the Pattern

All the patterns discover Apache Mesos deployed on UNIX.

Identification

Software Instance Triggers

PatternTrigger NodeAttributeConditionArgument
MesosMasterDiscoveredProcesscmdmatchesunix_cmd 'mesos-master'
MesosAgentDiscoveredProcesscmdmatchesunix_cmd 'mesos-slave'
MesosClusterSoftwareInstance type ='Apache Mesos Master'
and
cluster_idexists

Simple Identification Mappings

The following processes are identified by the pattern.

NameCondition
Apache Mesos Masterunix_cmd "mesos_master"
Apache Mesos Agentunix_cmd "mesos_slave"


Versioning

Apache Mesos Master and Apache Mesos Agent patterns use the same versioning approaches:

 Active

Pattern executes:

  • <process_cmd> --version

From the output like : mesos 1.2.0 full version is extracted by means of regex:

  • (?i)mesos\s*(\d+(?:\.\d+)*)

Package

If active versioning approach fails pattern looks for the "mesos" package and takes its version.

Attributes

Listening Ports

Listening ports for Master SI are extracted from process arguments by means of regex:

  • (?i)--port=(\d+)

Expected: 5050

Mesos Master Leader

Mesos Master pattern will run command:

curl http://localhost:8080/v2/leader

The output will show the IP of the leader of the quorum.

E.g.

{"leader":"172.25.144.111:8080"}

Node IP

Target pattern extracts Node IP attribute value from /etc/mesos-master/ip or /etc/mesos-slave/ip file relatively.

Using regex:

  • (\d+(?:\.\d+){3})

If such approach fails, tries to extract the information from process arguments by meansd of regex:

  • (\d+(?:\.\d+){3})

If the latest approach failed then pattern tries to extract hostname using regex :

  • hostname:(\S+\.com)

If hostname is extracted it is resolved to IP address.

Cluster ID

Both Apache Mesos Master and Apache Mesos Agent patterns extract cluster_id(which is the list of all cluster nodes addresses) from the  /etc/mesos/zk file by means of regex:

  • zk:\/\/(.+)/mesos

If such approach fails, tries to extract the information from process arguments by means of regex:

  •  zk:\/\/(.+)/mesos

State and Status

Both Apache Mesos Master and Apache Mesos Agent patterns run

either

  • status mesos-master

or

  • status mesos-slave

command and extracts staus and state values from the command output, which can be like:

mesos-master start/running, process 22207

Apache Mesos Master

Relations :

  • If Leader state is enabled - Manages Apache Mesos Cluster
  • Client-Server relations to Apache Zookeeper server

Apache Mesos Agent

Cluster: Apache Mesos Cluster

 

AttributesDescription/CommentSource
node typeCluster 
typeApache Mesos Cluster 
key <cluster_id>/<cluster_type> 
name <cluster_id> inherited from trigger 'Apache Mesos Master' SI
short_name<short_cluster_id>  extracted from <cluster_id>
id  <cluster_id>inherited from trigger 'Apache Mesos Master' SI
Links
Service:SoftwareService:ServiceProvider:SoftwareInstance

type = "Apache Mesos Master"

or

type = "Apache Mesos Agent"

 
Container:Containment:Contained:ClusterMember member_type := "Host in Mesos Cluster" 
HostContainer:HostContainment:ContainedHost:Host  
ManagedElement:Management:Manager:SoftwareInstancetype = 'Apache Mesos Master'

 

Subject Matter Expertise

Subject Matter Expert input will be welcome on any other potential approaches not discussed.

Testing

The patterns have been tested against the live installations on UNIX platforms.

Information Sources

More information can be found here

Open Issues

There are no known open issues with this pattern.
The full text of this page is only available to our customers.

Please login or sign up. You may also need to provide your support ID if you have not already done so.

© Copyright 2003-2017 BMC Software, Inc, Legal notices
Click here for the provisions described in the BMC License Agreement and Order related to third party products or technologies included in the BMC Product.