Add LICENSE and update README

Signed-off-by: Alex Ellis <[email protected]>

Author: alexellis

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2019 OpenFaaS Author(s)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -1,14 +1,57 @@
+faas-federation
+-----
+
+faas-federation is an implementation of the [faas-provider](https://github.com/openfaas/faas-provider) which can be used to unify one or more OpenFaaS clusters under a single API.
+
+## Why do we need this?
+
+This project exists to join together two or more distinct OpenFaaS clusters.
+
+* Multi-region - east/west
+
+Get a single API / control-plane for one or more clusters split by location, such as east/west.
+
+* Edge locations
+
+You may have one or more edge locations (or even ARM/IoT OpenFaaS installations). You can join them together under a single set of credentials and control plane.
+
+* Varying provider types
+
+You can connect two or more different OpenFaaS provider types together. For instance: Kubernetes (faas-netes) and Lambda (faas-lambda). This means you can have a single, centralized control-plane but deploy to both AWS Lambda and Kubernetes at the same time.
+
+## Getting started
+
+`faas-federation` can replace your provider in your existing OpenFaaS deployment.
+
+More coming soon.
+
+### Example
+
+Coming soon: deploy OpenFaaS with two separate [`faas-memory`](https://github.com/openfaas-incubator/faas-memory) providers.
+
+### helm chart
+
+See also: example of Kubernetes and AWS Lambda federated configuration in the sample [helm chart](deployment/chart/of-federation).
+
 ## Constraints
+
 | Annotation | Description |
 | ----|----|
 | federation.provider_name | route the request based on the provider name i.e. `kubernetes`, `swarm` |
 
 ## Configuration
+
 All configuration is managed using environment variables
 
 | Option                            | Usage                                                                                          | Default                  | Required |
 |-----------------------------------|------------------------------------------------------------------------------------------------|--------------------------|----------|
 | `providers`           | comma separated list of provider URLs i.e. `http://faas-netes:8080,http://faas-lambda:8080` | - |   yes    |
 | `default_provider`    | default provider URLs used when no deployment constraints are matched i.e. `http://faas-netes:8080` | - |   yes    |
 
+## Acknowledgements
+
+Idea by Alex Ellis and Edward Wilde.
+
+## License
 
+MIT