Support for SSL certificate mappings on Cloud Load Balancers

[tcdent]

Implement 5 endpoints for certificate mappings as described in documentation.

http://docs.rackspace.com/loadbalancers/api/v1.0/clb-devguide/content/CertificateMappings.html

[briancurtin]

This isn't necessary, we'll handle this if it's released.

[tcdent]

Realized that after I PR'd; underestimated the involvement you guys have.

[briancurtin]

Can you tell me a bit about how you're using this, what it's solving for you, etc? We're not really working on Pyrax anymore and are in the process of building up another project that will provide access to our APIs via Python, so I'd like to simultaneously understand what you're doing for Pyrax and also make sure it's covered in the new project.

[briancurtin]

Additionally, can you take a look at the https://github.com/rackspace/pyrax/blob/master/CONTRIBUTING.rst doc and rebase the changes/PR on the working branch?

[tcdent]

By leveraging SNI, Certificate Mappings allow you to configure multiple SSL termination domains on a single load balancer (and a single IP address).

The Rackspace 'mycloud' portal does not have support for this feature, either.

If there is interest, I will refine this PR as I find the time.

Is this new project public anywhere? I'd be very interested in seeing where this is headed for future projects.

[briancurtin]

Yeah, if you want to refine it, I'll take a look and see if we can get it in here.

As for the new project, it's called OpenStack SDK, and it was born from discussions with a number of other OpenStack-based cloud providers in getting together and creating a great experience for Python users of our clouds. For Rackspace, we already had pyrax, and for other vendors, they were using the libraries each service provides (e.g., using python-novaclient directly, which pyrax wraps). All in all, we decided to create a project that provides one clean and consistent view of OpenStack's many services, smoothing over the many differences among them, from how the APIs work to how things are named, and just about anything you can think of. We've been working on it for a while now, and we're getting closer to the project being ready for a 1.0 release.

Right now it's documented on readthedocs, and a Github mirror of the source is available at stackforge/python-openstacksdk (the canonical repo is here. The PyPI package is openstacksdk.

As this is an upstream OpenStack project, vendors - such as Rackspace - will provide plugins for their services as needed, ours being called rackspacesdk. Right now we have a plugin that covers our auth system (OpenStack Keystone-based, but not actually Keystone), and a tiny service extension that allows our Cloud Files bulk delete functionality to work. The source is currently at rackerlabs/rackspace-sdk-plugin, and we're working on figuring out a good docs solution while planning out the various services to add to it. Cloud Load Balancers is one of the services we'll have to implement support for in this plugin, as it's not an OpenStack-based service.

OpenStack SDK is fairly close to a 1.0 release, within the next few months. The Rackspace plugin part of it is a little further out as we've been focused on making the upstream base the best we can. I hope to have some writing up on our blog about what's going on and what the plans are soon.

If you have any questions, feel free to email me at [email protected]