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 > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
