2 июня 2016 г. 10:19 PM пользователь "Loo, Ruby" <ruby....@intel.com> написал: > > Hi, > > I recently reviewed a patch [1] that is trying to address an issue with ironic (master) talking to a ramdisk that has a mitaka IPA lurking around. > > It made me think that IPA may no longer be a teenager (yay, boo). IPA now has a stable branch. I think it is time it grows up and acts responsibly. Ironic needs to know which era of IPA it is talking to. Or conversely, does ironic want to specify which microversion of IPA it wants to use? (Sorry, Dmitry, I realize you are cringing.)
With versioning in place we'll have to fix one IPA version in ironic. Meaning, as soon as we introduce a new feature, we have to explicitly break compatibility with old ramdisk by requesting a version it does not support. Even if the feature itself is optional. Or we have to wait some long time before using new IPA features in ironic. I hate both options. Well, or we can use some different versioning procedure :) > > Has anyone thought more than I have about this (i.e., more than 2ish minutes)? > > If the solution (whatever it is) is going to take a long time to implement, is there anything we can do in the short term (ie, in this cycle)? > > --ruby > > [1] https://review.openstack.org/#/c/319183/ > > > > __________________________________________________________________________ > 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
