openstack/deb-sahara
Code Issues Proposed changes
a0162c8639
deb-sahara/doc/source/architecture.rst
Xi Yang ab4df88b0c Refine the doc for sahara 
As a rookie stepping into sahara, I just find some nits
that can be corrected in the doc. This patch is going to
address them.

Change-Id: If8eadce0db8b5fca22d495ed5ed48abbda93aba1
2015-10-30 09:18:19 +08:00

1.2 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.
  • 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).