Understanding Views Development, Persona, Versions, and Deployment
Views are basically web applications that can be “plugged in to” Ambari. Just like a typical web application, a View can include server-side resources and client-side assets. Server-side resources, which are written in Java, can integrate with external systems (such as cluster services) and expose REST end-points that are used by the view. Client-side assets, such as HTML, JavaScript, and CSS, provide the UI for the view that is rendered in the Ambari web interface.
Development
Ambari Views Framework Ambari exposes the Views Framework as the basis for View development. The Framework provides the following:
Method for describing and packaging a View
Method for deploying a View
Framework services for a View to integrate with Ambari
Method for managing View versions, instances, and permissions
The Ambari Views framework is separate from Views themselves. The framework is a core feature of Ambari that you use to create, deploy, integrate, and manage your own, custom views.
You develop and deliver a view by performing the following tasks:
Develop the View (similar to how you would build a web application)
Package the View (similar to a WAR)
Deploy the View to Ambari (using the Ambari Administration interface)
Create and configure instances of the View (performed by Ambari Admins)
Persona
Three user persona interact with Views:
- View developer
Person who builds the front end and back end of a View and uses the framework services available during development. The developer creates the View, resulting in a View package that is delivered to an Ambari Admin.
- Ambari Admin
Ambari user that has Ambari Admin privilege and uses the Views Management section of the Ambari Administration interface to create and managing instances of Views. Ambari Admin also deploys the View packages delivered by the View developer.
- View user
Ambari user that has access to one or more Views in the Ambari web (basically, the end user).
Versions
Each View must have a unique name, although it can have one or more View versions. Each View name and version combination is a single View package. After a View package is deployed, Ambari Admins can create View instances, each of which is identified by a unique View instance name. The Ambari Admin can then set access permissions for each View instance.
Deployment
Views can be deployed and managed in the operational Ambari Server, the Ambari Server operating your cluster. Alternatively, Views can be deployed and managed in one or more separate standalone Ambari Servers. Running standalone Ambari Server instances is useful when users who will access views will not have (and should not) have access to the operational Ambari Server. You can run one or more separate standalone Ambari Server instances to scale-out your solution for handling a large number of users.
The following table provides details about the Ambari views currently available to you, including two that have Technical Preview status.
|
View | Automatically Created? |
Description |
HDP Stacks |
Required Services |
|---|---|---|---|---|
| Yes |
Provides a visual way to configure YARN capacity scheduler queue capacity. |
HDP 2.3 or later |
YARN | |
| Yes |
Allows you to browse the HDFS file system. |
HDP 2.2 or later |
HDFS | |
| Yes |
Exposes a way to find, author, execute and debug Hive queries. |
HDP 2.3 or later |
HDFS, YARN, Hive | |
| No |
Supports migrating Hue artifacts to an Ambari View. |
HDP 2.4 or later |
Hue | |
| No |
Provides a way to author and execute Pig Scripts. |
HDP 2.2 or later |
HDFS, Hive, Pig | |
| No |
A tool to help deploy and manage Slider-based applications. This view has been marked deprecated. |
HDP 2.2 or later |
HDFS, YARN | |
| SmartSense | Yes |
Allows you to capture bundles, set bundle capture schedule, and view and download captured bundles. |
HDP 2.0 or later |
SmartSense |
| Storm | No |
Supports monitoring Storm cluster status and topologies. This view has been marked deprecated. |
HDP 2.5 or later |
Storm |
| Yes |
View information related to Tez jobs that are executing on the cluster. |
HDP 2.2.4.2 or later |
HDFS, YARN, Tez | |
| Workflow Designer | No |
This View is Tech Preview |
HDP 2.4 or later |
Oozie |
Subsequent chapters in this guide describe tasks performed by an Ambari Administrator to make Views available to users in their Ambari-managed cluster. This guide does not describe View development and packaging. You can learn more about the Ambari Views Framework from the following resources:
More Information
Running Ambari Server Standalone
https://cwiki.apache.org/confluence/display/AMBARI/Views
https://github.com/apache/ambari/tree/trunk/ambari-views/examples