Test Server

Had a spare ProLiant DL380 G6 lying around at work, so I filled all 16 drive bays with some drives I also had lying around, and I've put it into the test rack for me to have a play about with



One of the drives was DOA so got swapped out, and rebuilt the array


Only a low end CPU

Code:

model name      : Intel(R) Xeon(R) CPU           E5504  @ 2.00GHz

but it's decent enough for testing with.

Currently running CentOS 7.6

Code:

# cat /etc/redhat-release
CentOS Linux release 7.6.1810 (Core)

 

Just put another 3 of them in the rack, so we are going to play about with openstack

 

Undercloud node also has a failed drive, so currently rebuilding the array.



Have added a switch into the mix as well to connect them all over their additional NICs.

 

All up and running now. Have set up some HA testing on there with 6 VMs with galara cluster, haproxy, gluster and nginx.

 

Its average at best TBH. We are running NFS storage for the servers (8TB RAID10 array, but it's on 7k drives). Using gluster4.1 which does seem faster than the last time I tried it on 3.7.

 

Code:

[[email protected] html]# gluster volume status

Status of volume: gvol0

Gluster process                             TCP Port  RDMA Port  Online  Pid

------------------------------------------------------------------------------

Brick web-1:/mnt/gvol0/brick0/brick         49152     0          Y       9957

Brick web-2:/mnt/gvol0/brick0/brick         49152     0          Y       9934

Brick web-3:/mnt/gvol0/brick0/brick         49152     0          Y       9927

Self-heal Daemon on localhost               N/A       N/A        Y       9980

Self-heal Daemon on web-3                   N/A       N/A        Y       9950

Self-heal Daemon on web-2                   N/A       N/A        Y       9957

 

Task Status of Volume gvol0

------------------------------------------------------------------------------

There are no active volume tasks

 

I'll do some testing on Monday when I'm back in the office to see what it's really like. It was pretty slow extracting the WP archive into the file system.