Jump to: navigation, search

Difference between revisions of "Poppy"

m (Resources)
m (Developer quick start)
Line 53: Line 53:
  
 
===== Developer quick start =====
 
===== Developer quick start =====
* [[Poppy/Welcome New Contributors|Welcome New Contributors]]
+
* [[Poppy/Welcome New Contributors|Welcome new contributors]]
 
* [[Poppy/Contributing|Contributing]]
 
* [[Poppy/Contributing|Contributing]]
* [https://poppy.readthedocs.org Read The Docs]
+
* [https://poppy.readthedocs.org Read the docs]
* [[Poppy/FAQ|Frequently Asked Questions]]
+
* [[Poppy/FAQ|Frequently asked questions]]
  
 
===== API specs =====
 
===== API specs =====

Revision as of 20:12, 27 August 2014

Summary

An OpenStack-related Stackforge project designed to make CDN services easier to consume with a generic vendor-neutral API.

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

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.

Weekly Poppy team meeting

If you are interested in Poppy, you can attend the public meetings held weekly in `#openstack-meeting-alt` on freenode.

Meeting Time Local Time
UTC 1900 Thursdays http://www.timeanddate.com/worldclock/fixedtime.html?msg=Poppy+Meeting&iso=20140807T15

Please feel free to add items to the agenda below with your name and we will cover them.

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.  Proposal
 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 cannot find the information that you are looking for, please drop us a line in IRC (#openstack-poppy) and we'll be happy to help.

Developer quick start
API specs
Design
Quality engineering
Resources
Community

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!