Content-Type: text/plain; charset=utf-8
The following is a new meeting request:
Subject: oVirt3.5 - deep dive - Moving to Json/STOMP rpc
Organizer: "Barak Azulay" <bazulay(a)redhat.com>
Time: Wednesday, August 27, 2014, 4:30:00 PM - 5:15:00 PM GMT +02:00 Jerusalem
Invitees: pkliczew(a)redhat.com; ovedo(a)redhat.com; users(a)ovirt.org; devel(a)ovirt.org
In this session we will explain how the communication model has changed between existing xmlrpc and new jsonrpc.
And explore the new implementation details.
google hangout link: https://www.youtube.com/watch?v=0FwM2oeb788
Content-Type: text/calendar; charset=utf-8; method=REQUEST; name=meeting.ics
SUMMARY:oVirt3.5 - deep dive - Moving to Json/STOMP rpc
DESCRIPTION:The following is a new meeting request:\n\nSubject: oVirt3.5 - d
eep dive - Moving to Json/STOMP rpc \nOrganizer: "Barak Azulay" <bazulay@red
hat.com> \n\nTime: Wednesday\, August 27\, 2014\, 4:30:00 PM - 5:15:00 PM GM
T +02:00 Jerusalem\n \nInvitees: pkliczew(a)redhat.com\; ovedo(a)redhat.com\; us
ers(a)ovirt.org\; devel(a)ovirt.org \n\n\n*~*~*~*~*~*~*~*~*~*\n\nIn this session
we will explain how the communication model has changed between existing xm
lrpc and new jsonrpc. \nAnd explore the new implementation details. \n\n\ngo
ogle hangout link: https://www.youtube.com/watch?v=0FwM2oeb788 \nwiki page:h
Ever since starting to work on oVirt around 3 years ago I've been
striving for the perfect development and test environment. I was
inspired by Yaniv's recent deep dive on Foreman integration and
thought I'd ask people to share their setups and any tips and tricks
so we can all become better, more efficient developers.
My setup consists of my main work laptop and two mini-Dell servers. I
run the engine on my laptop and I serve NFS and iSCSI (using
targetcli) from this system as well. I use the ethernet port on the
laptop to connect it to a subnet with the two Dell systems.
Some goals for my setup are:
- Easy provisioning of the virt-hosts so I can quickly test on Fedora
and CentOS without spending lots of time reinstalling
- Ability to test block and nfs storage
- Automation of test scenarios involving engine and hosts
To help me reach these goals I've deployed cobbler on my laptop and it
does a pretty good job at managing PXE boot configurations for my
hosts (and VMs) so they can be automatically intalled as needed.
After viewing Yaniv's presentation, it seems that Forman/Puppet are
the way of the future but it does seem a bit more involved to set up.
I am definitely curious if others are using Foreman in their personal
dev/test environment and can offer some insight on how that is working
Thanks, and I look forward to reading about more of your setups! If
we get enough of these, maybe this could make a good section of the
The CfP for the eleventh annual Latin American Free Software Conference closes on Aug. 29.
(The page appears to be down right now, but hopefully will be up soon.)
oVirt Community Manager
Project Atomic Community Lead
Open Source and Standards, Red Hat - http://community.redhat.com
Phone: +1 574 383 9BKP
IRC: bkp @ OFTC
I'm having problem connecting from terminal session (not X session)
Everything works perfectly well from the X session.
One of my pam modules connects to vm manager, but triggers the following error:
File "/usr/lib/python2.6/site-packages/ovirtsdk/infrastructure/proxy.py", line 169, in __doRequest
raise ConnectionError, str(e)
ovirtsdk.infrastructure.errors.ConnectionError: [ERROR]::Connection failure, [Errno 13] Permission denied
I can't figure out what the reason is
Content-Type: text/plain; charset=utf-8
The proposed feature will allow defining an arbitrary network in the DC as the management network for the cluster, which in its turn will allow assigning different VLANs for the management networks in the same DC.
Feature page can be found here - http://www.ovirt.org/Features/Management_Network_As_A_Role .
Please take a look into the page especially into "Open issues" section. I'd like to have your opinions on that.
Content-Type: text/html; charset=utf-8
<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>Hi All,<br></div><div><br></div><div>The proposed feature will allow defining an arbitrary network in the DC as the management network for the cluster, which in its turn will allow assigning different VLANs for the management networks in the same DC.<br></div><div><br></div><div>Feature page can be found here - <a target="_blank" href="http://www.ovirt.org/Features/Management_Network_As_A_Role" data-mce-href="http://www.ovirt.org/Features/Management_Network_As_A_Role">http://www.ovirt.org/Features/Management_Network_As_A_Role</a>.<br></div><div><br></div><div>Please take a look into the page especially into "Open issues" section. I'd like to have your opinions on that.<br></div><div><br></div><div><br>Best regards, <br>Yevgeny Zaspitsky <br><br></div></div></body></html>
The existing host networking API suffers from several deficiencies:
1. Part of it is a deprecated api designed for 3.0 clusters
2. SetupNetworks api introduced on 3.1 which is too complicated and
verbose on the one hand, and incapable to natively support network
topologies such as an isolated networks (network which isn't configured
on any network interface).
The complete list of deficiencies is listed on .
I'd like to propose an alternative API which addresses the existing
issues and will allow us to support new networking features .
In addition, there are requests samples on  to demonstrate how the api
should be called in order to achieve few of most commonly used network
Please review and share your feedback.