ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez" <afernan...@hortonworks.com>
Subject Re: Review Request 38238: Bootstrap HDP 2.1 repo, cluster_version, and host_versions as CURRENT after upgrading Ambari
Date Fri, 11 Sep 2015 18:16:05 GMT


> On Sept. 11, 2015, 7:56 a.m., Dmitro Lisnichenko wrote:
> > ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog212.java,
line 63
> > <https://reviews.apache.org/r/38238/diff/3/?file=1067688#file1067688line63>
> >
> >     BTW, why we are targeting not upgrade UpgradeCatalog220? As I understand, changes
anyway are not going to go into branch-2.1 and to current release?

Once we merge to trunk we'll need to call the same function from UpgradeCatalog220.


- Alejandro


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38238/#review98578
-----------------------------------------------------------


On Sept. 10, 2015, 9:09 p.m., Alejandro Fernandez wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38238/
> -----------------------------------------------------------
> 
> (Updated Sept. 10, 2015, 9:09 p.m.)
> 
> 
> Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan Hurley, Nate
Cole, and Sid Wagle.
> 
> 
> Bugs: AMBARI-13001
>     https://issues.apache.org/jira/browse/AMBARI-13001
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> In Ambari 2.1, if the stack is HDP 2.1, the user does not even see a Stacks and Versions
page.
> The Ambari upgrade will have to bootstrap the versions by
> * Inserting repo_vesion for HDP 2.1
> * Inserting cluster_vesion as CURRENT
> * Inserting host_versions as CURRENT
> 
> This will then allow clicking on the "Perform Upgrade" button to call the Upgrades endpoint
correctly, which needs to know the source version in order to calculate the upgrade pack and
configs to use.
> 
> 
> Diffs
> -----
> 
>   ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
2c9714e 
>   ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ClusterVersionDAO.java
d3326b1 
>   ambari-server/src/main/java/org/apache/ambari/server/orm/dao/CrudDAO.java 4382f59 
>   ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostVersionDAO.java a2ff211

>   ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog212.java
6919e64 
>   ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
PRE-CREATION 
>   ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog212Test.java
6268f91 
> 
> Diff: https://reviews.apache.org/r/38238/diff/
> 
> 
> Testing
> -------
> 
> Installed Ambari 2.1.1 with HDP 2.1.0.0
> Upgraded Ambari to 2.1.2 using my build, which updated the schema, and also populated
the repo_version, cluster_version, and host_version.
> In my install, only the repo_version had an id in the ambari_sequences table, so I also
tested that a value was inserted if not already present for all 3 entities.
> 
> I also added a basic upgrade pack for HDP 2.1 -> 2.3 for basic testing, which can
be started using a curl call.
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>


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