The table below provides the list of service-related commands and their descriptions:
|or2-manage-service ... -s ambari -a -c cluster_name -k key
||Starts the service in the specified project and region
||Sets up an Ambari cluster for the project
|or2-describe-maestro-stack-resources -p project -r region -s cluster_stack_name
||Retrieves the information on the resources created in the Ambari cluster
|or2-describe-instances -p project -r region -l "cluster_name=your_cluster_name"
Further on this page, you can find the examples of the commands usage for Ambari Service manipulation.
Starting a One-Node Ambari Server and Configuring the Cluster
To activate the service and create an Ambari server, run the or2-manage-service (or2ms) command with --activate (-a) , --service-name (-s) ambari and other necessary flags:
or2ms -p project -r region -a -s ambari -c cluster_name -k key --customize
-c (--cluster-name) specifies the name for the newly created Ambari cluster.
-k (--key-name) the SSH key name that will be used for all Ambari resources.
--customize is an optional parameter that allows to customize the parameters defined in the service stack template, including the blueprint to be used, in case you
don't want to use the default one(see the details below).
Ambari Blueprint is a declarative definition of a cluster. With a Blueprint, you specify a Stack,
the Component layout and the Configurations to materialize a Hadoop cluster instance (via a REST API) without having to use the Ambari Cluster Install Wizard.
The service, when activated, starts an Ambari-server (CentOS6-template, MEDIUM) and reserves a cluster with the specified name and configuration parameters.
Configuring and Starting Cluster Nodes
When the Server is up and running, you can start setting up the Ambari-Agents and describe the cluster configuration parameters.
All the settings are taken from two files:
The blueprint file you specified at the Ambari-Serveractivation step. It provides the information on the software stack to be installed on the cluster's VMs.
The configuration file you specify with the or2-ambari-cluster command describes the cluster hardware stack (the number of VMs in each group, additional
volumes attached to those, etc.). The command is called as follows:
or2ac -p project -r region -c cluster_name -a create --config-file json
where -c is the name of the Ambari cluster you want to set up, and --config-file is the full path to a locally stored .json file with cluster
configurations (see Configuration Example below on this page) .
To make sure that the cluster was started successfully, use the or2-describe-services Maestro CLI command:
Before you start creating an Ambari cluster, please, make sure that the action will not exceed the project resource quota (either daily or monthly). If it does,
the cluster creation will fail, but some of the resources may remain active and billed.
To see your monthly quota usage info, please, call the command:
or2report -p project -r region -y year -m month -t quota
To see your project daily quota limitation, use:
or2dpro -p project --full
and see the volumeCreationInterval_count, instanceCreationInterval_count and maxVolumeSizw_GB values for resource creation and volumes size limits.
Manipulating Cluster Nodes
The or2-abmari-cluster (or2ac) command can also be used to start and stop all existing Ambari clusters at once:
To stop all the existing cluster instances, run the or2ac command with the -a stop parameter:
or2ac -c cluster_name -p project -r region -a stop
To start all the stopped Ambari cluster instances and all the services in Abmari, use the or2ac command with -a start parameter:
or2ac -c cluster_name -p project -r region -a start
There are several ways to get the information on the resources engaged in Ambari Service:
To get the service availability, the name of the stack that launched the service and the details on the Ambari Server, use:
or2dser -p project -r region
To get the information on the resources created in the Ambari cluster, use the following commands:
or2dmsr -p project -r region -s cluster_stack_name
or2din -p project -r region -l "cluster_name=your_cluster_name"
or2ac -p project -r region -a describe
When you start the Ambari service and the server is run, you can login to it using its DNS name and port 8080:
The server URL is also returned as a part of or2-describe-services command output.
Use the following credentials to login to the Ambari server in EPAM Cloud regions:
To login to the Ambari Server hosted in AWS, please, use the 'centos' login and the SSH key you specified at service start.
However, there is no information on the server until the Ambari cluster resources are up and running. After the or2-ambari-cluster command execution,
the information on the cluster resources appear on the Server. You will see an operation on maestro on the main toolbar, and if you click it,
you will get the statistics on the cluster resources setup:
It is strongly recommended not to perform any operations on the server till the setup is finished.
When the setup is completed, the Ambari service is ready to use.
The service usage price is defined by the price of the created Ambari Resources and will depend on the number and parameters of cluster VMs.
To get more detailed estimations, please, use our Cost Estimator tool.