This is an automatically generated e-mail. To reply, visit:
(Updated May 19, 2016, 3:23 p.m.)
Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Jayush Luniya,
and Nate Cole.
Switched the <after> tag to be <add-after-group> and <add-after-group-entry>.
This distinguishes between the two possible meanings the <after> tag used to
have. UpgradePackTest has a test to check that a new group can be added after
an existing group and at the same time entries in the new group can be ordered
using the <add-after-group-entry> tag, if the same group is mentioned in
several service upgrade xml files (although the actual test just adds the same
group twice in a service upgrade xml file).
Currently the upgrade is defined as a series of xml files specific to the
current stack version and the target stack version. Each upgrade xml defines
the overall sequence of the upgrade and what needs to be done for each service.
It would both easier to maintain and easier to add new services, if the
services themselves could specify what should be done during their upgrade.
There are two ways to make these changes, the alternate approach would be to
only make the java changes and not split the upgrade xml files. This would
still allow new services to add themselves into the upgrade. The benefit of
this is that for the stack services you only have one upgrade xml file. The
problem with that is it is easier for a particular service to have
unintentional changes between upgrade xml files.
Manual testing so far. I have the code read the upgrade xml and all of its
service specific xml files, built the upgrade pack and then write the full
upgrade xml to disk and then compare the results to the original upgrade xml.
This review is mostly for the design doc which is attached to the JIRA. Not
sure how to create a review board with a design doc instead of a patch file.