User Tools

Site Tools


joid:b_installguide

This is an old revision of the document!


Deploy JOID in your LAB:

Bare Metal Installations:

Requirements as per Pharos:

Networking:

minimum 2 networks ( 1 for Admin network with gateway to access external network and other for public network to consume by tenants for floating ips) JOID support multiple isolated networks for data as well as storage. Based on your network options for Openstack.

Minimum 6 physical servers.

1. Jump Host server:

Minimum H/W Spec needed
 CPU cores: 16
 Memory: 32 GB
 Hard Disk: 1(250 GB)
 NIC: eth0(Admin, Management), eth1 (external network)
 

2. Control Node Servers (minimum 3):

 Minimum H/W Spec
 CPU cores: 16
 Memory: 32 GB
 Hard Disk: 1(500 GB)
 NIC: eth0(Admin, Management), eth1 (external network)

3. Compute Node Servers (minimum 2):

 Minimum H/W Spec
 CPU cores: 16
 Memory: 32 GB
 Hard Disk: 1(1 TB) this includes the space for ceph as well
 NIC: eth0(Admin, Management), eth1 (external network)

NOTE: Above configuration is minimum and for better performance and usage of the Openstack please consider higher spec for each nodes.

Make sure all servers are connected to top of rack switch and configured accordingly. No DHCP server should be up and configured. Only gateway at eth0 and eth1 network should be configure to access the network outside your lab.

Jump Node configuration:

1. Install Ubuntu 14.04 LTS server version of OS on the nodes. 2. Install the git and bridge-utils packages on the server and configure minimum two bridges on jump host:

brAdm and brPublic cat /etc/network/interfaces # The loopback network interface auto lo iface lo inet loopback

iface eth0 inet manual

auto brAdm iface brAdm inet static

      address 10.4.1.1
      netmask 255.255.248.0
      network 10.4.0.0
      broadcast 10.4.7.255
      gateway 10.4.0.1

# dns-* options are implemented by the resolvconf package, if installed

      dns-nameservers 10.4.0.2
      bridge_ports eth0

auto brPublic iface brPublic inet static

      address 10.2.66.2
      netmask 255.255.255.0
      bridge_ports eth2

NOTE: If you choose to use the separate network for management, data and storage then you need to create bridge for each interface. In case of VLAN tags use the appropriate network on jump-host depend upon VLAN ID on the interface.

joid/b_installguide.1453269606.txt.gz · Last modified: 2016/01/20 06:00 by Narinder Gupta