Difference between revisions of "Poppy"
Amit Gandhi (talk | contribs) (→Design) |
Amit Gandhi (talk | contribs) (→Getting Started) |
||
Line 40: | Line 40: | ||
===== Getting Started ===== | ===== Getting Started ===== | ||
− | * [[Poppy/Welcome New Contributors | + | * [[Poppy/Welcome New Contributors|Welcome New Contributors]] |
− | * [[Give Poppy a Try | + | * [[Poppy/Give Poppy a Try|Give Poppy a Try]] |
− | * [[Your First Patch | + | * [[Poppy/Your First Patch|Your First Patch]] |
− | * [[Your First Review | + | * [[Poppy/Your First Review|Your First Review]] |
− | * [[Write the Tests! | + | * [[Poppy/Write the Tests!|Write the Tests!]] |
− | * [[Write the Docs! | + | * [[Poppy/Write the Docs!|Write the Docs!]] |
===== API Specs ===== | ===== API Specs ===== |
Revision as of 21:49, 5 August 2014
Contents
Overview
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
Provide a generic and modular vendor-neutral API that wraps provisioning instructions for CDN vendors that support it.
Status
Poppy is still 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.
Resources
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.
Documentation
Talks
Openstack Summit - Paris (Nov 2014) pop.py: An Open API for CDN Provisioning. Vote Now Allan Metts (Director of Engineering - Rackspace) and Amit Gandhi (Senior Software Manager - Rackspace)
Contributor Guide
Note: The Poppy team is currently building out this section of the wiki with tons of content to help you get started, so some pages are missing or incomplete at the moment. If you can't find the information you are looking for, please drop us a line in IRC (#openstack-poppy) and we'll be happy to help.
Getting Started
- Welcome New Contributors
- Give Poppy a Try
- Your First Patch
- Your First Review
- Write the Tests!
- Write the Docs!
API Specs
- API v1.0 ("under development")
Design
Quality Engineering
- Application Security
- Performance Testing
- Unit Testing
- Functional Testing
- API Testing
- Integration Testing
Resources
- About the Program
- Frequently Asked Questions
- Development Process
- Blueprinting Process
- Programming Style Guide
- Reviewer Guide
- Getting Help
Community
CDN Providers
- Fastly (under development)
- MaxCDN (under development)
- Amazon CloudFront (under development)
- Insert Your CDN Here !!!