SyNc meeting - Vdsm 26.1
by Yaniv Bronheim
(ybronhei, piotr, fromani, mzamazal, edwafh, ydary)
Hi,
Yaniv Dary raised the desire to modify vdsm name to ovirt-host-agent. The
motivation is to align with ovirt components (ovirt-agent, ovirt-engine,
ovirt-host-deploy, ovirt-node .... and so on). In addition, vdsm versions
are not aligned with ovirt versions at all (historical reasons which we
keep to avoid upgrade issues).
GSS gets many questions about the differences between vdsm and other
components in ovirt, and this will make their life easier.
Basically, we all agreed that it is a good direction to have consistency
with other components in ovirt but ovirt-host-agent sounds less than what
vdsm actually does (sounds like ovirt-host-manager fits better).
Yaniv will send official mail to devel list and we'll discuss it more
deeply there.
Francesco backported health patches merged to ovirt-3.5, will be published
as part of vdsm v4.16.33 (https://gerrit.ovirt.org/#/c/52699 h
ttps://gerrit.ovirt.org/#/c/52700 <https://gerrit.ovirt.org/#/c/52700>
https://gerrit.ovirt.org/#/c/52701) it can help for later investigations
with 3.5 vdsms.
Milan works on debian packing, he arranges the mess we have under our
current Debian folder. He currently discovered issues with sanlock package
in debian which he still investigates.
Greetings,
--
*Yaniv Bronhaim.*
8 years, 10 months
removing parameterized constructors from queries.
by Martin Mucha
Hi,
I got another bug about missing constructor:
public …(P parameters, EngineContext engineContext) {
super(parameters, engineContext);
}
so I looked into:
org.ovirt.engine.core.bll.QueriesCommandBase
and it seems, that sole 'problem' is with initialization of user in @PostConstruct method. It seems, that we can easily set all those fields via setters, and user initialization can be done later, for example before calling executeQueryCommand in:
org.ovirt.engine.core.bll.QueriesCommandBase#executeCommand
doing this will move us closer to CDI and avoid errors because of forgotten constructor. Is there a obstacle blocking us from doing this?
thanks,
Mar.
Edit: I had some time left so I tried to implement it, and it seems to be working. It's big patch, but mostly there's just constructors removal. Actual changes are in:
QueriesCommandBase
CommandsFactory
RegisterVdsQuery
GetAllTemplateBasedEntityQuery
GetAllInstanceTypesQuery
GetAllVmTemplatesQuery
GetAllImageTypesQuery
and test files.
8 years, 10 months
oVirt 3.6.3 RC1 build starting
by Rafael Martins
Fyi oVirt products maintainers,
An oVirt build for an official release is going to start right now.
If you're a maintainer for any of the projects included in oVirt distribution and you have changes in your package ready to be released please:
- bump version and release to be GA ready
- tag your release within git (implies a GitHub Release to be automatically created)
- build your packages within jenkins / koji / copr / whatever
- verify all bugs on MODIFIED have target release and target milestone set.
--
Rafael Martins
8 years, 10 months
oVirt 3.6.1 branch has been created
by Rafael Martins
Hi,
just an heads up we branched for 3.6.3 stabilization this morning.
If you have patches targeted to 3.6.3 you now need to cherry-pick them to 3.6.3 branch too.
--
Rafael Martins
8 years, 10 months
[ANN] oVirt 3.6.2 Final Release is now available
by Sandro Bonazzola
The oVirt Project is pleased to announce today the general availability of
oVirt 3.6.2.
This latest community release includes several new features, such as:
- More feedback about the status of the recovery
- Rebalance option have been disabled on the menu for non-distributed
volumes
- Host in maintenance mode now stop glusterd and glusterfsd processes
- Host activation now restart glusterd
- Improved DNF support
- Improved MOM performances
- Added the ability to override the Storage Domain name field
oVirt is an open-source, openly-governed enterprise virtualization
management application, developed by a global community. You can use the
oVirt management interface (oVirt Engine) to manage hardware nodes, storage
and network resources, and to deploy and monitor virtual machines running
in your data center.
If you are familiar with VMware products, oVirt is conceptually similar to
vSphere. oVirt serves as the bedrock for Red Hat's Enterprise
Virtualization product, and it is the "upstream" project where new features
are developed prior to their inclusion in Red Hat's supported product
offering.
Additional Resources:
* Read more about the oVirt 3.6.2 release highlights:
http://www.ovirt.org/OVirt_3.6.2_Release_Notes
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Read more about oVirt Project community events:
http://www.ovirt.org/Upcoming_events
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
8 years, 10 months
[UI plugins] replacing RestApiSessionAcquired event
by Vojtech Szocs
Hi,
in oVirt 4.0 the RestApiSessionAcquired event will be replaced
with API to create authenticated requests for Engine services.
Using REST API persistent session mechanism where UI acquires
a single session to be shared by all UI plugins led us to many
problems in the past, typically observed by end users as "Auth
Required" browser popups.
The new API proposed by [1] creates XMLHttpRequest object with
following properties:
* sets "Authorization: Bearer xxx" header before sending
* logs request and response details (enabled via API option)
[1] https://gerrit.ovirt.org/#/c/49278/
Example:
var xhr = api.createEngineHttpRequest();
xhr.open('GET', 'http://example.com/ovirt-engine/api', true);
xhr.setRequestHeader('Accept', 'application/json');
xhr.send(null);
Since REST API persistent session mechanism currently relies
on cookie (JSESSIONID), individual UI plugins should not try
to create a REST session on their own to avoid any clashes.
Regards,
Vojtech
8 years, 10 months
Packaging: Rationale for some split packages
by Milan Zamazal
I work on inclusion of Vdsm into Debian. I don't know what are the
reasons for having separate `infra', `xmlrpc', `yajsonrpc', and
`jsonrpc' packages.
Could you please provide rationale for having each of those packages,
separated from `vdsm' and `vdsm-python'? I need to put proper
explanations into package descriptions so that the users know whether
they should install/remove those packages or not.
Thanks,
Milan
8 years, 10 months
