You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by Viraj Jasani <vj...@apache.org> on 2022/06/29 04:52:01 UTC
[DISCUSS] Move Ambari select packages to Bigtop
Hi Ambari/Bigtop dev,
As per the new roadmap of Apache Ambari, we would like to propose moving
certain scripts (previously known as hdp-select and conf-select) to Bigtop
so that their rpm installation could be managed independently.
These scripts are a basic necessity in the Ambari framework for the
installation of various Bigdata packages. The only major changes they would
receive is when we onboard new services and components to Ambari, else they
usually do not receive updates. In the past, we used to get hdp-select rpm
downloaded and installed from HDP repositories.
We have still not officially finalized the new replacement name for
hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
the purpose of bdp-select and conf-select remains the same.
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by xiaojun tong <to...@gmail.com>.
From the perspective of brand publicity and protection, the name bigtop is
more appropriate. Directly link the ambari and bigtop projects.
Kengo Seki <se...@apache.org> 于2022年7月8日周五 22:36写道：
> Thank you for your explanation, Brahma.
> CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
> trademark of Redoop, so they can name the script crh-select without
> problem.
> But regarding BDP for example, I can easily find products that have
> the same name [2][3][4] as you already mentioned, so I'd like to
> recommend bigtop-select for avoiding unnecessary trouble.
> Or, a single and more general word just like conf-select may be less
> troublesome than bdp. How about "stack-select", for example?
>
> [1]: https://docs.redoop.com/
> [2]: https://datumstudio.jp/en/bigdataplatform/
> [3]:
> https://help.talend.com/r/en-US/8.0/studio-getting-started-guide-big-data-platform/introduction
> [4]: https://www.harmony-alliance.eu/bigdata-platform/big-data-platform
>
> Kengo Seki <se...@apache.org>
>
> On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com>
> wrote:
> >
> > >Do you mean that you're going to name the module (same as
> "component"
> > >in the Bigtop terminology, I think) bigtop-distro-select,
> > >and still the script in question bdp-select? If so, is there any
> > >reason that the script must be that name?
> > >(No offence, I just want to understand your thoughts and its
> > >background, and avoid the conflict or user's confusion with existing
> > >trademarks or products)
> >
> > Thanks @Kengo Seki for consolidating all the concerns. Name should
> represent the stack which includes all the components hence planning to
> have like bdp,bds...and this only one file like below[1] which has done
> redoop.
> >
> >
> >
> https://github.com/redoop/bigtop/tree/e5f9fe81773180159d291f18ec366ac8bfa4d6d2/bigtop-packages/src/common/ambari-mpacks/selector
> >
> >
> > On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
> >
> > The following concern Masatake mentioned before is an important
> point,
> > so I talked to Brahma for clarifying his intention on the ASF Slack
> > yesterday.
> >
> > > Multiple versions of the same package (deb/rpm) can not be
> installed at the same time.
> > > IIRC, HDP uses convention in which the product version is part of
> package name
> > > for addressing this.
> >
> > > I don't like to bring the awkward package name convention to Bigtop
> > > at least by default.
> >
> > He's planning to adopt the same mitigation as HDP for now, but he
> > doesn't intend to change the default package naming convention of
> > Bigtop,
> > but just add a new functionality to include an extra part into the
> > package name for avoiding conflict, which is disabled by default.
> >
> > And Brahma, let me confirm about the following reply:
> >
> > > Sure, we can have module name like bigtop-distro-select.
> >
> > Do you mean that you're going to name the module (same as "component"
> > in the Bigtop terminology, I think) bigtop-distro-select,
> > and still the script in question bdp-select? If so, is there any
> > reason that the script must be that name?
> > (No offence, I just want to understand your thoughts and its
> > background, and avoid the conflict or user's confusion with existing
> > trademarks or products)
> >
> > Kengo Seki <se...@apache.org>
> >
> > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
> > <bb...@visa.com.invalid> wrote:
> > >
> > > > The name of stack based no Bigtop should be Bigtop.
> > > > If you can not accept the name like bigtop-*, the work
> should done outside of Bigtop.
> > > > I will cast -1 if someone submit a patch to add a module with
> the name spoiling branding.
> > >
> > > Sure, we can have module name like bigtop-distro-select.
> > > Initially we'll do this separate branch.
> > >
> > >
> > >
> > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.co.jp> wrote:
> > >
> > > > I believe it's for project name. isn't it.?
> > >
> > > projects and products.
> > >
> > > > IMO, We need to create folders and refer stacknames so
> ambari-select,bigtop-select wn't looks good.
> > >
> > > The name of stack based no Bigtop should be Bigtop.
> > > If you can not accept the name like bigtop-*, the work should
> done outside of Bigtop.
> > > I will cast -1 if someone submit a patch to add a module with
> the name spoiling branding.
> > >
> > >
> > > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> > > >
> > > > I believe it's for project name. isn't it.?
> > > >
> > > >
> > > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.co.jp> wrote:
> > > >
> > > > > But As we are not releasing as enterprise should be
> fine I think. IMO, We need to create folders and refer stacknames so
> ambari-select,bigtop-select wn't looks good.
> > > >
> > > > Not fine.
> > > > We have a trademark policy.
> > > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=uLAUZWy9EpJRNUYeuhSL951CbEdtLYFxrOFK%2BWW5Elg%3D&reserved=0
> > > >
> > > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> > > > >> Should we avoid unrecognized brand which may be
> trademark of someone?
> > > > >> ambari-select or bigtop-select should be enough.
> > > > >
> > > > > Not sure, where to confirm whether there is already
> trademark. When I googled found so many.
> > > > > But As we are not releasing as enterprise should be
> fine I think. IMO, We need to create folders and refer stacknames so
> ambari-select,bigtop-select wn't looks good.
> > > > > May be you can refer the initial proposal [2] where I
> mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > > >
> > > > > Finally thanks a bunch for long healthy discussions
> on this. Mostly we all same page now.
> > > > >
> > > > > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8NSFFz1Ko1oZFar%2Bz0%2FML9LgJHUNf0bLw7VVbtGP1ck%3D&reserved=0
> > > > >
> > > > > 2.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=I%2BbQoYUU5upYS1VQT1rux5ZZhh%2Fx1yeyD%2BnLW8HJwkw%3D&reserved=0
> > > > >
> > > > >
> > > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.co.jp> wrote:
> > > > >
> > > > > > We have still not officially finalized the new
> replacement name for
> > > > > > hdp-select, it would likely be bdp-select
> (bdp: BigData Platform). However,
> > > > > > the purpose of bdp-select and conf-select
> remains the same.
> > > > >
> > > > > Should we avoid unrecognized brand which may be
> trademark of someone?
> > > > > ambari-select or bigtop-select should be enough.
> > > > >
> > > > > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > > > > Hi Ambari/Bigtop dev,
> > > > > >
> > > > > > As per the new roadmap of Apache Ambari, we
> would like to propose moving
> > > > > > certain scripts (previously known as
> hdp-select and conf-select) to Bigtop
> > > > > > so that their rpm installation could be
> managed independently.
> > > > > > These scripts are a basic necessity in the
> Ambari framework for the
> > > > > > installation of various Bigdata packages. The
> only major changes they would
> > > > > > receive is when we onboard new services and
> components to Ambari, else they
> > > > > > usually do not receive updates. In the past,
> we used to get hdp-select rpm
> > > > > > downloaded and installed from HDP repositories.
> > > > > >
> > > > > > We have still not officially finalized the new
> replacement name for
> > > > > > hdp-select, it would likely be bdp-select
> (bdp: BigData Platform). However,
> > > > > > the purpose of bdp-select and conf-select
> remains the same.
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > > For additional commands, e-mail: dev-help@ambari.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
> >
>
--
tongxiaojun
website: http://www.redoop.com <http://www.redhadoop.com>
mail: tongxiaojun@gmail.com
tel: 18613807209
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
Is it Sept 9th .? Or Aug,29th..?
On 23/08/22, 8:50 PM, "Viraj Jasani" <vj...@apache.org> wrote:
Does 25th Aug 9 pm PST (26th Aug 9:30 am IST) work?
On Tue, Aug 23, 2022 at 2:48 AM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
> @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get the
> final conclusion on this..?
>
> Please let me know your availability, Can have one call to discuss on
> this..
>
>
> On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
> wrote:
>
> > -1 on development in branch.
> > It is not worth for maintaining the branch if the modules is so
> small
> > and barely updated as explained here.
> > It should not conflict to existing code.
> > I feel I must check the code before check-in based on this
> thread.
>
>
> Sure, Viraj or me can show the code to you.
>
> Can we've call on this Friday/Thrusday if that works..?
>
>
> On 11/07/22, 11:54 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com>
> wrote:
>
> > Sure, we can havemodule name like bigtop-distro-select.
> > Initially we'll do this separate branch.
>
> -1 on development in branch.
> It is not worth for maintaining the branch if the modules is so
> small
> and barely updated as explained here.
> It should not conflict to existing code.
> I feel I must check the code before check-in based on this thread.
>
> Masatake Iwasaki
>
> On 2022/07/11 8:23, Kengo Seki wrote:
> >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls.
> >
> > Oh, I interpreted your words "conclude" and "finalize" as you
> were
> > going to make a final decision. Brainstorming is welcome, of
> course.
> > (But I'm not so sure if all people concerned could join, due to
> time
> > difference and their schedule, etc.)
> >
> >> Can you suggest, how the changes will be also.. like folder,
> where you suggest to keep this...?
> >
> > Sure, here's my proposal:
> >
> > * Stack name: "BIGTOP"
> >
> > - The same name as the existing one [1]
> > - Because it deploys the packages generated by Bigtop
> > - The existing stack should be replaced with it, because that
> is
> > based on Bigtop 0.8 and too old to use now
> > - No concern about infringing others' trademark
> >
> > * Component/folder name: "bigtop-select"
> >
> > - Consistent naming convention with the existing tools such as
> > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > - If it sounds too simple and a bit unclear, a more
> descriptive name
> > might be an option, for example "bigtop-ambari-stack-selector"
> >
> > * Script name: "bigtop-select"
> >
> > - Consistent with the stack name
> > - No concern about infringing others' trademark
> >
> > [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154442656%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nxyJH5gFWfbVIvmL%2FI68CqnedwXr6dAOSaO8yVxrEi0%3D&reserved=0
> > [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154442656%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3HjYr5bEk92zB8w%2BNxiILTfwk6%2FD01yVScVqCZRdOSM%3D&reserved=0
> >
> > Kengo Seki <se...@apache.org>
> >
> > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> > <bb...@visa.com.invalid> wrote:
> >>
> >>> Technical decisions shouldn't be done on other places than
> public mailing lists,
> >>> as described in the "Open Communications" section of [1] and
> [2].
> >> > So we should conclude the discussion in this mailing list.
> >> > (And with my poor English, I'm not so confident to catch up
> with your
> >> > fluent talk ;)
> >>
> >> I believe , I knew the apache way which you mentioned. We are
> not going conclude anything which comes to bigtop other than this mailing
> list.
> >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls. Hence asking let's
> have call so that we can brainstorm. Even after call, everything will be
> published what we discussed.
> >>
> >> I think, whiteboarding will help to catch up with you.
> >>
> >> You all the think "bigtop-select" will be best option right..?
> Can you suggest, how the changes will be also.. like folder, where you
> suggest to keep this...?
> >>
> >> And if the name represents the stack which we are going to
> deploy should fine I feel.. (if it's not BDP, may be
> OBDP:OpensourceBigDataPlatform.)
> >>
> >> @Viraj Jasani and others any thoughts..?
> >>
> >>
> >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org> wrote:
> >>
> >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> >>
> >> Technical decisions shouldn't be done on other places than
> public mailing lists,
> >> as described in the "Open Communications" section of [1]
> and [2].
> >> So we should conclude the discussion in this mailing list.
> >> (And with my poor English, I'm not so confident to catch
> up with your
> >> fluent talk ;)
> >>
> >> > FYI. Even looks bigtop used some where also..
> >>
> >> Bigtop is ASF's trademark as you can see in the "Apache
> Bigtop®
> >> software" section of [3].
> >> So it doesn't have the risk of trademark infringement.
> >>
> >> [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154442656%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BKaxiwRrPD99gV1ryMQY%2F1S0Gp3iV5xsT7Pw5l1bCHA%3D&reserved=0
> >> [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154442656%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=z%2BqHDEs9Z08Q7lxVpizkcUCZ2ts6r0keL4jveRl9gaw%3D&reserved=0
> >> [3]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154442656%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=SAg10ICLr2RAoi4WEQEKzu6Y7PS0Nri1d6%2FsjOFvpbo%3D&reserved=0
> >>
> >> Kengo Seki <se...@apache.org>
> >>
> >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> >> <bb...@visa.com.invalid> wrote:
> >> >
> >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> >> >
> >> > FYI. Even looks bigtop used some where[1] also..
> >> > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154442656%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=2z0gWzY%2FE0XLqpCCtPpLUS8KFJm9%2BNdd0WFa%2BiMivjM%3D&reserved=0(Microsoft_product)
> >> >
> >> >
> >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
> wrote:
> >> >
> >> > Thank you for your explanation, Brahma.
> >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1])
> is supposed to be a
> >> > trademark of Redoop, so they can name the script
> crh-select without
> >> > problem.
> >> > But regarding BDP for example, I can easily find
> products that have
> >> > the same name [2][3][4] as you already mentioned, so
> I'd like to
> >> > recommend bigtop-select for avoiding unnecessary
> trouble.
> >> > Or, a single and more general word just like
> conf-select may be less
> >> > troublesome than bdp. How about "stack-select", for
> example?
> >> >
> >> > [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154598913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=r6VVzkoCsFI9aqRDqsPHRmvGIfFNEfK5vxmeB8YPn60%3D&reserved=0
> >> > [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154598913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DRwdWtO1nULYwZfbNO6Nd1cyxCA3yLX7GN%2FvruwlvCY%3D&reserved=0
> >> > [3]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154598913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=W0Jk1U%2F8Qy%2FitQfXo3UxEnEIU%2Ffq5THuKwUgeZt8Vr4%3D&reserved=0
> >> > [4]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154598913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xtOYwDwYrv8Uw%2BaCFU0m7fPHD%2BUK1mJEObIS2gkWoW8%3D&reserved=0
> >> >
> >> > Kengo Seki <se...@apache.org>
> >> >
> >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy
> <bb...@visa.com> wrote:
> >> > >
> >> > > >Do you mean that you're going to name the
> module (same as "component"
> >> > > >in the Bigtop terminology, I think)
> bigtop-distro-select,
> >> > > >and still the script in question bdp-select?
> If so, is there any
> >> > > >reason that the script must be that name?
> >> > > >(No offence, I just want to understand your
> thoughts and its
> >> > > >background, and avoid the conflict or user's
> confusion with existing
> >> > > >trademarks or products)
> >> > >
> >> > > Thanks @Kengo Seki for consolidating all the
> concerns. Name should represent the stack which includes all the components
> hence planning to have like bdp,bds...and this only one file like below[1]
> which has done redoop.
> >> > >
> >> > >
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154598913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=v9l0wppngIH0oX%2B%2F3orjM1J5%2F1qz%2Bai%2FGMyVrKDn1Ng%3D&reserved=0
> >> > >
> >> > >
> >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
> sekikn@apache.org> wrote:
> >> > >
> >> > > The following concern Masatake mentioned
> before is an important point,
> >> > > so I talked to Brahma for clarifying his
> intention on the ASF Slack
> >> > > yesterday.
> >> > >
> >> > > > Multiple versions of the same package
> (deb/rpm) can not be installed at the same time.
> >> > > > IIRC, HDP uses convention in which the
> product version is part of package name
> >> > > > for addressing this.
> >> > >
> >> > > > I don't like to bring the awkward package
> name convention to Bigtop
> >> > > > at least by default.
> >> > >
> >> > > He's planning to adopt the same mitigation as
> HDP for now, but he
> >> > > doesn't intend to change the default package
> naming convention of
> >> > > Bigtop,
> >> > > but just add a new functionality to include an
> extra part into the
> >> > > package name for avoiding conflict, which is
> disabled by default.
> >> > >
> >> > > And Brahma, let me confirm about the following
> reply:
> >> > >
> >> > > > Sure, we can have module name like
> bigtop-distro-select.
> >> > >
> >> > > Do you mean that you're going to name the
> module (same as "component"
> >> > > in the Bigtop terminology, I think)
> bigtop-distro-select,
> >> > > and still the script in question bdp-select?
> If so, is there any
> >> > > reason that the script must be that name?
> >> > > (No offence, I just want to understand your
> thoughts and its
> >> > > background, and avoid the conflict or user's
> confusion with existing
> >> > > trademarks or products)
> >> > >
> >> > > Kengo Seki <se...@apache.org>
> >> > >
> >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma
> Reddy
> >> > > <bb...@visa.com.invalid> wrote:
> >> > > >
> >> > > > > The name of stack based no Bigtop should
> be Bigtop.
> >> > > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> >> > > > > I will cast -1 if someone submit a
> patch to add a module with the name spoiling branding.
> >> > > >
> >> > > > Sure, we can have module name like
> bigtop-distro-select.
> >> > > > Initially we'll do this separate branch.
> >> > > >
> >> > > >
> >> > > >
> >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.co.jp> wrote:
> >> > > >
> >> > > > > I believe it's for project name. isn't
> it.?
> >> > > >
> >> > > > projects and products.
> >> > > >
> >> > > > > IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> >> > > >
> >> > > > The name of stack based no Bigtop should
> be Bigtop.
> >> > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> >> > > > I will cast -1 if someone submit a patch
> to add a module with the name spoiling branding.
> >> > > >
> >> > > >
> >> > > > On 2022/07/06 11:44, Battula, Brahma
> Reddy wrote:
> >> > > > >
> >> > > > > I believe it's for project name. isn't
> it.?
> >> > > > >
> >> > > > >
> >> > > > > On 06/07/22, 7:27 AM, "Masatake
> Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >> > > > >
> >> > > > > > But As we are not releasing as
> enterprise should be fine I think. IMO, We need to create folders and refer
> stacknames so ambari-select,bigtop-select wn't looks good.
> >> > > > >
> >> > > > > Not fine.
> >> > > > > We have a trademark policy.
> >> > > > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154598913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7fg1SLd4T%2BHcatC%2FfydvbBHMuUCGsELUVG0K0cz9twE%3D&reserved=0
> >> > > > >
> >> > > > > On 2022/07/06 10:37, Battula,
> Brahma Reddy wrote:
> >> > > > > >> Should we avoid unrecognized
> brand which may be trademark of someone?
> >> > > > > >> ambari-select or bigtop-select
> should be enough.
> >> > > > > >
> >> > > > > > Not sure, where to confirm
> whether there is already trademark. When I googled found so many.
> >> > > > > > But As we are not releasing as
> enterprise should be fine I think. IMO, We need to create folders and refer
> stacknames so ambari-select,bigtop-select wn't looks good.
> >> > > > > > May be you can refer the
> initial proposal [2] where I mentioned some more names.
> (BDS-BigDataStack,OSS-OpenSourceSelect..)
> >> > > > > >
> >> > > > > > Finally thanks a bunch for long
> healthy discussions on this. Mostly we all same page now.
> >> > > > > >
> >> > > > > > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154598913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NRbHBco2%2B8CBz9UhK15tOzLSl80zjnonKI1jV6bAs6o%3D&reserved=0
> >> > > > > >
> >> > > > > > 2.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154598913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=MWAVUH1ANFYOJv8L98vv7tFntLIxLHvuU8TbQKI2W5Y%3D&reserved=0
> >> > > > > >
> >> > > > > >
> >> > > > > > On 06/07/22, 4:01 AM, "Masatake
> Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >> > > > > >
> >> > > > > > > We have still not
> officially finalized the new replacement name for
> >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> >> > > > > >
> >> > > > > > Should we avoid
> unrecognized brand which may be trademark of someone?
> >> > > > > > ambari-select or
> bigtop-select should be enough.
> >> > > > > >
> >> > > > > > On 2022/06/29 13:52, Viraj
> Jasani wrote:
> >> > > > > > > Hi Ambari/Bigtop dev,
> >> > > > > > >
> >> > > > > > > As per the new roadmap
> of Apache Ambari, we would like to propose moving
> >> > > > > > > certain scripts
> (previously known as hdp-select and conf-select) to Bigtop
> >> > > > > > > so that their rpm
> installation could be managed independently.
> >> > > > > > > These scripts are a
> basic necessity in the Ambari framework for the
> >> > > > > > > installation of various
> Bigdata packages. The only major changes they would
> >> > > > > > > receive is when we
> onboard new services and components to Ambari, else they
> >> > > > > > > usually do not receive
> updates. In the past, we used to get hdp-select rpm
> >> > > > > > > downloaded and installed
> from HDP repositories.
> >> > > > > > >
> >> > > > > > > We have still not
> officially finalized the new replacement name for
> >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > >
> >> > > >
> ---------------------------------------------------------------------
> >> > > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> >> > > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> >> > > >
> >> > >
> >> > >
> ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> >> > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> >> > >
> >> > >
> >> >
> >> >
> ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> >> > For additional commands, e-mail:
> dev-help@ambari.apache.org
> >> >
> >> >
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> For additional commands, e-mail:
> dev-help@ambari.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
Is it Sept 9th .? Or Aug,29th..?
On 23/08/22, 8:50 PM, "Viraj Jasani" <vj...@apache.org> wrote:
Does 25th Aug 9 pm PST (26th Aug 9:30 am IST) work?
On Tue, Aug 23, 2022 at 2:48 AM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
> @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get the
> final conclusion on this..?
>
> Please let me know your availability, Can have one call to discuss on
> this..
>
>
> On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
> wrote:
>
> > -1 on development in branch.
> > It is not worth for maintaining the branch if the modules is so
> small
> > and barely updated as explained here.
> > It should not conflict to existing code.
> > I feel I must check the code before check-in based on this
> thread.
>
>
> Sure, Viraj or me can show the code to you.
>
> Can we've call on this Friday/Thrusday if that works..?
>
>
> On 11/07/22, 11:54 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com>
> wrote:
>
> > Sure, we can havemodule name like bigtop-distro-select.
> > Initially we'll do this separate branch.
>
> -1 on development in branch.
> It is not worth for maintaining the branch if the modules is so
> small
> and barely updated as explained here.
> It should not conflict to existing code.
> I feel I must check the code before check-in based on this thread.
>
> Masatake Iwasaki
>
> On 2022/07/11 8:23, Kengo Seki wrote:
> >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls.
> >
> > Oh, I interpreted your words "conclude" and "finalize" as you
> were
> > going to make a final decision. Brainstorming is welcome, of
> course.
> > (But I'm not so sure if all people concerned could join, due to
> time
> > difference and their schedule, etc.)
> >
> >> Can you suggest, how the changes will be also.. like folder,
> where you suggest to keep this...?
> >
> > Sure, here's my proposal:
> >
> > * Stack name: "BIGTOP"
> >
> > - The same name as the existing one [1]
> > - Because it deploys the packages generated by Bigtop
> > - The existing stack should be replaced with it, because that
> is
> > based on Bigtop 0.8 and too old to use now
> > - No concern about infringing others' trademark
> >
> > * Component/folder name: "bigtop-select"
> >
> > - Consistent naming convention with the existing tools such as
> > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > - If it sounds too simple and a bit unclear, a more
> descriptive name
> > might be an option, for example "bigtop-ambari-stack-selector"
> >
> > * Script name: "bigtop-select"
> >
> > - Consistent with the stack name
> > - No concern about infringing others' trademark
> >
> > [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154442656%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nxyJH5gFWfbVIvmL%2FI68CqnedwXr6dAOSaO8yVxrEi0%3D&reserved=0
> > [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154442656%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3HjYr5bEk92zB8w%2BNxiILTfwk6%2FD01yVScVqCZRdOSM%3D&reserved=0
> >
> > Kengo Seki <se...@apache.org>
> >
> > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> > <bb...@visa.com.invalid> wrote:
> >>
> >>> Technical decisions shouldn't be done on other places than
> public mailing lists,
> >>> as described in the "Open Communications" section of [1] and
> [2].
> >> > So we should conclude the discussion in this mailing list.
> >> > (And with my poor English, I'm not so confident to catch up
> with your
> >> > fluent talk ;)
> >>
> >> I believe , I knew the apache way which you mentioned. We are
> not going conclude anything which comes to bigtop other than this mailing
> list.
> >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls. Hence asking let's
> have call so that we can brainstorm. Even after call, everything will be
> published what we discussed.
> >>
> >> I think, whiteboarding will help to catch up with you.
> >>
> >> You all the think "bigtop-select" will be best option right..?
> Can you suggest, how the changes will be also.. like folder, where you
> suggest to keep this...?
> >>
> >> And if the name represents the stack which we are going to
> deploy should fine I feel.. (if it's not BDP, may be
> OBDP:OpensourceBigDataPlatform.)
> >>
> >> @Viraj Jasani and others any thoughts..?
> >>
> >>
> >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org> wrote:
> >>
> >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> >>
> >> Technical decisions shouldn't be done on other places than
> public mailing lists,
> >> as described in the "Open Communications" section of [1]
> and [2].
> >> So we should conclude the discussion in this mailing list.
> >> (And with my poor English, I'm not so confident to catch
> up with your
> >> fluent talk ;)
> >>
> >> > FYI. Even looks bigtop used some where also..
> >>
> >> Bigtop is ASF's trademark as you can see in the "Apache
> Bigtop®
> >> software" section of [3].
> >> So it doesn't have the risk of trademark infringement.
> >>
> >> [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154442656%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BKaxiwRrPD99gV1ryMQY%2F1S0Gp3iV5xsT7Pw5l1bCHA%3D&reserved=0
> >> [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154442656%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=z%2BqHDEs9Z08Q7lxVpizkcUCZ2ts6r0keL4jveRl9gaw%3D&reserved=0
> >> [3]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154442656%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=SAg10ICLr2RAoi4WEQEKzu6Y7PS0Nri1d6%2FsjOFvpbo%3D&reserved=0
> >>
> >> Kengo Seki <se...@apache.org>
> >>
> >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> >> <bb...@visa.com.invalid> wrote:
> >> >
> >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> >> >
> >> > FYI. Even looks bigtop used some where[1] also..
> >> > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154442656%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=2z0gWzY%2FE0XLqpCCtPpLUS8KFJm9%2BNdd0WFa%2BiMivjM%3D&reserved=0(Microsoft_product)
> >> >
> >> >
> >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
> wrote:
> >> >
> >> > Thank you for your explanation, Brahma.
> >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1])
> is supposed to be a
> >> > trademark of Redoop, so they can name the script
> crh-select without
> >> > problem.
> >> > But regarding BDP for example, I can easily find
> products that have
> >> > the same name [2][3][4] as you already mentioned, so
> I'd like to
> >> > recommend bigtop-select for avoiding unnecessary
> trouble.
> >> > Or, a single and more general word just like
> conf-select may be less
> >> > troublesome than bdp. How about "stack-select", for
> example?
> >> >
> >> > [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154598913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=r6VVzkoCsFI9aqRDqsPHRmvGIfFNEfK5vxmeB8YPn60%3D&reserved=0
> >> > [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154598913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DRwdWtO1nULYwZfbNO6Nd1cyxCA3yLX7GN%2FvruwlvCY%3D&reserved=0
> >> > [3]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154598913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=W0Jk1U%2F8Qy%2FitQfXo3UxEnEIU%2Ffq5THuKwUgeZt8Vr4%3D&reserved=0
> >> > [4]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154598913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xtOYwDwYrv8Uw%2BaCFU0m7fPHD%2BUK1mJEObIS2gkWoW8%3D&reserved=0
> >> >
> >> > Kengo Seki <se...@apache.org>
> >> >
> >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy
> <bb...@visa.com> wrote:
> >> > >
> >> > > >Do you mean that you're going to name the
> module (same as "component"
> >> > > >in the Bigtop terminology, I think)
> bigtop-distro-select,
> >> > > >and still the script in question bdp-select?
> If so, is there any
> >> > > >reason that the script must be that name?
> >> > > >(No offence, I just want to understand your
> thoughts and its
> >> > > >background, and avoid the conflict or user's
> confusion with existing
> >> > > >trademarks or products)
> >> > >
> >> > > Thanks @Kengo Seki for consolidating all the
> concerns. Name should represent the stack which includes all the components
> hence planning to have like bdp,bds...and this only one file like below[1]
> which has done redoop.
> >> > >
> >> > >
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154598913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=v9l0wppngIH0oX%2B%2F3orjM1J5%2F1qz%2Bai%2FGMyVrKDn1Ng%3D&reserved=0
> >> > >
> >> > >
> >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
> sekikn@apache.org> wrote:
> >> > >
> >> > > The following concern Masatake mentioned
> before is an important point,
> >> > > so I talked to Brahma for clarifying his
> intention on the ASF Slack
> >> > > yesterday.
> >> > >
> >> > > > Multiple versions of the same package
> (deb/rpm) can not be installed at the same time.
> >> > > > IIRC, HDP uses convention in which the
> product version is part of package name
> >> > > > for addressing this.
> >> > >
> >> > > > I don't like to bring the awkward package
> name convention to Bigtop
> >> > > > at least by default.
> >> > >
> >> > > He's planning to adopt the same mitigation as
> HDP for now, but he
> >> > > doesn't intend to change the default package
> naming convention of
> >> > > Bigtop,
> >> > > but just add a new functionality to include an
> extra part into the
> >> > > package name for avoiding conflict, which is
> disabled by default.
> >> > >
> >> > > And Brahma, let me confirm about the following
> reply:
> >> > >
> >> > > > Sure, we can have module name like
> bigtop-distro-select.
> >> > >
> >> > > Do you mean that you're going to name the
> module (same as "component"
> >> > > in the Bigtop terminology, I think)
> bigtop-distro-select,
> >> > > and still the script in question bdp-select?
> If so, is there any
> >> > > reason that the script must be that name?
> >> > > (No offence, I just want to understand your
> thoughts and its
> >> > > background, and avoid the conflict or user's
> confusion with existing
> >> > > trademarks or products)
> >> > >
> >> > > Kengo Seki <se...@apache.org>
> >> > >
> >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma
> Reddy
> >> > > <bb...@visa.com.invalid> wrote:
> >> > > >
> >> > > > > The name of stack based no Bigtop should
> be Bigtop.
> >> > > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> >> > > > > I will cast -1 if someone submit a
> patch to add a module with the name spoiling branding.
> >> > > >
> >> > > > Sure, we can have module name like
> bigtop-distro-select.
> >> > > > Initially we'll do this separate branch.
> >> > > >
> >> > > >
> >> > > >
> >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.co.jp> wrote:
> >> > > >
> >> > > > > I believe it's for project name. isn't
> it.?
> >> > > >
> >> > > > projects and products.
> >> > > >
> >> > > > > IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> >> > > >
> >> > > > The name of stack based no Bigtop should
> be Bigtop.
> >> > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> >> > > > I will cast -1 if someone submit a patch
> to add a module with the name spoiling branding.
> >> > > >
> >> > > >
> >> > > > On 2022/07/06 11:44, Battula, Brahma
> Reddy wrote:
> >> > > > >
> >> > > > > I believe it's for project name. isn't
> it.?
> >> > > > >
> >> > > > >
> >> > > > > On 06/07/22, 7:27 AM, "Masatake
> Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >> > > > >
> >> > > > > > But As we are not releasing as
> enterprise should be fine I think. IMO, We need to create folders and refer
> stacknames so ambari-select,bigtop-select wn't looks good.
> >> > > > >
> >> > > > > Not fine.
> >> > > > > We have a trademark policy.
> >> > > > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154598913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7fg1SLd4T%2BHcatC%2FfydvbBHMuUCGsELUVG0K0cz9twE%3D&reserved=0
> >> > > > >
> >> > > > > On 2022/07/06 10:37, Battula,
> Brahma Reddy wrote:
> >> > > > > >> Should we avoid unrecognized
> brand which may be trademark of someone?
> >> > > > > >> ambari-select or bigtop-select
> should be enough.
> >> > > > > >
> >> > > > > > Not sure, where to confirm
> whether there is already trademark. When I googled found so many.
> >> > > > > > But As we are not releasing as
> enterprise should be fine I think. IMO, We need to create folders and refer
> stacknames so ambari-select,bigtop-select wn't looks good.
> >> > > > > > May be you can refer the
> initial proposal [2] where I mentioned some more names.
> (BDS-BigDataStack,OSS-OpenSourceSelect..)
> >> > > > > >
> >> > > > > > Finally thanks a bunch for long
> healthy discussions on this. Mostly we all same page now.
> >> > > > > >
> >> > > > > > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154598913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NRbHBco2%2B8CBz9UhK15tOzLSl80zjnonKI1jV6bAs6o%3D&reserved=0
> >> > > > > >
> >> > > > > > 2.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C297c4921c8c44eb2937108da851afa2e%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637968648154598913%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=MWAVUH1ANFYOJv8L98vv7tFntLIxLHvuU8TbQKI2W5Y%3D&reserved=0
> >> > > > > >
> >> > > > > >
> >> > > > > > On 06/07/22, 4:01 AM, "Masatake
> Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >> > > > > >
> >> > > > > > > We have still not
> officially finalized the new replacement name for
> >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> >> > > > > >
> >> > > > > > Should we avoid
> unrecognized brand which may be trademark of someone?
> >> > > > > > ambari-select or
> bigtop-select should be enough.
> >> > > > > >
> >> > > > > > On 2022/06/29 13:52, Viraj
> Jasani wrote:
> >> > > > > > > Hi Ambari/Bigtop dev,
> >> > > > > > >
> >> > > > > > > As per the new roadmap
> of Apache Ambari, we would like to propose moving
> >> > > > > > > certain scripts
> (previously known as hdp-select and conf-select) to Bigtop
> >> > > > > > > so that their rpm
> installation could be managed independently.
> >> > > > > > > These scripts are a
> basic necessity in the Ambari framework for the
> >> > > > > > > installation of various
> Bigdata packages. The only major changes they would
> >> > > > > > > receive is when we
> onboard new services and components to Ambari, else they
> >> > > > > > > usually do not receive
> updates. In the past, we used to get hdp-select rpm
> >> > > > > > > downloaded and installed
> from HDP repositories.
> >> > > > > > >
> >> > > > > > > We have still not
> officially finalized the new replacement name for
> >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > >
> >> > > >
> ---------------------------------------------------------------------
> >> > > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> >> > > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> >> > > >
> >> > >
> >> > >
> ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> >> > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> >> > >
> >> > >
> >> >
> >> >
> ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> >> > For additional commands, e-mail:
> dev-help@ambari.apache.org
> >> >
> >> >
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> For additional commands, e-mail:
> dev-help@ambari.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Viraj Jasani <vj...@apache.org>.
Does 25th Aug 9 pm PST (26th Aug 9:30 am IST) work?
On Tue, Aug 23, 2022 at 2:48 AM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
> @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get the
> final conclusion on this..?
>
> Please let me know your availability, Can have one call to discuss on
> this..
>
>
> On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
> wrote:
>
> > -1 on development in branch.
> > It is not worth for maintaining the branch if the modules is so
> small
> > and barely updated as explained here.
> > It should not conflict to existing code.
> > I feel I must check the code before check-in based on this
> thread.
>
>
> Sure, Viraj or me can show the code to you.
>
> Can we've call on this Friday/Thrusday if that works..?
>
>
> On 11/07/22, 11:54 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com>
> wrote:
>
> > Sure, we can havemodule name like bigtop-distro-select.
> > Initially we'll do this separate branch.
>
> -1 on development in branch.
> It is not worth for maintaining the branch if the modules is so
> small
> and barely updated as explained here.
> It should not conflict to existing code.
> I feel I must check the code before check-in based on this thread.
>
> Masatake Iwasaki
>
> On 2022/07/11 8:23, Kengo Seki wrote:
> >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls.
> >
> > Oh, I interpreted your words "conclude" and "finalize" as you
> were
> > going to make a final decision. Brainstorming is welcome, of
> course.
> > (But I'm not so sure if all people concerned could join, due to
> time
> > difference and their schedule, etc.)
> >
> >> Can you suggest, how the changes will be also.. like folder,
> where you suggest to keep this...?
> >
> > Sure, here's my proposal:
> >
> > * Stack name: "BIGTOP"
> >
> > - The same name as the existing one [1]
> > - Because it deploys the packages generated by Bigtop
> > - The existing stack should be replaced with it, because that
> is
> > based on Bigtop 0.8 and too old to use now
> > - No concern about infringing others' trademark
> >
> > * Component/folder name: "bigtop-select"
> >
> > - Consistent naming convention with the existing tools such as
> > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > - If it sounds too simple and a bit unclear, a more
> descriptive name
> > might be an option, for example "bigtop-ambari-stack-selector"
> >
> > * Script name: "bigtop-select"
> >
> > - Consistent with the stack name
> > - No concern about infringing others' trademark
> >
> > [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=l6OMfWaJl4yKV6zjSYiMQXYy1HBuJhs5nej0Co9K3FA%3D&reserved=0
> > [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5nM8IrpP067odUjmxS%2Bv8xxDchCLGVOplmA%2Fo8Iq%2BOg%3D&reserved=0
> >
> > Kengo Seki <se...@apache.org>
> >
> > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> > <bb...@visa.com.invalid> wrote:
> >>
> >>> Technical decisions shouldn't be done on other places than
> public mailing lists,
> >>> as described in the "Open Communications" section of [1] and
> [2].
> >> > So we should conclude the discussion in this mailing list.
> >> > (And with my poor English, I'm not so confident to catch up
> with your
> >> > fluent talk ;)
> >>
> >> I believe , I knew the apache way which you mentioned. We are
> not going conclude anything which comes to bigtop other than this mailing
> list.
> >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls. Hence asking let's
> have call so that we can brainstorm. Even after call, everything will be
> published what we discussed.
> >>
> >> I think, whiteboarding will help to catch up with you.
> >>
> >> You all the think "bigtop-select" will be best option right..?
> Can you suggest, how the changes will be also.. like folder, where you
> suggest to keep this...?
> >>
> >> And if the name represents the stack which we are going to
> deploy should fine I feel.. (if it's not BDP, may be
> OBDP:OpensourceBigDataPlatform.)
> >>
> >> @Viraj Jasani and others any thoughts..?
> >>
> >>
> >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org> wrote:
> >>
> >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> >>
> >> Technical decisions shouldn't be done on other places than
> public mailing lists,
> >> as described in the "Open Communications" section of [1]
> and [2].
> >> So we should conclude the discussion in this mailing list.
> >> (And with my poor English, I'm not so confident to catch
> up with your
> >> fluent talk ;)
> >>
> >> > FYI. Even looks bigtop used some where also..
> >>
> >> Bigtop is ASF's trademark as you can see in the "Apache
> Bigtop®
> >> software" section of [3].
> >> So it doesn't have the risk of trademark infringement.
> >>
> >> [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zaDwUjNvgU0eP5NY7wPq2BISd%2FiLs7dp92fwFUfwFCI%3D&reserved=0
> >> [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DlCOz5ajX%2FziXmx7ZeD5xa0WzX06Akm3pYuMs5KX9h4%3D&reserved=0
> >> [3]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KVc1YjBSUzAFexYTQ2IoiLOr0vkm85NBqI8WZC7g67s%3D&reserved=0
> >>
> >> Kengo Seki <se...@apache.org>
> >>
> >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> >> <bb...@visa.com.invalid> wrote:
> >> >
> >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> >> >
> >> > FYI. Even looks bigtop used some where[1] also..
> >> > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BPQQCUDhl%2BHGNS%2F1aLtS38Qah9zDs06qd2y%2B%2BUE%2FBKk%3D&reserved=0(Microsoft_product)
> >> >
> >> >
> >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
> wrote:
> >> >
> >> > Thank you for your explanation, Brahma.
> >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1])
> is supposed to be a
> >> > trademark of Redoop, so they can name the script
> crh-select without
> >> > problem.
> >> > But regarding BDP for example, I can easily find
> products that have
> >> > the same name [2][3][4] as you already mentioned, so
> I'd like to
> >> > recommend bigtop-select for avoiding unnecessary
> trouble.
> >> > Or, a single and more general word just like
> conf-select may be less
> >> > troublesome than bdp. How about "stack-select", for
> example?
> >> >
> >> > [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CM8y%2Bom6hpEl98x8G2ve5J98W%2FVeEkSPnwgFiYd2C98%3D&reserved=0
> >> > [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=g2ng5E0%2BTb6N52isJ7guO10C3zTGA86dSafV9h0LXbU%3D&reserved=0
> >> > [3]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qrU%2F4FJ5EjqoD0opzxVL1wM%2FTEM%2B%2B8MoqkZHHZNA%2Fk0%3D&reserved=0
> >> > [4]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KfEGcZwpdvVZUaW1XsaUMGqVYcZyysmZhjl%2BR6Iq2wI%3D&reserved=0
> >> >
> >> > Kengo Seki <se...@apache.org>
> >> >
> >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy
> <bb...@visa.com> wrote:
> >> > >
> >> > > >Do you mean that you're going to name the
> module (same as "component"
> >> > > >in the Bigtop terminology, I think)
> bigtop-distro-select,
> >> > > >and still the script in question bdp-select?
> If so, is there any
> >> > > >reason that the script must be that name?
> >> > > >(No offence, I just want to understand your
> thoughts and its
> >> > > >background, and avoid the conflict or user's
> confusion with existing
> >> > > >trademarks or products)
> >> > >
> >> > > Thanks @Kengo Seki for consolidating all the
> concerns. Name should represent the stack which includes all the components
> hence planning to have like bdp,bds...and this only one file like below[1]
> which has done redoop.
> >> > >
> >> > >
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=e4oze4857dGtVIq14Ow8yzFnDhW9b2OG85sJMWfXbi4%3D&reserved=0
> >> > >
> >> > >
> >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
> sekikn@apache.org> wrote:
> >> > >
> >> > > The following concern Masatake mentioned
> before is an important point,
> >> > > so I talked to Brahma for clarifying his
> intention on the ASF Slack
> >> > > yesterday.
> >> > >
> >> > > > Multiple versions of the same package
> (deb/rpm) can not be installed at the same time.
> >> > > > IIRC, HDP uses convention in which the
> product version is part of package name
> >> > > > for addressing this.
> >> > >
> >> > > > I don't like to bring the awkward package
> name convention to Bigtop
> >> > > > at least by default.
> >> > >
> >> > > He's planning to adopt the same mitigation as
> HDP for now, but he
> >> > > doesn't intend to change the default package
> naming convention of
> >> > > Bigtop,
> >> > > but just add a new functionality to include an
> extra part into the
> >> > > package name for avoiding conflict, which is
> disabled by default.
> >> > >
> >> > > And Brahma, let me confirm about the following
> reply:
> >> > >
> >> > > > Sure, we can have module name like
> bigtop-distro-select.
> >> > >
> >> > > Do you mean that you're going to name the
> module (same as "component"
> >> > > in the Bigtop terminology, I think)
> bigtop-distro-select,
> >> > > and still the script in question bdp-select?
> If so, is there any
> >> > > reason that the script must be that name?
> >> > > (No offence, I just want to understand your
> thoughts and its
> >> > > background, and avoid the conflict or user's
> confusion with existing
> >> > > trademarks or products)
> >> > >
> >> > > Kengo Seki <se...@apache.org>
> >> > >
> >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma
> Reddy
> >> > > <bb...@visa.com.invalid> wrote:
> >> > > >
> >> > > > > The name of stack based no Bigtop should
> be Bigtop.
> >> > > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> >> > > > > I will cast -1 if someone submit a
> patch to add a module with the name spoiling branding.
> >> > > >
> >> > > > Sure, we can have module name like
> bigtop-distro-select.
> >> > > > Initially we'll do this separate branch.
> >> > > >
> >> > > >
> >> > > >
> >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.co.jp> wrote:
> >> > > >
> >> > > > > I believe it's for project name. isn't
> it.?
> >> > > >
> >> > > > projects and products.
> >> > > >
> >> > > > > IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> >> > > >
> >> > > > The name of stack based no Bigtop should
> be Bigtop.
> >> > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> >> > > > I will cast -1 if someone submit a patch
> to add a module with the name spoiling branding.
> >> > > >
> >> > > >
> >> > > > On 2022/07/06 11:44, Battula, Brahma
> Reddy wrote:
> >> > > > >
> >> > > > > I believe it's for project name. isn't
> it.?
> >> > > > >
> >> > > > >
> >> > > > > On 06/07/22, 7:27 AM, "Masatake
> Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >> > > > >
> >> > > > > > But As we are not releasing as
> enterprise should be fine I think. IMO, We need to create folders and refer
> stacknames so ambari-select,bigtop-select wn't looks good.
> >> > > > >
> >> > > > > Not fine.
> >> > > > > We have a trademark policy.
> >> > > > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Aj5p2h78PdIXFHsJi7Q6ouR5eG33vf1LA2wdGnlaF%2FQ%3D&reserved=0
> >> > > > >
> >> > > > > On 2022/07/06 10:37, Battula,
> Brahma Reddy wrote:
> >> > > > > >> Should we avoid unrecognized
> brand which may be trademark of someone?
> >> > > > > >> ambari-select or bigtop-select
> should be enough.
> >> > > > > >
> >> > > > > > Not sure, where to confirm
> whether there is already trademark. When I googled found so many.
> >> > > > > > But As we are not releasing as
> enterprise should be fine I think. IMO, We need to create folders and refer
> stacknames so ambari-select,bigtop-select wn't looks good.
> >> > > > > > May be you can refer the
> initial proposal [2] where I mentioned some more names.
> (BDS-BigDataStack,OSS-OpenSourceSelect..)
> >> > > > > >
> >> > > > > > Finally thanks a bunch for long
> healthy discussions on this. Mostly we all same page now.
> >> > > > > >
> >> > > > > > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=p1br7DcndgZq6Z5m4CvTSZOSFhkKtie%2BeqXERXuY58Q%3D&reserved=0
> >> > > > > >
> >> > > > > > 2.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EON1ukunh1oyFb5HID57FuOv9DjIBteeoCYuQfx34Gg%3D&reserved=0
> >> > > > > >
> >> > > > > >
> >> > > > > > On 06/07/22, 4:01 AM, "Masatake
> Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >> > > > > >
> >> > > > > > > We have still not
> officially finalized the new replacement name for
> >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> >> > > > > >
> >> > > > > > Should we avoid
> unrecognized brand which may be trademark of someone?
> >> > > > > > ambari-select or
> bigtop-select should be enough.
> >> > > > > >
> >> > > > > > On 2022/06/29 13:52, Viraj
> Jasani wrote:
> >> > > > > > > Hi Ambari/Bigtop dev,
> >> > > > > > >
> >> > > > > > > As per the new roadmap
> of Apache Ambari, we would like to propose moving
> >> > > > > > > certain scripts
> (previously known as hdp-select and conf-select) to Bigtop
> >> > > > > > > so that their rpm
> installation could be managed independently.
> >> > > > > > > These scripts are a
> basic necessity in the Ambari framework for the
> >> > > > > > > installation of various
> Bigdata packages. The only major changes they would
> >> > > > > > > receive is when we
> onboard new services and components to Ambari, else they
> >> > > > > > > usually do not receive
> updates. In the past, we used to get hdp-select rpm
> >> > > > > > > downloaded and installed
> from HDP repositories.
> >> > > > > > >
> >> > > > > > > We have still not
> officially finalized the new replacement name for
> >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > >
> >> > > >
> ---------------------------------------------------------------------
> >> > > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> >> > > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> >> > > >
> >> > >
> >> > >
> ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> >> > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> >> > >
> >> > >
> >> >
> >> >
> ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> >> > For additional commands, e-mail:
> dev-help@ambari.apache.org
> >> >
> >> >
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> For additional commands, e-mail:
> dev-help@ambari.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Viraj Jasani <vj...@apache.org>.
Does 25th Aug 9 pm PST (26th Aug 9:30 am IST) work?
On Tue, Aug 23, 2022 at 2:48 AM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
> @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get the
> final conclusion on this..?
>
> Please let me know your availability, Can have one call to discuss on
> this..
>
>
> On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
> wrote:
>
> > -1 on development in branch.
> > It is not worth for maintaining the branch if the modules is so
> small
> > and barely updated as explained here.
> > It should not conflict to existing code.
> > I feel I must check the code before check-in based on this
> thread.
>
>
> Sure, Viraj or me can show the code to you.
>
> Can we've call on this Friday/Thrusday if that works..?
>
>
> On 11/07/22, 11:54 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com>
> wrote:
>
> > Sure, we can havemodule name like bigtop-distro-select.
> > Initially we'll do this separate branch.
>
> -1 on development in branch.
> It is not worth for maintaining the branch if the modules is so
> small
> and barely updated as explained here.
> It should not conflict to existing code.
> I feel I must check the code before check-in based on this thread.
>
> Masatake Iwasaki
>
> On 2022/07/11 8:23, Kengo Seki wrote:
> >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls.
> >
> > Oh, I interpreted your words "conclude" and "finalize" as you
> were
> > going to make a final decision. Brainstorming is welcome, of
> course.
> > (But I'm not so sure if all people concerned could join, due to
> time
> > difference and their schedule, etc.)
> >
> >> Can you suggest, how the changes will be also.. like folder,
> where you suggest to keep this...?
> >
> > Sure, here's my proposal:
> >
> > * Stack name: "BIGTOP"
> >
> > - The same name as the existing one [1]
> > - Because it deploys the packages generated by Bigtop
> > - The existing stack should be replaced with it, because that
> is
> > based on Bigtop 0.8 and too old to use now
> > - No concern about infringing others' trademark
> >
> > * Component/folder name: "bigtop-select"
> >
> > - Consistent naming convention with the existing tools such as
> > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > - If it sounds too simple and a bit unclear, a more
> descriptive name
> > might be an option, for example "bigtop-ambari-stack-selector"
> >
> > * Script name: "bigtop-select"
> >
> > - Consistent with the stack name
> > - No concern about infringing others' trademark
> >
> > [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=l6OMfWaJl4yKV6zjSYiMQXYy1HBuJhs5nej0Co9K3FA%3D&reserved=0
> > [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5nM8IrpP067odUjmxS%2Bv8xxDchCLGVOplmA%2Fo8Iq%2BOg%3D&reserved=0
> >
> > Kengo Seki <se...@apache.org>
> >
> > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> > <bb...@visa.com.invalid> wrote:
> >>
> >>> Technical decisions shouldn't be done on other places than
> public mailing lists,
> >>> as described in the "Open Communications" section of [1] and
> [2].
> >> > So we should conclude the discussion in this mailing list.
> >> > (And with my poor English, I'm not so confident to catch up
> with your
> >> > fluent talk ;)
> >>
> >> I believe , I knew the apache way which you mentioned. We are
> not going conclude anything which comes to bigtop other than this mailing
> list.
> >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls. Hence asking let's
> have call so that we can brainstorm. Even after call, everything will be
> published what we discussed.
> >>
> >> I think, whiteboarding will help to catch up with you.
> >>
> >> You all the think "bigtop-select" will be best option right..?
> Can you suggest, how the changes will be also.. like folder, where you
> suggest to keep this...?
> >>
> >> And if the name represents the stack which we are going to
> deploy should fine I feel.. (if it's not BDP, may be
> OBDP:OpensourceBigDataPlatform.)
> >>
> >> @Viraj Jasani and others any thoughts..?
> >>
> >>
> >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org> wrote:
> >>
> >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> >>
> >> Technical decisions shouldn't be done on other places than
> public mailing lists,
> >> as described in the "Open Communications" section of [1]
> and [2].
> >> So we should conclude the discussion in this mailing list.
> >> (And with my poor English, I'm not so confident to catch
> up with your
> >> fluent talk ;)
> >>
> >> > FYI. Even looks bigtop used some where also..
> >>
> >> Bigtop is ASF's trademark as you can see in the "Apache
> Bigtop®
> >> software" section of [3].
> >> So it doesn't have the risk of trademark infringement.
> >>
> >> [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zaDwUjNvgU0eP5NY7wPq2BISd%2FiLs7dp92fwFUfwFCI%3D&reserved=0
> >> [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DlCOz5ajX%2FziXmx7ZeD5xa0WzX06Akm3pYuMs5KX9h4%3D&reserved=0
> >> [3]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KVc1YjBSUzAFexYTQ2IoiLOr0vkm85NBqI8WZC7g67s%3D&reserved=0
> >>
> >> Kengo Seki <se...@apache.org>
> >>
> >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> >> <bb...@visa.com.invalid> wrote:
> >> >
> >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> >> >
> >> > FYI. Even looks bigtop used some where[1] also..
> >> > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BPQQCUDhl%2BHGNS%2F1aLtS38Qah9zDs06qd2y%2B%2BUE%2FBKk%3D&reserved=0(Microsoft_product)
> >> >
> >> >
> >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
> wrote:
> >> >
> >> > Thank you for your explanation, Brahma.
> >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1])
> is supposed to be a
> >> > trademark of Redoop, so they can name the script
> crh-select without
> >> > problem.
> >> > But regarding BDP for example, I can easily find
> products that have
> >> > the same name [2][3][4] as you already mentioned, so
> I'd like to
> >> > recommend bigtop-select for avoiding unnecessary
> trouble.
> >> > Or, a single and more general word just like
> conf-select may be less
> >> > troublesome than bdp. How about "stack-select", for
> example?
> >> >
> >> > [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CM8y%2Bom6hpEl98x8G2ve5J98W%2FVeEkSPnwgFiYd2C98%3D&reserved=0
> >> > [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=g2ng5E0%2BTb6N52isJ7guO10C3zTGA86dSafV9h0LXbU%3D&reserved=0
> >> > [3]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qrU%2F4FJ5EjqoD0opzxVL1wM%2FTEM%2B%2B8MoqkZHHZNA%2Fk0%3D&reserved=0
> >> > [4]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KfEGcZwpdvVZUaW1XsaUMGqVYcZyysmZhjl%2BR6Iq2wI%3D&reserved=0
> >> >
> >> > Kengo Seki <se...@apache.org>
> >> >
> >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy
> <bb...@visa.com> wrote:
> >> > >
> >> > > >Do you mean that you're going to name the
> module (same as "component"
> >> > > >in the Bigtop terminology, I think)
> bigtop-distro-select,
> >> > > >and still the script in question bdp-select?
> If so, is there any
> >> > > >reason that the script must be that name?
> >> > > >(No offence, I just want to understand your
> thoughts and its
> >> > > >background, and avoid the conflict or user's
> confusion with existing
> >> > > >trademarks or products)
> >> > >
> >> > > Thanks @Kengo Seki for consolidating all the
> concerns. Name should represent the stack which includes all the components
> hence planning to have like bdp,bds...and this only one file like below[1]
> which has done redoop.
> >> > >
> >> > >
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=e4oze4857dGtVIq14Ow8yzFnDhW9b2OG85sJMWfXbi4%3D&reserved=0
> >> > >
> >> > >
> >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
> sekikn@apache.org> wrote:
> >> > >
> >> > > The following concern Masatake mentioned
> before is an important point,
> >> > > so I talked to Brahma for clarifying his
> intention on the ASF Slack
> >> > > yesterday.
> >> > >
> >> > > > Multiple versions of the same package
> (deb/rpm) can not be installed at the same time.
> >> > > > IIRC, HDP uses convention in which the
> product version is part of package name
> >> > > > for addressing this.
> >> > >
> >> > > > I don't like to bring the awkward package
> name convention to Bigtop
> >> > > > at least by default.
> >> > >
> >> > > He's planning to adopt the same mitigation as
> HDP for now, but he
> >> > > doesn't intend to change the default package
> naming convention of
> >> > > Bigtop,
> >> > > but just add a new functionality to include an
> extra part into the
> >> > > package name for avoiding conflict, which is
> disabled by default.
> >> > >
> >> > > And Brahma, let me confirm about the following
> reply:
> >> > >
> >> > > > Sure, we can have module name like
> bigtop-distro-select.
> >> > >
> >> > > Do you mean that you're going to name the
> module (same as "component"
> >> > > in the Bigtop terminology, I think)
> bigtop-distro-select,
> >> > > and still the script in question bdp-select?
> If so, is there any
> >> > > reason that the script must be that name?
> >> > > (No offence, I just want to understand your
> thoughts and its
> >> > > background, and avoid the conflict or user's
> confusion with existing
> >> > > trademarks or products)
> >> > >
> >> > > Kengo Seki <se...@apache.org>
> >> > >
> >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma
> Reddy
> >> > > <bb...@visa.com.invalid> wrote:
> >> > > >
> >> > > > > The name of stack based no Bigtop should
> be Bigtop.
> >> > > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> >> > > > > I will cast -1 if someone submit a
> patch to add a module with the name spoiling branding.
> >> > > >
> >> > > > Sure, we can have module name like
> bigtop-distro-select.
> >> > > > Initially we'll do this separate branch.
> >> > > >
> >> > > >
> >> > > >
> >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.co.jp> wrote:
> >> > > >
> >> > > > > I believe it's for project name. isn't
> it.?
> >> > > >
> >> > > > projects and products.
> >> > > >
> >> > > > > IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> >> > > >
> >> > > > The name of stack based no Bigtop should
> be Bigtop.
> >> > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> >> > > > I will cast -1 if someone submit a patch
> to add a module with the name spoiling branding.
> >> > > >
> >> > > >
> >> > > > On 2022/07/06 11:44, Battula, Brahma
> Reddy wrote:
> >> > > > >
> >> > > > > I believe it's for project name. isn't
> it.?
> >> > > > >
> >> > > > >
> >> > > > > On 06/07/22, 7:27 AM, "Masatake
> Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >> > > > >
> >> > > > > > But As we are not releasing as
> enterprise should be fine I think. IMO, We need to create folders and refer
> stacknames so ambari-select,bigtop-select wn't looks good.
> >> > > > >
> >> > > > > Not fine.
> >> > > > > We have a trademark policy.
> >> > > > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Aj5p2h78PdIXFHsJi7Q6ouR5eG33vf1LA2wdGnlaF%2FQ%3D&reserved=0
> >> > > > >
> >> > > > > On 2022/07/06 10:37, Battula,
> Brahma Reddy wrote:
> >> > > > > >> Should we avoid unrecognized
> brand which may be trademark of someone?
> >> > > > > >> ambari-select or bigtop-select
> should be enough.
> >> > > > > >
> >> > > > > > Not sure, where to confirm
> whether there is already trademark. When I googled found so many.
> >> > > > > > But As we are not releasing as
> enterprise should be fine I think. IMO, We need to create folders and refer
> stacknames so ambari-select,bigtop-select wn't looks good.
> >> > > > > > May be you can refer the
> initial proposal [2] where I mentioned some more names.
> (BDS-BigDataStack,OSS-OpenSourceSelect..)
> >> > > > > >
> >> > > > > > Finally thanks a bunch for long
> healthy discussions on this. Mostly we all same page now.
> >> > > > > >
> >> > > > > > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=p1br7DcndgZq6Z5m4CvTSZOSFhkKtie%2BeqXERXuY58Q%3D&reserved=0
> >> > > > > >
> >> > > > > > 2.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EON1ukunh1oyFb5HID57FuOv9DjIBteeoCYuQfx34Gg%3D&reserved=0
> >> > > > > >
> >> > > > > >
> >> > > > > > On 06/07/22, 4:01 AM, "Masatake
> Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >> > > > > >
> >> > > > > > > We have still not
> officially finalized the new replacement name for
> >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> >> > > > > >
> >> > > > > > Should we avoid
> unrecognized brand which may be trademark of someone?
> >> > > > > > ambari-select or
> bigtop-select should be enough.
> >> > > > > >
> >> > > > > > On 2022/06/29 13:52, Viraj
> Jasani wrote:
> >> > > > > > > Hi Ambari/Bigtop dev,
> >> > > > > > >
> >> > > > > > > As per the new roadmap
> of Apache Ambari, we would like to propose moving
> >> > > > > > > certain scripts
> (previously known as hdp-select and conf-select) to Bigtop
> >> > > > > > > so that their rpm
> installation could be managed independently.
> >> > > > > > > These scripts are a
> basic necessity in the Ambari framework for the
> >> > > > > > > installation of various
> Bigdata packages. The only major changes they would
> >> > > > > > > receive is when we
> onboard new services and components to Ambari, else they
> >> > > > > > > usually do not receive
> updates. In the past, we used to get hdp-select rpm
> >> > > > > > > downloaded and installed
> from HDP repositories.
> >> > > > > > >
> >> > > > > > > We have still not
> officially finalized the new replacement name for
> >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > >
> >> > > >
> ---------------------------------------------------------------------
> >> > > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> >> > > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> >> > > >
> >> > >
> >> > >
> ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> >> > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> >> > >
> >> > >
> >> >
> >> >
> ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> >> > For additional commands, e-mail:
> dev-help@ambari.apache.org
> >> >
> >> >
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> For additional commands, e-mail:
> dev-help@ambari.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Viraj Jasani <vj...@apache.org>.
Do we want to use the BIGTOP stack for 2.7.7 as well? Or we want to use it
for 2.8.0 and 3.0.0 onwards only to minimize the big changes for 2.7.7
patch release?
On Tue, Sep 20, 2022 at 7:12 PM 吴治国 <wz...@163.com> wrote:
> I think we have enough to go on with Kengo’s proposal,
> Currently we don’t have enough developers(and I’m not willing to) to
> maintain a stack on our own like BDP.
>
> > Sure, here's my proposal:
> >
> > * Stack name: "BIGTOP"
> >
> > - The same name as the existing one [1]
> > - Because it deploys the packages generated by Bigtop
> > - The existing stack should be replaced with it, because that is
> > based on Bigtop 0.8 and too old to use now
> > - No concern about infringing others' trademark
> >
> > * Component/folder name: "bigtop-select"
> >
> > - Consistent naming convention with the existing tools such as
> > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > - If it sounds too simple and a bit unclear, a more descriptive name
> > might be an option, for example "bigtop-ambari-stack-selector"
> >
> > * Script name: "bigtop-select"
> >
> > - Consistent with the stack name
> > - No concern about infringing others' trademark
> >
> > [1]:
> https://github.com/apache/ambari/tree/release-2.7.6/ambari-server/src/main/resources/stacks/BIGTOP/0.8
> > [2]:
> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common <
> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common>
>
> Best Regards,
> Zhiguo Wu
>
> > On Sep 16, 2022, at 08:44, Masatake Iwasaki <iw...@oss.nttdata.com>
> wrote:
> >
> >
> >>>> May be we can name it as bdp-select. Or (bgp-select)
> >>> -1 as we already discussed.
> >> Thanks for your feedback, I would definitely honour it. As you are not
> open for discussion and asked us raise the PR hence you thought of
> discussing on the PR. What will be your final suggestion on this..?
> >
> > I'm -1 on the name like bdp-select or bgp-select as we discussed.
> > Feel free to open PR with appropriate module name.
> >
> > On 2022/09/05 16:30, Battula, Brahma Reddy wrote:
> >> Hi @Masatake Iwasaki,
> >>> -1 as we already discussed.
> >> Thanks for your feedback, I would definitely honour it. As you are not
> open for discussion and asked us raise the PR hence you thought of
> discussing on the PR. What will be your final suggestion on this..?
> >> @Roman Shaposhnik
> >> I just gone through the following jira[1] where you brought ambari to
> bigtop. Looks stack-select is not included, how it was maintained.?
> >> I thinking we should have one stack which can support for upgrading the
> existing the HDP deployed clusters. Even I can see somebody asking on
> bigtop[2].
> >> If bigtop is not right place, shall we include in ambari..? Please let
> me know your thoughts on this. This blocks the 2.7.7 release.
> >> Note : There is on-going ambari mpack which might take some more time.
> Even upgrades will take some time.
> >> 1. https://issues.apache.org/jira/browse/BIGTOP-709
> >> 2. https://issues.apache.org/jira/browse/BIGTOP-3651
> >> Regards,
> >> Brahma Reddy Battula
> >> On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com>
> wrote:
> >> > May be we can name it as bdp-select. Or (bgp-select)
> >> -1 as we already discussed.
> >> On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
> >> > Ok, thanks Viraj.
> >> >
> >> > Hopefully you can place here like all other how it's maintained.
> Let me know any help required on this. May be we can name it as bdp-select.
> Or (bgp-select)
> >> >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> >> >
> >> >
> >> > On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org> wrote:
> >> >
> >> > Masatake, Brahma,
> >> >
> >> > Hopefully I should be able to create Jira and PR in Bigtop.
> Will let you
> >> > know once ready for review. Thanks
> >> >
> >> >
> >> > On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <
> iwasakims@oss.nttdata.com>
> >> > wrote:
> >> >
> >> > > Please file a JIRA and submit a pull request if you want
> to show the code
> >> > > and get feedback.
> >> > > There is nothing I want to discuss off the record.
> >> > >
> >> > > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> >> > > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and
> others, can we get
> >> > > the final conclusion on this..?
> >> > > >
> >> > > > Please let me know your availability, Can have one call
> to discuss on
> >> > > this..
> >> > > >
> >> > > >
> >> > > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy"
> <bb...@visa.com.INVALID>
> >> > > wrote:
> >> > > >
> >> > > > > -1 on development in branch.
> >> > > > > It is not worth for maintaining the branch if
> the modules is
> >> > > so small
> >> > > > > and barely updated as explained here.
> >> > > > > It should not conflict to existing code.
> >> > > > > I feel I must check the code before check-in
> based on this
> >> > > thread.
> >> > > >
> >> > > >
> >> > > > Sure, Viraj or me can show the code to you.
> >> > > >
> >> > > > Can we've call on this Friday/Thrusday if that
> works..?
> >> > > >
> >> > > >
> >> > > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> >> > > iwasakims@oss.nttdata.com> wrote:
> >> > > >
> >> > > > > Sure, we can havemodule name like
> bigtop-distro-select.
> >> > > > > Initially we'll do this separate branch.
> >> > > >
> >> > > > -1 on development in branch.
> >> > > > It is not worth for maintaining the branch if
> the modules is so
> >> > > small
> >> > > > and barely updated as explained here.
> >> > > > It should not conflict to existing code.
> >> > > > I feel I must check the code before check-in
> based on this
> >> > > thread.
> >> > > >
> >> > > > Masatake Iwasaki
> >> > > >
> >> > > > On 2022/07/11 8:23, Kengo Seki wrote:
> >> > > > >> As there are different opinions on this and
> took long time,
> >> > > just to brainstorm all the possibilities and pitfalls.
> >> > > > >
> >> > > > > Oh, I interpreted your words "conclude" and
> "finalize" as you
> >> > > were
> >> > > > > going to make a final decision. Brainstorming
> is welcome, of
> >> > > course.
> >> > > > > (But I'm not so sure if all people concerned
> could join, due
> >> > > to time
> >> > > > > difference and their schedule, etc.)
> >> > > > >
> >> > > > >> Can you suggest, how the changes will be
> also.. like folder,
> >> > > where you suggest to keep this...?
> >> > > > >
> >> > > > > Sure, here's my proposal:
> >> > > > >
> >> > > > > * Stack name: "BIGTOP"
> >> > > > >
> >> > > > > - The same name as the existing one [1]
> >> > > > > - Because it deploys the packages
> generated by Bigtop
> >> > > > > - The existing stack should be replaced
> with it, because
> >> > > that is
> >> > > > > based on Bigtop 0.8 and too old to use now
> >> > > > > - No concern about infringing others'
> trademark
> >> > > > >
> >> > > > > * Component/folder name: "bigtop-select"
> >> > > > >
> >> > > > > - Consistent naming convention with the
> existing tools
> >> > > such as
> >> > > > > "bigtop-groovy", "bigtop-jsvc",
> "bigtop-utils" [2]
> >> > > > > - If it sounds too simple and a bit
> unclear, a more
> >> > > descriptive name
> >> > > > > might be an option, for example
> "bigtop-ambari-stack-selector"
> >> > > > >
> >> > > > > * Script name: "bigtop-select"
> >> > > > >
> >> > > > > - Consistent with the stack name
> >> > > > > - No concern about infringing others'
> trademark
> >> > > > >
> >> > > > > [1]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
> >> > > > > [2]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> >> > > > >
> >> > > > > Kengo Seki <se...@apache.org>
> >> > > > >
> >> > > > > On Mon, Jul 11, 2022 at 3:19 AM Battula,
> Brahma Reddy
> >> > > > > <bb...@visa.com.invalid> wrote:
> >> > > > >>
> >> > > > >>> Technical decisions shouldn't be done on
> other places
> >> > > than public mailing lists,
> >> > > > >>> as described in the "Open Communications"
> section of [1]
> >> > > and [2].
> >> > > > >> > So we should conclude the discussion in
> this mailing
> >> > > list.
> >> > > > >> > (And with my poor English, I'm not so
> confident to catch
> >> > > up with your
> >> > > > >> > fluent talk ;)
> >> > > > >>
> >> > > > >> I believe , I knew the apache way which you
> mentioned. We
> >> > > are not going conclude anything which comes to bigtop
> other than this
> >> > > mailing list.
> >> > > > >> As there are different opinions on this and
> took long time,
> >> > > just to brainstorm all the possibilities and pitfalls.
> Hence asking let's
> >> > > have call so that we can brainstorm. Even after call,
> everything will be
> >> > > published what we discussed.
> >> > > > >>
> >> > > > >> I think, whiteboarding will help to catch up
> with you.
> >> > > > >>
> >> > > > >> You all the think "bigtop-select" will be
> best option
> >> > > right..? Can you suggest, how the changes will be also..
> like folder, where
> >> > > you suggest to keep this...?
> >> > > > >>
> >> > > > >> And if the name represents the stack which
> we are going to
> >> > > deploy should fine I feel.. (if it's not BDP, may be
> >> > > OBDP:OpensourceBigDataPlatform.)
> >> > > > >>
> >> > > > >> @Viraj Jasani and others any thoughts..?
> >> > > > >>
> >> > > > >>
> >> > > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <
> sekikn@apache.org>
> >> > > wrote:
> >> > > > >>
> >> > > > >> > Looks we had so much discussed here,
> Let's try to
> >> > > conclude. Can we've one call on this and finalize this..?
> >> > > > >>
> >> > > > >> Technical decisions shouldn't be done
> on other places
> >> > > than public mailing lists,
> >> > > > >> as described in the "Open
> Communications" section of
> >> > > [1] and [2].
> >> > > > >> So we should conclude the discussion in
> this mailing
> >> > > list.
> >> > > > >> (And with my poor English, I'm not so
> confident to
> >> > > catch up with your
> >> > > > >> fluent talk ;)
> >> > > > >>
> >> > > > >> > FYI. Even looks bigtop used some
> where also..
> >> > > > >>
> >> > > > >> Bigtop is ASF's trademark as you can
> see in the "Apache
> >> > > Bigtop®
> >> > > > >> software" section of [3].
> >> > > > >> So it doesn't have the risk of
> trademark infringement.
> >> > > > >>
> >> > > > >> [1]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
> >> > > > >> [2]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
> >> > > > >> [3]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
> >> > > > >>
> >> > > > >> Kengo Seki <se...@apache.org>
> >> > > > >>
> >> > > > >> On Sun, Jul 10, 2022 at 4:11 AM
> Battula, Brahma Reddy
> >> > > > >> <bb...@visa.com.invalid> wrote:
> >> > > > >> >
> >> > > > >> > Looks we had so much discussed here,
> Let's try to
> >> > > conclude. Can we've one call on this and finalize this..?
> >> > > > >> >
> >> > > > >> > FYI. Even looks bigtop used some
> where[1] also..
> >> > > > >> > 1.
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
> >> > > > >> >
> >> > > > >> >
> >> > > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <
> sekikn@apache.org>
> >> > > wrote:
> >> > > > >> >
> >> > > > >> > Thank you for your explanation,
> Brahma.
> >> > > > >> > CRH (abbreviation of "CHINA
> REDOOP HYPERLOOP"
> >> > > [1]) is supposed to be a
> >> > > > >> > trademark of Redoop, so they can
> name the script
> >> > > crh-select without
> >> > > > >> > problem.
> >> > > > >> > But regarding BDP for example, I
> can easily find
> >> > > products that have
> >> > > > >> > the same name [2][3][4] as you
> already mentioned,
> >> > > so I'd like to
> >> > > > >> > recommend bigtop-select for
> avoiding unnecessary
> >> > > trouble.
> >> > > > >> > Or, a single and more general
> word just like
> >> > > conf-select may be less
> >> > > > >> > troublesome than bdp. How about
> "stack-select",
> >> > > for example?
> >> > > > >> >
> >> > > > >> > [1]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
> >> > > > >> > [2]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
> >> > > > >> > [3]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
> >> > > > >> > [4]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
> >> > > > >> >
> >> > > > >> > Kengo Seki <se...@apache.org>
> >> > > > >> >
> >> > > > >> > On Fri, Jul 8, 2022 at 2:51 AM
> Battula, Brahma
> >> > > Reddy <bb...@visa.com> wrote:
> >> > > > >> > >
> >> > > > >> > > >Do you mean that you're
> going to name the
> >> > > module (same as "component"
> >> > > > >> > > >in the Bigtop terminology,
> I think)
> >> > > bigtop-distro-select,
> >> > > > >> > > >and still the script in
> question
> >> > > bdp-select? If so, is there any
> >> > > > >> > > >reason that the script
> must be that name?
> >> > > > >> > > >(No offence, I just want
> to understand
> >> > > your thoughts and its
> >> > > > >> > > >background, and avoid the
> conflict or
> >> > > user's confusion with existing
> >> > > > >> > > >trademarks or products)
> >> > > > >> > >
> >> > > > >> > > Thanks @Kengo Seki for
> consolidating all the
> >> > > concerns. Name should represent the stack which includes
> all the components
> >> > > hence planning to have like bdp,bds...and this only one
> file like below[1]
> >> > > which has done redoop.
> >> > > > >> > >
> >> > > > >> > >
> >> > > > >> > >
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
> >> > > > >> > >
> >> > > > >> > >
> >> > > > >> > > On 07/07/22, 6:07 AM, "Kengo
> Seki" <
> >> > > sekikn@apache.org> wrote:
> >> > > > >> > >
> >> > > > >> > > The following concern
> Masatake mentioned
> >> > > before is an important point,
> >> > > > >> > > so I talked to Brahma for
> clarifying his
> >> > > intention on the ASF Slack
> >> > > > >> > > yesterday.
> >> > > > >> > >
> >> > > > >> > > > Multiple versions of the
> same package
> >> > > (deb/rpm) can not be installed at the same time.
> >> > > > >> > > > IIRC, HDP uses convention
> in which the
> >> > > product version is part of package name
> >> > > > >> > > > for addressing this.
> >> > > > >> > >
> >> > > > >> > > > I don't like to bring the
> awkward package
> >> > > name convention to Bigtop
> >> > > > >> > > > at least by default.
> >> > > > >> > >
> >> > > > >> > > He's planning to adopt the
> same mitigation
> >> > > as HDP for now, but he
> >> > > > >> > > doesn't intend to change
> the default
> >> > > package naming convention of
> >> > > > >> > > Bigtop,
> >> > > > >> > > but just add a new
> functionality to include
> >> > > an extra part into the
> >> > > > >> > > package name for avoiding
> conflict, which
> >> > > is disabled by default.
> >> > > > >> > >
> >> > > > >> > > And Brahma, let me confirm
> about the
> >> > > following reply:
> >> > > > >> > >
> >> > > > >> > > > Sure, we can have module
> name like
> >> > > bigtop-distro-select.
> >> > > > >> > >
> >> > > > >> > > Do you mean that you're
> going to name the
> >> > > module (same as "component"
> >> > > > >> > > in the Bigtop terminology,
> I think)
> >> > > bigtop-distro-select,
> >> > > > >> > > and still the script in
> question
> >> > > bdp-select? If so, is there any
> >> > > > >> > > reason that the script must
> be that name?
> >> > > > >> > > (No offence, I just want to
> understand your
> >> > > thoughts and its
> >> > > > >> > > background, and avoid the
> conflict or
> >> > > user's confusion with existing
> >> > > > >> > > trademarks or products)
> >> > > > >> > >
> >> > > > >> > > Kengo Seki <
> sekikn@apache.org>
> >> > > > >> > >
> >> > > > >> > > On Thu, Jul 7, 2022 at 2:08
> AM Battula,
> >> > > Brahma Reddy
> >> > > > >> > > <bb...@visa.com.invalid>
> wrote:
> >> > > > >> > > >
> >> > > > >> > > > > The name of stack
> based no Bigtop
> >> > > should be Bigtop.
> >> > > > >> > > > > If you can not
> accept the name like
> >> > > bigtop-*, the work should done outside of Bigtop.
> >> > > > >> > > > > I will cast -1 if
> someone submit a
> >> > > patch to add a module with the name spoiling branding.
> >> > > > >> > > >
> >> > > > >> > > > Sure, we can have module
> name like
> >> > > bigtop-distro-select.
> >> > > > >> > > > Initially we'll do this
> separate branch.
> >> > > > >> > > >
> >> > > > >> > > >
> >> > > > >> > > >
> >> > > > >> > > > On 06/07/22, 8:55 AM,
> "Masatake Iwasaki" <
> >> > > iwasakims@oss.nttdata.co.jp> wrote:
> >> > > > >> > > >
> >> > > > >> > > > > I believe it's for
> project name.
> >> > > isn't it.?
> >> > > > >> > > >
> >> > > > >> > > > projects and products.
> >> > > > >> > > >
> >> > > > >> > > > > IMO, We need to
> create folders and
> >> > > refer stacknames so ambari-select,bigtop-select wn't looks
> good.
> >> > > > >> > > >
> >> > > > >> > > > The name of stack
> based no Bigtop
> >> > > should be Bigtop.
> >> > > > >> > > > If you can not accept
> the name like
> >> > > bigtop-*, the work should done outside of Bigtop.
> >> > > > >> > > > I will cast -1 if
> someone submit a
> >> > > patch to add a module with the name spoiling branding.
> >> > > > >> > > >
> >> > > > >> > > >
> >> > > > >> > > > On 2022/07/06 11:44,
> Battula, Brahma
> >> > > Reddy wrote:
> >> > > > >> > > > >
> >> > > > >> > > > > I believe it's for
> project name.
> >> > > isn't it.?
> >> > > > >> > > > >
> >> > > > >> > > > >
> >> > > > >> > > > > On 06/07/22, 7:27
> AM, "Masatake
> >> > > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >> > > > >> > > > >
> >> > > > >> > > > > > But As we
> are not releasing
> >> > > as enterprise should be fine I think. IMO, We need to
> create folders and
> >> > > refer stacknames so ambari-select,bigtop-select wn't looks
> good.
> >> > > > >> > > > >
> >> > > > >> > > > > Not fine.
> >> > > > >> > > > > We have a
> trademark policy.
> >> > > > >> > > > >
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
> >> > > > >> > > > >
> >> > > > >> > > > > On 2022/07/06
> 10:37, Battula,
> >> > > Brahma Reddy wrote:
> >> > > > >> > > > > >> Should we
> avoid
> >> > > unrecognized brand which may be trademark of someone?
> >> > > > >> > > > > >>
> ambari-select or
> >> > > bigtop-select should be enough.
> >> > > > >> > > > > >
> >> > > > >> > > > > > Not sure,
> where to confirm
> >> > > whether there is already trademark. When I googled found
> so many.
> >> > > > >> > > > > > But As we
> are not releasing
> >> > > as enterprise should be fine I think. IMO, We need to
> create folders and
> >> > > refer stacknames so ambari-select,bigtop-select wn't looks
> good.
> >> > > > >> > > > > > May be you
> can refer the
> >> > > initial proposal [2] where I mentioned some more names.
> >> > > (BDS-BigDataStack,OSS-OpenSourceSelect..)
> >> > > > >> > > > > >
> >> > > > >> > > > > > Finally
> thanks a bunch for
> >> > > long healthy discussions on this. Mostly we all same page
> now.
> >> > > > >> > > > > >
> >> > > > >> > > > > > 1.
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
> >> > > > >> > > > > >
> >> > > > >> > > > > > 2.
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
> >> > > > >> > > > > >
> >> > > > >> > > > > >
> >> > > > >> > > > > > On 06/07/22,
> 4:01 AM,
> >> > > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >> > > > >> > > > > >
> >> > > > >> > > > > > > We
> have still not
> >> > > officially finalized the new replacement name for
> >> > > > >> > > > > > >
> hdp-select, it would
> >> > > likely be bdp-select (bdp: BigData Platform). However,
> >> > > > >> > > > > > > the
> purpose of
> >> > > bdp-select and conf-select remains the same.
> >> > > > >> > > > > >
> >> > > > >> > > > > > Should
> we avoid
> >> > > unrecognized brand which may be trademark of someone?
> >> > > > >> > > > > >
> ambari-select or
> >> > > bigtop-select should be enough.
> >> > > > >> > > > > >
> >> > > > >> > > > > > On
> 2022/06/29 13:52,
> >> > > Viraj Jasani wrote:
> >> > > > >> > > > > > > Hi
> Ambari/Bigtop dev,
> >> > > > >> > > > > > >
> >> > > > >> > > > > > > As
> per the new
> >> > > roadmap of Apache Ambari, we would like to propose moving
> >> > > > >> > > > > > >
> certain scripts
> >> > > (previously known as hdp-select and conf-select) to Bigtop
> >> > > > >> > > > > > > so
> that their rpm
> >> > > installation could be managed independently.
> >> > > > >> > > > > > > These
> scripts are a
> >> > > basic necessity in the Ambari framework for the
> >> > > > >> > > > > > >
> installation of
> >> > > various Bigdata packages. The only major changes they would
> >> > > > >> > > > > > >
> receive is when we
> >> > > onboard new services and components to Ambari, else they
> >> > > > >> > > > > > >
> usually do not
> >> > > receive updates. In the past, we used to get hdp-select rpm
> >> > > > >> > > > > > >
> downloaded and
> >> > > installed from HDP repositories.
> >> > > > >> > > > > > >
> >> > > > >> > > > > > > We
> have still not
> >> > > officially finalized the new replacement name for
> >> > > > >> > > > > > >
> hdp-select, it would
> >> > > likely be bdp-select (bdp: BigData Platform). However,
> >> > > > >> > > > > > > the
> purpose of
> >> > > bdp-select and conf-select remains the same.
> >> > > > >> > > > > > >
> >> > > > >> > > > > >
> >> > > > >> > > > >
> >> > > > >> > > >
> >> > > > >> > > >
> >> > > > >> > > >
> >> > >
> ---------------------------------------------------------------------
> >> > > > >> > > > To unsubscribe, e-mail:
> >> > > dev-unsubscribe@ambari.apache.org
> >> > > > >> > > > For additional commands,
> e-mail:
> >> > > dev-help@ambari.apache.org
> >> > > > >> > > >
> >> > > > >> > >
> >> > > > >> > >
> >> > >
> ---------------------------------------------------------------------
> >> > > > >> > > To unsubscribe, e-mail:
> >> > > dev-unsubscribe@ambari.apache.org
> >> > > > >> > > For additional commands,
> e-mail:
> >> > > dev-help@ambari.apache.org
> >> > > > >> > >
> >> > > > >> > >
> >> > > > >> >
> >> > > > >> >
> >> > >
> ---------------------------------------------------------------------
> >> > > > >> > To unsubscribe, e-mail:
> >> > > dev-unsubscribe@ambari.apache.org
> >> > > > >> > For additional commands, e-mail:
> >> > > dev-help@ambari.apache.org
> >> > > > >> >
> >> > > > >> >
> >> > > > >>
> >> > > > >>
> >> > >
> ---------------------------------------------------------------------
> >> > > > >> To unsubscribe, e-mail:
> >> > > dev-unsubscribe@ambari.apache.org
> >> > > > >> For additional commands, e-mail:
> >> > > dev-help@ambari.apache.org
> >> > > > >>
> >> > > > >>
> >> > > >
> >> > > >
> >> > > >
> >> > >
> ---------------------------------------------------------------------
> >> > > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> >> > > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> >> > > >
> >> > > >
> >> > >
> >> >
> >> >
> >> >
> ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> > For additional commands, e-mail: dev-help@ambari.apache.org
> >> >
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> For additional commands, e-mail: dev-help@ambari.apache.org
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> For additional commands, e-mail: dev-help@ambari.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Brahma Reddy Battula <br...@apache.org>.
FYKI, bigtop stack already merged to Ambari.
And if you are thinking about another stack-select ,I am waiting for
Roman’s opinion.
On Mon, 26 Sep 2022 at 6:15 AM, Masatake Iwasaki <iw...@oss.nttdata.com>
wrote:
> > IMHO, Bigtop stack mpack was planned for trunk only. It could even merge
> > with a separate branch till it's stable.
>
> -1 on managing branch as we have already discussed:
>
> On 2022/07/24 5:01, Battula, Brahma Reddy wrote:
> >> -1 on development in branch.
> > > It is not worth for maintaining the branch if the modules is so
> small
> > > and barely updated as explained here.
> > > It should not conflict to existing code.
> > > I feel I must check the code before check-in based on this thread.
> >
> >
> > Sure, Viraj or me can show the code to you.
>
> On 2022/09/26 2:29, Brahma Reddy Battula wrote:
> > IMHO, Bigtop stack mpack was planned for trunk only. It could even merge
> > with a separate branch till it's stable.
> >
> > On Thu, Sep 22, 2022 at 5:02 PM Masatake Iwasaki <
> iwasakims@oss.nttdata.com>
> > wrote:
> >
> >> +1
> >>
> >> On 2022/09/21 11:12, 吴治国 wrote:
> >>> I think we have enough to go on with Kengo’s proposal,
> >>> Currently we don’t have enough developers(and I’m not willing to) to
> >> maintain a stack on our own like BDP.
> >>>
> >>>> Sure, here's my proposal:
> >>>>
> >>>> * Stack name: "BIGTOP"
> >>>>
> >>>> - The same name as the existing one [1]
> >>>> - Because it deploys the packages generated by Bigtop
> >>>> - The existing stack should be replaced with it, because that is
> >>>> based on Bigtop 0.8 and too old to use now
> >>>> - No concern about infringing others' trademark
> >>>>
> >>>> * Component/folder name: "bigtop-select"
> >>>>
> >>>> - Consistent naming convention with the existing tools such as
> >>>> "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> >>>> - If it sounds too simple and a bit unclear, a more descriptive
> name
> >>>> might be an option, for example "bigtop-ambari-stack-selector"
> >>>>
> >>>> * Script name: "bigtop-select"
> >>>>
> >>>> - Consistent with the stack name
> >>>> - No concern about infringing others' trademark
> >>>>
> >>>> [1]:
> >>
> https://github.com/apache/ambari/tree/release-2.7.6/ambari-server/src/main/resources/stacks/BIGTOP/0.8
> >>>> [2]:
> >> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common
> <
> >> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common
> >
> >>>
> >>> Best Regards,
> >>> Zhiguo Wu
> >>>
> >>>> On Sep 16, 2022, at 08:44, Masatake Iwasaki <
> iwasakims@oss.nttdata.com>
> >> wrote:
> >>>>
> >>>>
> >>>>>>> May be we can name it as bdp-select. Or (bgp-select)
> >>>>>> -1 as we already discussed.
> >>>>> Thanks for your feedback, I would definitely honour it. As you are
> not
> >> open for discussion and asked us raise the PR hence you thought of
> >> discussing on the PR. What will be your final suggestion on this..?
> >>>>
> >>>> I'm -1 on the name like bdp-select or bgp-select as we discussed.
> >>>> Feel free to open PR with appropriate module name.
> >>>>
> >>>> On 2022/09/05 16:30, Battula, Brahma Reddy wrote:
> >>>>> Hi @Masatake Iwasaki,
> >>>>>> -1 as we already discussed.
> >>>>> Thanks for your feedback, I would definitely honour it. As you are
> not
> >> open for discussion and asked us raise the PR hence you thought of
> >> discussing on the PR. What will be your final suggestion on this..?
> >>>>> @Roman Shaposhnik
> >>>>> I just gone through the following jira[1] where you brought ambari to
> >> bigtop. Looks stack-select is not included, how it was maintained.?
> >>>>> I thinking we should have one stack which can support for upgrading
> >> the existing the HDP deployed clusters. Even I can see somebody asking
> on
> >> bigtop[2].
> >>>>> If bigtop is not right place, shall we include in ambari..? Please
> >> let me know your thoughts on this. This blocks the 2.7.7 release.
> >>>>> Note : There is on-going ambari mpack which might take some more
> >> time. Even upgrades will take some time.
> >>>>> 1. https://issues.apache.org/jira/browse/BIGTOP-709
> >>>>> 2. https://issues.apache.org/jira/browse/BIGTOP-3651
> >>>>> Regards,
> >>>>> Brahma Reddy Battula
> >>>>> On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iwasakims@oss.nttdata.com
> >
> >> wrote:
> >>>>> > May be we can name it as bdp-select. Or (bgp-select)
> >>>>> -1 as we already discussed.
> >>>>> On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
> >>>>> > Ok, thanks Viraj.
> >>>>> >
> >>>>> > Hopefully you can place here like all other how it's
> >> maintained. Let me know any help required on this. May be we can name
> it as
> >> bdp-select. Or (bgp-select)
> >>>>> >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> >>>>> >
> >>>>> >
> >>>>> > On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org>
> >> wrote:
> >>>>> >
> >>>>> > Masatake, Brahma,
> >>>>> >
> >>>>> > Hopefully I should be able to create Jira and PR in
> >> Bigtop. Will let you
> >>>>> > know once ready for review. Thanks
> >>>>> >
> >>>>> >
> >>>>> > On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <
> >> iwasakims@oss.nttdata.com>
> >>>>> > wrote:
> >>>>> >
> >>>>> > > Please file a JIRA and submit a pull request if you
> want
> >> to show the code
> >>>>> > > and get feedback.
> >>>>> > > There is nothing I want to discuss off the record.
> >>>>> > >
> >>>>> > > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> >>>>> > > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and
> >> others, can we get
> >>>>> > > the final conclusion on this..?
> >>>>> > > >
> >>>>> > > > Please let me know your availability, Can have one
> >> call to discuss on
> >>>>> > > this..
> >>>>> > > >
> >>>>> > > >
> >>>>> > > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy"
> >> <bb...@visa.com.INVALID>
> >>>>> > > wrote:
> >>>>> > > >
> >>>>> > > > > -1 on development in branch.
> >>>>> > > > > It is not worth for maintaining the branch
> >> if the modules is
> >>>>> > > so small
> >>>>> > > > > and barely updated as explained here.
> >>>>> > > > > It should not conflict to existing code.
> >>>>> > > > > I feel I must check the code before
> >> check-in based on this
> >>>>> > > thread.
> >>>>> > > >
> >>>>> > > >
> >>>>> > > > Sure, Viraj or me can show the code to you.
> >>>>> > > >
> >>>>> > > > Can we've call on this Friday/Thrusday if that
> >> works..?
> >>>>> > > >
> >>>>> > > >
> >>>>> > > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> >>>>> > > iwasakims@oss.nttdata.com> wrote:
> >>>>> > > >
> >>>>> > > > > Sure, we can havemodule name like
> >> bigtop-distro-select.
> >>>>> > > > > Initially we'll do this separate branch.
> >>>>> > > >
> >>>>> > > > -1 on development in branch.
> >>>>> > > > It is not worth for maintaining the branch
> if
> >> the modules is so
> >>>>> > > small
> >>>>> > > > and barely updated as explained here.
> >>>>> > > > It should not conflict to existing code.
> >>>>> > > > I feel I must check the code before
> check-in
> >> based on this
> >>>>> > > thread.
> >>>>> > > >
> >>>>> > > > Masatake Iwasaki
> >>>>> > > >
> >>>>> > > > On 2022/07/11 8:23, Kengo Seki wrote:
> >>>>> > > > >> As there are different opinions on this
> >> and took long time,
> >>>>> > > just to brainstorm all the possibilities and pitfalls.
> >>>>> > > > >
> >>>>> > > > > Oh, I interpreted your words "conclude"
> and
> >> "finalize" as you
> >>>>> > > were
> >>>>> > > > > going to make a final decision.
> >> Brainstorming is welcome, of
> >>>>> > > course.
> >>>>> > > > > (But I'm not so sure if all people
> >> concerned could join, due
> >>>>> > > to time
> >>>>> > > > > difference and their schedule, etc.)
> >>>>> > > > >
> >>>>> > > > >> Can you suggest, how the changes will be
> >> also.. like folder,
> >>>>> > > where you suggest to keep this...?
> >>>>> > > > >
> >>>>> > > > > Sure, here's my proposal:
> >>>>> > > > >
> >>>>> > > > > * Stack name: "BIGTOP"
> >>>>> > > > >
> >>>>> > > > > - The same name as the existing one
> [1]
> >>>>> > > > > - Because it deploys the packages
> >> generated by Bigtop
> >>>>> > > > > - The existing stack should be
> replaced
> >> with it, because
> >>>>> > > that is
> >>>>> > > > > based on Bigtop 0.8 and too old to use
> now
> >>>>> > > > > - No concern about infringing others'
> >> trademark
> >>>>> > > > >
> >>>>> > > > > * Component/folder name: "bigtop-select"
> >>>>> > > > >
> >>>>> > > > > - Consistent naming convention with
> the
> >> existing tools
> >>>>> > > such as
> >>>>> > > > > "bigtop-groovy", "bigtop-jsvc",
> >> "bigtop-utils" [2]
> >>>>> > > > > - If it sounds too simple and a bit
> >> unclear, a more
> >>>>> > > descriptive name
> >>>>> > > > > might be an option, for example
> >> "bigtop-ambari-stack-selector"
> >>>>> > > > >
> >>>>> > > > > * Script name: "bigtop-select"
> >>>>> > > > >
> >>>>> > > > > - Consistent with the stack name
> >>>>> > > > > - No concern about infringing others'
> >> trademark
> >>>>> > > > >
> >>>>> > > > > [1]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
> >>>>> > > > > [2]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> >>>>> > > > >
> >>>>> > > > > Kengo Seki <se...@apache.org>
> >>>>> > > > >
> >>>>> > > > > On Mon, Jul 11, 2022 at 3:19 AM Battula,
> >> Brahma Reddy
> >>>>> > > > > <bb...@visa.com.invalid> wrote:
> >>>>> > > > >>
> >>>>> > > > >>> Technical decisions shouldn't be done
> >> on other places
> >>>>> > > than public mailing lists,
> >>>>> > > > >>> as described in the "Open
> >> Communications" section of [1]
> >>>>> > > and [2].
> >>>>> > > > >> > So we should conclude the discussion
> >> in this mailing
> >>>>> > > list.
> >>>>> > > > >> > (And with my poor English, I'm not
> so
> >> confident to catch
> >>>>> > > up with your
> >>>>> > > > >> > fluent talk ;)
> >>>>> > > > >>
> >>>>> > > > >> I believe , I knew the apache way which
> >> you mentioned. We
> >>>>> > > are not going conclude anything which comes to bigtop
> >> other than this
> >>>>> > > mailing list.
> >>>>> > > > >> As there are different opinions on this
> >> and took long time,
> >>>>> > > just to brainstorm all the possibilities and pitfalls.
> >> Hence asking let's
> >>>>> > > have call so that we can brainstorm. Even after call,
> >> everything will be
> >>>>> > > published what we discussed.
> >>>>> > > > >>
> >>>>> > > > >> I think, whiteboarding will help to
> catch
> >> up with you.
> >>>>> > > > >>
> >>>>> > > > >> You all the think "bigtop-select" will
> be
> >> best option
> >>>>> > > right..? Can you suggest, how the changes will be
> also..
> >> like folder, where
> >>>>> > > you suggest to keep this...?
> >>>>> > > > >>
> >>>>> > > > >> And if the name represents the stack
> which
> >> we are going to
> >>>>> > > deploy should fine I feel.. (if it's not BDP, may be
> >>>>> > > OBDP:OpensourceBigDataPlatform.)
> >>>>> > > > >>
> >>>>> > > > >> @Viraj Jasani and others any thoughts..?
> >>>>> > > > >>
> >>>>> > > > >>
> >>>>> > > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <
> >> sekikn@apache.org>
> >>>>> > > wrote:
> >>>>> > > > >>
> >>>>> > > > >> > Looks we had so much discussed
> >> here, Let's try to
> >>>>> > > conclude. Can we've one call on this and finalize
> this..?
> >>>>> > > > >>
> >>>>> > > > >> Technical decisions shouldn't be
> done
> >> on other places
> >>>>> > > than public mailing lists,
> >>>>> > > > >> as described in the "Open
> >> Communications" section of
> >>>>> > > [1] and [2].
> >>>>> > > > >> So we should conclude the
> discussion
> >> in this mailing
> >>>>> > > list.
> >>>>> > > > >> (And with my poor English, I'm not
> so
> >> confident to
> >>>>> > > catch up with your
> >>>>> > > > >> fluent talk ;)
> >>>>> > > > >>
> >>>>> > > > >> > FYI. Even looks bigtop used some
> >> where also..
> >>>>> > > > >>
> >>>>> > > > >> Bigtop is ASF's trademark as you
> can
> >> see in the "Apache
> >>>>> > > Bigtop®
> >>>>> > > > >> software" section of [3].
> >>>>> > > > >> So it doesn't have the risk of
> >> trademark infringement.
> >>>>> > > > >>
> >>>>> > > > >> [1]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
> >>>>> > > > >> [2]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
> >>>>> > > > >> [3]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
> >>>>> > > > >>
> >>>>> > > > >> Kengo Seki <se...@apache.org>
> >>>>> > > > >>
> >>>>> > > > >> On Sun, Jul 10, 2022 at 4:11 AM
> >> Battula, Brahma Reddy
> >>>>> > > > >> <bb...@visa.com.invalid> wrote:
> >>>>> > > > >> >
> >>>>> > > > >> > Looks we had so much discussed
> >> here, Let's try to
> >>>>> > > conclude. Can we've one call on this and finalize
> this..?
> >>>>> > > > >> >
> >>>>> > > > >> > FYI. Even looks bigtop used some
> >> where[1] also..
> >>>>> > > > >> > 1.
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
> >>>>> > > > >> >
> >>>>> > > > >> >
> >>>>> > > > >> > On 08/07/22, 8:06 PM, "Kengo
> Seki" <
> >> sekikn@apache.org>
> >>>>> > > wrote:
> >>>>> > > > >> >
> >>>>> > > > >> > Thank you for your
> explanation,
> >> Brahma.
> >>>>> > > > >> > CRH (abbreviation of "CHINA
> >> REDOOP HYPERLOOP"
> >>>>> > > [1]) is supposed to be a
> >>>>> > > > >> > trademark of Redoop, so they
> >> can name the script
> >>>>> > > crh-select without
> >>>>> > > > >> > problem.
> >>>>> > > > >> > But regarding BDP for
> example,
> >> I can easily find
> >>>>> > > products that have
> >>>>> > > > >> > the same name [2][3][4] as
> you
> >> already mentioned,
> >>>>> > > so I'd like to
> >>>>> > > > >> > recommend bigtop-select for
> >> avoiding unnecessary
> >>>>> > > trouble.
> >>>>> > > > >> > Or, a single and more general
> >> word just like
> >>>>> > > conf-select may be less
> >>>>> > > > >> > troublesome than bdp. How
> about
> >> "stack-select",
> >>>>> > > for example?
> >>>>> > > > >> >
> >>>>> > > > >> > [1]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
> >>>>> > > > >> > [2]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
> >>>>> > > > >> > [3]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
> >>>>> > > > >> > [4]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
> >>>>> > > > >> >
> >>>>> > > > >> > Kengo Seki <
> sekikn@apache.org>
> >>>>> > > > >> >
> >>>>> > > > >> > On Fri, Jul 8, 2022 at 2:51
> AM
> >> Battula, Brahma
> >>>>> > > Reddy <bb...@visa.com> wrote:
> >>>>> > > > >> > >
> >>>>> > > > >> > > >Do you mean that
> you're
> >> going to name the
> >>>>> > > module (same as "component"
> >>>>> > > > >> > > >in the Bigtop
> >> terminology, I think)
> >>>>> > > bigtop-distro-select,
> >>>>> > > > >> > > >and still the script
> in
> >> question
> >>>>> > > bdp-select? If so, is there any
> >>>>> > > > >> > > >reason that the script
> >> must be that name?
> >>>>> > > > >> > > >(No offence, I just
> want
> >> to understand
> >>>>> > > your thoughts and its
> >>>>> > > > >> > > >background, and avoid
> >> the conflict or
> >>>>> > > user's confusion with existing
> >>>>> > > > >> > > >trademarks or
> products)
> >>>>> > > > >> > >
> >>>>> > > > >> > > Thanks @Kengo Seki for
> >> consolidating all the
> >>>>> > > concerns. Name should represent the stack which
> includes
> >> all the components
> >>>>> > > hence planning to have like bdp,bds...and this only
> one
> >> file like below[1]
> >>>>> > > which has done redoop.
> >>>>> > > > >> > >
> >>>>> > > > >> > >
> >>>>> > > > >> > >
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
> >>>>> > > > >> > >
> >>>>> > > > >> > >
> >>>>> > > > >> > > On 07/07/22, 6:07 AM,
> "Kengo
> >> Seki" <
> >>>>> > > sekikn@apache.org> wrote:
> >>>>> > > > >> > >
> >>>>> > > > >> > > The following concern
> >> Masatake mentioned
> >>>>> > > before is an important point,
> >>>>> > > > >> > > so I talked to Brahma
> for
> >> clarifying his
> >>>>> > > intention on the ASF Slack
> >>>>> > > > >> > > yesterday.
> >>>>> > > > >> > >
> >>>>> > > > >> > > > Multiple versions of
> >> the same package
> >>>>> > > (deb/rpm) can not be installed at the same time.
> >>>>> > > > >> > > > IIRC, HDP uses
> >> convention in which the
> >>>>> > > product version is part of package name
> >>>>> > > > >> > > > for addressing this.
> >>>>> > > > >> > >
> >>>>> > > > >> > > > I don't like to bring
> >> the awkward package
> >>>>> > > name convention to Bigtop
> >>>>> > > > >> > > > at least by default.
> >>>>> > > > >> > >
> >>>>> > > > >> > > He's planning to adopt
> >> the same mitigation
> >>>>> > > as HDP for now, but he
> >>>>> > > > >> > > doesn't intend to
> change
> >> the default
> >>>>> > > package naming convention of
> >>>>> > > > >> > > Bigtop,
> >>>>> > > > >> > > but just add a new
> >> functionality to include
> >>>>> > > an extra part into the
> >>>>> > > > >> > > package name for
> avoiding
> >> conflict, which
> >>>>> > > is disabled by default.
> >>>>> > > > >> > >
> >>>>> > > > >> > > And Brahma, let me
> >> confirm about the
> >>>>> > > following reply:
> >>>>> > > > >> > >
> >>>>> > > > >> > > > Sure, we can have
> >> module name like
> >>>>> > > bigtop-distro-select.
> >>>>> > > > >> > >
> >>>>> > > > >> > > Do you mean that you're
> >> going to name the
> >>>>> > > module (same as "component"
> >>>>> > > > >> > > in the Bigtop
> >> terminology, I think)
> >>>>> > > bigtop-distro-select,
> >>>>> > > > >> > > and still the script in
> >> question
> >>>>> > > bdp-select? If so, is there any
> >>>>> > > > >> > > reason that the script
> >> must be that name?
> >>>>> > > > >> > > (No offence, I just
> want
> >> to understand your
> >>>>> > > thoughts and its
> >>>>> > > > >> > > background, and avoid
> the
> >> conflict or
> >>>>> > > user's confusion with existing
> >>>>> > > > >> > > trademarks or products)
> >>>>> > > > >> > >
> >>>>> > > > >> > > Kengo Seki <
> >> sekikn@apache.org>
> >>>>> > > > >> > >
> >>>>> > > > >> > > On Thu, Jul 7, 2022 at
> >> 2:08 AM Battula,
> >>>>> > > Brahma Reddy
> >>>>> > > > >> > >
> <bb...@visa.com.invalid>
> >> wrote:
> >>>>> > > > >> > > >
> >>>>> > > > >> > > > > The name of stack
> >> based no Bigtop
> >>>>> > > should be Bigtop.
> >>>>> > > > >> > > > > If you can not
> >> accept the name like
> >>>>> > > bigtop-*, the work should done outside of Bigtop.
> >>>>> > > > >> > > > > I will cast -1
> if
> >> someone submit a
> >>>>> > > patch to add a module with the name spoiling branding.
> >>>>> > > > >> > > >
> >>>>> > > > >> > > > Sure, we can have
> >> module name like
> >>>>> > > bigtop-distro-select.
> >>>>> > > > >> > > > Initially we'll do
> this
> >> separate branch.
> >>>>> > > > >> > > >
> >>>>> > > > >> > > >
> >>>>> > > > >> > > >
> >>>>> > > > >> > > > On 06/07/22, 8:55 AM,
> >> "Masatake Iwasaki" <
> >>>>> > > iwasakims@oss.nttdata.co.jp> wrote:
> >>>>> > > > >> > > >
> >>>>> > > > >> > > > > I believe it's
> >> for project name.
> >>>>> > > isn't it.?
> >>>>> > > > >> > > >
> >>>>> > > > >> > > > projects and
> >> products.
> >>>>> > > > >> > > >
> >>>>> > > > >> > > > > IMO, We need to
> >> create folders and
> >>>>> > > refer stacknames so ambari-select,bigtop-select wn't
> >> looks good.
> >>>>> > > > >> > > >
> >>>>> > > > >> > > > The name of stack
> >> based no Bigtop
> >>>>> > > should be Bigtop.
> >>>>> > > > >> > > > If you can not
> >> accept the name like
> >>>>> > > bigtop-*, the work should done outside of Bigtop.
> >>>>> > > > >> > > > I will cast -1 if
> >> someone submit a
> >>>>> > > patch to add a module with the name spoiling branding.
> >>>>> > > > >> > > >
> >>>>> > > > >> > > >
> >>>>> > > > >> > > > On 2022/07/06
> >> 11:44, Battula, Brahma
> >>>>> > > Reddy wrote:
> >>>>> > > > >> > > > >
> >>>>> > > > >> > > > > I believe it's
> >> for project name.
> >>>>> > > isn't it.?
> >>>>> > > > >> > > > >
> >>>>> > > > >> > > > >
> >>>>> > > > >> > > > > On 06/07/22,
> 7:27
> >> AM, "Masatake
> >>>>> > > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >>>>> > > > >> > > > >
> >>>>> > > > >> > > > > > But As
> we
> >> are not releasing
> >>>>> > > as enterprise should be fine I think. IMO, We need to
> >> create folders and
> >>>>> > > refer stacknames so ambari-select,bigtop-select wn't
> >> looks good.
> >>>>> > > > >> > > > >
> >>>>> > > > >> > > > > Not fine.
> >>>>> > > > >> > > > > We have a
> >> trademark policy.
> >>>>> > > > >> > > > >
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
> >>>>> > > > >> > > > >
> >>>>> > > > >> > > > > On
> >> 2022/07/06 10:37, Battula,
> >>>>> > > Brahma Reddy wrote:
> >>>>> > > > >> > > > > >> Should
> we
> >> avoid
> >>>>> > > unrecognized brand which may be trademark of someone?
> >>>>> > > > >> > > > > >>
> >> ambari-select or
> >>>>> > > bigtop-select should be enough.
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > > Not
> sure,
> >> where to confirm
> >>>>> > > whether there is already trademark. When I googled
> found
> >> so many.
> >>>>> > > > >> > > > > > But As
> we
> >> are not releasing
> >>>>> > > as enterprise should be fine I think. IMO, We need to
> >> create folders and
> >>>>> > > refer stacknames so ambari-select,bigtop-select wn't
> >> looks good.
> >>>>> > > > >> > > > > > May be
> you
> >> can refer the
> >>>>> > > initial proposal [2] where I mentioned some more
> names.
> >>>>> > > (BDS-BigDataStack,OSS-OpenSourceSelect..)
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > > Finally
> >> thanks a bunch for
> >>>>> > > long healthy discussions on this. Mostly we all same
> >> page now.
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > > 1.
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > > 2.
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > > On
> >> 06/07/22, 4:01 AM,
> >>>>> > > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp>
> wrote:
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > > >
> We
> >> have still not
> >>>>> > > officially finalized the new replacement name for
> >>>>> > > > >> > > > > > >
> >> hdp-select, it would
> >>>>> > > likely be bdp-select (bdp: BigData Platform). However,
> >>>>> > > > >> > > > > > >
> the
> >> purpose of
> >>>>> > > bdp-select and conf-select remains the same.
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > >
> >> Should we avoid
> >>>>> > > unrecognized brand which may be trademark of someone?
> >>>>> > > > >> > > > > >
> >> ambari-select or
> >>>>> > > bigtop-select should be enough.
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > > On
> >> 2022/06/29 13:52,
> >>>>> > > Viraj Jasani wrote:
> >>>>> > > > >> > > > > > >
> Hi
> >> Ambari/Bigtop dev,
> >>>>> > > > >> > > > > > >
> >>>>> > > > >> > > > > > >
> As
> >> per the new
> >>>>> > > roadmap of Apache Ambari, we would like to propose
> moving
> >>>>> > > > >> > > > > > >
> >> certain scripts
> >>>>> > > (previously known as hdp-select and conf-select) to
> >> Bigtop
> >>>>> > > > >> > > > > > >
> so
> >> that their rpm
> >>>>> > > installation could be managed independently.
> >>>>> > > > >> > > > > > >
> >> These scripts are a
> >>>>> > > basic necessity in the Ambari framework for the
> >>>>> > > > >> > > > > > >
> >> installation of
> >>>>> > > various Bigdata packages. The only major changes they
> >> would
> >>>>> > > > >> > > > > > >
> >> receive is when we
> >>>>> > > onboard new services and components to Ambari, else
> they
> >>>>> > > > >> > > > > > >
> >> usually do not
> >>>>> > > receive updates. In the past, we used to get
> hdp-select
> >> rpm
> >>>>> > > > >> > > > > > >
> >> downloaded and
> >>>>> > > installed from HDP repositories.
> >>>>> > > > >> > > > > > >
> >>>>> > > > >> > > > > > >
> We
> >> have still not
> >>>>> > > officially finalized the new replacement name for
> >>>>> > > > >> > > > > > >
> >> hdp-select, it would
> >>>>> > > likely be bdp-select (bdp: BigData Platform). However,
> >>>>> > > > >> > > > > > >
> the
> >> purpose of
> >>>>> > > bdp-select and conf-select remains the same.
> >>>>> > > > >> > > > > > >
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > >
> >>>>> > > > >> > > >
> >>>>> > > > >> > > >
> >>>>> > > > >> > > >
> >>>>> > >
> >> ---------------------------------------------------------------------
> >>>>> > > > >> > > > To unsubscribe,
> e-mail:
> >>>>> > > dev-unsubscribe@ambari.apache.org
> >>>>> > > > >> > > > For additional
> >> commands, e-mail:
> >>>>> > > dev-help@ambari.apache.org
> >>>>> > > > >> > > >
> >>>>> > > > >> > >
> >>>>> > > > >> > >
> >>>>> > >
> >> ---------------------------------------------------------------------
> >>>>> > > > >> > > To unsubscribe, e-mail:
> >>>>> > > dev-unsubscribe@ambari.apache.org
> >>>>> > > > >> > > For additional
> commands,
> >> e-mail:
> >>>>> > > dev-help@ambari.apache.org
> >>>>> > > > >> > >
> >>>>> > > > >> > >
> >>>>> > > > >> >
> >>>>> > > > >> >
> >>>>> > >
> >> ---------------------------------------------------------------------
> >>>>> > > > >> > To unsubscribe, e-mail:
> >>>>> > > dev-unsubscribe@ambari.apache.org
> >>>>> > > > >> > For additional commands,
> e-mail:
> >>>>> > > dev-help@ambari.apache.org
> >>>>> > > > >> >
> >>>>> > > > >> >
> >>>>> > > > >>
> >>>>> > > > >>
> >>>>> > >
> >> ---------------------------------------------------------------------
> >>>>> > > > >> To unsubscribe, e-mail:
> >>>>> > > dev-unsubscribe@ambari.apache.org
> >>>>> > > > >> For additional commands, e-mail:
> >>>>> > > dev-help@ambari.apache.org
> >>>>> > > > >>
> >>>>> > > > >>
> >>>>> > > >
> >>>>> > > >
> >>>>> > > >
> >>>>> > >
> >> ---------------------------------------------------------------------
> >>>>> > > > To unsubscribe, e-mail:
> >> dev-unsubscribe@ambari.apache.org
> >>>>> > > > For additional commands, e-mail:
> >> dev-help@ambari.apache.org
> >>>>> > > >
> >>>>> > > >
> >>>>> > >
> >>>>> >
> >>>>> >
> >>>>> >
> >> ---------------------------------------------------------------------
> >>>>> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >>>>> > For additional commands, e-mail: dev-help@ambari.apache.org
> >>>>> >
> >>>>>
> >> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >>>>> For additional commands, e-mail: dev-help@ambari.apache.org
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >>>>> For additional commands, e-mail: dev-help@ambari.apache.org
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >>>> For additional commands, e-mail: dev-help@ambari.apache.org
> >>>
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> For additional commands, e-mail: dev-help@ambari.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Brahma Reddy Battula <br...@apache.org>.
FYKI, bigtop stack already merged to Ambari.
And if you are thinking about another stack-select ,I am waiting for
Roman’s opinion.
On Mon, 26 Sep 2022 at 6:15 AM, Masatake Iwasaki <iw...@oss.nttdata.com>
wrote:
> > IMHO, Bigtop stack mpack was planned for trunk only. It could even merge
> > with a separate branch till it's stable.
>
> -1 on managing branch as we have already discussed:
>
> On 2022/07/24 5:01, Battula, Brahma Reddy wrote:
> >> -1 on development in branch.
> > > It is not worth for maintaining the branch if the modules is so
> small
> > > and barely updated as explained here.
> > > It should not conflict to existing code.
> > > I feel I must check the code before check-in based on this thread.
> >
> >
> > Sure, Viraj or me can show the code to you.
>
> On 2022/09/26 2:29, Brahma Reddy Battula wrote:
> > IMHO, Bigtop stack mpack was planned for trunk only. It could even merge
> > with a separate branch till it's stable.
> >
> > On Thu, Sep 22, 2022 at 5:02 PM Masatake Iwasaki <
> iwasakims@oss.nttdata.com>
> > wrote:
> >
> >> +1
> >>
> >> On 2022/09/21 11:12, 吴治国 wrote:
> >>> I think we have enough to go on with Kengo’s proposal,
> >>> Currently we don’t have enough developers(and I’m not willing to) to
> >> maintain a stack on our own like BDP.
> >>>
> >>>> Sure, here's my proposal:
> >>>>
> >>>> * Stack name: "BIGTOP"
> >>>>
> >>>> - The same name as the existing one [1]
> >>>> - Because it deploys the packages generated by Bigtop
> >>>> - The existing stack should be replaced with it, because that is
> >>>> based on Bigtop 0.8 and too old to use now
> >>>> - No concern about infringing others' trademark
> >>>>
> >>>> * Component/folder name: "bigtop-select"
> >>>>
> >>>> - Consistent naming convention with the existing tools such as
> >>>> "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> >>>> - If it sounds too simple and a bit unclear, a more descriptive
> name
> >>>> might be an option, for example "bigtop-ambari-stack-selector"
> >>>>
> >>>> * Script name: "bigtop-select"
> >>>>
> >>>> - Consistent with the stack name
> >>>> - No concern about infringing others' trademark
> >>>>
> >>>> [1]:
> >>
> https://github.com/apache/ambari/tree/release-2.7.6/ambari-server/src/main/resources/stacks/BIGTOP/0.8
> >>>> [2]:
> >> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common
> <
> >> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common
> >
> >>>
> >>> Best Regards,
> >>> Zhiguo Wu
> >>>
> >>>> On Sep 16, 2022, at 08:44, Masatake Iwasaki <
> iwasakims@oss.nttdata.com>
> >> wrote:
> >>>>
> >>>>
> >>>>>>> May be we can name it as bdp-select. Or (bgp-select)
> >>>>>> -1 as we already discussed.
> >>>>> Thanks for your feedback, I would definitely honour it. As you are
> not
> >> open for discussion and asked us raise the PR hence you thought of
> >> discussing on the PR. What will be your final suggestion on this..?
> >>>>
> >>>> I'm -1 on the name like bdp-select or bgp-select as we discussed.
> >>>> Feel free to open PR with appropriate module name.
> >>>>
> >>>> On 2022/09/05 16:30, Battula, Brahma Reddy wrote:
> >>>>> Hi @Masatake Iwasaki,
> >>>>>> -1 as we already discussed.
> >>>>> Thanks for your feedback, I would definitely honour it. As you are
> not
> >> open for discussion and asked us raise the PR hence you thought of
> >> discussing on the PR. What will be your final suggestion on this..?
> >>>>> @Roman Shaposhnik
> >>>>> I just gone through the following jira[1] where you brought ambari to
> >> bigtop. Looks stack-select is not included, how it was maintained.?
> >>>>> I thinking we should have one stack which can support for upgrading
> >> the existing the HDP deployed clusters. Even I can see somebody asking
> on
> >> bigtop[2].
> >>>>> If bigtop is not right place, shall we include in ambari..? Please
> >> let me know your thoughts on this. This blocks the 2.7.7 release.
> >>>>> Note : There is on-going ambari mpack which might take some more
> >> time. Even upgrades will take some time.
> >>>>> 1. https://issues.apache.org/jira/browse/BIGTOP-709
> >>>>> 2. https://issues.apache.org/jira/browse/BIGTOP-3651
> >>>>> Regards,
> >>>>> Brahma Reddy Battula
> >>>>> On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iwasakims@oss.nttdata.com
> >
> >> wrote:
> >>>>> > May be we can name it as bdp-select. Or (bgp-select)
> >>>>> -1 as we already discussed.
> >>>>> On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
> >>>>> > Ok, thanks Viraj.
> >>>>> >
> >>>>> > Hopefully you can place here like all other how it's
> >> maintained. Let me know any help required on this. May be we can name
> it as
> >> bdp-select. Or (bgp-select)
> >>>>> >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> >>>>> >
> >>>>> >
> >>>>> > On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org>
> >> wrote:
> >>>>> >
> >>>>> > Masatake, Brahma,
> >>>>> >
> >>>>> > Hopefully I should be able to create Jira and PR in
> >> Bigtop. Will let you
> >>>>> > know once ready for review. Thanks
> >>>>> >
> >>>>> >
> >>>>> > On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <
> >> iwasakims@oss.nttdata.com>
> >>>>> > wrote:
> >>>>> >
> >>>>> > > Please file a JIRA and submit a pull request if you
> want
> >> to show the code
> >>>>> > > and get feedback.
> >>>>> > > There is nothing I want to discuss off the record.
> >>>>> > >
> >>>>> > > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> >>>>> > > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and
> >> others, can we get
> >>>>> > > the final conclusion on this..?
> >>>>> > > >
> >>>>> > > > Please let me know your availability, Can have one
> >> call to discuss on
> >>>>> > > this..
> >>>>> > > >
> >>>>> > > >
> >>>>> > > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy"
> >> <bb...@visa.com.INVALID>
> >>>>> > > wrote:
> >>>>> > > >
> >>>>> > > > > -1 on development in branch.
> >>>>> > > > > It is not worth for maintaining the branch
> >> if the modules is
> >>>>> > > so small
> >>>>> > > > > and barely updated as explained here.
> >>>>> > > > > It should not conflict to existing code.
> >>>>> > > > > I feel I must check the code before
> >> check-in based on this
> >>>>> > > thread.
> >>>>> > > >
> >>>>> > > >
> >>>>> > > > Sure, Viraj or me can show the code to you.
> >>>>> > > >
> >>>>> > > > Can we've call on this Friday/Thrusday if that
> >> works..?
> >>>>> > > >
> >>>>> > > >
> >>>>> > > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> >>>>> > > iwasakims@oss.nttdata.com> wrote:
> >>>>> > > >
> >>>>> > > > > Sure, we can havemodule name like
> >> bigtop-distro-select.
> >>>>> > > > > Initially we'll do this separate branch.
> >>>>> > > >
> >>>>> > > > -1 on development in branch.
> >>>>> > > > It is not worth for maintaining the branch
> if
> >> the modules is so
> >>>>> > > small
> >>>>> > > > and barely updated as explained here.
> >>>>> > > > It should not conflict to existing code.
> >>>>> > > > I feel I must check the code before
> check-in
> >> based on this
> >>>>> > > thread.
> >>>>> > > >
> >>>>> > > > Masatake Iwasaki
> >>>>> > > >
> >>>>> > > > On 2022/07/11 8:23, Kengo Seki wrote:
> >>>>> > > > >> As there are different opinions on this
> >> and took long time,
> >>>>> > > just to brainstorm all the possibilities and pitfalls.
> >>>>> > > > >
> >>>>> > > > > Oh, I interpreted your words "conclude"
> and
> >> "finalize" as you
> >>>>> > > were
> >>>>> > > > > going to make a final decision.
> >> Brainstorming is welcome, of
> >>>>> > > course.
> >>>>> > > > > (But I'm not so sure if all people
> >> concerned could join, due
> >>>>> > > to time
> >>>>> > > > > difference and their schedule, etc.)
> >>>>> > > > >
> >>>>> > > > >> Can you suggest, how the changes will be
> >> also.. like folder,
> >>>>> > > where you suggest to keep this...?
> >>>>> > > > >
> >>>>> > > > > Sure, here's my proposal:
> >>>>> > > > >
> >>>>> > > > > * Stack name: "BIGTOP"
> >>>>> > > > >
> >>>>> > > > > - The same name as the existing one
> [1]
> >>>>> > > > > - Because it deploys the packages
> >> generated by Bigtop
> >>>>> > > > > - The existing stack should be
> replaced
> >> with it, because
> >>>>> > > that is
> >>>>> > > > > based on Bigtop 0.8 and too old to use
> now
> >>>>> > > > > - No concern about infringing others'
> >> trademark
> >>>>> > > > >
> >>>>> > > > > * Component/folder name: "bigtop-select"
> >>>>> > > > >
> >>>>> > > > > - Consistent naming convention with
> the
> >> existing tools
> >>>>> > > such as
> >>>>> > > > > "bigtop-groovy", "bigtop-jsvc",
> >> "bigtop-utils" [2]
> >>>>> > > > > - If it sounds too simple and a bit
> >> unclear, a more
> >>>>> > > descriptive name
> >>>>> > > > > might be an option, for example
> >> "bigtop-ambari-stack-selector"
> >>>>> > > > >
> >>>>> > > > > * Script name: "bigtop-select"
> >>>>> > > > >
> >>>>> > > > > - Consistent with the stack name
> >>>>> > > > > - No concern about infringing others'
> >> trademark
> >>>>> > > > >
> >>>>> > > > > [1]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
> >>>>> > > > > [2]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> >>>>> > > > >
> >>>>> > > > > Kengo Seki <se...@apache.org>
> >>>>> > > > >
> >>>>> > > > > On Mon, Jul 11, 2022 at 3:19 AM Battula,
> >> Brahma Reddy
> >>>>> > > > > <bb...@visa.com.invalid> wrote:
> >>>>> > > > >>
> >>>>> > > > >>> Technical decisions shouldn't be done
> >> on other places
> >>>>> > > than public mailing lists,
> >>>>> > > > >>> as described in the "Open
> >> Communications" section of [1]
> >>>>> > > and [2].
> >>>>> > > > >> > So we should conclude the discussion
> >> in this mailing
> >>>>> > > list.
> >>>>> > > > >> > (And with my poor English, I'm not
> so
> >> confident to catch
> >>>>> > > up with your
> >>>>> > > > >> > fluent talk ;)
> >>>>> > > > >>
> >>>>> > > > >> I believe , I knew the apache way which
> >> you mentioned. We
> >>>>> > > are not going conclude anything which comes to bigtop
> >> other than this
> >>>>> > > mailing list.
> >>>>> > > > >> As there are different opinions on this
> >> and took long time,
> >>>>> > > just to brainstorm all the possibilities and pitfalls.
> >> Hence asking let's
> >>>>> > > have call so that we can brainstorm. Even after call,
> >> everything will be
> >>>>> > > published what we discussed.
> >>>>> > > > >>
> >>>>> > > > >> I think, whiteboarding will help to
> catch
> >> up with you.
> >>>>> > > > >>
> >>>>> > > > >> You all the think "bigtop-select" will
> be
> >> best option
> >>>>> > > right..? Can you suggest, how the changes will be
> also..
> >> like folder, where
> >>>>> > > you suggest to keep this...?
> >>>>> > > > >>
> >>>>> > > > >> And if the name represents the stack
> which
> >> we are going to
> >>>>> > > deploy should fine I feel.. (if it's not BDP, may be
> >>>>> > > OBDP:OpensourceBigDataPlatform.)
> >>>>> > > > >>
> >>>>> > > > >> @Viraj Jasani and others any thoughts..?
> >>>>> > > > >>
> >>>>> > > > >>
> >>>>> > > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <
> >> sekikn@apache.org>
> >>>>> > > wrote:
> >>>>> > > > >>
> >>>>> > > > >> > Looks we had so much discussed
> >> here, Let's try to
> >>>>> > > conclude. Can we've one call on this and finalize
> this..?
> >>>>> > > > >>
> >>>>> > > > >> Technical decisions shouldn't be
> done
> >> on other places
> >>>>> > > than public mailing lists,
> >>>>> > > > >> as described in the "Open
> >> Communications" section of
> >>>>> > > [1] and [2].
> >>>>> > > > >> So we should conclude the
> discussion
> >> in this mailing
> >>>>> > > list.
> >>>>> > > > >> (And with my poor English, I'm not
> so
> >> confident to
> >>>>> > > catch up with your
> >>>>> > > > >> fluent talk ;)
> >>>>> > > > >>
> >>>>> > > > >> > FYI. Even looks bigtop used some
> >> where also..
> >>>>> > > > >>
> >>>>> > > > >> Bigtop is ASF's trademark as you
> can
> >> see in the "Apache
> >>>>> > > Bigtop®
> >>>>> > > > >> software" section of [3].
> >>>>> > > > >> So it doesn't have the risk of
> >> trademark infringement.
> >>>>> > > > >>
> >>>>> > > > >> [1]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
> >>>>> > > > >> [2]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
> >>>>> > > > >> [3]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
> >>>>> > > > >>
> >>>>> > > > >> Kengo Seki <se...@apache.org>
> >>>>> > > > >>
> >>>>> > > > >> On Sun, Jul 10, 2022 at 4:11 AM
> >> Battula, Brahma Reddy
> >>>>> > > > >> <bb...@visa.com.invalid> wrote:
> >>>>> > > > >> >
> >>>>> > > > >> > Looks we had so much discussed
> >> here, Let's try to
> >>>>> > > conclude. Can we've one call on this and finalize
> this..?
> >>>>> > > > >> >
> >>>>> > > > >> > FYI. Even looks bigtop used some
> >> where[1] also..
> >>>>> > > > >> > 1.
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
> >>>>> > > > >> >
> >>>>> > > > >> >
> >>>>> > > > >> > On 08/07/22, 8:06 PM, "Kengo
> Seki" <
> >> sekikn@apache.org>
> >>>>> > > wrote:
> >>>>> > > > >> >
> >>>>> > > > >> > Thank you for your
> explanation,
> >> Brahma.
> >>>>> > > > >> > CRH (abbreviation of "CHINA
> >> REDOOP HYPERLOOP"
> >>>>> > > [1]) is supposed to be a
> >>>>> > > > >> > trademark of Redoop, so they
> >> can name the script
> >>>>> > > crh-select without
> >>>>> > > > >> > problem.
> >>>>> > > > >> > But regarding BDP for
> example,
> >> I can easily find
> >>>>> > > products that have
> >>>>> > > > >> > the same name [2][3][4] as
> you
> >> already mentioned,
> >>>>> > > so I'd like to
> >>>>> > > > >> > recommend bigtop-select for
> >> avoiding unnecessary
> >>>>> > > trouble.
> >>>>> > > > >> > Or, a single and more general
> >> word just like
> >>>>> > > conf-select may be less
> >>>>> > > > >> > troublesome than bdp. How
> about
> >> "stack-select",
> >>>>> > > for example?
> >>>>> > > > >> >
> >>>>> > > > >> > [1]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
> >>>>> > > > >> > [2]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
> >>>>> > > > >> > [3]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
> >>>>> > > > >> > [4]:
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
> >>>>> > > > >> >
> >>>>> > > > >> > Kengo Seki <
> sekikn@apache.org>
> >>>>> > > > >> >
> >>>>> > > > >> > On Fri, Jul 8, 2022 at 2:51
> AM
> >> Battula, Brahma
> >>>>> > > Reddy <bb...@visa.com> wrote:
> >>>>> > > > >> > >
> >>>>> > > > >> > > >Do you mean that
> you're
> >> going to name the
> >>>>> > > module (same as "component"
> >>>>> > > > >> > > >in the Bigtop
> >> terminology, I think)
> >>>>> > > bigtop-distro-select,
> >>>>> > > > >> > > >and still the script
> in
> >> question
> >>>>> > > bdp-select? If so, is there any
> >>>>> > > > >> > > >reason that the script
> >> must be that name?
> >>>>> > > > >> > > >(No offence, I just
> want
> >> to understand
> >>>>> > > your thoughts and its
> >>>>> > > > >> > > >background, and avoid
> >> the conflict or
> >>>>> > > user's confusion with existing
> >>>>> > > > >> > > >trademarks or
> products)
> >>>>> > > > >> > >
> >>>>> > > > >> > > Thanks @Kengo Seki for
> >> consolidating all the
> >>>>> > > concerns. Name should represent the stack which
> includes
> >> all the components
> >>>>> > > hence planning to have like bdp,bds...and this only
> one
> >> file like below[1]
> >>>>> > > which has done redoop.
> >>>>> > > > >> > >
> >>>>> > > > >> > >
> >>>>> > > > >> > >
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
> >>>>> > > > >> > >
> >>>>> > > > >> > >
> >>>>> > > > >> > > On 07/07/22, 6:07 AM,
> "Kengo
> >> Seki" <
> >>>>> > > sekikn@apache.org> wrote:
> >>>>> > > > >> > >
> >>>>> > > > >> > > The following concern
> >> Masatake mentioned
> >>>>> > > before is an important point,
> >>>>> > > > >> > > so I talked to Brahma
> for
> >> clarifying his
> >>>>> > > intention on the ASF Slack
> >>>>> > > > >> > > yesterday.
> >>>>> > > > >> > >
> >>>>> > > > >> > > > Multiple versions of
> >> the same package
> >>>>> > > (deb/rpm) can not be installed at the same time.
> >>>>> > > > >> > > > IIRC, HDP uses
> >> convention in which the
> >>>>> > > product version is part of package name
> >>>>> > > > >> > > > for addressing this.
> >>>>> > > > >> > >
> >>>>> > > > >> > > > I don't like to bring
> >> the awkward package
> >>>>> > > name convention to Bigtop
> >>>>> > > > >> > > > at least by default.
> >>>>> > > > >> > >
> >>>>> > > > >> > > He's planning to adopt
> >> the same mitigation
> >>>>> > > as HDP for now, but he
> >>>>> > > > >> > > doesn't intend to
> change
> >> the default
> >>>>> > > package naming convention of
> >>>>> > > > >> > > Bigtop,
> >>>>> > > > >> > > but just add a new
> >> functionality to include
> >>>>> > > an extra part into the
> >>>>> > > > >> > > package name for
> avoiding
> >> conflict, which
> >>>>> > > is disabled by default.
> >>>>> > > > >> > >
> >>>>> > > > >> > > And Brahma, let me
> >> confirm about the
> >>>>> > > following reply:
> >>>>> > > > >> > >
> >>>>> > > > >> > > > Sure, we can have
> >> module name like
> >>>>> > > bigtop-distro-select.
> >>>>> > > > >> > >
> >>>>> > > > >> > > Do you mean that you're
> >> going to name the
> >>>>> > > module (same as "component"
> >>>>> > > > >> > > in the Bigtop
> >> terminology, I think)
> >>>>> > > bigtop-distro-select,
> >>>>> > > > >> > > and still the script in
> >> question
> >>>>> > > bdp-select? If so, is there any
> >>>>> > > > >> > > reason that the script
> >> must be that name?
> >>>>> > > > >> > > (No offence, I just
> want
> >> to understand your
> >>>>> > > thoughts and its
> >>>>> > > > >> > > background, and avoid
> the
> >> conflict or
> >>>>> > > user's confusion with existing
> >>>>> > > > >> > > trademarks or products)
> >>>>> > > > >> > >
> >>>>> > > > >> > > Kengo Seki <
> >> sekikn@apache.org>
> >>>>> > > > >> > >
> >>>>> > > > >> > > On Thu, Jul 7, 2022 at
> >> 2:08 AM Battula,
> >>>>> > > Brahma Reddy
> >>>>> > > > >> > >
> <bb...@visa.com.invalid>
> >> wrote:
> >>>>> > > > >> > > >
> >>>>> > > > >> > > > > The name of stack
> >> based no Bigtop
> >>>>> > > should be Bigtop.
> >>>>> > > > >> > > > > If you can not
> >> accept the name like
> >>>>> > > bigtop-*, the work should done outside of Bigtop.
> >>>>> > > > >> > > > > I will cast -1
> if
> >> someone submit a
> >>>>> > > patch to add a module with the name spoiling branding.
> >>>>> > > > >> > > >
> >>>>> > > > >> > > > Sure, we can have
> >> module name like
> >>>>> > > bigtop-distro-select.
> >>>>> > > > >> > > > Initially we'll do
> this
> >> separate branch.
> >>>>> > > > >> > > >
> >>>>> > > > >> > > >
> >>>>> > > > >> > > >
> >>>>> > > > >> > > > On 06/07/22, 8:55 AM,
> >> "Masatake Iwasaki" <
> >>>>> > > iwasakims@oss.nttdata.co.jp> wrote:
> >>>>> > > > >> > > >
> >>>>> > > > >> > > > > I believe it's
> >> for project name.
> >>>>> > > isn't it.?
> >>>>> > > > >> > > >
> >>>>> > > > >> > > > projects and
> >> products.
> >>>>> > > > >> > > >
> >>>>> > > > >> > > > > IMO, We need to
> >> create folders and
> >>>>> > > refer stacknames so ambari-select,bigtop-select wn't
> >> looks good.
> >>>>> > > > >> > > >
> >>>>> > > > >> > > > The name of stack
> >> based no Bigtop
> >>>>> > > should be Bigtop.
> >>>>> > > > >> > > > If you can not
> >> accept the name like
> >>>>> > > bigtop-*, the work should done outside of Bigtop.
> >>>>> > > > >> > > > I will cast -1 if
> >> someone submit a
> >>>>> > > patch to add a module with the name spoiling branding.
> >>>>> > > > >> > > >
> >>>>> > > > >> > > >
> >>>>> > > > >> > > > On 2022/07/06
> >> 11:44, Battula, Brahma
> >>>>> > > Reddy wrote:
> >>>>> > > > >> > > > >
> >>>>> > > > >> > > > > I believe it's
> >> for project name.
> >>>>> > > isn't it.?
> >>>>> > > > >> > > > >
> >>>>> > > > >> > > > >
> >>>>> > > > >> > > > > On 06/07/22,
> 7:27
> >> AM, "Masatake
> >>>>> > > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >>>>> > > > >> > > > >
> >>>>> > > > >> > > > > > But As
> we
> >> are not releasing
> >>>>> > > as enterprise should be fine I think. IMO, We need to
> >> create folders and
> >>>>> > > refer stacknames so ambari-select,bigtop-select wn't
> >> looks good.
> >>>>> > > > >> > > > >
> >>>>> > > > >> > > > > Not fine.
> >>>>> > > > >> > > > > We have a
> >> trademark policy.
> >>>>> > > > >> > > > >
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
> >>>>> > > > >> > > > >
> >>>>> > > > >> > > > > On
> >> 2022/07/06 10:37, Battula,
> >>>>> > > Brahma Reddy wrote:
> >>>>> > > > >> > > > > >> Should
> we
> >> avoid
> >>>>> > > unrecognized brand which may be trademark of someone?
> >>>>> > > > >> > > > > >>
> >> ambari-select or
> >>>>> > > bigtop-select should be enough.
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > > Not
> sure,
> >> where to confirm
> >>>>> > > whether there is already trademark. When I googled
> found
> >> so many.
> >>>>> > > > >> > > > > > But As
> we
> >> are not releasing
> >>>>> > > as enterprise should be fine I think. IMO, We need to
> >> create folders and
> >>>>> > > refer stacknames so ambari-select,bigtop-select wn't
> >> looks good.
> >>>>> > > > >> > > > > > May be
> you
> >> can refer the
> >>>>> > > initial proposal [2] where I mentioned some more
> names.
> >>>>> > > (BDS-BigDataStack,OSS-OpenSourceSelect..)
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > > Finally
> >> thanks a bunch for
> >>>>> > > long healthy discussions on this. Mostly we all same
> >> page now.
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > > 1.
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > > 2.
> >>>>> > >
> >>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > > On
> >> 06/07/22, 4:01 AM,
> >>>>> > > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp>
> wrote:
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > > >
> We
> >> have still not
> >>>>> > > officially finalized the new replacement name for
> >>>>> > > > >> > > > > > >
> >> hdp-select, it would
> >>>>> > > likely be bdp-select (bdp: BigData Platform). However,
> >>>>> > > > >> > > > > > >
> the
> >> purpose of
> >>>>> > > bdp-select and conf-select remains the same.
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > >
> >> Should we avoid
> >>>>> > > unrecognized brand which may be trademark of someone?
> >>>>> > > > >> > > > > >
> >> ambari-select or
> >>>>> > > bigtop-select should be enough.
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > > > On
> >> 2022/06/29 13:52,
> >>>>> > > Viraj Jasani wrote:
> >>>>> > > > >> > > > > > >
> Hi
> >> Ambari/Bigtop dev,
> >>>>> > > > >> > > > > > >
> >>>>> > > > >> > > > > > >
> As
> >> per the new
> >>>>> > > roadmap of Apache Ambari, we would like to propose
> moving
> >>>>> > > > >> > > > > > >
> >> certain scripts
> >>>>> > > (previously known as hdp-select and conf-select) to
> >> Bigtop
> >>>>> > > > >> > > > > > >
> so
> >> that their rpm
> >>>>> > > installation could be managed independently.
> >>>>> > > > >> > > > > > >
> >> These scripts are a
> >>>>> > > basic necessity in the Ambari framework for the
> >>>>> > > > >> > > > > > >
> >> installation of
> >>>>> > > various Bigdata packages. The only major changes they
> >> would
> >>>>> > > > >> > > > > > >
> >> receive is when we
> >>>>> > > onboard new services and components to Ambari, else
> they
> >>>>> > > > >> > > > > > >
> >> usually do not
> >>>>> > > receive updates. In the past, we used to get
> hdp-select
> >> rpm
> >>>>> > > > >> > > > > > >
> >> downloaded and
> >>>>> > > installed from HDP repositories.
> >>>>> > > > >> > > > > > >
> >>>>> > > > >> > > > > > >
> We
> >> have still not
> >>>>> > > officially finalized the new replacement name for
> >>>>> > > > >> > > > > > >
> >> hdp-select, it would
> >>>>> > > likely be bdp-select (bdp: BigData Platform). However,
> >>>>> > > > >> > > > > > >
> the
> >> purpose of
> >>>>> > > bdp-select and conf-select remains the same.
> >>>>> > > > >> > > > > > >
> >>>>> > > > >> > > > > >
> >>>>> > > > >> > > > >
> >>>>> > > > >> > > >
> >>>>> > > > >> > > >
> >>>>> > > > >> > > >
> >>>>> > >
> >> ---------------------------------------------------------------------
> >>>>> > > > >> > > > To unsubscribe,
> e-mail:
> >>>>> > > dev-unsubscribe@ambari.apache.org
> >>>>> > > > >> > > > For additional
> >> commands, e-mail:
> >>>>> > > dev-help@ambari.apache.org
> >>>>> > > > >> > > >
> >>>>> > > > >> > >
> >>>>> > > > >> > >
> >>>>> > >
> >> ---------------------------------------------------------------------
> >>>>> > > > >> > > To unsubscribe, e-mail:
> >>>>> > > dev-unsubscribe@ambari.apache.org
> >>>>> > > > >> > > For additional
> commands,
> >> e-mail:
> >>>>> > > dev-help@ambari.apache.org
> >>>>> > > > >> > >
> >>>>> > > > >> > >
> >>>>> > > > >> >
> >>>>> > > > >> >
> >>>>> > >
> >> ---------------------------------------------------------------------
> >>>>> > > > >> > To unsubscribe, e-mail:
> >>>>> > > dev-unsubscribe@ambari.apache.org
> >>>>> > > > >> > For additional commands,
> e-mail:
> >>>>> > > dev-help@ambari.apache.org
> >>>>> > > > >> >
> >>>>> > > > >> >
> >>>>> > > > >>
> >>>>> > > > >>
> >>>>> > >
> >> ---------------------------------------------------------------------
> >>>>> > > > >> To unsubscribe, e-mail:
> >>>>> > > dev-unsubscribe@ambari.apache.org
> >>>>> > > > >> For additional commands, e-mail:
> >>>>> > > dev-help@ambari.apache.org
> >>>>> > > > >>
> >>>>> > > > >>
> >>>>> > > >
> >>>>> > > >
> >>>>> > > >
> >>>>> > >
> >> ---------------------------------------------------------------------
> >>>>> > > > To unsubscribe, e-mail:
> >> dev-unsubscribe@ambari.apache.org
> >>>>> > > > For additional commands, e-mail:
> >> dev-help@ambari.apache.org
> >>>>> > > >
> >>>>> > > >
> >>>>> > >
> >>>>> >
> >>>>> >
> >>>>> >
> >> ---------------------------------------------------------------------
> >>>>> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >>>>> > For additional commands, e-mail: dev-help@ambari.apache.org
> >>>>> >
> >>>>>
> >> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >>>>> For additional commands, e-mail: dev-help@ambari.apache.org
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >>>>> For additional commands, e-mail: dev-help@ambari.apache.org
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >>>> For additional commands, e-mail: dev-help@ambari.apache.org
> >>>
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> For additional commands, e-mail: dev-help@ambari.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.com>.
> IMHO, Bigtop stack mpack was planned for trunk only. It could even merge
> with a separate branch till it's stable.
-1 on managing branch as we have already discussed:
On 2022/07/24 5:01, Battula, Brahma Reddy wrote:
>> -1 on development in branch.
> > It is not worth for maintaining the branch if the modules is so small
> > and barely updated as explained here.
> > It should not conflict to existing code.
> > I feel I must check the code before check-in based on this thread.
>
>
> Sure, Viraj or me can show the code to you.
On 2022/09/26 2:29, Brahma Reddy Battula wrote:
> IMHO, Bigtop stack mpack was planned for trunk only. It could even merge
> with a separate branch till it's stable.
>
> On Thu, Sep 22, 2022 at 5:02 PM Masatake Iwasaki <iw...@oss.nttdata.com>
> wrote:
>
>> +1
>>
>> On 2022/09/21 11:12, 吴治国 wrote:
>>> I think we have enough to go on with Kengo’s proposal,
>>> Currently we don’t have enough developers(and I’m not willing to) to
>> maintain a stack on our own like BDP.
>>>
>>>> Sure, here's my proposal:
>>>>
>>>> * Stack name: "BIGTOP"
>>>>
>>>> - The same name as the existing one [1]
>>>> - Because it deploys the packages generated by Bigtop
>>>> - The existing stack should be replaced with it, because that is
>>>> based on Bigtop 0.8 and too old to use now
>>>> - No concern about infringing others' trademark
>>>>
>>>> * Component/folder name: "bigtop-select"
>>>>
>>>> - Consistent naming convention with the existing tools such as
>>>> "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
>>>> - If it sounds too simple and a bit unclear, a more descriptive name
>>>> might be an option, for example "bigtop-ambari-stack-selector"
>>>>
>>>> * Script name: "bigtop-select"
>>>>
>>>> - Consistent with the stack name
>>>> - No concern about infringing others' trademark
>>>>
>>>> [1]:
>> https://github.com/apache/ambari/tree/release-2.7.6/ambari-server/src/main/resources/stacks/BIGTOP/0.8
>>>> [2]:
>> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common <
>> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common>
>>>
>>> Best Regards,
>>> Zhiguo Wu
>>>
>>>> On Sep 16, 2022, at 08:44, Masatake Iwasaki <iw...@oss.nttdata.com>
>> wrote:
>>>>
>>>>
>>>>>>> May be we can name it as bdp-select. Or (bgp-select)
>>>>>> -1 as we already discussed.
>>>>> Thanks for your feedback, I would definitely honour it. As you are not
>> open for discussion and asked us raise the PR hence you thought of
>> discussing on the PR. What will be your final suggestion on this..?
>>>>
>>>> I'm -1 on the name like bdp-select or bgp-select as we discussed.
>>>> Feel free to open PR with appropriate module name.
>>>>
>>>> On 2022/09/05 16:30, Battula, Brahma Reddy wrote:
>>>>> Hi @Masatake Iwasaki,
>>>>>> -1 as we already discussed.
>>>>> Thanks for your feedback, I would definitely honour it. As you are not
>> open for discussion and asked us raise the PR hence you thought of
>> discussing on the PR. What will be your final suggestion on this..?
>>>>> @Roman Shaposhnik
>>>>> I just gone through the following jira[1] where you brought ambari to
>> bigtop. Looks stack-select is not included, how it was maintained.?
>>>>> I thinking we should have one stack which can support for upgrading
>> the existing the HDP deployed clusters. Even I can see somebody asking on
>> bigtop[2].
>>>>> If bigtop is not right place, shall we include in ambari..? Please
>> let me know your thoughts on this. This blocks the 2.7.7 release.
>>>>> Note : There is on-going ambari mpack which might take some more
>> time. Even upgrades will take some time.
>>>>> 1. https://issues.apache.org/jira/browse/BIGTOP-709
>>>>> 2. https://issues.apache.org/jira/browse/BIGTOP-3651
>>>>> Regards,
>>>>> Brahma Reddy Battula
>>>>> On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com>
>> wrote:
>>>>> > May be we can name it as bdp-select. Or (bgp-select)
>>>>> -1 as we already discussed.
>>>>> On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
>>>>> > Ok, thanks Viraj.
>>>>> >
>>>>> > Hopefully you can place here like all other how it's
>> maintained. Let me know any help required on this. May be we can name it as
>> bdp-select. Or (bgp-select)
>>>>> >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
>>>>> >
>>>>> >
>>>>> > On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org>
>> wrote:
>>>>> >
>>>>> > Masatake, Brahma,
>>>>> >
>>>>> > Hopefully I should be able to create Jira and PR in
>> Bigtop. Will let you
>>>>> > know once ready for review. Thanks
>>>>> >
>>>>> >
>>>>> > On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <
>> iwasakims@oss.nttdata.com>
>>>>> > wrote:
>>>>> >
>>>>> > > Please file a JIRA and submit a pull request if you want
>> to show the code
>>>>> > > and get feedback.
>>>>> > > There is nothing I want to discuss off the record.
>>>>> > >
>>>>> > > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
>>>>> > > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and
>> others, can we get
>>>>> > > the final conclusion on this..?
>>>>> > > >
>>>>> > > > Please let me know your availability, Can have one
>> call to discuss on
>>>>> > > this..
>>>>> > > >
>>>>> > > >
>>>>> > > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy"
>> <bb...@visa.com.INVALID>
>>>>> > > wrote:
>>>>> > > >
>>>>> > > > > -1 on development in branch.
>>>>> > > > > It is not worth for maintaining the branch
>> if the modules is
>>>>> > > so small
>>>>> > > > > and barely updated as explained here.
>>>>> > > > > It should not conflict to existing code.
>>>>> > > > > I feel I must check the code before
>> check-in based on this
>>>>> > > thread.
>>>>> > > >
>>>>> > > >
>>>>> > > > Sure, Viraj or me can show the code to you.
>>>>> > > >
>>>>> > > > Can we've call on this Friday/Thrusday if that
>> works..?
>>>>> > > >
>>>>> > > >
>>>>> > > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
>>>>> > > iwasakims@oss.nttdata.com> wrote:
>>>>> > > >
>>>>> > > > > Sure, we can havemodule name like
>> bigtop-distro-select.
>>>>> > > > > Initially we'll do this separate branch.
>>>>> > > >
>>>>> > > > -1 on development in branch.
>>>>> > > > It is not worth for maintaining the branch if
>> the modules is so
>>>>> > > small
>>>>> > > > and barely updated as explained here.
>>>>> > > > It should not conflict to existing code.
>>>>> > > > I feel I must check the code before check-in
>> based on this
>>>>> > > thread.
>>>>> > > >
>>>>> > > > Masatake Iwasaki
>>>>> > > >
>>>>> > > > On 2022/07/11 8:23, Kengo Seki wrote:
>>>>> > > > >> As there are different opinions on this
>> and took long time,
>>>>> > > just to brainstorm all the possibilities and pitfalls.
>>>>> > > > >
>>>>> > > > > Oh, I interpreted your words "conclude" and
>> "finalize" as you
>>>>> > > were
>>>>> > > > > going to make a final decision.
>> Brainstorming is welcome, of
>>>>> > > course.
>>>>> > > > > (But I'm not so sure if all people
>> concerned could join, due
>>>>> > > to time
>>>>> > > > > difference and their schedule, etc.)
>>>>> > > > >
>>>>> > > > >> Can you suggest, how the changes will be
>> also.. like folder,
>>>>> > > where you suggest to keep this...?
>>>>> > > > >
>>>>> > > > > Sure, here's my proposal:
>>>>> > > > >
>>>>> > > > > * Stack name: "BIGTOP"
>>>>> > > > >
>>>>> > > > > - The same name as the existing one [1]
>>>>> > > > > - Because it deploys the packages
>> generated by Bigtop
>>>>> > > > > - The existing stack should be replaced
>> with it, because
>>>>> > > that is
>>>>> > > > > based on Bigtop 0.8 and too old to use now
>>>>> > > > > - No concern about infringing others'
>> trademark
>>>>> > > > >
>>>>> > > > > * Component/folder name: "bigtop-select"
>>>>> > > > >
>>>>> > > > > - Consistent naming convention with the
>> existing tools
>>>>> > > such as
>>>>> > > > > "bigtop-groovy", "bigtop-jsvc",
>> "bigtop-utils" [2]
>>>>> > > > > - If it sounds too simple and a bit
>> unclear, a more
>>>>> > > descriptive name
>>>>> > > > > might be an option, for example
>> "bigtop-ambari-stack-selector"
>>>>> > > > >
>>>>> > > > > * Script name: "bigtop-select"
>>>>> > > > >
>>>>> > > > > - Consistent with the stack name
>>>>> > > > > - No concern about infringing others'
>> trademark
>>>>> > > > >
>>>>> > > > > [1]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
>>>>> > > > > [2]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
>>>>> > > > >
>>>>> > > > > Kengo Seki <se...@apache.org>
>>>>> > > > >
>>>>> > > > > On Mon, Jul 11, 2022 at 3:19 AM Battula,
>> Brahma Reddy
>>>>> > > > > <bb...@visa.com.invalid> wrote:
>>>>> > > > >>
>>>>> > > > >>> Technical decisions shouldn't be done
>> on other places
>>>>> > > than public mailing lists,
>>>>> > > > >>> as described in the "Open
>> Communications" section of [1]
>>>>> > > and [2].
>>>>> > > > >> > So we should conclude the discussion
>> in this mailing
>>>>> > > list.
>>>>> > > > >> > (And with my poor English, I'm not so
>> confident to catch
>>>>> > > up with your
>>>>> > > > >> > fluent talk ;)
>>>>> > > > >>
>>>>> > > > >> I believe , I knew the apache way which
>> you mentioned. We
>>>>> > > are not going conclude anything which comes to bigtop
>> other than this
>>>>> > > mailing list.
>>>>> > > > >> As there are different opinions on this
>> and took long time,
>>>>> > > just to brainstorm all the possibilities and pitfalls.
>> Hence asking let's
>>>>> > > have call so that we can brainstorm. Even after call,
>> everything will be
>>>>> > > published what we discussed.
>>>>> > > > >>
>>>>> > > > >> I think, whiteboarding will help to catch
>> up with you.
>>>>> > > > >>
>>>>> > > > >> You all the think "bigtop-select" will be
>> best option
>>>>> > > right..? Can you suggest, how the changes will be also..
>> like folder, where
>>>>> > > you suggest to keep this...?
>>>>> > > > >>
>>>>> > > > >> And if the name represents the stack which
>> we are going to
>>>>> > > deploy should fine I feel.. (if it's not BDP, may be
>>>>> > > OBDP:OpensourceBigDataPlatform.)
>>>>> > > > >>
>>>>> > > > >> @Viraj Jasani and others any thoughts..?
>>>>> > > > >>
>>>>> > > > >>
>>>>> > > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <
>> sekikn@apache.org>
>>>>> > > wrote:
>>>>> > > > >>
>>>>> > > > >> > Looks we had so much discussed
>> here, Let's try to
>>>>> > > conclude. Can we've one call on this and finalize this..?
>>>>> > > > >>
>>>>> > > > >> Technical decisions shouldn't be done
>> on other places
>>>>> > > than public mailing lists,
>>>>> > > > >> as described in the "Open
>> Communications" section of
>>>>> > > [1] and [2].
>>>>> > > > >> So we should conclude the discussion
>> in this mailing
>>>>> > > list.
>>>>> > > > >> (And with my poor English, I'm not so
>> confident to
>>>>> > > catch up with your
>>>>> > > > >> fluent talk ;)
>>>>> > > > >>
>>>>> > > > >> > FYI. Even looks bigtop used some
>> where also..
>>>>> > > > >>
>>>>> > > > >> Bigtop is ASF's trademark as you can
>> see in the "Apache
>>>>> > > Bigtop®
>>>>> > > > >> software" section of [3].
>>>>> > > > >> So it doesn't have the risk of
>> trademark infringement.
>>>>> > > > >>
>>>>> > > > >> [1]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
>>>>> > > > >> [2]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
>>>>> > > > >> [3]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
>>>>> > > > >>
>>>>> > > > >> Kengo Seki <se...@apache.org>
>>>>> > > > >>
>>>>> > > > >> On Sun, Jul 10, 2022 at 4:11 AM
>> Battula, Brahma Reddy
>>>>> > > > >> <bb...@visa.com.invalid> wrote:
>>>>> > > > >> >
>>>>> > > > >> > Looks we had so much discussed
>> here, Let's try to
>>>>> > > conclude. Can we've one call on this and finalize this..?
>>>>> > > > >> >
>>>>> > > > >> > FYI. Even looks bigtop used some
>> where[1] also..
>>>>> > > > >> > 1.
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
>>>>> > > > >> >
>>>>> > > > >> >
>>>>> > > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <
>> sekikn@apache.org>
>>>>> > > wrote:
>>>>> > > > >> >
>>>>> > > > >> > Thank you for your explanation,
>> Brahma.
>>>>> > > > >> > CRH (abbreviation of "CHINA
>> REDOOP HYPERLOOP"
>>>>> > > [1]) is supposed to be a
>>>>> > > > >> > trademark of Redoop, so they
>> can name the script
>>>>> > > crh-select without
>>>>> > > > >> > problem.
>>>>> > > > >> > But regarding BDP for example,
>> I can easily find
>>>>> > > products that have
>>>>> > > > >> > the same name [2][3][4] as you
>> already mentioned,
>>>>> > > so I'd like to
>>>>> > > > >> > recommend bigtop-select for
>> avoiding unnecessary
>>>>> > > trouble.
>>>>> > > > >> > Or, a single and more general
>> word just like
>>>>> > > conf-select may be less
>>>>> > > > >> > troublesome than bdp. How about
>> "stack-select",
>>>>> > > for example?
>>>>> > > > >> >
>>>>> > > > >> > [1]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
>>>>> > > > >> > [2]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
>>>>> > > > >> > [3]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
>>>>> > > > >> > [4]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
>>>>> > > > >> >
>>>>> > > > >> > Kengo Seki <se...@apache.org>
>>>>> > > > >> >
>>>>> > > > >> > On Fri, Jul 8, 2022 at 2:51 AM
>> Battula, Brahma
>>>>> > > Reddy <bb...@visa.com> wrote:
>>>>> > > > >> > >
>>>>> > > > >> > > >Do you mean that you're
>> going to name the
>>>>> > > module (same as "component"
>>>>> > > > >> > > >in the Bigtop
>> terminology, I think)
>>>>> > > bigtop-distro-select,
>>>>> > > > >> > > >and still the script in
>> question
>>>>> > > bdp-select? If so, is there any
>>>>> > > > >> > > >reason that the script
>> must be that name?
>>>>> > > > >> > > >(No offence, I just want
>> to understand
>>>>> > > your thoughts and its
>>>>> > > > >> > > >background, and avoid
>> the conflict or
>>>>> > > user's confusion with existing
>>>>> > > > >> > > >trademarks or products)
>>>>> > > > >> > >
>>>>> > > > >> > > Thanks @Kengo Seki for
>> consolidating all the
>>>>> > > concerns. Name should represent the stack which includes
>> all the components
>>>>> > > hence planning to have like bdp,bds...and this only one
>> file like below[1]
>>>>> > > which has done redoop.
>>>>> > > > >> > >
>>>>> > > > >> > >
>>>>> > > > >> > >
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
>>>>> > > > >> > >
>>>>> > > > >> > >
>>>>> > > > >> > > On 07/07/22, 6:07 AM, "Kengo
>> Seki" <
>>>>> > > sekikn@apache.org> wrote:
>>>>> > > > >> > >
>>>>> > > > >> > > The following concern
>> Masatake mentioned
>>>>> > > before is an important point,
>>>>> > > > >> > > so I talked to Brahma for
>> clarifying his
>>>>> > > intention on the ASF Slack
>>>>> > > > >> > > yesterday.
>>>>> > > > >> > >
>>>>> > > > >> > > > Multiple versions of
>> the same package
>>>>> > > (deb/rpm) can not be installed at the same time.
>>>>> > > > >> > > > IIRC, HDP uses
>> convention in which the
>>>>> > > product version is part of package name
>>>>> > > > >> > > > for addressing this.
>>>>> > > > >> > >
>>>>> > > > >> > > > I don't like to bring
>> the awkward package
>>>>> > > name convention to Bigtop
>>>>> > > > >> > > > at least by default.
>>>>> > > > >> > >
>>>>> > > > >> > > He's planning to adopt
>> the same mitigation
>>>>> > > as HDP for now, but he
>>>>> > > > >> > > doesn't intend to change
>> the default
>>>>> > > package naming convention of
>>>>> > > > >> > > Bigtop,
>>>>> > > > >> > > but just add a new
>> functionality to include
>>>>> > > an extra part into the
>>>>> > > > >> > > package name for avoiding
>> conflict, which
>>>>> > > is disabled by default.
>>>>> > > > >> > >
>>>>> > > > >> > > And Brahma, let me
>> confirm about the
>>>>> > > following reply:
>>>>> > > > >> > >
>>>>> > > > >> > > > Sure, we can have
>> module name like
>>>>> > > bigtop-distro-select.
>>>>> > > > >> > >
>>>>> > > > >> > > Do you mean that you're
>> going to name the
>>>>> > > module (same as "component"
>>>>> > > > >> > > in the Bigtop
>> terminology, I think)
>>>>> > > bigtop-distro-select,
>>>>> > > > >> > > and still the script in
>> question
>>>>> > > bdp-select? If so, is there any
>>>>> > > > >> > > reason that the script
>> must be that name?
>>>>> > > > >> > > (No offence, I just want
>> to understand your
>>>>> > > thoughts and its
>>>>> > > > >> > > background, and avoid the
>> conflict or
>>>>> > > user's confusion with existing
>>>>> > > > >> > > trademarks or products)
>>>>> > > > >> > >
>>>>> > > > >> > > Kengo Seki <
>> sekikn@apache.org>
>>>>> > > > >> > >
>>>>> > > > >> > > On Thu, Jul 7, 2022 at
>> 2:08 AM Battula,
>>>>> > > Brahma Reddy
>>>>> > > > >> > > <bb...@visa.com.invalid>
>> wrote:
>>>>> > > > >> > > >
>>>>> > > > >> > > > > The name of stack
>> based no Bigtop
>>>>> > > should be Bigtop.
>>>>> > > > >> > > > > If you can not
>> accept the name like
>>>>> > > bigtop-*, the work should done outside of Bigtop.
>>>>> > > > >> > > > > I will cast -1 if
>> someone submit a
>>>>> > > patch to add a module with the name spoiling branding.
>>>>> > > > >> > > >
>>>>> > > > >> > > > Sure, we can have
>> module name like
>>>>> > > bigtop-distro-select.
>>>>> > > > >> > > > Initially we'll do this
>> separate branch.
>>>>> > > > >> > > >
>>>>> > > > >> > > >
>>>>> > > > >> > > >
>>>>> > > > >> > > > On 06/07/22, 8:55 AM,
>> "Masatake Iwasaki" <
>>>>> > > iwasakims@oss.nttdata.co.jp> wrote:
>>>>> > > > >> > > >
>>>>> > > > >> > > > > I believe it's
>> for project name.
>>>>> > > isn't it.?
>>>>> > > > >> > > >
>>>>> > > > >> > > > projects and
>> products.
>>>>> > > > >> > > >
>>>>> > > > >> > > > > IMO, We need to
>> create folders and
>>>>> > > refer stacknames so ambari-select,bigtop-select wn't
>> looks good.
>>>>> > > > >> > > >
>>>>> > > > >> > > > The name of stack
>> based no Bigtop
>>>>> > > should be Bigtop.
>>>>> > > > >> > > > If you can not
>> accept the name like
>>>>> > > bigtop-*, the work should done outside of Bigtop.
>>>>> > > > >> > > > I will cast -1 if
>> someone submit a
>>>>> > > patch to add a module with the name spoiling branding.
>>>>> > > > >> > > >
>>>>> > > > >> > > >
>>>>> > > > >> > > > On 2022/07/06
>> 11:44, Battula, Brahma
>>>>> > > Reddy wrote:
>>>>> > > > >> > > > >
>>>>> > > > >> > > > > I believe it's
>> for project name.
>>>>> > > isn't it.?
>>>>> > > > >> > > > >
>>>>> > > > >> > > > >
>>>>> > > > >> > > > > On 06/07/22, 7:27
>> AM, "Masatake
>>>>> > > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>>> > > > >> > > > >
>>>>> > > > >> > > > > > But As we
>> are not releasing
>>>>> > > as enterprise should be fine I think. IMO, We need to
>> create folders and
>>>>> > > refer stacknames so ambari-select,bigtop-select wn't
>> looks good.
>>>>> > > > >> > > > >
>>>>> > > > >> > > > > Not fine.
>>>>> > > > >> > > > > We have a
>> trademark policy.
>>>>> > > > >> > > > >
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
>>>>> > > > >> > > > >
>>>>> > > > >> > > > > On
>> 2022/07/06 10:37, Battula,
>>>>> > > Brahma Reddy wrote:
>>>>> > > > >> > > > > >> Should we
>> avoid
>>>>> > > unrecognized brand which may be trademark of someone?
>>>>> > > > >> > > > > >>
>> ambari-select or
>>>>> > > bigtop-select should be enough.
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > > Not sure,
>> where to confirm
>>>>> > > whether there is already trademark. When I googled found
>> so many.
>>>>> > > > >> > > > > > But As we
>> are not releasing
>>>>> > > as enterprise should be fine I think. IMO, We need to
>> create folders and
>>>>> > > refer stacknames so ambari-select,bigtop-select wn't
>> looks good.
>>>>> > > > >> > > > > > May be you
>> can refer the
>>>>> > > initial proposal [2] where I mentioned some more names.
>>>>> > > (BDS-BigDataStack,OSS-OpenSourceSelect..)
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > > Finally
>> thanks a bunch for
>>>>> > > long healthy discussions on this. Mostly we all same
>> page now.
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > > 1.
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > > 2.
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > > On
>> 06/07/22, 4:01 AM,
>>>>> > > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > > > We
>> have still not
>>>>> > > officially finalized the new replacement name for
>>>>> > > > >> > > > > > >
>> hdp-select, it would
>>>>> > > likely be bdp-select (bdp: BigData Platform). However,
>>>>> > > > >> > > > > > > the
>> purpose of
>>>>> > > bdp-select and conf-select remains the same.
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > >
>> Should we avoid
>>>>> > > unrecognized brand which may be trademark of someone?
>>>>> > > > >> > > > > >
>> ambari-select or
>>>>> > > bigtop-select should be enough.
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > > On
>> 2022/06/29 13:52,
>>>>> > > Viraj Jasani wrote:
>>>>> > > > >> > > > > > > Hi
>> Ambari/Bigtop dev,
>>>>> > > > >> > > > > > >
>>>>> > > > >> > > > > > > As
>> per the new
>>>>> > > roadmap of Apache Ambari, we would like to propose moving
>>>>> > > > >> > > > > > >
>> certain scripts
>>>>> > > (previously known as hdp-select and conf-select) to
>> Bigtop
>>>>> > > > >> > > > > > > so
>> that their rpm
>>>>> > > installation could be managed independently.
>>>>> > > > >> > > > > > >
>> These scripts are a
>>>>> > > basic necessity in the Ambari framework for the
>>>>> > > > >> > > > > > >
>> installation of
>>>>> > > various Bigdata packages. The only major changes they
>> would
>>>>> > > > >> > > > > > >
>> receive is when we
>>>>> > > onboard new services and components to Ambari, else they
>>>>> > > > >> > > > > > >
>> usually do not
>>>>> > > receive updates. In the past, we used to get hdp-select
>> rpm
>>>>> > > > >> > > > > > >
>> downloaded and
>>>>> > > installed from HDP repositories.
>>>>> > > > >> > > > > > >
>>>>> > > > >> > > > > > > We
>> have still not
>>>>> > > officially finalized the new replacement name for
>>>>> > > > >> > > > > > >
>> hdp-select, it would
>>>>> > > likely be bdp-select (bdp: BigData Platform). However,
>>>>> > > > >> > > > > > > the
>> purpose of
>>>>> > > bdp-select and conf-select remains the same.
>>>>> > > > >> > > > > > >
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > >
>>>>> > > > >> > > >
>>>>> > > > >> > > >
>>>>> > > > >> > > >
>>>>> > >
>> ---------------------------------------------------------------------
>>>>> > > > >> > > > To unsubscribe, e-mail:
>>>>> > > dev-unsubscribe@ambari.apache.org
>>>>> > > > >> > > > For additional
>> commands, e-mail:
>>>>> > > dev-help@ambari.apache.org
>>>>> > > > >> > > >
>>>>> > > > >> > >
>>>>> > > > >> > >
>>>>> > >
>> ---------------------------------------------------------------------
>>>>> > > > >> > > To unsubscribe, e-mail:
>>>>> > > dev-unsubscribe@ambari.apache.org
>>>>> > > > >> > > For additional commands,
>> e-mail:
>>>>> > > dev-help@ambari.apache.org
>>>>> > > > >> > >
>>>>> > > > >> > >
>>>>> > > > >> >
>>>>> > > > >> >
>>>>> > >
>> ---------------------------------------------------------------------
>>>>> > > > >> > To unsubscribe, e-mail:
>>>>> > > dev-unsubscribe@ambari.apache.org
>>>>> > > > >> > For additional commands, e-mail:
>>>>> > > dev-help@ambari.apache.org
>>>>> > > > >> >
>>>>> > > > >> >
>>>>> > > > >>
>>>>> > > > >>
>>>>> > >
>> ---------------------------------------------------------------------
>>>>> > > > >> To unsubscribe, e-mail:
>>>>> > > dev-unsubscribe@ambari.apache.org
>>>>> > > > >> For additional commands, e-mail:
>>>>> > > dev-help@ambari.apache.org
>>>>> > > > >>
>>>>> > > > >>
>>>>> > > >
>>>>> > > >
>>>>> > > >
>>>>> > >
>> ---------------------------------------------------------------------
>>>>> > > > To unsubscribe, e-mail:
>> dev-unsubscribe@ambari.apache.org
>>>>> > > > For additional commands, e-mail:
>> dev-help@ambari.apache.org
>>>>> > > >
>>>>> > > >
>>>>> > >
>>>>> >
>>>>> >
>>>>> >
>> ---------------------------------------------------------------------
>>>>> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>>>> > For additional commands, e-mail: dev-help@ambari.apache.org
>>>>> >
>>>>>
>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>>>> For additional commands, e-mail: dev-help@ambari.apache.org
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>>>> For additional commands, e-mail: dev-help@ambari.apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>>> For additional commands, e-mail: dev-help@ambari.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> For additional commands, e-mail: dev-help@ambari.apache.org
>>
>>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.com>.
> IMHO, Bigtop stack mpack was planned for trunk only. It could even merge
> with a separate branch till it's stable.
-1 on managing branch as we have already discussed:
On 2022/07/24 5:01, Battula, Brahma Reddy wrote:
>> -1 on development in branch.
> > It is not worth for maintaining the branch if the modules is so small
> > and barely updated as explained here.
> > It should not conflict to existing code.
> > I feel I must check the code before check-in based on this thread.
>
>
> Sure, Viraj or me can show the code to you.
On 2022/09/26 2:29, Brahma Reddy Battula wrote:
> IMHO, Bigtop stack mpack was planned for trunk only. It could even merge
> with a separate branch till it's stable.
>
> On Thu, Sep 22, 2022 at 5:02 PM Masatake Iwasaki <iw...@oss.nttdata.com>
> wrote:
>
>> +1
>>
>> On 2022/09/21 11:12, 吴治国 wrote:
>>> I think we have enough to go on with Kengo’s proposal,
>>> Currently we don’t have enough developers(and I’m not willing to) to
>> maintain a stack on our own like BDP.
>>>
>>>> Sure, here's my proposal:
>>>>
>>>> * Stack name: "BIGTOP"
>>>>
>>>> - The same name as the existing one [1]
>>>> - Because it deploys the packages generated by Bigtop
>>>> - The existing stack should be replaced with it, because that is
>>>> based on Bigtop 0.8 and too old to use now
>>>> - No concern about infringing others' trademark
>>>>
>>>> * Component/folder name: "bigtop-select"
>>>>
>>>> - Consistent naming convention with the existing tools such as
>>>> "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
>>>> - If it sounds too simple and a bit unclear, a more descriptive name
>>>> might be an option, for example "bigtop-ambari-stack-selector"
>>>>
>>>> * Script name: "bigtop-select"
>>>>
>>>> - Consistent with the stack name
>>>> - No concern about infringing others' trademark
>>>>
>>>> [1]:
>> https://github.com/apache/ambari/tree/release-2.7.6/ambari-server/src/main/resources/stacks/BIGTOP/0.8
>>>> [2]:
>> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common <
>> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common>
>>>
>>> Best Regards,
>>> Zhiguo Wu
>>>
>>>> On Sep 16, 2022, at 08:44, Masatake Iwasaki <iw...@oss.nttdata.com>
>> wrote:
>>>>
>>>>
>>>>>>> May be we can name it as bdp-select. Or (bgp-select)
>>>>>> -1 as we already discussed.
>>>>> Thanks for your feedback, I would definitely honour it. As you are not
>> open for discussion and asked us raise the PR hence you thought of
>> discussing on the PR. What will be your final suggestion on this..?
>>>>
>>>> I'm -1 on the name like bdp-select or bgp-select as we discussed.
>>>> Feel free to open PR with appropriate module name.
>>>>
>>>> On 2022/09/05 16:30, Battula, Brahma Reddy wrote:
>>>>> Hi @Masatake Iwasaki,
>>>>>> -1 as we already discussed.
>>>>> Thanks for your feedback, I would definitely honour it. As you are not
>> open for discussion and asked us raise the PR hence you thought of
>> discussing on the PR. What will be your final suggestion on this..?
>>>>> @Roman Shaposhnik
>>>>> I just gone through the following jira[1] where you brought ambari to
>> bigtop. Looks stack-select is not included, how it was maintained.?
>>>>> I thinking we should have one stack which can support for upgrading
>> the existing the HDP deployed clusters. Even I can see somebody asking on
>> bigtop[2].
>>>>> If bigtop is not right place, shall we include in ambari..? Please
>> let me know your thoughts on this. This blocks the 2.7.7 release.
>>>>> Note : There is on-going ambari mpack which might take some more
>> time. Even upgrades will take some time.
>>>>> 1. https://issues.apache.org/jira/browse/BIGTOP-709
>>>>> 2. https://issues.apache.org/jira/browse/BIGTOP-3651
>>>>> Regards,
>>>>> Brahma Reddy Battula
>>>>> On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com>
>> wrote:
>>>>> > May be we can name it as bdp-select. Or (bgp-select)
>>>>> -1 as we already discussed.
>>>>> On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
>>>>> > Ok, thanks Viraj.
>>>>> >
>>>>> > Hopefully you can place here like all other how it's
>> maintained. Let me know any help required on this. May be we can name it as
>> bdp-select. Or (bgp-select)
>>>>> >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
>>>>> >
>>>>> >
>>>>> > On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org>
>> wrote:
>>>>> >
>>>>> > Masatake, Brahma,
>>>>> >
>>>>> > Hopefully I should be able to create Jira and PR in
>> Bigtop. Will let you
>>>>> > know once ready for review. Thanks
>>>>> >
>>>>> >
>>>>> > On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <
>> iwasakims@oss.nttdata.com>
>>>>> > wrote:
>>>>> >
>>>>> > > Please file a JIRA and submit a pull request if you want
>> to show the code
>>>>> > > and get feedback.
>>>>> > > There is nothing I want to discuss off the record.
>>>>> > >
>>>>> > > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
>>>>> > > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and
>> others, can we get
>>>>> > > the final conclusion on this..?
>>>>> > > >
>>>>> > > > Please let me know your availability, Can have one
>> call to discuss on
>>>>> > > this..
>>>>> > > >
>>>>> > > >
>>>>> > > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy"
>> <bb...@visa.com.INVALID>
>>>>> > > wrote:
>>>>> > > >
>>>>> > > > > -1 on development in branch.
>>>>> > > > > It is not worth for maintaining the branch
>> if the modules is
>>>>> > > so small
>>>>> > > > > and barely updated as explained here.
>>>>> > > > > It should not conflict to existing code.
>>>>> > > > > I feel I must check the code before
>> check-in based on this
>>>>> > > thread.
>>>>> > > >
>>>>> > > >
>>>>> > > > Sure, Viraj or me can show the code to you.
>>>>> > > >
>>>>> > > > Can we've call on this Friday/Thrusday if that
>> works..?
>>>>> > > >
>>>>> > > >
>>>>> > > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
>>>>> > > iwasakims@oss.nttdata.com> wrote:
>>>>> > > >
>>>>> > > > > Sure, we can havemodule name like
>> bigtop-distro-select.
>>>>> > > > > Initially we'll do this separate branch.
>>>>> > > >
>>>>> > > > -1 on development in branch.
>>>>> > > > It is not worth for maintaining the branch if
>> the modules is so
>>>>> > > small
>>>>> > > > and barely updated as explained here.
>>>>> > > > It should not conflict to existing code.
>>>>> > > > I feel I must check the code before check-in
>> based on this
>>>>> > > thread.
>>>>> > > >
>>>>> > > > Masatake Iwasaki
>>>>> > > >
>>>>> > > > On 2022/07/11 8:23, Kengo Seki wrote:
>>>>> > > > >> As there are different opinions on this
>> and took long time,
>>>>> > > just to brainstorm all the possibilities and pitfalls.
>>>>> > > > >
>>>>> > > > > Oh, I interpreted your words "conclude" and
>> "finalize" as you
>>>>> > > were
>>>>> > > > > going to make a final decision.
>> Brainstorming is welcome, of
>>>>> > > course.
>>>>> > > > > (But I'm not so sure if all people
>> concerned could join, due
>>>>> > > to time
>>>>> > > > > difference and their schedule, etc.)
>>>>> > > > >
>>>>> > > > >> Can you suggest, how the changes will be
>> also.. like folder,
>>>>> > > where you suggest to keep this...?
>>>>> > > > >
>>>>> > > > > Sure, here's my proposal:
>>>>> > > > >
>>>>> > > > > * Stack name: "BIGTOP"
>>>>> > > > >
>>>>> > > > > - The same name as the existing one [1]
>>>>> > > > > - Because it deploys the packages
>> generated by Bigtop
>>>>> > > > > - The existing stack should be replaced
>> with it, because
>>>>> > > that is
>>>>> > > > > based on Bigtop 0.8 and too old to use now
>>>>> > > > > - No concern about infringing others'
>> trademark
>>>>> > > > >
>>>>> > > > > * Component/folder name: "bigtop-select"
>>>>> > > > >
>>>>> > > > > - Consistent naming convention with the
>> existing tools
>>>>> > > such as
>>>>> > > > > "bigtop-groovy", "bigtop-jsvc",
>> "bigtop-utils" [2]
>>>>> > > > > - If it sounds too simple and a bit
>> unclear, a more
>>>>> > > descriptive name
>>>>> > > > > might be an option, for example
>> "bigtop-ambari-stack-selector"
>>>>> > > > >
>>>>> > > > > * Script name: "bigtop-select"
>>>>> > > > >
>>>>> > > > > - Consistent with the stack name
>>>>> > > > > - No concern about infringing others'
>> trademark
>>>>> > > > >
>>>>> > > > > [1]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
>>>>> > > > > [2]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
>>>>> > > > >
>>>>> > > > > Kengo Seki <se...@apache.org>
>>>>> > > > >
>>>>> > > > > On Mon, Jul 11, 2022 at 3:19 AM Battula,
>> Brahma Reddy
>>>>> > > > > <bb...@visa.com.invalid> wrote:
>>>>> > > > >>
>>>>> > > > >>> Technical decisions shouldn't be done
>> on other places
>>>>> > > than public mailing lists,
>>>>> > > > >>> as described in the "Open
>> Communications" section of [1]
>>>>> > > and [2].
>>>>> > > > >> > So we should conclude the discussion
>> in this mailing
>>>>> > > list.
>>>>> > > > >> > (And with my poor English, I'm not so
>> confident to catch
>>>>> > > up with your
>>>>> > > > >> > fluent talk ;)
>>>>> > > > >>
>>>>> > > > >> I believe , I knew the apache way which
>> you mentioned. We
>>>>> > > are not going conclude anything which comes to bigtop
>> other than this
>>>>> > > mailing list.
>>>>> > > > >> As there are different opinions on this
>> and took long time,
>>>>> > > just to brainstorm all the possibilities and pitfalls.
>> Hence asking let's
>>>>> > > have call so that we can brainstorm. Even after call,
>> everything will be
>>>>> > > published what we discussed.
>>>>> > > > >>
>>>>> > > > >> I think, whiteboarding will help to catch
>> up with you.
>>>>> > > > >>
>>>>> > > > >> You all the think "bigtop-select" will be
>> best option
>>>>> > > right..? Can you suggest, how the changes will be also..
>> like folder, where
>>>>> > > you suggest to keep this...?
>>>>> > > > >>
>>>>> > > > >> And if the name represents the stack which
>> we are going to
>>>>> > > deploy should fine I feel.. (if it's not BDP, may be
>>>>> > > OBDP:OpensourceBigDataPlatform.)
>>>>> > > > >>
>>>>> > > > >> @Viraj Jasani and others any thoughts..?
>>>>> > > > >>
>>>>> > > > >>
>>>>> > > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <
>> sekikn@apache.org>
>>>>> > > wrote:
>>>>> > > > >>
>>>>> > > > >> > Looks we had so much discussed
>> here, Let's try to
>>>>> > > conclude. Can we've one call on this and finalize this..?
>>>>> > > > >>
>>>>> > > > >> Technical decisions shouldn't be done
>> on other places
>>>>> > > than public mailing lists,
>>>>> > > > >> as described in the "Open
>> Communications" section of
>>>>> > > [1] and [2].
>>>>> > > > >> So we should conclude the discussion
>> in this mailing
>>>>> > > list.
>>>>> > > > >> (And with my poor English, I'm not so
>> confident to
>>>>> > > catch up with your
>>>>> > > > >> fluent talk ;)
>>>>> > > > >>
>>>>> > > > >> > FYI. Even looks bigtop used some
>> where also..
>>>>> > > > >>
>>>>> > > > >> Bigtop is ASF's trademark as you can
>> see in the "Apache
>>>>> > > Bigtop®
>>>>> > > > >> software" section of [3].
>>>>> > > > >> So it doesn't have the risk of
>> trademark infringement.
>>>>> > > > >>
>>>>> > > > >> [1]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
>>>>> > > > >> [2]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
>>>>> > > > >> [3]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
>>>>> > > > >>
>>>>> > > > >> Kengo Seki <se...@apache.org>
>>>>> > > > >>
>>>>> > > > >> On Sun, Jul 10, 2022 at 4:11 AM
>> Battula, Brahma Reddy
>>>>> > > > >> <bb...@visa.com.invalid> wrote:
>>>>> > > > >> >
>>>>> > > > >> > Looks we had so much discussed
>> here, Let's try to
>>>>> > > conclude. Can we've one call on this and finalize this..?
>>>>> > > > >> >
>>>>> > > > >> > FYI. Even looks bigtop used some
>> where[1] also..
>>>>> > > > >> > 1.
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
>>>>> > > > >> >
>>>>> > > > >> >
>>>>> > > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <
>> sekikn@apache.org>
>>>>> > > wrote:
>>>>> > > > >> >
>>>>> > > > >> > Thank you for your explanation,
>> Brahma.
>>>>> > > > >> > CRH (abbreviation of "CHINA
>> REDOOP HYPERLOOP"
>>>>> > > [1]) is supposed to be a
>>>>> > > > >> > trademark of Redoop, so they
>> can name the script
>>>>> > > crh-select without
>>>>> > > > >> > problem.
>>>>> > > > >> > But regarding BDP for example,
>> I can easily find
>>>>> > > products that have
>>>>> > > > >> > the same name [2][3][4] as you
>> already mentioned,
>>>>> > > so I'd like to
>>>>> > > > >> > recommend bigtop-select for
>> avoiding unnecessary
>>>>> > > trouble.
>>>>> > > > >> > Or, a single and more general
>> word just like
>>>>> > > conf-select may be less
>>>>> > > > >> > troublesome than bdp. How about
>> "stack-select",
>>>>> > > for example?
>>>>> > > > >> >
>>>>> > > > >> > [1]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
>>>>> > > > >> > [2]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
>>>>> > > > >> > [3]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
>>>>> > > > >> > [4]:
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
>>>>> > > > >> >
>>>>> > > > >> > Kengo Seki <se...@apache.org>
>>>>> > > > >> >
>>>>> > > > >> > On Fri, Jul 8, 2022 at 2:51 AM
>> Battula, Brahma
>>>>> > > Reddy <bb...@visa.com> wrote:
>>>>> > > > >> > >
>>>>> > > > >> > > >Do you mean that you're
>> going to name the
>>>>> > > module (same as "component"
>>>>> > > > >> > > >in the Bigtop
>> terminology, I think)
>>>>> > > bigtop-distro-select,
>>>>> > > > >> > > >and still the script in
>> question
>>>>> > > bdp-select? If so, is there any
>>>>> > > > >> > > >reason that the script
>> must be that name?
>>>>> > > > >> > > >(No offence, I just want
>> to understand
>>>>> > > your thoughts and its
>>>>> > > > >> > > >background, and avoid
>> the conflict or
>>>>> > > user's confusion with existing
>>>>> > > > >> > > >trademarks or products)
>>>>> > > > >> > >
>>>>> > > > >> > > Thanks @Kengo Seki for
>> consolidating all the
>>>>> > > concerns. Name should represent the stack which includes
>> all the components
>>>>> > > hence planning to have like bdp,bds...and this only one
>> file like below[1]
>>>>> > > which has done redoop.
>>>>> > > > >> > >
>>>>> > > > >> > >
>>>>> > > > >> > >
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
>>>>> > > > >> > >
>>>>> > > > >> > >
>>>>> > > > >> > > On 07/07/22, 6:07 AM, "Kengo
>> Seki" <
>>>>> > > sekikn@apache.org> wrote:
>>>>> > > > >> > >
>>>>> > > > >> > > The following concern
>> Masatake mentioned
>>>>> > > before is an important point,
>>>>> > > > >> > > so I talked to Brahma for
>> clarifying his
>>>>> > > intention on the ASF Slack
>>>>> > > > >> > > yesterday.
>>>>> > > > >> > >
>>>>> > > > >> > > > Multiple versions of
>> the same package
>>>>> > > (deb/rpm) can not be installed at the same time.
>>>>> > > > >> > > > IIRC, HDP uses
>> convention in which the
>>>>> > > product version is part of package name
>>>>> > > > >> > > > for addressing this.
>>>>> > > > >> > >
>>>>> > > > >> > > > I don't like to bring
>> the awkward package
>>>>> > > name convention to Bigtop
>>>>> > > > >> > > > at least by default.
>>>>> > > > >> > >
>>>>> > > > >> > > He's planning to adopt
>> the same mitigation
>>>>> > > as HDP for now, but he
>>>>> > > > >> > > doesn't intend to change
>> the default
>>>>> > > package naming convention of
>>>>> > > > >> > > Bigtop,
>>>>> > > > >> > > but just add a new
>> functionality to include
>>>>> > > an extra part into the
>>>>> > > > >> > > package name for avoiding
>> conflict, which
>>>>> > > is disabled by default.
>>>>> > > > >> > >
>>>>> > > > >> > > And Brahma, let me
>> confirm about the
>>>>> > > following reply:
>>>>> > > > >> > >
>>>>> > > > >> > > > Sure, we can have
>> module name like
>>>>> > > bigtop-distro-select.
>>>>> > > > >> > >
>>>>> > > > >> > > Do you mean that you're
>> going to name the
>>>>> > > module (same as "component"
>>>>> > > > >> > > in the Bigtop
>> terminology, I think)
>>>>> > > bigtop-distro-select,
>>>>> > > > >> > > and still the script in
>> question
>>>>> > > bdp-select? If so, is there any
>>>>> > > > >> > > reason that the script
>> must be that name?
>>>>> > > > >> > > (No offence, I just want
>> to understand your
>>>>> > > thoughts and its
>>>>> > > > >> > > background, and avoid the
>> conflict or
>>>>> > > user's confusion with existing
>>>>> > > > >> > > trademarks or products)
>>>>> > > > >> > >
>>>>> > > > >> > > Kengo Seki <
>> sekikn@apache.org>
>>>>> > > > >> > >
>>>>> > > > >> > > On Thu, Jul 7, 2022 at
>> 2:08 AM Battula,
>>>>> > > Brahma Reddy
>>>>> > > > >> > > <bb...@visa.com.invalid>
>> wrote:
>>>>> > > > >> > > >
>>>>> > > > >> > > > > The name of stack
>> based no Bigtop
>>>>> > > should be Bigtop.
>>>>> > > > >> > > > > If you can not
>> accept the name like
>>>>> > > bigtop-*, the work should done outside of Bigtop.
>>>>> > > > >> > > > > I will cast -1 if
>> someone submit a
>>>>> > > patch to add a module with the name spoiling branding.
>>>>> > > > >> > > >
>>>>> > > > >> > > > Sure, we can have
>> module name like
>>>>> > > bigtop-distro-select.
>>>>> > > > >> > > > Initially we'll do this
>> separate branch.
>>>>> > > > >> > > >
>>>>> > > > >> > > >
>>>>> > > > >> > > >
>>>>> > > > >> > > > On 06/07/22, 8:55 AM,
>> "Masatake Iwasaki" <
>>>>> > > iwasakims@oss.nttdata.co.jp> wrote:
>>>>> > > > >> > > >
>>>>> > > > >> > > > > I believe it's
>> for project name.
>>>>> > > isn't it.?
>>>>> > > > >> > > >
>>>>> > > > >> > > > projects and
>> products.
>>>>> > > > >> > > >
>>>>> > > > >> > > > > IMO, We need to
>> create folders and
>>>>> > > refer stacknames so ambari-select,bigtop-select wn't
>> looks good.
>>>>> > > > >> > > >
>>>>> > > > >> > > > The name of stack
>> based no Bigtop
>>>>> > > should be Bigtop.
>>>>> > > > >> > > > If you can not
>> accept the name like
>>>>> > > bigtop-*, the work should done outside of Bigtop.
>>>>> > > > >> > > > I will cast -1 if
>> someone submit a
>>>>> > > patch to add a module with the name spoiling branding.
>>>>> > > > >> > > >
>>>>> > > > >> > > >
>>>>> > > > >> > > > On 2022/07/06
>> 11:44, Battula, Brahma
>>>>> > > Reddy wrote:
>>>>> > > > >> > > > >
>>>>> > > > >> > > > > I believe it's
>> for project name.
>>>>> > > isn't it.?
>>>>> > > > >> > > > >
>>>>> > > > >> > > > >
>>>>> > > > >> > > > > On 06/07/22, 7:27
>> AM, "Masatake
>>>>> > > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>>> > > > >> > > > >
>>>>> > > > >> > > > > > But As we
>> are not releasing
>>>>> > > as enterprise should be fine I think. IMO, We need to
>> create folders and
>>>>> > > refer stacknames so ambari-select,bigtop-select wn't
>> looks good.
>>>>> > > > >> > > > >
>>>>> > > > >> > > > > Not fine.
>>>>> > > > >> > > > > We have a
>> trademark policy.
>>>>> > > > >> > > > >
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
>>>>> > > > >> > > > >
>>>>> > > > >> > > > > On
>> 2022/07/06 10:37, Battula,
>>>>> > > Brahma Reddy wrote:
>>>>> > > > >> > > > > >> Should we
>> avoid
>>>>> > > unrecognized brand which may be trademark of someone?
>>>>> > > > >> > > > > >>
>> ambari-select or
>>>>> > > bigtop-select should be enough.
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > > Not sure,
>> where to confirm
>>>>> > > whether there is already trademark. When I googled found
>> so many.
>>>>> > > > >> > > > > > But As we
>> are not releasing
>>>>> > > as enterprise should be fine I think. IMO, We need to
>> create folders and
>>>>> > > refer stacknames so ambari-select,bigtop-select wn't
>> looks good.
>>>>> > > > >> > > > > > May be you
>> can refer the
>>>>> > > initial proposal [2] where I mentioned some more names.
>>>>> > > (BDS-BigDataStack,OSS-OpenSourceSelect..)
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > > Finally
>> thanks a bunch for
>>>>> > > long healthy discussions on this. Mostly we all same
>> page now.
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > > 1.
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > > 2.
>>>>> > >
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > > On
>> 06/07/22, 4:01 AM,
>>>>> > > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > > > We
>> have still not
>>>>> > > officially finalized the new replacement name for
>>>>> > > > >> > > > > > >
>> hdp-select, it would
>>>>> > > likely be bdp-select (bdp: BigData Platform). However,
>>>>> > > > >> > > > > > > the
>> purpose of
>>>>> > > bdp-select and conf-select remains the same.
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > >
>> Should we avoid
>>>>> > > unrecognized brand which may be trademark of someone?
>>>>> > > > >> > > > > >
>> ambari-select or
>>>>> > > bigtop-select should be enough.
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > > > On
>> 2022/06/29 13:52,
>>>>> > > Viraj Jasani wrote:
>>>>> > > > >> > > > > > > Hi
>> Ambari/Bigtop dev,
>>>>> > > > >> > > > > > >
>>>>> > > > >> > > > > > > As
>> per the new
>>>>> > > roadmap of Apache Ambari, we would like to propose moving
>>>>> > > > >> > > > > > >
>> certain scripts
>>>>> > > (previously known as hdp-select and conf-select) to
>> Bigtop
>>>>> > > > >> > > > > > > so
>> that their rpm
>>>>> > > installation could be managed independently.
>>>>> > > > >> > > > > > >
>> These scripts are a
>>>>> > > basic necessity in the Ambari framework for the
>>>>> > > > >> > > > > > >
>> installation of
>>>>> > > various Bigdata packages. The only major changes they
>> would
>>>>> > > > >> > > > > > >
>> receive is when we
>>>>> > > onboard new services and components to Ambari, else they
>>>>> > > > >> > > > > > >
>> usually do not
>>>>> > > receive updates. In the past, we used to get hdp-select
>> rpm
>>>>> > > > >> > > > > > >
>> downloaded and
>>>>> > > installed from HDP repositories.
>>>>> > > > >> > > > > > >
>>>>> > > > >> > > > > > > We
>> have still not
>>>>> > > officially finalized the new replacement name for
>>>>> > > > >> > > > > > >
>> hdp-select, it would
>>>>> > > likely be bdp-select (bdp: BigData Platform). However,
>>>>> > > > >> > > > > > > the
>> purpose of
>>>>> > > bdp-select and conf-select remains the same.
>>>>> > > > >> > > > > > >
>>>>> > > > >> > > > > >
>>>>> > > > >> > > > >
>>>>> > > > >> > > >
>>>>> > > > >> > > >
>>>>> > > > >> > > >
>>>>> > >
>> ---------------------------------------------------------------------
>>>>> > > > >> > > > To unsubscribe, e-mail:
>>>>> > > dev-unsubscribe@ambari.apache.org
>>>>> > > > >> > > > For additional
>> commands, e-mail:
>>>>> > > dev-help@ambari.apache.org
>>>>> > > > >> > > >
>>>>> > > > >> > >
>>>>> > > > >> > >
>>>>> > >
>> ---------------------------------------------------------------------
>>>>> > > > >> > > To unsubscribe, e-mail:
>>>>> > > dev-unsubscribe@ambari.apache.org
>>>>> > > > >> > > For additional commands,
>> e-mail:
>>>>> > > dev-help@ambari.apache.org
>>>>> > > > >> > >
>>>>> > > > >> > >
>>>>> > > > >> >
>>>>> > > > >> >
>>>>> > >
>> ---------------------------------------------------------------------
>>>>> > > > >> > To unsubscribe, e-mail:
>>>>> > > dev-unsubscribe@ambari.apache.org
>>>>> > > > >> > For additional commands, e-mail:
>>>>> > > dev-help@ambari.apache.org
>>>>> > > > >> >
>>>>> > > > >> >
>>>>> > > > >>
>>>>> > > > >>
>>>>> > >
>> ---------------------------------------------------------------------
>>>>> > > > >> To unsubscribe, e-mail:
>>>>> > > dev-unsubscribe@ambari.apache.org
>>>>> > > > >> For additional commands, e-mail:
>>>>> > > dev-help@ambari.apache.org
>>>>> > > > >>
>>>>> > > > >>
>>>>> > > >
>>>>> > > >
>>>>> > > >
>>>>> > >
>> ---------------------------------------------------------------------
>>>>> > > > To unsubscribe, e-mail:
>> dev-unsubscribe@ambari.apache.org
>>>>> > > > For additional commands, e-mail:
>> dev-help@ambari.apache.org
>>>>> > > >
>>>>> > > >
>>>>> > >
>>>>> >
>>>>> >
>>>>> >
>> ---------------------------------------------------------------------
>>>>> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>>>> > For additional commands, e-mail: dev-help@ambari.apache.org
>>>>> >
>>>>>
>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>>>> For additional commands, e-mail: dev-help@ambari.apache.org
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>>>> For additional commands, e-mail: dev-help@ambari.apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>>> For additional commands, e-mail: dev-help@ambari.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> For additional commands, e-mail: dev-help@ambari.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Brahma Reddy Battula <br...@apache.org>.
IMHO, Bigtop stack mpack was planned for trunk only. It could even merge
with a separate branch till it's stable.
On Thu, Sep 22, 2022 at 5:02 PM Masatake Iwasaki <iw...@oss.nttdata.com>
wrote:
> +1
>
> On 2022/09/21 11:12, 吴治国 wrote:
> > I think we have enough to go on with Kengo’s proposal,
> > Currently we don’t have enough developers(and I’m not willing to) to
> maintain a stack on our own like BDP.
> >
> >> Sure, here's my proposal:
> >>
> >> * Stack name: "BIGTOP"
> >>
> >> - The same name as the existing one [1]
> >> - Because it deploys the packages generated by Bigtop
> >> - The existing stack should be replaced with it, because that is
> >> based on Bigtop 0.8 and too old to use now
> >> - No concern about infringing others' trademark
> >>
> >> * Component/folder name: "bigtop-select"
> >>
> >> - Consistent naming convention with the existing tools such as
> >> "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> >> - If it sounds too simple and a bit unclear, a more descriptive name
> >> might be an option, for example "bigtop-ambari-stack-selector"
> >>
> >> * Script name: "bigtop-select"
> >>
> >> - Consistent with the stack name
> >> - No concern about infringing others' trademark
> >>
> >> [1]:
> https://github.com/apache/ambari/tree/release-2.7.6/ambari-server/src/main/resources/stacks/BIGTOP/0.8
> >> [2]:
> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common <
> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common>
> >
> > Best Regards,
> > Zhiguo Wu
> >
> >> On Sep 16, 2022, at 08:44, Masatake Iwasaki <iw...@oss.nttdata.com>
> wrote:
> >>
> >>
> >>>>> May be we can name it as bdp-select. Or (bgp-select)
> >>>> -1 as we already discussed.
> >>> Thanks for your feedback, I would definitely honour it. As you are not
> open for discussion and asked us raise the PR hence you thought of
> discussing on the PR. What will be your final suggestion on this..?
> >>
> >> I'm -1 on the name like bdp-select or bgp-select as we discussed.
> >> Feel free to open PR with appropriate module name.
> >>
> >> On 2022/09/05 16:30, Battula, Brahma Reddy wrote:
> >>> Hi @Masatake Iwasaki,
> >>>> -1 as we already discussed.
> >>> Thanks for your feedback, I would definitely honour it. As you are not
> open for discussion and asked us raise the PR hence you thought of
> discussing on the PR. What will be your final suggestion on this..?
> >>> @Roman Shaposhnik
> >>> I just gone through the following jira[1] where you brought ambari to
> bigtop. Looks stack-select is not included, how it was maintained.?
> >>> I thinking we should have one stack which can support for upgrading
> the existing the HDP deployed clusters. Even I can see somebody asking on
> bigtop[2].
> >>> If bigtop is not right place, shall we include in ambari..? Please
> let me know your thoughts on this. This blocks the 2.7.7 release.
> >>> Note : There is on-going ambari mpack which might take some more
> time. Even upgrades will take some time.
> >>> 1. https://issues.apache.org/jira/browse/BIGTOP-709
> >>> 2. https://issues.apache.org/jira/browse/BIGTOP-3651
> >>> Regards,
> >>> Brahma Reddy Battula
> >>> On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com>
> wrote:
> >>> > May be we can name it as bdp-select. Or (bgp-select)
> >>> -1 as we already discussed.
> >>> On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
> >>> > Ok, thanks Viraj.
> >>> >
> >>> > Hopefully you can place here like all other how it's
> maintained. Let me know any help required on this. May be we can name it as
> bdp-select. Or (bgp-select)
> >>> >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> >>> >
> >>> >
> >>> > On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org>
> wrote:
> >>> >
> >>> > Masatake, Brahma,
> >>> >
> >>> > Hopefully I should be able to create Jira and PR in
> Bigtop. Will let you
> >>> > know once ready for review. Thanks
> >>> >
> >>> >
> >>> > On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <
> iwasakims@oss.nttdata.com>
> >>> > wrote:
> >>> >
> >>> > > Please file a JIRA and submit a pull request if you want
> to show the code
> >>> > > and get feedback.
> >>> > > There is nothing I want to discuss off the record.
> >>> > >
> >>> > > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> >>> > > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and
> others, can we get
> >>> > > the final conclusion on this..?
> >>> > > >
> >>> > > > Please let me know your availability, Can have one
> call to discuss on
> >>> > > this..
> >>> > > >
> >>> > > >
> >>> > > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy"
> <bb...@visa.com.INVALID>
> >>> > > wrote:
> >>> > > >
> >>> > > > > -1 on development in branch.
> >>> > > > > It is not worth for maintaining the branch
> if the modules is
> >>> > > so small
> >>> > > > > and barely updated as explained here.
> >>> > > > > It should not conflict to existing code.
> >>> > > > > I feel I must check the code before
> check-in based on this
> >>> > > thread.
> >>> > > >
> >>> > > >
> >>> > > > Sure, Viraj or me can show the code to you.
> >>> > > >
> >>> > > > Can we've call on this Friday/Thrusday if that
> works..?
> >>> > > >
> >>> > > >
> >>> > > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> >>> > > iwasakims@oss.nttdata.com> wrote:
> >>> > > >
> >>> > > > > Sure, we can havemodule name like
> bigtop-distro-select.
> >>> > > > > Initially we'll do this separate branch.
> >>> > > >
> >>> > > > -1 on development in branch.
> >>> > > > It is not worth for maintaining the branch if
> the modules is so
> >>> > > small
> >>> > > > and barely updated as explained here.
> >>> > > > It should not conflict to existing code.
> >>> > > > I feel I must check the code before check-in
> based on this
> >>> > > thread.
> >>> > > >
> >>> > > > Masatake Iwasaki
> >>> > > >
> >>> > > > On 2022/07/11 8:23, Kengo Seki wrote:
> >>> > > > >> As there are different opinions on this
> and took long time,
> >>> > > just to brainstorm all the possibilities and pitfalls.
> >>> > > > >
> >>> > > > > Oh, I interpreted your words "conclude" and
> "finalize" as you
> >>> > > were
> >>> > > > > going to make a final decision.
> Brainstorming is welcome, of
> >>> > > course.
> >>> > > > > (But I'm not so sure if all people
> concerned could join, due
> >>> > > to time
> >>> > > > > difference and their schedule, etc.)
> >>> > > > >
> >>> > > > >> Can you suggest, how the changes will be
> also.. like folder,
> >>> > > where you suggest to keep this...?
> >>> > > > >
> >>> > > > > Sure, here's my proposal:
> >>> > > > >
> >>> > > > > * Stack name: "BIGTOP"
> >>> > > > >
> >>> > > > > - The same name as the existing one [1]
> >>> > > > > - Because it deploys the packages
> generated by Bigtop
> >>> > > > > - The existing stack should be replaced
> with it, because
> >>> > > that is
> >>> > > > > based on Bigtop 0.8 and too old to use now
> >>> > > > > - No concern about infringing others'
> trademark
> >>> > > > >
> >>> > > > > * Component/folder name: "bigtop-select"
> >>> > > > >
> >>> > > > > - Consistent naming convention with the
> existing tools
> >>> > > such as
> >>> > > > > "bigtop-groovy", "bigtop-jsvc",
> "bigtop-utils" [2]
> >>> > > > > - If it sounds too simple and a bit
> unclear, a more
> >>> > > descriptive name
> >>> > > > > might be an option, for example
> "bigtop-ambari-stack-selector"
> >>> > > > >
> >>> > > > > * Script name: "bigtop-select"
> >>> > > > >
> >>> > > > > - Consistent with the stack name
> >>> > > > > - No concern about infringing others'
> trademark
> >>> > > > >
> >>> > > > > [1]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
> >>> > > > > [2]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> >>> > > > >
> >>> > > > > Kengo Seki <se...@apache.org>
> >>> > > > >
> >>> > > > > On Mon, Jul 11, 2022 at 3:19 AM Battula,
> Brahma Reddy
> >>> > > > > <bb...@visa.com.invalid> wrote:
> >>> > > > >>
> >>> > > > >>> Technical decisions shouldn't be done
> on other places
> >>> > > than public mailing lists,
> >>> > > > >>> as described in the "Open
> Communications" section of [1]
> >>> > > and [2].
> >>> > > > >> > So we should conclude the discussion
> in this mailing
> >>> > > list.
> >>> > > > >> > (And with my poor English, I'm not so
> confident to catch
> >>> > > up with your
> >>> > > > >> > fluent talk ;)
> >>> > > > >>
> >>> > > > >> I believe , I knew the apache way which
> you mentioned. We
> >>> > > are not going conclude anything which comes to bigtop
> other than this
> >>> > > mailing list.
> >>> > > > >> As there are different opinions on this
> and took long time,
> >>> > > just to brainstorm all the possibilities and pitfalls.
> Hence asking let's
> >>> > > have call so that we can brainstorm. Even after call,
> everything will be
> >>> > > published what we discussed.
> >>> > > > >>
> >>> > > > >> I think, whiteboarding will help to catch
> up with you.
> >>> > > > >>
> >>> > > > >> You all the think "bigtop-select" will be
> best option
> >>> > > right..? Can you suggest, how the changes will be also..
> like folder, where
> >>> > > you suggest to keep this...?
> >>> > > > >>
> >>> > > > >> And if the name represents the stack which
> we are going to
> >>> > > deploy should fine I feel.. (if it's not BDP, may be
> >>> > > OBDP:OpensourceBigDataPlatform.)
> >>> > > > >>
> >>> > > > >> @Viraj Jasani and others any thoughts..?
> >>> > > > >>
> >>> > > > >>
> >>> > > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <
> sekikn@apache.org>
> >>> > > wrote:
> >>> > > > >>
> >>> > > > >> > Looks we had so much discussed
> here, Let's try to
> >>> > > conclude. Can we've one call on this and finalize this..?
> >>> > > > >>
> >>> > > > >> Technical decisions shouldn't be done
> on other places
> >>> > > than public mailing lists,
> >>> > > > >> as described in the "Open
> Communications" section of
> >>> > > [1] and [2].
> >>> > > > >> So we should conclude the discussion
> in this mailing
> >>> > > list.
> >>> > > > >> (And with my poor English, I'm not so
> confident to
> >>> > > catch up with your
> >>> > > > >> fluent talk ;)
> >>> > > > >>
> >>> > > > >> > FYI. Even looks bigtop used some
> where also..
> >>> > > > >>
> >>> > > > >> Bigtop is ASF's trademark as you can
> see in the "Apache
> >>> > > Bigtop®
> >>> > > > >> software" section of [3].
> >>> > > > >> So it doesn't have the risk of
> trademark infringement.
> >>> > > > >>
> >>> > > > >> [1]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
> >>> > > > >> [2]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
> >>> > > > >> [3]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
> >>> > > > >>
> >>> > > > >> Kengo Seki <se...@apache.org>
> >>> > > > >>
> >>> > > > >> On Sun, Jul 10, 2022 at 4:11 AM
> Battula, Brahma Reddy
> >>> > > > >> <bb...@visa.com.invalid> wrote:
> >>> > > > >> >
> >>> > > > >> > Looks we had so much discussed
> here, Let's try to
> >>> > > conclude. Can we've one call on this and finalize this..?
> >>> > > > >> >
> >>> > > > >> > FYI. Even looks bigtop used some
> where[1] also..
> >>> > > > >> > 1.
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
> >>> > > > >> >
> >>> > > > >> >
> >>> > > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <
> sekikn@apache.org>
> >>> > > wrote:
> >>> > > > >> >
> >>> > > > >> > Thank you for your explanation,
> Brahma.
> >>> > > > >> > CRH (abbreviation of "CHINA
> REDOOP HYPERLOOP"
> >>> > > [1]) is supposed to be a
> >>> > > > >> > trademark of Redoop, so they
> can name the script
> >>> > > crh-select without
> >>> > > > >> > problem.
> >>> > > > >> > But regarding BDP for example,
> I can easily find
> >>> > > products that have
> >>> > > > >> > the same name [2][3][4] as you
> already mentioned,
> >>> > > so I'd like to
> >>> > > > >> > recommend bigtop-select for
> avoiding unnecessary
> >>> > > trouble.
> >>> > > > >> > Or, a single and more general
> word just like
> >>> > > conf-select may be less
> >>> > > > >> > troublesome than bdp. How about
> "stack-select",
> >>> > > for example?
> >>> > > > >> >
> >>> > > > >> > [1]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
> >>> > > > >> > [2]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
> >>> > > > >> > [3]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
> >>> > > > >> > [4]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
> >>> > > > >> >
> >>> > > > >> > Kengo Seki <se...@apache.org>
> >>> > > > >> >
> >>> > > > >> > On Fri, Jul 8, 2022 at 2:51 AM
> Battula, Brahma
> >>> > > Reddy <bb...@visa.com> wrote:
> >>> > > > >> > >
> >>> > > > >> > > >Do you mean that you're
> going to name the
> >>> > > module (same as "component"
> >>> > > > >> > > >in the Bigtop
> terminology, I think)
> >>> > > bigtop-distro-select,
> >>> > > > >> > > >and still the script in
> question
> >>> > > bdp-select? If so, is there any
> >>> > > > >> > > >reason that the script
> must be that name?
> >>> > > > >> > > >(No offence, I just want
> to understand
> >>> > > your thoughts and its
> >>> > > > >> > > >background, and avoid
> the conflict or
> >>> > > user's confusion with existing
> >>> > > > >> > > >trademarks or products)
> >>> > > > >> > >
> >>> > > > >> > > Thanks @Kengo Seki for
> consolidating all the
> >>> > > concerns. Name should represent the stack which includes
> all the components
> >>> > > hence planning to have like bdp,bds...and this only one
> file like below[1]
> >>> > > which has done redoop.
> >>> > > > >> > >
> >>> > > > >> > >
> >>> > > > >> > >
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
> >>> > > > >> > >
> >>> > > > >> > >
> >>> > > > >> > > On 07/07/22, 6:07 AM, "Kengo
> Seki" <
> >>> > > sekikn@apache.org> wrote:
> >>> > > > >> > >
> >>> > > > >> > > The following concern
> Masatake mentioned
> >>> > > before is an important point,
> >>> > > > >> > > so I talked to Brahma for
> clarifying his
> >>> > > intention on the ASF Slack
> >>> > > > >> > > yesterday.
> >>> > > > >> > >
> >>> > > > >> > > > Multiple versions of
> the same package
> >>> > > (deb/rpm) can not be installed at the same time.
> >>> > > > >> > > > IIRC, HDP uses
> convention in which the
> >>> > > product version is part of package name
> >>> > > > >> > > > for addressing this.
> >>> > > > >> > >
> >>> > > > >> > > > I don't like to bring
> the awkward package
> >>> > > name convention to Bigtop
> >>> > > > >> > > > at least by default.
> >>> > > > >> > >
> >>> > > > >> > > He's planning to adopt
> the same mitigation
> >>> > > as HDP for now, but he
> >>> > > > >> > > doesn't intend to change
> the default
> >>> > > package naming convention of
> >>> > > > >> > > Bigtop,
> >>> > > > >> > > but just add a new
> functionality to include
> >>> > > an extra part into the
> >>> > > > >> > > package name for avoiding
> conflict, which
> >>> > > is disabled by default.
> >>> > > > >> > >
> >>> > > > >> > > And Brahma, let me
> confirm about the
> >>> > > following reply:
> >>> > > > >> > >
> >>> > > > >> > > > Sure, we can have
> module name like
> >>> > > bigtop-distro-select.
> >>> > > > >> > >
> >>> > > > >> > > Do you mean that you're
> going to name the
> >>> > > module (same as "component"
> >>> > > > >> > > in the Bigtop
> terminology, I think)
> >>> > > bigtop-distro-select,
> >>> > > > >> > > and still the script in
> question
> >>> > > bdp-select? If so, is there any
> >>> > > > >> > > reason that the script
> must be that name?
> >>> > > > >> > > (No offence, I just want
> to understand your
> >>> > > thoughts and its
> >>> > > > >> > > background, and avoid the
> conflict or
> >>> > > user's confusion with existing
> >>> > > > >> > > trademarks or products)
> >>> > > > >> > >
> >>> > > > >> > > Kengo Seki <
> sekikn@apache.org>
> >>> > > > >> > >
> >>> > > > >> > > On Thu, Jul 7, 2022 at
> 2:08 AM Battula,
> >>> > > Brahma Reddy
> >>> > > > >> > > <bb...@visa.com.invalid>
> wrote:
> >>> > > > >> > > >
> >>> > > > >> > > > > The name of stack
> based no Bigtop
> >>> > > should be Bigtop.
> >>> > > > >> > > > > If you can not
> accept the name like
> >>> > > bigtop-*, the work should done outside of Bigtop.
> >>> > > > >> > > > > I will cast -1 if
> someone submit a
> >>> > > patch to add a module with the name spoiling branding.
> >>> > > > >> > > >
> >>> > > > >> > > > Sure, we can have
> module name like
> >>> > > bigtop-distro-select.
> >>> > > > >> > > > Initially we'll do this
> separate branch.
> >>> > > > >> > > >
> >>> > > > >> > > >
> >>> > > > >> > > >
> >>> > > > >> > > > On 06/07/22, 8:55 AM,
> "Masatake Iwasaki" <
> >>> > > iwasakims@oss.nttdata.co.jp> wrote:
> >>> > > > >> > > >
> >>> > > > >> > > > > I believe it's
> for project name.
> >>> > > isn't it.?
> >>> > > > >> > > >
> >>> > > > >> > > > projects and
> products.
> >>> > > > >> > > >
> >>> > > > >> > > > > IMO, We need to
> create folders and
> >>> > > refer stacknames so ambari-select,bigtop-select wn't
> looks good.
> >>> > > > >> > > >
> >>> > > > >> > > > The name of stack
> based no Bigtop
> >>> > > should be Bigtop.
> >>> > > > >> > > > If you can not
> accept the name like
> >>> > > bigtop-*, the work should done outside of Bigtop.
> >>> > > > >> > > > I will cast -1 if
> someone submit a
> >>> > > patch to add a module with the name spoiling branding.
> >>> > > > >> > > >
> >>> > > > >> > > >
> >>> > > > >> > > > On 2022/07/06
> 11:44, Battula, Brahma
> >>> > > Reddy wrote:
> >>> > > > >> > > > >
> >>> > > > >> > > > > I believe it's
> for project name.
> >>> > > isn't it.?
> >>> > > > >> > > > >
> >>> > > > >> > > > >
> >>> > > > >> > > > > On 06/07/22, 7:27
> AM, "Masatake
> >>> > > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >>> > > > >> > > > >
> >>> > > > >> > > > > > But As we
> are not releasing
> >>> > > as enterprise should be fine I think. IMO, We need to
> create folders and
> >>> > > refer stacknames so ambari-select,bigtop-select wn't
> looks good.
> >>> > > > >> > > > >
> >>> > > > >> > > > > Not fine.
> >>> > > > >> > > > > We have a
> trademark policy.
> >>> > > > >> > > > >
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
> >>> > > > >> > > > >
> >>> > > > >> > > > > On
> 2022/07/06 10:37, Battula,
> >>> > > Brahma Reddy wrote:
> >>> > > > >> > > > > >> Should we
> avoid
> >>> > > unrecognized brand which may be trademark of someone?
> >>> > > > >> > > > > >>
> ambari-select or
> >>> > > bigtop-select should be enough.
> >>> > > > >> > > > > >
> >>> > > > >> > > > > > Not sure,
> where to confirm
> >>> > > whether there is already trademark. When I googled found
> so many.
> >>> > > > >> > > > > > But As we
> are not releasing
> >>> > > as enterprise should be fine I think. IMO, We need to
> create folders and
> >>> > > refer stacknames so ambari-select,bigtop-select wn't
> looks good.
> >>> > > > >> > > > > > May be you
> can refer the
> >>> > > initial proposal [2] where I mentioned some more names.
> >>> > > (BDS-BigDataStack,OSS-OpenSourceSelect..)
> >>> > > > >> > > > > >
> >>> > > > >> > > > > > Finally
> thanks a bunch for
> >>> > > long healthy discussions on this. Mostly we all same
> page now.
> >>> > > > >> > > > > >
> >>> > > > >> > > > > > 1.
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
> >>> > > > >> > > > > >
> >>> > > > >> > > > > > 2.
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
> >>> > > > >> > > > > >
> >>> > > > >> > > > > >
> >>> > > > >> > > > > > On
> 06/07/22, 4:01 AM,
> >>> > > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >>> > > > >> > > > > >
> >>> > > > >> > > > > > > We
> have still not
> >>> > > officially finalized the new replacement name for
> >>> > > > >> > > > > > >
> hdp-select, it would
> >>> > > likely be bdp-select (bdp: BigData Platform). However,
> >>> > > > >> > > > > > > the
> purpose of
> >>> > > bdp-select and conf-select remains the same.
> >>> > > > >> > > > > >
> >>> > > > >> > > > > >
> Should we avoid
> >>> > > unrecognized brand which may be trademark of someone?
> >>> > > > >> > > > > >
> ambari-select or
> >>> > > bigtop-select should be enough.
> >>> > > > >> > > > > >
> >>> > > > >> > > > > > On
> 2022/06/29 13:52,
> >>> > > Viraj Jasani wrote:
> >>> > > > >> > > > > > > Hi
> Ambari/Bigtop dev,
> >>> > > > >> > > > > > >
> >>> > > > >> > > > > > > As
> per the new
> >>> > > roadmap of Apache Ambari, we would like to propose moving
> >>> > > > >> > > > > > >
> certain scripts
> >>> > > (previously known as hdp-select and conf-select) to
> Bigtop
> >>> > > > >> > > > > > > so
> that their rpm
> >>> > > installation could be managed independently.
> >>> > > > >> > > > > > >
> These scripts are a
> >>> > > basic necessity in the Ambari framework for the
> >>> > > > >> > > > > > >
> installation of
> >>> > > various Bigdata packages. The only major changes they
> would
> >>> > > > >> > > > > > >
> receive is when we
> >>> > > onboard new services and components to Ambari, else they
> >>> > > > >> > > > > > >
> usually do not
> >>> > > receive updates. In the past, we used to get hdp-select
> rpm
> >>> > > > >> > > > > > >
> downloaded and
> >>> > > installed from HDP repositories.
> >>> > > > >> > > > > > >
> >>> > > > >> > > > > > > We
> have still not
> >>> > > officially finalized the new replacement name for
> >>> > > > >> > > > > > >
> hdp-select, it would
> >>> > > likely be bdp-select (bdp: BigData Platform). However,
> >>> > > > >> > > > > > > the
> purpose of
> >>> > > bdp-select and conf-select remains the same.
> >>> > > > >> > > > > > >
> >>> > > > >> > > > > >
> >>> > > > >> > > > >
> >>> > > > >> > > >
> >>> > > > >> > > >
> >>> > > > >> > > >
> >>> > >
> ---------------------------------------------------------------------
> >>> > > > >> > > > To unsubscribe, e-mail:
> >>> > > dev-unsubscribe@ambari.apache.org
> >>> > > > >> > > > For additional
> commands, e-mail:
> >>> > > dev-help@ambari.apache.org
> >>> > > > >> > > >
> >>> > > > >> > >
> >>> > > > >> > >
> >>> > >
> ---------------------------------------------------------------------
> >>> > > > >> > > To unsubscribe, e-mail:
> >>> > > dev-unsubscribe@ambari.apache.org
> >>> > > > >> > > For additional commands,
> e-mail:
> >>> > > dev-help@ambari.apache.org
> >>> > > > >> > >
> >>> > > > >> > >
> >>> > > > >> >
> >>> > > > >> >
> >>> > >
> ---------------------------------------------------------------------
> >>> > > > >> > To unsubscribe, e-mail:
> >>> > > dev-unsubscribe@ambari.apache.org
> >>> > > > >> > For additional commands, e-mail:
> >>> > > dev-help@ambari.apache.org
> >>> > > > >> >
> >>> > > > >> >
> >>> > > > >>
> >>> > > > >>
> >>> > >
> ---------------------------------------------------------------------
> >>> > > > >> To unsubscribe, e-mail:
> >>> > > dev-unsubscribe@ambari.apache.org
> >>> > > > >> For additional commands, e-mail:
> >>> > > dev-help@ambari.apache.org
> >>> > > > >>
> >>> > > > >>
> >>> > > >
> >>> > > >
> >>> > > >
> >>> > >
> ---------------------------------------------------------------------
> >>> > > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> >>> > > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> >>> > > >
> >>> > > >
> >>> > >
> >>> >
> >>> >
> >>> >
> ---------------------------------------------------------------------
> >>> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >>> > For additional commands, e-mail: dev-help@ambari.apache.org
> >>> >
> >>>
> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >>> For additional commands, e-mail: dev-help@ambari.apache.org
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >>> For additional commands, e-mail: dev-help@ambari.apache.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> For additional commands, e-mail: dev-help@ambari.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Brahma Reddy Battula <br...@apache.org>.
IMHO, Bigtop stack mpack was planned for trunk only. It could even merge
with a separate branch till it's stable.
On Thu, Sep 22, 2022 at 5:02 PM Masatake Iwasaki <iw...@oss.nttdata.com>
wrote:
> +1
>
> On 2022/09/21 11:12, 吴治国 wrote:
> > I think we have enough to go on with Kengo’s proposal,
> > Currently we don’t have enough developers(and I’m not willing to) to
> maintain a stack on our own like BDP.
> >
> >> Sure, here's my proposal:
> >>
> >> * Stack name: "BIGTOP"
> >>
> >> - The same name as the existing one [1]
> >> - Because it deploys the packages generated by Bigtop
> >> - The existing stack should be replaced with it, because that is
> >> based on Bigtop 0.8 and too old to use now
> >> - No concern about infringing others' trademark
> >>
> >> * Component/folder name: "bigtop-select"
> >>
> >> - Consistent naming convention with the existing tools such as
> >> "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> >> - If it sounds too simple and a bit unclear, a more descriptive name
> >> might be an option, for example "bigtop-ambari-stack-selector"
> >>
> >> * Script name: "bigtop-select"
> >>
> >> - Consistent with the stack name
> >> - No concern about infringing others' trademark
> >>
> >> [1]:
> https://github.com/apache/ambari/tree/release-2.7.6/ambari-server/src/main/resources/stacks/BIGTOP/0.8
> >> [2]:
> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common <
> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common>
> >
> > Best Regards,
> > Zhiguo Wu
> >
> >> On Sep 16, 2022, at 08:44, Masatake Iwasaki <iw...@oss.nttdata.com>
> wrote:
> >>
> >>
> >>>>> May be we can name it as bdp-select. Or (bgp-select)
> >>>> -1 as we already discussed.
> >>> Thanks for your feedback, I would definitely honour it. As you are not
> open for discussion and asked us raise the PR hence you thought of
> discussing on the PR. What will be your final suggestion on this..?
> >>
> >> I'm -1 on the name like bdp-select or bgp-select as we discussed.
> >> Feel free to open PR with appropriate module name.
> >>
> >> On 2022/09/05 16:30, Battula, Brahma Reddy wrote:
> >>> Hi @Masatake Iwasaki,
> >>>> -1 as we already discussed.
> >>> Thanks for your feedback, I would definitely honour it. As you are not
> open for discussion and asked us raise the PR hence you thought of
> discussing on the PR. What will be your final suggestion on this..?
> >>> @Roman Shaposhnik
> >>> I just gone through the following jira[1] where you brought ambari to
> bigtop. Looks stack-select is not included, how it was maintained.?
> >>> I thinking we should have one stack which can support for upgrading
> the existing the HDP deployed clusters. Even I can see somebody asking on
> bigtop[2].
> >>> If bigtop is not right place, shall we include in ambari..? Please
> let me know your thoughts on this. This blocks the 2.7.7 release.
> >>> Note : There is on-going ambari mpack which might take some more
> time. Even upgrades will take some time.
> >>> 1. https://issues.apache.org/jira/browse/BIGTOP-709
> >>> 2. https://issues.apache.org/jira/browse/BIGTOP-3651
> >>> Regards,
> >>> Brahma Reddy Battula
> >>> On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com>
> wrote:
> >>> > May be we can name it as bdp-select. Or (bgp-select)
> >>> -1 as we already discussed.
> >>> On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
> >>> > Ok, thanks Viraj.
> >>> >
> >>> > Hopefully you can place here like all other how it's
> maintained. Let me know any help required on this. May be we can name it as
> bdp-select. Or (bgp-select)
> >>> >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> >>> >
> >>> >
> >>> > On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org>
> wrote:
> >>> >
> >>> > Masatake, Brahma,
> >>> >
> >>> > Hopefully I should be able to create Jira and PR in
> Bigtop. Will let you
> >>> > know once ready for review. Thanks
> >>> >
> >>> >
> >>> > On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <
> iwasakims@oss.nttdata.com>
> >>> > wrote:
> >>> >
> >>> > > Please file a JIRA and submit a pull request if you want
> to show the code
> >>> > > and get feedback.
> >>> > > There is nothing I want to discuss off the record.
> >>> > >
> >>> > > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> >>> > > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and
> others, can we get
> >>> > > the final conclusion on this..?
> >>> > > >
> >>> > > > Please let me know your availability, Can have one
> call to discuss on
> >>> > > this..
> >>> > > >
> >>> > > >
> >>> > > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy"
> <bb...@visa.com.INVALID>
> >>> > > wrote:
> >>> > > >
> >>> > > > > -1 on development in branch.
> >>> > > > > It is not worth for maintaining the branch
> if the modules is
> >>> > > so small
> >>> > > > > and barely updated as explained here.
> >>> > > > > It should not conflict to existing code.
> >>> > > > > I feel I must check the code before
> check-in based on this
> >>> > > thread.
> >>> > > >
> >>> > > >
> >>> > > > Sure, Viraj or me can show the code to you.
> >>> > > >
> >>> > > > Can we've call on this Friday/Thrusday if that
> works..?
> >>> > > >
> >>> > > >
> >>> > > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> >>> > > iwasakims@oss.nttdata.com> wrote:
> >>> > > >
> >>> > > > > Sure, we can havemodule name like
> bigtop-distro-select.
> >>> > > > > Initially we'll do this separate branch.
> >>> > > >
> >>> > > > -1 on development in branch.
> >>> > > > It is not worth for maintaining the branch if
> the modules is so
> >>> > > small
> >>> > > > and barely updated as explained here.
> >>> > > > It should not conflict to existing code.
> >>> > > > I feel I must check the code before check-in
> based on this
> >>> > > thread.
> >>> > > >
> >>> > > > Masatake Iwasaki
> >>> > > >
> >>> > > > On 2022/07/11 8:23, Kengo Seki wrote:
> >>> > > > >> As there are different opinions on this
> and took long time,
> >>> > > just to brainstorm all the possibilities and pitfalls.
> >>> > > > >
> >>> > > > > Oh, I interpreted your words "conclude" and
> "finalize" as you
> >>> > > were
> >>> > > > > going to make a final decision.
> Brainstorming is welcome, of
> >>> > > course.
> >>> > > > > (But I'm not so sure if all people
> concerned could join, due
> >>> > > to time
> >>> > > > > difference and their schedule, etc.)
> >>> > > > >
> >>> > > > >> Can you suggest, how the changes will be
> also.. like folder,
> >>> > > where you suggest to keep this...?
> >>> > > > >
> >>> > > > > Sure, here's my proposal:
> >>> > > > >
> >>> > > > > * Stack name: "BIGTOP"
> >>> > > > >
> >>> > > > > - The same name as the existing one [1]
> >>> > > > > - Because it deploys the packages
> generated by Bigtop
> >>> > > > > - The existing stack should be replaced
> with it, because
> >>> > > that is
> >>> > > > > based on Bigtop 0.8 and too old to use now
> >>> > > > > - No concern about infringing others'
> trademark
> >>> > > > >
> >>> > > > > * Component/folder name: "bigtop-select"
> >>> > > > >
> >>> > > > > - Consistent naming convention with the
> existing tools
> >>> > > such as
> >>> > > > > "bigtop-groovy", "bigtop-jsvc",
> "bigtop-utils" [2]
> >>> > > > > - If it sounds too simple and a bit
> unclear, a more
> >>> > > descriptive name
> >>> > > > > might be an option, for example
> "bigtop-ambari-stack-selector"
> >>> > > > >
> >>> > > > > * Script name: "bigtop-select"
> >>> > > > >
> >>> > > > > - Consistent with the stack name
> >>> > > > > - No concern about infringing others'
> trademark
> >>> > > > >
> >>> > > > > [1]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
> >>> > > > > [2]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> >>> > > > >
> >>> > > > > Kengo Seki <se...@apache.org>
> >>> > > > >
> >>> > > > > On Mon, Jul 11, 2022 at 3:19 AM Battula,
> Brahma Reddy
> >>> > > > > <bb...@visa.com.invalid> wrote:
> >>> > > > >>
> >>> > > > >>> Technical decisions shouldn't be done
> on other places
> >>> > > than public mailing lists,
> >>> > > > >>> as described in the "Open
> Communications" section of [1]
> >>> > > and [2].
> >>> > > > >> > So we should conclude the discussion
> in this mailing
> >>> > > list.
> >>> > > > >> > (And with my poor English, I'm not so
> confident to catch
> >>> > > up with your
> >>> > > > >> > fluent talk ;)
> >>> > > > >>
> >>> > > > >> I believe , I knew the apache way which
> you mentioned. We
> >>> > > are not going conclude anything which comes to bigtop
> other than this
> >>> > > mailing list.
> >>> > > > >> As there are different opinions on this
> and took long time,
> >>> > > just to brainstorm all the possibilities and pitfalls.
> Hence asking let's
> >>> > > have call so that we can brainstorm. Even after call,
> everything will be
> >>> > > published what we discussed.
> >>> > > > >>
> >>> > > > >> I think, whiteboarding will help to catch
> up with you.
> >>> > > > >>
> >>> > > > >> You all the think "bigtop-select" will be
> best option
> >>> > > right..? Can you suggest, how the changes will be also..
> like folder, where
> >>> > > you suggest to keep this...?
> >>> > > > >>
> >>> > > > >> And if the name represents the stack which
> we are going to
> >>> > > deploy should fine I feel.. (if it's not BDP, may be
> >>> > > OBDP:OpensourceBigDataPlatform.)
> >>> > > > >>
> >>> > > > >> @Viraj Jasani and others any thoughts..?
> >>> > > > >>
> >>> > > > >>
> >>> > > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <
> sekikn@apache.org>
> >>> > > wrote:
> >>> > > > >>
> >>> > > > >> > Looks we had so much discussed
> here, Let's try to
> >>> > > conclude. Can we've one call on this and finalize this..?
> >>> > > > >>
> >>> > > > >> Technical decisions shouldn't be done
> on other places
> >>> > > than public mailing lists,
> >>> > > > >> as described in the "Open
> Communications" section of
> >>> > > [1] and [2].
> >>> > > > >> So we should conclude the discussion
> in this mailing
> >>> > > list.
> >>> > > > >> (And with my poor English, I'm not so
> confident to
> >>> > > catch up with your
> >>> > > > >> fluent talk ;)
> >>> > > > >>
> >>> > > > >> > FYI. Even looks bigtop used some
> where also..
> >>> > > > >>
> >>> > > > >> Bigtop is ASF's trademark as you can
> see in the "Apache
> >>> > > Bigtop®
> >>> > > > >> software" section of [3].
> >>> > > > >> So it doesn't have the risk of
> trademark infringement.
> >>> > > > >>
> >>> > > > >> [1]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
> >>> > > > >> [2]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
> >>> > > > >> [3]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
> >>> > > > >>
> >>> > > > >> Kengo Seki <se...@apache.org>
> >>> > > > >>
> >>> > > > >> On Sun, Jul 10, 2022 at 4:11 AM
> Battula, Brahma Reddy
> >>> > > > >> <bb...@visa.com.invalid> wrote:
> >>> > > > >> >
> >>> > > > >> > Looks we had so much discussed
> here, Let's try to
> >>> > > conclude. Can we've one call on this and finalize this..?
> >>> > > > >> >
> >>> > > > >> > FYI. Even looks bigtop used some
> where[1] also..
> >>> > > > >> > 1.
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
> >>> > > > >> >
> >>> > > > >> >
> >>> > > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <
> sekikn@apache.org>
> >>> > > wrote:
> >>> > > > >> >
> >>> > > > >> > Thank you for your explanation,
> Brahma.
> >>> > > > >> > CRH (abbreviation of "CHINA
> REDOOP HYPERLOOP"
> >>> > > [1]) is supposed to be a
> >>> > > > >> > trademark of Redoop, so they
> can name the script
> >>> > > crh-select without
> >>> > > > >> > problem.
> >>> > > > >> > But regarding BDP for example,
> I can easily find
> >>> > > products that have
> >>> > > > >> > the same name [2][3][4] as you
> already mentioned,
> >>> > > so I'd like to
> >>> > > > >> > recommend bigtop-select for
> avoiding unnecessary
> >>> > > trouble.
> >>> > > > >> > Or, a single and more general
> word just like
> >>> > > conf-select may be less
> >>> > > > >> > troublesome than bdp. How about
> "stack-select",
> >>> > > for example?
> >>> > > > >> >
> >>> > > > >> > [1]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
> >>> > > > >> > [2]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
> >>> > > > >> > [3]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
> >>> > > > >> > [4]:
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
> >>> > > > >> >
> >>> > > > >> > Kengo Seki <se...@apache.org>
> >>> > > > >> >
> >>> > > > >> > On Fri, Jul 8, 2022 at 2:51 AM
> Battula, Brahma
> >>> > > Reddy <bb...@visa.com> wrote:
> >>> > > > >> > >
> >>> > > > >> > > >Do you mean that you're
> going to name the
> >>> > > module (same as "component"
> >>> > > > >> > > >in the Bigtop
> terminology, I think)
> >>> > > bigtop-distro-select,
> >>> > > > >> > > >and still the script in
> question
> >>> > > bdp-select? If so, is there any
> >>> > > > >> > > >reason that the script
> must be that name?
> >>> > > > >> > > >(No offence, I just want
> to understand
> >>> > > your thoughts and its
> >>> > > > >> > > >background, and avoid
> the conflict or
> >>> > > user's confusion with existing
> >>> > > > >> > > >trademarks or products)
> >>> > > > >> > >
> >>> > > > >> > > Thanks @Kengo Seki for
> consolidating all the
> >>> > > concerns. Name should represent the stack which includes
> all the components
> >>> > > hence planning to have like bdp,bds...and this only one
> file like below[1]
> >>> > > which has done redoop.
> >>> > > > >> > >
> >>> > > > >> > >
> >>> > > > >> > >
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
> >>> > > > >> > >
> >>> > > > >> > >
> >>> > > > >> > > On 07/07/22, 6:07 AM, "Kengo
> Seki" <
> >>> > > sekikn@apache.org> wrote:
> >>> > > > >> > >
> >>> > > > >> > > The following concern
> Masatake mentioned
> >>> > > before is an important point,
> >>> > > > >> > > so I talked to Brahma for
> clarifying his
> >>> > > intention on the ASF Slack
> >>> > > > >> > > yesterday.
> >>> > > > >> > >
> >>> > > > >> > > > Multiple versions of
> the same package
> >>> > > (deb/rpm) can not be installed at the same time.
> >>> > > > >> > > > IIRC, HDP uses
> convention in which the
> >>> > > product version is part of package name
> >>> > > > >> > > > for addressing this.
> >>> > > > >> > >
> >>> > > > >> > > > I don't like to bring
> the awkward package
> >>> > > name convention to Bigtop
> >>> > > > >> > > > at least by default.
> >>> > > > >> > >
> >>> > > > >> > > He's planning to adopt
> the same mitigation
> >>> > > as HDP for now, but he
> >>> > > > >> > > doesn't intend to change
> the default
> >>> > > package naming convention of
> >>> > > > >> > > Bigtop,
> >>> > > > >> > > but just add a new
> functionality to include
> >>> > > an extra part into the
> >>> > > > >> > > package name for avoiding
> conflict, which
> >>> > > is disabled by default.
> >>> > > > >> > >
> >>> > > > >> > > And Brahma, let me
> confirm about the
> >>> > > following reply:
> >>> > > > >> > >
> >>> > > > >> > > > Sure, we can have
> module name like
> >>> > > bigtop-distro-select.
> >>> > > > >> > >
> >>> > > > >> > > Do you mean that you're
> going to name the
> >>> > > module (same as "component"
> >>> > > > >> > > in the Bigtop
> terminology, I think)
> >>> > > bigtop-distro-select,
> >>> > > > >> > > and still the script in
> question
> >>> > > bdp-select? If so, is there any
> >>> > > > >> > > reason that the script
> must be that name?
> >>> > > > >> > > (No offence, I just want
> to understand your
> >>> > > thoughts and its
> >>> > > > >> > > background, and avoid the
> conflict or
> >>> > > user's confusion with existing
> >>> > > > >> > > trademarks or products)
> >>> > > > >> > >
> >>> > > > >> > > Kengo Seki <
> sekikn@apache.org>
> >>> > > > >> > >
> >>> > > > >> > > On Thu, Jul 7, 2022 at
> 2:08 AM Battula,
> >>> > > Brahma Reddy
> >>> > > > >> > > <bb...@visa.com.invalid>
> wrote:
> >>> > > > >> > > >
> >>> > > > >> > > > > The name of stack
> based no Bigtop
> >>> > > should be Bigtop.
> >>> > > > >> > > > > If you can not
> accept the name like
> >>> > > bigtop-*, the work should done outside of Bigtop.
> >>> > > > >> > > > > I will cast -1 if
> someone submit a
> >>> > > patch to add a module with the name spoiling branding.
> >>> > > > >> > > >
> >>> > > > >> > > > Sure, we can have
> module name like
> >>> > > bigtop-distro-select.
> >>> > > > >> > > > Initially we'll do this
> separate branch.
> >>> > > > >> > > >
> >>> > > > >> > > >
> >>> > > > >> > > >
> >>> > > > >> > > > On 06/07/22, 8:55 AM,
> "Masatake Iwasaki" <
> >>> > > iwasakims@oss.nttdata.co.jp> wrote:
> >>> > > > >> > > >
> >>> > > > >> > > > > I believe it's
> for project name.
> >>> > > isn't it.?
> >>> > > > >> > > >
> >>> > > > >> > > > projects and
> products.
> >>> > > > >> > > >
> >>> > > > >> > > > > IMO, We need to
> create folders and
> >>> > > refer stacknames so ambari-select,bigtop-select wn't
> looks good.
> >>> > > > >> > > >
> >>> > > > >> > > > The name of stack
> based no Bigtop
> >>> > > should be Bigtop.
> >>> > > > >> > > > If you can not
> accept the name like
> >>> > > bigtop-*, the work should done outside of Bigtop.
> >>> > > > >> > > > I will cast -1 if
> someone submit a
> >>> > > patch to add a module with the name spoiling branding.
> >>> > > > >> > > >
> >>> > > > >> > > >
> >>> > > > >> > > > On 2022/07/06
> 11:44, Battula, Brahma
> >>> > > Reddy wrote:
> >>> > > > >> > > > >
> >>> > > > >> > > > > I believe it's
> for project name.
> >>> > > isn't it.?
> >>> > > > >> > > > >
> >>> > > > >> > > > >
> >>> > > > >> > > > > On 06/07/22, 7:27
> AM, "Masatake
> >>> > > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >>> > > > >> > > > >
> >>> > > > >> > > > > > But As we
> are not releasing
> >>> > > as enterprise should be fine I think. IMO, We need to
> create folders and
> >>> > > refer stacknames so ambari-select,bigtop-select wn't
> looks good.
> >>> > > > >> > > > >
> >>> > > > >> > > > > Not fine.
> >>> > > > >> > > > > We have a
> trademark policy.
> >>> > > > >> > > > >
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
> >>> > > > >> > > > >
> >>> > > > >> > > > > On
> 2022/07/06 10:37, Battula,
> >>> > > Brahma Reddy wrote:
> >>> > > > >> > > > > >> Should we
> avoid
> >>> > > unrecognized brand which may be trademark of someone?
> >>> > > > >> > > > > >>
> ambari-select or
> >>> > > bigtop-select should be enough.
> >>> > > > >> > > > > >
> >>> > > > >> > > > > > Not sure,
> where to confirm
> >>> > > whether there is already trademark. When I googled found
> so many.
> >>> > > > >> > > > > > But As we
> are not releasing
> >>> > > as enterprise should be fine I think. IMO, We need to
> create folders and
> >>> > > refer stacknames so ambari-select,bigtop-select wn't
> looks good.
> >>> > > > >> > > > > > May be you
> can refer the
> >>> > > initial proposal [2] where I mentioned some more names.
> >>> > > (BDS-BigDataStack,OSS-OpenSourceSelect..)
> >>> > > > >> > > > > >
> >>> > > > >> > > > > > Finally
> thanks a bunch for
> >>> > > long healthy discussions on this. Mostly we all same
> page now.
> >>> > > > >> > > > > >
> >>> > > > >> > > > > > 1.
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
> >>> > > > >> > > > > >
> >>> > > > >> > > > > > 2.
> >>> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
> >>> > > > >> > > > > >
> >>> > > > >> > > > > >
> >>> > > > >> > > > > > On
> 06/07/22, 4:01 AM,
> >>> > > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >>> > > > >> > > > > >
> >>> > > > >> > > > > > > We
> have still not
> >>> > > officially finalized the new replacement name for
> >>> > > > >> > > > > > >
> hdp-select, it would
> >>> > > likely be bdp-select (bdp: BigData Platform). However,
> >>> > > > >> > > > > > > the
> purpose of
> >>> > > bdp-select and conf-select remains the same.
> >>> > > > >> > > > > >
> >>> > > > >> > > > > >
> Should we avoid
> >>> > > unrecognized brand which may be trademark of someone?
> >>> > > > >> > > > > >
> ambari-select or
> >>> > > bigtop-select should be enough.
> >>> > > > >> > > > > >
> >>> > > > >> > > > > > On
> 2022/06/29 13:52,
> >>> > > Viraj Jasani wrote:
> >>> > > > >> > > > > > > Hi
> Ambari/Bigtop dev,
> >>> > > > >> > > > > > >
> >>> > > > >> > > > > > > As
> per the new
> >>> > > roadmap of Apache Ambari, we would like to propose moving
> >>> > > > >> > > > > > >
> certain scripts
> >>> > > (previously known as hdp-select and conf-select) to
> Bigtop
> >>> > > > >> > > > > > > so
> that their rpm
> >>> > > installation could be managed independently.
> >>> > > > >> > > > > > >
> These scripts are a
> >>> > > basic necessity in the Ambari framework for the
> >>> > > > >> > > > > > >
> installation of
> >>> > > various Bigdata packages. The only major changes they
> would
> >>> > > > >> > > > > > >
> receive is when we
> >>> > > onboard new services and components to Ambari, else they
> >>> > > > >> > > > > > >
> usually do not
> >>> > > receive updates. In the past, we used to get hdp-select
> rpm
> >>> > > > >> > > > > > >
> downloaded and
> >>> > > installed from HDP repositories.
> >>> > > > >> > > > > > >
> >>> > > > >> > > > > > > We
> have still not
> >>> > > officially finalized the new replacement name for
> >>> > > > >> > > > > > >
> hdp-select, it would
> >>> > > likely be bdp-select (bdp: BigData Platform). However,
> >>> > > > >> > > > > > > the
> purpose of
> >>> > > bdp-select and conf-select remains the same.
> >>> > > > >> > > > > > >
> >>> > > > >> > > > > >
> >>> > > > >> > > > >
> >>> > > > >> > > >
> >>> > > > >> > > >
> >>> > > > >> > > >
> >>> > >
> ---------------------------------------------------------------------
> >>> > > > >> > > > To unsubscribe, e-mail:
> >>> > > dev-unsubscribe@ambari.apache.org
> >>> > > > >> > > > For additional
> commands, e-mail:
> >>> > > dev-help@ambari.apache.org
> >>> > > > >> > > >
> >>> > > > >> > >
> >>> > > > >> > >
> >>> > >
> ---------------------------------------------------------------------
> >>> > > > >> > > To unsubscribe, e-mail:
> >>> > > dev-unsubscribe@ambari.apache.org
> >>> > > > >> > > For additional commands,
> e-mail:
> >>> > > dev-help@ambari.apache.org
> >>> > > > >> > >
> >>> > > > >> > >
> >>> > > > >> >
> >>> > > > >> >
> >>> > >
> ---------------------------------------------------------------------
> >>> > > > >> > To unsubscribe, e-mail:
> >>> > > dev-unsubscribe@ambari.apache.org
> >>> > > > >> > For additional commands, e-mail:
> >>> > > dev-help@ambari.apache.org
> >>> > > > >> >
> >>> > > > >> >
> >>> > > > >>
> >>> > > > >>
> >>> > >
> ---------------------------------------------------------------------
> >>> > > > >> To unsubscribe, e-mail:
> >>> > > dev-unsubscribe@ambari.apache.org
> >>> > > > >> For additional commands, e-mail:
> >>> > > dev-help@ambari.apache.org
> >>> > > > >>
> >>> > > > >>
> >>> > > >
> >>> > > >
> >>> > > >
> >>> > >
> ---------------------------------------------------------------------
> >>> > > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> >>> > > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> >>> > > >
> >>> > > >
> >>> > >
> >>> >
> >>> >
> >>> >
> ---------------------------------------------------------------------
> >>> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >>> > For additional commands, e-mail: dev-help@ambari.apache.org
> >>> >
> >>>
> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >>> For additional commands, e-mail: dev-help@ambari.apache.org
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >>> For additional commands, e-mail: dev-help@ambari.apache.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> For additional commands, e-mail: dev-help@ambari.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.com>.
+1
On 2022/09/21 11:12, 吴治国 wrote:
> I think we have enough to go on with Kengo’s proposal,
> Currently we don’t have enough developers(and I’m not willing to) to maintain a stack on our own like BDP.
>
>> Sure, here's my proposal:
>>
>> * Stack name: "BIGTOP"
>>
>> - The same name as the existing one [1]
>> - Because it deploys the packages generated by Bigtop
>> - The existing stack should be replaced with it, because that is
>> based on Bigtop 0.8 and too old to use now
>> - No concern about infringing others' trademark
>>
>> * Component/folder name: "bigtop-select"
>>
>> - Consistent naming convention with the existing tools such as
>> "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
>> - If it sounds too simple and a bit unclear, a more descriptive name
>> might be an option, for example "bigtop-ambari-stack-selector"
>>
>> * Script name: "bigtop-select"
>>
>> - Consistent with the stack name
>> - No concern about infringing others' trademark
>>
>> [1]: https://github.com/apache/ambari/tree/release-2.7.6/ambari-server/src/main/resources/stacks/BIGTOP/0.8
>> [2]: https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common <https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common>
>
> Best Regards,
> Zhiguo Wu
>
>> On Sep 16, 2022, at 08:44, Masatake Iwasaki <iw...@oss.nttdata.com> wrote:
>>
>>
>>>>> May be we can name it as bdp-select. Or (bgp-select)
>>>> -1 as we already discussed.
>>> Thanks for your feedback, I would definitely honour it. As you are not open for discussion and asked us raise the PR hence you thought of discussing on the PR. What will be your final suggestion on this..?
>>
>> I'm -1 on the name like bdp-select or bgp-select as we discussed.
>> Feel free to open PR with appropriate module name.
>>
>> On 2022/09/05 16:30, Battula, Brahma Reddy wrote:
>>> Hi @Masatake Iwasaki,
>>>> -1 as we already discussed.
>>> Thanks for your feedback, I would definitely honour it. As you are not open for discussion and asked us raise the PR hence you thought of discussing on the PR. What will be your final suggestion on this..?
>>> @Roman Shaposhnik
>>> I just gone through the following jira[1] where you brought ambari to bigtop. Looks stack-select is not included, how it was maintained.?
>>> I thinking we should have one stack which can support for upgrading the existing the HDP deployed clusters. Even I can see somebody asking on bigtop[2].
>>> If bigtop is not right place, shall we include in ambari..? Please let me know your thoughts on this. This blocks the 2.7.7 release.
>>> Note : There is on-going ambari mpack which might take some more time. Even upgrades will take some time.
>>> 1. https://issues.apache.org/jira/browse/BIGTOP-709
>>> 2. https://issues.apache.org/jira/browse/BIGTOP-3651
>>> Regards,
>>> Brahma Reddy Battula
>>> On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com> wrote:
>>> > May be we can name it as bdp-select. Or (bgp-select)
>>> -1 as we already discussed.
>>> On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
>>> > Ok, thanks Viraj.
>>> >
>>> > Hopefully you can place here like all other how it's maintained. Let me know any help required on this. May be we can name it as bdp-select. Or (bgp-select)
>>> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
>>> >
>>> >
>>> > On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org> wrote:
>>> >
>>> > Masatake, Brahma,
>>> >
>>> > Hopefully I should be able to create Jira and PR in Bigtop. Will let you
>>> > know once ready for review. Thanks
>>> >
>>> >
>>> > On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <iw...@oss.nttdata.com>
>>> > wrote:
>>> >
>>> > > Please file a JIRA and submit a pull request if you want to show the code
>>> > > and get feedback.
>>> > > There is nothing I want to discuss off the record.
>>> > >
>>> > > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
>>> > > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get
>>> > > the final conclusion on this..?
>>> > > >
>>> > > > Please let me know your availability, Can have one call to discuss on
>>> > > this..
>>> > > >
>>> > > >
>>> > > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
>>> > > wrote:
>>> > > >
>>> > > > > -1 on development in branch.
>>> > > > > It is not worth for maintaining the branch if the modules is
>>> > > so small
>>> > > > > and barely updated as explained here.
>>> > > > > It should not conflict to existing code.
>>> > > > > I feel I must check the code before check-in based on this
>>> > > thread.
>>> > > >
>>> > > >
>>> > > > Sure, Viraj or me can show the code to you.
>>> > > >
>>> > > > Can we've call on this Friday/Thrusday if that works..?
>>> > > >
>>> > > >
>>> > > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
>>> > > iwasakims@oss.nttdata.com> wrote:
>>> > > >
>>> > > > > Sure, we can havemodule name like bigtop-distro-select.
>>> > > > > Initially we'll do this separate branch.
>>> > > >
>>> > > > -1 on development in branch.
>>> > > > It is not worth for maintaining the branch if the modules is so
>>> > > small
>>> > > > and barely updated as explained here.
>>> > > > It should not conflict to existing code.
>>> > > > I feel I must check the code before check-in based on this
>>> > > thread.
>>> > > >
>>> > > > Masatake Iwasaki
>>> > > >
>>> > > > On 2022/07/11 8:23, Kengo Seki wrote:
>>> > > > >> As there are different opinions on this and took long time,
>>> > > just to brainstorm all the possibilities and pitfalls.
>>> > > > >
>>> > > > > Oh, I interpreted your words "conclude" and "finalize" as you
>>> > > were
>>> > > > > going to make a final decision. Brainstorming is welcome, of
>>> > > course.
>>> > > > > (But I'm not so sure if all people concerned could join, due
>>> > > to time
>>> > > > > difference and their schedule, etc.)
>>> > > > >
>>> > > > >> Can you suggest, how the changes will be also.. like folder,
>>> > > where you suggest to keep this...?
>>> > > > >
>>> > > > > Sure, here's my proposal:
>>> > > > >
>>> > > > > * Stack name: "BIGTOP"
>>> > > > >
>>> > > > > - The same name as the existing one [1]
>>> > > > > - Because it deploys the packages generated by Bigtop
>>> > > > > - The existing stack should be replaced with it, because
>>> > > that is
>>> > > > > based on Bigtop 0.8 and too old to use now
>>> > > > > - No concern about infringing others' trademark
>>> > > > >
>>> > > > > * Component/folder name: "bigtop-select"
>>> > > > >
>>> > > > > - Consistent naming convention with the existing tools
>>> > > such as
>>> > > > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
>>> > > > > - If it sounds too simple and a bit unclear, a more
>>> > > descriptive name
>>> > > > > might be an option, for example "bigtop-ambari-stack-selector"
>>> > > > >
>>> > > > > * Script name: "bigtop-select"
>>> > > > >
>>> > > > > - Consistent with the stack name
>>> > > > > - No concern about infringing others' trademark
>>> > > > >
>>> > > > > [1]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
>>> > > > > [2]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
>>> > > > >
>>> > > > > Kengo Seki <se...@apache.org>
>>> > > > >
>>> > > > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
>>> > > > > <bb...@visa.com.invalid> wrote:
>>> > > > >>
>>> > > > >>> Technical decisions shouldn't be done on other places
>>> > > than public mailing lists,
>>> > > > >>> as described in the "Open Communications" section of [1]
>>> > > and [2].
>>> > > > >> > So we should conclude the discussion in this mailing
>>> > > list.
>>> > > > >> > (And with my poor English, I'm not so confident to catch
>>> > > up with your
>>> > > > >> > fluent talk ;)
>>> > > > >>
>>> > > > >> I believe , I knew the apache way which you mentioned. We
>>> > > are not going conclude anything which comes to bigtop other than this
>>> > > mailing list.
>>> > > > >> As there are different opinions on this and took long time,
>>> > > just to brainstorm all the possibilities and pitfalls. Hence asking let's
>>> > > have call so that we can brainstorm. Even after call, everything will be
>>> > > published what we discussed.
>>> > > > >>
>>> > > > >> I think, whiteboarding will help to catch up with you.
>>> > > > >>
>>> > > > >> You all the think "bigtop-select" will be best option
>>> > > right..? Can you suggest, how the changes will be also.. like folder, where
>>> > > you suggest to keep this...?
>>> > > > >>
>>> > > > >> And if the name represents the stack which we are going to
>>> > > deploy should fine I feel.. (if it's not BDP, may be
>>> > > OBDP:OpensourceBigDataPlatform.)
>>> > > > >>
>>> > > > >> @Viraj Jasani and others any thoughts..?
>>> > > > >>
>>> > > > >>
>>> > > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org>
>>> > > wrote:
>>> > > > >>
>>> > > > >> > Looks we had so much discussed here, Let's try to
>>> > > conclude. Can we've one call on this and finalize this..?
>>> > > > >>
>>> > > > >> Technical decisions shouldn't be done on other places
>>> > > than public mailing lists,
>>> > > > >> as described in the "Open Communications" section of
>>> > > [1] and [2].
>>> > > > >> So we should conclude the discussion in this mailing
>>> > > list.
>>> > > > >> (And with my poor English, I'm not so confident to
>>> > > catch up with your
>>> > > > >> fluent talk ;)
>>> > > > >>
>>> > > > >> > FYI. Even looks bigtop used some where also..
>>> > > > >>
>>> > > > >> Bigtop is ASF's trademark as you can see in the "Apache
>>> > > Bigtop®
>>> > > > >> software" section of [3].
>>> > > > >> So it doesn't have the risk of trademark infringement.
>>> > > > >>
>>> > > > >> [1]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
>>> > > > >> [2]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
>>> > > > >> [3]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
>>> > > > >>
>>> > > > >> Kengo Seki <se...@apache.org>
>>> > > > >>
>>> > > > >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
>>> > > > >> <bb...@visa.com.invalid> wrote:
>>> > > > >> >
>>> > > > >> > Looks we had so much discussed here, Let's try to
>>> > > conclude. Can we've one call on this and finalize this..?
>>> > > > >> >
>>> > > > >> > FYI. Even looks bigtop used some where[1] also..
>>> > > > >> > 1.
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
>>> > > > >> >
>>> > > > >> >
>>> > > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
>>> > > wrote:
>>> > > > >> >
>>> > > > >> > Thank you for your explanation, Brahma.
>>> > > > >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP"
>>> > > [1]) is supposed to be a
>>> > > > >> > trademark of Redoop, so they can name the script
>>> > > crh-select without
>>> > > > >> > problem.
>>> > > > >> > But regarding BDP for example, I can easily find
>>> > > products that have
>>> > > > >> > the same name [2][3][4] as you already mentioned,
>>> > > so I'd like to
>>> > > > >> > recommend bigtop-select for avoiding unnecessary
>>> > > trouble.
>>> > > > >> > Or, a single and more general word just like
>>> > > conf-select may be less
>>> > > > >> > troublesome than bdp. How about "stack-select",
>>> > > for example?
>>> > > > >> >
>>> > > > >> > [1]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
>>> > > > >> > [2]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
>>> > > > >> > [3]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
>>> > > > >> > [4]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
>>> > > > >> >
>>> > > > >> > Kengo Seki <se...@apache.org>
>>> > > > >> >
>>> > > > >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma
>>> > > Reddy <bb...@visa.com> wrote:
>>> > > > >> > >
>>> > > > >> > > >Do you mean that you're going to name the
>>> > > module (same as "component"
>>> > > > >> > > >in the Bigtop terminology, I think)
>>> > > bigtop-distro-select,
>>> > > > >> > > >and still the script in question
>>> > > bdp-select? If so, is there any
>>> > > > >> > > >reason that the script must be that name?
>>> > > > >> > > >(No offence, I just want to understand
>>> > > your thoughts and its
>>> > > > >> > > >background, and avoid the conflict or
>>> > > user's confusion with existing
>>> > > > >> > > >trademarks or products)
>>> > > > >> > >
>>> > > > >> > > Thanks @Kengo Seki for consolidating all the
>>> > > concerns. Name should represent the stack which includes all the components
>>> > > hence planning to have like bdp,bds...and this only one file like below[1]
>>> > > which has done redoop.
>>> > > > >> > >
>>> > > > >> > >
>>> > > > >> > >
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
>>> > > > >> > >
>>> > > > >> > >
>>> > > > >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
>>> > > sekikn@apache.org> wrote:
>>> > > > >> > >
>>> > > > >> > > The following concern Masatake mentioned
>>> > > before is an important point,
>>> > > > >> > > so I talked to Brahma for clarifying his
>>> > > intention on the ASF Slack
>>> > > > >> > > yesterday.
>>> > > > >> > >
>>> > > > >> > > > Multiple versions of the same package
>>> > > (deb/rpm) can not be installed at the same time.
>>> > > > >> > > > IIRC, HDP uses convention in which the
>>> > > product version is part of package name
>>> > > > >> > > > for addressing this.
>>> > > > >> > >
>>> > > > >> > > > I don't like to bring the awkward package
>>> > > name convention to Bigtop
>>> > > > >> > > > at least by default.
>>> > > > >> > >
>>> > > > >> > > He's planning to adopt the same mitigation
>>> > > as HDP for now, but he
>>> > > > >> > > doesn't intend to change the default
>>> > > package naming convention of
>>> > > > >> > > Bigtop,
>>> > > > >> > > but just add a new functionality to include
>>> > > an extra part into the
>>> > > > >> > > package name for avoiding conflict, which
>>> > > is disabled by default.
>>> > > > >> > >
>>> > > > >> > > And Brahma, let me confirm about the
>>> > > following reply:
>>> > > > >> > >
>>> > > > >> > > > Sure, we can have module name like
>>> > > bigtop-distro-select.
>>> > > > >> > >
>>> > > > >> > > Do you mean that you're going to name the
>>> > > module (same as "component"
>>> > > > >> > > in the Bigtop terminology, I think)
>>> > > bigtop-distro-select,
>>> > > > >> > > and still the script in question
>>> > > bdp-select? If so, is there any
>>> > > > >> > > reason that the script must be that name?
>>> > > > >> > > (No offence, I just want to understand your
>>> > > thoughts and its
>>> > > > >> > > background, and avoid the conflict or
>>> > > user's confusion with existing
>>> > > > >> > > trademarks or products)
>>> > > > >> > >
>>> > > > >> > > Kengo Seki <se...@apache.org>
>>> > > > >> > >
>>> > > > >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula,
>>> > > Brahma Reddy
>>> > > > >> > > <bb...@visa.com.invalid> wrote:
>>> > > > >> > > >
>>> > > > >> > > > > The name of stack based no Bigtop
>>> > > should be Bigtop.
>>> > > > >> > > > > If you can not accept the name like
>>> > > bigtop-*, the work should done outside of Bigtop.
>>> > > > >> > > > > I will cast -1 if someone submit a
>>> > > patch to add a module with the name spoiling branding.
>>> > > > >> > > >
>>> > > > >> > > > Sure, we can have module name like
>>> > > bigtop-distro-select.
>>> > > > >> > > > Initially we'll do this separate branch.
>>> > > > >> > > >
>>> > > > >> > > >
>>> > > > >> > > >
>>> > > > >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
>>> > > iwasakims@oss.nttdata.co.jp> wrote:
>>> > > > >> > > >
>>> > > > >> > > > > I believe it's for project name.
>>> > > isn't it.?
>>> > > > >> > > >
>>> > > > >> > > > projects and products.
>>> > > > >> > > >
>>> > > > >> > > > > IMO, We need to create folders and
>>> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
>>> > > > >> > > >
>>> > > > >> > > > The name of stack based no Bigtop
>>> > > should be Bigtop.
>>> > > > >> > > > If you can not accept the name like
>>> > > bigtop-*, the work should done outside of Bigtop.
>>> > > > >> > > > I will cast -1 if someone submit a
>>> > > patch to add a module with the name spoiling branding.
>>> > > > >> > > >
>>> > > > >> > > >
>>> > > > >> > > > On 2022/07/06 11:44, Battula, Brahma
>>> > > Reddy wrote:
>>> > > > >> > > > >
>>> > > > >> > > > > I believe it's for project name.
>>> > > isn't it.?
>>> > > > >> > > > >
>>> > > > >> > > > >
>>> > > > >> > > > > On 06/07/22, 7:27 AM, "Masatake
>>> > > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>> > > > >> > > > >
>>> > > > >> > > > > > But As we are not releasing
>>> > > as enterprise should be fine I think. IMO, We need to create folders and
>>> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
>>> > > > >> > > > >
>>> > > > >> > > > > Not fine.
>>> > > > >> > > > > We have a trademark policy.
>>> > > > >> > > > >
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
>>> > > > >> > > > >
>>> > > > >> > > > > On 2022/07/06 10:37, Battula,
>>> > > Brahma Reddy wrote:
>>> > > > >> > > > > >> Should we avoid
>>> > > unrecognized brand which may be trademark of someone?
>>> > > > >> > > > > >> ambari-select or
>>> > > bigtop-select should be enough.
>>> > > > >> > > > > >
>>> > > > >> > > > > > Not sure, where to confirm
>>> > > whether there is already trademark. When I googled found so many.
>>> > > > >> > > > > > But As we are not releasing
>>> > > as enterprise should be fine I think. IMO, We need to create folders and
>>> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
>>> > > > >> > > > > > May be you can refer the
>>> > > initial proposal [2] where I mentioned some more names.
>>> > > (BDS-BigDataStack,OSS-OpenSourceSelect..)
>>> > > > >> > > > > >
>>> > > > >> > > > > > Finally thanks a bunch for
>>> > > long healthy discussions on this. Mostly we all same page now.
>>> > > > >> > > > > >
>>> > > > >> > > > > > 1.
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
>>> > > > >> > > > > >
>>> > > > >> > > > > > 2.
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
>>> > > > >> > > > > >
>>> > > > >> > > > > >
>>> > > > >> > > > > > On 06/07/22, 4:01 AM,
>>> > > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>> > > > >> > > > > >
>>> > > > >> > > > > > > We have still not
>>> > > officially finalized the new replacement name for
>>> > > > >> > > > > > > hdp-select, it would
>>> > > likely be bdp-select (bdp: BigData Platform). However,
>>> > > > >> > > > > > > the purpose of
>>> > > bdp-select and conf-select remains the same.
>>> > > > >> > > > > >
>>> > > > >> > > > > > Should we avoid
>>> > > unrecognized brand which may be trademark of someone?
>>> > > > >> > > > > > ambari-select or
>>> > > bigtop-select should be enough.
>>> > > > >> > > > > >
>>> > > > >> > > > > > On 2022/06/29 13:52,
>>> > > Viraj Jasani wrote:
>>> > > > >> > > > > > > Hi Ambari/Bigtop dev,
>>> > > > >> > > > > > >
>>> > > > >> > > > > > > As per the new
>>> > > roadmap of Apache Ambari, we would like to propose moving
>>> > > > >> > > > > > > certain scripts
>>> > > (previously known as hdp-select and conf-select) to Bigtop
>>> > > > >> > > > > > > so that their rpm
>>> > > installation could be managed independently.
>>> > > > >> > > > > > > These scripts are a
>>> > > basic necessity in the Ambari framework for the
>>> > > > >> > > > > > > installation of
>>> > > various Bigdata packages. The only major changes they would
>>> > > > >> > > > > > > receive is when we
>>> > > onboard new services and components to Ambari, else they
>>> > > > >> > > > > > > usually do not
>>> > > receive updates. In the past, we used to get hdp-select rpm
>>> > > > >> > > > > > > downloaded and
>>> > > installed from HDP repositories.
>>> > > > >> > > > > > >
>>> > > > >> > > > > > > We have still not
>>> > > officially finalized the new replacement name for
>>> > > > >> > > > > > > hdp-select, it would
>>> > > likely be bdp-select (bdp: BigData Platform). However,
>>> > > > >> > > > > > > the purpose of
>>> > > bdp-select and conf-select remains the same.
>>> > > > >> > > > > > >
>>> > > > >> > > > > >
>>> > > > >> > > > >
>>> > > > >> > > >
>>> > > > >> > > >
>>> > > > >> > > >
>>> > > ---------------------------------------------------------------------
>>> > > > >> > > > To unsubscribe, e-mail:
>>> > > dev-unsubscribe@ambari.apache.org
>>> > > > >> > > > For additional commands, e-mail:
>>> > > dev-help@ambari.apache.org
>>> > > > >> > > >
>>> > > > >> > >
>>> > > > >> > >
>>> > > ---------------------------------------------------------------------
>>> > > > >> > > To unsubscribe, e-mail:
>>> > > dev-unsubscribe@ambari.apache.org
>>> > > > >> > > For additional commands, e-mail:
>>> > > dev-help@ambari.apache.org
>>> > > > >> > >
>>> > > > >> > >
>>> > > > >> >
>>> > > > >> >
>>> > > ---------------------------------------------------------------------
>>> > > > >> > To unsubscribe, e-mail:
>>> > > dev-unsubscribe@ambari.apache.org
>>> > > > >> > For additional commands, e-mail:
>>> > > dev-help@ambari.apache.org
>>> > > > >> >
>>> > > > >> >
>>> > > > >>
>>> > > > >>
>>> > > ---------------------------------------------------------------------
>>> > > > >> To unsubscribe, e-mail:
>>> > > dev-unsubscribe@ambari.apache.org
>>> > > > >> For additional commands, e-mail:
>>> > > dev-help@ambari.apache.org
>>> > > > >>
>>> > > > >>
>>> > > >
>>> > > >
>>> > > >
>>> > > ---------------------------------------------------------------------
>>> > > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>> > > > For additional commands, e-mail: dev-help@ambari.apache.org
>>> > > >
>>> > > >
>>> > >
>>> >
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>> > For additional commands, e-mail: dev-help@ambari.apache.org
>>> >
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>> For additional commands, e-mail: dev-help@ambari.apache.org
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>> For additional commands, e-mail: dev-help@ambari.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Viraj Jasani <vj...@apache.org>.
Do we want to use the BIGTOP stack for 2.7.7 as well? Or we want to use it
for 2.8.0 and 3.0.0 onwards only to minimize the big changes for 2.7.7
patch release?
On Tue, Sep 20, 2022 at 7:12 PM 吴治国 <wz...@163.com> wrote:
> I think we have enough to go on with Kengo’s proposal,
> Currently we don’t have enough developers(and I’m not willing to) to
> maintain a stack on our own like BDP.
>
> > Sure, here's my proposal:
> >
> > * Stack name: "BIGTOP"
> >
> > - The same name as the existing one [1]
> > - Because it deploys the packages generated by Bigtop
> > - The existing stack should be replaced with it, because that is
> > based on Bigtop 0.8 and too old to use now
> > - No concern about infringing others' trademark
> >
> > * Component/folder name: "bigtop-select"
> >
> > - Consistent naming convention with the existing tools such as
> > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > - If it sounds too simple and a bit unclear, a more descriptive name
> > might be an option, for example "bigtop-ambari-stack-selector"
> >
> > * Script name: "bigtop-select"
> >
> > - Consistent with the stack name
> > - No concern about infringing others' trademark
> >
> > [1]:
> https://github.com/apache/ambari/tree/release-2.7.6/ambari-server/src/main/resources/stacks/BIGTOP/0.8
> > [2]:
> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common <
> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common>
>
> Best Regards,
> Zhiguo Wu
>
> > On Sep 16, 2022, at 08:44, Masatake Iwasaki <iw...@oss.nttdata.com>
> wrote:
> >
> >
> >>>> May be we can name it as bdp-select. Or (bgp-select)
> >>> -1 as we already discussed.
> >> Thanks for your feedback, I would definitely honour it. As you are not
> open for discussion and asked us raise the PR hence you thought of
> discussing on the PR. What will be your final suggestion on this..?
> >
> > I'm -1 on the name like bdp-select or bgp-select as we discussed.
> > Feel free to open PR with appropriate module name.
> >
> > On 2022/09/05 16:30, Battula, Brahma Reddy wrote:
> >> Hi @Masatake Iwasaki,
> >>> -1 as we already discussed.
> >> Thanks for your feedback, I would definitely honour it. As you are not
> open for discussion and asked us raise the PR hence you thought of
> discussing on the PR. What will be your final suggestion on this..?
> >> @Roman Shaposhnik
> >> I just gone through the following jira[1] where you brought ambari to
> bigtop. Looks stack-select is not included, how it was maintained.?
> >> I thinking we should have one stack which can support for upgrading the
> existing the HDP deployed clusters. Even I can see somebody asking on
> bigtop[2].
> >> If bigtop is not right place, shall we include in ambari..? Please let
> me know your thoughts on this. This blocks the 2.7.7 release.
> >> Note : There is on-going ambari mpack which might take some more time.
> Even upgrades will take some time.
> >> 1. https://issues.apache.org/jira/browse/BIGTOP-709
> >> 2. https://issues.apache.org/jira/browse/BIGTOP-3651
> >> Regards,
> >> Brahma Reddy Battula
> >> On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com>
> wrote:
> >> > May be we can name it as bdp-select. Or (bgp-select)
> >> -1 as we already discussed.
> >> On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
> >> > Ok, thanks Viraj.
> >> >
> >> > Hopefully you can place here like all other how it's maintained.
> Let me know any help required on this. May be we can name it as bdp-select.
> Or (bgp-select)
> >> >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> >> >
> >> >
> >> > On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org> wrote:
> >> >
> >> > Masatake, Brahma,
> >> >
> >> > Hopefully I should be able to create Jira and PR in Bigtop.
> Will let you
> >> > know once ready for review. Thanks
> >> >
> >> >
> >> > On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <
> iwasakims@oss.nttdata.com>
> >> > wrote:
> >> >
> >> > > Please file a JIRA and submit a pull request if you want
> to show the code
> >> > > and get feedback.
> >> > > There is nothing I want to discuss off the record.
> >> > >
> >> > > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> >> > > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and
> others, can we get
> >> > > the final conclusion on this..?
> >> > > >
> >> > > > Please let me know your availability, Can have one call
> to discuss on
> >> > > this..
> >> > > >
> >> > > >
> >> > > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy"
> <bb...@visa.com.INVALID>
> >> > > wrote:
> >> > > >
> >> > > > > -1 on development in branch.
> >> > > > > It is not worth for maintaining the branch if
> the modules is
> >> > > so small
> >> > > > > and barely updated as explained here.
> >> > > > > It should not conflict to existing code.
> >> > > > > I feel I must check the code before check-in
> based on this
> >> > > thread.
> >> > > >
> >> > > >
> >> > > > Sure, Viraj or me can show the code to you.
> >> > > >
> >> > > > Can we've call on this Friday/Thrusday if that
> works..?
> >> > > >
> >> > > >
> >> > > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> >> > > iwasakims@oss.nttdata.com> wrote:
> >> > > >
> >> > > > > Sure, we can havemodule name like
> bigtop-distro-select.
> >> > > > > Initially we'll do this separate branch.
> >> > > >
> >> > > > -1 on development in branch.
> >> > > > It is not worth for maintaining the branch if
> the modules is so
> >> > > small
> >> > > > and barely updated as explained here.
> >> > > > It should not conflict to existing code.
> >> > > > I feel I must check the code before check-in
> based on this
> >> > > thread.
> >> > > >
> >> > > > Masatake Iwasaki
> >> > > >
> >> > > > On 2022/07/11 8:23, Kengo Seki wrote:
> >> > > > >> As there are different opinions on this and
> took long time,
> >> > > just to brainstorm all the possibilities and pitfalls.
> >> > > > >
> >> > > > > Oh, I interpreted your words "conclude" and
> "finalize" as you
> >> > > were
> >> > > > > going to make a final decision. Brainstorming
> is welcome, of
> >> > > course.
> >> > > > > (But I'm not so sure if all people concerned
> could join, due
> >> > > to time
> >> > > > > difference and their schedule, etc.)
> >> > > > >
> >> > > > >> Can you suggest, how the changes will be
> also.. like folder,
> >> > > where you suggest to keep this...?
> >> > > > >
> >> > > > > Sure, here's my proposal:
> >> > > > >
> >> > > > > * Stack name: "BIGTOP"
> >> > > > >
> >> > > > > - The same name as the existing one [1]
> >> > > > > - Because it deploys the packages
> generated by Bigtop
> >> > > > > - The existing stack should be replaced
> with it, because
> >> > > that is
> >> > > > > based on Bigtop 0.8 and too old to use now
> >> > > > > - No concern about infringing others'
> trademark
> >> > > > >
> >> > > > > * Component/folder name: "bigtop-select"
> >> > > > >
> >> > > > > - Consistent naming convention with the
> existing tools
> >> > > such as
> >> > > > > "bigtop-groovy", "bigtop-jsvc",
> "bigtop-utils" [2]
> >> > > > > - If it sounds too simple and a bit
> unclear, a more
> >> > > descriptive name
> >> > > > > might be an option, for example
> "bigtop-ambari-stack-selector"
> >> > > > >
> >> > > > > * Script name: "bigtop-select"
> >> > > > >
> >> > > > > - Consistent with the stack name
> >> > > > > - No concern about infringing others'
> trademark
> >> > > > >
> >> > > > > [1]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
> >> > > > > [2]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> >> > > > >
> >> > > > > Kengo Seki <se...@apache.org>
> >> > > > >
> >> > > > > On Mon, Jul 11, 2022 at 3:19 AM Battula,
> Brahma Reddy
> >> > > > > <bb...@visa.com.invalid> wrote:
> >> > > > >>
> >> > > > >>> Technical decisions shouldn't be done on
> other places
> >> > > than public mailing lists,
> >> > > > >>> as described in the "Open Communications"
> section of [1]
> >> > > and [2].
> >> > > > >> > So we should conclude the discussion in
> this mailing
> >> > > list.
> >> > > > >> > (And with my poor English, I'm not so
> confident to catch
> >> > > up with your
> >> > > > >> > fluent talk ;)
> >> > > > >>
> >> > > > >> I believe , I knew the apache way which you
> mentioned. We
> >> > > are not going conclude anything which comes to bigtop
> other than this
> >> > > mailing list.
> >> > > > >> As there are different opinions on this and
> took long time,
> >> > > just to brainstorm all the possibilities and pitfalls.
> Hence asking let's
> >> > > have call so that we can brainstorm. Even after call,
> everything will be
> >> > > published what we discussed.
> >> > > > >>
> >> > > > >> I think, whiteboarding will help to catch up
> with you.
> >> > > > >>
> >> > > > >> You all the think "bigtop-select" will be
> best option
> >> > > right..? Can you suggest, how the changes will be also..
> like folder, where
> >> > > you suggest to keep this...?
> >> > > > >>
> >> > > > >> And if the name represents the stack which
> we are going to
> >> > > deploy should fine I feel.. (if it's not BDP, may be
> >> > > OBDP:OpensourceBigDataPlatform.)
> >> > > > >>
> >> > > > >> @Viraj Jasani and others any thoughts..?
> >> > > > >>
> >> > > > >>
> >> > > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <
> sekikn@apache.org>
> >> > > wrote:
> >> > > > >>
> >> > > > >> > Looks we had so much discussed here,
> Let's try to
> >> > > conclude. Can we've one call on this and finalize this..?
> >> > > > >>
> >> > > > >> Technical decisions shouldn't be done
> on other places
> >> > > than public mailing lists,
> >> > > > >> as described in the "Open
> Communications" section of
> >> > > [1] and [2].
> >> > > > >> So we should conclude the discussion in
> this mailing
> >> > > list.
> >> > > > >> (And with my poor English, I'm not so
> confident to
> >> > > catch up with your
> >> > > > >> fluent talk ;)
> >> > > > >>
> >> > > > >> > FYI. Even looks bigtop used some
> where also..
> >> > > > >>
> >> > > > >> Bigtop is ASF's trademark as you can
> see in the "Apache
> >> > > Bigtop®
> >> > > > >> software" section of [3].
> >> > > > >> So it doesn't have the risk of
> trademark infringement.
> >> > > > >>
> >> > > > >> [1]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
> >> > > > >> [2]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
> >> > > > >> [3]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
> >> > > > >>
> >> > > > >> Kengo Seki <se...@apache.org>
> >> > > > >>
> >> > > > >> On Sun, Jul 10, 2022 at 4:11 AM
> Battula, Brahma Reddy
> >> > > > >> <bb...@visa.com.invalid> wrote:
> >> > > > >> >
> >> > > > >> > Looks we had so much discussed here,
> Let's try to
> >> > > conclude. Can we've one call on this and finalize this..?
> >> > > > >> >
> >> > > > >> > FYI. Even looks bigtop used some
> where[1] also..
> >> > > > >> > 1.
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
> >> > > > >> >
> >> > > > >> >
> >> > > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <
> sekikn@apache.org>
> >> > > wrote:
> >> > > > >> >
> >> > > > >> > Thank you for your explanation,
> Brahma.
> >> > > > >> > CRH (abbreviation of "CHINA
> REDOOP HYPERLOOP"
> >> > > [1]) is supposed to be a
> >> > > > >> > trademark of Redoop, so they can
> name the script
> >> > > crh-select without
> >> > > > >> > problem.
> >> > > > >> > But regarding BDP for example, I
> can easily find
> >> > > products that have
> >> > > > >> > the same name [2][3][4] as you
> already mentioned,
> >> > > so I'd like to
> >> > > > >> > recommend bigtop-select for
> avoiding unnecessary
> >> > > trouble.
> >> > > > >> > Or, a single and more general
> word just like
> >> > > conf-select may be less
> >> > > > >> > troublesome than bdp. How about
> "stack-select",
> >> > > for example?
> >> > > > >> >
> >> > > > >> > [1]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
> >> > > > >> > [2]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
> >> > > > >> > [3]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
> >> > > > >> > [4]:
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
> >> > > > >> >
> >> > > > >> > Kengo Seki <se...@apache.org>
> >> > > > >> >
> >> > > > >> > On Fri, Jul 8, 2022 at 2:51 AM
> Battula, Brahma
> >> > > Reddy <bb...@visa.com> wrote:
> >> > > > >> > >
> >> > > > >> > > >Do you mean that you're
> going to name the
> >> > > module (same as "component"
> >> > > > >> > > >in the Bigtop terminology,
> I think)
> >> > > bigtop-distro-select,
> >> > > > >> > > >and still the script in
> question
> >> > > bdp-select? If so, is there any
> >> > > > >> > > >reason that the script
> must be that name?
> >> > > > >> > > >(No offence, I just want
> to understand
> >> > > your thoughts and its
> >> > > > >> > > >background, and avoid the
> conflict or
> >> > > user's confusion with existing
> >> > > > >> > > >trademarks or products)
> >> > > > >> > >
> >> > > > >> > > Thanks @Kengo Seki for
> consolidating all the
> >> > > concerns. Name should represent the stack which includes
> all the components
> >> > > hence planning to have like bdp,bds...and this only one
> file like below[1]
> >> > > which has done redoop.
> >> > > > >> > >
> >> > > > >> > >
> >> > > > >> > >
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
> >> > > > >> > >
> >> > > > >> > >
> >> > > > >> > > On 07/07/22, 6:07 AM, "Kengo
> Seki" <
> >> > > sekikn@apache.org> wrote:
> >> > > > >> > >
> >> > > > >> > > The following concern
> Masatake mentioned
> >> > > before is an important point,
> >> > > > >> > > so I talked to Brahma for
> clarifying his
> >> > > intention on the ASF Slack
> >> > > > >> > > yesterday.
> >> > > > >> > >
> >> > > > >> > > > Multiple versions of the
> same package
> >> > > (deb/rpm) can not be installed at the same time.
> >> > > > >> > > > IIRC, HDP uses convention
> in which the
> >> > > product version is part of package name
> >> > > > >> > > > for addressing this.
> >> > > > >> > >
> >> > > > >> > > > I don't like to bring the
> awkward package
> >> > > name convention to Bigtop
> >> > > > >> > > > at least by default.
> >> > > > >> > >
> >> > > > >> > > He's planning to adopt the
> same mitigation
> >> > > as HDP for now, but he
> >> > > > >> > > doesn't intend to change
> the default
> >> > > package naming convention of
> >> > > > >> > > Bigtop,
> >> > > > >> > > but just add a new
> functionality to include
> >> > > an extra part into the
> >> > > > >> > > package name for avoiding
> conflict, which
> >> > > is disabled by default.
> >> > > > >> > >
> >> > > > >> > > And Brahma, let me confirm
> about the
> >> > > following reply:
> >> > > > >> > >
> >> > > > >> > > > Sure, we can have module
> name like
> >> > > bigtop-distro-select.
> >> > > > >> > >
> >> > > > >> > > Do you mean that you're
> going to name the
> >> > > module (same as "component"
> >> > > > >> > > in the Bigtop terminology,
> I think)
> >> > > bigtop-distro-select,
> >> > > > >> > > and still the script in
> question
> >> > > bdp-select? If so, is there any
> >> > > > >> > > reason that the script must
> be that name?
> >> > > > >> > > (No offence, I just want to
> understand your
> >> > > thoughts and its
> >> > > > >> > > background, and avoid the
> conflict or
> >> > > user's confusion with existing
> >> > > > >> > > trademarks or products)
> >> > > > >> > >
> >> > > > >> > > Kengo Seki <
> sekikn@apache.org>
> >> > > > >> > >
> >> > > > >> > > On Thu, Jul 7, 2022 at 2:08
> AM Battula,
> >> > > Brahma Reddy
> >> > > > >> > > <bb...@visa.com.invalid>
> wrote:
> >> > > > >> > > >
> >> > > > >> > > > > The name of stack
> based no Bigtop
> >> > > should be Bigtop.
> >> > > > >> > > > > If you can not
> accept the name like
> >> > > bigtop-*, the work should done outside of Bigtop.
> >> > > > >> > > > > I will cast -1 if
> someone submit a
> >> > > patch to add a module with the name spoiling branding.
> >> > > > >> > > >
> >> > > > >> > > > Sure, we can have module
> name like
> >> > > bigtop-distro-select.
> >> > > > >> > > > Initially we'll do this
> separate branch.
> >> > > > >> > > >
> >> > > > >> > > >
> >> > > > >> > > >
> >> > > > >> > > > On 06/07/22, 8:55 AM,
> "Masatake Iwasaki" <
> >> > > iwasakims@oss.nttdata.co.jp> wrote:
> >> > > > >> > > >
> >> > > > >> > > > > I believe it's for
> project name.
> >> > > isn't it.?
> >> > > > >> > > >
> >> > > > >> > > > projects and products.
> >> > > > >> > > >
> >> > > > >> > > > > IMO, We need to
> create folders and
> >> > > refer stacknames so ambari-select,bigtop-select wn't looks
> good.
> >> > > > >> > > >
> >> > > > >> > > > The name of stack
> based no Bigtop
> >> > > should be Bigtop.
> >> > > > >> > > > If you can not accept
> the name like
> >> > > bigtop-*, the work should done outside of Bigtop.
> >> > > > >> > > > I will cast -1 if
> someone submit a
> >> > > patch to add a module with the name spoiling branding.
> >> > > > >> > > >
> >> > > > >> > > >
> >> > > > >> > > > On 2022/07/06 11:44,
> Battula, Brahma
> >> > > Reddy wrote:
> >> > > > >> > > > >
> >> > > > >> > > > > I believe it's for
> project name.
> >> > > isn't it.?
> >> > > > >> > > > >
> >> > > > >> > > > >
> >> > > > >> > > > > On 06/07/22, 7:27
> AM, "Masatake
> >> > > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >> > > > >> > > > >
> >> > > > >> > > > > > But As we
> are not releasing
> >> > > as enterprise should be fine I think. IMO, We need to
> create folders and
> >> > > refer stacknames so ambari-select,bigtop-select wn't looks
> good.
> >> > > > >> > > > >
> >> > > > >> > > > > Not fine.
> >> > > > >> > > > > We have a
> trademark policy.
> >> > > > >> > > > >
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
> >> > > > >> > > > >
> >> > > > >> > > > > On 2022/07/06
> 10:37, Battula,
> >> > > Brahma Reddy wrote:
> >> > > > >> > > > > >> Should we
> avoid
> >> > > unrecognized brand which may be trademark of someone?
> >> > > > >> > > > > >>
> ambari-select or
> >> > > bigtop-select should be enough.
> >> > > > >> > > > > >
> >> > > > >> > > > > > Not sure,
> where to confirm
> >> > > whether there is already trademark. When I googled found
> so many.
> >> > > > >> > > > > > But As we
> are not releasing
> >> > > as enterprise should be fine I think. IMO, We need to
> create folders and
> >> > > refer stacknames so ambari-select,bigtop-select wn't looks
> good.
> >> > > > >> > > > > > May be you
> can refer the
> >> > > initial proposal [2] where I mentioned some more names.
> >> > > (BDS-BigDataStack,OSS-OpenSourceSelect..)
> >> > > > >> > > > > >
> >> > > > >> > > > > > Finally
> thanks a bunch for
> >> > > long healthy discussions on this. Mostly we all same page
> now.
> >> > > > >> > > > > >
> >> > > > >> > > > > > 1.
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
> >> > > > >> > > > > >
> >> > > > >> > > > > > 2.
> >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
> >> > > > >> > > > > >
> >> > > > >> > > > > >
> >> > > > >> > > > > > On 06/07/22,
> 4:01 AM,
> >> > > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >> > > > >> > > > > >
> >> > > > >> > > > > > > We
> have still not
> >> > > officially finalized the new replacement name for
> >> > > > >> > > > > > >
> hdp-select, it would
> >> > > likely be bdp-select (bdp: BigData Platform). However,
> >> > > > >> > > > > > > the
> purpose of
> >> > > bdp-select and conf-select remains the same.
> >> > > > >> > > > > >
> >> > > > >> > > > > > Should
> we avoid
> >> > > unrecognized brand which may be trademark of someone?
> >> > > > >> > > > > >
> ambari-select or
> >> > > bigtop-select should be enough.
> >> > > > >> > > > > >
> >> > > > >> > > > > > On
> 2022/06/29 13:52,
> >> > > Viraj Jasani wrote:
> >> > > > >> > > > > > > Hi
> Ambari/Bigtop dev,
> >> > > > >> > > > > > >
> >> > > > >> > > > > > > As
> per the new
> >> > > roadmap of Apache Ambari, we would like to propose moving
> >> > > > >> > > > > > >
> certain scripts
> >> > > (previously known as hdp-select and conf-select) to Bigtop
> >> > > > >> > > > > > > so
> that their rpm
> >> > > installation could be managed independently.
> >> > > > >> > > > > > > These
> scripts are a
> >> > > basic necessity in the Ambari framework for the
> >> > > > >> > > > > > >
> installation of
> >> > > various Bigdata packages. The only major changes they would
> >> > > > >> > > > > > >
> receive is when we
> >> > > onboard new services and components to Ambari, else they
> >> > > > >> > > > > > >
> usually do not
> >> > > receive updates. In the past, we used to get hdp-select rpm
> >> > > > >> > > > > > >
> downloaded and
> >> > > installed from HDP repositories.
> >> > > > >> > > > > > >
> >> > > > >> > > > > > > We
> have still not
> >> > > officially finalized the new replacement name for
> >> > > > >> > > > > > >
> hdp-select, it would
> >> > > likely be bdp-select (bdp: BigData Platform). However,
> >> > > > >> > > > > > > the
> purpose of
> >> > > bdp-select and conf-select remains the same.
> >> > > > >> > > > > > >
> >> > > > >> > > > > >
> >> > > > >> > > > >
> >> > > > >> > > >
> >> > > > >> > > >
> >> > > > >> > > >
> >> > >
> ---------------------------------------------------------------------
> >> > > > >> > > > To unsubscribe, e-mail:
> >> > > dev-unsubscribe@ambari.apache.org
> >> > > > >> > > > For additional commands,
> e-mail:
> >> > > dev-help@ambari.apache.org
> >> > > > >> > > >
> >> > > > >> > >
> >> > > > >> > >
> >> > >
> ---------------------------------------------------------------------
> >> > > > >> > > To unsubscribe, e-mail:
> >> > > dev-unsubscribe@ambari.apache.org
> >> > > > >> > > For additional commands,
> e-mail:
> >> > > dev-help@ambari.apache.org
> >> > > > >> > >
> >> > > > >> > >
> >> > > > >> >
> >> > > > >> >
> >> > >
> ---------------------------------------------------------------------
> >> > > > >> > To unsubscribe, e-mail:
> >> > > dev-unsubscribe@ambari.apache.org
> >> > > > >> > For additional commands, e-mail:
> >> > > dev-help@ambari.apache.org
> >> > > > >> >
> >> > > > >> >
> >> > > > >>
> >> > > > >>
> >> > >
> ---------------------------------------------------------------------
> >> > > > >> To unsubscribe, e-mail:
> >> > > dev-unsubscribe@ambari.apache.org
> >> > > > >> For additional commands, e-mail:
> >> > > dev-help@ambari.apache.org
> >> > > > >>
> >> > > > >>
> >> > > >
> >> > > >
> >> > > >
> >> > >
> ---------------------------------------------------------------------
> >> > > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> >> > > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> >> > > >
> >> > > >
> >> > >
> >> >
> >> >
> >> >
> ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> > For additional commands, e-mail: dev-help@ambari.apache.org
> >> >
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> For additional commands, e-mail: dev-help@ambari.apache.org
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> For additional commands, e-mail: dev-help@ambari.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.com>.
+1
On 2022/09/21 11:12, 吴治国 wrote:
> I think we have enough to go on with Kengo’s proposal,
> Currently we don’t have enough developers(and I’m not willing to) to maintain a stack on our own like BDP.
>
>> Sure, here's my proposal:
>>
>> * Stack name: "BIGTOP"
>>
>> - The same name as the existing one [1]
>> - Because it deploys the packages generated by Bigtop
>> - The existing stack should be replaced with it, because that is
>> based on Bigtop 0.8 and too old to use now
>> - No concern about infringing others' trademark
>>
>> * Component/folder name: "bigtop-select"
>>
>> - Consistent naming convention with the existing tools such as
>> "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
>> - If it sounds too simple and a bit unclear, a more descriptive name
>> might be an option, for example "bigtop-ambari-stack-selector"
>>
>> * Script name: "bigtop-select"
>>
>> - Consistent with the stack name
>> - No concern about infringing others' trademark
>>
>> [1]: https://github.com/apache/ambari/tree/release-2.7.6/ambari-server/src/main/resources/stacks/BIGTOP/0.8
>> [2]: https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common <https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common>
>
> Best Regards,
> Zhiguo Wu
>
>> On Sep 16, 2022, at 08:44, Masatake Iwasaki <iw...@oss.nttdata.com> wrote:
>>
>>
>>>>> May be we can name it as bdp-select. Or (bgp-select)
>>>> -1 as we already discussed.
>>> Thanks for your feedback, I would definitely honour it. As you are not open for discussion and asked us raise the PR hence you thought of discussing on the PR. What will be your final suggestion on this..?
>>
>> I'm -1 on the name like bdp-select or bgp-select as we discussed.
>> Feel free to open PR with appropriate module name.
>>
>> On 2022/09/05 16:30, Battula, Brahma Reddy wrote:
>>> Hi @Masatake Iwasaki,
>>>> -1 as we already discussed.
>>> Thanks for your feedback, I would definitely honour it. As you are not open for discussion and asked us raise the PR hence you thought of discussing on the PR. What will be your final suggestion on this..?
>>> @Roman Shaposhnik
>>> I just gone through the following jira[1] where you brought ambari to bigtop. Looks stack-select is not included, how it was maintained.?
>>> I thinking we should have one stack which can support for upgrading the existing the HDP deployed clusters. Even I can see somebody asking on bigtop[2].
>>> If bigtop is not right place, shall we include in ambari..? Please let me know your thoughts on this. This blocks the 2.7.7 release.
>>> Note : There is on-going ambari mpack which might take some more time. Even upgrades will take some time.
>>> 1. https://issues.apache.org/jira/browse/BIGTOP-709
>>> 2. https://issues.apache.org/jira/browse/BIGTOP-3651
>>> Regards,
>>> Brahma Reddy Battula
>>> On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com> wrote:
>>> > May be we can name it as bdp-select. Or (bgp-select)
>>> -1 as we already discussed.
>>> On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
>>> > Ok, thanks Viraj.
>>> >
>>> > Hopefully you can place here like all other how it's maintained. Let me know any help required on this. May be we can name it as bdp-select. Or (bgp-select)
>>> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
>>> >
>>> >
>>> > On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org> wrote:
>>> >
>>> > Masatake, Brahma,
>>> >
>>> > Hopefully I should be able to create Jira and PR in Bigtop. Will let you
>>> > know once ready for review. Thanks
>>> >
>>> >
>>> > On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <iw...@oss.nttdata.com>
>>> > wrote:
>>> >
>>> > > Please file a JIRA and submit a pull request if you want to show the code
>>> > > and get feedback.
>>> > > There is nothing I want to discuss off the record.
>>> > >
>>> > > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
>>> > > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get
>>> > > the final conclusion on this..?
>>> > > >
>>> > > > Please let me know your availability, Can have one call to discuss on
>>> > > this..
>>> > > >
>>> > > >
>>> > > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
>>> > > wrote:
>>> > > >
>>> > > > > -1 on development in branch.
>>> > > > > It is not worth for maintaining the branch if the modules is
>>> > > so small
>>> > > > > and barely updated as explained here.
>>> > > > > It should not conflict to existing code.
>>> > > > > I feel I must check the code before check-in based on this
>>> > > thread.
>>> > > >
>>> > > >
>>> > > > Sure, Viraj or me can show the code to you.
>>> > > >
>>> > > > Can we've call on this Friday/Thrusday if that works..?
>>> > > >
>>> > > >
>>> > > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
>>> > > iwasakims@oss.nttdata.com> wrote:
>>> > > >
>>> > > > > Sure, we can havemodule name like bigtop-distro-select.
>>> > > > > Initially we'll do this separate branch.
>>> > > >
>>> > > > -1 on development in branch.
>>> > > > It is not worth for maintaining the branch if the modules is so
>>> > > small
>>> > > > and barely updated as explained here.
>>> > > > It should not conflict to existing code.
>>> > > > I feel I must check the code before check-in based on this
>>> > > thread.
>>> > > >
>>> > > > Masatake Iwasaki
>>> > > >
>>> > > > On 2022/07/11 8:23, Kengo Seki wrote:
>>> > > > >> As there are different opinions on this and took long time,
>>> > > just to brainstorm all the possibilities and pitfalls.
>>> > > > >
>>> > > > > Oh, I interpreted your words "conclude" and "finalize" as you
>>> > > were
>>> > > > > going to make a final decision. Brainstorming is welcome, of
>>> > > course.
>>> > > > > (But I'm not so sure if all people concerned could join, due
>>> > > to time
>>> > > > > difference and their schedule, etc.)
>>> > > > >
>>> > > > >> Can you suggest, how the changes will be also.. like folder,
>>> > > where you suggest to keep this...?
>>> > > > >
>>> > > > > Sure, here's my proposal:
>>> > > > >
>>> > > > > * Stack name: "BIGTOP"
>>> > > > >
>>> > > > > - The same name as the existing one [1]
>>> > > > > - Because it deploys the packages generated by Bigtop
>>> > > > > - The existing stack should be replaced with it, because
>>> > > that is
>>> > > > > based on Bigtop 0.8 and too old to use now
>>> > > > > - No concern about infringing others' trademark
>>> > > > >
>>> > > > > * Component/folder name: "bigtop-select"
>>> > > > >
>>> > > > > - Consistent naming convention with the existing tools
>>> > > such as
>>> > > > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
>>> > > > > - If it sounds too simple and a bit unclear, a more
>>> > > descriptive name
>>> > > > > might be an option, for example "bigtop-ambari-stack-selector"
>>> > > > >
>>> > > > > * Script name: "bigtop-select"
>>> > > > >
>>> > > > > - Consistent with the stack name
>>> > > > > - No concern about infringing others' trademark
>>> > > > >
>>> > > > > [1]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
>>> > > > > [2]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
>>> > > > >
>>> > > > > Kengo Seki <se...@apache.org>
>>> > > > >
>>> > > > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
>>> > > > > <bb...@visa.com.invalid> wrote:
>>> > > > >>
>>> > > > >>> Technical decisions shouldn't be done on other places
>>> > > than public mailing lists,
>>> > > > >>> as described in the "Open Communications" section of [1]
>>> > > and [2].
>>> > > > >> > So we should conclude the discussion in this mailing
>>> > > list.
>>> > > > >> > (And with my poor English, I'm not so confident to catch
>>> > > up with your
>>> > > > >> > fluent talk ;)
>>> > > > >>
>>> > > > >> I believe , I knew the apache way which you mentioned. We
>>> > > are not going conclude anything which comes to bigtop other than this
>>> > > mailing list.
>>> > > > >> As there are different opinions on this and took long time,
>>> > > just to brainstorm all the possibilities and pitfalls. Hence asking let's
>>> > > have call so that we can brainstorm. Even after call, everything will be
>>> > > published what we discussed.
>>> > > > >>
>>> > > > >> I think, whiteboarding will help to catch up with you.
>>> > > > >>
>>> > > > >> You all the think "bigtop-select" will be best option
>>> > > right..? Can you suggest, how the changes will be also.. like folder, where
>>> > > you suggest to keep this...?
>>> > > > >>
>>> > > > >> And if the name represents the stack which we are going to
>>> > > deploy should fine I feel.. (if it's not BDP, may be
>>> > > OBDP:OpensourceBigDataPlatform.)
>>> > > > >>
>>> > > > >> @Viraj Jasani and others any thoughts..?
>>> > > > >>
>>> > > > >>
>>> > > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org>
>>> > > wrote:
>>> > > > >>
>>> > > > >> > Looks we had so much discussed here, Let's try to
>>> > > conclude. Can we've one call on this and finalize this..?
>>> > > > >>
>>> > > > >> Technical decisions shouldn't be done on other places
>>> > > than public mailing lists,
>>> > > > >> as described in the "Open Communications" section of
>>> > > [1] and [2].
>>> > > > >> So we should conclude the discussion in this mailing
>>> > > list.
>>> > > > >> (And with my poor English, I'm not so confident to
>>> > > catch up with your
>>> > > > >> fluent talk ;)
>>> > > > >>
>>> > > > >> > FYI. Even looks bigtop used some where also..
>>> > > > >>
>>> > > > >> Bigtop is ASF's trademark as you can see in the "Apache
>>> > > Bigtop®
>>> > > > >> software" section of [3].
>>> > > > >> So it doesn't have the risk of trademark infringement.
>>> > > > >>
>>> > > > >> [1]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
>>> > > > >> [2]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
>>> > > > >> [3]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
>>> > > > >>
>>> > > > >> Kengo Seki <se...@apache.org>
>>> > > > >>
>>> > > > >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
>>> > > > >> <bb...@visa.com.invalid> wrote:
>>> > > > >> >
>>> > > > >> > Looks we had so much discussed here, Let's try to
>>> > > conclude. Can we've one call on this and finalize this..?
>>> > > > >> >
>>> > > > >> > FYI. Even looks bigtop used some where[1] also..
>>> > > > >> > 1.
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
>>> > > > >> >
>>> > > > >> >
>>> > > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
>>> > > wrote:
>>> > > > >> >
>>> > > > >> > Thank you for your explanation, Brahma.
>>> > > > >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP"
>>> > > [1]) is supposed to be a
>>> > > > >> > trademark of Redoop, so they can name the script
>>> > > crh-select without
>>> > > > >> > problem.
>>> > > > >> > But regarding BDP for example, I can easily find
>>> > > products that have
>>> > > > >> > the same name [2][3][4] as you already mentioned,
>>> > > so I'd like to
>>> > > > >> > recommend bigtop-select for avoiding unnecessary
>>> > > trouble.
>>> > > > >> > Or, a single and more general word just like
>>> > > conf-select may be less
>>> > > > >> > troublesome than bdp. How about "stack-select",
>>> > > for example?
>>> > > > >> >
>>> > > > >> > [1]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
>>> > > > >> > [2]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
>>> > > > >> > [3]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
>>> > > > >> > [4]:
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
>>> > > > >> >
>>> > > > >> > Kengo Seki <se...@apache.org>
>>> > > > >> >
>>> > > > >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma
>>> > > Reddy <bb...@visa.com> wrote:
>>> > > > >> > >
>>> > > > >> > > >Do you mean that you're going to name the
>>> > > module (same as "component"
>>> > > > >> > > >in the Bigtop terminology, I think)
>>> > > bigtop-distro-select,
>>> > > > >> > > >and still the script in question
>>> > > bdp-select? If so, is there any
>>> > > > >> > > >reason that the script must be that name?
>>> > > > >> > > >(No offence, I just want to understand
>>> > > your thoughts and its
>>> > > > >> > > >background, and avoid the conflict or
>>> > > user's confusion with existing
>>> > > > >> > > >trademarks or products)
>>> > > > >> > >
>>> > > > >> > > Thanks @Kengo Seki for consolidating all the
>>> > > concerns. Name should represent the stack which includes all the components
>>> > > hence planning to have like bdp,bds...and this only one file like below[1]
>>> > > which has done redoop.
>>> > > > >> > >
>>> > > > >> > >
>>> > > > >> > >
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
>>> > > > >> > >
>>> > > > >> > >
>>> > > > >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
>>> > > sekikn@apache.org> wrote:
>>> > > > >> > >
>>> > > > >> > > The following concern Masatake mentioned
>>> > > before is an important point,
>>> > > > >> > > so I talked to Brahma for clarifying his
>>> > > intention on the ASF Slack
>>> > > > >> > > yesterday.
>>> > > > >> > >
>>> > > > >> > > > Multiple versions of the same package
>>> > > (deb/rpm) can not be installed at the same time.
>>> > > > >> > > > IIRC, HDP uses convention in which the
>>> > > product version is part of package name
>>> > > > >> > > > for addressing this.
>>> > > > >> > >
>>> > > > >> > > > I don't like to bring the awkward package
>>> > > name convention to Bigtop
>>> > > > >> > > > at least by default.
>>> > > > >> > >
>>> > > > >> > > He's planning to adopt the same mitigation
>>> > > as HDP for now, but he
>>> > > > >> > > doesn't intend to change the default
>>> > > package naming convention of
>>> > > > >> > > Bigtop,
>>> > > > >> > > but just add a new functionality to include
>>> > > an extra part into the
>>> > > > >> > > package name for avoiding conflict, which
>>> > > is disabled by default.
>>> > > > >> > >
>>> > > > >> > > And Brahma, let me confirm about the
>>> > > following reply:
>>> > > > >> > >
>>> > > > >> > > > Sure, we can have module name like
>>> > > bigtop-distro-select.
>>> > > > >> > >
>>> > > > >> > > Do you mean that you're going to name the
>>> > > module (same as "component"
>>> > > > >> > > in the Bigtop terminology, I think)
>>> > > bigtop-distro-select,
>>> > > > >> > > and still the script in question
>>> > > bdp-select? If so, is there any
>>> > > > >> > > reason that the script must be that name?
>>> > > > >> > > (No offence, I just want to understand your
>>> > > thoughts and its
>>> > > > >> > > background, and avoid the conflict or
>>> > > user's confusion with existing
>>> > > > >> > > trademarks or products)
>>> > > > >> > >
>>> > > > >> > > Kengo Seki <se...@apache.org>
>>> > > > >> > >
>>> > > > >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula,
>>> > > Brahma Reddy
>>> > > > >> > > <bb...@visa.com.invalid> wrote:
>>> > > > >> > > >
>>> > > > >> > > > > The name of stack based no Bigtop
>>> > > should be Bigtop.
>>> > > > >> > > > > If you can not accept the name like
>>> > > bigtop-*, the work should done outside of Bigtop.
>>> > > > >> > > > > I will cast -1 if someone submit a
>>> > > patch to add a module with the name spoiling branding.
>>> > > > >> > > >
>>> > > > >> > > > Sure, we can have module name like
>>> > > bigtop-distro-select.
>>> > > > >> > > > Initially we'll do this separate branch.
>>> > > > >> > > >
>>> > > > >> > > >
>>> > > > >> > > >
>>> > > > >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
>>> > > iwasakims@oss.nttdata.co.jp> wrote:
>>> > > > >> > > >
>>> > > > >> > > > > I believe it's for project name.
>>> > > isn't it.?
>>> > > > >> > > >
>>> > > > >> > > > projects and products.
>>> > > > >> > > >
>>> > > > >> > > > > IMO, We need to create folders and
>>> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
>>> > > > >> > > >
>>> > > > >> > > > The name of stack based no Bigtop
>>> > > should be Bigtop.
>>> > > > >> > > > If you can not accept the name like
>>> > > bigtop-*, the work should done outside of Bigtop.
>>> > > > >> > > > I will cast -1 if someone submit a
>>> > > patch to add a module with the name spoiling branding.
>>> > > > >> > > >
>>> > > > >> > > >
>>> > > > >> > > > On 2022/07/06 11:44, Battula, Brahma
>>> > > Reddy wrote:
>>> > > > >> > > > >
>>> > > > >> > > > > I believe it's for project name.
>>> > > isn't it.?
>>> > > > >> > > > >
>>> > > > >> > > > >
>>> > > > >> > > > > On 06/07/22, 7:27 AM, "Masatake
>>> > > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>> > > > >> > > > >
>>> > > > >> > > > > > But As we are not releasing
>>> > > as enterprise should be fine I think. IMO, We need to create folders and
>>> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
>>> > > > >> > > > >
>>> > > > >> > > > > Not fine.
>>> > > > >> > > > > We have a trademark policy.
>>> > > > >> > > > >
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
>>> > > > >> > > > >
>>> > > > >> > > > > On 2022/07/06 10:37, Battula,
>>> > > Brahma Reddy wrote:
>>> > > > >> > > > > >> Should we avoid
>>> > > unrecognized brand which may be trademark of someone?
>>> > > > >> > > > > >> ambari-select or
>>> > > bigtop-select should be enough.
>>> > > > >> > > > > >
>>> > > > >> > > > > > Not sure, where to confirm
>>> > > whether there is already trademark. When I googled found so many.
>>> > > > >> > > > > > But As we are not releasing
>>> > > as enterprise should be fine I think. IMO, We need to create folders and
>>> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
>>> > > > >> > > > > > May be you can refer the
>>> > > initial proposal [2] where I mentioned some more names.
>>> > > (BDS-BigDataStack,OSS-OpenSourceSelect..)
>>> > > > >> > > > > >
>>> > > > >> > > > > > Finally thanks a bunch for
>>> > > long healthy discussions on this. Mostly we all same page now.
>>> > > > >> > > > > >
>>> > > > >> > > > > > 1.
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
>>> > > > >> > > > > >
>>> > > > >> > > > > > 2.
>>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
>>> > > > >> > > > > >
>>> > > > >> > > > > >
>>> > > > >> > > > > > On 06/07/22, 4:01 AM,
>>> > > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>> > > > >> > > > > >
>>> > > > >> > > > > > > We have still not
>>> > > officially finalized the new replacement name for
>>> > > > >> > > > > > > hdp-select, it would
>>> > > likely be bdp-select (bdp: BigData Platform). However,
>>> > > > >> > > > > > > the purpose of
>>> > > bdp-select and conf-select remains the same.
>>> > > > >> > > > > >
>>> > > > >> > > > > > Should we avoid
>>> > > unrecognized brand which may be trademark of someone?
>>> > > > >> > > > > > ambari-select or
>>> > > bigtop-select should be enough.
>>> > > > >> > > > > >
>>> > > > >> > > > > > On 2022/06/29 13:52,
>>> > > Viraj Jasani wrote:
>>> > > > >> > > > > > > Hi Ambari/Bigtop dev,
>>> > > > >> > > > > > >
>>> > > > >> > > > > > > As per the new
>>> > > roadmap of Apache Ambari, we would like to propose moving
>>> > > > >> > > > > > > certain scripts
>>> > > (previously known as hdp-select and conf-select) to Bigtop
>>> > > > >> > > > > > > so that their rpm
>>> > > installation could be managed independently.
>>> > > > >> > > > > > > These scripts are a
>>> > > basic necessity in the Ambari framework for the
>>> > > > >> > > > > > > installation of
>>> > > various Bigdata packages. The only major changes they would
>>> > > > >> > > > > > > receive is when we
>>> > > onboard new services and components to Ambari, else they
>>> > > > >> > > > > > > usually do not
>>> > > receive updates. In the past, we used to get hdp-select rpm
>>> > > > >> > > > > > > downloaded and
>>> > > installed from HDP repositories.
>>> > > > >> > > > > > >
>>> > > > >> > > > > > > We have still not
>>> > > officially finalized the new replacement name for
>>> > > > >> > > > > > > hdp-select, it would
>>> > > likely be bdp-select (bdp: BigData Platform). However,
>>> > > > >> > > > > > > the purpose of
>>> > > bdp-select and conf-select remains the same.
>>> > > > >> > > > > > >
>>> > > > >> > > > > >
>>> > > > >> > > > >
>>> > > > >> > > >
>>> > > > >> > > >
>>> > > > >> > > >
>>> > > ---------------------------------------------------------------------
>>> > > > >> > > > To unsubscribe, e-mail:
>>> > > dev-unsubscribe@ambari.apache.org
>>> > > > >> > > > For additional commands, e-mail:
>>> > > dev-help@ambari.apache.org
>>> > > > >> > > >
>>> > > > >> > >
>>> > > > >> > >
>>> > > ---------------------------------------------------------------------
>>> > > > >> > > To unsubscribe, e-mail:
>>> > > dev-unsubscribe@ambari.apache.org
>>> > > > >> > > For additional commands, e-mail:
>>> > > dev-help@ambari.apache.org
>>> > > > >> > >
>>> > > > >> > >
>>> > > > >> >
>>> > > > >> >
>>> > > ---------------------------------------------------------------------
>>> > > > >> > To unsubscribe, e-mail:
>>> > > dev-unsubscribe@ambari.apache.org
>>> > > > >> > For additional commands, e-mail:
>>> > > dev-help@ambari.apache.org
>>> > > > >> >
>>> > > > >> >
>>> > > > >>
>>> > > > >>
>>> > > ---------------------------------------------------------------------
>>> > > > >> To unsubscribe, e-mail:
>>> > > dev-unsubscribe@ambari.apache.org
>>> > > > >> For additional commands, e-mail:
>>> > > dev-help@ambari.apache.org
>>> > > > >>
>>> > > > >>
>>> > > >
>>> > > >
>>> > > >
>>> > > ---------------------------------------------------------------------
>>> > > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>> > > > For additional commands, e-mail: dev-help@ambari.apache.org
>>> > > >
>>> > > >
>>> > >
>>> >
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>> > For additional commands, e-mail: dev-help@ambari.apache.org
>>> >
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>> For additional commands, e-mail: dev-help@ambari.apache.org
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>> For additional commands, e-mail: dev-help@ambari.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by 吴治国 <wz...@163.com>.
I think we have enough to go on with Kengo’s proposal,
Currently we don’t have enough developers(and I’m not willing to) to maintain a stack on our own like BDP.
> Sure, here's my proposal:
>
> * Stack name: "BIGTOP"
>
> - The same name as the existing one [1]
> - Because it deploys the packages generated by Bigtop
> - The existing stack should be replaced with it, because that is
> based on Bigtop 0.8 and too old to use now
> - No concern about infringing others' trademark
>
> * Component/folder name: "bigtop-select"
>
> - Consistent naming convention with the existing tools such as
> "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> - If it sounds too simple and a bit unclear, a more descriptive name
> might be an option, for example "bigtop-ambari-stack-selector"
>
> * Script name: "bigtop-select"
>
> - Consistent with the stack name
> - No concern about infringing others' trademark
>
> [1]: https://github.com/apache/ambari/tree/release-2.7.6/ambari-server/src/main/resources/stacks/BIGTOP/0.8
> [2]: https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common <https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common>
Best Regards,
Zhiguo Wu
> On Sep 16, 2022, at 08:44, Masatake Iwasaki <iw...@oss.nttdata.com> wrote:
>
>
>>>> May be we can name it as bdp-select. Or (bgp-select)
>>> -1 as we already discussed.
>> Thanks for your feedback, I would definitely honour it. As you are not open for discussion and asked us raise the PR hence you thought of discussing on the PR. What will be your final suggestion on this..?
>
> I'm -1 on the name like bdp-select or bgp-select as we discussed.
> Feel free to open PR with appropriate module name.
>
> On 2022/09/05 16:30, Battula, Brahma Reddy wrote:
>> Hi @Masatake Iwasaki,
>>> -1 as we already discussed.
>> Thanks for your feedback, I would definitely honour it. As you are not open for discussion and asked us raise the PR hence you thought of discussing on the PR. What will be your final suggestion on this..?
>> @Roman Shaposhnik
>> I just gone through the following jira[1] where you brought ambari to bigtop. Looks stack-select is not included, how it was maintained.?
>> I thinking we should have one stack which can support for upgrading the existing the HDP deployed clusters. Even I can see somebody asking on bigtop[2].
>> If bigtop is not right place, shall we include in ambari..? Please let me know your thoughts on this. This blocks the 2.7.7 release.
>> Note : There is on-going ambari mpack which might take some more time. Even upgrades will take some time.
>> 1. https://issues.apache.org/jira/browse/BIGTOP-709
>> 2. https://issues.apache.org/jira/browse/BIGTOP-3651
>> Regards,
>> Brahma Reddy Battula
>> On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com> wrote:
>> > May be we can name it as bdp-select. Or (bgp-select)
>> -1 as we already discussed.
>> On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
>> > Ok, thanks Viraj.
>> >
>> > Hopefully you can place here like all other how it's maintained. Let me know any help required on this. May be we can name it as bdp-select. Or (bgp-select)
>> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
>> >
>> >
>> > On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org> wrote:
>> >
>> > Masatake, Brahma,
>> >
>> > Hopefully I should be able to create Jira and PR in Bigtop. Will let you
>> > know once ready for review. Thanks
>> >
>> >
>> > On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <iw...@oss.nttdata.com>
>> > wrote:
>> >
>> > > Please file a JIRA and submit a pull request if you want to show the code
>> > > and get feedback.
>> > > There is nothing I want to discuss off the record.
>> > >
>> > > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
>> > > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get
>> > > the final conclusion on this..?
>> > > >
>> > > > Please let me know your availability, Can have one call to discuss on
>> > > this..
>> > > >
>> > > >
>> > > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
>> > > wrote:
>> > > >
>> > > > > -1 on development in branch.
>> > > > > It is not worth for maintaining the branch if the modules is
>> > > so small
>> > > > > and barely updated as explained here.
>> > > > > It should not conflict to existing code.
>> > > > > I feel I must check the code before check-in based on this
>> > > thread.
>> > > >
>> > > >
>> > > > Sure, Viraj or me can show the code to you.
>> > > >
>> > > > Can we've call on this Friday/Thrusday if that works..?
>> > > >
>> > > >
>> > > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
>> > > iwasakims@oss.nttdata.com> wrote:
>> > > >
>> > > > > Sure, we can havemodule name like bigtop-distro-select.
>> > > > > Initially we'll do this separate branch.
>> > > >
>> > > > -1 on development in branch.
>> > > > It is not worth for maintaining the branch if the modules is so
>> > > small
>> > > > and barely updated as explained here.
>> > > > It should not conflict to existing code.
>> > > > I feel I must check the code before check-in based on this
>> > > thread.
>> > > >
>> > > > Masatake Iwasaki
>> > > >
>> > > > On 2022/07/11 8:23, Kengo Seki wrote:
>> > > > >> As there are different opinions on this and took long time,
>> > > just to brainstorm all the possibilities and pitfalls.
>> > > > >
>> > > > > Oh, I interpreted your words "conclude" and "finalize" as you
>> > > were
>> > > > > going to make a final decision. Brainstorming is welcome, of
>> > > course.
>> > > > > (But I'm not so sure if all people concerned could join, due
>> > > to time
>> > > > > difference and their schedule, etc.)
>> > > > >
>> > > > >> Can you suggest, how the changes will be also.. like folder,
>> > > where you suggest to keep this...?
>> > > > >
>> > > > > Sure, here's my proposal:
>> > > > >
>> > > > > * Stack name: "BIGTOP"
>> > > > >
>> > > > > - The same name as the existing one [1]
>> > > > > - Because it deploys the packages generated by Bigtop
>> > > > > - The existing stack should be replaced with it, because
>> > > that is
>> > > > > based on Bigtop 0.8 and too old to use now
>> > > > > - No concern about infringing others' trademark
>> > > > >
>> > > > > * Component/folder name: "bigtop-select"
>> > > > >
>> > > > > - Consistent naming convention with the existing tools
>> > > such as
>> > > > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
>> > > > > - If it sounds too simple and a bit unclear, a more
>> > > descriptive name
>> > > > > might be an option, for example "bigtop-ambari-stack-selector"
>> > > > >
>> > > > > * Script name: "bigtop-select"
>> > > > >
>> > > > > - Consistent with the stack name
>> > > > > - No concern about infringing others' trademark
>> > > > >
>> > > > > [1]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
>> > > > > [2]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
>> > > > >
>> > > > > Kengo Seki <se...@apache.org>
>> > > > >
>> > > > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
>> > > > > <bb...@visa.com.invalid> wrote:
>> > > > >>
>> > > > >>> Technical decisions shouldn't be done on other places
>> > > than public mailing lists,
>> > > > >>> as described in the "Open Communications" section of [1]
>> > > and [2].
>> > > > >> > So we should conclude the discussion in this mailing
>> > > list.
>> > > > >> > (And with my poor English, I'm not so confident to catch
>> > > up with your
>> > > > >> > fluent talk ;)
>> > > > >>
>> > > > >> I believe , I knew the apache way which you mentioned. We
>> > > are not going conclude anything which comes to bigtop other than this
>> > > mailing list.
>> > > > >> As there are different opinions on this and took long time,
>> > > just to brainstorm all the possibilities and pitfalls. Hence asking let's
>> > > have call so that we can brainstorm. Even after call, everything will be
>> > > published what we discussed.
>> > > > >>
>> > > > >> I think, whiteboarding will help to catch up with you.
>> > > > >>
>> > > > >> You all the think "bigtop-select" will be best option
>> > > right..? Can you suggest, how the changes will be also.. like folder, where
>> > > you suggest to keep this...?
>> > > > >>
>> > > > >> And if the name represents the stack which we are going to
>> > > deploy should fine I feel.. (if it's not BDP, may be
>> > > OBDP:OpensourceBigDataPlatform.)
>> > > > >>
>> > > > >> @Viraj Jasani and others any thoughts..?
>> > > > >>
>> > > > >>
>> > > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org>
>> > > wrote:
>> > > > >>
>> > > > >> > Looks we had so much discussed here, Let's try to
>> > > conclude. Can we've one call on this and finalize this..?
>> > > > >>
>> > > > >> Technical decisions shouldn't be done on other places
>> > > than public mailing lists,
>> > > > >> as described in the "Open Communications" section of
>> > > [1] and [2].
>> > > > >> So we should conclude the discussion in this mailing
>> > > list.
>> > > > >> (And with my poor English, I'm not so confident to
>> > > catch up with your
>> > > > >> fluent talk ;)
>> > > > >>
>> > > > >> > FYI. Even looks bigtop used some where also..
>> > > > >>
>> > > > >> Bigtop is ASF's trademark as you can see in the "Apache
>> > > Bigtop®
>> > > > >> software" section of [3].
>> > > > >> So it doesn't have the risk of trademark infringement.
>> > > > >>
>> > > > >> [1]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
>> > > > >> [2]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
>> > > > >> [3]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
>> > > > >>
>> > > > >> Kengo Seki <se...@apache.org>
>> > > > >>
>> > > > >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
>> > > > >> <bb...@visa.com.invalid> wrote:
>> > > > >> >
>> > > > >> > Looks we had so much discussed here, Let's try to
>> > > conclude. Can we've one call on this and finalize this..?
>> > > > >> >
>> > > > >> > FYI. Even looks bigtop used some where[1] also..
>> > > > >> > 1.
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
>> > > > >> >
>> > > > >> >
>> > > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
>> > > wrote:
>> > > > >> >
>> > > > >> > Thank you for your explanation, Brahma.
>> > > > >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP"
>> > > [1]) is supposed to be a
>> > > > >> > trademark of Redoop, so they can name the script
>> > > crh-select without
>> > > > >> > problem.
>> > > > >> > But regarding BDP for example, I can easily find
>> > > products that have
>> > > > >> > the same name [2][3][4] as you already mentioned,
>> > > so I'd like to
>> > > > >> > recommend bigtop-select for avoiding unnecessary
>> > > trouble.
>> > > > >> > Or, a single and more general word just like
>> > > conf-select may be less
>> > > > >> > troublesome than bdp. How about "stack-select",
>> > > for example?
>> > > > >> >
>> > > > >> > [1]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
>> > > > >> > [2]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
>> > > > >> > [3]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
>> > > > >> > [4]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
>> > > > >> >
>> > > > >> > Kengo Seki <se...@apache.org>
>> > > > >> >
>> > > > >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma
>> > > Reddy <bb...@visa.com> wrote:
>> > > > >> > >
>> > > > >> > > >Do you mean that you're going to name the
>> > > module (same as "component"
>> > > > >> > > >in the Bigtop terminology, I think)
>> > > bigtop-distro-select,
>> > > > >> > > >and still the script in question
>> > > bdp-select? If so, is there any
>> > > > >> > > >reason that the script must be that name?
>> > > > >> > > >(No offence, I just want to understand
>> > > your thoughts and its
>> > > > >> > > >background, and avoid the conflict or
>> > > user's confusion with existing
>> > > > >> > > >trademarks or products)
>> > > > >> > >
>> > > > >> > > Thanks @Kengo Seki for consolidating all the
>> > > concerns. Name should represent the stack which includes all the components
>> > > hence planning to have like bdp,bds...and this only one file like below[1]
>> > > which has done redoop.
>> > > > >> > >
>> > > > >> > >
>> > > > >> > >
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
>> > > > >> > >
>> > > > >> > >
>> > > > >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
>> > > sekikn@apache.org> wrote:
>> > > > >> > >
>> > > > >> > > The following concern Masatake mentioned
>> > > before is an important point,
>> > > > >> > > so I talked to Brahma for clarifying his
>> > > intention on the ASF Slack
>> > > > >> > > yesterday.
>> > > > >> > >
>> > > > >> > > > Multiple versions of the same package
>> > > (deb/rpm) can not be installed at the same time.
>> > > > >> > > > IIRC, HDP uses convention in which the
>> > > product version is part of package name
>> > > > >> > > > for addressing this.
>> > > > >> > >
>> > > > >> > > > I don't like to bring the awkward package
>> > > name convention to Bigtop
>> > > > >> > > > at least by default.
>> > > > >> > >
>> > > > >> > > He's planning to adopt the same mitigation
>> > > as HDP for now, but he
>> > > > >> > > doesn't intend to change the default
>> > > package naming convention of
>> > > > >> > > Bigtop,
>> > > > >> > > but just add a new functionality to include
>> > > an extra part into the
>> > > > >> > > package name for avoiding conflict, which
>> > > is disabled by default.
>> > > > >> > >
>> > > > >> > > And Brahma, let me confirm about the
>> > > following reply:
>> > > > >> > >
>> > > > >> > > > Sure, we can have module name like
>> > > bigtop-distro-select.
>> > > > >> > >
>> > > > >> > > Do you mean that you're going to name the
>> > > module (same as "component"
>> > > > >> > > in the Bigtop terminology, I think)
>> > > bigtop-distro-select,
>> > > > >> > > and still the script in question
>> > > bdp-select? If so, is there any
>> > > > >> > > reason that the script must be that name?
>> > > > >> > > (No offence, I just want to understand your
>> > > thoughts and its
>> > > > >> > > background, and avoid the conflict or
>> > > user's confusion with existing
>> > > > >> > > trademarks or products)
>> > > > >> > >
>> > > > >> > > Kengo Seki <se...@apache.org>
>> > > > >> > >
>> > > > >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula,
>> > > Brahma Reddy
>> > > > >> > > <bb...@visa.com.invalid> wrote:
>> > > > >> > > >
>> > > > >> > > > > The name of stack based no Bigtop
>> > > should be Bigtop.
>> > > > >> > > > > If you can not accept the name like
>> > > bigtop-*, the work should done outside of Bigtop.
>> > > > >> > > > > I will cast -1 if someone submit a
>> > > patch to add a module with the name spoiling branding.
>> > > > >> > > >
>> > > > >> > > > Sure, we can have module name like
>> > > bigtop-distro-select.
>> > > > >> > > > Initially we'll do this separate branch.
>> > > > >> > > >
>> > > > >> > > >
>> > > > >> > > >
>> > > > >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
>> > > iwasakims@oss.nttdata.co.jp> wrote:
>> > > > >> > > >
>> > > > >> > > > > I believe it's for project name.
>> > > isn't it.?
>> > > > >> > > >
>> > > > >> > > > projects and products.
>> > > > >> > > >
>> > > > >> > > > > IMO, We need to create folders and
>> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > > >> > > >
>> > > > >> > > > The name of stack based no Bigtop
>> > > should be Bigtop.
>> > > > >> > > > If you can not accept the name like
>> > > bigtop-*, the work should done outside of Bigtop.
>> > > > >> > > > I will cast -1 if someone submit a
>> > > patch to add a module with the name spoiling branding.
>> > > > >> > > >
>> > > > >> > > >
>> > > > >> > > > On 2022/07/06 11:44, Battula, Brahma
>> > > Reddy wrote:
>> > > > >> > > > >
>> > > > >> > > > > I believe it's for project name.
>> > > isn't it.?
>> > > > >> > > > >
>> > > > >> > > > >
>> > > > >> > > > > On 06/07/22, 7:27 AM, "Masatake
>> > > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > > >> > > > >
>> > > > >> > > > > > But As we are not releasing
>> > > as enterprise should be fine I think. IMO, We need to create folders and
>> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > > >> > > > >
>> > > > >> > > > > Not fine.
>> > > > >> > > > > We have a trademark policy.
>> > > > >> > > > >
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
>> > > > >> > > > >
>> > > > >> > > > > On 2022/07/06 10:37, Battula,
>> > > Brahma Reddy wrote:
>> > > > >> > > > > >> Should we avoid
>> > > unrecognized brand which may be trademark of someone?
>> > > > >> > > > > >> ambari-select or
>> > > bigtop-select should be enough.
>> > > > >> > > > > >
>> > > > >> > > > > > Not sure, where to confirm
>> > > whether there is already trademark. When I googled found so many.
>> > > > >> > > > > > But As we are not releasing
>> > > as enterprise should be fine I think. IMO, We need to create folders and
>> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > > >> > > > > > May be you can refer the
>> > > initial proposal [2] where I mentioned some more names.
>> > > (BDS-BigDataStack,OSS-OpenSourceSelect..)
>> > > > >> > > > > >
>> > > > >> > > > > > Finally thanks a bunch for
>> > > long healthy discussions on this. Mostly we all same page now.
>> > > > >> > > > > >
>> > > > >> > > > > > 1.
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
>> > > > >> > > > > >
>> > > > >> > > > > > 2.
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
>> > > > >> > > > > >
>> > > > >> > > > > >
>> > > > >> > > > > > On 06/07/22, 4:01 AM,
>> > > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > > >> > > > > >
>> > > > >> > > > > > > We have still not
>> > > officially finalized the new replacement name for
>> > > > >> > > > > > > hdp-select, it would
>> > > likely be bdp-select (bdp: BigData Platform). However,
>> > > > >> > > > > > > the purpose of
>> > > bdp-select and conf-select remains the same.
>> > > > >> > > > > >
>> > > > >> > > > > > Should we avoid
>> > > unrecognized brand which may be trademark of someone?
>> > > > >> > > > > > ambari-select or
>> > > bigtop-select should be enough.
>> > > > >> > > > > >
>> > > > >> > > > > > On 2022/06/29 13:52,
>> > > Viraj Jasani wrote:
>> > > > >> > > > > > > Hi Ambari/Bigtop dev,
>> > > > >> > > > > > >
>> > > > >> > > > > > > As per the new
>> > > roadmap of Apache Ambari, we would like to propose moving
>> > > > >> > > > > > > certain scripts
>> > > (previously known as hdp-select and conf-select) to Bigtop
>> > > > >> > > > > > > so that their rpm
>> > > installation could be managed independently.
>> > > > >> > > > > > > These scripts are a
>> > > basic necessity in the Ambari framework for the
>> > > > >> > > > > > > installation of
>> > > various Bigdata packages. The only major changes they would
>> > > > >> > > > > > > receive is when we
>> > > onboard new services and components to Ambari, else they
>> > > > >> > > > > > > usually do not
>> > > receive updates. In the past, we used to get hdp-select rpm
>> > > > >> > > > > > > downloaded and
>> > > installed from HDP repositories.
>> > > > >> > > > > > >
>> > > > >> > > > > > > We have still not
>> > > officially finalized the new replacement name for
>> > > > >> > > > > > > hdp-select, it would
>> > > likely be bdp-select (bdp: BigData Platform). However,
>> > > > >> > > > > > > the purpose of
>> > > bdp-select and conf-select remains the same.
>> > > > >> > > > > > >
>> > > > >> > > > > >
>> > > > >> > > > >
>> > > > >> > > >
>> > > > >> > > >
>> > > > >> > > >
>> > > ---------------------------------------------------------------------
>> > > > >> > > > To unsubscribe, e-mail:
>> > > dev-unsubscribe@ambari.apache.org
>> > > > >> > > > For additional commands, e-mail:
>> > > dev-help@ambari.apache.org
>> > > > >> > > >
>> > > > >> > >
>> > > > >> > >
>> > > ---------------------------------------------------------------------
>> > > > >> > > To unsubscribe, e-mail:
>> > > dev-unsubscribe@ambari.apache.org
>> > > > >> > > For additional commands, e-mail:
>> > > dev-help@ambari.apache.org
>> > > > >> > >
>> > > > >> > >
>> > > > >> >
>> > > > >> >
>> > > ---------------------------------------------------------------------
>> > > > >> > To unsubscribe, e-mail:
>> > > dev-unsubscribe@ambari.apache.org
>> > > > >> > For additional commands, e-mail:
>> > > dev-help@ambari.apache.org
>> > > > >> >
>> > > > >> >
>> > > > >>
>> > > > >>
>> > > ---------------------------------------------------------------------
>> > > > >> To unsubscribe, e-mail:
>> > > dev-unsubscribe@ambari.apache.org
>> > > > >> For additional commands, e-mail:
>> > > dev-help@ambari.apache.org
>> > > > >>
>> > > > >>
>> > > >
>> > > >
>> > > >
>> > > ---------------------------------------------------------------------
>> > > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > > > For additional commands, e-mail: dev-help@ambari.apache.org
>> > > >
>> > > >
>> > >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > For additional commands, e-mail: dev-help@ambari.apache.org
>> >
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> For additional commands, e-mail: dev-help@ambari.apache.org
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> For additional commands, e-mail: dev-help@ambari.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by 吴治国 <wz...@163.com>.
I think we have enough to go on with Kengo’s proposal,
Currently we don’t have enough developers(and I’m not willing to) to maintain a stack on our own like BDP.
> Sure, here's my proposal:
>
> * Stack name: "BIGTOP"
>
> - The same name as the existing one [1]
> - Because it deploys the packages generated by Bigtop
> - The existing stack should be replaced with it, because that is
> based on Bigtop 0.8 and too old to use now
> - No concern about infringing others' trademark
>
> * Component/folder name: "bigtop-select"
>
> - Consistent naming convention with the existing tools such as
> "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> - If it sounds too simple and a bit unclear, a more descriptive name
> might be an option, for example "bigtop-ambari-stack-selector"
>
> * Script name: "bigtop-select"
>
> - Consistent with the stack name
> - No concern about infringing others' trademark
>
> [1]: https://github.com/apache/ambari/tree/release-2.7.6/ambari-server/src/main/resources/stacks/BIGTOP/0.8
> [2]: https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common <https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common>
Best Regards,
Zhiguo Wu
> On Sep 16, 2022, at 08:44, Masatake Iwasaki <iw...@oss.nttdata.com> wrote:
>
>
>>>> May be we can name it as bdp-select. Or (bgp-select)
>>> -1 as we already discussed.
>> Thanks for your feedback, I would definitely honour it. As you are not open for discussion and asked us raise the PR hence you thought of discussing on the PR. What will be your final suggestion on this..?
>
> I'm -1 on the name like bdp-select or bgp-select as we discussed.
> Feel free to open PR with appropriate module name.
>
> On 2022/09/05 16:30, Battula, Brahma Reddy wrote:
>> Hi @Masatake Iwasaki,
>>> -1 as we already discussed.
>> Thanks for your feedback, I would definitely honour it. As you are not open for discussion and asked us raise the PR hence you thought of discussing on the PR. What will be your final suggestion on this..?
>> @Roman Shaposhnik
>> I just gone through the following jira[1] where you brought ambari to bigtop. Looks stack-select is not included, how it was maintained.?
>> I thinking we should have one stack which can support for upgrading the existing the HDP deployed clusters. Even I can see somebody asking on bigtop[2].
>> If bigtop is not right place, shall we include in ambari..? Please let me know your thoughts on this. This blocks the 2.7.7 release.
>> Note : There is on-going ambari mpack which might take some more time. Even upgrades will take some time.
>> 1. https://issues.apache.org/jira/browse/BIGTOP-709
>> 2. https://issues.apache.org/jira/browse/BIGTOP-3651
>> Regards,
>> Brahma Reddy Battula
>> On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com> wrote:
>> > May be we can name it as bdp-select. Or (bgp-select)
>> -1 as we already discussed.
>> On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
>> > Ok, thanks Viraj.
>> >
>> > Hopefully you can place here like all other how it's maintained. Let me know any help required on this. May be we can name it as bdp-select. Or (bgp-select)
>> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
>> >
>> >
>> > On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org> wrote:
>> >
>> > Masatake, Brahma,
>> >
>> > Hopefully I should be able to create Jira and PR in Bigtop. Will let you
>> > know once ready for review. Thanks
>> >
>> >
>> > On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <iw...@oss.nttdata.com>
>> > wrote:
>> >
>> > > Please file a JIRA and submit a pull request if you want to show the code
>> > > and get feedback.
>> > > There is nothing I want to discuss off the record.
>> > >
>> > > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
>> > > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get
>> > > the final conclusion on this..?
>> > > >
>> > > > Please let me know your availability, Can have one call to discuss on
>> > > this..
>> > > >
>> > > >
>> > > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
>> > > wrote:
>> > > >
>> > > > > -1 on development in branch.
>> > > > > It is not worth for maintaining the branch if the modules is
>> > > so small
>> > > > > and barely updated as explained here.
>> > > > > It should not conflict to existing code.
>> > > > > I feel I must check the code before check-in based on this
>> > > thread.
>> > > >
>> > > >
>> > > > Sure, Viraj or me can show the code to you.
>> > > >
>> > > > Can we've call on this Friday/Thrusday if that works..?
>> > > >
>> > > >
>> > > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
>> > > iwasakims@oss.nttdata.com> wrote:
>> > > >
>> > > > > Sure, we can havemodule name like bigtop-distro-select.
>> > > > > Initially we'll do this separate branch.
>> > > >
>> > > > -1 on development in branch.
>> > > > It is not worth for maintaining the branch if the modules is so
>> > > small
>> > > > and barely updated as explained here.
>> > > > It should not conflict to existing code.
>> > > > I feel I must check the code before check-in based on this
>> > > thread.
>> > > >
>> > > > Masatake Iwasaki
>> > > >
>> > > > On 2022/07/11 8:23, Kengo Seki wrote:
>> > > > >> As there are different opinions on this and took long time,
>> > > just to brainstorm all the possibilities and pitfalls.
>> > > > >
>> > > > > Oh, I interpreted your words "conclude" and "finalize" as you
>> > > were
>> > > > > going to make a final decision. Brainstorming is welcome, of
>> > > course.
>> > > > > (But I'm not so sure if all people concerned could join, due
>> > > to time
>> > > > > difference and their schedule, etc.)
>> > > > >
>> > > > >> Can you suggest, how the changes will be also.. like folder,
>> > > where you suggest to keep this...?
>> > > > >
>> > > > > Sure, here's my proposal:
>> > > > >
>> > > > > * Stack name: "BIGTOP"
>> > > > >
>> > > > > - The same name as the existing one [1]
>> > > > > - Because it deploys the packages generated by Bigtop
>> > > > > - The existing stack should be replaced with it, because
>> > > that is
>> > > > > based on Bigtop 0.8 and too old to use now
>> > > > > - No concern about infringing others' trademark
>> > > > >
>> > > > > * Component/folder name: "bigtop-select"
>> > > > >
>> > > > > - Consistent naming convention with the existing tools
>> > > such as
>> > > > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
>> > > > > - If it sounds too simple and a bit unclear, a more
>> > > descriptive name
>> > > > > might be an option, for example "bigtop-ambari-stack-selector"
>> > > > >
>> > > > > * Script name: "bigtop-select"
>> > > > >
>> > > > > - Consistent with the stack name
>> > > > > - No concern about infringing others' trademark
>> > > > >
>> > > > > [1]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
>> > > > > [2]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
>> > > > >
>> > > > > Kengo Seki <se...@apache.org>
>> > > > >
>> > > > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
>> > > > > <bb...@visa.com.invalid> wrote:
>> > > > >>
>> > > > >>> Technical decisions shouldn't be done on other places
>> > > than public mailing lists,
>> > > > >>> as described in the "Open Communications" section of [1]
>> > > and [2].
>> > > > >> > So we should conclude the discussion in this mailing
>> > > list.
>> > > > >> > (And with my poor English, I'm not so confident to catch
>> > > up with your
>> > > > >> > fluent talk ;)
>> > > > >>
>> > > > >> I believe , I knew the apache way which you mentioned. We
>> > > are not going conclude anything which comes to bigtop other than this
>> > > mailing list.
>> > > > >> As there are different opinions on this and took long time,
>> > > just to brainstorm all the possibilities and pitfalls. Hence asking let's
>> > > have call so that we can brainstorm. Even after call, everything will be
>> > > published what we discussed.
>> > > > >>
>> > > > >> I think, whiteboarding will help to catch up with you.
>> > > > >>
>> > > > >> You all the think "bigtop-select" will be best option
>> > > right..? Can you suggest, how the changes will be also.. like folder, where
>> > > you suggest to keep this...?
>> > > > >>
>> > > > >> And if the name represents the stack which we are going to
>> > > deploy should fine I feel.. (if it's not BDP, may be
>> > > OBDP:OpensourceBigDataPlatform.)
>> > > > >>
>> > > > >> @Viraj Jasani and others any thoughts..?
>> > > > >>
>> > > > >>
>> > > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org>
>> > > wrote:
>> > > > >>
>> > > > >> > Looks we had so much discussed here, Let's try to
>> > > conclude. Can we've one call on this and finalize this..?
>> > > > >>
>> > > > >> Technical decisions shouldn't be done on other places
>> > > than public mailing lists,
>> > > > >> as described in the "Open Communications" section of
>> > > [1] and [2].
>> > > > >> So we should conclude the discussion in this mailing
>> > > list.
>> > > > >> (And with my poor English, I'm not so confident to
>> > > catch up with your
>> > > > >> fluent talk ;)
>> > > > >>
>> > > > >> > FYI. Even looks bigtop used some where also..
>> > > > >>
>> > > > >> Bigtop is ASF's trademark as you can see in the "Apache
>> > > Bigtop®
>> > > > >> software" section of [3].
>> > > > >> So it doesn't have the risk of trademark infringement.
>> > > > >>
>> > > > >> [1]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
>> > > > >> [2]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
>> > > > >> [3]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
>> > > > >>
>> > > > >> Kengo Seki <se...@apache.org>
>> > > > >>
>> > > > >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
>> > > > >> <bb...@visa.com.invalid> wrote:
>> > > > >> >
>> > > > >> > Looks we had so much discussed here, Let's try to
>> > > conclude. Can we've one call on this and finalize this..?
>> > > > >> >
>> > > > >> > FYI. Even looks bigtop used some where[1] also..
>> > > > >> > 1.
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
>> > > > >> >
>> > > > >> >
>> > > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
>> > > wrote:
>> > > > >> >
>> > > > >> > Thank you for your explanation, Brahma.
>> > > > >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP"
>> > > [1]) is supposed to be a
>> > > > >> > trademark of Redoop, so they can name the script
>> > > crh-select without
>> > > > >> > problem.
>> > > > >> > But regarding BDP for example, I can easily find
>> > > products that have
>> > > > >> > the same name [2][3][4] as you already mentioned,
>> > > so I'd like to
>> > > > >> > recommend bigtop-select for avoiding unnecessary
>> > > trouble.
>> > > > >> > Or, a single and more general word just like
>> > > conf-select may be less
>> > > > >> > troublesome than bdp. How about "stack-select",
>> > > for example?
>> > > > >> >
>> > > > >> > [1]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
>> > > > >> > [2]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
>> > > > >> > [3]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
>> > > > >> > [4]:
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
>> > > > >> >
>> > > > >> > Kengo Seki <se...@apache.org>
>> > > > >> >
>> > > > >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma
>> > > Reddy <bb...@visa.com> wrote:
>> > > > >> > >
>> > > > >> > > >Do you mean that you're going to name the
>> > > module (same as "component"
>> > > > >> > > >in the Bigtop terminology, I think)
>> > > bigtop-distro-select,
>> > > > >> > > >and still the script in question
>> > > bdp-select? If so, is there any
>> > > > >> > > >reason that the script must be that name?
>> > > > >> > > >(No offence, I just want to understand
>> > > your thoughts and its
>> > > > >> > > >background, and avoid the conflict or
>> > > user's confusion with existing
>> > > > >> > > >trademarks or products)
>> > > > >> > >
>> > > > >> > > Thanks @Kengo Seki for consolidating all the
>> > > concerns. Name should represent the stack which includes all the components
>> > > hence planning to have like bdp,bds...and this only one file like below[1]
>> > > which has done redoop.
>> > > > >> > >
>> > > > >> > >
>> > > > >> > >
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
>> > > > >> > >
>> > > > >> > >
>> > > > >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
>> > > sekikn@apache.org> wrote:
>> > > > >> > >
>> > > > >> > > The following concern Masatake mentioned
>> > > before is an important point,
>> > > > >> > > so I talked to Brahma for clarifying his
>> > > intention on the ASF Slack
>> > > > >> > > yesterday.
>> > > > >> > >
>> > > > >> > > > Multiple versions of the same package
>> > > (deb/rpm) can not be installed at the same time.
>> > > > >> > > > IIRC, HDP uses convention in which the
>> > > product version is part of package name
>> > > > >> > > > for addressing this.
>> > > > >> > >
>> > > > >> > > > I don't like to bring the awkward package
>> > > name convention to Bigtop
>> > > > >> > > > at least by default.
>> > > > >> > >
>> > > > >> > > He's planning to adopt the same mitigation
>> > > as HDP for now, but he
>> > > > >> > > doesn't intend to change the default
>> > > package naming convention of
>> > > > >> > > Bigtop,
>> > > > >> > > but just add a new functionality to include
>> > > an extra part into the
>> > > > >> > > package name for avoiding conflict, which
>> > > is disabled by default.
>> > > > >> > >
>> > > > >> > > And Brahma, let me confirm about the
>> > > following reply:
>> > > > >> > >
>> > > > >> > > > Sure, we can have module name like
>> > > bigtop-distro-select.
>> > > > >> > >
>> > > > >> > > Do you mean that you're going to name the
>> > > module (same as "component"
>> > > > >> > > in the Bigtop terminology, I think)
>> > > bigtop-distro-select,
>> > > > >> > > and still the script in question
>> > > bdp-select? If so, is there any
>> > > > >> > > reason that the script must be that name?
>> > > > >> > > (No offence, I just want to understand your
>> > > thoughts and its
>> > > > >> > > background, and avoid the conflict or
>> > > user's confusion with existing
>> > > > >> > > trademarks or products)
>> > > > >> > >
>> > > > >> > > Kengo Seki <se...@apache.org>
>> > > > >> > >
>> > > > >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula,
>> > > Brahma Reddy
>> > > > >> > > <bb...@visa.com.invalid> wrote:
>> > > > >> > > >
>> > > > >> > > > > The name of stack based no Bigtop
>> > > should be Bigtop.
>> > > > >> > > > > If you can not accept the name like
>> > > bigtop-*, the work should done outside of Bigtop.
>> > > > >> > > > > I will cast -1 if someone submit a
>> > > patch to add a module with the name spoiling branding.
>> > > > >> > > >
>> > > > >> > > > Sure, we can have module name like
>> > > bigtop-distro-select.
>> > > > >> > > > Initially we'll do this separate branch.
>> > > > >> > > >
>> > > > >> > > >
>> > > > >> > > >
>> > > > >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
>> > > iwasakims@oss.nttdata.co.jp> wrote:
>> > > > >> > > >
>> > > > >> > > > > I believe it's for project name.
>> > > isn't it.?
>> > > > >> > > >
>> > > > >> > > > projects and products.
>> > > > >> > > >
>> > > > >> > > > > IMO, We need to create folders and
>> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > > >> > > >
>> > > > >> > > > The name of stack based no Bigtop
>> > > should be Bigtop.
>> > > > >> > > > If you can not accept the name like
>> > > bigtop-*, the work should done outside of Bigtop.
>> > > > >> > > > I will cast -1 if someone submit a
>> > > patch to add a module with the name spoiling branding.
>> > > > >> > > >
>> > > > >> > > >
>> > > > >> > > > On 2022/07/06 11:44, Battula, Brahma
>> > > Reddy wrote:
>> > > > >> > > > >
>> > > > >> > > > > I believe it's for project name.
>> > > isn't it.?
>> > > > >> > > > >
>> > > > >> > > > >
>> > > > >> > > > > On 06/07/22, 7:27 AM, "Masatake
>> > > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > > >> > > > >
>> > > > >> > > > > > But As we are not releasing
>> > > as enterprise should be fine I think. IMO, We need to create folders and
>> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > > >> > > > >
>> > > > >> > > > > Not fine.
>> > > > >> > > > > We have a trademark policy.
>> > > > >> > > > >
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
>> > > > >> > > > >
>> > > > >> > > > > On 2022/07/06 10:37, Battula,
>> > > Brahma Reddy wrote:
>> > > > >> > > > > >> Should we avoid
>> > > unrecognized brand which may be trademark of someone?
>> > > > >> > > > > >> ambari-select or
>> > > bigtop-select should be enough.
>> > > > >> > > > > >
>> > > > >> > > > > > Not sure, where to confirm
>> > > whether there is already trademark. When I googled found so many.
>> > > > >> > > > > > But As we are not releasing
>> > > as enterprise should be fine I think. IMO, We need to create folders and
>> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > > >> > > > > > May be you can refer the
>> > > initial proposal [2] where I mentioned some more names.
>> > > (BDS-BigDataStack,OSS-OpenSourceSelect..)
>> > > > >> > > > > >
>> > > > >> > > > > > Finally thanks a bunch for
>> > > long healthy discussions on this. Mostly we all same page now.
>> > > > >> > > > > >
>> > > > >> > > > > > 1.
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
>> > > > >> > > > > >
>> > > > >> > > > > > 2.
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
>> > > > >> > > > > >
>> > > > >> > > > > >
>> > > > >> > > > > > On 06/07/22, 4:01 AM,
>> > > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > > >> > > > > >
>> > > > >> > > > > > > We have still not
>> > > officially finalized the new replacement name for
>> > > > >> > > > > > > hdp-select, it would
>> > > likely be bdp-select (bdp: BigData Platform). However,
>> > > > >> > > > > > > the purpose of
>> > > bdp-select and conf-select remains the same.
>> > > > >> > > > > >
>> > > > >> > > > > > Should we avoid
>> > > unrecognized brand which may be trademark of someone?
>> > > > >> > > > > > ambari-select or
>> > > bigtop-select should be enough.
>> > > > >> > > > > >
>> > > > >> > > > > > On 2022/06/29 13:52,
>> > > Viraj Jasani wrote:
>> > > > >> > > > > > > Hi Ambari/Bigtop dev,
>> > > > >> > > > > > >
>> > > > >> > > > > > > As per the new
>> > > roadmap of Apache Ambari, we would like to propose moving
>> > > > >> > > > > > > certain scripts
>> > > (previously known as hdp-select and conf-select) to Bigtop
>> > > > >> > > > > > > so that their rpm
>> > > installation could be managed independently.
>> > > > >> > > > > > > These scripts are a
>> > > basic necessity in the Ambari framework for the
>> > > > >> > > > > > > installation of
>> > > various Bigdata packages. The only major changes they would
>> > > > >> > > > > > > receive is when we
>> > > onboard new services and components to Ambari, else they
>> > > > >> > > > > > > usually do not
>> > > receive updates. In the past, we used to get hdp-select rpm
>> > > > >> > > > > > > downloaded and
>> > > installed from HDP repositories.
>> > > > >> > > > > > >
>> > > > >> > > > > > > We have still not
>> > > officially finalized the new replacement name for
>> > > > >> > > > > > > hdp-select, it would
>> > > likely be bdp-select (bdp: BigData Platform). However,
>> > > > >> > > > > > > the purpose of
>> > > bdp-select and conf-select remains the same.
>> > > > >> > > > > > >
>> > > > >> > > > > >
>> > > > >> > > > >
>> > > > >> > > >
>> > > > >> > > >
>> > > > >> > > >
>> > > ---------------------------------------------------------------------
>> > > > >> > > > To unsubscribe, e-mail:
>> > > dev-unsubscribe@ambari.apache.org
>> > > > >> > > > For additional commands, e-mail:
>> > > dev-help@ambari.apache.org
>> > > > >> > > >
>> > > > >> > >
>> > > > >> > >
>> > > ---------------------------------------------------------------------
>> > > > >> > > To unsubscribe, e-mail:
>> > > dev-unsubscribe@ambari.apache.org
>> > > > >> > > For additional commands, e-mail:
>> > > dev-help@ambari.apache.org
>> > > > >> > >
>> > > > >> > >
>> > > > >> >
>> > > > >> >
>> > > ---------------------------------------------------------------------
>> > > > >> > To unsubscribe, e-mail:
>> > > dev-unsubscribe@ambari.apache.org
>> > > > >> > For additional commands, e-mail:
>> > > dev-help@ambari.apache.org
>> > > > >> >
>> > > > >> >
>> > > > >>
>> > > > >>
>> > > ---------------------------------------------------------------------
>> > > > >> To unsubscribe, e-mail:
>> > > dev-unsubscribe@ambari.apache.org
>> > > > >> For additional commands, e-mail:
>> > > dev-help@ambari.apache.org
>> > > > >>
>> > > > >>
>> > > >
>> > > >
>> > > >
>> > > ---------------------------------------------------------------------
>> > > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > > > For additional commands, e-mail: dev-help@ambari.apache.org
>> > > >
>> > > >
>> > >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > For additional commands, e-mail: dev-help@ambari.apache.org
>> >
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> For additional commands, e-mail: dev-help@ambari.apache.org
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> For additional commands, e-mail: dev-help@ambari.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.com>.
>>> May be we can name it as bdp-select. Or (bgp-select)
>> -1 as we already discussed.
> Thanks for your feedback, I would definitely honour it. As you are not open for discussion and asked us raise the PR hence you thought of discussing on the PR. What will be your final suggestion on this..?
I'm -1 on the name like bdp-select or bgp-select as we discussed.
Feel free to open PR with appropriate module name.
On 2022/09/05 16:30, Battula, Brahma Reddy wrote:
> Hi @Masatake Iwasaki,
>
>> -1 as we already discussed.
> Thanks for your feedback, I would definitely honour it. As you are not open for discussion and asked us raise the PR hence you thought of discussing on the PR. What will be your final suggestion on this..?
>
> @Roman Shaposhnik
> I just gone through the following jira[1] where you brought ambari to bigtop. Looks stack-select is not included, how it was maintained.?
> I thinking we should have one stack which can support for upgrading the existing the HDP deployed clusters. Even I can see somebody asking on bigtop[2].
>
> If bigtop is not right place, shall we include in ambari..? Please let me know your thoughts on this. This blocks the 2.7.7 release.
>
> Note : There is on-going ambari mpack which might take some more time. Even upgrades will take some time.
>
>
> 1. https://issues.apache.org/jira/browse/BIGTOP-709
> 2. https://issues.apache.org/jira/browse/BIGTOP-3651
>
>
> Regards,
> Brahma Reddy Battula
>
>
> On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com> wrote:
>
> > May be we can name it as bdp-select. Or (bgp-select)
>
> -1 as we already discussed.
>
> On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
> > Ok, thanks Viraj.
> >
> > Hopefully you can place here like all other how it's maintained. Let me know any help required on this. May be we can name it as bdp-select. Or (bgp-select)
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> >
> >
> > On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org> wrote:
> >
> > Masatake, Brahma,
> >
> > Hopefully I should be able to create Jira and PR in Bigtop. Will let you
> > know once ready for review. Thanks
> >
> >
> > On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <iw...@oss.nttdata.com>
> > wrote:
> >
> > > Please file a JIRA and submit a pull request if you want to show the code
> > > and get feedback.
> > > There is nothing I want to discuss off the record.
> > >
> > > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> > > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get
> > > the final conclusion on this..?
> > > >
> > > > Please let me know your availability, Can have one call to discuss on
> > > this..
> > > >
> > > >
> > > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
> > > wrote:
> > > >
> > > > > -1 on development in branch.
> > > > > It is not worth for maintaining the branch if the modules is
> > > so small
> > > > > and barely updated as explained here.
> > > > > It should not conflict to existing code.
> > > > > I feel I must check the code before check-in based on this
> > > thread.
> > > >
> > > >
> > > > Sure, Viraj or me can show the code to you.
> > > >
> > > > Can we've call on this Friday/Thrusday if that works..?
> > > >
> > > >
> > > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> > > iwasakims@oss.nttdata.com> wrote:
> > > >
> > > > > Sure, we can havemodule name like bigtop-distro-select.
> > > > > Initially we'll do this separate branch.
> > > >
> > > > -1 on development in branch.
> > > > It is not worth for maintaining the branch if the modules is so
> > > small
> > > > and barely updated as explained here.
> > > > It should not conflict to existing code.
> > > > I feel I must check the code before check-in based on this
> > > thread.
> > > >
> > > > Masatake Iwasaki
> > > >
> > > > On 2022/07/11 8:23, Kengo Seki wrote:
> > > > >> As there are different opinions on this and took long time,
> > > just to brainstorm all the possibilities and pitfalls.
> > > > >
> > > > > Oh, I interpreted your words "conclude" and "finalize" as you
> > > were
> > > > > going to make a final decision. Brainstorming is welcome, of
> > > course.
> > > > > (But I'm not so sure if all people concerned could join, due
> > > to time
> > > > > difference and their schedule, etc.)
> > > > >
> > > > >> Can you suggest, how the changes will be also.. like folder,
> > > where you suggest to keep this...?
> > > > >
> > > > > Sure, here's my proposal:
> > > > >
> > > > > * Stack name: "BIGTOP"
> > > > >
> > > > > - The same name as the existing one [1]
> > > > > - Because it deploys the packages generated by Bigtop
> > > > > - The existing stack should be replaced with it, because
> > > that is
> > > > > based on Bigtop 0.8 and too old to use now
> > > > > - No concern about infringing others' trademark
> > > > >
> > > > > * Component/folder name: "bigtop-select"
> > > > >
> > > > > - Consistent naming convention with the existing tools
> > > such as
> > > > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > > > > - If it sounds too simple and a bit unclear, a more
> > > descriptive name
> > > > > might be an option, for example "bigtop-ambari-stack-selector"
> > > > >
> > > > > * Script name: "bigtop-select"
> > > > >
> > > > > - Consistent with the stack name
> > > > > - No concern about infringing others' trademark
> > > > >
> > > > > [1]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
> > > > > [2]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> > > > >
> > > > > Kengo Seki <se...@apache.org>
> > > > >
> > > > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> > > > > <bb...@visa.com.invalid> wrote:
> > > > >>
> > > > >>> Technical decisions shouldn't be done on other places
> > > than public mailing lists,
> > > > >>> as described in the "Open Communications" section of [1]
> > > and [2].
> > > > >> > So we should conclude the discussion in this mailing
> > > list.
> > > > >> > (And with my poor English, I'm not so confident to catch
> > > up with your
> > > > >> > fluent talk ;)
> > > > >>
> > > > >> I believe , I knew the apache way which you mentioned. We
> > > are not going conclude anything which comes to bigtop other than this
> > > mailing list.
> > > > >> As there are different opinions on this and took long time,
> > > just to brainstorm all the possibilities and pitfalls. Hence asking let's
> > > have call so that we can brainstorm. Even after call, everything will be
> > > published what we discussed.
> > > > >>
> > > > >> I think, whiteboarding will help to catch up with you.
> > > > >>
> > > > >> You all the think "bigtop-select" will be best option
> > > right..? Can you suggest, how the changes will be also.. like folder, where
> > > you suggest to keep this...?
> > > > >>
> > > > >> And if the name represents the stack which we are going to
> > > deploy should fine I feel.. (if it's not BDP, may be
> > > OBDP:OpensourceBigDataPlatform.)
> > > > >>
> > > > >> @Viraj Jasani and others any thoughts..?
> > > > >>
> > > > >>
> > > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org>
> > > wrote:
> > > > >>
> > > > >> > Looks we had so much discussed here, Let's try to
> > > conclude. Can we've one call on this and finalize this..?
> > > > >>
> > > > >> Technical decisions shouldn't be done on other places
> > > than public mailing lists,
> > > > >> as described in the "Open Communications" section of
> > > [1] and [2].
> > > > >> So we should conclude the discussion in this mailing
> > > list.
> > > > >> (And with my poor English, I'm not so confident to
> > > catch up with your
> > > > >> fluent talk ;)
> > > > >>
> > > > >> > FYI. Even looks bigtop used some where also..
> > > > >>
> > > > >> Bigtop is ASF's trademark as you can see in the "Apache
> > > Bigtop®
> > > > >> software" section of [3].
> > > > >> So it doesn't have the risk of trademark infringement.
> > > > >>
> > > > >> [1]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
> > > > >> [2]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
> > > > >> [3]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
> > > > >>
> > > > >> Kengo Seki <se...@apache.org>
> > > > >>
> > > > >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> > > > >> <bb...@visa.com.invalid> wrote:
> > > > >> >
> > > > >> > Looks we had so much discussed here, Let's try to
> > > conclude. Can we've one call on this and finalize this..?
> > > > >> >
> > > > >> > FYI. Even looks bigtop used some where[1] also..
> > > > >> > 1.
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
> > > > >> >
> > > > >> >
> > > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
> > > wrote:
> > > > >> >
> > > > >> > Thank you for your explanation, Brahma.
> > > > >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP"
> > > [1]) is supposed to be a
> > > > >> > trademark of Redoop, so they can name the script
> > > crh-select without
> > > > >> > problem.
> > > > >> > But regarding BDP for example, I can easily find
> > > products that have
> > > > >> > the same name [2][3][4] as you already mentioned,
> > > so I'd like to
> > > > >> > recommend bigtop-select for avoiding unnecessary
> > > trouble.
> > > > >> > Or, a single and more general word just like
> > > conf-select may be less
> > > > >> > troublesome than bdp. How about "stack-select",
> > > for example?
> > > > >> >
> > > > >> > [1]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
> > > > >> > [2]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
> > > > >> > [3]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
> > > > >> > [4]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
> > > > >> >
> > > > >> > Kengo Seki <se...@apache.org>
> > > > >> >
> > > > >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma
> > > Reddy <bb...@visa.com> wrote:
> > > > >> > >
> > > > >> > > >Do you mean that you're going to name the
> > > module (same as "component"
> > > > >> > > >in the Bigtop terminology, I think)
> > > bigtop-distro-select,
> > > > >> > > >and still the script in question
> > > bdp-select? If so, is there any
> > > > >> > > >reason that the script must be that name?
> > > > >> > > >(No offence, I just want to understand
> > > your thoughts and its
> > > > >> > > >background, and avoid the conflict or
> > > user's confusion with existing
> > > > >> > > >trademarks or products)
> > > > >> > >
> > > > >> > > Thanks @Kengo Seki for consolidating all the
> > > concerns. Name should represent the stack which includes all the components
> > > hence planning to have like bdp,bds...and this only one file like below[1]
> > > which has done redoop.
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
> > > > >> > >
> > > > >> > >
> > > > >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
> > > sekikn@apache.org> wrote:
> > > > >> > >
> > > > >> > > The following concern Masatake mentioned
> > > before is an important point,
> > > > >> > > so I talked to Brahma for clarifying his
> > > intention on the ASF Slack
> > > > >> > > yesterday.
> > > > >> > >
> > > > >> > > > Multiple versions of the same package
> > > (deb/rpm) can not be installed at the same time.
> > > > >> > > > IIRC, HDP uses convention in which the
> > > product version is part of package name
> > > > >> > > > for addressing this.
> > > > >> > >
> > > > >> > > > I don't like to bring the awkward package
> > > name convention to Bigtop
> > > > >> > > > at least by default.
> > > > >> > >
> > > > >> > > He's planning to adopt the same mitigation
> > > as HDP for now, but he
> > > > >> > > doesn't intend to change the default
> > > package naming convention of
> > > > >> > > Bigtop,
> > > > >> > > but just add a new functionality to include
> > > an extra part into the
> > > > >> > > package name for avoiding conflict, which
> > > is disabled by default.
> > > > >> > >
> > > > >> > > And Brahma, let me confirm about the
> > > following reply:
> > > > >> > >
> > > > >> > > > Sure, we can have module name like
> > > bigtop-distro-select.
> > > > >> > >
> > > > >> > > Do you mean that you're going to name the
> > > module (same as "component"
> > > > >> > > in the Bigtop terminology, I think)
> > > bigtop-distro-select,
> > > > >> > > and still the script in question
> > > bdp-select? If so, is there any
> > > > >> > > reason that the script must be that name?
> > > > >> > > (No offence, I just want to understand your
> > > thoughts and its
> > > > >> > > background, and avoid the conflict or
> > > user's confusion with existing
> > > > >> > > trademarks or products)
> > > > >> > >
> > > > >> > > Kengo Seki <se...@apache.org>
> > > > >> > >
> > > > >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula,
> > > Brahma Reddy
> > > > >> > > <bb...@visa.com.invalid> wrote:
> > > > >> > > >
> > > > >> > > > > The name of stack based no Bigtop
> > > should be Bigtop.
> > > > >> > > > > If you can not accept the name like
> > > bigtop-*, the work should done outside of Bigtop.
> > > > >> > > > > I will cast -1 if someone submit a
> > > patch to add a module with the name spoiling branding.
> > > > >> > > >
> > > > >> > > > Sure, we can have module name like
> > > bigtop-distro-select.
> > > > >> > > > Initially we'll do this separate branch.
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
> > > iwasakims@oss.nttdata.co.jp> wrote:
> > > > >> > > >
> > > > >> > > > > I believe it's for project name.
> > > isn't it.?
> > > > >> > > >
> > > > >> > > > projects and products.
> > > > >> > > >
> > > > >> > > > > IMO, We need to create folders and
> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > >> > > >
> > > > >> > > > The name of stack based no Bigtop
> > > should be Bigtop.
> > > > >> > > > If you can not accept the name like
> > > bigtop-*, the work should done outside of Bigtop.
> > > > >> > > > I will cast -1 if someone submit a
> > > patch to add a module with the name spoiling branding.
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > On 2022/07/06 11:44, Battula, Brahma
> > > Reddy wrote:
> > > > >> > > > >
> > > > >> > > > > I believe it's for project name.
> > > isn't it.?
> > > > >> > > > >
> > > > >> > > > >
> > > > >> > > > > On 06/07/22, 7:27 AM, "Masatake
> > > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > > >> > > > >
> > > > >> > > > > > But As we are not releasing
> > > as enterprise should be fine I think. IMO, We need to create folders and
> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > >> > > > >
> > > > >> > > > > Not fine.
> > > > >> > > > > We have a trademark policy.
> > > > >> > > > >
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
> > > > >> > > > >
> > > > >> > > > > On 2022/07/06 10:37, Battula,
> > > Brahma Reddy wrote:
> > > > >> > > > > >> Should we avoid
> > > unrecognized brand which may be trademark of someone?
> > > > >> > > > > >> ambari-select or
> > > bigtop-select should be enough.
> > > > >> > > > > >
> > > > >> > > > > > Not sure, where to confirm
> > > whether there is already trademark. When I googled found so many.
> > > > >> > > > > > But As we are not releasing
> > > as enterprise should be fine I think. IMO, We need to create folders and
> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > >> > > > > > May be you can refer the
> > > initial proposal [2] where I mentioned some more names.
> > > (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > > >> > > > > >
> > > > >> > > > > > Finally thanks a bunch for
> > > long healthy discussions on this. Mostly we all same page now.
> > > > >> > > > > >
> > > > >> > > > > > 1.
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
> > > > >> > > > > >
> > > > >> > > > > > 2.
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > > On 06/07/22, 4:01 AM,
> > > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > > >> > > > > >
> > > > >> > > > > > > We have still not
> > > officially finalized the new replacement name for
> > > > >> > > > > > > hdp-select, it would
> > > likely be bdp-select (bdp: BigData Platform). However,
> > > > >> > > > > > > the purpose of
> > > bdp-select and conf-select remains the same.
> > > > >> > > > > >
> > > > >> > > > > > Should we avoid
> > > unrecognized brand which may be trademark of someone?
> > > > >> > > > > > ambari-select or
> > > bigtop-select should be enough.
> > > > >> > > > > >
> > > > >> > > > > > On 2022/06/29 13:52,
> > > Viraj Jasani wrote:
> > > > >> > > > > > > Hi Ambari/Bigtop dev,
> > > > >> > > > > > >
> > > > >> > > > > > > As per the new
> > > roadmap of Apache Ambari, we would like to propose moving
> > > > >> > > > > > > certain scripts
> > > (previously known as hdp-select and conf-select) to Bigtop
> > > > >> > > > > > > so that their rpm
> > > installation could be managed independently.
> > > > >> > > > > > > These scripts are a
> > > basic necessity in the Ambari framework for the
> > > > >> > > > > > > installation of
> > > various Bigdata packages. The only major changes they would
> > > > >> > > > > > > receive is when we
> > > onboard new services and components to Ambari, else they
> > > > >> > > > > > > usually do not
> > > receive updates. In the past, we used to get hdp-select rpm
> > > > >> > > > > > > downloaded and
> > > installed from HDP repositories.
> > > > >> > > > > > >
> > > > >> > > > > > > We have still not
> > > officially finalized the new replacement name for
> > > > >> > > > > > > hdp-select, it would
> > > likely be bdp-select (bdp: BigData Platform). However,
> > > > >> > > > > > > the purpose of
> > > bdp-select and conf-select remains the same.
> > > > >> > > > > > >
> > > > >> > > > > >
> > > > >> > > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > ---------------------------------------------------------------------
> > > > >> > > > To unsubscribe, e-mail:
> > > dev-unsubscribe@ambari.apache.org
> > > > >> > > > For additional commands, e-mail:
> > > dev-help@ambari.apache.org
> > > > >> > > >
> > > > >> > >
> > > > >> > >
> > > ---------------------------------------------------------------------
> > > > >> > > To unsubscribe, e-mail:
> > > dev-unsubscribe@ambari.apache.org
> > > > >> > > For additional commands, e-mail:
> > > dev-help@ambari.apache.org
> > > > >> > >
> > > > >> > >
> > > > >> >
> > > > >> >
> > > ---------------------------------------------------------------------
> > > > >> > To unsubscribe, e-mail:
> > > dev-unsubscribe@ambari.apache.org
> > > > >> > For additional commands, e-mail:
> > > dev-help@ambari.apache.org
> > > > >> >
> > > > >> >
> > > > >>
> > > > >>
> > > ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail:
> > > dev-unsubscribe@ambari.apache.org
> > > > >> For additional commands, e-mail:
> > > dev-help@ambari.apache.org
> > > > >>
> > > > >>
> > > >
> > > >
> > > >
> > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > > > For additional commands, e-mail: dev-help@ambari.apache.org
> > > >
> > > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.com>.
>>> May be we can name it as bdp-select. Or (bgp-select)
>> -1 as we already discussed.
> Thanks for your feedback, I would definitely honour it. As you are not open for discussion and asked us raise the PR hence you thought of discussing on the PR. What will be your final suggestion on this..?
I'm -1 on the name like bdp-select or bgp-select as we discussed.
Feel free to open PR with appropriate module name.
On 2022/09/05 16:30, Battula, Brahma Reddy wrote:
> Hi @Masatake Iwasaki,
>
>> -1 as we already discussed.
> Thanks for your feedback, I would definitely honour it. As you are not open for discussion and asked us raise the PR hence you thought of discussing on the PR. What will be your final suggestion on this..?
>
> @Roman Shaposhnik
> I just gone through the following jira[1] where you brought ambari to bigtop. Looks stack-select is not included, how it was maintained.?
> I thinking we should have one stack which can support for upgrading the existing the HDP deployed clusters. Even I can see somebody asking on bigtop[2].
>
> If bigtop is not right place, shall we include in ambari..? Please let me know your thoughts on this. This blocks the 2.7.7 release.
>
> Note : There is on-going ambari mpack which might take some more time. Even upgrades will take some time.
>
>
> 1. https://issues.apache.org/jira/browse/BIGTOP-709
> 2. https://issues.apache.org/jira/browse/BIGTOP-3651
>
>
> Regards,
> Brahma Reddy Battula
>
>
> On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com> wrote:
>
> > May be we can name it as bdp-select. Or (bgp-select)
>
> -1 as we already discussed.
>
> On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
> > Ok, thanks Viraj.
> >
> > Hopefully you can place here like all other how it's maintained. Let me know any help required on this. May be we can name it as bdp-select. Or (bgp-select)
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> >
> >
> > On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org> wrote:
> >
> > Masatake, Brahma,
> >
> > Hopefully I should be able to create Jira and PR in Bigtop. Will let you
> > know once ready for review. Thanks
> >
> >
> > On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <iw...@oss.nttdata.com>
> > wrote:
> >
> > > Please file a JIRA and submit a pull request if you want to show the code
> > > and get feedback.
> > > There is nothing I want to discuss off the record.
> > >
> > > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> > > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get
> > > the final conclusion on this..?
> > > >
> > > > Please let me know your availability, Can have one call to discuss on
> > > this..
> > > >
> > > >
> > > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
> > > wrote:
> > > >
> > > > > -1 on development in branch.
> > > > > It is not worth for maintaining the branch if the modules is
> > > so small
> > > > > and barely updated as explained here.
> > > > > It should not conflict to existing code.
> > > > > I feel I must check the code before check-in based on this
> > > thread.
> > > >
> > > >
> > > > Sure, Viraj or me can show the code to you.
> > > >
> > > > Can we've call on this Friday/Thrusday if that works..?
> > > >
> > > >
> > > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> > > iwasakims@oss.nttdata.com> wrote:
> > > >
> > > > > Sure, we can havemodule name like bigtop-distro-select.
> > > > > Initially we'll do this separate branch.
> > > >
> > > > -1 on development in branch.
> > > > It is not worth for maintaining the branch if the modules is so
> > > small
> > > > and barely updated as explained here.
> > > > It should not conflict to existing code.
> > > > I feel I must check the code before check-in based on this
> > > thread.
> > > >
> > > > Masatake Iwasaki
> > > >
> > > > On 2022/07/11 8:23, Kengo Seki wrote:
> > > > >> As there are different opinions on this and took long time,
> > > just to brainstorm all the possibilities and pitfalls.
> > > > >
> > > > > Oh, I interpreted your words "conclude" and "finalize" as you
> > > were
> > > > > going to make a final decision. Brainstorming is welcome, of
> > > course.
> > > > > (But I'm not so sure if all people concerned could join, due
> > > to time
> > > > > difference and their schedule, etc.)
> > > > >
> > > > >> Can you suggest, how the changes will be also.. like folder,
> > > where you suggest to keep this...?
> > > > >
> > > > > Sure, here's my proposal:
> > > > >
> > > > > * Stack name: "BIGTOP"
> > > > >
> > > > > - The same name as the existing one [1]
> > > > > - Because it deploys the packages generated by Bigtop
> > > > > - The existing stack should be replaced with it, because
> > > that is
> > > > > based on Bigtop 0.8 and too old to use now
> > > > > - No concern about infringing others' trademark
> > > > >
> > > > > * Component/folder name: "bigtop-select"
> > > > >
> > > > > - Consistent naming convention with the existing tools
> > > such as
> > > > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > > > > - If it sounds too simple and a bit unclear, a more
> > > descriptive name
> > > > > might be an option, for example "bigtop-ambari-stack-selector"
> > > > >
> > > > > * Script name: "bigtop-select"
> > > > >
> > > > > - Consistent with the stack name
> > > > > - No concern about infringing others' trademark
> > > > >
> > > > > [1]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
> > > > > [2]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> > > > >
> > > > > Kengo Seki <se...@apache.org>
> > > > >
> > > > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> > > > > <bb...@visa.com.invalid> wrote:
> > > > >>
> > > > >>> Technical decisions shouldn't be done on other places
> > > than public mailing lists,
> > > > >>> as described in the "Open Communications" section of [1]
> > > and [2].
> > > > >> > So we should conclude the discussion in this mailing
> > > list.
> > > > >> > (And with my poor English, I'm not so confident to catch
> > > up with your
> > > > >> > fluent talk ;)
> > > > >>
> > > > >> I believe , I knew the apache way which you mentioned. We
> > > are not going conclude anything which comes to bigtop other than this
> > > mailing list.
> > > > >> As there are different opinions on this and took long time,
> > > just to brainstorm all the possibilities and pitfalls. Hence asking let's
> > > have call so that we can brainstorm. Even after call, everything will be
> > > published what we discussed.
> > > > >>
> > > > >> I think, whiteboarding will help to catch up with you.
> > > > >>
> > > > >> You all the think "bigtop-select" will be best option
> > > right..? Can you suggest, how the changes will be also.. like folder, where
> > > you suggest to keep this...?
> > > > >>
> > > > >> And if the name represents the stack which we are going to
> > > deploy should fine I feel.. (if it's not BDP, may be
> > > OBDP:OpensourceBigDataPlatform.)
> > > > >>
> > > > >> @Viraj Jasani and others any thoughts..?
> > > > >>
> > > > >>
> > > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org>
> > > wrote:
> > > > >>
> > > > >> > Looks we had so much discussed here, Let's try to
> > > conclude. Can we've one call on this and finalize this..?
> > > > >>
> > > > >> Technical decisions shouldn't be done on other places
> > > than public mailing lists,
> > > > >> as described in the "Open Communications" section of
> > > [1] and [2].
> > > > >> So we should conclude the discussion in this mailing
> > > list.
> > > > >> (And with my poor English, I'm not so confident to
> > > catch up with your
> > > > >> fluent talk ;)
> > > > >>
> > > > >> > FYI. Even looks bigtop used some where also..
> > > > >>
> > > > >> Bigtop is ASF's trademark as you can see in the "Apache
> > > Bigtop®
> > > > >> software" section of [3].
> > > > >> So it doesn't have the risk of trademark infringement.
> > > > >>
> > > > >> [1]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
> > > > >> [2]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
> > > > >> [3]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
> > > > >>
> > > > >> Kengo Seki <se...@apache.org>
> > > > >>
> > > > >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> > > > >> <bb...@visa.com.invalid> wrote:
> > > > >> >
> > > > >> > Looks we had so much discussed here, Let's try to
> > > conclude. Can we've one call on this and finalize this..?
> > > > >> >
> > > > >> > FYI. Even looks bigtop used some where[1] also..
> > > > >> > 1.
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
> > > > >> >
> > > > >> >
> > > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
> > > wrote:
> > > > >> >
> > > > >> > Thank you for your explanation, Brahma.
> > > > >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP"
> > > [1]) is supposed to be a
> > > > >> > trademark of Redoop, so they can name the script
> > > crh-select without
> > > > >> > problem.
> > > > >> > But regarding BDP for example, I can easily find
> > > products that have
> > > > >> > the same name [2][3][4] as you already mentioned,
> > > so I'd like to
> > > > >> > recommend bigtop-select for avoiding unnecessary
> > > trouble.
> > > > >> > Or, a single and more general word just like
> > > conf-select may be less
> > > > >> > troublesome than bdp. How about "stack-select",
> > > for example?
> > > > >> >
> > > > >> > [1]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
> > > > >> > [2]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
> > > > >> > [3]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
> > > > >> > [4]:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
> > > > >> >
> > > > >> > Kengo Seki <se...@apache.org>
> > > > >> >
> > > > >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma
> > > Reddy <bb...@visa.com> wrote:
> > > > >> > >
> > > > >> > > >Do you mean that you're going to name the
> > > module (same as "component"
> > > > >> > > >in the Bigtop terminology, I think)
> > > bigtop-distro-select,
> > > > >> > > >and still the script in question
> > > bdp-select? If so, is there any
> > > > >> > > >reason that the script must be that name?
> > > > >> > > >(No offence, I just want to understand
> > > your thoughts and its
> > > > >> > > >background, and avoid the conflict or
> > > user's confusion with existing
> > > > >> > > >trademarks or products)
> > > > >> > >
> > > > >> > > Thanks @Kengo Seki for consolidating all the
> > > concerns. Name should represent the stack which includes all the components
> > > hence planning to have like bdp,bds...and this only one file like below[1]
> > > which has done redoop.
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
> > > > >> > >
> > > > >> > >
> > > > >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
> > > sekikn@apache.org> wrote:
> > > > >> > >
> > > > >> > > The following concern Masatake mentioned
> > > before is an important point,
> > > > >> > > so I talked to Brahma for clarifying his
> > > intention on the ASF Slack
> > > > >> > > yesterday.
> > > > >> > >
> > > > >> > > > Multiple versions of the same package
> > > (deb/rpm) can not be installed at the same time.
> > > > >> > > > IIRC, HDP uses convention in which the
> > > product version is part of package name
> > > > >> > > > for addressing this.
> > > > >> > >
> > > > >> > > > I don't like to bring the awkward package
> > > name convention to Bigtop
> > > > >> > > > at least by default.
> > > > >> > >
> > > > >> > > He's planning to adopt the same mitigation
> > > as HDP for now, but he
> > > > >> > > doesn't intend to change the default
> > > package naming convention of
> > > > >> > > Bigtop,
> > > > >> > > but just add a new functionality to include
> > > an extra part into the
> > > > >> > > package name for avoiding conflict, which
> > > is disabled by default.
> > > > >> > >
> > > > >> > > And Brahma, let me confirm about the
> > > following reply:
> > > > >> > >
> > > > >> > > > Sure, we can have module name like
> > > bigtop-distro-select.
> > > > >> > >
> > > > >> > > Do you mean that you're going to name the
> > > module (same as "component"
> > > > >> > > in the Bigtop terminology, I think)
> > > bigtop-distro-select,
> > > > >> > > and still the script in question
> > > bdp-select? If so, is there any
> > > > >> > > reason that the script must be that name?
> > > > >> > > (No offence, I just want to understand your
> > > thoughts and its
> > > > >> > > background, and avoid the conflict or
> > > user's confusion with existing
> > > > >> > > trademarks or products)
> > > > >> > >
> > > > >> > > Kengo Seki <se...@apache.org>
> > > > >> > >
> > > > >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula,
> > > Brahma Reddy
> > > > >> > > <bb...@visa.com.invalid> wrote:
> > > > >> > > >
> > > > >> > > > > The name of stack based no Bigtop
> > > should be Bigtop.
> > > > >> > > > > If you can not accept the name like
> > > bigtop-*, the work should done outside of Bigtop.
> > > > >> > > > > I will cast -1 if someone submit a
> > > patch to add a module with the name spoiling branding.
> > > > >> > > >
> > > > >> > > > Sure, we can have module name like
> > > bigtop-distro-select.
> > > > >> > > > Initially we'll do this separate branch.
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
> > > iwasakims@oss.nttdata.co.jp> wrote:
> > > > >> > > >
> > > > >> > > > > I believe it's for project name.
> > > isn't it.?
> > > > >> > > >
> > > > >> > > > projects and products.
> > > > >> > > >
> > > > >> > > > > IMO, We need to create folders and
> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > >> > > >
> > > > >> > > > The name of stack based no Bigtop
> > > should be Bigtop.
> > > > >> > > > If you can not accept the name like
> > > bigtop-*, the work should done outside of Bigtop.
> > > > >> > > > I will cast -1 if someone submit a
> > > patch to add a module with the name spoiling branding.
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > On 2022/07/06 11:44, Battula, Brahma
> > > Reddy wrote:
> > > > >> > > > >
> > > > >> > > > > I believe it's for project name.
> > > isn't it.?
> > > > >> > > > >
> > > > >> > > > >
> > > > >> > > > > On 06/07/22, 7:27 AM, "Masatake
> > > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > > >> > > > >
> > > > >> > > > > > But As we are not releasing
> > > as enterprise should be fine I think. IMO, We need to create folders and
> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > >> > > > >
> > > > >> > > > > Not fine.
> > > > >> > > > > We have a trademark policy.
> > > > >> > > > >
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
> > > > >> > > > >
> > > > >> > > > > On 2022/07/06 10:37, Battula,
> > > Brahma Reddy wrote:
> > > > >> > > > > >> Should we avoid
> > > unrecognized brand which may be trademark of someone?
> > > > >> > > > > >> ambari-select or
> > > bigtop-select should be enough.
> > > > >> > > > > >
> > > > >> > > > > > Not sure, where to confirm
> > > whether there is already trademark. When I googled found so many.
> > > > >> > > > > > But As we are not releasing
> > > as enterprise should be fine I think. IMO, We need to create folders and
> > > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > >> > > > > > May be you can refer the
> > > initial proposal [2] where I mentioned some more names.
> > > (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > > >> > > > > >
> > > > >> > > > > > Finally thanks a bunch for
> > > long healthy discussions on this. Mostly we all same page now.
> > > > >> > > > > >
> > > > >> > > > > > 1.
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
> > > > >> > > > > >
> > > > >> > > > > > 2.
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > > On 06/07/22, 4:01 AM,
> > > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > > >> > > > > >
> > > > >> > > > > > > We have still not
> > > officially finalized the new replacement name for
> > > > >> > > > > > > hdp-select, it would
> > > likely be bdp-select (bdp: BigData Platform). However,
> > > > >> > > > > > > the purpose of
> > > bdp-select and conf-select remains the same.
> > > > >> > > > > >
> > > > >> > > > > > Should we avoid
> > > unrecognized brand which may be trademark of someone?
> > > > >> > > > > > ambari-select or
> > > bigtop-select should be enough.
> > > > >> > > > > >
> > > > >> > > > > > On 2022/06/29 13:52,
> > > Viraj Jasani wrote:
> > > > >> > > > > > > Hi Ambari/Bigtop dev,
> > > > >> > > > > > >
> > > > >> > > > > > > As per the new
> > > roadmap of Apache Ambari, we would like to propose moving
> > > > >> > > > > > > certain scripts
> > > (previously known as hdp-select and conf-select) to Bigtop
> > > > >> > > > > > > so that their rpm
> > > installation could be managed independently.
> > > > >> > > > > > > These scripts are a
> > > basic necessity in the Ambari framework for the
> > > > >> > > > > > > installation of
> > > various Bigdata packages. The only major changes they would
> > > > >> > > > > > > receive is when we
> > > onboard new services and components to Ambari, else they
> > > > >> > > > > > > usually do not
> > > receive updates. In the past, we used to get hdp-select rpm
> > > > >> > > > > > > downloaded and
> > > installed from HDP repositories.
> > > > >> > > > > > >
> > > > >> > > > > > > We have still not
> > > officially finalized the new replacement name for
> > > > >> > > > > > > hdp-select, it would
> > > likely be bdp-select (bdp: BigData Platform). However,
> > > > >> > > > > > > the purpose of
> > > bdp-select and conf-select remains the same.
> > > > >> > > > > > >
> > > > >> > > > > >
> > > > >> > > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > ---------------------------------------------------------------------
> > > > >> > > > To unsubscribe, e-mail:
> > > dev-unsubscribe@ambari.apache.org
> > > > >> > > > For additional commands, e-mail:
> > > dev-help@ambari.apache.org
> > > > >> > > >
> > > > >> > >
> > > > >> > >
> > > ---------------------------------------------------------------------
> > > > >> > > To unsubscribe, e-mail:
> > > dev-unsubscribe@ambari.apache.org
> > > > >> > > For additional commands, e-mail:
> > > dev-help@ambari.apache.org
> > > > >> > >
> > > > >> > >
> > > > >> >
> > > > >> >
> > > ---------------------------------------------------------------------
> > > > >> > To unsubscribe, e-mail:
> > > dev-unsubscribe@ambari.apache.org
> > > > >> > For additional commands, e-mail:
> > > dev-help@ambari.apache.org
> > > > >> >
> > > > >> >
> > > > >>
> > > > >>
> > > ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail:
> > > dev-unsubscribe@ambari.apache.org
> > > > >> For additional commands, e-mail:
> > > dev-help@ambari.apache.org
> > > > >>
> > > > >>
> > > >
> > > >
> > > >
> > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > > > For additional commands, e-mail: dev-help@ambari.apache.org
> > > >
> > > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Viraj Jasani <vj...@apache.org>.
Bumping this thread.
> I thinking we should have one stack which can support for upgrading the
existing the HDP deployed clusters. Even I can see somebody asking on
bigtop[2].
+1, we should have HDP (similar) stack to support minor version upgrades.
On Mon, Sep 5, 2022 at 12:30 AM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
> Hi @Masatake Iwasaki,
>
> > -1 as we already discussed.
> Thanks for your feedback, I would definitely honour it. As you are not
> open for discussion and asked us raise the PR hence you thought of
> discussing on the PR. What will be your final suggestion on this..?
>
> @Roman Shaposhnik
> I just gone through the following jira[1] where you brought ambari to
> bigtop. Looks stack-select is not included, how it was maintained.?
> I thinking we should have one stack which can support for upgrading the
> existing the HDP deployed clusters. Even I can see somebody asking on
> bigtop[2].
>
> If bigtop is not right place, shall we include in ambari..? Please let me
> know your thoughts on this. This blocks the 2.7.7 release.
>
> Note : There is on-going ambari mpack which might take some more time.
> Even upgrades will take some time.
>
>
> 1. https://issues.apache.org/jira/browse/BIGTOP-709
> 2. https://issues.apache.org/jira/browse/BIGTOP-3651
>
>
> Regards,
> Brahma Reddy Battula
>
>
> On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com>
> wrote:
>
> > May be we can name it as bdp-select. Or (bgp-select)
>
> -1 as we already discussed.
>
> On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
> > Ok, thanks Viraj.
> >
> > Hopefully you can place here like all other how it's maintained. Let
> me know any help required on this. May be we can name it as bdp-select. Or
> (bgp-select)
> >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> >
> >
> > On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org> wrote:
> >
> > Masatake, Brahma,
> >
> > Hopefully I should be able to create Jira and PR in Bigtop.
> Will let you
> > know once ready for review. Thanks
> >
> >
> > On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <
> iwasakims@oss.nttdata.com>
> > wrote:
> >
> > > Please file a JIRA and submit a pull request if you want to
> show the code
> > > and get feedback.
> > > There is nothing I want to discuss off the record.
> > >
> > > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> > > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others,
> can we get
> > > the final conclusion on this..?
> > > >
> > > > Please let me know your availability, Can have one call to
> discuss on
> > > this..
> > > >
> > > >
> > > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy"
> <bb...@visa.com.INVALID>
> > > wrote:
> > > >
> > > > > -1 on development in branch.
> > > > > It is not worth for maintaining the branch if the
> modules is
> > > so small
> > > > > and barely updated as explained here.
> > > > > It should not conflict to existing code.
> > > > > I feel I must check the code before check-in
> based on this
> > > thread.
> > > >
> > > >
> > > > Sure, Viraj or me can show the code to you.
> > > >
> > > > Can we've call on this Friday/Thrusday if that works..?
> > > >
> > > >
> > > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> > > iwasakims@oss.nttdata.com> wrote:
> > > >
> > > > > Sure, we can havemodule name like
> bigtop-distro-select.
> > > > > Initially we'll do this separate branch.
> > > >
> > > > -1 on development in branch.
> > > > It is not worth for maintaining the branch if the
> modules is so
> > > small
> > > > and barely updated as explained here.
> > > > It should not conflict to existing code.
> > > > I feel I must check the code before check-in based
> on this
> > > thread.
> > > >
> > > > Masatake Iwasaki
> > > >
> > > > On 2022/07/11 8:23, Kengo Seki wrote:
> > > > >> As there are different opinions on this and
> took long time,
> > > just to brainstorm all the possibilities and pitfalls.
> > > > >
> > > > > Oh, I interpreted your words "conclude" and
> "finalize" as you
> > > were
> > > > > going to make a final decision. Brainstorming is
> welcome, of
> > > course.
> > > > > (But I'm not so sure if all people concerned
> could join, due
> > > to time
> > > > > difference and their schedule, etc.)
> > > > >
> > > > >> Can you suggest, how the changes will be also..
> like folder,
> > > where you suggest to keep this...?
> > > > >
> > > > > Sure, here's my proposal:
> > > > >
> > > > > * Stack name: "BIGTOP"
> > > > >
> > > > > - The same name as the existing one [1]
> > > > > - Because it deploys the packages generated
> by Bigtop
> > > > > - The existing stack should be replaced with
> it, because
> > > that is
> > > > > based on Bigtop 0.8 and too old to use now
> > > > > - No concern about infringing others'
> trademark
> > > > >
> > > > > * Component/folder name: "bigtop-select"
> > > > >
> > > > > - Consistent naming convention with the
> existing tools
> > > such as
> > > > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils"
> [2]
> > > > > - If it sounds too simple and a bit unclear,
> a more
> > > descriptive name
> > > > > might be an option, for example
> "bigtop-ambari-stack-selector"
> > > > >
> > > > > * Script name: "bigtop-select"
> > > > >
> > > > > - Consistent with the stack name
> > > > > - No concern about infringing others'
> trademark
> > > > >
> > > > > [1]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
> > > > > [2]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> > > > >
> > > > > Kengo Seki <se...@apache.org>
> > > > >
> > > > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma
> Reddy
> > > > > <bb...@visa.com.invalid> wrote:
> > > > >>
> > > > >>> Technical decisions shouldn't be done on
> other places
> > > than public mailing lists,
> > > > >>> as described in the "Open Communications"
> section of [1]
> > > and [2].
> > > > >> > So we should conclude the discussion in
> this mailing
> > > list.
> > > > >> > (And with my poor English, I'm not so
> confident to catch
> > > up with your
> > > > >> > fluent talk ;)
> > > > >>
> > > > >> I believe , I knew the apache way which you
> mentioned. We
> > > are not going conclude anything which comes to bigtop other
> than this
> > > mailing list.
> > > > >> As there are different opinions on this and
> took long time,
> > > just to brainstorm all the possibilities and pitfalls. Hence
> asking let's
> > > have call so that we can brainstorm. Even after call,
> everything will be
> > > published what we discussed.
> > > > >>
> > > > >> I think, whiteboarding will help to catch up
> with you.
> > > > >>
> > > > >> You all the think "bigtop-select" will be best
> option
> > > right..? Can you suggest, how the changes will be also.. like
> folder, where
> > > you suggest to keep this...?
> > > > >>
> > > > >> And if the name represents the stack which we
> are going to
> > > deploy should fine I feel.. (if it's not BDP, may be
> > > OBDP:OpensourceBigDataPlatform.)
> > > > >>
> > > > >> @Viraj Jasani and others any thoughts..?
> > > > >>
> > > > >>
> > > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <
> sekikn@apache.org>
> > > wrote:
> > > > >>
> > > > >> > Looks we had so much discussed here,
> Let's try to
> > > conclude. Can we've one call on this and finalize this..?
> > > > >>
> > > > >> Technical decisions shouldn't be done on
> other places
> > > than public mailing lists,
> > > > >> as described in the "Open Communications"
> section of
> > > [1] and [2].
> > > > >> So we should conclude the discussion in
> this mailing
> > > list.
> > > > >> (And with my poor English, I'm not so
> confident to
> > > catch up with your
> > > > >> fluent talk ;)
> > > > >>
> > > > >> > FYI. Even looks bigtop used some where
> also..
> > > > >>
> > > > >> Bigtop is ASF's trademark as you can see
> in the "Apache
> > > Bigtop®
> > > > >> software" section of [3].
> > > > >> So it doesn't have the risk of trademark
> infringement.
> > > > >>
> > > > >> [1]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
> > > > >> [2]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
> > > > >> [3]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
> > > > >>
> > > > >> Kengo Seki <se...@apache.org>
> > > > >>
> > > > >> On Sun, Jul 10, 2022 at 4:11 AM Battula,
> Brahma Reddy
> > > > >> <bb...@visa.com.invalid> wrote:
> > > > >> >
> > > > >> > Looks we had so much discussed here,
> Let's try to
> > > conclude. Can we've one call on this and finalize this..?
> > > > >> >
> > > > >> > FYI. Even looks bigtop used some
> where[1] also..
> > > > >> > 1.
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
> > > > >> >
> > > > >> >
> > > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <
> sekikn@apache.org>
> > > wrote:
> > > > >> >
> > > > >> > Thank you for your explanation,
> Brahma.
> > > > >> > CRH (abbreviation of "CHINA REDOOP
> HYPERLOOP"
> > > [1]) is supposed to be a
> > > > >> > trademark of Redoop, so they can
> name the script
> > > crh-select without
> > > > >> > problem.
> > > > >> > But regarding BDP for example, I can
> easily find
> > > products that have
> > > > >> > the same name [2][3][4] as you
> already mentioned,
> > > so I'd like to
> > > > >> > recommend bigtop-select for avoiding
> unnecessary
> > > trouble.
> > > > >> > Or, a single and more general word
> just like
> > > conf-select may be less
> > > > >> > troublesome than bdp. How about
> "stack-select",
> > > for example?
> > > > >> >
> > > > >> > [1]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
> > > > >> > [2]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
> > > > >> > [3]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
> > > > >> > [4]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
> > > > >> >
> > > > >> > Kengo Seki <se...@apache.org>
> > > > >> >
> > > > >> > On Fri, Jul 8, 2022 at 2:51 AM
> Battula, Brahma
> > > Reddy <bb...@visa.com> wrote:
> > > > >> > >
> > > > >> > > >Do you mean that you're going
> to name the
> > > module (same as "component"
> > > > >> > > >in the Bigtop terminology, I
> think)
> > > bigtop-distro-select,
> > > > >> > > >and still the script in
> question
> > > bdp-select? If so, is there any
> > > > >> > > >reason that the script must
> be that name?
> > > > >> > > >(No offence, I just want to
> understand
> > > your thoughts and its
> > > > >> > > >background, and avoid the
> conflict or
> > > user's confusion with existing
> > > > >> > > >trademarks or products)
> > > > >> > >
> > > > >> > > Thanks @Kengo Seki for
> consolidating all the
> > > concerns. Name should represent the stack which includes all
> the components
> > > hence planning to have like bdp,bds...and this only one file
> like below[1]
> > > which has done redoop.
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
> > > > >> > >
> > > > >> > >
> > > > >> > > On 07/07/22, 6:07 AM, "Kengo Seki"
> <
> > > sekikn@apache.org> wrote:
> > > > >> > >
> > > > >> > > The following concern Masatake
> mentioned
> > > before is an important point,
> > > > >> > > so I talked to Brahma for
> clarifying his
> > > intention on the ASF Slack
> > > > >> > > yesterday.
> > > > >> > >
> > > > >> > > > Multiple versions of the
> same package
> > > (deb/rpm) can not be installed at the same time.
> > > > >> > > > IIRC, HDP uses convention in
> which the
> > > product version is part of package name
> > > > >> > > > for addressing this.
> > > > >> > >
> > > > >> > > > I don't like to bring the
> awkward package
> > > name convention to Bigtop
> > > > >> > > > at least by default.
> > > > >> > >
> > > > >> > > He's planning to adopt the
> same mitigation
> > > as HDP for now, but he
> > > > >> > > doesn't intend to change the
> default
> > > package naming convention of
> > > > >> > > Bigtop,
> > > > >> > > but just add a new
> functionality to include
> > > an extra part into the
> > > > >> > > package name for avoiding
> conflict, which
> > > is disabled by default.
> > > > >> > >
> > > > >> > > And Brahma, let me confirm
> about the
> > > following reply:
> > > > >> > >
> > > > >> > > > Sure, we can have module
> name like
> > > bigtop-distro-select.
> > > > >> > >
> > > > >> > > Do you mean that you're going
> to name the
> > > module (same as "component"
> > > > >> > > in the Bigtop terminology, I
> think)
> > > bigtop-distro-select,
> > > > >> > > and still the script in
> question
> > > bdp-select? If so, is there any
> > > > >> > > reason that the script must be
> that name?
> > > > >> > > (No offence, I just want to
> understand your
> > > thoughts and its
> > > > >> > > background, and avoid the
> conflict or
> > > user's confusion with existing
> > > > >> > > trademarks or products)
> > > > >> > >
> > > > >> > > Kengo Seki <se...@apache.org>
> > > > >> > >
> > > > >> > > On Thu, Jul 7, 2022 at 2:08 AM
> Battula,
> > > Brahma Reddy
> > > > >> > > <bb...@visa.com.invalid>
> wrote:
> > > > >> > > >
> > > > >> > > > > The name of stack based
> no Bigtop
> > > should be Bigtop.
> > > > >> > > > > If you can not accept
> the name like
> > > bigtop-*, the work should done outside of Bigtop.
> > > > >> > > > > I will cast -1 if
> someone submit a
> > > patch to add a module with the name spoiling branding.
> > > > >> > > >
> > > > >> > > > Sure, we can have module
> name like
> > > bigtop-distro-select.
> > > > >> > > > Initially we'll do this
> separate branch.
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > On 06/07/22, 8:55 AM,
> "Masatake Iwasaki" <
> > > iwasakims@oss.nttdata.co.jp> wrote:
> > > > >> > > >
> > > > >> > > > > I believe it's for
> project name.
> > > isn't it.?
> > > > >> > > >
> > > > >> > > > projects and products.
> > > > >> > > >
> > > > >> > > > > IMO, We need to create
> folders and
> > > refer stacknames so ambari-select,bigtop-select wn't looks
> good.
> > > > >> > > >
> > > > >> > > > The name of stack based
> no Bigtop
> > > should be Bigtop.
> > > > >> > > > If you can not accept
> the name like
> > > bigtop-*, the work should done outside of Bigtop.
> > > > >> > > > I will cast -1 if
> someone submit a
> > > patch to add a module with the name spoiling branding.
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > On 2022/07/06 11:44,
> Battula, Brahma
> > > Reddy wrote:
> > > > >> > > > >
> > > > >> > > > > I believe it's for
> project name.
> > > isn't it.?
> > > > >> > > > >
> > > > >> > > > >
> > > > >> > > > > On 06/07/22, 7:27 AM,
> "Masatake
> > > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > > >> > > > >
> > > > >> > > > > > But As we are
> not releasing
> > > as enterprise should be fine I think. IMO, We need to create
> folders and
> > > refer stacknames so ambari-select,bigtop-select wn't looks
> good.
> > > > >> > > > >
> > > > >> > > > > Not fine.
> > > > >> > > > > We have a
> trademark policy.
> > > > >> > > > >
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
> > > > >> > > > >
> > > > >> > > > > On 2022/07/06
> 10:37, Battula,
> > > Brahma Reddy wrote:
> > > > >> > > > > >> Should we avoid
> > > unrecognized brand which may be trademark of someone?
> > > > >> > > > > >> ambari-select
> or
> > > bigtop-select should be enough.
> > > > >> > > > > >
> > > > >> > > > > > Not sure, where
> to confirm
> > > whether there is already trademark. When I googled found so
> many.
> > > > >> > > > > > But As we are
> not releasing
> > > as enterprise should be fine I think. IMO, We need to create
> folders and
> > > refer stacknames so ambari-select,bigtop-select wn't looks
> good.
> > > > >> > > > > > May be you can
> refer the
> > > initial proposal [2] where I mentioned some more names.
> > > (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > > >> > > > > >
> > > > >> > > > > > Finally thanks
> a bunch for
> > > long healthy discussions on this. Mostly we all same page now.
> > > > >> > > > > >
> > > > >> > > > > > 1.
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
> > > > >> > > > > >
> > > > >> > > > > > 2.
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > > On 06/07/22,
> 4:01 AM,
> > > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > > >> > > > > >
> > > > >> > > > > > > We have
> still not
> > > officially finalized the new replacement name for
> > > > >> > > > > > >
> hdp-select, it would
> > > likely be bdp-select (bdp: BigData Platform). However,
> > > > >> > > > > > > the
> purpose of
> > > bdp-select and conf-select remains the same.
> > > > >> > > > > >
> > > > >> > > > > > Should we
> avoid
> > > unrecognized brand which may be trademark of someone?
> > > > >> > > > > >
> ambari-select or
> > > bigtop-select should be enough.
> > > > >> > > > > >
> > > > >> > > > > > On
> 2022/06/29 13:52,
> > > Viraj Jasani wrote:
> > > > >> > > > > > > Hi
> Ambari/Bigtop dev,
> > > > >> > > > > > >
> > > > >> > > > > > > As per
> the new
> > > roadmap of Apache Ambari, we would like to propose moving
> > > > >> > > > > > > certain
> scripts
> > > (previously known as hdp-select and conf-select) to Bigtop
> > > > >> > > > > > > so that
> their rpm
> > > installation could be managed independently.
> > > > >> > > > > > > These
> scripts are a
> > > basic necessity in the Ambari framework for the
> > > > >> > > > > > >
> installation of
> > > various Bigdata packages. The only major changes they would
> > > > >> > > > > > > receive
> is when we
> > > onboard new services and components to Ambari, else they
> > > > >> > > > > > > usually
> do not
> > > receive updates. In the past, we used to get hdp-select rpm
> > > > >> > > > > > >
> downloaded and
> > > installed from HDP repositories.
> > > > >> > > > > > >
> > > > >> > > > > > > We have
> still not
> > > officially finalized the new replacement name for
> > > > >> > > > > > >
> hdp-select, it would
> > > likely be bdp-select (bdp: BigData Platform). However,
> > > > >> > > > > > > the
> purpose of
> > > bdp-select and conf-select remains the same.
> > > > >> > > > > > >
> > > > >> > > > > >
> > > > >> > > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > >
> ---------------------------------------------------------------------
> > > > >> > > > To unsubscribe, e-mail:
> > > dev-unsubscribe@ambari.apache.org
> > > > >> > > > For additional commands,
> e-mail:
> > > dev-help@ambari.apache.org
> > > > >> > > >
> > > > >> > >
> > > > >> > >
> > >
> ---------------------------------------------------------------------
> > > > >> > > To unsubscribe, e-mail:
> > > dev-unsubscribe@ambari.apache.org
> > > > >> > > For additional commands,
> e-mail:
> > > dev-help@ambari.apache.org
> > > > >> > >
> > > > >> > >
> > > > >> >
> > > > >> >
> > >
> ---------------------------------------------------------------------
> > > > >> > To unsubscribe, e-mail:
> > > dev-unsubscribe@ambari.apache.org
> > > > >> > For additional commands, e-mail:
> > > dev-help@ambari.apache.org
> > > > >> >
> > > > >> >
> > > > >>
> > > > >>
> > >
> ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail:
> > > dev-unsubscribe@ambari.apache.org
> > > > >> For additional commands, e-mail:
> > > dev-help@ambari.apache.org
> > > > >>
> > > > >>
> > > >
> > > >
> > > >
> > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> > > >
> > > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Viraj Jasani <vj...@apache.org>.
Bumping this thread.
> I thinking we should have one stack which can support for upgrading the
existing the HDP deployed clusters. Even I can see somebody asking on
bigtop[2].
+1, we should have HDP (similar) stack to support minor version upgrades.
On Mon, Sep 5, 2022 at 12:30 AM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
> Hi @Masatake Iwasaki,
>
> > -1 as we already discussed.
> Thanks for your feedback, I would definitely honour it. As you are not
> open for discussion and asked us raise the PR hence you thought of
> discussing on the PR. What will be your final suggestion on this..?
>
> @Roman Shaposhnik
> I just gone through the following jira[1] where you brought ambari to
> bigtop. Looks stack-select is not included, how it was maintained.?
> I thinking we should have one stack which can support for upgrading the
> existing the HDP deployed clusters. Even I can see somebody asking on
> bigtop[2].
>
> If bigtop is not right place, shall we include in ambari..? Please let me
> know your thoughts on this. This blocks the 2.7.7 release.
>
> Note : There is on-going ambari mpack which might take some more time.
> Even upgrades will take some time.
>
>
> 1. https://issues.apache.org/jira/browse/BIGTOP-709
> 2. https://issues.apache.org/jira/browse/BIGTOP-3651
>
>
> Regards,
> Brahma Reddy Battula
>
>
> On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com>
> wrote:
>
> > May be we can name it as bdp-select. Or (bgp-select)
>
> -1 as we already discussed.
>
> On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
> > Ok, thanks Viraj.
> >
> > Hopefully you can place here like all other how it's maintained. Let
> me know any help required on this. May be we can name it as bdp-select. Or
> (bgp-select)
> >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> >
> >
> > On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org> wrote:
> >
> > Masatake, Brahma,
> >
> > Hopefully I should be able to create Jira and PR in Bigtop.
> Will let you
> > know once ready for review. Thanks
> >
> >
> > On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <
> iwasakims@oss.nttdata.com>
> > wrote:
> >
> > > Please file a JIRA and submit a pull request if you want to
> show the code
> > > and get feedback.
> > > There is nothing I want to discuss off the record.
> > >
> > > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> > > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others,
> can we get
> > > the final conclusion on this..?
> > > >
> > > > Please let me know your availability, Can have one call to
> discuss on
> > > this..
> > > >
> > > >
> > > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy"
> <bb...@visa.com.INVALID>
> > > wrote:
> > > >
> > > > > -1 on development in branch.
> > > > > It is not worth for maintaining the branch if the
> modules is
> > > so small
> > > > > and barely updated as explained here.
> > > > > It should not conflict to existing code.
> > > > > I feel I must check the code before check-in
> based on this
> > > thread.
> > > >
> > > >
> > > > Sure, Viraj or me can show the code to you.
> > > >
> > > > Can we've call on this Friday/Thrusday if that works..?
> > > >
> > > >
> > > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> > > iwasakims@oss.nttdata.com> wrote:
> > > >
> > > > > Sure, we can havemodule name like
> bigtop-distro-select.
> > > > > Initially we'll do this separate branch.
> > > >
> > > > -1 on development in branch.
> > > > It is not worth for maintaining the branch if the
> modules is so
> > > small
> > > > and barely updated as explained here.
> > > > It should not conflict to existing code.
> > > > I feel I must check the code before check-in based
> on this
> > > thread.
> > > >
> > > > Masatake Iwasaki
> > > >
> > > > On 2022/07/11 8:23, Kengo Seki wrote:
> > > > >> As there are different opinions on this and
> took long time,
> > > just to brainstorm all the possibilities and pitfalls.
> > > > >
> > > > > Oh, I interpreted your words "conclude" and
> "finalize" as you
> > > were
> > > > > going to make a final decision. Brainstorming is
> welcome, of
> > > course.
> > > > > (But I'm not so sure if all people concerned
> could join, due
> > > to time
> > > > > difference and their schedule, etc.)
> > > > >
> > > > >> Can you suggest, how the changes will be also..
> like folder,
> > > where you suggest to keep this...?
> > > > >
> > > > > Sure, here's my proposal:
> > > > >
> > > > > * Stack name: "BIGTOP"
> > > > >
> > > > > - The same name as the existing one [1]
> > > > > - Because it deploys the packages generated
> by Bigtop
> > > > > - The existing stack should be replaced with
> it, because
> > > that is
> > > > > based on Bigtop 0.8 and too old to use now
> > > > > - No concern about infringing others'
> trademark
> > > > >
> > > > > * Component/folder name: "bigtop-select"
> > > > >
> > > > > - Consistent naming convention with the
> existing tools
> > > such as
> > > > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils"
> [2]
> > > > > - If it sounds too simple and a bit unclear,
> a more
> > > descriptive name
> > > > > might be an option, for example
> "bigtop-ambari-stack-selector"
> > > > >
> > > > > * Script name: "bigtop-select"
> > > > >
> > > > > - Consistent with the stack name
> > > > > - No concern about infringing others'
> trademark
> > > > >
> > > > > [1]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
> > > > > [2]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> > > > >
> > > > > Kengo Seki <se...@apache.org>
> > > > >
> > > > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma
> Reddy
> > > > > <bb...@visa.com.invalid> wrote:
> > > > >>
> > > > >>> Technical decisions shouldn't be done on
> other places
> > > than public mailing lists,
> > > > >>> as described in the "Open Communications"
> section of [1]
> > > and [2].
> > > > >> > So we should conclude the discussion in
> this mailing
> > > list.
> > > > >> > (And with my poor English, I'm not so
> confident to catch
> > > up with your
> > > > >> > fluent talk ;)
> > > > >>
> > > > >> I believe , I knew the apache way which you
> mentioned. We
> > > are not going conclude anything which comes to bigtop other
> than this
> > > mailing list.
> > > > >> As there are different opinions on this and
> took long time,
> > > just to brainstorm all the possibilities and pitfalls. Hence
> asking let's
> > > have call so that we can brainstorm. Even after call,
> everything will be
> > > published what we discussed.
> > > > >>
> > > > >> I think, whiteboarding will help to catch up
> with you.
> > > > >>
> > > > >> You all the think "bigtop-select" will be best
> option
> > > right..? Can you suggest, how the changes will be also.. like
> folder, where
> > > you suggest to keep this...?
> > > > >>
> > > > >> And if the name represents the stack which we
> are going to
> > > deploy should fine I feel.. (if it's not BDP, may be
> > > OBDP:OpensourceBigDataPlatform.)
> > > > >>
> > > > >> @Viraj Jasani and others any thoughts..?
> > > > >>
> > > > >>
> > > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <
> sekikn@apache.org>
> > > wrote:
> > > > >>
> > > > >> > Looks we had so much discussed here,
> Let's try to
> > > conclude. Can we've one call on this and finalize this..?
> > > > >>
> > > > >> Technical decisions shouldn't be done on
> other places
> > > than public mailing lists,
> > > > >> as described in the "Open Communications"
> section of
> > > [1] and [2].
> > > > >> So we should conclude the discussion in
> this mailing
> > > list.
> > > > >> (And with my poor English, I'm not so
> confident to
> > > catch up with your
> > > > >> fluent talk ;)
> > > > >>
> > > > >> > FYI. Even looks bigtop used some where
> also..
> > > > >>
> > > > >> Bigtop is ASF's trademark as you can see
> in the "Apache
> > > Bigtop®
> > > > >> software" section of [3].
> > > > >> So it doesn't have the risk of trademark
> infringement.
> > > > >>
> > > > >> [1]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
> > > > >> [2]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
> > > > >> [3]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
> > > > >>
> > > > >> Kengo Seki <se...@apache.org>
> > > > >>
> > > > >> On Sun, Jul 10, 2022 at 4:11 AM Battula,
> Brahma Reddy
> > > > >> <bb...@visa.com.invalid> wrote:
> > > > >> >
> > > > >> > Looks we had so much discussed here,
> Let's try to
> > > conclude. Can we've one call on this and finalize this..?
> > > > >> >
> > > > >> > FYI. Even looks bigtop used some
> where[1] also..
> > > > >> > 1.
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
> > > > >> >
> > > > >> >
> > > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <
> sekikn@apache.org>
> > > wrote:
> > > > >> >
> > > > >> > Thank you for your explanation,
> Brahma.
> > > > >> > CRH (abbreviation of "CHINA REDOOP
> HYPERLOOP"
> > > [1]) is supposed to be a
> > > > >> > trademark of Redoop, so they can
> name the script
> > > crh-select without
> > > > >> > problem.
> > > > >> > But regarding BDP for example, I can
> easily find
> > > products that have
> > > > >> > the same name [2][3][4] as you
> already mentioned,
> > > so I'd like to
> > > > >> > recommend bigtop-select for avoiding
> unnecessary
> > > trouble.
> > > > >> > Or, a single and more general word
> just like
> > > conf-select may be less
> > > > >> > troublesome than bdp. How about
> "stack-select",
> > > for example?
> > > > >> >
> > > > >> > [1]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
> > > > >> > [2]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
> > > > >> > [3]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
> > > > >> > [4]:
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
> > > > >> >
> > > > >> > Kengo Seki <se...@apache.org>
> > > > >> >
> > > > >> > On Fri, Jul 8, 2022 at 2:51 AM
> Battula, Brahma
> > > Reddy <bb...@visa.com> wrote:
> > > > >> > >
> > > > >> > > >Do you mean that you're going
> to name the
> > > module (same as "component"
> > > > >> > > >in the Bigtop terminology, I
> think)
> > > bigtop-distro-select,
> > > > >> > > >and still the script in
> question
> > > bdp-select? If so, is there any
> > > > >> > > >reason that the script must
> be that name?
> > > > >> > > >(No offence, I just want to
> understand
> > > your thoughts and its
> > > > >> > > >background, and avoid the
> conflict or
> > > user's confusion with existing
> > > > >> > > >trademarks or products)
> > > > >> > >
> > > > >> > > Thanks @Kengo Seki for
> consolidating all the
> > > concerns. Name should represent the stack which includes all
> the components
> > > hence planning to have like bdp,bds...and this only one file
> like below[1]
> > > which has done redoop.
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
> > > > >> > >
> > > > >> > >
> > > > >> > > On 07/07/22, 6:07 AM, "Kengo Seki"
> <
> > > sekikn@apache.org> wrote:
> > > > >> > >
> > > > >> > > The following concern Masatake
> mentioned
> > > before is an important point,
> > > > >> > > so I talked to Brahma for
> clarifying his
> > > intention on the ASF Slack
> > > > >> > > yesterday.
> > > > >> > >
> > > > >> > > > Multiple versions of the
> same package
> > > (deb/rpm) can not be installed at the same time.
> > > > >> > > > IIRC, HDP uses convention in
> which the
> > > product version is part of package name
> > > > >> > > > for addressing this.
> > > > >> > >
> > > > >> > > > I don't like to bring the
> awkward package
> > > name convention to Bigtop
> > > > >> > > > at least by default.
> > > > >> > >
> > > > >> > > He's planning to adopt the
> same mitigation
> > > as HDP for now, but he
> > > > >> > > doesn't intend to change the
> default
> > > package naming convention of
> > > > >> > > Bigtop,
> > > > >> > > but just add a new
> functionality to include
> > > an extra part into the
> > > > >> > > package name for avoiding
> conflict, which
> > > is disabled by default.
> > > > >> > >
> > > > >> > > And Brahma, let me confirm
> about the
> > > following reply:
> > > > >> > >
> > > > >> > > > Sure, we can have module
> name like
> > > bigtop-distro-select.
> > > > >> > >
> > > > >> > > Do you mean that you're going
> to name the
> > > module (same as "component"
> > > > >> > > in the Bigtop terminology, I
> think)
> > > bigtop-distro-select,
> > > > >> > > and still the script in
> question
> > > bdp-select? If so, is there any
> > > > >> > > reason that the script must be
> that name?
> > > > >> > > (No offence, I just want to
> understand your
> > > thoughts and its
> > > > >> > > background, and avoid the
> conflict or
> > > user's confusion with existing
> > > > >> > > trademarks or products)
> > > > >> > >
> > > > >> > > Kengo Seki <se...@apache.org>
> > > > >> > >
> > > > >> > > On Thu, Jul 7, 2022 at 2:08 AM
> Battula,
> > > Brahma Reddy
> > > > >> > > <bb...@visa.com.invalid>
> wrote:
> > > > >> > > >
> > > > >> > > > > The name of stack based
> no Bigtop
> > > should be Bigtop.
> > > > >> > > > > If you can not accept
> the name like
> > > bigtop-*, the work should done outside of Bigtop.
> > > > >> > > > > I will cast -1 if
> someone submit a
> > > patch to add a module with the name spoiling branding.
> > > > >> > > >
> > > > >> > > > Sure, we can have module
> name like
> > > bigtop-distro-select.
> > > > >> > > > Initially we'll do this
> separate branch.
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > On 06/07/22, 8:55 AM,
> "Masatake Iwasaki" <
> > > iwasakims@oss.nttdata.co.jp> wrote:
> > > > >> > > >
> > > > >> > > > > I believe it's for
> project name.
> > > isn't it.?
> > > > >> > > >
> > > > >> > > > projects and products.
> > > > >> > > >
> > > > >> > > > > IMO, We need to create
> folders and
> > > refer stacknames so ambari-select,bigtop-select wn't looks
> good.
> > > > >> > > >
> > > > >> > > > The name of stack based
> no Bigtop
> > > should be Bigtop.
> > > > >> > > > If you can not accept
> the name like
> > > bigtop-*, the work should done outside of Bigtop.
> > > > >> > > > I will cast -1 if
> someone submit a
> > > patch to add a module with the name spoiling branding.
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > On 2022/07/06 11:44,
> Battula, Brahma
> > > Reddy wrote:
> > > > >> > > > >
> > > > >> > > > > I believe it's for
> project name.
> > > isn't it.?
> > > > >> > > > >
> > > > >> > > > >
> > > > >> > > > > On 06/07/22, 7:27 AM,
> "Masatake
> > > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > > >> > > > >
> > > > >> > > > > > But As we are
> not releasing
> > > as enterprise should be fine I think. IMO, We need to create
> folders and
> > > refer stacknames so ambari-select,bigtop-select wn't looks
> good.
> > > > >> > > > >
> > > > >> > > > > Not fine.
> > > > >> > > > > We have a
> trademark policy.
> > > > >> > > > >
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
> > > > >> > > > >
> > > > >> > > > > On 2022/07/06
> 10:37, Battula,
> > > Brahma Reddy wrote:
> > > > >> > > > > >> Should we avoid
> > > unrecognized brand which may be trademark of someone?
> > > > >> > > > > >> ambari-select
> or
> > > bigtop-select should be enough.
> > > > >> > > > > >
> > > > >> > > > > > Not sure, where
> to confirm
> > > whether there is already trademark. When I googled found so
> many.
> > > > >> > > > > > But As we are
> not releasing
> > > as enterprise should be fine I think. IMO, We need to create
> folders and
> > > refer stacknames so ambari-select,bigtop-select wn't looks
> good.
> > > > >> > > > > > May be you can
> refer the
> > > initial proposal [2] where I mentioned some more names.
> > > (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > > >> > > > > >
> > > > >> > > > > > Finally thanks
> a bunch for
> > > long healthy discussions on this. Mostly we all same page now.
> > > > >> > > > > >
> > > > >> > > > > > 1.
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
> > > > >> > > > > >
> > > > >> > > > > > 2.
> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > > On 06/07/22,
> 4:01 AM,
> > > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > > >> > > > > >
> > > > >> > > > > > > We have
> still not
> > > officially finalized the new replacement name for
> > > > >> > > > > > >
> hdp-select, it would
> > > likely be bdp-select (bdp: BigData Platform). However,
> > > > >> > > > > > > the
> purpose of
> > > bdp-select and conf-select remains the same.
> > > > >> > > > > >
> > > > >> > > > > > Should we
> avoid
> > > unrecognized brand which may be trademark of someone?
> > > > >> > > > > >
> ambari-select or
> > > bigtop-select should be enough.
> > > > >> > > > > >
> > > > >> > > > > > On
> 2022/06/29 13:52,
> > > Viraj Jasani wrote:
> > > > >> > > > > > > Hi
> Ambari/Bigtop dev,
> > > > >> > > > > > >
> > > > >> > > > > > > As per
> the new
> > > roadmap of Apache Ambari, we would like to propose moving
> > > > >> > > > > > > certain
> scripts
> > > (previously known as hdp-select and conf-select) to Bigtop
> > > > >> > > > > > > so that
> their rpm
> > > installation could be managed independently.
> > > > >> > > > > > > These
> scripts are a
> > > basic necessity in the Ambari framework for the
> > > > >> > > > > > >
> installation of
> > > various Bigdata packages. The only major changes they would
> > > > >> > > > > > > receive
> is when we
> > > onboard new services and components to Ambari, else they
> > > > >> > > > > > > usually
> do not
> > > receive updates. In the past, we used to get hdp-select rpm
> > > > >> > > > > > >
> downloaded and
> > > installed from HDP repositories.
> > > > >> > > > > > >
> > > > >> > > > > > > We have
> still not
> > > officially finalized the new replacement name for
> > > > >> > > > > > >
> hdp-select, it would
> > > likely be bdp-select (bdp: BigData Platform). However,
> > > > >> > > > > > > the
> purpose of
> > > bdp-select and conf-select remains the same.
> > > > >> > > > > > >
> > > > >> > > > > >
> > > > >> > > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > >
> ---------------------------------------------------------------------
> > > > >> > > > To unsubscribe, e-mail:
> > > dev-unsubscribe@ambari.apache.org
> > > > >> > > > For additional commands,
> e-mail:
> > > dev-help@ambari.apache.org
> > > > >> > > >
> > > > >> > >
> > > > >> > >
> > >
> ---------------------------------------------------------------------
> > > > >> > > To unsubscribe, e-mail:
> > > dev-unsubscribe@ambari.apache.org
> > > > >> > > For additional commands,
> e-mail:
> > > dev-help@ambari.apache.org
> > > > >> > >
> > > > >> > >
> > > > >> >
> > > > >> >
> > >
> ---------------------------------------------------------------------
> > > > >> > To unsubscribe, e-mail:
> > > dev-unsubscribe@ambari.apache.org
> > > > >> > For additional commands, e-mail:
> > > dev-help@ambari.apache.org
> > > > >> >
> > > > >> >
> > > > >>
> > > > >>
> > >
> ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail:
> > > dev-unsubscribe@ambari.apache.org
> > > > >> For additional commands, e-mail:
> > > dev-help@ambari.apache.org
> > > > >>
> > > > >>
> > > >
> > > >
> > > >
> > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> > > >
> > > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
Hi @Masatake Iwasaki,
> -1 as we already discussed.
Thanks for your feedback, I would definitely honour it. As you are not open for discussion and asked us raise the PR hence you thought of discussing on the PR. What will be your final suggestion on this..?
@Roman Shaposhnik
I just gone through the following jira[1] where you brought ambari to bigtop. Looks stack-select is not included, how it was maintained.?
I thinking we should have one stack which can support for upgrading the existing the HDP deployed clusters. Even I can see somebody asking on bigtop[2].
If bigtop is not right place, shall we include in ambari..? Please let me know your thoughts on this. This blocks the 2.7.7 release.
Note : There is on-going ambari mpack which might take some more time. Even upgrades will take some time.
1. https://issues.apache.org/jira/browse/BIGTOP-709
2. https://issues.apache.org/jira/browse/BIGTOP-3651
Regards,
Brahma Reddy Battula
On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com> wrote:
> May be we can name it as bdp-select. Or (bgp-select)
-1 as we already discussed.
On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
> Ok, thanks Viraj.
>
> Hopefully you can place here like all other how it's maintained. Let me know any help required on this. May be we can name it as bdp-select. Or (bgp-select)
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
>
>
> On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org> wrote:
>
> Masatake, Brahma,
>
> Hopefully I should be able to create Jira and PR in Bigtop. Will let you
> know once ready for review. Thanks
>
>
> On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <iw...@oss.nttdata.com>
> wrote:
>
> > Please file a JIRA and submit a pull request if you want to show the code
> > and get feedback.
> > There is nothing I want to discuss off the record.
> >
> > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get
> > the final conclusion on this..?
> > >
> > > Please let me know your availability, Can have one call to discuss on
> > this..
> > >
> > >
> > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
> > wrote:
> > >
> > > > -1 on development in branch.
> > > > It is not worth for maintaining the branch if the modules is
> > so small
> > > > and barely updated as explained here.
> > > > It should not conflict to existing code.
> > > > I feel I must check the code before check-in based on this
> > thread.
> > >
> > >
> > > Sure, Viraj or me can show the code to you.
> > >
> > > Can we've call on this Friday/Thrusday if that works..?
> > >
> > >
> > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> > iwasakims@oss.nttdata.com> wrote:
> > >
> > > > Sure, we can havemodule name like bigtop-distro-select.
> > > > Initially we'll do this separate branch.
> > >
> > > -1 on development in branch.
> > > It is not worth for maintaining the branch if the modules is so
> > small
> > > and barely updated as explained here.
> > > It should not conflict to existing code.
> > > I feel I must check the code before check-in based on this
> > thread.
> > >
> > > Masatake Iwasaki
> > >
> > > On 2022/07/11 8:23, Kengo Seki wrote:
> > > >> As there are different opinions on this and took long time,
> > just to brainstorm all the possibilities and pitfalls.
> > > >
> > > > Oh, I interpreted your words "conclude" and "finalize" as you
> > were
> > > > going to make a final decision. Brainstorming is welcome, of
> > course.
> > > > (But I'm not so sure if all people concerned could join, due
> > to time
> > > > difference and their schedule, etc.)
> > > >
> > > >> Can you suggest, how the changes will be also.. like folder,
> > where you suggest to keep this...?
> > > >
> > > > Sure, here's my proposal:
> > > >
> > > > * Stack name: "BIGTOP"
> > > >
> > > > - The same name as the existing one [1]
> > > > - Because it deploys the packages generated by Bigtop
> > > > - The existing stack should be replaced with it, because
> > that is
> > > > based on Bigtop 0.8 and too old to use now
> > > > - No concern about infringing others' trademark
> > > >
> > > > * Component/folder name: "bigtop-select"
> > > >
> > > > - Consistent naming convention with the existing tools
> > such as
> > > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > > > - If it sounds too simple and a bit unclear, a more
> > descriptive name
> > > > might be an option, for example "bigtop-ambari-stack-selector"
> > > >
> > > > * Script name: "bigtop-select"
> > > >
> > > > - Consistent with the stack name
> > > > - No concern about infringing others' trademark
> > > >
> > > > [1]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
> > > > [2]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> > > >
> > > > Kengo Seki <se...@apache.org>
> > > >
> > > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> > > > <bb...@visa.com.invalid> wrote:
> > > >>
> > > >>> Technical decisions shouldn't be done on other places
> > than public mailing lists,
> > > >>> as described in the "Open Communications" section of [1]
> > and [2].
> > > >> > So we should conclude the discussion in this mailing
> > list.
> > > >> > (And with my poor English, I'm not so confident to catch
> > up with your
> > > >> > fluent talk ;)
> > > >>
> > > >> I believe , I knew the apache way which you mentioned. We
> > are not going conclude anything which comes to bigtop other than this
> > mailing list.
> > > >> As there are different opinions on this and took long time,
> > just to brainstorm all the possibilities and pitfalls. Hence asking let's
> > have call so that we can brainstorm. Even after call, everything will be
> > published what we discussed.
> > > >>
> > > >> I think, whiteboarding will help to catch up with you.
> > > >>
> > > >> You all the think "bigtop-select" will be best option
> > right..? Can you suggest, how the changes will be also.. like folder, where
> > you suggest to keep this...?
> > > >>
> > > >> And if the name represents the stack which we are going to
> > deploy should fine I feel.. (if it's not BDP, may be
> > OBDP:OpensourceBigDataPlatform.)
> > > >>
> > > >> @Viraj Jasani and others any thoughts..?
> > > >>
> > > >>
> > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org>
> > wrote:
> > > >>
> > > >> > Looks we had so much discussed here, Let's try to
> > conclude. Can we've one call on this and finalize this..?
> > > >>
> > > >> Technical decisions shouldn't be done on other places
> > than public mailing lists,
> > > >> as described in the "Open Communications" section of
> > [1] and [2].
> > > >> So we should conclude the discussion in this mailing
> > list.
> > > >> (And with my poor English, I'm not so confident to
> > catch up with your
> > > >> fluent talk ;)
> > > >>
> > > >> > FYI. Even looks bigtop used some where also..
> > > >>
> > > >> Bigtop is ASF's trademark as you can see in the "Apache
> > Bigtop®
> > > >> software" section of [3].
> > > >> So it doesn't have the risk of trademark infringement.
> > > >>
> > > >> [1]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
> > > >> [2]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
> > > >> [3]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
> > > >>
> > > >> Kengo Seki <se...@apache.org>
> > > >>
> > > >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> > > >> <bb...@visa.com.invalid> wrote:
> > > >> >
> > > >> > Looks we had so much discussed here, Let's try to
> > conclude. Can we've one call on this and finalize this..?
> > > >> >
> > > >> > FYI. Even looks bigtop used some where[1] also..
> > > >> > 1.
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
> > > >> >
> > > >> >
> > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
> > wrote:
> > > >> >
> > > >> > Thank you for your explanation, Brahma.
> > > >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP"
> > [1]) is supposed to be a
> > > >> > trademark of Redoop, so they can name the script
> > crh-select without
> > > >> > problem.
> > > >> > But regarding BDP for example, I can easily find
> > products that have
> > > >> > the same name [2][3][4] as you already mentioned,
> > so I'd like to
> > > >> > recommend bigtop-select for avoiding unnecessary
> > trouble.
> > > >> > Or, a single and more general word just like
> > conf-select may be less
> > > >> > troublesome than bdp. How about "stack-select",
> > for example?
> > > >> >
> > > >> > [1]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
> > > >> > [2]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
> > > >> > [3]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
> > > >> > [4]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
> > > >> >
> > > >> > Kengo Seki <se...@apache.org>
> > > >> >
> > > >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma
> > Reddy <bb...@visa.com> wrote:
> > > >> > >
> > > >> > > >Do you mean that you're going to name the
> > module (same as "component"
> > > >> > > >in the Bigtop terminology, I think)
> > bigtop-distro-select,
> > > >> > > >and still the script in question
> > bdp-select? If so, is there any
> > > >> > > >reason that the script must be that name?
> > > >> > > >(No offence, I just want to understand
> > your thoughts and its
> > > >> > > >background, and avoid the conflict or
> > user's confusion with existing
> > > >> > > >trademarks or products)
> > > >> > >
> > > >> > > Thanks @Kengo Seki for consolidating all the
> > concerns. Name should represent the stack which includes all the components
> > hence planning to have like bdp,bds...and this only one file like below[1]
> > which has done redoop.
> > > >> > >
> > > >> > >
> > > >> > >
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
> > > >> > >
> > > >> > >
> > > >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
> > sekikn@apache.org> wrote:
> > > >> > >
> > > >> > > The following concern Masatake mentioned
> > before is an important point,
> > > >> > > so I talked to Brahma for clarifying his
> > intention on the ASF Slack
> > > >> > > yesterday.
> > > >> > >
> > > >> > > > Multiple versions of the same package
> > (deb/rpm) can not be installed at the same time.
> > > >> > > > IIRC, HDP uses convention in which the
> > product version is part of package name
> > > >> > > > for addressing this.
> > > >> > >
> > > >> > > > I don't like to bring the awkward package
> > name convention to Bigtop
> > > >> > > > at least by default.
> > > >> > >
> > > >> > > He's planning to adopt the same mitigation
> > as HDP for now, but he
> > > >> > > doesn't intend to change the default
> > package naming convention of
> > > >> > > Bigtop,
> > > >> > > but just add a new functionality to include
> > an extra part into the
> > > >> > > package name for avoiding conflict, which
> > is disabled by default.
> > > >> > >
> > > >> > > And Brahma, let me confirm about the
> > following reply:
> > > >> > >
> > > >> > > > Sure, we can have module name like
> > bigtop-distro-select.
> > > >> > >
> > > >> > > Do you mean that you're going to name the
> > module (same as "component"
> > > >> > > in the Bigtop terminology, I think)
> > bigtop-distro-select,
> > > >> > > and still the script in question
> > bdp-select? If so, is there any
> > > >> > > reason that the script must be that name?
> > > >> > > (No offence, I just want to understand your
> > thoughts and its
> > > >> > > background, and avoid the conflict or
> > user's confusion with existing
> > > >> > > trademarks or products)
> > > >> > >
> > > >> > > Kengo Seki <se...@apache.org>
> > > >> > >
> > > >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula,
> > Brahma Reddy
> > > >> > > <bb...@visa.com.invalid> wrote:
> > > >> > > >
> > > >> > > > > The name of stack based no Bigtop
> > should be Bigtop.
> > > >> > > > > If you can not accept the name like
> > bigtop-*, the work should done outside of Bigtop.
> > > >> > > > > I will cast -1 if someone submit a
> > patch to add a module with the name spoiling branding.
> > > >> > > >
> > > >> > > > Sure, we can have module name like
> > bigtop-distro-select.
> > > >> > > > Initially we'll do this separate branch.
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
> > iwasakims@oss.nttdata.co.jp> wrote:
> > > >> > > >
> > > >> > > > > I believe it's for project name.
> > isn't it.?
> > > >> > > >
> > > >> > > > projects and products.
> > > >> > > >
> > > >> > > > > IMO, We need to create folders and
> > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >> > > >
> > > >> > > > The name of stack based no Bigtop
> > should be Bigtop.
> > > >> > > > If you can not accept the name like
> > bigtop-*, the work should done outside of Bigtop.
> > > >> > > > I will cast -1 if someone submit a
> > patch to add a module with the name spoiling branding.
> > > >> > > >
> > > >> > > >
> > > >> > > > On 2022/07/06 11:44, Battula, Brahma
> > Reddy wrote:
> > > >> > > > >
> > > >> > > > > I believe it's for project name.
> > isn't it.?
> > > >> > > > >
> > > >> > > > >
> > > >> > > > > On 06/07/22, 7:27 AM, "Masatake
> > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >> > > > >
> > > >> > > > > > But As we are not releasing
> > as enterprise should be fine I think. IMO, We need to create folders and
> > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >> > > > >
> > > >> > > > > Not fine.
> > > >> > > > > We have a trademark policy.
> > > >> > > > >
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
> > > >> > > > >
> > > >> > > > > On 2022/07/06 10:37, Battula,
> > Brahma Reddy wrote:
> > > >> > > > > >> Should we avoid
> > unrecognized brand which may be trademark of someone?
> > > >> > > > > >> ambari-select or
> > bigtop-select should be enough.
> > > >> > > > > >
> > > >> > > > > > Not sure, where to confirm
> > whether there is already trademark. When I googled found so many.
> > > >> > > > > > But As we are not releasing
> > as enterprise should be fine I think. IMO, We need to create folders and
> > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >> > > > > > May be you can refer the
> > initial proposal [2] where I mentioned some more names.
> > (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > >> > > > > >
> > > >> > > > > > Finally thanks a bunch for
> > long healthy discussions on this. Mostly we all same page now.
> > > >> > > > > >
> > > >> > > > > > 1.
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
> > > >> > > > > >
> > > >> > > > > > 2.
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > > On 06/07/22, 4:01 AM,
> > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >> > > > > >
> > > >> > > > > > > We have still not
> > officially finalized the new replacement name for
> > > >> > > > > > > hdp-select, it would
> > likely be bdp-select (bdp: BigData Platform). However,
> > > >> > > > > > > the purpose of
> > bdp-select and conf-select remains the same.
> > > >> > > > > >
> > > >> > > > > > Should we avoid
> > unrecognized brand which may be trademark of someone?
> > > >> > > > > > ambari-select or
> > bigtop-select should be enough.
> > > >> > > > > >
> > > >> > > > > > On 2022/06/29 13:52,
> > Viraj Jasani wrote:
> > > >> > > > > > > Hi Ambari/Bigtop dev,
> > > >> > > > > > >
> > > >> > > > > > > As per the new
> > roadmap of Apache Ambari, we would like to propose moving
> > > >> > > > > > > certain scripts
> > (previously known as hdp-select and conf-select) to Bigtop
> > > >> > > > > > > so that their rpm
> > installation could be managed independently.
> > > >> > > > > > > These scripts are a
> > basic necessity in the Ambari framework for the
> > > >> > > > > > > installation of
> > various Bigdata packages. The only major changes they would
> > > >> > > > > > > receive is when we
> > onboard new services and components to Ambari, else they
> > > >> > > > > > > usually do not
> > receive updates. In the past, we used to get hdp-select rpm
> > > >> > > > > > > downloaded and
> > installed from HDP repositories.
> > > >> > > > > > >
> > > >> > > > > > > We have still not
> > officially finalized the new replacement name for
> > > >> > > > > > > hdp-select, it would
> > likely be bdp-select (bdp: BigData Platform). However,
> > > >> > > > > > > the purpose of
> > bdp-select and conf-select remains the same.
> > > >> > > > > > >
> > > >> > > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > ---------------------------------------------------------------------
> > > >> > > > To unsubscribe, e-mail:
> > dev-unsubscribe@ambari.apache.org
> > > >> > > > For additional commands, e-mail:
> > dev-help@ambari.apache.org
> > > >> > > >
> > > >> > >
> > > >> > >
> > ---------------------------------------------------------------------
> > > >> > > To unsubscribe, e-mail:
> > dev-unsubscribe@ambari.apache.org
> > > >> > > For additional commands, e-mail:
> > dev-help@ambari.apache.org
> > > >> > >
> > > >> > >
> > > >> >
> > > >> >
> > ---------------------------------------------------------------------
> > > >> > To unsubscribe, e-mail:
> > dev-unsubscribe@ambari.apache.org
> > > >> > For additional commands, e-mail:
> > dev-help@ambari.apache.org
> > > >> >
> > > >> >
> > > >>
> > > >>
> > ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail:
> > dev-unsubscribe@ambari.apache.org
> > > >> For additional commands, e-mail:
> > dev-help@ambari.apache.org
> > > >>
> > > >>
> > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > > For additional commands, e-mail: dev-help@ambari.apache.org
> > >
> > >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
Hi @Masatake Iwasaki,
> -1 as we already discussed.
Thanks for your feedback, I would definitely honour it. As you are not open for discussion and asked us raise the PR hence you thought of discussing on the PR. What will be your final suggestion on this..?
@Roman Shaposhnik
I just gone through the following jira[1] where you brought ambari to bigtop. Looks stack-select is not included, how it was maintained.?
I thinking we should have one stack which can support for upgrading the existing the HDP deployed clusters. Even I can see somebody asking on bigtop[2].
If bigtop is not right place, shall we include in ambari..? Please let me know your thoughts on this. This blocks the 2.7.7 release.
Note : There is on-going ambari mpack which might take some more time. Even upgrades will take some time.
1. https://issues.apache.org/jira/browse/BIGTOP-709
2. https://issues.apache.org/jira/browse/BIGTOP-3651
Regards,
Brahma Reddy Battula
On 01/09/22, 6:39 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com> wrote:
> May be we can name it as bdp-select. Or (bgp-select)
-1 as we already discussed.
On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
> Ok, thanks Viraj.
>
> Hopefully you can place here like all other how it's maintained. Let me know any help required on this. May be we can name it as bdp-select. Or (bgp-select)
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
>
>
> On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org> wrote:
>
> Masatake, Brahma,
>
> Hopefully I should be able to create Jira and PR in Bigtop. Will let you
> know once ready for review. Thanks
>
>
> On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <iw...@oss.nttdata.com>
> wrote:
>
> > Please file a JIRA and submit a pull request if you want to show the code
> > and get feedback.
> > There is nothing I want to discuss off the record.
> >
> > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get
> > the final conclusion on this..?
> > >
> > > Please let me know your availability, Can have one call to discuss on
> > this..
> > >
> > >
> > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
> > wrote:
> > >
> > > > -1 on development in branch.
> > > > It is not worth for maintaining the branch if the modules is
> > so small
> > > > and barely updated as explained here.
> > > > It should not conflict to existing code.
> > > > I feel I must check the code before check-in based on this
> > thread.
> > >
> > >
> > > Sure, Viraj or me can show the code to you.
> > >
> > > Can we've call on this Friday/Thrusday if that works..?
> > >
> > >
> > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> > iwasakims@oss.nttdata.com> wrote:
> > >
> > > > Sure, we can havemodule name like bigtop-distro-select.
> > > > Initially we'll do this separate branch.
> > >
> > > -1 on development in branch.
> > > It is not worth for maintaining the branch if the modules is so
> > small
> > > and barely updated as explained here.
> > > It should not conflict to existing code.
> > > I feel I must check the code before check-in based on this
> > thread.
> > >
> > > Masatake Iwasaki
> > >
> > > On 2022/07/11 8:23, Kengo Seki wrote:
> > > >> As there are different opinions on this and took long time,
> > just to brainstorm all the possibilities and pitfalls.
> > > >
> > > > Oh, I interpreted your words "conclude" and "finalize" as you
> > were
> > > > going to make a final decision. Brainstorming is welcome, of
> > course.
> > > > (But I'm not so sure if all people concerned could join, due
> > to time
> > > > difference and their schedule, etc.)
> > > >
> > > >> Can you suggest, how the changes will be also.. like folder,
> > where you suggest to keep this...?
> > > >
> > > > Sure, here's my proposal:
> > > >
> > > > * Stack name: "BIGTOP"
> > > >
> > > > - The same name as the existing one [1]
> > > > - Because it deploys the packages generated by Bigtop
> > > > - The existing stack should be replaced with it, because
> > that is
> > > > based on Bigtop 0.8 and too old to use now
> > > > - No concern about infringing others' trademark
> > > >
> > > > * Component/folder name: "bigtop-select"
> > > >
> > > > - Consistent naming convention with the existing tools
> > such as
> > > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > > > - If it sounds too simple and a bit unclear, a more
> > descriptive name
> > > > might be an option, for example "bigtop-ambari-stack-selector"
> > > >
> > > > * Script name: "bigtop-select"
> > > >
> > > > - Consistent with the stack name
> > > > - No concern about infringing others' trademark
> > > >
> > > > [1]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9BsY7Ho%2FS9Ogep35Yt0iiv0TXUULMbR2Ml25NP%2FX3gE%3D&reserved=0
> > > > [2]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=S%2FpiuGqaMjpNpr3AziXPz1QWTV5pD5OGx%2BICpSiXetE%3D&reserved=0
> > > >
> > > > Kengo Seki <se...@apache.org>
> > > >
> > > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> > > > <bb...@visa.com.invalid> wrote:
> > > >>
> > > >>> Technical decisions shouldn't be done on other places
> > than public mailing lists,
> > > >>> as described in the "Open Communications" section of [1]
> > and [2].
> > > >> > So we should conclude the discussion in this mailing
> > list.
> > > >> > (And with my poor English, I'm not so confident to catch
> > up with your
> > > >> > fluent talk ;)
> > > >>
> > > >> I believe , I knew the apache way which you mentioned. We
> > are not going conclude anything which comes to bigtop other than this
> > mailing list.
> > > >> As there are different opinions on this and took long time,
> > just to brainstorm all the possibilities and pitfalls. Hence asking let's
> > have call so that we can brainstorm. Even after call, everything will be
> > published what we discussed.
> > > >>
> > > >> I think, whiteboarding will help to catch up with you.
> > > >>
> > > >> You all the think "bigtop-select" will be best option
> > right..? Can you suggest, how the changes will be also.. like folder, where
> > you suggest to keep this...?
> > > >>
> > > >> And if the name represents the stack which we are going to
> > deploy should fine I feel.. (if it's not BDP, may be
> > OBDP:OpensourceBigDataPlatform.)
> > > >>
> > > >> @Viraj Jasani and others any thoughts..?
> > > >>
> > > >>
> > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org>
> > wrote:
> > > >>
> > > >> > Looks we had so much discussed here, Let's try to
> > conclude. Can we've one call on this and finalize this..?
> > > >>
> > > >> Technical decisions shouldn't be done on other places
> > than public mailing lists,
> > > >> as described in the "Open Communications" section of
> > [1] and [2].
> > > >> So we should conclude the discussion in this mailing
> > list.
> > > >> (And with my poor English, I'm not so confident to
> > catch up with your
> > > >> fluent talk ;)
> > > >>
> > > >> > FYI. Even looks bigtop used some where also..
> > > >>
> > > >> Bigtop is ASF's trademark as you can see in the "Apache
> > Bigtop®
> > > >> software" section of [3].
> > > >> So it doesn't have the risk of trademark infringement.
> > > >>
> > > >> [1]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JNFdxHAV%2B180ytJ84yCiX2MF1c3WptpCHkMMq2VIAvI%3D&reserved=0
> > > >> [2]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BX41Bd7gtizi4%2BoL922V1Se5hXMBUulwoDw1G4PuDKs%3D&reserved=0
> > > >> [3]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JURnKKTtR1bQhf1uQGgKgXUXZ%2FIxQMgsCpyoOKbAVjw%3D&reserved=0
> > > >>
> > > >> Kengo Seki <se...@apache.org>
> > > >>
> > > >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> > > >> <bb...@visa.com.invalid> wrote:
> > > >> >
> > > >> > Looks we had so much discussed here, Let's try to
> > conclude. Can we've one call on this and finalize this..?
> > > >> >
> > > >> > FYI. Even looks bigtop used some where[1] also..
> > > >> > 1.
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0%2Bd1Fdpqvm7xIg3xuifU4A4YxDyudbqR5QAcM3CY16A%3D&reserved=0(Microsoft_product)
> > > >> >
> > > >> >
> > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
> > wrote:
> > > >> >
> > > >> > Thank you for your explanation, Brahma.
> > > >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP"
> > [1]) is supposed to be a
> > > >> > trademark of Redoop, so they can name the script
> > crh-select without
> > > >> > problem.
> > > >> > But regarding BDP for example, I can easily find
> > products that have
> > > >> > the same name [2][3][4] as you already mentioned,
> > so I'd like to
> > > >> > recommend bigtop-select for avoiding unnecessary
> > trouble.
> > > >> > Or, a single and more general word just like
> > conf-select may be less
> > > >> > troublesome than bdp. How about "stack-select",
> > for example?
> > > >> >
> > > >> > [1]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnRgIq2HQVdtc1Kb%2BBLvnCTvS%2FhFKosRI8RUT%2FLdMWg%3D&reserved=0
> > > >> > [2]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J%2FU7YtNSZf3bj2gJdtAlqKOD32spN9WhxdXWFq99SNs%3D&reserved=0
> > > >> > [3]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VrvAvV2XqTceYlL0ECZALubZTYr9l3nCF8AGqRdpTwU%3D&reserved=0
> > > >> > [4]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BeN59qsYv8TtqHAmZiVGfgTDw8z8CS0SGvttMxrl1Sc%3D&reserved=0
> > > >> >
> > > >> > Kengo Seki <se...@apache.org>
> > > >> >
> > > >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma
> > Reddy <bb...@visa.com> wrote:
> > > >> > >
> > > >> > > >Do you mean that you're going to name the
> > module (same as "component"
> > > >> > > >in the Bigtop terminology, I think)
> > bigtop-distro-select,
> > > >> > > >and still the script in question
> > bdp-select? If so, is there any
> > > >> > > >reason that the script must be that name?
> > > >> > > >(No offence, I just want to understand
> > your thoughts and its
> > > >> > > >background, and avoid the conflict or
> > user's confusion with existing
> > > >> > > >trademarks or products)
> > > >> > >
> > > >> > > Thanks @Kengo Seki for consolidating all the
> > concerns. Name should represent the stack which includes all the components
> > hence planning to have like bdp,bds...and this only one file like below[1]
> > which has done redoop.
> > > >> > >
> > > >> > >
> > > >> > >
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cl4GkOSgDS%2BsmXbNAduR7Q9WDrirZuNH3BxRnVExdOs%3D&reserved=0
> > > >> > >
> > > >> > >
> > > >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
> > sekikn@apache.org> wrote:
> > > >> > >
> > > >> > > The following concern Masatake mentioned
> > before is an important point,
> > > >> > > so I talked to Brahma for clarifying his
> > intention on the ASF Slack
> > > >> > > yesterday.
> > > >> > >
> > > >> > > > Multiple versions of the same package
> > (deb/rpm) can not be installed at the same time.
> > > >> > > > IIRC, HDP uses convention in which the
> > product version is part of package name
> > > >> > > > for addressing this.
> > > >> > >
> > > >> > > > I don't like to bring the awkward package
> > name convention to Bigtop
> > > >> > > > at least by default.
> > > >> > >
> > > >> > > He's planning to adopt the same mitigation
> > as HDP for now, but he
> > > >> > > doesn't intend to change the default
> > package naming convention of
> > > >> > > Bigtop,
> > > >> > > but just add a new functionality to include
> > an extra part into the
> > > >> > > package name for avoiding conflict, which
> > is disabled by default.
> > > >> > >
> > > >> > > And Brahma, let me confirm about the
> > following reply:
> > > >> > >
> > > >> > > > Sure, we can have module name like
> > bigtop-distro-select.
> > > >> > >
> > > >> > > Do you mean that you're going to name the
> > module (same as "component"
> > > >> > > in the Bigtop terminology, I think)
> > bigtop-distro-select,
> > > >> > > and still the script in question
> > bdp-select? If so, is there any
> > > >> > > reason that the script must be that name?
> > > >> > > (No offence, I just want to understand your
> > thoughts and its
> > > >> > > background, and avoid the conflict or
> > user's confusion with existing
> > > >> > > trademarks or products)
> > > >> > >
> > > >> > > Kengo Seki <se...@apache.org>
> > > >> > >
> > > >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula,
> > Brahma Reddy
> > > >> > > <bb...@visa.com.invalid> wrote:
> > > >> > > >
> > > >> > > > > The name of stack based no Bigtop
> > should be Bigtop.
> > > >> > > > > If you can not accept the name like
> > bigtop-*, the work should done outside of Bigtop.
> > > >> > > > > I will cast -1 if someone submit a
> > patch to add a module with the name spoiling branding.
> > > >> > > >
> > > >> > > > Sure, we can have module name like
> > bigtop-distro-select.
> > > >> > > > Initially we'll do this separate branch.
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
> > iwasakims@oss.nttdata.co.jp> wrote:
> > > >> > > >
> > > >> > > > > I believe it's for project name.
> > isn't it.?
> > > >> > > >
> > > >> > > > projects and products.
> > > >> > > >
> > > >> > > > > IMO, We need to create folders and
> > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >> > > >
> > > >> > > > The name of stack based no Bigtop
> > should be Bigtop.
> > > >> > > > If you can not accept the name like
> > bigtop-*, the work should done outside of Bigtop.
> > > >> > > > I will cast -1 if someone submit a
> > patch to add a module with the name spoiling branding.
> > > >> > > >
> > > >> > > >
> > > >> > > > On 2022/07/06 11:44, Battula, Brahma
> > Reddy wrote:
> > > >> > > > >
> > > >> > > > > I believe it's for project name.
> > isn't it.?
> > > >> > > > >
> > > >> > > > >
> > > >> > > > > On 06/07/22, 7:27 AM, "Masatake
> > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >> > > > >
> > > >> > > > > > But As we are not releasing
> > as enterprise should be fine I think. IMO, We need to create folders and
> > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >> > > > >
> > > >> > > > > Not fine.
> > > >> > > > > We have a trademark policy.
> > > >> > > > >
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qkTFTQlsip9TRVtauQkfYZ4AiGsv8trePgiUfatgIBk%3D&reserved=0
> > > >> > > > >
> > > >> > > > > On 2022/07/06 10:37, Battula,
> > Brahma Reddy wrote:
> > > >> > > > > >> Should we avoid
> > unrecognized brand which may be trademark of someone?
> > > >> > > > > >> ambari-select or
> > bigtop-select should be enough.
> > > >> > > > > >
> > > >> > > > > > Not sure, where to confirm
> > whether there is already trademark. When I googled found so many.
> > > >> > > > > > But As we are not releasing
> > as enterprise should be fine I think. IMO, We need to create folders and
> > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >> > > > > > May be you can refer the
> > initial proposal [2] where I mentioned some more names.
> > (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > >> > > > > >
> > > >> > > > > > Finally thanks a bunch for
> > long healthy discussions on this. Mostly we all same page now.
> > > >> > > > > >
> > > >> > > > > > 1.
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RGK%2BHXKy7f%2FBt9mE6WPnD7t2HalGvCG3EyRe7fO0wpM%3D&reserved=0
> > > >> > > > > >
> > > >> > > > > > 2.
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Caf797ca5e4694d7c174a08da8bb69b8b%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637975913668870137%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dsitL9J4ubgqbNv3Dd1NngYqCMKYxvsuZZrhK6wSnpE%3D&reserved=0
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > > On 06/07/22, 4:01 AM,
> > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >> > > > > >
> > > >> > > > > > > We have still not
> > officially finalized the new replacement name for
> > > >> > > > > > > hdp-select, it would
> > likely be bdp-select (bdp: BigData Platform). However,
> > > >> > > > > > > the purpose of
> > bdp-select and conf-select remains the same.
> > > >> > > > > >
> > > >> > > > > > Should we avoid
> > unrecognized brand which may be trademark of someone?
> > > >> > > > > > ambari-select or
> > bigtop-select should be enough.
> > > >> > > > > >
> > > >> > > > > > On 2022/06/29 13:52,
> > Viraj Jasani wrote:
> > > >> > > > > > > Hi Ambari/Bigtop dev,
> > > >> > > > > > >
> > > >> > > > > > > As per the new
> > roadmap of Apache Ambari, we would like to propose moving
> > > >> > > > > > > certain scripts
> > (previously known as hdp-select and conf-select) to Bigtop
> > > >> > > > > > > so that their rpm
> > installation could be managed independently.
> > > >> > > > > > > These scripts are a
> > basic necessity in the Ambari framework for the
> > > >> > > > > > > installation of
> > various Bigdata packages. The only major changes they would
> > > >> > > > > > > receive is when we
> > onboard new services and components to Ambari, else they
> > > >> > > > > > > usually do not
> > receive updates. In the past, we used to get hdp-select rpm
> > > >> > > > > > > downloaded and
> > installed from HDP repositories.
> > > >> > > > > > >
> > > >> > > > > > > We have still not
> > officially finalized the new replacement name for
> > > >> > > > > > > hdp-select, it would
> > likely be bdp-select (bdp: BigData Platform). However,
> > > >> > > > > > > the purpose of
> > bdp-select and conf-select remains the same.
> > > >> > > > > > >
> > > >> > > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > ---------------------------------------------------------------------
> > > >> > > > To unsubscribe, e-mail:
> > dev-unsubscribe@ambari.apache.org
> > > >> > > > For additional commands, e-mail:
> > dev-help@ambari.apache.org
> > > >> > > >
> > > >> > >
> > > >> > >
> > ---------------------------------------------------------------------
> > > >> > > To unsubscribe, e-mail:
> > dev-unsubscribe@ambari.apache.org
> > > >> > > For additional commands, e-mail:
> > dev-help@ambari.apache.org
> > > >> > >
> > > >> > >
> > > >> >
> > > >> >
> > ---------------------------------------------------------------------
> > > >> > To unsubscribe, e-mail:
> > dev-unsubscribe@ambari.apache.org
> > > >> > For additional commands, e-mail:
> > dev-help@ambari.apache.org
> > > >> >
> > > >> >
> > > >>
> > > >>
> > ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail:
> > dev-unsubscribe@ambari.apache.org
> > > >> For additional commands, e-mail:
> > dev-help@ambari.apache.org
> > > >>
> > > >>
> > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > > For additional commands, e-mail: dev-help@ambari.apache.org
> > >
> > >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.com>.
> May be we can name it as bdp-select. Or (bgp-select)
-1 as we already discussed.
On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
> Ok, thanks Viraj.
>
> Hopefully you can place here like all other how it's maintained. Let me know any help required on this. May be we can name it as bdp-select. Or (bgp-select)
> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common
>
>
> On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org> wrote:
>
> Masatake, Brahma,
>
> Hopefully I should be able to create Jira and PR in Bigtop. Will let you
> know once ready for review. Thanks
>
>
> On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <iw...@oss.nttdata.com>
> wrote:
>
> > Please file a JIRA and submit a pull request if you want to show the code
> > and get feedback.
> > There is nothing I want to discuss off the record.
> >
> > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get
> > the final conclusion on this..?
> > >
> > > Please let me know your availability, Can have one call to discuss on
> > this..
> > >
> > >
> > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
> > wrote:
> > >
> > > > -1 on development in branch.
> > > > It is not worth for maintaining the branch if the modules is
> > so small
> > > > and barely updated as explained here.
> > > > It should not conflict to existing code.
> > > > I feel I must check the code before check-in based on this
> > thread.
> > >
> > >
> > > Sure, Viraj or me can show the code to you.
> > >
> > > Can we've call on this Friday/Thrusday if that works..?
> > >
> > >
> > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> > iwasakims@oss.nttdata.com> wrote:
> > >
> > > > Sure, we can havemodule name like bigtop-distro-select.
> > > > Initially we'll do this separate branch.
> > >
> > > -1 on development in branch.
> > > It is not worth for maintaining the branch if the modules is so
> > small
> > > and barely updated as explained here.
> > > It should not conflict to existing code.
> > > I feel I must check the code before check-in based on this
> > thread.
> > >
> > > Masatake Iwasaki
> > >
> > > On 2022/07/11 8:23, Kengo Seki wrote:
> > > >> As there are different opinions on this and took long time,
> > just to brainstorm all the possibilities and pitfalls.
> > > >
> > > > Oh, I interpreted your words "conclude" and "finalize" as you
> > were
> > > > going to make a final decision. Brainstorming is welcome, of
> > course.
> > > > (But I'm not so sure if all people concerned could join, due
> > to time
> > > > difference and their schedule, etc.)
> > > >
> > > >> Can you suggest, how the changes will be also.. like folder,
> > where you suggest to keep this...?
> > > >
> > > > Sure, here's my proposal:
> > > >
> > > > * Stack name: "BIGTOP"
> > > >
> > > > - The same name as the existing one [1]
> > > > - Because it deploys the packages generated by Bigtop
> > > > - The existing stack should be replaced with it, because
> > that is
> > > > based on Bigtop 0.8 and too old to use now
> > > > - No concern about infringing others' trademark
> > > >
> > > > * Component/folder name: "bigtop-select"
> > > >
> > > > - Consistent naming convention with the existing tools
> > such as
> > > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > > > - If it sounds too simple and a bit unclear, a more
> > descriptive name
> > > > might be an option, for example "bigtop-ambari-stack-selector"
> > > >
> > > > * Script name: "bigtop-select"
> > > >
> > > > - Consistent with the stack name
> > > > - No concern about infringing others' trademark
> > > >
> > > > [1]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sOGC38xRa2H2AYhpz1XxwyiBwwYUfEw87soznjX9fmI%3D&reserved=0
> > > > [2]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CKqWD99nsiBrKv3IZtZXInadLmVzatK3zsSQxWkbLX4%3D&reserved=0
> > > >
> > > > Kengo Seki <se...@apache.org>
> > > >
> > > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> > > > <bb...@visa.com.invalid> wrote:
> > > >>
> > > >>> Technical decisions shouldn't be done on other places
> > than public mailing lists,
> > > >>> as described in the "Open Communications" section of [1]
> > and [2].
> > > >> > So we should conclude the discussion in this mailing
> > list.
> > > >> > (And with my poor English, I'm not so confident to catch
> > up with your
> > > >> > fluent talk ;)
> > > >>
> > > >> I believe , I knew the apache way which you mentioned. We
> > are not going conclude anything which comes to bigtop other than this
> > mailing list.
> > > >> As there are different opinions on this and took long time,
> > just to brainstorm all the possibilities and pitfalls. Hence asking let's
> > have call so that we can brainstorm. Even after call, everything will be
> > published what we discussed.
> > > >>
> > > >> I think, whiteboarding will help to catch up with you.
> > > >>
> > > >> You all the think "bigtop-select" will be best option
> > right..? Can you suggest, how the changes will be also.. like folder, where
> > you suggest to keep this...?
> > > >>
> > > >> And if the name represents the stack which we are going to
> > deploy should fine I feel.. (if it's not BDP, may be
> > OBDP:OpensourceBigDataPlatform.)
> > > >>
> > > >> @Viraj Jasani and others any thoughts..?
> > > >>
> > > >>
> > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org>
> > wrote:
> > > >>
> > > >> > Looks we had so much discussed here, Let's try to
> > conclude. Can we've one call on this and finalize this..?
> > > >>
> > > >> Technical decisions shouldn't be done on other places
> > than public mailing lists,
> > > >> as described in the "Open Communications" section of
> > [1] and [2].
> > > >> So we should conclude the discussion in this mailing
> > list.
> > > >> (And with my poor English, I'm not so confident to
> > catch up with your
> > > >> fluent talk ;)
> > > >>
> > > >> > FYI. Even looks bigtop used some where also..
> > > >>
> > > >> Bigtop is ASF's trademark as you can see in the "Apache
> > Bigtop®
> > > >> software" section of [3].
> > > >> So it doesn't have the risk of trademark infringement.
> > > >>
> > > >> [1]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VnSOJv998y6BR%2B%2B3gEwt3gC4ajiqxR3yxv%2FMuym14OI%3D&reserved=0
> > > >> [2]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Z8lzba6TN%2FCgEXb%2FfBK6Fc6P%2FD74ICMmrGo8O8%2BvmsU%3D&reserved=0
> > > >> [3]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CFeD4ngXC7I8E6v0GcV9LmD0KLlOfL3jsrWcwj%2BibWA%3D&reserved=0
> > > >>
> > > >> Kengo Seki <se...@apache.org>
> > > >>
> > > >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> > > >> <bb...@visa.com.invalid> wrote:
> > > >> >
> > > >> > Looks we had so much discussed here, Let's try to
> > conclude. Can we've one call on this and finalize this..?
> > > >> >
> > > >> > FYI. Even looks bigtop used some where[1] also..
> > > >> > 1.
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=F0Fa4qQC1DwyNDUqBamzb7eCZSphpuxQ%2FqWkE10w%2F3o%3D&reserved=0(Microsoft_product)
> > > >> >
> > > >> >
> > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
> > wrote:
> > > >> >
> > > >> > Thank you for your explanation, Brahma.
> > > >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP"
> > [1]) is supposed to be a
> > > >> > trademark of Redoop, so they can name the script
> > crh-select without
> > > >> > problem.
> > > >> > But regarding BDP for example, I can easily find
> > products that have
> > > >> > the same name [2][3][4] as you already mentioned,
> > so I'd like to
> > > >> > recommend bigtop-select for avoiding unnecessary
> > trouble.
> > > >> > Or, a single and more general word just like
> > conf-select may be less
> > > >> > troublesome than bdp. How about "stack-select",
> > for example?
> > > >> >
> > > >> > [1]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dy6I2wH2aSIkQKa9fJX7nDbbUWjQ07aTvcdSZXCGCYM%3D&reserved=0
> > > >> > [2]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sE%2Fb5kum9UIOQQ1NonfA0ZZk04cghtU%2BYIpvLf1mofo%3D&reserved=0
> > > >> > [3]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ey61twpiXZXBJ10YFWhmBWV4w8KyQ4NadpM5itom83Q%3D&reserved=0
> > > >> > [4]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=AzmiiA7TLiJmWR2M0iD%2BQJnS9XZrCU5t2K7KjipzvDg%3D&reserved=0
> > > >> >
> > > >> > Kengo Seki <se...@apache.org>
> > > >> >
> > > >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma
> > Reddy <bb...@visa.com> wrote:
> > > >> > >
> > > >> > > >Do you mean that you're going to name the
> > module (same as "component"
> > > >> > > >in the Bigtop terminology, I think)
> > bigtop-distro-select,
> > > >> > > >and still the script in question
> > bdp-select? If so, is there any
> > > >> > > >reason that the script must be that name?
> > > >> > > >(No offence, I just want to understand
> > your thoughts and its
> > > >> > > >background, and avoid the conflict or
> > user's confusion with existing
> > > >> > > >trademarks or products)
> > > >> > >
> > > >> > > Thanks @Kengo Seki for consolidating all the
> > concerns. Name should represent the stack which includes all the components
> > hence planning to have like bdp,bds...and this only one file like below[1]
> > which has done redoop.
> > > >> > >
> > > >> > >
> > > >> > >
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dNFPGfC2F9DUoKX3TPGwTiz4%2BQXacQ4FZzr3%2B6eHLRg%3D&reserved=0
> > > >> > >
> > > >> > >
> > > >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
> > sekikn@apache.org> wrote:
> > > >> > >
> > > >> > > The following concern Masatake mentioned
> > before is an important point,
> > > >> > > so I talked to Brahma for clarifying his
> > intention on the ASF Slack
> > > >> > > yesterday.
> > > >> > >
> > > >> > > > Multiple versions of the same package
> > (deb/rpm) can not be installed at the same time.
> > > >> > > > IIRC, HDP uses convention in which the
> > product version is part of package name
> > > >> > > > for addressing this.
> > > >> > >
> > > >> > > > I don't like to bring the awkward package
> > name convention to Bigtop
> > > >> > > > at least by default.
> > > >> > >
> > > >> > > He's planning to adopt the same mitigation
> > as HDP for now, but he
> > > >> > > doesn't intend to change the default
> > package naming convention of
> > > >> > > Bigtop,
> > > >> > > but just add a new functionality to include
> > an extra part into the
> > > >> > > package name for avoiding conflict, which
> > is disabled by default.
> > > >> > >
> > > >> > > And Brahma, let me confirm about the
> > following reply:
> > > >> > >
> > > >> > > > Sure, we can have module name like
> > bigtop-distro-select.
> > > >> > >
> > > >> > > Do you mean that you're going to name the
> > module (same as "component"
> > > >> > > in the Bigtop terminology, I think)
> > bigtop-distro-select,
> > > >> > > and still the script in question
> > bdp-select? If so, is there any
> > > >> > > reason that the script must be that name?
> > > >> > > (No offence, I just want to understand your
> > thoughts and its
> > > >> > > background, and avoid the conflict or
> > user's confusion with existing
> > > >> > > trademarks or products)
> > > >> > >
> > > >> > > Kengo Seki <se...@apache.org>
> > > >> > >
> > > >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula,
> > Brahma Reddy
> > > >> > > <bb...@visa.com.invalid> wrote:
> > > >> > > >
> > > >> > > > > The name of stack based no Bigtop
> > should be Bigtop.
> > > >> > > > > If you can not accept the name like
> > bigtop-*, the work should done outside of Bigtop.
> > > >> > > > > I will cast -1 if someone submit a
> > patch to add a module with the name spoiling branding.
> > > >> > > >
> > > >> > > > Sure, we can have module name like
> > bigtop-distro-select.
> > > >> > > > Initially we'll do this separate branch.
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
> > iwasakims@oss.nttdata.co.jp> wrote:
> > > >> > > >
> > > >> > > > > I believe it's for project name.
> > isn't it.?
> > > >> > > >
> > > >> > > > projects and products.
> > > >> > > >
> > > >> > > > > IMO, We need to create folders and
> > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >> > > >
> > > >> > > > The name of stack based no Bigtop
> > should be Bigtop.
> > > >> > > > If you can not accept the name like
> > bigtop-*, the work should done outside of Bigtop.
> > > >> > > > I will cast -1 if someone submit a
> > patch to add a module with the name spoiling branding.
> > > >> > > >
> > > >> > > >
> > > >> > > > On 2022/07/06 11:44, Battula, Brahma
> > Reddy wrote:
> > > >> > > > >
> > > >> > > > > I believe it's for project name.
> > isn't it.?
> > > >> > > > >
> > > >> > > > >
> > > >> > > > > On 06/07/22, 7:27 AM, "Masatake
> > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >> > > > >
> > > >> > > > > > But As we are not releasing
> > as enterprise should be fine I think. IMO, We need to create folders and
> > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >> > > > >
> > > >> > > > > Not fine.
> > > >> > > > > We have a trademark policy.
> > > >> > > > >
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=XQM8jgnE0tJRSDpjDELPXw1%2B%2Fsq0forEMVS15aYgWbg%3D&reserved=0
> > > >> > > > >
> > > >> > > > > On 2022/07/06 10:37, Battula,
> > Brahma Reddy wrote:
> > > >> > > > > >> Should we avoid
> > unrecognized brand which may be trademark of someone?
> > > >> > > > > >> ambari-select or
> > bigtop-select should be enough.
> > > >> > > > > >
> > > >> > > > > > Not sure, where to confirm
> > whether there is already trademark. When I googled found so many.
> > > >> > > > > > But As we are not releasing
> > as enterprise should be fine I think. IMO, We need to create folders and
> > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >> > > > > > May be you can refer the
> > initial proposal [2] where I mentioned some more names.
> > (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > >> > > > > >
> > > >> > > > > > Finally thanks a bunch for
> > long healthy discussions on this. Mostly we all same page now.
> > > >> > > > > >
> > > >> > > > > > 1.
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GGtYy%2B6poKMJ62Cp9vrrjiou1YrciQ7ow0RFU1vTQRA%3D&reserved=0
> > > >> > > > > >
> > > >> > > > > > 2.
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ucOrDSTO2EiSbVb67pmT3d7w4OBv%2BPpckx5KDdc8%2FWU%3D&reserved=0
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > > On 06/07/22, 4:01 AM,
> > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >> > > > > >
> > > >> > > > > > > We have still not
> > officially finalized the new replacement name for
> > > >> > > > > > > hdp-select, it would
> > likely be bdp-select (bdp: BigData Platform). However,
> > > >> > > > > > > the purpose of
> > bdp-select and conf-select remains the same.
> > > >> > > > > >
> > > >> > > > > > Should we avoid
> > unrecognized brand which may be trademark of someone?
> > > >> > > > > > ambari-select or
> > bigtop-select should be enough.
> > > >> > > > > >
> > > >> > > > > > On 2022/06/29 13:52,
> > Viraj Jasani wrote:
> > > >> > > > > > > Hi Ambari/Bigtop dev,
> > > >> > > > > > >
> > > >> > > > > > > As per the new
> > roadmap of Apache Ambari, we would like to propose moving
> > > >> > > > > > > certain scripts
> > (previously known as hdp-select and conf-select) to Bigtop
> > > >> > > > > > > so that their rpm
> > installation could be managed independently.
> > > >> > > > > > > These scripts are a
> > basic necessity in the Ambari framework for the
> > > >> > > > > > > installation of
> > various Bigdata packages. The only major changes they would
> > > >> > > > > > > receive is when we
> > onboard new services and components to Ambari, else they
> > > >> > > > > > > usually do not
> > receive updates. In the past, we used to get hdp-select rpm
> > > >> > > > > > > downloaded and
> > installed from HDP repositories.
> > > >> > > > > > >
> > > >> > > > > > > We have still not
> > officially finalized the new replacement name for
> > > >> > > > > > > hdp-select, it would
> > likely be bdp-select (bdp: BigData Platform). However,
> > > >> > > > > > > the purpose of
> > bdp-select and conf-select remains the same.
> > > >> > > > > > >
> > > >> > > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > ---------------------------------------------------------------------
> > > >> > > > To unsubscribe, e-mail:
> > dev-unsubscribe@ambari.apache.org
> > > >> > > > For additional commands, e-mail:
> > dev-help@ambari.apache.org
> > > >> > > >
> > > >> > >
> > > >> > >
> > ---------------------------------------------------------------------
> > > >> > > To unsubscribe, e-mail:
> > dev-unsubscribe@ambari.apache.org
> > > >> > > For additional commands, e-mail:
> > dev-help@ambari.apache.org
> > > >> > >
> > > >> > >
> > > >> >
> > > >> >
> > ---------------------------------------------------------------------
> > > >> > To unsubscribe, e-mail:
> > dev-unsubscribe@ambari.apache.org
> > > >> > For additional commands, e-mail:
> > dev-help@ambari.apache.org
> > > >> >
> > > >> >
> > > >>
> > > >>
> > ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail:
> > dev-unsubscribe@ambari.apache.org
> > > >> For additional commands, e-mail:
> > dev-help@ambari.apache.org
> > > >>
> > > >>
> > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > > For additional commands, e-mail: dev-help@ambari.apache.org
> > >
> > >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.com>.
> May be we can name it as bdp-select. Or (bgp-select)
-1 as we already discussed.
On 2022/09/01 4:43, Battula, Brahma Reddy wrote:
> Ok, thanks Viraj.
>
> Hopefully you can place here like all other how it's maintained. Let me know any help required on this. May be we can name it as bdp-select. Or (bgp-select)
> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common
>
>
> On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org> wrote:
>
> Masatake, Brahma,
>
> Hopefully I should be able to create Jira and PR in Bigtop. Will let you
> know once ready for review. Thanks
>
>
> On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <iw...@oss.nttdata.com>
> wrote:
>
> > Please file a JIRA and submit a pull request if you want to show the code
> > and get feedback.
> > There is nothing I want to discuss off the record.
> >
> > On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> > > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get
> > the final conclusion on this..?
> > >
> > > Please let me know your availability, Can have one call to discuss on
> > this..
> > >
> > >
> > > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
> > wrote:
> > >
> > > > -1 on development in branch.
> > > > It is not worth for maintaining the branch if the modules is
> > so small
> > > > and barely updated as explained here.
> > > > It should not conflict to existing code.
> > > > I feel I must check the code before check-in based on this
> > thread.
> > >
> > >
> > > Sure, Viraj or me can show the code to you.
> > >
> > > Can we've call on this Friday/Thrusday if that works..?
> > >
> > >
> > > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> > iwasakims@oss.nttdata.com> wrote:
> > >
> > > > Sure, we can havemodule name like bigtop-distro-select.
> > > > Initially we'll do this separate branch.
> > >
> > > -1 on development in branch.
> > > It is not worth for maintaining the branch if the modules is so
> > small
> > > and barely updated as explained here.
> > > It should not conflict to existing code.
> > > I feel I must check the code before check-in based on this
> > thread.
> > >
> > > Masatake Iwasaki
> > >
> > > On 2022/07/11 8:23, Kengo Seki wrote:
> > > >> As there are different opinions on this and took long time,
> > just to brainstorm all the possibilities and pitfalls.
> > > >
> > > > Oh, I interpreted your words "conclude" and "finalize" as you
> > were
> > > > going to make a final decision. Brainstorming is welcome, of
> > course.
> > > > (But I'm not so sure if all people concerned could join, due
> > to time
> > > > difference and their schedule, etc.)
> > > >
> > > >> Can you suggest, how the changes will be also.. like folder,
> > where you suggest to keep this...?
> > > >
> > > > Sure, here's my proposal:
> > > >
> > > > * Stack name: "BIGTOP"
> > > >
> > > > - The same name as the existing one [1]
> > > > - Because it deploys the packages generated by Bigtop
> > > > - The existing stack should be replaced with it, because
> > that is
> > > > based on Bigtop 0.8 and too old to use now
> > > > - No concern about infringing others' trademark
> > > >
> > > > * Component/folder name: "bigtop-select"
> > > >
> > > > - Consistent naming convention with the existing tools
> > such as
> > > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > > > - If it sounds too simple and a bit unclear, a more
> > descriptive name
> > > > might be an option, for example "bigtop-ambari-stack-selector"
> > > >
> > > > * Script name: "bigtop-select"
> > > >
> > > > - Consistent with the stack name
> > > > - No concern about infringing others' trademark
> > > >
> > > > [1]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sOGC38xRa2H2AYhpz1XxwyiBwwYUfEw87soznjX9fmI%3D&reserved=0
> > > > [2]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CKqWD99nsiBrKv3IZtZXInadLmVzatK3zsSQxWkbLX4%3D&reserved=0
> > > >
> > > > Kengo Seki <se...@apache.org>
> > > >
> > > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> > > > <bb...@visa.com.invalid> wrote:
> > > >>
> > > >>> Technical decisions shouldn't be done on other places
> > than public mailing lists,
> > > >>> as described in the "Open Communications" section of [1]
> > and [2].
> > > >> > So we should conclude the discussion in this mailing
> > list.
> > > >> > (And with my poor English, I'm not so confident to catch
> > up with your
> > > >> > fluent talk ;)
> > > >>
> > > >> I believe , I knew the apache way which you mentioned. We
> > are not going conclude anything which comes to bigtop other than this
> > mailing list.
> > > >> As there are different opinions on this and took long time,
> > just to brainstorm all the possibilities and pitfalls. Hence asking let's
> > have call so that we can brainstorm. Even after call, everything will be
> > published what we discussed.
> > > >>
> > > >> I think, whiteboarding will help to catch up with you.
> > > >>
> > > >> You all the think "bigtop-select" will be best option
> > right..? Can you suggest, how the changes will be also.. like folder, where
> > you suggest to keep this...?
> > > >>
> > > >> And if the name represents the stack which we are going to
> > deploy should fine I feel.. (if it's not BDP, may be
> > OBDP:OpensourceBigDataPlatform.)
> > > >>
> > > >> @Viraj Jasani and others any thoughts..?
> > > >>
> > > >>
> > > >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org>
> > wrote:
> > > >>
> > > >> > Looks we had so much discussed here, Let's try to
> > conclude. Can we've one call on this and finalize this..?
> > > >>
> > > >> Technical decisions shouldn't be done on other places
> > than public mailing lists,
> > > >> as described in the "Open Communications" section of
> > [1] and [2].
> > > >> So we should conclude the discussion in this mailing
> > list.
> > > >> (And with my poor English, I'm not so confident to
> > catch up with your
> > > >> fluent talk ;)
> > > >>
> > > >> > FYI. Even looks bigtop used some where also..
> > > >>
> > > >> Bigtop is ASF's trademark as you can see in the "Apache
> > Bigtop®
> > > >> software" section of [3].
> > > >> So it doesn't have the risk of trademark infringement.
> > > >>
> > > >> [1]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VnSOJv998y6BR%2B%2B3gEwt3gC4ajiqxR3yxv%2FMuym14OI%3D&reserved=0
> > > >> [2]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Z8lzba6TN%2FCgEXb%2FfBK6Fc6P%2FD74ICMmrGo8O8%2BvmsU%3D&reserved=0
> > > >> [3]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CFeD4ngXC7I8E6v0GcV9LmD0KLlOfL3jsrWcwj%2BibWA%3D&reserved=0
> > > >>
> > > >> Kengo Seki <se...@apache.org>
> > > >>
> > > >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> > > >> <bb...@visa.com.invalid> wrote:
> > > >> >
> > > >> > Looks we had so much discussed here, Let's try to
> > conclude. Can we've one call on this and finalize this..?
> > > >> >
> > > >> > FYI. Even looks bigtop used some where[1] also..
> > > >> > 1.
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=F0Fa4qQC1DwyNDUqBamzb7eCZSphpuxQ%2FqWkE10w%2F3o%3D&reserved=0(Microsoft_product)
> > > >> >
> > > >> >
> > > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
> > wrote:
> > > >> >
> > > >> > Thank you for your explanation, Brahma.
> > > >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP"
> > [1]) is supposed to be a
> > > >> > trademark of Redoop, so they can name the script
> > crh-select without
> > > >> > problem.
> > > >> > But regarding BDP for example, I can easily find
> > products that have
> > > >> > the same name [2][3][4] as you already mentioned,
> > so I'd like to
> > > >> > recommend bigtop-select for avoiding unnecessary
> > trouble.
> > > >> > Or, a single and more general word just like
> > conf-select may be less
> > > >> > troublesome than bdp. How about "stack-select",
> > for example?
> > > >> >
> > > >> > [1]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dy6I2wH2aSIkQKa9fJX7nDbbUWjQ07aTvcdSZXCGCYM%3D&reserved=0
> > > >> > [2]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sE%2Fb5kum9UIOQQ1NonfA0ZZk04cghtU%2BYIpvLf1mofo%3D&reserved=0
> > > >> > [3]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ey61twpiXZXBJ10YFWhmBWV4w8KyQ4NadpM5itom83Q%3D&reserved=0
> > > >> > [4]:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=AzmiiA7TLiJmWR2M0iD%2BQJnS9XZrCU5t2K7KjipzvDg%3D&reserved=0
> > > >> >
> > > >> > Kengo Seki <se...@apache.org>
> > > >> >
> > > >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma
> > Reddy <bb...@visa.com> wrote:
> > > >> > >
> > > >> > > >Do you mean that you're going to name the
> > module (same as "component"
> > > >> > > >in the Bigtop terminology, I think)
> > bigtop-distro-select,
> > > >> > > >and still the script in question
> > bdp-select? If so, is there any
> > > >> > > >reason that the script must be that name?
> > > >> > > >(No offence, I just want to understand
> > your thoughts and its
> > > >> > > >background, and avoid the conflict or
> > user's confusion with existing
> > > >> > > >trademarks or products)
> > > >> > >
> > > >> > > Thanks @Kengo Seki for consolidating all the
> > concerns. Name should represent the stack which includes all the components
> > hence planning to have like bdp,bds...and this only one file like below[1]
> > which has done redoop.
> > > >> > >
> > > >> > >
> > > >> > >
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dNFPGfC2F9DUoKX3TPGwTiz4%2BQXacQ4FZzr3%2B6eHLRg%3D&reserved=0
> > > >> > >
> > > >> > >
> > > >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
> > sekikn@apache.org> wrote:
> > > >> > >
> > > >> > > The following concern Masatake mentioned
> > before is an important point,
> > > >> > > so I talked to Brahma for clarifying his
> > intention on the ASF Slack
> > > >> > > yesterday.
> > > >> > >
> > > >> > > > Multiple versions of the same package
> > (deb/rpm) can not be installed at the same time.
> > > >> > > > IIRC, HDP uses convention in which the
> > product version is part of package name
> > > >> > > > for addressing this.
> > > >> > >
> > > >> > > > I don't like to bring the awkward package
> > name convention to Bigtop
> > > >> > > > at least by default.
> > > >> > >
> > > >> > > He's planning to adopt the same mitigation
> > as HDP for now, but he
> > > >> > > doesn't intend to change the default
> > package naming convention of
> > > >> > > Bigtop,
> > > >> > > but just add a new functionality to include
> > an extra part into the
> > > >> > > package name for avoiding conflict, which
> > is disabled by default.
> > > >> > >
> > > >> > > And Brahma, let me confirm about the
> > following reply:
> > > >> > >
> > > >> > > > Sure, we can have module name like
> > bigtop-distro-select.
> > > >> > >
> > > >> > > Do you mean that you're going to name the
> > module (same as "component"
> > > >> > > in the Bigtop terminology, I think)
> > bigtop-distro-select,
> > > >> > > and still the script in question
> > bdp-select? If so, is there any
> > > >> > > reason that the script must be that name?
> > > >> > > (No offence, I just want to understand your
> > thoughts and its
> > > >> > > background, and avoid the conflict or
> > user's confusion with existing
> > > >> > > trademarks or products)
> > > >> > >
> > > >> > > Kengo Seki <se...@apache.org>
> > > >> > >
> > > >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula,
> > Brahma Reddy
> > > >> > > <bb...@visa.com.invalid> wrote:
> > > >> > > >
> > > >> > > > > The name of stack based no Bigtop
> > should be Bigtop.
> > > >> > > > > If you can not accept the name like
> > bigtop-*, the work should done outside of Bigtop.
> > > >> > > > > I will cast -1 if someone submit a
> > patch to add a module with the name spoiling branding.
> > > >> > > >
> > > >> > > > Sure, we can have module name like
> > bigtop-distro-select.
> > > >> > > > Initially we'll do this separate branch.
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
> > iwasakims@oss.nttdata.co.jp> wrote:
> > > >> > > >
> > > >> > > > > I believe it's for project name.
> > isn't it.?
> > > >> > > >
> > > >> > > > projects and products.
> > > >> > > >
> > > >> > > > > IMO, We need to create folders and
> > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >> > > >
> > > >> > > > The name of stack based no Bigtop
> > should be Bigtop.
> > > >> > > > If you can not accept the name like
> > bigtop-*, the work should done outside of Bigtop.
> > > >> > > > I will cast -1 if someone submit a
> > patch to add a module with the name spoiling branding.
> > > >> > > >
> > > >> > > >
> > > >> > > > On 2022/07/06 11:44, Battula, Brahma
> > Reddy wrote:
> > > >> > > > >
> > > >> > > > > I believe it's for project name.
> > isn't it.?
> > > >> > > > >
> > > >> > > > >
> > > >> > > > > On 06/07/22, 7:27 AM, "Masatake
> > Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >> > > > >
> > > >> > > > > > But As we are not releasing
> > as enterprise should be fine I think. IMO, We need to create folders and
> > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >> > > > >
> > > >> > > > > Not fine.
> > > >> > > > > We have a trademark policy.
> > > >> > > > >
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=XQM8jgnE0tJRSDpjDELPXw1%2B%2Fsq0forEMVS15aYgWbg%3D&reserved=0
> > > >> > > > >
> > > >> > > > > On 2022/07/06 10:37, Battula,
> > Brahma Reddy wrote:
> > > >> > > > > >> Should we avoid
> > unrecognized brand which may be trademark of someone?
> > > >> > > > > >> ambari-select or
> > bigtop-select should be enough.
> > > >> > > > > >
> > > >> > > > > > Not sure, where to confirm
> > whether there is already trademark. When I googled found so many.
> > > >> > > > > > But As we are not releasing
> > as enterprise should be fine I think. IMO, We need to create folders and
> > refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >> > > > > > May be you can refer the
> > initial proposal [2] where I mentioned some more names.
> > (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > >> > > > > >
> > > >> > > > > > Finally thanks a bunch for
> > long healthy discussions on this. Mostly we all same page now.
> > > >> > > > > >
> > > >> > > > > > 1.
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GGtYy%2B6poKMJ62Cp9vrrjiou1YrciQ7ow0RFU1vTQRA%3D&reserved=0
> > > >> > > > > >
> > > >> > > > > > 2.
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ucOrDSTO2EiSbVb67pmT3d7w4OBv%2BPpckx5KDdc8%2FWU%3D&reserved=0
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > > On 06/07/22, 4:01 AM,
> > "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >> > > > > >
> > > >> > > > > > > We have still not
> > officially finalized the new replacement name for
> > > >> > > > > > > hdp-select, it would
> > likely be bdp-select (bdp: BigData Platform). However,
> > > >> > > > > > > the purpose of
> > bdp-select and conf-select remains the same.
> > > >> > > > > >
> > > >> > > > > > Should we avoid
> > unrecognized brand which may be trademark of someone?
> > > >> > > > > > ambari-select or
> > bigtop-select should be enough.
> > > >> > > > > >
> > > >> > > > > > On 2022/06/29 13:52,
> > Viraj Jasani wrote:
> > > >> > > > > > > Hi Ambari/Bigtop dev,
> > > >> > > > > > >
> > > >> > > > > > > As per the new
> > roadmap of Apache Ambari, we would like to propose moving
> > > >> > > > > > > certain scripts
> > (previously known as hdp-select and conf-select) to Bigtop
> > > >> > > > > > > so that their rpm
> > installation could be managed independently.
> > > >> > > > > > > These scripts are a
> > basic necessity in the Ambari framework for the
> > > >> > > > > > > installation of
> > various Bigdata packages. The only major changes they would
> > > >> > > > > > > receive is when we
> > onboard new services and components to Ambari, else they
> > > >> > > > > > > usually do not
> > receive updates. In the past, we used to get hdp-select rpm
> > > >> > > > > > > downloaded and
> > installed from HDP repositories.
> > > >> > > > > > >
> > > >> > > > > > > We have still not
> > officially finalized the new replacement name for
> > > >> > > > > > > hdp-select, it would
> > likely be bdp-select (bdp: BigData Platform). However,
> > > >> > > > > > > the purpose of
> > bdp-select and conf-select remains the same.
> > > >> > > > > > >
> > > >> > > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > ---------------------------------------------------------------------
> > > >> > > > To unsubscribe, e-mail:
> > dev-unsubscribe@ambari.apache.org
> > > >> > > > For additional commands, e-mail:
> > dev-help@ambari.apache.org
> > > >> > > >
> > > >> > >
> > > >> > >
> > ---------------------------------------------------------------------
> > > >> > > To unsubscribe, e-mail:
> > dev-unsubscribe@ambari.apache.org
> > > >> > > For additional commands, e-mail:
> > dev-help@ambari.apache.org
> > > >> > >
> > > >> > >
> > > >> >
> > > >> >
> > ---------------------------------------------------------------------
> > > >> > To unsubscribe, e-mail:
> > dev-unsubscribe@ambari.apache.org
> > > >> > For additional commands, e-mail:
> > dev-help@ambari.apache.org
> > > >> >
> > > >> >
> > > >>
> > > >>
> > ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail:
> > dev-unsubscribe@ambari.apache.org
> > > >> For additional commands, e-mail:
> > dev-help@ambari.apache.org
> > > >>
> > > >>
> > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > > For additional commands, e-mail: dev-help@ambari.apache.org
> > >
> > >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
Ok, thanks Viraj.
Hopefully you can place here like all other how it's maintained. Let me know any help required on this. May be we can name it as bdp-select. Or (bgp-select)
https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common
On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org> wrote:
Masatake, Brahma,
Hopefully I should be able to create Jira and PR in Bigtop. Will let you
know once ready for review. Thanks
On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <iw...@oss.nttdata.com>
wrote:
> Please file a JIRA and submit a pull request if you want to show the code
> and get feedback.
> There is nothing I want to discuss off the record.
>
> On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get
> the final conclusion on this..?
> >
> > Please let me know your availability, Can have one call to discuss on
> this..
> >
> >
> > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
> wrote:
> >
> > > -1 on development in branch.
> > > It is not worth for maintaining the branch if the modules is
> so small
> > > and barely updated as explained here.
> > > It should not conflict to existing code.
> > > I feel I must check the code before check-in based on this
> thread.
> >
> >
> > Sure, Viraj or me can show the code to you.
> >
> > Can we've call on this Friday/Thrusday if that works..?
> >
> >
> > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.com> wrote:
> >
> > > Sure, we can havemodule name like bigtop-distro-select.
> > > Initially we'll do this separate branch.
> >
> > -1 on development in branch.
> > It is not worth for maintaining the branch if the modules is so
> small
> > and barely updated as explained here.
> > It should not conflict to existing code.
> > I feel I must check the code before check-in based on this
> thread.
> >
> > Masatake Iwasaki
> >
> > On 2022/07/11 8:23, Kengo Seki wrote:
> > >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls.
> > >
> > > Oh, I interpreted your words "conclude" and "finalize" as you
> were
> > > going to make a final decision. Brainstorming is welcome, of
> course.
> > > (But I'm not so sure if all people concerned could join, due
> to time
> > > difference and their schedule, etc.)
> > >
> > >> Can you suggest, how the changes will be also.. like folder,
> where you suggest to keep this...?
> > >
> > > Sure, here's my proposal:
> > >
> > > * Stack name: "BIGTOP"
> > >
> > > - The same name as the existing one [1]
> > > - Because it deploys the packages generated by Bigtop
> > > - The existing stack should be replaced with it, because
> that is
> > > based on Bigtop 0.8 and too old to use now
> > > - No concern about infringing others' trademark
> > >
> > > * Component/folder name: "bigtop-select"
> > >
> > > - Consistent naming convention with the existing tools
> such as
> > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > > - If it sounds too simple and a bit unclear, a more
> descriptive name
> > > might be an option, for example "bigtop-ambari-stack-selector"
> > >
> > > * Script name: "bigtop-select"
> > >
> > > - Consistent with the stack name
> > > - No concern about infringing others' trademark
> > >
> > > [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sOGC38xRa2H2AYhpz1XxwyiBwwYUfEw87soznjX9fmI%3D&reserved=0
> > > [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CKqWD99nsiBrKv3IZtZXInadLmVzatK3zsSQxWkbLX4%3D&reserved=0
> > >
> > > Kengo Seki <se...@apache.org>
> > >
> > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> > > <bb...@visa.com.invalid> wrote:
> > >>
> > >>> Technical decisions shouldn't be done on other places
> than public mailing lists,
> > >>> as described in the "Open Communications" section of [1]
> and [2].
> > >> > So we should conclude the discussion in this mailing
> list.
> > >> > (And with my poor English, I'm not so confident to catch
> up with your
> > >> > fluent talk ;)
> > >>
> > >> I believe , I knew the apache way which you mentioned. We
> are not going conclude anything which comes to bigtop other than this
> mailing list.
> > >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls. Hence asking let's
> have call so that we can brainstorm. Even after call, everything will be
> published what we discussed.
> > >>
> > >> I think, whiteboarding will help to catch up with you.
> > >>
> > >> You all the think "bigtop-select" will be best option
> right..? Can you suggest, how the changes will be also.. like folder, where
> you suggest to keep this...?
> > >>
> > >> And if the name represents the stack which we are going to
> deploy should fine I feel.. (if it's not BDP, may be
> OBDP:OpensourceBigDataPlatform.)
> > >>
> > >> @Viraj Jasani and others any thoughts..?
> > >>
> > >>
> > >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org>
> wrote:
> > >>
> > >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> > >>
> > >> Technical decisions shouldn't be done on other places
> than public mailing lists,
> > >> as described in the "Open Communications" section of
> [1] and [2].
> > >> So we should conclude the discussion in this mailing
> list.
> > >> (And with my poor English, I'm not so confident to
> catch up with your
> > >> fluent talk ;)
> > >>
> > >> > FYI. Even looks bigtop used some where also..
> > >>
> > >> Bigtop is ASF's trademark as you can see in the "Apache
> Bigtop®
> > >> software" section of [3].
> > >> So it doesn't have the risk of trademark infringement.
> > >>
> > >> [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VnSOJv998y6BR%2B%2B3gEwt3gC4ajiqxR3yxv%2FMuym14OI%3D&reserved=0
> > >> [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Z8lzba6TN%2FCgEXb%2FfBK6Fc6P%2FD74ICMmrGo8O8%2BvmsU%3D&reserved=0
> > >> [3]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CFeD4ngXC7I8E6v0GcV9LmD0KLlOfL3jsrWcwj%2BibWA%3D&reserved=0
> > >>
> > >> Kengo Seki <se...@apache.org>
> > >>
> > >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> > >> <bb...@visa.com.invalid> wrote:
> > >> >
> > >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> > >> >
> > >> > FYI. Even looks bigtop used some where[1] also..
> > >> > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=F0Fa4qQC1DwyNDUqBamzb7eCZSphpuxQ%2FqWkE10w%2F3o%3D&reserved=0(Microsoft_product)
> > >> >
> > >> >
> > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
> wrote:
> > >> >
> > >> > Thank you for your explanation, Brahma.
> > >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP"
> [1]) is supposed to be a
> > >> > trademark of Redoop, so they can name the script
> crh-select without
> > >> > problem.
> > >> > But regarding BDP for example, I can easily find
> products that have
> > >> > the same name [2][3][4] as you already mentioned,
> so I'd like to
> > >> > recommend bigtop-select for avoiding unnecessary
> trouble.
> > >> > Or, a single and more general word just like
> conf-select may be less
> > >> > troublesome than bdp. How about "stack-select",
> for example?
> > >> >
> > >> > [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dy6I2wH2aSIkQKa9fJX7nDbbUWjQ07aTvcdSZXCGCYM%3D&reserved=0
> > >> > [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sE%2Fb5kum9UIOQQ1NonfA0ZZk04cghtU%2BYIpvLf1mofo%3D&reserved=0
> > >> > [3]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ey61twpiXZXBJ10YFWhmBWV4w8KyQ4NadpM5itom83Q%3D&reserved=0
> > >> > [4]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=AzmiiA7TLiJmWR2M0iD%2BQJnS9XZrCU5t2K7KjipzvDg%3D&reserved=0
> > >> >
> > >> > Kengo Seki <se...@apache.org>
> > >> >
> > >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma
> Reddy <bb...@visa.com> wrote:
> > >> > >
> > >> > > >Do you mean that you're going to name the
> module (same as "component"
> > >> > > >in the Bigtop terminology, I think)
> bigtop-distro-select,
> > >> > > >and still the script in question
> bdp-select? If so, is there any
> > >> > > >reason that the script must be that name?
> > >> > > >(No offence, I just want to understand
> your thoughts and its
> > >> > > >background, and avoid the conflict or
> user's confusion with existing
> > >> > > >trademarks or products)
> > >> > >
> > >> > > Thanks @Kengo Seki for consolidating all the
> concerns. Name should represent the stack which includes all the components
> hence planning to have like bdp,bds...and this only one file like below[1]
> which has done redoop.
> > >> > >
> > >> > >
> > >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dNFPGfC2F9DUoKX3TPGwTiz4%2BQXacQ4FZzr3%2B6eHLRg%3D&reserved=0
> > >> > >
> > >> > >
> > >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
> sekikn@apache.org> wrote:
> > >> > >
> > >> > > The following concern Masatake mentioned
> before is an important point,
> > >> > > so I talked to Brahma for clarifying his
> intention on the ASF Slack
> > >> > > yesterday.
> > >> > >
> > >> > > > Multiple versions of the same package
> (deb/rpm) can not be installed at the same time.
> > >> > > > IIRC, HDP uses convention in which the
> product version is part of package name
> > >> > > > for addressing this.
> > >> > >
> > >> > > > I don't like to bring the awkward package
> name convention to Bigtop
> > >> > > > at least by default.
> > >> > >
> > >> > > He's planning to adopt the same mitigation
> as HDP for now, but he
> > >> > > doesn't intend to change the default
> package naming convention of
> > >> > > Bigtop,
> > >> > > but just add a new functionality to include
> an extra part into the
> > >> > > package name for avoiding conflict, which
> is disabled by default.
> > >> > >
> > >> > > And Brahma, let me confirm about the
> following reply:
> > >> > >
> > >> > > > Sure, we can have module name like
> bigtop-distro-select.
> > >> > >
> > >> > > Do you mean that you're going to name the
> module (same as "component"
> > >> > > in the Bigtop terminology, I think)
> bigtop-distro-select,
> > >> > > and still the script in question
> bdp-select? If so, is there any
> > >> > > reason that the script must be that name?
> > >> > > (No offence, I just want to understand your
> thoughts and its
> > >> > > background, and avoid the conflict or
> user's confusion with existing
> > >> > > trademarks or products)
> > >> > >
> > >> > > Kengo Seki <se...@apache.org>
> > >> > >
> > >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula,
> Brahma Reddy
> > >> > > <bb...@visa.com.invalid> wrote:
> > >> > > >
> > >> > > > > The name of stack based no Bigtop
> should be Bigtop.
> > >> > > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> > >> > > > > I will cast -1 if someone submit a
> patch to add a module with the name spoiling branding.
> > >> > > >
> > >> > > > Sure, we can have module name like
> bigtop-distro-select.
> > >> > > > Initially we'll do this separate branch.
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.co.jp> wrote:
> > >> > > >
> > >> > > > > I believe it's for project name.
> isn't it.?
> > >> > > >
> > >> > > > projects and products.
> > >> > > >
> > >> > > > > IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >> > > >
> > >> > > > The name of stack based no Bigtop
> should be Bigtop.
> > >> > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> > >> > > > I will cast -1 if someone submit a
> patch to add a module with the name spoiling branding.
> > >> > > >
> > >> > > >
> > >> > > > On 2022/07/06 11:44, Battula, Brahma
> Reddy wrote:
> > >> > > > >
> > >> > > > > I believe it's for project name.
> isn't it.?
> > >> > > > >
> > >> > > > >
> > >> > > > > On 06/07/22, 7:27 AM, "Masatake
> Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >> > > > >
> > >> > > > > > But As we are not releasing
> as enterprise should be fine I think. IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >> > > > >
> > >> > > > > Not fine.
> > >> > > > > We have a trademark policy.
> > >> > > > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=XQM8jgnE0tJRSDpjDELPXw1%2B%2Fsq0forEMVS15aYgWbg%3D&reserved=0
> > >> > > > >
> > >> > > > > On 2022/07/06 10:37, Battula,
> Brahma Reddy wrote:
> > >> > > > > >> Should we avoid
> unrecognized brand which may be trademark of someone?
> > >> > > > > >> ambari-select or
> bigtop-select should be enough.
> > >> > > > > >
> > >> > > > > > Not sure, where to confirm
> whether there is already trademark. When I googled found so many.
> > >> > > > > > But As we are not releasing
> as enterprise should be fine I think. IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >> > > > > > May be you can refer the
> initial proposal [2] where I mentioned some more names.
> (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > >> > > > > >
> > >> > > > > > Finally thanks a bunch for
> long healthy discussions on this. Mostly we all same page now.
> > >> > > > > >
> > >> > > > > > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GGtYy%2B6poKMJ62Cp9vrrjiou1YrciQ7ow0RFU1vTQRA%3D&reserved=0
> > >> > > > > >
> > >> > > > > > 2.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ucOrDSTO2EiSbVb67pmT3d7w4OBv%2BPpckx5KDdc8%2FWU%3D&reserved=0
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > On 06/07/22, 4:01 AM,
> "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >> > > > > >
> > >> > > > > > > We have still not
> officially finalized the new replacement name for
> > >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> > >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> > >> > > > > >
> > >> > > > > > Should we avoid
> unrecognized brand which may be trademark of someone?
> > >> > > > > > ambari-select or
> bigtop-select should be enough.
> > >> > > > > >
> > >> > > > > > On 2022/06/29 13:52,
> Viraj Jasani wrote:
> > >> > > > > > > Hi Ambari/Bigtop dev,
> > >> > > > > > >
> > >> > > > > > > As per the new
> roadmap of Apache Ambari, we would like to propose moving
> > >> > > > > > > certain scripts
> (previously known as hdp-select and conf-select) to Bigtop
> > >> > > > > > > so that their rpm
> installation could be managed independently.
> > >> > > > > > > These scripts are a
> basic necessity in the Ambari framework for the
> > >> > > > > > > installation of
> various Bigdata packages. The only major changes they would
> > >> > > > > > > receive is when we
> onboard new services and components to Ambari, else they
> > >> > > > > > > usually do not
> receive updates. In the past, we used to get hdp-select rpm
> > >> > > > > > > downloaded and
> installed from HDP repositories.
> > >> > > > > > >
> > >> > > > > > > We have still not
> officially finalized the new replacement name for
> > >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> > >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> > >> > > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > > >
> > >> > > >
> ---------------------------------------------------------------------
> > >> > > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > >> > > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> > >> > > >
> > >> > >
> > >> > >
> ---------------------------------------------------------------------
> > >> > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > >> > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> > >> > >
> > >> > >
> > >> >
> > >> >
> ---------------------------------------------------------------------
> > >> > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > >> > For additional commands, e-mail:
> dev-help@ambari.apache.org
> > >> >
> > >> >
> > >>
> > >>
> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > >> For additional commands, e-mail:
> dev-help@ambari.apache.org
> > >>
> > >>
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
> >
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
Ok, thanks Viraj.
Hopefully you can place here like all other how it's maintained. Let me know any help required on this. May be we can name it as bdp-select. Or (bgp-select)
https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common
On 30/08/22, 5:26 AM, "Viraj Jasani" <vj...@apache.org> wrote:
Masatake, Brahma,
Hopefully I should be able to create Jira and PR in Bigtop. Will let you
know once ready for review. Thanks
On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <iw...@oss.nttdata.com>
wrote:
> Please file a JIRA and submit a pull request if you want to show the code
> and get feedback.
> There is nothing I want to discuss off the record.
>
> On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get
> the final conclusion on this..?
> >
> > Please let me know your availability, Can have one call to discuss on
> this..
> >
> >
> > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
> wrote:
> >
> > > -1 on development in branch.
> > > It is not worth for maintaining the branch if the modules is
> so small
> > > and barely updated as explained here.
> > > It should not conflict to existing code.
> > > I feel I must check the code before check-in based on this
> thread.
> >
> >
> > Sure, Viraj or me can show the code to you.
> >
> > Can we've call on this Friday/Thrusday if that works..?
> >
> >
> > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.com> wrote:
> >
> > > Sure, we can havemodule name like bigtop-distro-select.
> > > Initially we'll do this separate branch.
> >
> > -1 on development in branch.
> > It is not worth for maintaining the branch if the modules is so
> small
> > and barely updated as explained here.
> > It should not conflict to existing code.
> > I feel I must check the code before check-in based on this
> thread.
> >
> > Masatake Iwasaki
> >
> > On 2022/07/11 8:23, Kengo Seki wrote:
> > >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls.
> > >
> > > Oh, I interpreted your words "conclude" and "finalize" as you
> were
> > > going to make a final decision. Brainstorming is welcome, of
> course.
> > > (But I'm not so sure if all people concerned could join, due
> to time
> > > difference and their schedule, etc.)
> > >
> > >> Can you suggest, how the changes will be also.. like folder,
> where you suggest to keep this...?
> > >
> > > Sure, here's my proposal:
> > >
> > > * Stack name: "BIGTOP"
> > >
> > > - The same name as the existing one [1]
> > > - Because it deploys the packages generated by Bigtop
> > > - The existing stack should be replaced with it, because
> that is
> > > based on Bigtop 0.8 and too old to use now
> > > - No concern about infringing others' trademark
> > >
> > > * Component/folder name: "bigtop-select"
> > >
> > > - Consistent naming convention with the existing tools
> such as
> > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > > - If it sounds too simple and a bit unclear, a more
> descriptive name
> > > might be an option, for example "bigtop-ambari-stack-selector"
> > >
> > > * Script name: "bigtop-select"
> > >
> > > - Consistent with the stack name
> > > - No concern about infringing others' trademark
> > >
> > > [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sOGC38xRa2H2AYhpz1XxwyiBwwYUfEw87soznjX9fmI%3D&reserved=0
> > > [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CKqWD99nsiBrKv3IZtZXInadLmVzatK3zsSQxWkbLX4%3D&reserved=0
> > >
> > > Kengo Seki <se...@apache.org>
> > >
> > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> > > <bb...@visa.com.invalid> wrote:
> > >>
> > >>> Technical decisions shouldn't be done on other places
> than public mailing lists,
> > >>> as described in the "Open Communications" section of [1]
> and [2].
> > >> > So we should conclude the discussion in this mailing
> list.
> > >> > (And with my poor English, I'm not so confident to catch
> up with your
> > >> > fluent talk ;)
> > >>
> > >> I believe , I knew the apache way which you mentioned. We
> are not going conclude anything which comes to bigtop other than this
> mailing list.
> > >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls. Hence asking let's
> have call so that we can brainstorm. Even after call, everything will be
> published what we discussed.
> > >>
> > >> I think, whiteboarding will help to catch up with you.
> > >>
> > >> You all the think "bigtop-select" will be best option
> right..? Can you suggest, how the changes will be also.. like folder, where
> you suggest to keep this...?
> > >>
> > >> And if the name represents the stack which we are going to
> deploy should fine I feel.. (if it's not BDP, may be
> OBDP:OpensourceBigDataPlatform.)
> > >>
> > >> @Viraj Jasani and others any thoughts..?
> > >>
> > >>
> > >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org>
> wrote:
> > >>
> > >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> > >>
> > >> Technical decisions shouldn't be done on other places
> than public mailing lists,
> > >> as described in the "Open Communications" section of
> [1] and [2].
> > >> So we should conclude the discussion in this mailing
> list.
> > >> (And with my poor English, I'm not so confident to
> catch up with your
> > >> fluent talk ;)
> > >>
> > >> > FYI. Even looks bigtop used some where also..
> > >>
> > >> Bigtop is ASF's trademark as you can see in the "Apache
> Bigtop®
> > >> software" section of [3].
> > >> So it doesn't have the risk of trademark infringement.
> > >>
> > >> [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VnSOJv998y6BR%2B%2B3gEwt3gC4ajiqxR3yxv%2FMuym14OI%3D&reserved=0
> > >> [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Z8lzba6TN%2FCgEXb%2FfBK6Fc6P%2FD74ICMmrGo8O8%2BvmsU%3D&reserved=0
> > >> [3]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678199768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CFeD4ngXC7I8E6v0GcV9LmD0KLlOfL3jsrWcwj%2BibWA%3D&reserved=0
> > >>
> > >> Kengo Seki <se...@apache.org>
> > >>
> > >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> > >> <bb...@visa.com.invalid> wrote:
> > >> >
> > >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> > >> >
> > >> > FYI. Even looks bigtop used some where[1] also..
> > >> > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=F0Fa4qQC1DwyNDUqBamzb7eCZSphpuxQ%2FqWkE10w%2F3o%3D&reserved=0(Microsoft_product)
> > >> >
> > >> >
> > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
> wrote:
> > >> >
> > >> > Thank you for your explanation, Brahma.
> > >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP"
> [1]) is supposed to be a
> > >> > trademark of Redoop, so they can name the script
> crh-select without
> > >> > problem.
> > >> > But regarding BDP for example, I can easily find
> products that have
> > >> > the same name [2][3][4] as you already mentioned,
> so I'd like to
> > >> > recommend bigtop-select for avoiding unnecessary
> trouble.
> > >> > Or, a single and more general word just like
> conf-select may be less
> > >> > troublesome than bdp. How about "stack-select",
> for example?
> > >> >
> > >> > [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dy6I2wH2aSIkQKa9fJX7nDbbUWjQ07aTvcdSZXCGCYM%3D&reserved=0
> > >> > [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sE%2Fb5kum9UIOQQ1NonfA0ZZk04cghtU%2BYIpvLf1mofo%3D&reserved=0
> > >> > [3]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ey61twpiXZXBJ10YFWhmBWV4w8KyQ4NadpM5itom83Q%3D&reserved=0
> > >> > [4]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=AzmiiA7TLiJmWR2M0iD%2BQJnS9XZrCU5t2K7KjipzvDg%3D&reserved=0
> > >> >
> > >> > Kengo Seki <se...@apache.org>
> > >> >
> > >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma
> Reddy <bb...@visa.com> wrote:
> > >> > >
> > >> > > >Do you mean that you're going to name the
> module (same as "component"
> > >> > > >in the Bigtop terminology, I think)
> bigtop-distro-select,
> > >> > > >and still the script in question
> bdp-select? If so, is there any
> > >> > > >reason that the script must be that name?
> > >> > > >(No offence, I just want to understand
> your thoughts and its
> > >> > > >background, and avoid the conflict or
> user's confusion with existing
> > >> > > >trademarks or products)
> > >> > >
> > >> > > Thanks @Kengo Seki for consolidating all the
> concerns. Name should represent the stack which includes all the components
> hence planning to have like bdp,bds...and this only one file like below[1]
> which has done redoop.
> > >> > >
> > >> > >
> > >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dNFPGfC2F9DUoKX3TPGwTiz4%2BQXacQ4FZzr3%2B6eHLRg%3D&reserved=0
> > >> > >
> > >> > >
> > >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
> sekikn@apache.org> wrote:
> > >> > >
> > >> > > The following concern Masatake mentioned
> before is an important point,
> > >> > > so I talked to Brahma for clarifying his
> intention on the ASF Slack
> > >> > > yesterday.
> > >> > >
> > >> > > > Multiple versions of the same package
> (deb/rpm) can not be installed at the same time.
> > >> > > > IIRC, HDP uses convention in which the
> product version is part of package name
> > >> > > > for addressing this.
> > >> > >
> > >> > > > I don't like to bring the awkward package
> name convention to Bigtop
> > >> > > > at least by default.
> > >> > >
> > >> > > He's planning to adopt the same mitigation
> as HDP for now, but he
> > >> > > doesn't intend to change the default
> package naming convention of
> > >> > > Bigtop,
> > >> > > but just add a new functionality to include
> an extra part into the
> > >> > > package name for avoiding conflict, which
> is disabled by default.
> > >> > >
> > >> > > And Brahma, let me confirm about the
> following reply:
> > >> > >
> > >> > > > Sure, we can have module name like
> bigtop-distro-select.
> > >> > >
> > >> > > Do you mean that you're going to name the
> module (same as "component"
> > >> > > in the Bigtop terminology, I think)
> bigtop-distro-select,
> > >> > > and still the script in question
> bdp-select? If so, is there any
> > >> > > reason that the script must be that name?
> > >> > > (No offence, I just want to understand your
> thoughts and its
> > >> > > background, and avoid the conflict or
> user's confusion with existing
> > >> > > trademarks or products)
> > >> > >
> > >> > > Kengo Seki <se...@apache.org>
> > >> > >
> > >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula,
> Brahma Reddy
> > >> > > <bb...@visa.com.invalid> wrote:
> > >> > > >
> > >> > > > > The name of stack based no Bigtop
> should be Bigtop.
> > >> > > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> > >> > > > > I will cast -1 if someone submit a
> patch to add a module with the name spoiling branding.
> > >> > > >
> > >> > > > Sure, we can have module name like
> bigtop-distro-select.
> > >> > > > Initially we'll do this separate branch.
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.co.jp> wrote:
> > >> > > >
> > >> > > > > I believe it's for project name.
> isn't it.?
> > >> > > >
> > >> > > > projects and products.
> > >> > > >
> > >> > > > > IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >> > > >
> > >> > > > The name of stack based no Bigtop
> should be Bigtop.
> > >> > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> > >> > > > I will cast -1 if someone submit a
> patch to add a module with the name spoiling branding.
> > >> > > >
> > >> > > >
> > >> > > > On 2022/07/06 11:44, Battula, Brahma
> Reddy wrote:
> > >> > > > >
> > >> > > > > I believe it's for project name.
> isn't it.?
> > >> > > > >
> > >> > > > >
> > >> > > > > On 06/07/22, 7:27 AM, "Masatake
> Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >> > > > >
> > >> > > > > > But As we are not releasing
> as enterprise should be fine I think. IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >> > > > >
> > >> > > > > Not fine.
> > >> > > > > We have a trademark policy.
> > >> > > > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=XQM8jgnE0tJRSDpjDELPXw1%2B%2Fsq0forEMVS15aYgWbg%3D&reserved=0
> > >> > > > >
> > >> > > > > On 2022/07/06 10:37, Battula,
> Brahma Reddy wrote:
> > >> > > > > >> Should we avoid
> unrecognized brand which may be trademark of someone?
> > >> > > > > >> ambari-select or
> bigtop-select should be enough.
> > >> > > > > >
> > >> > > > > > Not sure, where to confirm
> whether there is already trademark. When I googled found so many.
> > >> > > > > > But As we are not releasing
> as enterprise should be fine I think. IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >> > > > > > May be you can refer the
> initial proposal [2] where I mentioned some more names.
> (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > >> > > > > >
> > >> > > > > > Finally thanks a bunch for
> long healthy discussions on this. Mostly we all same page now.
> > >> > > > > >
> > >> > > > > > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GGtYy%2B6poKMJ62Cp9vrrjiou1YrciQ7ow0RFU1vTQRA%3D&reserved=0
> > >> > > > > >
> > >> > > > > > 2.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C579ee713d763478e698e08da8a1a08b6%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637974141678355536%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ucOrDSTO2EiSbVb67pmT3d7w4OBv%2BPpckx5KDdc8%2FWU%3D&reserved=0
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > On 06/07/22, 4:01 AM,
> "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >> > > > > >
> > >> > > > > > > We have still not
> officially finalized the new replacement name for
> > >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> > >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> > >> > > > > >
> > >> > > > > > Should we avoid
> unrecognized brand which may be trademark of someone?
> > >> > > > > > ambari-select or
> bigtop-select should be enough.
> > >> > > > > >
> > >> > > > > > On 2022/06/29 13:52,
> Viraj Jasani wrote:
> > >> > > > > > > Hi Ambari/Bigtop dev,
> > >> > > > > > >
> > >> > > > > > > As per the new
> roadmap of Apache Ambari, we would like to propose moving
> > >> > > > > > > certain scripts
> (previously known as hdp-select and conf-select) to Bigtop
> > >> > > > > > > so that their rpm
> installation could be managed independently.
> > >> > > > > > > These scripts are a
> basic necessity in the Ambari framework for the
> > >> > > > > > > installation of
> various Bigdata packages. The only major changes they would
> > >> > > > > > > receive is when we
> onboard new services and components to Ambari, else they
> > >> > > > > > > usually do not
> receive updates. In the past, we used to get hdp-select rpm
> > >> > > > > > > downloaded and
> installed from HDP repositories.
> > >> > > > > > >
> > >> > > > > > > We have still not
> officially finalized the new replacement name for
> > >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> > >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> > >> > > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > > >
> > >> > > >
> ---------------------------------------------------------------------
> > >> > > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > >> > > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> > >> > > >
> > >> > >
> > >> > >
> ---------------------------------------------------------------------
> > >> > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > >> > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> > >> > >
> > >> > >
> > >> >
> > >> >
> ---------------------------------------------------------------------
> > >> > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > >> > For additional commands, e-mail:
> dev-help@ambari.apache.org
> > >> >
> > >> >
> > >>
> > >>
> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > >> For additional commands, e-mail:
> dev-help@ambari.apache.org
> > >>
> > >>
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Viraj Jasani <vj...@apache.org>.
Masatake, Brahma,
Hopefully I should be able to create Jira and PR in Bigtop. Will let you
know once ready for review. Thanks
On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <iw...@oss.nttdata.com>
wrote:
> Please file a JIRA and submit a pull request if you want to show the code
> and get feedback.
> There is nothing I want to discuss off the record.
>
> On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get
> the final conclusion on this..?
> >
> > Please let me know your availability, Can have one call to discuss on
> this..
> >
> >
> > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
> wrote:
> >
> > > -1 on development in branch.
> > > It is not worth for maintaining the branch if the modules is
> so small
> > > and barely updated as explained here.
> > > It should not conflict to existing code.
> > > I feel I must check the code before check-in based on this
> thread.
> >
> >
> > Sure, Viraj or me can show the code to you.
> >
> > Can we've call on this Friday/Thrusday if that works..?
> >
> >
> > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.com> wrote:
> >
> > > Sure, we can havemodule name like bigtop-distro-select.
> > > Initially we'll do this separate branch.
> >
> > -1 on development in branch.
> > It is not worth for maintaining the branch if the modules is so
> small
> > and barely updated as explained here.
> > It should not conflict to existing code.
> > I feel I must check the code before check-in based on this
> thread.
> >
> > Masatake Iwasaki
> >
> > On 2022/07/11 8:23, Kengo Seki wrote:
> > >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls.
> > >
> > > Oh, I interpreted your words "conclude" and "finalize" as you
> were
> > > going to make a final decision. Brainstorming is welcome, of
> course.
> > > (But I'm not so sure if all people concerned could join, due
> to time
> > > difference and their schedule, etc.)
> > >
> > >> Can you suggest, how the changes will be also.. like folder,
> where you suggest to keep this...?
> > >
> > > Sure, here's my proposal:
> > >
> > > * Stack name: "BIGTOP"
> > >
> > > - The same name as the existing one [1]
> > > - Because it deploys the packages generated by Bigtop
> > > - The existing stack should be replaced with it, because
> that is
> > > based on Bigtop 0.8 and too old to use now
> > > - No concern about infringing others' trademark
> > >
> > > * Component/folder name: "bigtop-select"
> > >
> > > - Consistent naming convention with the existing tools
> such as
> > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > > - If it sounds too simple and a bit unclear, a more
> descriptive name
> > > might be an option, for example "bigtop-ambari-stack-selector"
> > >
> > > * Script name: "bigtop-select"
> > >
> > > - Consistent with the stack name
> > > - No concern about infringing others' trademark
> > >
> > > [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=l6OMfWaJl4yKV6zjSYiMQXYy1HBuJhs5nej0Co9K3FA%3D&reserved=0
> > > [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5nM8IrpP067odUjmxS%2Bv8xxDchCLGVOplmA%2Fo8Iq%2BOg%3D&reserved=0
> > >
> > > Kengo Seki <se...@apache.org>
> > >
> > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> > > <bb...@visa.com.invalid> wrote:
> > >>
> > >>> Technical decisions shouldn't be done on other places
> than public mailing lists,
> > >>> as described in the "Open Communications" section of [1]
> and [2].
> > >> > So we should conclude the discussion in this mailing
> list.
> > >> > (And with my poor English, I'm not so confident to catch
> up with your
> > >> > fluent talk ;)
> > >>
> > >> I believe , I knew the apache way which you mentioned. We
> are not going conclude anything which comes to bigtop other than this
> mailing list.
> > >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls. Hence asking let's
> have call so that we can brainstorm. Even after call, everything will be
> published what we discussed.
> > >>
> > >> I think, whiteboarding will help to catch up with you.
> > >>
> > >> You all the think "bigtop-select" will be best option
> right..? Can you suggest, how the changes will be also.. like folder, where
> you suggest to keep this...?
> > >>
> > >> And if the name represents the stack which we are going to
> deploy should fine I feel.. (if it's not BDP, may be
> OBDP:OpensourceBigDataPlatform.)
> > >>
> > >> @Viraj Jasani and others any thoughts..?
> > >>
> > >>
> > >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org>
> wrote:
> > >>
> > >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> > >>
> > >> Technical decisions shouldn't be done on other places
> than public mailing lists,
> > >> as described in the "Open Communications" section of
> [1] and [2].
> > >> So we should conclude the discussion in this mailing
> list.
> > >> (And with my poor English, I'm not so confident to
> catch up with your
> > >> fluent talk ;)
> > >>
> > >> > FYI. Even looks bigtop used some where also..
> > >>
> > >> Bigtop is ASF's trademark as you can see in the "Apache
> Bigtop®
> > >> software" section of [3].
> > >> So it doesn't have the risk of trademark infringement.
> > >>
> > >> [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zaDwUjNvgU0eP5NY7wPq2BISd%2FiLs7dp92fwFUfwFCI%3D&reserved=0
> > >> [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DlCOz5ajX%2FziXmx7ZeD5xa0WzX06Akm3pYuMs5KX9h4%3D&reserved=0
> > >> [3]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KVc1YjBSUzAFexYTQ2IoiLOr0vkm85NBqI8WZC7g67s%3D&reserved=0
> > >>
> > >> Kengo Seki <se...@apache.org>
> > >>
> > >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> > >> <bb...@visa.com.invalid> wrote:
> > >> >
> > >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> > >> >
> > >> > FYI. Even looks bigtop used some where[1] also..
> > >> > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BPQQCUDhl%2BHGNS%2F1aLtS38Qah9zDs06qd2y%2B%2BUE%2FBKk%3D&reserved=0(Microsoft_product)
> > >> >
> > >> >
> > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
> wrote:
> > >> >
> > >> > Thank you for your explanation, Brahma.
> > >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP"
> [1]) is supposed to be a
> > >> > trademark of Redoop, so they can name the script
> crh-select without
> > >> > problem.
> > >> > But regarding BDP for example, I can easily find
> products that have
> > >> > the same name [2][3][4] as you already mentioned,
> so I'd like to
> > >> > recommend bigtop-select for avoiding unnecessary
> trouble.
> > >> > Or, a single and more general word just like
> conf-select may be less
> > >> > troublesome than bdp. How about "stack-select",
> for example?
> > >> >
> > >> > [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CM8y%2Bom6hpEl98x8G2ve5J98W%2FVeEkSPnwgFiYd2C98%3D&reserved=0
> > >> > [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=g2ng5E0%2BTb6N52isJ7guO10C3zTGA86dSafV9h0LXbU%3D&reserved=0
> > >> > [3]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qrU%2F4FJ5EjqoD0opzxVL1wM%2FTEM%2B%2B8MoqkZHHZNA%2Fk0%3D&reserved=0
> > >> > [4]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KfEGcZwpdvVZUaW1XsaUMGqVYcZyysmZhjl%2BR6Iq2wI%3D&reserved=0
> > >> >
> > >> > Kengo Seki <se...@apache.org>
> > >> >
> > >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma
> Reddy <bb...@visa.com> wrote:
> > >> > >
> > >> > > >Do you mean that you're going to name the
> module (same as "component"
> > >> > > >in the Bigtop terminology, I think)
> bigtop-distro-select,
> > >> > > >and still the script in question
> bdp-select? If so, is there any
> > >> > > >reason that the script must be that name?
> > >> > > >(No offence, I just want to understand
> your thoughts and its
> > >> > > >background, and avoid the conflict or
> user's confusion with existing
> > >> > > >trademarks or products)
> > >> > >
> > >> > > Thanks @Kengo Seki for consolidating all the
> concerns. Name should represent the stack which includes all the components
> hence planning to have like bdp,bds...and this only one file like below[1]
> which has done redoop.
> > >> > >
> > >> > >
> > >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=e4oze4857dGtVIq14Ow8yzFnDhW9b2OG85sJMWfXbi4%3D&reserved=0
> > >> > >
> > >> > >
> > >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
> sekikn@apache.org> wrote:
> > >> > >
> > >> > > The following concern Masatake mentioned
> before is an important point,
> > >> > > so I talked to Brahma for clarifying his
> intention on the ASF Slack
> > >> > > yesterday.
> > >> > >
> > >> > > > Multiple versions of the same package
> (deb/rpm) can not be installed at the same time.
> > >> > > > IIRC, HDP uses convention in which the
> product version is part of package name
> > >> > > > for addressing this.
> > >> > >
> > >> > > > I don't like to bring the awkward package
> name convention to Bigtop
> > >> > > > at least by default.
> > >> > >
> > >> > > He's planning to adopt the same mitigation
> as HDP for now, but he
> > >> > > doesn't intend to change the default
> package naming convention of
> > >> > > Bigtop,
> > >> > > but just add a new functionality to include
> an extra part into the
> > >> > > package name for avoiding conflict, which
> is disabled by default.
> > >> > >
> > >> > > And Brahma, let me confirm about the
> following reply:
> > >> > >
> > >> > > > Sure, we can have module name like
> bigtop-distro-select.
> > >> > >
> > >> > > Do you mean that you're going to name the
> module (same as "component"
> > >> > > in the Bigtop terminology, I think)
> bigtop-distro-select,
> > >> > > and still the script in question
> bdp-select? If so, is there any
> > >> > > reason that the script must be that name?
> > >> > > (No offence, I just want to understand your
> thoughts and its
> > >> > > background, and avoid the conflict or
> user's confusion with existing
> > >> > > trademarks or products)
> > >> > >
> > >> > > Kengo Seki <se...@apache.org>
> > >> > >
> > >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula,
> Brahma Reddy
> > >> > > <bb...@visa.com.invalid> wrote:
> > >> > > >
> > >> > > > > The name of stack based no Bigtop
> should be Bigtop.
> > >> > > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> > >> > > > > I will cast -1 if someone submit a
> patch to add a module with the name spoiling branding.
> > >> > > >
> > >> > > > Sure, we can have module name like
> bigtop-distro-select.
> > >> > > > Initially we'll do this separate branch.
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.co.jp> wrote:
> > >> > > >
> > >> > > > > I believe it's for project name.
> isn't it.?
> > >> > > >
> > >> > > > projects and products.
> > >> > > >
> > >> > > > > IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >> > > >
> > >> > > > The name of stack based no Bigtop
> should be Bigtop.
> > >> > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> > >> > > > I will cast -1 if someone submit a
> patch to add a module with the name spoiling branding.
> > >> > > >
> > >> > > >
> > >> > > > On 2022/07/06 11:44, Battula, Brahma
> Reddy wrote:
> > >> > > > >
> > >> > > > > I believe it's for project name.
> isn't it.?
> > >> > > > >
> > >> > > > >
> > >> > > > > On 06/07/22, 7:27 AM, "Masatake
> Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >> > > > >
> > >> > > > > > But As we are not releasing
> as enterprise should be fine I think. IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >> > > > >
> > >> > > > > Not fine.
> > >> > > > > We have a trademark policy.
> > >> > > > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Aj5p2h78PdIXFHsJi7Q6ouR5eG33vf1LA2wdGnlaF%2FQ%3D&reserved=0
> > >> > > > >
> > >> > > > > On 2022/07/06 10:37, Battula,
> Brahma Reddy wrote:
> > >> > > > > >> Should we avoid
> unrecognized brand which may be trademark of someone?
> > >> > > > > >> ambari-select or
> bigtop-select should be enough.
> > >> > > > > >
> > >> > > > > > Not sure, where to confirm
> whether there is already trademark. When I googled found so many.
> > >> > > > > > But As we are not releasing
> as enterprise should be fine I think. IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >> > > > > > May be you can refer the
> initial proposal [2] where I mentioned some more names.
> (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > >> > > > > >
> > >> > > > > > Finally thanks a bunch for
> long healthy discussions on this. Mostly we all same page now.
> > >> > > > > >
> > >> > > > > > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=p1br7DcndgZq6Z5m4CvTSZOSFhkKtie%2BeqXERXuY58Q%3D&reserved=0
> > >> > > > > >
> > >> > > > > > 2.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EON1ukunh1oyFb5HID57FuOv9DjIBteeoCYuQfx34Gg%3D&reserved=0
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > On 06/07/22, 4:01 AM,
> "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >> > > > > >
> > >> > > > > > > We have still not
> officially finalized the new replacement name for
> > >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> > >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> > >> > > > > >
> > >> > > > > > Should we avoid
> unrecognized brand which may be trademark of someone?
> > >> > > > > > ambari-select or
> bigtop-select should be enough.
> > >> > > > > >
> > >> > > > > > On 2022/06/29 13:52,
> Viraj Jasani wrote:
> > >> > > > > > > Hi Ambari/Bigtop dev,
> > >> > > > > > >
> > >> > > > > > > As per the new
> roadmap of Apache Ambari, we would like to propose moving
> > >> > > > > > > certain scripts
> (previously known as hdp-select and conf-select) to Bigtop
> > >> > > > > > > so that their rpm
> installation could be managed independently.
> > >> > > > > > > These scripts are a
> basic necessity in the Ambari framework for the
> > >> > > > > > > installation of
> various Bigdata packages. The only major changes they would
> > >> > > > > > > receive is when we
> onboard new services and components to Ambari, else they
> > >> > > > > > > usually do not
> receive updates. In the past, we used to get hdp-select rpm
> > >> > > > > > > downloaded and
> installed from HDP repositories.
> > >> > > > > > >
> > >> > > > > > > We have still not
> officially finalized the new replacement name for
> > >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> > >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> > >> > > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > > >
> > >> > > >
> ---------------------------------------------------------------------
> > >> > > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > >> > > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> > >> > > >
> > >> > >
> > >> > >
> ---------------------------------------------------------------------
> > >> > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > >> > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> > >> > >
> > >> > >
> > >> >
> > >> >
> ---------------------------------------------------------------------
> > >> > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > >> > For additional commands, e-mail:
> dev-help@ambari.apache.org
> > >> >
> > >> >
> > >>
> > >>
> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > >> For additional commands, e-mail:
> dev-help@ambari.apache.org
> > >>
> > >>
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
> >
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Viraj Jasani <vj...@apache.org>.
Masatake, Brahma,
Hopefully I should be able to create Jira and PR in Bigtop. Will let you
know once ready for review. Thanks
On Tue, Aug 23, 2022 at 9:22 AM Masatake Iwasaki <iw...@oss.nttdata.com>
wrote:
> Please file a JIRA and submit a pull request if you want to show the code
> and get feedback.
> There is nothing I want to discuss off the record.
>
> On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> > @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get
> the final conclusion on this..?
> >
> > Please let me know your availability, Can have one call to discuss on
> this..
> >
> >
> > On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID>
> wrote:
> >
> > > -1 on development in branch.
> > > It is not worth for maintaining the branch if the modules is
> so small
> > > and barely updated as explained here.
> > > It should not conflict to existing code.
> > > I feel I must check the code before check-in based on this
> thread.
> >
> >
> > Sure, Viraj or me can show the code to you.
> >
> > Can we've call on this Friday/Thrusday if that works..?
> >
> >
> > On 11/07/22, 11:54 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.com> wrote:
> >
> > > Sure, we can havemodule name like bigtop-distro-select.
> > > Initially we'll do this separate branch.
> >
> > -1 on development in branch.
> > It is not worth for maintaining the branch if the modules is so
> small
> > and barely updated as explained here.
> > It should not conflict to existing code.
> > I feel I must check the code before check-in based on this
> thread.
> >
> > Masatake Iwasaki
> >
> > On 2022/07/11 8:23, Kengo Seki wrote:
> > >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls.
> > >
> > > Oh, I interpreted your words "conclude" and "finalize" as you
> were
> > > going to make a final decision. Brainstorming is welcome, of
> course.
> > > (But I'm not so sure if all people concerned could join, due
> to time
> > > difference and their schedule, etc.)
> > >
> > >> Can you suggest, how the changes will be also.. like folder,
> where you suggest to keep this...?
> > >
> > > Sure, here's my proposal:
> > >
> > > * Stack name: "BIGTOP"
> > >
> > > - The same name as the existing one [1]
> > > - Because it deploys the packages generated by Bigtop
> > > - The existing stack should be replaced with it, because
> that is
> > > based on Bigtop 0.8 and too old to use now
> > > - No concern about infringing others' trademark
> > >
> > > * Component/folder name: "bigtop-select"
> > >
> > > - Consistent naming convention with the existing tools
> such as
> > > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > > - If it sounds too simple and a bit unclear, a more
> descriptive name
> > > might be an option, for example "bigtop-ambari-stack-selector"
> > >
> > > * Script name: "bigtop-select"
> > >
> > > - Consistent with the stack name
> > > - No concern about infringing others' trademark
> > >
> > > [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=l6OMfWaJl4yKV6zjSYiMQXYy1HBuJhs5nej0Co9K3FA%3D&reserved=0
> > > [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5nM8IrpP067odUjmxS%2Bv8xxDchCLGVOplmA%2Fo8Iq%2BOg%3D&reserved=0
> > >
> > > Kengo Seki <se...@apache.org>
> > >
> > > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> > > <bb...@visa.com.invalid> wrote:
> > >>
> > >>> Technical decisions shouldn't be done on other places
> than public mailing lists,
> > >>> as described in the "Open Communications" section of [1]
> and [2].
> > >> > So we should conclude the discussion in this mailing
> list.
> > >> > (And with my poor English, I'm not so confident to catch
> up with your
> > >> > fluent talk ;)
> > >>
> > >> I believe , I knew the apache way which you mentioned. We
> are not going conclude anything which comes to bigtop other than this
> mailing list.
> > >> As there are different opinions on this and took long time,
> just to brainstorm all the possibilities and pitfalls. Hence asking let's
> have call so that we can brainstorm. Even after call, everything will be
> published what we discussed.
> > >>
> > >> I think, whiteboarding will help to catch up with you.
> > >>
> > >> You all the think "bigtop-select" will be best option
> right..? Can you suggest, how the changes will be also.. like folder, where
> you suggest to keep this...?
> > >>
> > >> And if the name represents the stack which we are going to
> deploy should fine I feel.. (if it's not BDP, may be
> OBDP:OpensourceBigDataPlatform.)
> > >>
> > >> @Viraj Jasani and others any thoughts..?
> > >>
> > >>
> > >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org>
> wrote:
> > >>
> > >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> > >>
> > >> Technical decisions shouldn't be done on other places
> than public mailing lists,
> > >> as described in the "Open Communications" section of
> [1] and [2].
> > >> So we should conclude the discussion in this mailing
> list.
> > >> (And with my poor English, I'm not so confident to
> catch up with your
> > >> fluent talk ;)
> > >>
> > >> > FYI. Even looks bigtop used some where also..
> > >>
> > >> Bigtop is ASF's trademark as you can see in the "Apache
> Bigtop®
> > >> software" section of [3].
> > >> So it doesn't have the risk of trademark infringement.
> > >>
> > >> [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zaDwUjNvgU0eP5NY7wPq2BISd%2FiLs7dp92fwFUfwFCI%3D&reserved=0
> > >> [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DlCOz5ajX%2FziXmx7ZeD5xa0WzX06Akm3pYuMs5KX9h4%3D&reserved=0
> > >> [3]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KVc1YjBSUzAFexYTQ2IoiLOr0vkm85NBqI8WZC7g67s%3D&reserved=0
> > >>
> > >> Kengo Seki <se...@apache.org>
> > >>
> > >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> > >> <bb...@visa.com.invalid> wrote:
> > >> >
> > >> > Looks we had so much discussed here, Let's try to
> conclude. Can we've one call on this and finalize this..?
> > >> >
> > >> > FYI. Even looks bigtop used some where[1] also..
> > >> > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BPQQCUDhl%2BHGNS%2F1aLtS38Qah9zDs06qd2y%2B%2BUE%2FBKk%3D&reserved=0(Microsoft_product)
> > >> >
> > >> >
> > >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org>
> wrote:
> > >> >
> > >> > Thank you for your explanation, Brahma.
> > >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP"
> [1]) is supposed to be a
> > >> > trademark of Redoop, so they can name the script
> crh-select without
> > >> > problem.
> > >> > But regarding BDP for example, I can easily find
> products that have
> > >> > the same name [2][3][4] as you already mentioned,
> so I'd like to
> > >> > recommend bigtop-select for avoiding unnecessary
> trouble.
> > >> > Or, a single and more general word just like
> conf-select may be less
> > >> > troublesome than bdp. How about "stack-select",
> for example?
> > >> >
> > >> > [1]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CM8y%2Bom6hpEl98x8G2ve5J98W%2FVeEkSPnwgFiYd2C98%3D&reserved=0
> > >> > [2]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=g2ng5E0%2BTb6N52isJ7guO10C3zTGA86dSafV9h0LXbU%3D&reserved=0
> > >> > [3]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qrU%2F4FJ5EjqoD0opzxVL1wM%2FTEM%2B%2B8MoqkZHHZNA%2Fk0%3D&reserved=0
> > >> > [4]:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KfEGcZwpdvVZUaW1XsaUMGqVYcZyysmZhjl%2BR6Iq2wI%3D&reserved=0
> > >> >
> > >> > Kengo Seki <se...@apache.org>
> > >> >
> > >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma
> Reddy <bb...@visa.com> wrote:
> > >> > >
> > >> > > >Do you mean that you're going to name the
> module (same as "component"
> > >> > > >in the Bigtop terminology, I think)
> bigtop-distro-select,
> > >> > > >and still the script in question
> bdp-select? If so, is there any
> > >> > > >reason that the script must be that name?
> > >> > > >(No offence, I just want to understand
> your thoughts and its
> > >> > > >background, and avoid the conflict or
> user's confusion with existing
> > >> > > >trademarks or products)
> > >> > >
> > >> > > Thanks @Kengo Seki for consolidating all the
> concerns. Name should represent the stack which includes all the components
> hence planning to have like bdp,bds...and this only one file like below[1]
> which has done redoop.
> > >> > >
> > >> > >
> > >> > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=e4oze4857dGtVIq14Ow8yzFnDhW9b2OG85sJMWfXbi4%3D&reserved=0
> > >> > >
> > >> > >
> > >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <
> sekikn@apache.org> wrote:
> > >> > >
> > >> > > The following concern Masatake mentioned
> before is an important point,
> > >> > > so I talked to Brahma for clarifying his
> intention on the ASF Slack
> > >> > > yesterday.
> > >> > >
> > >> > > > Multiple versions of the same package
> (deb/rpm) can not be installed at the same time.
> > >> > > > IIRC, HDP uses convention in which the
> product version is part of package name
> > >> > > > for addressing this.
> > >> > >
> > >> > > > I don't like to bring the awkward package
> name convention to Bigtop
> > >> > > > at least by default.
> > >> > >
> > >> > > He's planning to adopt the same mitigation
> as HDP for now, but he
> > >> > > doesn't intend to change the default
> package naming convention of
> > >> > > Bigtop,
> > >> > > but just add a new functionality to include
> an extra part into the
> > >> > > package name for avoiding conflict, which
> is disabled by default.
> > >> > >
> > >> > > And Brahma, let me confirm about the
> following reply:
> > >> > >
> > >> > > > Sure, we can have module name like
> bigtop-distro-select.
> > >> > >
> > >> > > Do you mean that you're going to name the
> module (same as "component"
> > >> > > in the Bigtop terminology, I think)
> bigtop-distro-select,
> > >> > > and still the script in question
> bdp-select? If so, is there any
> > >> > > reason that the script must be that name?
> > >> > > (No offence, I just want to understand your
> thoughts and its
> > >> > > background, and avoid the conflict or
> user's confusion with existing
> > >> > > trademarks or products)
> > >> > >
> > >> > > Kengo Seki <se...@apache.org>
> > >> > >
> > >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula,
> Brahma Reddy
> > >> > > <bb...@visa.com.invalid> wrote:
> > >> > > >
> > >> > > > > The name of stack based no Bigtop
> should be Bigtop.
> > >> > > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> > >> > > > > I will cast -1 if someone submit a
> patch to add a module with the name spoiling branding.
> > >> > > >
> > >> > > > Sure, we can have module name like
> bigtop-distro-select.
> > >> > > > Initially we'll do this separate branch.
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.co.jp> wrote:
> > >> > > >
> > >> > > > > I believe it's for project name.
> isn't it.?
> > >> > > >
> > >> > > > projects and products.
> > >> > > >
> > >> > > > > IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >> > > >
> > >> > > > The name of stack based no Bigtop
> should be Bigtop.
> > >> > > > If you can not accept the name like
> bigtop-*, the work should done outside of Bigtop.
> > >> > > > I will cast -1 if someone submit a
> patch to add a module with the name spoiling branding.
> > >> > > >
> > >> > > >
> > >> > > > On 2022/07/06 11:44, Battula, Brahma
> Reddy wrote:
> > >> > > > >
> > >> > > > > I believe it's for project name.
> isn't it.?
> > >> > > > >
> > >> > > > >
> > >> > > > > On 06/07/22, 7:27 AM, "Masatake
> Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >> > > > >
> > >> > > > > > But As we are not releasing
> as enterprise should be fine I think. IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >> > > > >
> > >> > > > > Not fine.
> > >> > > > > We have a trademark policy.
> > >> > > > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Aj5p2h78PdIXFHsJi7Q6ouR5eG33vf1LA2wdGnlaF%2FQ%3D&reserved=0
> > >> > > > >
> > >> > > > > On 2022/07/06 10:37, Battula,
> Brahma Reddy wrote:
> > >> > > > > >> Should we avoid
> unrecognized brand which may be trademark of someone?
> > >> > > > > >> ambari-select or
> bigtop-select should be enough.
> > >> > > > > >
> > >> > > > > > Not sure, where to confirm
> whether there is already trademark. When I googled found so many.
> > >> > > > > > But As we are not releasing
> as enterprise should be fine I think. IMO, We need to create folders and
> refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >> > > > > > May be you can refer the
> initial proposal [2] where I mentioned some more names.
> (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > >> > > > > >
> > >> > > > > > Finally thanks a bunch for
> long healthy discussions on this. Mostly we all same page now.
> > >> > > > > >
> > >> > > > > > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=p1br7DcndgZq6Z5m4CvTSZOSFhkKtie%2BeqXERXuY58Q%3D&reserved=0
> > >> > > > > >
> > >> > > > > > 2.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EON1ukunh1oyFb5HID57FuOv9DjIBteeoCYuQfx34Gg%3D&reserved=0
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > On 06/07/22, 4:01 AM,
> "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >> > > > > >
> > >> > > > > > > We have still not
> officially finalized the new replacement name for
> > >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> > >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> > >> > > > > >
> > >> > > > > > Should we avoid
> unrecognized brand which may be trademark of someone?
> > >> > > > > > ambari-select or
> bigtop-select should be enough.
> > >> > > > > >
> > >> > > > > > On 2022/06/29 13:52,
> Viraj Jasani wrote:
> > >> > > > > > > Hi Ambari/Bigtop dev,
> > >> > > > > > >
> > >> > > > > > > As per the new
> roadmap of Apache Ambari, we would like to propose moving
> > >> > > > > > > certain scripts
> (previously known as hdp-select and conf-select) to Bigtop
> > >> > > > > > > so that their rpm
> installation could be managed independently.
> > >> > > > > > > These scripts are a
> basic necessity in the Ambari framework for the
> > >> > > > > > > installation of
> various Bigdata packages. The only major changes they would
> > >> > > > > > > receive is when we
> onboard new services and components to Ambari, else they
> > >> > > > > > > usually do not
> receive updates. In the past, we used to get hdp-select rpm
> > >> > > > > > > downloaded and
> installed from HDP repositories.
> > >> > > > > > >
> > >> > > > > > > We have still not
> officially finalized the new replacement name for
> > >> > > > > > > hdp-select, it would
> likely be bdp-select (bdp: BigData Platform). However,
> > >> > > > > > > the purpose of
> bdp-select and conf-select remains the same.
> > >> > > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > > >
> > >> > > >
> ---------------------------------------------------------------------
> > >> > > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > >> > > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> > >> > > >
> > >> > >
> > >> > >
> ---------------------------------------------------------------------
> > >> > > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > >> > > For additional commands, e-mail:
> dev-help@ambari.apache.org
> > >> > >
> > >> > >
> > >> >
> > >> >
> ---------------------------------------------------------------------
> > >> > To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > >> > For additional commands, e-mail:
> dev-help@ambari.apache.org
> > >> >
> > >> >
> > >>
> > >>
> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail:
> dev-unsubscribe@ambari.apache.org
> > >> For additional commands, e-mail:
> dev-help@ambari.apache.org
> > >>
> > >>
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
> >
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.com>.
Please file a JIRA and submit a pull request if you want to show the code and get feedback.
There is nothing I want to discuss off the record.
On 2022/08/23 18:48, Battula, Brahma Reddy wrote:
> @Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get the final conclusion on this..?
>
> Please let me know your availability, Can have one call to discuss on this..
>
>
> On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID> wrote:
>
> > -1 on development in branch.
> > It is not worth for maintaining the branch if the modules is so small
> > and barely updated as explained here.
> > It should not conflict to existing code.
> > I feel I must check the code before check-in based on this thread.
>
>
> Sure, Viraj or me can show the code to you.
>
> Can we've call on this Friday/Thrusday if that works..?
>
>
> On 11/07/22, 11:54 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com> wrote:
>
> > Sure, we can havemodule name like bigtop-distro-select.
> > Initially we'll do this separate branch.
>
> -1 on development in branch.
> It is not worth for maintaining the branch if the modules is so small
> and barely updated as explained here.
> It should not conflict to existing code.
> I feel I must check the code before check-in based on this thread.
>
> Masatake Iwasaki
>
> On 2022/07/11 8:23, Kengo Seki wrote:
> >> As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls.
> >
> > Oh, I interpreted your words "conclude" and "finalize" as you were
> > going to make a final decision. Brainstorming is welcome, of course.
> > (But I'm not so sure if all people concerned could join, due to time
> > difference and their schedule, etc.)
> >
> >> Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
> >
> > Sure, here's my proposal:
> >
> > * Stack name: "BIGTOP"
> >
> > - The same name as the existing one [1]
> > - Because it deploys the packages generated by Bigtop
> > - The existing stack should be replaced with it, because that is
> > based on Bigtop 0.8 and too old to use now
> > - No concern about infringing others' trademark
> >
> > * Component/folder name: "bigtop-select"
> >
> > - Consistent naming convention with the existing tools such as
> > "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> > - If it sounds too simple and a bit unclear, a more descriptive name
> > might be an option, for example "bigtop-ambari-stack-selector"
> >
> > * Script name: "bigtop-select"
> >
> > - Consistent with the stack name
> > - No concern about infringing others' trademark
> >
> > [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=l6OMfWaJl4yKV6zjSYiMQXYy1HBuJhs5nej0Co9K3FA%3D&reserved=0
> > [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5nM8IrpP067odUjmxS%2Bv8xxDchCLGVOplmA%2Fo8Iq%2BOg%3D&reserved=0
> >
> > Kengo Seki <se...@apache.org>
> >
> > On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> > <bb...@visa.com.invalid> wrote:
> >>
> >>> Technical decisions shouldn't be done on other places than public mailing lists,
> >>> as described in the "Open Communications" section of [1] and [2].
> >> > So we should conclude the discussion in this mailing list.
> >> > (And with my poor English, I'm not so confident to catch up with your
> >> > fluent talk ;)
> >>
> >> I believe , I knew the apache way which you mentioned. We are not going conclude anything which comes to bigtop other than this mailing list.
> >> As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls. Hence asking let's have call so that we can brainstorm. Even after call, everything will be published what we discussed.
> >>
> >> I think, whiteboarding will help to catch up with you.
> >>
> >> You all the think "bigtop-select" will be best option right..? Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
> >>
> >> And if the name represents the stack which we are going to deploy should fine I feel.. (if it's not BDP, may be OBDP:OpensourceBigDataPlatform.)
> >>
> >> @Viraj Jasani and others any thoughts..?
> >>
> >>
> >> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org> wrote:
> >>
> >> > Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
> >>
> >> Technical decisions shouldn't be done on other places than public mailing lists,
> >> as described in the "Open Communications" section of [1] and [2].
> >> So we should conclude the discussion in this mailing list.
> >> (And with my poor English, I'm not so confident to catch up with your
> >> fluent talk ;)
> >>
> >> > FYI. Even looks bigtop used some where also..
> >>
> >> Bigtop is ASF's trademark as you can see in the "Apache Bigtop®
> >> software" section of [3].
> >> So it doesn't have the risk of trademark infringement.
> >>
> >> [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zaDwUjNvgU0eP5NY7wPq2BISd%2FiLs7dp92fwFUfwFCI%3D&reserved=0
> >> [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DlCOz5ajX%2FziXmx7ZeD5xa0WzX06Akm3pYuMs5KX9h4%3D&reserved=0
> >> [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KVc1YjBSUzAFexYTQ2IoiLOr0vkm85NBqI8WZC7g67s%3D&reserved=0
> >>
> >> Kengo Seki <se...@apache.org>
> >>
> >> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> >> <bb...@visa.com.invalid> wrote:
> >> >
> >> > Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
> >> >
> >> > FYI. Even looks bigtop used some where[1] also..
> >> > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BPQQCUDhl%2BHGNS%2F1aLtS38Qah9zDs06qd2y%2B%2BUE%2FBKk%3D&reserved=0(Microsoft_product)
> >> >
> >> >
> >> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org> wrote:
> >> >
> >> > Thank you for your explanation, Brahma.
> >> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
> >> > trademark of Redoop, so they can name the script crh-select without
> >> > problem.
> >> > But regarding BDP for example, I can easily find products that have
> >> > the same name [2][3][4] as you already mentioned, so I'd like to
> >> > recommend bigtop-select for avoiding unnecessary trouble.
> >> > Or, a single and more general word just like conf-select may be less
> >> > troublesome than bdp. How about "stack-select", for example?
> >> >
> >> > [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CM8y%2Bom6hpEl98x8G2ve5J98W%2FVeEkSPnwgFiYd2C98%3D&reserved=0
> >> > [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=g2ng5E0%2BTb6N52isJ7guO10C3zTGA86dSafV9h0LXbU%3D&reserved=0
> >> > [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qrU%2F4FJ5EjqoD0opzxVL1wM%2FTEM%2B%2B8MoqkZHHZNA%2Fk0%3D&reserved=0
> >> > [4]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KfEGcZwpdvVZUaW1XsaUMGqVYcZyysmZhjl%2BR6Iq2wI%3D&reserved=0
> >> >
> >> > Kengo Seki <se...@apache.org>
> >> >
> >> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com> wrote:
> >> > >
> >> > > >Do you mean that you're going to name the module (same as "component"
> >> > > >in the Bigtop terminology, I think) bigtop-distro-select,
> >> > > >and still the script in question bdp-select? If so, is there any
> >> > > >reason that the script must be that name?
> >> > > >(No offence, I just want to understand your thoughts and its
> >> > > >background, and avoid the conflict or user's confusion with existing
> >> > > >trademarks or products)
> >> > >
> >> > > Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
> >> > >
> >> > >
> >> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=e4oze4857dGtVIq14Ow8yzFnDhW9b2OG85sJMWfXbi4%3D&reserved=0
> >> > >
> >> > >
> >> > > On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
> >> > >
> >> > > The following concern Masatake mentioned before is an important point,
> >> > > so I talked to Brahma for clarifying his intention on the ASF Slack
> >> > > yesterday.
> >> > >
> >> > > > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> >> > > > IIRC, HDP uses convention in which the product version is part of package name
> >> > > > for addressing this.
> >> > >
> >> > > > I don't like to bring the awkward package name convention to Bigtop
> >> > > > at least by default.
> >> > >
> >> > > He's planning to adopt the same mitigation as HDP for now, but he
> >> > > doesn't intend to change the default package naming convention of
> >> > > Bigtop,
> >> > > but just add a new functionality to include an extra part into the
> >> > > package name for avoiding conflict, which is disabled by default.
> >> > >
> >> > > And Brahma, let me confirm about the following reply:
> >> > >
> >> > > > Sure, we can have module name like bigtop-distro-select.
> >> > >
> >> > > Do you mean that you're going to name the module (same as "component"
> >> > > in the Bigtop terminology, I think) bigtop-distro-select,
> >> > > and still the script in question bdp-select? If so, is there any
> >> > > reason that the script must be that name?
> >> > > (No offence, I just want to understand your thoughts and its
> >> > > background, and avoid the conflict or user's confusion with existing
> >> > > trademarks or products)
> >> > >
> >> > > Kengo Seki <se...@apache.org>
> >> > >
> >> > > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
> >> > > <bb...@visa.com.invalid> wrote:
> >> > > >
> >> > > > > The name of stack based no Bigtop should be Bigtop.
> >> > > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> >> > > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> >> > > >
> >> > > > Sure, we can have module name like bigtop-distro-select.
> >> > > > Initially we'll do this separate branch.
> >> > > >
> >> > > >
> >> > > >
> >> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >> > > >
> >> > > > > I believe it's for project name. isn't it.?
> >> > > >
> >> > > > projects and products.
> >> > > >
> >> > > > > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> >> > > >
> >> > > > The name of stack based no Bigtop should be Bigtop.
> >> > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> >> > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> >> > > >
> >> > > >
> >> > > > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> >> > > > >
> >> > > > > I believe it's for project name. isn't it.?
> >> > > > >
> >> > > > >
> >> > > > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >> > > > >
> >> > > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> >> > > > >
> >> > > > > Not fine.
> >> > > > > We have a trademark policy.
> >> > > > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Aj5p2h78PdIXFHsJi7Q6ouR5eG33vf1LA2wdGnlaF%2FQ%3D&reserved=0
> >> > > > >
> >> > > > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> >> > > > > >> Should we avoid unrecognized brand which may be trademark of someone?
> >> > > > > >> ambari-select or bigtop-select should be enough.
> >> > > > > >
> >> > > > > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> >> > > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> >> > > > > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> >> > > > > >
> >> > > > > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> >> > > > > >
> >> > > > > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=p1br7DcndgZq6Z5m4CvTSZOSFhkKtie%2BeqXERXuY58Q%3D&reserved=0
> >> > > > > >
> >> > > > > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EON1ukunh1oyFb5HID57FuOv9DjIBteeoCYuQfx34Gg%3D&reserved=0
> >> > > > > >
> >> > > > > >
> >> > > > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >> > > > > >
> >> > > > > > > We have still not officially finalized the new replacement name for
> >> > > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> >> > > > > > > the purpose of bdp-select and conf-select remains the same.
> >> > > > > >
> >> > > > > > Should we avoid unrecognized brand which may be trademark of someone?
> >> > > > > > ambari-select or bigtop-select should be enough.
> >> > > > > >
> >> > > > > > On 2022/06/29 13:52, Viraj Jasani wrote:
> >> > > > > > > Hi Ambari/Bigtop dev,
> >> > > > > > >
> >> > > > > > > As per the new roadmap of Apache Ambari, we would like to propose moving
> >> > > > > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> >> > > > > > > so that their rpm installation could be managed independently.
> >> > > > > > > These scripts are a basic necessity in the Ambari framework for the
> >> > > > > > > installation of various Bigdata packages. The only major changes they would
> >> > > > > > > receive is when we onboard new services and components to Ambari, else they
> >> > > > > > > usually do not receive updates. In the past, we used to get hdp-select rpm
> >> > > > > > > downloaded and installed from HDP repositories.
> >> > > > > > >
> >> > > > > > > We have still not officially finalized the new replacement name for
> >> > > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> >> > > > > > > the purpose of bdp-select and conf-select remains the same.
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > >
> >> > > > ---------------------------------------------------------------------
> >> > > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> > > > For additional commands, e-mail: dev-help@ambari.apache.org
> >> > > >
> >> > >
> >> > > ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> > > For additional commands, e-mail: dev-help@ambari.apache.org
> >> > >
> >> > >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> > For additional commands, e-mail: dev-help@ambari.apache.org
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> >> For additional commands, e-mail: dev-help@ambari.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
@Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get the final conclusion on this..?
Please let me know your availability, Can have one call to discuss on this..
On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID> wrote:
> -1 on development in branch.
> It is not worth for maintaining the branch if the modules is so small
> and barely updated as explained here.
> It should not conflict to existing code.
> I feel I must check the code before check-in based on this thread.
Sure, Viraj or me can show the code to you.
Can we've call on this Friday/Thrusday if that works..?
On 11/07/22, 11:54 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com> wrote:
> Sure, we can havemodule name like bigtop-distro-select.
> Initially we'll do this separate branch.
-1 on development in branch.
It is not worth for maintaining the branch if the modules is so small
and barely updated as explained here.
It should not conflict to existing code.
I feel I must check the code before check-in based on this thread.
Masatake Iwasaki
On 2022/07/11 8:23, Kengo Seki wrote:
>> As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls.
>
> Oh, I interpreted your words "conclude" and "finalize" as you were
> going to make a final decision. Brainstorming is welcome, of course.
> (But I'm not so sure if all people concerned could join, due to time
> difference and their schedule, etc.)
>
>> Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
>
> Sure, here's my proposal:
>
> * Stack name: "BIGTOP"
>
> - The same name as the existing one [1]
> - Because it deploys the packages generated by Bigtop
> - The existing stack should be replaced with it, because that is
> based on Bigtop 0.8 and too old to use now
> - No concern about infringing others' trademark
>
> * Component/folder name: "bigtop-select"
>
> - Consistent naming convention with the existing tools such as
> "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> - If it sounds too simple and a bit unclear, a more descriptive name
> might be an option, for example "bigtop-ambari-stack-selector"
>
> * Script name: "bigtop-select"
>
> - Consistent with the stack name
> - No concern about infringing others' trademark
>
> [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=l6OMfWaJl4yKV6zjSYiMQXYy1HBuJhs5nej0Co9K3FA%3D&reserved=0
> [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5nM8IrpP067odUjmxS%2Bv8xxDchCLGVOplmA%2Fo8Iq%2BOg%3D&reserved=0
>
> Kengo Seki <se...@apache.org>
>
> On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
>>
>>> Technical decisions shouldn't be done on other places than public mailing lists,
>>> as described in the "Open Communications" section of [1] and [2].
>> > So we should conclude the discussion in this mailing list.
>> > (And with my poor English, I'm not so confident to catch up with your
>> > fluent talk ;)
>>
>> I believe , I knew the apache way which you mentioned. We are not going conclude anything which comes to bigtop other than this mailing list.
>> As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls. Hence asking let's have call so that we can brainstorm. Even after call, everything will be published what we discussed.
>>
>> I think, whiteboarding will help to catch up with you.
>>
>> You all the think "bigtop-select" will be best option right..? Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
>>
>> And if the name represents the stack which we are going to deploy should fine I feel.. (if it's not BDP, may be OBDP:OpensourceBigDataPlatform.)
>>
>> @Viraj Jasani and others any thoughts..?
>>
>>
>> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org> wrote:
>>
>> > Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
>>
>> Technical decisions shouldn't be done on other places than public mailing lists,
>> as described in the "Open Communications" section of [1] and [2].
>> So we should conclude the discussion in this mailing list.
>> (And with my poor English, I'm not so confident to catch up with your
>> fluent talk ;)
>>
>> > FYI. Even looks bigtop used some where also..
>>
>> Bigtop is ASF's trademark as you can see in the "Apache Bigtop®
>> software" section of [3].
>> So it doesn't have the risk of trademark infringement.
>>
>> [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zaDwUjNvgU0eP5NY7wPq2BISd%2FiLs7dp92fwFUfwFCI%3D&reserved=0
>> [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DlCOz5ajX%2FziXmx7ZeD5xa0WzX06Akm3pYuMs5KX9h4%3D&reserved=0
>> [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KVc1YjBSUzAFexYTQ2IoiLOr0vkm85NBqI8WZC7g67s%3D&reserved=0
>>
>> Kengo Seki <se...@apache.org>
>>
>> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
>> <bb...@visa.com.invalid> wrote:
>> >
>> > Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
>> >
>> > FYI. Even looks bigtop used some where[1] also..
>> > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BPQQCUDhl%2BHGNS%2F1aLtS38Qah9zDs06qd2y%2B%2BUE%2FBKk%3D&reserved=0(Microsoft_product)
>> >
>> >
>> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org> wrote:
>> >
>> > Thank you for your explanation, Brahma.
>> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
>> > trademark of Redoop, so they can name the script crh-select without
>> > problem.
>> > But regarding BDP for example, I can easily find products that have
>> > the same name [2][3][4] as you already mentioned, so I'd like to
>> > recommend bigtop-select for avoiding unnecessary trouble.
>> > Or, a single and more general word just like conf-select may be less
>> > troublesome than bdp. How about "stack-select", for example?
>> >
>> > [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CM8y%2Bom6hpEl98x8G2ve5J98W%2FVeEkSPnwgFiYd2C98%3D&reserved=0
>> > [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=g2ng5E0%2BTb6N52isJ7guO10C3zTGA86dSafV9h0LXbU%3D&reserved=0
>> > [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qrU%2F4FJ5EjqoD0opzxVL1wM%2FTEM%2B%2B8MoqkZHHZNA%2Fk0%3D&reserved=0
>> > [4]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KfEGcZwpdvVZUaW1XsaUMGqVYcZyysmZhjl%2BR6Iq2wI%3D&reserved=0
>> >
>> > Kengo Seki <se...@apache.org>
>> >
>> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com> wrote:
>> > >
>> > > >Do you mean that you're going to name the module (same as "component"
>> > > >in the Bigtop terminology, I think) bigtop-distro-select,
>> > > >and still the script in question bdp-select? If so, is there any
>> > > >reason that the script must be that name?
>> > > >(No offence, I just want to understand your thoughts and its
>> > > >background, and avoid the conflict or user's confusion with existing
>> > > >trademarks or products)
>> > >
>> > > Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
>> > >
>> > >
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=e4oze4857dGtVIq14Ow8yzFnDhW9b2OG85sJMWfXbi4%3D&reserved=0
>> > >
>> > >
>> > > On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
>> > >
>> > > The following concern Masatake mentioned before is an important point,
>> > > so I talked to Brahma for clarifying his intention on the ASF Slack
>> > > yesterday.
>> > >
>> > > > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
>> > > > IIRC, HDP uses convention in which the product version is part of package name
>> > > > for addressing this.
>> > >
>> > > > I don't like to bring the awkward package name convention to Bigtop
>> > > > at least by default.
>> > >
>> > > He's planning to adopt the same mitigation as HDP for now, but he
>> > > doesn't intend to change the default package naming convention of
>> > > Bigtop,
>> > > but just add a new functionality to include an extra part into the
>> > > package name for avoiding conflict, which is disabled by default.
>> > >
>> > > And Brahma, let me confirm about the following reply:
>> > >
>> > > > Sure, we can have module name like bigtop-distro-select.
>> > >
>> > > Do you mean that you're going to name the module (same as "component"
>> > > in the Bigtop terminology, I think) bigtop-distro-select,
>> > > and still the script in question bdp-select? If so, is there any
>> > > reason that the script must be that name?
>> > > (No offence, I just want to understand your thoughts and its
>> > > background, and avoid the conflict or user's confusion with existing
>> > > trademarks or products)
>> > >
>> > > Kengo Seki <se...@apache.org>
>> > >
>> > > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
>> > > <bb...@visa.com.invalid> wrote:
>> > > >
>> > > > > The name of stack based no Bigtop should be Bigtop.
>> > > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>> > > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>> > > >
>> > > > Sure, we can have module name like bigtop-distro-select.
>> > > > Initially we'll do this separate branch.
>> > > >
>> > > >
>> > > >
>> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > >
>> > > > > I believe it's for project name. isn't it.?
>> > > >
>> > > > projects and products.
>> > > >
>> > > > > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > >
>> > > > The name of stack based no Bigtop should be Bigtop.
>> > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>> > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>> > > >
>> > > >
>> > > > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
>> > > > >
>> > > > > I believe it's for project name. isn't it.?
>> > > > >
>> > > > >
>> > > > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > > >
>> > > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > > >
>> > > > > Not fine.
>> > > > > We have a trademark policy.
>> > > > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Aj5p2h78PdIXFHsJi7Q6ouR5eG33vf1LA2wdGnlaF%2FQ%3D&reserved=0
>> > > > >
>> > > > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
>> > > > > >> Should we avoid unrecognized brand which may be trademark of someone?
>> > > > > >> ambari-select or bigtop-select should be enough.
>> > > > > >
>> > > > > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
>> > > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > > > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
>> > > > > >
>> > > > > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
>> > > > > >
>> > > > > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=p1br7DcndgZq6Z5m4CvTSZOSFhkKtie%2BeqXERXuY58Q%3D&reserved=0
>> > > > > >
>> > > > > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EON1ukunh1oyFb5HID57FuOv9DjIBteeoCYuQfx34Gg%3D&reserved=0
>> > > > > >
>> > > > > >
>> > > > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > > > >
>> > > > > > > We have still not officially finalized the new replacement name for
>> > > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>> > > > > > > the purpose of bdp-select and conf-select remains the same.
>> > > > > >
>> > > > > > Should we avoid unrecognized brand which may be trademark of someone?
>> > > > > > ambari-select or bigtop-select should be enough.
>> > > > > >
>> > > > > > On 2022/06/29 13:52, Viraj Jasani wrote:
>> > > > > > > Hi Ambari/Bigtop dev,
>> > > > > > >
>> > > > > > > As per the new roadmap of Apache Ambari, we would like to propose moving
>> > > > > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
>> > > > > > > so that their rpm installation could be managed independently.
>> > > > > > > These scripts are a basic necessity in the Ambari framework for the
>> > > > > > > installation of various Bigdata packages. The only major changes they would
>> > > > > > > receive is when we onboard new services and components to Ambari, else they
>> > > > > > > usually do not receive updates. In the past, we used to get hdp-select rpm
>> > > > > > > downloaded and installed from HDP repositories.
>> > > > > > >
>> > > > > > > We have still not officially finalized the new replacement name for
>> > > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>> > > > > > > the purpose of bdp-select and conf-select remains the same.
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > >
>> > > > ---------------------------------------------------------------------
>> > > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > > > For additional commands, e-mail: dev-help@ambari.apache.org
>> > > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > > For additional commands, e-mail: dev-help@ambari.apache.org
>> > >
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > For additional commands, e-mail: dev-help@ambari.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> For additional commands, e-mail: dev-help@ambari.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
@Masatake Iwasaki ,@Viraj Jasani , @Kengo Seki and others, can we get the final conclusion on this..?
Please let me know your availability, Can have one call to discuss on this..
On 24/07/22, 1:31 AM, "Battula, Brahma Reddy" <bb...@visa.com.INVALID> wrote:
> -1 on development in branch.
> It is not worth for maintaining the branch if the modules is so small
> and barely updated as explained here.
> It should not conflict to existing code.
> I feel I must check the code before check-in based on this thread.
Sure, Viraj or me can show the code to you.
Can we've call on this Friday/Thrusday if that works..?
On 11/07/22, 11:54 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com> wrote:
> Sure, we can havemodule name like bigtop-distro-select.
> Initially we'll do this separate branch.
-1 on development in branch.
It is not worth for maintaining the branch if the modules is so small
and barely updated as explained here.
It should not conflict to existing code.
I feel I must check the code before check-in based on this thread.
Masatake Iwasaki
On 2022/07/11 8:23, Kengo Seki wrote:
>> As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls.
>
> Oh, I interpreted your words "conclude" and "finalize" as you were
> going to make a final decision. Brainstorming is welcome, of course.
> (But I'm not so sure if all people concerned could join, due to time
> difference and their schedule, etc.)
>
>> Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
>
> Sure, here's my proposal:
>
> * Stack name: "BIGTOP"
>
> - The same name as the existing one [1]
> - Because it deploys the packages generated by Bigtop
> - The existing stack should be replaced with it, because that is
> based on Bigtop 0.8 and too old to use now
> - No concern about infringing others' trademark
>
> * Component/folder name: "bigtop-select"
>
> - Consistent naming convention with the existing tools such as
> "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> - If it sounds too simple and a bit unclear, a more descriptive name
> might be an option, for example "bigtop-ambari-stack-selector"
>
> * Script name: "bigtop-select"
>
> - Consistent with the stack name
> - No concern about infringing others' trademark
>
> [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=l6OMfWaJl4yKV6zjSYiMQXYy1HBuJhs5nej0Co9K3FA%3D&reserved=0
> [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5nM8IrpP067odUjmxS%2Bv8xxDchCLGVOplmA%2Fo8Iq%2BOg%3D&reserved=0
>
> Kengo Seki <se...@apache.org>
>
> On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
>>
>>> Technical decisions shouldn't be done on other places than public mailing lists,
>>> as described in the "Open Communications" section of [1] and [2].
>> > So we should conclude the discussion in this mailing list.
>> > (And with my poor English, I'm not so confident to catch up with your
>> > fluent talk ;)
>>
>> I believe , I knew the apache way which you mentioned. We are not going conclude anything which comes to bigtop other than this mailing list.
>> As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls. Hence asking let's have call so that we can brainstorm. Even after call, everything will be published what we discussed.
>>
>> I think, whiteboarding will help to catch up with you.
>>
>> You all the think "bigtop-select" will be best option right..? Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
>>
>> And if the name represents the stack which we are going to deploy should fine I feel.. (if it's not BDP, may be OBDP:OpensourceBigDataPlatform.)
>>
>> @Viraj Jasani and others any thoughts..?
>>
>>
>> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org> wrote:
>>
>> > Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
>>
>> Technical decisions shouldn't be done on other places than public mailing lists,
>> as described in the "Open Communications" section of [1] and [2].
>> So we should conclude the discussion in this mailing list.
>> (And with my poor English, I'm not so confident to catch up with your
>> fluent talk ;)
>>
>> > FYI. Even looks bigtop used some where also..
>>
>> Bigtop is ASF's trademark as you can see in the "Apache Bigtop®
>> software" section of [3].
>> So it doesn't have the risk of trademark infringement.
>>
>> [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097121021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zaDwUjNvgU0eP5NY7wPq2BISd%2FiLs7dp92fwFUfwFCI%3D&reserved=0
>> [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DlCOz5ajX%2FziXmx7ZeD5xa0WzX06Akm3pYuMs5KX9h4%3D&reserved=0
>> [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KVc1YjBSUzAFexYTQ2IoiLOr0vkm85NBqI8WZC7g67s%3D&reserved=0
>>
>> Kengo Seki <se...@apache.org>
>>
>> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
>> <bb...@visa.com.invalid> wrote:
>> >
>> > Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
>> >
>> > FYI. Even looks bigtop used some where[1] also..
>> > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BPQQCUDhl%2BHGNS%2F1aLtS38Qah9zDs06qd2y%2B%2BUE%2FBKk%3D&reserved=0(Microsoft_product)
>> >
>> >
>> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org> wrote:
>> >
>> > Thank you for your explanation, Brahma.
>> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
>> > trademark of Redoop, so they can name the script crh-select without
>> > problem.
>> > But regarding BDP for example, I can easily find products that have
>> > the same name [2][3][4] as you already mentioned, so I'd like to
>> > recommend bigtop-select for avoiding unnecessary trouble.
>> > Or, a single and more general word just like conf-select may be less
>> > troublesome than bdp. How about "stack-select", for example?
>> >
>> > [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CM8y%2Bom6hpEl98x8G2ve5J98W%2FVeEkSPnwgFiYd2C98%3D&reserved=0
>> > [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=g2ng5E0%2BTb6N52isJ7guO10C3zTGA86dSafV9h0LXbU%3D&reserved=0
>> > [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qrU%2F4FJ5EjqoD0opzxVL1wM%2FTEM%2B%2B8MoqkZHHZNA%2Fk0%3D&reserved=0
>> > [4]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KfEGcZwpdvVZUaW1XsaUMGqVYcZyysmZhjl%2BR6Iq2wI%3D&reserved=0
>> >
>> > Kengo Seki <se...@apache.org>
>> >
>> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com> wrote:
>> > >
>> > > >Do you mean that you're going to name the module (same as "component"
>> > > >in the Bigtop terminology, I think) bigtop-distro-select,
>> > > >and still the script in question bdp-select? If so, is there any
>> > > >reason that the script must be that name?
>> > > >(No offence, I just want to understand your thoughts and its
>> > > >background, and avoid the conflict or user's confusion with existing
>> > > >trademarks or products)
>> > >
>> > > Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
>> > >
>> > >
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=e4oze4857dGtVIq14Ow8yzFnDhW9b2OG85sJMWfXbi4%3D&reserved=0
>> > >
>> > >
>> > > On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
>> > >
>> > > The following concern Masatake mentioned before is an important point,
>> > > so I talked to Brahma for clarifying his intention on the ASF Slack
>> > > yesterday.
>> > >
>> > > > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
>> > > > IIRC, HDP uses convention in which the product version is part of package name
>> > > > for addressing this.
>> > >
>> > > > I don't like to bring the awkward package name convention to Bigtop
>> > > > at least by default.
>> > >
>> > > He's planning to adopt the same mitigation as HDP for now, but he
>> > > doesn't intend to change the default package naming convention of
>> > > Bigtop,
>> > > but just add a new functionality to include an extra part into the
>> > > package name for avoiding conflict, which is disabled by default.
>> > >
>> > > And Brahma, let me confirm about the following reply:
>> > >
>> > > > Sure, we can have module name like bigtop-distro-select.
>> > >
>> > > Do you mean that you're going to name the module (same as "component"
>> > > in the Bigtop terminology, I think) bigtop-distro-select,
>> > > and still the script in question bdp-select? If so, is there any
>> > > reason that the script must be that name?
>> > > (No offence, I just want to understand your thoughts and its
>> > > background, and avoid the conflict or user's confusion with existing
>> > > trademarks or products)
>> > >
>> > > Kengo Seki <se...@apache.org>
>> > >
>> > > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
>> > > <bb...@visa.com.invalid> wrote:
>> > > >
>> > > > > The name of stack based no Bigtop should be Bigtop.
>> > > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>> > > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>> > > >
>> > > > Sure, we can have module name like bigtop-distro-select.
>> > > > Initially we'll do this separate branch.
>> > > >
>> > > >
>> > > >
>> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > >
>> > > > > I believe it's for project name. isn't it.?
>> > > >
>> > > > projects and products.
>> > > >
>> > > > > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > >
>> > > > The name of stack based no Bigtop should be Bigtop.
>> > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>> > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>> > > >
>> > > >
>> > > > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
>> > > > >
>> > > > > I believe it's for project name. isn't it.?
>> > > > >
>> > > > >
>> > > > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > > >
>> > > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > > >
>> > > > > Not fine.
>> > > > > We have a trademark policy.
>> > > > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Aj5p2h78PdIXFHsJi7Q6ouR5eG33vf1LA2wdGnlaF%2FQ%3D&reserved=0
>> > > > >
>> > > > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
>> > > > > >> Should we avoid unrecognized brand which may be trademark of someone?
>> > > > > >> ambari-select or bigtop-select should be enough.
>> > > > > >
>> > > > > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
>> > > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > > > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
>> > > > > >
>> > > > > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
>> > > > > >
>> > > > > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=p1br7DcndgZq6Z5m4CvTSZOSFhkKtie%2BeqXERXuY58Q%3D&reserved=0
>> > > > > >
>> > > > > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C918f1d660eb946b9883a08da6ce62b67%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637942033097277244%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EON1ukunh1oyFb5HID57FuOv9DjIBteeoCYuQfx34Gg%3D&reserved=0
>> > > > > >
>> > > > > >
>> > > > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > > > >
>> > > > > > > We have still not officially finalized the new replacement name for
>> > > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>> > > > > > > the purpose of bdp-select and conf-select remains the same.
>> > > > > >
>> > > > > > Should we avoid unrecognized brand which may be trademark of someone?
>> > > > > > ambari-select or bigtop-select should be enough.
>> > > > > >
>> > > > > > On 2022/06/29 13:52, Viraj Jasani wrote:
>> > > > > > > Hi Ambari/Bigtop dev,
>> > > > > > >
>> > > > > > > As per the new roadmap of Apache Ambari, we would like to propose moving
>> > > > > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
>> > > > > > > so that their rpm installation could be managed independently.
>> > > > > > > These scripts are a basic necessity in the Ambari framework for the
>> > > > > > > installation of various Bigdata packages. The only major changes they would
>> > > > > > > receive is when we onboard new services and components to Ambari, else they
>> > > > > > > usually do not receive updates. In the past, we used to get hdp-select rpm
>> > > > > > > downloaded and installed from HDP repositories.
>> > > > > > >
>> > > > > > > We have still not officially finalized the new replacement name for
>> > > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>> > > > > > > the purpose of bdp-select and conf-select remains the same.
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > >
>> > > > ---------------------------------------------------------------------
>> > > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > > > For additional commands, e-mail: dev-help@ambari.apache.org
>> > > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > > For additional commands, e-mail: dev-help@ambari.apache.org
>> > >
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > For additional commands, e-mail: dev-help@ambari.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> For additional commands, e-mail: dev-help@ambari.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
> -1 on development in branch.
> It is not worth for maintaining the branch if the modules is so small
> and barely updated as explained here.
> It should not conflict to existing code.
> I feel I must check the code before check-in based on this thread.
Sure, Viraj or me can show the code to you.
Can we've call on this Friday/Thrusday if that works..?
On 11/07/22, 11:54 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com> wrote:
> Sure, we can havemodule name like bigtop-distro-select.
> Initially we'll do this separate branch.
-1 on development in branch.
It is not worth for maintaining the branch if the modules is so small
and barely updated as explained here.
It should not conflict to existing code.
I feel I must check the code before check-in based on this thread.
Masatake Iwasaki
On 2022/07/11 8:23, Kengo Seki wrote:
>> As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls.
>
> Oh, I interpreted your words "conclude" and "finalize" as you were
> going to make a final decision. Brainstorming is welcome, of course.
> (But I'm not so sure if all people concerned could join, due to time
> difference and their schedule, etc.)
>
>> Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
>
> Sure, here's my proposal:
>
> * Stack name: "BIGTOP"
>
> - The same name as the existing one [1]
> - Because it deploys the packages generated by Bigtop
> - The existing stack should be replaced with it, because that is
> based on Bigtop 0.8 and too old to use now
> - No concern about infringing others' trademark
>
> * Component/folder name: "bigtop-select"
>
> - Consistent naming convention with the existing tools such as
> "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> - If it sounds too simple and a bit unclear, a more descriptive name
> might be an option, for example "bigtop-ambari-stack-selector"
>
> * Script name: "bigtop-select"
>
> - Consistent with the stack name
> - No concern about infringing others' trademark
>
> [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cYO7N4wNF6iVqlTHL3Gsm74GEY5md2KmRFGAkd4IWVM%3D&reserved=0
> [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=P7Wdms8Kg%2Fkj%2BJCPjRr2Bn5zh5%2BLypqgzRROHKk%2FRa4%3D&reserved=0
>
> Kengo Seki <se...@apache.org>
>
> On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
>>
>>> Technical decisions shouldn't be done on other places than public mailing lists,
>>> as described in the "Open Communications" section of [1] and [2].
>> > So we should conclude the discussion in this mailing list.
>> > (And with my poor English, I'm not so confident to catch up with your
>> > fluent talk ;)
>>
>> I believe , I knew the apache way which you mentioned. We are not going conclude anything which comes to bigtop other than this mailing list.
>> As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls. Hence asking let's have call so that we can brainstorm. Even after call, everything will be published what we discussed.
>>
>> I think, whiteboarding will help to catch up with you.
>>
>> You all the think "bigtop-select" will be best option right..? Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
>>
>> And if the name represents the stack which we are going to deploy should fine I feel.. (if it's not BDP, may be OBDP:OpensourceBigDataPlatform.)
>>
>> @Viraj Jasani and others any thoughts..?
>>
>>
>> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org> wrote:
>>
>> > Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
>>
>> Technical decisions shouldn't be done on other places than public mailing lists,
>> as described in the "Open Communications" section of [1] and [2].
>> So we should conclude the discussion in this mailing list.
>> (And with my poor English, I'm not so confident to catch up with your
>> fluent talk ;)
>>
>> > FYI. Even looks bigtop used some where also..
>>
>> Bigtop is ASF's trademark as you can see in the "Apache Bigtop®
>> software" section of [3].
>> So it doesn't have the risk of trademark infringement.
>>
>> [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZiI5wOax4wrL4jELjM4tzltWjrfpbXlDfo5Vtfcng6U%3D&reserved=0
>> [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DBAYgiwIrW0KhQ4hfIZW3DS%2FvmLcyktovArD8T71nds%3D&reserved=0
>> [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rXmlwNSIEAUEnlwAiz0VV9Y%2FCpQwQgTGGx96E63SfPc%3D&reserved=0
>>
>> Kengo Seki <se...@apache.org>
>>
>> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
>> <bb...@visa.com.invalid> wrote:
>> >
>> > Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
>> >
>> > FYI. Even looks bigtop used some where[1] also..
>> > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WGZMIU%2FLk6GtsJ5bmVwQtVLOLuKueWeEqe85Loe4WDc%3D&reserved=0(Microsoft_product)
>> >
>> >
>> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org> wrote:
>> >
>> > Thank you for your explanation, Brahma.
>> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
>> > trademark of Redoop, so they can name the script crh-select without
>> > problem.
>> > But regarding BDP for example, I can easily find products that have
>> > the same name [2][3][4] as you already mentioned, so I'd like to
>> > recommend bigtop-select for avoiding unnecessary trouble.
>> > Or, a single and more general word just like conf-select may be less
>> > troublesome than bdp. How about "stack-select", for example?
>> >
>> > [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=h5nrgAU65uL2LA8KObbthvTYIwe%2Bl82u6KIptqQbWmw%3D&reserved=0
>> > [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Cms1cMLLNOTfVRobRzXUVG%2F3rxm4An82ZAP57KP56%2BM%3D&reserved=0
>> > [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BVAyB%2FOM8LkmWwdS5J3k8m9FSy5Bli3%2FoFRYkFO5mvM%3D&reserved=0
>> > [4]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vHmh60JYNAZMmJwJn5LBMtBu3NfHgVKPbZKlMuVW708%3D&reserved=0
>> >
>> > Kengo Seki <se...@apache.org>
>> >
>> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com> wrote:
>> > >
>> > > >Do you mean that you're going to name the module (same as "component"
>> > > >in the Bigtop terminology, I think) bigtop-distro-select,
>> > > >and still the script in question bdp-select? If so, is there any
>> > > >reason that the script must be that name?
>> > > >(No offence, I just want to understand your thoughts and its
>> > > >background, and avoid the conflict or user's confusion with existing
>> > > >trademarks or products)
>> > >
>> > > Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
>> > >
>> > >
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=59VKLQ6R4wdH6SPvZBx%2Fk%2FQp2HgeM0XKmL32jcGrFlc%3D&reserved=0
>> > >
>> > >
>> > > On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
>> > >
>> > > The following concern Masatake mentioned before is an important point,
>> > > so I talked to Brahma for clarifying his intention on the ASF Slack
>> > > yesterday.
>> > >
>> > > > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
>> > > > IIRC, HDP uses convention in which the product version is part of package name
>> > > > for addressing this.
>> > >
>> > > > I don't like to bring the awkward package name convention to Bigtop
>> > > > at least by default.
>> > >
>> > > He's planning to adopt the same mitigation as HDP for now, but he
>> > > doesn't intend to change the default package naming convention of
>> > > Bigtop,
>> > > but just add a new functionality to include an extra part into the
>> > > package name for avoiding conflict, which is disabled by default.
>> > >
>> > > And Brahma, let me confirm about the following reply:
>> > >
>> > > > Sure, we can have module name like bigtop-distro-select.
>> > >
>> > > Do you mean that you're going to name the module (same as "component"
>> > > in the Bigtop terminology, I think) bigtop-distro-select,
>> > > and still the script in question bdp-select? If so, is there any
>> > > reason that the script must be that name?
>> > > (No offence, I just want to understand your thoughts and its
>> > > background, and avoid the conflict or user's confusion with existing
>> > > trademarks or products)
>> > >
>> > > Kengo Seki <se...@apache.org>
>> > >
>> > > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
>> > > <bb...@visa.com.invalid> wrote:
>> > > >
>> > > > > The name of stack based no Bigtop should be Bigtop.
>> > > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>> > > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>> > > >
>> > > > Sure, we can have module name like bigtop-distro-select.
>> > > > Initially we'll do this separate branch.
>> > > >
>> > > >
>> > > >
>> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > >
>> > > > > I believe it's for project name. isn't it.?
>> > > >
>> > > > projects and products.
>> > > >
>> > > > > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > >
>> > > > The name of stack based no Bigtop should be Bigtop.
>> > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>> > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>> > > >
>> > > >
>> > > > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
>> > > > >
>> > > > > I believe it's for project name. isn't it.?
>> > > > >
>> > > > >
>> > > > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > > >
>> > > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > > >
>> > > > > Not fine.
>> > > > > We have a trademark policy.
>> > > > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=L6%2BiYaEd4poJPDvIveyb1ELhlAJtJtmb%2B0qvc01JKSA%3D&reserved=0
>> > > > >
>> > > > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
>> > > > > >> Should we avoid unrecognized brand which may be trademark of someone?
>> > > > > >> ambari-select or bigtop-select should be enough.
>> > > > > >
>> > > > > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
>> > > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > > > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
>> > > > > >
>> > > > > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
>> > > > > >
>> > > > > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RIkodYudAuJ8WHOlyqh9pxeXTScBpY9CEOcEOS1mYvc%3D&reserved=0
>> > > > > >
>> > > > > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966801339%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jpgY0UAlpNwO9oMykyon2eRy5dsO1xtXJwlDaXHqTBQ%3D&reserved=0
>> > > > > >
>> > > > > >
>> > > > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > > > >
>> > > > > > > We have still not officially finalized the new replacement name for
>> > > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>> > > > > > > the purpose of bdp-select and conf-select remains the same.
>> > > > > >
>> > > > > > Should we avoid unrecognized brand which may be trademark of someone?
>> > > > > > ambari-select or bigtop-select should be enough.
>> > > > > >
>> > > > > > On 2022/06/29 13:52, Viraj Jasani wrote:
>> > > > > > > Hi Ambari/Bigtop dev,
>> > > > > > >
>> > > > > > > As per the new roadmap of Apache Ambari, we would like to propose moving
>> > > > > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
>> > > > > > > so that their rpm installation could be managed independently.
>> > > > > > > These scripts are a basic necessity in the Ambari framework for the
>> > > > > > > installation of various Bigdata packages. The only major changes they would
>> > > > > > > receive is when we onboard new services and components to Ambari, else they
>> > > > > > > usually do not receive updates. In the past, we used to get hdp-select rpm
>> > > > > > > downloaded and installed from HDP repositories.
>> > > > > > >
>> > > > > > > We have still not officially finalized the new replacement name for
>> > > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>> > > > > > > the purpose of bdp-select and conf-select remains the same.
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > >
>> > > > ---------------------------------------------------------------------
>> > > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > > > For additional commands, e-mail: dev-help@ambari.apache.org
>> > > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > > For additional commands, e-mail: dev-help@ambari.apache.org
>> > >
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > For additional commands, e-mail: dev-help@ambari.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> For additional commands, e-mail: dev-help@ambari.apache.org
>>
>>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
> -1 on development in branch.
> It is not worth for maintaining the branch if the modules is so small
> and barely updated as explained here.
> It should not conflict to existing code.
> I feel I must check the code before check-in based on this thread.
Sure, Viraj or me can show the code to you.
Can we've call on this Friday/Thrusday if that works..?
On 11/07/22, 11:54 AM, "Masatake Iwasaki" <iw...@oss.nttdata.com> wrote:
> Sure, we can havemodule name like bigtop-distro-select.
> Initially we'll do this separate branch.
-1 on development in branch.
It is not worth for maintaining the branch if the modules is so small
and barely updated as explained here.
It should not conflict to existing code.
I feel I must check the code before check-in based on this thread.
Masatake Iwasaki
On 2022/07/11 8:23, Kengo Seki wrote:
>> As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls.
>
> Oh, I interpreted your words "conclude" and "finalize" as you were
> going to make a final decision. Brainstorming is welcome, of course.
> (But I'm not so sure if all people concerned could join, due to time
> difference and their schedule, etc.)
>
>> Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
>
> Sure, here's my proposal:
>
> * Stack name: "BIGTOP"
>
> - The same name as the existing one [1]
> - Because it deploys the packages generated by Bigtop
> - The existing stack should be replaced with it, because that is
> based on Bigtop 0.8 and too old to use now
> - No concern about infringing others' trademark
>
> * Component/folder name: "bigtop-select"
>
> - Consistent naming convention with the existing tools such as
> "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> - If it sounds too simple and a bit unclear, a more descriptive name
> might be an option, for example "bigtop-ambari-stack-selector"
>
> * Script name: "bigtop-select"
>
> - Consistent with the stack name
> - No concern about infringing others' trademark
>
> [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fambari%2Ftree%2Frelease-2.7.6%2Fambari-server%2Fsrc%2Fmain%2Fresources%2Fstacks%2FBIGTOP%2F0.8&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cYO7N4wNF6iVqlTHL3Gsm74GEY5md2KmRFGAkd4IWVM%3D&reserved=0
> [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fbigtop%2Ftree%2Fmaster%2Fbigtop-packages%2Fsrc%2Fcommon&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=P7Wdms8Kg%2Fkj%2BJCPjRr2Bn5zh5%2BLypqgzRROHKk%2FRa4%3D&reserved=0
>
> Kengo Seki <se...@apache.org>
>
> On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
>>
>>> Technical decisions shouldn't be done on other places than public mailing lists,
>>> as described in the "Open Communications" section of [1] and [2].
>> > So we should conclude the discussion in this mailing list.
>> > (And with my poor English, I'm not so confident to catch up with your
>> > fluent talk ;)
>>
>> I believe , I knew the apache way which you mentioned. We are not going conclude anything which comes to bigtop other than this mailing list.
>> As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls. Hence asking let's have call so that we can brainstorm. Even after call, everything will be published what we discussed.
>>
>> I think, whiteboarding will help to catch up with you.
>>
>> You all the think "bigtop-select" will be best option right..? Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
>>
>> And if the name represents the stack which we are going to deploy should fine I feel.. (if it's not BDP, may be OBDP:OpensourceBigDataPlatform.)
>>
>> @Viraj Jasani and others any thoughts..?
>>
>>
>> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org> wrote:
>>
>> > Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
>>
>> Technical decisions shouldn't be done on other places than public mailing lists,
>> as described in the "Open Communications" section of [1] and [2].
>> So we should conclude the discussion in this mailing list.
>> (And with my poor English, I'm not so confident to catch up with your
>> fluent talk ;)
>>
>> > FYI. Even looks bigtop used some where also..
>>
>> Bigtop is ASF's trademark as you can see in the "Apache Bigtop®
>> software" section of [3].
>> So it doesn't have the risk of trademark infringement.
>>
>> [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZiI5wOax4wrL4jELjM4tzltWjrfpbXlDfo5Vtfcng6U%3D&reserved=0
>> [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DBAYgiwIrW0KhQ4hfIZW3DS%2FvmLcyktovArD8T71nds%3D&reserved=0
>> [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rXmlwNSIEAUEnlwAiz0VV9Y%2FCpQwQgTGGx96E63SfPc%3D&reserved=0
>>
>> Kengo Seki <se...@apache.org>
>>
>> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
>> <bb...@visa.com.invalid> wrote:
>> >
>> > Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
>> >
>> > FYI. Even looks bigtop used some where[1] also..
>> > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WGZMIU%2FLk6GtsJ5bmVwQtVLOLuKueWeEqe85Loe4WDc%3D&reserved=0(Microsoft_product)
>> >
>> >
>> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org> wrote:
>> >
>> > Thank you for your explanation, Brahma.
>> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
>> > trademark of Redoop, so they can name the script crh-select without
>> > problem.
>> > But regarding BDP for example, I can easily find products that have
>> > the same name [2][3][4] as you already mentioned, so I'd like to
>> > recommend bigtop-select for avoiding unnecessary trouble.
>> > Or, a single and more general word just like conf-select may be less
>> > troublesome than bdp. How about "stack-select", for example?
>> >
>> > [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=h5nrgAU65uL2LA8KObbthvTYIwe%2Bl82u6KIptqQbWmw%3D&reserved=0
>> > [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Cms1cMLLNOTfVRobRzXUVG%2F3rxm4An82ZAP57KP56%2BM%3D&reserved=0
>> > [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BVAyB%2FOM8LkmWwdS5J3k8m9FSy5Bli3%2FoFRYkFO5mvM%3D&reserved=0
>> > [4]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vHmh60JYNAZMmJwJn5LBMtBu3NfHgVKPbZKlMuVW708%3D&reserved=0
>> >
>> > Kengo Seki <se...@apache.org>
>> >
>> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com> wrote:
>> > >
>> > > >Do you mean that you're going to name the module (same as "component"
>> > > >in the Bigtop terminology, I think) bigtop-distro-select,
>> > > >and still the script in question bdp-select? If so, is there any
>> > > >reason that the script must be that name?
>> > > >(No offence, I just want to understand your thoughts and its
>> > > >background, and avoid the conflict or user's confusion with existing
>> > > >trademarks or products)
>> > >
>> > > Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
>> > >
>> > >
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=59VKLQ6R4wdH6SPvZBx%2Fk%2FQp2HgeM0XKmL32jcGrFlc%3D&reserved=0
>> > >
>> > >
>> > > On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
>> > >
>> > > The following concern Masatake mentioned before is an important point,
>> > > so I talked to Brahma for clarifying his intention on the ASF Slack
>> > > yesterday.
>> > >
>> > > > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
>> > > > IIRC, HDP uses convention in which the product version is part of package name
>> > > > for addressing this.
>> > >
>> > > > I don't like to bring the awkward package name convention to Bigtop
>> > > > at least by default.
>> > >
>> > > He's planning to adopt the same mitigation as HDP for now, but he
>> > > doesn't intend to change the default package naming convention of
>> > > Bigtop,
>> > > but just add a new functionality to include an extra part into the
>> > > package name for avoiding conflict, which is disabled by default.
>> > >
>> > > And Brahma, let me confirm about the following reply:
>> > >
>> > > > Sure, we can have module name like bigtop-distro-select.
>> > >
>> > > Do you mean that you're going to name the module (same as "component"
>> > > in the Bigtop terminology, I think) bigtop-distro-select,
>> > > and still the script in question bdp-select? If so, is there any
>> > > reason that the script must be that name?
>> > > (No offence, I just want to understand your thoughts and its
>> > > background, and avoid the conflict or user's confusion with existing
>> > > trademarks or products)
>> > >
>> > > Kengo Seki <se...@apache.org>
>> > >
>> > > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
>> > > <bb...@visa.com.invalid> wrote:
>> > > >
>> > > > > The name of stack based no Bigtop should be Bigtop.
>> > > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>> > > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>> > > >
>> > > > Sure, we can have module name like bigtop-distro-select.
>> > > > Initially we'll do this separate branch.
>> > > >
>> > > >
>> > > >
>> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > >
>> > > > > I believe it's for project name. isn't it.?
>> > > >
>> > > > projects and products.
>> > > >
>> > > > > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > >
>> > > > The name of stack based no Bigtop should be Bigtop.
>> > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>> > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>> > > >
>> > > >
>> > > > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
>> > > > >
>> > > > > I believe it's for project name. isn't it.?
>> > > > >
>> > > > >
>> > > > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > > >
>> > > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > > >
>> > > > > Not fine.
>> > > > > We have a trademark policy.
>> > > > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=L6%2BiYaEd4poJPDvIveyb1ELhlAJtJtmb%2B0qvc01JKSA%3D&reserved=0
>> > > > >
>> > > > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
>> > > > > >> Should we avoid unrecognized brand which may be trademark of someone?
>> > > > > >> ambari-select or bigtop-select should be enough.
>> > > > > >
>> > > > > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
>> > > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > > > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
>> > > > > >
>> > > > > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
>> > > > > >
>> > > > > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966645584%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RIkodYudAuJ8WHOlyqh9pxeXTScBpY9CEOcEOS1mYvc%3D&reserved=0
>> > > > > >
>> > > > > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Ccfdddab2cd0f4aabddfd08da63061196%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637931174966801339%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jpgY0UAlpNwO9oMykyon2eRy5dsO1xtXJwlDaXHqTBQ%3D&reserved=0
>> > > > > >
>> > > > > >
>> > > > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > > > >
>> > > > > > > We have still not officially finalized the new replacement name for
>> > > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>> > > > > > > the purpose of bdp-select and conf-select remains the same.
>> > > > > >
>> > > > > > Should we avoid unrecognized brand which may be trademark of someone?
>> > > > > > ambari-select or bigtop-select should be enough.
>> > > > > >
>> > > > > > On 2022/06/29 13:52, Viraj Jasani wrote:
>> > > > > > > Hi Ambari/Bigtop dev,
>> > > > > > >
>> > > > > > > As per the new roadmap of Apache Ambari, we would like to propose moving
>> > > > > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
>> > > > > > > so that their rpm installation could be managed independently.
>> > > > > > > These scripts are a basic necessity in the Ambari framework for the
>> > > > > > > installation of various Bigdata packages. The only major changes they would
>> > > > > > > receive is when we onboard new services and components to Ambari, else they
>> > > > > > > usually do not receive updates. In the past, we used to get hdp-select rpm
>> > > > > > > downloaded and installed from HDP repositories.
>> > > > > > >
>> > > > > > > We have still not officially finalized the new replacement name for
>> > > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>> > > > > > > the purpose of bdp-select and conf-select remains the same.
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > >
>> > > > ---------------------------------------------------------------------
>> > > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > > > For additional commands, e-mail: dev-help@ambari.apache.org
>> > > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > > For additional commands, e-mail: dev-help@ambari.apache.org
>> > >
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > For additional commands, e-mail: dev-help@ambari.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> For additional commands, e-mail: dev-help@ambari.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.com>.
> Sure, we can havemodule name like bigtop-distro-select.
> Initially we'll do this separate branch.
-1 on development in branch.
It is not worth for maintaining the branch if the modules is so small
and barely updated as explained here.
It should not conflict to existing code.
I feel I must check the code before check-in based on this thread.
Masatake Iwasaki
On 2022/07/11 8:23, Kengo Seki wrote:
>> As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls.
>
> Oh, I interpreted your words "conclude" and "finalize" as you were
> going to make a final decision. Brainstorming is welcome, of course.
> (But I'm not so sure if all people concerned could join, due to time
> difference and their schedule, etc.)
>
>> Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
>
> Sure, here's my proposal:
>
> * Stack name: "BIGTOP"
>
> - The same name as the existing one [1]
> - Because it deploys the packages generated by Bigtop
> - The existing stack should be replaced with it, because that is
> based on Bigtop 0.8 and too old to use now
> - No concern about infringing others' trademark
>
> * Component/folder name: "bigtop-select"
>
> - Consistent naming convention with the existing tools such as
> "bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
> - If it sounds too simple and a bit unclear, a more descriptive name
> might be an option, for example "bigtop-ambari-stack-selector"
>
> * Script name: "bigtop-select"
>
> - Consistent with the stack name
> - No concern about infringing others' trademark
>
> [1]: https://github.com/apache/ambari/tree/release-2.7.6/ambari-server/src/main/resources/stacks/BIGTOP/0.8
> [2]: https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common
>
> Kengo Seki <se...@apache.org>
>
> On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
>>
>>> Technical decisions shouldn't be done on other places than public mailing lists,
>>> as described in the "Open Communications" section of [1] and [2].
>> > So we should conclude the discussion in this mailing list.
>> > (And with my poor English, I'm not so confident to catch up with your
>> > fluent talk ;)
>>
>> I believe , I knew the apache way which you mentioned. We are not going conclude anything which comes to bigtop other than this mailing list.
>> As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls. Hence asking let's have call so that we can brainstorm. Even after call, everything will be published what we discussed.
>>
>> I think, whiteboarding will help to catch up with you.
>>
>> You all the think "bigtop-select" will be best option right..? Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
>>
>> And if the name represents the stack which we are going to deploy should fine I feel.. (if it's not BDP, may be OBDP:OpensourceBigDataPlatform.)
>>
>> @Viraj Jasani and others any thoughts..?
>>
>>
>> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org> wrote:
>>
>> > Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
>>
>> Technical decisions shouldn't be done on other places than public mailing lists,
>> as described in the "Open Communications" section of [1] and [2].
>> So we should conclude the discussion in this mailing list.
>> (And with my poor English, I'm not so confident to catch up with your
>> fluent talk ;)
>>
>> > FYI. Even looks bigtop used some where also..
>>
>> Bigtop is ASF's trademark as you can see in the "Apache Bigtop®
>> software" section of [3].
>> So it doesn't have the risk of trademark infringement.
>>
>> [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=wZnePXjGrZV8qKXKnc%2Bitzk1CKAq%2B4tU%2Bk5x9xfbtqo%3D&reserved=0
>> [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1rBTRJ9ojoa1iDQqEyebVVYQMEh5FH9u0lLkiBVE%2FgE%3D&reserved=0
>> [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1xktddBWr6aMaWIPHooMuELx4C0INpnl140VSv1dAoQ%3D&reserved=0
>>
>> Kengo Seki <se...@apache.org>
>>
>> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
>> <bb...@visa.com.invalid> wrote:
>> >
>> > Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
>> >
>> > FYI. Even looks bigtop used some where[1] also..
>> > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lcwX%2BgrLqAqjPJdVAnWDf8lv7sbI11htDx3QO7VNOXY%3D&reserved=0(Microsoft_product)
>> >
>> >
>> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org> wrote:
>> >
>> > Thank you for your explanation, Brahma.
>> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
>> > trademark of Redoop, so they can name the script crh-select without
>> > problem.
>> > But regarding BDP for example, I can easily find products that have
>> > the same name [2][3][4] as you already mentioned, so I'd like to
>> > recommend bigtop-select for avoiding unnecessary trouble.
>> > Or, a single and more general word just like conf-select may be less
>> > troublesome than bdp. How about "stack-select", for example?
>> >
>> > [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vEd%2BvoUH%2F6p%2BEmtK4Lhhi8qi3f1YPfdELHeToWR8VnU%3D&reserved=0
>> > [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EGoGDLI7JSuEksBaReqLny%2BQgI%2Bk0uKhb9%2BJPSf9kDs%3D&reserved=0
>> > [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=UNbYxvQpXlgK3k80qr8KFHcJZdDw9xhRrY3VlcOWL2Q%3D&reserved=0
>> > [4]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vy%2BEcsGFs4FP339AN%2B%2F2rCw617Qxd5nbUN41dLRPKRU%3D&reserved=0
>> >
>> > Kengo Seki <se...@apache.org>
>> >
>> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com> wrote:
>> > >
>> > > >Do you mean that you're going to name the module (same as "component"
>> > > >in the Bigtop terminology, I think) bigtop-distro-select,
>> > > >and still the script in question bdp-select? If so, is there any
>> > > >reason that the script must be that name?
>> > > >(No offence, I just want to understand your thoughts and its
>> > > >background, and avoid the conflict or user's confusion with existing
>> > > >trademarks or products)
>> > >
>> > > Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
>> > >
>> > >
>> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BPe6X6A9%2B0iZj%2BrXGVCEdGp81NbIZOzZ0gHoEPFYjis%3D&reserved=0
>> > >
>> > >
>> > > On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
>> > >
>> > > The following concern Masatake mentioned before is an important point,
>> > > so I talked to Brahma for clarifying his intention on the ASF Slack
>> > > yesterday.
>> > >
>> > > > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
>> > > > IIRC, HDP uses convention in which the product version is part of package name
>> > > > for addressing this.
>> > >
>> > > > I don't like to bring the awkward package name convention to Bigtop
>> > > > at least by default.
>> > >
>> > > He's planning to adopt the same mitigation as HDP for now, but he
>> > > doesn't intend to change the default package naming convention of
>> > > Bigtop,
>> > > but just add a new functionality to include an extra part into the
>> > > package name for avoiding conflict, which is disabled by default.
>> > >
>> > > And Brahma, let me confirm about the following reply:
>> > >
>> > > > Sure, we can have module name like bigtop-distro-select.
>> > >
>> > > Do you mean that you're going to name the module (same as "component"
>> > > in the Bigtop terminology, I think) bigtop-distro-select,
>> > > and still the script in question bdp-select? If so, is there any
>> > > reason that the script must be that name?
>> > > (No offence, I just want to understand your thoughts and its
>> > > background, and avoid the conflict or user's confusion with existing
>> > > trademarks or products)
>> > >
>> > > Kengo Seki <se...@apache.org>
>> > >
>> > > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
>> > > <bb...@visa.com.invalid> wrote:
>> > > >
>> > > > > The name of stack based no Bigtop should be Bigtop.
>> > > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>> > > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>> > > >
>> > > > Sure, we can have module name like bigtop-distro-select.
>> > > > Initially we'll do this separate branch.
>> > > >
>> > > >
>> > > >
>> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > >
>> > > > > I believe it's for project name. isn't it.?
>> > > >
>> > > > projects and products.
>> > > >
>> > > > > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > >
>> > > > The name of stack based no Bigtop should be Bigtop.
>> > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>> > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>> > > >
>> > > >
>> > > > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
>> > > > >
>> > > > > I believe it's for project name. isn't it.?
>> > > > >
>> > > > >
>> > > > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > > >
>> > > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > > >
>> > > > > Not fine.
>> > > > > We have a trademark policy.
>> > > > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VljKIm7VEf31j65Z9qYO3dRvLlHEYzHhjv%2B780tQMFU%3D&reserved=0
>> > > > >
>> > > > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
>> > > > > >> Should we avoid unrecognized brand which may be trademark of someone?
>> > > > > >> ambari-select or bigtop-select should be enough.
>> > > > > >
>> > > > > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
>> > > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>> > > > > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
>> > > > > >
>> > > > > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
>> > > > > >
>> > > > > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lRrIYUg7AyzKk276YdE5k7p7FyIfKdfdSrE7kHGnZVs%3D&reserved=0
>> > > > > >
>> > > > > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dODih3q2eq2IqjPmK9vArJB9V17HuXon6NzlnU%2BVHSw%3D&reserved=0
>> > > > > >
>> > > > > >
>> > > > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>> > > > > >
>> > > > > > > We have still not officially finalized the new replacement name for
>> > > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>> > > > > > > the purpose of bdp-select and conf-select remains the same.
>> > > > > >
>> > > > > > Should we avoid unrecognized brand which may be trademark of someone?
>> > > > > > ambari-select or bigtop-select should be enough.
>> > > > > >
>> > > > > > On 2022/06/29 13:52, Viraj Jasani wrote:
>> > > > > > > Hi Ambari/Bigtop dev,
>> > > > > > >
>> > > > > > > As per the new roadmap of Apache Ambari, we would like to propose moving
>> > > > > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
>> > > > > > > so that their rpm installation could be managed independently.
>> > > > > > > These scripts are a basic necessity in the Ambari framework for the
>> > > > > > > installation of various Bigdata packages. The only major changes they would
>> > > > > > > receive is when we onboard new services and components to Ambari, else they
>> > > > > > > usually do not receive updates. In the past, we used to get hdp-select rpm
>> > > > > > > downloaded and installed from HDP repositories.
>> > > > > > >
>> > > > > > > We have still not officially finalized the new replacement name for
>> > > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>> > > > > > > the purpose of bdp-select and conf-select remains the same.
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > >
>> > > > ---------------------------------------------------------------------
>> > > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > > > For additional commands, e-mail: dev-help@ambari.apache.org
>> > > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > > For additional commands, e-mail: dev-help@ambari.apache.org
>> > >
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> > For additional commands, e-mail: dev-help@ambari.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> For additional commands, e-mail: dev-help@ambari.apache.org
>>
>>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Kengo Seki <se...@apache.org>.
> As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls.
Oh, I interpreted your words "conclude" and "finalize" as you were
going to make a final decision. Brainstorming is welcome, of course.
(But I'm not so sure if all people concerned could join, due to time
difference and their schedule, etc.)
> Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
Sure, here's my proposal:
* Stack name: "BIGTOP"
- The same name as the existing one [1]
- Because it deploys the packages generated by Bigtop
- The existing stack should be replaced with it, because that is
based on Bigtop 0.8 and too old to use now
- No concern about infringing others' trademark
* Component/folder name: "bigtop-select"
- Consistent naming convention with the existing tools such as
"bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
- If it sounds too simple and a bit unclear, a more descriptive name
might be an option, for example "bigtop-ambari-stack-selector"
* Script name: "bigtop-select"
- Consistent with the stack name
- No concern about infringing others' trademark
[1]: https://github.com/apache/ambari/tree/release-2.7.6/ambari-server/src/main/resources/stacks/BIGTOP/0.8
[2]: https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common
Kengo Seki <se...@apache.org>
On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
>
> > Technical decisions shouldn't be done on other places than public mailing lists,
> > as described in the "Open Communications" section of [1] and [2].
> > So we should conclude the discussion in this mailing list.
> > (And with my poor English, I'm not so confident to catch up with your
> > fluent talk ;)
>
> I believe , I knew the apache way which you mentioned. We are not going conclude anything which comes to bigtop other than this mailing list.
> As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls. Hence asking let's have call so that we can brainstorm. Even after call, everything will be published what we discussed.
>
> I think, whiteboarding will help to catch up with you.
>
> You all the think "bigtop-select" will be best option right..? Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
>
> And if the name represents the stack which we are going to deploy should fine I feel.. (if it's not BDP, may be OBDP:OpensourceBigDataPlatform.)
>
> @Viraj Jasani and others any thoughts..?
>
>
> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org> wrote:
>
> > Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
>
> Technical decisions shouldn't be done on other places than public mailing lists,
> as described in the "Open Communications" section of [1] and [2].
> So we should conclude the discussion in this mailing list.
> (And with my poor English, I'm not so confident to catch up with your
> fluent talk ;)
>
> > FYI. Even looks bigtop used some where also..
>
> Bigtop is ASF's trademark as you can see in the "Apache Bigtop®
> software" section of [3].
> So it doesn't have the risk of trademark infringement.
>
> [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=wZnePXjGrZV8qKXKnc%2Bitzk1CKAq%2B4tU%2Bk5x9xfbtqo%3D&reserved=0
> [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1rBTRJ9ojoa1iDQqEyebVVYQMEh5FH9u0lLkiBVE%2FgE%3D&reserved=0
> [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1xktddBWr6aMaWIPHooMuELx4C0INpnl140VSv1dAoQ%3D&reserved=0
>
> Kengo Seki <se...@apache.org>
>
> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
> >
> > Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
> >
> > FYI. Even looks bigtop used some where[1] also..
> > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lcwX%2BgrLqAqjPJdVAnWDf8lv7sbI11htDx3QO7VNOXY%3D&reserved=0(Microsoft_product)
> >
> >
> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org> wrote:
> >
> > Thank you for your explanation, Brahma.
> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
> > trademark of Redoop, so they can name the script crh-select without
> > problem.
> > But regarding BDP for example, I can easily find products that have
> > the same name [2][3][4] as you already mentioned, so I'd like to
> > recommend bigtop-select for avoiding unnecessary trouble.
> > Or, a single and more general word just like conf-select may be less
> > troublesome than bdp. How about "stack-select", for example?
> >
> > [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vEd%2BvoUH%2F6p%2BEmtK4Lhhi8qi3f1YPfdELHeToWR8VnU%3D&reserved=0
> > [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EGoGDLI7JSuEksBaReqLny%2BQgI%2Bk0uKhb9%2BJPSf9kDs%3D&reserved=0
> > [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=UNbYxvQpXlgK3k80qr8KFHcJZdDw9xhRrY3VlcOWL2Q%3D&reserved=0
> > [4]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vy%2BEcsGFs4FP339AN%2B%2F2rCw617Qxd5nbUN41dLRPKRU%3D&reserved=0
> >
> > Kengo Seki <se...@apache.org>
> >
> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com> wrote:
> > >
> > > >Do you mean that you're going to name the module (same as "component"
> > > >in the Bigtop terminology, I think) bigtop-distro-select,
> > > >and still the script in question bdp-select? If so, is there any
> > > >reason that the script must be that name?
> > > >(No offence, I just want to understand your thoughts and its
> > > >background, and avoid the conflict or user's confusion with existing
> > > >trademarks or products)
> > >
> > > Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
> > >
> > >
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BPe6X6A9%2B0iZj%2BrXGVCEdGp81NbIZOzZ0gHoEPFYjis%3D&reserved=0
> > >
> > >
> > > On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
> > >
> > > The following concern Masatake mentioned before is an important point,
> > > so I talked to Brahma for clarifying his intention on the ASF Slack
> > > yesterday.
> > >
> > > > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > > > IIRC, HDP uses convention in which the product version is part of package name
> > > > for addressing this.
> > >
> > > > I don't like to bring the awkward package name convention to Bigtop
> > > > at least by default.
> > >
> > > He's planning to adopt the same mitigation as HDP for now, but he
> > > doesn't intend to change the default package naming convention of
> > > Bigtop,
> > > but just add a new functionality to include an extra part into the
> > > package name for avoiding conflict, which is disabled by default.
> > >
> > > And Brahma, let me confirm about the following reply:
> > >
> > > > Sure, we can have module name like bigtop-distro-select.
> > >
> > > Do you mean that you're going to name the module (same as "component"
> > > in the Bigtop terminology, I think) bigtop-distro-select,
> > > and still the script in question bdp-select? If so, is there any
> > > reason that the script must be that name?
> > > (No offence, I just want to understand your thoughts and its
> > > background, and avoid the conflict or user's confusion with existing
> > > trademarks or products)
> > >
> > > Kengo Seki <se...@apache.org>
> > >
> > > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
> > > <bb...@visa.com.invalid> wrote:
> > > >
> > > > > The name of stack based no Bigtop should be Bigtop.
> > > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> > > >
> > > > Sure, we can have module name like bigtop-distro-select.
> > > > Initially we'll do this separate branch.
> > > >
> > > >
> > > >
> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >
> > > > > I believe it's for project name. isn't it.?
> > > >
> > > > projects and products.
> > > >
> > > > > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >
> > > > The name of stack based no Bigtop should be Bigtop.
> > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> > > >
> > > >
> > > > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> > > > >
> > > > > I believe it's for project name. isn't it.?
> > > > >
> > > > >
> > > > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > > >
> > > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > >
> > > > > Not fine.
> > > > > We have a trademark policy.
> > > > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VljKIm7VEf31j65Z9qYO3dRvLlHEYzHhjv%2B780tQMFU%3D&reserved=0
> > > > >
> > > > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> > > > > >> Should we avoid unrecognized brand which may be trademark of someone?
> > > > > >> ambari-select or bigtop-select should be enough.
> > > > > >
> > > > > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > > > >
> > > > > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> > > > > >
> > > > > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lRrIYUg7AyzKk276YdE5k7p7FyIfKdfdSrE7kHGnZVs%3D&reserved=0
> > > > > >
> > > > > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dODih3q2eq2IqjPmK9vArJB9V17HuXon6NzlnU%2BVHSw%3D&reserved=0
> > > > > >
> > > > > >
> > > > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > > > >
> > > > > > > We have still not officially finalized the new replacement name for
> > > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > > > the purpose of bdp-select and conf-select remains the same.
> > > > > >
> > > > > > Should we avoid unrecognized brand which may be trademark of someone?
> > > > > > ambari-select or bigtop-select should be enough.
> > > > > >
> > > > > > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > > > > > Hi Ambari/Bigtop dev,
> > > > > > >
> > > > > > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > > > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > > > > > so that their rpm installation could be managed independently.
> > > > > > > These scripts are a basic necessity in the Ambari framework for the
> > > > > > > installation of various Bigdata packages. The only major changes they would
> > > > > > > receive is when we onboard new services and components to Ambari, else they
> > > > > > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > > > > > downloaded and installed from HDP repositories.
> > > > > > >
> > > > > > > We have still not officially finalized the new replacement name for
> > > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > > > the purpose of bdp-select and conf-select remains the same.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > > > For additional commands, e-mail: dev-help@ambari.apache.org
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > > For additional commands, e-mail: dev-help@ambari.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Kengo Seki <se...@apache.org>.
> As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls.
Oh, I interpreted your words "conclude" and "finalize" as you were
going to make a final decision. Brainstorming is welcome, of course.
(But I'm not so sure if all people concerned could join, due to time
difference and their schedule, etc.)
> Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
Sure, here's my proposal:
* Stack name: "BIGTOP"
- The same name as the existing one [1]
- Because it deploys the packages generated by Bigtop
- The existing stack should be replaced with it, because that is
based on Bigtop 0.8 and too old to use now
- No concern about infringing others' trademark
* Component/folder name: "bigtop-select"
- Consistent naming convention with the existing tools such as
"bigtop-groovy", "bigtop-jsvc", "bigtop-utils" [2]
- If it sounds too simple and a bit unclear, a more descriptive name
might be an option, for example "bigtop-ambari-stack-selector"
* Script name: "bigtop-select"
- Consistent with the stack name
- No concern about infringing others' trademark
[1]: https://github.com/apache/ambari/tree/release-2.7.6/ambari-server/src/main/resources/stacks/BIGTOP/0.8
[2]: https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common
Kengo Seki <se...@apache.org>
On Mon, Jul 11, 2022 at 3:19 AM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
>
> > Technical decisions shouldn't be done on other places than public mailing lists,
> > as described in the "Open Communications" section of [1] and [2].
> > So we should conclude the discussion in this mailing list.
> > (And with my poor English, I'm not so confident to catch up with your
> > fluent talk ;)
>
> I believe , I knew the apache way which you mentioned. We are not going conclude anything which comes to bigtop other than this mailing list.
> As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls. Hence asking let's have call so that we can brainstorm. Even after call, everything will be published what we discussed.
>
> I think, whiteboarding will help to catch up with you.
>
> You all the think "bigtop-select" will be best option right..? Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
>
> And if the name represents the stack which we are going to deploy should fine I feel.. (if it's not BDP, may be OBDP:OpensourceBigDataPlatform.)
>
> @Viraj Jasani and others any thoughts..?
>
>
> On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org> wrote:
>
> > Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
>
> Technical decisions shouldn't be done on other places than public mailing lists,
> as described in the "Open Communications" section of [1] and [2].
> So we should conclude the discussion in this mailing list.
> (And with my poor English, I'm not so confident to catch up with your
> fluent talk ;)
>
> > FYI. Even looks bigtop used some where also..
>
> Bigtop is ASF's trademark as you can see in the "Apache Bigtop®
> software" section of [3].
> So it doesn't have the risk of trademark infringement.
>
> [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=wZnePXjGrZV8qKXKnc%2Bitzk1CKAq%2B4tU%2Bk5x9xfbtqo%3D&reserved=0
> [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1rBTRJ9ojoa1iDQqEyebVVYQMEh5FH9u0lLkiBVE%2FgE%3D&reserved=0
> [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1xktddBWr6aMaWIPHooMuELx4C0INpnl140VSv1dAoQ%3D&reserved=0
>
> Kengo Seki <se...@apache.org>
>
> On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
> >
> > Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
> >
> > FYI. Even looks bigtop used some where[1] also..
> > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lcwX%2BgrLqAqjPJdVAnWDf8lv7sbI11htDx3QO7VNOXY%3D&reserved=0(Microsoft_product)
> >
> >
> > On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org> wrote:
> >
> > Thank you for your explanation, Brahma.
> > CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
> > trademark of Redoop, so they can name the script crh-select without
> > problem.
> > But regarding BDP for example, I can easily find products that have
> > the same name [2][3][4] as you already mentioned, so I'd like to
> > recommend bigtop-select for avoiding unnecessary trouble.
> > Or, a single and more general word just like conf-select may be less
> > troublesome than bdp. How about "stack-select", for example?
> >
> > [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vEd%2BvoUH%2F6p%2BEmtK4Lhhi8qi3f1YPfdELHeToWR8VnU%3D&reserved=0
> > [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EGoGDLI7JSuEksBaReqLny%2BQgI%2Bk0uKhb9%2BJPSf9kDs%3D&reserved=0
> > [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=UNbYxvQpXlgK3k80qr8KFHcJZdDw9xhRrY3VlcOWL2Q%3D&reserved=0
> > [4]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vy%2BEcsGFs4FP339AN%2B%2F2rCw617Qxd5nbUN41dLRPKRU%3D&reserved=0
> >
> > Kengo Seki <se...@apache.org>
> >
> > On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com> wrote:
> > >
> > > >Do you mean that you're going to name the module (same as "component"
> > > >in the Bigtop terminology, I think) bigtop-distro-select,
> > > >and still the script in question bdp-select? If so, is there any
> > > >reason that the script must be that name?
> > > >(No offence, I just want to understand your thoughts and its
> > > >background, and avoid the conflict or user's confusion with existing
> > > >trademarks or products)
> > >
> > > Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
> > >
> > >
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BPe6X6A9%2B0iZj%2BrXGVCEdGp81NbIZOzZ0gHoEPFYjis%3D&reserved=0
> > >
> > >
> > > On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
> > >
> > > The following concern Masatake mentioned before is an important point,
> > > so I talked to Brahma for clarifying his intention on the ASF Slack
> > > yesterday.
> > >
> > > > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > > > IIRC, HDP uses convention in which the product version is part of package name
> > > > for addressing this.
> > >
> > > > I don't like to bring the awkward package name convention to Bigtop
> > > > at least by default.
> > >
> > > He's planning to adopt the same mitigation as HDP for now, but he
> > > doesn't intend to change the default package naming convention of
> > > Bigtop,
> > > but just add a new functionality to include an extra part into the
> > > package name for avoiding conflict, which is disabled by default.
> > >
> > > And Brahma, let me confirm about the following reply:
> > >
> > > > Sure, we can have module name like bigtop-distro-select.
> > >
> > > Do you mean that you're going to name the module (same as "component"
> > > in the Bigtop terminology, I think) bigtop-distro-select,
> > > and still the script in question bdp-select? If so, is there any
> > > reason that the script must be that name?
> > > (No offence, I just want to understand your thoughts and its
> > > background, and avoid the conflict or user's confusion with existing
> > > trademarks or products)
> > >
> > > Kengo Seki <se...@apache.org>
> > >
> > > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
> > > <bb...@visa.com.invalid> wrote:
> > > >
> > > > > The name of stack based no Bigtop should be Bigtop.
> > > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> > > >
> > > > Sure, we can have module name like bigtop-distro-select.
> > > > Initially we'll do this separate branch.
> > > >
> > > >
> > > >
> > > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >
> > > > > I believe it's for project name. isn't it.?
> > > >
> > > > projects and products.
> > > >
> > > > > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >
> > > > The name of stack based no Bigtop should be Bigtop.
> > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> > > >
> > > >
> > > > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> > > > >
> > > > > I believe it's for project name. isn't it.?
> > > > >
> > > > >
> > > > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > > >
> > > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > >
> > > > > Not fine.
> > > > > We have a trademark policy.
> > > > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VljKIm7VEf31j65Z9qYO3dRvLlHEYzHhjv%2B780tQMFU%3D&reserved=0
> > > > >
> > > > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> > > > > >> Should we avoid unrecognized brand which may be trademark of someone?
> > > > > >> ambari-select or bigtop-select should be enough.
> > > > > >
> > > > > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > > > >
> > > > > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> > > > > >
> > > > > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lRrIYUg7AyzKk276YdE5k7p7FyIfKdfdSrE7kHGnZVs%3D&reserved=0
> > > > > >
> > > > > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dODih3q2eq2IqjPmK9vArJB9V17HuXon6NzlnU%2BVHSw%3D&reserved=0
> > > > > >
> > > > > >
> > > > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > > > >
> > > > > > > We have still not officially finalized the new replacement name for
> > > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > > > the purpose of bdp-select and conf-select remains the same.
> > > > > >
> > > > > > Should we avoid unrecognized brand which may be trademark of someone?
> > > > > > ambari-select or bigtop-select should be enough.
> > > > > >
> > > > > > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > > > > > Hi Ambari/Bigtop dev,
> > > > > > >
> > > > > > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > > > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > > > > > so that their rpm installation could be managed independently.
> > > > > > > These scripts are a basic necessity in the Ambari framework for the
> > > > > > > installation of various Bigdata packages. The only major changes they would
> > > > > > > receive is when we onboard new services and components to Ambari, else they
> > > > > > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > > > > > downloaded and installed from HDP repositories.
> > > > > > >
> > > > > > > We have still not officially finalized the new replacement name for
> > > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > > > the purpose of bdp-select and conf-select remains the same.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > > > For additional commands, e-mail: dev-help@ambari.apache.org
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > > For additional commands, e-mail: dev-help@ambari.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
> Technical decisions shouldn't be done on other places than public mailing lists,
> as described in the "Open Communications" section of [1] and [2].
> So we should conclude the discussion in this mailing list.
> (And with my poor English, I'm not so confident to catch up with your
> fluent talk ;)
I believe , I knew the apache way which you mentioned. We are not going conclude anything which comes to bigtop other than this mailing list.
As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls. Hence asking let's have call so that we can brainstorm. Even after call, everything will be published what we discussed.
I think, whiteboarding will help to catch up with you.
You all the think "bigtop-select" will be best option right..? Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
And if the name represents the stack which we are going to deploy should fine I feel.. (if it's not BDP, may be OBDP:OpensourceBigDataPlatform.)
@Viraj Jasani and others any thoughts..?
On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org> wrote:
> Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
Technical decisions shouldn't be done on other places than public mailing lists,
as described in the "Open Communications" section of [1] and [2].
So we should conclude the discussion in this mailing list.
(And with my poor English, I'm not so confident to catch up with your
fluent talk ;)
> FYI. Even looks bigtop used some where also..
Bigtop is ASF's trademark as you can see in the "Apache Bigtop®
software" section of [3].
So it doesn't have the risk of trademark infringement.
[1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=wZnePXjGrZV8qKXKnc%2Bitzk1CKAq%2B4tU%2Bk5x9xfbtqo%3D&reserved=0
[2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1rBTRJ9ojoa1iDQqEyebVVYQMEh5FH9u0lLkiBVE%2FgE%3D&reserved=0
[3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1xktddBWr6aMaWIPHooMuELx4C0INpnl140VSv1dAoQ%3D&reserved=0
Kengo Seki <se...@apache.org>
On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
>
> Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
>
> FYI. Even looks bigtop used some where[1] also..
> 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lcwX%2BgrLqAqjPJdVAnWDf8lv7sbI11htDx3QO7VNOXY%3D&reserved=0(Microsoft_product)
>
>
> On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org> wrote:
>
> Thank you for your explanation, Brahma.
> CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
> trademark of Redoop, so they can name the script crh-select without
> problem.
> But regarding BDP for example, I can easily find products that have
> the same name [2][3][4] as you already mentioned, so I'd like to
> recommend bigtop-select for avoiding unnecessary trouble.
> Or, a single and more general word just like conf-select may be less
> troublesome than bdp. How about "stack-select", for example?
>
> [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vEd%2BvoUH%2F6p%2BEmtK4Lhhi8qi3f1YPfdELHeToWR8VnU%3D&reserved=0
> [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EGoGDLI7JSuEksBaReqLny%2BQgI%2Bk0uKhb9%2BJPSf9kDs%3D&reserved=0
> [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=UNbYxvQpXlgK3k80qr8KFHcJZdDw9xhRrY3VlcOWL2Q%3D&reserved=0
> [4]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vy%2BEcsGFs4FP339AN%2B%2F2rCw617Qxd5nbUN41dLRPKRU%3D&reserved=0
>
> Kengo Seki <se...@apache.org>
>
> On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com> wrote:
> >
> > >Do you mean that you're going to name the module (same as "component"
> > >in the Bigtop terminology, I think) bigtop-distro-select,
> > >and still the script in question bdp-select? If so, is there any
> > >reason that the script must be that name?
> > >(No offence, I just want to understand your thoughts and its
> > >background, and avoid the conflict or user's confusion with existing
> > >trademarks or products)
> >
> > Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
> >
> >
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BPe6X6A9%2B0iZj%2BrXGVCEdGp81NbIZOzZ0gHoEPFYjis%3D&reserved=0
> >
> >
> > On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
> >
> > The following concern Masatake mentioned before is an important point,
> > so I talked to Brahma for clarifying his intention on the ASF Slack
> > yesterday.
> >
> > > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > > IIRC, HDP uses convention in which the product version is part of package name
> > > for addressing this.
> >
> > > I don't like to bring the awkward package name convention to Bigtop
> > > at least by default.
> >
> > He's planning to adopt the same mitigation as HDP for now, but he
> > doesn't intend to change the default package naming convention of
> > Bigtop,
> > but just add a new functionality to include an extra part into the
> > package name for avoiding conflict, which is disabled by default.
> >
> > And Brahma, let me confirm about the following reply:
> >
> > > Sure, we can have module name like bigtop-distro-select.
> >
> > Do you mean that you're going to name the module (same as "component"
> > in the Bigtop terminology, I think) bigtop-distro-select,
> > and still the script in question bdp-select? If so, is there any
> > reason that the script must be that name?
> > (No offence, I just want to understand your thoughts and its
> > background, and avoid the conflict or user's confusion with existing
> > trademarks or products)
> >
> > Kengo Seki <se...@apache.org>
> >
> > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
> > <bb...@visa.com.invalid> wrote:
> > >
> > > > The name of stack based no Bigtop should be Bigtop.
> > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> > >
> > > Sure, we can have module name like bigtop-distro-select.
> > > Initially we'll do this separate branch.
> > >
> > >
> > >
> > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >
> > > > I believe it's for project name. isn't it.?
> > >
> > > projects and products.
> > >
> > > > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >
> > > The name of stack based no Bigtop should be Bigtop.
> > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> > >
> > >
> > > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> > > >
> > > > I believe it's for project name. isn't it.?
> > > >
> > > >
> > > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >
> > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >
> > > > Not fine.
> > > > We have a trademark policy.
> > > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VljKIm7VEf31j65Z9qYO3dRvLlHEYzHhjv%2B780tQMFU%3D&reserved=0
> > > >
> > > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> > > > >> Should we avoid unrecognized brand which may be trademark of someone?
> > > > >> ambari-select or bigtop-select should be enough.
> > > > >
> > > > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > > >
> > > > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> > > > >
> > > > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lRrIYUg7AyzKk276YdE5k7p7FyIfKdfdSrE7kHGnZVs%3D&reserved=0
> > > > >
> > > > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dODih3q2eq2IqjPmK9vArJB9V17HuXon6NzlnU%2BVHSw%3D&reserved=0
> > > > >
> > > > >
> > > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > > >
> > > > > > We have still not officially finalized the new replacement name for
> > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > > the purpose of bdp-select and conf-select remains the same.
> > > > >
> > > > > Should we avoid unrecognized brand which may be trademark of someone?
> > > > > ambari-select or bigtop-select should be enough.
> > > > >
> > > > > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > > > > Hi Ambari/Bigtop dev,
> > > > > >
> > > > > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > > > > so that their rpm installation could be managed independently.
> > > > > > These scripts are a basic necessity in the Ambari framework for the
> > > > > > installation of various Bigdata packages. The only major changes they would
> > > > > > receive is when we onboard new services and components to Ambari, else they
> > > > > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > > > > downloaded and installed from HDP repositories.
> > > > > >
> > > > > > We have still not officially finalized the new replacement name for
> > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > > the purpose of bdp-select and conf-select remains the same.
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > > For additional commands, e-mail: dev-help@ambari.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
> Technical decisions shouldn't be done on other places than public mailing lists,
> as described in the "Open Communications" section of [1] and [2].
> So we should conclude the discussion in this mailing list.
> (And with my poor English, I'm not so confident to catch up with your
> fluent talk ;)
I believe , I knew the apache way which you mentioned. We are not going conclude anything which comes to bigtop other than this mailing list.
As there are different opinions on this and took long time, just to brainstorm all the possibilities and pitfalls. Hence asking let's have call so that we can brainstorm. Even after call, everything will be published what we discussed.
I think, whiteboarding will help to catch up with you.
You all the think "bigtop-select" will be best option right..? Can you suggest, how the changes will be also.. like folder, where you suggest to keep this...?
And if the name represents the stack which we are going to deploy should fine I feel.. (if it's not BDP, may be OBDP:OpensourceBigDataPlatform.)
@Viraj Jasani and others any thoughts..?
On 10/07/22, 11:03 AM, "Kengo Seki" <se...@apache.org> wrote:
> Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
Technical decisions shouldn't be done on other places than public mailing lists,
as described in the "Open Communications" section of [1] and [2].
So we should conclude the discussion in this mailing list.
(And with my poor English, I'm not so confident to catch up with your
fluent talk ;)
> FYI. Even looks bigtop used some where also..
Bigtop is ASF's trademark as you can see in the "Apache Bigtop®
software" section of [3].
So it doesn't have the risk of trademark infringement.
[1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ftheapacheway%2Findex.html%23what-makes-the-apache-way-so-hard-to-define&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=wZnePXjGrZV8qKXKnc%2Bitzk1CKAq%2B4tU%2Bk5x9xfbtqo%3D&reserved=0
[2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Fdev%2Fpmc.html%23mailing-list-naming-policy&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1rBTRJ9ojoa1iDQqEyebVVYQMEh5FH9u0lLkiBVE%2FgE%3D&reserved=0
[3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2Flist%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1xktddBWr6aMaWIPHooMuELx4C0INpnl140VSv1dAoQ%3D&reserved=0
Kengo Seki <se...@apache.org>
On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
>
> Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
>
> FYI. Even looks bigtop used some where[1] also..
> 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FBigtop_&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lcwX%2BgrLqAqjPJdVAnWDf8lv7sbI11htDx3QO7VNOXY%3D&reserved=0(Microsoft_product)
>
>
> On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org> wrote:
>
> Thank you for your explanation, Brahma.
> CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
> trademark of Redoop, so they can name the script crh-select without
> problem.
> But regarding BDP for example, I can easily find products that have
> the same name [2][3][4] as you already mentioned, so I'd like to
> recommend bigtop-select for avoiding unnecessary trouble.
> Or, a single and more general word just like conf-select may be less
> troublesome than bdp. How about "stack-select", for example?
>
> [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vEd%2BvoUH%2F6p%2BEmtK4Lhhi8qi3f1YPfdELHeToWR8VnU%3D&reserved=0
> [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EGoGDLI7JSuEksBaReqLny%2BQgI%2Bk0uKhb9%2BJPSf9kDs%3D&reserved=0
> [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=UNbYxvQpXlgK3k80qr8KFHcJZdDw9xhRrY3VlcOWL2Q%3D&reserved=0
> [4]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vy%2BEcsGFs4FP339AN%2B%2F2rCw617Qxd5nbUN41dLRPKRU%3D&reserved=0
>
> Kengo Seki <se...@apache.org>
>
> On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com> wrote:
> >
> > >Do you mean that you're going to name the module (same as "component"
> > >in the Bigtop terminology, I think) bigtop-distro-select,
> > >and still the script in question bdp-select? If so, is there any
> > >reason that the script must be that name?
> > >(No offence, I just want to understand your thoughts and its
> > >background, and avoid the conflict or user's confusion with existing
> > >trademarks or products)
> >
> > Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
> >
> >
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BPe6X6A9%2B0iZj%2BrXGVCEdGp81NbIZOzZ0gHoEPFYjis%3D&reserved=0
> >
> >
> > On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
> >
> > The following concern Masatake mentioned before is an important point,
> > so I talked to Brahma for clarifying his intention on the ASF Slack
> > yesterday.
> >
> > > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > > IIRC, HDP uses convention in which the product version is part of package name
> > > for addressing this.
> >
> > > I don't like to bring the awkward package name convention to Bigtop
> > > at least by default.
> >
> > He's planning to adopt the same mitigation as HDP for now, but he
> > doesn't intend to change the default package naming convention of
> > Bigtop,
> > but just add a new functionality to include an extra part into the
> > package name for avoiding conflict, which is disabled by default.
> >
> > And Brahma, let me confirm about the following reply:
> >
> > > Sure, we can have module name like bigtop-distro-select.
> >
> > Do you mean that you're going to name the module (same as "component"
> > in the Bigtop terminology, I think) bigtop-distro-select,
> > and still the script in question bdp-select? If so, is there any
> > reason that the script must be that name?
> > (No offence, I just want to understand your thoughts and its
> > background, and avoid the conflict or user's confusion with existing
> > trademarks or products)
> >
> > Kengo Seki <se...@apache.org>
> >
> > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
> > <bb...@visa.com.invalid> wrote:
> > >
> > > > The name of stack based no Bigtop should be Bigtop.
> > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> > >
> > > Sure, we can have module name like bigtop-distro-select.
> > > Initially we'll do this separate branch.
> > >
> > >
> > >
> > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >
> > > > I believe it's for project name. isn't it.?
> > >
> > > projects and products.
> > >
> > > > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >
> > > The name of stack based no Bigtop should be Bigtop.
> > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> > >
> > >
> > > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> > > >
> > > > I believe it's for project name. isn't it.?
> > > >
> > > >
> > > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >
> > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >
> > > > Not fine.
> > > > We have a trademark policy.
> > > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VljKIm7VEf31j65Z9qYO3dRvLlHEYzHhjv%2B780tQMFU%3D&reserved=0
> > > >
> > > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> > > > >> Should we avoid unrecognized brand which may be trademark of someone?
> > > > >> ambari-select or bigtop-select should be enough.
> > > > >
> > > > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > > >
> > > > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> > > > >
> > > > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lRrIYUg7AyzKk276YdE5k7p7FyIfKdfdSrE7kHGnZVs%3D&reserved=0
> > > > >
> > > > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C259e0505deb045128ed408da6235c1a7%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637930280293864025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dODih3q2eq2IqjPmK9vArJB9V17HuXon6NzlnU%2BVHSw%3D&reserved=0
> > > > >
> > > > >
> > > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > > >
> > > > > > We have still not officially finalized the new replacement name for
> > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > > the purpose of bdp-select and conf-select remains the same.
> > > > >
> > > > > Should we avoid unrecognized brand which may be trademark of someone?
> > > > > ambari-select or bigtop-select should be enough.
> > > > >
> > > > > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > > > > Hi Ambari/Bigtop dev,
> > > > > >
> > > > > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > > > > so that their rpm installation could be managed independently.
> > > > > > These scripts are a basic necessity in the Ambari framework for the
> > > > > > installation of various Bigdata packages. The only major changes they would
> > > > > > receive is when we onboard new services and components to Ambari, else they
> > > > > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > > > > downloaded and installed from HDP repositories.
> > > > > >
> > > > > > We have still not officially finalized the new replacement name for
> > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > > the purpose of bdp-select and conf-select remains the same.
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > > For additional commands, e-mail: dev-help@ambari.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Kengo Seki <se...@apache.org>.
> Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
Technical decisions shouldn't be done on other places than public mailing lists,
as described in the "Open Communications" section of [1] and [2].
So we should conclude the discussion in this mailing list.
(And with my poor English, I'm not so confident to catch up with your
fluent talk ;)
> FYI. Even looks bigtop used some where also..
Bigtop is ASF's trademark as you can see in the "Apache Bigtop®
software" section of [3].
So it doesn't have the risk of trademark infringement.
[1]: https://www.apache.org/theapacheway/index.html#what-makes-the-apache-way-so-hard-to-define
[2]: https://www.apache.org/dev/pmc.html#mailing-list-naming-policy
[3]: https://www.apache.org/foundation/marks/list/
Kengo Seki <se...@apache.org>
On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
>
> Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
>
> FYI. Even looks bigtop used some where[1] also..
> 1. https://en.wikipedia.org/wiki/Bigtop_(Microsoft_product)
>
>
> On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org> wrote:
>
> Thank you for your explanation, Brahma.
> CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
> trademark of Redoop, so they can name the script crh-select without
> problem.
> But regarding BDP for example, I can easily find products that have
> the same name [2][3][4] as you already mentioned, so I'd like to
> recommend bigtop-select for avoiding unnecessary trouble.
> Or, a single and more general word just like conf-select may be less
> troublesome than bdp. How about "stack-select", for example?
>
> [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994379337%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GGowKe08K0CoMwQsKMA4%2FIE5w%2FC6ouh0affpiusraaU%3D&reserved=0
> [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994379337%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tTQPVQs28P2n08b8qvsbRrwfG4xulzxaalu7XF1AFNE%3D&reserved=0
> [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RN38y2gBsrfxJL%2BA2rR5jh15RL7V%2BP0h8NT00X8YVLs%3D&reserved=0
> [4]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=M6HNTNAi4sWJLBmR%2FVlfumbtvhjUoYR7eYFhg%2FWg0Eo%3D&reserved=0
>
> Kengo Seki <se...@apache.org>
>
> On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com> wrote:
> >
> > >Do you mean that you're going to name the module (same as "component"
> > >in the Bigtop terminology, I think) bigtop-distro-select,
> > >and still the script in question bdp-select? If so, is there any
> > >reason that the script must be that name?
> > >(No offence, I just want to understand your thoughts and its
> > >background, and avoid the conflict or user's confusion with existing
> > >trademarks or products)
> >
> > Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
> >
> >
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vP3NafvMeQyhrpflbPHYtG7gpOzPli8%2FiPm1GxshA5g%3D&reserved=0
> >
> >
> > On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
> >
> > The following concern Masatake mentioned before is an important point,
> > so I talked to Brahma for clarifying his intention on the ASF Slack
> > yesterday.
> >
> > > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > > IIRC, HDP uses convention in which the product version is part of package name
> > > for addressing this.
> >
> > > I don't like to bring the awkward package name convention to Bigtop
> > > at least by default.
> >
> > He's planning to adopt the same mitigation as HDP for now, but he
> > doesn't intend to change the default package naming convention of
> > Bigtop,
> > but just add a new functionality to include an extra part into the
> > package name for avoiding conflict, which is disabled by default.
> >
> > And Brahma, let me confirm about the following reply:
> >
> > > Sure, we can have module name like bigtop-distro-select.
> >
> > Do you mean that you're going to name the module (same as "component"
> > in the Bigtop terminology, I think) bigtop-distro-select,
> > and still the script in question bdp-select? If so, is there any
> > reason that the script must be that name?
> > (No offence, I just want to understand your thoughts and its
> > background, and avoid the conflict or user's confusion with existing
> > trademarks or products)
> >
> > Kengo Seki <se...@apache.org>
> >
> > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
> > <bb...@visa.com.invalid> wrote:
> > >
> > > > The name of stack based no Bigtop should be Bigtop.
> > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> > >
> > > Sure, we can have module name like bigtop-distro-select.
> > > Initially we'll do this separate branch.
> > >
> > >
> > >
> > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >
> > > > I believe it's for project name. isn't it.?
> > >
> > > projects and products.
> > >
> > > > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >
> > > The name of stack based no Bigtop should be Bigtop.
> > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> > >
> > >
> > > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> > > >
> > > > I believe it's for project name. isn't it.?
> > > >
> > > >
> > > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >
> > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >
> > > > Not fine.
> > > > We have a trademark policy.
> > > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Ry1C9%2F3yRgwDAfOxsYUxjAX2nufDkyvgi3pk6YD2y%2F4%3D&reserved=0
> > > >
> > > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> > > > >> Should we avoid unrecognized brand which may be trademark of someone?
> > > > >> ambari-select or bigtop-select should be enough.
> > > > >
> > > > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > > >
> > > > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> > > > >
> > > > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=P6xNjfFVvSIo9ipokO%2Fshg6dOMojqxoPihFJD3vIOIQ%3D&reserved=0
> > > > >
> > > > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zxWOo4vFt1YUkN4kFPOfWqcX2Tguus6MNRff5Rh8FH8%3D&reserved=0
> > > > >
> > > > >
> > > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > > >
> > > > > > We have still not officially finalized the new replacement name for
> > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > > the purpose of bdp-select and conf-select remains the same.
> > > > >
> > > > > Should we avoid unrecognized brand which may be trademark of someone?
> > > > > ambari-select or bigtop-select should be enough.
> > > > >
> > > > > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > > > > Hi Ambari/Bigtop dev,
> > > > > >
> > > > > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > > > > so that their rpm installation could be managed independently.
> > > > > > These scripts are a basic necessity in the Ambari framework for the
> > > > > > installation of various Bigdata packages. The only major changes they would
> > > > > > receive is when we onboard new services and components to Ambari, else they
> > > > > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > > > > downloaded and installed from HDP repositories.
> > > > > >
> > > > > > We have still not officially finalized the new replacement name for
> > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > > the purpose of bdp-select and conf-select remains the same.
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > > For additional commands, e-mail: dev-help@ambari.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Kengo Seki <se...@apache.org>.
> Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
Technical decisions shouldn't be done on other places than public mailing lists,
as described in the "Open Communications" section of [1] and [2].
So we should conclude the discussion in this mailing list.
(And with my poor English, I'm not so confident to catch up with your
fluent talk ;)
> FYI. Even looks bigtop used some where also..
Bigtop is ASF's trademark as you can see in the "Apache Bigtop®
software" section of [3].
So it doesn't have the risk of trademark infringement.
[1]: https://www.apache.org/theapacheway/index.html#what-makes-the-apache-way-so-hard-to-define
[2]: https://www.apache.org/dev/pmc.html#mailing-list-naming-policy
[3]: https://www.apache.org/foundation/marks/list/
Kengo Seki <se...@apache.org>
On Sun, Jul 10, 2022 at 4:11 AM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
>
> Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
>
> FYI. Even looks bigtop used some where[1] also..
> 1. https://en.wikipedia.org/wiki/Bigtop_(Microsoft_product)
>
>
> On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org> wrote:
>
> Thank you for your explanation, Brahma.
> CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
> trademark of Redoop, so they can name the script crh-select without
> problem.
> But regarding BDP for example, I can easily find products that have
> the same name [2][3][4] as you already mentioned, so I'd like to
> recommend bigtop-select for avoiding unnecessary trouble.
> Or, a single and more general word just like conf-select may be less
> troublesome than bdp. How about "stack-select", for example?
>
> [1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994379337%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GGowKe08K0CoMwQsKMA4%2FIE5w%2FC6ouh0affpiusraaU%3D&reserved=0
> [2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994379337%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tTQPVQs28P2n08b8qvsbRrwfG4xulzxaalu7XF1AFNE%3D&reserved=0
> [3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RN38y2gBsrfxJL%2BA2rR5jh15RL7V%2BP0h8NT00X8YVLs%3D&reserved=0
> [4]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=M6HNTNAi4sWJLBmR%2FVlfumbtvhjUoYR7eYFhg%2FWg0Eo%3D&reserved=0
>
> Kengo Seki <se...@apache.org>
>
> On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com> wrote:
> >
> > >Do you mean that you're going to name the module (same as "component"
> > >in the Bigtop terminology, I think) bigtop-distro-select,
> > >and still the script in question bdp-select? If so, is there any
> > >reason that the script must be that name?
> > >(No offence, I just want to understand your thoughts and its
> > >background, and avoid the conflict or user's confusion with existing
> > >trademarks or products)
> >
> > Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
> >
> >
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vP3NafvMeQyhrpflbPHYtG7gpOzPli8%2FiPm1GxshA5g%3D&reserved=0
> >
> >
> > On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
> >
> > The following concern Masatake mentioned before is an important point,
> > so I talked to Brahma for clarifying his intention on the ASF Slack
> > yesterday.
> >
> > > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > > IIRC, HDP uses convention in which the product version is part of package name
> > > for addressing this.
> >
> > > I don't like to bring the awkward package name convention to Bigtop
> > > at least by default.
> >
> > He's planning to adopt the same mitigation as HDP for now, but he
> > doesn't intend to change the default package naming convention of
> > Bigtop,
> > but just add a new functionality to include an extra part into the
> > package name for avoiding conflict, which is disabled by default.
> >
> > And Brahma, let me confirm about the following reply:
> >
> > > Sure, we can have module name like bigtop-distro-select.
> >
> > Do you mean that you're going to name the module (same as "component"
> > in the Bigtop terminology, I think) bigtop-distro-select,
> > and still the script in question bdp-select? If so, is there any
> > reason that the script must be that name?
> > (No offence, I just want to understand your thoughts and its
> > background, and avoid the conflict or user's confusion with existing
> > trademarks or products)
> >
> > Kengo Seki <se...@apache.org>
> >
> > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
> > <bb...@visa.com.invalid> wrote:
> > >
> > > > The name of stack based no Bigtop should be Bigtop.
> > > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> > >
> > > Sure, we can have module name like bigtop-distro-select.
> > > Initially we'll do this separate branch.
> > >
> > >
> > >
> > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >
> > > > I believe it's for project name. isn't it.?
> > >
> > > projects and products.
> > >
> > > > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >
> > > The name of stack based no Bigtop should be Bigtop.
> > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> > >
> > >
> > > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> > > >
> > > > I believe it's for project name. isn't it.?
> > > >
> > > >
> > > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >
> > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > >
> > > > Not fine.
> > > > We have a trademark policy.
> > > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Ry1C9%2F3yRgwDAfOxsYUxjAX2nufDkyvgi3pk6YD2y%2F4%3D&reserved=0
> > > >
> > > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> > > > >> Should we avoid unrecognized brand which may be trademark of someone?
> > > > >> ambari-select or bigtop-select should be enough.
> > > > >
> > > > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > > >
> > > > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> > > > >
> > > > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=P6xNjfFVvSIo9ipokO%2Fshg6dOMojqxoPihFJD3vIOIQ%3D&reserved=0
> > > > >
> > > > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zxWOo4vFt1YUkN4kFPOfWqcX2Tguus6MNRff5Rh8FH8%3D&reserved=0
> > > > >
> > > > >
> > > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > > >
> > > > > > We have still not officially finalized the new replacement name for
> > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > > the purpose of bdp-select and conf-select remains the same.
> > > > >
> > > > > Should we avoid unrecognized brand which may be trademark of someone?
> > > > > ambari-select or bigtop-select should be enough.
> > > > >
> > > > > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > > > > Hi Ambari/Bigtop dev,
> > > > > >
> > > > > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > > > > so that their rpm installation could be managed independently.
> > > > > > These scripts are a basic necessity in the Ambari framework for the
> > > > > > installation of various Bigdata packages. The only major changes they would
> > > > > > receive is when we onboard new services and components to Ambari, else they
> > > > > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > > > > downloaded and installed from HDP repositories.
> > > > > >
> > > > > > We have still not officially finalized the new replacement name for
> > > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > > the purpose of bdp-select and conf-select remains the same.
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > > For additional commands, e-mail: dev-help@ambari.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
FYI. Even looks bigtop used some where[1] also..
1. https://en.wikipedia.org/wiki/Bigtop_(Microsoft_product)
On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org> wrote:
Thank you for your explanation, Brahma.
CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
trademark of Redoop, so they can name the script crh-select without
problem.
But regarding BDP for example, I can easily find products that have
the same name [2][3][4] as you already mentioned, so I'd like to
recommend bigtop-select for avoiding unnecessary trouble.
Or, a single and more general word just like conf-select may be less
troublesome than bdp. How about "stack-select", for example?
[1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994379337%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GGowKe08K0CoMwQsKMA4%2FIE5w%2FC6ouh0affpiusraaU%3D&reserved=0
[2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994379337%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tTQPVQs28P2n08b8qvsbRrwfG4xulzxaalu7XF1AFNE%3D&reserved=0
[3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RN38y2gBsrfxJL%2BA2rR5jh15RL7V%2BP0h8NT00X8YVLs%3D&reserved=0
[4]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=M6HNTNAi4sWJLBmR%2FVlfumbtvhjUoYR7eYFhg%2FWg0Eo%3D&reserved=0
Kengo Seki <se...@apache.org>
On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com> wrote:
>
> >Do you mean that you're going to name the module (same as "component"
> >in the Bigtop terminology, I think) bigtop-distro-select,
> >and still the script in question bdp-select? If so, is there any
> >reason that the script must be that name?
> >(No offence, I just want to understand your thoughts and its
> >background, and avoid the conflict or user's confusion with existing
> >trademarks or products)
>
> Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
>
>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vP3NafvMeQyhrpflbPHYtG7gpOzPli8%2FiPm1GxshA5g%3D&reserved=0
>
>
> On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
>
> The following concern Masatake mentioned before is an important point,
> so I talked to Brahma for clarifying his intention on the ASF Slack
> yesterday.
>
> > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > IIRC, HDP uses convention in which the product version is part of package name
> > for addressing this.
>
> > I don't like to bring the awkward package name convention to Bigtop
> > at least by default.
>
> He's planning to adopt the same mitigation as HDP for now, but he
> doesn't intend to change the default package naming convention of
> Bigtop,
> but just add a new functionality to include an extra part into the
> package name for avoiding conflict, which is disabled by default.
>
> And Brahma, let me confirm about the following reply:
>
> > Sure, we can have module name like bigtop-distro-select.
>
> Do you mean that you're going to name the module (same as "component"
> in the Bigtop terminology, I think) bigtop-distro-select,
> and still the script in question bdp-select? If so, is there any
> reason that the script must be that name?
> (No offence, I just want to understand your thoughts and its
> background, and avoid the conflict or user's confusion with existing
> trademarks or products)
>
> Kengo Seki <se...@apache.org>
>
> On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
> >
> > > The name of stack based no Bigtop should be Bigtop.
> > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> >
> > Sure, we can have module name like bigtop-distro-select.
> > Initially we'll do this separate branch.
> >
> >
> >
> > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >
> > > I believe it's for project name. isn't it.?
> >
> > projects and products.
> >
> > > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> >
> > The name of stack based no Bigtop should be Bigtop.
> > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> >
> >
> > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> > >
> > > I believe it's for project name. isn't it.?
> > >
> > >
> > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >
> > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >
> > > Not fine.
> > > We have a trademark policy.
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Ry1C9%2F3yRgwDAfOxsYUxjAX2nufDkyvgi3pk6YD2y%2F4%3D&reserved=0
> > >
> > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> > > >> Should we avoid unrecognized brand which may be trademark of someone?
> > > >> ambari-select or bigtop-select should be enough.
> > > >
> > > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > >
> > > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> > > >
> > > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=P6xNjfFVvSIo9ipokO%2Fshg6dOMojqxoPihFJD3vIOIQ%3D&reserved=0
> > > >
> > > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zxWOo4vFt1YUkN4kFPOfWqcX2Tguus6MNRff5Rh8FH8%3D&reserved=0
> > > >
> > > >
> > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >
> > > > > We have still not officially finalized the new replacement name for
> > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > the purpose of bdp-select and conf-select remains the same.
> > > >
> > > > Should we avoid unrecognized brand which may be trademark of someone?
> > > > ambari-select or bigtop-select should be enough.
> > > >
> > > > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > > > Hi Ambari/Bigtop dev,
> > > > >
> > > > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > > > so that their rpm installation could be managed independently.
> > > > > These scripts are a basic necessity in the Ambari framework for the
> > > > > installation of various Bigdata packages. The only major changes they would
> > > > > receive is when we onboard new services and components to Ambari, else they
> > > > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > > > downloaded and installed from HDP repositories.
> > > > >
> > > > > We have still not officially finalized the new replacement name for
> > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > the purpose of bdp-select and conf-select remains the same.
> > > > >
> > > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by xiaojun tong <to...@gmail.com>.
From the perspective of brand publicity and protection, the name bigtop is
more appropriate. Directly link the ambari and bigtop projects.
Kengo Seki <se...@apache.org> 于2022年7月8日周五 22:36写道：
> Thank you for your explanation, Brahma.
> CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
> trademark of Redoop, so they can name the script crh-select without
> problem.
> But regarding BDP for example, I can easily find products that have
> the same name [2][3][4] as you already mentioned, so I'd like to
> recommend bigtop-select for avoiding unnecessary trouble.
> Or, a single and more general word just like conf-select may be less
> troublesome than bdp. How about "stack-select", for example?
>
> [1]: https://docs.redoop.com/
> [2]: https://datumstudio.jp/en/bigdataplatform/
> [3]:
> https://help.talend.com/r/en-US/8.0/studio-getting-started-guide-big-data-platform/introduction
> [4]: https://www.harmony-alliance.eu/bigdata-platform/big-data-platform
>
> Kengo Seki <se...@apache.org>
>
> On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com>
> wrote:
> >
> > >Do you mean that you're going to name the module (same as
> "component"
> > >in the Bigtop terminology, I think) bigtop-distro-select,
> > >and still the script in question bdp-select? If so, is there any
> > >reason that the script must be that name?
> > >(No offence, I just want to understand your thoughts and its
> > >background, and avoid the conflict or user's confusion with existing
> > >trademarks or products)
> >
> > Thanks @Kengo Seki for consolidating all the concerns. Name should
> represent the stack which includes all the components hence planning to
> have like bdp,bds...and this only one file like below[1] which has done
> redoop.
> >
> >
> >
> https://github.com/redoop/bigtop/tree/e5f9fe81773180159d291f18ec366ac8bfa4d6d2/bigtop-packages/src/common/ambari-mpacks/selector
> >
> >
> > On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
> >
> > The following concern Masatake mentioned before is an important
> point,
> > so I talked to Brahma for clarifying his intention on the ASF Slack
> > yesterday.
> >
> > > Multiple versions of the same package (deb/rpm) can not be
> installed at the same time.
> > > IIRC, HDP uses convention in which the product version is part of
> package name
> > > for addressing this.
> >
> > > I don't like to bring the awkward package name convention to Bigtop
> > > at least by default.
> >
> > He's planning to adopt the same mitigation as HDP for now, but he
> > doesn't intend to change the default package naming convention of
> > Bigtop,
> > but just add a new functionality to include an extra part into the
> > package name for avoiding conflict, which is disabled by default.
> >
> > And Brahma, let me confirm about the following reply:
> >
> > > Sure, we can have module name like bigtop-distro-select.
> >
> > Do you mean that you're going to name the module (same as "component"
> > in the Bigtop terminology, I think) bigtop-distro-select,
> > and still the script in question bdp-select? If so, is there any
> > reason that the script must be that name?
> > (No offence, I just want to understand your thoughts and its
> > background, and avoid the conflict or user's confusion with existing
> > trademarks or products)
> >
> > Kengo Seki <se...@apache.org>
> >
> > On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
> > <bb...@visa.com.invalid> wrote:
> > >
> > > > The name of stack based no Bigtop should be Bigtop.
> > > > If you can not accept the name like bigtop-*, the work
> should done outside of Bigtop.
> > > > I will cast -1 if someone submit a patch to add a module with
> the name spoiling branding.
> > >
> > > Sure, we can have module name like bigtop-distro-select.
> > > Initially we'll do this separate branch.
> > >
> > >
> > >
> > > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.co.jp> wrote:
> > >
> > > > I believe it's for project name. isn't it.?
> > >
> > > projects and products.
> > >
> > > > IMO, We need to create folders and refer stacknames so
> ambari-select,bigtop-select wn't looks good.
> > >
> > > The name of stack based no Bigtop should be Bigtop.
> > > If you can not accept the name like bigtop-*, the work should
> done outside of Bigtop.
> > > I will cast -1 if someone submit a patch to add a module with
> the name spoiling branding.
> > >
> > >
> > > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> > > >
> > > > I believe it's for project name. isn't it.?
> > > >
> > > >
> > > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.co.jp> wrote:
> > > >
> > > > > But As we are not releasing as enterprise should be
> fine I think. IMO, We need to create folders and refer stacknames so
> ambari-select,bigtop-select wn't looks good.
> > > >
> > > > Not fine.
> > > > We have a trademark policy.
> > > >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=uLAUZWy9EpJRNUYeuhSL951CbEdtLYFxrOFK%2BWW5Elg%3D&reserved=0
> > > >
> > > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> > > > >> Should we avoid unrecognized brand which may be
> trademark of someone?
> > > > >> ambari-select or bigtop-select should be enough.
> > > > >
> > > > > Not sure, where to confirm whether there is already
> trademark. When I googled found so many.
> > > > > But As we are not releasing as enterprise should be
> fine I think. IMO, We need to create folders and refer stacknames so
> ambari-select,bigtop-select wn't looks good.
> > > > > May be you can refer the initial proposal [2] where I
> mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > > >
> > > > > Finally thanks a bunch for long healthy discussions
> on this. Mostly we all same page now.
> > > > >
> > > > > 1.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8NSFFz1Ko1oZFar%2Bz0%2FML9LgJHUNf0bLw7VVbtGP1ck%3D&reserved=0
> > > > >
> > > > > 2.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=I%2BbQoYUU5upYS1VQT1rux5ZZhh%2Fx1yeyD%2BnLW8HJwkw%3D&reserved=0
> > > > >
> > > > >
> > > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.co.jp> wrote:
> > > > >
> > > > > > We have still not officially finalized the new
> replacement name for
> > > > > > hdp-select, it would likely be bdp-select
> (bdp: BigData Platform). However,
> > > > > > the purpose of bdp-select and conf-select
> remains the same.
> > > > >
> > > > > Should we avoid unrecognized brand which may be
> trademark of someone?
> > > > > ambari-select or bigtop-select should be enough.
> > > > >
> > > > > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > > > > Hi Ambari/Bigtop dev,
> > > > > >
> > > > > > As per the new roadmap of Apache Ambari, we
> would like to propose moving
> > > > > > certain scripts (previously known as
> hdp-select and conf-select) to Bigtop
> > > > > > so that their rpm installation could be
> managed independently.
> > > > > > These scripts are a basic necessity in the
> Ambari framework for the
> > > > > > installation of various Bigdata packages. The
> only major changes they would
> > > > > > receive is when we onboard new services and
> components to Ambari, else they
> > > > > > usually do not receive updates. In the past,
> we used to get hdp-select rpm
> > > > > > downloaded and installed from HDP repositories.
> > > > > >
> > > > > > We have still not officially finalized the new
> replacement name for
> > > > > > hdp-select, it would likely be bdp-select
> (bdp: BigData Platform). However,
> > > > > > the purpose of bdp-select and conf-select
> remains the same.
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > > For additional commands, e-mail: dev-help@ambari.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
> >
>
--
tongxiaojun
website: http://www.redoop.com <http://www.redhadoop.com>
mail: tongxiaojun@gmail.com
tel: 18613807209
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
Looks we had so much discussed here, Let's try to conclude. Can we've one call on this and finalize this..?
FYI. Even looks bigtop used some where[1] also..
1. https://en.wikipedia.org/wiki/Bigtop_(Microsoft_product)
On 08/07/22, 8:06 PM, "Kengo Seki" <se...@apache.org> wrote:
Thank you for your explanation, Brahma.
CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
trademark of Redoop, so they can name the script crh-select without
problem.
But regarding BDP for example, I can easily find products that have
the same name [2][3][4] as you already mentioned, so I'd like to
recommend bigtop-select for avoiding unnecessary trouble.
Or, a single and more general word just like conf-select may be less
troublesome than bdp. How about "stack-select", for example?
[1]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.redoop.com%2F&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994379337%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GGowKe08K0CoMwQsKMA4%2FIE5w%2FC6ouh0affpiusraaU%3D&reserved=0
[2]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatumstudio.jp%2Fen%2Fbigdataplatform%2F&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994379337%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tTQPVQs28P2n08b8qvsbRrwfG4xulzxaalu7XF1AFNE%3D&reserved=0
[3]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.talend.com%2Fr%2Fen-US%2F8.0%2Fstudio-getting-started-guide-big-data-platform%2Fintroduction&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RN38y2gBsrfxJL%2BA2rR5jh15RL7V%2BP0h8NT00X8YVLs%3D&reserved=0
[4]: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.harmony-alliance.eu%2Fbigdata-platform%2Fbig-data-platform&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=M6HNTNAi4sWJLBmR%2FVlfumbtvhjUoYR7eYFhg%2FWg0Eo%3D&reserved=0
Kengo Seki <se...@apache.org>
On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com> wrote:
>
> >Do you mean that you're going to name the module (same as "component"
> >in the Bigtop terminology, I think) bigtop-distro-select,
> >and still the script in question bdp-select? If so, is there any
> >reason that the script must be that name?
> >(No offence, I just want to understand your thoughts and its
> >background, and avoid the conflict or user's confusion with existing
> >trademarks or products)
>
> Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
>
>
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredoop%2Fbigtop%2Ftree%2Fe5f9fe81773180159d291f18ec366ac8bfa4d6d2%2Fbigtop-packages%2Fsrc%2Fcommon%2Fambari-mpacks%2Fselector&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vP3NafvMeQyhrpflbPHYtG7gpOzPli8%2FiPm1GxshA5g%3D&reserved=0
>
>
> On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
>
> The following concern Masatake mentioned before is an important point,
> so I talked to Brahma for clarifying his intention on the ASF Slack
> yesterday.
>
> > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > IIRC, HDP uses convention in which the product version is part of package name
> > for addressing this.
>
> > I don't like to bring the awkward package name convention to Bigtop
> > at least by default.
>
> He's planning to adopt the same mitigation as HDP for now, but he
> doesn't intend to change the default package naming convention of
> Bigtop,
> but just add a new functionality to include an extra part into the
> package name for avoiding conflict, which is disabled by default.
>
> And Brahma, let me confirm about the following reply:
>
> > Sure, we can have module name like bigtop-distro-select.
>
> Do you mean that you're going to name the module (same as "component"
> in the Bigtop terminology, I think) bigtop-distro-select,
> and still the script in question bdp-select? If so, is there any
> reason that the script must be that name?
> (No offence, I just want to understand your thoughts and its
> background, and avoid the conflict or user's confusion with existing
> trademarks or products)
>
> Kengo Seki <se...@apache.org>
>
> On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
> >
> > > The name of stack based no Bigtop should be Bigtop.
> > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> >
> > Sure, we can have module name like bigtop-distro-select.
> > Initially we'll do this separate branch.
> >
> >
> >
> > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >
> > > I believe it's for project name. isn't it.?
> >
> > projects and products.
> >
> > > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> >
> > The name of stack based no Bigtop should be Bigtop.
> > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> >
> >
> > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> > >
> > > I believe it's for project name. isn't it.?
> > >
> > >
> > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >
> > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >
> > > Not fine.
> > > We have a trademark policy.
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Ry1C9%2F3yRgwDAfOxsYUxjAX2nufDkyvgi3pk6YD2y%2F4%3D&reserved=0
> > >
> > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> > > >> Should we avoid unrecognized brand which may be trademark of someone?
> > > >> ambari-select or bigtop-select should be enough.
> > > >
> > > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > >
> > > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> > > >
> > > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=P6xNjfFVvSIo9ipokO%2Fshg6dOMojqxoPihFJD3vIOIQ%3D&reserved=0
> > > >
> > > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C5710428143074e43882708da60ef4387%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637928877994535472%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zxWOo4vFt1YUkN4kFPOfWqcX2Tguus6MNRff5Rh8FH8%3D&reserved=0
> > > >
> > > >
> > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >
> > > > > We have still not officially finalized the new replacement name for
> > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > the purpose of bdp-select and conf-select remains the same.
> > > >
> > > > Should we avoid unrecognized brand which may be trademark of someone?
> > > > ambari-select or bigtop-select should be enough.
> > > >
> > > > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > > > Hi Ambari/Bigtop dev,
> > > > >
> > > > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > > > so that their rpm installation could be managed independently.
> > > > > These scripts are a basic necessity in the Ambari framework for the
> > > > > installation of various Bigdata packages. The only major changes they would
> > > > > receive is when we onboard new services and components to Ambari, else they
> > > > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > > > downloaded and installed from HDP repositories.
> > > > >
> > > > > We have still not officially finalized the new replacement name for
> > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > the purpose of bdp-select and conf-select remains the same.
> > > > >
> > > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Kengo Seki <se...@apache.org>.
Thank you for your explanation, Brahma.
CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
trademark of Redoop, so they can name the script crh-select without
problem.
But regarding BDP for example, I can easily find products that have
the same name [2][3][4] as you already mentioned, so I'd like to
recommend bigtop-select for avoiding unnecessary trouble.
Or, a single and more general word just like conf-select may be less
troublesome than bdp. How about "stack-select", for example?
[1]: https://docs.redoop.com/
[2]: https://datumstudio.jp/en/bigdataplatform/
[3]: https://help.talend.com/r/en-US/8.0/studio-getting-started-guide-big-data-platform/introduction
[4]: https://www.harmony-alliance.eu/bigdata-platform/big-data-platform
Kengo Seki <se...@apache.org>
On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com> wrote:
>
> >Do you mean that you're going to name the module (same as "component"
> >in the Bigtop terminology, I think) bigtop-distro-select,
> >and still the script in question bdp-select? If so, is there any
> >reason that the script must be that name?
> >(No offence, I just want to understand your thoughts and its
> >background, and avoid the conflict or user's confusion with existing
> >trademarks or products)
>
> Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
>
>
> https://github.com/redoop/bigtop/tree/e5f9fe81773180159d291f18ec366ac8bfa4d6d2/bigtop-packages/src/common/ambari-mpacks/selector
>
>
> On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
>
> The following concern Masatake mentioned before is an important point,
> so I talked to Brahma for clarifying his intention on the ASF Slack
> yesterday.
>
> > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > IIRC, HDP uses convention in which the product version is part of package name
> > for addressing this.
>
> > I don't like to bring the awkward package name convention to Bigtop
> > at least by default.
>
> He's planning to adopt the same mitigation as HDP for now, but he
> doesn't intend to change the default package naming convention of
> Bigtop,
> but just add a new functionality to include an extra part into the
> package name for avoiding conflict, which is disabled by default.
>
> And Brahma, let me confirm about the following reply:
>
> > Sure, we can have module name like bigtop-distro-select.
>
> Do you mean that you're going to name the module (same as "component"
> in the Bigtop terminology, I think) bigtop-distro-select,
> and still the script in question bdp-select? If so, is there any
> reason that the script must be that name?
> (No offence, I just want to understand your thoughts and its
> background, and avoid the conflict or user's confusion with existing
> trademarks or products)
>
> Kengo Seki <se...@apache.org>
>
> On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
> >
> > > The name of stack based no Bigtop should be Bigtop.
> > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> >
> > Sure, we can have module name like bigtop-distro-select.
> > Initially we'll do this separate branch.
> >
> >
> >
> > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >
> > > I believe it's for project name. isn't it.?
> >
> > projects and products.
> >
> > > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> >
> > The name of stack based no Bigtop should be Bigtop.
> > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> >
> >
> > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> > >
> > > I believe it's for project name. isn't it.?
> > >
> > >
> > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >
> > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >
> > > Not fine.
> > > We have a trademark policy.
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=uLAUZWy9EpJRNUYeuhSL951CbEdtLYFxrOFK%2BWW5Elg%3D&reserved=0
> > >
> > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> > > >> Should we avoid unrecognized brand which may be trademark of someone?
> > > >> ambari-select or bigtop-select should be enough.
> > > >
> > > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > >
> > > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> > > >
> > > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8NSFFz1Ko1oZFar%2Bz0%2FML9LgJHUNf0bLw7VVbtGP1ck%3D&reserved=0
> > > >
> > > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=I%2BbQoYUU5upYS1VQT1rux5ZZhh%2Fx1yeyD%2BnLW8HJwkw%3D&reserved=0
> > > >
> > > >
> > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >
> > > > > We have still not officially finalized the new replacement name for
> > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > the purpose of bdp-select and conf-select remains the same.
> > > >
> > > > Should we avoid unrecognized brand which may be trademark of someone?
> > > > ambari-select or bigtop-select should be enough.
> > > >
> > > > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > > > Hi Ambari/Bigtop dev,
> > > > >
> > > > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > > > so that their rpm installation could be managed independently.
> > > > > These scripts are a basic necessity in the Ambari framework for the
> > > > > installation of various Bigdata packages. The only major changes they would
> > > > > receive is when we onboard new services and components to Ambari, else they
> > > > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > > > downloaded and installed from HDP repositories.
> > > > >
> > > > > We have still not officially finalized the new replacement name for
> > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > the purpose of bdp-select and conf-select remains the same.
> > > > >
> > > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Kengo Seki <se...@apache.org>.
Thank you for your explanation, Brahma.
CRH (abbreviation of "CHINA REDOOP HYPERLOOP" [1]) is supposed to be a
trademark of Redoop, so they can name the script crh-select without
problem.
But regarding BDP for example, I can easily find products that have
the same name [2][3][4] as you already mentioned, so I'd like to
recommend bigtop-select for avoiding unnecessary trouble.
Or, a single and more general word just like conf-select may be less
troublesome than bdp. How about "stack-select", for example?
[1]: https://docs.redoop.com/
[2]: https://datumstudio.jp/en/bigdataplatform/
[3]: https://help.talend.com/r/en-US/8.0/studio-getting-started-guide-big-data-platform/introduction
[4]: https://www.harmony-alliance.eu/bigdata-platform/big-data-platform
Kengo Seki <se...@apache.org>
On Fri, Jul 8, 2022 at 2:51 AM Battula, Brahma Reddy <bb...@visa.com> wrote:
>
> >Do you mean that you're going to name the module (same as "component"
> >in the Bigtop terminology, I think) bigtop-distro-select,
> >and still the script in question bdp-select? If so, is there any
> >reason that the script must be that name?
> >(No offence, I just want to understand your thoughts and its
> >background, and avoid the conflict or user's confusion with existing
> >trademarks or products)
>
> Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
>
>
> https://github.com/redoop/bigtop/tree/e5f9fe81773180159d291f18ec366ac8bfa4d6d2/bigtop-packages/src/common/ambari-mpacks/selector
>
>
> On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
>
> The following concern Masatake mentioned before is an important point,
> so I talked to Brahma for clarifying his intention on the ASF Slack
> yesterday.
>
> > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > IIRC, HDP uses convention in which the product version is part of package name
> > for addressing this.
>
> > I don't like to bring the awkward package name convention to Bigtop
> > at least by default.
>
> He's planning to adopt the same mitigation as HDP for now, but he
> doesn't intend to change the default package naming convention of
> Bigtop,
> but just add a new functionality to include an extra part into the
> package name for avoiding conflict, which is disabled by default.
>
> And Brahma, let me confirm about the following reply:
>
> > Sure, we can have module name like bigtop-distro-select.
>
> Do you mean that you're going to name the module (same as "component"
> in the Bigtop terminology, I think) bigtop-distro-select,
> and still the script in question bdp-select? If so, is there any
> reason that the script must be that name?
> (No offence, I just want to understand your thoughts and its
> background, and avoid the conflict or user's confusion with existing
> trademarks or products)
>
> Kengo Seki <se...@apache.org>
>
> On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
> >
> > > The name of stack based no Bigtop should be Bigtop.
> > > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> >
> > Sure, we can have module name like bigtop-distro-select.
> > Initially we'll do this separate branch.
> >
> >
> >
> > On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >
> > > I believe it's for project name. isn't it.?
> >
> > projects and products.
> >
> > > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> >
> > The name of stack based no Bigtop should be Bigtop.
> > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
> >
> >
> > On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> > >
> > > I believe it's for project name. isn't it.?
> > >
> > >
> > > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >
> > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > >
> > > Not fine.
> > > We have a trademark policy.
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=uLAUZWy9EpJRNUYeuhSL951CbEdtLYFxrOFK%2BWW5Elg%3D&reserved=0
> > >
> > > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> > > >> Should we avoid unrecognized brand which may be trademark of someone?
> > > >> ambari-select or bigtop-select should be enough.
> > > >
> > > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > > >
> > > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> > > >
> > > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8NSFFz1Ko1oZFar%2Bz0%2FML9LgJHUNf0bLw7VVbtGP1ck%3D&reserved=0
> > > >
> > > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=I%2BbQoYUU5upYS1VQT1rux5ZZhh%2Fx1yeyD%2BnLW8HJwkw%3D&reserved=0
> > > >
> > > >
> > > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > > >
> > > > > We have still not officially finalized the new replacement name for
> > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > the purpose of bdp-select and conf-select remains the same.
> > > >
> > > > Should we avoid unrecognized brand which may be trademark of someone?
> > > > ambari-select or bigtop-select should be enough.
> > > >
> > > > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > > > Hi Ambari/Bigtop dev,
> > > > >
> > > > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > > > so that their rpm installation could be managed independently.
> > > > > These scripts are a basic necessity in the Ambari framework for the
> > > > > installation of various Bigdata packages. The only major changes they would
> > > > > receive is when we onboard new services and components to Ambari, else they
> > > > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > > > downloaded and installed from HDP repositories.
> > > > >
> > > > > We have still not officially finalized the new replacement name for
> > > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > > the purpose of bdp-select and conf-select remains the same.
> > > > >
> > > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> > For additional commands, e-mail: dev-help@ambari.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
>Do you mean that you're going to name the module (same as "component"
>in the Bigtop terminology, I think) bigtop-distro-select,
>and still the script in question bdp-select? If so, is there any
>reason that the script must be that name?
>(No offence, I just want to understand your thoughts and its
>background, and avoid the conflict or user's confusion with existing
>trademarks or products)
Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
https://github.com/redoop/bigtop/tree/e5f9fe81773180159d291f18ec366ac8bfa4d6d2/bigtop-packages/src/common/ambari-mpacks/selector
On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
The following concern Masatake mentioned before is an important point,
so I talked to Brahma for clarifying his intention on the ASF Slack
yesterday.
> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> IIRC, HDP uses convention in which the product version is part of package name
> for addressing this.
> I don't like to bring the awkward package name convention to Bigtop
> at least by default.
He's planning to adopt the same mitigation as HDP for now, but he
doesn't intend to change the default package naming convention of
Bigtop,
but just add a new functionality to include an extra part into the
package name for avoiding conflict, which is disabled by default.
And Brahma, let me confirm about the following reply:
> Sure, we can have module name like bigtop-distro-select.
Do you mean that you're going to name the module (same as "component"
in the Bigtop terminology, I think) bigtop-distro-select,
and still the script in question bdp-select? If so, is there any
reason that the script must be that name?
(No offence, I just want to understand your thoughts and its
background, and avoid the conflict or user's confusion with existing
trademarks or products)
Kengo Seki <se...@apache.org>
On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
>
> > The name of stack based no Bigtop should be Bigtop.
> > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>
> Sure, we can have module name like bigtop-distro-select.
> Initially we'll do this separate branch.
>
>
>
> On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>
> > I believe it's for project name. isn't it.?
>
> projects and products.
>
> > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>
> The name of stack based no Bigtop should be Bigtop.
> If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>
>
> On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> >
> > I believe it's for project name. isn't it.?
> >
> >
> > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >
> > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> >
> > Not fine.
> > We have a trademark policy.
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=uLAUZWy9EpJRNUYeuhSL951CbEdtLYFxrOFK%2BWW5Elg%3D&reserved=0
> >
> > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> > >> Should we avoid unrecognized brand which may be trademark of someone?
> > >> ambari-select or bigtop-select should be enough.
> > >
> > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > >
> > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> > >
> > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8NSFFz1Ko1oZFar%2Bz0%2FML9LgJHUNf0bLw7VVbtGP1ck%3D&reserved=0
> > >
> > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=I%2BbQoYUU5upYS1VQT1rux5ZZhh%2Fx1yeyD%2BnLW8HJwkw%3D&reserved=0
> > >
> > >
> > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >
> > > > We have still not officially finalized the new replacement name for
> > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > the purpose of bdp-select and conf-select remains the same.
> > >
> > > Should we avoid unrecognized brand which may be trademark of someone?
> > > ambari-select or bigtop-select should be enough.
> > >
> > > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > > Hi Ambari/Bigtop dev,
> > > >
> > > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > > so that their rpm installation could be managed independently.
> > > > These scripts are a basic necessity in the Ambari framework for the
> > > > installation of various Bigdata packages. The only major changes they would
> > > > receive is when we onboard new services and components to Ambari, else they
> > > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > > downloaded and installed from HDP repositories.
> > > >
> > > > We have still not officially finalized the new replacement name for
> > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > the purpose of bdp-select and conf-select remains the same.
> > > >
> > >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by 吴治国 <wz...@163.com>.
>> I’d like to propose BGTP as stack name(already used in Bigtop Ambari Mpack) with bgtp-select,
>
> It is a good time to get rid of useless abbreviation.
> Why not BIGTOP?
BIGTOP with bigtop-select works for me too, but the mpack is using BGTP as stack name now.
Best Regards,
Zhiguo Wu
> On Jul 7, 2022, at 10:59, Masatake Iwasaki <iw...@oss.nttdata.co.jp> wrote:
>
>> I’d like to propose BGTP as stack name(already used in Bigtop Ambari Mpack) with bgtp-select,
>
> It is a good time to get rid of useless abbreviation.
> Why not BIGTOP?
>
> On 2022/07/07 11:07, 吴治国 wrote:
>>>> Sure, we can have module name like bigtop-distro-select.
>>>
>>> Do you mean that you're going to name the module (same as "component"
>>> in the Bigtop terminology, I think) bigtop-distro-select,
>>> and still the script in question bdp-select? If so, is there any
>>> reason that the script must be that name?
>>> (No offence, I just want to understand your thoughts and its
>>> background, and avoid the conflict or user's confusion with existing
>>> trademarks or products)
>> I’d like to propose BGTP as stack name(already used in Bigtop Ambari Mpack) with bgtp-select, BDP(Bigtop Data Platform) with bdp-select or Bigtop with bigtop-select.
>> BDP(Big Data Platform) with bigtop-distro-select confuse me.
>> Best Regards,
>> Zhiguo Wu
>>> On Jul 7, 2022, at 08:37, Kengo Seki <se...@apache.org> wrote:
>>>
>>> The following concern Masatake mentioned before is an important point,
>>> so I talked to Brahma for clarifying his intention on the ASF Slack
>>> yesterday.
>>>
>>>> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
>>>> IIRC, HDP uses convention in which the product version is part of package name
>>>> for addressing this.
>>>
>>>> I don't like to bring the awkward package name convention to Bigtop
>>>> at least by default.
>>>
>>> He's planning to adopt the same mitigation as HDP for now, but he
>>> doesn't intend to change the default package naming convention of
>>> Bigtop,
>>> but just add a new functionality to include an extra part into the
>>> package name for avoiding conflict, which is disabled by default.
>>>
>>> And Brahma, let me confirm about the following reply:
>>>
>>>> Sure, we can have module name like bigtop-distro-select.
>>>
>>> Do you mean that you're going to name the module (same as "component"
>>> in the Bigtop terminology, I think) bigtop-distro-select,
>>> and still the script in question bdp-select? If so, is there any
>>> reason that the script must be that name?
>>> (No offence, I just want to understand your thoughts and its
>>> background, and avoid the conflict or user's confusion with existing
>>> trademarks or products)
>>>
>>> Kengo Seki <se...@apache.org>
>>>
>>> On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
>>> <bb...@visa.com.invalid> wrote:
>>>>
>>>>> The name of stack based no Bigtop should be Bigtop.
>>>>> If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>>>>> I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>>>>
>>>> Sure, we can have module name like bigtop-distro-select.
>>>> Initially we'll do this separate branch.
>>>>
>>>>
>>>>
>>>> On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>>
>>>>> I believe it's for project name. isn't it.?
>>>>
>>>> projects and products.
>>>>
>>>>> IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>>>>
>>>> The name of stack based no Bigtop should be Bigtop.
>>>> If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>>>> I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>>>>
>>>>
>>>> On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
>>>>>
>>>>> I believe it's for project name. isn't it.?
>>>>>
>>>>>
>>>>> On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>>>
>>>>>> But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>>>>>
>>>>> Not fine.
>>>>> We have a trademark policy.
>>>>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gDhqEuyGhsdvPKcxrA65I4G9BRD86Ai%2BoasW0ycTfng%3D&reserved=0
>>>>>
>>>>> On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
>>>>>>> Should we avoid unrecognized brand which may be trademark of someone?
>>>>>>> ambari-select or bigtop-select should be enough.
>>>>>>
>>>>>> Not sure, where to confirm whether there is already trademark. When I googled found so many.
>>>>>> But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>>>>>> May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
>>>>>>
>>>>>> Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
>>>>>>
>>>>>> 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZFYaWY1a45yniMuLQaZjKVQGt9kE5elMrLNh8Cm9HL4%3D&reserved=0
>>>>>>
>>>>>> 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3awZ5TFt9AyItE5CkLBLSANkjX4KIr%2FqCrdDirKEBew%3D&reserved=0
>>>>>>
>>>>>>
>>>>>> On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>>>>
>>>>>>> We have still not officially finalized the new replacement name for
>>>>>>> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>>>>>>> the purpose of bdp-select and conf-select remains the same.
>>>>>>
>>>>>> Should we avoid unrecognized brand which may be trademark of someone?
>>>>>> ambari-select or bigtop-select should be enough.
>>>>>>
>>>>>> On 2022/06/29 13:52, Viraj Jasani wrote:
>>>>>>> Hi Ambari/Bigtop dev,
>>>>>>>
>>>>>>> As per the new roadmap of Apache Ambari, we would like to propose moving
>>>>>>> certain scripts (previously known as hdp-select and conf-select) to Bigtop
>>>>>>> so that their rpm installation could be managed independently.
>>>>>>> These scripts are a basic necessity in the Ambari framework for the
>>>>>>> installation of various Bigdata packages. The only major changes they would
>>>>>>> receive is when we onboard new services and components to Ambari, else they
>>>>>>> usually do not receive updates. In the past, we used to get hdp-select rpm
>>>>>>> downloaded and installed from HDP repositories.
>>>>>>>
>>>>>>> We have still not officially finalized the new replacement name for
>>>>>>> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>>>>>>> the purpose of bdp-select and conf-select remains the same.
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>>> For additional commands, e-mail: dev-help@ambari.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>> For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by 吴治国 <wz...@163.com>.
>> I’d like to propose BGTP as stack name(already used in Bigtop Ambari Mpack) with bgtp-select,
>
> It is a good time to get rid of useless abbreviation.
> Why not BIGTOP?
BIGTOP with bigtop-select works for me too, but the mpack is using BGTP as stack name now.
Best Regards,
Zhiguo Wu
> On Jul 7, 2022, at 10:59, Masatake Iwasaki <iw...@oss.nttdata.co.jp> wrote:
>
>> I’d like to propose BGTP as stack name(already used in Bigtop Ambari Mpack) with bgtp-select,
>
> It is a good time to get rid of useless abbreviation.
> Why not BIGTOP?
>
> On 2022/07/07 11:07, 吴治国 wrote:
>>>> Sure, we can have module name like bigtop-distro-select.
>>>
>>> Do you mean that you're going to name the module (same as "component"
>>> in the Bigtop terminology, I think) bigtop-distro-select,
>>> and still the script in question bdp-select? If so, is there any
>>> reason that the script must be that name?
>>> (No offence, I just want to understand your thoughts and its
>>> background, and avoid the conflict or user's confusion with existing
>>> trademarks or products)
>> I’d like to propose BGTP as stack name(already used in Bigtop Ambari Mpack) with bgtp-select, BDP(Bigtop Data Platform) with bdp-select or Bigtop with bigtop-select.
>> BDP(Big Data Platform) with bigtop-distro-select confuse me.
>> Best Regards,
>> Zhiguo Wu
>>> On Jul 7, 2022, at 08:37, Kengo Seki <se...@apache.org> wrote:
>>>
>>> The following concern Masatake mentioned before is an important point,
>>> so I talked to Brahma for clarifying his intention on the ASF Slack
>>> yesterday.
>>>
>>>> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
>>>> IIRC, HDP uses convention in which the product version is part of package name
>>>> for addressing this.
>>>
>>>> I don't like to bring the awkward package name convention to Bigtop
>>>> at least by default.
>>>
>>> He's planning to adopt the same mitigation as HDP for now, but he
>>> doesn't intend to change the default package naming convention of
>>> Bigtop,
>>> but just add a new functionality to include an extra part into the
>>> package name for avoiding conflict, which is disabled by default.
>>>
>>> And Brahma, let me confirm about the following reply:
>>>
>>>> Sure, we can have module name like bigtop-distro-select.
>>>
>>> Do you mean that you're going to name the module (same as "component"
>>> in the Bigtop terminology, I think) bigtop-distro-select,
>>> and still the script in question bdp-select? If so, is there any
>>> reason that the script must be that name?
>>> (No offence, I just want to understand your thoughts and its
>>> background, and avoid the conflict or user's confusion with existing
>>> trademarks or products)
>>>
>>> Kengo Seki <se...@apache.org>
>>>
>>> On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
>>> <bb...@visa.com.invalid> wrote:
>>>>
>>>>> The name of stack based no Bigtop should be Bigtop.
>>>>> If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>>>>> I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>>>>
>>>> Sure, we can have module name like bigtop-distro-select.
>>>> Initially we'll do this separate branch.
>>>>
>>>>
>>>>
>>>> On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>>
>>>>> I believe it's for project name. isn't it.?
>>>>
>>>> projects and products.
>>>>
>>>>> IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>>>>
>>>> The name of stack based no Bigtop should be Bigtop.
>>>> If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>>>> I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>>>>
>>>>
>>>> On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
>>>>>
>>>>> I believe it's for project name. isn't it.?
>>>>>
>>>>>
>>>>> On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>>>
>>>>>> But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>>>>>
>>>>> Not fine.
>>>>> We have a trademark policy.
>>>>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gDhqEuyGhsdvPKcxrA65I4G9BRD86Ai%2BoasW0ycTfng%3D&reserved=0
>>>>>
>>>>> On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
>>>>>>> Should we avoid unrecognized brand which may be trademark of someone?
>>>>>>> ambari-select or bigtop-select should be enough.
>>>>>>
>>>>>> Not sure, where to confirm whether there is already trademark. When I googled found so many.
>>>>>> But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>>>>>> May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
>>>>>>
>>>>>> Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
>>>>>>
>>>>>> 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZFYaWY1a45yniMuLQaZjKVQGt9kE5elMrLNh8Cm9HL4%3D&reserved=0
>>>>>>
>>>>>> 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3awZ5TFt9AyItE5CkLBLSANkjX4KIr%2FqCrdDirKEBew%3D&reserved=0
>>>>>>
>>>>>>
>>>>>> On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>>>>
>>>>>>> We have still not officially finalized the new replacement name for
>>>>>>> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>>>>>>> the purpose of bdp-select and conf-select remains the same.
>>>>>>
>>>>>> Should we avoid unrecognized brand which may be trademark of someone?
>>>>>> ambari-select or bigtop-select should be enough.
>>>>>>
>>>>>> On 2022/06/29 13:52, Viraj Jasani wrote:
>>>>>>> Hi Ambari/Bigtop dev,
>>>>>>>
>>>>>>> As per the new roadmap of Apache Ambari, we would like to propose moving
>>>>>>> certain scripts (previously known as hdp-select and conf-select) to Bigtop
>>>>>>> so that their rpm installation could be managed independently.
>>>>>>> These scripts are a basic necessity in the Ambari framework for the
>>>>>>> installation of various Bigdata packages. The only major changes they would
>>>>>>> receive is when we onboard new services and components to Ambari, else they
>>>>>>> usually do not receive updates. In the past, we used to get hdp-select rpm
>>>>>>> downloaded and installed from HDP repositories.
>>>>>>>
>>>>>>> We have still not officially finalized the new replacement name for
>>>>>>> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>>>>>>> the purpose of bdp-select and conf-select remains the same.
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>>> For additional commands, e-mail: dev-help@ambari.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>> For additional commands, e-mail: dev-help@ambari.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
> I’d like to propose BGTP as stack name(already used in Bigtop Ambari Mpack) with bgtp-select,
It is a good time to get rid of useless abbreviation.
Why not BIGTOP?
On 2022/07/07 11:07, 吴治国 wrote:
>>> Sure, we can have module name like bigtop-distro-select.
>>
>> Do you mean that you're going to name the module (same as "component"
>> in the Bigtop terminology, I think) bigtop-distro-select,
>> and still the script in question bdp-select? If so, is there any
>> reason that the script must be that name?
>> (No offence, I just want to understand your thoughts and its
>> background, and avoid the conflict or user's confusion with existing
>> trademarks or products)
>
> I’d like to propose BGTP as stack name(already used in Bigtop Ambari Mpack) with bgtp-select, BDP(Bigtop Data Platform) with bdp-select or Bigtop with bigtop-select.
>
> BDP(Big Data Platform) with bigtop-distro-select confuse me.
>
> Best Regards,
> Zhiguo Wu
>
>> On Jul 7, 2022, at 08:37, Kengo Seki <se...@apache.org> wrote:
>>
>> The following concern Masatake mentioned before is an important point,
>> so I talked to Brahma for clarifying his intention on the ASF Slack
>> yesterday.
>>
>>> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
>>> IIRC, HDP uses convention in which the product version is part of package name
>>> for addressing this.
>>
>>> I don't like to bring the awkward package name convention to Bigtop
>>> at least by default.
>>
>> He's planning to adopt the same mitigation as HDP for now, but he
>> doesn't intend to change the default package naming convention of
>> Bigtop,
>> but just add a new functionality to include an extra part into the
>> package name for avoiding conflict, which is disabled by default.
>>
>> And Brahma, let me confirm about the following reply:
>>
>>> Sure, we can have module name like bigtop-distro-select.
>>
>> Do you mean that you're going to name the module (same as "component"
>> in the Bigtop terminology, I think) bigtop-distro-select,
>> and still the script in question bdp-select? If so, is there any
>> reason that the script must be that name?
>> (No offence, I just want to understand your thoughts and its
>> background, and avoid the conflict or user's confusion with existing
>> trademarks or products)
>>
>> Kengo Seki <se...@apache.org>
>>
>> On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
>> <bb...@visa.com.invalid> wrote:
>>>
>>>> The name of stack based no Bigtop should be Bigtop.
>>>> If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>>>> I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>>>
>>> Sure, we can have module name like bigtop-distro-select.
>>> Initially we'll do this separate branch.
>>>
>>>
>>>
>>> On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>
>>>> I believe it's for project name. isn't it.?
>>>
>>> projects and products.
>>>
>>>> IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>>>
>>> The name of stack based no Bigtop should be Bigtop.
>>> If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>>> I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>>>
>>>
>>> On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
>>>>
>>>> I believe it's for project name. isn't it.?
>>>>
>>>>
>>>> On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>>
>>>>> But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>>>>
>>>> Not fine.
>>>> We have a trademark policy.
>>>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gDhqEuyGhsdvPKcxrA65I4G9BRD86Ai%2BoasW0ycTfng%3D&reserved=0
>>>>
>>>> On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
>>>>>> Should we avoid unrecognized brand which may be trademark of someone?
>>>>>> ambari-select or bigtop-select should be enough.
>>>>>
>>>>> Not sure, where to confirm whether there is already trademark. When I googled found so many.
>>>>> But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>>>>> May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
>>>>>
>>>>> Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
>>>>>
>>>>> 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZFYaWY1a45yniMuLQaZjKVQGt9kE5elMrLNh8Cm9HL4%3D&reserved=0
>>>>>
>>>>> 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3awZ5TFt9AyItE5CkLBLSANkjX4KIr%2FqCrdDirKEBew%3D&reserved=0
>>>>>
>>>>>
>>>>> On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>>>
>>>>>> We have still not officially finalized the new replacement name for
>>>>>> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>>>>>> the purpose of bdp-select and conf-select remains the same.
>>>>>
>>>>> Should we avoid unrecognized brand which may be trademark of someone?
>>>>> ambari-select or bigtop-select should be enough.
>>>>>
>>>>> On 2022/06/29 13:52, Viraj Jasani wrote:
>>>>>> Hi Ambari/Bigtop dev,
>>>>>>
>>>>>> As per the new roadmap of Apache Ambari, we would like to propose moving
>>>>>> certain scripts (previously known as hdp-select and conf-select) to Bigtop
>>>>>> so that their rpm installation could be managed independently.
>>>>>> These scripts are a basic necessity in the Ambari framework for the
>>>>>> installation of various Bigdata packages. The only major changes they would
>>>>>> receive is when we onboard new services and components to Ambari, else they
>>>>>> usually do not receive updates. In the past, we used to get hdp-select rpm
>>>>>> downloaded and installed from HDP repositories.
>>>>>>
>>>>>> We have still not officially finalized the new replacement name for
>>>>>> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>>>>>> the purpose of bdp-select and conf-select remains the same.
>>>>>>
>>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>>> For additional commands, e-mail: dev-help@ambari.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> For additional commands, e-mail: dev-help@ambari.apache.org
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by 吴治国 <wz...@163.com>.
>> Sure, we can have module name like bigtop-distro-select.
>
> Do you mean that you're going to name the module (same as "component"
> in the Bigtop terminology, I think) bigtop-distro-select,
> and still the script in question bdp-select? If so, is there any
> reason that the script must be that name?
> (No offence, I just want to understand your thoughts and its
> background, and avoid the conflict or user's confusion with existing
> trademarks or products)
I’d like to propose BGTP as stack name(already used in Bigtop Ambari Mpack) with bgtp-select, BDP(Bigtop Data Platform) with bdp-select or Bigtop with bigtop-select.
BDP(Big Data Platform) with bigtop-distro-select confuse me.
Best Regards,
Zhiguo Wu
> On Jul 7, 2022, at 08:37, Kengo Seki <se...@apache.org> wrote:
>
> The following concern Masatake mentioned before is an important point,
> so I talked to Brahma for clarifying his intention on the ASF Slack
> yesterday.
>
>> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
>> IIRC, HDP uses convention in which the product version is part of package name
>> for addressing this.
>
>> I don't like to bring the awkward package name convention to Bigtop
>> at least by default.
>
> He's planning to adopt the same mitigation as HDP for now, but he
> doesn't intend to change the default package naming convention of
> Bigtop,
> but just add a new functionality to include an extra part into the
> package name for avoiding conflict, which is disabled by default.
>
> And Brahma, let me confirm about the following reply:
>
>> Sure, we can have module name like bigtop-distro-select.
>
> Do you mean that you're going to name the module (same as "component"
> in the Bigtop terminology, I think) bigtop-distro-select,
> and still the script in question bdp-select? If so, is there any
> reason that the script must be that name?
> (No offence, I just want to understand your thoughts and its
> background, and avoid the conflict or user's confusion with existing
> trademarks or products)
>
> Kengo Seki <se...@apache.org>
>
> On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
>>
>>> The name of stack based no Bigtop should be Bigtop.
>>> If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>>> I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>>
>> Sure, we can have module name like bigtop-distro-select.
>> Initially we'll do this separate branch.
>>
>>
>>
>> On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>
>>> I believe it's for project name. isn't it.?
>>
>> projects and products.
>>
>>> IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>>
>> The name of stack based no Bigtop should be Bigtop.
>> If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>> I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>>
>>
>> On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
>>>
>>> I believe it's for project name. isn't it.?
>>>
>>>
>>> On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>
>>>> But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>>>
>>> Not fine.
>>> We have a trademark policy.
>>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gDhqEuyGhsdvPKcxrA65I4G9BRD86Ai%2BoasW0ycTfng%3D&reserved=0
>>>
>>> On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
>>>>> Should we avoid unrecognized brand which may be trademark of someone?
>>>>> ambari-select or bigtop-select should be enough.
>>>>
>>>> Not sure, where to confirm whether there is already trademark. When I googled found so many.
>>>> But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>>>> May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
>>>>
>>>> Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
>>>>
>>>> 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZFYaWY1a45yniMuLQaZjKVQGt9kE5elMrLNh8Cm9HL4%3D&reserved=0
>>>>
>>>> 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3awZ5TFt9AyItE5CkLBLSANkjX4KIr%2FqCrdDirKEBew%3D&reserved=0
>>>>
>>>>
>>>> On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>>
>>>>> We have still not officially finalized the new replacement name for
>>>>> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>>>>> the purpose of bdp-select and conf-select remains the same.
>>>>
>>>> Should we avoid unrecognized brand which may be trademark of someone?
>>>> ambari-select or bigtop-select should be enough.
>>>>
>>>> On 2022/06/29 13:52, Viraj Jasani wrote:
>>>>> Hi Ambari/Bigtop dev,
>>>>>
>>>>> As per the new roadmap of Apache Ambari, we would like to propose moving
>>>>> certain scripts (previously known as hdp-select and conf-select) to Bigtop
>>>>> so that their rpm installation could be managed independently.
>>>>> These scripts are a basic necessity in the Ambari framework for the
>>>>> installation of various Bigdata packages. The only major changes they would
>>>>> receive is when we onboard new services and components to Ambari, else they
>>>>> usually do not receive updates. In the past, we used to get hdp-select rpm
>>>>> downloaded and installed from HDP repositories.
>>>>>
>>>>> We have still not officially finalized the new replacement name for
>>>>> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>>>>> the purpose of bdp-select and conf-select remains the same.
>>>>>
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> For additional commands, e-mail: dev-help@ambari.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by 吴治国 <wz...@163.com>.
>> Sure, we can have module name like bigtop-distro-select.
>
> Do you mean that you're going to name the module (same as "component"
> in the Bigtop terminology, I think) bigtop-distro-select,
> and still the script in question bdp-select? If so, is there any
> reason that the script must be that name?
> (No offence, I just want to understand your thoughts and its
> background, and avoid the conflict or user's confusion with existing
> trademarks or products)
I’d like to propose BGTP as stack name(already used in Bigtop Ambari Mpack) with bgtp-select, BDP(Bigtop Data Platform) with bdp-select or Bigtop with bigtop-select.
BDP(Big Data Platform) with bigtop-distro-select confuse me.
Best Regards,
Zhiguo Wu
> On Jul 7, 2022, at 08:37, Kengo Seki <se...@apache.org> wrote:
>
> The following concern Masatake mentioned before is an important point,
> so I talked to Brahma for clarifying his intention on the ASF Slack
> yesterday.
>
>> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
>> IIRC, HDP uses convention in which the product version is part of package name
>> for addressing this.
>
>> I don't like to bring the awkward package name convention to Bigtop
>> at least by default.
>
> He's planning to adopt the same mitigation as HDP for now, but he
> doesn't intend to change the default package naming convention of
> Bigtop,
> but just add a new functionality to include an extra part into the
> package name for avoiding conflict, which is disabled by default.
>
> And Brahma, let me confirm about the following reply:
>
>> Sure, we can have module name like bigtop-distro-select.
>
> Do you mean that you're going to name the module (same as "component"
> in the Bigtop terminology, I think) bigtop-distro-select,
> and still the script in question bdp-select? If so, is there any
> reason that the script must be that name?
> (No offence, I just want to understand your thoughts and its
> background, and avoid the conflict or user's confusion with existing
> trademarks or products)
>
> Kengo Seki <se...@apache.org>
>
> On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
>>
>>> The name of stack based no Bigtop should be Bigtop.
>>> If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>>> I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>>
>> Sure, we can have module name like bigtop-distro-select.
>> Initially we'll do this separate branch.
>>
>>
>>
>> On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>
>>> I believe it's for project name. isn't it.?
>>
>> projects and products.
>>
>>> IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>>
>> The name of stack based no Bigtop should be Bigtop.
>> If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
>> I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>>
>>
>> On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
>>>
>>> I believe it's for project name. isn't it.?
>>>
>>>
>>> On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>
>>>> But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>>>
>>> Not fine.
>>> We have a trademark policy.
>>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gDhqEuyGhsdvPKcxrA65I4G9BRD86Ai%2BoasW0ycTfng%3D&reserved=0
>>>
>>> On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
>>>>> Should we avoid unrecognized brand which may be trademark of someone?
>>>>> ambari-select or bigtop-select should be enough.
>>>>
>>>> Not sure, where to confirm whether there is already trademark. When I googled found so many.
>>>> But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>>>> May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
>>>>
>>>> Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
>>>>
>>>> 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZFYaWY1a45yniMuLQaZjKVQGt9kE5elMrLNh8Cm9HL4%3D&reserved=0
>>>>
>>>> 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3awZ5TFt9AyItE5CkLBLSANkjX4KIr%2FqCrdDirKEBew%3D&reserved=0
>>>>
>>>>
>>>> On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>>>>
>>>>> We have still not officially finalized the new replacement name for
>>>>> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>>>>> the purpose of bdp-select and conf-select remains the same.
>>>>
>>>> Should we avoid unrecognized brand which may be trademark of someone?
>>>> ambari-select or bigtop-select should be enough.
>>>>
>>>> On 2022/06/29 13:52, Viraj Jasani wrote:
>>>>> Hi Ambari/Bigtop dev,
>>>>>
>>>>> As per the new roadmap of Apache Ambari, we would like to propose moving
>>>>> certain scripts (previously known as hdp-select and conf-select) to Bigtop
>>>>> so that their rpm installation could be managed independently.
>>>>> These scripts are a basic necessity in the Ambari framework for the
>>>>> installation of various Bigdata packages. The only major changes they would
>>>>> receive is when we onboard new services and components to Ambari, else they
>>>>> usually do not receive updates. In the past, we used to get hdp-select rpm
>>>>> downloaded and installed from HDP repositories.
>>>>>
>>>>> We have still not officially finalized the new replacement name for
>>>>> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>>>>> the purpose of bdp-select and conf-select remains the same.
>>>>>
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
>> For additional commands, e-mail: dev-help@ambari.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
>Do you mean that you're going to name the module (same as "component"
>in the Bigtop terminology, I think) bigtop-distro-select,
>and still the script in question bdp-select? If so, is there any
>reason that the script must be that name?
>(No offence, I just want to understand your thoughts and its
>background, and avoid the conflict or user's confusion with existing
>trademarks or products)
Thanks @Kengo Seki for consolidating all the concerns. Name should represent the stack which includes all the components hence planning to have like bdp,bds...and this only one file like below[1] which has done redoop.
https://github.com/redoop/bigtop/tree/e5f9fe81773180159d291f18ec366ac8bfa4d6d2/bigtop-packages/src/common/ambari-mpacks/selector
On 07/07/22, 6:07 AM, "Kengo Seki" <se...@apache.org> wrote:
The following concern Masatake mentioned before is an important point,
so I talked to Brahma for clarifying his intention on the ASF Slack
yesterday.
> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> IIRC, HDP uses convention in which the product version is part of package name
> for addressing this.
> I don't like to bring the awkward package name convention to Bigtop
> at least by default.
He's planning to adopt the same mitigation as HDP for now, but he
doesn't intend to change the default package naming convention of
Bigtop,
but just add a new functionality to include an extra part into the
package name for avoiding conflict, which is disabled by default.
And Brahma, let me confirm about the following reply:
> Sure, we can have module name like bigtop-distro-select.
Do you mean that you're going to name the module (same as "component"
in the Bigtop terminology, I think) bigtop-distro-select,
and still the script in question bdp-select? If so, is there any
reason that the script must be that name?
(No offence, I just want to understand your thoughts and its
background, and avoid the conflict or user's confusion with existing
trademarks or products)
Kengo Seki <se...@apache.org>
On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
>
> > The name of stack based no Bigtop should be Bigtop.
> > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>
> Sure, we can have module name like bigtop-distro-select.
> Initially we'll do this separate branch.
>
>
>
> On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>
> > I believe it's for project name. isn't it.?
>
> projects and products.
>
> > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>
> The name of stack based no Bigtop should be Bigtop.
> If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>
>
> On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> >
> > I believe it's for project name. isn't it.?
> >
> >
> > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >
> > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> >
> > Not fine.
> > We have a trademark policy.
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=uLAUZWy9EpJRNUYeuhSL951CbEdtLYFxrOFK%2BWW5Elg%3D&reserved=0
> >
> > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> > >> Should we avoid unrecognized brand which may be trademark of someone?
> > >> ambari-select or bigtop-select should be enough.
> > >
> > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > >
> > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> > >
> > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8NSFFz1Ko1oZFar%2Bz0%2FML9LgJHUNf0bLw7VVbtGP1ck%3D&reserved=0
> > >
> > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7C2cf3b754b1274bf79c1a08da5fb0edaf%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637927510750937928%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=I%2BbQoYUU5upYS1VQT1rux5ZZhh%2Fx1yeyD%2BnLW8HJwkw%3D&reserved=0
> > >
> > >
> > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >
> > > > We have still not officially finalized the new replacement name for
> > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > the purpose of bdp-select and conf-select remains the same.
> > >
> > > Should we avoid unrecognized brand which may be trademark of someone?
> > > ambari-select or bigtop-select should be enough.
> > >
> > > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > > Hi Ambari/Bigtop dev,
> > > >
> > > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > > so that their rpm installation could be managed independently.
> > > > These scripts are a basic necessity in the Ambari framework for the
> > > > installation of various Bigdata packages. The only major changes they would
> > > > receive is when we onboard new services and components to Ambari, else they
> > > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > > downloaded and installed from HDP repositories.
> > > >
> > > > We have still not officially finalized the new replacement name for
> > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > the purpose of bdp-select and conf-select remains the same.
> > > >
> > >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Kengo Seki <se...@apache.org>.
The following concern Masatake mentioned before is an important point,
so I talked to Brahma for clarifying his intention on the ASF Slack
yesterday.
> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> IIRC, HDP uses convention in which the product version is part of package name
> for addressing this.
> I don't like to bring the awkward package name convention to Bigtop
> at least by default.
He's planning to adopt the same mitigation as HDP for now, but he
doesn't intend to change the default package naming convention of
Bigtop,
but just add a new functionality to include an extra part into the
package name for avoiding conflict, which is disabled by default.
And Brahma, let me confirm about the following reply:
> Sure, we can have module name like bigtop-distro-select.
Do you mean that you're going to name the module (same as "component"
in the Bigtop terminology, I think) bigtop-distro-select,
and still the script in question bdp-select? If so, is there any
reason that the script must be that name?
(No offence, I just want to understand your thoughts and its
background, and avoid the conflict or user's confusion with existing
trademarks or products)
Kengo Seki <se...@apache.org>
On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
>
> > The name of stack based no Bigtop should be Bigtop.
> > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>
> Sure, we can have module name like bigtop-distro-select.
> Initially we'll do this separate branch.
>
>
>
> On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>
> > I believe it's for project name. isn't it.?
>
> projects and products.
>
> > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>
> The name of stack based no Bigtop should be Bigtop.
> If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>
>
> On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> >
> > I believe it's for project name. isn't it.?
> >
> >
> > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >
> > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> >
> > Not fine.
> > We have a trademark policy.
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gDhqEuyGhsdvPKcxrA65I4G9BRD86Ai%2BoasW0ycTfng%3D&reserved=0
> >
> > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> > >> Should we avoid unrecognized brand which may be trademark of someone?
> > >> ambari-select or bigtop-select should be enough.
> > >
> > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > >
> > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> > >
> > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZFYaWY1a45yniMuLQaZjKVQGt9kE5elMrLNh8Cm9HL4%3D&reserved=0
> > >
> > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3awZ5TFt9AyItE5CkLBLSANkjX4KIr%2FqCrdDirKEBew%3D&reserved=0
> > >
> > >
> > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >
> > > > We have still not officially finalized the new replacement name for
> > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > the purpose of bdp-select and conf-select remains the same.
> > >
> > > Should we avoid unrecognized brand which may be trademark of someone?
> > > ambari-select or bigtop-select should be enough.
> > >
> > > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > > Hi Ambari/Bigtop dev,
> > > >
> > > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > > so that their rpm installation could be managed independently.
> > > > These scripts are a basic necessity in the Ambari framework for the
> > > > installation of various Bigdata packages. The only major changes they would
> > > > receive is when we onboard new services and components to Ambari, else they
> > > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > > downloaded and installed from HDP repositories.
> > > >
> > > > We have still not officially finalized the new replacement name for
> > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > the purpose of bdp-select and conf-select remains the same.
> > > >
> > >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Kengo Seki <se...@apache.org>.
The following concern Masatake mentioned before is an important point,
so I talked to Brahma for clarifying his intention on the ASF Slack
yesterday.
> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> IIRC, HDP uses convention in which the product version is part of package name
> for addressing this.
> I don't like to bring the awkward package name convention to Bigtop
> at least by default.
He's planning to adopt the same mitigation as HDP for now, but he
doesn't intend to change the default package naming convention of
Bigtop,
but just add a new functionality to include an extra part into the
package name for avoiding conflict, which is disabled by default.
And Brahma, let me confirm about the following reply:
> Sure, we can have module name like bigtop-distro-select.
Do you mean that you're going to name the module (same as "component"
in the Bigtop terminology, I think) bigtop-distro-select,
and still the script in question bdp-select? If so, is there any
reason that the script must be that name?
(No offence, I just want to understand your thoughts and its
background, and avoid the conflict or user's confusion with existing
trademarks or products)
Kengo Seki <se...@apache.org>
On Thu, Jul 7, 2022 at 2:08 AM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
>
> > The name of stack based no Bigtop should be Bigtop.
> > If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> > I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>
> Sure, we can have module name like bigtop-distro-select.
> Initially we'll do this separate branch.
>
>
>
> On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>
> > I believe it's for project name. isn't it.?
>
> projects and products.
>
> > IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>
> The name of stack based no Bigtop should be Bigtop.
> If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
>
>
> On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
> >
> > I believe it's for project name. isn't it.?
> >
> >
> > On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >
> > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> >
> > Not fine.
> > We have a trademark policy.
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gDhqEuyGhsdvPKcxrA65I4G9BRD86Ai%2BoasW0ycTfng%3D&reserved=0
> >
> > On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> > >> Should we avoid unrecognized brand which may be trademark of someone?
> > >> ambari-select or bigtop-select should be enough.
> > >
> > > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> > >
> > > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> > >
> > > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZFYaWY1a45yniMuLQaZjKVQGt9kE5elMrLNh8Cm9HL4%3D&reserved=0
> > >
> > > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3awZ5TFt9AyItE5CkLBLSANkjX4KIr%2FqCrdDirKEBew%3D&reserved=0
> > >
> > >
> > > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > >
> > > > We have still not officially finalized the new replacement name for
> > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > the purpose of bdp-select and conf-select remains the same.
> > >
> > > Should we avoid unrecognized brand which may be trademark of someone?
> > > ambari-select or bigtop-select should be enough.
> > >
> > > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > > Hi Ambari/Bigtop dev,
> > > >
> > > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > > so that their rpm installation could be managed independently.
> > > > These scripts are a basic necessity in the Ambari framework for the
> > > > installation of various Bigdata packages. The only major changes they would
> > > > receive is when we onboard new services and components to Ambari, else they
> > > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > > downloaded and installed from HDP repositories.
> > > >
> > > > We have still not officially finalized the new replacement name for
> > > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > > the purpose of bdp-select and conf-select remains the same.
> > > >
> > >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
> For additional commands, e-mail: dev-help@ambari.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
> The name of stack based no Bigtop should be Bigtop.
> If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
Sure, we can have module name like bigtop-distro-select.
Initially we'll do this separate branch.
On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> I believe it's for project name. isn't it.?
projects and products.
> IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
The name of stack based no Bigtop should be Bigtop.
If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
>
> I believe it's for project name. isn't it.?
>
>
> On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>
> > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>
> Not fine.
> We have a trademark policy.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gDhqEuyGhsdvPKcxrA65I4G9BRD86Ai%2BoasW0ycTfng%3D&reserved=0
>
> On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> >> Should we avoid unrecognized brand which may be trademark of someone?
> >> ambari-select or bigtop-select should be enough.
> >
> > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> >
> > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> >
> > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZFYaWY1a45yniMuLQaZjKVQGt9kE5elMrLNh8Cm9HL4%3D&reserved=0
> >
> > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3awZ5TFt9AyItE5CkLBLSANkjX4KIr%2FqCrdDirKEBew%3D&reserved=0
> >
> >
> > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >
> > > We have still not officially finalized the new replacement name for
> > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > the purpose of bdp-select and conf-select remains the same.
> >
> > Should we avoid unrecognized brand which may be trademark of someone?
> > ambari-select or bigtop-select should be enough.
> >
> > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > Hi Ambari/Bigtop dev,
> > >
> > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > so that their rpm installation could be managed independently.
> > > These scripts are a basic necessity in the Ambari framework for the
> > > installation of various Bigdata packages. The only major changes they would
> > > receive is when we onboard new services and components to Ambari, else they
> > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > downloaded and installed from HDP repositories.
> > >
> > > We have still not officially finalized the new replacement name for
> > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > the purpose of bdp-select and conf-select remains the same.
> > >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
> The name of stack based no Bigtop should be Bigtop.
> If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
> I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
Sure, we can have module name like bigtop-distro-select.
Initially we'll do this separate branch.
On 06/07/22, 8:55 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> I believe it's for project name. isn't it.?
projects and products.
> IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
The name of stack based no Bigtop should be Bigtop.
If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
>
> I believe it's for project name. isn't it.?
>
>
> On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>
> > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>
> Not fine.
> We have a trademark policy.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gDhqEuyGhsdvPKcxrA65I4G9BRD86Ai%2BoasW0ycTfng%3D&reserved=0
>
> On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> >> Should we avoid unrecognized brand which may be trademark of someone?
> >> ambari-select or bigtop-select should be enough.
> >
> > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> >
> > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> >
> > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZFYaWY1a45yniMuLQaZjKVQGt9kE5elMrLNh8Cm9HL4%3D&reserved=0
> >
> > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Cc35272ff938645e034f908da5eff1bcc%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926747017162847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3awZ5TFt9AyItE5CkLBLSANkjX4KIr%2FqCrdDirKEBew%3D&reserved=0
> >
> >
> > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >
> > > We have still not officially finalized the new replacement name for
> > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > the purpose of bdp-select and conf-select remains the same.
> >
> > Should we avoid unrecognized brand which may be trademark of someone?
> > ambari-select or bigtop-select should be enough.
> >
> > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > Hi Ambari/Bigtop dev,
> > >
> > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > so that their rpm installation could be managed independently.
> > > These scripts are a basic necessity in the Ambari framework for the
> > > installation of various Bigdata packages. The only major changes they would
> > > receive is when we onboard new services and components to Ambari, else they
> > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > downloaded and installed from HDP repositories.
> > >
> > > We have still not officially finalized the new replacement name for
> > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > the purpose of bdp-select and conf-select remains the same.
> > >
> >
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
> I believe it's for project name. isn't it.?
projects and products.
> IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
The name of stack based no Bigtop should be Bigtop.
If you can not accept the name like bigtop-*, the work should done outside of Bigtop.
I will cast -1 if someone submit a patch to add a module with the name spoiling branding.
On 2022/07/06 11:44, Battula, Brahma Reddy wrote:
>
> I believe it's for project name. isn't it.?
>
>
> On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>
> > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
>
> Not fine.
> We have a trademark policy.
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Cb64a88fb78394de8aaf508da5ef2db2f%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926694401723403%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=d%2FFv5RAGFpP%2BP15jme5yHf5Bj2B47qHxbo8CVwwFXNo%3D&reserved=0
>
> On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
> >> Should we avoid unrecognized brand which may be trademark of someone?
> >> ambari-select or bigtop-select should be enough.
> >
> > Not sure, where to confirm whether there is already trademark. When I googled found so many.
> > But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> > May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
> >
> > Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
> >
> > 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Cb64a88fb78394de8aaf508da5ef2db2f%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926694401723403%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bmAvP%2BO3vXS4Ro4f%2BBLh9Z8w56kPcBIFaULHFQ0zCgM%3D&reserved=0
> >
> > 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Cb64a88fb78394de8aaf508da5ef2db2f%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926694401723403%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VhxZFBE0kjTNGqO18iXr2ITBsH8RRKxlyXGZuqJN9xA%3D&reserved=0
> >
> >
> > On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >
> > > We have still not officially finalized the new replacement name for
> > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > the purpose of bdp-select and conf-select remains the same.
> >
> > Should we avoid unrecognized brand which may be trademark of someone?
> > ambari-select or bigtop-select should be enough.
> >
> > On 2022/06/29 13:52, Viraj Jasani wrote:
> > > Hi Ambari/Bigtop dev,
> > >
> > > As per the new roadmap of Apache Ambari, we would like to propose moving
> > > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > > so that their rpm installation could be managed independently.
> > > These scripts are a basic necessity in the Ambari framework for the
> > > installation of various Bigdata packages. The only major changes they would
> > > receive is when we onboard new services and components to Ambari, else they
> > > usually do not receive updates. In the past, we used to get hdp-select rpm
> > > downloaded and installed from HDP repositories.
> > >
> > > We have still not officially finalized the new replacement name for
> > > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > > the purpose of bdp-select and conf-select remains the same.
> > >
> >
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
I believe it's for project name. isn't it.?
On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
Not fine.
We have a trademark policy.
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Cb64a88fb78394de8aaf508da5ef2db2f%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926694401723403%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=d%2FFv5RAGFpP%2BP15jme5yHf5Bj2B47qHxbo8CVwwFXNo%3D&reserved=0
On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
>> Should we avoid unrecognized brand which may be trademark of someone?
>> ambari-select or bigtop-select should be enough.
>
> Not sure, where to confirm whether there is already trademark. When I googled found so many.
> But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
>
> Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
>
> 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Cb64a88fb78394de8aaf508da5ef2db2f%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926694401723403%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bmAvP%2BO3vXS4Ro4f%2BBLh9Z8w56kPcBIFaULHFQ0zCgM%3D&reserved=0
>
> 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Cb64a88fb78394de8aaf508da5ef2db2f%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926694401723403%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VhxZFBE0kjTNGqO18iXr2ITBsH8RRKxlyXGZuqJN9xA%3D&reserved=0
>
>
> On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>
> > We have still not officially finalized the new replacement name for
> > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > the purpose of bdp-select and conf-select remains the same.
>
> Should we avoid unrecognized brand which may be trademark of someone?
> ambari-select or bigtop-select should be enough.
>
> On 2022/06/29 13:52, Viraj Jasani wrote:
> > Hi Ambari/Bigtop dev,
> >
> > As per the new roadmap of Apache Ambari, we would like to propose moving
> > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > so that their rpm installation could be managed independently.
> > These scripts are a basic necessity in the Ambari framework for the
> > installation of various Bigdata packages. The only major changes they would
> > receive is when we onboard new services and components to Ambari, else they
> > usually do not receive updates. In the past, we used to get hdp-select rpm
> > downloaded and installed from HDP repositories.
> >
> > We have still not officially finalized the new replacement name for
> > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > the purpose of bdp-select and conf-select remains the same.
> >
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
I believe it's for project name. isn't it.?
On 06/07/22, 7:27 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
Not fine.
We have a trademark policy.
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fmarks%2F&data=05%7C01%7Cbbattula%40visa.com%7Cb64a88fb78394de8aaf508da5ef2db2f%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926694401723403%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=d%2FFv5RAGFpP%2BP15jme5yHf5Bj2B47qHxbo8CVwwFXNo%3D&reserved=0
On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
>> Should we avoid unrecognized brand which may be trademark of someone?
>> ambari-select or bigtop-select should be enough.
>
> Not sure, where to confirm whether there is already trademark. When I googled found so many.
> But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
>
> Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
>
> 1. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dbdp%26safe%3Dactive%26sxsrf%3DALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%253A1657070844287%26ei%3D_OTEYsuWEYrD4-EPp4uKqAE%26ved%3D0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4%26uact%3D5%26oq%3Dbdp%26gs_lcp%3DCgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE%26sclient%3Dgws-wiz&data=05%7C01%7Cbbattula%40visa.com%7Cb64a88fb78394de8aaf508da5ef2db2f%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926694401723403%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bmAvP%2BO3vXS4Ro4f%2BBLh9Z8w56kPcBIFaULHFQ0zCgM%3D&reserved=0
>
> 2. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fm77lhzo0njr2dhoock5twtm0c19j2py8&data=05%7C01%7Cbbattula%40visa.com%7Cb64a88fb78394de8aaf508da5ef2db2f%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637926694401723403%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VhxZFBE0kjTNGqO18iXr2ITBsH8RRKxlyXGZuqJN9xA%3D&reserved=0
>
>
> On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>
> > We have still not officially finalized the new replacement name for
> > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > the purpose of bdp-select and conf-select remains the same.
>
> Should we avoid unrecognized brand which may be trademark of someone?
> ambari-select or bigtop-select should be enough.
>
> On 2022/06/29 13:52, Viraj Jasani wrote:
> > Hi Ambari/Bigtop dev,
> >
> > As per the new roadmap of Apache Ambari, we would like to propose moving
> > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > so that their rpm installation could be managed independently.
> > These scripts are a basic necessity in the Ambari framework for the
> > installation of various Bigdata packages. The only major changes they would
> > receive is when we onboard new services and components to Ambari, else they
> > usually do not receive updates. In the past, we used to get hdp-select rpm
> > downloaded and installed from HDP repositories.
> >
> > We have still not officially finalized the new replacement name for
> > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > the purpose of bdp-select and conf-select remains the same.
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
> But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
Not fine.
We have a trademark policy.
https://www.apache.org/foundation/marks/
On 2022/07/06 10:37, Battula, Brahma Reddy wrote:
>> Should we avoid unrecognized brand which may be trademark of someone?
>> ambari-select or bigtop-select should be enough.
>
> Not sure, where to confirm whether there is already trademark. When I googled found so many.
> But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
> May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
>
> Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
>
> 1. https://www.google.com/search?q=bdp&safe=active&sxsrf=ALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%3A1657070844287&ei=_OTEYsuWEYrD4-EPp4uKqAE&ved=0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4&uact=5&oq=bdp&gs_lcp=Cgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE&sclient=gws-wiz
>
> 2. https://lists.apache.org/thread/m77lhzo0njr2dhoock5twtm0c19j2py8
>
>
> On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>
> > We have still not officially finalized the new replacement name for
> > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > the purpose of bdp-select and conf-select remains the same.
>
> Should we avoid unrecognized brand which may be trademark of someone?
> ambari-select or bigtop-select should be enough.
>
> On 2022/06/29 13:52, Viraj Jasani wrote:
> > Hi Ambari/Bigtop dev,
> >
> > As per the new roadmap of Apache Ambari, we would like to propose moving
> > certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > so that their rpm installation could be managed independently.
> > These scripts are a basic necessity in the Ambari framework for the
> > installation of various Bigdata packages. The only major changes they would
> > receive is when we onboard new services and components to Ambari, else they
> > usually do not receive updates. In the past, we used to get hdp-select rpm
> > downloaded and installed from HDP repositories.
> >
> > We have still not officially finalized the new replacement name for
> > hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > the purpose of bdp-select and conf-select remains the same.
> >
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
> Should we avoid unrecognized brand which may be trademark of someone?
> ambari-select or bigtop-select should be enough.
Not sure, where to confirm whether there is already trademark. When I googled found so many.
But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
1. https://www.google.com/search?q=bdp&safe=active&sxsrf=ALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%3A1657070844287&ei=_OTEYsuWEYrD4-EPp4uKqAE&ved=0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4&uact=5&oq=bdp&gs_lcp=Cgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE&sclient=gws-wiz
2. https://lists.apache.org/thread/m77lhzo0njr2dhoock5twtm0c19j2py8
On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> We have still not officially finalized the new replacement name for
> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> the purpose of bdp-select and conf-select remains the same.
Should we avoid unrecognized brand which may be trademark of someone?
ambari-select or bigtop-select should be enough.
On 2022/06/29 13:52, Viraj Jasani wrote:
> Hi Ambari/Bigtop dev,
>
> As per the new roadmap of Apache Ambari, we would like to propose moving
> certain scripts (previously known as hdp-select and conf-select) to Bigtop
> so that their rpm installation could be managed independently.
> These scripts are a basic necessity in the Ambari framework for the
> installation of various Bigdata packages. The only major changes they would
> receive is when we onboard new services and components to Ambari, else they
> usually do not receive updates. In the past, we used to get hdp-select rpm
> downloaded and installed from HDP repositories.
>
> We have still not officially finalized the new replacement name for
> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> the purpose of bdp-select and conf-select remains the same.
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
> Should we avoid unrecognized brand which may be trademark of someone?
> ambari-select or bigtop-select should be enough.
Not sure, where to confirm whether there is already trademark. When I googled found so many.
But As we are not releasing as enterprise should be fine I think. IMO, We need to create folders and refer stacknames so ambari-select,bigtop-select wn't looks good.
May be you can refer the initial proposal [2] where I mentioned some more names. (BDS-BigDataStack,OSS-OpenSourceSelect..)
Finally thanks a bunch for long healthy discussions on this. Mostly we all same page now.
1. https://www.google.com/search?q=bdp&safe=active&sxsrf=ALiCzsaQDcQS0gb8KbAMfjadXuG-jomxRQ%3A1657070844287&ei=_OTEYsuWEYrD4-EPp4uKqAE&ved=0ahUKEwjLhKr4jeP4AhWK4TgGHaeFAhUQ4dUDCA4&uact=5&oq=bdp&gs_lcp=Cgdnd3Mtd2l6EAMyBAgjECcyBAgjECcyCggAELEDEIMBEEMyCwgAEIAEELEDEIMBMgsIABCABBCxAxCDATIRCC4QgAQQsQMQgwEQxwEQ0QMyBQgAEIAEMgUIABCABDIFCAAQgAQyBQgAEIAEOgcIABBHELADOgYIABAeEBY6CggAEB4QDxAWEAo6CggAEIAEEIcCEBQ6CwguEIAEEMcBEK8BOgcIABCABBAKOhYILhCABBCHAhCxAxCDARDHARDRAxAUSgQIQRgASgQIRhgAUKsHWNgRYLoWaAFwAXgAgAGoAYgBtAeSAQMwLjiYAQCgAQHIAQjAAQE&sclient=gws-wiz
2. https://lists.apache.org/thread/m77lhzo0njr2dhoock5twtm0c19j2py8
On 06/07/22, 4:01 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> We have still not officially finalized the new replacement name for
> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> the purpose of bdp-select and conf-select remains the same.
Should we avoid unrecognized brand which may be trademark of someone?
ambari-select or bigtop-select should be enough.
On 2022/06/29 13:52, Viraj Jasani wrote:
> Hi Ambari/Bigtop dev,
>
> As per the new roadmap of Apache Ambari, we would like to propose moving
> certain scripts (previously known as hdp-select and conf-select) to Bigtop
> so that their rpm installation could be managed independently.
> These scripts are a basic necessity in the Ambari framework for the
> installation of various Bigdata packages. The only major changes they would
> receive is when we onboard new services and components to Ambari, else they
> usually do not receive updates. In the past, we used to get hdp-select rpm
> downloaded and installed from HDP repositories.
>
> We have still not officially finalized the new replacement name for
> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> the purpose of bdp-select and conf-select remains the same.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
> We have still not officially finalized the new replacement name for
> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> the purpose of bdp-select and conf-select remains the same.
Should we avoid unrecognized brand which may be trademark of someone?
ambari-select or bigtop-select should be enough.
On 2022/06/29 13:52, Viraj Jasani wrote:
> Hi Ambari/Bigtop dev,
>
> As per the new roadmap of Apache Ambari, we would like to propose moving
> certain scripts (previously known as hdp-select and conf-select) to Bigtop
> so that their rpm installation could be managed independently.
> These scripts are a basic necessity in the Ambari framework for the
> installation of various Bigdata packages. The only major changes they would
> receive is when we onboard new services and components to Ambari, else they
> usually do not receive updates. In the past, we used to get hdp-select rpm
> downloaded and installed from HDP repositories.
>
> We have still not officially finalized the new replacement name for
> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> the purpose of bdp-select and conf-select remains the same.
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
> If it is the tool to switch distribution to Bigtop and
> does not care about other distributions,
> hosting it in Bigtop as bigtop-select would make sense.
> If the tool need to care about distribution other than Bigtop,
> it should be under Ambari.
All the component rpm's creation[1] will be happening through bigtop only right which is used for Ambari cluster deployment.?
Ambari is not creating any rpm's right.
We can have as separate module , So, whoever uses[1] they can change *-select accordingly.
1. https://github.com/apache/bigtop/tree/master/bigtop-packages/src/rpm
On 05/07/22, 6:25 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> Firstly we'll not multiple select's right..? We can have distro-select and conf-select which can be included as part of the bigtop code. User's can adopt it and even they can write their own. And user will not deploy with multiple selects right, as they can get the conflicts..
If it is the tool to switch distribution to Bigtop and
does not care about other distributions,
hosting it in Bigtop as bigtop-select would make sense.
If the tool need to care about distribution other than Bigtop,
it should be under Ambari.
On 2022/07/04 23:39, Battula, Brahma Reddy wrote:
>> Could you elaborate the reason why we need the *-select if so?
>
> Firstly we'll not multiple select's right..? We can have distro-select and conf-select which can be included as part of the bigtop code. User's can adopt it and even they can write their own. And user will not deploy with multiple selects right, as they can get the conflicts..
>
>> It does not make sense.
>> While Hadoop rpm/deb are built with Bigtop, Hadoop is independent project.
>
> As of today rpm's built from bigtop which are used to deploy with ambari right which is single source...Even projects are independent, Might not be the best way to create rpm's from project's like Hadoop right?
>
>> In the past, we used to get hdp-select rpm
> > | downloaded and installed from HDP repositories
>
> As HDP repo's will not available now, what's your suggestion for any new user who want to adopt their own stack..?
>
>
> On 04/07/22, 4:37 PM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>
> > > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > I dn't think, we'll required to install multiple versions same time. Even this can be handled.
>
> Could you elaborate the reason why we need the *-select if so?
>
>
> > IMO, as components rpm's are build with bigtop, having it in bigtop will be perfect choice. As we need to change the spec's.
>
> It does not make sense.
> While Hadoop rpm/deb are built with Bigtop, Hadoop is independent project.
> The following description implies that the *-select is updated along with Ambari
> and Ambari is the perfect place to host it.
>
> | These scripts are a basic necessity in the Ambari framework for the
> | installation of various Bigdata packages. The only major changes they would
> | receive is when we onboard new services and components to Ambari, else they
> | usually do not receive updates. In the past, we used to get hdp-select rpm
> | downloaded and installed from HDP repositories.
>
>
> On 2022/07/04 19:35, Battula, Brahma Reddy wrote:
> >> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > I dn't think, we'll required to install multiple versions same time. Even this can be handled.
> > Anyway Bigtop will be used to create the RPM's not for deploying the cluster with ambari now.
> >
> >> I feel hdp-select/bdp-select should belongs to Ambari
> >> since it is assuming the convention specific to HDP/BDP/Ambari.
> > > We can easily add packaging for the code under Ambari
> > > (as ambari-bdp-select for example) based on the existing stuff under
> > > bigtop-packages/*/ambari.
> >
> > IMO, as components rpm's are build with bigtop, having it in bigtop will be perfect choice. As we need to change the spec's.
> >
> >
> >
> > On 03/07/22, 9:56 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >
> > > For example, assuming that the following stack is installed:
> > >
> > > /usr/hdp/SOME_VERSION/hadoop/...
> > > /spark/...
> > > /zookeeper/...
> >
> > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > IIRC, HDP uses convention in which the product version is part of package name
> > for addressing this. like::
> >
> > $ rpm -qi hadoop_2_6_1_0_129
> > Name : hadoop_2_6_1_0_129
> > Version : 2.7.3.2.6.1.0
> > ...
> >
> >
> > > So if we accept bdp-select, we also have to develop a new feature to
> > > change install directories of the packages,
> > > keeping the current default for avoiding user-facing incompatibility.
> > > Otherwise bdp-select itself is useless.
> >
> > I don't like to bring the awkward package name convention to Bigtop
> > at least by default.
> >
> > I feel hdp-select/bdp-select should belongs to Ambari
> > since it is assuming the convention specific to HDP/BDP/Ambari.
> > We can easily add packaging for the code under Ambari
> > (as ambari-bdp-select for example) based on the existing stuff under
> > bigtop-packages/*/ambari.
> >
> >
> > Masatake Iwasaki
> >
> > On 2022/07/03 7:17, Kengo Seki wrote:
> > > Thank you for proposing this, Viraj and Brahma.
> > > This proposal may feel sudden to someone, so let me explain some context,
> > > mainly to the Bigtop community.
> > >
> > > Ambari went to Attic once due to inactivity,
> > > but some of its users and developers are reviving it now.
> > > From the Bigtop community, Roman and Evans undertook the role of
> > > initial PMC members,
> > > and Jun, Yuqi, Ganesh, Masatake, and I are also going to support it.
> > >
> > > The default stack of Ambari was HDP, but it has gone behind paywall,
> > > so we have to add an alternative stack in the next release of Ambari.
> > > Viraj and Brahma are planning to leverage Bigtop packages for that purpose,
> > > and that stack is tentatively named BDP (BigData Platform).
> > >
> > > We would also like to take over a feature called hdp-select,
> > > which enables users to switch the current stack easily with symlink.
> > > For example, assuming that the following stack is installed:
> > >
> > > /usr/hdp/SOME_VERSION/hadoop/...
> > > /spark/...
> > > /zookeeper/...
> > >
> > > /etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks of
> > > /usr/hdp/SOME_VERSION/hadoop/etc, /usr/hdp/SOME_VERSION/hadoop/var/lib,
> > > /usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
> > >
> > > Then the new stack is installed under /usr/hdp/NEW_VERSION,
> > > users can run hdp-select to switch the symlinks to the new directories
> > > for upgrading the stack.
> > > (Is my understanding correct? Correct me if I'm wrong, Viraj and Brahma)
> > >
> > > hdp-select was provided as a RPM/DEB package just like other packages
> > > HDP provided,
> > > so it is user-friendly to provide bdp-select (the BDP version of
> > > hdp-select) as well.
> > > This is the background of Viraj's proposal.
> > >
> > > But there is a problem here to leverage Bigtop packages in this manner.
> > > Bigtop respects Linux's Filesystem Hierarchy Standard,
> > > so it doesn't install files into a single place (/usr/hdp/VERSION in
> > > the example above),
> > > but directly into /etc, /usr, /var and so on.
> > > So if we accept bdp-select, we also have to develop a new feature to
> > > change install directories of the packages,
> > > keeping the current default for avoiding user-facing incompatibility.
> > > Otherwise bdp-select itself is useless.
> > > But it will be a tough work, because installation paths are hard-coded
> > > in the RPM specs and DEB packaging scripts now.
> > >
> > > Based on the above, how about creating a new branch for adding hdp-select
> > > and developing the feature to switch installation paths?
> > > After finishing the work on that branch and ensuring that it works expectedly,
> > > we can merge it into master, I think.
> > >
> > > Kengo Seki <se...@apache.org>
> > >
> > > On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
> > > <bb...@visa.com.invalid> wrote:
> > >>
> > >> Thanks @Viraj Jasani to start discussing on this.
> > >>
> > >> IMO, For upcoming ambari release(2.7.7) , we should have select other than HDP so that people can start using the ambari without HDP.
> > >>
> > >> I am +1(non-binding) on this approach to have selects in bigtop code. May be for long term , we can think for tarballs or mpacks which can go in mabari trunk.
> > >>
> > >>
> > >> On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
> > >>
> > >> Hi Ambari/Bigtop dev,
> > >>
> > >> As per the new roadmap of Apache Ambari, we would like to propose moving
> > >> certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > >> so that their rpm installation could be managed independently.
> > >> These scripts are a basic necessity in the Ambari framework for the
> > >> installation of various Bigdata packages. The only major changes they would
> > >> receive is when we onboard new services and components to Ambari, else they
> > >> usually do not receive updates. In the past, we used to get hdp-select rpm
> > >> downloaded and installed from HDP repositories.
> > >>
> > >> We have still not officially finalized the new replacement name for
> > >> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > >> the purpose of bdp-select and conf-select remains the same.
> > >>
> >
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
> If it is the tool to switch distribution to Bigtop and
> does not care about other distributions,
> hosting it in Bigtop as bigtop-select would make sense.
> If the tool need to care about distribution other than Bigtop,
> it should be under Ambari.
All the component rpm's creation[1] will be happening through bigtop only right which is used for Ambari cluster deployment.?
Ambari is not creating any rpm's right.
We can have as separate module , So, whoever uses[1] they can change *-select accordingly.
1. https://github.com/apache/bigtop/tree/master/bigtop-packages/src/rpm
On 05/07/22, 6:25 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> Firstly we'll not multiple select's right..? We can have distro-select and conf-select which can be included as part of the bigtop code. User's can adopt it and even they can write their own. And user will not deploy with multiple selects right, as they can get the conflicts..
If it is the tool to switch distribution to Bigtop and
does not care about other distributions,
hosting it in Bigtop as bigtop-select would make sense.
If the tool need to care about distribution other than Bigtop,
it should be under Ambari.
On 2022/07/04 23:39, Battula, Brahma Reddy wrote:
>> Could you elaborate the reason why we need the *-select if so?
>
> Firstly we'll not multiple select's right..? We can have distro-select and conf-select which can be included as part of the bigtop code. User's can adopt it and even they can write their own. And user will not deploy with multiple selects right, as they can get the conflicts..
>
>> It does not make sense.
>> While Hadoop rpm/deb are built with Bigtop, Hadoop is independent project.
>
> As of today rpm's built from bigtop which are used to deploy with ambari right which is single source...Even projects are independent, Might not be the best way to create rpm's from project's like Hadoop right?
>
>> In the past, we used to get hdp-select rpm
> > | downloaded and installed from HDP repositories
>
> As HDP repo's will not available now, what's your suggestion for any new user who want to adopt their own stack..?
>
>
> On 04/07/22, 4:37 PM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>
> > > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > I dn't think, we'll required to install multiple versions same time. Even this can be handled.
>
> Could you elaborate the reason why we need the *-select if so?
>
>
> > IMO, as components rpm's are build with bigtop, having it in bigtop will be perfect choice. As we need to change the spec's.
>
> It does not make sense.
> While Hadoop rpm/deb are built with Bigtop, Hadoop is independent project.
> The following description implies that the *-select is updated along with Ambari
> and Ambari is the perfect place to host it.
>
> | These scripts are a basic necessity in the Ambari framework for the
> | installation of various Bigdata packages. The only major changes they would
> | receive is when we onboard new services and components to Ambari, else they
> | usually do not receive updates. In the past, we used to get hdp-select rpm
> | downloaded and installed from HDP repositories.
>
>
> On 2022/07/04 19:35, Battula, Brahma Reddy wrote:
> >> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > I dn't think, we'll required to install multiple versions same time. Even this can be handled.
> > Anyway Bigtop will be used to create the RPM's not for deploying the cluster with ambari now.
> >
> >> I feel hdp-select/bdp-select should belongs to Ambari
> >> since it is assuming the convention specific to HDP/BDP/Ambari.
> > > We can easily add packaging for the code under Ambari
> > > (as ambari-bdp-select for example) based on the existing stuff under
> > > bigtop-packages/*/ambari.
> >
> > IMO, as components rpm's are build with bigtop, having it in bigtop will be perfect choice. As we need to change the spec's.
> >
> >
> >
> > On 03/07/22, 9:56 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >
> > > For example, assuming that the following stack is installed:
> > >
> > > /usr/hdp/SOME_VERSION/hadoop/...
> > > /spark/...
> > > /zookeeper/...
> >
> > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > IIRC, HDP uses convention in which the product version is part of package name
> > for addressing this. like::
> >
> > $ rpm -qi hadoop_2_6_1_0_129
> > Name : hadoop_2_6_1_0_129
> > Version : 2.7.3.2.6.1.0
> > ...
> >
> >
> > > So if we accept bdp-select, we also have to develop a new feature to
> > > change install directories of the packages,
> > > keeping the current default for avoiding user-facing incompatibility.
> > > Otherwise bdp-select itself is useless.
> >
> > I don't like to bring the awkward package name convention to Bigtop
> > at least by default.
> >
> > I feel hdp-select/bdp-select should belongs to Ambari
> > since it is assuming the convention specific to HDP/BDP/Ambari.
> > We can easily add packaging for the code under Ambari
> > (as ambari-bdp-select for example) based on the existing stuff under
> > bigtop-packages/*/ambari.
> >
> >
> > Masatake Iwasaki
> >
> > On 2022/07/03 7:17, Kengo Seki wrote:
> > > Thank you for proposing this, Viraj and Brahma.
> > > This proposal may feel sudden to someone, so let me explain some context,
> > > mainly to the Bigtop community.
> > >
> > > Ambari went to Attic once due to inactivity,
> > > but some of its users and developers are reviving it now.
> > > From the Bigtop community, Roman and Evans undertook the role of
> > > initial PMC members,
> > > and Jun, Yuqi, Ganesh, Masatake, and I are also going to support it.
> > >
> > > The default stack of Ambari was HDP, but it has gone behind paywall,
> > > so we have to add an alternative stack in the next release of Ambari.
> > > Viraj and Brahma are planning to leverage Bigtop packages for that purpose,
> > > and that stack is tentatively named BDP (BigData Platform).
> > >
> > > We would also like to take over a feature called hdp-select,
> > > which enables users to switch the current stack easily with symlink.
> > > For example, assuming that the following stack is installed:
> > >
> > > /usr/hdp/SOME_VERSION/hadoop/...
> > > /spark/...
> > > /zookeeper/...
> > >
> > > /etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks of
> > > /usr/hdp/SOME_VERSION/hadoop/etc, /usr/hdp/SOME_VERSION/hadoop/var/lib,
> > > /usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
> > >
> > > Then the new stack is installed under /usr/hdp/NEW_VERSION,
> > > users can run hdp-select to switch the symlinks to the new directories
> > > for upgrading the stack.
> > > (Is my understanding correct? Correct me if I'm wrong, Viraj and Brahma)
> > >
> > > hdp-select was provided as a RPM/DEB package just like other packages
> > > HDP provided,
> > > so it is user-friendly to provide bdp-select (the BDP version of
> > > hdp-select) as well.
> > > This is the background of Viraj's proposal.
> > >
> > > But there is a problem here to leverage Bigtop packages in this manner.
> > > Bigtop respects Linux's Filesystem Hierarchy Standard,
> > > so it doesn't install files into a single place (/usr/hdp/VERSION in
> > > the example above),
> > > but directly into /etc, /usr, /var and so on.
> > > So if we accept bdp-select, we also have to develop a new feature to
> > > change install directories of the packages,
> > > keeping the current default for avoiding user-facing incompatibility.
> > > Otherwise bdp-select itself is useless.
> > > But it will be a tough work, because installation paths are hard-coded
> > > in the RPM specs and DEB packaging scripts now.
> > >
> > > Based on the above, how about creating a new branch for adding hdp-select
> > > and developing the feature to switch installation paths?
> > > After finishing the work on that branch and ensuring that it works expectedly,
> > > we can merge it into master, I think.
> > >
> > > Kengo Seki <se...@apache.org>
> > >
> > > On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
> > > <bb...@visa.com.invalid> wrote:
> > >>
> > >> Thanks @Viraj Jasani to start discussing on this.
> > >>
> > >> IMO, For upcoming ambari release(2.7.7) , we should have select other than HDP so that people can start using the ambari without HDP.
> > >>
> > >> I am +1(non-binding) on this approach to have selects in bigtop code. May be for long term , we can think for tarballs or mpacks which can go in mabari trunk.
> > >>
> > >>
> > >> On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
> > >>
> > >> Hi Ambari/Bigtop dev,
> > >>
> > >> As per the new roadmap of Apache Ambari, we would like to propose moving
> > >> certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > >> so that their rpm installation could be managed independently.
> > >> These scripts are a basic necessity in the Ambari framework for the
> > >> installation of various Bigdata packages. The only major changes they would
> > >> receive is when we onboard new services and components to Ambari, else they
> > >> usually do not receive updates. In the past, we used to get hdp-select rpm
> > >> downloaded and installed from HDP repositories.
> > >>
> > >> We have still not officially finalized the new replacement name for
> > >> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > >> the purpose of bdp-select and conf-select remains the same.
> > >>
> >
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
> On the other hand, it becomes bit more complex to keep and manage
> them within Ambari as well.
Why?
> Moreover the only time they get any changes is
> when we need to onboard new service to Ambari.
Are Ambari committers happy to lose their control over such a module?
On 2022/07/05 13:06, Viraj Jasani wrote:
> Hi Masatake,
>
> Ambari needs rpms of select package just like we need rpms of the Bigdata
> packages.
>
> At my place, we follow the practice of keeping hdp-select and conf-select
> as separate scripts as part of a new github project and let bigtop generate
> rpms from this github source. For opensource community, I think it might
> not make much sense to create a new git repo just to maintain two select
> scripts. On the other hand, it becomes bit more complex to keep and manage
> them within Ambari as well. Moreover the only time they get any changes is
> when we need to onboard new service to Ambari. Hence I believe keeping
> these two scripts within bigtop would be bit more simplified for opensource
> community. Bigtop can generate rpms for *-select package just like it does
> for bigtop-utils for instance and it’s going to be quite lightweight.
>
>
> On Mon, Jul 4, 2022 at 5:54 PM Masatake Iwasaki <iw...@oss.nttdata.co.jp>
> wrote:
>
>>> Firstly we'll not multiple select's right..? We can have distro-select
>> and conf-select which can be included as part of the bigtop code. User's
>> can adopt it and even they can write their own. And user will not deploy
>> with multiple selects right, as they can get the conflicts..
>>
>> If it is the tool to switch distribution to Bigtop and
>> does not care about other distributions,
>> hosting it in Bigtop as bigtop-select would make sense.
>> If the tool need to care about distribution other than Bigtop,
>> it should be under Ambari.
>>
>>
>> On 2022/07/04 23:39, Battula, Brahma Reddy wrote:
>>>> Could you elaborate the reason why we need the *-select if so?
>>>
>>> Firstly we'll not multiple select's right..? We can have distro-select
>> and conf-select which can be included as part of the bigtop code. User's
>> can adopt it and even they can write their own. And user will not deploy
>> with multiple selects right, as they can get the conflicts..
>>>
>>>> It does not make sense.
>>>> While Hadoop rpm/deb are built with Bigtop, Hadoop is independent
>> project.
>>>
>>> As of today rpm's built from bigtop which are used to deploy with ambari
>> right which is single source...Even projects are independent, Might not be
>> the best way to create rpm's from project's like Hadoop right?
>>>
>>>> In the past, we used to get hdp-select rpm
>>> > | downloaded and installed from HDP repositories
>>>
>>> As HDP repo's will not available now, what's your suggestion for any new
>> user who want to adopt their own stack..?
>>>
>>>
>>> On 04/07/22, 4:37 PM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp>
>> wrote:
>>>
>>> > > Multiple versions of the same package (deb/rpm) can not be
>> installed at the same time.
>>> > I dn't think, we'll required to install multiple versions same
>> time. Even this can be handled.
>>>
>>> Could you elaborate the reason why we need the *-select if so?
>>>
>>>
>>> > IMO, as components rpm's are build with bigtop, having it in
>> bigtop will be perfect choice. As we need to change the spec's.
>>>
>>> It does not make sense.
>>> While Hadoop rpm/deb are built with Bigtop, Hadoop is independent
>> project.
>>> The following description implies that the *-select is updated
>> along with Ambari
>>> and Ambari is the perfect place to host it.
>>>
>>> | These scripts are a basic necessity in the Ambari framework for
>> the
>>> | installation of various Bigdata packages. The only major changes
>> they would
>>> | receive is when we onboard new services and components to Ambari,
>> else they
>>> | usually do not receive updates. In the past, we used to get
>> hdp-select rpm
>>> | downloaded and installed from HDP repositories.
>>>
>>>
>>> On 2022/07/04 19:35, Battula, Brahma Reddy wrote:
>>> >> Multiple versions of the same package (deb/rpm) can not be
>> installed at the same time.
>>> > I dn't think, we'll required to install multiple versions same
>> time. Even this can be handled.
>>> > Anyway Bigtop will be used to create the RPM's not for deploying
>> the cluster with ambari now.
>>> >
>>> >> I feel hdp-select/bdp-select should belongs to Ambari
>>> >> since it is assuming the convention specific to HDP/BDP/Ambari.
>>> > > We can easily add packaging for the code under Ambari
>>> > > (as ambari-bdp-select for example) based on the existing
>> stuff under
>>> > > bigtop-packages/*/ambari.
>>> >
>>> > IMO, as components rpm's are build with bigtop, having it in
>> bigtop will be perfect choice. As we need to change the spec's.
>>> >
>>> >
>>> >
>>> > On 03/07/22, 9:56 AM, "Masatake Iwasaki" <
>> iwasakims@oss.nttdata.co.jp> wrote:
>>> >
>>> > > For example, assuming that the following stack is
>> installed:
>>> > >
>>> > > /usr/hdp/SOME_VERSION/hadoop/...
>>> > > /spark/...
>>> > > /zookeeper/...
>>> >
>>> > Multiple versions of the same package (deb/rpm) can not be
>> installed at the same time.
>>> > IIRC, HDP uses convention in which the product version is
>> part of package name
>>> > for addressing this. like::
>>> >
>>> > $ rpm -qi hadoop_2_6_1_0_129
>>> > Name : hadoop_2_6_1_0_129
>>> > Version : 2.7.3.2.6.1.0
>>> > ...
>>> >
>>> >
>>> > > So if we accept bdp-select, we also have to develop a new
>> feature to
>>> > > change install directories of the packages,
>>> > > keeping the current default for avoiding user-facing
>> incompatibility.
>>> > > Otherwise bdp-select itself is useless.
>>> >
>>> > I don't like to bring the awkward package name convention to
>> Bigtop
>>> > at least by default.
>>> >
>>> > I feel hdp-select/bdp-select should belongs to Ambari
>>> > since it is assuming the convention specific to
>> HDP/BDP/Ambari.
>>> > We can easily add packaging for the code under Ambari
>>> > (as ambari-bdp-select for example) based on the existing
>> stuff under
>>> > bigtop-packages/*/ambari.
>>> >
>>> >
>>> > Masatake Iwasaki
>>> >
>>> > On 2022/07/03 7:17, Kengo Seki wrote:
>>> > > Thank you for proposing this, Viraj and Brahma.
>>> > > This proposal may feel sudden to someone, so let me
>> explain some context,
>>> > > mainly to the Bigtop community.
>>> > >
>>> > > Ambari went to Attic once due to inactivity,
>>> > > but some of its users and developers are reviving it now.
>>> > > From the Bigtop community, Roman and Evans undertook the
>> role of
>>> > > initial PMC members,
>>> > > and Jun, Yuqi, Ganesh, Masatake, and I are also going to
>> support it.
>>> > >
>>> > > The default stack of Ambari was HDP, but it has gone
>> behind paywall,
>>> > > so we have to add an alternative stack in the next release
>> of Ambari.
>>> > > Viraj and Brahma are planning to leverage Bigtop packages
>> for that purpose,
>>> > > and that stack is tentatively named BDP (BigData Platform).
>>> > >
>>> > > We would also like to take over a feature called
>> hdp-select,
>>> > > which enables users to switch the current stack easily
>> with symlink.
>>> > > For example, assuming that the following stack is
>> installed:
>>> > >
>>> > > /usr/hdp/SOME_VERSION/hadoop/...
>>> > > /spark/...
>>> > > /zookeeper/...
>>> > >
>>> > > /etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks
>> of
>>> > > /usr/hdp/SOME_VERSION/hadoop/etc,
>> /usr/hdp/SOME_VERSION/hadoop/var/lib,
>>> > > /usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
>>> > >
>>> > > Then the new stack is installed under /usr/hdp/NEW_VERSION,
>>> > > users can run hdp-select to switch the symlinks to the new
>> directories
>>> > > for upgrading the stack.
>>> > > (Is my understanding correct? Correct me if I'm wrong,
>> Viraj and Brahma)
>>> > >
>>> > > hdp-select was provided as a RPM/DEB package just like
>> other packages
>>> > > HDP provided,
>>> > > so it is user-friendly to provide bdp-select (the BDP
>> version of
>>> > > hdp-select) as well.
>>> > > This is the background of Viraj's proposal.
>>> > >
>>> > > But there is a problem here to leverage Bigtop packages in
>> this manner.
>>> > > Bigtop respects Linux's Filesystem Hierarchy Standard,
>>> > > so it doesn't install files into a single place
>> (/usr/hdp/VERSION in
>>> > > the example above),
>>> > > but directly into /etc, /usr, /var and so on.
>>> > > So if we accept bdp-select, we also have to develop a new
>> feature to
>>> > > change install directories of the packages,
>>> > > keeping the current default for avoiding user-facing
>> incompatibility.
>>> > > Otherwise bdp-select itself is useless.
>>> > > But it will be a tough work, because installation paths
>> are hard-coded
>>> > > in the RPM specs and DEB packaging scripts now.
>>> > >
>>> > > Based on the above, how about creating a new branch for
>> adding hdp-select
>>> > > and developing the feature to switch installation paths?
>>> > > After finishing the work on that branch and ensuring that
>> it works expectedly,
>>> > > we can merge it into master, I think.
>>> > >
>>> > > Kengo Seki <se...@apache.org>
>>> > >
>>> > > On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
>>> > > <bb...@visa.com.invalid> wrote:
>>> > >>
>>> > >> Thanks @Viraj Jasani to start discussing on this.
>>> > >>
>>> > >> IMO, For upcoming ambari release(2.7.7) , we should have
>> select other than HDP so that people can start using the ambari without HDP.
>>> > >>
>>> > >> I am +1(non-binding) on this approach to have selects in
>> bigtop code. May be for long term , we can think for tarballs or mpacks
>> which can go in mabari trunk.
>>> > >>
>>> > >>
>>> > >> On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org>
>> wrote:
>>> > >>
>>> > >> Hi Ambari/Bigtop dev,
>>> > >>
>>> > >> As per the new roadmap of Apache Ambari, we would
>> like to propose moving
>>> > >> certain scripts (previously known as hdp-select and
>> conf-select) to Bigtop
>>> > >> so that their rpm installation could be managed
>> independently.
>>> > >> These scripts are a basic necessity in the Ambari
>> framework for the
>>> > >> installation of various Bigdata packages. The only
>> major changes they would
>>> > >> receive is when we onboard new services and
>> components to Ambari, else they
>>> > >> usually do not receive updates. In the past, we used
>> to get hdp-select rpm
>>> > >> downloaded and installed from HDP repositories.
>>> > >>
>>> > >> We have still not officially finalized the new
>> replacement name for
>>> > >> hdp-select, it would likely be bdp-select (bdp:
>> BigData Platform). However,
>>> > >> the purpose of bdp-select and conf-select remains
>> the same.
>>> > >>
>>> >
>>>
>>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Viraj Jasani <vj...@apache.org>.
Hi Masatake,
Ambari needs rpms of select package just like we need rpms of the Bigdata
packages.
At my place, we follow the practice of keeping hdp-select and conf-select
as separate scripts as part of a new github project and let bigtop generate
rpms from this github source. For opensource community, I think it might
not make much sense to create a new git repo just to maintain two select
scripts. On the other hand, it becomes bit more complex to keep and manage
them within Ambari as well. Moreover the only time they get any changes is
when we need to onboard new service to Ambari. Hence I believe keeping
these two scripts within bigtop would be bit more simplified for opensource
community. Bigtop can generate rpms for *-select package just like it does
for bigtop-utils for instance and it’s going to be quite lightweight.
On Mon, Jul 4, 2022 at 5:54 PM Masatake Iwasaki <iw...@oss.nttdata.co.jp>
wrote:
> > Firstly we'll not multiple select's right..? We can have distro-select
> and conf-select which can be included as part of the bigtop code. User's
> can adopt it and even they can write their own. And user will not deploy
> with multiple selects right, as they can get the conflicts..
>
> If it is the tool to switch distribution to Bigtop and
> does not care about other distributions,
> hosting it in Bigtop as bigtop-select would make sense.
> If the tool need to care about distribution other than Bigtop,
> it should be under Ambari.
>
>
> On 2022/07/04 23:39, Battula, Brahma Reddy wrote:
> >> Could you elaborate the reason why we need the *-select if so?
> >
> > Firstly we'll not multiple select's right..? We can have distro-select
> and conf-select which can be included as part of the bigtop code. User's
> can adopt it and even they can write their own. And user will not deploy
> with multiple selects right, as they can get the conflicts..
> >
> >> It does not make sense.
> >> While Hadoop rpm/deb are built with Bigtop, Hadoop is independent
> project.
> >
> > As of today rpm's built from bigtop which are used to deploy with ambari
> right which is single source...Even projects are independent, Might not be
> the best way to create rpm's from project's like Hadoop right?
> >
> >> In the past, we used to get hdp-select rpm
> > > | downloaded and installed from HDP repositories
> >
> > As HDP repo's will not available now, what's your suggestion for any new
> user who want to adopt their own stack..?
> >
> >
> > On 04/07/22, 4:37 PM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp>
> wrote:
> >
> > > > Multiple versions of the same package (deb/rpm) can not be
> installed at the same time.
> > > I dn't think, we'll required to install multiple versions same
> time. Even this can be handled.
> >
> > Could you elaborate the reason why we need the *-select if so?
> >
> >
> > > IMO, as components rpm's are build with bigtop, having it in
> bigtop will be perfect choice. As we need to change the spec's.
> >
> > It does not make sense.
> > While Hadoop rpm/deb are built with Bigtop, Hadoop is independent
> project.
> > The following description implies that the *-select is updated
> along with Ambari
> > and Ambari is the perfect place to host it.
> >
> > | These scripts are a basic necessity in the Ambari framework for
> the
> > | installation of various Bigdata packages. The only major changes
> they would
> > | receive is when we onboard new services and components to Ambari,
> else they
> > | usually do not receive updates. In the past, we used to get
> hdp-select rpm
> > | downloaded and installed from HDP repositories.
> >
> >
> > On 2022/07/04 19:35, Battula, Brahma Reddy wrote:
> > >> Multiple versions of the same package (deb/rpm) can not be
> installed at the same time.
> > > I dn't think, we'll required to install multiple versions same
> time. Even this can be handled.
> > > Anyway Bigtop will be used to create the RPM's not for deploying
> the cluster with ambari now.
> > >
> > >> I feel hdp-select/bdp-select should belongs to Ambari
> > >> since it is assuming the convention specific to HDP/BDP/Ambari.
> > > > We can easily add packaging for the code under Ambari
> > > > (as ambari-bdp-select for example) based on the existing
> stuff under
> > > > bigtop-packages/*/ambari.
> > >
> > > IMO, as components rpm's are build with bigtop, having it in
> bigtop will be perfect choice. As we need to change the spec's.
> > >
> > >
> > >
> > > On 03/07/22, 9:56 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.co.jp> wrote:
> > >
> > > > For example, assuming that the following stack is
> installed:
> > > >
> > > > /usr/hdp/SOME_VERSION/hadoop/...
> > > > /spark/...
> > > > /zookeeper/...
> > >
> > > Multiple versions of the same package (deb/rpm) can not be
> installed at the same time.
> > > IIRC, HDP uses convention in which the product version is
> part of package name
> > > for addressing this. like::
> > >
> > > $ rpm -qi hadoop_2_6_1_0_129
> > > Name : hadoop_2_6_1_0_129
> > > Version : 2.7.3.2.6.1.0
> > > ...
> > >
> > >
> > > > So if we accept bdp-select, we also have to develop a new
> feature to
> > > > change install directories of the packages,
> > > > keeping the current default for avoiding user-facing
> incompatibility.
> > > > Otherwise bdp-select itself is useless.
> > >
> > > I don't like to bring the awkward package name convention to
> Bigtop
> > > at least by default.
> > >
> > > I feel hdp-select/bdp-select should belongs to Ambari
> > > since it is assuming the convention specific to
> HDP/BDP/Ambari.
> > > We can easily add packaging for the code under Ambari
> > > (as ambari-bdp-select for example) based on the existing
> stuff under
> > > bigtop-packages/*/ambari.
> > >
> > >
> > > Masatake Iwasaki
> > >
> > > On 2022/07/03 7:17, Kengo Seki wrote:
> > > > Thank you for proposing this, Viraj and Brahma.
> > > > This proposal may feel sudden to someone, so let me
> explain some context,
> > > > mainly to the Bigtop community.
> > > >
> > > > Ambari went to Attic once due to inactivity,
> > > > but some of its users and developers are reviving it now.
> > > > From the Bigtop community, Roman and Evans undertook the
> role of
> > > > initial PMC members,
> > > > and Jun, Yuqi, Ganesh, Masatake, and I are also going to
> support it.
> > > >
> > > > The default stack of Ambari was HDP, but it has gone
> behind paywall,
> > > > so we have to add an alternative stack in the next release
> of Ambari.
> > > > Viraj and Brahma are planning to leverage Bigtop packages
> for that purpose,
> > > > and that stack is tentatively named BDP (BigData Platform).
> > > >
> > > > We would also like to take over a feature called
> hdp-select,
> > > > which enables users to switch the current stack easily
> with symlink.
> > > > For example, assuming that the following stack is
> installed:
> > > >
> > > > /usr/hdp/SOME_VERSION/hadoop/...
> > > > /spark/...
> > > > /zookeeper/...
> > > >
> > > > /etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks
> of
> > > > /usr/hdp/SOME_VERSION/hadoop/etc,
> /usr/hdp/SOME_VERSION/hadoop/var/lib,
> > > > /usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
> > > >
> > > > Then the new stack is installed under /usr/hdp/NEW_VERSION,
> > > > users can run hdp-select to switch the symlinks to the new
> directories
> > > > for upgrading the stack.
> > > > (Is my understanding correct? Correct me if I'm wrong,
> Viraj and Brahma)
> > > >
> > > > hdp-select was provided as a RPM/DEB package just like
> other packages
> > > > HDP provided,
> > > > so it is user-friendly to provide bdp-select (the BDP
> version of
> > > > hdp-select) as well.
> > > > This is the background of Viraj's proposal.
> > > >
> > > > But there is a problem here to leverage Bigtop packages in
> this manner.
> > > > Bigtop respects Linux's Filesystem Hierarchy Standard,
> > > > so it doesn't install files into a single place
> (/usr/hdp/VERSION in
> > > > the example above),
> > > > but directly into /etc, /usr, /var and so on.
> > > > So if we accept bdp-select, we also have to develop a new
> feature to
> > > > change install directories of the packages,
> > > > keeping the current default for avoiding user-facing
> incompatibility.
> > > > Otherwise bdp-select itself is useless.
> > > > But it will be a tough work, because installation paths
> are hard-coded
> > > > in the RPM specs and DEB packaging scripts now.
> > > >
> > > > Based on the above, how about creating a new branch for
> adding hdp-select
> > > > and developing the feature to switch installation paths?
> > > > After finishing the work on that branch and ensuring that
> it works expectedly,
> > > > we can merge it into master, I think.
> > > >
> > > > Kengo Seki <se...@apache.org>
> > > >
> > > > On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
> > > > <bb...@visa.com.invalid> wrote:
> > > >>
> > > >> Thanks @Viraj Jasani to start discussing on this.
> > > >>
> > > >> IMO, For upcoming ambari release(2.7.7) , we should have
> select other than HDP so that people can start using the ambari without HDP.
> > > >>
> > > >> I am +1(non-binding) on this approach to have selects in
> bigtop code. May be for long term , we can think for tarballs or mpacks
> which can go in mabari trunk.
> > > >>
> > > >>
> > > >> On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org>
> wrote:
> > > >>
> > > >> Hi Ambari/Bigtop dev,
> > > >>
> > > >> As per the new roadmap of Apache Ambari, we would
> like to propose moving
> > > >> certain scripts (previously known as hdp-select and
> conf-select) to Bigtop
> > > >> so that their rpm installation could be managed
> independently.
> > > >> These scripts are a basic necessity in the Ambari
> framework for the
> > > >> installation of various Bigdata packages. The only
> major changes they would
> > > >> receive is when we onboard new services and
> components to Ambari, else they
> > > >> usually do not receive updates. In the past, we used
> to get hdp-select rpm
> > > >> downloaded and installed from HDP repositories.
> > > >>
> > > >> We have still not officially finalized the new
> replacement name for
> > > >> hdp-select, it would likely be bdp-select (bdp:
> BigData Platform). However,
> > > >> the purpose of bdp-select and conf-select remains
> the same.
> > > >>
> > >
> >
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Viraj Jasani <vj...@apache.org>.
Hi Masatake,
Ambari needs rpms of select package just like we need rpms of the Bigdata
packages.
At my place, we follow the practice of keeping hdp-select and conf-select
as separate scripts as part of a new github project and let bigtop generate
rpms from this github source. For opensource community, I think it might
not make much sense to create a new git repo just to maintain two select
scripts. On the other hand, it becomes bit more complex to keep and manage
them within Ambari as well. Moreover the only time they get any changes is
when we need to onboard new service to Ambari. Hence I believe keeping
these two scripts within bigtop would be bit more simplified for opensource
community. Bigtop can generate rpms for *-select package just like it does
for bigtop-utils for instance and it’s going to be quite lightweight.
On Mon, Jul 4, 2022 at 5:54 PM Masatake Iwasaki <iw...@oss.nttdata.co.jp>
wrote:
> > Firstly we'll not multiple select's right..? We can have distro-select
> and conf-select which can be included as part of the bigtop code. User's
> can adopt it and even they can write their own. And user will not deploy
> with multiple selects right, as they can get the conflicts..
>
> If it is the tool to switch distribution to Bigtop and
> does not care about other distributions,
> hosting it in Bigtop as bigtop-select would make sense.
> If the tool need to care about distribution other than Bigtop,
> it should be under Ambari.
>
>
> On 2022/07/04 23:39, Battula, Brahma Reddy wrote:
> >> Could you elaborate the reason why we need the *-select if so?
> >
> > Firstly we'll not multiple select's right..? We can have distro-select
> and conf-select which can be included as part of the bigtop code. User's
> can adopt it and even they can write their own. And user will not deploy
> with multiple selects right, as they can get the conflicts..
> >
> >> It does not make sense.
> >> While Hadoop rpm/deb are built with Bigtop, Hadoop is independent
> project.
> >
> > As of today rpm's built from bigtop which are used to deploy with ambari
> right which is single source...Even projects are independent, Might not be
> the best way to create rpm's from project's like Hadoop right?
> >
> >> In the past, we used to get hdp-select rpm
> > > | downloaded and installed from HDP repositories
> >
> > As HDP repo's will not available now, what's your suggestion for any new
> user who want to adopt their own stack..?
> >
> >
> > On 04/07/22, 4:37 PM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp>
> wrote:
> >
> > > > Multiple versions of the same package (deb/rpm) can not be
> installed at the same time.
> > > I dn't think, we'll required to install multiple versions same
> time. Even this can be handled.
> >
> > Could you elaborate the reason why we need the *-select if so?
> >
> >
> > > IMO, as components rpm's are build with bigtop, having it in
> bigtop will be perfect choice. As we need to change the spec's.
> >
> > It does not make sense.
> > While Hadoop rpm/deb are built with Bigtop, Hadoop is independent
> project.
> > The following description implies that the *-select is updated
> along with Ambari
> > and Ambari is the perfect place to host it.
> >
> > | These scripts are a basic necessity in the Ambari framework for
> the
> > | installation of various Bigdata packages. The only major changes
> they would
> > | receive is when we onboard new services and components to Ambari,
> else they
> > | usually do not receive updates. In the past, we used to get
> hdp-select rpm
> > | downloaded and installed from HDP repositories.
> >
> >
> > On 2022/07/04 19:35, Battula, Brahma Reddy wrote:
> > >> Multiple versions of the same package (deb/rpm) can not be
> installed at the same time.
> > > I dn't think, we'll required to install multiple versions same
> time. Even this can be handled.
> > > Anyway Bigtop will be used to create the RPM's not for deploying
> the cluster with ambari now.
> > >
> > >> I feel hdp-select/bdp-select should belongs to Ambari
> > >> since it is assuming the convention specific to HDP/BDP/Ambari.
> > > > We can easily add packaging for the code under Ambari
> > > > (as ambari-bdp-select for example) based on the existing
> stuff under
> > > > bigtop-packages/*/ambari.
> > >
> > > IMO, as components rpm's are build with bigtop, having it in
> bigtop will be perfect choice. As we need to change the spec's.
> > >
> > >
> > >
> > > On 03/07/22, 9:56 AM, "Masatake Iwasaki" <
> iwasakims@oss.nttdata.co.jp> wrote:
> > >
> > > > For example, assuming that the following stack is
> installed:
> > > >
> > > > /usr/hdp/SOME_VERSION/hadoop/...
> > > > /spark/...
> > > > /zookeeper/...
> > >
> > > Multiple versions of the same package (deb/rpm) can not be
> installed at the same time.
> > > IIRC, HDP uses convention in which the product version is
> part of package name
> > > for addressing this. like::
> > >
> > > $ rpm -qi hadoop_2_6_1_0_129
> > > Name : hadoop_2_6_1_0_129
> > > Version : 2.7.3.2.6.1.0
> > > ...
> > >
> > >
> > > > So if we accept bdp-select, we also have to develop a new
> feature to
> > > > change install directories of the packages,
> > > > keeping the current default for avoiding user-facing
> incompatibility.
> > > > Otherwise bdp-select itself is useless.
> > >
> > > I don't like to bring the awkward package name convention to
> Bigtop
> > > at least by default.
> > >
> > > I feel hdp-select/bdp-select should belongs to Ambari
> > > since it is assuming the convention specific to
> HDP/BDP/Ambari.
> > > We can easily add packaging for the code under Ambari
> > > (as ambari-bdp-select for example) based on the existing
> stuff under
> > > bigtop-packages/*/ambari.
> > >
> > >
> > > Masatake Iwasaki
> > >
> > > On 2022/07/03 7:17, Kengo Seki wrote:
> > > > Thank you for proposing this, Viraj and Brahma.
> > > > This proposal may feel sudden to someone, so let me
> explain some context,
> > > > mainly to the Bigtop community.
> > > >
> > > > Ambari went to Attic once due to inactivity,
> > > > but some of its users and developers are reviving it now.
> > > > From the Bigtop community, Roman and Evans undertook the
> role of
> > > > initial PMC members,
> > > > and Jun, Yuqi, Ganesh, Masatake, and I are also going to
> support it.
> > > >
> > > > The default stack of Ambari was HDP, but it has gone
> behind paywall,
> > > > so we have to add an alternative stack in the next release
> of Ambari.
> > > > Viraj and Brahma are planning to leverage Bigtop packages
> for that purpose,
> > > > and that stack is tentatively named BDP (BigData Platform).
> > > >
> > > > We would also like to take over a feature called
> hdp-select,
> > > > which enables users to switch the current stack easily
> with symlink.
> > > > For example, assuming that the following stack is
> installed:
> > > >
> > > > /usr/hdp/SOME_VERSION/hadoop/...
> > > > /spark/...
> > > > /zookeeper/...
> > > >
> > > > /etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks
> of
> > > > /usr/hdp/SOME_VERSION/hadoop/etc,
> /usr/hdp/SOME_VERSION/hadoop/var/lib,
> > > > /usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
> > > >
> > > > Then the new stack is installed under /usr/hdp/NEW_VERSION,
> > > > users can run hdp-select to switch the symlinks to the new
> directories
> > > > for upgrading the stack.
> > > > (Is my understanding correct? Correct me if I'm wrong,
> Viraj and Brahma)
> > > >
> > > > hdp-select was provided as a RPM/DEB package just like
> other packages
> > > > HDP provided,
> > > > so it is user-friendly to provide bdp-select (the BDP
> version of
> > > > hdp-select) as well.
> > > > This is the background of Viraj's proposal.
> > > >
> > > > But there is a problem here to leverage Bigtop packages in
> this manner.
> > > > Bigtop respects Linux's Filesystem Hierarchy Standard,
> > > > so it doesn't install files into a single place
> (/usr/hdp/VERSION in
> > > > the example above),
> > > > but directly into /etc, /usr, /var and so on.
> > > > So if we accept bdp-select, we also have to develop a new
> feature to
> > > > change install directories of the packages,
> > > > keeping the current default for avoiding user-facing
> incompatibility.
> > > > Otherwise bdp-select itself is useless.
> > > > But it will be a tough work, because installation paths
> are hard-coded
> > > > in the RPM specs and DEB packaging scripts now.
> > > >
> > > > Based on the above, how about creating a new branch for
> adding hdp-select
> > > > and developing the feature to switch installation paths?
> > > > After finishing the work on that branch and ensuring that
> it works expectedly,
> > > > we can merge it into master, I think.
> > > >
> > > > Kengo Seki <se...@apache.org>
> > > >
> > > > On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
> > > > <bb...@visa.com.invalid> wrote:
> > > >>
> > > >> Thanks @Viraj Jasani to start discussing on this.
> > > >>
> > > >> IMO, For upcoming ambari release(2.7.7) , we should have
> select other than HDP so that people can start using the ambari without HDP.
> > > >>
> > > >> I am +1(non-binding) on this approach to have selects in
> bigtop code. May be for long term , we can think for tarballs or mpacks
> which can go in mabari trunk.
> > > >>
> > > >>
> > > >> On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org>
> wrote:
> > > >>
> > > >> Hi Ambari/Bigtop dev,
> > > >>
> > > >> As per the new roadmap of Apache Ambari, we would
> like to propose moving
> > > >> certain scripts (previously known as hdp-select and
> conf-select) to Bigtop
> > > >> so that their rpm installation could be managed
> independently.
> > > >> These scripts are a basic necessity in the Ambari
> framework for the
> > > >> installation of various Bigdata packages. The only
> major changes they would
> > > >> receive is when we onboard new services and
> components to Ambari, else they
> > > >> usually do not receive updates. In the past, we used
> to get hdp-select rpm
> > > >> downloaded and installed from HDP repositories.
> > > >>
> > > >> We have still not officially finalized the new
> replacement name for
> > > >> hdp-select, it would likely be bdp-select (bdp:
> BigData Platform). However,
> > > >> the purpose of bdp-select and conf-select remains
> the same.
> > > >>
> > >
> >
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
> Firstly we'll not multiple select's right..? We can have distro-select and conf-select which can be included as part of the bigtop code. User's can adopt it and even they can write their own. And user will not deploy with multiple selects right, as they can get the conflicts..
If it is the tool to switch distribution to Bigtop and
does not care about other distributions,
hosting it in Bigtop as bigtop-select would make sense.
If the tool need to care about distribution other than Bigtop,
it should be under Ambari.
On 2022/07/04 23:39, Battula, Brahma Reddy wrote:
>> Could you elaborate the reason why we need the *-select if so?
>
> Firstly we'll not multiple select's right..? We can have distro-select and conf-select which can be included as part of the bigtop code. User's can adopt it and even they can write their own. And user will not deploy with multiple selects right, as they can get the conflicts..
>
>> It does not make sense.
>> While Hadoop rpm/deb are built with Bigtop, Hadoop is independent project.
>
> As of today rpm's built from bigtop which are used to deploy with ambari right which is single source...Even projects are independent, Might not be the best way to create rpm's from project's like Hadoop right?
>
>> In the past, we used to get hdp-select rpm
> > | downloaded and installed from HDP repositories
>
> As HDP repo's will not available now, what's your suggestion for any new user who want to adopt their own stack..?
>
>
> On 04/07/22, 4:37 PM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>
> > > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > I dn't think, we'll required to install multiple versions same time. Even this can be handled.
>
> Could you elaborate the reason why we need the *-select if so?
>
>
> > IMO, as components rpm's are build with bigtop, having it in bigtop will be perfect choice. As we need to change the spec's.
>
> It does not make sense.
> While Hadoop rpm/deb are built with Bigtop, Hadoop is independent project.
> The following description implies that the *-select is updated along with Ambari
> and Ambari is the perfect place to host it.
>
> | These scripts are a basic necessity in the Ambari framework for the
> | installation of various Bigdata packages. The only major changes they would
> | receive is when we onboard new services and components to Ambari, else they
> | usually do not receive updates. In the past, we used to get hdp-select rpm
> | downloaded and installed from HDP repositories.
>
>
> On 2022/07/04 19:35, Battula, Brahma Reddy wrote:
> >> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > I dn't think, we'll required to install multiple versions same time. Even this can be handled.
> > Anyway Bigtop will be used to create the RPM's not for deploying the cluster with ambari now.
> >
> >> I feel hdp-select/bdp-select should belongs to Ambari
> >> since it is assuming the convention specific to HDP/BDP/Ambari.
> > > We can easily add packaging for the code under Ambari
> > > (as ambari-bdp-select for example) based on the existing stuff under
> > > bigtop-packages/*/ambari.
> >
> > IMO, as components rpm's are build with bigtop, having it in bigtop will be perfect choice. As we need to change the spec's.
> >
> >
> >
> > On 03/07/22, 9:56 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> >
> > > For example, assuming that the following stack is installed:
> > >
> > > /usr/hdp/SOME_VERSION/hadoop/...
> > > /spark/...
> > > /zookeeper/...
> >
> > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> > IIRC, HDP uses convention in which the product version is part of package name
> > for addressing this. like::
> >
> > $ rpm -qi hadoop_2_6_1_0_129
> > Name : hadoop_2_6_1_0_129
> > Version : 2.7.3.2.6.1.0
> > ...
> >
> >
> > > So if we accept bdp-select, we also have to develop a new feature to
> > > change install directories of the packages,
> > > keeping the current default for avoiding user-facing incompatibility.
> > > Otherwise bdp-select itself is useless.
> >
> > I don't like to bring the awkward package name convention to Bigtop
> > at least by default.
> >
> > I feel hdp-select/bdp-select should belongs to Ambari
> > since it is assuming the convention specific to HDP/BDP/Ambari.
> > We can easily add packaging for the code under Ambari
> > (as ambari-bdp-select for example) based on the existing stuff under
> > bigtop-packages/*/ambari.
> >
> >
> > Masatake Iwasaki
> >
> > On 2022/07/03 7:17, Kengo Seki wrote:
> > > Thank you for proposing this, Viraj and Brahma.
> > > This proposal may feel sudden to someone, so let me explain some context,
> > > mainly to the Bigtop community.
> > >
> > > Ambari went to Attic once due to inactivity,
> > > but some of its users and developers are reviving it now.
> > > From the Bigtop community, Roman and Evans undertook the role of
> > > initial PMC members,
> > > and Jun, Yuqi, Ganesh, Masatake, and I are also going to support it.
> > >
> > > The default stack of Ambari was HDP, but it has gone behind paywall,
> > > so we have to add an alternative stack in the next release of Ambari.
> > > Viraj and Brahma are planning to leverage Bigtop packages for that purpose,
> > > and that stack is tentatively named BDP (BigData Platform).
> > >
> > > We would also like to take over a feature called hdp-select,
> > > which enables users to switch the current stack easily with symlink.
> > > For example, assuming that the following stack is installed:
> > >
> > > /usr/hdp/SOME_VERSION/hadoop/...
> > > /spark/...
> > > /zookeeper/...
> > >
> > > /etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks of
> > > /usr/hdp/SOME_VERSION/hadoop/etc, /usr/hdp/SOME_VERSION/hadoop/var/lib,
> > > /usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
> > >
> > > Then the new stack is installed under /usr/hdp/NEW_VERSION,
> > > users can run hdp-select to switch the symlinks to the new directories
> > > for upgrading the stack.
> > > (Is my understanding correct? Correct me if I'm wrong, Viraj and Brahma)
> > >
> > > hdp-select was provided as a RPM/DEB package just like other packages
> > > HDP provided,
> > > so it is user-friendly to provide bdp-select (the BDP version of
> > > hdp-select) as well.
> > > This is the background of Viraj's proposal.
> > >
> > > But there is a problem here to leverage Bigtop packages in this manner.
> > > Bigtop respects Linux's Filesystem Hierarchy Standard,
> > > so it doesn't install files into a single place (/usr/hdp/VERSION in
> > > the example above),
> > > but directly into /etc, /usr, /var and so on.
> > > So if we accept bdp-select, we also have to develop a new feature to
> > > change install directories of the packages,
> > > keeping the current default for avoiding user-facing incompatibility.
> > > Otherwise bdp-select itself is useless.
> > > But it will be a tough work, because installation paths are hard-coded
> > > in the RPM specs and DEB packaging scripts now.
> > >
> > > Based on the above, how about creating a new branch for adding hdp-select
> > > and developing the feature to switch installation paths?
> > > After finishing the work on that branch and ensuring that it works expectedly,
> > > we can merge it into master, I think.
> > >
> > > Kengo Seki <se...@apache.org>
> > >
> > > On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
> > > <bb...@visa.com.invalid> wrote:
> > >>
> > >> Thanks @Viraj Jasani to start discussing on this.
> > >>
> > >> IMO, For upcoming ambari release(2.7.7) , we should have select other than HDP so that people can start using the ambari without HDP.
> > >>
> > >> I am +1(non-binding) on this approach to have selects in bigtop code. May be for long term , we can think for tarballs or mpacks which can go in mabari trunk.
> > >>
> > >>
> > >> On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
> > >>
> > >> Hi Ambari/Bigtop dev,
> > >>
> > >> As per the new roadmap of Apache Ambari, we would like to propose moving
> > >> certain scripts (previously known as hdp-select and conf-select) to Bigtop
> > >> so that their rpm installation could be managed independently.
> > >> These scripts are a basic necessity in the Ambari framework for the
> > >> installation of various Bigdata packages. The only major changes they would
> > >> receive is when we onboard new services and components to Ambari, else they
> > >> usually do not receive updates. In the past, we used to get hdp-select rpm
> > >> downloaded and installed from HDP repositories.
> > >>
> > >> We have still not officially finalized the new replacement name for
> > >> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> > >> the purpose of bdp-select and conf-select remains the same.
> > >>
> >
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
> Could you elaborate the reason why we need the *-select if so?
Firstly we'll not multiple select's right..? We can have distro-select and conf-select which can be included as part of the bigtop code. User's can adopt it and even they can write their own. And user will not deploy with multiple selects right, as they can get the conflicts..
> It does not make sense.
> While Hadoop rpm/deb are built with Bigtop, Hadoop is independent project.
As of today rpm's built from bigtop which are used to deploy with ambari right which is single source...Even projects are independent, Might not be the best way to create rpm's from project's like Hadoop right?
> In the past, we used to get hdp-select rpm
> | downloaded and installed from HDP repositories
As HDP repo's will not available now, what's your suggestion for any new user who want to adopt their own stack..?
On 04/07/22, 4:37 PM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> I dn't think, we'll required to install multiple versions same time. Even this can be handled.
Could you elaborate the reason why we need the *-select if so?
> IMO, as components rpm's are build with bigtop, having it in bigtop will be perfect choice. As we need to change the spec's.
It does not make sense.
While Hadoop rpm/deb are built with Bigtop, Hadoop is independent project.
The following description implies that the *-select is updated along with Ambari
and Ambari is the perfect place to host it.
| These scripts are a basic necessity in the Ambari framework for the
| installation of various Bigdata packages. The only major changes they would
| receive is when we onboard new services and components to Ambari, else they
| usually do not receive updates. In the past, we used to get hdp-select rpm
| downloaded and installed from HDP repositories.
On 2022/07/04 19:35, Battula, Brahma Reddy wrote:
>> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> I dn't think, we'll required to install multiple versions same time. Even this can be handled.
> Anyway Bigtop will be used to create the RPM's not for deploying the cluster with ambari now.
>
>> I feel hdp-select/bdp-select should belongs to Ambari
>> since it is assuming the convention specific to HDP/BDP/Ambari.
> > We can easily add packaging for the code under Ambari
> > (as ambari-bdp-select for example) based on the existing stuff under
> > bigtop-packages/*/ambari.
>
> IMO, as components rpm's are build with bigtop, having it in bigtop will be perfect choice. As we need to change the spec's.
>
>
>
> On 03/07/22, 9:56 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>
> > For example, assuming that the following stack is installed:
> >
> > /usr/hdp/SOME_VERSION/hadoop/...
> > /spark/...
> > /zookeeper/...
>
> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> IIRC, HDP uses convention in which the product version is part of package name
> for addressing this. like::
>
> $ rpm -qi hadoop_2_6_1_0_129
> Name : hadoop_2_6_1_0_129
> Version : 2.7.3.2.6.1.0
> ...
>
>
> > So if we accept bdp-select, we also have to develop a new feature to
> > change install directories of the packages,
> > keeping the current default for avoiding user-facing incompatibility.
> > Otherwise bdp-select itself is useless.
>
> I don't like to bring the awkward package name convention to Bigtop
> at least by default.
>
> I feel hdp-select/bdp-select should belongs to Ambari
> since it is assuming the convention specific to HDP/BDP/Ambari.
> We can easily add packaging for the code under Ambari
> (as ambari-bdp-select for example) based on the existing stuff under
> bigtop-packages/*/ambari.
>
>
> Masatake Iwasaki
>
> On 2022/07/03 7:17, Kengo Seki wrote:
> > Thank you for proposing this, Viraj and Brahma.
> > This proposal may feel sudden to someone, so let me explain some context,
> > mainly to the Bigtop community.
> >
> > Ambari went to Attic once due to inactivity,
> > but some of its users and developers are reviving it now.
> > From the Bigtop community, Roman and Evans undertook the role of
> > initial PMC members,
> > and Jun, Yuqi, Ganesh, Masatake, and I are also going to support it.
> >
> > The default stack of Ambari was HDP, but it has gone behind paywall,
> > so we have to add an alternative stack in the next release of Ambari.
> > Viraj and Brahma are planning to leverage Bigtop packages for that purpose,
> > and that stack is tentatively named BDP (BigData Platform).
> >
> > We would also like to take over a feature called hdp-select,
> > which enables users to switch the current stack easily with symlink.
> > For example, assuming that the following stack is installed:
> >
> > /usr/hdp/SOME_VERSION/hadoop/...
> > /spark/...
> > /zookeeper/...
> >
> > /etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks of
> > /usr/hdp/SOME_VERSION/hadoop/etc, /usr/hdp/SOME_VERSION/hadoop/var/lib,
> > /usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
> >
> > Then the new stack is installed under /usr/hdp/NEW_VERSION,
> > users can run hdp-select to switch the symlinks to the new directories
> > for upgrading the stack.
> > (Is my understanding correct? Correct me if I'm wrong, Viraj and Brahma)
> >
> > hdp-select was provided as a RPM/DEB package just like other packages
> > HDP provided,
> > so it is user-friendly to provide bdp-select (the BDP version of
> > hdp-select) as well.
> > This is the background of Viraj's proposal.
> >
> > But there is a problem here to leverage Bigtop packages in this manner.
> > Bigtop respects Linux's Filesystem Hierarchy Standard,
> > so it doesn't install files into a single place (/usr/hdp/VERSION in
> > the example above),
> > but directly into /etc, /usr, /var and so on.
> > So if we accept bdp-select, we also have to develop a new feature to
> > change install directories of the packages,
> > keeping the current default for avoiding user-facing incompatibility.
> > Otherwise bdp-select itself is useless.
> > But it will be a tough work, because installation paths are hard-coded
> > in the RPM specs and DEB packaging scripts now.
> >
> > Based on the above, how about creating a new branch for adding hdp-select
> > and developing the feature to switch installation paths?
> > After finishing the work on that branch and ensuring that it works expectedly,
> > we can merge it into master, I think.
> >
> > Kengo Seki <se...@apache.org>
> >
> > On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
> > <bb...@visa.com.invalid> wrote:
> >>
> >> Thanks @Viraj Jasani to start discussing on this.
> >>
> >> IMO, For upcoming ambari release(2.7.7) , we should have select other than HDP so that people can start using the ambari without HDP.
> >>
> >> I am +1(non-binding) on this approach to have selects in bigtop code. May be for long term , we can think for tarballs or mpacks which can go in mabari trunk.
> >>
> >>
> >> On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
> >>
> >> Hi Ambari/Bigtop dev,
> >>
> >> As per the new roadmap of Apache Ambari, we would like to propose moving
> >> certain scripts (previously known as hdp-select and conf-select) to Bigtop
> >> so that their rpm installation could be managed independently.
> >> These scripts are a basic necessity in the Ambari framework for the
> >> installation of various Bigdata packages. The only major changes they would
> >> receive is when we onboard new services and components to Ambari, else they
> >> usually do not receive updates. In the past, we used to get hdp-select rpm
> >> downloaded and installed from HDP repositories.
> >>
> >> We have still not officially finalized the new replacement name for
> >> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> >> the purpose of bdp-select and conf-select remains the same.
> >>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
> Could you elaborate the reason why we need the *-select if so?
Firstly we'll not multiple select's right..? We can have distro-select and conf-select which can be included as part of the bigtop code. User's can adopt it and even they can write their own. And user will not deploy with multiple selects right, as they can get the conflicts..
> It does not make sense.
> While Hadoop rpm/deb are built with Bigtop, Hadoop is independent project.
As of today rpm's built from bigtop which are used to deploy with ambari right which is single source...Even projects are independent, Might not be the best way to create rpm's from project's like Hadoop right?
> In the past, we used to get hdp-select rpm
> | downloaded and installed from HDP repositories
As HDP repo's will not available now, what's your suggestion for any new user who want to adopt their own stack..?
On 04/07/22, 4:37 PM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> I dn't think, we'll required to install multiple versions same time. Even this can be handled.
Could you elaborate the reason why we need the *-select if so?
> IMO, as components rpm's are build with bigtop, having it in bigtop will be perfect choice. As we need to change the spec's.
It does not make sense.
While Hadoop rpm/deb are built with Bigtop, Hadoop is independent project.
The following description implies that the *-select is updated along with Ambari
and Ambari is the perfect place to host it.
| These scripts are a basic necessity in the Ambari framework for the
| installation of various Bigdata packages. The only major changes they would
| receive is when we onboard new services and components to Ambari, else they
| usually do not receive updates. In the past, we used to get hdp-select rpm
| downloaded and installed from HDP repositories.
On 2022/07/04 19:35, Battula, Brahma Reddy wrote:
>> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> I dn't think, we'll required to install multiple versions same time. Even this can be handled.
> Anyway Bigtop will be used to create the RPM's not for deploying the cluster with ambari now.
>
>> I feel hdp-select/bdp-select should belongs to Ambari
>> since it is assuming the convention specific to HDP/BDP/Ambari.
> > We can easily add packaging for the code under Ambari
> > (as ambari-bdp-select for example) based on the existing stuff under
> > bigtop-packages/*/ambari.
>
> IMO, as components rpm's are build with bigtop, having it in bigtop will be perfect choice. As we need to change the spec's.
>
>
>
> On 03/07/22, 9:56 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>
> > For example, assuming that the following stack is installed:
> >
> > /usr/hdp/SOME_VERSION/hadoop/...
> > /spark/...
> > /zookeeper/...
>
> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> IIRC, HDP uses convention in which the product version is part of package name
> for addressing this. like::
>
> $ rpm -qi hadoop_2_6_1_0_129
> Name : hadoop_2_6_1_0_129
> Version : 2.7.3.2.6.1.0
> ...
>
>
> > So if we accept bdp-select, we also have to develop a new feature to
> > change install directories of the packages,
> > keeping the current default for avoiding user-facing incompatibility.
> > Otherwise bdp-select itself is useless.
>
> I don't like to bring the awkward package name convention to Bigtop
> at least by default.
>
> I feel hdp-select/bdp-select should belongs to Ambari
> since it is assuming the convention specific to HDP/BDP/Ambari.
> We can easily add packaging for the code under Ambari
> (as ambari-bdp-select for example) based on the existing stuff under
> bigtop-packages/*/ambari.
>
>
> Masatake Iwasaki
>
> On 2022/07/03 7:17, Kengo Seki wrote:
> > Thank you for proposing this, Viraj and Brahma.
> > This proposal may feel sudden to someone, so let me explain some context,
> > mainly to the Bigtop community.
> >
> > Ambari went to Attic once due to inactivity,
> > but some of its users and developers are reviving it now.
> > From the Bigtop community, Roman and Evans undertook the role of
> > initial PMC members,
> > and Jun, Yuqi, Ganesh, Masatake, and I are also going to support it.
> >
> > The default stack of Ambari was HDP, but it has gone behind paywall,
> > so we have to add an alternative stack in the next release of Ambari.
> > Viraj and Brahma are planning to leverage Bigtop packages for that purpose,
> > and that stack is tentatively named BDP (BigData Platform).
> >
> > We would also like to take over a feature called hdp-select,
> > which enables users to switch the current stack easily with symlink.
> > For example, assuming that the following stack is installed:
> >
> > /usr/hdp/SOME_VERSION/hadoop/...
> > /spark/...
> > /zookeeper/...
> >
> > /etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks of
> > /usr/hdp/SOME_VERSION/hadoop/etc, /usr/hdp/SOME_VERSION/hadoop/var/lib,
> > /usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
> >
> > Then the new stack is installed under /usr/hdp/NEW_VERSION,
> > users can run hdp-select to switch the symlinks to the new directories
> > for upgrading the stack.
> > (Is my understanding correct? Correct me if I'm wrong, Viraj and Brahma)
> >
> > hdp-select was provided as a RPM/DEB package just like other packages
> > HDP provided,
> > so it is user-friendly to provide bdp-select (the BDP version of
> > hdp-select) as well.
> > This is the background of Viraj's proposal.
> >
> > But there is a problem here to leverage Bigtop packages in this manner.
> > Bigtop respects Linux's Filesystem Hierarchy Standard,
> > so it doesn't install files into a single place (/usr/hdp/VERSION in
> > the example above),
> > but directly into /etc, /usr, /var and so on.
> > So if we accept bdp-select, we also have to develop a new feature to
> > change install directories of the packages,
> > keeping the current default for avoiding user-facing incompatibility.
> > Otherwise bdp-select itself is useless.
> > But it will be a tough work, because installation paths are hard-coded
> > in the RPM specs and DEB packaging scripts now.
> >
> > Based on the above, how about creating a new branch for adding hdp-select
> > and developing the feature to switch installation paths?
> > After finishing the work on that branch and ensuring that it works expectedly,
> > we can merge it into master, I think.
> >
> > Kengo Seki <se...@apache.org>
> >
> > On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
> > <bb...@visa.com.invalid> wrote:
> >>
> >> Thanks @Viraj Jasani to start discussing on this.
> >>
> >> IMO, For upcoming ambari release(2.7.7) , we should have select other than HDP so that people can start using the ambari without HDP.
> >>
> >> I am +1(non-binding) on this approach to have selects in bigtop code. May be for long term , we can think for tarballs or mpacks which can go in mabari trunk.
> >>
> >>
> >> On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
> >>
> >> Hi Ambari/Bigtop dev,
> >>
> >> As per the new roadmap of Apache Ambari, we would like to propose moving
> >> certain scripts (previously known as hdp-select and conf-select) to Bigtop
> >> so that their rpm installation could be managed independently.
> >> These scripts are a basic necessity in the Ambari framework for the
> >> installation of various Bigdata packages. The only major changes they would
> >> receive is when we onboard new services and components to Ambari, else they
> >> usually do not receive updates. In the past, we used to get hdp-select rpm
> >> downloaded and installed from HDP repositories.
> >>
> >> We have still not officially finalized the new replacement name for
> >> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> >> the purpose of bdp-select and conf-select remains the same.
> >>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
> > Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> I dn't think, we'll required to install multiple versions same time. Even this can be handled.
Could you elaborate the reason why we need the *-select if so?
> IMO, as components rpm's are build with bigtop, having it in bigtop will be perfect choice. As we need to change the spec's.
It does not make sense.
While Hadoop rpm/deb are built with Bigtop, Hadoop is independent project.
The following description implies that the *-select is updated along with Ambari
and Ambari is the perfect place to host it.
| These scripts are a basic necessity in the Ambari framework for the
| installation of various Bigdata packages. The only major changes they would
| receive is when we onboard new services and components to Ambari, else they
| usually do not receive updates. In the past, we used to get hdp-select rpm
| downloaded and installed from HDP repositories.
On 2022/07/04 19:35, Battula, Brahma Reddy wrote:
>> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> I dn't think, we'll required to install multiple versions same time. Even this can be handled.
> Anyway Bigtop will be used to create the RPM's not for deploying the cluster with ambari now.
>
>> I feel hdp-select/bdp-select should belongs to Ambari
>> since it is assuming the convention specific to HDP/BDP/Ambari.
> > We can easily add packaging for the code under Ambari
> > (as ambari-bdp-select for example) based on the existing stuff under
> > bigtop-packages/*/ambari.
>
> IMO, as components rpm's are build with bigtop, having it in bigtop will be perfect choice. As we need to change the spec's.
>
>
>
> On 03/07/22, 9:56 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
>
> > For example, assuming that the following stack is installed:
> >
> > /usr/hdp/SOME_VERSION/hadoop/...
> > /spark/...
> > /zookeeper/...
>
> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
> IIRC, HDP uses convention in which the product version is part of package name
> for addressing this. like::
>
> $ rpm -qi hadoop_2_6_1_0_129
> Name : hadoop_2_6_1_0_129
> Version : 2.7.3.2.6.1.0
> ...
>
>
> > So if we accept bdp-select, we also have to develop a new feature to
> > change install directories of the packages,
> > keeping the current default for avoiding user-facing incompatibility.
> > Otherwise bdp-select itself is useless.
>
> I don't like to bring the awkward package name convention to Bigtop
> at least by default.
>
> I feel hdp-select/bdp-select should belongs to Ambari
> since it is assuming the convention specific to HDP/BDP/Ambari.
> We can easily add packaging for the code under Ambari
> (as ambari-bdp-select for example) based on the existing stuff under
> bigtop-packages/*/ambari.
>
>
> Masatake Iwasaki
>
> On 2022/07/03 7:17, Kengo Seki wrote:
> > Thank you for proposing this, Viraj and Brahma.
> > This proposal may feel sudden to someone, so let me explain some context,
> > mainly to the Bigtop community.
> >
> > Ambari went to Attic once due to inactivity,
> > but some of its users and developers are reviving it now.
> > From the Bigtop community, Roman and Evans undertook the role of
> > initial PMC members,
> > and Jun, Yuqi, Ganesh, Masatake, and I are also going to support it.
> >
> > The default stack of Ambari was HDP, but it has gone behind paywall,
> > so we have to add an alternative stack in the next release of Ambari.
> > Viraj and Brahma are planning to leverage Bigtop packages for that purpose,
> > and that stack is tentatively named BDP (BigData Platform).
> >
> > We would also like to take over a feature called hdp-select,
> > which enables users to switch the current stack easily with symlink.
> > For example, assuming that the following stack is installed:
> >
> > /usr/hdp/SOME_VERSION/hadoop/...
> > /spark/...
> > /zookeeper/...
> >
> > /etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks of
> > /usr/hdp/SOME_VERSION/hadoop/etc, /usr/hdp/SOME_VERSION/hadoop/var/lib,
> > /usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
> >
> > Then the new stack is installed under /usr/hdp/NEW_VERSION,
> > users can run hdp-select to switch the symlinks to the new directories
> > for upgrading the stack.
> > (Is my understanding correct? Correct me if I'm wrong, Viraj and Brahma)
> >
> > hdp-select was provided as a RPM/DEB package just like other packages
> > HDP provided,
> > so it is user-friendly to provide bdp-select (the BDP version of
> > hdp-select) as well.
> > This is the background of Viraj's proposal.
> >
> > But there is a problem here to leverage Bigtop packages in this manner.
> > Bigtop respects Linux's Filesystem Hierarchy Standard,
> > so it doesn't install files into a single place (/usr/hdp/VERSION in
> > the example above),
> > but directly into /etc, /usr, /var and so on.
> > So if we accept bdp-select, we also have to develop a new feature to
> > change install directories of the packages,
> > keeping the current default for avoiding user-facing incompatibility.
> > Otherwise bdp-select itself is useless.
> > But it will be a tough work, because installation paths are hard-coded
> > in the RPM specs and DEB packaging scripts now.
> >
> > Based on the above, how about creating a new branch for adding hdp-select
> > and developing the feature to switch installation paths?
> > After finishing the work on that branch and ensuring that it works expectedly,
> > we can merge it into master, I think.
> >
> > Kengo Seki <se...@apache.org>
> >
> > On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
> > <bb...@visa.com.invalid> wrote:
> >>
> >> Thanks @Viraj Jasani to start discussing on this.
> >>
> >> IMO, For upcoming ambari release(2.7.7) , we should have select other than HDP so that people can start using the ambari without HDP.
> >>
> >> I am +1(non-binding) on this approach to have selects in bigtop code. May be for long term , we can think for tarballs or mpacks which can go in mabari trunk.
> >>
> >>
> >> On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
> >>
> >> Hi Ambari/Bigtop dev,
> >>
> >> As per the new roadmap of Apache Ambari, we would like to propose moving
> >> certain scripts (previously known as hdp-select and conf-select) to Bigtop
> >> so that their rpm installation could be managed independently.
> >> These scripts are a basic necessity in the Ambari framework for the
> >> installation of various Bigdata packages. The only major changes they would
> >> receive is when we onboard new services and components to Ambari, else they
> >> usually do not receive updates. In the past, we used to get hdp-select rpm
> >> downloaded and installed from HDP repositories.
> >>
> >> We have still not officially finalized the new replacement name for
> >> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> >> the purpose of bdp-select and conf-select remains the same.
> >>
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
I dn't think, we'll required to install multiple versions same time. Even this can be handled.
Anyway Bigtop will be used to create the RPM's not for deploying the cluster with ambari now.
> I feel hdp-select/bdp-select should belongs to Ambari
> since it is assuming the convention specific to HDP/BDP/Ambari.
> We can easily add packaging for the code under Ambari
> (as ambari-bdp-select for example) based on the existing stuff under
> bigtop-packages/*/ambari.
IMO, as components rpm's are build with bigtop, having it in bigtop will be perfect choice. As we need to change the spec's.
On 03/07/22, 9:56 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> For example, assuming that the following stack is installed:
>
> /usr/hdp/SOME_VERSION/hadoop/...
> /spark/...
> /zookeeper/...
Multiple versions of the same package (deb/rpm) can not be installed at the same time.
IIRC, HDP uses convention in which the product version is part of package name
for addressing this. like::
$ rpm -qi hadoop_2_6_1_0_129
Name : hadoop_2_6_1_0_129
Version : 2.7.3.2.6.1.0
...
> So if we accept bdp-select, we also have to develop a new feature to
> change install directories of the packages,
> keeping the current default for avoiding user-facing incompatibility.
> Otherwise bdp-select itself is useless.
I don't like to bring the awkward package name convention to Bigtop
at least by default.
I feel hdp-select/bdp-select should belongs to Ambari
since it is assuming the convention specific to HDP/BDP/Ambari.
We can easily add packaging for the code under Ambari
(as ambari-bdp-select for example) based on the existing stuff under
bigtop-packages/*/ambari.
Masatake Iwasaki
On 2022/07/03 7:17, Kengo Seki wrote:
> Thank you for proposing this, Viraj and Brahma.
> This proposal may feel sudden to someone, so let me explain some context,
> mainly to the Bigtop community.
>
> Ambari went to Attic once due to inactivity,
> but some of its users and developers are reviving it now.
> From the Bigtop community, Roman and Evans undertook the role of
> initial PMC members,
> and Jun, Yuqi, Ganesh, Masatake, and I are also going to support it.
>
> The default stack of Ambari was HDP, but it has gone behind paywall,
> so we have to add an alternative stack in the next release of Ambari.
> Viraj and Brahma are planning to leverage Bigtop packages for that purpose,
> and that stack is tentatively named BDP (BigData Platform).
>
> We would also like to take over a feature called hdp-select,
> which enables users to switch the current stack easily with symlink.
> For example, assuming that the following stack is installed:
>
> /usr/hdp/SOME_VERSION/hadoop/...
> /spark/...
> /zookeeper/...
>
> /etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks of
> /usr/hdp/SOME_VERSION/hadoop/etc, /usr/hdp/SOME_VERSION/hadoop/var/lib,
> /usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
>
> Then the new stack is installed under /usr/hdp/NEW_VERSION,
> users can run hdp-select to switch the symlinks to the new directories
> for upgrading the stack.
> (Is my understanding correct? Correct me if I'm wrong, Viraj and Brahma)
>
> hdp-select was provided as a RPM/DEB package just like other packages
> HDP provided,
> so it is user-friendly to provide bdp-select (the BDP version of
> hdp-select) as well.
> This is the background of Viraj's proposal.
>
> But there is a problem here to leverage Bigtop packages in this manner.
> Bigtop respects Linux's Filesystem Hierarchy Standard,
> so it doesn't install files into a single place (/usr/hdp/VERSION in
> the example above),
> but directly into /etc, /usr, /var and so on.
> So if we accept bdp-select, we also have to develop a new feature to
> change install directories of the packages,
> keeping the current default for avoiding user-facing incompatibility.
> Otherwise bdp-select itself is useless.
> But it will be a tough work, because installation paths are hard-coded
> in the RPM specs and DEB packaging scripts now.
>
> Based on the above, how about creating a new branch for adding hdp-select
> and developing the feature to switch installation paths?
> After finishing the work on that branch and ensuring that it works expectedly,
> we can merge it into master, I think.
>
> Kengo Seki <se...@apache.org>
>
> On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
>>
>> Thanks @Viraj Jasani to start discussing on this.
>>
>> IMO, For upcoming ambari release(2.7.7) , we should have select other than HDP so that people can start using the ambari without HDP.
>>
>> I am +1(non-binding) on this approach to have selects in bigtop code. May be for long term , we can think for tarballs or mpacks which can go in mabari trunk.
>>
>>
>> On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
>>
>> Hi Ambari/Bigtop dev,
>>
>> As per the new roadmap of Apache Ambari, we would like to propose moving
>> certain scripts (previously known as hdp-select and conf-select) to Bigtop
>> so that their rpm installation could be managed independently.
>> These scripts are a basic necessity in the Ambari framework for the
>> installation of various Bigdata packages. The only major changes they would
>> receive is when we onboard new services and components to Ambari, else they
>> usually do not receive updates. In the past, we used to get hdp-select rpm
>> downloaded and installed from HDP repositories.
>>
>> We have still not officially finalized the new replacement name for
>> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>> the purpose of bdp-select and conf-select remains the same.
>>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
> Multiple versions of the same package (deb/rpm) can not be installed at the same time.
I dn't think, we'll required to install multiple versions same time. Even this can be handled.
Anyway Bigtop will be used to create the RPM's not for deploying the cluster with ambari now.
> I feel hdp-select/bdp-select should belongs to Ambari
> since it is assuming the convention specific to HDP/BDP/Ambari.
> We can easily add packaging for the code under Ambari
> (as ambari-bdp-select for example) based on the existing stuff under
> bigtop-packages/*/ambari.
IMO, as components rpm's are build with bigtop, having it in bigtop will be perfect choice. As we need to change the spec's.
On 03/07/22, 9:56 AM, "Masatake Iwasaki" <iw...@oss.nttdata.co.jp> wrote:
> For example, assuming that the following stack is installed:
>
> /usr/hdp/SOME_VERSION/hadoop/...
> /spark/...
> /zookeeper/...
Multiple versions of the same package (deb/rpm) can not be installed at the same time.
IIRC, HDP uses convention in which the product version is part of package name
for addressing this. like::
$ rpm -qi hadoop_2_6_1_0_129
Name : hadoop_2_6_1_0_129
Version : 2.7.3.2.6.1.0
...
> So if we accept bdp-select, we also have to develop a new feature to
> change install directories of the packages,
> keeping the current default for avoiding user-facing incompatibility.
> Otherwise bdp-select itself is useless.
I don't like to bring the awkward package name convention to Bigtop
at least by default.
I feel hdp-select/bdp-select should belongs to Ambari
since it is assuming the convention specific to HDP/BDP/Ambari.
We can easily add packaging for the code under Ambari
(as ambari-bdp-select for example) based on the existing stuff under
bigtop-packages/*/ambari.
Masatake Iwasaki
On 2022/07/03 7:17, Kengo Seki wrote:
> Thank you for proposing this, Viraj and Brahma.
> This proposal may feel sudden to someone, so let me explain some context,
> mainly to the Bigtop community.
>
> Ambari went to Attic once due to inactivity,
> but some of its users and developers are reviving it now.
> From the Bigtop community, Roman and Evans undertook the role of
> initial PMC members,
> and Jun, Yuqi, Ganesh, Masatake, and I are also going to support it.
>
> The default stack of Ambari was HDP, but it has gone behind paywall,
> so we have to add an alternative stack in the next release of Ambari.
> Viraj and Brahma are planning to leverage Bigtop packages for that purpose,
> and that stack is tentatively named BDP (BigData Platform).
>
> We would also like to take over a feature called hdp-select,
> which enables users to switch the current stack easily with symlink.
> For example, assuming that the following stack is installed:
>
> /usr/hdp/SOME_VERSION/hadoop/...
> /spark/...
> /zookeeper/...
>
> /etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks of
> /usr/hdp/SOME_VERSION/hadoop/etc, /usr/hdp/SOME_VERSION/hadoop/var/lib,
> /usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
>
> Then the new stack is installed under /usr/hdp/NEW_VERSION,
> users can run hdp-select to switch the symlinks to the new directories
> for upgrading the stack.
> (Is my understanding correct? Correct me if I'm wrong, Viraj and Brahma)
>
> hdp-select was provided as a RPM/DEB package just like other packages
> HDP provided,
> so it is user-friendly to provide bdp-select (the BDP version of
> hdp-select) as well.
> This is the background of Viraj's proposal.
>
> But there is a problem here to leverage Bigtop packages in this manner.
> Bigtop respects Linux's Filesystem Hierarchy Standard,
> so it doesn't install files into a single place (/usr/hdp/VERSION in
> the example above),
> but directly into /etc, /usr, /var and so on.
> So if we accept bdp-select, we also have to develop a new feature to
> change install directories of the packages,
> keeping the current default for avoiding user-facing incompatibility.
> Otherwise bdp-select itself is useless.
> But it will be a tough work, because installation paths are hard-coded
> in the RPM specs and DEB packaging scripts now.
>
> Based on the above, how about creating a new branch for adding hdp-select
> and developing the feature to switch installation paths?
> After finishing the work on that branch and ensuring that it works expectedly,
> we can merge it into master, I think.
>
> Kengo Seki <se...@apache.org>
>
> On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
>>
>> Thanks @Viraj Jasani to start discussing on this.
>>
>> IMO, For upcoming ambari release(2.7.7) , we should have select other than HDP so that people can start using the ambari without HDP.
>>
>> I am +1(non-binding) on this approach to have selects in bigtop code. May be for long term , we can think for tarballs or mpacks which can go in mabari trunk.
>>
>>
>> On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
>>
>> Hi Ambari/Bigtop dev,
>>
>> As per the new roadmap of Apache Ambari, we would like to propose moving
>> certain scripts (previously known as hdp-select and conf-select) to Bigtop
>> so that their rpm installation could be managed independently.
>> These scripts are a basic necessity in the Ambari framework for the
>> installation of various Bigdata packages. The only major changes they would
>> receive is when we onboard new services and components to Ambari, else they
>> usually do not receive updates. In the past, we used to get hdp-select rpm
>> downloaded and installed from HDP repositories.
>>
>> We have still not officially finalized the new replacement name for
>> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>> the purpose of bdp-select and conf-select remains the same.
>>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
> For example, assuming that the following stack is installed:
>
> /usr/hdp/SOME_VERSION/hadoop/...
> /spark/...
> /zookeeper/...
Multiple versions of the same package (deb/rpm) can not be installed at the same time.
IIRC, HDP uses convention in which the product version is part of package name
for addressing this. like::
$ rpm -qi hadoop_2_6_1_0_129
Name : hadoop_2_6_1_0_129
Version : 2.7.3.2.6.1.0
...
> So if we accept bdp-select, we also have to develop a new feature to
> change install directories of the packages,
> keeping the current default for avoiding user-facing incompatibility.
> Otherwise bdp-select itself is useless.
I don't like to bring the awkward package name convention to Bigtop
at least by default.
I feel hdp-select/bdp-select should belongs to Ambari
since it is assuming the convention specific to HDP/BDP/Ambari.
We can easily add packaging for the code under Ambari
(as ambari-bdp-select for example) based on the existing stuff under
bigtop-packages/*/ambari.
Masatake Iwasaki
On 2022/07/03 7:17, Kengo Seki wrote:
> Thank you for proposing this, Viraj and Brahma.
> This proposal may feel sudden to someone, so let me explain some context,
> mainly to the Bigtop community.
>
> Ambari went to Attic once due to inactivity,
> but some of its users and developers are reviving it now.
> From the Bigtop community, Roman and Evans undertook the role of
> initial PMC members,
> and Jun, Yuqi, Ganesh, Masatake, and I are also going to support it.
>
> The default stack of Ambari was HDP, but it has gone behind paywall,
> so we have to add an alternative stack in the next release of Ambari.
> Viraj and Brahma are planning to leverage Bigtop packages for that purpose,
> and that stack is tentatively named BDP (BigData Platform).
>
> We would also like to take over a feature called hdp-select,
> which enables users to switch the current stack easily with symlink.
> For example, assuming that the following stack is installed:
>
> /usr/hdp/SOME_VERSION/hadoop/...
> /spark/...
> /zookeeper/...
>
> /etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks of
> /usr/hdp/SOME_VERSION/hadoop/etc, /usr/hdp/SOME_VERSION/hadoop/var/lib,
> /usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
>
> Then the new stack is installed under /usr/hdp/NEW_VERSION,
> users can run hdp-select to switch the symlinks to the new directories
> for upgrading the stack.
> (Is my understanding correct? Correct me if I'm wrong, Viraj and Brahma)
>
> hdp-select was provided as a RPM/DEB package just like other packages
> HDP provided,
> so it is user-friendly to provide bdp-select (the BDP version of
> hdp-select) as well.
> This is the background of Viraj's proposal.
>
> But there is a problem here to leverage Bigtop packages in this manner.
> Bigtop respects Linux's Filesystem Hierarchy Standard,
> so it doesn't install files into a single place (/usr/hdp/VERSION in
> the example above),
> but directly into /etc, /usr, /var and so on.
> So if we accept bdp-select, we also have to develop a new feature to
> change install directories of the packages,
> keeping the current default for avoiding user-facing incompatibility.
> Otherwise bdp-select itself is useless.
> But it will be a tough work, because installation paths are hard-coded
> in the RPM specs and DEB packaging scripts now.
>
> Based on the above, how about creating a new branch for adding hdp-select
> and developing the feature to switch installation paths?
> After finishing the work on that branch and ensuring that it works expectedly,
> we can merge it into master, I think.
>
> Kengo Seki <se...@apache.org>
>
> On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
>>
>> Thanks @Viraj Jasani to start discussing on this.
>>
>> IMO, For upcoming ambari release(2.7.7) , we should have select other than HDP so that people can start using the ambari without HDP.
>>
>> I am +1(non-binding) on this approach to have selects in bigtop code. May be for long term , we can think for tarballs or mpacks which can go in mabari trunk.
>>
>>
>> On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
>>
>> Hi Ambari/Bigtop dev,
>>
>> As per the new roadmap of Apache Ambari, we would like to propose moving
>> certain scripts (previously known as hdp-select and conf-select) to Bigtop
>> so that their rpm installation could be managed independently.
>> These scripts are a basic necessity in the Ambari framework for the
>> installation of various Bigdata packages. The only major changes they would
>> receive is when we onboard new services and components to Ambari, else they
>> usually do not receive updates. In the past, we used to get hdp-select rpm
>> downloaded and installed from HDP repositories.
>>
>> We have still not officially finalized the new replacement name for
>> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
>> the purpose of bdp-select and conf-select remains the same.
>>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
Thanks @Kengo Seki and your team to support us.
IMO, it should ok to work on separate branch now.
@Andrew Purtell update-alternatives can be good option. we need to change the spec files also. Is it okay to do it in separate branch and explore more as we need to support redhat also..?
On 03/07/22, 5:26 AM, "Andrew Purtell" <ap...@apache.org> wrote:
You have Debian's 'alternatives' as a model for developing a new
"hdp-select" for a LSB compliant installation. See
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.debian.org%2FDebianAlternatives&data=05%7C01%7Cbbattula%40visa.com%7C1437b3558f584fb7495508da5c86816f%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637924030087181274%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vz7xqnjnsHFiwmVyEnmiut5yPD7lLs365fIW1Yelvxw%3D&reserved=0 . The "hdp" package may
primarily install itself into a place like /usr/lib/<component>-<version>
or /usr/lib/<component>/<version> but configuration files may be symlinked
into /etc and binfiles into /usr/bin using 'alternatives. For your
consideration.
On Sat, Jul 2, 2022 at 3:17 PM Kengo Seki <se...@apache.org> wrote:
> Thank you for proposing this, Viraj and Brahma.
> This proposal may feel sudden to someone, so let me explain some context,
> mainly to the Bigtop community.
>
> Ambari went to Attic once due to inactivity,
> but some of its users and developers are reviving it now.
> From the Bigtop community, Roman and Evans undertook the role of
> initial PMC members,
> and Jun, Yuqi, Ganesh, Masatake, and I are also going to support it.
>
> The default stack of Ambari was HDP, but it has gone behind paywall,
> so we have to add an alternative stack in the next release of Ambari.
> Viraj and Brahma are planning to leverage Bigtop packages for that purpose,
> and that stack is tentatively named BDP (BigData Platform).
>
> We would also like to take over a feature called hdp-select,
> which enables users to switch the current stack easily with symlink.
> For example, assuming that the following stack is installed:
>
> /usr/hdp/SOME_VERSION/hadoop/...
> /spark/...
> /zookeeper/...
>
> /etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks of
> /usr/hdp/SOME_VERSION/hadoop/etc, /usr/hdp/SOME_VERSION/hadoop/var/lib,
> /usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
>
> Then the new stack is installed under /usr/hdp/NEW_VERSION,
> users can run hdp-select to switch the symlinks to the new directories
> for upgrading the stack.
> (Is my understanding correct? Correct me if I'm wrong, Viraj and Brahma)
>
> hdp-select was provided as a RPM/DEB package just like other packages
> HDP provided,
> so it is user-friendly to provide bdp-select (the BDP version of
> hdp-select) as well.
> This is the background of Viraj's proposal.
>
> But there is a problem here to leverage Bigtop packages in this manner.
> Bigtop respects Linux's Filesystem Hierarchy Standard,
> so it doesn't install files into a single place (/usr/hdp/VERSION in
> the example above),
> but directly into /etc, /usr, /var and so on.
> So if we accept bdp-select, we also have to develop a new feature to
> change install directories of the packages,
> keeping the current default for avoiding user-facing incompatibility.
> Otherwise bdp-select itself is useless.
> But it will be a tough work, because installation paths are hard-coded
> in the RPM specs and DEB packaging scripts now.
>
> Based on the above, how about creating a new branch for adding hdp-select
> and developing the feature to switch installation paths?
> After finishing the work on that branch and ensuring that it works
> expectedly,
> we can merge it into master, I think.
>
> Kengo Seki <se...@apache.org>
>
> On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
> >
> > Thanks @Viraj Jasani to start discussing on this.
> >
> > IMO, For upcoming ambari release(2.7.7) , we should have select other
> than HDP so that people can start using the ambari without HDP.
> >
> > I am +1(non-binding) on this approach to have selects in bigtop code.
> May be for long term , we can think for tarballs or mpacks which can go in
> mabari trunk.
> >
> >
> > On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
> >
> > Hi Ambari/Bigtop dev,
> >
> > As per the new roadmap of Apache Ambari, we would like to propose
> moving
> > certain scripts (previously known as hdp-select and conf-select) to
> Bigtop
> > so that their rpm installation could be managed independently.
> > These scripts are a basic necessity in the Ambari framework for the
> > installation of various Bigdata packages. The only major changes
> they would
> > receive is when we onboard new services and components to Ambari,
> else they
> > usually do not receive updates. In the past, we used to get
> hdp-select rpm
> > downloaded and installed from HDP repositories.
> >
> > We have still not officially finalized the new replacement name for
> > hdp-select, it would likely be bdp-select (bdp: BigData Platform).
> However,
> > the purpose of bdp-select and conf-select remains the same.
> >
>
--
Best regards,
Andrew
Unrest, ignorance distilled, nihilistic imbeciles -
It's what we’ve earned
Welcome, apocalypse, what’s taken you so long?
Bring us the fitting end that we’ve been counting on
- A23, Welcome, Apocalypse
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
Thanks @Kengo Seki and your team to support us.
IMO, it should ok to work on separate branch now.
@Andrew Purtell update-alternatives can be good option. we need to change the spec files also. Is it okay to do it in separate branch and explore more as we need to support redhat also..?
On 03/07/22, 5:26 AM, "Andrew Purtell" <ap...@apache.org> wrote:
You have Debian's 'alternatives' as a model for developing a new
"hdp-select" for a LSB compliant installation. See
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.debian.org%2FDebianAlternatives&data=05%7C01%7Cbbattula%40visa.com%7C1437b3558f584fb7495508da5c86816f%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C637924030087181274%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vz7xqnjnsHFiwmVyEnmiut5yPD7lLs365fIW1Yelvxw%3D&reserved=0 . The "hdp" package may
primarily install itself into a place like /usr/lib/<component>-<version>
or /usr/lib/<component>/<version> but configuration files may be symlinked
into /etc and binfiles into /usr/bin using 'alternatives. For your
consideration.
On Sat, Jul 2, 2022 at 3:17 PM Kengo Seki <se...@apache.org> wrote:
> Thank you for proposing this, Viraj and Brahma.
> This proposal may feel sudden to someone, so let me explain some context,
> mainly to the Bigtop community.
>
> Ambari went to Attic once due to inactivity,
> but some of its users and developers are reviving it now.
> From the Bigtop community, Roman and Evans undertook the role of
> initial PMC members,
> and Jun, Yuqi, Ganesh, Masatake, and I are also going to support it.
>
> The default stack of Ambari was HDP, but it has gone behind paywall,
> so we have to add an alternative stack in the next release of Ambari.
> Viraj and Brahma are planning to leverage Bigtop packages for that purpose,
> and that stack is tentatively named BDP (BigData Platform).
>
> We would also like to take over a feature called hdp-select,
> which enables users to switch the current stack easily with symlink.
> For example, assuming that the following stack is installed:
>
> /usr/hdp/SOME_VERSION/hadoop/...
> /spark/...
> /zookeeper/...
>
> /etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks of
> /usr/hdp/SOME_VERSION/hadoop/etc, /usr/hdp/SOME_VERSION/hadoop/var/lib,
> /usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
>
> Then the new stack is installed under /usr/hdp/NEW_VERSION,
> users can run hdp-select to switch the symlinks to the new directories
> for upgrading the stack.
> (Is my understanding correct? Correct me if I'm wrong, Viraj and Brahma)
>
> hdp-select was provided as a RPM/DEB package just like other packages
> HDP provided,
> so it is user-friendly to provide bdp-select (the BDP version of
> hdp-select) as well.
> This is the background of Viraj's proposal.
>
> But there is a problem here to leverage Bigtop packages in this manner.
> Bigtop respects Linux's Filesystem Hierarchy Standard,
> so it doesn't install files into a single place (/usr/hdp/VERSION in
> the example above),
> but directly into /etc, /usr, /var and so on.
> So if we accept bdp-select, we also have to develop a new feature to
> change install directories of the packages,
> keeping the current default for avoiding user-facing incompatibility.
> Otherwise bdp-select itself is useless.
> But it will be a tough work, because installation paths are hard-coded
> in the RPM specs and DEB packaging scripts now.
>
> Based on the above, how about creating a new branch for adding hdp-select
> and developing the feature to switch installation paths?
> After finishing the work on that branch and ensuring that it works
> expectedly,
> we can merge it into master, I think.
>
> Kengo Seki <se...@apache.org>
>
> On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
> >
> > Thanks @Viraj Jasani to start discussing on this.
> >
> > IMO, For upcoming ambari release(2.7.7) , we should have select other
> than HDP so that people can start using the ambari without HDP.
> >
> > I am +1(non-binding) on this approach to have selects in bigtop code.
> May be for long term , we can think for tarballs or mpacks which can go in
> mabari trunk.
> >
> >
> > On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
> >
> > Hi Ambari/Bigtop dev,
> >
> > As per the new roadmap of Apache Ambari, we would like to propose
> moving
> > certain scripts (previously known as hdp-select and conf-select) to
> Bigtop
> > so that their rpm installation could be managed independently.
> > These scripts are a basic necessity in the Ambari framework for the
> > installation of various Bigdata packages. The only major changes
> they would
> > receive is when we onboard new services and components to Ambari,
> else they
> > usually do not receive updates. In the past, we used to get
> hdp-select rpm
> > downloaded and installed from HDP repositories.
> >
> > We have still not officially finalized the new replacement name for
> > hdp-select, it would likely be bdp-select (bdp: BigData Platform).
> However,
> > the purpose of bdp-select and conf-select remains the same.
> >
>
--
Best regards,
Andrew
Unrest, ignorance distilled, nihilistic imbeciles -
It's what we’ve earned
Welcome, apocalypse, what’s taken you so long?
Bring us the fitting end that we’ve been counting on
- A23, Welcome, Apocalypse
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Andrew Purtell <ap...@apache.org>.
You have Debian's 'alternatives' as a model for developing a new
"hdp-select" for a LSB compliant installation. See
https://wiki.debian.org/DebianAlternatives . The "hdp" package may
primarily install itself into a place like /usr/lib/<component>-<version>
or /usr/lib/<component>/<version> but configuration files may be symlinked
into /etc and binfiles into /usr/bin using 'alternatives. For your
consideration.
On Sat, Jul 2, 2022 at 3:17 PM Kengo Seki <se...@apache.org> wrote:
> Thank you for proposing this, Viraj and Brahma.
> This proposal may feel sudden to someone, so let me explain some context,
> mainly to the Bigtop community.
>
> Ambari went to Attic once due to inactivity,
> but some of its users and developers are reviving it now.
> From the Bigtop community, Roman and Evans undertook the role of
> initial PMC members,
> and Jun, Yuqi, Ganesh, Masatake, and I are also going to support it.
>
> The default stack of Ambari was HDP, but it has gone behind paywall,
> so we have to add an alternative stack in the next release of Ambari.
> Viraj and Brahma are planning to leverage Bigtop packages for that purpose,
> and that stack is tentatively named BDP (BigData Platform).
>
> We would also like to take over a feature called hdp-select,
> which enables users to switch the current stack easily with symlink.
> For example, assuming that the following stack is installed:
>
> /usr/hdp/SOME_VERSION/hadoop/...
> /spark/...
> /zookeeper/...
>
> /etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks of
> /usr/hdp/SOME_VERSION/hadoop/etc, /usr/hdp/SOME_VERSION/hadoop/var/lib,
> /usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
>
> Then the new stack is installed under /usr/hdp/NEW_VERSION,
> users can run hdp-select to switch the symlinks to the new directories
> for upgrading the stack.
> (Is my understanding correct? Correct me if I'm wrong, Viraj and Brahma)
>
> hdp-select was provided as a RPM/DEB package just like other packages
> HDP provided,
> so it is user-friendly to provide bdp-select (the BDP version of
> hdp-select) as well.
> This is the background of Viraj's proposal.
>
> But there is a problem here to leverage Bigtop packages in this manner.
> Bigtop respects Linux's Filesystem Hierarchy Standard,
> so it doesn't install files into a single place (/usr/hdp/VERSION in
> the example above),
> but directly into /etc, /usr, /var and so on.
> So if we accept bdp-select, we also have to develop a new feature to
> change install directories of the packages,
> keeping the current default for avoiding user-facing incompatibility.
> Otherwise bdp-select itself is useless.
> But it will be a tough work, because installation paths are hard-coded
> in the RPM specs and DEB packaging scripts now.
>
> Based on the above, how about creating a new branch for adding hdp-select
> and developing the feature to switch installation paths?
> After finishing the work on that branch and ensuring that it works
> expectedly,
> we can merge it into master, I think.
>
> Kengo Seki <se...@apache.org>
>
> On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
> >
> > Thanks @Viraj Jasani to start discussing on this.
> >
> > IMO, For upcoming ambari release(2.7.7) , we should have select other
> than HDP so that people can start using the ambari without HDP.
> >
> > I am +1(non-binding) on this approach to have selects in bigtop code.
> May be for long term , we can think for tarballs or mpacks which can go in
> mabari trunk.
> >
> >
> > On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
> >
> > Hi Ambari/Bigtop dev,
> >
> > As per the new roadmap of Apache Ambari, we would like to propose
> moving
> > certain scripts (previously known as hdp-select and conf-select) to
> Bigtop
> > so that their rpm installation could be managed independently.
> > These scripts are a basic necessity in the Ambari framework for the
> > installation of various Bigdata packages. The only major changes
> they would
> > receive is when we onboard new services and components to Ambari,
> else they
> > usually do not receive updates. In the past, we used to get
> hdp-select rpm
> > downloaded and installed from HDP repositories.
> >
> > We have still not officially finalized the new replacement name for
> > hdp-select, it would likely be bdp-select (bdp: BigData Platform).
> However,
> > the purpose of bdp-select and conf-select remains the same.
> >
>
--
Best regards,
Andrew
Unrest, ignorance distilled, nihilistic imbeciles -
It's what we’ve earned
Welcome, apocalypse, what’s taken you so long?
Bring us the fitting end that we’ve been counting on
- A23, Welcome, Apocalypse
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Andrew Purtell <ap...@apache.org>.
You have Debian's 'alternatives' as a model for developing a new
"hdp-select" for a LSB compliant installation. See
https://wiki.debian.org/DebianAlternatives . The "hdp" package may
primarily install itself into a place like /usr/lib/<component>-<version>
or /usr/lib/<component>/<version> but configuration files may be symlinked
into /etc and binfiles into /usr/bin using 'alternatives. For your
consideration.
On Sat, Jul 2, 2022 at 3:17 PM Kengo Seki <se...@apache.org> wrote:
> Thank you for proposing this, Viraj and Brahma.
> This proposal may feel sudden to someone, so let me explain some context,
> mainly to the Bigtop community.
>
> Ambari went to Attic once due to inactivity,
> but some of its users and developers are reviving it now.
> From the Bigtop community, Roman and Evans undertook the role of
> initial PMC members,
> and Jun, Yuqi, Ganesh, Masatake, and I are also going to support it.
>
> The default stack of Ambari was HDP, but it has gone behind paywall,
> so we have to add an alternative stack in the next release of Ambari.
> Viraj and Brahma are planning to leverage Bigtop packages for that purpose,
> and that stack is tentatively named BDP (BigData Platform).
>
> We would also like to take over a feature called hdp-select,
> which enables users to switch the current stack easily with symlink.
> For example, assuming that the following stack is installed:
>
> /usr/hdp/SOME_VERSION/hadoop/...
> /spark/...
> /zookeeper/...
>
> /etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks of
> /usr/hdp/SOME_VERSION/hadoop/etc, /usr/hdp/SOME_VERSION/hadoop/var/lib,
> /usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
>
> Then the new stack is installed under /usr/hdp/NEW_VERSION,
> users can run hdp-select to switch the symlinks to the new directories
> for upgrading the stack.
> (Is my understanding correct? Correct me if I'm wrong, Viraj and Brahma)
>
> hdp-select was provided as a RPM/DEB package just like other packages
> HDP provided,
> so it is user-friendly to provide bdp-select (the BDP version of
> hdp-select) as well.
> This is the background of Viraj's proposal.
>
> But there is a problem here to leverage Bigtop packages in this manner.
> Bigtop respects Linux's Filesystem Hierarchy Standard,
> so it doesn't install files into a single place (/usr/hdp/VERSION in
> the example above),
> but directly into /etc, /usr, /var and so on.
> So if we accept bdp-select, we also have to develop a new feature to
> change install directories of the packages,
> keeping the current default for avoiding user-facing incompatibility.
> Otherwise bdp-select itself is useless.
> But it will be a tough work, because installation paths are hard-coded
> in the RPM specs and DEB packaging scripts now.
>
> Based on the above, how about creating a new branch for adding hdp-select
> and developing the feature to switch installation paths?
> After finishing the work on that branch and ensuring that it works
> expectedly,
> we can merge it into master, I think.
>
> Kengo Seki <se...@apache.org>
>
> On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
> <bb...@visa.com.invalid> wrote:
> >
> > Thanks @Viraj Jasani to start discussing on this.
> >
> > IMO, For upcoming ambari release(2.7.7) , we should have select other
> than HDP so that people can start using the ambari without HDP.
> >
> > I am +1(non-binding) on this approach to have selects in bigtop code.
> May be for long term , we can think for tarballs or mpacks which can go in
> mabari trunk.
> >
> >
> > On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
> >
> > Hi Ambari/Bigtop dev,
> >
> > As per the new roadmap of Apache Ambari, we would like to propose
> moving
> > certain scripts (previously known as hdp-select and conf-select) to
> Bigtop
> > so that their rpm installation could be managed independently.
> > These scripts are a basic necessity in the Ambari framework for the
> > installation of various Bigdata packages. The only major changes
> they would
> > receive is when we onboard new services and components to Ambari,
> else they
> > usually do not receive updates. In the past, we used to get
> hdp-select rpm
> > downloaded and installed from HDP repositories.
> >
> > We have still not officially finalized the new replacement name for
> > hdp-select, it would likely be bdp-select (bdp: BigData Platform).
> However,
> > the purpose of bdp-select and conf-select remains the same.
> >
>
--
Best regards,
Andrew
Unrest, ignorance distilled, nihilistic imbeciles -
It's what we’ve earned
Welcome, apocalypse, what’s taken you so long?
Bring us the fitting end that we’ve been counting on
- A23, Welcome, Apocalypse
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Kengo Seki <se...@apache.org>.
Thank you for proposing this, Viraj and Brahma.
This proposal may feel sudden to someone, so let me explain some context,
mainly to the Bigtop community.
Ambari went to Attic once due to inactivity,
but some of its users and developers are reviving it now.
From the Bigtop community, Roman and Evans undertook the role of
initial PMC members,
and Jun, Yuqi, Ganesh, Masatake, and I are also going to support it.
The default stack of Ambari was HDP, but it has gone behind paywall,
so we have to add an alternative stack in the next release of Ambari.
Viraj and Brahma are planning to leverage Bigtop packages for that purpose,
and that stack is tentatively named BDP (BigData Platform).
We would also like to take over a feature called hdp-select,
which enables users to switch the current stack easily with symlink.
For example, assuming that the following stack is installed:
/usr/hdp/SOME_VERSION/hadoop/...
/spark/...
/zookeeper/...
/etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks of
/usr/hdp/SOME_VERSION/hadoop/etc, /usr/hdp/SOME_VERSION/hadoop/var/lib,
/usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
Then the new stack is installed under /usr/hdp/NEW_VERSION,
users can run hdp-select to switch the symlinks to the new directories
for upgrading the stack.
(Is my understanding correct? Correct me if I'm wrong, Viraj and Brahma)
hdp-select was provided as a RPM/DEB package just like other packages
HDP provided,
so it is user-friendly to provide bdp-select (the BDP version of
hdp-select) as well.
This is the background of Viraj's proposal.
But there is a problem here to leverage Bigtop packages in this manner.
Bigtop respects Linux's Filesystem Hierarchy Standard,
so it doesn't install files into a single place (/usr/hdp/VERSION in
the example above),
but directly into /etc, /usr, /var and so on.
So if we accept bdp-select, we also have to develop a new feature to
change install directories of the packages,
keeping the current default for avoiding user-facing incompatibility.
Otherwise bdp-select itself is useless.
But it will be a tough work, because installation paths are hard-coded
in the RPM specs and DEB packaging scripts now.
Based on the above, how about creating a new branch for adding hdp-select
and developing the feature to switch installation paths?
After finishing the work on that branch and ensuring that it works expectedly,
we can merge it into master, I think.
Kengo Seki <se...@apache.org>
On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
>
> Thanks @Viraj Jasani to start discussing on this.
>
> IMO, For upcoming ambari release(2.7.7) , we should have select other than HDP so that people can start using the ambari without HDP.
>
> I am +1(non-binding) on this approach to have selects in bigtop code. May be for long term , we can think for tarballs or mpacks which can go in mabari trunk.
>
>
> On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
>
> Hi Ambari/Bigtop dev,
>
> As per the new roadmap of Apache Ambari, we would like to propose moving
> certain scripts (previously known as hdp-select and conf-select) to Bigtop
> so that their rpm installation could be managed independently.
> These scripts are a basic necessity in the Ambari framework for the
> installation of various Bigdata packages. The only major changes they would
> receive is when we onboard new services and components to Ambari, else they
> usually do not receive updates. In the past, we used to get hdp-select rpm
> downloaded and installed from HDP repositories.
>
> We have still not officially finalized the new replacement name for
> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> the purpose of bdp-select and conf-select remains the same.
>
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by Kengo Seki <se...@apache.org>.
Thank you for proposing this, Viraj and Brahma.
This proposal may feel sudden to someone, so let me explain some context,
mainly to the Bigtop community.
Ambari went to Attic once due to inactivity,
but some of its users and developers are reviving it now.
From the Bigtop community, Roman and Evans undertook the role of
initial PMC members,
and Jun, Yuqi, Ganesh, Masatake, and I are also going to support it.
The default stack of Ambari was HDP, but it has gone behind paywall,
so we have to add an alternative stack in the next release of Ambari.
Viraj and Brahma are planning to leverage Bigtop packages for that purpose,
and that stack is tentatively named BDP (BigData Platform).
We would also like to take over a feature called hdp-select,
which enables users to switch the current stack easily with symlink.
For example, assuming that the following stack is installed:
/usr/hdp/SOME_VERSION/hadoop/...
/spark/...
/zookeeper/...
/etc/hadoop, /var/lib/hadoop, /usr/lib/hadoop are symlinks of
/usr/hdp/SOME_VERSION/hadoop/etc, /usr/hdp/SOME_VERSION/hadoop/var/lib,
/usr/hdp/SOME_VERSION/hadoop/usr/lib respectively.
Then the new stack is installed under /usr/hdp/NEW_VERSION,
users can run hdp-select to switch the symlinks to the new directories
for upgrading the stack.
(Is my understanding correct? Correct me if I'm wrong, Viraj and Brahma)
hdp-select was provided as a RPM/DEB package just like other packages
HDP provided,
so it is user-friendly to provide bdp-select (the BDP version of
hdp-select) as well.
This is the background of Viraj's proposal.
But there is a problem here to leverage Bigtop packages in this manner.
Bigtop respects Linux's Filesystem Hierarchy Standard,
so it doesn't install files into a single place (/usr/hdp/VERSION in
the example above),
but directly into /etc, /usr, /var and so on.
So if we accept bdp-select, we also have to develop a new feature to
change install directories of the packages,
keeping the current default for avoiding user-facing incompatibility.
Otherwise bdp-select itself is useless.
But it will be a tough work, because installation paths are hard-coded
in the RPM specs and DEB packaging scripts now.
Based on the above, how about creating a new branch for adding hdp-select
and developing the feature to switch installation paths?
After finishing the work on that branch and ensuring that it works expectedly,
we can merge it into master, I think.
Kengo Seki <se...@apache.org>
On Thu, Jun 30, 2022 at 4:21 PM Battula, Brahma Reddy
<bb...@visa.com.invalid> wrote:
>
> Thanks @Viraj Jasani to start discussing on this.
>
> IMO, For upcoming ambari release(2.7.7) , we should have select other than HDP so that people can start using the ambari without HDP.
>
> I am +1(non-binding) on this approach to have selects in bigtop code. May be for long term , we can think for tarballs or mpacks which can go in mabari trunk.
>
>
> On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
>
> Hi Ambari/Bigtop dev,
>
> As per the new roadmap of Apache Ambari, we would like to propose moving
> certain scripts (previously known as hdp-select and conf-select) to Bigtop
> so that their rpm installation could be managed independently.
> These scripts are a basic necessity in the Ambari framework for the
> installation of various Bigdata packages. The only major changes they would
> receive is when we onboard new services and components to Ambari, else they
> usually do not receive updates. In the past, we used to get hdp-select rpm
> downloaded and installed from HDP repositories.
>
> We have still not officially finalized the new replacement name for
> hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
> the purpose of bdp-select and conf-select remains the same.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
Thanks @Viraj Jasani to start discussing on this.
IMO, For upcoming ambari release(2.7.7) , we should have select other than HDP so that people can start using the ambari without HDP.
I am +1(non-binding) on this approach to have selects in bigtop code. May be for long term , we can think for tarballs or mpacks which can go in mabari trunk.
On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
Hi Ambari/Bigtop dev,
As per the new roadmap of Apache Ambari, we would like to propose moving
certain scripts (previously known as hdp-select and conf-select) to Bigtop
so that their rpm installation could be managed independently.
These scripts are a basic necessity in the Ambari framework for the
installation of various Bigdata packages. The only major changes they would
receive is when we onboard new services and components to Ambari, else they
usually do not receive updates. In the past, we used to get hdp-select rpm
downloaded and installed from HDP repositories.
We have still not officially finalized the new replacement name for
hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
the purpose of bdp-select and conf-select remains the same.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ambari.apache.org
For additional commands, e-mail: dev-help@ambari.apache.org
Re: [DISCUSS] Move Ambari select packages to Bigtop
Posted by "Battula, Brahma Reddy" <bb...@visa.com.INVALID>.
Thanks @Viraj Jasani to start discussing on this.
IMO, For upcoming ambari release(2.7.7) , we should have select other than HDP so that people can start using the ambari without HDP.
I am +1(non-binding) on this approach to have selects in bigtop code. May be for long term , we can think for tarballs or mpacks which can go in mabari trunk.
On 29/06/22, 10:22 AM, "Viraj Jasani" <vj...@apache.org> wrote:
Hi Ambari/Bigtop dev,
As per the new roadmap of Apache Ambari, we would like to propose moving
certain scripts (previously known as hdp-select and conf-select) to Bigtop
so that their rpm installation could be managed independently.
These scripts are a basic necessity in the Ambari framework for the
installation of various Bigdata packages. The only major changes they would
receive is when we onboard new services and components to Ambari, else they
usually do not receive updates. In the past, we used to get hdp-select rpm
downloaded and installed from HDP repositories.
We have still not officially finalized the new replacement name for
hdp-select, it would likely be bdp-select (bdp: BigData Platform). However,
the purpose of bdp-select and conf-select remains the same.