Changing DNS servers
by Chris Adams
I am trying to change the DNS servers on the hosts on a 4.1 cluster. It
appears that oVirt has "learned" them somewhere. They are in
/etc/sysconfig/network-scripts/ifcfg-ovirtmgmt (and of course
/etc/resolv.conf), but that file gets rewritten on a reboot (so if I
change it they just change back). I can't find anything in the web UI
to set/change DNS, but obviously they're stored somewhere.
I see /var/lib/vdsm/persistence/netconf.<number>/nets/ovirtmgmt has
the config; is it safe to directly edit that file?
--
Chris Adams <cma(a)cmadams.net>
6 years, 2 months
[ANN] oVirt 4.3.0 Fifth Release Candidate is now available for testing
by Sandro Bonazzola
The oVirt Project is pleased to announce the availability of the Fifth
Release Candidate of oVirt 4.3.0, as of January 31th, 2019
This is pre-release software. This pre-release should not to be used in
production.
Please take a look at our community page[1] to learn how to ask questions
and interact with developers and users.
All issues or bugs should be reported via oVirt Bugzilla[2].
This update is the first release candidate of the 4.3.0 version.
This release brings more than 130 enhancements and more than 450 bug fixes
on top of oVirt 4.2 series.
What's new in oVirt 4.3.0?
* Q35 chipset, support booting using UEFI and Secure Boot
* Skylake-server and AMD EPYC support
* New smbus driver in windows guest tools
* Improved support for v2v
* OVA export / import of Templates
* Full support for live migration of High Performance VMs
* Microsoft Failover clustering support (SCSI Persistent Reservation) for
Direct LUN disks
* Hundreds of bug fixes on top of oVirt 4.2 series
* New VM portal details page (see a preview here:
https://imgur.com/a/ExINpci)
* New Cluster upgrade UI
* OVN security groups
* IPv6 (static host addresses)
* Support of Neutron from RDO OpenStack 13 as external network provider
* Support of using Skydive from RDO OpenStack 14 as Tech Preview
* Support for 3.6 and 4.0 data centers, clusters and hosts were removed
* Now using PostgreSQL 10
* New metrics support using rsyslog instead of fluentd
This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 7.6 or later
* CentOS Linux (or similar) 7.6 or later
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 7.6 or later
* CentOS Linux (or similar) 7.6 or later
* oVirt Node 4.3 (available for x86_64 only)
Experimental tech preview for x86_64 and s390x architectures for Fedora 28
is also included.
See the release notes draft [3] for installation / upgrade instructions and
a list of new features and bugs fixed.
Notes:
- oVirt Appliance is already available for CentOS 7
- oVirt Appliance for Fedora 28 (tech preview) is being delayed due to
build issues with the build system.
Additional Resources:
* Read more about the oVirt 4.3.0 release highlights:
http://www.ovirt.org/release/4.3.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] https://www.ovirt.org/community/
[2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
[3] http://www.ovirt.org/release/4.3.0/
[4] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://red.ht/sig>
6 years, 2 months
host NonResponsive after trying to update network MTUs
by Edward Berger
I have a problem host which also is the one I deployed a hyperconverged
oVirt node-ng cluster from with the cockpit's hyperconverged installation
wizard.
When I realized after deploying that I hadn't set the MTUs correctly for
the engine-mgmt, associated vlan and eno.2 device and also for my
infiniband interface ib0, I went in and tried to set them to new values
9000 and 65520 it got into some kind of hung state.
The engine task window shows a task in "executing" and a never ending
spinning widget
"Handing non responsive Host track00..."
I can tried updating the hosts /etc/sysconfig/network-scripts by hand.
I've tried every combination of the engines set host in maintenance mode ,
"sync networks" "refresh host capabilities" activating and rebooting, but
I'm still stuck with an unresponsive host.
I had another host that also failed but it allowed me to put it into
maintenance mode and then remove it from the cluster and "add new" it back
and it was happy.
This one won't let me remove it because its serving the gluster volume
mount point, even though I did give the mount options for the 2nd and 3rd
backup volume servers.
I'd appreciate any help restoring it to proper working order.
I'm attaching the gzip'd engine log.
6 years, 2 months
ovirt-sdk_external network add
by ada per
Hello everyone,
I have the following script,
i ve been looking in ovirt-sdk but i cannot seem to find the proper way of adding an external provider network under ovirt-ovn
I manage to add logical networks and vlans but no luck in external provider.
Any advice is appreciated
network = networks_service.add(
network=types.Network(
name='ext_net',
description='Testing network',
data_center=types.DataCenter(
name='Default'
),
usages=[types.NetworkUsage.VM],
external_provider='ovirt-provider-ovn', -->i know this part is wrong what is it supposed to be called?
),
6 years, 2 months
Changing CPU type in oVirt Cluster 4.2
by Juhani Rautiainen
Hi!
I made two node oVirt cluster with self hosted engine. It's running top of
oVirt Node 4.2. Hardware is built on AMD Epyc processors. I just noticed
that "Clusters"-view warns that I have AMD Opteron G3 as CPU type and it
will not supported in the future. Didn't check this during installation so
it probably came automatically. But question is how can I change this? I
get warning 'Error while executing action: Cannot change Cluster CPU to
higher CPU type when there are active Hosts with lower CPU type.'. I saw
old thread from 2016 where it was suggested that you change value straight
to db. Put that seems bit dangerous. Is there any other way to solve this
problem?
Thanks,
Juhani
--
Juhani Rautiainen jrauti(a)iki.fi
6 years, 2 months
Deploying single instance - error
by Leo David
Hello Everyone,
Using version 4.2.8, ( ovirt-node-ng-installer-4.2.0-2019012606.el7.iso
) for deploying one node instance by following from within CockpitUI seems
not to be possible.
Here's the generated inventory ( i've specified "jbod" in the wizard ):
#gdeploy configuration generated by cockpit-gluster plugin
[hosts]
192.168.80.191
[script1:192.168.80.191]
action=execute
ignore_script_errors=no
file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h
192.168.80.191
[disktype]
jbod
[service1]
action=enable
service=chronyd
[service2]
action=restart
service=chronyd
[shell2]
action=execute
command=vdsm-tool configure --force
[script3]
action=execute
file=/usr/share/gdeploy/scripts/blacklist_all_disks.sh
ignore_script_errors=no
[pv1:192.168.80.191]
action=create
devices=sdb
ignore_pv_errors=no
[vg1:192.168.80.191]
action=create
vgname=gluster_vg_sdb
pvname=sdb
ignore_vg_errors=no
[lv1:192.168.80.191]
action=create
lvname=gluster_lv_engine
ignore_lv_errors=no
vgname=gluster_vg_sdb
mount=/gluster_bricks/engine
size=230GB
lvtype=thick
[selinux]
yes
[service3]
action=restart
service=glusterd
slice_setup=yes
[firewalld]
action=add
ports=111/tcp,2049/tcp,54321/tcp,5900/tcp,5900-6923/tcp,5666/tcp,16514/tcp,54322/tcp
services=glusterfs
[script2]
action=execute
file=/usr/share/gdeploy/scripts/disable-gluster-hooks.sh
[shell3]
action=execute
command=usermod -a -G gluster qemu
[volume1]
action=create
volname=engine
transport=tcp
key=storage.owner-uid,storage.owner-gid,features.shard,performance.low-prio-threads,performance.strict-o-direct,network.remote-dio,network.ping-timeout,user.cifs,nfs.disable,performance.quick-read,performance.read-ahead,performance.io-cache,cluster.eager-lock
value=36,36,on,32,on,off,30,off,on,off,off,off,enable
brick_dirs=192.168.80.191:/gluster_bricks/engine/engine
ignore_volume_errors=no
It does not get to finish, throwing the following error:
PLAY [gluster_servers]
*********************************************************
TASK [Create volume group on the disks]
****************************************
changed: [192.168.80.191] => (item={u'brick': u'/dev/sdb', u'vg':
u'gluster_vg_sdb'})
PLAY RECAP
*********************************************************************
192.168.80.191 : ok=1 changed=1 unreachable=0
failed=0
*Error: Section diskcount not found in the configuration file*
Any thoughts ?
--
Best regards, Leo David
6 years, 2 months
VDO volume - storage domain size
by Leo David
Hello Everyone,
I'm I trying to benefit of vdo capabilities, but it seems that I don;t
have too much luck with this.
I have both created a vdo based gluster volume usign both following methods:
- at hyperconverged wizard cluster setup by enabling compression per device
- after installation, by creating a new gluster volume and enabling
compression
In both cases, I end up with a real device size gluster volume/storage
domain, although the vdo's appear in node's cockpit UI as being 10 times
then physical device.
ie: 3 nodes, each having 1 x 900GB ssd device, turns into 9t device vdo
device per host, but the storage domain (gluster replica 3 ) ends up as
being 900GB .
Am I missing something , or maybe doing something wrong?
Thank you very much !
Leo
Best regards, Leo David
6 years, 2 months
