Our infra team already deploy HE via ansible you can check their work under
https://github.com/fusor/ansible-ovirt
Best Regards
On Wed, Sep 27, 2017 at 6:16 PM, Yaniv Kaul wrote:
>
>
> On Wed, Sep 27, 2017 at 5:15 PM, Phillip Bailey
> wrote:
>
>> Hi all,
Yes.
On Sep 27, 2017 19:52, "Greg Sheremeta" wrote:
Hi Ori,
Sounds nice :) Your invite came through for me at "Mon Oct 2, 2017 4pm –
5pm (EDT)" -- but double checking, this is 4pm Israel time, right?
Best wishes,
Greg
On Wed, Sep 27, 2017 at 9:42 AM, Ori Liel
Hi Ori,
Sounds nice :) Your invite came through for me at "Mon Oct 2, 2017 4pm –
5pm (EDT)" -- but double checking, this is 4pm Israel time, right?
Best wishes,
Greg
On Wed, Sep 27, 2017 at 9:42 AM, Ori Liel wrote:
> This coming Monday, Oct 2, I will present a new feature
On Wed, Sep 27, 2017 at 12:22 PM, John Marks wrote:
> Thanks Greg. I will add this link.
> Also, under the same list, the *Release Management *link leads to an
> empty page. Any suggestions?
>
Not from me :)
+sandro
> Thanks
> John
>
> On Wed, Sep 27, 2017 at 6:33 PM, Greg
Thanks Greg. I will add this link.
Also, under the same list, the *Release Management *link leads to an empty
page. Any suggestions?
Thanks
John
On Wed, Sep 27, 2017 at 6:33 PM, Greg Sheremeta wrote:
> I would link it to
>
On Wed, Sep 27, 2017 at 10:56 AM, Juan Hernández
wrote:
> On 09/27/2017 03:51 PM, Dafna Ron wrote:
>
>> hi,
>>
>> we have some failures in CQ and they seem to be related to failure to
>> build engine packages.
>>
>>
>> 1. first failure reported:
>>
I would link it to
https://www.ovirt.org/develop/developer-guide/engine/engine-development-environment/
which I have spent a lot of time trying to make very clear :)
Let me know if you have improvements!
Best wishes,
Greg
On Wed, Sep 27, 2017 at 10:49 AM, John Marks wrote:
On Wed, Sep 27, 2017 at 5:15 PM, Phillip Bailey wrote:
> Hi all,
>
> I'm working on the new Cockpit hosted engine wizard and could use some
> input from all of you. One goal of this project is to move away from
> reliance on the existing OTOPI-based tools and towards an
Thanks guys. Rebase fixed the issue
On Wed, Sep 27, 2017 at 10:14 AM, Eyal Edri wrote:
> In the past, we had similar issues when jobs didn't clean up after their
> run, if we're using shared maven cache per slave, it might be the same
> issue.
> So, if a previous job run on
On 09/27/2017 03:51 PM, Dafna Ron wrote:
hi,
we have some failures in CQ and they seem to be related to failure to
build engine packages.
1. first failure reported:
http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64/5313/
This happened due to failed build:
On Wed, Sep 27, 2017 at 5:29 PM, Sandro Bonazzola wrote:
>
>
> 2017-09-27 15:31 GMT+02:00 Dan Kenigsberg :
>>
>> On Wed, Sep 27, 2017 at 3:34 PM, Yedidyah Bar David
>> wrote:
>> > On Wed, Sep 27, 2017 at 1:42 PM, Dan Kenigsberg
2017-09-27 15:31 GMT+02:00 Dan Kenigsberg :
> On Wed, Sep 27, 2017 at 3:34 PM, Yedidyah Bar David
> wrote:
> > On Wed, Sep 27, 2017 at 1:42 PM, Dan Kenigsberg
> wrote:
> >> On Wed, Sep 27, 2017 at 1:27 PM, Yaniv Kaul
Hi all,
I'm working on the new Cockpit hosted engine wizard and could use some
input from all of you. One goal of this project is to move away from
reliance on the existing OTOPI-based tools and towards an ansible-based
approach.
The items below are things we'd like to do using ansible, if
hi,
we have some failures in CQ and they seem to be related to failure to
build engine packages.
1. first failure reported:
http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64/5313/
This happened due to failed build:
This coming Monday, Oct 2, I will present a new feature in the API which
has to do with documentation of API operations (it's more exciting than it
sounds).
This presentation is important for everyone submitting patches to the
ovirt-engine-api-model, because these patches will be required to use
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20171002T20Z
DTEND:20171002T21Z
DTSTAMP:20170927T133606Z
ORGANIZER;CN=ol...@redhat.com:mailto:ol...@redhat.com
UID:77bll67vjabrf99d6329pv1...@google.com
On Wed, Sep 27, 2017 at 3:34 PM, Yedidyah Bar David wrote:
> On Wed, Sep 27, 2017 at 1:42 PM, Dan Kenigsberg wrote:
>> On Wed, Sep 27, 2017 at 1:27 PM, Yaniv Kaul wrote:
>>>
>>>
>>> On Wed, Sep 27, 2017 at 12:50 PM, Dan Kenigsberg
On Wed, Sep 27, 2017 at 1:42 PM, Dan Kenigsberg wrote:
> On Wed, Sep 27, 2017 at 1:27 PM, Yaniv Kaul wrote:
>>
>>
>> On Wed, Sep 27, 2017 at 12:50 PM, Dan Kenigsberg wrote:
>>>
>>> When trying to install ovirt-host-4.2 from
>>>
>>>
On Wed, Sep 27, 2017 at 1:27 PM, Yaniv Kaul wrote:
>
>
> On Wed, Sep 27, 2017 at 12:50 PM, Dan Kenigsberg wrote:
>>
>> When trying to install ovirt-host-4.2 from
>>
>> ovirt-release-master-4.2.0-0.5.master.2017092721.git88364d1.el7.centos.noarch
>> on a
On Wed, Sep 27, 2017 at 12:50 PM, Dan Kenigsberg wrote:
> When trying to install ovirt-host-4.2 from
> ovirt-release-master-4.2.0-0.5.master.2017092721.
> git88364d1.el7.centos.noarch
> on a RHEL-7.4 host we get
>
> Error: Package:
>
When trying to install ovirt-host-4.2 from
ovirt-release-master-4.2.0-0.5.master.2017092721.git88364d1.el7.centos.noarch
on a RHEL-7.4 host we get
Error: Package:
ovirt-host-4.2.0-0.0.master.20170913090858.git0bfa7ab.el7.centos.noarch
(ovirt-master-snapshot)
Requires:
In the past, we had similar issues when jobs didn't clean up after their
run, if we're using shared maven cache per slave, it might be the same
issue.
So, if a previous job run on the same slave and left artifacts there, it
might affect another job.
What we did in the old job is to remove any
On Wed, Sep 27, 2017 at 9:10 AM, Barak Korren wrote:
>
>
> On 26 September 2017 at 23:22, Ala Hino wrote:
>
>> Hi,
>>
>> In the following build, I see that the build passes on Fedora but is
>> unstable on RHEL. However, checking CI console, I see that the
On 26 September 2017 at 23:22, Ala Hino wrote:
> Hi,
>
> In the following build, I see that the build passes on Fedora but is
> unstable on RHEL. However, checking CI console, I see that the build
> succeeded.
>
> Links to builds:
>
>
24 matches
Mail list logo