Changes between Version 109 and Version 110 of flukes

Show
Ignore:
Timestamp:
09/05/13 23:44:24 (6 years ago)
Author:
ibaldin (IP: 108.65.62.60)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • flukes

    v109 v110  
    112112 
    113113Flukes offers a convenient option to login to the provisioned slivers. By default it tries to use ~/.ssh/id_dsa private key and ~/.ssh/id_dsa.pub public key if the user has them. These settings can be overridden by setting ssh.key and ssh.pubkey properties in ~/.flukes.properties. Also the experimenter can override the application used to provide terminal capabilities (xterm, by default) and the options passed to SSH client. Again, the default settings can be seen in 'Help | Preferences' window and can be overridden in ~/.flukes.properties. 
     114 
     115By default Flukes instructs ORCA to enable root logins into nodes using user's public SSH key. It is possible to have Flukes create an additional account on each node that will be associated with a separate SSH public key, to, for example, provide someone else access to slivers in your slice. To do that you must modify the following properties in ~/.flukes.properties file: 
     116{{{ 
     117# Secondary login (works with ssh.other.pubkey). It can be set to 'root', which will give both you and the other user access to root login 
     118ssh.other.login=username 
     119# Secondary public SSH key (perhaps belonging to other users) that should be installed in the slice. 
     120ssh.other.pubkey=~/Desktop/id_rsa.pub 
     121# Should the secondary account have sudo privileges 
     122ssh.other.sudo=yes 
     123}}} 
    114124 
    115125=== Post Boot Scripts and templates  ===