Re: Testing Docker images (and possibly other cloud images) in CentOS CI
On Thu, Jul 2, 2015 at 8:12 PM, Matthew Miller mat...@fedoraproject.org wrote: At Summit, I talked briefly to Karanbir Singh from CentOS. CentOS has a Jenkins system with a lot of hardware behind it (https://ci.centos.org/), and they run all of their layered image builds* through that. KB offered to run their tests on any images Fedora produces. That seems cool, but I'm not sure how we could best take advantage of this. How could we integrate such tests into our processes? As a first step, does anyone have a problem with saying to CentOS, Cool! Start running those tests! Thanks! — even if we don't know what exactly what we're going to do with any results? I'm imagining that once we get to $futurephase of the build service plan, layered images will go through Bodhi just like RPMs, and at that point, this feedback could be hooked in there. In the meantime, packagers of layered images could simply be told to look manually. This sounds great. I am already doing similar kind of work for Python upstream in ci.centos.org. The tests themselves, as I understand it, are documented at http://wiki.centos.org/QaWiki/AutomatedTests/WritingTests/t_functional, by the way, including contribution information. We can use most of these t_fuctional tests, just that instead of yum, we have dnf. * See change proposal for a layered image build service for Fedora — actually testing images which are produced is a next step specifically listed as out of scope for the change itself. https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service +1 Kushal -- Fedora Cloud Engineer CPython Core Developer http://kushaldas.in ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Testing Docker images (and possibly other cloud images) in CentOS CI
Mike, KB would like to see our test cases for the cloud images. Could you forward them to him? Regards H. ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Testing Docker images (and possibly other cloud images) in CentOS CI
At Summit, I talked briefly to Karanbir Singh from CentOS. CentOS has a Jenkins system with a lot of hardware behind it (https://ci.centos.org/), and they run all of their layered image builds* through that. KB offered to run their tests on any images Fedora produces. That seems cool, but I'm not sure how we could best take advantage of this. How could we integrate such tests into our processes? As a first step, does anyone have a problem with saying to CentOS, Cool! Start running those tests! Thanks! — even if we don't know what exactly what we're going to do with any results? I'm imagining that once we get to $futurephase of the build service plan, layered images will go through Bodhi just like RPMs, and at that point, this feedback could be hooked in there. In the meantime, packagers of layered images could simply be told to look manually. The tests themselves, as I understand it, are documented at http://wiki.centos.org/QaWiki/AutomatedTests/WritingTests/t_functional, by the way, including contribution information. * See change proposal for a layered image build service for Fedora — actually testing images which are produced is a next step specifically listed as out of scope for the change itself. https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Testing Docker images (and possibly other cloud images) in CentOS CI
On 07/02/2015 10:42 AM, Matthew Miller wrote: As a first step, does anyone have a problem with saying to CentOS, Cool! Start running those tests! Thanks! — even if we don't know what exactly what we're going to do with any results? Heck no, no problem whatsoever. Surely we subscribe to the idea that anybody should be free to run or test our software as part of the freedom we promote with Fedora. Totally happy to see the CentOS folks doing this. Best, jzb -- Joe Brockmeier | Community Team, OSAS j...@redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ signature.asc Description: OpenPGP digital signature ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Testing Docker images (and possibly other cloud images) in CentOS CI
2015-07-02 16:42 GMT+02:00 Matthew Miller mat...@fedoraproject.org: As a first step, does anyone have a problem with saying to CentOS, Cool! Start running those tests! Thanks! — even if we don't know what exactly what we're going to do with any results? I'm imagining that once we get to $futurephase of the build service plan, layered images will go through Bodhi just like RPMs, and at that point, this feedback could be hooked in there. In the meantime, packagers of layered images could simply be told to look manually. Not at all. More QA never hurts, and this is a step toward more collaboration between Fedora CentOS. *We* are more than just two distro but a whole ecosystem. Regards, H. ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Testing Docker images (and possibly other cloud images) in CentOS CI
On 07/02/2015 09:42 AM, Matthew Miller wrote: At Summit, I talked briefly to Karanbir Singh from CentOS. CentOS has a Jenkins system with a lot of hardware behind it (https://ci.centos.org/), and they run all of their layered image builds* through that. KB offered to run their tests on any images Fedora produces. That seems cool, but I'm not sure how we could best take advantage of this. How could we integrate such tests into our processes? As a first step, does anyone have a problem with saying to CentOS, Cool! Start running those tests! Thanks! — even if we don't know what exactly what we're going to do with any results? No problem at all. This is great news and I've brought up the need for this many times in the past. Excellent. Thanks for driving this. I'm imagining that once we get to $futurephase of the build service plan, layered images will go through Bodhi just like RPMs, and at that point, this feedback could be hooked in there. In the meantime, packagers of layered images could simply be told to look manually. AIUI, this all goes through the Fedora-Dockerfiles repo. I don't know what this would look like, but I'm envisioning the CentOS Jenkins system pulling in this repo, and then running x scripts to confirm things are working, based on some trigger. At that point, maybe it sends an email out to a list for pass / fail? Which list? These are details we will work out. The tests themselves, as I understand it, are documented at http://wiki.centos.org/QaWiki/AutomatedTests/WritingTests/t_functional, by the way, including contribution information. I'll have a look at this. It would be good to have others look at it too. We can coordinate this effort on the next cloud-sig meeting? * See change proposal for a layered image build service for Fedora — actually testing images which are produced is a next step specifically listed as out of scope for the change itself. https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service I'm curious how this will work. After reading this, I found this statement: This Change does not include running a Fedora container registry. Although we might want to do so in the future, this should not be a blocker. Container images will be a) delivered to the upstream Docker Hub and b) put on the Fedora FTP/HTTP mirror network. What I'm focusing on is the statement for a. This would break the docker trusted builds for Fedora the way they are currently structured. ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Testing Docker images (and possibly other cloud images) in CentOS CI
On Thu, Jul 02, 2015 at 12:22:54PM -0500, Scott Collier wrote: AIUI, this all goes through the Fedora-Dockerfiles repo. I don't know what this would look like, but I'm envisioning the CentOS Jenkins system pulling in this repo, and then running x scripts to confirm things are working, based on some trigger. At that point, maybe it sends an email out to a list for pass / fail? Which list? These are details we will work out. *nod* (And taking the test list off of the CC since the following isn't a test discussion...) I can't believe I didn't consult with you on the Layered Builds change proposal, since you've been doing the Fedora Dockerfiles. Sorry — I should have made sure you were included. As you've probably seen, the change calls for dist-git style management of the dockerfiles, which would mean one repo for each one, rather than one mega-repo — the theory being that this can scale better and allow more independence. This seemed like a good idea to me, but I hadn't really stopped to consider the impact on the current Fedora Dockerfiles package. I guess eventually it could be separated into various components — or in fact could be the basis of an initial immediate set. What do you think? Another thing of note: we could talk with Infrastructure about adding Pagure support to all the new dist-git repos, so they'd all have a web based interface, pull requests, etc. -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Testing Docker images (and possibly other cloud images) in CentOS CI
On 07/02/2015 01:39 PM, Matthew Miller wrote: On Thu, Jul 02, 2015 at 12:22:54PM -0500, Scott Collier wrote: AIUI, this all goes through the Fedora-Dockerfiles repo. I don't know what this would look like, but I'm envisioning the CentOS Jenkins system pulling in this repo, and then running x scripts to confirm things are working, based on some trigger. At that point, maybe it sends an email out to a list for pass / fail? Which list? These are details we will work out. *nod* (And taking the test list off of the CC since the following isn't a test discussion...) I can't believe I didn't consult with you on the Layered Builds change proposal, since you've been doing the Fedora Dockerfiles. Sorry — I should have made sure you were included. no problem. happy to participate in future discussions if needed. As you've probably seen, the change calls for dist-git style management of the dockerfiles, which would mean one repo for each one, rather than one mega-repo — the theory being that this can scale better and allow more independence. I agree with this approach. I think it would encourage ownership as well. This seemed like a good idea to me, but I hadn't really stopped to consider the impact on the current Fedora Dockerfiles package. I guess eventually it could be separated into various components This could be done without to much trouble. Each directory in Fedora-Dockerfiles stands on it's own. It would be a good starting point for the eventual maintainer of each component. I do think it would make sense to leave Fedora-Dockerfiles in some working state moving forward for others to practice on. Unless there was some well defined process for sharing the dist-git content. I'm not familiar with dist-get. — or in fact could be the basis of an initial immediate set. What do you think? Yup, could do that. Another thing of note: we could talk with Infrastructure about adding Pagure support to all the new dist-git repos, so they'd all have a web based interface, pull requests, etc. ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Testing Docker images (and possibly other cloud images) in CentOS CI
On Thu, Jul 02, 2015 at 12:22:54PM -0500, Scott Collier wrote: This Change does not include running a Fedora container registry. Although we might want to do so in the future, this should not be a blocker. Container images will be a) delivered to the upstream Docker Hub and b) put on the Fedora FTP/HTTP mirror network. What I'm focusing on is the statement for a. This would break the docker trusted builds for Fedora the way they are currently structured. H, thanks for noting this. What's the impact/downside of that? I know that Docker changed trusted to automated, because they're not actually offering any claim to trust through this feature. Is there a way we could structure it differently to get any similar benefit? -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Testing Docker images (and possibly other cloud images) in CentOS CI
On Thu, Jul 2, 2015, at 02:39 PM, Matthew Miller wrote: As you've probably seen, the change calls for dist-git style management of the dockerfiles, which would mean one repo for each one, rather than one mega-repo — the theory being that this can scale better and allow more independence. Honestly I've often wished dist-git supported multiple packages per git repo. (Really, everything should support aggregration, including less lame chain-builds). For example, it's quite common when submitting new packages for review to have *multiple* which are very similar (A depends on B), and we just amplify our pain for little gain by splitting everything up all of the time into tiny little bits. Github does quite well with the $organization/$component model, and in a lot of cases it'd make sense to match that in dist-git (and package names...). ___ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
