Hi Torin,
Masakari supports 4 different types of recovery methods at the time of creation
of failover_segment.
1. auto: It will let nova decide on which compute host the instances should be
evacuated.
2. reserved_host: You will first need to add reserved hosts to the failover
segments.
Hello Shyam,
I did not have so much experience with s3curl but it looks like the problem is
caused by client but it seems like the s3token middleware, which is to get
authentication with keystone.
So let us check "What authentication are you using", then check "your exisiting
configuration".
On Sat, May 5, 2018 at 1:53 AM, Eric K wrote:
> Thanks a lot Witold and Thomas!
>
> So it doesn't seem that someone is currently using a keystone token to
> authenticate web hook? Is is simply because most of the use cases had
> involved services which do not use
Akihiro, thank you for your precious help!
Regarding the choice of Neutron as PoC, I'm sorry for not providing much
details when I said "because of its specific data model",
effectively the original mention was "its API exposes things at an
individual table level, requiring the client to
To test whether it's our new patch that causes the problem, I submitted a
dummy patch[1] to trigger CI and the CI failed again. Checking the log of
nova scheduler, it's very strange that the scheduling starts with 0 host at
the beginning.
May 06 09:40:34.358585