there is a "Import VM" tab which
will allow you to import your VMs.
Anyone have idea on how this is done?
I can see .meta and .lease files but not sure how this would be used to
import VMs.
It would be nice to tell it to review current "disk / images" and compare to
what is in library ...
Thanks for reply.. It really is appreciated.
1) Note about VM import
-> Can you provide details / Example. For me I click on
oVirt-> Compute -> Virtual Machines -> Import
-> Source Option (only ones making any sense would be "Export Domain" rest
are unrelated and KVM one would need xml.. wh
Thanks,
the gluster volume is just a test and the main reason was to test
the upgrade of a node with gluster bricks.
I don't know why lvm doesn\t work which is what oVirt is using.
Regards,
Paul S.
From: Strahil Nikolov
Sent: 25 Sept
Ok.. digging around a bit.
##
[root@medusa vmstore]# tree -h /media/data/
/media/data/
├── [ 48] 7801d608-0416-4e5e-a469-2fefa2398d06
│ ├── [ 89] dom_md
│ │ ├── [ 1.0M] ids
│ │ ├── [ 16M] inbox
│ │ ├── [ 2.0M] leases
│ │ ├── [ 549] metada
>1 node I wiped it clean and the other I left the 3 gluster brick drives
>untouch.
If the last node from the original is untouched you can:
1. Go to the old host and use 'gluster volume remove-brick replica 1
wiped_host:/path/to-brick untouched_bricks_host:/path/to-brick force'
2. Remove the 2
>Question:
>1) Can someone point me to the manual on how to re-constitute a VM and >bring
>it back into oVirt where all "oVirt-engines" were redeployed. It is >only
>three or four VMs I typically care about (HA cluster and OCP >ignition/
>Ansible tower VM).
Ensure that the old Engine is power
>"Error while executing action: Cannot add Host. Connecting to host via SSH
>>has failed, verify that the host is reachable (IP address, routable address
>>etc.) You may refer to the engine.log file for further details."
>Tested SSH between all nodes and works without password.
Engine is not run
It's a clean disk, already did a wipefs -a /dev/sdb
did a partprobe and checked using blkid to make sure all the multipath elements
we seeing the clean disk.
From: Jayme
Sent: 25 September 2020 17:09
To: Staniforth, Paul
Cc: Users
Subject: Re: [ovirt-users] No
Assuming you don't care about data on the drive you may just need to use
wipefs on the device i.e. wipefs -a /dev/sdb
On Fri, Sep 25, 2020 at 12:53 PM Staniforth, Paul <
p.stanifo...@leedsbeckett.ac.uk> wrote:
> Hello,
> how do you manage a gluster host when upgrading a node?
>
> I upgr
Hello,
how do you manage a gluster host when upgrading a node?
I upgraded/replaced 2 nodes with the new install and can't recreate any gluster
bricks.
1 node I wiped it clean and the other I left the 3 gluster brick drives
untouched.
If I try to create bricks using the UI on the nodes
Il giorno lun 21 set 2020 alle ore 17:44 Gianluca Cecchi <
gianluca.cec...@gmail.com> ha scritto:
>
>
> On Mon, Sep 21, 2020 at 5:26 PM Sandro Bonazzola
> wrote:
>
>>
>>
>> Il giorno lun 21 set 2020 alle ore 17:13 Gianluca Cecchi <
>> gianluca.cec...@gmail.com> ha scritto:
>>
>>>
>>> On Thu, Sep
Il giorno ven 25 set 2020 alle ore 15:32 Gianluca Cecchi <
gianluca.cec...@gmail.com> ha scritto:
>
>
> On Fri, Sep 25, 2020 at 1:57 PM Sandro Bonazzola
> wrote:
>
>> oVirt Node 4.4.2 is now generally available
>>
>> The oVirt project is pleased to announce the general availability of
>> oVirt No
It turns out that for security reasons the university sets a default cap
of two MAC addresses per port, so host and engine maxed it out. I
requested that they increase the cap on this port and now things work as
expected.
--
As a result of Coronavirus-related precautions, NYU and the Center fo
On Fri, Sep 25, 2020 at 1:57 PM Sandro Bonazzola
wrote:
> oVirt Node 4.4.2 is now generally available
>
> The oVirt project is pleased to announce the general availability of oVirt
> Node 4.4.2 , as of September 25th, 2020.
>
> This release completes the oVirt 4.4.2 release published on September
oVirt 4.4.3 Second Release Candidate is now available for testing
The oVirt Project is pleased to announce the availability of oVirt 4.4.3
Second Release Candidate for testing, as of September 25th, 2020.
This update is the third in a series of stabilization updates to the 4.4
series.
How to prev
oVirt Node 4.4.2 is now generally available
The oVirt project is pleased to announce the general availability of oVirt
Node 4.4.2 , as of September 25th, 2020.
This release completes the oVirt 4.4.2 release published on September 17th
Important notes before you install / upgrade
Please note that
As expected... this is a learning curve. My three node cluster.. in an
attempt to learn how to do admin work on it, debug it... I have now
redeployed the engine and even added second one on a node in cluster.
But.
I now realize that my "production vms" are gone.
In the past, on a manual b
Il giorno ven 25 set 2020 alle ore 08:52 Tommaso - Shellrent <
tomm...@shellrent.com> ha scritto:
> Hi to all.
>
> Hi try to ank another time the same question:
>
> in our tests ovirt seems to be able to make only one export to ova at
> time. also on different hosts and datacenter.
>
> Someone can
18 matches
Mail list logo
