ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Nettleton" <>
Subject Review Request 27250: Proper handling exporting of addresses with Blueprints
Date Mon, 27 Oct 2014 21:58:42 GMT

This is an automatically generated e-mail. To reply, visit:

Review request for Ambari, John Speidel and Nate Cole.

Repository: ambari


This patch implements a fix for AMBARI-7988.

The Blueprints config processor does not currently allow service
  config properties with the IP address of "" to be
  included in an exported Blueprint.

The following properties:


are not included in an exported Blueprint after a successful
  cluster deployment the Yarn Application Timeline Service

The problem occurs because the default values for these
  properties is typically "".  This is
  a special IP address that the current Blueprints processor
  does no recognize as a valid service address.  Currently,
  the processor will remove any properties that require
  host topology information, but don't have any valid hostname
  included in the property.

This patch resolves the problem by adding some handling
  code to the Blueprint export processing.  If a property, such
  as the ones listed above, uses the default "" address, then
  this property is now allowed in the exported blueprint, as this
  is a valid server address, but is not directly tied to the specific
  server topology of a given cluster.  If the user overrides these
  properties, then the hostname substitution process/export process
  will work as before.

This patch also implements a new unit test to verify this change.





1. Ran the ambari-server unit tests with this patch applied (both trunk and 1.7.0), and all
unit tests are passing with this change.
2. Manually verified the fix on 1.7.0. 
3. Manually verified the fix on trunk.


Robert Nettleton

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message