If you want to interact with Sunstone you have to open a new browser and go to the url where your Sunstone server is deployed. You will find the login screen where the username and password correspond to the OpenNebula credentials.

After logging into Sunstone, the view defined in /etc/one/sunstone-view for the user/group will be loaded automatically.

Sunstone users can configure several options from the configuration tab:

• Language: select the language that they want to use for the UI.
• Use secure websockets for VNC: Try to connect using secure websockets when starting VNC sessions.
• Views: change between the different available views for the given user/group

This options are saved in the user template. If not defined, defaults from sunstone-server.conf are taken.

If more than one view are available for this user, she can easily change between them in the settings window, along with other settings (e.g. language).

For more information on customizing Susntone views.

Sunstone support multiple languages. If you want to contribute a new language, make corrections or complete a translation, you can visit our:

• Transifex poject page

Translating through Transifex is easy and quick. All translations should be submitted via Transifex.

Users can update or contribute translations anytime. Prior to every release, normally after the beta release, a call for translations will be made in the user list. Then the source strings will be updated in Transifex so all the translations can be updated to the latest OpenNebula version. Translation with an acceptable level of completeness will be added to the final OpenNebula release.

In order to use this feature, make sure that:

• The VM template has a GRAPHICS section defined, that the TYPE attribute in it is set to VNC.

• The specified VNC port on the host on which the VM is deployed is accessible from the Sunstone server host.

• The VM is in running state.

If the VM supports VNC and is running, then the VNC icon on the Virtual Machines view should be visible and clickable:

When clicking the VNC icon, the process of starting a session begins:

• A request is made and if a VNC session is possible, Sunstone server will add the VM Host to the list of allowed vnc session targets and create a random token associated to it.

• The server responds with the session token, then a noVNC dialog pops up.

• The VNC console embedded in this dialog will try to connect to the proxy either using websockets (default) or emulating them using Flash. Only connections providing the right token will be successful. Websockets are supported from Firefox 4.0 (manual activation required in this version) and Chrome. The token expires and cannot be reused.

In order to close the VNC session just close the console dialog.

From Sunstone 3.8, a single instance of the VNC proxy is launched when Sunstone server starts. This instance will listen on a single port and proxy all connections from there.

Image file upload to the server via the client browser is possible with the help of a vendor library. The process is as follow:

• Step 1: The client uploads the whole image to the server in a temporal file in the tpmdir folder specified in the configuration.
• Step 2: OpenNebula registers an image setting the PATH to that temporal file.
• Step 3: OpenNebula copies the images to the datastore.
• Step 4: The temporal file is deleted and the request returns successfully to the user (a message pops up indicating that image was uploaded correctly).

Note that when file sizes become big (normally over 1GB), and depending on your hardware, it may take long to complete the copying in step 3. Since the upload request needs to stay pending until copying is sucessful (so it can delete the temp file safely), there might be Ajax timeouts and/or lack of response from the server. This may cause errors, or trigger re-uploads (which reinitiate the loading progress bar).

As of Firefox 11 and previous versions, uploads seem to be limited to 2GB. Chrome seems to work well with images > 4 GB.