oVirt 3.6.1 branch has been created
by Sandro Bonazzola
Hi,
just an heads up we branched for 3.6.1 stabilization this morning.
If you have patches targeted to 3.6.1 you now need to cherry-pick them to
3.6.1 branch too.
A build is scheduled for today at 2 PM TLV time.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
9 years
[Need help] Want to write my graduate thesis related to ovirt
by John Hunter
Hi guys,
I am college student who is going to graduate next year, major in CS, I
want to
work on my graduate thesis related to ovirt.
For now I need a project which I can work on for the next 6 month, so I need
an idealist which I can reference to write a proposal.
I have contributed to #dri-devel during my Google Summer of Code project,
so I
know how opensource groups works, though workflow are kind of different.
I am appreciate if anyone could help, and I hope some one could be my
mentor.
BR,
Zhao Junwang
--
Best regards
Junwang Zhao
Department of Computer Science &Technology
Peking University
Beijing, 100871, PRC
9 years
FOSDEM16 Virt & IaaS Devroom CFP Extension, Speaker Mentoring, CoC
by Mikey Ariel
The CFP for the Virtualization & IaaS devroom at FOSDEM 2016 is in full
swing, and we'd like to share a few updates with you:
-------------------------
Speaker Mentoring Program
-------------------------
As a part of the rising efforts to grow our communities and encourage a
diverse and inclusive conference ecosystem, we're happy to announce that
we'll be offering mentoring for newcomer speakers. Our mentors can help
you with tasks such as reviewing your abstract, reviewing your
presentation outline or slides, or practicing your talk with you.
You may apply to the mentoring program as a newcomer speaker if you:
* Never presented before or
* Presented only lightning talks or
* Presented full-length talks at small meetups (<50 ppl)
Submission guidelines:
* Mentored presentations will have 25-minute slots, where 20 minutes
will include the presentation and 5 minutes will be reserved for questions.
* The number of newcomer session slots is limited, so we will probably
not be able to accept all applications.
* You must submit your talk and abstract to apply for the mentoring
program, our mentors are volunteering their time and will happily
provide feedback but won't write your presentation for you! If you are
experiencing problems with Pentabarf, the proposal submission interface,
or have other questions, you can email iaas-virt-devroom at
lists.fosdem.org and we will try to help you.
How to apply:
* Follow the same procedure to submit an abstract in Pentabarf as
standard sessions. Instructions can be found in our original CFP
announcement:
http://community.redhat.com/blog/2015/10/call-for-proposals-fosdem16-virt...
* In addition to agreeing to video recording and confirming that you can
attend FOSDEM in case your session is accepted, please write "speaker
mentoring program application" in the "Submission notes" field, and list
any prior speaking experience or other relevant information for your
application.
Call for mentors!
Interested in mentoring newcomer speakers? We'd love to have your help!
Please email iaas-virt-devroom at lists.fosdem.org with a short speaker
bio and any specific fields of expertise (for example, KVM, OpenStack,
storage, etc) so that we can match you with a newcomer speaker from a
similar field. Estimated time investment can be as low as a 5-10 hours
in total, usually distributed weekly or bi-weekly.
Never mentored a newcomer speaker but interested to try? Our mentoring
program coordinator will be happy to answer your questions and give you
tips on how to optimize the mentoring process. Email us and we'll be
happy to answer your questions!
-------------------------
CFP Deadline Extension
-------------------------
To help accommodate the newcomer speaker proposals, we have decided to
extend the deadline for submitting proposals by one week.
The new deadline is **TUESDAY, DECEMBER 8 @ midnight CET**.
-------------------------
Code of Conduct
-------------------------
Following the release of the updated code of conduct for FOSDEM[1], we'd
like to remind all speakers and attendees that all of the presentations
and discussions in our devroom are held under the guidelines set in the
CoC and we expect attendees, speakers, and volunteers to follow the CoC
at all times.
If you submit a proposal and it is accepted, you will be required to
confirm that you accept the FOSDEM CoC. If you have any questions about
the CoC or wish to have one of the devroom organizers review your
presentation slides or any other content for CoC compliance, please
email iaas-virt-devroom at lists.fosdem.org and we will do our best to
help you out.
[1] https://www.fosdem.org/2016/practical/conduct/
--
Mikey Ariel
Community Lead, oVirt
www.ovirt.org
"To be is to do" (Socrates)
"To do is to be" (Jean-Paul Sartre)
"Do be do be do" (Frank Sinatra)
Mobile: +420-702-131-141
IRC: mariel / thatdocslady
Twitter: @ThatDocsLady
9 years
Scripts for Engine development
by Shmuel Melamud
Hi!
These are scripts that I'm using for development. Maybe they will save your
time or at least will be helpful for newbies. Please, let me know if you
find something useful.
They assume the following setup: there is a directory for the Engine (set
by ENGINE_ROOT conf var). Subdirectories under it correspond to revisions
(master, 3.6, 3.5 etc.). You can freely add suffixes (e.g. 3.6-upgr). There
is always a current revision you're working on and ~/bin/engine-bin is set
to the corresponding bin/ directory. I've added ~/bin/engine-bin to PATH
and now if I run, for example, engine-setup, it runs engine-setup of the
revision I need currently.
Config file:
engine-scripts-conf - review it shortly just in case you need to change
something to fit your setup
Scripts:
engine - run the Engine
engine-autosetup - run engine-setup (taking into account additional options
that should be passed for 3.5, for example)
engine-build - build the Engine (this script has many options)
engine-dao-tests - run DAO tests
engine-gwt-debug - run the frontend in GWT debugging mode (there are also
several options in engine-build for GWT debugging)
engine-root - print current Engine root directory name
engine-setrevision - set or print the current revision
And one script for VDSM - it should be run on a host:
vdsm-deploy - removes old VDSM rpms, builds and installs the new ones,
puts ssl=false into vdsm.conf and restarts VDSM. If restart fails, runs
vdsm-tool configure --force and tries to start again. Maybe some of these
operations are redundant, but at the end I always get working VDSM ;)
vdsm-fix-firewall - fixes /etc/sysconfig/iptables to open non-TLS libvirtd
port. It is run automatically from vdsm-deploy, but may be run separately.
Shmuel
9 years
[vdsm] merge rights on master branch
by Dan Kenigsberg
Nir Soffer has been contributing to Vdsm for more than two years now.
Beyond his storage-related expertise, he is well-known for his thorough
code reviews and his pains when the master branch is broken. It's time
for him to take even bigger responsibility.
David, please grant Nir Soffer with merge rights on the master branch of
Vdsm.
I'll keep merging network, virt, and infra patches myself, but much less
than before. Adam keeps his merge right as before (he tends to use them
on emergencies only).
Regards,
Dan.
9 years
[2015-11-23] Weekly infra team status
by David Caro
--+Hr//EUsa8//ouuB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi everyone, last week updates:
* Jenkins upgraded to 1.638 from 1.60
This change cause a little havoc on friday builds, as the upgrade was n=
ot
as easy as it used to, there was an issue with the slaves config that
reverted it to an old version, making most of the slaves unavailable and
the available ones unstable, that was fixed on friday too, but due to
another unrelated network issue, it persisted a bit more than expected.
Thanks amachuk++!
* Network outage on friday
On friday there was an issue with the vendor that provides communication
between the PHX datacenter and europe, causing a huge delay and instabi=
lity
in the network, affecting the upgrade process above, it was partially
solved on friday evening, and it's totally solved now.
* Repoproxy issues
On sunday there was a few hours where one of the mirroring services we =
have
on phx stopped working and made any jobs that use it fail (with unable =
to
contact repo), that was solved on site and most of the patches affected
were retriggered manually, thanks eedri for handling this.
NOTE: So for all that have failed jobs from friday/saturday/sunday that
were not retriggered, to get it retriggered just take note of the last
patch in the change that changed something more than just the commit, t=
hen
go to [1] and enter the change-id/commit-id, **make sure you hit the
'Inclued All Patchsets' checkbox, then tick the change with more than j=
ust
commit changes, and hit 'trigger selected'. That will retrigger the tes=
ts
only for that patch, but the result of that run will be propagated to a=
ll
the patches that have no code changes from that one.
[1]: http://jenkins.ovirt.org/gerrit_manual_trigger/
* Github group
We started adding people to the Github organization to get more visibil=
ity
in Github for the oVirt project, and so far we have 41 members :)
Just make sure to set yourself as 'public' member there, so anyone can =
see
you are part of it!
If anyone has not received the invite, please send me an email or ping =
me
on irc and I'll send you one.
--=20
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605
Email: dcaro(a)redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605
--+Hr//EUsa8//ouuB
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJWUyWUAAoJEEBxx+HSYmnDZSAIAIoJv1oBipTmHLdcf256WGGu
tqr7a5XdkJWk/m6FY8QM1wNUxpUlvrONznUdHxmKhXnM8kab9IrV0/UUM5VL4gOw
VtS24s4lOaWG8NF9crJ9T9RDH91dV4C+rFchIqez2nFM7/Yvr6XMwfN1wDcN3xXd
o5geFJcXeZAo+snuJ0dMg6mCI/opxz+on7kC9N/BqzXRfsHY8qcq29q7sA+VrgBt
aSiABLMDSzm93RDyX+jvoAPfmkKIat/IeQDrnFztdNjM/FP5YcM/t64mDzaXVsyb
8yMaCQEcqh38NoykgRwcsTs9kq46XaNWkMQlCsl6GyjFZZNKYEa7Xu1/GG0QI/A=
=MpK2
-----END PGP SIGNATURE-----
--+Hr//EUsa8//ouuB--
9 years
In windows OS & firefox brower, Window.Location.replace(url) would stop System to execute Command, and would not catch any error info.But other OS like firefox in linux would not happen like that
by 温蓓
This is a multi-part message in MIME format.
------=_NextPart_56442692_0A1FE740_5741B7DF
Content-Type: text/plain;
charset="gb18030"
Content-Transfer-Encoding: base64
SGlJIHdhbnQgdG8gcmVkaXJjdCB0aGUgcGFnZSB3aGVuIG92aXJ0IGFkbWluIGxvZ291dCwg
c28gSSBhZGQgOldpbmRvdy5Mb2NhdGlvbi5yZXBsYWNlKCIvdGVzdC5odG1sIikgaW4gQXBw
bGljYXRpb25QbGFjZU1hbmFnZXIuamF2YSBhcyBiZWxvdzogIEBPdmVycmlkZSAgICAgcHVi
bGljIHZvaWQgcmV2ZWFsRGVmYXVsdFBsYWNlKCkgeyAgICAgICAgIFBsYWNlUmVxdWVzdCBw
ciA9IGdldERlZmF1bHRQbGFjZSgpOyAgICAgICAgIGlmIChwciA9PSBudWxsKSB7ICAgICAg
ICAgICAgIC8vV2luZG93LkxvY2F0aW9uLnJlcGxhY2UoIi90ZXN0Lmh0bWwiKTsgLy8kTk9O
LU5MUy0xJCAgICAgICAgIH0gZWxzZSB7ICAgICAgICAgICAgIHJldmVhbFBsYWNlKHByKTsg
ICAgICAgICB9ICAgICB9IG9yIGluIExvZ2luTW9kZWwuamF2YVxCYXNlQXBwbGljYXRpb25J
bml0LmphdmEgZXRjLiBJdCBjYW4gYWNoaWV2ZSB0byByZWRpcmVjdCBieSBjaHJvbWUsSUUg
YW5kIGZpcmVmb3ggaW4gTGludXgsIGFuZCB3b3VsZCBleGVjdXRlIExvZ291dFVzZXJDb21t
YW5kIHRvIGNsZWFuIHVzZXIgc2Vzc2lvbixUaGVuIGF0IGZpcmVmb3ggaW4gV2luZG93cyBu
byBtYXR0ZXIgd2hpY2ggdmVyc2lvbiwgaXQgY291bGQgcmVkaXJlY3QgYnV0IHdvdWxkIG5v
dCBleGVjdXRlIExvZ291dFVzZXJDb21tYW5kLCBzbyBJIGNhbiBsb2cgaW50byBTeXN0ZW0g
YnkgcHJldmlvdXMgVVJMIHdpdGhvdXQgcGFzc3dvcmQuICBIb3cgY2FuIEkgcmVkaXJlY3Qg
VVJMIHdoZW4gbG9nb3V0P0lzIHRoZXJlIGFueSBjb25maWcgZmlsZXMgZm9yIHRoaXM/IEkg
Y291bGQgbm90IGZpbmQgaXQsIHRoYW5rcyBhIGxvdCA6KSBWZXJzaW9uLVJlbGVhc2UgbnVt
YmVyIG9mIHNlbGVjdGVkIGNvbXBvbmVudCAoaWYgYXBwbGljYWJsZSk6IDMuNC41IFN0ZXBz
IHRvIFJlcHJvZHVjZTogMS51cGRhdGUgY29kZTpBcHBsaWNhdGlvblBsYWNlTWFuYWdlci5q
YXZhICBwdWJsaWMgdm9pZCByZXZlYWxEZWZhdWx0UGxhY2UoKSB7ICAgICAgICAgUGxhY2VS
ZXF1ZXN0IHByID0gZ2V0RGVmYXVsdFBsYWNlKCk7ICAgICAgICAgaWYgKHByID09IG51bGwp
IHsgICAgICAgICAgICAgLy9XaW5kb3cuTG9jYXRpb24ucmVwbGFjZSgiL3Rlc3QuaHRtbCIp
OyAvLyROT04tTkxTLTEkICAgICAgICAgfSBlbHNlIHsgICAgICAgICAgICAgcmV2ZWFsUGxh
Y2UocHIpOyAgICAgICAgIH0gICAgIH0gMi5sb2dpbiBzeXN0ZW0gYW5kIGxvZ291dCAzLmlu
cHV0IHByZXZpb3VzIHVybCBsaWtlIDp4eHh4eHgvb3ZpcnQtZW5naW5lL3dlYmFkbWluLz9s
b2NhbGU9emhfQ04jdm1zIGFuZCBjYW4gcmVkaXJlY3QuIEFjdHVhbCByZXN1bHRzOiByZWRp
cmVjdCBpbnRvIHZtIHBhZ2UuIEV4cGVjdGVkIHJlc3VsdHM6IHJlZGlyZWN0IGludG8gbG9n
aW4gcGFnZS4=
------=_NextPart_56442692_0A1FE740_5741B7DF
Content-Type: text/html;
charset="gb18030"
Content-Transfer-Encoding: base64
SGk8cHJlIGNsYXNzPSJiel9jb21tZW50X3RleHQKICAgICAgICAgICAgICAgICBiel93cmFw
X2NvbW1lbnRfdGV4dCIgaWQ9ImNvbW1lbnRfdGV4dF8wIj5JIHdhbnQgdG8gcmVkaXJjdCB0
aGUgcGFnZSB3aGVuIG92aXJ0IGFkbWluIGxvZ291dCwgc28gSSBhZGQgOldpbmRvdy5Mb2Nh
dGlvbi5yZXBsYWNlKCIvdGVzdC5odG1sIikgaW4gQXBwbGljYXRpb25QbGFjZU1hbmFnZXIu
amF2YSBhcyBiZWxvdzoKIEBPdmVycmlkZQogICAgcHVibGljIHZvaWQgcmV2ZWFsRGVmYXVs
dFBsYWNlKCkgewogICAgICAgIFBsYWNlUmVxdWVzdCBwciA9IGdldERlZmF1bHRQbGFjZSgp
OwogICAgICAgIGlmIChwciA9PSBudWxsKSB7CiAgICAgICAgICAgIC8vV2luZG93LkxvY2F0
aW9uLnJlcGxhY2UoIi90ZXN0Lmh0bWwiKTsgLy8kTk9OLU5MUy0xJAogICAgICAgIH0gZWxz
ZSB7CiAgICAgICAgICAgIHJldmVhbFBsYWNlKHByKTsKICAgICAgICB9CiAgICB9Cm9yIGlu
IExvZ2luTW9kZWwuamF2YVxCYXNlQXBwbGljYXRpb25Jbml0LmphdmEgZXRjLgpJdCBjYW4g
YWNoaWV2ZSB0byByZWRpcmVjdCBieSBjaHJvbWUsSUUgYW5kIGZpcmVmb3ggaW4gTGludXgs
IGFuZCB3b3VsZCBleGVjdXRlIExvZ291dFVzZXJDb21tYW5kIHRvIGNsZWFuIHVzZXIgc2Vz
c2lvbixUaGVuIGF0IGZpcmVmb3ggaW4gV2luZG93cyBubyBtYXR0ZXIgd2hpY2ggdmVyc2lv
biwgaXQgY291bGQgcmVkaXJlY3QgYnV0IHdvdWxkIG5vdCBleGVjdXRlIExvZ291dFVzZXJD
b21tYW5kLCBzbyBJIGNhbiBsb2cgaW50byBTeXN0ZW0gYnkgcHJldmlvdXMgVVJMIHdpdGhv
dXQgcGFzc3dvcmQuIApIb3cgY2FuIEkgcmVkaXJlY3QgVVJMIHdoZW4gbG9nb3V0P0lzIHRo
ZXJlIGFueSBjb25maWcgZmlsZXMgZm9yIHRoaXM/IEkgY291bGQgbm90IGZpbmQgaXQsIHRo
YW5rcyBhIGxvdCA6KQoKVmVyc2lvbi1SZWxlYXNlIG51bWJlciBvZiBzZWxlY3RlZCBjb21w
b25lbnQgKGlmIGFwcGxpY2FibGUpOgozLjQuNQoKU3RlcHMgdG8gUmVwcm9kdWNlOgoxLnVw
ZGF0ZSBjb2RlOkFwcGxpY2F0aW9uUGxhY2VNYW5hZ2VyLmphdmEKIHB1YmxpYyB2b2lkIHJl
dmVhbERlZmF1bHRQbGFjZSgpIHsKICAgICAgICBQbGFjZVJlcXVlc3QgcHIgPSBnZXREZWZh
dWx0UGxhY2UoKTsKICAgICAgICBpZiAocHIgPT0gbnVsbCkgewogICAgICAgICAgICAvL1dp
bmRvdy5Mb2NhdGlvbi5yZXBsYWNlKCIvdGVzdC5odG1sIik7IC8vJE5PTi1OTFMtMSQKICAg
ICAgICB9IGVsc2UgewogICAgICAgICAgICByZXZlYWxQbGFjZShwcik7CiAgICAgICAgfQog
ICAgfQoyLmxvZ2luIHN5c3RlbSBhbmQgbG9nb3V0CjMuaW5wdXQgcHJldmlvdXMgdXJsIGxp
a2UgOnh4eHh4eC9vdmlydC1lbmdpbmUvd2ViYWRtaW4vP2xvY2FsZT16aF9DTiN2bXMKYW5k
IGNhbiByZWRpcmVjdC4KCkFjdHVhbCByZXN1bHRzOgpyZWRpcmVjdCBpbnRvIHZtIHBhZ2Uu
CgpFeHBlY3RlZCByZXN1bHRzOgpyZWRpcmVjdCBpbnRvIGxvZ2luIHBhZ2UuCjwvcHJlPjxi
cj4=
------=_NextPart_56442692_0A1FE740_5741B7DF--
9 years
Fwd: engine-setup fails
by Idan Shaby
Solved the issue..
Thanks,
Idan
---------- Forwarded message ----------
From: Fred Rolland <frolland(a)redhat.com>
Date: Sun, Nov 22, 2015 at 11:56 AM
Subject: Re: [ovirt-devel] engine-setup fails
To: Idan Shaby <ishaby(a)redhat.com>
yum install ovirt-setup-lib
On Sun, Nov 22, 2015 at 11:46 AM, Idan Shaby <ishaby(a)redhat.com> wrote:
> Hi,
>
> I am trying to run engine-setup but it fails with this error:
> ***L:ERROR Internal error: No module named ovirt_setup_lib
>
> Does anyone know what's the issue?
>
> Thanks,
> Idan
>
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
9 years
engine-setup fails
by Idan Shaby
Hi,
I am trying to run engine-setup but it fails with this error:
***L:ERROR Internal error: No module named ovirt_setup_lib
Does anyone know what's the issue?
Thanks,
Idan
9 years
