CloudPlatform Advanced Networking Survival Guide

CloudPlatform Advanced Networking Survival Guide

10:42 AM
CloudPlatform Advanced Networking Survival Guide -

This position is based on my own experience and understanding of CloudPlatform, began originally as a document I created after being charged to install an advanced environment CloudPlatform. I am not an expert on CloudPlatform but we hope this guide will be able to help people come to terms with the fundamentals.

This guide is designed to help people who are familiar with the basic principles of networks and a basic understanding of CloudPlatform building blocks (Zones, Pods, clusters, hosts)

He will present: -.

  • differences between the two types of networks CloudPlatform
  • The different types of traffic you encounter in CloudPlatform
  • The details you need before everything pass
  • what you'll need to have before starting.
  • A short walkthrough to get started on the Advanced Setup wizard.

differences between Basic and Advanced Networking

With CloudPlatform you have two options for networking, basic and advanced, it is set when the zone is first installed and can not be changed once the zone is created. The main difference is the advanced networking adds features such as isolation and network load balancing. (A full list can be found online in the official guide advanced installation)

  • Basic

    The following is a basic network, as you can see there is only one subnet with all machines connecting to this single subnet, the separation of tenants is achieved through the use of security groups (firewall and IP address filtering).

    the virtual router in this configuration is mainly used for tasks such as DHCP / DNS / BOOTP, a complete list of services that can be run on this router can be found online in the installation of CloudPlatform guide.

  • Advanced

    This installation is a bit more complicated as shown in the diagram below, the host servers using one or more network and VLANs cards to separate network. While certainly more complicated that offers additional features, for example using virtual routers as load balancers, NAT, etc.

We first examine describing the different types of traffic, VLANs and subnets used in advanced CloudPlatform network.

traffic, VLANs and Subnets

this section will present the 4 different types of traffic within CloudPlatform, this should give you a better idea of ​​what is needed for a typical installation CloudPlatform. Traffic types are: -

  • Management
  • Storage
  • Public
  • Guest (Detached shared)

the following sections detail the requirements for a single pod (usually a server rack) in an area: -

  • management

    These VLANs are used to access the different hypervisors our management interfaces within the pod and where we will run the system virtual machines (ie proxies of the console or secondary VM Storage).
    Ideally we will need at least one accessible VLAN (routed) per pod, but you have the ability to use a large VLAN to cover all your pods.

    • VLAN pod


      for this example, we have a pod with a single management VLAN with a rout / 24 subnet ( gateway xxx1 / 24), all hypervisors (VMware and XenServer) use static IP addresses within this network in xxx100-199 range.
      We have also placed the storage on the same VLAN as the two can be combined (see store for details)

    • VLAN Zone

      for this example we have a single management VLAN with a rout / 24 subnet (gateway to xxx1 / 24) for all pods. We divide u all hypervisors (VMware and XenServer) use static IP addresses within this network in xxx100-199 range.

      We have also placed the storage on the same VLAN as the two can be combined (see store for details)

  • storage

    as shown in our memory of the previous examples can be run on the same VLAN as the management traffic, but it can also be run on its own dedicated VLAN.
    This is to reduce congestion between traffic management and access to storage while reducing the need to route traffic from VLAN. Although this traffic can be routed, we recommend placing your storage on the same VLAN to improve performance.

  • Public

    These VLANs will be used to provide IP addresses available to the public in the whole area, default CloudPlatform uses virtual routers with IP addresses to provide public services such as virtual private networks and NAT access to their remote customer networks.

    for our example, we have been awarded a range of addresses on a VLAN DMZ, it is a / 24 subnet, a default gateway. We need to specify an address range for it to use, we'll use two zones, so I've only used the lower half of the area for that area.

  • isolated Guest

    There are two types of customer traffic, isolated and shared the guest (isolated) VLANs are a variety of non-routed VLANs example (1000-1500) CloudPlatform resume these VLANs that the customer VLANs are created, they then provide a private network for users to run virtual machines. It will also automatically create a virtual router connecting networks between public and guests.

    Some network deals can be adapted in the menu offerings in the main screen, for example, if we do not want to enable DHCP / DNS / NAT we can the off.

  • Guest Shared

    The guest (shared) VLANs are a range of VLANs routed which, unlike the networks of remote clients that are specific tenants, they are shared between tenants. By default, we must provide the gateway router, but also creates the virtual router that provides the remaining services.

Now we have described the traffic details, we can move to the collection of information required for your CloudPlatform

details

as you go through this section, we recommend filling the sheet CloudPlatform Preperation seal

naming conventions

Before starting the installation of any software we must address the naming conventions, it is important to do things, not only does not promote group elements logically, it will also save you time and energy later if you need to identify The problems.

