Am 18.06.19 um 16:33 schrieb David Galloway:
What's the status of registry.ceph.com? Has it been abandoned? Can we repurpose or kill it? It's currently in OVH's cloud (not Sepia). We can host a container registry (publicly) in the Sepia lab no problem. We could even use the LRC as backing storage.
I kind of like the idea of including tarballs with existing chacra repos
Are these tarsthen consumable (pullable) like any other container image? Or differently, is Rook able to consume them?
like what Dan mentions. I suspect that would minimize the amount of hacking needed of other tools.
This isn't something we can accomplish this week but we can certainly get a game plan going. I would recommend we start with a nightly build before building every sha1.
If we end up going with a simple container registry, teuthology will need some hacking. If we want to use shaman/chacra, the will both need some hacking along with teuthology.
On 6/17/19 12:43 PM, Dan Mick wrote:
I've been having good luck with experiments of creating the container as a tarball and shipping it around as an asset in parallel to the packages. This might ease the integration with teuthology and other things that consume shaman without having to worry about running a docker registry separately.
On Mon, Jun 17, 2019, 9:06 AM Sage Weil <sweil@redhat.com <mailto:sweil@redhat.com>> wrote:
On Mon, 17 Jun 2019, Sebastien Han wrote: > +Dimitri Savineau for ceph-container related questions. > I think it'd be nice to have the registry public so that everyone can > access and test a build.
Definitely!
sage
> > Thanks! > ––––––––– > Sébastien Han > Principal Software Engineer, Storage Architect > > "Always give 100%. Unless you're giving blood." > > On Mon, Jun 17, 2019 at 5:34 PM Sage Weil <sweil@redhat.com <mailto:sweil@redhat.com>> wrote: > > > > Hi everyone, > > > > I'd really like to push this through and get something working this week. > > After poking around it seems clear that there aren't any other registries > > we should be using for our temp/test builds (unless we just spam > > dockerhub, but that seems unwise). So, let's just get over ourselves and > > run our own registry. > > > > 1- Where to put it? I'm assuming this should go in the same place that > > chacra is putting our other temp builds. This is in RDU, right? What > > machine(s) should we use? If we use the same retention policy as the > > debs/rpms then this will be an incremental increase in the storage needed. > > > > 2- What registry software to use? We don't need any fancy featuers > > whatsoever--just the ability to push, pull, and delete images. So, > > whatever is easiest to set up. > > > > 3- Jenkins integration. I think we need to have a child job linked to the > > centos build to do the ceph-container build and then push. Similarly, > > whatever it is that removes the old packages from the repos needs to also > > delete the image. > > > > 4- Chacra/shaman integration? Should the container build show up in > > shaman/chacra as well? Is there extra work needed to do that? > > > > Thanks! > > sage > > > _______________________________________________ > Sepia mailing list -- sepia@ceph.io <mailto:sepia@ceph.io> > To unsubscribe send an email to sepia-leave@ceph.io <mailto:sepia-leave@ceph.io> > _______________________________________________ Sepia mailing list -- sepia@ceph.io <mailto:sepia@ceph.io> To unsubscribe send an email to sepia-leave@ceph.io <mailto:sepia-leave@ceph.io>
_______________________________________________ Sepia mailing list -- sepia@ceph.io To unsubscribe send an email to sepia-leave@ceph.io
_______________________________________________ Sepia mailing list -- sepia@ceph.io To unsubscribe send an email to sepia-leave@ceph.io
-- SUSE Linux GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nürnberg)