Poppy/Incubation Application

Based on Incubation Template: Note - Poppy has currently NOT applied for Incubation

Project codename
Poppy

Trademarks
(Does this project name, codename or contents use any trademarks, and if so, who owns them? List the codenames or other marks for which a trademark search should occur.)

No known trademarks. Project codename is "poppy"

Summary
Poppy is a CDN provisioning API for OpenStack Operators

Parent Program name and PTL
Program Name: PTL: Amit Gandhi

Mission statement
(if the project is part of a new OpenStack program)

Detailed Description
(what is the purpose of the project and vision for it? describe the relevance of the project to other OpenStack projects and the OpenStack mission to provide a ubiquitous cloud computing platform)

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.

Location of project source code
https://github.com/stackforge/poppy

Language
Python

Dependencies

 * DNS Provider (designate or rackspace cloud dns)
 * Database Server (sqlalchemy or cassandra)
 * CDN Provider
 * Keystone

Is project currently open sourced? What license?
Yes - Licensed under the Apache License, Version 2.0

Software
Still in development

Team
The team was formed in July 2014 and has grown to include a diverse group of highly skilled developers from a range of companies including, HP, and Rackspace.

Core team review process
One core team member must "+2" a proposed change in gerrit in order to merge the code. There must be a total of +3 from members of the team. A reviewer cannot +1 their own patch.

Amit Gandhi
Rackspace - Senior Manager, Core Developer

Malini Kamalambal
Rackspace - Software Developer in Test IV

Tony Tan
Rackspace - Software Developer

Obulpathi Challa
Rackspace - Software Developer

Miguel Quintero
HP - Senior Developer

Infrastructure requirements
(testing, etc)

Have all current contributors agreed to the OpenStack CLA?
Yes