Hi Jayush, Thanks for the insights, we will discuss on using common-services.
Thanks, Mahesh On Tue, Dec 16, 2014 at 6:15 PM, Jayush Luniya <[email protected]> wrote: > > Hi Mahesh, > Instead of adding a dependency on HDP stack, I would recommend that you > inherit the stack services from common-services. We are in process of > refactoring out HDP 2.0.6 stack to use common services. > > References: > > Common Services > https://issues.apache.org/jira/browse/AMBARI-7201 > > Refactor of HDP 2.0.6 HDFS and ZOOKEEPER services > https://issues.apache.org/jira/browse/AMBARI-8695 > > Thanks > Jayush > > On Tue, Dec 16, 2014 at 2:51 PM, Mahesh Kumar Somashekar < > [email protected]> wrote: > > > > Hello, > > > > This is Mahesh from Pivotal. We are working on cross-stack definition > > inheritance story which require design inputs from Ambari team, as it > needs > > some changes in HDP stack definitions. > > > > Here is the case that we are trying to solve: > > Currently, Ambari supports inheriting stack definitions within a > particular > > stack, for example, HDP-2.2 stack definition inherits HDP-2.1. But > > inheritance between stacks is not yet supported, like PHD inheriting HDP > > stack definition. We are working on adding this support. > > > > Design problem that we are facing: > > Supporting cross-stack definition inheritance means both HDP and PHD > > definitions should be deployed while deploying PHD cluster. As both > > definitions are deployed, we need to make HDP definitions as in-active, > > otherwise, HDP option will show up for PHD based deployment. In order to > do > > so, we need to change some logic in HDP definitions as well and that's > > where we need input. > > > > Below are the options that we are proposing, please feel free to give > > comments, > > > > Option-1: > > Introducing two properties, hdp.active & hdp.inactive, in main pom.xml > and > > all HDP stack definitions will be updated to use these properties to > > enable/disable stacks. While building for PHD, both will be set to false. > > > > ./pom.xml: > > <stack.distribution>HDP</stack.distribution> > > + <hdp.active>true</hdp.active> > > + <hdp.inactive>false</hdp.inactive> > > </properties> > > > > ./ambari-server/src/main/resources/stacks/HDP/2.2/metainfo.xml > > <versions> > > - <active>true</active> > > + <active>${hdp.active}</active> > > </versions> > > > > ./ambari-server/src/main/resources/stacks/HDP/2.0.6/metainfo.xml > > <versions> > > - <active>false</active> > > + <active>${hdp.inactive}</active> > > </versions> > > > > > > Option-2: > > Adding property per stack definition to enable/disable stacks. While > > building for PHD, all those properties will be set to false. > > > > ./pom.xml: > > <stack.distribution>HDP</stack.distribution> > > + <hdp.22.active>true</hdp.22.active> > > + <hdp.21.active>true</hdp.21.active> > > + <hdp.206.active>false</hdp.206.active> > > </properties> > > > > ./ambari-server/src/main/resources/stacks/HDP/2.2/metainfo.xml > > <versions> > > - <active>true</active> > > + <active>${hdp.22.active}</active> > > </versions> > > > > ./ambari-server/src/main/resources/stacks/HDP/2.1/metainfo.xml > > <versions> > > - <active>true</active> > > + <active>${hdp.21.active}</active> > > </versions> > > > > ./ambari-server/src/main/resources/stacks/HDP/2.0.6/metainfo.xml > > <versions> > > - <active>false</active> > > + <active>${hdp.206.active}</active> > > </versions> > > > > > > Thanks in advance for the inputs. > > > > > > Thanks, > > Mahesh > > > > -- > 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, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. >
