Re: Review Request 28336: Provide stage resource information via REST API
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28336/
---
(Updated Nov. 22, 2014, 1:48 p.m.)
Review request for Ambari, Jonathan Hurley, John Speidel, Nate Cole, and Robert
Levas.
Bugs: AMBARI-8163
https://issues.apache.org/jira/browse/AMBARI-8163
Repository: ambari
Description
---
Currently, it is possible to query Ambari (via the REST API) for details about
_asynchronous_ requests and their related tasks. This useful when trying to
obtain progress information. However, some information necessary for the UI to
indicate meaningful progress is not available. This information is related to
the stages that are generated.
*NOTE:* Each _asynchronous_ request is broken down into 1 or more stages and
each stage contains 1 or more tasks.
If stage information was available via the REST API, it would be possible for
the caller (maybe a UI) to track high-level tasks (at the {{stage}} level)
rather than each lower-level unit of work (at the {{task}} level).
To allow for this, a new API resource (and associated handler) needs to be
created. The resource should be read-only (like {{requests}} and {{tasks}}),
and should provide information stored in the {{stage}} table from the Ambari
database.
The following properties should be returned for each {{stage}}:
* stage_id
* request_id
* cluster_id
* request_context
** _This should probably be renamed to something more appropriate, like
stage_context, stage_name, or etc..._
* start_time
* end_time
* progress_percent
* status
It is expected that the resources would be queried using:
{code}
GET /api/v1/clusters/{clusterid}/requests/{requestid}/stages
{code}
Also, some subset of the stage data should be provided when querying for
details about a specific {{request}}, like in:
{code}
GET /api/v1/clusters/{clusterid}/requests/{requestid}
{code}
See {{request}} and {{task}} resource for examples.
Diffs (updated)
-
ambari-server/src/main/java/org/apache/ambari/server/api/query/QueryImpl.java
a1c4882
ambari-server/src/main/java/org/apache/ambari/server/api/resources/BaseResourceDefinition.java
a5a7234
ambari-server/src/main/java/org/apache/ambari/server/api/resources/RequestResourceDefinition.java
291b01a
ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java
ba3f32f
ambari-server/src/main/java/org/apache/ambari/server/api/resources/SimpleResourceDefinition.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/api/services/RequestService.java
fc1b515
ambari-server/src/main/java/org/apache/ambari/server/api/services/StageService.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/api/services/TaskService.java
ade8d9c
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertHistoryResourceProvider.java
409aace
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertNoticeResourceProvider.java
956f710
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterControllerImpl.java
ec40c4f
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/DefaultProviderModule.java
d0ce1cf
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/QueryResponseImpl.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestImpl.java
9b98737
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StageResourceProvider.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/ClusterController.java
35ea680
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/ExtendedResourceProvider.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/QueryResponse.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Request.java
92c5db5
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Resource.java
b71b43c
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/PropertyHelper.java
3e2111e
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/StageDAO.java
900dbeb
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/StageEntity_.java
PRE-CREATION
ambari-server/src/test/java/org/apache/ambari/server/api/resources/SimpleResourceDefinitionTest.java
PRE-CREATION
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterControllerImplTest.java
cfb2efb
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/QueryResponseImplTest.java
PRE-CREATION
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StageResourceProviderTest.java
Re: Review Request 28336: Provide stage resource information via REST API
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28336/#review62730
---
Ship it!
Ship It!
- Nate Cole
On Nov. 22, 2014, 8:48 a.m., Tom Beerbower wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28336/
---
(Updated Nov. 22, 2014, 8:48 a.m.)
Review request for Ambari, Jonathan Hurley, John Speidel, Nate Cole, and
Robert Levas.
Bugs: AMBARI-8163
https://issues.apache.org/jira/browse/AMBARI-8163
Repository: ambari
Description
---
Currently, it is possible to query Ambari (via the REST API) for details
about _asynchronous_ requests and their related tasks. This useful when
trying to obtain progress information. However, some information necessary
for the UI to indicate meaningful progress is not available. This
information is related to the stages that are generated.
*NOTE:* Each _asynchronous_ request is broken down into 1 or more stages and
each stage contains 1 or more tasks.
If stage information was available via the REST API, it would be possible for
the caller (maybe a UI) to track high-level tasks (at the {{stage}} level)
rather than each lower-level unit of work (at the {{task}} level).
To allow for this, a new API resource (and associated handler) needs to be
created. The resource should be read-only (like {{requests}} and {{tasks}}),
and should provide information stored in the {{stage}} table from the Ambari
database.
The following properties should be returned for each {{stage}}:
* stage_id
* request_id
* cluster_id
* request_context
** _This should probably be renamed to something more appropriate, like
stage_context, stage_name, or etc..._
* start_time
* end_time
* progress_percent
* status
It is expected that the resources would be queried using:
{code}
GET /api/v1/clusters/{clusterid}/requests/{requestid}/stages
{code}
Also, some subset of the stage data should be provided when querying for
details about a specific {{request}}, like in:
{code}
GET /api/v1/clusters/{clusterid}/requests/{requestid}
{code}
See {{request}} and {{task}} resource for examples.
Diffs
-
ambari-server/src/main/java/org/apache/ambari/server/api/query/QueryImpl.java
a1c4882
ambari-server/src/main/java/org/apache/ambari/server/api/resources/BaseResourceDefinition.java
a5a7234
ambari-server/src/main/java/org/apache/ambari/server/api/resources/RequestResourceDefinition.java
291b01a
ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java
ba3f32f
ambari-server/src/main/java/org/apache/ambari/server/api/resources/SimpleResourceDefinition.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/api/services/RequestService.java
fc1b515
ambari-server/src/main/java/org/apache/ambari/server/api/services/StageService.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/api/services/TaskService.java
ade8d9c
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertHistoryResourceProvider.java
409aace
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertNoticeResourceProvider.java
956f710
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterControllerImpl.java
ec40c4f
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/DefaultProviderModule.java
d0ce1cf
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/QueryResponseImpl.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestImpl.java
9b98737
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StageResourceProvider.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/ClusterController.java
35ea680
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/ExtendedResourceProvider.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/QueryResponse.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Request.java
92c5db5
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Resource.java
b71b43c
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/PropertyHelper.java
3e2111e
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/StageDAO.java
900dbeb
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/StageEntity_.java
PRE-CREATION
Re: [VOTE] Ambari 1.7.0 release
+1 for 1.7.0 On Nov 22, 2014 1:54 AM, Jaimin Jetly jai...@hortonworks.com wrote: +1 for the 1.7.0 release candidate. Thanks Jaimin Jetly On Fri, Nov 21, 2014 at 10:11 PM, jun aoki ja...@apache.org wrote: +1 Great work! On Fri, Nov 21, 2014 at 6:07 PM, Ravi Mutyala rmuty...@gmail.com wrote: +1 (non binding) Built from source and created a 5 node cluster. On Friday, November 21, 2014, Alejandro Fernandez alejan...@apache.org wrote: +1 In case anyone wants the steps to verify, curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.md5 curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.sha curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.sig curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz curl -o 'alejandro_public.asc' http://people.apache.org/~alejandro/alejandro.asc gpg --import alejandro_public.asc gpg --verify ambari-1.7.0.tar.gz.sig ambari-1.7.0.tar.gz openssl md5 ambari-1.7.0.tar.gz ambari-1.7.0.tar.gz.md5.mine openssl sha1 ambari-1.7.0.tar.gz ambari-1.7.0.tar.gz.sha.mine diff -s ambari-1.7.0.tar.gz.md5 ambari-1.7.0.tar.gz.md5.mine diff -s ambari-1.7.0.tar.gz.sha ambari-1.7.0.tar.gz.sha.mine tar -xzvf ambari-1.7.0.tar.gz ambari-1.7.0 cd ambari-1.7.0 mvn clean apache-rat:check On Wed, Nov 19, 2014 at 2:36 PM, Alejandro Fernandez alejan...@apache.org javascript:; wrote: Hi all, The time has come to vote on releasing Ambari 1.7.0. In the past couple of weeks, the Ambari 1.7.0 release branch has received a lot of bug fixes and finally reached 0 open Jiras; you should all be very proud of yourselves for resolving a grand total of 1565 Jiras in the 1.7.0 release! Total Jiras fixed https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%201.7.0%20AND%20status%20%3D%20resolved%20AND%20resolution%20IN%20(Fixed%2C%20Done%2C%20Implemented) Over the last week, the number of Blocker, Critical, Major issues created for the Ambari 1.7.0 branch has steadily decreased from 23 to 0, so I'm confident that the branch is stable as a result of testing and finding fewer issues every day. Jiras created in past x days https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%201.7.0%20AND%20priority%20in%20(Blocker%2C%20Critical%2C%20Major)%20and%20created%20%3E%3D%20startOfDay(-1) (8 days ago = 23, 4 days ago = 7, 3 days ago = 6, 2 days ago = 5, 1 day ago = 3, today = 0) What is the proposed release candidate? branch-1.7.0 at commit * https://github.com/apache/ambari/commit/ff850fc06b23d8ab1b62ccd10265d15c7a27d465 https://github.com/apache/ambari/commit/ff850fc06b23d8ab1b62ccd10265d15c7a27d465 * Git source tag: release-1.7.0-rc0 https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-1.7.0-rc0 You can view all of the issues in the Ambari 1.7.0 release in https://issues.apache.org/jira/browse/AMBARI/fixforversion/12326546 I've uploaded the tarball and artifacts here for review, http://people.apache.org/~alejandro/ambari-1.7.0-rc0 gpg --verify ambari-1.7.0.tar.gz.sig ambari-1.7.0.tar.gz PGP release keys (signed using 392F57AC), http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x392F57AC *Voting process:* - How long does the voting take? The voting starts immediately and will last 3 days to provide ample opportunity for committers in different timezones. It will end on Saturday 22 at 8 pm UTC (equivalent to Saturday noon Pacific Time), - Who can vote? Committers and Ambari PMC - What are the voting options? In order to cast your vote, you must reply-all with one of the following, - [ ] +1 approve - [ ] +0 no opinion - [ ] -1 disapprove (and reason why) - What are the requirements to make the release? After 3 days, we will tally the results; at least three +1s from PMCs, and more +1s than -1s from all voters. Thanks, Alejandro Fernandez Ambari 1.7.0 Release Manager -- -jun -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying,
Re: Review Request 28336: Provide stage resource information via REST API
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28336/
---
(Updated Nov. 22, 2014, 1:58 p.m.)
Review request for Ambari, Jonathan Hurley, John Speidel, Nate Cole, and Robert
Levas.
Bugs: AMBARI-8163
https://issues.apache.org/jira/browse/AMBARI-8163
Repository: ambari
Description
---
Currently, it is possible to query Ambari (via the REST API) for details about
_asynchronous_ requests and their related tasks. This useful when trying to
obtain progress information. However, some information necessary for the UI to
indicate meaningful progress is not available. This information is related to
the stages that are generated.
*NOTE:* Each _asynchronous_ request is broken down into 1 or more stages and
each stage contains 1 or more tasks.
If stage information was available via the REST API, it would be possible for
the caller (maybe a UI) to track high-level tasks (at the {{stage}} level)
rather than each lower-level unit of work (at the {{task}} level).
To allow for this, a new API resource (and associated handler) needs to be
created. The resource should be read-only (like {{requests}} and {{tasks}}),
and should provide information stored in the {{stage}} table from the Ambari
database.
The following properties should be returned for each {{stage}}:
* stage_id
* request_id
* cluster_id
* request_context
** _This should probably be renamed to something more appropriate, like
stage_context, stage_name, or etc..._
* start_time
* end_time
* progress_percent
* status
It is expected that the resources would be queried using:
{code}
GET /api/v1/clusters/{clusterid}/requests/{requestid}/stages
{code}
Also, some subset of the stage data should be provided when querying for
details about a specific {{request}}, like in:
{code}
GET /api/v1/clusters/{clusterid}/requests/{requestid}
{code}
See {{request}} and {{task}} resource for examples.
Diffs (updated)
-
ambari-server/src/main/java/org/apache/ambari/server/api/query/QueryImpl.java
a1c4882
ambari-server/src/main/java/org/apache/ambari/server/api/resources/BaseResourceDefinition.java
a5a7234
ambari-server/src/main/java/org/apache/ambari/server/api/resources/RequestResourceDefinition.java
291b01a
ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java
ba3f32f
ambari-server/src/main/java/org/apache/ambari/server/api/resources/SimpleResourceDefinition.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/api/services/RequestService.java
fc1b515
ambari-server/src/main/java/org/apache/ambari/server/api/services/StageService.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/api/services/TaskService.java
ade8d9c
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertHistoryResourceProvider.java
409aace
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertNoticeResourceProvider.java
956f710
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterControllerImpl.java
ec40c4f
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/DefaultProviderModule.java
d0ce1cf
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/QueryResponseImpl.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestImpl.java
9b98737
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StageResourceProvider.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/ClusterController.java
35ea680
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/ExtendedResourceProvider.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/QueryResponse.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Request.java
92c5db5
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Resource.java
b71b43c
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/PropertyHelper.java
3e2111e
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/StageDAO.java
900dbeb
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/StageEntity_.java
PRE-CREATION
ambari-server/src/test/java/org/apache/ambari/server/api/resources/SimpleResourceDefinitionTest.java
PRE-CREATION
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterControllerImplTest.java
cfb2efb
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/QueryResponseImplTest.java
PRE-CREATION
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StageResourceProviderTest.java
Re: Review Request 28336: Provide stage resource information via REST API
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28336/
---
(Updated Nov. 22, 2014, 1:59 p.m.)
Review request for Ambari, Jonathan Hurley, John Speidel, Nate Cole, and Robert
Levas.
Bugs: AMBARI-8163
https://issues.apache.org/jira/browse/AMBARI-8163
Repository: ambari
Description
---
Currently, it is possible to query Ambari (via the REST API) for details about
_asynchronous_ requests and their related tasks. This useful when trying to
obtain progress information. However, some information necessary for the UI to
indicate meaningful progress is not available. This information is related to
the stages that are generated.
*NOTE:* Each _asynchronous_ request is broken down into 1 or more stages and
each stage contains 1 or more tasks.
If stage information was available via the REST API, it would be possible for
the caller (maybe a UI) to track high-level tasks (at the {{stage}} level)
rather than each lower-level unit of work (at the {{task}} level).
To allow for this, a new API resource (and associated handler) needs to be
created. The resource should be read-only (like {{requests}} and {{tasks}}),
and should provide information stored in the {{stage}} table from the Ambari
database.
The following properties should be returned for each {{stage}}:
* stage_id
* request_id
* cluster_id
* request_context
** _This should probably be renamed to something more appropriate, like
stage_context, stage_name, or etc..._
* start_time
* end_time
* progress_percent
* status
It is expected that the resources would be queried using:
{code}
GET /api/v1/clusters/{clusterid}/requests/{requestid}/stages
{code}
Also, some subset of the stage data should be provided when querying for
details about a specific {{request}}, like in:
{code}
GET /api/v1/clusters/{clusterid}/requests/{requestid}
{code}
See {{request}} and {{task}} resource for examples.
Diffs
-
ambari-server/src/main/java/org/apache/ambari/server/api/query/QueryImpl.java
a1c4882
ambari-server/src/main/java/org/apache/ambari/server/api/resources/BaseResourceDefinition.java
a5a7234
ambari-server/src/main/java/org/apache/ambari/server/api/resources/RequestResourceDefinition.java
291b01a
ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java
ba3f32f
ambari-server/src/main/java/org/apache/ambari/server/api/resources/SimpleResourceDefinition.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/api/services/RequestService.java
fc1b515
ambari-server/src/main/java/org/apache/ambari/server/api/services/StageService.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/api/services/TaskService.java
ade8d9c
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertHistoryResourceProvider.java
409aace
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertNoticeResourceProvider.java
956f710
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterControllerImpl.java
ec40c4f
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/DefaultProviderModule.java
d0ce1cf
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/QueryResponseImpl.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestImpl.java
9b98737
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StageResourceProvider.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/ClusterController.java
35ea680
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/ExtendedResourceProvider.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/QueryResponse.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Request.java
92c5db5
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Resource.java
b71b43c
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/PropertyHelper.java
3e2111e
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/StageDAO.java
900dbeb
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/StageEntity_.java
PRE-CREATION
ambari-server/src/test/java/org/apache/ambari/server/api/resources/SimpleResourceDefinitionTest.java
PRE-CREATION
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterControllerImplTest.java
cfb2efb
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/QueryResponseImplTest.java
PRE-CREATION
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StageResourceProviderTest.java
PRE-CREATION
Re: Review Request 28336: Provide stage resource information via REST API
On Nov. 21, 2014, 10:40 p.m., Nate Cole wrote:
Thanks for the review.
On Nov. 21, 2014, 10:40 p.m., Nate Cole wrote:
ambari-server/src/main/java/org/apache/ambari/server/api/resources/StageResourceDefinition.java,
lines 41-43
https://reviews.apache.org/r/28336/diff/1/?file=772235#file772235line41
Should be stage?
Doh! Thanks for catching that. I don't even know if the singular name is
actually used.
On Nov. 21, 2014, 10:40 p.m., Nate Cole wrote:
ambari-server/src/main/java/org/apache/ambari/server/api/resources/BaseResourceDefinition.java,
line 70
https://reviews.apache.org/r/28336/diff/1/?file=772232#file772232line70
I didn't even think this was a valid construct. It's weird! :) I
don't have any issues with it, but you'd have to look at the ctor to know
what to correctly provide.
Yeah, I think looking at the ctor it makes sense but looking at the call you
just see a single list of types. I got rid of StageResourceDefinition and
turned it into a generic class (SimpleResourceDefinition) that also takes the
singular and plural names into the ctor. Now the call looks cleaner, I think,
because the type and subtypes are broken up in the argument list.
- Tom
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28336/#review62668
---
On Nov. 22, 2014, 1:59 p.m., Tom Beerbower wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28336/
---
(Updated Nov. 22, 2014, 1:59 p.m.)
Review request for Ambari, Jonathan Hurley, John Speidel, Nate Cole, and
Robert Levas.
Bugs: AMBARI-8163
https://issues.apache.org/jira/browse/AMBARI-8163
Repository: ambari
Description
---
Currently, it is possible to query Ambari (via the REST API) for details
about _asynchronous_ requests and their related tasks. This useful when
trying to obtain progress information. However, some information necessary
for the UI to indicate meaningful progress is not available. This
information is related to the stages that are generated.
*NOTE:* Each _asynchronous_ request is broken down into 1 or more stages and
each stage contains 1 or more tasks.
If stage information was available via the REST API, it would be possible for
the caller (maybe a UI) to track high-level tasks (at the {{stage}} level)
rather than each lower-level unit of work (at the {{task}} level).
To allow for this, a new API resource (and associated handler) needs to be
created. The resource should be read-only (like {{requests}} and {{tasks}}),
and should provide information stored in the {{stage}} table from the Ambari
database.
The following properties should be returned for each {{stage}}:
* stage_id
* request_id
* cluster_id
* request_context
** _This should probably be renamed to something more appropriate, like
stage_context, stage_name, or etc..._
* start_time
* end_time
* progress_percent
* status
It is expected that the resources would be queried using:
{code}
GET /api/v1/clusters/{clusterid}/requests/{requestid}/stages
{code}
Also, some subset of the stage data should be provided when querying for
details about a specific {{request}}, like in:
{code}
GET /api/v1/clusters/{clusterid}/requests/{requestid}
{code}
See {{request}} and {{task}} resource for examples.
Diffs
-
ambari-server/src/main/java/org/apache/ambari/server/api/query/QueryImpl.java
a1c4882
ambari-server/src/main/java/org/apache/ambari/server/api/resources/BaseResourceDefinition.java
a5a7234
ambari-server/src/main/java/org/apache/ambari/server/api/resources/RequestResourceDefinition.java
291b01a
ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java
ba3f32f
ambari-server/src/main/java/org/apache/ambari/server/api/resources/SimpleResourceDefinition.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/api/services/RequestService.java
fc1b515
ambari-server/src/main/java/org/apache/ambari/server/api/services/StageService.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/api/services/TaskService.java
ade8d9c
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertHistoryResourceProvider.java
409aace
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertNoticeResourceProvider.java
956f710
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterControllerImpl.java
ec40c4f
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/DefaultProviderModule.java
Re: Review Request 28336: Provide stage resource information via REST API
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28336/
---
(Updated Nov. 22, 2014, 2:18 p.m.)
Review request for Ambari, Jonathan Hurley, John Speidel, Nate Cole, and Robert
Levas.
Bugs: AMBARI-8163
https://issues.apache.org/jira/browse/AMBARI-8163
Repository: ambari
Description
---
Currently, it is possible to query Ambari (via the REST API) for details about
_asynchronous_ requests and their related tasks. This useful when trying to
obtain progress information. However, some information necessary for the UI to
indicate meaningful progress is not available. This information is related to
the stages that are generated.
*NOTE:* Each _asynchronous_ request is broken down into 1 or more stages and
each stage contains 1 or more tasks.
If stage information was available via the REST API, it would be possible for
the caller (maybe a UI) to track high-level tasks (at the {{stage}} level)
rather than each lower-level unit of work (at the {{task}} level).
To allow for this, a new API resource (and associated handler) needs to be
created. The resource should be read-only (like {{requests}} and {{tasks}}),
and should provide information stored in the {{stage}} table from the Ambari
database.
The following properties should be returned for each {{stage}}:
* stage_id
* request_id
* cluster_id
* request_context
** _This should probably be renamed to something more appropriate, like
stage_context, stage_name, or etc..._
* start_time
* end_time
* progress_percent
* status
It is expected that the resources would be queried using:
{code}
GET /api/v1/clusters/{clusterid}/requests/{requestid}/stages
{code}
Also, some subset of the stage data should be provided when querying for
details about a specific {{request}}, like in:
{code}
GET /api/v1/clusters/{clusterid}/requests/{requestid}
{code}
See {{request}} and {{task}} resource for examples.
Diffs (updated)
-
ambari-server/src/main/java/org/apache/ambari/server/api/query/QueryImpl.java
a1c4882
ambari-server/src/main/java/org/apache/ambari/server/api/resources/BaseResourceDefinition.java
a5a7234
ambari-server/src/main/java/org/apache/ambari/server/api/resources/RequestResourceDefinition.java
291b01a
ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java
ba3f32f
ambari-server/src/main/java/org/apache/ambari/server/api/resources/SimpleResourceDefinition.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/api/services/RequestService.java
fc1b515
ambari-server/src/main/java/org/apache/ambari/server/api/services/StageService.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/api/services/TaskService.java
ade8d9c
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertHistoryResourceProvider.java
409aace
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertNoticeResourceProvider.java
956f710
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterControllerImpl.java
ec40c4f
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/DefaultProviderModule.java
d0ce1cf
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/QueryResponseImpl.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestImpl.java
9b98737
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StageResourceProvider.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/ClusterController.java
35ea680
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/ExtendedResourceProvider.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/QueryResponse.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Request.java
92c5db5
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Resource.java
b71b43c
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/PropertyHelper.java
3e2111e
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/StageDAO.java
900dbeb
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/StageEntity_.java
PRE-CREATION
ambari-server/src/test/java/org/apache/ambari/server/api/resources/SimpleResourceDefinitionTest.java
PRE-CREATION
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterControllerImplTest.java
cfb2efb
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/QueryResponseImplTest.java
PRE-CREATION
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StageResourceProviderTest.java
Re: Review Request 28336: Provide stage resource information via REST API
On Nov. 21, 2014, 7:21 p.m., Robert Levas wrote:
Thanks for the review.
On Nov. 21, 2014, 7:21 p.m., Robert Levas wrote:
ambari-server/src/main/java/org/apache/ambari/server/api/resources/BaseResourceDefinition.java,
line 70
https://reviews.apache.org/r/28336/diff/1/?file=772232#file772232line70
This seems to be confusing since the caller sees X number of
`Resources.Type` arguments that do not indicate any hierarchy, yet the
implementation takes the first as the main type and the rest as the sub
types.
This type of syntax seems to make better sense when all of the
arguements are used the same way.
I would rather see something like `public
BaseResourceDefinition(Resource.Type resourceType,
CollectionResource.Type subTypes)` making the invocation of this
constructor look like:
`super(Resource.Type.Request, Arrays.asList(Resource.Type.State,
Resource.Type.Task))`
Which looks clearer (to me) than:
`super(Resource.Type.Request, Resource.Type.State, Resource.Type.Task)`
If there are no other issues and no on else cares about this, then
don't let this hold up progress.
Same comment to Nate ...
Yeah, I think looking at the ctor it makes sense but looking at the call you
just see a single list of types. I got rid of StageResourceDefinition and
turned it into a generic class (SimpleResourceDefinition) that also takes the
singular and plural names into the ctor. Now the call looks cleaner, I think,
because the type and subtypes are broken up in the argument list.
On Nov. 21, 2014, 7:21 p.m., Robert Levas wrote:
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterControllerImpl.java,
line 908
https://reviews.apache.org/r/28336/diff/1/?file=772241#file772241line908
Is there any particular reason this is an _inner_ class. Technically
is it not really an inner class. That said, I am typically a fan of the
`private static (inner) class`; however this is a `protected static (inner)
class` in an _implementation_ class (not a class one would expect to be
used as a base class).
Might it be better to move this out to its own class? Maybe it will be
useful elsewhere?
Yeah, I don't see this ever being used outside ClusterControllerImpl. I
changed it to private.
On Nov. 21, 2014, 7:21 p.m., Robert Levas wrote:
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StageResourceProvider.java,
line 294
https://reviews.apache.org/r/28336/diff/1/?file=772245#file772245line294
The comment here is confusing since we are counting non-`COMPLETED`
statuses twice. We just don't want to doubly count the `COMPLETED` statuses
twice.
It took a little digging to figure out that this is not a bug due to
how the counts are used elsewhere in this class.
Good point. I updated the comment.
- Tom
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28336/#review62584
---
On Nov. 22, 2014, 2:18 p.m., Tom Beerbower wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28336/
---
(Updated Nov. 22, 2014, 2:18 p.m.)
Review request for Ambari, Jonathan Hurley, John Speidel, Nate Cole, and
Robert Levas.
Bugs: AMBARI-8163
https://issues.apache.org/jira/browse/AMBARI-8163
Repository: ambari
Description
---
Currently, it is possible to query Ambari (via the REST API) for details
about _asynchronous_ requests and their related tasks. This useful when
trying to obtain progress information. However, some information necessary
for the UI to indicate meaningful progress is not available. This
information is related to the stages that are generated.
*NOTE:* Each _asynchronous_ request is broken down into 1 or more stages and
each stage contains 1 or more tasks.
If stage information was available via the REST API, it would be possible for
the caller (maybe a UI) to track high-level tasks (at the {{stage}} level)
rather than each lower-level unit of work (at the {{task}} level).
To allow for this, a new API resource (and associated handler) needs to be
created. The resource should be read-only (like {{requests}} and {{tasks}}),
and should provide information stored in the {{stage}} table from the Ambari
database.
The following properties should be returned for each {{stage}}:
* stage_id
* request_id
* cluster_id
* request_context
** _This should probably be renamed to something more appropriate, like
stage_context, stage_name, or etc..._
* start_time
* end_time
* progress_percent
*
[jira] [Created] (AMBARI-8422) Upgrade Execute: create database mappings for Upgrades to Requests
Nate Cole created AMBARI-8422: - Summary: Upgrade Execute: create database mappings for Upgrades to Requests Key: AMBARI-8422 URL: https://issues.apache.org/jira/browse/AMBARI-8422 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.0.0 Tie together upgrades to requests, and upgrade_items to stages. Provide an upgrade status based on stage status -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8422) Upgrade Execute: create database mappings for Upgrades to Requests
[ https://issues.apache.org/jira/browse/AMBARI-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-8422: -- Attachment: AMBARI-8422.patch Upgrade Execute: create database mappings for Upgrades to Requests -- Key: AMBARI-8422 URL: https://issues.apache.org/jira/browse/AMBARI-8422 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.0.0 Attachments: AMBARI-8422.patch Tie together upgrades to requests, and upgrade_items to stages. Provide an upgrade status based on stage status -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8422) Upgrade Execute: create database mappings for Upgrades to Requests
[ https://issues.apache.org/jira/browse/AMBARI-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-8422: -- Attachment: (was: AMBARI-8422.patch) Upgrade Execute: create database mappings for Upgrades to Requests -- Key: AMBARI-8422 URL: https://issues.apache.org/jira/browse/AMBARI-8422 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.0.0 Tie together upgrades to requests, and upgrade_items to stages. Provide an upgrade status based on stage status -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8422) Upgrade Execute: create database mappings for Upgrades to Requests
[ https://issues.apache.org/jira/browse/AMBARI-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-8422: -- Attachment: AMBARI-8422.patch Upgrade Execute: create database mappings for Upgrades to Requests -- Key: AMBARI-8422 URL: https://issues.apache.org/jira/browse/AMBARI-8422 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.0.0 Attachments: AMBARI-8422.patch Tie together upgrades to requests, and upgrade_items to stages. Provide an upgrade status based on stage status -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Review Request 28370: Upgrade Execute: create database mappings for Upgrades to Requests
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/28370/ --- Review request for Ambari, Alejandro Fernandez, Dmitro Lisnichenko, and Yurii Shylov. Bugs: AMBARI-8422 https://issues.apache.org/jira/browse/AMBARI-8422 Repository: ambari Description --- Added database columns to link to Request and added a state calculation for items. Also updated the property Upgrade/version to Upgrade/repository_version from latest discussions. Diffs - ambari-server/src/main/java/org/apache/ambari/server/actionmanager/HostRoleStatus.java 447aead ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeItemResourceProvider.java d7e8271 ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java eb2ad76 ambari-server/src/main/java/org/apache/ambari/server/orm/entities/UpgradeEntity.java 8695f84 ambari-server/src/main/java/org/apache/ambari/server/orm/entities/UpgradeItemEntity.java 0453e72 ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeState.java 3d69541 ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog200.java b5556ed ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql edcaa50 ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql 8ab0619 ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql a918f22 ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql 2e7aa07 ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql e3e3414 ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java 87a0a48 ambari-server/src/test/java/org/apache/ambari/server/orm/dao/UpgradeDAOTest.java c61a473 ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog200Test.java be9c9bf Diff: https://reviews.apache.org/r/28370/diff/ Testing --- [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 18:10.658s [INFO] Finished at: Sat Nov 22 11:25:40 EST 2014 [INFO] Final Memory: 29M/614M [INFO] Thanks, Nate Cole
[jira] [Commented] (AMBARI-8422) Upgrade Execute: create database mappings for Upgrades to Requests
[
https://issues.apache.org/jira/browse/AMBARI-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222055#comment-14222055
]
Hadoop QA commented on AMBARI-8422:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12683058/AMBARI-8422.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/721//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/721//console
This message is automatically generated.
Upgrade Execute: create database mappings for Upgrades to Requests
--
Key: AMBARI-8422
URL: https://issues.apache.org/jira/browse/AMBARI-8422
Project: Ambari
Issue Type: Task
Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Fix For: 2.0.0
Attachments: AMBARI-8422.patch
Tie together upgrades to requests, and upgrade_items to stages. Provide an
upgrade status based on stage status
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Review Request 28301: SSH Bootstrap is broken
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/28301/#review62735 --- Ship it! Ship It! - Sid Wagle On Nov. 20, 2014, 9:53 p.m., Andrew Onischuk wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/28301/ --- (Updated Nov. 20, 2014, 9:53 p.m.) Review request for Ambari, Mahadev Konar and Sid Wagle. Bugs: AMBARI-8405 https://issues.apache.org/jira/browse/AMBARI-8405 Repository: ambari Description --- In Install Wizard, I specified 2 hosts and used the SSH bootstrap method by supplying a valid private key. The hosts failed to bootstrap with errors. See attached. Diffs - ambari-server/src/main/python/setupAgent.py e320245 Diff: https://reviews.apache.org/r/28301/diff/ Testing --- mvn clean test Thanks, Andrew Onischuk
Re: Review Request 28336: Provide stage resource information via REST API
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28336/#review62736
---
Ship it!
Ship It!
- Nate Cole
On Nov. 22, 2014, 9:18 a.m., Tom Beerbower wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28336/
---
(Updated Nov. 22, 2014, 9:18 a.m.)
Review request for Ambari, Jonathan Hurley, John Speidel, Nate Cole, and
Robert Levas.
Bugs: AMBARI-8163
https://issues.apache.org/jira/browse/AMBARI-8163
Repository: ambari
Description
---
Currently, it is possible to query Ambari (via the REST API) for details
about _asynchronous_ requests and their related tasks. This useful when
trying to obtain progress information. However, some information necessary
for the UI to indicate meaningful progress is not available. This
information is related to the stages that are generated.
*NOTE:* Each _asynchronous_ request is broken down into 1 or more stages and
each stage contains 1 or more tasks.
If stage information was available via the REST API, it would be possible for
the caller (maybe a UI) to track high-level tasks (at the {{stage}} level)
rather than each lower-level unit of work (at the {{task}} level).
To allow for this, a new API resource (and associated handler) needs to be
created. The resource should be read-only (like {{requests}} and {{tasks}}),
and should provide information stored in the {{stage}} table from the Ambari
database.
The following properties should be returned for each {{stage}}:
* stage_id
* request_id
* cluster_id
* request_context
** _This should probably be renamed to something more appropriate, like
stage_context, stage_name, or etc..._
* start_time
* end_time
* progress_percent
* status
It is expected that the resources would be queried using:
{code}
GET /api/v1/clusters/{clusterid}/requests/{requestid}/stages
{code}
Also, some subset of the stage data should be provided when querying for
details about a specific {{request}}, like in:
{code}
GET /api/v1/clusters/{clusterid}/requests/{requestid}
{code}
See {{request}} and {{task}} resource for examples.
Diffs
-
ambari-server/src/main/java/org/apache/ambari/server/api/query/QueryImpl.java
a1c4882
ambari-server/src/main/java/org/apache/ambari/server/api/resources/BaseResourceDefinition.java
a5a7234
ambari-server/src/main/java/org/apache/ambari/server/api/resources/RequestResourceDefinition.java
291b01a
ambari-server/src/main/java/org/apache/ambari/server/api/resources/ResourceInstanceFactoryImpl.java
ba3f32f
ambari-server/src/main/java/org/apache/ambari/server/api/resources/SimpleResourceDefinition.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/api/services/RequestService.java
fc1b515
ambari-server/src/main/java/org/apache/ambari/server/api/services/StageService.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/api/services/TaskService.java
ade8d9c
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertHistoryResourceProvider.java
409aace
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertNoticeResourceProvider.java
956f710
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterControllerImpl.java
ec40c4f
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/DefaultProviderModule.java
d0ce1cf
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/QueryResponseImpl.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestImpl.java
9b98737
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StageResourceProvider.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/ClusterController.java
35ea680
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/ExtendedResourceProvider.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/QueryResponse.java
PRE-CREATION
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Request.java
92c5db5
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/Resource.java
b71b43c
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/PropertyHelper.java
3e2111e
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/StageDAO.java
900dbeb
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/StageEntity_.java
PRE-CREATION
[jira] [Created] (AMBARI-8423) Automated Upgrade - Execution Engine
Nate Cole created AMBARI-8423: - Summary: Automated Upgrade - Execution Engine Key: AMBARI-8423 URL: https://issues.apache.org/jira/browse/AMBARI-8423 Project: Ambari Issue Type: Story Components: ambari-agent, ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.0.0 The backend should have an engine that is responsible for scheduling and executing an automated/rolling upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8144) Upgrade Execute: Create API endpoint for upgrades and upgrade items
[ https://issues.apache.org/jira/browse/AMBARI-8144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-8144: -- Issue Type: Sub-task (was: Task) Parent: AMBARI-8423 Upgrade Execute: Create API endpoint for upgrades and upgrade items Key: AMBARI-8144 URL: https://issues.apache.org/jira/browse/AMBARI-8144 Project: Ambari Issue Type: Sub-task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.0.0 Attachments: AMBARI-8144.patch Create skeleton and API endpoints for upgrade processing. These are only stubs and will be filled out as development progresses -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8298) Distribute Repositories/Install Components - custom action script
[ https://issues.apache.org/jira/browse/AMBARI-8298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-8298: -- Issue Type: Technical task (was: Improvement) Parent: AMBARI-8423 Distribute Repositories/Install Components - custom action script - Key: AMBARI-8298 URL: https://issues.apache.org/jira/browse/AMBARI-8298 Project: Ambari Issue Type: Technical task Components: ambari-server Affects Versions: 2.0.0 Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Fix For: 2.0.0 Distribute Repositories/Install Components - custom action script -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8206) Upgrade Execute: Load and parse upgrade packs from stack directory
[ https://issues.apache.org/jira/browse/AMBARI-8206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-8206: -- Issue Type: Sub-task (was: Task) Parent: AMBARI-8423 Upgrade Execute: Load and parse upgrade packs from stack directory -- Key: AMBARI-8206 URL: https://issues.apache.org/jira/browse/AMBARI-8206 Project: Ambari Issue Type: Sub-task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.0.0 Attachments: AMBARI-8206.patch Create the classes required to parse an upgrade pack -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8346) Upgrade Execute: define db schema to store upgrade artifacts
[ https://issues.apache.org/jira/browse/AMBARI-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-8346: -- Issue Type: Sub-task (was: Task) Parent: AMBARI-8423 Upgrade Execute: define db schema to store upgrade artifacts Key: AMBARI-8346 URL: https://issues.apache.org/jira/browse/AMBARI-8346 Project: Ambari Issue Type: Sub-task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.0.0 Attachments: AMBARI-8346.patch, AMBARI-8346.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8392) Upgrade Execute: Create stages and tasks
[ https://issues.apache.org/jira/browse/AMBARI-8392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-8392: -- Issue Type: Sub-task (was: Task) Parent: AMBARI-8423 Upgrade Execute: Create stages and tasks Key: AMBARI-8392 URL: https://issues.apache.org/jira/browse/AMBARI-8392 Project: Ambari Issue Type: Sub-task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.0.0 Attachments: AMBARI-8392.patch From the creation of and upgrade and upgrade items, add the workflow to make request/stages/tasks out of them (even if they're currently incomplete) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8406) Upgrade Execute: implement proper RESTART commands
[ https://issues.apache.org/jira/browse/AMBARI-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-8406: -- Issue Type: Technical task (was: Task) Parent: AMBARI-8423 Upgrade Execute: implement proper RESTART commands -- Key: AMBARI-8406 URL: https://issues.apache.org/jira/browse/AMBARI-8406 Project: Ambari Issue Type: Technical task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.0.0 Attachments: AMBARI-8406.patch Replace stub restart with an actual restart command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8422) Upgrade Execute: create database mappings for Upgrades to Requests
[ https://issues.apache.org/jira/browse/AMBARI-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-8422: -- Issue Type: Technical task (was: Task) Parent: AMBARI-8423 Upgrade Execute: create database mappings for Upgrades to Requests -- Key: AMBARI-8422 URL: https://issues.apache.org/jira/browse/AMBARI-8422 Project: Ambari Issue Type: Technical task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.0.0 Attachments: AMBARI-8422.patch Tie together upgrades to requests, and upgrade_items to stages. Provide an upgrade status based on stage status -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8298) Distribute Repositories/Install Components - custom action script
[ https://issues.apache.org/jira/browse/AMBARI-8298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-8298: -- Issue Type: Task (was: Technical task) Parent: (was: AMBARI-8423) Distribute Repositories/Install Components - custom action script - Key: AMBARI-8298 URL: https://issues.apache.org/jira/browse/AMBARI-8298 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.0.0 Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Fix For: 2.0.0 Distribute Repositories/Install Components - custom action script -- This message was sent by Atlassian JIRA (v6.3.4#6332)
RE: [VOTE] Ambari 1.7.0 release
+1 -Original Message- From: Jonathan Hurley [jhur...@hortonworks.com] Received: Saturday, 22 Nov 2014, 6:54AM To: dev [dev@ambari.apache.org] Subject: Re: [VOTE] Ambari 1.7.0 release +1 for 1.7.0 On Nov 22, 2014 1:54 AM, Jaimin Jetly jai...@hortonworks.com wrote: +1 for the 1.7.0 release candidate. Thanks Jaimin Jetly On Fri, Nov 21, 2014 at 10:11 PM, jun aoki ja...@apache.org wrote: +1 Great work! On Fri, Nov 21, 2014 at 6:07 PM, Ravi Mutyala rmuty...@gmail.com wrote: +1 (non binding) Built from source and created a 5 node cluster. On Friday, November 21, 2014, Alejandro Fernandez alejan...@apache.org wrote: +1 In case anyone wants the steps to verify, curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.md5 curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.sha curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.sig curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz curl -o 'alejandro_public.asc' http://people.apache.org/~alejandro/alejandro.asc gpg --import alejandro_public.asc gpg --verify ambari-1.7.0.tar.gz.sig ambari-1.7.0.tar.gz openssl md5 ambari-1.7.0.tar.gz ambari-1.7.0.tar.gz.md5.mine openssl sha1 ambari-1.7.0.tar.gz ambari-1.7.0.tar.gz.sha.mine diff -s ambari-1.7.0.tar.gz.md5 ambari-1.7.0.tar.gz.md5.mine diff -s ambari-1.7.0.tar.gz.sha ambari-1.7.0.tar.gz.sha.mine tar -xzvf ambari-1.7.0.tar.gz ambari-1.7.0 cd ambari-1.7.0 mvn clean apache-rat:check On Wed, Nov 19, 2014 at 2:36 PM, Alejandro Fernandez alejan...@apache.org javascript:; wrote: Hi all, The time has come to vote on releasing Ambari 1.7.0. In the past couple of weeks, the Ambari 1.7.0 release branch has received a lot of bug fixes and finally reached 0 open Jiras; you should all be very proud of yourselves for resolving a grand total of 1565 Jiras in the 1.7.0 release! Total Jiras fixed https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%201.7.0%20AND%20status%20%3D%20resolved%20AND%20resolution%20IN%20(Fixed%2C%20Done%2C%20Implemented) Over the last week, the number of Blocker, Critical, Major issues created for the Ambari 1.7.0 branch has steadily decreased from 23 to 0, so I'm confident that the branch is stable as a result of testing and finding fewer issues every day. Jiras created in past x days https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%201.7.0%20AND%20priority%20in%20(Blocker%2C%20Critical%2C%20Major)%20and%20created%20%3E%3D%20startOfDay(-1) (8 days ago = 23, 4 days ago = 7, 3 days ago = 6, 2 days ago = 5, 1 day ago = 3, today = 0) What is the proposed release candidate? branch-1.7.0 at commit * https://github.com/apache/ambari/commit/ff850fc06b23d8ab1b62ccd10265d15c7a27d465 https://github.com/apache/ambari/commit/ff850fc06b23d8ab1b62ccd10265d15c7a27d465 * Git source tag: release-1.7.0-rc0 https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-1.7.0-rc0 You can view all of the issues in the Ambari 1.7.0 release in https://issues.apache.org/jira/browse/AMBARI/fixforversion/12326546 I've uploaded the tarball and artifacts here for review, http://people.apache.org/~alejandro/ambari-1.7.0-rc0 gpg --verify ambari-1.7.0.tar.gz.sig ambari-1.7.0.tar.gz PGP release keys (signed using 392F57AC), http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x392F57AC *Voting process:* - How long does the voting take? The voting starts immediately and will last 3 days to provide ample opportunity for committers in different timezones. It will end on Saturday 22 at 8 pm UTC (equivalent to Saturday noon Pacific Time), - Who can vote? Committers and Ambari PMC - What are the voting options? In order to cast your vote, you must reply-all with one of the following, - [ ] +1 approve - [ ] +0 no opinion - [ ] -1 disapprove (and reason why) - What are the requirements to make the release? After 3 days, we will tally the results; at least three +1s from PMCs, and more +1s than -1s from all voters. Thanks, Alejandro Fernandez Ambari 1.7.0 Release Manager -- -jun -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is
RE: [VOTE] Ambari 1.7.0 release
+1 -Original Message- From: Jonathan Hurley [jhur...@hortonworks.com] Received: Saturday, 22 Nov 2014, 6:54AM To: dev [dev@ambari.apache.org] Subject: Re: [VOTE] Ambari 1.7.0 release +1 for 1.7.0 On Nov 22, 2014 1:54 AM, Jaimin Jetly jai...@hortonworks.com wrote: +1 for the 1.7.0 release candidate. Thanks Jaimin Jetly On Fri, Nov 21, 2014 at 10:11 PM, jun aoki ja...@apache.org wrote: +1 Great work! On Fri, Nov 21, 2014 at 6:07 PM, Ravi Mutyala rmuty...@gmail.com wrote: +1 (non binding) Built from source and created a 5 node cluster. On Friday, November 21, 2014, Alejandro Fernandez alejan...@apache.org wrote: +1 In case anyone wants the steps to verify, curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.md5 curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.sha curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.sig curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz curl -o 'alejandro_public.asc' http://people.apache.org/~alejandro/alejandro.asc gpg --import alejandro_public.asc gpg --verify ambari-1.7.0.tar.gz.sig ambari-1.7.0.tar.gz openssl md5 ambari-1.7.0.tar.gz ambari-1.7.0.tar.gz.md5.mine openssl sha1 ambari-1.7.0.tar.gz ambari-1.7.0.tar.gz.sha.mine diff -s ambari-1.7.0.tar.gz.md5 ambari-1.7.0.tar.gz.md5.mine diff -s ambari-1.7.0.tar.gz.sha ambari-1.7.0.tar.gz.sha.mine tar -xzvf ambari-1.7.0.tar.gz ambari-1.7.0 cd ambari-1.7.0 mvn clean apache-rat:check On Wed, Nov 19, 2014 at 2:36 PM, Alejandro Fernandez alejan...@apache.org javascript:; wrote: Hi all, The time has come to vote on releasing Ambari 1.7.0. In the past couple of weeks, the Ambari 1.7.0 release branch has received a lot of bug fixes and finally reached 0 open Jiras; you should all be very proud of yourselves for resolving a grand total of 1565 Jiras in the 1.7.0 release! Total Jiras fixed https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%201.7.0%20AND%20status%20%3D%20resolved%20AND%20resolution%20IN%20(Fixed%2C%20Done%2C%20Implemented) Over the last week, the number of Blocker, Critical, Major issues created for the Ambari 1.7.0 branch has steadily decreased from 23 to 0, so I'm confident that the branch is stable as a result of testing and finding fewer issues every day. Jiras created in past x days https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%201.7.0%20AND%20priority%20in%20(Blocker%2C%20Critical%2C%20Major)%20and%20created%20%3E%3D%20startOfDay(-1) (8 days ago = 23, 4 days ago = 7, 3 days ago = 6, 2 days ago = 5, 1 day ago = 3, today = 0) What is the proposed release candidate? branch-1.7.0 at commit * https://github.com/apache/ambari/commit/ff850fc06b23d8ab1b62ccd10265d15c7a27d465 https://github.com/apache/ambari/commit/ff850fc06b23d8ab1b62ccd10265d15c7a27d465 * Git source tag: release-1.7.0-rc0 https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-1.7.0-rc0 You can view all of the issues in the Ambari 1.7.0 release in https://issues.apache.org/jira/browse/AMBARI/fixforversion/12326546 I've uploaded the tarball and artifacts here for review, http://people.apache.org/~alejandro/ambari-1.7.0-rc0 gpg --verify ambari-1.7.0.tar.gz.sig ambari-1.7.0.tar.gz PGP release keys (signed using 392F57AC), http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x392F57AC *Voting process:* - How long does the voting take? The voting starts immediately and will last 3 days to provide ample opportunity for committers in different timezones. It will end on Saturday 22 at 8 pm UTC (equivalent to Saturday noon Pacific Time), - Who can vote? Committers and Ambari PMC - What are the voting options? In order to cast your vote, you must reply-all with one of the following, - [ ] +1 approve - [ ] +0 no opinion - [ ] -1 disapprove (and reason why) - What are the requirements to make the release? After 3 days, we will tally the results; at least three +1s from PMCs, and more +1s than -1s from all voters. Thanks, Alejandro Fernandez Ambari 1.7.0 Release Manager -- -jun -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is
RE: [VOTE] Ambari 1.7.0 release
+1 -Original Message- From: Jonathan Hurley [jhur...@hortonworks.com] Received: Saturday, 22 Nov 2014, 6:54AM To: dev [dev@ambari.apache.org] Subject: Re: [VOTE] Ambari 1.7.0 release +1 for 1.7.0 On Nov 22, 2014 1:54 AM, Jaimin Jetly jai...@hortonworks.com wrote: +1 for the 1.7.0 release candidate. Thanks Jaimin Jetly On Fri, Nov 21, 2014 at 10:11 PM, jun aoki ja...@apache.org wrote: +1 Great work! On Fri, Nov 21, 2014 at 6:07 PM, Ravi Mutyala rmuty...@gmail.com wrote: +1 (non binding) Built from source and created a 5 node cluster. On Friday, November 21, 2014, Alejandro Fernandez alejan...@apache.org wrote: +1 In case anyone wants the steps to verify, curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.md5 curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.sha curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.sig curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz curl -o 'alejandro_public.asc' http://people.apache.org/~alejandro/alejandro.asc gpg --import alejandro_public.asc gpg --verify ambari-1.7.0.tar.gz.sig ambari-1.7.0.tar.gz openssl md5 ambari-1.7.0.tar.gz ambari-1.7.0.tar.gz.md5.mine openssl sha1 ambari-1.7.0.tar.gz ambari-1.7.0.tar.gz.sha.mine diff -s ambari-1.7.0.tar.gz.md5 ambari-1.7.0.tar.gz.md5.mine diff -s ambari-1.7.0.tar.gz.sha ambari-1.7.0.tar.gz.sha.mine tar -xzvf ambari-1.7.0.tar.gz ambari-1.7.0 cd ambari-1.7.0 mvn clean apache-rat:check On Wed, Nov 19, 2014 at 2:36 PM, Alejandro Fernandez alejan...@apache.org javascript:; wrote: Hi all, The time has come to vote on releasing Ambari 1.7.0. In the past couple of weeks, the Ambari 1.7.0 release branch has received a lot of bug fixes and finally reached 0 open Jiras; you should all be very proud of yourselves for resolving a grand total of 1565 Jiras in the 1.7.0 release! Total Jiras fixed https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%201.7.0%20AND%20status%20%3D%20resolved%20AND%20resolution%20IN%20(Fixed%2C%20Done%2C%20Implemented) Over the last week, the number of Blocker, Critical, Major issues created for the Ambari 1.7.0 branch has steadily decreased from 23 to 0, so I'm confident that the branch is stable as a result of testing and finding fewer issues every day. Jiras created in past x days https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%201.7.0%20AND%20priority%20in%20(Blocker%2C%20Critical%2C%20Major)%20and%20created%20%3E%3D%20startOfDay(-1) (8 days ago = 23, 4 days ago = 7, 3 days ago = 6, 2 days ago = 5, 1 day ago = 3, today = 0) What is the proposed release candidate? branch-1.7.0 at commit * https://github.com/apache/ambari/commit/ff850fc06b23d8ab1b62ccd10265d15c7a27d465 https://github.com/apache/ambari/commit/ff850fc06b23d8ab1b62ccd10265d15c7a27d465 * Git source tag: release-1.7.0-rc0 https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-1.7.0-rc0 You can view all of the issues in the Ambari 1.7.0 release in https://issues.apache.org/jira/browse/AMBARI/fixforversion/12326546 I've uploaded the tarball and artifacts here for review, http://people.apache.org/~alejandro/ambari-1.7.0-rc0 gpg --verify ambari-1.7.0.tar.gz.sig ambari-1.7.0.tar.gz PGP release keys (signed using 392F57AC), http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x392F57AC *Voting process:* - How long does the voting take? The voting starts immediately and will last 3 days to provide ample opportunity for committers in different timezones. It will end on Saturday 22 at 8 pm UTC (equivalent to Saturday noon Pacific Time), - Who can vote? Committers and Ambari PMC - What are the voting options? In order to cast your vote, you must reply-all with one of the following, - [ ] +1 approve - [ ] +0 no opinion - [ ] -1 disapprove (and reason why) - What are the requirements to make the release? After 3 days, we will tally the results; at least three +1s from PMCs, and more +1s than -1s from all voters. Thanks, Alejandro Fernandez Ambari 1.7.0 Release Manager -- -jun -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is
RE: [VOTE] Ambari 1.7.0 release
+1 -Original Message- From: Jonathan Hurley [jhur...@hortonworks.com] Received: Saturday, 22 Nov 2014, 6:54AM To: dev [dev@ambari.apache.org] Subject: Re: [VOTE] Ambari 1.7.0 release +1 for 1.7.0 On Nov 22, 2014 1:54 AM, Jaimin Jetly jai...@hortonworks.com wrote: +1 for the 1.7.0 release candidate. Thanks Jaimin Jetly On Fri, Nov 21, 2014 at 10:11 PM, jun aoki ja...@apache.org wrote: +1 Great work! On Fri, Nov 21, 2014 at 6:07 PM, Ravi Mutyala rmuty...@gmail.com wrote: +1 (non binding) Built from source and created a 5 node cluster. On Friday, November 21, 2014, Alejandro Fernandez alejan...@apache.org wrote: +1 In case anyone wants the steps to verify, curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.md5 curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.sha curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.sig curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz curl -o 'alejandro_public.asc' http://people.apache.org/~alejandro/alejandro.asc gpg --import alejandro_public.asc gpg --verify ambari-1.7.0.tar.gz.sig ambari-1.7.0.tar.gz openssl md5 ambari-1.7.0.tar.gz ambari-1.7.0.tar.gz.md5.mine openssl sha1 ambari-1.7.0.tar.gz ambari-1.7.0.tar.gz.sha.mine diff -s ambari-1.7.0.tar.gz.md5 ambari-1.7.0.tar.gz.md5.mine diff -s ambari-1.7.0.tar.gz.sha ambari-1.7.0.tar.gz.sha.mine tar -xzvf ambari-1.7.0.tar.gz ambari-1.7.0 cd ambari-1.7.0 mvn clean apache-rat:check On Wed, Nov 19, 2014 at 2:36 PM, Alejandro Fernandez alejan...@apache.org javascript:; wrote: Hi all, The time has come to vote on releasing Ambari 1.7.0. In the past couple of weeks, the Ambari 1.7.0 release branch has received a lot of bug fixes and finally reached 0 open Jiras; you should all be very proud of yourselves for resolving a grand total of 1565 Jiras in the 1.7.0 release! Total Jiras fixed https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%201.7.0%20AND%20status%20%3D%20resolved%20AND%20resolution%20IN%20(Fixed%2C%20Done%2C%20Implemented) Over the last week, the number of Blocker, Critical, Major issues created for the Ambari 1.7.0 branch has steadily decreased from 23 to 0, so I'm confident that the branch is stable as a result of testing and finding fewer issues every day. Jiras created in past x days https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%201.7.0%20AND%20priority%20in%20(Blocker%2C%20Critical%2C%20Major)%20and%20created%20%3E%3D%20startOfDay(-1) (8 days ago = 23, 4 days ago = 7, 3 days ago = 6, 2 days ago = 5, 1 day ago = 3, today = 0) What is the proposed release candidate? branch-1.7.0 at commit * https://github.com/apache/ambari/commit/ff850fc06b23d8ab1b62ccd10265d15c7a27d465 https://github.com/apache/ambari/commit/ff850fc06b23d8ab1b62ccd10265d15c7a27d465 * Git source tag: release-1.7.0-rc0 https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-1.7.0-rc0 You can view all of the issues in the Ambari 1.7.0 release in https://issues.apache.org/jira/browse/AMBARI/fixforversion/12326546 I've uploaded the tarball and artifacts here for review, http://people.apache.org/~alejandro/ambari-1.7.0-rc0 gpg --verify ambari-1.7.0.tar.gz.sig ambari-1.7.0.tar.gz PGP release keys (signed using 392F57AC), http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x392F57AC *Voting process:* - How long does the voting take? The voting starts immediately and will last 3 days to provide ample opportunity for committers in different timezones. It will end on Saturday 22 at 8 pm UTC (equivalent to Saturday noon Pacific Time), - Who can vote? Committers and Ambari PMC - What are the voting options? In order to cast your vote, you must reply-all with one of the following, - [ ] +1 approve - [ ] +0 no opinion - [ ] -1 disapprove (and reason why) - What are the requirements to make the release? After 3 days, we will tally the results; at least three +1s from PMCs, and more +1s than -1s from all voters. Thanks, Alejandro Fernandez Ambari 1.7.0 Release Manager -- -jun -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is
RE: [VOTE] Ambari 1.7.0 release
+1 -Original Message- From: Jonathan Hurley [jhur...@hortonworks.com] Received: Saturday, 22 Nov 2014, 6:54AM To: dev [dev@ambari.apache.org] Subject: Re: [VOTE] Ambari 1.7.0 release +1 for 1.7.0 On Nov 22, 2014 1:54 AM, Jaimin Jetly jai...@hortonworks.com wrote: +1 for the 1.7.0 release candidate. Thanks Jaimin Jetly On Fri, Nov 21, 2014 at 10:11 PM, jun aoki ja...@apache.org wrote: +1 Great work! On Fri, Nov 21, 2014 at 6:07 PM, Ravi Mutyala rmuty...@gmail.com wrote: +1 (non binding) Built from source and created a 5 node cluster. On Friday, November 21, 2014, Alejandro Fernandez alejan...@apache.org wrote: +1 In case anyone wants the steps to verify, curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.md5 curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.sha curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.sig curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz curl -o 'alejandro_public.asc' http://people.apache.org/~alejandro/alejandro.asc gpg --import alejandro_public.asc gpg --verify ambari-1.7.0.tar.gz.sig ambari-1.7.0.tar.gz openssl md5 ambari-1.7.0.tar.gz ambari-1.7.0.tar.gz.md5.mine openssl sha1 ambari-1.7.0.tar.gz ambari-1.7.0.tar.gz.sha.mine diff -s ambari-1.7.0.tar.gz.md5 ambari-1.7.0.tar.gz.md5.mine diff -s ambari-1.7.0.tar.gz.sha ambari-1.7.0.tar.gz.sha.mine tar -xzvf ambari-1.7.0.tar.gz ambari-1.7.0 cd ambari-1.7.0 mvn clean apache-rat:check On Wed, Nov 19, 2014 at 2:36 PM, Alejandro Fernandez alejan...@apache.org javascript:; wrote: Hi all, The time has come to vote on releasing Ambari 1.7.0. In the past couple of weeks, the Ambari 1.7.0 release branch has received a lot of bug fixes and finally reached 0 open Jiras; you should all be very proud of yourselves for resolving a grand total of 1565 Jiras in the 1.7.0 release! Total Jiras fixed https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%201.7.0%20AND%20status%20%3D%20resolved%20AND%20resolution%20IN%20(Fixed%2C%20Done%2C%20Implemented) Over the last week, the number of Blocker, Critical, Major issues created for the Ambari 1.7.0 branch has steadily decreased from 23 to 0, so I'm confident that the branch is stable as a result of testing and finding fewer issues every day. Jiras created in past x days https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%201.7.0%20AND%20priority%20in%20(Blocker%2C%20Critical%2C%20Major)%20and%20created%20%3E%3D%20startOfDay(-1) (8 days ago = 23, 4 days ago = 7, 3 days ago = 6, 2 days ago = 5, 1 day ago = 3, today = 0) What is the proposed release candidate? branch-1.7.0 at commit * https://github.com/apache/ambari/commit/ff850fc06b23d8ab1b62ccd10265d15c7a27d465 https://github.com/apache/ambari/commit/ff850fc06b23d8ab1b62ccd10265d15c7a27d465 * Git source tag: release-1.7.0-rc0 https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-1.7.0-rc0 You can view all of the issues in the Ambari 1.7.0 release in https://issues.apache.org/jira/browse/AMBARI/fixforversion/12326546 I've uploaded the tarball and artifacts here for review, http://people.apache.org/~alejandro/ambari-1.7.0-rc0 gpg --verify ambari-1.7.0.tar.gz.sig ambari-1.7.0.tar.gz PGP release keys (signed using 392F57AC), http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x392F57AC *Voting process:* - How long does the voting take? The voting starts immediately and will last 3 days to provide ample opportunity for committers in different timezones. It will end on Saturday 22 at 8 pm UTC (equivalent to Saturday noon Pacific Time), - Who can vote? Committers and Ambari PMC - What are the voting options? In order to cast your vote, you must reply-all with one of the following, - [ ] +1 approve - [ ] +0 no opinion - [ ] -1 disapprove (and reason why) - What are the requirements to make the release? After 3 days, we will tally the results; at least three +1s from PMCs, and more +1s than -1s from all voters. Thanks, Alejandro Fernandez Ambari 1.7.0 Release Manager -- -jun -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is
RE: [VOTE] Ambari 1.7.0 release
+1 -Original Message- From: Jonathan Hurley [jhur...@hortonworks.com] Received: Saturday, 22 Nov 2014, 6:54AM To: dev [dev@ambari.apache.org] Subject: Re: [VOTE] Ambari 1.7.0 release +1 for 1.7.0 On Nov 22, 2014 1:54 AM, Jaimin Jetly jai...@hortonworks.com wrote: +1 for the 1.7.0 release candidate. Thanks Jaimin Jetly On Fri, Nov 21, 2014 at 10:11 PM, jun aoki ja...@apache.org wrote: +1 Great work! On Fri, Nov 21, 2014 at 6:07 PM, Ravi Mutyala rmuty...@gmail.com wrote: +1 (non binding) Built from source and created a 5 node cluster. On Friday, November 21, 2014, Alejandro Fernandez alejan...@apache.org wrote: +1 In case anyone wants the steps to verify, curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.md5 curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.sha curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz.sig curl -O http://people.apache.org/~alejandro/ambari-1.7.0-rc0/ambari-1.7.0.tar.gz curl -o 'alejandro_public.asc' http://people.apache.org/~alejandro/alejandro.asc gpg --import alejandro_public.asc gpg --verify ambari-1.7.0.tar.gz.sig ambari-1.7.0.tar.gz openssl md5 ambari-1.7.0.tar.gz ambari-1.7.0.tar.gz.md5.mine openssl sha1 ambari-1.7.0.tar.gz ambari-1.7.0.tar.gz.sha.mine diff -s ambari-1.7.0.tar.gz.md5 ambari-1.7.0.tar.gz.md5.mine diff -s ambari-1.7.0.tar.gz.sha ambari-1.7.0.tar.gz.sha.mine tar -xzvf ambari-1.7.0.tar.gz ambari-1.7.0 cd ambari-1.7.0 mvn clean apache-rat:check On Wed, Nov 19, 2014 at 2:36 PM, Alejandro Fernandez alejan...@apache.org javascript:; wrote: Hi all, The time has come to vote on releasing Ambari 1.7.0. In the past couple of weeks, the Ambari 1.7.0 release branch has received a lot of bug fixes and finally reached 0 open Jiras; you should all be very proud of yourselves for resolving a grand total of 1565 Jiras in the 1.7.0 release! Total Jiras fixed https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%201.7.0%20AND%20status%20%3D%20resolved%20AND%20resolution%20IN%20(Fixed%2C%20Done%2C%20Implemented) Over the last week, the number of Blocker, Critical, Major issues created for the Ambari 1.7.0 branch has steadily decreased from 23 to 0, so I'm confident that the branch is stable as a result of testing and finding fewer issues every day. Jiras created in past x days https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%201.7.0%20AND%20priority%20in%20(Blocker%2C%20Critical%2C%20Major)%20and%20created%20%3E%3D%20startOfDay(-1) (8 days ago = 23, 4 days ago = 7, 3 days ago = 6, 2 days ago = 5, 1 day ago = 3, today = 0) What is the proposed release candidate? branch-1.7.0 at commit * https://github.com/apache/ambari/commit/ff850fc06b23d8ab1b62ccd10265d15c7a27d465 https://github.com/apache/ambari/commit/ff850fc06b23d8ab1b62ccd10265d15c7a27d465 * Git source tag: release-1.7.0-rc0 https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-1.7.0-rc0 You can view all of the issues in the Ambari 1.7.0 release in https://issues.apache.org/jira/browse/AMBARI/fixforversion/12326546 I've uploaded the tarball and artifacts here for review, http://people.apache.org/~alejandro/ambari-1.7.0-rc0 gpg --verify ambari-1.7.0.tar.gz.sig ambari-1.7.0.tar.gz PGP release keys (signed using 392F57AC), http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x392F57AC *Voting process:* - How long does the voting take? The voting starts immediately and will last 3 days to provide ample opportunity for committers in different timezones. It will end on Saturday 22 at 8 pm UTC (equivalent to Saturday noon Pacific Time), - Who can vote? Committers and Ambari PMC - What are the voting options? In order to cast your vote, you must reply-all with one of the following, - [ ] +1 approve - [ ] +0 no opinion - [ ] -1 disapprove (and reason why) - What are the requirements to make the release? After 3 days, we will tally the results; at least three +1s from PMCs, and more +1s than -1s from all voters. Thanks, Alejandro Fernandez Ambari 1.7.0 Release Manager -- -jun -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is
