Personal tools
You are here: Home Blog Archive 2010 March 03 User preferences in Cloud Shell
Document Actions

User preferences in Cloud Shell

Filed Under:

VPS/Cloud customers may now set user preferences via the cloud-shell application.  Currently, we're supporting two such preferences and will continue to expand this list to support a wide array of user-configurable options...

The current variables include:

 cpu_arch, which should be '32' or '64'. Default is 64.

 autoheal, which should be 1 or 0.  Default is 1.

The cpu_arch setting will be used to determine which architecture kernel should be loaded on boot.  Please note that the boot_method variable may override this setting.  WARNING: the legacy command 'boot32' has been removed in favor of this user-preference.

The autoheal setting will determine whether or not the configured instance pool will be automatically restored/rebooted upon failure.

To set or get these variables, use the commands 'setpref' and 'getpref' as such:

cloud-shell> setpref cpu_arch 32

cloud-shell> setpref autoheal 0

cloud-shell> getpref

$VAR1 = {
          'client:NNN:pref:cpu_arch' => '32',
          'client:NNN:pref:autoheal' => '0'
        };


It should be noted that reimaging your OS currently cannot modify these variables.  Thus, if you switch from a 32-bit or 64-bit OS, you must modify the cpu_arch variable manually. This is a forthcoming improvement we must make to the system.

UPDATE:  New 'boot_method' preference available!
Currently accepted boot methods are:
  • pv - Paravirtualized (default)
  • pv_part - Paravirtualized, Partitioned disk
  • pvgrub - Paravirtualized, with GRUB
  • rescue - Boot into rescue image
Boot methods internally implement CPU architecture support and may optionally ignore or reject a configured cpu_arch setting.
Syndication
Facebook
GrokThis.net on Facebook
Twitter
Tag cloud
upgrade vps contest xen howto feature rails django hardware failure ajax virtualization security mason support cloud software
Log in


Forgot your password?
New user?
Archives
 

Powered by Plone CMS, the Open Source Content Management System

This site conforms to the following standards: