You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

This capability is currently under development.

Ambari Views offer a systematic way to plug-in UI capabilities to surface custom visualization, management and monitoring features in Ambari Web. A "view" is a way of extending Ambari that allows 3rd parties to plug in new resource types along with the APIs, providers and UI to support them. In other words, a view is an application that is deployed into the Ambari container.

Terminology

The following section describes the basic terminology associated with views.

TermDescription
View NameThe name of the view. The view name identifies the view to Ambari.
View VersionThe version of the view. A unique view name can have multiple versions deployed in Ambari.
View PackageThis is the JAR package that contains the view definition and all view resources (server-side classes + dependencies and client-side assets) for a given version. See View Package for more information on the contents and structure of the package.
View DefinitionThis defines the view name, version, resources and required/optional configuration parameters for a view. The view definition file is included in the view package. See View Definition for more information on the view definition file syntax and features.
View InstanceAn unique instance of a view, that is based on a view definition and specific version that is configured. See Versions and Instances for more information.
View APIThe REST API for viewing the list of deployed views and creating view instances. See View API for more information.
Framework ServicesThe server-side of the view framework exposes certain services for use with your views. This includes persistence of view instance data and view eventing. See Framework Services for more information.

View Package

The assets associated with a view are delivered as a JAR package. The view definition file must be at the root of the package. UI assets and server-side classes are served from the root. Dependent Java libraries are placed in the WEB-INF/lib directory.

view.jar
|
|- view.xml
|
|- <server packages + classes>
|
|- <ui assets>
|
|_ WEB-INF
  |
  |_ lib/*.jar

Versions and Instances

Multiple versions of a given view can be deployed into Ambari and multiple instances of each view can be created for each version. For example, I can have a view named FILES and deploy versions 0.1.0 and 0.2.0. I can then create instances of each version FILES{0.1.0} and FILES{0.2.0} allowing some Ambari users to have an older version of FILES (0.1.0), and other users to have the newer FILES version (0.2.0).

I can also create multiple instances for each version, configuring each differently. Using the example above, I can create two instances of the FILES{0.2.0} version, one instance that is configured a certain way and the second that is configured differently. This allows some Ambari users to use FILES one way, and other users a different way.

Useful Resources

ResourceLink
Views Framework API Docshttps://github.com/apache/ambari/blob/trunk/ambari-views/docs/index.md
Views Framework Exampleshttps://github.com/apache/ambari/tree/trunk/ambari-views/examples

 

 

  • No labels