Jessica Tomechak created CLOUDSTACK-1525:
--------------------------------------------
Summary: Add section on how to ssh in to system VMs
Key: CLOUDSTACK-1525
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1525
Project: CloudStack
Issue Type: Improvement
Security Level: Public (Anyone can view this level - this is the default.)
Components: Doc
Affects Versions: 4.0.0, 4.1.0
Reporter: Jessica Tomechak
Priority: Minor
Fix For: 4.2.0
In the "Working with System VMs" section of the Admin Guide, there is no
"Accessing System VMs" section. There should be one, similar to the "Accessing
VMs" section in the earlier "Working with Virtual Machines" section. You can
access system VMs through the UI, in the Infrastructure tab. You can also ssh
in, using the following techniques.
To access a system VM directly over the network, use one of the following
techniques, depending on the hypervisor.
XenServer or KVM:
SSH in by using the link local IP address of the system VM. For example, in the
command below, substitute your own path to the private key used to log in to
the system VM and your own link local IP.
Run the following command on the XenServer or KVM host on which the system VM
is present:
# ssh -i <private-key-path> <link-local-ip> -p 3922
Now you can run commands on the system VM. For example, to check the software
version:
# cat /etc/cloudstack-release
The output should be like the following:
Cloudstack Release 4.0 Mon Feb 6 15:10:04 PST 2013
ESXi:
SSH in using the private IP address of the system VM. For example, in the
command below, substitute your own path to the private key used to log in to
the system VM and your own private IP.
Run the following command on the Management Server:
# ssh -i <private-key-path> <private-ip> -p 3922
Now you can run commands on the system VM. For example, to check the software
version:
# cat /etc/cloudstack-release
The output should be like the following:
Cloudstack Release 4.0 Mon Feb 6 15:10:04 PST 2013
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
