Re: [openstack-dev] [TripleO] CI needs YOU
Latest outage was due to nodepool having a stuck TCP connection to the HP1 region again. I've filed https://bugs.launchpad.net/python-novaclient/+bug/1323862 about it. If someone were to pick this up and run with it it would be super useful. -Rob On 24 May 2014 05:01, Clint Byrum wrote: > I forgot to include a link explaining our cloud: > > https://wiki.openstack.org/wiki/TripleO/TripleOCloud > > Thanks! > > Excerpts from Clint Byrum's message of 2014-05-22 15:24:05 -0700: >> Ahoy there, TripleO interested parties. In the last few months, we've >> gotten a relatively robust, though not nearly complete, CI system for >> TripleO. It is a bit unorthodox, as we have a strong desire to ensure >> PXE booting works, and that requires us running in our own cloud. >> >> We have this working, in two regions of TripleO deployed clouds which >> we manage ourselves. We've had quite a few issues, mostly hardware >> related, and some related to the fact that TripleO doesn't have HA yet, >> so our CI clouds go down whenever our controllers go down. >> >> Anyway, Derek Higgins, Dan Prince, Robert Collins, and myself, have been >> doing most of the heavy lifting on this. As a result, CI is not up and >> working all that often. It needs more operational support. >> >> So, I would encourage anyone interested in TripleO development to start >> working with us to maintain these two cloud regions (hopefully more >> regions will come up soon) so that we can keep CI flowing and expand >> coverage to include even more of TripleO. >> >> Thank you! > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Robert Collins Distinguished Technologist HP Converged Cloud ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] CI needs YOU
I forgot to include a link explaining our cloud: https://wiki.openstack.org/wiki/TripleO/TripleOCloud Thanks! Excerpts from Clint Byrum's message of 2014-05-22 15:24:05 -0700: > Ahoy there, TripleO interested parties. In the last few months, we've > gotten a relatively robust, though not nearly complete, CI system for > TripleO. It is a bit unorthodox, as we have a strong desire to ensure > PXE booting works, and that requires us running in our own cloud. > > We have this working, in two regions of TripleO deployed clouds which > we manage ourselves. We've had quite a few issues, mostly hardware > related, and some related to the fact that TripleO doesn't have HA yet, > so our CI clouds go down whenever our controllers go down. > > Anyway, Derek Higgins, Dan Prince, Robert Collins, and myself, have been > doing most of the heavy lifting on this. As a result, CI is not up and > working all that often. It needs more operational support. > > So, I would encourage anyone interested in TripleO development to start > working with us to maintain these two cloud regions (hopefully more > regions will come up soon) so that we can keep CI flowing and expand > coverage to include even more of TripleO. > > Thank you! ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] CI needs YOU
Hi Clint, Please count me in. Cristian On 22/05/14 19:24, "Clint Byrum" wrote: >Ahoy there, TripleO interested parties. In the last few months, we've >gotten a relatively robust, though not nearly complete, CI system for >TripleO. It is a bit unorthodox, as we have a strong desire to ensure >PXE booting works, and that requires us running in our own cloud. > >We have this working, in two regions of TripleO deployed clouds which >we manage ourselves. We've had quite a few issues, mostly hardware >related, and some related to the fact that TripleO doesn't have HA yet, >so our CI clouds go down whenever our controllers go down. > >Anyway, Derek Higgins, Dan Prince, Robert Collins, and myself, have been >doing most of the heavy lifting on this. As a result, CI is not up and >working all that often. It needs more operational support. > >So, I would encourage anyone interested in TripleO development to start >working with us to maintain these two cloud regions (hopefully more >regions will come up soon) so that we can keep CI flowing and expand >coverage to include even more of TripleO. > >Thank you! > >___ >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
[openstack-dev] [TripleO] CI needs YOU
Ahoy there, TripleO interested parties. In the last few months, we've gotten a relatively robust, though not nearly complete, CI system for TripleO. It is a bit unorthodox, as we have a strong desire to ensure PXE booting works, and that requires us running in our own cloud. We have this working, in two regions of TripleO deployed clouds which we manage ourselves. We've had quite a few issues, mostly hardware related, and some related to the fact that TripleO doesn't have HA yet, so our CI clouds go down whenever our controllers go down. Anyway, Derek Higgins, Dan Prince, Robert Collins, and myself, have been doing most of the heavy lifting on this. As a result, CI is not up and working all that often. It needs more operational support. So, I would encourage anyone interested in TripleO development to start working with us to maintain these two cloud regions (hopefully more regions will come up soon) so that we can keep CI flowing and expand coverage to include even more of TripleO. Thank you! ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
