DO Ideas 2

transfer droplet ownership

i would like to be able to transfer a droplet as is (completely with IP address and RUNNING) from an account to another. this has nothing to do with droplet properties and it should be a simple change in database (for droplet_id change owner_id from user_X to user_Y or something like this).

from the interface point of view, it can be handled in a similar way with snapshot transfer, with one user offering and another user accepting the transfer

this is useful for billing purposes.

  • vang
  • Sep 11 2018
  • Attach files
  • Mato SUstak commented
    September 11, 2018 16:50

    Yes, this would be amazing!! I really need this to not cause service downtime while transfering droplets to another accounts.

  • The-any-Key commented
    September 11, 2018 16:50

    I would really need this. Sometimes you setup a droplet and a client want it in his own account. It would be great to have this feature.

  • Anonymous commented
    September 11, 2018 16:50

    I have the exact same issue as Christopher Wright and many others by the look of it :)

  • Christopher Wright commented
    September 11, 2018 16:50

    I have an account with a personal droplet and a business droplet. I created a team for the business and I would love to transfer the business droplet to the team for billing purposes.

  • Peter Knowles commented
    September 11, 2018 16:50

    I agree that transferring ownership should be possible. Similar to adding someone to a team, the current owner should initialize the transfer by entering email of recipient. Then the recipient upon accepting should become the owner.

  • John commented
    September 11, 2018 16:50

    The current way of transferring droplets using snapshots does not really work with configured email servers. For email servers to work properly they need to be running on a stable IP address to gain "reputation" among other bigger email providers like GMail. Without a good reputation the email sent with the server will be spam flagged for up to a month.

    If I transfer an email server to a client and their emails start getting spam flagged for a month due to the IP changing then it is a big problem for the client and they will loose business.

  • Anonymous commented
    September 11, 2018 16:50

    Not sure why this is still just an idea...

  • Yoandro Gonzalez commented
    September 11, 2018 16:50

    For those of us managing multiple projects and organizing teams, it would be extremely useful to have droplet ownership transfers available.

  • Mathias Baer commented
    September 11, 2018 16:50

    How many votes do we need to have this feature?

  • Michael Sullivan commented
    September 11, 2018 16:50

    Snapshot transfer is really great and relatively painless. However, there is a tiny bit of downtime and it requires changes to DNS. It would be great to be able to just transfer the actual droplet. I disagree that it doesn't add value to the transfer process. This would remove any possibility of human error from the process in terms of backing up and restoring or changing DNS.

  • Georgi commented
    September 11, 2018 16:50

    Guys, I don't want to sounds demanding, but we uses biggest plans on DO and we pay big money for hosting busy websites. This is a serious things that needs to be implemented ASAP, as the cost of stopping and moving these huge sites is enormous. The clients are not happy, therefore we are into a trouble. Also, the new Team functionality you implemented is very basic, as the only thing we can do is to provide the same full access login just with another email.... We should be able to assign roles with permissions/droplets.

  • Ted Wood commented
    September 11, 2018 16:50

    Yes, due to the flaw, incomplete Teams implementation, I'm faced with having to move a droplet for a client to a separate DO account so that I can grant access to managing the droplet to the client (their request). However, there's no way to do this.... we must shut down the droplet, take a snapshot, transfer the snapshot to the new account, create a new droplet from that snapshot, and then update the DNS settings.

    I haven't yet tried, but I wonder how does the DNS system handles the same zone being set up in two different DO accounts? Hmmm.

  • Anonymous commented
    September 11, 2018 16:50

    How to boot clash of clans

  • Anonymous commented
    September 11, 2018 16:50

    It should be a very high priority! Why have downtime at all, when the process of switching ownership is a very simple one?

    As ben said, it saves a few minutes... Rated at an average of $7,900 per minute, it saves a lot of money... Why would I want to lose money on digitalocean when rackspace seems to have a better grip of things.

    P.S. I did not make up the $7,900 - http://www.datacenterdynamics.com/critical-environment/one-minute-of-data-center-downtime-costs-us7900-on-average/83956.fullarticle

  • vang commented
    September 11, 2018 16:50

    reasons for droplet transfer instead of snapshot transfer:
    - users may really need it. for example if you run a DNS server with hundreds of domains served, it may be complicated if you change it's main IP address
    - it should be trivial easy to implement it (if the database system is sanely implemented)
    - the snapshot transfer is just a transfer of files. it can be done with other tools (make an archive, unpack it on a pristine droplet etc). the running droplet transfer (keeping all the droplet properties) cannot be done otherwise. frankly i even don't understand why they implemented snapshot transfer...
    - if you are a consultant working for non-tech customers, it is really confortable for them to buy a particular service, tested and running "as is" (the droplet transfer) instead of a bunch of files which has to be configures/installed/etc (the snapshot transfer or archive or anything else).

  • ben commented
    September 11, 2018 16:50

    So you want to be able to transfer droplets while they're running, instead of having to shut them down, make a snapshot, and transfer that snapshot?

    I'll say that it would certainly be handy, but I don't think this should be a high priority at all. It saves a few minutes but doesn't add value to the transfer process.

  • vang commented
    September 11, 2018 16:50

    Hello DigitalOcean,

    Do you think top 2 in the "hot ideeas" maybe deserves at least an answer?

    As an incentive for you, here is how Rackspace is handling this sort of problem: if both customers, one yielding and one accepting a particular service, are sending tickets to support, they just change the ownership for that particular service. They did not automate the process but at least they have a procedure for doing it, at customers request.