Merge "Fix doc issues"
This commit is contained in:
commit
16d181e397
@ -3,7 +3,7 @@ Setting Up a Development Environment
|
||||
|
||||
This page describes how to setup a Sahara development environment by either
|
||||
installing it as a part of DevStack or pointing a local running instance at an
|
||||
external OpenStack. You should be able to debug and test your changes without
|
||||
external OpenStack. You should be able to debug and test your changes without
|
||||
having to deploy Sahara.
|
||||
|
||||
Setup a Local Environment with Sahara inside DevStack
|
||||
|
@ -85,7 +85,7 @@ For analytic as a service generic workflow will be as following:
|
||||
|
||||
* get the results of computations (for example, from Swift).
|
||||
|
||||
User’s Perspective
|
||||
User's Perspective
|
||||
------------------
|
||||
|
||||
While provisioning cluster through Sahara, user operates on three types of entities: Node Group Templates, Cluster Templates and Clusters.
|
||||
|
@ -13,7 +13,7 @@ The HDP plugin can make use of Ambari Blueprints for cluster provisioning.
|
||||
Apache Ambari Blueprints
|
||||
------------------------
|
||||
Apache Ambari Blueprints is a portable document definition, which provides a complete definition for an Apache Hadoop cluster, including cluster topology, components, services and their configurations. Ambari Blueprints can be consumed by the HDP plugin to instantiate a Hadoop cluster on OpenStack. The benefits of this approach is that it allows for Hadoop clusters to be configured and deployed using an Ambari native format that can be used with as well as outside of OpenStack allowing for clusters to be re-instantiated in a variety of environments.
|
||||
|
||||
|
||||
For more information about Apache Ambari Blueprints, refer to: https://issues.apache.org/jira/browse/AMBARI-1783. Note that Apache Ambari Blueprints are not yet finalized.
|
||||
|
||||
Operation
|
||||
@ -28,7 +28,7 @@ The HDP Plugin performs the following four primary functions during cluster crea
|
||||
Images
|
||||
------
|
||||
The Sahara HDP plugin can make use of either minimal (operating system only) images or pre-populated HDP images. The base requirement for both is that the image is cloud-init enabled and contains a supported operating system (see http://docs.hortonworks.com/HDPDocuments/HDP1/HDP-1.2.4/bk_hdp1-system-admin-guide/content/sysadminguides_ha_chap2_3.html).
|
||||
|
||||
|
||||
The advantage of a pre-populated image is that provisioning time is reduced, as packages do not need to be downloaded and installed which make up the majority of the time spent in the provisioning cycle. In addition, provisioning large clusters will put a burden on the network as packages for all nodes need to be downloaded from the package repository.
|
||||
|
||||
For more information about HDP images, refer to https://github.com/openstack/sahara-image-elements.
|
||||
|
@ -15,7 +15,7 @@ consistent state. We suggest the following options:
|
||||
To install with Fuel
|
||||
--------------------
|
||||
|
||||
1. Start by following the `Quickstart
|
||||
1. Start by following the `MOS Quickstart
|
||||
<http://software.mirantis.com/quick-start/>`_ to install and setup
|
||||
OpenStack.
|
||||
|
||||
@ -26,7 +26,7 @@ To install with Fuel
|
||||
To install with RDO
|
||||
-------------------
|
||||
|
||||
1. Start by following the `Quickstart
|
||||
1. Start by following the `RDO Quickstart
|
||||
<http://openstack.redhat.com/Quickstart>`_ to install and setup
|
||||
OpenStack.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user