Hi Andrian, this is High priority blueprint [1] for 7.0 timeframe. It seems we still didn't merge the main part [2], and need FF exception for additional stuff.
The question is about quality. If we focus on enhancements, then we don't focus on bugs. Which whether means to deliver work with lower quality of slip the release. My opinion is rather don't give FF exception in this case, and don't have Ceilometer support for this new feature. [1] https://blueprints.launchpad.net/fuel/+spec/compute-vmware-role [2] https://review.openstack.org/#/c/196114/ On Thu, Jul 23, 2015 at 1:39 PM Andrian Noga <an...@mirantis.com> wrote: > Hi, > > The patch patch for fuel-library > <https://review.openstack.org/#/c/196114/> that implements > 'compute-vwmare' role (https://mirantis.jira.com/browse/PROD-627) requires > additional work to do (ceilometer support.), but as far as I can see it > doesn't affect any other parts of the product. > > We plan to implement it in 3 working days (2 for implementation, 1 day > for writing system test and test runs), it should not be hard since we > already support ceilometer compute agent deployment on controller nodes. > > We need 1 DevOps engineer and 1 QA engineer to be engaged for this work. > > So I think it's ok to accept this feature as an exception for feature > freeze. > > Regards, > Andrian Noga > Project manager > Partner Centric Engineering > Mirantis, Inc > > Mob.phone: +38 (063) 966-21-24 > > Email: an...@mirantis.com > Skype: bigfoot_ua > -- Mike Scherbakov #mihgen
__________________________________________________________________________ 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
