openstack/sahara
Code Issues Proposed changes
744ea162d1
sahara/doc/source/architecture.rst
Nikita Konovalov 38b793d4e5 Updated Sahara arch diagram 
Format switched to .svg for better scalability

Closes-bug: #1373563
Change-Id: I2d65e452a02b61ee3c6bd1c02f469f2325917c39
2016-03-21 14:34:04 +03:00

1.3 KiB
Raw Blame History

Architecture

image

The Sahara architecture consists of several components:

  • Auth component - responsible for client authentication & authorization, communicates with the OpenStack Identity service (keystone).
  • DAL - Data Access Layer, persists internal models in DB.
  • Secure Storage Access Layer - persists the authentication data like passwords and private keys in a secure storage.
  • Provisioning Engine - component responsible for communication with the OpenStack Compute (nova), Orchestration (heat), Block Storage (cinder) and Image (glance) services.
  • Vendor Plugins - pluggable mechanism responsible for configuring and launching data processing frameworks on provisioned VMs. Existing management solutions like Apache Ambari and Cloudera Management Console could be utilized for that purpose as well.
  • EDP - ../userdoc/edp responsible for scheduling and managing data processing jobs on clusters provisioned by sahara.
  • REST API - exposes sahara functionality via REST HTTP interface.
  • Python Sahara Client - like other OpenStack components, sahara has its own python client.
  • Sahara pages - a GUI for the sahara is located in the OpenStack Dashboard (horizon).