Comment 2 for bug 1582702
Revision history for this message
| Belmiro Moreira (moreira-belmiro-email-lists) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Hi Andrey,
at CERN we don't allow users to update resources names,
because our OpenStack it's integrated with several external systems.
So, we block resources updates in the policy.
After creating resources the ec2api tries to update the name
(ex for VMs: i-xxxxxxxx).
At the moment I just commented the update.
Would be acceptable to disable updates with a configuration option?
I'm willing to implement it.