This change reformats all files according to clang-format rules (the
same that Angular JS has) and forces the files to comply with the
formatting.

Initial implementation for replica set detail view

The implementation consists of backend code and sample frontend view
that dumps the data into an ugly looking table. Subsequent changes will
implement frontend so that things look pretty.

Connect replica set list and detail views

This change connects replica set list and detail views and applies
RESTful conventions to the API.

Now API and app URLs follow RESTful API conventions. This change is also
an example of how views hould be connected. See state params and state
name exports.

Bug fix. Prevent for double call isRunning() function

Add travis configuration to run local kubernetes cluster

Implemented existing namespaces handling in deploy form

Fix path to main module file in webpack config

Without this fix, `gulp serve` fails.

Rename JS files from dot to underscore case

Fix js_module_root compiler option

This is a required change because with dot case we cannot reference
other modules inside JSDoc `@type` annotations. For example, if you want
to reference `@type {./deploy.controller.FooType}` does not work,
because the compiler does not know whether `deploy` is a module or
`deploy.controller`. Changing dot case to undersocre, camel or dash case
solves this problem.

I decided to go with underscore case because this is what golang uses
(e.g., `foo_test.js`) so we'll have higher similarity of backend and
frontend codebases.

Replica set view: added additional fields to cards

The cards now display mostly fake data, but they look more complete. The
backend will be implemented soon.

Now it is correctly specified and allows for imports anchored at
frontend src, e.g., `import 'chrome/chrome';`.

Simplified gulp scripts

spawn backend in development and production mode

View setup for the replica set detail page

This is all frontend boilerplate for the view.

Creates cluster for development/integration tests/CI

Rename microservice list view to replica set view

Per discussion in: https://github.com/kubernetes/dashboard/issues/65

This change does only renaming, no functional modifications.

Initial implementation of zerostate view.

Microservice list view implementation

This is to show in a simple layout what the backend returns.

Initial e2e implementation of the deploy view

Based on mocks:
https://github.com/kubernetes/dashboard/blob/master/designs/11-11-2015/08_deploy%20form.png

This change implements both backend and frontend for the view. This is
the approach I'll follow in the future.

Backend implementation of the service list view

1. This is a model for mocks:
https://github.com/kubernetes/dashboard/blob/master/designs/11-11-2015/16_card%20variations.png
2. Did little renaming (used the word "microservice") until we agree what the list exactly shows.
3. The implementation is very basic and will evolve over time.