Based on Incubation Template:  Note - Poppy has currently NOT applied for Incubation
- 1 Project codename
- 2 Trademarks
- 3 Summary
- 4 Parent Program name and PTL
- 5 Mission statement
- 6 Detailed Description
- 7 Basic roadmap for the project
- 8 Location of project source code
- 9 Programming language, required technology dependencies
- 10 Is project currently open sourced? What license?
- 11 Level of maturity of software and team
- 12 Project developers qualifications
- 13 Infrastructure requirements
- 14 Have all current contributors agreed to the OpenStack CLA?
(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"
Poppy is a CDN provisioning API for OpenStack Operators
Parent Program name and PTL
Program Name: PTL: Amit Gandhi
(if the project is part of a new OpenStack program)
(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.
Basic roadmap for the project
Location of project source code
Programming language, required technology dependencies
- DNS Provider (designate or rackspace cloud dns)
- Database Server (sqlalchemy or cassandra)
- CDN Provider
Is project currently open sourced? What license?
Yes - Licensed under the Apache License, Version 2.0
Level of maturity of software and team
Still in development
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.
Project developers qualifications
Rackspace - Senior Manager, Core Developer
Rackspace - Software Developer in Test IV
Rackspace - Software Developer
Rackspace - Software Developer
HP - Senior Developer
Have all current contributors agreed to the OpenStack CLA?