[Container-tools] Hosting Atomic Registry

[Karanbir Singh]

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

On 24/03/16 02:18, Aaron Weitekamp wrote:
> I had a thought that it would be good to host a sandbox registry
> that people could login in via github & google SSO, push something,
> share with a colleague. We would implement quota control and prune
> images daily(?) to keep costs down.
> 
> But I'm wondering how this relates to the build pipeline. What is
> the registry story there? Do we have plans to host a community
> registry for the world? Is there budget? Would quotas help?

would really like to work on this, and help facilitate.

Having a Registry2Go that folks can walk away with, on prem deploy and
consume in a similar fashion to a git workflow, has been something
I've been very keen to do; this might be the way to make that happen too
.

w.r.t the wider pub registry - yes, we will host an end point
(registry!) for all content built via the centos container pipeline.
Even for content folks want delivered elsewhere. We need this for the
lifecycle/update reporting followup.

hoping to work with soft quotas to start with, might need to implement
fair-use if things get hectic. Mostly constrained by network capacity.

Regards

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

iQEcBAEBAgAGBQJW81BhAAoJEI3Oi2Mx7xbtz5gH/2O5f+PpBXkW4nGpqrNs5shW
j7gsZVsWuyqLymbwi4ck9tq2EMu4e7c6EkLaQZ4wPcI8w5GKCGZOkFwKOq/qqVFT
a8IbAFObP3IchRF8UmQGtIhP4SpFdx5jdvrv2Bwd86Y98c2Ktq/gZPTLKw1UHr3j
5WyHOyukgi3b8RwEF0wgIC5/gpcJWbvkTnMLCLFMhCg0si81eN/sI+FK9+H61Iae
9VVYzpBuXXaWrbmCFuT7cpufH83fJYUicVRU3n6FdOD8iTWgnpG5x2kpJMHV+Pwi
YJ13LTsnKR6pLSK1shj0L9sZYyMuhIz8rOsz7FjRGhUzejdp8vlcOFEsmmQYB4k=
=yDll
-----END PGP SIGNATURE-----