Billing Support in Mesos – Motivation – Pipeline

Motivation

• Companies build Container as a Service platforms (sloppy.io)
• Learning patterns and understanding own cluster
• Metrics over opinions!

Prior art

(hacking in Cabo with Niklas)

• Status updates only
• Stored in circular buffer in Mesos
• Aggregation and visualization in Mesos

What's new

• Reservations, allocations, actual usage, revocable resources
• Push-based to subscribers (streaming HTTP)
• Storage and visualization are separated from each other (and from Mesos)

Pipeline

Mesos endpoint

↓

Mesos-InfluxDB bridge

↓

InfluxDB

↓

Grafana

Additions to Mesos: accounting events

struct AccountingEvent {
    std::string id;
    FrameworkID frameworkId;
    Resource resource;
    std::string what; // reservation, allocation, usage
    process::Time timestamp;
  };

Additions to Mesos: /accounting endpoint

External tools: InfluxDB

External tools: Grafana