@ha_tu_su
After using gparted to wiping out all disks, sr-create command works as expected to create XOSTOR.
Best posts made by ha_tu_su
-
RE: XOSTOR hyperconvergence preview
-
RE: Three-node Networking for XOSTOR
I am experimenting with xcp-ng as a viable option to replace my company's 3 node clusters (2 main nodes + 1 witness node) at customer sites. The hardware we are using has 2 10Gig NICs and rest are 1Gig.
Since XOSTOR is based on LINSTOR I experimented with implementing LINSTOR HA cluster on 3 nodes on ProxMox first. Although mesh network was an option, I wanted to explore other options of implementing a storage network without a switch, since mesh network is only 'community-supported' at the moment. I ended up doing the following:
- Only 2 nodes contribute to the storage pool. 3rd node is just there to maintain quorum for hypervisor and for LINSTOR.
- All 3 nodes are connected to each other via a 1Gig Ethernet switch. This is the management network for the cluster.
- 2 main nodes are directly connected to each other via a 10Gig link. This is the storage network. Note that the witness node is not connected to storage network.
- Create a loopback interface on witness node which has an IP in the storage network subnet.
- Enable ipv_forward=1 on all 3 nodes.
- Add static routes to 2 main hosts like following:
ip route add <witness_node_storage_int_ip>/32 dev <main_host_mgmt_int_name> - Add static route to witness node like following:
ip route add <main_node1_storage_int_ip>/32 dev <witness_host_mgmt_int_name>
ip route add <main_node2_storage_int_ip>/32 dev <witness_host_mgmt_int_name> - After this all 3 nodes can talk to each other on storage subnet. LINSTOR traffic to and from witness node will use the management network. Since this traffic would not be much, it will not hamper other traffic on management network.
Now I want to do a similar implementation in xcp-ng and XOSTOR. Proxmox was basically a learning ground to iron out issues and get a grasp on LINSTOR concepts. So now the questions are:
- Is the above method doable on xcp-ng?
- Is it advisable to do 3 node storage network without switches this way?
- Any issues with enterprise support if someone does this?
Thanks.
-
RE: Import from VMWare vSAN fails with 404 Not Found
@Danp
Thanks for the info. I will retest after next update to XOA and let you know. Thanks for all the wonderful work that you guys are doing.Cheers!!
-
RE: XCP-ng 8.3 betas and RCs feedback π
@olivierlambert
Thanks for the info. No hurry. Better to do it right than fast.
Latest posts made by ha_tu_su
-
RE: Ubuntu 24.04 VMs not reporting IP addresses to XCP-NG 8.2.1
I checked terminal history of my Ubuntu VM and the guest agent was installed from guest-tools.iso
-
Other 2 hosts reboot when 1 host in HA enabled pool is powered off
Hello,
Before I elaborate more on the problem below are some details of the setup for testing.
Hardware
VH1: Dell PowerEdge R640, 2x Intel(R) Xeon(R) Gold 6240 CPU @ 2.60GHz256, 256 GB RAM
VH2: Dell PowerEdge R640, 2x Intel(R) Xeon(R) Gold 6240 CPU @ 2.60GHz256, 256 GB RAM
VW1: Dell PowerEdge R350,1x Intel(R) Xeon(R) E-2378 CPU @ 2.60GHz, 32 GB RAMSoftware
XCP-ng 8.2.1 installed on all 3 hosts. All hosts updated 3 weeks back using yum update.
XO from sources updated to commit 6fcb8.Configuration
All the 3 hosts are added to a pool.
I have created XOSTOR shared storage using disks from all 3 hosts.
Enabled HA on pool, used XOSTOR storage as hearbeat SR.
Created few Windows Server 2002 and Ubuntu 24.04 VMs.
Enabled HA on some of the VMs (best-effort + restart). Made sure that sum of RAM on HA enabled VMs is less than 32 GB (it is 20 GB) to account for the smallest host.
Checked max hosts failure that can be tolerated by running:[12:31 xcp-ng-vh1 ~]# xe pool-ha-compute-max-host-failures-to-tolerate 2
Test Case
Power off VW1 from IDRAC (Power Off System)
Expected Output: The 2 Ubuntu VMs running on VW1 will be migrated to surviving hosts.
Observed Output: After VW1 is powered of, other 2 surviving hosts in the cluster get rebooted. Have repeated this test case many times and same behaviour is observed.Disabling HA on the pool and repeating the test case does not exhibit the same behaviour. When VW1 is powered off, other hosts are unaffected.
Anyone have any idea why this can be happening?
Thanks.
-
RE: Ubuntu 24.04 VMs not reporting IP addresses to XCP-NG 8.2.1
I have Ubuntu 24.04 installed and Management Agent version listed in XO UI is 7.30.0-12.
I had installed the agent some time back so don't remember whether I installed using guest-utils ISO or from apt. -
RE: XCP-ng 8.3 betas and RCs feedback π
@olivierlambert
Thanks for the info. No hurry. Better to do it right than fast. -
RE: Three-node Networking for XOSTOR
@ronan-a
Unfortunately, I am in the process of reinstalling XCP-ng on the nodes to start from scratch. Just thought I have tried too many things and somewhere forgot to undo the βwrongβ configs. So canβt run the command now. Although I had run this command before when I posted all the screenshots. The output had 2 entries (from my memory):1. StltCon <mgmt_ip> 3366 Plain 2. <storage_nw_ip> 3366 Plain
I will repost with the required data when I get everything configured again.
Thanks.
-
Removing xcp-persistent-database resource
Hi
I am experimenting with XOSTOR. I removed the SR related to XOSTOR and then started deleting the resources from command line using
linstor resource-definition delete <rd_name>
. I am now only left withxcp-persistent-database
but I am not able to delete it because it is always in use by the host which is linstor-controller. Can anyone suggest me how I can delete this resource?I did read this reply from @ronan-a: https://xcp-ng.org/forum/topic/5361/xostor-hyperconvergence-preview/205
As per this I didwipefs -a -f /dev/<disk>
on disks which were part of XOSTOR previously, but I don't see then in the XOA UI when I go to create new XOSTOR.Thanks.
-
RE: Three-node Networking for XOSTOR
@ha_tu_su
@olivierlambert @ronan-a : Any insight into this? -
RE: How to associate a VIF to a Network
@martinpedros
If you want to create an internal network for the VMs to talk to each other without that traffic getting out of a physical NIC, private network is what you are looking for.Take a look at this post: https://xcp-ng.org/forum/topic/7309/option-to-create-host-only-private-network
-
RE: Import from VMWare vSAN fails with 404 Not Found
@Danp
Thanks for the info. I will retest after next update to XOA and let you know. Thanks for all the wonderful work that you guys are doing.Cheers!!