Open Stack

On Nov 17, 2014, at 3:46 PM, Amit Gandhi <amit.gandhi at rackspace.com> wrote:
> 
> I can see where this makes a lot of sense in API¹s such as Nova¹s where
> flavors represent some combination of memory, disk, and cpu performance.

For Nova, flavors emerged more as a billing convenience than anything technical regarding creating a VM with certain characteristics.

> In the case of CDN, the flavor represents a list of CDN providers.
> 
> So... you could have a flavor representing a region of the world
> (America¹s) consisting of one or more CDN providers with a strong presence
> in those regions.
> Or a flavor could represent performance or features offered (number of
> edge nodes, speed, etc).  And it is up to the operator to define those
> flavors and assign one or more appropriate CDN providers to those flavors.

Again, this seems like the sort of packaging you would need to charge customers for different levels of service, and not something that you would need to make a working CDN API.


-- Ed Leafe





-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141117/1d889cef/attachment.pgp>