4:39 a.m.
I wonder if the xleases volume mentioned here refers to ovf_store ?
* A new xleases volume to support VM leases - this feature adds the
ability to acquire a lease per virtual machine on shared storage without
attaching the lease to a virtual machine disk.
A VM lease offers two important capabilities:
* Avoiding split-brain.
* Starting a VM on another host if the original host becomes
non-responsive, which improves the availability of HA VMs.
6:11 a.m.
On Wednesday, 22 September 2021 10:39:34 CEST Tommy Sway wrote:
I wonder if the xleases volume mentioned here refers to ovf_store ?
No, xleases is part of the disk space used internally by oVirt (to manage
concurrent access to the resources, e.g. disk image) and shouldn't be touched
by the user.
OVF store is Open Virtualization Format [1] and it's used for storing these
files, see [2] for more details.
[1] https://en.wikipedia.org/wiki/Open_Virtualization_Format
[2] https://www.ovirt.org/develop/release-management/features/storage/
importstoragedomain.html
* A new xleases volume to support VM leases - this feature adds the
ability to acquire a lease per virtual machine on shared storage without
attaching the lease to a virtual machine disk.
A VM lease offers two important capabilities:
* Avoiding split-brain.
* Starting a VM on another host if the original host becomes
non-responsive, which improves the availability of HA VMs.
6:48 a.m.
Are you referring to the description of this passage?
Detailed Description
VM/Template configurations (including disks info) are stored on the master
storage domain only for backup purposes and in order to provide the ability
to run VMs without having a running engine/db. This feature aims to change
the current place in which the OVFs are stored while using the existing
<https://www.ovirt.org/develop/release-management/features/storage/ovfautoup
dater.html> OvfAutoUpdater feature (asynchronous incremental OVF updates).
The expected benefits are:
1. Having "self contained" Storage Domains which will enable to recover
in case of data loss (oVirt supports registration of unknown disks stored on
storage domain in the engine and adding VM from OVF configuration - so
having the VM OVF stored on the same Storage Domain of it's disks will allow
to recover the vm "completeness" from that Storage Domain to the oVirt
engine).
2. Moving out from using the master_fs on the storage domain, as part
of this change the OVFs will be stored on a designated volume located on
each Storage Domain.
3. Adding support for streaming files from the engine to vdsm (will be
discussed later on).
-----Original Message-----
From: Vojtech Juranek <vjuranek(a)redhat.com Sent:
Wednesday, September 22, 2021 6:12 PM
To: users(a)ovirt.org
Cc: Tommy Sway <sz_cuitao(a)163.com>
Subject: Re: [ovirt-users] about the OVF_STORE and the xleases volume
On Wednesday, 22 September 2021 10:39:34 CEST Tommy Sway wrote:
I wonder if the xleases volume mentioned here refers to ovf_store ?
No, xleases is part of the disk space used internally by oVirt (to manage
concurrent access to the resources, e.g. disk image) and shouldn't be
touched by the user.
OVF store is Open Virtualization Format [1] and it's used for storing these
files, see [2] for more details.
[1] <https://en.wikipedia.org/wiki/Open_Virtualization_Format>
https://en.wikipedia.org/wiki/Open_Virtualization_Format
[2] <https://www.ovirt.org/develop/release-management/features/storage/>
https://www.ovirt.org/develop/release-management/features/storage/
importstoragedomain.html
* A new xleases volume to support VM leases - this feature adds
the
ability to acquire a lease per virtual machine on shared storage
without attaching the lease to a virtual machine disk.
A VM lease offers two important capabilities:
* Avoiding split-brain.
* Starting a VM on another host if the original host becomes
non-responsive, which improves the availability of HA VMs.
6:58 a.m.
I got it.
Today, oVirt supports importing ISO and Export Storage Domains, however,
there is no support for importing an existing Data Storage Domain. A Data
Storage Domain contains disks volumes and VMs/Templates OVF files. The OVF
file is an XML standard representing the VM/Template configuration including
disks, memory, CPU and more. Based on this information stored in the Storage
Domain we can revive entities such as disks, VMs and Templates in the setup
of any Data Center the Storage Domain will be attached to. The usability of
the feature might be useful for various use cases, here are some of them:
* Recover after the loss of the oVirt Engine's database.
* Transfer VMs between setups without the need to copy the data into
and out of the export domain.
* Support migrating Storage Domains between different oVirt
installations.
Storage Domains that can be restored for VMs/Templates must contain
OVF_STORE disks. Since OVF_STORE disk is only supported from a 3.5v Data
Center, the Storage Domains that can be restored have to be managed in a
3.5v Data Center before the disaster. As long as the setup contains 3.5v
Data Centers, the Import Storage Domain feature will automatically be
supported for those Data Centers.
From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On Behalf Of Tommy
Sway
Sent: Wednesday, September 22, 2021 6:48 PM
To: 'Vojtech Juranek' <vjuranek(a)redhat.com>; users(a)ovirt.org
Subject: [ovirt-users] Re: about the OVF_STORE and the xleases volume
Are you referring to the description of this passage?
Detailed Description
VM/Template configurations (including disks info) are stored on the master
storage domain only for backup purposes and in order to provide the ability
to run VMs without having a running engine/db. This feature aims to change
the current place in which the OVFs are stored while using the existing
<https://www.ovirt.org/develop/release-management/features/storage/ovfautoup
dater.html> OvfAutoUpdater feature (asynchronous incremental OVF updates).
The expected benefits are:
1. Having "self contained" Storage Domains which will enable to recover
in case of data loss (oVirt supports registration of unknown disks stored on
storage domain in the engine and adding VM from OVF configuration - so
having the VM OVF stored on the same Storage Domain of it's disks will allow
to recover the vm "completeness" from that Storage Domain to the oVirt
engine).
2. Moving out from using the master_fs on the storage domain, as part
of this change the OVFs will be stored on a designated volume located on
each Storage Domain.
3. Adding support for streaming files from the engine to vdsm (will be
discussed later on).
-----Original Message-----
From: Vojtech Juranek <vjuranek(a)redhat.com <mailto:vjuranek@redhat.com> Sent: Wednesday, September 22, 2021 6:12 PM
To: users(a)ovirt.org <mailto:users@ovirt.org Cc:
Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> >
Subject: Re: [ovirt-users] about the OVF_STORE and the xleases volume
On Wednesday, 22 September 2021 10:39:34 CEST Tommy Sway wrote:
I wonder if the xleases volume mentioned here refers to ovf_store ?
No, xleases is part of the disk space used internally by oVirt (to manage
concurrent access to the resources, e.g. disk image) and shouldn't be
touched by the user.
OVF store is Open Virtualization Format [1] and it's used for storing these
files, see [2] for more details.
[1] <https://en.wikipedia.org/wiki/Open_Virtualization_Format>
https://en.wikipedia.org/wiki/Open_Virtualization_Format
[2] <https://www.ovirt.org/develop/release-management/features/storage/>
https://www.ovirt.org/develop/release-management/features/storage/
importstoragedomain.html
* A new xleases volume to support VM leases - this feature adds
the
ability to acquire a lease per virtual machine on shared storage
without attaching the lease to a virtual machine disk.
A VM lease offers two important capabilities:
* Avoiding split-brain.
* Starting a VM on another host if the original host becomes
non-responsive, which improves the availability of HA VMs.
7:20 a.m.
* The OVF_STORE disk will contain all the entities configuration which
are candidates to be registered. The candidates are VMs and Templates which
has at least one disk exists in the Storage Domain OVF contained in the
unregistered_ovf_of_entities table.
In my mind, OVF_STORE is also a disk that holds VM or Template configuration
information in XML format, which is used when importing data domains into a
new data center.
But why do I find more than one OVF_STORE disk in the same storage domain?
From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On Behalf Of Tommy
Sway
Sent: Wednesday, September 22, 2021 6:58 PM
To: 'Vojtech Juranek' <vjuranek(a)redhat.com>; users(a)ovirt.org
Subject: [ovirt-users] Re: about the OVF_STORE and the xleases volume
I got it.
Today, oVirt supports importing ISO and Export Storage Domains, however,
there is no support for importing an existing Data Storage Domain. A Data
Storage Domain contains disks volumes and VMs/Templates OVF files. The OVF
file is an XML standard representing the VM/Template configuration including
disks, memory, CPU and more. Based on this information stored in the Storage
Domain we can revive entities such as disks, VMs and Templates in the setup
of any Data Center the Storage Domain will be attached to. The usability of
the feature might be useful for various use cases, here are some of them:
* Recover after the loss of the oVirt Engine's database.
* Transfer VMs between setups without the need to copy the data into
and out of the export domain.
* Support migrating Storage Domains between different oVirt
installations.
Storage Domains that can be restored for VMs/Templates must contain
OVF_STORE disks. Since OVF_STORE disk is only supported from a 3.5v Data
Center, the Storage Domains that can be restored have to be managed in a
3.5v Data Center before the disaster. As long as the setup contains 3.5v
Data Centers, the Import Storage Domain feature will automatically be
supported for those Data Centers.
From: users-bounces(a)ovirt.org <mailto:users-bounces@ovirt.org>
<users-bounces(a)ovirt.org <mailto:users-bounces@ovirt.org> > On Behalf Of
Tommy Sway
Sent: Wednesday, September 22, 2021 6:48 PM
To: 'Vojtech Juranek' <vjuranek(a)redhat.com <mailto:vjuranek@redhat.com>
>;
users(a)ovirt.org <mailto:users@ovirt.org Subject:
[ovirt-users] Re: about the OVF_STORE and the xleases volume
Are you referring to the description of this passage?
Detailed Description
VM/Template configurations (including disks info) are stored on the master
storage domain only for backup purposes and in order to provide the ability
to run VMs without having a running engine/db. This feature aims to change
the current place in which the OVFs are stored while using the existing
<https://www.ovirt.org/develop/release-management/features/storage/ovfautoup
dater.html> OvfAutoUpdater feature (asynchronous incremental OVF updates).
The expected benefits are:
1. Having "self contained" Storage Domains which will enable to recover
in case of data loss (oVirt supports registration of unknown disks stored on
storage domain in the engine and adding VM from OVF configuration - so
having the VM OVF stored on the same Storage Domain of it's disks will allow
to recover the vm "completeness" from that Storage Domain to the oVirt
engine).
2. Moving out from using the master_fs on the storage domain, as part
of this change the OVFs will be stored on a designated volume located on
each Storage Domain.
3. Adding support for streaming files from the engine to vdsm (will be
discussed later on).
-----Original Message-----
From: Vojtech Juranek <vjuranek(a)redhat.com <mailto:vjuranek@redhat.com> Sent: Wednesday, September 22, 2021 6:12 PM
To: users(a)ovirt.org <mailto:users@ovirt.org Cc:
Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> >
Subject: Re: [ovirt-users] about the OVF_STORE and the xleases volume
On Wednesday, 22 September 2021 10:39:34 CEST Tommy Sway wrote:
I wonder if the xleases volume mentioned here refers to ovf_store ?
No, xleases is part of the disk space used internally by oVirt (to manage
concurrent access to the resources, e.g. disk image) and shouldn't be
touched by the user.
OVF store is Open Virtualization Format [1] and it's used for storing these
files, see [2] for more details.
[1] <https://en.wikipedia.org/wiki/Open_Virtualization_Format>
https://en.wikipedia.org/wiki/Open_Virtualization_Format
[2] <https://www.ovirt.org/develop/release-management/features/storage/>
https://www.ovirt.org/develop/release-management/features/storage/
importstoragedomain.html
* A new xleases volume to support VM leases - this feature adds
the
ability to acquire a lease per virtual machine on shared storage
without attaching the lease to a virtual machine disk.
A VM lease offers two important capabilities:
* Avoiding split-brain.
* Starting a VM on another host if the original host becomes
non-responsive, which improves the availability of HA VMs.
8:08 p.m.
Thank you!
lrwxrwxrwx. 1 vdsm kvm 45 Jun 12 23:42 ids ->
/dev/41bc1316-5c1d-4836-a103-5acbbf0c47a1/ids
lrwxrwxrwx. 1 vdsm kvm 47 Jun 12 23:42 inbox ->
/dev/41bc1316-5c1d-4836-a103-5acbbf0c47a1/inbox
lrwxrwxrwx. 1 vdsm kvm 48 Jun 12 23:42 leases ->
/dev/41bc1316-5c1d-4836-a103-5acbbf0c47a1/leases
lrwxrwxrwx. 1 vdsm kvm 48 Jun 12 23:42 master ->
/dev/41bc1316-5c1d-4836-a103-5acbbf0c47a1/master
lrwxrwxrwx. 1 vdsm kvm 50 Jun 12 23:42 metadata ->
/dev/41bc1316-5c1d-4836-a103-5acbbf0c47a1/metadata
lrwxrwxrwx. 1 vdsm kvm 48 Jun 12 23:42 outbox ->
/dev/41bc1316-5c1d-4836-a103-5acbbf0c47a1/outbox
lrwxrwxrwx. 1 vdsm kvm 49 Jun 12 23:42 xleases ->
/dev/41bc1316-5c1d-4836-a103-5acbbf0c47a1/xleases
and what difference between the xleases and leases on the list?
-----Original Message-----
From: Vojtech Juranek <vjuranek(a)redhat.com>
Sent: Wednesday, September 22, 2021 6:12 PM
To: users(a)ovirt.org
Cc: Tommy Sway <sz_cuitao(a)163.com>
Subject: Re: [ovirt-users] about the OVF_STORE and the xleases volume
On Wednesday, 22 September 2021 10:39:34 CEST Tommy Sway wrote:
I wonder if the xleases volume mentioned here refers to ovf_store ?
No, xleases is part of the disk space used internally by oVirt (to manage
concurrent access to the resources, e.g. disk image) and shouldn't be
touched by the user.
OVF store is Open Virtualization Format [1] and it's used for storing these
files, see [2] for more details.
[1] https://en.wikipedia.org/wiki/Open_Virtualization_Format
[2] https://www.ovirt.org/develop/release-management/features/storage/
importstoragedomain.html
* A new xleases volume to support VM leases - this feature adds the
ability to acquire a lease per virtual machine on shared storage
without attaching the lease to a virtual machine disk.
A VM lease offers two important capabilities:
* Avoiding split-brain.
* Starting a VM on another host if the original host becomes
non-responsive, which improves the availability of HA VMs.
1190
days inactive
1191
days old
5 comments
2 participants
participants (2)
-
Tommy Sway -
Vojtech Juranek