I have a pair of questions I could use some help with.
1. Does the oVirt guest agent collect filesystem level information? I'm
hoping something like what `df -h` would report. File systems, free vs
used space, etc. Bonus points if we can get that kind of info from linux
and windows agents.
2. Assuming that info is available, where can I access it? I assume it
isn't surfaced via the REST api (yet), but it would be good to know where
it is available.
Why? I'm updating VM Portal (web-ui), and it would be great to chart/report
guest derived data rather than infrastructure disk provisioned vs allocated
Senior Software Engineer
RHV-M Engineering - UX Team
Red Hat, Inc
I just found out that there is no option for autostart VM's.
This functionality is extremely crucial when a system is going down after a
UPS ran out of juice (or that it didn't work when the power failed).
Starting VMs automatically help the recovery process, and editable startup
list could help a lot more (for example: if 10 VMs are dependent on AD
services, the Windows 2012 should be booted 2nd, right after HE, and then
the other machines).
Autostart VM's could help a lot with UPS if the list can go "backward" to
power off VMs in a serialized matter, so when a UPS detects a power loss,
it could signal the HE to start shutting down VMs by a list.
Any chance to have this feature in 4.3?
VM Portal UI redesign -- weekly report [29-Jul-2018 - 4-Aug-2018]
screens: https://github.com/oVirt/ovirt-design/pulls and
StatusThe updated landing page (VM List) is in code review
The edit page has made good progress, but is getting a bit bogged down
- we've started doing official sprints / agile on the team, hopefully
will help accelerate things
- when we don't have REST API capabilities, we should consider tabling
those items and progressing on other things
A VM Portal release (1.4.2) is scheduled for Friday, August 10. It will
- new VM List page with new PatternFly notification drawer
- new Edit page skeleton
- Edit > Overview card working
- Edit > Details working
- Edit > Snapshots working
[We will be officially releasing VM Portal every two weeks now, at the
completion of each sprint.]
Aug 2 2018
Greg, Scott, Bohdan, Laura, Liz, Lucie
Edit > Snapshots card -- design is complete, coding is almost complete and
Edit > Overview card (top left) -- coded, sagas are not quite done
Edit > Overview card (top left) -- we overlooked icon upload
Edit > Details card -- IP address discussion. It would be nice to show IPs
(v4, v6?). Liz will mockup.
Edit > Utilization card -- revisiting disks. Scott needs to do some legwork
-- looks like data we have is missing in the REST API results
Edit > NIC and Disks review (Liz): they are very similar. Designs are
close, perhaps complete
Discussion re: hotplugging
Need to offer user option to hotplug (modal)
Alert box for pending changes (in each card)
We can grab Next Run config (vs current) in REST
(vm name is runtime changeable)
Discussion re: disabling buttons vs hiding them when users don’t have
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
gshereme(a)redhat.com IRC: gshereme
I pulled the latest mater rpms from nightly builds  and there seems to
be a issue running engine-setup.
engine-setup fails with message
[root@laptop ovirt-engine-master-new9]# engine-setup
***L:ERROR Internal error: No module named 'async_tasks_map'
I had the same issue with dev env on master