User-friendly, extensible client for cloud computing. Currently targeting OpenStack.

Real-time chat (sign in with email or GitHub)

Try Exosphere on GitHub Pages

First install node.js + npm. (On Ubuntu/Debian you may also need to apt-get install nodejs-legacy.)

Then install the project's dependencies (including Elm). Convenience command to do this (run from the root of the exosphere repo):

npm install

To compile the app:

elm-make src/Exosphere.elm

Then browse to the compiled index.html.

We plan to build OS-specific application packages for Exosphere using electron-builder, but haven't gotten to it yet. Here's how to get Exosphere running with a few extra steps.

First install node.js + npm. (On Ubuntu/Debian you may also need to apt-get install nodejs-legacy.)

Then install the project's dependencies (including Elm & Electron). Convenience command to do this (run from the root of the exosphere repo):

npm install

To compile and run the app:

npm run electron-build
npm run electron-start

To watch for changes to *.elm files, auto-compile when they change, and hot-reloading of the app:

npm run electron-watch

Based on the instructions found here:

https://medium.com/@ezekeal/building-an-electron-app-with-elm-part-1-boilerplate-3416a730731f

Note: connecting to cloud providers from Exosphere running in a browser is currently problematic because of the same-origin policy (making cross-origin credentialed requests and viewing headers of the responses). A way around this is to 1. install a browser extension like CORS Everywhere, and 2. Connect to an OpenStack cloud whose Keystone is configured to allow cross-origin requests. This works for testing/evaluation purposes but is not recommended for security reasons.

• First, install Elm
• Run elm-reactor from the root of this repository
• Visit http://localhost:8000/src/Exosphere.elm

In the spirit of PEP 8, each file should import modules grouped into sections as follows:

1. Elm Standard libraries
2. Community libraries
3. Local app-specific libraries/imports

Unlike Python/PEP8 you will not be able to separate each section with a space because elm-format will remove the spaces. The spaces are not an Elm convention.

The imports in each section should be in alphabetical order.

In order to use Exosphere, OpenStack services must be configured to allow cross-origin requests. This is because Exosphere is served from a different domain than the OpenStack APIs.

(todo describe security implications)

The OpenStack admin guide has a great page on how to enable CORS across OpenStack services. This guide was removed but is fortunately still accessible via Wayback Machine.

At minimum, need the following in keystone.conf and neutron.conf:

[cors]
allowed_origin: *

The following in nova.conf:

[cors]
allowed_origin = *
allow_headers = Content-Type,Cache-Control,Content-Language,Expires,Last-Modified,Pragma,X-Custom-Header,OpenStack-API-Version, X-Auth-Token