To reiterate the Juno release plan from: https://wiki.openstack.org/wiki/Juno_Release_Schedule Feature freeze is at: 21st August.
I am listing tasks which we should consider to be done for Juno and who should handle them. The following might be considered as critical path to get anything for Juno: 1. LBaaS Plugin, API, DB - when is a code commit expected? 2. CLI 3. LBaaS Driver Interfaces - done - https://review.openstack.org/#/c/100690/ 4. Connecting the Plugin calls to the drive - I have not seen any reference to this. I think we should use the "provider" capabilities until "flavor" gets implemented. Is this addressed by item 1 above or does it required an additional task? 5. HA proxy reference implementation - when is a code commit expected? 6. Tempest Tests Additional "Core" features 1. Horizon UI 2. Quota update/fix 3. API Compatibility a. Connecting the "OLD API Plugin calls to "old/new" drivers. Is this still planned? 4. Driver Compatibility a. Connecting the Plugin calls to "old" drivers. Is this still planned? In addition/parallel 1. TLS - a. BP is approved. b. WIP code was committed and waiting for the code of the basic API/model to be available for start of review. c. HA Proxy reference implementation d. CLI e. Horizon Support f. Tempest Tests 2. L7 context switching a. BP in review b. WIP code in progress and waiting for the code of the basic API/model to be available for initial commit c. HA Proxy reference implementation d. CLI e. Horizon Support f. Tempest Tests Anything else? Regards, -Sam.
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
