Dates for This Phase of GSoC
by Brian Proffitt
I've had some questions about the Google Summer of Code, and I wanted to
share with you the dates and milestones for the student/mentor onboarding
phase of the event. All dates can be found on the GSoC site[1].
Right now we are in the student application phase, which goes until April
3. By that time, students should have their draft proposals in. Then we
review them and turn them in to Google by April 16. On April 17, we ask for
student slots, and then on April 19, slots are allocated to us.
Finally, on April 24, we tell Google which students are going to take the
slots, and then on May 3, Google announces all projects/students/mentors.
Hopefully this helps. Please watch your inbox for notifications from Google
to ensure what you are getting does not need an action item. What I get as
one of the oVirt admins for GSoC is different that what you get as
(potential) mentors.
Peace,
Brian
[1] https://summerofcode.withgoogle.com/dashboard/timeline/
--
Brian Proffitt
Principal Community Analyst
Open Source and Standards
@TheTechScribe
574.383.9BKP
8 years
planned Jenkins restart
by Evgheni Dereveanchin
Hi everyone,
I'll be performing a planned Jenkins restart within the next hour.
No new builds will be scheduled during this maintenance period.
I will inform you once it is over.
Regards,
Evgheni Dereveanchin
8 years
[ OST Failure Report ] [ oVirt master ] [ 21-03-2017 ] [test-repo_ovirt_experimental_master]
by Shlomo Ben David
Hi,
Test failed: [ test-repo_ovirt_experimental_master ]
Link to suspected patches: N/A
Link to Job:
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5945
Link to all logs:
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5945/art...
Error snippet from the log:
<error>
2017-03-21 11:55:15,975-0400 ERROR (jsonrpc/7) [storage.TaskManager.Task]
(Task='02a8b5a3-ff82-4a07-bc8a-b3a756630e8c') 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 1158, in attachStorageDomain
pool.attachSD(sdUUID)
File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line
79, in wrapper
return method(self, *args, **kwargs)
File "/usr/share/vdsm/storage/sp.py", line 930, in attachSD
dom = sdCache.produce(sdUUID)
File "/usr/share/vdsm/storage/sdc.py", line 112, in produce
domain.getRealDomain()
File "/usr/share/vdsm/storage/sdc.py", line 53, in getRealDomain
return self._cache._realProduce(self._sdUUID)
File "/usr/share/vdsm/storage/sdc.py", line 136, in _realProduce
domain = self._findDomain(sdUUID)
File "/usr/share/vdsm/storage/sdc.py", line 153, in _findDomain
return findMethod(sdUUID)
File "/usr/share/vdsm/storage/sdc.py", line 178, in _findUnfetchedDomain
raise se.StorageDomainDoesNotExist(sdUUID)
StorageDomainDoesNotExist: Storage domain does not exist:
(u'a8739fae-284f-4640-800d-016c084de7e6',)
</error>
Best Regards,
Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
RHCSA | RHCVA | RHCE
IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)
OPEN SOURCE - 1 4 011 && 011 4 1
8 years
Get Involved with the oVirt Project! Spring 2017 Edition
by Sandro Bonazzola
Hi,
Got some time to spare? Join us on the oVirt project!
oVirt is a feature rich server virtualization management system with
advanced capabilities. It also provides a crucial venue for user and
developer cooperation, and is the first truly open and comprehensive data
center virtualization management initiative.
If you are new to oVirt, we recommend that you visit the develop
<https://www.ovirt.org/develop/> page to learn more about the project, and
the working with Gerrit
<https://www.ovirt.org/develop/dev-process/working-with-gerrit/> page for
more about our code review system. If you haven’t worked with Gerrit
before, we recommend you visit the introduction to Gerrit
<https://gerrit-review.googlesource.com/Documentation> page.
On our community page <https://www.ovirt.org/community/> you’ll discover
the many ways in which you can contribute to the project, even without
programming skills.
More suggestions? Below you’ll find other ways in which you can contribute
to the oVirt project.
Keep ‘em Fresh
Like the idea of having fresh disk images of your favorite distribution in
the oVirt Glance repository? You can help in two ways: First, test existing
online images to ensure that they work with cloud-init. Second, create an
online image and report your success to devel(a)ovirt.org. We’ll be happy to
upload the images once they are ready.
Get Vdsm Running on Debian
If you like Debian and have programming or packaging skills, you can help
with the ongoing effort to get VDSM running on Debian
<https://www.ovirt.org/develop/release-management/features/debian-support-...>.
All the current work on Debian (VDSM and related packages) can be found in
the Debian git repositories <http://git.debian.org/>. You can also keep up
to date on how the work is progressing by subscribing to the oVirt devel
mailing list <http://lists.ovirt.org/mailman/listinfo/devel>.
Fix Some Bugs
These bugs are just waiting to be resolved:
Bug ID
Summary
1411133
Hosted-Engine: iscsi activation storage failing
1209881
[RFE] Remove iptables from hosted-engine.spec file to be able to deploy
hosted-engine without firewall services installed
1353713
[RFE] - iSCSI Setup Should use different User/Password For Discovery and
Portal
1130445
[TEXT] - If engine-setup asks for updates and choice is no, suggest
'--offline' on re-run.
1174236
[RFE] Integrate installation with Server Roles of Fedora Server
1356425
[TEXT] 'hosted-engine --vm-start' said it destroyed the VM
1328488
The engine fails with oracle java8
Port oVirt to Your Favorite Distribution
Are you sure-handed at packaging software, and using a distribution
currently unsupported by oVirt? Help to get oVirt ported to any of the
following distributions:
Fedora <http://lists.ovirt.org/pipermail/devel/2015-September/011426.html>
CentOS <https://wiki.centos.org/SpecialInterestGroup/Virtualization>
Gentoo <https://wiki.gentoo.org/wiki/OVirt>. Also, check out Google Summer
of Code <https://wiki.gentoo.org/wiki/Google_Summer_of_Code/2016/Ideas> to
learn how you can contribute to Gentoo and get paid for it!
Debian
<http://www.ovirt.org/develop/release-management/features/debian-support-f...>:
Archlinux <http://www.ovirt.org/develop/developer-guide/arch-linux/>
OpenSUSE <https://build.opensuse.org/project/show/Virtualization:oVirt>
Get into DevOps
If you love DevOps and find yourself counting stable builds in Jenkins CI
while trying to fall asleep, then the oVirt infrastructure team is looking
for you! Join us and dive into the latest and coolest DevOps tools today!
Check out these open tasks
<https://ovirt-jira.atlassian.net/secure/RapidBoard.jspa?rapidView=6.>.
You can also help by telling us how you use oVirt in your DevOps
environment. Email us at devel(a)ovirt.org (Please use [DevOps] in the
subject line. For more information on oVirt DevOps, visit oVirt
infrastructure docs
<http://ovirt-infra-docs.readthedocs.io/en/latest/> and oVirt
infra documentation
<http://www.ovirt.org/develop/infra/infrastructure-documentation/>.
Improve the oVirt System Testing
Make oVirt system testing
<https://gerrit.ovirt.org/gitweb?p=ovirt-system-tests.git;a=summary> - and
the Lago system <https://github.com/lago-project/lago> that runs it - even
better. Visit Lago project documentation
<http://lago.readthedocs.io/en/stable/> to learn how to run the test suite
yourself.
More Bugs, No Coding Required
No time for DevOps and you are not a programer? You can still contribute.
Here are some easy bugs to fix
<https://bugzilla.redhat.com/buglist.cgi?quicksearch=classification%3Aovir...>
that don’t require a single line of code.
Tests to Run
Do you prefer to test things? Here are some test cases you can try
<http://www.ovirt.org/develop/infra/testing/>, using nightly snapshots
<http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/>.
Switching to Fedora 25
For oVirt 4.2, support for Fedora will be based on Fedora 25. You can help
to get it ready by running nightly snapshots
<http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/> and
reporting any issues.
Create Your Own Test Cases
We’d love you to contribute some much needed test cases for oVirt features
<http://www.ovirt.org/develop/release-management/features/>.
Get Creative
You are welcome to contribute artwork, such as oVirt live backgrounds and
covers, release banners, stickers, and t-shirt designs. Check out Fedora
artworks <https://fedoraproject.org/wiki/Artwork#Resources> for inspiration.
Get Alternative
Into alternative architectures? Test ppc64le
<https://cbs.centos.org/repos/virt7-ovirt-41-release/ppc64le/> and aarch64
<https://cbs.centos.org/repos/virt7-ovirt-41-release/aarch64/> packages
from CentOS Virt SIG.
Talk to Us!
Feel free to ask any other question about development by emailing us at
devel(a)ovirt.org, or by reaching out on the IRC channel
<https://www.ovirt.org/community/>.
Spread the Good News
Help to spread the word about oVirt! We are the complete virtual machine
management system that’s free and comes with an impressive list of enterprise
capabilities
<http://www.zdnet.com/article/how-much-longer-can-red-hats-ovirt-remain-co...>
including live migration, high availability, load balancing, a self-hosted
engine, an intuitive user-interface, and much more.
How to Contribute
If you’d like to get involved, we’d love to hear from you! Simply shoot us
an email at devel(a)ovirt.org and tell us how you’d like to contribute.
We look forward to hearing from you!.
The oVirt Development Team
oVirt: Better technology. Faster Innovation. Powered by community
innovation.
8 years
UI dialog visual update
by Alexander Wels
Hi,
I just merged a large patch that does a complete visual update of all dialogs
in oVirt. All the dialogs should now follow the standard patternfly modal
dialog visuals and layout. One of the consequences of this is that you can no
longer move the dialogs around in the application like before. This is by
design.
I tried very hard to make sure I updated every dialog in the application to
match the look and feel as needed, or at the very least did not display any
major issues like missing content or extra scrollbars where none were needed.
Please report any issues you find to me, and I will try to make sure they get
fixed ASAP.
Alexander
ps. attached are some screenshots from my development environment.
8 years
[ OST Failure Report ] [ oVirt master ] [ 20-03-2017 ] [007_sd_reattach.reattach_storage_domain]
by Shlomo Ben David
Hi,
Test failed: [ 007_sd_reattach.reattach_storage_domain ]
Link to suspected patches: N/A
Link to Job:
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5915/con...
Link to all logs:
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5915/art...
Error snippet from the log:
<error>
12:01:51 [basic_suit_el7] @ Run test: 007_sd_reattach.py: ERROR (in 0:00:44)
12:01:51 [basic_suit_el7] Error occured, aborting
12:01:51 [basic_suit_el7] Traceback (most recent call last):
12:01:51 [basic_suit_el7] File
"/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 267, in do_run
12:01:51 [basic_suit_el7] self.cli_plugins[args.ovirtverb].do_run(args)
12:01:51 [basic_suit_el7] File
"/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in do_run
12:01:51 [basic_suit_el7] self._do_run(**vars(args))
12:01:51 [basic_suit_el7] File
"/usr/lib/python2.7/site-packages/lago/utils.py", line 495, in wrapper
12:01:51 [basic_suit_el7] return func(*args, **kwargs)
12:01:51 [basic_suit_el7] File
"/usr/lib/python2.7/site-packages/lago/utils.py", line 506, in wrapper
12:01:51 [basic_suit_el7] return func(*args, prefix=prefix, **kwargs)
12:01:51 [basic_suit_el7] File
"/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 96, in
do_ovirt_runtest
12:01:51 [basic_suit_el7] raise RuntimeError('Some tests failed')
12:01:51 [basic_suit_el7] RuntimeError: Some tests failed
</error>
Best Regards,
Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
RHCSA | RHCVA | RHCE
IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)
OPEN SOURCE - 1 4 011 && 011 4 1
8 years
Re: [ovirt-devel] [vdsm] Engine XML: metadata and devices from XML
by Francesco Romani
On 03/17/2017 11:07 PM, Michal Skrivanek wrote:
>> On 17 Mar 2017, at 15:57, Francesco Romani <fromani(a)redhat.com> wrote:
>>
>> On 03/16/2017 08:03 PM, Francesco Romani wrote:
>>> On 03/16/2017 01:26 PM, Francesco Romani wrote:
>>>> On 03/16/2017 11:47 AM, Michal Skrivanek wrote:
>>>>>> On 16 Mar 2017, at 09:45, Francesco Romani <fromani(a)redhat.com> wrote:
>>>>>>
>>>>>> We talked about sending storage device purely on metadata, letting Vdsm
>>>>>> rebuild them and getting the XML like today.
>>>>>>
>>>>>> In the other direction, Vdsm will pass through the XML (perhaps only
>>>>>> parts of it, e.g. the devices subtree) like before.
>>>>>>
>>>>>> This way we can minimize the changes we are uncertain of, and more
>>>>>> importantly, we can minimize the risky changes.
>>>>>>
>>>>>>
>>>>>> The following is a realistic example of how the XML could look like if
>>>>>> we send all but the storage devices. It is built using my pyxmlpickle
>>>>>> module (see [3] below).
>>>>> That’s quite verbose. How much work would it need to actually minimize it and turn it into something more simple.
>>>>> Most such stuff should go away and I believe it would be beneficial to make it difficult to use to discourage using metadata as a generic junkyard
>>>> It is verbose because it is generic - indeed perhaps too generic.
>>>> I can try something else based on a concept from Martin Polednik. Will
>>>> follow up soon.
>>> Early preview:
>>> https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic...
>>>
>>> still plenty of TODOs, I expect to be reviewable material worst case
>>> monday morning.
>> This is how typical XML could look like:
>>
>> <metadata>
>> <ovirt-tune:qos />
>> <ovirt-vm:vm />
>> <devices>
>> <ovirt-instance:graphics>
> not under the <ovirt-vm:vm>?
> any reason?
No reason, I'll move under it
Bests,
--
Francesco Romani
Red Hat Engineering Virtualization R & D
IRC: fromani
8 years
Friendly reminder on how to run OST on your patches
by Eyal Edri
Hi oVirt developers,
A few weeks ago we announced that it is now possible to run oVirt System
Tests on any open patch in oVirt [1].
Just wanted to remind everyone how easy it to run the whole basic suite or
upgrade suite on your open patches.
Here is a summary of the steps needed to run the job [2]:
*How to use?*
-
Add a comment to your open patch in Gerrit and write '*ci please build*'
-
Wait for the 'build-on-demand' job to finish and copy the URL of
the build that shows up on the comments in Gerrit.
-
Go the manual job [2] and click 'Build with parameters' [3]
-
Add your 'build-on-demand' URLs to the job (you can put multiple
URLs, one per line)
-
Choose the oVirt version you wish to test (should match to the
oVirt version of your patch).
-
Choose the suite type from the drop-down menu (choose basic to run
normal sanity or upgrade to test upgrade engine)
There are other options to choose, but the default ones will work best
for most cases,
You can checkout the documentation [4] for more detailed info.
Feel free to reach out to infra team for more info or help!
[1] https://lists.ovirt.org/pipermail/devel/2017-February/029565.html
[2] http://jenkins.ovirt.org/job/ovirt-system-tests_manual/
[3] make sure you have the 'dev' role for Jenkins, if you don't, send email
to infra-support(a)ovirt.org and ask to be added.
[4]
http://ovirt-system-tests.readthedocs.io/en/latest/docs/CI/developers_inf...
--
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
8 years, 1 month
