Splitting the project into layers

[Zarquan]

I think we need to split this project into three separate GitHub projects to reflect the different layers in the system. Hopefully this will make it easier to manage the source code, issues and testing for each of the layers.

1. Deploy Kubernetes into an empty OpenStack project space.
2. Deploy Spark and Zeppelin into an empty Kubernetes cluster.
3. Develop a set of Spark and Zeppelin tools for analysing the Gaia data.

• Each layer is deployable and testable as a separate component in its own right.
• Each layer has a separate GitHub repo, including code base, issues, and CI testing process.

This way we can be working on development versions of the Kubernetes and Spark layers, while at the same time using the current release versions of them as a stable platform to develop the Spark and Zeppelin analysis tools.

This has implications for issue #33. Each layer would have its own CI integration, using the other layers as components to build the CI test environment.

[Zarquan]

Based on what we have learned so far, (1) and (2) are now probably merged into a single 'infrastructure' layer, but (3) is still a separate layer.

[Zarquan]

This is no longer an issue.