On Tue, Mar 10, 2015 at 12:08 PM, Doug Wiegley <doug...@parksidesoftware.com > wrote:
> Hi all, > > LBaaS v2 is going out in Kilo, and we have quite a few vendor drivers > ready to merge, but most are waiting for the tempest tests/job to be done > before they can satisfy their third-party CI requirements. Because that > job is likely to be done so close to FF for Kilo, I am proposing that we > begin merging vendor drivers for lbaas v2 with the following guidelines: > > - There must be a CI from that vendor posting in the neutron-lbaas repo, > running either the v1 tempest suite, or installing devstack/v2 and exiting. > - The CI *must* start running the lbaas v2 tempest jobs within 1 week of > the openstack lbaasv2 job merging and voting in the neutron-lbaas gate. > > I expect that vendor CIs can start modeling their jobs after the > experimental tempest job [1] within the next few days (depends on how long > the experimental queue takes to run a few times.) > > Ack on this plan, it all sounds good to me Doug! Kyle > Thanks, > doug > > [1] https://review.openstack.org/#/c/161432/ > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
