Copyright (c) 2006-2014 MindTouch Inc.
This file and accompanying files are licensed under the MindTouch Master Subscription Agreement (MSA).
At any time, you shall not, directly or indirectly: (i) sublicense, resell, rent, lease, distribute, market, commercialize or otherwise transfer rights or usage to: (a) the Software, (b) any modified version or derivative work of the Software created by you or for you, or (c) MindTouch Open Source (which includes all non-supported versions of MindTouch-developed software), for any purpose including timesharing or service bureau purposes; (ii) remove or alter any copyright, trademark or proprietary notice in the Software; (iii) transfer, use or export the Software in violation of any applicable laws or regulations of any government or governmental agency; (iv) use or run on any of your hardware, or have deployed for use, any production version of MindTouch Open Source; (v) use any of the Support Services, Error corrections, Updates or Upgrades, for the MindTouch Open Source software or for any Server for which Support Services are not then purchased as provided hereunder; or (vi) reverse engineer, decompile or modify any encrypted or encoded portion of the Software.
A complete copy of the MSA is available at http://www.mindtouch.com/msa
To SSH into a running Cloud.com CloudStack server.
Table of Contents
Before you can successfully SSH into a public server, you must first assign it a public IP address with the appropriate port forward rules (firewall permissions). If you are attempting to SSH into a private server, you'll need to disable port forwarding as well as multiple subnets.
Only the CloudStack administrator can provision public IP addresses. You can associate a public IP to any running server, but it cannot be associated to more than one server at a time. If an unassigned public IP address is not available, contact the CloudStack administrator.
Note: Port forwarding rules apply to an IP address and not to the running instance. So, if you terminate an instance that was assigned an IP (e.g. 220.127.116.11), which had port forwarding rules for TCP ports 22 and 80, and then you assign the same public IP to a new server, it will automatically apply its existing port forwarding rules.
To be able to SSH into a private IP, you will need to disable port fowarding rules and multiple subnets.
|Glossary | 用語 | 용어||Site Map | Site Help||Community||Corporate Site||Get Support||Dashboard Login|
|Doc Feedback||Product Feedback||Resources||MultiCloud Marketplace||Forums|
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.