m>>
Cc: Openstack
mailto:openstack@lists.launchpad.net>>
Subject: Re: [Openstack] Thinking about Openstack Volume API
Hey Vish,
Yes, we have been thinking about that a bit. The current idea is to have
volume types, and depending on the type, it would expect a certain amount of
data f
Hey Vish,
Yes, we have been thinking about that a bit. The current idea is to have
volume types, and depending on the type, it would expect a certain amount of
data for that type. The scheduler would then map that type and
corresponding data to provision the right type of storage.
--
Chuck
On
This all seems reasonable to me. Do you have a concept of how you will expose
different SLAs within the deployment. Is it metadata on the volume that and
handled by the scheduler? Or will different SLAs be at separate endpoints?
In other words am i creating a volume with a PUT
/provider.com/
One of the first steps needed to help decouple volumes from Nova, is to
define what the Openstack Volume API should look like. I would like to
start
by discussing the main api endpoints, and discussing the interaction of
compute attaching/detaching from volumes.
All of the following endpoints wil
4 matches
Mail list logo
