You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by John Speidel <js...@hortonworks.com> on 2014/03/26 17:46:52 UTC
Review Request 19687: proxy user settings need to be set when provisioning
via a blueprint
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/19687/
-----------------------------------------------------------
Review request for Ambari, Nate Cole, Sid Wagle, and Tom Beerbower.
Bugs: AMBARI-5206
https://issues.apache.org/jira/browse/AMBARI-5206
Repository: ambari
Description
-------
In core-site, there are a bunch of proxyuser settings.
These are in the form of :
hadoop.proxyuser.<username>.hosts
hadoop.proxyuser.<username>.groups
These are dynamically generated property names because they contain the user name in the property name.
These are currently not present in the stack definitions and are generated by the UI.
These are currently not being set when provisioning via a blueprint.
Until this is completed, users that deploy clusters that require proxy user properties will have to add them to the blueprint manually.
Diffs
-----
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterResourceProvider.java 8afee6e
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterResourceProviderTest.java ca881d4
Diff: https://reviews.apache.org/r/19687/diff/
Testing
-------
unit tests:
- Updated existing unit test
- Ran all unit tests with one failure that I have determined to be unrelated
-- Will rerun unit tests prior to pushing change
functional tests:
- confirmed that proxy user configurations were set and that the oozie service test was successful
Thanks,
John Speidel
Re: Review Request 19687: proxy user settings need to be set when
provisioning via a blueprint
Posted by Sid Wagle <sw...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/19687/#review38622
-----------------------------------------------------------
Ship it!
Ship It!
- Sid Wagle
On March 26, 2014, 4:46 p.m., John Speidel wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19687/
> -----------------------------------------------------------
>
> (Updated March 26, 2014, 4:46 p.m.)
>
>
> Review request for Ambari, Nate Cole, Sid Wagle, and Tom Beerbower.
>
>
> Bugs: AMBARI-5206
> https://issues.apache.org/jira/browse/AMBARI-5206
>
>
> Repository: ambari
>
>
> Description
> -------
>
> In core-site, there are a bunch of proxyuser settings.
>
> These are in the form of :
> hadoop.proxyuser.<username>.hosts
> hadoop.proxyuser.<username>.groups
>
> These are dynamically generated property names because they contain the user name in the property name.
> These are currently not present in the stack definitions and are generated by the UI.
>
> These are currently not being set when provisioning via a blueprint.
>
> Until this is completed, users that deploy clusters that require proxy user properties will have to add them to the blueprint manually.
>
>
> Diffs
> -----
>
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterResourceProvider.java 8afee6e
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterResourceProviderTest.java ca881d4
>
> Diff: https://reviews.apache.org/r/19687/diff/
>
>
> Testing
> -------
>
> unit tests:
> - Updated existing unit test
> - Ran all unit tests with one failure that I have determined to be unrelated
> -- Will rerun unit tests prior to pushing change
>
> functional tests:
> - confirmed that proxy user configurations were set and that the oozie service test was successful
>
>
> Thanks,
>
> John Speidel
>
>
Re: Review Request 19687: proxy user settings need to be set when
provisioning via a blueprint
Posted by Tom Beerbower <tb...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/19687/#review38633
-----------------------------------------------------------
Ship it!
Ship It!
- Tom Beerbower
On March 26, 2014, 4:46 p.m., John Speidel wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19687/
> -----------------------------------------------------------
>
> (Updated March 26, 2014, 4:46 p.m.)
>
>
> Review request for Ambari, Nate Cole, Sid Wagle, and Tom Beerbower.
>
>
> Bugs: AMBARI-5206
> https://issues.apache.org/jira/browse/AMBARI-5206
>
>
> Repository: ambari
>
>
> Description
> -------
>
> In core-site, there are a bunch of proxyuser settings.
>
> These are in the form of :
> hadoop.proxyuser.<username>.hosts
> hadoop.proxyuser.<username>.groups
>
> These are dynamically generated property names because they contain the user name in the property name.
> These are currently not present in the stack definitions and are generated by the UI.
>
> These are currently not being set when provisioning via a blueprint.
>
> Until this is completed, users that deploy clusters that require proxy user properties will have to add them to the blueprint manually.
>
>
> Diffs
> -----
>
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterResourceProvider.java 8afee6e
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterResourceProviderTest.java ca881d4
>
> Diff: https://reviews.apache.org/r/19687/diff/
>
>
> Testing
> -------
>
> unit tests:
> - Updated existing unit test
> - Ran all unit tests with one failure that I have determined to be unrelated
> -- Will rerun unit tests prior to pushing change
>
> functional tests:
> - confirmed that proxy user configurations were set and that the oozie service test was successful
>
>
> Thanks,
>
> John Speidel
>
>
Re: Review Request 19687: proxy user settings need to be set when
provisioning via a blueprint
Posted by Nate Cole <nc...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/19687/#review38623
-----------------------------------------------------------
Ship it!
Ship It!
- Nate Cole
On March 26, 2014, 12:46 p.m., John Speidel wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19687/
> -----------------------------------------------------------
>
> (Updated March 26, 2014, 12:46 p.m.)
>
>
> Review request for Ambari, Nate Cole, Sid Wagle, and Tom Beerbower.
>
>
> Bugs: AMBARI-5206
> https://issues.apache.org/jira/browse/AMBARI-5206
>
>
> Repository: ambari
>
>
> Description
> -------
>
> In core-site, there are a bunch of proxyuser settings.
>
> These are in the form of :
> hadoop.proxyuser.<username>.hosts
> hadoop.proxyuser.<username>.groups
>
> These are dynamically generated property names because they contain the user name in the property name.
> These are currently not present in the stack definitions and are generated by the UI.
>
> These are currently not being set when provisioning via a blueprint.
>
> Until this is completed, users that deploy clusters that require proxy user properties will have to add them to the blueprint manually.
>
>
> Diffs
> -----
>
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterResourceProvider.java 8afee6e
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterResourceProviderTest.java ca881d4
>
> Diff: https://reviews.apache.org/r/19687/diff/
>
>
> Testing
> -------
>
> unit tests:
> - Updated existing unit test
> - Ran all unit tests with one failure that I have determined to be unrelated
> -- Will rerun unit tests prior to pushing change
>
> functional tests:
> - confirmed that proxy user configurations were set and that the oozie service test was successful
>
>
> Thanks,
>
> John Speidel
>
>