I’ll explain how React is moving towards a minimal API surface area. Instead of providing many framework features, React is trying to utilize patterns, paradigms and JavaScript language features to accomplish the same tasks that other frameworks have dedicated APIs for. Not all environments have these natively. We need to polyfill new an experimental features. How can we safely do that? Is it better to have a non-standard library?
1) Infrastructure services offered by multiple Openstack deployments in geographical distributed DCs need to be consolidated into a unified one;
2) Vendor agnostic and unified Openstack API is expected even when the Openstack resource pools in different DCs are provided by different vendors
3) Unified Openstack resource pooling needs to flexibly scale out from several Servers/VMs up to millions of Servers/ VMs;
4) Rolling update with minimized service interruption is expected when upgrading the Openstack Cloud OS software, SOA Restful API is preferred over RPC internal messaging interface for the orchestration & communication between different availability zones.
The answer is OpenStack Cascading solution. The speech will cover background requirements and customer value analysis, technical elaboration of OpenStack Cascading solution, and its Demo. Overview of OpenStack cascading solution can be found at wiki.openstack.org/wiki/OpenStack_cascading_solution.
1) Infrastructure services offered by multiple Openstack deployments in geographical distributed DCs need to be consolidated into a unified one;
2) Vendor agnostic and unified Openstack API is expected even when the Openstack resource pools in different DCs are provided by different vendors
3) Unified Openstack resource pooling needs to flexibly scale out from several Servers/VMs up to millions of Servers/ VMs;
4) Rolling update with minimized service interruption is expected when upgrading the Openstack Cloud OS software, SOA Restful API is preferred over RPC internal messaging interface for the orchestration & communication between different availability zones.
The answer is OpenStack Cascading solution. The speech will cover background requirements and customer value analysis, technical elaboration of OpenStack Cascading solution, and its Demo. Overview of OpenStack cascading solution can be found at wiki.openstack.org/wiki/OpenStack_cascading_solution.
Keystone is the reference implementation of the Identity API in OpenStack. It needs to deal with traditional identity concepts such as users and groups as well as centrally managing authorization. This session will cover how Keystone can leverage existing identity sources for authentication and identity information and instead focus on it's primary job of centrally managing access to cloud services and resources.
Keystone has a pluggable architecture that allows it to work with different identity sources. These options range from storing identity information locally to using external identity sources such as an LDAP server or a SAML identity provider. Nearly all companies and organizations already have an existing authoritative identity source that provides centralized authentication and user and group information. Configuring Keystone to use this central identity source is a popular goal for those deploying OpenStack, yet its not straight-forward to actually accomplish due to variations of different identity sources.
In this presentation, Nathan Kinder will review how Keystone has evolved around the concept of identity to date. An overview of the very latest options for handling identity information will be provided, along with the pros and cons of the available approaches. We will also discuss how Keystone can leverage existing identity sources to provide strong authentication mechanisms in addition to discussing more complex scenarios such as using multiple external identity sources from a single Keystone instance.
“Your body is a system, a machine; like all machines it can be tuned.”
This talk is the story of how I hacked my body, got my sleep cycle under control, and how I’m using JavaScript to do it. It’s an optimistic tale of crazy hacks and how we can use technology to complement our humanity instead of fighting it (and how we can all get a little more sleep).
We’ll start in the year 2009, in the cold snowy planes of upstate New York. A young college student is suffering from the winter blues and having trouble sleeping. And then, with some hardware and programming the first spark: his first artificial sunrise! We’ll talk about the science behind “dawn and dusk simulations” and why so many developers are using tools like f.lux to help them get a good night’s rest. Then we’ll follow the development of the system I’ve worked on, called Spirit, to the present day. I’ll talk through why I chose JavaScript, how the system works, and how others can get started on a similar journey (and for less money and effort than ever before).
Extending your Rails app with some Go, Scala, Elixir or node.js sound interesting to you? The first challenge to get there is to safely share the session between your apps. Crypto is hard… but that won't prevent us from looking into how Rails sessions work and how to share them across programming languages.
Julia is a new, up-and-coming language that has many similarities to Python, but some differences. One of its main advantages is the speed gain obtained by automatically compiling all code (in a somewhat similar way to PyPy, Cython, numba, etc.), despite having an interactive interface very similar to that of Python.
This will be a tutorial on the basic features of Julia from scratch, given by a user (rather than a developer) of the language, emphasising those features which are similar to Python (and hence do not require much explanation) and those features which are rather different.
The idea of the tutorial is to give an idea of why there is suddenly such a buzz around Julia and why it can be useful for certain projects.
This tutorial is aimed at people who are already familiar with the basic scientific Python packages; it is not aimed at beginners in scientific programming.
A internal civil war has been my life for years as I've walked the razor wire separating breakers and builders.
I'd like to share my experiences presenting outside the security industry at developer conferences like Djangocon, JSConf (trackb), and RealtimeConf what it's like to be the lone security professional in a sea of builders, what it feels like, what they say, what they really care about, how not to speak to them, how to completely disrespect them, and how to fail miserably.
