-1 My concerns are the following: 1. This feature is of a High priority, not Essential [1] 2. We already had to give exception for flexible networking CLI part [2], as it is essential one. So basically that means we have a conflict of focus for SMEs in the area. 3. Just by working on this, we don't spend time on bugs. Which increases risk of delivering on time with expected level of quality
+390, -35 LOC also scare me a little bit, it's not a tiny change. One of the possible workarounds can be, if we deliver this patch after HCF, and have an updated package of client. If someone want it in experimental mode, then the one could update client package and have this functionality. If you convince me though that it can be finished by end of the week with only code reviews from SMEs (and only after flexible networking part is done), only after it I can change my mind. [1] https://blueprints.launchpad.net/fuel/+spec/node-custom-attributes [2] https://review.openstack.org/#/c/204321/ On Thu, Jul 23, 2015 at 10:53 AM Sebastian Kalinowski < skalinow...@mirantis.com> wrote: > +1 for this FFE as it's important to have this functionality covered in CLI > > 2015-07-23 19:46 GMT+02:00 Igor Kalnitsky <ikalnit...@mirantis.com>: > >> Hi Julia, >> >> I'm ok with FF exception for CLI part. I don't think it can somehow >> decrease product quality, so as a core I'll help to land it. >> >> Thanks, >> Igor >> >> On Thu, Jul 23, 2015 at 7:50 PM, Julia Aranovich >> <jkirnos...@mirantis.com> wrote: >> > Team, >> > >> > I would like to request an exception from the Feature Freeze for CLI >> changes >> > of working with custom node labels added to fuelclient (fuel2) [1]. UI >> and >> > Nailgun parts of the story are already merged [2]. >> > >> > There CLI request is being actively reviewed, the base flow is accepted. >> > There are minimal risks here since the changes added to fuel2 version. >> > >> > Please, respond if you have any questions or concerns related to this >> > request. >> > >> > Thanks in advance, >> > Julia >> > >> > [1] https://review.openstack.org/#/c/204524/ >> > [2] https://review.openstack.org/#/c/201472/ >> > >> > >> __________________________________________________________________________ >> > 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 >> > > __________________________________________________________________________ > 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 > -- 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
