Isnt this an existing issue with traits specified in flavor as well?
Server is created using flavor1 requiring trait A on RP1. Before the
rebuild is called, the underlying RP1 can be updated to remove trait A and
when a rebuild is requested(regardless of whether the image is updated or
not), we sk
On 5/2/2018 5:39 PM, Jay Pipes wrote:
My personal preference is to add less technical debt and go with a
solution that checks if image traits have changed in nova-api and if so,
simply refuse to perform a rebuild.
So, what if when I created my server, the image I used, let's say
image1, had r
> What if the API compares the original image required traits against the
new image required traits, and if the new image has required traits which
weren't in the original image, then (punt) fail in the API? Then you would
at least have a chance > to rebuild with a new image that has required
trai
On 5/1/2018 5:26 PM, Arvind N wrote:
In cases of rebuilding of an instance using a different image where the
image traits have changed between the original launch and the rebuild,
is it reasonable to ask to just re-launch a new instance with the new image?
The argument for this approach is tha
Reminder for Operators, Please provide feedback either way.
In cases of rebuilding of an instance using a different image where the
image traits have changed between the original launch and the rebuild, is
it reasonable to ask to just re-launch a new instance with the new image?
The argument for
Sorry folks for the late reply, I'll try to also weigh in the Gerrit change.
On Tue, Apr 24, 2018 at 2:55 PM, Jay Pipes wrote:
> On 04/23/2018 05:51 PM, Arvind N wrote:
>
>> Thanks for the detailed options Matt/eric/jay.
>>
>> Just few of my thoughts,
>>
>> For #1, we can make the explanation ve
