[Dev] zona downloads

[Brett Wooldridge]

We already look for a "ztools" header in bundles to determine whether it contains tools.  I think that's sufficient, and allows for the possibility for an adapter bundle to also be a tools bundle given that they employ different headers.  The bundle names are mostly for our benefit, and have no operational impact (nor should they).

-Brett



On 11/27/07 8:49 PM, "Ryan Kruse" <rkruse at alterpoint.com> wrote:

I agree with Brett on the naming scheme too.

Brett, in the adapter bundle manifest we set a Bundle-Type: adapter field rather than a relying on a naming scheme.  We might want to do the same for tools or at least only look for *.tools.*.  I can imagine that a reseller might build <reseller>.tools.* and <reseller>.adapters.* bundles as well.

-Ryan

________________________________
From: dev-bounces at ziptie.org [mailto:dev-bounces at ziptie.org] On Behalf Of Brett Wooldridge
Sent: Tuesday, November 27, 2007 8:42 PM
To: ZipTie Development List
Subject: Re: [Dev] zona downloads

This looks good, other than a proposed name change for tools bundles.  In the same way that we have:

ziptie.adapters.cisco...
ziptie.adapters.riverbed...

We should have:

ziptie.tools.cisco...
ziptie.tools.riverbed...

Rather than org.ziptie.tools.scripts.cisco, org.ziptie.tools.script.riverbed.  This makes it easier to distinguish core ZipTie bundles from tools, which is why we chose the naming scheme for adapters.  Doing do also makes it a little easier in build tooling.  Also removing 'scripts' from the bundle name is good because Java tools are also possible.

I'm not sure on the _<version> in the crate name, I'll let Leo weigh in on that one..  But I think crates have an internal version number as well.

-Brett


On 11/27/07 7:22 PM, "Kartick Suriamoorthy" <ksuriamoorthy at alterpoint.com> wrote:



All,

As we flesh out the ZONA vendor  pages, end users
will need a mechanism to download the content  from
those pages. As of now content consists of either
adapters or  tools.

Adapter downloads :
Since an adapter can contain multiple  folders or
files, users should be able to download a zip file
containing  all the files necessary to deploy that
adapter. The zip file shall contain  the adapter
bundle and a crate file that contains the adapter
bundle id,  version, location, etc.

Example :
The  ziptie.adapters.riverbed.steelhead.zip should
contain all the files that  are part of the Riverbed
Steelhead adapter bundle and a crate file  -
ziptie.adapters.riverbed.steelhead_<version>.crate

Tools  downloads :
All vendor specific tools are going to be checked
into their  own bundle. A zip of that bundle will
be made available to end users via  the ZONA vendor
page. Users get to download all the available
tools for  that vendor and will not be able to pick
and choose the individual tools  that they want
or do not want from the download page (users can
always  delete the tools that they are not interested
in after downloading the  tools bundle).

Example :
All Riverbed tools are going to be checked  into a
bundle called org.ziptie.tools.scripts.riverbed.
A zip file  (o.z.tools.scripts.riverbed.zip) will
be made available for users to  download. This zip
will also contain a crate file  -
org.ziptie.tools.scripts.riverbed_<version>.crate

Nightly  Build :
The nighly build should create these zips and push
it out to  ziptie.org/builds directory. The builds
directory will have a "zona"  directory, which will
contain all the zips.

Please let me know if  anybody has any feedback or
needs more info on how this is going to  work.

Thanks,
Kartick

_______________________________________________
Dev  mailing list
Dev at ziptie.org
http://mailman.ziptie.org/listinfo/dev





-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ziptie.org/pipermail/dev/attachments/20071127/81a79b14/attachment-0001.html