As an operator dealing with platforms that do cold migration I would like
to be able to abort and rollback the process.
That would give us a better service quality and availability.
We do have no choices but to use cold migration on some of our remote sites
as they don’t get a unified storage suc
Thanks Tim, pre-emptible instances are definitely of interest too. I'll
be in Vancouver, hope to meet up at some point.
And thanks Mathieu for sharing the code, if we build anything of wider
interest I'll try to get it shared.
Cheers,
Dave
--
** Dave Holland ** Systems Support -- Informatics Sys
Emilien Macchi wrote:
Could we change the title of the slot and actually be a TripleO
Project Update session?
It would have been great to have the onboarding session but I guess we
also have 2 other sessions where we'll have occasions to meet:
TripleO Ops and User feedback and TripleO and Ans
On Wed, May 2, 2018 at 5:19 AM, Jimmy McArthur wrote:
>
> No problem, we have both on the schedule. I moved the Project Update to
> 11-11:20 so you can have a few minutes before the Onboarding starts at
> 11:50.
>
> https://www.openstack.org/summit/vancouver-2018/summit-sched
> ule/global-search?
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
> 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
The baremetal scheduling options were deprecated in Pike [1] and the
ironic_host_manager was deprecated in Queens [2] and is now being
removed [3]. Deployments must use resource classes now for baremetal
scheduling. [4]
The large host subset size value is also no longer needed. [5]
I've gone
What's the state of caching_scheduler which could still be using those configs?
Mathieu
On Wed, May 2, 2018 at 12:25 PM, Matt Riedemann wrote:
> The baremetal scheduling options were deprecated in Pike [1] and the
> ironic_host_manager was deprecated in Queens [2] and is now being removed
> [3].
On 5/2/2018 11:40 AM, Mathieu Gagné wrote:
What's the state of caching_scheduler which could still be using those configs?
The CachingScheduler has been deprecated since Pike [1]. We discussed
the CachingScheduler at the Rocky PTG in Dublin [2] and have a TODO to
write a nova-manage data migr
On Wed, May 2, 2018 at 12:49 PM, Matt Riedemann wrote:
> On 5/2/2018 11:40 AM, Mathieu Gagné wrote:
>>
>> What's the state of caching_scheduler which could still be using those
>> configs?
>
>
> The CachingScheduler has been deprecated since Pike [1]. We discussed the
> CachingScheduler at the Roc
On 5/2/2018 12:00 PM, Mathieu Gagné wrote:
If one can still run CachingScheduler (even if it's deprecated), I
think we shouldn't remove the above options.
As you can end up with a broken setup and IIUC no way to migrate to
placement since migration script has yet to be written.
You're currently
On Wed, May 2, 2018 at 1:39 PM, Matt Riedemann wrote:
>
> I know you're just one case, but I don't know how many people are really
> running the CachingScheduler with ironic either, so it might be rare. It
> would be nice to get other operator input here, like I'm guessing CERN has
> their cells c
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
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 12:39 PM, Matt Riedemann wrote:
FWIW, I think we can also backport the data migration CLI to stable
branches once we have it available so you can do your migration in let's
say Queens before g
FYI, here is the start on the data migration CLI:
https://review.openstack.org/#/c/56588
15 matches
Mail list logo
