There is a big difference between DocImpact (i.e. needing some improvements to the doc) and putting the migration effort onto the users without automation to help... as I have said previously, while this (and others like it) may be a worthwhile change in isolation, making the upgrade process more difficult needs to be balanced with the technical benefits of the change. These questions need to be part of the review approval.
Tim > -----Original Message----- > From: Pádraig Brady [mailto:[email protected]] > Sent: 30 December 2013 14:00 > To: OpenStack Development Mailing List (not for usage questions); Day, Phil > Subject: Re: [openstack-dev] [nova] - Revert change of default ephemeral fs > to ext4 > ... > To be most general and avoid this consistency issue, I suppose we could > change the name format for these cached CoW base images from > ephemeral_10_default, ephemeral_20_linux etc. > to 'ephemeral_20_' + md5(mkfs_command)[:7] That would impose a performance > hit at first boot with this new logic, and we'd have to > double check that the cache cleaning logic would handle removing unused older > format images. > Alternatively we might just document this issue and put the onus on users to > clean these cached ephemeral disk on upgrade (the commit > is already tagged as DocImpact). > > thanks, > Pádraig. > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