Important

This is one of the most common things that people tend to overlook, think about this before you do anything else.

CloudPlatform consists of the following groups, we can use to logically decompose eg

* If you use multiple types of hypervisors
names + host is processed by your internal DNS for example LSB_R4_33.yourdomain.com

Note that the host name will vary slightly for other naming conventions, it is because it is only important to know where it is in the rack / pod (issue) we can change its group. or hypervisor

Zone Type - This guide covers the installation without advanced security groups

Zone Configuration

takes the first screen the general details of CloudPlatform , they appear. be some pretty basic details but it is important to put some thought into them. The table below gives an example of the necessary information which we will expand on

  • Name -. The name of the area we create, this may be the full name to increase readability. For example. . London South Bank / New York
  • internal and external DNS servers - The addresses of the interior and external DNS servers, we will prepare in the next Preperation section. These must be accessible by the various internal and external virtual machines, for example using a public DNS service like Google DNS for external and your own internal DNS for your machines
  • Guest CIDR -. CIDR details to be used for all individual customer networks, when an isolated VLAN is created that CIDR will be used.
    I recommend using a CIDR RFC1918 which is not used in your internal networks as it will help to identify the traffic if it "leaks" in your internal networks

Network Setup

in an advanced installation, we must consider the different networks, they should be planned and created before beginning the installation of CloudPlatform.

configuration network > physical Networks

this is based on the number of network adapters servers have, this is set by Zone if some servers have two NICs and the rest have 4 you can never have 2 physical networks

  • traffic types of physical networks -. We need to specify which traffic will connect to which NIC, online guides can give some guidance on the types of traffic that regroup. (For example, the management and storage traffic on a network card and clients and the public on the other.)
  • physical network names - This is a friendly label used to group the types of traffic CloudPlatform within your web console does not bind traffic to a specific network adapter, but helps to visually aggregate traffic to the administration so that they know what traffic flows on which networks.For physical Example: -
    • Two NPI - "internal (blue wire)" and "external (Yellow wiring)"
    • Four NPI - "management (blue cabling)", "Storage (Red cabling)", " public (green cabling) "and" invited (yellow cabling) "
  • traffic labels - These labels are important, it is how we specify which NIC each type of traffic use. These labels must match the labels we assign individual NICs on the hosts. We will specify the VLAN and network details at a later stage
    For example :. "Internal" / (2 NPI) "external" or "storage" / "management" / "public" / "Guest" (4 NPI)
    Please refer to the " Prepare network labels" section on how to set network labels on the hosts.

Network Configuration> Public Traffic

here we will specify the details for public traffic, if necessary, we can specify multiple public networks. This network will route traffic accessible to the public either address a public IP subnet specified by your ISP or your own internal network range

  • Gateway and Netmask -. The IP gateway address and mask of the range
  • VLAN - VLAN iD for the public traffic
  • Start and End IP addresses - the beginning and End IP addresses to use for public IP addresses
    [Important1945023]

    This is the first VLAN (s) you install, it / they will bring the public traffic within your network.

Network Setup> Pod

We will need details for the first pod to add to your area

  • Pod Name -. This is a label for your pod, it is best to follow your naming convention such as if it is a rack using his number (for example, LSB-P4)
  • information management network - details your management network as the gateway, Netmask, Home and End IP addresses. This network will contain all of your host machines, virtual management machines that are created and (if you use the storage on your VLAN management) IP addresses of storage
    Important

    This is the second network (s), we will need to create, see the VLAN management section for details on how to divide it.

    • We recommend that the your native VLAN management VLAN for the respective switches .li>
    • These VLANs must be accessible by your management server (VLAN Routing) li >
    • the host static IP addresses (either set manually or DHCP reservations)
    • We used the position in the rack to determine the static address such XXX112 = 12 slot in XXX130 rack = 30 slot in the rack
    • Make no overlap between your range and host IP addresses.
    • If you combine traffic management and storage, storage devices can be in a different subnet, but it is not recommended because it means that we should carry storage traffic.

Network Setup> Guest Traffic

(isolated) -. here we will specify a VLAN range for use by customers of networks, default CloudPlatform will create virtual routers so that these VLANs must be non-routed and shared among all pods in the area

Important

This is the third set of networks, we need to create, they must be accessible to all pods in the area (all switches with the area must be capable of carrying VLANs)

Network Setup> storage traffic

that storage traffic is optional, if you do not use this to skip this section.

We will specify the details for the storage traffic, if necessary, we can specify multiple storage networks. This network storage traffic transport be it a public address IP subnet specified by your ISP or your own internal network range

  • Gateway and Netmask -. The IP gateway address and mask of the range
  • VLAN - VLAN iD for the public traffic
  • Start and End IP addresses -. the beginning and ending IP addresses to use for the public IP addresses

Add Resources> Cluster

We'll add the first cluster, host and storage in our area; we start with the name Clusters

  • Cluster name -. Using our predefined naming conventions, specify the name of the cluster that you add. If you are using VMware, it must exactly match the name you used in vCenter. If you add a XenServer host you can skip the following sections which relate to other hypervisors such as VMware managed centrally
  • vCenter host, username and password - the vCenter server FQDN / IP address, the user name of an administrator and password
  • Datacenter -. the name of the VMware Datacenter in which you placed the cluster

Add Resources> Host

The host details (VMware notes will not work this section as it gets details of the specified vCenter server in the previous section). The hostname / DNS address must point to the management network adapter on the host.

Add Resources> Primary Storage

This depends on the hypervisor you use will vary and as such, see online how to configure different types. The most common are NFS / iSCSI / VMFS but there are others such as Fibre Channel.

Important

You will need to create these actions, each group has its own primary storage space, so if you have 5 clusters you will need 5 storage operations. This is the equivalent of shared storage pools XenServer or VMware datastores for clusters.

Add Resources> Secondary Storage

These are the secondary storage details, it only supports NFS at this stage.

Important

Again, you will need to create these actions, each Zone has at least one secondary storage, so if you have two areas, you will need 2 storage operations. This storage is used to hold the various iso and models you'll be using.

This is all the information we need we can start now.

Preparation

This section will provide an overview of what we will need to prepare before starting the installation and configuration

  • wiring

    A good code of practice is to ensure that all wiring is the same for all servers in the cluster.

    Important

    If you are bonding NICs you must ensure that all cluster servers are wired in the same way that the Cluster will duplicate the network configuration from the first host.

  • Switches

    These are important, as our CloudPlatform with advanced networks carry multiple VLANs we must define the network ports for trunked on the respective switches

    Note :. all VLANs we will use will be shared among all hosts to have to be enabled on all switches.

    You will also need to create own VLANs that we identified when passing through the details section.

  • DNS

    You will need to create at least one DNS server on your internal network, it can be used for your external DNS as well, but you must ensure it can be reached by your virtual machines in your guest network. In a production environment, you would probably set for internal networks and other external DNS.

  • Install OS and software

    This is where we recommend that you follow the installation guide CloudPlatform, install the cloud management software or on a machine dedicated or as a virtual machine on a hypervisor
    Important

    We found an issue where installing CentOS on XenServer using the "other installation media "template on XenServer brings to install only as a 100Mbps NIC rather than a 1Gbps meaning the CloudPlatform not working properly that the connection is not fast enough. (The minimum requirement for CloudPlatform is 1Gbps)

    The following list details what you need to install before you can proceed with the configuration CloudPlatform. Instructions can be found in the CloudPlatform online

    * Can be installed on the management server

  • [1945009Guide"Installationavancée"] Prepare labels network

    Each type of traffic must be said that the network card to use on servers, we do this using the labels in the detail section. The first hypervisor (In our example, we'll use the XenServer)

    Select the appropriate network, click Properties, change its label. Do this for all networks.

We are now ready to start putting all the pieces together.

Installation

We have now placed all the pieces we need in the right order, we'll put it all together and build a Cloud. This section will get you started, using what you have written, you should have more than enough to start.

  • Login and passwords

    The first thing we must do is to connect to our server and change user names and default passwords

    • default connection

      using a local Web browser such as Internet Explorer, log on CloudPlatform console using the following information by default : -

      URL http: // : 8080 / customer
      username administration
      Password Password

    • Welcome

      screen

      is where we would normally install the basic version of CloudPlatform, but we want to install the advanced version. Read and acknowledge the license agreements, when presented with the choice of continuing to use the basic version, click I used CloudPlatform before exit install.

    • Admin Password

      We are now the main dashboard CloudPlatform, when it is empty we do not even anything configured. First though, we need to change the default administrator password, this is done by clicking on Accounts> Administration> Users> Admin Then select the key icon to change your password .

In this area, we can also create new admin users and standard users, limit the number of virtual machines or public IP addresses that they can use with many more options. I can recommend taking a look through the available options.

  • Creating a Zone

    Select Infrastructure tab, it currently is empty we have added anything to this management server, we will now go ahead and create the Zone. This is done by Click Other under tile areas and Add Zone.

  • Use the information collected

    We can now use the table, we finished installing the CloudPlatform.

I hope this helps at least guide someone in the right direction, if you spot any errors feel free please let me know and I can the correct.

Next
« Prev Post
Previous
Next Post »
0 Komentar

Subscribe to: Post Comments (Atom)