Difference between revisions of "Gyrex/Administrator Guide/Console"

From Eclipsepedia

Jump to: navigation, search
Line 7: Line 7:
 
=== SSH ===
 
=== SSH ===
 
The OSGi Console is also available via SSH. This is the recommended way of connecting to production systems. However, please [https://bugs.eclipse.org/bugs/show_bug.cgi?id=378969 be careful with the close/exit commands]. The SSH console listens on port '''3122'''.
 
The OSGi Console is also available via SSH. This is the recommended way of connecting to production systems. However, please [https://bugs.eclipse.org/bugs/show_bug.cgi?id=378969 be careful with the close/exit commands]. The SSH console listens on port '''3122'''.
 +
 +
==== Authorization ====
 +
Currently only key-based authorization is supported in the Gyrex bundled SSH consule. In order to be able to login an <code>authorized_keys</code> file need to be created in the instance data location at <code>&lt;runtime-workspace&gt;/etc/.ssh/authorized_keys</code>. That's a regular <code>authorized_keys</code> file as typically found on Linux systems.

Revision as of 05:31, 25 June 2012

Contents

OSGi Console

Gyrex integrates the Equinox Console which is based on the Apache GoGo Shell. Countless console commands are provided in order to simplify administration of a Gyrex cloud. The Equinox Console is extensible and Gyrex also includes ARGS4J which allows developing additional commands using annotations.

Terminal

In order to activate the OSGi Console one simply needs to pass the "-console" command line argument when starting Gyrex using the gyrex executable. This is the default in all Gyrex server packages.

SSH

The OSGi Console is also available via SSH. This is the recommended way of connecting to production systems. However, please be careful with the close/exit commands. The SSH console listens on port 3122.

Authorization

Currently only key-based authorization is supported in the Gyrex bundled SSH consule. In order to be able to login an authorized_keys file need to be created in the instance data location at <runtime-workspace>/etc/.ssh/authorized_keys. That's a regular authorized_keys file as typically found on Linux systems.