[JIRA] (OVIRT-711) Re: ovirt-provider-ovn - new gerrit.ovirt.org project
by danken (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-711?page=com.atlassian.jira... ]
danken commented on OVIRT-711:
------------------------------
On Mon, Aug 29, 2016 at 02:43:02PM +0300, Eyal Edri wrote:
> On Mon, Aug 29, 2016 at 1:11 PM, Marcin Mirecki <mmirecki(a)redhat.com> wrote:
>
> > All,
> >
> > Can you please add a new project to gerrit.ovirt.org?
> > The project name: ovirt-provider-ovn
> >
> > The project will contain the ovn external network provider.
> > I will maintain it.
Ack from my end.
We need this package to server as an external network provider for OVN
(https://github.com/openvswitch/ovs/tree/master/ovn ) that is slated for
ovirt-4.1.
Regards,
Dan.
> Re: ovirt-provider-ovn - new gerrit.ovirt.org project
> -----------------------------------------------------
>
> Key: OVIRT-711
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-711
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: eyal edri [Administrator]
> Assignee: Barak Korren
>
> On Mon, Aug 29, 2016 at 1:11 PM, Marcin Mirecki <mmirecki(a)redhat.com> wrote:
> > All,
> >
> > Can you please add a new project to gerrit.ovirt.org?
> > The project name: ovirt-provider-ovn
> >
> > The project will contain the ovn external network provider.
> > I will maintain it.
> >
> > Thanks,
> > Marcin
> >
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
--
This message was sent by Atlassian JIRA
(v1000.285.1#100011)
8 years, 3 months
[JIRA] (OVIRT-713) Clean reposync directory after n times of sync failure
by Gal Ben Haim (oVirt JIRA)
Gal Ben Haim created OVIRT-713:
----------------------------------
Summary: Clean reposync directory after n times of sync failure
Key: OVIRT-713
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-713
Project: oVirt - virtualization made easy
Issue Type: New Feature
Reporter: Gal Ben Haim
Assignee: infra
Sometimes reposync fail to sync rpms that already been synced.
To resolve this issue, lago removes those rpms, and runs reposync again.
This resolution doesn't always work, and then we need to clean all the rpms that were synced.
We want lago to clear the cached rpms after n times of sync failure, and then try to sync again.
--
This message was sent by Atlassian JIRA
(v1000.285.1#100011)
8 years, 3 months
[JIRA] (OVIRT-712) Use repoman extra sources feature in VDSM check merge
by Gal Ben Haim (oVirt JIRA)
Gal Ben Haim created OVIRT-712:
----------------------------------
Summary: Use repoman extra sources feature in VDSM check merge
Key: OVIRT-712
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-712
Project: oVirt - virtualization made easy
Issue Type: New Feature
Reporter: Gal Ben Haim
Assignee: infra
When running check merge, new rpms with the latest patch are being generated.
currently those repos are being copied by reposync to /var/lib/lago/reposync.
Those rpms shouldn't be saved to the cache, thus we need to use repoman to include those rpms in the internal repo.
--
This message was sent by Atlassian JIRA
(v1000.285.1#100011)
8 years, 3 months
[JIRA] (OVIRT-711) Re: ovirt-provider-ovn - new gerrit.ovirt.org project
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-711?page=com.atlassian.jira... ]
Barak Korren reassigned OVIRT-711:
----------------------------------
Assignee: Barak Korren (was: infra)
> Re: ovirt-provider-ovn - new gerrit.ovirt.org project
> -----------------------------------------------------
>
> Key: OVIRT-711
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-711
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: eyal edri [Administrator]
> Assignee: Barak Korren
>
> On Mon, Aug 29, 2016 at 1:11 PM, Marcin Mirecki <mmirecki(a)redhat.com> wrote:
> > All,
> >
> > Can you please add a new project to gerrit.ovirt.org?
> > The project name: ovirt-provider-ovn
> >
> > The project will contain the ovn external network provider.
> > I will maintain it.
> >
> > Thanks,
> > Marcin
> >
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
--
This message was sent by Atlassian JIRA
(v1000.285.1#100011)
8 years, 3 months
[JIRA] (OVIRT-711) Re: ovirt-provider-ovn - new gerrit.ovirt.org project
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-711?page=com.atlassian.jira... ]
Barak Korren commented on OVIRT-711:
------------------------------------
> On Mon, Aug 29, 2016 at 1:11 PM, Marcin Mirecki <mmirecki(a)redhat.com> wrote:
>>
>> All,
>>
>> Can you please add a new project to gerrit.ovirt.org?
>> The project name: ovirt-provider-ovn
>>
>> The project will contain the ovn external network provider.
>> I will maintain it.
>>
Project created.
https://gerrit.ovirt.org/#/admin/projects/ovirt-provider-ovn
--
Barak Korren
bkorren(a)redhat.com
RHEV-CI Team
> Re: ovirt-provider-ovn - new gerrit.ovirt.org project
> -----------------------------------------------------
>
> Key: OVIRT-711
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-711
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: eyal edri [Administrator]
> Assignee: infra
>
> On Mon, Aug 29, 2016 at 1:11 PM, Marcin Mirecki <mmirecki(a)redhat.com> wrote:
> > All,
> >
> > Can you please add a new project to gerrit.ovirt.org?
> > The project name: ovirt-provider-ovn
> >
> > The project will contain the ovn external network provider.
> > I will maintain it.
> >
> > Thanks,
> > Marcin
> >
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
--
This message was sent by Atlassian JIRA
(v1000.285.1#100011)
8 years, 3 months
[JIRA] (OVIRT-711) Re: ovirt-provider-ovn - new gerrit.ovirt.org project
by eyal edri [Administrator] (oVirt JIRA)
eyal edri [Administrator] created OVIRT-711:
-----------------------------------------------
Summary: Re: ovirt-provider-ovn - new gerrit.ovirt.org project
Key: OVIRT-711
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-711
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: eyal edri [Administrator]
Assignee: infra
On Mon, Aug 29, 2016 at 1:11 PM, Marcin Mirecki <mmirecki(a)redhat.com> wrote:
> All,
>
> Can you please add a new project to gerrit.ovirt.org?
> The project name: ovirt-provider-ovn
>
> The project will contain the ovn external network provider.
> I will maintain it.
>
> Thanks,
> Marcin
>
--
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
--
This message was sent by Atlassian JIRA
(v1000.285.1#100011)
8 years, 3 months
Ansible work and organization
by Marc Dequènes (Duck)
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--rUake15nkmeqAJaPQq15DNkrU3qSBauM5
Content-Type: multipart/mixed; boundary="Bc659WIoxXX4Lhv6F7nK4c8PBqsasJf6j"
From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck(a)redhat.com>
To: oVirt Infra <infra(a)ovirt.org>
Cc: Michael Scherer <misc(a)redhat.com>, Karsten Wade <kwade(a)redhat.com>
Message-ID: <81a28335-daf0-6bec-f7ae-92490f605606(a)redhat.com>
Subject: Ansible work and organization
--Bc659WIoxXX4Lhv6F7nK4c8PBqsasJf6j
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Hello folks,
Since I started working on MM3 migration using Ansible, I received
absolutely no feedback on the Ansible side of my work (and I asked
several time, specifically on this aspect). At first I was new in the
project, this was an attempt, I did not have much access, so it was
created as an external git repository. Now very quickly an
'infra-ansible' repo was created and is already filling with review
requests, but it seems to me we missed a few steps to coordinate.
I'm not very familiar with the Gerrit workflow, but I'm learning, that's
why I asked how I could integrate my work into the new repo but got no
reply. It seemed to me my work could be a proper startup point, but now
I'm faced with splitting and reintegrating my work with what is already
coming in. It feels really useless a work, frustrating, and I also see
no reason to loose all the history.
Also I talked (ML, JIRA) about the roles we (in OSAS) were working on in
order to share the load of the maintenance across several projects. Our
experience is we often need almost the same classic features, so no
reason to recreate the wheel and maintain different versions. We cannot
trust any role on the Internet, but we can trust people in Red Hat or
well known contributors. Nobody seemed to have an objection on this;
nobody adked any question either. Nevertheless now the incoming reviews
shows all of this is ignored and we're doing exactly it: a new
postgresql role just popped-up in one review for example=C2=B8 but we alr=
eady
have one which is used by the MM3 work.
I really tried to not be pushy, to ask for your opinions and reviews,
but not much happened. I thought people were busy and it would come in
time. Now I really don't know how I can catch up.
So, we need to discuss:
- how OSAS is going to work with the infra team:
I'm new, so it's ok to feel a bit off, but I'd like better coordinati=
on.
I should not have to do extra work for integrating what I did on
MM3, so clearly it's a failure I would like to avoid in the future.
- how the config management will be organized/managed:
there's many ways to organize, to call the roles, to test the rules.
I've based my work on Misc's good work and added a few things myself.=
I've also started working on testing using Vagrant: it works but has
limitations. There's other attempts on the Internet but they also have
drawbacks, maybe others we did not find yet. So there's room for
discussion too, and integration with your CI. The current setup is in my
repo.
- how some resources (Ansible roles=E2=80=A6) are to be shared or not:
the OSAS team is very small, shares its time and energy among
several projects, you have several people with a good Puppet background
but less so on Ansible, so I would advise sharing workload. The OSAS
team can act as a neutral third party and insure all needed features are
taken into account, reviews are done in a timely manner, for example. It
was just a logical move from us to allow us spending less time on these
tasks=C2=B8 but this is open to discussion (as stated on my previous mess=
ages)
As we say here: yoroshiku onegai shimasu.
\_o<
--Bc659WIoxXX4Lhv6F7nK4c8PBqsasJf6j--
--rUake15nkmeqAJaPQq15DNkrU3qSBauM5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJXw8HRAAoJEFXp+fesHEQ/C5QP/27m98NAIpmdAi/tuJOruiOb
y96pBd8KajR2ZUDtEqumZsNZaloVNHVBTDjPC4Cz6QHdiq4ECWUoe5L67fuscVow
CNH8GNa6XwJyDnbas+57S0WSXHTkuZe3Tbib43kiYvI/VRrgJ9V9GdMe3KOwC2Pj
1LXnpCl3zSt3ktw99ErCj2c5nxzAl0AElPWzh0Ph6Mi7UfbhAAL05MpY3vK8Kwcq
I/IKDytMLSJi8aeUqGGRZ7kj0G5Kvn2pvZ3ogA8dOgPopNMW4BysEuOoYcjzQZfB
8LujlKU8pVjb87gnQpJZcDiRPXkZVOwTplTvBhgr+RIaRTZ++NbDOvrM0kDIpnjp
QEkD7x0Z8HkJ0vzX1j/sduiGPJ3xDK28mH/AtlmU4JIl2otYOgMoFPpgL+J3W+6C
REcH9AFyEg0sCdaoGfKgOCXTQAYxNOgtiNw98QROE/LiVSkNv8ZUiupr0fM0Izfw
HkCF+o5dES80Xl914gjSKXYnvv5EF1u76gMzBKvL/PcmCB4BbR6oo1ErOx1ZS3xX
/+pJDSUIWiUxW6DBKNIGGfMNvEQYL8nI5mMBjXA8W7jA/3JWe+Gwnmd6/rkGNcA6
Bfq96ECwRrEcKhksYEam+FHeaVwdD8IcEfE3NF/liYi4Y3VGDHeUHmKFCYvoGWU8
bUveh9mS1l848tksFYWu
=35u9
-----END PGP SIGNATURE-----
--rUake15nkmeqAJaPQq15DNkrU3qSBauM5--
8 years, 3 months