The System VM Template

In-Reply-To: <70dce7e46df64989b9cdbc3fddef9604@git.apache.org> References: <70dce7e46df64989b9cdbc3fddef9604@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [22/51] [partial] cloudstack-docs git commit: Remove all old docbook files http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/system-vm-template.xml ---------------------------------------------------------------------- diff --git a/en-US/system-vm-template.xml b/en-US/system-vm-template.xml deleted file mode 100644 index a9477f3..0000000 --- a/en-US/system-vm-template.xml +++ /dev/null @@ -1,37 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- The System VM Template - The System VMs come from a single template. The System VM has the following characteristics: - - Debian 6.0 ("Squeeze"), 2.6.32 kernel with the latest security patches from the Debian security APT repository - Has a minimal set of packages installed thereby reducing the attack surface - 32-bit for enhanced performance on Xen/VMWare - pvops kernel with Xen PV drivers, KVM virtio drivers, and VMware tools for optimum performance on all hypervisors - Xen tools inclusion allows performance monitoring - Latest versions of HAProxy, iptables, IPsec, and Apache from debian repository ensures improved security and speed - Latest version of JRE from Sun/Oracle ensures improved security and speed - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/tagging-resources.xml ---------------------------------------------------------------------- diff --git a/en-US/tagging-resources.xml b/en-US/tagging-resources.xml deleted file mode 100644 index 31ee382..0000000 --- a/en-US/tagging-resources.xml +++ /dev/null @@ -1,69 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Using Tags to Organize Resources in the Cloud - A tag is a key-value pair that stores metadata about a resource in the cloud. Tags are - useful for categorizing resources. For example, you can tag a user VM with a - value that indicates the user's city of residence. In this case, the key would - be "city" and the value might be "Toronto" or "Tokyo." You can then request - &PRODUCT; to find all resources that have a given tag; for example, VMs for - users in a given city. - You can tag a user virtual machine, volume, snapshot, guest network, template, - ISO, firewall rule, port forwarding rule, public IP address, security group, - load balancer rule, project, VPC, network ACL, or static route. You can not tag - a remote access VPN. - You can work with tags through the UI or through the API commands createTags, - deleteTags, and listTags. You can define multiple tags for each resource. There - is no limit on the number of tags you can define. Each tag can be up to 255 - characters long. Users can define tags on the resources they own, and - administrators can define tags on any resources in the cloud. - An optional input parameter, "tags," exists on many of the list* API commands. - The following example shows how to use this new parameter to find all the volumes - having tag region=canada OR tag city=Toronto: - command=listVolumes - &listAll=true - &tags[0].key=region - &tags[0].value=canada - &tags[1].key=city - &tags[1].value=Toronto - The following API commands have the "tags" input parameter: - - listVirtualMachines - listVolumes - listSnapshots - listNetworks - listTemplates - listIsos - listFirewallRules - listPortForwardingRules - listPublicIpAddresses - listSecurityGroups - listLoadBalancerRules - listProjects - listVPCs - listNetworkACLs - listStaticRoutes - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/template-iso-snapshot-usage-record-format.xml ---------------------------------------------------------------------- diff --git a/en-US/template-iso-snapshot-usage-record-format.xml b/en-US/template-iso-snapshot-usage-record-format.xml deleted file mode 100644 index 3f34f36..0000000 --- a/en-US/template-iso-snapshot-usage-record-format.xml +++ /dev/null @@ -1,42 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Template, ISO, and Snapshot Usage Record Format - - account – name of the account - accountid – ID of the account - domainid – ID of the domain in which this account resides - zoneid – Zone where the usage occurred - description – A string describing what the usage record is tracking - usage – String representation of the usage, including the units of usage (e.g. 'Hrs' for hours) - usagetype – A number representing the usage type (see Usage Types) - rawusage – A number representing the actual usage in hours - usageid – The ID of the the template, ISO, or snapshot - offeringid – The ID of the disk offering - templateid – – Included only for templates (usage type 7). Source template ID. - size – Size of the template, ISO, or snapshot - startdate, enddate – The range of time for which the usage is aggregated; see Dates in the Usage Record - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/templates.xml ---------------------------------------------------------------------- diff --git a/en-US/templates.xml b/en-US/templates.xml deleted file mode 100644 index faecf1b..0000000 --- a/en-US/templates.xml +++ /dev/null @@ -1,29 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Templates - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/third-party-ui-plugin.xml ---------------------------------------------------------------------- diff --git a/en-US/third-party-ui-plugin.xml b/en-US/third-party-ui-plugin.xml deleted file mode 100644 index 297fdaa..0000000 --- a/en-US/third-party-ui-plugin.xml +++ /dev/null @@ -1,364 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - Third-Party UI Plugin Framework - Using the new third-party plugin framework, you can write and install extensions to - &PRODUCT;. The installed and enabled plugins will appear in the UI alongside the - other features. - The code for the plugin is simply placed in a special directory - within &PRODUCT;’s installed code at any time after &PRODUCT; installation. The new plugin - appears only when it is enabled by the cloud administrator. - - - - - - plugin_intro.jpg: New plugin button in product navbar - - - The left navigation bar of the &PRODUCT; UI has a new Plugins button to help you work with UI plugins. -

