Hi Alex, I don't see the tripleo ovs hardware offload feature. The spec was merge into queens [1], but for some reason the blueprint is not in approve state [2].
I has only 3 patches left: 1. https://review.openstack.org/#/c/507401/ has 2 +2 2. https://review.openstack.org/#/c/507100/ has 1 +2 3. https://review.openstack.org/#/c/518715/ I would appreciated if we can land all the patches to queens release. [1] - https://review.openstack.org/#/c/502313/ [2] - https://blueprints.launchpad.net/tripleo/+spec/tripleo-ovs-hw-offload > -----Original Message----- > From: Alex Schultz [mailto:aschu...@redhat.com] > Sent: Saturday, December 9, 2017 1:34 AM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: [openstack-dev] [tripleo] Blueprints moved out to Rocky > > Hey folks, > > So I went through the list of blueprints and moved some that were either not > updated or appeared to have a bunch of patches not in a mergable state. > > Please take some time to review the list of blueprints currently associated > with Rocky[0] to see if your efforts have been moved. If you believe you're > close to implementing the feature in the next week or two, let me know and > we can move it back into Queens. If you think it will take an extended period > of time (more than 2 weeks) to land but we need it in Queens, please submit > an FFE. > > If you have an blueprint that is currently not in implemented in Queens[1], > please make sure to update the blueprint status if possible. For the ones I > left in due to the patches being in a decent state, please make sure those get > merged in the next few weeks or we will need to push them out to Rocky. > > Thanks, > -Alex > > > [0] > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblu > eprints.launchpad.net%2Ftripleo%2Frocky&data=02%7C01%7Cmoshele%40 > mellanox.com%7C0abe7d8deef74a13d29508d53e945633%7Ca652971c7d2e4d > 9ba6a4d149256f461b%7C0%7C0%7C636483729194465277&sdata=xDwvHSmx > niqu6HN5FaQB2DTc6N8mRS879Ku1y4FDLss%3D&reserved=0 > [1] > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblu > eprints.launchpad.net%2Ftripleo%2Fqueens&data=02%7C01%7Cmoshele%4 > 0mellanox.com%7C0abe7d8deef74a13d29508d53e945633%7Ca652971c7d2e4 > d9ba6a4d149256f461b%7C0%7C0%7C636483729194465277&sdata=v6v1yDjt1f > dc3FAILGsS2voCiMUmaLQGPwwxNtTzcso%3D&reserved=0 > > __________________________________________________________ > ________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev- > requ...@lists.openstack.org?subject:unsubscribe > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists. > openstack.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fopenstack- > dev&data=02%7C01%7Cmoshele%40mellanox.com%7C0abe7d8deef74a13d2 > 9508d53e945633%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636 > 483729194465277&sdata=N%2B78nm8bMlSWsASO6uIX2mJlO1%2BX9VfTM2 > A3qUu6GUk%3D&reserved=0 __________________________________________________________________________ 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
