How can I transfer a droplet between the teams?

September 27, 2016 11.1k views
System Tools Deployment DigitalOcean Ubuntu 16.04

How can I transfer a droplet between the teams within the same accounts without change of IP address?

1 comment
  • All of the above plus:

    I have a droplet (personal account) and my dev partner has another droplet (also personal account) in the same datacenter.

    What I'd like is to create a team and move my droplet and his droplet to this team without changing IPs or other hassle, it should be straightforward from the admin panel to move droplets between accounts/teams.

    Is this going to be supported anytime soon or we have to change configs all over the place and put the machines down for hours?

12 Answers

I need to invoice different clients for different droplets. Currently I have all my droplets under my account, I've set up a team for each of my clients but then find out that there is no way to move droplets between teams. This is a problem, it should be possible to do this so that the droplets can be grouped into different invoices. I know I can recreate a droplet from a snapshot, but it's not smooth, result in changed IPs etc..

I agree that this would be a very nice feature. Like others have mentioned, I have a server on my account for a client that I would like to transfer to a team for individualized billing. Setting up a new server with a new IP would require a lot of updates for various implementations.

Hi,

What I need is to selectively transfer some Droplets to a Team.
Actually, I also need to transfer some Domains, Volumes, Snapshots, etc..
When I created the team, the only option available is transfer EVERYTHING, which is not an option for me, as my account runs several non-Team resources.

Do you plan on supporting or working on something like this?
Selective transfer of some resources like Droplets, Domains, Floating IPs, etc. to another Team?
I won't mind even if this is a manual process and I need to submit a support ticket.

Thanks!

  • Precisely the predicament I currently find myself in - there were some personal droplets in my mix which I preferred were not associated with my group entity in any way. Looking back, I now am thinking I might be better off having made a concession on my preference and just porting everything over en masse.

I completely agree. I was hoping to split up all the droplets I had to teams related to different clients. The way it works now is nice for new clients, but shame we can't use it with our old clients. Snapshotting and killing just isn't an option with the downtime or branching data that will create.

  • Agree. With eCommerce clients - or really anything involving money or sensitive data - this just isn't good enough.

Same for me, I have to group my droplets under individual teams in order to get separate invoices. I need to pass the invoices on, and each client should pay for only their droplets. Please make it possibme to transfer between teams without the hassle of rebuilding from a snapshot and getting new IP (I can live with getting a new IP is I must), but don't like to have to destroy and recreate each droplet.

Another option could be to simply allow for droplets to be grouped under tags or folders, and then have the option to group these into individual invoices. The invoicing issue is probably often the reason people need teams, more than the actual authentication thing, so this could solve it for those that just needs to separate invoices.

I recently created a team and now I wish to transfer several droplets into the team as different teams need to have different access levels.

I think the key takeaway to consider is:

Given that a team's roles are dynamic and can change overtime, shouldn't droplets be able to change teams as well?

A lot of brilliant use cases have already been presented above.

I think that in order for permission systems to be effective, a group within a system needs the ability to be flexible as to a.) it's members and b.) it's assets.

I think the DO team got the members part down pat and it would be really nice to have the assets (droplets) part in place as well.

If I were to take UNIX file permissions as an example, it's great that I can add/remove users from groups and edit permissions per group but I think it would be very tedious if I'd have to recreate a file just to change it's group.

Nonetheless, thank you DO team and love your excellent platform!

Hello,

It is not possible to transfer a droplet between teams or accounts. You can take a snapshot and transfer it between teams and accounts, but you would get a new IP.

--Andrew

  • This would definitely be an issue for sites with no-to-near-zero downtime contractual obligations, or for anyone with slightly more complex network infrastructures relying on a static IP address. It would be great if those use cases were considered as well.

This would be extremely valuable for us as well, especially in the case of spaces

+1 for this feature. I tried to do something like this thinking it would be available so I searched for it but realized it is not an option yet, sounds very intuitive to me.

This definitely would be an awesome functionality. I was like "Digital Ocean is AMAZING!" and then after my next click I was like "Awwwww...." - wish this was a feature; it would be super helpful.

  • But you guys really are still amazing ;) Groups are just currently useless for my existing droplets.

Yeah, I just opened a ticket for this as I thought it was a bug, but it is a feature that is lacking it seems. I have three droplets I wanted to move from my personal account to a new team and I cannot do that. Only option I had but realized to late is convert existing account to team and move all droplets there.. But that would not have helped as I had one droplet that does not belong in this new team anyways. Do hope this becomes possible soon!

Have another answer? Share your knowledge.