메인 콘텐츠로 건너뛰기
블로그 리노드 (주)linode.클론 () API 외침

linode.클론 () API 외침

1

우리는 우리의 최신 을 발표하게 된 것을 기쁘게 생각합니다. API 전화: linode.클론().  이 API 호출을 사용하면 기존 Linode를 선택한 데이터 센터의 새 인스턴스로 쉽게 복제할 수 있습니다.  소스 Linode에 있는 모든 구성 프로파일 및 디스크 이미지를 복제합니다.

이 메서드는 Linode 인프라를 보호하기 위해 동일한 소스 Linode에서 5개의 동시 클론의 제한이 있습니다.  동시성 한도에서 다른 복제본을 실행하려고 하면 API "유효성 검사" 오류로 반환됩니다.  대규모 클론 프로세스를 실행하려는 경우 원래 Linode를 5번 복제한 다음 복제된 리노드가 각각 5회 동시에 복제될 수 있습니다.  이렇게 하면 인프라를 단일 리노드에서 수백 개의 리노드로 빠르게 확장할 수 있습니다.

우리는 당신이 이 새로운 것을 즐기기를 바랍니다. API 리노드 클라우드에서 향후 배포에 유용합니다.

- 팀


댓글 (10)

  1. Author Photo

    Wow, great!

    We’ve been looking for something like this for a while

  2. Author Photo

    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?

  3. Author Photo

    AWESOME! Been waiting for this for so long, at least now we can script our scaling activities!

  4. Author Photo

    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.)

  5. Author Photo

    @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.

  6. Author Photo

    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?

  7. Author Photo

    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

  8. Author Photo

    How would you suggest auto scaling in an HA environment where you want to clone and configure network addresses all in one go?

  9. Author Photo

    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”..?

  10. Author Photo

    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.

댓글 남기기

이메일 주소는 게시되지 않습니다. 필수 필드가 표시됩니다 *