Difference between revisions of "Poppy"
Amit Gandhi (talk | contribs) (→Primary Mission) |
Amit Gandhi (talk | contribs) (→CDN Providers) |
||
Line 89: | Line 89: | ||
* [http://aws.amazon.com/cloudfront/ Amazon CloudFront] (under development) | * [http://aws.amazon.com/cloudfront/ Amazon CloudFront] (under development) | ||
* [https://developer.akamai.com/api Akamai] (coming soon) | * [https://developer.akamai.com/api Akamai] (coming soon) | ||
+ | * [http://www.edgecast.com Edgecast] (coming soon) | ||
* Insert Your CDN Here !!! | * Insert Your CDN Here !!! |
Revision as of 19:06, 17 October 2014
Contents
Summary
An OpenStack-related Stackforge project designed to make CDN services easier to consume with a generic vendor-neutral API.
Overview
Poppy provides CDNaaS for OpenStack:
- REST API for CDN service provisioning
- Multi-tenant
- Integrated with Keystone for Authentication
- Integrated with Designate for dynamic CNAMEing
- Support for CDN providers (Fastly, MaxCDN, CloudFront, Akamai, Edgecast)
OpenStack operators have many choices when incorporating a Content Delivery Network (CDN) into their infrastructure -- the CDN marketplace has both tried-and-true vendors and up-and-coming upstarts with innovative new features.
But these vendors often have highly-customized and proprietary provisioning APIs. This can be problematic when an operator wishes to support multiple providers -- or swap out one vendor for another. And these challenges spill over to developers who become forced into codifying the CDN instructions for multiple vendors into their applications.
Poppy aims to solve these challenges. Written as a modular, vendor-neutral API, Poppy incorporates a driver-based model that wraps provisioning instructions for all CDN vendors that support it. Application developers can write their code once, and Poppy will handle all the requisite translations behind-the-scenes.
Primary Mission
Poppy's primary mission is to provide a generic and modular vendor-neutral API that wraps provisioning instructions for CDN vendors that support it.
Status
Poppy is in its early development phase. As the API is fleshed out, and basic vendor support is added, the product will mature.
Poppy is open to the developer community and CDN vendors to collaborate and build this exciting new product.
Community
Launchpad
Meetings
If you are interested in Poppy, you can attend the public meetings held weekly in `#openstack-meeting-alt` on freenode.
Agenda: Meetings/Poppy
Meeting Time | Local Time |
---|---|
UTC 1900 Thursdays | http://www.timeanddate.com/worldclock/fixedtime.html?msg=Poppy+Meeting&iso=20140807T15 |
IRC (Freenode)
The Poppy team hangs out in #openstack-poppy
channel on Freenode. Feel free to stop in anytime to chat with us. The crew is always happy to hear your ideas and answer questions.
If you run into a bug, please report it using our issue tracker.
Presentations
Status
Source
Design
- API v1.0 ("under development")
- Poppy use cases
- Server architecture
- Frequently asked questions
CDN Providers
We are always looking for new CDN providers to join Poppy. Feel free to ping us on #openstack-poppy to chat how you can contribute, and read some of the Getting Started guides above. We look forward to having you on board!
- Fastly (under development)
- MaxCDN (under development)
- Amazon CloudFront (under development)
- Akamai (coming soon)
- Edgecast (coming soon)
- Insert Your CDN Here !!!