openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #17194
Re: Compute API behavior
Agreed - the resources used to create a server should be copied into the
server's data if those resources can be deleted (or even modified
independently of the servers using them).
thanks
-Doug
________________________________________________________
STSM | Standards Architect | IBM Software Group
(919) 254-6905 | IBM 444-6905 | dug@xxxxxxxxxx
The more I'm around some people, the more I like my dog.
From: Luis Gervaso <luis@xxxxxxxxx>
To: openstack@xxxxxxxxxxxxxxxxxxx,
Date: 10/04/2012 10:10 AM
Subject: [Openstack] Compute API behavior
Sent by: openstack-bounces+dug=us.ibm.com@xxxxxxxxxxxxxxxxxxx
Hi,
I have found an use case which breaks the compute api. May be I'm not doing
the stuff in the right way. Anyway I want to share with you.
1. Supose I create a server with an image and flavor.
2. Then I delete the image or flavor.
3. Now, when I list the server the image/flavor associated with the server
is not found (actually the api returns a link to image/flavor that no
longer exists)
I think the link is not the correct way to store these info of a server.
The links (following HATEOAS) should be for actions performed on a server:
let's say reboot, pause, show console and so on ...
Cheers!
--
-------------------------------------------
Luis Alberto Gervaso Martin
Woorea Solutions, S.L
CEO & CTO
mobile: (+34) 627983344
luis@xxxxxxxxx
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
References