HostedEngine add more RAM
by Joseph Goldman
Hi List,
I'm having troubles adding more RAM to my HostedEngine VM. When the
cluster first got up and running I only had a little bit of RAM so I
only gave the HE 4GB, but i'm constantly getting BadHealth alerts so I
want to up it to 8GB.
I have tried multiple ways - mostly any time i edit the HE VM through
the UI it simply reverts back to 4096MB RAM, never upgrades to 8192MB. I
have tried with global HA maintenance on as well but no luck. No errors,
it saves as if it has completed the action but when I re-open the VM (or
even after a fresh boot) it has simply reverted back to 4096MB.
Any help appreciated.
Thanks,
Joe
3 years, 11 months
Re: Migrate hosted engine to standalone host
by Anton Louw
Hello,
I am not sure if the below thread went missing somewhere. Just to add on as well, when moving the hosted engine to a standalone host, will the process look similar to the below:
Backup and remove Hosted Engine:
1. Backup Hosted Engine (engine-backup --scope=all --mode=backup --file=Full --log=Log_Full)
2. Download the backup files from HE using WinSCP
3. Enable global Maintenance (hosted-engine --set-maintenance --mode=global)
4. Power down hosted engine (hosted-engine --vm-shutdown)
---------------------------------------------------------------------------------------------
Redeploy Hosted Engine:
Build new CentOS VM in another environment
*Same IP
*Same name
*Same resources
1. sudo yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm
2. sudo yum install -y ovirt-engine
3. Copy backup files to newly deployed CentOS VM
4. engine-backup --mode=restore --file=Full --log=Log_Full --provision-db --provision-dwh-db --restore-permissions
5. after retore has completed, run engine-setup
Or are there any additional steps I need to take? I have tried this in my one lab environment, and it works without any issues, however when trying this on my second lab environment, everything shows as “down”, ie. Hosts, Data Center and Storage Domains.
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
From: Anton Louw via Users <users(a)ovirt.org>
Sent: 14 May 2020 14:49
To: users(a)ovirt.org
Subject: [ovirt-users] Migrate hosted engine to standalone host
Hi All,
So I have been playing around a bit, and I would just like some recommendations.
I moved my HE from an oVirt node to my VMware environment, basically running as a standalone host now. Is there anything I should look out for?
I can see there is a problem when configuring the HE after the move, where it says that global maintenance is not enabled. How will this work if the hosted engine is not sitting on a oVirt node anymore?
Any feedback\suggestions will be greatly appreciated.
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<mailto:anton.louw@voxtelecom.co.za>
A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg
www.vox.co.za<http://www.vox.co.za>
[F]<https://www.facebook.com/voxtelecomZA>
[T]<https://www.twitter.com/voxtelecom>
[I]<https://www.instagram.com/voxtelecomza>
[L]<https://www.linkedin.com/company/voxtelecom>
[Y]<https://www.youtube.com/user/VoxTelecom>
[#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>.
3 years, 11 months
Bridge not forwarding frames on node.
by s.danzi
Hi to all!I'm having an issue with networks bridges on ovirt node.It's look like this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1279161On VM I have a bridge between a tap device and network interface. On node side the interface is bridged with bond0 vlan 128 (bond0.128 lacp).When I ping an host on the other side of tap device I can see this:Arp request goes from my lan to the tap device on vm. Arp reply return from tap vm and bridge forward this to vm networks interface. Using tcpdump on vm interface on node I can see the arp reply, using tcpdump on bond0.128 or on bridge I can't see the arp reply. Arp request is forwarded from bond0.128 to vm net but arp reply isn't forwarded from vm net to bond0.128. Very strange.....
3 years, 11 months
Glance disk images credentials oVirt4.4
by bjkelley＠us.ibm.com
So if I use this to build a VM and I setup Cloud_init to set user id and passwords.
should I not be able to login to the VM from Console?
Bryan
3 years, 11 months
[ANN] oVirt 4.4.0 Second Release Candidate is now available for testing
by Lev Veyde
oVirt 4.4.0 Second Release Candidate is now available for testing
The oVirt Project is excited to announce the availability of oVirt 4.4.0
Second Release Candidate for testing, as of May 15th, 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 pre-release build.
The oVirt Project makes no guarantees as to its suitability or usefulness.
This pre-release must not to be used in production.
Some of the features included in oVirt 4.4.0 Release Candidate 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.
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 postgresql:12 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?
-
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
-
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 or newer
* CentOS Linux (or similar) 8.1 or newer
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 8.1 or newer
* CentOS Linux (or similar) 8.1 or newer
* 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/
--
Lev Veyde
Senior Software Engineer, RHCE | RHCVA | MCITP
Red Hat Israel
<https://www.redhat.com>
lev(a)redhat.com | lveyde(a)redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
3 years, 11 months
POWER9 Support: VDSM requiring LVM2 package that's missing
by Vinícius Ferrão
Hello,
I would like to know if this is a bug or not, if yes I will submit to Red Hat.
I’m trying to add a ppc64le (POWER9) machine to the hosts pool, but there’s missing dependencies on VDSM:
--> Processing Dependency: lvm2 >= 7:2.02.186-7.el7_8.1 for package: vdsm-4.30.44-1.el7ev.ppc64le
--> Finished Dependency Resolution
Error: Package: vdsm-4.30.44-1.el7ev.ppc64le (rhel-7-server-rhv-4-mgmt-agent-for-power-9-rpms)
Requires: lvm2 >= 7:2.02.186-7.el7_8.1
Available: 7:lvm2-2.02.171-8.el7.ppc64le (rhel-7-for-power-9-rpms)
lvm2 = 7:2.02.171-8.el7
Available: 7:lvm2-2.02.177-4.el7.ppc64le (rhel-7-for-power-9-rpms)
lvm2 = 7:2.02.177-4.el7
Available: 7:lvm2-2.02.180-8.el7.ppc64le (rhel-7-for-power-9-rpms)
lvm2 = 7:2.02.180-8.el7
Available: 7:lvm2-2.02.180-10.el7_6.1.ppc64le (rhel-7-for-power-9-rpms)
lvm2 = 7:2.02.180-10.el7_6.1
Available: 7:lvm2-2.02.180-10.el7_6.2.ppc64le (rhel-7-for-power-9-rpms)
lvm2 = 7:2.02.180-10.el7_6.2
Available: 7:lvm2-2.02.180-10.el7_6.3.ppc64le (rhel-7-for-power-9-rpms)
lvm2 = 7:2.02.180-10.el7_6.3
Available: 7:lvm2-2.02.180-10.el7_6.7.ppc64le (rhel-7-for-power-9-rpms)
lvm2 = 7:2.02.180-10.el7_6.7
Available: 7:lvm2-2.02.180-10.el7_6.8.ppc64le (rhel-7-for-power-9-rpms)
lvm2 = 7:2.02.180-10.el7_6.8
Installing: 7:lvm2-2.02.180-10.el7_6.9.ppc64le (rhel-7-for-power-9-rpms)
lvm2 = 7:2.02.180-10.el7_6.9
Thanks,
3 years, 11 months
