Learn how go from zero lines of code to a simple Google Cloud Endpoints API targeting the Python runtime of the Google App Engine. The videos discuss writing your own ProtoRPC message classes, creating API methods and wrap up by adding OAuth 2.0 authentication.
The App Engine Python 2.7 runtime is more than a simple upgrade to the Python 2.5 runtime: it has fewer restrictions, introduces some popular third-party libraries and allows for concurrent requests. The session will explain how to get the most out of these new capabilities.
This talk covers using Python to initiate change on the infrastructure side; we’ll discuss on great tools like Django, libCloud, and Celery. We will focus on node creation and destruction within multiple clouds, as well as the frameworks used to achieve this.
A developer talks about her lessons learned with setting up her first server, and offers advice to others about to tread that path.
Over the past year, Heroku has expanded by going polyglot and supporting languages like Java, Clojure, Python, Node.js, and Scala in addition to Ruby. In this session, we will discuss major updates to the platform and our emphasis on making the Ruby developer experience even better. We’ll leave plenty of …
This video presents the challenges faced and lessons learned in building an infrastructure to deploy web applications to the cloud with Python. You will learn about which packages are critical for a secure, Python-centric LAMP stack (and what it takes to build them); tips for developing, deploying, and scaling Python …
Apache Libcloud is an open-source client library that abstracts away differences among multiple cloud provider APIs, exposing common functionality in a nice, clean and concise API. The current version allows users to manage four different cloud resources: Cloud Servers (services such as Amazon EC2 and Rackspace), Cloud Storage, Load Balancers …
This talks start by defining the place of OpenStack in the general “cloud” landscape and explaining why a fully open cloud infrastructure stack is necessary to avoid vendor lock-in. It then focuses on the OpenStack project goals, its developer community, its open design and release processes and the developer tools …