- How to Write a Plugin: Overview - The basic procedure for writing a plugin is: - - - Write the code and create the other files needed. You will need the plugin code - itself (in Javascript), a thumbnail image, the plugin listing, and a CSS file. - - - - - - plugin1.jpg: Write the plugin code - - - All UI plugins have the following set of files: - +-- cloudstack/ - +-- ui/ - +-- plugins/ - +-- csMyFirstPlugin/ - +-- config.js --> Plugin metadata (title, author, vendor URL, etc.) - +-- icon.png --> Icon, shown on side nav bar and plugin listing - (should be square, and ~50x50px) - +-- csMyFirstPlugin.css --> CSS file, loaded automatically when plugin loads - +-- csMyFirstPlugin.js --> Main JS file, containing plugin code - - The same files must also be present at /tomcat/webapps/client/plugins. - - - The &PRODUCT; administrator adds the folder containing your plugin code under the - &PRODUCT; PLUGINS folder. - - - - - - plugin2.jpg: The plugin code is placed in the PLUGINS folder - - - - - The administrator also adds the name of your plugin to the plugin.js file in the - PLUGINS folder. - - - - - - plugin3.jpg: The plugin name is added to plugin.js in the PLUGINS - folder - - - - - The next time the user refreshes the UI in the browser, your plugin will appear in - the left navigation bar. - - - - - - plugin4.jpg: The plugin appears in the UI - - - - -

- How to Write a Plugin: Implementation Details - This section requires an understanding of JavaScript and the &PRODUCT; API. You don't - need knowledge of specific frameworks for this tutorial (jQuery, etc.), since the - &PRODUCT; UI handles the front-end rendering for you. - There is much more to the &PRODUCT; UI framework than can be described here. The UI is - very flexible to handle many use cases, so there are countless options and variations. The - best reference right now is to read the existing code for the main UI, which is in the /ui - folder. Plugins are written in a very similar way to the main UI. - - - Create the directory to hold your plugin. - All plugins are composed of set of required files in the directory - /ui/plugins/pluginID, where pluginID is a short name for your plugin. It's recommended - that you prefix your folder name (for example, bfMyPlugin) to avoid naming conflicts - with other people's plugins. - In this example, the plugin is named csMyFirstPlugin. - $ cd cloudstack/ui/plugins -$ mkdir csMyFirstPlugin -$ ls -l - -total 8 -drwxr-xr-x 2 bgregory staff 68 Feb 11 14:44 csMyFirstPlugin --rw-r--r-- 1 bgregory staff 101 Feb 11 14:26 plugins.js - - - - Change to your new plugin directory. - $ cd csMyFirstPlugin - - - - Set up the listing. - Add the file config.js, using your favorite editor. - $ vi config.js - Add the following content to config.js. This information will be displayed on the - plugin listing page in the UI: - (function (cloudStack) { - cloudStack.plugins.csMyFirstPlugin.config = { - title: 'My first plugin', - desc: 'Tutorial plugin', - externalLink: 'http://www.cloudstack.org/', - authorName: 'Test Plugin Developer', - authorEmail: 'plugin.developer@example.com' - }; -}(cloudStack)); - - - - Add a new main section. - Add the file csMyFirstPlugin.js, using your favorite editor. - $ vi csMyFirstPlugin.js - Add the following content to csMyFirstPlugin.js: - (function (cloudStack) { - cloudStack.plugins.csMyFirstPlugin = function(plugin) { - plugin.ui.addSection({ - id: 'csMyFirstPlugin', - title: 'My Plugin', - preFilter: function(args) { - return isAdmin(); - }, - show: function() { - return $('<div>').html('Content will go here'); - } - }); - }; -}(cloudStack)); - - - - Register the plugin. - You now have the minimal content needed to run the plugin, so you can activate the - plugin in the UI by adding it to plugins.js. First, edit the file: - $ cd cloudstack/ui/plugins -$ vi plugins.js - - Now add the following to plugins.js: - (function($, cloudStack) { - cloudStack.plugins = [ - 'csMyFirstPlugin' - ]; -}(jQuery, cloudStack)); - - - - Check the plugin in the UI. - First, copy all the plugin code that you have created so far to - /tomcat/webapps/client/plugins. Then refresh the browser and click Plugins in the side - navigation bar. You should see your new plugin. - - - Make the plugin do something. - Right now, you just have placeholder content in the new plugin. It's time to add - real code. In this example, you will write a basic list view, which renders data from - an API call. You will list all virtual machines owned by the logged-in user. To do - this, replace the 'show' function in the plugin code with a 'listView' block, - containing the required syntax for a list view. To get the data, use the - listVirtualMachines API call. Without any parameters, it will return VMs only for your - active user. Use the provided 'apiCall' helper method to handle the server call. Of - course, you are free to use any other method for making the AJAX call (for example, - jQuery's $.ajax method). - First, open your plugin's JavaScript source file in your favorite editor: - $ cd csMyFirstPlugin -$ vi csMyFirstPlugin.js - - Add the following code in csMyFirstPlugin.js: - (function (cloudStack) { - cloudStack.plugins.csMyFirstPlugin = function(plugin) { - plugin.ui.addSection({ - id: 'csMyFirstPlugin', - title: 'My Plugin', - preFilter: function(args) { - return isAdmin(); - }, - - // Render page as a list view - listView: { - id: 'testPluginInstances', - fields: { - name: { label: 'label.name' }, - instancename: { label: 'label.internal.name' }, - displayname: { label: 'label.display.name' }, - zonename: { label: 'label.zone.name' } - }, - dataProvider: function(args) { - // API calls go here, to retrive the data asynchronously - // - // On successful retrieval, call - // args.response.success({ data: [data array] }); - plugin.ui.apiCall('listVirtualMachines', { - success: function(json) { - var vms = json.listvirtualmachinesresponse.virtualmachine; - - args.response.success({ data: vms }); - }, - error: function(errorMessage) { - args.response.error(errorMessage) - } - }); - } - } - }); - }; -}(cloudStack)); - - - - Test the plugin. - First, copy all the plugin code that you have created so far to - /tomcat/webapps/client/plugins. Then refresh the browser. You can see that your - placeholder content was replaced with a list table, containing 4 columns of virtual - machine data. - - - Add an action button. - Let's add an action button to the list view, which will reboot the VM. To do this, - add an actions block under listView. After specifying the correct format, the actions - will appear automatically to the right of each row of data. - $ vi csMyFirstPlugin.js - - Now add the following new code in csMyFirstPlugin.js. (The dots ... show where we - have omitted some existing code for the sake of space. Don't actually cut and paste - that part): - ... - listView: { - id: 'testPluginInstances', - ... - - actions: { - // The key/ID you specify here will determine what icon is - // shown in the UI for this action, - // and will be added as a CSS class to the action's element - // (i.e., '.action.restart') - // - // -- here, 'restart' is a predefined name in &PRODUCT; that will - // automatically show a 'reboot' arrow as an icon; - // this can be changed in csMyFirstPlugin.css - restart: { - label: 'Restart VM', - messages: { - confirm: function() { return 'Are you sure you want to restart this VM?' }, - notification: function() { return 'Rebooted VM' } - }, - action: function(args) { - // Get the instance object of the selected row from context - // - // -- all currently loaded state is stored in 'context' as objects, - // such as the selected list view row, - // the selected section, and active user - // - // -- for list view actions, the object's key will be the same as - // listView.id, specified above; - // always make sure you specify an 'id' for the listView, - // or else it will be 'undefined!' - var instance = args.context.testPluginInstances[0]; - - plugin.ui.apiCall('rebootVirtualMachine', { - // These will be appended to the API request - // - // i.e., rebootVirtualMachine&id=... - data: { - id: instance.id - }, - success: function(json) { - args.response.success({ - // This is an async job, so success here only indicates - // that the job was initiated. - // - // To pass the job ID to the notification UI - // (for checking to see when action is completed), - // '_custom: { jobID: ... }' needs to always be passed on success, - // in the same format as below - _custom: { jobId: json.rebootvirtualmachineresponse.jobid } - }); - }, - - - error: function(errorMessage) { - args.response.error(errorMessage); // Cancel action, show error message returned - } - }); - }, - - // Because rebootVirtualMachine is an async job, we need to add - // a poll function, which will perodically check - // the management server to see if the job is ready - // (via pollAsyncJobResult API call) - // - // The plugin API provides a helper function, 'plugin.ui.pollAsyncJob', - / which will work for most jobs - // in &PRODUCT; - notification: { - poll: plugin.ui.pollAsyncJob - } - } - }, - - dataProvider: function(args) { - ... -... - - - - Add the thumbnail icon. - Create an icon file; it should be square, about 50x50 pixels, and named icon.png. - Copy it into the same directory with your plugin code: - cloudstack/ui/plugins/csMyFirstPlugin/icon.png. - - - Add the stylesheet. - Create a CSS file, with the same name as your .js file. Copy it into the same - directory with your plugin code: - cloudstack/ui/plugins/csMyFirstPlugin/csMyFirstPlugin.css. - - -

- http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/time-zones.xml ---------------------------------------------------------------------- diff --git a/en-US/time-zones.xml b/en-US/time-zones.xml deleted file mode 100644 index 6b3b64e..0000000 --- a/en-US/time-zones.xml +++ /dev/null @@ -1,137 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - Time Zones - The following time zone identifiers are accepted by &PRODUCT;. There are several places that have a time zone as a required or optional parameter. These include scheduling recurring snapshots, creating a user, and specifying the usage time zone in the Configuration table. - - - - - - - - Etc/GMT+12 - Etc/GMT+11 - Pacific/Samoa - - - Pacific/Honolulu - US/Alaska - America/Los_Angeles - - - Mexico/BajaNorte - US/Arizona - US/Mountain - - - America/Chihuahua - America/Chicago - America/Costa_Rica - - - America/Mexico_City - Canada/Saskatchewan - America/Bogota - - - America/New_York - America/Caracas - America/Asuncion - - - America/Cuiaba - America/Halifax - America/La_Paz - - - America/Santiago - America/St_Johns - America/Araguaina - - - America/Argentina/Buenos_Aires - America/Cayenne - America/Godthab - - - America/Montevideo - Etc/GMT+2 - Atlantic/Azores - - - Atlantic/Cape_Verde - Africa/Casablanca - Etc/UTC - - - Atlantic/Reykjavik - Europe/London - CET - - - Europe/Bucharest - Africa/Johannesburg - Asia/Beirut - - - Africa/Cairo - Asia/Jerusalem - Europe/Minsk - - - Europe/Moscow - Africa/Nairobi - Asia/Karachi - - - Asia/Kolkata - Asia/Bangkok - Asia/Shanghai - - - Asia/Kuala_Lumpur - Australia/Perth - Asia/Taipei - - - Asia/Tokyo - Asia/Seoul - Australia/Adelaide - - - Australia/Darwin - Australia/Brisbane - Australia/Canberra - - - Pacific/Guam - Pacific/Auckland - - - - - - http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/tools.xml ---------------------------------------------------------------------- diff --git a/en-US/tools.xml b/en-US/tools.xml deleted file mode 100644 index 8cddf28..0000000 --- a/en-US/tools.xml +++ /dev/null @@ -1,31 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - Tools - - - - - http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/topology-req.xml ---------------------------------------------------------------------- diff --git a/en-US/topology-req.xml b/en-US/topology-req.xml deleted file mode 100644 index f342ee4..0000000 --- a/en-US/topology-req.xml +++ /dev/null @@ -1,33 +0,0 @@ - - -%BOOK_ENTITIES; -]> - -

- Topology Requirements - - - - - - - - - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/translating-documentation.xml ---------------------------------------------------------------------- diff --git a/en-US/translating-documentation.xml b/en-US/translating-documentation.xml deleted file mode 100644 index 4d5e3d2..0000000 --- a/en-US/translating-documentation.xml +++ /dev/null @@ -1,38 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Translating &PRODUCT; Documentation - - There are two ways to translate the documentation: - - - Directly using the Transifex website and using their user interface. - Using the Transifex client and pushing your translated strings to the website. - - - Once a translation is complete, a site admin will pull the translated strings within the &PRODUCT; repository, build the documentation and publish it. - For instructions on how to use the Transifex website see http://sebgoa.blogspot.ch/2012/11/translating-apache-cloudstack-docs-with.html - For instructions on how to use the Transifex client to translate from the command line see http://sebgoa.blogspot.ch/2012/12/using-transifex-client-to-translate.html -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/troubleshooting-alerts.xml ---------------------------------------------------------------------- diff --git a/en-US/troubleshooting-alerts.xml b/en-US/troubleshooting-alerts.xml deleted file mode 100644 index 0efeb81..0000000 --- a/en-US/troubleshooting-alerts.xml +++ /dev/null @@ -1,57 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Alerts - The following is the list of alert type numbers. - -MEMORY = 0 -CPU = 1 -STORAGE =2 -STORAGE_ALLOCATED = 3 -PUBLIC_IP = 4 -PRIVATE_IP = 5 -HOST = 6 -USERVM = 7 -DOMAIN_ROUTER = 8 -CONSOLE_PROXY = 9 -ROUTING = 10// lost connection to default route (to the gateway) -STORAGE_MISC = 11 // lost connection to default route (to the gateway) -USAGE_SERVER = 12 // lost connection to default route (to the gateway) -MANAGMENT_NODE = 13 // lost connection to default route (to the gateway) -DOMAIN_ROUTER_MIGRATE = 14 -CONSOLE_PROXY_MIGRATE = 15 -USERVM_MIGRATE = 16 -VLAN = 17 -SSVM = 18 -USAGE_SERVER_RESULT = 19 -STORAGE_DELETE = 20; -UPDATE_RESOURCE_COUNT = 21; //Generated when we fail to update the resource count -USAGE_SANITY_RESULT = 22; -DIRECT_ATTACHED_PUBLIC_IP = 23; -LOCAL_STORAGE = 24; -RESOURCE_LIMIT_EXCEEDED = 25; //Generated when the resource limit exceeds the limit. Currently used for recurring snapshots only - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/troubleshooting-lb-rules-fails.xml ---------------------------------------------------------------------- diff --git a/en-US/troubleshooting-lb-rules-fails.xml b/en-US/troubleshooting-lb-rules-fails.xml deleted file mode 100644 index 6295534..0000000 --- a/en-US/troubleshooting-lb-rules-fails.xml +++ /dev/null @@ -1,39 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Load balancer rules fail after changing network offering - - Symptom - After changing the network offering on a network, load balancer rules stop working. - - - Cause - Load balancing rules were created while using a network service offering that includes an external load balancer device such as NetScaler, and later the network service offering changed to one that uses the &PRODUCT; virtual router. - - - Solution - Create a firewall rule on the virtual router for each of your existing load balancing rules so that they continue to function. - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/troubleshooting-recover-lost-virtual-router.xml ---------------------------------------------------------------------- diff --git a/en-US/troubleshooting-recover-lost-virtual-router.xml b/en-US/troubleshooting-recover-lost-virtual-router.xml deleted file mode 100644 index 12a5150..0000000 --- a/en-US/troubleshooting-recover-lost-virtual-router.xml +++ /dev/null @@ -1,46 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Recovering a Lost Virtual Router - - Symptom - A virtual router is running, but the host is disconnected. A virtual router no longer functions as expected. - - - Cause - The Virtual router is lost or down. - - - Solution - If you are sure that a virtual router is down forever, or no longer functions as expected, destroy it. You must create one afresh while keeping the backup router up and running (it is assumed this is in a redundant router setup): - - - Force stop the router. Use the stopRouter API with forced=true parameter to do so. - Before you continue with destroying this router, ensure that the backup router is running. Otherwise the network connection will be lost. - Destroy the router by using the destroyRouter API. - - Recreate the missing router by using the restartNetwork API with cleanup=false parameter. For more information about redundant router setup, see Creating a New Network Offering. - For more information about the API syntax, see the API Reference at API Reference. -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/troubleshooting-unable-to-deploy-vms.xml ---------------------------------------------------------------------- diff --git a/en-US/troubleshooting-unable-to-deploy-vms.xml b/en-US/troubleshooting-unable-to-deploy-vms.xml deleted file mode 100644 index 412b9bf..0000000 --- a/en-US/troubleshooting-unable-to-deploy-vms.xml +++ /dev/null @@ -1,39 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Unable to deploy VMs from uploaded vSphere template - - Symptom - When attempting to create a VM, the VM will not deploy. - - - Cause - If the template was created by uploading an OVA file that was created using vSphere Client, it is possible the OVA contained an ISO image. If it does, the deployment of VMs from the template will fail. - - - Solution - Remove the ISO and re-upload the template. - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/troubleshooting-unable-to-power-on-vm.xml ---------------------------------------------------------------------- diff --git a/en-US/troubleshooting-unable-to-power-on-vm.xml b/en-US/troubleshooting-unable-to-power-on-vm.xml deleted file mode 100644 index e037eda..0000000 --- a/en-US/troubleshooting-unable-to-power-on-vm.xml +++ /dev/null @@ -1,45 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Unable to power on virtual machine on VMware - - Symptom - Virtual machine does not power on. You might see errors like: - - - Unable to open Swap File - Unable to access a file since it is locked - Unable to access Virtual machine configuration - - - Cause - A known issue on VMware machines. ESX hosts lock certain critical virtual machine files and file systems to prevent concurrent changes. Sometimes the files are not unlocked when the virtual machine is powered off. When a virtual machine attempts to power on, it can not access these critical files, and the virtual machine is unable to power on. - - - Solution - See the following: - - VMware Knowledge Base Article -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/troubleshooting-working-with-server-logs.xml ---------------------------------------------------------------------- diff --git a/en-US/troubleshooting-working-with-server-logs.xml b/en-US/troubleshooting-working-with-server-logs.xml deleted file mode 100644 index fa0f78c..0000000 --- a/en-US/troubleshooting-working-with-server-logs.xml +++ /dev/null @@ -1,41 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Working with Server Logs - The &PRODUCT; Management Server logs all web site, middle tier, and database activities for diagnostics purposes in /var/log/cloudstack/management/. The &PRODUCT; logs a variety of error messages. We recommend this command to find the problematic output in the Management Server log:. - When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text. - - grep -i -E 'exception|unable|fail|invalid|leak|warn|error' /var/log/cloudstack/management/management-server.log - - The &PRODUCT; processes requests with a Job ID. If you find an error in the logs and you are interested in debugging the issue you can grep for this job ID in the management server log. For example, suppose that you find the following ERROR message: - - 2010-10-04 13:49:32,595 ERROR [cloud.vm.UserVmManagerImpl] (Job-Executor-11:job-1076) Unable to find any host for [User|i-8-42-VM-untagged] - - Note that the job ID is 1076. You can track back the events relating to job 1076 with the following grep: - - grep "job-1076)" management-server.log - - The &PRODUCT; Agent Server logs its activities in /var/log/cloudstack/agent/. -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/troubleshooting.xml ---------------------------------------------------------------------- diff --git a/en-US/troubleshooting.xml b/en-US/troubleshooting.xml deleted file mode 100644 index 570d02e..0000000 --- a/en-US/troubleshooting.xml +++ /dev/null @@ -1,35 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - Troubleshooting - - - - - - - - - http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/troublesht-dataloss-on-exp-primary-storage.xml ---------------------------------------------------------------------- diff --git a/en-US/troublesht-dataloss-on-exp-primary-storage.xml b/en-US/troublesht-dataloss-on-exp-primary-storage.xml deleted file mode 100644 index f9a6efc..0000000 --- a/en-US/troublesht-dataloss-on-exp-primary-storage.xml +++ /dev/null @@ -1,45 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Data Loss on Exported Primary Storage - - Symptom - Loss of existing data on primary storage which has been exposed as a Linux NFS server export on an iSCSI volume. - - - Cause - It is possible that a client from outside the intended pool has mounted the storage. When this occurs, the LVM is wiped and all data in the volume is lost - - - Solution - When setting up LUN exports, restrict the range of IP addresses that are allowed access by specifying a subnet mask. For example: - - echo “/export 192.168.1.0/24(rw,async,no_root_squash,no_subtree_check)” > /etc/exports - Adjust the above command to suit your deployment needs. - - More Information - See the export procedure in the "Secondary Storage" section of the &PRODUCT; Installation Guide - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/troublesht-mtn-mode-not-working-on-vCenter.xml ---------------------------------------------------------------------- diff --git a/en-US/troublesht-mtn-mode-not-working-on-vCenter.xml b/en-US/troublesht-mtn-mode-not-working-on-vCenter.xml deleted file mode 100644 index 764d188..0000000 --- a/en-US/troublesht-mtn-mode-not-working-on-vCenter.xml +++ /dev/null @@ -1,43 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Maintenance mode not working on vCenter - - Symptom - Host was placed in maintenance mode, but still appears live in vCenter. - - - Cause - The &PRODUCT; administrator UI was used to place the host in scheduled maintenance mode. This mode is separate from vCenter's maintenance mode. - - - Solution - Use vCenter to place the host in maintenance mode. - - - More Information - See - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/tuning.xml ---------------------------------------------------------------------- diff --git a/en-US/tuning.xml b/en-US/tuning.xml deleted file mode 100644 index 4f9dd01..0000000 --- a/en-US/tuning.xml +++ /dev/null @@ -1,33 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - Tuning - This section provides tips on how to improve the performance of your cloud. - - - - - - http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/ucs.xml ---------------------------------------------------------------------- diff --git a/en-US/ucs.xml b/en-US/ucs.xml deleted file mode 100644 index 885753a..0000000 --- a/en-US/ucs.xml +++ /dev/null @@ -1,132 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- - Using Cisco UCS as a Bare Metal Host - (Supported only for use in &PRODUCT; zones with basic networking.) - You can provision Cisco UCS server blades into &PRODUCT; for use - as bare metal hosts. The goal is to enable easy expansion of the cloud by leveraging the - programmability of the UCS converged infrastructure and &PRODUCT;’s knowledge of the cloud - architecture and ability to orchestrate. &PRODUCT; can - automatically understand the UCS environment and server profiles so &PRODUCT; administrators can - deploy a bare metal OS on a Cisco UCS. - An overview of the steps involved in using UCS with &PRODUCT;: - - Set up your UCS blades, profiles, and UCS Manager according to Cisco documentation - Register the UCS Manager with &PRODUCT; - Associate a profile with a UCS blade - Provision the blade as a bare metal host as described in - . - Provisioning a Bare Metal Host with Kickstart in the &PRODUCT; Installation Guide. - - -

- Registering a UCS Manager - Register the UCS Manager with &PRODUCT; by following these steps: - - Install the UCS hardware (blades) and UCS Manager according to the vendor's instructions. - Make a note of the following information: - - UCS manager IP address - UCS manager username - UCS manager password - - - Log in to the &PRODUCT; UI as administrator. - In the left navigation bar, click Infrastructure, then click Zones. - Click the name of a zone where Network Type is Basic. - Click the Compute and Storage tab. - Scroll down in the diagram and click UCS. - Click the Add UCS Manager button. - In the dialog box, provide a display name, then the IP address, username, and password - that you made a note of in step . - Click OK. - - &PRODUCT; will register the UCS Manager, then automatically discover the blades on this UCS Manager and add them to the resource pool. -

- Associating a Profile with a UCS Blade - Before associating a profile with a UCS blade, you must first do the steps in - . - - Log in to the &PRODUCT; UI as administrator. - In the left navigation bar, click Infrastructure, then click Zones. - Click the name of a zone where you have registered a UCS Manager. - Click the Compute and Storage tab. - Scroll down in the diagram and click UCS. - Click the name of the UCS Manager. - Click the Blades tab. - A list is displayed that shows the names of the blades that are installed under the selected manager. - In the Actions column, click the Associate Profile icon. - - - - - - attach-disk-icon.png: Attach Profile icon for UCS blade - - - In the dialog, select the name of the template for the profile you want to associate with this blade, then click OK. - The dropdown list in the dialog box lists the profile templates that are currently defined in the UCS Manager where this blade resides. - The list is refreshed any time you add or remove profile templates on the UCS Manager. - You might need to wait a few minutes for this operation to finish. - The operation might take a long time, depending on the complexity of the setup. - The timeout is 60 minutes. - - -

- Disassociating a Profile from a UCS Blade - - Log in to the &PRODUCT; UI as administrator. - In the left navigation bar, click Infrastructure, then click Zones. - Click the name of a zone where you have registered a UCS Manager. - Click the Compute and Storage tab. - Scroll down in the diagram and click UCS. - Click the name of the UCS Manager. - Click the Blades tab. - A list is displayed that shows the names of the blades that are installed under the selected manager. - Select the name of a blade that has been associated with a profile. - In the Actions column, click the Disassociate Profile icon. - - - - - - detach-disk-icon.png: Detach Profile icon for UCS blade - - - Click OK. - You might need to wait a few minutes for this operation to finish. - The operation might take a long time, depending on the complexity of the setup. - The timeout is 60 minutes. - -

- Synchronizing UCS Manager Changes with &PRODUCT; - At any time, &PRODUCT; users might directly - associate or dissociate blades on the Cisco UCS Manager, - and &PRODUCT; would not be aware of these changes. - Periodically, or whenever you become aware that such changes have been made, - you can force &PRODUCT; to synchronize itself with UCS Manager - in order to become aware of - any changes that are made manually. - - Log in to the &PRODUCT; UI as administrator. - In the left navigation bar, click Infrastructure, then click Zones. - Click the name of a zone where you have registered a UCS Manager. - Click the Compute and Storage tab. - Scroll down in the diagram and click UCS. - Click the name of the UCS Manager. - Click the Blades tab. - Click the Refresh Blades button. - Click OK. - You might need to wait a few minutes for this operation to finish. - The operation might take a long time, depending on the complexity of the setup. - The timeout is 60 minutes. - -

\ No newline at end of file http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/ui.xml ---------------------------------------------------------------------- diff --git a/en-US/ui.xml b/en-US/ui.xml deleted file mode 100644 index 94ea4ea..0000000 --- a/en-US/ui.xml +++ /dev/null @@ -1,29 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - User Interface - - - http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/update-iso-vm.xml ---------------------------------------------------------------------- diff --git a/en-US/update-iso-vm.xml b/en-US/update-iso-vm.xml deleted file mode 100644 index 98105f5..0000000 --- a/en-US/update-iso-vm.xml +++ /dev/null @@ -1,47 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -

- - Changing a VM's Base Image - Every VM is created from a base image, which is a template or ISO which has been created and - stored in &PRODUCT;. Both cloud administrators and end users can create and modify templates, - ISOs, and VMs. - In &PRODUCT;, you can change an existing VM's base image from one template to another, - or from one ISO to another. (You can not change from an ISO to a template, or from a - template to an ISO). - For example, suppose there is a - template based on a particular operating system, and the OS vendor releases a software patch. - The administrator or user naturally wants to apply the patch and then make sure existing VMs - start using it. Whether a software update is involved or not, it's also possible to simply - switch a VM from its current template to any other desired template. - To change a VM's base image, call the restoreVirtualMachine API command and pass in the - virtual machine ID and a new template ID. The template ID parameter may refer to either a - template or an ISO, depending on which type of base image the VM was already using (it must - match the previous type of image). When this call occurs, the VM's root disk is first destroyed, - then a new root disk is created from the source designated in the template ID parameter. The new - root disk is attached to the VM, and now the VM is based on the new template. - You can also omit the template ID parameter from the restoreVirtualMachine call. In this - case, the VM's root disk is destroyed and recreated, but from the same template or ISO that was - already in use by the VM. -

\ No newline at end of file http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/upgrade-virtual-router-with-service-offering.xml ---------------------------------------------------------------------- diff --git a/en-US/upgrade-virtual-router-with-service-offering.xml b/en-US/upgrade-virtual-router-with-service-offering.xml deleted file mode 100644 index dad1d90..0000000 --- a/en-US/upgrade-virtual-router-with-service-offering.xml +++ /dev/null @@ -1,36 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Upgrading a Virtual Router with System Service Offerings - When &PRODUCT; creates a virtual router, it uses default settings which are defined in a default system service offering. See . All the virtual routers in a single guest network use the same system service offering. You can upgrade the capabilities of the virtual router by creating and applying a custom system service offering. - - Define your custom system service offering. See . In System VM Type, choose Domain Router. - Associate the system service offering with a network offering. - See "Creating Network Offerings" in the Administrator's Guide. - See . - - Apply the network offering to the network where you want the virtual routers to use the new system service offering. If this is a new network, follow the steps in Adding an Additional Guest Network on page 66. To change the service offering for existing virtual routers, follow the steps in . - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/upload-existing-volume-to-vm.xml ---------------------------------------------------------------------- diff --git a/en-US/upload-existing-volume-to-vm.xml b/en-US/upload-existing-volume-to-vm.xml deleted file mode 100644 index 3cbfc34..0000000 --- a/en-US/upload-existing-volume-to-vm.xml +++ /dev/null @@ -1,112 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Uploading an Existing Volume to a Virtual Machine - Existing data can be made accessible to a virtual machine. This is called uploading a volume - to the VM. For example, this is useful to upload data from a local file system and attach it to - a VM. Root administrators, domain administrators, and end users can all upload existing volumes - to VMs. - The upload is performed using HTTP. The uploaded volume is placed in the zone's secondary - storage - You cannot upload a volume if the preconfigured volume limit has already been reached. The - default limit for the cloud is set in the global configuration parameter max.account.volumes, - but administrators can also set per-domain limits that are different from the global default. - See Setting Usage Limits - To upload a volume: - - - (Optional) Create an MD5 hash (checksum) of the disk image file that you are going to - upload. After uploading the data disk, &PRODUCT; will use this value to verify that no data - corruption has occurred. - - - Log in to the &PRODUCT; UI as an administrator or user - - - In the left navigation bar, click Storage. - - - Click Upload Volume. - - - Provide the following: - - - Name and Description. Any desired name and a brief description that can be shown in - the UI. - - - Availability Zone. Choose the zone where you want to store the volume. VMs running - on hosts in this zone can attach the volume. - - - Format. Choose one of the following to indicate the disk image format of the - volume. - - - - - Hypervisor - Disk Image Format - - - - - XenServer - VHD - - - VMware - OVA - - - KVM - QCOW2 - - - - - - - - URL. The secure HTTP or HTTPS URL that &PRODUCT; can use to access your disk. The - type of file at the URL must match the value chosen in Format. For example, if Format is - VHD, the URL might look like the following: - http://yourFileServerIP/userdata/myDataDisk.vhd - - - MD5 checksum. (Optional) Use the hash that you created in step 1. - - - - - Wait until the status of the volume shows that the upload is complete. Click Instances - - Volumes, find the name you specified in step 5, and make sure the status is Uploaded. - - -