On Thu, Aug 18, 2016 at 9:45 AM, Eyal Edri wrote:
>
>
> On Thu, Aug 18, 2016 at 10:38 AM, Michal Skrivanek <
> michal.skriva...@redhat.com> wrote:
>
>>
>> On 18 Aug 2016, at 09:32, Sandro Bonazzola wrote:
>>
>>
>>
>> On Thu, Aug 18, 2016 at 9:19 AM, Michal
It is not run if you don't choose to deploy external provider on the host
add dialog.
It won't do that if you don't choose it.
Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email:
Hi all,
Though there are many solutions that integrate with oVirt to provide
disaster recovery for the guest images, these solutions either rely on
backup agents running on guests or third party software and are complicated
to setup
Since oVirt already integrates with glusterfs, we can leverage
On September 14, 2016 at 8:40:09 AM, Yaniv Dary (yd...@redhat.com) wrote:
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
>
> Tel : +972 (9) 7692306
> 8272306
> Email: yd...@redhat.com
> IRC : ydary
>
>
> On Wed,
Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary
On Wed, Sep 14, 2016 at 4:36 PM, Tony James wrote:
> On September 14,
On September 14, 2016 at 3:13:41 AM, Yaniv Dary (yd...@redhat.com) wrote:
> We will not be support installation for OSP. This is not part of the
> supported feature we added in 4.0.
In the process of deploying a node/hypervisor ovirt_host_deploy tries
to run the openstack-config command to write
Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary
On Wed, Sep 14, 2016 at 5:03 PM, Tony James wrote:
> On September 14,
On September 14, 2016 at 8:57:14 AM, Yaniv Dary (yd...@redhat.com) wrote:
> It is not run if you don't choose to deploy external provider on the host
> add dialog.
> It won't do that if you don't choose it.
True, thanks for clarifying. Why do we provide the option if using it
is not supported?
I think that what's missing in build-artifacts.sh is the following commands
that exist in check-patch.sh:
easy_install pip
pip install -U nose==1.3.7
This should install the right version for nose (that doesn't exist in rhel
yum repos)
On Wed, Sep 14, 2016 at 10:31 PM, Eyal Edri
The build-artifacts job is failing on master now with this error:
19:09:23 Error: NOSE is too old, please install NOSE 1.3.7 or later
19:09:23 make[1]: *** [tests] Error 1
19:09:23 make[1]: Leaving directory
Its actually a good question to know if standard CI supports versions of
RPMs.
Barak - do you know if we can specify in build-artifacts.packages file a
version requirement?
for e.g python-nose >= 1.3.7
On Wed, Sep 14, 2016 at 10:21 PM, Nir Soffer wrote:
> The
On Wed, Sep 14, 2016 at 10:31 PM, Eyal Edri wrote:
> Its actually a good question to know if standard CI supports versions of
> RPMs.
> Barak - do you know if we can specify in build-artifacts.packages file a
> version requirement?
>
> for e.g python-nose >= 1.3.7
This can be
On Wed, Sep 14, 2016 at 10:40 PM, Irit Goihman wrote:
> I think that what's missing in build-artifacts.sh is the following commands
> that exist in check-patch.sh:
>
> easy_install pip
> pip install -U nose==1.3.7
We cannot do this in brew/koji, you can use only packages
On Wed, Sep 14, 2016 at 10:43 PM, Nir Soffer wrote:
> On Wed, Sep 14, 2016 at 10:40 PM, Irit Goihman wrote:
>> I think that what's missing in build-artifacts.sh is the following commands
>> that exist in check-patch.sh:
>>
>> easy_install pip
>> pip
On Wed, Sep 14, 2016 at 10:23:29AM +0200, Sandro Bonazzola wrote:
> On Wed, Sep 14, 2016 at 10:13 AM, Yaniv Dary wrote:
>
> > We will not be support installation for OSP. This is not part of the
> > supported feature we added in 4.0.
> > We will not be testing this or making
On Wed, Sep 14, 2016 at 11:38 AM, Michal Skrivanek
wrote:
>
> > On 14 Sep 2016, at 11:06, Martin Polednik wrote:
> >
> > On 14/09/16 10:42 +0200, Sandro Bonazzola wrote:
> >> On Mon, Aug 29, 2016 at 11:01 AM, Sandro Bonazzola >
>
Fyi oVirt products maintainers,
An oVirt build for an official release is going to start right now.
If you're a maintainer for any of the projects included in oVirt
distribution and you have changes in your package ready to be released
please:
- bump version and release to be GA ready
- tag your
> On 14 Sep 2016, at 11:06, Martin Polednik wrote:
>
> On 14/09/16 10:42 +0200, Sandro Bonazzola wrote:
>> On Mon, Aug 29, 2016 at 11:01 AM, Sandro Bonazzola
>> wrote:
>>
>>> Hi,
>>> within CentOS Virt SIG interest in having ppc64le and aarch64 as
On Wed, Sep 14, 2016 at 11:09 AM, Sandro Bonazzola
wrote:
> Hi, we received a patch to ovirt-host-deploy
> https://gerrit.ovirt.org/63707 related to a change in OpenVSwitch
> configuration between
> Red Hat OpenStack Platform 7 or older and Red Hat OpenStack Platform 8 or
Hi, we received a patch to ovirt-host-deploy
https://gerrit.ovirt.org/63707 related
to a change in OpenVSwitch configuration between
Red Hat OpenStack Platform 7 or older and Red Hat OpenStack Platform 8 or
newer.
- We need to ensure to catch these changes in our testing
- We need to ensure oVirt
On Wed, Sep 14, 2016 at 10:13 AM, Yaniv Dary wrote:
> We will not be support installation for OSP. This is not part of the
> supported feature we added in 4.0.
> We will not be testing this or making fixes. We can accept patches and
> help with review, but it will be a upstream
On Mon, Aug 29, 2016 at 11:01 AM, Sandro Bonazzola
wrote:
> Hi,
> within CentOS Virt SIG interest in having ppc64le and aarch64 as supported
> architecture in oVirt has raised.
> Packages from oVirt 4.0.2 has been built for both architectures for
> hypervisor host side.
>
On 14/09/16 10:42 +0200, Sandro Bonazzola wrote:
On Mon, Aug 29, 2016 at 11:01 AM, Sandro Bonazzola
wrote:
Hi,
within CentOS Virt SIG interest in having ppc64le and aarch64 as supported
architecture in oVirt has raised.
Packages from oVirt 4.0.2 has been built for both
We will not be support installation for OSP. This is not part of the
supported feature we added in 4.0.
We will not be testing this or making fixes. We can accept patches and help
with review, but it will be a upstream driven effort and needs to be
backwords compatible.
Yaniv Dary
Technical
24 matches
Mail list logo