11:39 a.m.
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig266FD55343739ABC574C0324
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Minutes:
http://ovirt.org/meetings/ovirt/2012/ovirt.2012-10-15-15.01.html
Minutes (text):
http://ovirt.org/meetings/ovirt/2012/ovirt.2012-10-15-15.01.txt
Log:
http://ovirt.org/meetings/ovirt/2012/ovirt.2012-10-15-15.01.log.h=
tml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
#ovirt Meeting
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Meeting started by quaid at 15:01:05 UTC. The full logs are available at
http://ovirt.org/meetings/ovirt/2012/ovirt.2012-10-15-15.01.log.html .
Meeting summary
---------------
* rollcall & agenda check (quaid, 15:01:36)
* LINK:
http://wiki.ovirt.org/wiki/Infrastructure_team_meetings#2012-10-15
(mburns, 15:03:22)
* LINK:
http://wiki.ovirt.org/wiki/Infrastructure_team_meetings#2012-10-15
(quaid, 15:06:28)
* MediaWiki & www (quaid, 15:07:17)
* MW *still* not upgraded; quaid has failed to find the right window &
stick to it (quaid, 15:07:50)
* wiki may be offline for a few hours during Tel Aviv workday due to
challenge of finding compatible time (quaid, 15:09:10)
* ACTION: quaid to announce a new downtime window with as much lead
time as he can get (quaid, 15:09:25)
* quaid has control of *-ovirt.rhcloud.com namespace with extra enough
slots to put our services, once the upgrade is done the mirror with
new theme can be created at wiki-ovirt.rhcloud.com (quaid,
15:12:38)
* ACTION: quaid to do upgrade on Friday after Wed feature
meeting-topic (so wiki is available for making feature pages)
(quaid, 15:16:14)
* ACTION: quaid to test upgrade process with snapshot & new mirror
test on OpenShift (quaid, 15:16:33)
* Hosting (quaid, 15:18:01)
* quaid is still working with RHT IT on additional hosting
requirements (quaid, 15:18:24)
* quaid & itamar discussed risk of moving Gerrit & downtime potentials
(before, during, after); both are recommending that we stagger the
move of Gerrit until after Infra has stabilized its relationship and
proceeses with hosting sponsor Alter Way (quaid, 15:20:07)
* AGREED: Infra team agrees on holding on Gerrit move unitl after
Jenkins is stable, etc. (quaid, 15:22:23)
* Trac ticket review (quaid, 15:23:17)
* LINK: https://fedorahosted.org/ovirt/report/1 (quaid, 15:23:53)
* LINK: https://fedorahosted.org/ovirt/ticket/3 is in progress and
reported on - MediaWiki upgrade (quaid, 15:24:26)
* LINK: https://fedorahosted.org/ovirt/ticket/4 is dependent on #3
(quaid, 15:24:38)
* LINK: https://fedorahosted.org/ovirt/ticket/5 is currently unowned
(quaid, 15:25:50)
* ACTION: ewoud taking over #5 to give it a first draft (quaid,
15:30:15)
* Hosting take deux (quaid, 15:32:58)
* Board has approced Alter Way hosting (quaid, 15:33:10)
* dneary interviewed Alter Way Dir of R&D about their oVirt plans at
OWF (quaid, 15:33:42)
* Hosting details need to be defined (quaid, 15:33:59)
* IDEA: do Gerrit moving in two stages (quaid, 15:34:13)
* s/approced/approved/g (quaid, 15:36:32)
* IDEA: look in to Gerrit replication services - is there any concept
of a cluster or mirror? (quaid, 15:37:26)
* IDEA: Step 1 for gerrit migration. Clone git repos (if we need to),
set up new gerrit instance, clone data from live Gerrit (dneary,
15:37:27)
* IDEA: Step 2: Set "old" gerrit read-only, sync any comments/changes
that need it, set "new" gerrit live (dneary, 15:38:10)
* IDEA: mirror git repos to github (ewoud, 15:39:45)
* IDEA: script github push to happen as a daily cronjob on
git.ovirt.org (quaid, 15:42:09)
* Puppet & Foreman (quaid, 15:47:12)
* LINK: https://fedorahosted.org/ovirt/ticket/6 (quaid, 15:47:58)
* LINK: https://github.com/rtyler/puppet-jenkins could be the basis
for that (ewoud, 15:50:29)
* AGREED: Use Puppet for deploying all new services on Alter Way
(quaid, 15:51:22)
* IDEA: we can manage Jenkins from Puppet (quaid, 15:52:03)
* IDEA: manage our own IP and DNS from foreman (ewoud, 15:55:51)
* IDEA: puppet can manage versions, slaves, etc. (quaid, 15:56:04)
* next step is to build a jenkins server (quaid, 15:56:23)
* how to manage the git flow? (quaid, 15:56:38)
* IDEA: build the basis without gerrit and then import the git repo in
gerrit once it's running (quaid, 15:57:26)
* if we manage our own dhcp/dns, Foreman can manage them and and
create VMs automatically (quaid, 15:57:46)
* IDEA: it would be good to ahve our own VLAN and IP space at Alter
Way (quaid, 15:58:03)
* Jenkins (quaid, 16:01:16)
* IDEA: invite AlterWays for an infra meeting (ewoud, 16:06:45)
* Gerrit (quaid, 16:07:30)
* LINK:
http://gerrit-documentation.googlecode.com/svn/ReleaseNotes/ReleaseNotes-=
2.3.html#_drafts
(eedri, 16:08:57)
* A few developers haved asked for permission to few drafts in gerrit
(quaid, 16:09:02)
* ACTION: Gerrit admins need to enable viewing of drafts (quaid,
16:14:34)
* ACTION: eedri to follow up with itamar about enabling this option on
gerrit (mburns, 16:23:32)
* Infra presentation at Workshop in Barcelona (mburns, 16:24:01)
* ACTION: mburns to come up with a draft presentation for review by
next week's meeting (mburns, 16:26:47)
* no other comments on the presentation (mburns, 16:27:29)
* LINK:
https://www.google.com/calendar/ical/tj13m8saobjame27tiphp47vf8%40group.c=
alendar.google.com/public/basic.ics
(dneary, 16:27:32)
* other topics (mburns, 16:27:36)
* dneary created a google calendar with ovirt meetings (mburns,
16:27:49)
* LINK:
https://www.google.com/calendar/ical/tj13m8saobjame27tiphp47vf8%40group.c=
alendar.google.com/public/basic.ics
(mburns, 16:27:54)
Meeting ended at 16:29:42 UTC.
Action Items
------------
* quaid to announce a new downtime window with as much lead time as he
can get
* quaid to do upgrade on Friday after Wed feature meeting-topic (so wiki
is available for making feature pages)
* quaid to test upgrade process with snapshot & new mirror test on
OpenShift
* ewoud taking over #5 to give it a first draft
* Gerrit admins need to enable viewing of drafts
* eedri to follow up with itamar about enabling this option on gerrit
* mburns to come up with a draft presentation for review by next week's
meeting
Action Items, by person
-----------------------
* eedri
* eedri to follow up with itamar about enabling this option on gerrit
* ewoud
* ewoud taking over #5 to give it a first draft
* mburns
* mburns to come up with a draft presentation for review by next
week's meeting
* quaid
* quaid to announce a new downtime window with as much lead time as he
can get
* quaid to do upgrade on Friday after Wed feature meeting-topic (so
wiki is available for making feature pages)
* quaid to test upgrade process with snapshot & new mirror test on
OpenShift
* **UNASSIGNED**
* Gerrit admins need to enable viewing of drafts
People Present (lines said)
---------------------------
* quaid (139)
* mburns (74)
* ewoud (55)
* eedri (36)
* dneary (27)
* ovirtbot (15)
* SirDerigo (5)
* RobertM (2)
Generated by `MeetBot`_ 0.1.4
=2E. _`MeetBot`: http://wiki.debian.org/MeetBot
--=20
Karsten 'quaid' Wade, Sr. Analyst - Community Growth
http://TheOpenSourceWay.org .^\ http://community.redhat.com
@quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
--------------enig266FD55343739ABC574C0324
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iD8DBQFQfDxN2ZIOBq0ODEERAkjOAKCygXZG0+5zq1VUNbpxTNTI3epgAgCeKZZX
oXTDSbqRa/WOYRRvUW14xog=
=7meO
-----END PGP SIGNATURE-----
--------------enig266FD55343739ABC574C0324--
11:45 a.m.
On 10/15/2012 06:39 PM, Karsten 'quaid' Wade wrote:
* IDEA: do Gerrit moving in two stages (quaid, 15:34:13)
* s/approced/approved/g (quaid, 15:36:32)
* IDEA: look in to Gerrit replication services - is there any concept
of a cluster or mirror? (quaid, 15:37:26)
* IDEA: Step 1 for gerrit migration. Clone git repos (if we need to),
set up new gerrit instance, clone data from live Gerrit (dneary,
15:37:27)
* IDEA: Step 2: Set "old" gerrit read-only, sync any comments/changes
that need it, set "new" gerrit live (dneary, 15:38:10)
* IDEA: mirror git repos to github (ewoud, 15:39:45)
* IDEA: script github push to happen as a daily cronjob on
git.ovirt.org (quaid, 15:42:09)
we already use gerrit to git mirror on commit. only setup for
ovirt-engine due to lack of interested at the time it was setup from
other projects (I remember emailing about this and asking, but no takers)
https://github.com/gerrit-ovirt-org/ovirt-engine
(btw, this builtin feature of gerrit for git mirroring has been
modularized in gerrit 2.5 to an optional plugin, which we'll require
manual upgrade steps)
11:53 a.m.
On Mon, Oct 15, 2012 at 06:45:15PM +0200, Itamar Heim wrote:
On 10/15/2012 06:39 PM, Karsten 'quaid' Wade wrote:
> * IDEA: do Gerrit moving in two stages (quaid, 15:34:13)
> * s/approced/approved/g (quaid, 15:36:32)
> * IDEA: look in to Gerrit replication services - is there any concept
> of a cluster or mirror? (quaid, 15:37:26)
> * IDEA: Step 1 for gerrit migration. Clone git repos (if we need to),
> set up new gerrit instance, clone data from live Gerrit (dneary,
> 15:37:27)
> * IDEA: Step 2: Set "old" gerrit read-only, sync any comments/changes
> that need it, set "new" gerrit live (dneary, 15:38:10)
> * IDEA: mirror git repos to github (ewoud, 15:39:45)
> * IDEA: script github push to happen as a daily cronjob on
> git.ovirt.org (quaid, 15:42:09)
we already use gerrit to git mirror on commit. only setup for
ovirt-engine due to lack of interested at the time it was setup from
other projects (I remember emailing about this and asking, but no
takers)
https://github.com/gerrit-ovirt-org/ovirt-engine
Ah, so it's official. I was wondering whose it was (as you can see in
the minutes). Maybe move this to the ovirt account mburns syncs
manually?
11:59 a.m.
On 10/15/2012 06:39 PM, Karsten 'quaid' Wade wrote:
* Gerrit admins need to enable viewing of drafts
* eedri to follow up with itamar about enabling this option on gerrit
anyone knows this is possible?
the definition of the drafts features is:
"Drafts
A change can be submitted as a draft if, for example, it's not ready for
merging, or even general code review, but you would like to share it
selectively to get early comments. If you upload a change as a draft, by
default, no one else can see it. You must explicitly add each person you
would like to share it with as a reviewer. Reviewers you add can leave
comments, but cannot vote at this stage. You can continue to upload new
patchsets to the change as it evolves, and once it is ready for general
review, you can click the "Publish" button. It will then become a normal
change in Gerrit that everyone can see, including the earlier reviews
from the draft stage. This is a one way transition; once a draft is
published, it can't be made a draft again.
A draft change is uploaded by adding the "-D" option. Simply make
changes, commit them, and submit them as a draft:
git commit -a
git review -D"
noon
On 10/15/2012 06:53 PM, Ewoud Kohl van Wijngaarden wrote:
On Mon, Oct 15, 2012 at 06:45:15PM +0200, Itamar Heim wrote:
> On 10/15/2012 06:39 PM, Karsten 'quaid' Wade wrote:
>> * IDEA: do Gerrit moving in two stages (quaid, 15:34:13)
>> * s/approced/approved/g (quaid, 15:36:32)
>> * IDEA: look in to Gerrit replication services - is there any concept
>> of a cluster or mirror? (quaid, 15:37:26)
>> * IDEA: Step 1 for gerrit migration. Clone git repos (if we need to),
>> set up new gerrit instance, clone data from live Gerrit (dneary,
>> 15:37:27)
>> * IDEA: Step 2: Set "old" gerrit read-only, sync any
comments/changes
>> that need it, set "new" gerrit live (dneary, 15:38:10)
>> * IDEA: mirror git repos to github (ewoud, 15:39:45)
>> * IDEA: script github push to happen as a daily cronjob on
>> git.ovirt.org (quaid, 15:42:09)
>
> we already use gerrit to git mirror on commit. only setup for
> ovirt-engine due to lack of interested at the time it was setup from
> other projects (I remember emailing about this and asking, but no
> takers)
>
> https://github.com/gerrit-ovirt-org/ovirt-engine
Ah, so it's official. I was wondering whose it was (as you can see in
the minutes). Maybe move this to the ovirt account mburns syncs
manually?
I'll sync with mike to check.
3:08 p.m.
On Mon, Oct 15, 2012 at 06:59:25PM +0200, Itamar Heim wrote:
On 10/15/2012 06:39 PM, Karsten 'quaid' Wade wrote:
>* Gerrit admins need to enable viewing of drafts
>* eedri to follow up with itamar about enabling this option on gerrit
anyone knows this is possible?
the definition of the drafts features is:
"Drafts
A change can be submitted as a draft if, for example, it's not ready
for merging, or even general code review, but you would like to
share it selectively to get early comments. If you upload a change
as a draft, by default, no one else can see it. You must explicitly
add each person you would like to share it with as a reviewer.
Reviewers you add can leave comments, but cannot vote at this stage.
You can continue to upload new patchsets to the change as it
evolves, and once it is ready for general review, you can click the
"Publish" button. It will then become a normal change in Gerrit that
everyone can see, including the earlier reviews from the draft
stage. This is a one way transition; once a draft is published, it
can't be made a draft again.
A draft change is uploaded by adding the "-D" option. Simply make
changes, commit them, and submit them as a draft:
git commit -a
git review -D"
Personally I'm fine with this solution as long it's communicated
clearly. I suppose it would be nice to mark your draft as public for
proof-of-concept patches, but the main objective is then to not merge
them until they are ready. Since I think that's covered by our
maintainers it's an invoncenience and ugly, but unlikely to degrade the
general code quality.
4219
days inactive
4219
days old
5 comments
3 participants
participants (3)
-
Ewoud Kohl van Wijngaarden -
Itamar Heim -
Karsten 'quaid' Wade