On Tue, Jul 5, 2016 at 10:44 AM, Yaniv Bronheim wrote:
> Hi
> I do work to remove the cpopen usages from execCmd. Using std popen over
> py3 and subprocess32 over py2 which both implements the same api. The only
> gap is the output object for async calls that we need to
FYI,
Due to various holidays, PTOs and an on going 3.6.8 build there is not
infra support for the next two days.
If there are urgent issues, please open a ticket to infra-supp...@ovirt.org
and we'll do our best to handle it if possible.
--
Eyal Edri
Associate Manager
RHEV DevOps
EMEA ENG
Hi
I do work to remove the cpopen usages from execCmd. Using std popen over
py3 and subprocess32 over py2 which both implements the same api. The only
gap is the output object for async calls that we need to align with the
standard implementation and modify our current usages. I don't think that
Hi!
I'm writing code for a new verb (sparsifyInplace) in VDSM and got two
different opinions about whether to use SPM or SDM for it:
1) SDM is the new correct approach, need to use it.
2) SDM is on early stage and may be changed significantly, so it is better
to use SPM as mature and reliable
On 05/07/16 12:07 +0300, Shmuel Melamud wrote:
Hi!
I'm writing code for a new verb (sparsifyInplace) in VDSM and got two
different opinions about whether to use SPM or SDM for it:
1) SDM is the new correct approach, need to use it.
2) SDM is on early stage and may be changed significantly, so
Not only was June the occasion of the Red Hat Summit event in San
Francisco, where oVirt was well-represented in the event and within
Community Central, but it was also the month where the year's biggest
release, oVirt 4.0!
The latest release of oVirt features:
* A New Administration Portal
*
Hi Giorgio -
Unfortunately, I don't actually have any infiniband hardware to test with
in my lab. I'm not even sure anybody on the Node team knew there were IPoIB
use environments. That's great news (for 3.6)!
oVirt Node Next is much closer to "plain" RHEL. This sounds like it may be
a bug in