Change of ownership of resources
Bug #1792459 reported by
Tobias Rydberg
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Public Cloud WG |
New
|
Critical
|
Tobias Rydberg | ||
Bug Description
As a public cloud operator we often get the question of changing the ownership of resources, especially VMs. With that said, changing ownership of a VM is of course possible today, with snapshot. End users does not seam very happy with that answer, and they would like to have a more "cloudy way" of doing that. So, seamlessly moving resources would be the preferable option. And that doesn't only apply for VMs, full heat stacks and its resources is on the table.
Also preferable is some kind invite/approve process.
Revision history for this message
| Dan Smith (danms) wrote | #1 |
To post a comment you must log in.
In the public cloud operators session in Denver 2018, we discussed the potential for at least coalescing the direct-to-database ownership transfer operations into a single place where we could collaborate on the safest possible option.
I have put together what may be the start of that, which is a tool aiming to import and use the object and data modeling from the actual projects to do the transfer process. For Nova, this just manipulates the data directly, and for Cinder it automates the use of the existing transfer API but with a sort of "auto confirm/accept" of the transfer by the target project.
This is literally just a few hours of work while being distracted at PTG, but it trivially works for me in devstack. If people could test it (with due care) that would be great, and if it's reasonably useful I can see importing it as an openstack project so that collaboration is easier.
https:/