Siamo lieti di annunciare la nostra nuova API chiamata: linode.clone(). Questa API permette di clonare facilmente un Linode esistente in una nuova istanza nel datacenter di propria scelta. Clonerà tutti i profili di configurazione e le immagini del disco presenti sul Linode di origine.
Il metodo ha un limite di cinque cloni contemporanei dallo stesso Linode di origine per proteggere l'infrastruttura Linode. Se si tenta di eseguire un altro clone mentre si raggiunge il limite di concorrenza, il metodo API restituirà un errore di "convalida". Se si desidera eseguire un processo di clonazione su larga scala, il Linode originale può essere clonato cinque volte, quindi una volta terminati i cloni, i Linode clonati possono essere clonati cinque volte in contemporanea e così via. Ciò consente di scalare rapidamente l'infrastruttura da un singolo Linode a centinaia.
Ci auguriamo che questa nuova API e che sia utile per le vostre future implementazioni in Linode Cloud.
-Tim
Commenti (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.