[Container-tools] Creating a download location for ADB Vagrant boxes

[Karanbir Singh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/10/15 11:46, Lalatendu Mohanty wrote:
> On 10/08/2015 04:10 PM, Karanbir Singh wrote: On 08/10/15 11:32,
> Lalatendu Mohanty wrote:
>>>> Hi,
>>>> 
>>>> As part of ADB project we are planning to do time based
>>>> release (i.e. every month) +  intermediate releases for
>>>> blocker bugs and security issues etc.
>>>> 
>>>> There are two ways to deliver the vagrant box to users.
>>>> 
>>>> 1. Making the box available somewhere, so that users can
>>>> download it through http or ftp. 2. Uploading or link the
>>>> Vagrant box from atlas.hashicorp.com
>>>> 
>>>> So for both the two delivery mechanism we need a http/ftp
>>>> download location to put the boxes, so that community can
>>>> consume it. Currently the box is CentOS based, so we are
>>>> discussing to get the ADB Vagrant included in to CentOS SIG
>>>> (most be Atomic SIG or something appropriate) [1] .
>>>> 
>>>> However it is moving slowly then expected, so I think it
>>>> would be better to get a http/ftp location where we can host
>>>> boxes for community to consume. It will help us in below
>>>> things.
>>>> 
>>>> 1. This location can be used to host things from container
>>>> tools team. 2. We can host the Vagrant box till it is
>>>> accepted in respective communities.
>>>> 
>>>> Comments/suggestions are welcome.
>>>> 
>>>> [1] 
>>>> https://lists.centos.org/pipermail/centos-devel/2015-September/0137
77.
>
>>>> 
html
> 
> 
> how do yo define the target audience for this content ? that would 
> then define what release cadence you want to setup, and where you
> want to host the content and how you want to announce ( and where
> to )
>> The target audience of ADB box would be users who want to try
>> out atomicapp, Nulecule, OpenShift, docker (on Windows and OS
>> X).

so, 'try out' only ?

the key being that if you want to provide the people on this mailing
list with a very fast release cycle, perhaps nightly, so they can
validate their own work rapidly V/s providing the wider contributor
base V/s provider the wider userbase ( ! contributor ).

For the second two of those situations is where it makes sense to use
centos.org resources, and then do quickstart guides, announces,
mechanics from the CentOS side of things.

I suspect the first of those groups is likely happy with a yum update
in an established box, nightly ?

>> Release cadence would be building the box -> testing the box -> 
>> releasing the box -> sending announcements. I am open to
>> suggestion too.

a box is a point in time snapshot payload, consider the payload as a
constant stream of rpms and yum 'content pools'. the box to me, is a
way to get people started, once they are on it - you need a good
communication channel and content in that channel to keep them using
the box, updating to always-usable / tested content.

again, look at the audience this is being done for and work back from
there.

happy to help in whatever way we can,

- -- 
Karanbir Singh, The CentOS Project, London, UK
RH Ext. 8274455 | DID: 0044 207 009 4455
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJWFlEkAAoJEI3Oi2Mx7xbtHEYH/0QmvZs/P1wI3PjrtRpJ52J9
zyI5GwsL7WVAqkvEhObTFTeODSc1zkubKZanOS5ZWaGH9uEi78/wJ+aMFflZyMGt
ANq6uLKkA9v9AwIIdTInioKZkLrreC78v5QIDlb89vtvligrI5Ij/UEWDKsEbybb
Os3lUqVQ9LXv2qzvLd+PUhxHw670tjtu1F3kpJ1E7hCIc3rWyh6L96NlLZpAK1Rs
YIY2G8ZVPbnQwiIPQJkC7s3E5uWvTz0n3KTPH5K0pRJ63GFG5kX/eVeoQxG8jVib
g0wiJMqp6RhBGc0zTWybLXUVcGUyRk8clRmmNdeyK4CZSm01HPvjinPYJ4DO7ok=
=8DHt
-----END PGP SIGNATURE-----