You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by Ted Yu <yu...@gmail.com> on 2014/07/19 15:03:03 UTC
wildcard for version in package_list
Hi,
Currently user has to specify the version in package_list of appConfig.json
:
"package_list": "files/accumulo-${accumulo.version}-bin.tar.gz",
I wonder if we should allow for multiple versions (through wildcard).
The rationale is that there is only one tar ball under package/files
directory inside the app package.
By allowing multiple versions, user can use the same appConfig.json for
different app packages (corresponding to different releases of the
underlying app).
Cheers
Re: wildcard for version in package_list
Posted by Sumit Mohanty <su...@gmail.com>.
Sorry, my reply was meant for an internal discussion (pls. disregard). What
I meant was that an app package should only contain application tarballs
that are verified by the package producer.
On Wed, Jul 30, 2014 at 7:33 AM, Sumit Mohanty <su...@gmail.com>
wrote:
> Not the Slider releases but the app packages themselves - considering QE
> team will test only one version. I am referring to the app packages
> released by HWX. I guess, after Champlain we will have two tested versions
> of say HBase on Slider and at that point we can package more than one
> tarball into the same package.
>
>
> On Wed, Jul 30, 2014 at 3:02 AM, Steve Loughran <st...@hortonworks.com>
> wrote:
>
>> On 19 July 2014 18:24, Sumit Mohanty <su...@gmail.com> wrote:
>>
>> > If a package author wants to pack multiple tarballs and a directive to
>> > switch between them through appConfig they can do so. In my opinion, our
>> > packages should not be that way as at any given point HDP release only
>> has
>> > one specific version for each and thus the Slider App package should
>> also
>> > contain the same version.
>> >
>>
>> but we aren't constraining slider releases to be in sync with any hadoop
>> deployment -or the artifacts they deploy.
>>
>>
>>
>> >
>> >
>> > On Sat, Jul 19, 2014 at 8:12 AM, Billie Rinaldi <
>> billie.rinaldi@gmail.com>
>> > wrote:
>> >
>> > > There is also the app def property in app config that tells the name
>> of
>> > the
>> > > app package in HDFS. Currently this would have the Accumulo version
>> in it
>> > > as well. You can name the app package anything you want, but if you're
>> > > working with multiple packages for different app versions (which
>> seems to
>> > > be Ted's motivation), it would get confusing fast if you couldn't
>> > > distinguish them by the package name.
>> > >
>> > > And there's the app_root. That's the name of the untarred app
>> directory,
>> > > which also contains the version.
>> > >
>> > > So until we figure out ways to address all these issues, you're stuck
>> > with
>> > > with a different app config for each package.
>> > > On Jul 19, 2014 10:42 AM, "Jon Maron" <jm...@hortonworks.com> wrote:
>> > >
>> > > > If we limit the package to one app, is there a need for specifying
>> the
>> > > > version at all? If we do specify it, should it be regarded as the
>> > > > displayed version or application name value rather than a specific
>> file
>> > > > name?
>> > > >
>> > > >
>> > > > > On Jul 19, 2014, at 9:03 AM, Ted Yu <yu...@gmail.com> wrote:
>> > > > >
>> > > > > Hi,
>> > > > > Currently user has to specify the version in package_list of
>> > > > appConfig.json
>> > > > > :
>> > > > > "package_list":
>> "files/accumulo-${accumulo.version}-bin.tar.gz",
>> > > > >
>> > > > > I wonder if we should allow for multiple versions (through
>> wildcard).
>> > > > > The rationale is that there is only one tar ball under
>> package/files
>> > > > > directory inside the app package.
>> > > > > By allowing multiple versions, user can use the same
>> appConfig.json
>> > for
>> > > > > different app packages (corresponding to different releases of the
>> > > > > underlying app).
>> > > > >
>> > > > > Cheers
>> > > >
>> > > > --
>> > > > CONFIDENTIALITY NOTICE
>> > > > NOTICE: This message is intended for the use of the individual or
>> > entity
>> > > to
>> > > > which it is addressed and may contain information that is
>> confidential,
>> > > > privileged and exempt from disclosure under applicable law. If the
>> > reader
>> > > > of this message is not the intended recipient, you are hereby
>> notified
>> > > that
>> > > > any printing, copying, dissemination, distribution, disclosure or
>> > > > forwarding of this communication is strictly prohibited. If you have
>> > > > received this communication in error, please contact the sender
>> > > immediately
>> > > > and delete it from your system. Thank You.
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> > thanks
>> > Sumit
>> >
>>
>> --
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity
>> to
>> which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified
>> that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender
>> immediately
>> and delete it from your system. Thank You.
>>
>
>
>
> --
> thanks
> Sumit
>
--
thanks
Sumit
Re: wildcard for version in package_list
Posted by Sumit Mohanty <su...@gmail.com>.
Not the Slider releases but the app packages themselves - considering QE
team will test only one version. I am referring to the app packages
released by HWX. I guess, after Champlain we will have two tested versions
of say HBase on Slider and at that point we can package more than one
tarball into the same package.
On Wed, Jul 30, 2014 at 3:02 AM, Steve Loughran <st...@hortonworks.com>
wrote:
> On 19 July 2014 18:24, Sumit Mohanty <su...@gmail.com> wrote:
>
> > If a package author wants to pack multiple tarballs and a directive to
> > switch between them through appConfig they can do so. In my opinion, our
> > packages should not be that way as at any given point HDP release only
> has
> > one specific version for each and thus the Slider App package should also
> > contain the same version.
> >
>
> but we aren't constraining slider releases to be in sync with any hadoop
> deployment -or the artifacts they deploy.
>
>
>
> >
> >
> > On Sat, Jul 19, 2014 at 8:12 AM, Billie Rinaldi <
> billie.rinaldi@gmail.com>
> > wrote:
> >
> > > There is also the app def property in app config that tells the name of
> > the
> > > app package in HDFS. Currently this would have the Accumulo version in
> it
> > > as well. You can name the app package anything you want, but if you're
> > > working with multiple packages for different app versions (which seems
> to
> > > be Ted's motivation), it would get confusing fast if you couldn't
> > > distinguish them by the package name.
> > >
> > > And there's the app_root. That's the name of the untarred app
> directory,
> > > which also contains the version.
> > >
> > > So until we figure out ways to address all these issues, you're stuck
> > with
> > > with a different app config for each package.
> > > On Jul 19, 2014 10:42 AM, "Jon Maron" <jm...@hortonworks.com> wrote:
> > >
> > > > If we limit the package to one app, is there a need for specifying
> the
> > > > version at all? If we do specify it, should it be regarded as the
> > > > displayed version or application name value rather than a specific
> file
> > > > name?
> > > >
> > > >
> > > > > On Jul 19, 2014, at 9:03 AM, Ted Yu <yu...@gmail.com> wrote:
> > > > >
> > > > > Hi,
> > > > > Currently user has to specify the version in package_list of
> > > > appConfig.json
> > > > > :
> > > > > "package_list": "files/accumulo-${accumulo.version}-bin.tar.gz",
> > > > >
> > > > > I wonder if we should allow for multiple versions (through
> wildcard).
> > > > > The rationale is that there is only one tar ball under
> package/files
> > > > > directory inside the app package.
> > > > > By allowing multiple versions, user can use the same appConfig.json
> > for
> > > > > different app packages (corresponding to different releases of the
> > > > > underlying app).
> > > > >
> > > > > Cheers
> > > >
> > > > --
> > > > CONFIDENTIALITY NOTICE
> > > > NOTICE: This message is intended for the use of the individual or
> > entity
> > > to
> > > > which it is addressed and may contain information that is
> confidential,
> > > > privileged and exempt from disclosure under applicable law. If the
> > reader
> > > > of this message is not the intended recipient, you are hereby
> notified
> > > that
> > > > any printing, copying, dissemination, distribution, disclosure or
> > > > forwarding of this communication is strictly prohibited. If you have
> > > > received this communication in error, please contact the sender
> > > immediately
> > > > and delete it from your system. Thank You.
> > > >
> > >
> >
> >
> >
> > --
> > thanks
> > Sumit
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
--
thanks
Sumit
Re: wildcard for version in package_list
Posted by Steve Loughran <st...@hortonworks.com>.
On 19 July 2014 18:24, Sumit Mohanty <su...@gmail.com> wrote:
> If a package author wants to pack multiple tarballs and a directive to
> switch between them through appConfig they can do so. In my opinion, our
> packages should not be that way as at any given point HDP release only has
> one specific version for each and thus the Slider App package should also
> contain the same version.
>
but we aren't constraining slider releases to be in sync with any hadoop
deployment -or the artifacts they deploy.
>
>
> On Sat, Jul 19, 2014 at 8:12 AM, Billie Rinaldi <bi...@gmail.com>
> wrote:
>
> > There is also the app def property in app config that tells the name of
> the
> > app package in HDFS. Currently this would have the Accumulo version in it
> > as well. You can name the app package anything you want, but if you're
> > working with multiple packages for different app versions (which seems to
> > be Ted's motivation), it would get confusing fast if you couldn't
> > distinguish them by the package name.
> >
> > And there's the app_root. That's the name of the untarred app directory,
> > which also contains the version.
> >
> > So until we figure out ways to address all these issues, you're stuck
> with
> > with a different app config for each package.
> > On Jul 19, 2014 10:42 AM, "Jon Maron" <jm...@hortonworks.com> wrote:
> >
> > > If we limit the package to one app, is there a need for specifying the
> > > version at all? If we do specify it, should it be regarded as the
> > > displayed version or application name value rather than a specific file
> > > name?
> > >
> > >
> > > > On Jul 19, 2014, at 9:03 AM, Ted Yu <yu...@gmail.com> wrote:
> > > >
> > > > Hi,
> > > > Currently user has to specify the version in package_list of
> > > appConfig.json
> > > > :
> > > > "package_list": "files/accumulo-${accumulo.version}-bin.tar.gz",
> > > >
> > > > I wonder if we should allow for multiple versions (through wildcard).
> > > > The rationale is that there is only one tar ball under package/files
> > > > directory inside the app package.
> > > > By allowing multiple versions, user can use the same appConfig.json
> for
> > > > different app packages (corresponding to different releases of the
> > > > underlying app).
> > > >
> > > > Cheers
> > >
> > > --
> > > CONFIDENTIALITY NOTICE
> > > NOTICE: This message is intended for the use of the individual or
> entity
> > to
> > > which it is addressed and may contain information that is confidential,
> > > privileged and exempt from disclosure under applicable law. If the
> reader
> > > of this message is not the intended recipient, you are hereby notified
> > that
> > > any printing, copying, dissemination, distribution, disclosure or
> > > forwarding of this communication is strictly prohibited. If you have
> > > received this communication in error, please contact the sender
> > immediately
> > > and delete it from your system. Thank You.
> > >
> >
>
>
>
> --
> thanks
> Sumit
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: wildcard for version in package_list
Posted by Sumit Mohanty <su...@gmail.com>.
If a package author wants to pack multiple tarballs and a directive to
switch between them through appConfig they can do so. In my opinion, our
packages should not be that way as at any given point HDP release only has
one specific version for each and thus the Slider App package should also
contain the same version.
On Sat, Jul 19, 2014 at 8:12 AM, Billie Rinaldi <bi...@gmail.com>
wrote:
> There is also the app def property in app config that tells the name of the
> app package in HDFS. Currently this would have the Accumulo version in it
> as well. You can name the app package anything you want, but if you're
> working with multiple packages for different app versions (which seems to
> be Ted's motivation), it would get confusing fast if you couldn't
> distinguish them by the package name.
>
> And there's the app_root. That's the name of the untarred app directory,
> which also contains the version.
>
> So until we figure out ways to address all these issues, you're stuck with
> with a different app config for each package.
> On Jul 19, 2014 10:42 AM, "Jon Maron" <jm...@hortonworks.com> wrote:
>
> > If we limit the package to one app, is there a need for specifying the
> > version at all? If we do specify it, should it be regarded as the
> > displayed version or application name value rather than a specific file
> > name?
> >
> >
> > > On Jul 19, 2014, at 9:03 AM, Ted Yu <yu...@gmail.com> wrote:
> > >
> > > Hi,
> > > Currently user has to specify the version in package_list of
> > appConfig.json
> > > :
> > > "package_list": "files/accumulo-${accumulo.version}-bin.tar.gz",
> > >
> > > I wonder if we should allow for multiple versions (through wildcard).
> > > The rationale is that there is only one tar ball under package/files
> > > directory inside the app package.
> > > By allowing multiple versions, user can use the same appConfig.json for
> > > different app packages (corresponding to different releases of the
> > > underlying app).
> > >
> > > Cheers
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
> >
>
--
thanks
Sumit
Re: wildcard for version in package_list
Posted by Billie Rinaldi <bi...@gmail.com>.
There is also the app def property in app config that tells the name of the
app package in HDFS. Currently this would have the Accumulo version in it
as well. You can name the app package anything you want, but if you're
working with multiple packages for different app versions (which seems to
be Ted's motivation), it would get confusing fast if you couldn't
distinguish them by the package name.
And there's the app_root. That's the name of the untarred app directory,
which also contains the version.
So until we figure out ways to address all these issues, you're stuck with
with a different app config for each package.
On Jul 19, 2014 10:42 AM, "Jon Maron" <jm...@hortonworks.com> wrote:
> If we limit the package to one app, is there a need for specifying the
> version at all? If we do specify it, should it be regarded as the
> displayed version or application name value rather than a specific file
> name?
>
>
> > On Jul 19, 2014, at 9:03 AM, Ted Yu <yu...@gmail.com> wrote:
> >
> > Hi,
> > Currently user has to specify the version in package_list of
> appConfig.json
> > :
> > "package_list": "files/accumulo-${accumulo.version}-bin.tar.gz",
> >
> > I wonder if we should allow for multiple versions (through wildcard).
> > The rationale is that there is only one tar ball under package/files
> > directory inside the app package.
> > By allowing multiple versions, user can use the same appConfig.json for
> > different app packages (corresponding to different releases of the
> > underlying app).
> >
> > Cheers
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
Re: wildcard for version in package_list
Posted by Jon Maron <jm...@hortonworks.com>.
If we limit the package to one app, is there a need for specifying the version at all? If we do specify it, should it be regarded as the displayed version or application name value rather than a specific file name?
> On Jul 19, 2014, at 9:03 AM, Ted Yu <yu...@gmail.com> wrote:
>
> Hi,
> Currently user has to specify the version in package_list of appConfig.json
> :
> "package_list": "files/accumulo-${accumulo.version}-bin.tar.gz",
>
> I wonder if we should allow for multiple versions (through wildcard).
> The rationale is that there is only one tar ball under package/files
> directory inside the app package.
> By allowing multiple versions, user can use the same appConfig.json for
> different app packages (corresponding to different releases of the
> underlying app).
>
> Cheers
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.