Lowering the bar for wiki contribution?
by Roy Golan
I'm getting the feeling I'm not alone in this, authoring and publishing a
wiki page isn't as used to be for long time.
I want to suggest a bit lighter workflow:
1. Everyone can merge their page - (it's a wiki)
Same as with (public and open) code, no one has the motivation to publish
a badly written
wiki page under their name. True, it can have an impact, but not as with
broken code
2. Use Page-Status marker
The author first merges the draft. Its now out there and should be updated
as time goes and its
status is DRAFT. Maintainers will come later and after review would change
the status to
PUBLISH. That could be a header in on the page:
---
page status: DRAFT/PUBLISH
---
Simple I think, and should work.
7 years, 5 months
Update on Domain XML created by the engine
by Arik Hadas
Hi All,
Yesterday we merged the class LibvirtVmXmlBuilder in ovirt-engine.
It does not include the conversion of all the previously supported VM
properties (e.g., payload devices, OVS stuff, cinder disks - any help would
be appreciated btw) or covers all flows (e.g., run once) yet and there is
surely a place for improvement, but in its current state
LibvirtVmXmlBuilder is able to generate a libvirt's domxml on the engine
side for many typical VMs in our development environment.
If you happen to start working on a change that involves changing something
in the domxml, please do it by modifying this class. Our plan is to
deprecate the VM info map/dictionary soon.
Let me try to motivate you by example:
Let's say that you want to add support for a property of a disk called
'discard'.
In 4.1:
You had to patch VmInfoBuilderImpl to add another element to the VM info
map and then modify VDSM to use it when encoding the Disk device into XML.
Now:
You need to patch LibvirtVmXmlBuilder so the 'discard' property would be
set on the disk device element in the generated XML.
In order to test such a change you can:
(1) apply [1] to send the XML generated by the engine to VDSM
(2) apply [2] to send the XML generated by the engine to libvirt
[1] https://gerrit.ovirt.org/#/c/71088/
[2] https://gerrit.ovirt.org/#/c/65182/
Regards,
Arik
7 years, 9 months
Request to pull Italian translation for Master
by Gianluca Cecchi
Hello,
I have completed 100% of all parts except ApplicationConstants one, on
which I'm going to work during next weeks.
In the mean time I ask if it is possible to commit the current situation so
that upcoming oVirt 4.1 reflects it.
Thanks in advance,
Gianluca
7 years, 9 months
[ OST Failure Report ] [ oVirt master ] [ 31.01.2017 ] [add_secondary_storage_domains]
by Evgheni Dereveanchin
Test failed: add_secondary_storage_domains
Links to suspected patches:
https://gerrit.ovirt.org/71376
https://gerrit.ovirt.org/71427
https://gerrit.ovirt.org/71345
Link to Job:
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5040/
Link to all logs:
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5040/art...
Error snippet from log:
2017-01-31 05:54:53,862-0500 ERROR (jsonrpc/5) [storage.TaskManager.Task] (Task='ad8f48fc-de09-4c26-b052-7a036d7651ad') Unexpected error (task:871)
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 878, in _run
return fn(*args, **kargs)
File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 52, in wrapper
res = f(*args, **kwargs)
File "/usr/share/vdsm/storage/hsm.py", line 2215, in getAllTasksInfo
allTasksInfo = self._pool.getAllTasksInfo()
File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 77, in wrapper
raise SecureError("Secured object is not in safe state")
SecureError: Secured object is not in safe state
Regards,
Evgheni Dereveanchin
7 years, 9 months
[URGENT][ACTION REQUIRED] Re: Missing vdsm snapshots for Fedoras
by Sandro Bonazzola
We're one week after initial report that vdsm is missing in fc24 repository
for master.
We have automation broken due to this.
Please restore vdsm builder for fc24 master, it's affecting CI for
hosted-engine, ovirt-release, and possibly other projects...
On Thu, Jan 26, 2017 at 2:54 PM, Dan Kenigsberg <danken(a)redhat.com> wrote:
> On Thu, Jan 26, 2017 at 11:23 AM, Nir Soffer <nsoffer(a)redhat.com> wrote:
> > On Thu, Jan 26, 2017 at 11:17 AM, Gil Shinar <gshinar(a)redhat.com> wrote:
> >> VDSM master fc24 is not supported.
> >
> > This is the only fedora version we support now.
> >
> > Vdsm on Fedora 25 is broken due to m2crypto changes.
>
> It's a one-liner configuration change to have Vdsm use the
> python-native SSL support.
> We should not drag f24 just for that; we'd better just modify the
> default for Fedora 25 a-la https://gerrit.ovirt.org/#/c/71248/
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
7 years, 9 months
Updated VDSM for oVirt 4.1.0 Second Release Candidate
by Sandro Bonazzola
Hi,
we've update vdsm package within oVirt 4.1.0 Second Release Candidate
fixing:
Bug 1416112 - virt-v2v: Import from VMware, Xen and KVM failed with
"OSError: [Errno 9] Bad file descriptor" (workaround: upgrade
python-cpopen)
Being the fix just forcing Requires: python-cpopen >= 1.5 instead
of Requires: python-cpopen >= 1.4
and being python-cpopen >= 1.5 already availablein RC2, GA shouldn't have
any delay.
Thanks,
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
7 years, 9 months
oVirt 4.1.0 RC3 build planned today, GA possible delay.
by Sandro Bonazzola
Hi,
we have detected 2 blockers which requires a re-spin of vdsm and
ovirt-engine causing a RC3 build requirement.
This will probably imply a delay of GA.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
7 years, 9 months
[Vdsm][Heads up] branching out 4.1.0 on February, 1st.
by Francesco Romani
Hi everyone
I'm planning to branch out 4.1.0 on February 1st, to unlock merges on
the 4.1 branches, thus backporting to 4.0/3.6.
This will make even more important to backport only blocker fixes to 4.1.0.
Bests,
--
Francesco Romani
Red Hat Engineering Virtualization R & D
IRC: fromani
7 years, 9 months
VDSM master fc24 build artifacts fails
by Gil Shinar
Hi,
$subject job fails with the following exception:
*16:19:32* make[2]: Entering directory
'/home/jenkins/workspace/vdsm_master_build-artifacts-fc24-x86_64/vdsm/lib/api'*16:19:32*
Generate vdsm-api.html*16:19:32* chmod u+w .*16:19:32*
PYTHONPATH=./../:./../vdsm \*16:19:32* /usr/bin/python
schema_to_html.py vdsm-api.yml vdsm-api.html*16:19:32* Traceback (most
recent call last):*16:19:32* File "schema_to_html.py", line 29, in
<module>*16:19:32* from api import vdsmapi*16:19:32* File
"/home/jenkins/workspace/vdsm_master_build-artifacts-fc24-x86_64/vdsm/lib/api/vdsmapi.py",
line 28, in <module>*16:19:32* from vdsm.logUtils import
Suppressed*16:19:32* File
"/home/jenkins/workspace/vdsm_master_build-artifacts-fc24-x86_64/vdsm/lib/vdsm/logUtils.py",
line 29, in <module>*16:19:32* from dateutil import tz*16:19:32*
ImportError: No module named dateutil*16:19:32* Makefile:642: recipe
for target 'vdsm-api.html' failed*16:19:32* make[2]: ***
[vdsm-api.html] Error 1*16:19:32* make[2]: Leaving directory
'/home/jenkins/workspace/vdsm_master_build-artifacts-fc24-x86_64/vdsm/lib/api'*16:19:32*
Makefile:458: recipe for target 'all-recursive' failed*16:19:32*
make[1]: *** [all-recursive] Error 1*16:19:32* make[1]: Leaving
directory '/home/jenkins/workspace/vdsm_master_build-artifacts-fc24-x86_64/vdsm/lib'*16:19:32*
Makefile:524: recipe for target 'all-recursive' failed*16:19:32* make:
*** [all-recursive] Error 1
Can someone please take a look:
http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-fc24-x86_64/1/co...
Thanks
Gil
7 years, 9 months
