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

Compare with Current View Page History

Version 1 Next »

The following page describes proposed changes to the Apache Ambari JIRA to better help categorize and organize JIRAs around tasks, bugs and improvements across the core project + contributions.

Components

CurrentProposed RenameDescriptionAction
agentambari-agentJIRAs related to the Ambari Agent.
  • Rename this component from "agent" to "ambari-agent"
Ambari-SCOMcontribJIRAs related to contributions under "contrib", such as Ambari SCOM
  • Rename this component from "Ambari-SCOM" to "contrib"
  • Use a label with "contrib" component to categorize Ambari SCOM specific JIRAs.
buildinfraJIRAs related to project infrastructure including builds, releases mechanics and automation
  • Rename this component from "build" to "infra"
clientambari-clientJIRAs related to the Ambari Client.
  • Rename this component from "client" to "ambari-client"
 ambari-webNew component specifically for Ambari Web.
  • Create new component "ambari-web"
controllerambari-serverJIRAs related to the Ambari Server.
  • Rename this component from "controller" to "ambari-server"
 ambari-shellNew component specifically for Ambari Shell.
  • Create new component "ambari-shell"
 ambari-adminNew component specifically for Ambari Admin.
  • Create new component "ambari-admin"
documentation<no change>JIRAs related to project documentation including the wiki. 
site<no change>JIRAs related to the project site http://ambari.apache.org/ 
stackstacksJIRAs related to Ambari Stacks.
  • Rename this component from "stack" to "stacks"
  • Use a label with "stacks" component to categorize stack-specific JIRAs, such as HDP.
test<remove> 
  • Remove this component
  • Move all JIRAs into "infra" component
viewsambari-viewsJIRAs related to the Ambari Views framework. Specific Views that are built on the framework will be handled with labels.
  • Rename this component from "views" to "ambari-views"
  • Use a label with "ambari-views" component to categorize stack-specific JIRAs, such as "files" or "slider".
 blueprintsJIRAs related to Ambari Blueprints.
  • Create new component "blueprints"
 alertsJIRAs related to Ambari Alerts system.
  • Create new component "alerts"
 metricsJIRAs related to Ambari Metrics system.
  • Create new component "metrics"
 securityJIRAs related to Ambari security features, including Kerberos.
  • Create new component "security"

Use of Labels

In certain cases, the component listed above is "too broad" and you want to designate JIRAs to a specific area of that component. To handle these scenarios, we propose a combination of component + labels. Some examples:

Feature AreaDescriptionComponentLabel
HDP StackThese are specific Stack implements for HDP.stacksHDP
BigTopThis is a specific Stack implement for BigTop.stacksBigTop
Files ViewThis is a specific view implementation for Files.ambari-viewsFiles
Ambari SCOMThis is a specific contribution of a Management Pack for Microsoft System Center.contribAmbari-SCOM

 

 

 

 

  • No labels