Designing CloudX Solution using Mirantis Fuel OpenStack Software

Version 10

    This post is aim to spread the design considerations of CloudX solution when using Mirantis Fuel software package (OpenStack).

     

    References

     

    What is CloudX?

    CloudX is reference architecture for an efficient cloud infrastructure that makes use of open source cloud software, such as
    OpenStack, while running on Mellanox interconnect technology. CloudX utilize off-the-shelf building blocks (servers, storage, interconnect and software) to form flexible and cost-effective private, public, and hybrid clouds. In addition, it incorporates virtualization with high-bandwidth and low-latency interconnect solutions while significantly reducing data center costs. Built
    around the interconnect technology of 40Gb/s and 56Gb/s InfiniBand and Ethernet, CloudX provides the fast data transfer and most effective utilization of computing, storage and Flash SSD components.

     

    What is Fuel?

    Fuel is a Mirantis OpenStack distributions in a single commercially supported package. Click here for additional details.

     

     

    Recommended Hardware

     

    ComponentQuantityDescription
    Fuel node (master)1

    Intel server, 2 Gb Eth Ports, >4 cores CPU, >=8GB RAM, 0.5 TB SATA HDD.

    Compute nodes

    2-32

    Intel PCI-Ex Gen-3 server, at least one  8x PCI-Ex 3 slot, 2 Gb Eth Ports, >4 cores CPU x 2, >=128GB RAM RAM, 0.5 TB SATA HDD, SRIOV support in the BIOS.

    Network adapter: ConnectX-3 PRO VPI Dual Port  (P/N MCX354A-FCCT)

    Controller (and network) node

    1

    Intel PCI-Ex Gen 3 server, at least one 8x PCI-Ex 3 slot, >2 x 1 Gb Eth Ports, >4 cores CPU x 2, >=32 GB RAM, 1 TB SAS HDD, SRIOV support in the BIOS.

    Network adapter: ConnectX-3 PRO VPI Dual Port  (P/N MCX354A-FCCT)

    Ethernet switch1-2Mellanox SX1036 40/56Gb 36 port Ethernet.
    Management (PXE), Public switch1-21Gb/s switch.

    Note: The management switch and the public switch could be one switch.

    Cables

    FDR InfiniBand/56GbE copper cables up to 2m. P/N  MC2207130-XXX.

     

    Rack Design
    There are many options to design the rack. Each IT manager can take his own considerations with available rack space, cable length network location and so on.

     

    Basic Topology to support Mirantis Fuel 4.1
    Fuel3.png

     

    Basic Topology to support Mirantis Fuel 5.1

    5.1 arch.png
    Networks:

    1. Public Network

    • This network enables VMs and hypervisors to communicate externally (internet)
    • It uses 1GbE port on the servers.
    • The IP range of this network is split to two parts:
      • Floating IP network range: The range of IP addresses to be used for the VM external connectivity.
      • Public IP range: The range of IP addresses to be used for the hypervisors and hosts.

    2. Admin (PXE) Network:

    • This network (AKA the "internal" network) is used for Hypervisor PXE boot, OpenStack installation and Hypervisor OS access.
    • It uses the 1GbE port on the servers.
    • This network should have access from company LAN.
    • After FUEL installation the OpenStack dashboard is accessible from both Public network and the Admin (PXE) network.

    3. Private Network

    • This network is used for communication between tenant VMs. Each tenant may have several networks.
    • In case connectivity is required between networks own by the same tenants, the Network node provides the
      routing.
    • It is using the high speed network (40/56GbE) interface
    • It is recommended to use this network over port #1 in the ConnectX Pro adapter (via VLAN)
    • Note: Fuel 4.1 is based on OpenStack ‘Havana’ which does not support more than one network technology, that means that all the private networks in the OpenStack deployment will be using Mellanox Neutron agent which is based on VLANs assigned to VFs (Virtual functions/ SRIOV). It is not relevant for Fuel 5.1.

    4. Management Network

    • This network is used for the communication between the Controller, Storage and Hypervisors.
    • It uses the high speed network (40/56Gb) interface.
    • It is recommended to connect the servers via port #1 in the ConnectX-3 Pro adapter (via VLAN)

    5. Storage Network

    • This network is used for tenant storage services.
    • Block storage based on iSER transport is provided by the hypervisors using the high speed network (40/56Gb).
    • For Fuel 4.1 It is recommended to connect all hypervisors and storage nodes are connected to it via port #2 in the ConnectX-3 pro adapter.
    • For Fuel 5.1 It is recommended to connect all hypervisors and storage nodes are connected to it via port #1 in the ConnectX-3 pro adapter.

    6. BMC (IPMI/iLO) Network

    • It is recommended to setup BMC network. It is out-of-scope of this post.

     

    Example:

     

    NetworkSubnet/MaskGatewayVLAN IDNotes
    Admin (PXE)10.142.10.0/24N/A500 (1G switch)
    Public10.7.208.0/2410.7.208.1

    69 (1G switch)

    Public IP range 10.7.208.20-100 (hypervisors, storage, controller, Fuel node)

    Floating IP range 10.7.208.101-200 (VMs)

    Management192.168.0.0/24N/A3 (40/56Gb/s switch)
    Storage192.168.1.0/24N/Auntagged (mapped to vlan 2 in the 40/56Gb/s switch)

     

    Fuel GUI Network Setting Example:

    40.PNG.png

     

    41.PNG.png

     

    GUI Interface Configuration Example (Fuel 4.1):


    34.PNG.png

     

    Installation and Configuration: