Hey, I agree with Dmitry that this spec has a huge scope. If you resubmitted one with only the power interface, that could be considered for an exception.
A few specific reasons: 1) Auto-enrollment -- should probably be held off at the moment - This is something that was talked about extensively at mid-cycle meetup and will be a topic of much debate in Ironic for Kilo. Whatever comes out of that debate, if it ends up being considered within scope, would be what your spec would want to integrate with. - I'd suggest you come in IRC, say hello, and work with us as we go into kilo figuring out if auto-enrollment belongs in Ironic and if so, how your hardware could integrate with that system. 2) Power driver - If you split this out into another spec and resubmitted, it'd be at least a small enough scope to be considered. Just as a note though; Ironic has very specific priorities for Juno, the top of which is getting graduated. This means some new features have fallen aside in favor of graduation requirements. Thanks, Jay ________________________________________ From: Dmitry Tantsur <dtant...@redhat.com> Sent: Thursday, August 07, 2014 4:56 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Ironic] Exceptional approval request for Cisco Driver Blueprint Hi! Didn't read the spec thoroughly, but I'm concerned by it's huge scope. It's actually several specs squashed into one (not too detailed). My vote is splitting it into a chain of specs (at least 3: power driver, discovery, other configurations) and seek exception separately. Actually, I'm +1 on making exception for power driver, but -0 on the others, until I see a separate spec for them. Dmitry. On Thu, 2014-08-07 at 09:30 +0530, GopiKrishna Saripuri wrote: > Hi, > > > I've submitted Ironic Cisco driver blueprint post proposal freeze > date. This driver is critical for Cisco and few customers to test as > part of their private cloud expansion. The driver implementation is > ready along with unit-tests. Will submit the code for review once > blueprint is accepted. > > > The Blueprint review link: https://review.openstack.org/#/c/110217/ > > > Please let me know If its possible to include this in Juno release. > > > > Regards > GopiKrishna S > _______________________________________________ > OpenStack-dev mailing list > OpenStackemail@example.com > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev