Cannot upload image
by Green, Jacob Allen /C
Hello, I am in a precarious situation where I need to upload an image to the storage domain, I understand that normally you would achieve this via the upload button on the storage domain > Disks tab. However I currently do not have the ability to import the certificate. Is there a way from command line either on the RHV manager or otherwise to upload a qcow2 without using the image upload through the GUI?
Thank you.
5 years, 1 month
Gluster problems with new disk and device name change and overlap
by Gianluca Cecchi
Hi,
I have configured a single host HCI environment through the GUI wizard in
4.3.9.
Initial setup has thai layout of disks, as seen by the operating system:
/dev/sda -> for ovirt-node-ng OS
/dev/nvme0n1 --> for gluster, engine and data volumes
/dev/nvme1n1 --> for gluster, vmstore volume
So far so good and all is ok.
I notice that, even with single path internal disks, at the end oVirt
configures the gluster disks as multipath devices and LVM2 PV structure on
top of the multipath devices.
Is this for "code optimization" at low level or what is the rationale for
that, as with Gluster normally you do use local disks and so single path?
Multipath structure generated:
[root@ovirt ~]# multipath -l
nvme.8086-50484b53373530353031325233373541474e-494e54454c205353 dm-5
NVME,INTEL SSDPED1K375GA
size=349G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=0 status=active
`- 0:0:1:0 nvme0n1 259:0 active undef running
eui.01000000010000005cd2e4b5e7db4d51 dm-6 NVME,INTEL SSDPEDKX040T7
size=932G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=0 status=active
`- 2:0:1:0 nvme1n1 259:2 active undef running
[root@ovirt ~]#
Anyway, on top of the multipah devices
On /dev/nvme0n1:
gluster_vg_nvme0n1 volume group with gluster_lv_data and gluster_lv_engine
On /dev/nvme1n1
gluster_vg_nvme1n1 volume group with gluster_lv_vmstore logical volume
The problem arises when I add another nvme disk, that, occupying a PCI
slot, it seems has always higher priority of the previous /dev/nvme1n1 disk
and so takes its name.
After booting the node:
old nvme0n1 --> unmodified name
old nvme1n1 --> becomes nvme2n1
new disk --> gets name nvme1n1
From a funcional point of view I have no problems apart LVM warnings I send
below and also because the xfs entries in fstab are with UUID:
UUID=fa5dd3cb-aeef-470e-b982-432ac896d87a /gluster_bricks/engine xfs
inode64,noatime,nodiratime 0 0
UUID=43bed7de-66b1-491d-8055-5b4ef9b0482f /gluster_bricks/data xfs
inode64,noatime,nodiratime 0 0
UUID=b81a491c-0a4c-4c11-89d8-9db7fe82888e /gluster_bricks/vmstore xfs
inode64,noatime,nodiratime 0 0
lvs commands get:
[root@ovirt ~]# lvs
WARNING: Not using device /dev/nvme0n1 for PV
eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp.
WARNING: Not using device /dev/nvme2n1 for PV
O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl.
WARNING: PV eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp prefers device
/dev/mapper/nvme.8086-50484b53373530353031325233373541474e-494e54454c20535344504544314b3337354741-00000001
because device is used by LV.
WARNING: PV O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl prefers device
/dev/mapper/eui.01000000010000005cd2e4e359284f51 because device is used by
LV.
LV VG Attr LSize
Pool Origin
...
Or, for the old nvme1n1 disk, now nvme2n1 multipath device:
[root@ovirt ~]# pvdisplay /dev/mapper/eui.01000000010000005cd2e4e359284f51
WARNING: Not using device /dev/nvme0n1 for PV
eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp.
WARNING: Not using device /dev/nvme2n1 for PV
O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl.
WARNING: PV eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp prefers device
/dev/mapper/nvme.8086-50484b53373530353031325233373541474e-494e54454c20535344504544314b3337354741-00000001
because device is used by LV.
WARNING: PV O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl prefers device
/dev/mapper/eui.01000000010000005cd2e4e359284f51 because device is used by
LV.
--- Physical volume ---
PV Name /dev/mapper/eui.01000000010000005cd2e4e359284f51
VG Name gluster_vg_nvme1n1
PV Size 931.51 GiB / not usable 1.71 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 238467
Free PE 0
Allocated PE 238467
PV UUID O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl
[root@ovirt ~]#
I'm able to create PV on top of the new multipath device detected by the
system (see the nvme1n1 of the underlying disk):
eui.01000000010000005cd2e4b5e7db4d51 dm-6 NVME,INTEL SSDPEDKX040T7
size=3.6T features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=0 status=active
`- 1:0:1:0 nvme1n1 259:1 active undef running
[root@ovirt ~]# pvcreate --dataalignment 256K
/dev/mapper/eui.01000000010000005cd2e4b5e7db4d51
WARNING: Not using device /dev/nvme0n1 for PV
eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp.
WARNING: Not using device /dev/nvme2n1 for PV
O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl.
WARNING: PV eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp prefers device
/dev/mapper/nvme.8086-50484b53373530353031325233373541474e-494e54454c20535344504544314b3337354741-00000001
because device is used by LV.
WARNING: PV O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl prefers device
/dev/mapper/eui.01000000010000005cd2e4e359284f51 because device is used by
LV.
Physical volume "/dev/mapper/eui.01000000010000005cd2e4b5e7db4d51"
successfully created.
[root@ovirt ~]#
But then I'm unable to create a VG on top of it:
[root@ovirt ~]# vgcreate gluster_vg_4t
/dev/mapper/eui.01000000010000005cd2e4b5e7db4d51
WARNING: Not using device /dev/nvme0n1 for PV
eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp.
WARNING: Not using device /dev/nvme1n1 for PV
56ON99-hFFP-cGpZ-g4MX-GfjW-jXeE-fKZVG9.
WARNING: Not using device /dev/nvme2n1 for PV
O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl.
WARNING: PV eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp prefers device
/dev/mapper/nvme.8086-50484b53373530353031325233373541474e-494e54454c20535344504544314b3337354741-00000001
because device is used by LV.
WARNING: PV 56ON99-hFFP-cGpZ-g4MX-GfjW-jXeE-fKZVG9 prefers device
/dev/mapper/eui.01000000010000005cd2e4b5e7db4d51 because device is in dm
subsystem.
WARNING: PV O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl prefers device
/dev/mapper/eui.01000000010000005cd2e4e359284f51 because device is used by
LV.
WARNING: Not using device /dev/nvme0n1 for PV
eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp.
WARNING: Not using device /dev/nvme1n1 for PV
56ON99-hFFP-cGpZ-g4MX-GfjW-jXeE-fKZVG9.
WARNING: Not using device /dev/nvme2n1 for PV
O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl.
WARNING: PV eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp prefers device
/dev/mapper/nvme.8086-50484b53373530353031325233373541474e-494e54454c20535344504544314b3337354741-00000001
because of previous preference.
WARNING: PV 56ON99-hFFP-cGpZ-g4MX-GfjW-jXeE-fKZVG9 prefers device
/dev/mapper/eui.01000000010000005cd2e4b5e7db4d51 because of previous
preference.
WARNING: PV O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl prefers device
/dev/mapper/eui.01000000010000005cd2e4e359284f51 because of previous
preference.
Cannot use device /dev/mapper/eui.01000000010000005cd2e4b5e7db4d51 with
duplicates.
[root@ovirt ~]#
the same with the "-f" option.
I suspect I can solve the problem filtering out /dev/nvme* devices in
lvm.conf, but I'm not sure. The OS disk is seen as sda so it should not
have problems with this
Something like this:
filter = [ "r|/dev/nvme|", "a|.*/|" ]
And also I am not sure if I have to rebuild the initrd or not in this case
and if so what would be the exact sequence of commands to execute.
Any suggestions?
Thanks in advance,
Gianluca
5 years, 1 month
Auto-logout while editing
by Shareef Jalloq
There's a rather annoying bug in the Engine UI where you can be logged out
while actively using the system. I've been logged out twice now while
editing the settings for a new VM. I'm screen grabbing and documenting as
I go but I was just logged out while editing the System settings for a new
VM.
Shareef.
5 years, 1 month
snapshot options on remote NFS storage
by Jayme
Was wondering if there are any guides or if anyone could share their
storage configuration details for NFS. If using LVM is it safe to snapshot
volumes with running VM images for backup purposes?
5 years, 1 month
Re: Mount ISO to VM
by Shani Leviim
Hi Anton,
Sure thing.
During the creation of the NFS storage, you should specify an export path.
SSHing that export path will expose you to the storage domain's content.
You can visit the "Attaching NFS Storage" section in
https://ovirt.org/documentation/admin-guide/chap-Storage.html
*Regards,*
*Shani Leviim*
On Tue, Apr 7, 2020 at 1:37 PM Anton Louw <Anton.Louw(a)voxtelecom.co.za>
wrote:
>
>
> Hi Shani,
>
>
>
> Great, thank you very much.
>
>
>
> Do you perhaps know if I can access the storage domain if I SSH to a node?
> For instance, if I want to access a “datastore” in VMware, I SSH to a host
> and select /vmfs/volumes
>
>
>
> Is there anything like that available for oVirt?
>
>
>
> Thanks
>
>
>
> *Anton Louw*
> *Cloud Engineer: Storage and Virtualization* at *Vox*
> ------------------------------
> *T:* 087 805 0000 | *D:* 087 805 1572
> *M:* N/A
> *E:* anton.louw(a)voxtelecom.co.za
> *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg
> www.vox.co.za
>
> [image: F] <https://www.facebook.com/voxtelecomZA>
> [image: T] <https://www.twitter.com/voxtelecom>
> [image: I] <https://www.instagram.com/voxtelecomza/>
> [image: L] <https://www.linkedin.com/company/voxtelecom>
> [image: Y] <https://www.youtube.com/user/VoxTelecom>
>
> *From:* Shani Leviim <sleviim(a)redhat.com>
> *Sent:* 07 April 2020 11:35
> *To:* Anton Louw <Anton.Louw(a)voxtelecom.co.za>
> *Cc:* users(a)ovirt.org
> *Subject:* Re: [ovirt-users] Mount ISO to VM
>
>
>
> Hi Anton,
>
> You can upload an ISO file as a disk using the UI:
>
> Storage -> Disks -> upload.
>
> Further information can be found here under the "Uploading a Disk Image to
> a Storage Domain" section:
>
> https://www.ovirt.org/documentation/admin-guide/chap-Virtual_Machine_Disk...
>
>
>
> Or use the following script using SDK:
> https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload...
>
>
> *Regards,*
>
> *Shani Leviim*
>
>
>
>
>
> On Tue, Apr 7, 2020 at 11:45 AM Anton Louw <Anton.Louw(a)voxtelecom.co.za>
> wrote:
>
>
>
> Hi Everybody,
>
>
>
> Is there a way to mount an ISO to one of my VMs if I do not have an ISO
> domain, but the ISO file is on a Data domain?
>
>
>
> Thanks
>
>
>
> *Anton Louw*
>
> *Cloud Engineer: Storage and Virtualization* at *Vox*
> ------------------------------
>
> *T:* 087 805 0000 | *D:* 087 805 1572
> *M:* N/A
> *E:* anton.louw(a)voxtelecom.co.za
> *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg
> www.vox.co.za
>
>
>
> <https://www.facebook.com/voxtelecomZA>
>
> <https://www.facebook.com/voxtelecomZA>
>
> <https://www.facebook.com/voxtelecomZA>
>
> <https://www.facebook.com/voxtelecomZA>
>
> <https://www.facebook.com/voxtelecomZA>
>
> <https://www.facebook.com/voxtelecomZA>
>
> <https://www.facebook.com/voxtelecomZA>
>
> <https://www.facebook.com/voxtelecomZA>
>
> <https://www.facebook.com/voxtelecomZA>
>
> <https://www.facebook.com/voxtelecomZA>
>
> <https://www.facebook.com/voxtelecomZA>
>
> <https://www.facebook.com/voxtelecomZA>
>
>
> *Disclaimer* <https://www.facebook.com/voxtelecomZA>
>
> The contents of this email are confidential to the sender and the intended
> recipient. Unless the contents are clearly and entirely of a personal
> nature, they are subject to copyright in favour of the holding company of
> the Vox group of companies. Any recipient who receives this email in error
> should immediately report the error to the sender and permanently delete
> this email from all storage devices.
>
> This email has been scanned for viruses and malware, and may have been
> automatically archived by *Mimecast Ltd*, an innovator in Software as a
> Service (SaaS) for business. Providing a *safer* and *more useful* place
> for your human generated data. Specializing in; Security, archiving and
> compliance. To find out more *Click Here*.
> <https://www.facebook.com/voxtelecomZA>
>
> <https://www.facebook.com/voxtelecomZA>
>
> _______________________________________________
> Users mailing list -- *users(a)ovirt.org*
> To unsubscribe send an email to *users-leave(a)ovirt.org*
> Privacy Statement: *https://www.ovirt.org/privacy-policy.html*
> oVirt Code of Conduct:
> *https://www.ovirt.org/community/about/community-guidelines/*
> List Archives:
> *https://lists.ovirt.org/archives/list/users@ovirt.org/message/D7ONE6IJN6RK2IQRNUYCZE3EOXBJWHX4/*
> <https://www.facebook.com/voxtelecomZA>
>
>
>
5 years, 1 month
Re: Mount ISO to VM
by Shani Leviim
Hi Anton,
You can upload an ISO file as a disk using the UI:
Storage -> Disks -> upload.
Further information can be found here under the "Uploading a Disk Image to
a Storage Domain" section:
https://www.ovirt.org/documentation/admin-guide/chap-Virtual_Machine_Disk...
Or use the following script using SDK:
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload...
*Regards,*
*Shani Leviim*
On Tue, Apr 7, 2020 at 11:45 AM Anton Louw <Anton.Louw(a)voxtelecom.co.za>
wrote:
>
>
> Hi Everybody,
>
>
>
> Is there a way to mount an ISO to one of my VMs if I do not have an ISO
> domain, but the ISO file is on a Data domain?
>
>
>
> Thanks
>
> *Anton Louw*
> *Cloud Engineer: Storage and Virtualization* at *Vox*
> ------------------------------
> *T:* 087 805 0000 | *D:* 087 805 1572
> *M:* N/A
> *E:* anton.louw(a)voxtelecom.co.za
> *A:* Rutherford Estate, 1 Scott Street, Waverley, Johannesburg
> www.vox.co.za
>
> [image: F] <https://www.facebook.com/voxtelecomZA>
> [image: T] <https://www.twitter.com/voxtelecom>
> [image: I] <https://www.instagram.com/voxtelecomza/>
> [image: L] <https://www.linkedin.com/company/voxtelecom>
> [image: Y] <https://www.youtube.com/user/VoxTelecom>
>
> [image: #VoxBrand]
> <https://www.vox.co.za/fibre/fibre-to-the-home/?prod=HOME>
> *Disclaimer*
>
> The contents of this email are confidential to the sender and the intended
> recipient. Unless the contents are clearly and entirely of a personal
> nature, they are subject to copyright in favour of the holding company of
> the Vox group of companies. Any recipient who receives this email in error
> should immediately report the error to the sender and permanently delete
> this email from all storage devices.
>
> This email has been scanned for viruses and malware, and may have been
> automatically archived by *Mimecast Ltd*, an innovator in Software as a
> Service (SaaS) for business. Providing a *safer* and *more useful* place
> for your human generated data. Specializing in; Security, archiving and
> compliance. To find out more Click Here
> <https://www.voxtelecom.co.za/security/mimecast/?prod=Enterprise>.
>
>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/D7ONE6IJN6R...
>
5 years, 1 month
ISO and Export domains deprecated
by Colin Coe
Hi all
I'm trying to understand how ISO and Export domains going away is going to
affect us.
We have four RHV instances:
- Prod DC1 (RHV4.1)
- Prod DC2 (RHV4.1)
- DEV (RHV4.3)
- TEST (RHV4.3)
Prod DC1, DEV and TEST all share export and ISO domains.
Prod DC2 is remote and currently has its own ISO and Export domains.
When ISO and Export domains go away, can I still share ISO domains between
the RHV instances?
Thanks
5 years, 1 month
Mount ISO to VM
by Anton Louw
Hi Everybody,
Is there a way to mount an ISO to one of my VMs if I do not have an ISO domain, but the ISO file is on a Data domain?
Thanks
Anton Louw
Cloud Engineer: Storage and Virtualization
______________________________________
D: 087 805 1572 | M: N/A
A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg
anton.louw(a)voxtelecom.co.za
www.vox.co.za
5 years, 1 month
oVirt 4.4.0 Beta release refresh is now available for testing
by Sandro Bonazzola
oVirt 4.4.0 Beta release refresh is now available for testing
The oVirt Project is excited to announce the availability of the beta
release of oVirt 4.4.0 refresh for testing, as of April 3rd, 2020
This release unleashes an altogether more powerful and flexible open source
virtualization solution that encompasses hundreds of individual changes and
a wide range of enhancements across the engine, storage, network, user
interface, and analytics on top of oVirt 4.3.
Important notes before you try it
Please note this is a Beta release.
The oVirt Project makes no guarantees as to its suitability or usefulness.
This pre-release must not be used in production.
In particular, please note that upgrades from 4.3 and future upgrades from
this beta to the final 4.4 release from this version are not supported.
Some of the features included in oVirt 4.4.0 Beta require content that will
be available in CentOS Linux 8.2 but can’t be tested on RHEL 8.2 beta yet
due to some incompatibility in openvswitch package shipped in CentOS Virt
SIG which requires to rebuild openvswitch on top of CentOS 8.2.
Known Issues
-
ovirt-imageio development is still in progress. In this beta you can’t
upload images to data domains using the engine web application. You can
still copy iso images into the deprecated ISO domain for installing VMs or
upload and download to/from data domains is fully functional via the REST
API and SDK.
For uploading and downloading via the SDK, please see:
-
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload...
-
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/downlo...
Both scripts are standalone command line tools, try --help for more info.
Installation instructions
For the engine: either use appliance or:
- Install CentOS Linux 8 minimal from
http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-...
- dnf install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm
- dnf update (reboot if needed)
- dnf module enable -y javapackages-tools pki-deps 389-ds
- dnf install ovirt-engine
- engine-setup
For the nodes:
Either use oVirt Node ISO or:
- Install CentOS Linux 8 from
http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-...
; select minimal installation
- dnf install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm
- dnf update (reboot if needed)
- Attach the host to engine and let it be deployed.
What’s new in oVirt 4.4.0 Beta?
-
Hypervisors based on CentOS Linux 8 (rebuilt from award winning RHEL8),
for both oVirt Node and standalone CentOS Linux hosts
-
Easier network management and configuration flexibility with
NetworkManager
-
VMs based on a more modern Q35 chipset with legacy seabios and UEFI
firmware
-
Support for direct passthrough of local host disks to VMs
-
Live migration improvements for High Performance guests.
-
New Windows Guest tools installer based on WiX framework now moved to
VirtioWin project
-
Dropped support for cluster level prior to 4.2
-
Dropped SDK3 support
-
4K disks support only for file based storage. iSCSI/FC storage do not
support 4k disks yet.
-
Exporting a VM to a data domain
-
Editing of floating disks
-
Integrating ansible-runner into engine, which allows a more detailed
monitoring of playbooks executed from engine
-
Adding/reinstalling hosts are now completely based on Ansible
-
The OpenStack Neutron Agent cannot be configured by oVirt anymore, it
should be configured by TripleO instead
This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 8.1
* CentOS Linux (or similar) 8.1
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 8.1
* CentOS Linux (or similar) 8.1
* oVirt Node 4.4 based on CentOS Linux 8.1 (available for x86_64 only)
See the release notes [1] for installation instructions and a list of new
features and bugs fixed.
If you manage more than one oVirt instance, OKD or RDO we also recommend to
try ManageIQ <http://manageiq.org/>.
In such a case, please be sure to take the qc2 image and not the ova image.
Notes:
- oVirt Appliance is already available for CentOS Linux 8
- oVirt Node NG is already available for CentOS Linux 8
Additional Resources:
* Read more about the oVirt 4.4.0 release highlights:
http://www.ovirt.org/release/4.4.0/
* Get more oVirt project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/
[1] http://www.ovirt.org/release/4.4.0/
[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>*
<https://www.redhat.com/en/summit?sc_cid=7013a000002D2QxAAK>*
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
5 years, 1 month
Add gluster storage domain incomplete documentation
by Gianluca Cecchi
Hello,
I think both at oVirt and Red Hat official docs the steps regarding adding
a new Gluster storage domain on an existing installation is quite confusing
and misaligned.
Below I explain my reasons for both.
In the mean time, suppose I have a single host HCI with self hosted engine
(but it could be useful to have hints for multi-hosts too) and the 3
storage domains configured during install (engine and data on a disk and
vmstore on another disk).
The system initially had 3 disks, the first used for the ovirt-node-ng
system, the second for engine and data, the third for vmstore initial
gluster storage domains
Now I go and add a fourth disk, say 4Tb in size.
I would like to create a new Gluster storage domain on it
What are the suggested steps?
BTW: after booting, the new disk has been automatically included in
multipath
eui.01000000010000005cd2e4b5e7db4d51 dm-6 NVME,INTEL SSDPEDKX040T7
size=3.6T features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=0 status=active
`- 1:0:1:0 nvme1n1 259:1 active undef running
Coming back to the docs
- oVirt documentation
I base my considerations on page
https://www.ovirt.org/documentation/admin-guide/chap-Working_with_Gluster...
1) the picture in that page is still based on 3.6 GUI, so the initial
approach tends to make me feel the page could be not up to date
2) I would put the section "Creating a Storage Volume" before "Attaching a
Gluster Storage Volume as a Storage Domain" and not the opposite as it is
now
3) In "Creating a Storage Volume" there is the note that
"
You must create brick directories or mountpoints before you can add them to
volumes.
"
This sentence in my opinion is not so clear (see also details at the
end)... what is a user expected to have done on hypervisors? Creation of
directories or file systems (and what type: prefered xfs or ext4?). Perhaps
an example of commands would be useful.
4) in the workflow of creating volume, item 7:
Click the Add Bricks button to select bricks to add to the volume. Bricks
must be created externally on the Gluster Storage nodes.
I would expect an indication of commands to be run instead... This implies
knowledge of Gluster that the GUI functionality is aimed to hide... but so,
not completely...
I can see in my existing bricks, going to their advanced details:
"
xfs
rw,seclabel,noatime,nodiratime,attr2,inode64,logbsize=128k,sunit=256,swidth=512,noquota
"
There is also the fstab portion of creating bricks...
5) In the workflow of creating volume, item 9:
It is not clear the default "*" value for access if is the recommended one
or not.
I presume not
- RHV documentation
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/...
4.3 Administrator Guide downloaded today
Chapter 8, section 8.6
PREPARING AND ADDING RED HAT GLUSTER STORAGE
There is reference to Red Hat Gluster Storage, version 3.4.
I think it should be 3.5 instead?
Because at the same time in 3.4 there is reference to RHV 4.1, not 4.3.
While in "Configuring Red Hat Virtualization with Red Hat Gluster Storage"
version 3.5 there is correct reference to RHV 4.3
Anyway this mix of product documentation is not optimal in my opinion.
I would directly include inside RHV docs the Gluster part related to it,
without jumping between the two comlete, with the risk of misalignment in
time.
Also, in Gluster Storage guide referred, there is the part related to
volumes but not to bricks....
Possibly the correct reference for the brick part, that is the one missing
in webadmin GUI, could be this:
https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.5...
and/or this
https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.5...
?
Thanks for reading and hoping to get commands' workflow to configure this
new disk for a new gluster storage domain.
It seems inside the guides is oversimplified the process of creating
bricks, that in the documentation seem actually to be xfs filesystems
mounted over thin pool based logical volumes residing on top of volume
groups with particular alignment settings specified during their
creation....
Gianluca
5 years, 1 month
