Skip to content
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

[Migration] Adjust most scenarios with --p2p --tunnelled migration #1678

Open
dzhengfy opened this issue Jun 15, 2018 · 3 comments
Open

[Migration] Adjust most scenarios with --p2p --tunnelled migration #1678

dzhengfy opened this issue Jun 15, 2018 · 3 comments
Labels
migration migration feature

Comments

@dzhengfy
Copy link
Contributor

There is a requirement that --p2p --tunnelled migration has higher priority. So we plan add the two options to existing cases as much as possible.

@chunfuwen chunfuwen added the migration migration feature label Jun 15, 2018
@balamuruhans
Copy link
Member

@dzhengfy this scenario is available in virsh.migrate, can we use the same or is there different thoughts on it ?

- there_p2p:
# Uni-direction migration with option --p2p.
virsh_migrate_options = "--live --p2p"
- there_p2p_tunnelled:
# Uni-direction migration with option --tunnelled.
# --tunnelled should be used with --p2p.
virsh_migrate_options = "--live --p2p --tunnelled"

@dzhengfy
Copy link
Contributor Author

dzhengfy commented Jun 20, 2018

@balamuruhans , the purpose is to add '--p2p --tunnelled' to much more existing scenarios. Most existing scenarios should be able to work with this two options, however we need adjust some of them if need.

@balamuruhans
Copy link
Member

@dzhengfy Agree with you. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
migration migration feature
Projects
None yet
Development

No branches or pull requests

3 participants