This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|2 years ago|
|doc||3 years ago|
|docker||5 years ago|
|etc||5 years ago|
|hadoop||6 years ago|
|poppy||5 years ago|
|requirements||5 years ago|
|scripts||5 years ago|
|tests||5 years ago|
|tools||5 years ago|
|.coveragerc||7 years ago|
|.gitignore||6 years ago|
|.gitreview||2 years ago|
|.testr.conf||5 years ago|
|AUTHORS.rst||6 years ago|
|HACKING.rst||6 years ago|
|LICENSE||8 years ago|
|MANIFEST.in||8 years ago|
|README.rst||6 years ago|
|kill_poppy.sh||6 years ago|
|pylintrc||7 years ago|
|run_poppy.sh||6 years ago|
|run_tests.sh||6 years ago|
|setup.cfg||5 years ago|
|setup.py||6 years ago|
|tox.ini||5 years ago|
CDN as a Service
What is Poppy ============
Users have come to expect exceptional speed in their applications, websites, and video experiences. Because of this, using a CDN has become standard for companies, no matter their size.
Poppy will take all the guess work out of the CDN market for our users. Poppy will give them a consistently speedy experience from integrated partners, with an easy to use RESTful API.
Vendor lock-in to a particular CDN provider is removed by abstracting away the plethora of vendor API's available. This means that a customer only has to integrate with one CDN API, and reap the benefits of using multiple providers.
Your content can be distributed to multiple providers seamlessly instead of just one.
Running performance benchmarks against each configured CDN provider allows you to simply repoint your DNS at the new provider; and with that simple change you can ensure your application is running using the fastest provider at the time. It will also allow you to handle CDN failures and minimize disruption to your application from CDN outages.
- Wraps third party CDN provider API's
- Akamai (Production Ready)
- Fastly (In Development)
- Amazon CloudFront (In Development)
- MaxCDN (In Development)
- Your CDN Here...
- Sends configurations to n configured CDN providers
- Supports multiple backends (CassandraDB recommended)
- Your DB provider here
- Supports multiple dns providers
- Rackspace DNS
- Openstack Designate (Coming Soon)
- Openstack Compatable
- Uses Keystone for authentication
- Uses Swift for log delivery
- Multiple Origins to pull from (Public Servers, Amazon S3 Buckets, ...)
- Supports Multiple Domains
- Custom Caching and TTL rules
- Set Restrictions on who can access cached content
What Poppy is not
Poppy does not run its own Edge Cache or POP servers. This is purely a management API to abstract away the myriad of CDN providers on the market.
Note: These instructions are for running a local instance of CDN and not all of these steps are required. It is assumed you have CassandraDB and Zookeeper installed and running in a Docker Container.
From your home folder create the
~/.poppyfolder and clone the repo:
$ cd $ mkdir .poppy $ git clone https://github.com/openstack/poppy.git
Copy the Poppy config files to the directory
$ cp poppy/etc/poppy.conf ~/.poppy/poppy.conf $ cp poppy/etc/logging.conf ~/.poppy/logging.conf
~/.poppy/poppy.confand modify the URI to point to your local casssandra cluster:
[drivers:storage:cassandra] cluster = <docker ip> keyspace = poppy migrations_path = /home/poppy/poppy/storage/cassandra/migrations automatic_schema_migration = True #True is recommended for local dev machine
For logging, find the
~/.poppy/poppy.confand modify as desired:
log_file = server.log
Change directories back to your local copy of the repo:
$ cd poppy
Install general requirements:
$ pip install -r requirements/requirements.txt
Run the following so you can see the results of any changes you make to the code without having to reinstall the package each time:
$ pip install -e .
To install additional dependencies, see Additional Dependencies.
Install and start cassandra and zookeeper driver:
$ pip install docker-compose $ docker-compose -f docker/compose/dependencies.yml up -d
Start poppy task flow worker:
Start the Poppy server:
Test out that Poppy is working by requesting the home doc (with a sample project ID):
$ curl -i -X GET -H "X-Project-ID: 000" -H "X-Auth-Token: 000" -H "Content-Type: application/json" http://127.0.0.1:8888/v1.0/
You should get an HTTP 200 along with some headers that will look similar to this:
HTTP/1.0 200 OK Date: Thu, 13 Feb 2014 14:34:21 GMT Server: WSGIServer/0.1 Python/2.7.3 Content-Length: 464 Content-Type: application/json-home Cache-Control: max-age=86400
To run unit/functional test:
To run a full test suite with api test, you will need to put in correct CDN vendor configuration (in
~/.poppy/poppy.conf) first, e.g:
[drivers:provider:fastly] apikey = "<your_fastly_api_key>"
Then start a poppy server:
$ poppy-server -v
And run test suite with api test:
$ tox -- --exclude=none
For Python 2.7:
$ sudo apt-get install python-dev
For Python 3.4:
$ sudo apt-get install python3.4-dev
$ sudo apt-get install pypy-dev
Install these two packages regardless of the Python version:
$ sudo apt-get install libffi6 libffi-dev $ sudo apt-get install libssl-dev
Installing Cassandra and Zookeeper Locally
We recommend running Cassandra and Zookeeper in a docker container when developing locally.
Follow the instuctions in the /poppy/docker/compose/README.md file for running Poppy locally.
First install the additional requirements:
$ pip install tox
And then run tests: