We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
假设场景,从A环境导出作业到B环境, 导出的作业在A环境中,目标主机关键信息:hostId=1,ip=xx.xx.xx.10,cloudId=0 在B环境中,也有hostId=1的主机信息:hostId=1,ip=xx.xx.xx.100,cloudId=2 如果把A环境作业导入到B环境,该作业导入到B环境后,目标主机信息就是hostId=1,ip=xx.xx.xx.100,cloudId=2,对用户来说,虽然在A环境、B环境都存在一样的hostId,即使它是唯一,但是在不同的环境代表不同的信息,这里用户期望的目标主机不是xx.xx.xx.100,而是期望无效。
hostId=1,ip=xx.xx.xx.10,cloudId=0
hostId=1,ip=xx.xx.xx.100,cloudId=2
因此,在导入作业时,校验目标环境hostId存在的同时,也校验云区域+IP是否匹配,如果不匹配则认为该主机无效,是不是比较合理
The text was updated successfully, but these errors were encountered:
wangyu096
liuliaozhong
No branches or pull requests
假设场景,从A环境导出作业到B环境,
导出的作业在A环境中,目标主机关键信息:
hostId=1,ip=xx.xx.xx.10,cloudId=0
在B环境中,也有hostId=1的主机信息:
hostId=1,ip=xx.xx.xx.100,cloudId=2
如果把A环境作业导入到B环境,该作业导入到B环境后,目标主机信息就是
hostId=1,ip=xx.xx.xx.100,cloudId=2
,对用户来说,虽然在A环境、B环境都存在一样的hostId,即使它是唯一,但是在不同的环境代表不同的信息,这里用户期望的目标主机不是xx.xx.xx.100,而是期望无效。因此,在导入作业时,校验目标环境hostId存在的同时,也校验云区域+IP是否匹配,如果不匹配则认为该主机无效,是不是比较合理
The text was updated successfully, but these errors were encountered: