Merge pull request #138 from cloudops/docs/mcdocs-66-vmware

docs/mcdocs-66-vmware

en/vmware-compute-service/vmware-compute-service.md

@@ -0,0 +1,3 @@
+---
+name: VMware Cloud Director
+---

en/vmware-compute-service/vmware-networking.md

@@ -0,0 +1,50 @@
+---
+title: "VMware: Networking"
+slug: vmware-networking
+---
+
+
+Networking is a critical part of any cloud infrastructure. This article introduces the basic concepts of networking in VMware, and the corresponding features in the user interface.
+
+All networking features are accessible via the **Networking** section of the selected VMware environment.
+
+## Detailed overview
+
+VMware provides a full set of virtual networking features. A basic, isolated network can be created with no other prerequisites. The network provides a DHCP server for automatically configuring devices that connect to the network, using an IP space that you define at creation time. You can also manually configure the interfaces connecting to the network, if desired. An isolated network will allow the creation of virtual machines that can communicate with each other, but they will have no connectivity to any other network. To be able to connect to other networks or to the public Internet, an edge gateway must be configured in your environment.
+
+The following different types of networks are supported:
+
+-   **Isolated**
+
+    The most basic networking mode, an isolated network provides connectivity between interfaces attached to it. Isolated provides no connectivity to the outside world. Only virtual machines within the same environment as a isolated network can connect to that network.
+
+-   **Routed**
+
+    This is also known as a NAT routed network. A routed network provides external connectivity along with NAT, firewall, and VPN services.
+
+
+## Network status
+
+VMware networks have the following states:
+
+-   **Realized**
+
+    The network has been created and is ready for use.
+
+-   **Pending**
+
+    The network configuration has been submitted and is waiting to begin realization.
+
+-   **Configuring**
+
+    The network configuration is currently being realized.
+
+-   **Realization failed**
+
+    The system was unable to realize the network configuration.
+
+-   **Unknown**
+
+    The current state of the network is not known.
+
+

en/vmware-compute-service/vmware-service-overview.md

@@ -0,0 +1,21 @@
+---
+title: "VMware: Service overview"
+slug: vmware-service-overview
+---
+
+
+## Summary
+
+CloudMC allows cloud operators to access and manage infrastructure and resources that have been deployed on a VMware Cloud Director service delivery platform. This article will introduce basic concepts of VMware and working with VMWare Cloud Director resources in CloudMC.
+
+## Detailed overview
+
+VMware Cloud Director enables enterprises to build private clouds and datacenters, which can be used to deploy cloud-based applications. CloudMC provides a unified interface to access a VMware platform and other services from a single portal. Through CloudMC, users can manage:
+
+-   [Networks](vmware-networking.md)
+-   [Virtual machines](vmware-virtual-machines.md)
+-   [Virtual applications](vmware-virtual-applications.md)
+-   [Storage](vmware-storage.md)
+
+Because CloudMC acts as a portal to VMware Cloud Director services, you may find that some operations appear to behave differently than when interacting with VMware directly. However, behind the scenes, all operations execute exactly as they normally would. Changes made to VMware entities in CloudMC will be reflected immediately in the actual resources.
+

en/vmware-compute-service/vmware-virtual-applications.md

@@ -0,0 +1,58 @@
+---
+title: "VMware: Virtual Applications"
+slug: vmware-vapps
+---
+
+
+A virtual application is a container of virtual machines which provide the infrastructure for a cloud-native application. This article discusses the concept of virtual applications and how they are managed in CloudMC.
+
+Virtual applications are listed under the **Virtual Applications** section of the selected VMware environment.
+
+## Detailed overview
+
+A virtual application serves as a container for managing and executing an application as a single entity. It is composed of virtual machines that have been created as part of that virtual application, either from the **Virtual Applications** page or from the **Add Virtual Machine** wizard.
+
+A virtual application is created with its own network, which allows the virtual machines in the application to communicate with each other. A virtual application's network may be isolated or routed. It is automatically destroyed when the virtual application is deleted.
+
+## Virtual application status
+
+-   **Powered on**
+
+    All of the virtual machines assigned to this virtual application are powered on.
+
+-   **Partially powered off**
+
+    During the normal boot process, a virtual application will briefly enter this state.
+
+-   **Partially running**
+
+    One or more virtual machines assigned to this virtual application is either suspended or powered off.
+
+
+## Virtual application list
+
+Virtual applications are listed under the **Virtual Applications** section of the selected VMware environment.
+
+![A screenshot of the VMware virtual applications page, with numbered dots indicating features of interest](/assets/vmware-vapps-list-en.png)
+
+1.  **List of virtual applications**
+
+    A list of all virtual applications in the selected environment appears here in this area.
+
+2.  **Search box**
+
+    Type in the search box to filter the virtual applications list. The system will search through the name field, as well as the internal UUID, and returns any virtual application that matches the string in the search box.
+
+3.  **Add virtual application**
+
+    Clicking this button will open the **Add virtual application** wizard.
+
+4.  **Virtual application row**
+
+    Each row includes the name of the virtual application, its status, the total amount of vCPUs, memory, and storage provisioned among all the virtual machines in the virtual application, and a couple of the number of virtual machines in the application. Click on an entry to navigate to a page with configuration details and a list of all operations for that individual virtual application.
+
+5.  **Hidden Actions menu**
+
+    Each entry in the virtual applications list has a Hidden Actions menu. Click on the Hidden Actions menu to access a list of frequently-used operations for the virtual application.
+
+

en/vmware-compute-service/vmware-virtual-machines.md

@@ -0,0 +1,87 @@
+---
+title: "VMware: Virtual Machines"
+slug: vmware-vms
+---
+
+
+Virtual machines are a fundamental type of infrastructure provided by VMware Cloud Director. This article discusses the concept of virtual machines and how they are managed in CloudMC.
+
+Virtual machines are listed under the **Virtual Machines** section of the selected VMware environment.
+
+## Detailed overview
+
+Similar to other cloud platforms, a virtual machine is an abstraction of a physical computer, running a complete operating system and providing virtualized devices such as storage, network interfaces, and consoles. Once a virtual machine is provisioned, it can be used to execute the various components of your applications.
+
+A virtual machine can be based on a pre-defined image, called a template, or you can install and configure your own operating system from an ISO. VMware offers multiple pre-defined offerings of vCPU and memory, or you may define your own according to your business needs.
+
+Every virtual machine is created with a hard disk already attached. The size of this disk is determined by the template selected at configuration time. Additional storage may be created and attached to a virtual machine, as needed.
+
+When deploying a new virtual machine, it must be done so within an existing network. If there is no network in the active environment, you will not be allowed to add a new virtual machine.
+
+## Virtual machine status
+
+Virtual machines has have three main power states:
+
+-   **Powered on**
+
+    The virtual machine is running and able to execute its operating system and other processes. In this state either the Web console or remote console are available.
+
+-   **Powered off**
+
+    The virtual machine is stopped and no processes are executing. This is the only state from which a virtual machine may be deleted.
+
+-   **Suspended**
+
+    VMware can halt the execution of a virtual machine in the powered on state and save all current memory to disk. A virtual machine that has been suspended can be returned to the powered on state and resumes execution from the point at which it was suspended.
+
+
+A virtual machine may also transition through the following sub-states:
+
+-   **Inconsistent state**
+
+    A virtual machine in this state has been modified directly within VMware vSphere instead of through CloudMC, and is now out of synchronization with VMware Cloud Director. Power off the virtual machine and then power it back on to return it to a normal status.
+
+-   **Unresolved**
+
+    During creation.
+
+-   **Powering off**
+
+    Is being powered off
+
+-   **Deletion**
+
+    Is being deleted
+
+-   **Unknown**
+
+    Part of the deletion process
+
+
+## Virtual machines list
+
+Virtual machines are listed under the **Virtual Machines** section of the selected VMware environment.
+
+![A screenshot of the VMware Virtual Machines page, with numbered dots indicating features of interest](/assets/vmware-vms-list-en.png)
+
+1.  **List of virtual machines**
+
+    A list of all virtual machines in the selected environment appears here in this area.
+
+2.  **Search box**
+
+    Type in the search box to filter the virtual machines list. The system will search through the Name field, as well as the internal UUID, and returns any virtual machine that matches the string in the search box.
+
+3.  **Add virtual machine**
+
+    Clicking this button will open the **Add virtual machine** wizard.
+
+4.  **Virtual machine row**
+
+    Each row includes the name of the virtual machine, its current status, the amount of vCPUs and memory provisioned for this virtual machine, the name of the template which was used to create it, and if the virtual machine has been assigned to a virtual application, its name will also appear here. Click on an entry to navigate to a page with configuration details and a list of all operations for that individual virtual machine.
+
+5.  **Hidden Actions menu**
+
+    Each entry in the virtual machines list has a Hidden Actions menu. Click on the Hidden Actions menu to access a list of frequently-used operations for the virtual machine.
+
+

en/vmware-compute-service/vmware-vmware-add-a-network.md

@@ -0,0 +1,59 @@
+---
+title: "VMware: Add a network
+slug: vmware-add-a-network
+---
+
+
+## About this task
+
+This article will guide you through the process of adding a new network to a VMware environment. The CloudMC interface provides a single-page wizard for selecting and deploying a new network configuration.
+
+## Before you begin
+
+-   Your VMware environment must already exist
+-   To create a routed network, you must have an edge gateway already configured
+
+## Procedure
+
+1.  Navigate to the desired environment. The **Virtual Machines** page appears.
+
+2.  Click on the **Networking** tab.
+
+3.  Click on the **Add Network** button. The **Add Network** wizard appears.
+
+4.  Configure the new network:
+
+    1.  Enter a name into the **Name** field, or accept the default.
+
+    2.  *\(Optional\)* Enter a description into the **Description** field.
+
+    3.  Enter an IP address in CIDR format for the gateway into the **Gateway CIDR** field.
+
+        The system will interpret this entry for network number and subnet mask and use them to configure the network address and size. The IP address itself will be automatically assigned to the gateway that will be created for this network.
+
+    4.  Select the desired type of network from the **Network Type** popup menu.
+
+        To provide external connectivity to your network, choose **Routed**. You will be asked to specify an edge gateway from the **Edge Gateways** popup menu. If no edge gateway is configured for this environment, the new network will be unable to connect to the public Internet.
+
+        If you do not need external connectivity for your network, choose **Isolated**. This is useful for networks that have privileged or sensitive information, or for compliance with access restrictions and other business rules.
+
+    5.  Enter one or more IP addresses, or IP ranges, into the **Static IP Pools** field to reserve for static assignment.
+
+        These addresses will not be offered by the new network's DHCP server. This is useful for manually assigning IP addresses to interfaces on the network. All of the addresses must be within the address space of the new network, as specified in the **Gateway CIDR** field.
+
+        You may enter a single IP address or a single contiguous range \(specify the lowest and highest IP addresses in the range, separated by a hyphen\). To specify multiple individual IP addresses or ranges, use the **+** button to reveal additional input fields.
+
+    6.  *\(Optional\)* To override the default primary \(and, if desired, secondary\) DNS servers that will be offered by the DHCP server, enter the IP addresses of your name servers into the **Primary DNS** and **Secondary DNS** fields.
+
+5.  Click the **Submit** button.
+
+
+## Results
+
+-   The network with the specified configuration is realized in the active environment
+-   The address space, network size, and gateway IP address are as specified in the **Gateway CIDR** field
+-   The network is listed in the **Networking** tab
+
+-   **[Example: Add a network](vmware-example-add-a-network.md)**  
+
+

en/vmware-compute-service/vmware-vmware-add-a-virtual-application.md

@@ -0,0 +1,3 @@
+
+## About this task
+

en/vmware-compute-service/vmware-vmware-add-a-virtual-machine.md

@@ -0,0 +1,47 @@
+
+## About this task
+
+This article will guide you through the process of adding a new virtual machine to a VMware environment.
+
+## Before you begin
+
+-   You must have a network already realized in your VMware environment
+
+## Procedure
+
+1.  Navigate to the desired environment. The **Virtual Machines** page appears.
+
+2.  Click on the **Add Virtual Machine** buttton. The **Add Virtual Machine** wizard appears.
+
+3.  Enter a name for the new virtual machine in the **Name** field, or accept the default.
+
+4.  To have the virtual machine automatically power on at creation time, mark the **Power On** checkbox.
+
+5.  If you wish to have the virtual machine be a part of an existing virtual application, select the desired application from the **Virtual Application** popup menu.
+
+6.  Select from the **Network** popup menu which network to attach the new virtual machine to, or accept the default.
+
+7.  Select the manner in which to configure the new virtual machine using the **Type** popup menu:
+
+    1.  To configure a virtual machine from a template using predefined configurations, select **From Template**.
+
+        You will be able to select from a set of templates with various operating systems and versions already installed. Additionally, the default vCPU and memory sizes may be overridden by making a selection from the **VM Sizing Policy** popup menu.
+
+    2.  To configure a virtual machine with your own settings, select **Custom**.
+
+        For vCPU and memory sizes, use the **VM Sizing Policy** popup menu to select from a set of predefined offerings, or select **System Default** to enter your own settings \(limited by the system defaults defined by your administrator\).
+
+        For the operating system, first identify the type of operating system that you will install on the new virtual machine, and then select the corresponding ISO image to attached to the virtual machine at creation time from the **Boot Image** popup menu. You may also choose **None** and no ISO will be attached to the new virtual machine, useful for network-boot scenarios.
+
+8.  Click the **Submit** button to create the new virtual machine.
+
+
+## Results
+
+-   The virtual machine is created using the specified settings
+-   If **Power On** was selected, the system starts the virtual machine immediately after creating it
+-   The virtual machine is listed in the **Virtual Machines** screen
+
+-   **[Example: Add a virtual machine](vmware-example-add-a-virtual-machine.md)**  
+
+

layout.yaml

@@ -86,6 +86,16 @@ categories:
       - aws-add_a_subnetwork.md
       - aws-add_an_instance.md
       - aws-add_a_volume.md
+- category: vmware-compute-service
+  icon: fa fa-cloud
+  articles:
+      - vmware-service-overview.md
+      - vmware-networking.md
+      - vmware-virtual-machines.md
+      - vmware-virtual-applications.md
+      - vmware-vmware-add-a-network.md
+      - vmware-vmware-add-a-virtual-machine.md
+      - vmware-vmware-add-a-virtual-application.md
 - category: object-storage-service
   icon: fa fa-hdd-o
   articles: