Intro
Nowadays all the business markets are highly competitive and organizations want to take competitive advantages over others. When business is highly critical databases and application servers need to be up and running 24X7 . Virtualization is the technology that helps to maximize the IT infrastructure cost. High availability of VM can be achieved easily from virtualization clustering. Also, Virtualization technology will ease the cloud migration journey.
Virtualization can be deployed in two ways.
- Converged architecture.
- Hyper-converged architecture.
- A storage-area network (SAN)
- Direct-attached storage (DAS)
- Network-attached storage (NAS)
What is Hyper-converged architecture?
There are a few prerequisites you need to understand before creating a cluster.
- Are you going with converged or hyper-converged architecture?
- How many nodes do you need to cluster which helps with fencing and shared storage?
- What is the virtualization management network bandwidth?
- What is the shared storage type best suited for the environment?
For optimal virtualization architecture, we need at least 3 nodes. Having 3 nodes will handle the fencing more efficiently than 2 nodes.
All depend on the capex cost, you can start with 2 nodes and plan to move 3 nodes within 2 years or so. There is no restriction that you cannot create an OLVM cluster with 2 nodes, but some of the fencing features will not work as expected.
Note: Make sure not to implement glusterfs with 2 nodes. Glusterfs hyper-converged architecture storage you need to have 3 nodes.
In this article, I will cover how to implement a shared fiber domain between two nodes.
As per Figure 1: Fiber LUN should be mapped to both the KVM nodes. In OLVM shared cluster SPM (Storage Pool Manager) Role will handle this shared storage mounting in both nodes.
Note: Make sure to map the same Fiber LUN to both nodes.
Figure 1: How to map the Fiber storage domain to both nodes.
Mapping Fiber LUN to node01.
[root@KVM01 ~]# lsblk | grep 3624a93701561d6718da94a200001104c
└─3624a93701561d6718da94a200001104c 252:2 0 200G 0 mpath
└─3624a93701561d6718da94a200001104c 252:2 0 200G 0 mpath
└─3624a93701561d6718da94a200001104c 252:2 0 200G 0 mpath
└─3624a93701561d6718da94a200001104c 252:2 0 200G 0 mpath
[root@KVM120 ~]#
Mapping Fiber LUN to node02.
[root@KVM02 ~]# lsblk | grep 3624a93701561d6718da94a200001104c
└─3624a93701561d6718da94a200001104c 252:2 0 200G 0 mpath
└─3624a93701561d6718da94a200001104c 252:2 0 200G 0 mpath
└─3624a93701561d6718da94a200001104c 252:2 0 200G 0 mpath
└─3624a93701561d6718da94a200001104c 252:2 0 200G 0 mpath
[root@KVM121 ~]#
Adding FC storage from OLVM
Figure 2: Illustrates how to create a fiber channel data domain, Always double-check the LUN ID before selecting the disk. This will take 10min to create the lvm2 and the file structure.
Figure 2: Add Fiber LUN as an FC-Data-Domain.
If this is created successfully, all 3 tasks will be completed with a green color taskbar.
Figure 3: OLVM task detail tab.
No comments:
Post a Comment