>From the user perspective, splitting off the projects seems to be focussing on >the ease of commit compared to the final user experience. An 'extras' project >without *strong* testing co-ordination with packagers such as SUSE and RedHat >would end up with the consumers of the product facing the integration problems >rather than resolving where they should be, within the OpenStack project >itself.
I am sympathetic to the 'extra' drivers problem such as Hyper-V and powervm, but I do not feel the right solution is to split. As CERN uses the Hyper-V driver (we have a dual KVM/Hyper-V approach), we want that this configuration is certified before it reaches us. Assuming there is a summit session on how to address this, I can arrange a user representation in that session. Tim > -----Original Message----- > From: Dan Smith [mailto:d...@danplanet.com] > Sent: 12 October 2013 18:31 > To: OpenStack Development Mailing List > Subject: Re: [openstack-dev] [Hyper-V] Havana status > > > If the idea is to gate with nova-extra-drivers this could lead to a > > rather painful process to change the virt driver API. When all the > > drivers are in the same tree all of them can be updated at the same > > time as the infrastructure. > > Right, and I think if we split those drivers out, then we do *not* gate on > them for the main tree. It's asymmetric, which means potentially > more trouble for the maintainers of the extra drivers. However, as has been > said, we *want* the drivers in the tree as we have them now. > Being moved out would be something the owners of a driver would choose in > order to achieve a faster pace of development, with the > consequence of having to place catch-up if and when we change the driver API. > > Like I said, I'll be glad to submit patches to the extra tree in unison with > patches to the main tree to make some of the virt API changes > that will be coming soon, which should minimize the troubles. > > I believe Alex has already said that he'd prefer the occasional catch-up > activities over what he's currently experiencing. > > --Dan > > _______________________________________________ > 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
