Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems
Well, I could make it test every patchset, but then I have to look into how to limit at one build per time + queue the other builds. (didn't try that yet) Anyways, I just got my new CI machine so I'll be able to finalize the CI system relatively soon. 2014-08-14 1:01 GMT+02:00 Jeremy Stanley fu...@yuggoth.org: On 2014-08-13 16:30:23 + (+), Asselin, Ramy wrote: I remember infra team objected to the nightly builds. They wanted reports on every patch set in order to report to gerrit. [...] I can't imagine, nor do I recall, objecting to such an idea. The question is merely where you expect to publish the results, and how you deal with the fact that you're testing changes which have already merged rather than getting in front of the reviewers on proposed changes. I don't personally have any specific desire for third-party CI systems to report on changes in Gerrit, but individual projects supporting your drivers/features/whatever might. -- Jeremy Stanley ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- David Pineau, Developer RD at Scality ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems
Hello, I have currently setup the Scality CI not to report (mostly because it isn't fully functionnal yet, as the machine it runs on turns out to be undersized and thus the tests fails on some timeout), partly because it's currently a nightly build. I have no way of testing multiple patchsets at the same time so it is easier this way. How do you plan to Officialize the different 3rd party CIs ? I remember that the cinder meeting about that in the Atlanta Summit concluded that a nightly build would be enough, but such build cannot really report on gerrit. David Pineau gerrit: Joachim IRC#freenode: joa 2014-08-13 2:28 GMT+02:00 Asselin, Ramy ramy.asse...@hp.com: I forked jaypipe’s repos working on extending it to support nodepool, log server, etc. Still WIP but generally working. If you need help, ping me on IRC #openstack-cinder (asselin) Ramy From: Jesse Pretorius [mailto:jesse.pretor...@gmail.com] Sent: Monday, August 11, 2014 11:33 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems On 12 August 2014 07:26, Amit Das amit@cloudbyte.com wrote: I would like some guidance in this regards in form of some links, wiki pages etc. I am currently gathering the driver cert test results i.e. tempest tests from devstack in our environment CI setup would be my next step. This should get you started: http://ci.openstack.org/third_party.html Then Jay Pipes' excellent two part series will help you with the details of getting it done: http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing-system/ http://www.joinfu.com/2014/02/setting-up-an-openstack-external-testing-system-part-2/ ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- David Pineau, Developer RD at Scality ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems
I remember infra team objected to the nightly builds. They wanted reports on every patch set in order to report to gerrit. In the short-term, I suggest you test on every patch set, but limit the resources. This will cause 'long delays' but jobs will eventually go through. In the long-term, you'll need to scale. Currently, we're just running 1 job per back-end at a time. -Original Message- From: David Pineau [mailto:dav.pin...@gmail.com] Sent: Wednesday, August 13, 2014 2:19 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems Hello, I have currently setup the Scality CI not to report (mostly because it isn't fully functionnal yet, as the machine it runs on turns out to be undersized and thus the tests fails on some timeout), partly because it's currently a nightly build. I have no way of testing multiple patchsets at the same time so it is easier this way. How do you plan to Officialize the different 3rd party CIs ? I remember that the cinder meeting about that in the Atlanta Summit concluded that a nightly build would be enough, but such build cannot really report on gerrit. David Pineau gerrit: Joachim IRC#freenode: joa 2014-08-13 2:28 GMT+02:00 Asselin, Ramy ramy.asse...@hp.com: I forked jaypipe’s repos working on extending it to support nodepool, log server, etc. Still WIP but generally working. If you need help, ping me on IRC #openstack-cinder (asselin) Ramy From: Jesse Pretorius [mailto:jesse.pretor...@gmail.com] Sent: Monday, August 11, 2014 11:33 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems On 12 August 2014 07:26, Amit Das amit@cloudbyte.com wrote: I would like some guidance in this regards in form of some links, wiki pages etc. I am currently gathering the driver cert test results i.e. tempest tests from devstack in our environment CI setup would be my next step. This should get you started: http://ci.openstack.org/third_party.html Then Jay Pipes' excellent two part series will help you with the details of getting it done: http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing -system/ http://www.joinfu.com/2014/02/setting-up-an-openstack-external-testing -system-part-2/ ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- David Pineau, Developer RD at Scality ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems
If you limit yourself to only testing once jenkins has put a +1 on, then you can down a bit... Not sure how to build that into Jay Pipe's pipeline though On 13 August 2014 10:30, Asselin, Ramy ramy.asse...@hp.com wrote: I remember infra team objected to the nightly builds. They wanted reports on every patch set in order to report to gerrit. In the short-term, I suggest you test on every patch set, but limit the resources. This will cause 'long delays' but jobs will eventually go through. In the long-term, you'll need to scale. Currently, we're just running 1 job per back-end at a time. -Original Message- From: David Pineau [mailto:dav.pin...@gmail.com] Sent: Wednesday, August 13, 2014 2:19 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems Hello, I have currently setup the Scality CI not to report (mostly because it isn't fully functionnal yet, as the machine it runs on turns out to be undersized and thus the tests fails on some timeout), partly because it's currently a nightly build. I have no way of testing multiple patchsets at the same time so it is easier this way. How do you plan to Officialize the different 3rd party CIs ? I remember that the cinder meeting about that in the Atlanta Summit concluded that a nightly build would be enough, but such build cannot really report on gerrit. David Pineau gerrit: Joachim IRC#freenode: joa 2014-08-13 2:28 GMT+02:00 Asselin, Ramy ramy.asse...@hp.com: I forked jaypipe’s repos working on extending it to support nodepool, log server, etc. Still WIP but generally working. If you need help, ping me on IRC #openstack-cinder (asselin) Ramy From: Jesse Pretorius [mailto:jesse.pretor...@gmail.com] Sent: Monday, August 11, 2014 11:33 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems On 12 August 2014 07:26, Amit Das amit@cloudbyte.com wrote: I would like some guidance in this regards in form of some links, wiki pages etc. I am currently gathering the driver cert test results i.e. tempest tests from devstack in our environment CI setup would be my next step. This should get you started: http://ci.openstack.org/third_party.html Then Jay Pipes' excellent two part series will help you with the details of getting it done: http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing -system/ http://www.joinfu.com/2014/02/setting-up-an-openstack-external-testing -system-part-2/ ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- David Pineau, Developer RD at Scality ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Duncan Thomas ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems
On 2014-08-13 16:30:23 + (+), Asselin, Ramy wrote: I remember infra team objected to the nightly builds. They wanted reports on every patch set in order to report to gerrit. [...] I can't imagine, nor do I recall, objecting to such an idea. The question is merely where you expect to publish the results, and how you deal with the fact that you're testing changes which have already merged rather than getting in front of the reviewers on proposed changes. I don't personally have any specific desire for third-party CI systems to report on changes in Gerrit, but individual projects supporting your drivers/features/whatever might. -- Jeremy Stanley ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems
On 12 August 2014 07:26, Amit Das amit@cloudbyte.com wrote: I would like some guidance in this regards in form of some links, wiki pages etc. I am currently gathering the driver cert test results i.e. tempest tests from devstack in our environment CI setup would be my next step. This should get you started: http://ci.openstack.org/third_party.html Then Jay Pipes' excellent two part series will help you with the details of getting it done: http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing-system/ http://www.joinfu.com/2014/02/setting-up-an-openstack-external-testing-system-part-2/ ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems
I forked jaypipe’s repos working on extending it to support nodepool, log server, etc. Still WIP but generally working. If you need help, ping me on IRC #openstack-cinder (asselin) Ramy From: Jesse Pretorius [mailto:jesse.pretor...@gmail.com] Sent: Monday, August 11, 2014 11:33 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems On 12 August 2014 07:26, Amit Das amit@cloudbyte.commailto:amit@cloudbyte.com wrote: I would like some guidance in this regards in form of some links, wiki pages etc. I am currently gathering the driver cert test results i.e. tempest tests from devstack in our environment CI setup would be my next step. This should get you started: http://ci.openstack.org/third_party.html Then Jay Pipes' excellent two part series will help you with the details of getting it done: http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing-system/ http://www.joinfu.com/2014/02/setting-up-an-openstack-external-testing-system-part-2/ ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems
On 08/11/2014 06:26 PM, John Griffith wrote: Hey Cinder folks that have their CI systems up and running; first off... awesome!!! I do have one favor to ask however though. Please, please, please monitor your jobs and if they're not working either fix them or disable them. Currently the it seems that none of the implemented jobs are overly reliable (mostly seeing startup failures). Also, if you're jobs systems aren't actually ready (accessible html link to results files) please disable those as well. Thanks, John ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev In support of John's email, I will remind everyone that the sandbox repo is available for testing your third party ci system. Please don't automate the creation of patches, just submit them manually and adding patchsets to current patches is fine. The sandbox repo: http://git.openstack.org/cgit/openstack-dev/sandbox/ Do ask if you need some help or guidance using it. Thanks, Anita. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems
Hi John, I guess this is w.r.t 3rd party cinder drivers. I would like some guidance in this regards in form of some links, wiki pages etc. I am currently gathering the driver cert test results i.e. tempest tests from devstack in our environment CI setup would be my next step. Regards, Amit *CloudByte Inc.* http://www.cloudbyte.com/ On Tue, Aug 12, 2014 at 6:31 AM, Anita Kuno ante...@anteaya.info wrote: On 08/11/2014 06:26 PM, John Griffith wrote: Hey Cinder folks that have their CI systems up and running; first off... awesome!!! I do have one favor to ask however though. Please, please, please monitor your jobs and if they're not working either fix them or disable them. Currently the it seems that none of the implemented jobs are overly reliable (mostly seeing startup failures). Also, if you're jobs systems aren't actually ready (accessible html link to results files) please disable those as well. Thanks, John ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev In support of John's email, I will remind everyone that the sandbox repo is available for testing your third party ci system. Please don't automate the creation of patches, just submit them manually and adding patchsets to current patches is fine. The sandbox repo: http://git.openstack.org/cgit/openstack-dev/sandbox/ Do ask if you need some help or guidance using it. Thanks, Anita. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
