我们很高兴地宣布最新的 API 调用：linode.clone()。 通过该 API 调用，您可以轻松地将现有的 Linode 克隆到您选择的数据中心中的新实例。 它将克隆源 Linode 上的所有配置文件和磁盘镜像。
为了保护 Linode 基础架构，该方法限制从同一源 Linode 同时克隆 5 次。 如果您尝试在并发限制内执行另一次克隆，API 将返回 "验证 "错误。 如果您希望执行大规模克隆流程，原始 Linode 可以克隆五次，一旦这些克隆完成，被克隆的 Linode 可以同时各克隆五次，以此类推。 这样，您就可以将基础架构从单个 Linode 快速扩展到数百个。
我们希望您喜欢这个新的 API 调用，并希望它对您今后在 Linode 云中的部署有用。
-蒂姆
评论 (10)
Wow, great!
We’ve been looking for something like this for a while
Are there any pre-requisites for this API Call?
Is the Linode need to be shutdown or will be shutdown during the clone process?
How long would it take to clone? Is it the same thing as if its done from the console?
AWESOME! Been waiting for this for so long, at least now we can script our scaling activities!
Can we get one for checking the amount of bandwidth/transfer used for the current month next? (To compare against the existing call for finding the quota.)
@Dash
> Is the Linode need to be shutdown or will be shutdown during the clone process?
https://www.linode.com/api/linode/linode.clone —
“It is recommended that the source Linode be powered down during the clone.”
The source Linode doesn’t have to be powered down, but it is recommended to ensure that a consistent copy of your data is cloned.
> How long would it take to clone? Is it the same thing as if its done from the console?
1-2 minutes per GB of data within the same datacenter of the source Linode (the Linode you’re cloning from), or 5-10 minutes per GB of data if migrating to a different datacenter.
I assume that you should not .clone() a Linode that has static networking set up, since the static confi will render the new node unreachable… or am I missing something?
Xof:
You could still clone the Linode, but you’d need to use LISH to log in to the new Linode and adjust the networking configuration to the new IP address(es).
Tony Yarusso:
There isn’t currently a way to see how much transfer a particular Linode has used that I can see, but account.info() shows transfer pool amount and usage:
https://www.linode.com/api/utility/account.info
How would you suggest auto scaling in an HA environment where you want to clone and configure network addresses all in one go?
The limitation of 5 clones per source linode seems very arbitrary – you’re just offloading additional work to the side of the script doing the cloning. You might think we’re going to keep track of the clone count on our own, but the truth is we’re just going to iterate over existing linodes until the clone() call returns without an error.
What difference could it possibly make on your end whether we clone a single linode 10 times versus cloning an initial linode 5 times, and then cloning the first clone 5 additional times? There should be no difference in your ability to “protect Linode infrastructure”..?
Xof brought up a good question regarding the static networking setup causing new node unreachable. May I know what is the best solution for that in Linode? Doug’s suggestion to login using LISH and change it manually doesn’t make sense to me, as it defeats the purpose of autoscaling.