-
Notifications
You must be signed in to change notification settings - Fork 292
Mux mirror failure check for SXM #6439
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mux mirror failure check for SXM #6439
Conversation
eef608a
to
71299b4
Compare
Not sure what's going on with the CI... I can't seem to get it to rerun. |
a5fb4ea
to
71299b4
Compare
|
71299b4
to
c973256
Compare
The current logic in storage_migrate.ml for mirror failure check is specific to tapdisk, hence multiplex it. `pre_deactivate_hook` also has something similar to check for mirror failure, so do something similar there. Signed-off-by: Vincent Liu <shuntian.liu2@cloud.com>
Previously this was deleted in commit 1fe6389 as it was not multiplexed, but looks like we still need to keep it in storage_mux because sm-cli needs to make rpc calls to storage_mux when trying to list all the mirrors to make it work properly, due to the fact that the sr plugins are stored in the address space of the xapi process. There are other invocations in sm-cli such as `Storage_migrate.start` which may have similar problems. But I have left them alone as I don't any reasonable way of calling them from the cli. Signed-off-by: Vincent Liu <shuntian.liu2@cloud.com>
Do the same as DATA.MIRROR.list Signed-off-by: Vincent Liu <shuntian.liu2@cloud.com>
ea94a18
to
6de97ce
Compare
) | ||
with | ||
| Timeout elapsed -> | ||
D.error |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need identifying information here like a VM to make this more useful?
s.failed <- true | ||
| e -> | ||
D.error | ||
"Caught exception while finally checking mirror state: %s" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similar here?
Signed-off-by: Vincent Liu <shuntian.liu2@cloud.com>
6de97ce
to
bb994e0
Compare
This is a continuation of #6439 in the effort of implementing outbound SXM for SMAPIv3. We have reached the climatic point of this and can actually now implement the logic to do outbound SXM for SMAPIv3 SRs! This is a rather large PR and I expect it to take some time to be reviewed and merged, so I am opening this early to gather some feedback. Since #6439 is not yet merged and this PR depends on that one, I am marking this one as a draft, while reviewing please ignore the first three commit in this PR and look at #6439 first instead. I will update this one again when #6439 is merged There is also a couple of docs PR at the end documenting the design and approach taken in doing SMAPIv3 migration. In terms of testing plan, the important thing is to make sure for now that this is not regressing the SMAPIv1 migration. For that I will be using the SXM functional tests suite. I will also be using more tests to actually test the SMAPIv3 SXM feature.
Continuation of #6434, more mutiplexing for SXM, this time the mirror status checking logic.
No functional change.
More to come...