From 72d03963f9f5ce9106aa569dd5516f4500960cf1 Mon Sep 17 00:00:00 2001 From: Michael Ionkin Date: Thu, 15 Sep 2016 14:51:24 +0300 Subject: [PATCH] [DOC] update overview doc Change-Id: Ib38d3928bf6aec01911e5bfb2c9c9a570f3b8ec8 --- doc/source/overview.rst | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/doc/source/overview.rst b/doc/source/overview.rst index 946fee17..e0135399 100644 --- a/doc/source/overview.rst +++ b/doc/source/overview.rst @@ -63,6 +63,8 @@ The sahara product communicates with the following OpenStack services: instances. * Networking (neutron) - provides networking services to data processing clusters. +* DNS service (designate) - provides ability to communicate with cluster + instances and Hadoop services by their hostnames. * Telemetry (ceilometer) - used to collect measures of cluster usage for metering and monitoring purposes. * Shared file systems (manila) - can be used for storage of framework job @@ -87,7 +89,7 @@ For fast cluster provisioning a generic workflow will be as following: * for base images without a pre-installed framework, sahara will support pluggable deployment engines that integrate with vendor tooling. * you can download prepared up-to-date images from - http://sahara-files.mirantis.com/images/upstream/liberty/ + http://sahara-files.mirantis.com/images/upstream/ * define cluster configuration, including cluster size, topology, and framework parameters (for example, heap size): @@ -148,13 +150,8 @@ deployment. Users may choose one of the pre-configured Cluster Templates to start a Cluster. To get access to VMs after a Cluster has started, the user should specify a keypair. -Sahara provides several constraints on cluster framework topology. JobTracker -and NameNode processes could be run either on a single VM or two separate -VMs. Also a cluster could contain worker nodes of different types. Worker -nodes could run both TaskTracker and DataNode, or either of these processes -alone. Sahara allows a user to create a cluster with any combination of these -options, but it will not allow the creation of a non-working topology (for -example: a set of workers with DataNodes, but without a NameNode). +Sahara provides several constraints on cluster framework topology. You can see +all constraints in the documentation for the appropriate plugin. Each Cluster belongs to an Identity service project determined by the user. Users have access only to objects located in projects they have access to.