rohityadavcloud commented on code in PR #547: URL: https://github.com/apache/cloudstack-documentation/pull/547#discussion_r2303508244
########## source/adminguide/extensions/limitations.rst: ########## @@ -0,0 +1,51 @@ +.. Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information# + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + http://www.apache.org/licenses/LICENSE-2.0 + Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. + + +Limitations +=========== + +Although the external Instances behave a lot like CloudStack managed +Instances in many ways, there are some limitations. Some of these +limitations are due to the framework itself, while others can be addressed +by adding custom actions in the scripts written for the built-in extensions. + +**Features / Actions not supported at the framework level:** + + - Console access to the external Instances. + + - Data volumes. + + - User Data and Metadata services. + + - SSH key injection. + + - Affinity Groups. + + - Migrate Instance. Review Comment: @abh1sar could we also add host capacity & utilisation? Also do we support multiple nics (post-deployment or on initial deployment?) It may be exhaustive to list what we don't support, perhaps we can say at the end specifically what is supported and that all the list of things (above) are some of the general things that we don't support? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
