10:36 a.m.
The freeze doesn't technically end until tomorrow but because of the small
window between this freeze and the next I'd like to get some bits done.
1) Change the smolt api to point to its new location in
/var/www/smolt-wiki/ instead of /usr/share/mediawiki/
2) fas-server update. This is a yum update with some testing.
-Mike
10:41 a.m.
On Tue, Nov 4, 2008 at 5:36 PM, Mike McGrath <mmcgrath(a)redhat.com> wrote:
The freeze doesn't technically end until tomorrow but because of
the small
window between this freeze and the next I'd like to get some bits done.
1) Change the smolt api to point to its new location in
/var/www/smolt-wiki/ instead of /usr/share/mediawiki/
2) fas-server update. This is a yum update with some testing.
-Mike
+1
--
Xavier.t Lamien
--
10:42 a.m.
On 2008-11-04 10:36:47 AM, Mike McGrath wrote:
1) Change the smolt api to point to its new location in
/var/www/smolt-wiki/ instead of /usr/share/mediawiki/
+1
2) fas-server update. This is a yum update with some testing.
+1 (test in staging first, as you mentioned on IRC)
Thanks,
Ricky
10:48 a.m.
On Tuesday 04 November 2008 10:36:47 am Mike McGrath wrote:
The freeze doesn't technically end until tomorrow but because of
the small
window between this freeze and the next I'd like to get some bits done.
1) Change the smolt api to point to its new location in
/var/www/smolt-wiki/ instead of /usr/share/mediawiki/
2) fas-server update. This is a yum update with some testing.
-Mike
Id like to get started on load balancing koji. First step will be a soc
request to have koji's IP put on the load balancer. and pointed at koji1 and
koji2
second step will be to rebuild koji1 as a 32 bit guest. this should be
transparent to users since the existing koji2 will be up and serving
builders/users.
Dennis
12:41 p.m.
Dennis Gilmore wrote:
Id like to get started on load balancing koji. First step will be a
soc
request to have koji's IP put on the load balancer. and pointed at koji1 and
koji2
How will this affect people doing last minute rebuilds (I'm guessing it
should be transparent if koji2 works fine)? Is it easy to revert/work
around if something goes wrong?
Since koji won't affect the distribution of the pre-release, I'm
inclined to say the sooner we do this the less disruptive it will be.
second step will be to rebuild koji1 as a 32 bit guest. this should
be
transparent to users since the existing koji2 will be up and serving
builders/users.
If we do the first part, this part gets my +1
-Toshio
12:52 p.m.
On Tue, 2008-11-04 at 10:41 -0800, Toshio Kuratomi wrote:
Dennis Gilmore wrote:
> Id like to get started on load balancing koji. First step will be a soc
> request to have koji's IP put on the load balancer. and pointed at koji1 and
> koji2
>
How will this affect people doing last minute rebuilds (I'm guessing it
should be transparent if koji2 works fine)? Is it easy to revert/work
around if something goes wrong?
Since koji won't affect the distribution of the pre-release, I'm
inclined to say the sooner we do this the less disruptive it will be.
Timing-wise, maybe it makes sense to do this when CVS is down for mass
branching?
Jeremy
12:57 p.m.
On Tue, 4 Nov 2008, Jeremy Katz wrote:
On Tue, 2008-11-04 at 10:41 -0800, Toshio Kuratomi wrote:
> Dennis Gilmore wrote:
> > Id like to get started on load balancing koji. First step will be a soc
> > request to have koji's IP put on the load balancer. and pointed at koji1
and
> > koji2
> >
> How will this affect people doing last minute rebuilds (I'm guessing it
> should be transparent if koji2 works fine)? Is it easy to revert/work
> around if something goes wrong?
>
> Since koji won't affect the distribution of the pre-release, I'm
> inclined to say the sooner we do this the less disruptive it will be.
Timing-wise, maybe it makes sense to do this when CVS is down for mass
branching?
In theory the koji switch might not involve any downtime at all. if it
does we can time it. The mass branch is currently scheduled for Thursday.
-Mike
12:54 p.m.
On Tue, 4 Nov 2008, Toshio Kuratomi wrote:
Dennis Gilmore wrote:
> Id like to get started on load balancing koji. First step will be a soc
> request to have koji's IP put on the load balancer. and pointed at koji1 and
> koji2
>
How will this affect people doing last minute rebuilds (I'm guessing it
should be transparent if koji2 works fine)? Is it easy to revert/work
around if something goes wrong?
Since koji won't affect the distribution of the pre-release, I'm
inclined to say the sooner we do this the less disruptive it will be.
I think thats what dennis had in mind, get it in before the next change
freeze starts. I've submitted a ticket to get the network portion of this
ready. It gets a +1 from me.
The only thing to note is we won't be able to point the builders at the
load balanced IP until we get the builders / build system on its own
network. The route back through the same interface as source issue in our
balancer.
-Mike
1:11 p.m.
On Tuesday 04 November 2008 12:41:44 pm Toshio Kuratomi wrote:
Dennis Gilmore wrote:
> Id like to get started on load balancing koji. First step will be a soc
> request to have koji's IP put on the load balancer. and pointed at koji1
> and koji2
How will this affect people doing last minute rebuilds (I'm guessing it
should be transparent if koji2 works fine)? Is it easy to revert/work
around if something goes wrong?
ill shut down koji1 and make sure things work off
of koji2, if koji2 doesnt
work right ill bring back koji1 and shut down koji2
Since koji won't affect the distribution of the pre-release,
I'm
inclined to say the sooner we do this the less disruptive it will be.
> second step will be to rebuild koji1 as a 32 bit guest. this should be
> transparent to users since the existing koji2 will be up and serving
> builders/users.
If we do the first part, this part gets my +1
We wont rebuild koji1 until we are sure koji2 is working correctly.
Dennis
1:14 p.m.
Dennis Gilmore wrote:
On Tuesday 04 November 2008 12:41:44 pm Toshio Kuratomi wrote:
> Dennis Gilmore wrote:
>> Id like to get started on load balancing koji. First step will be a soc
>> request to have koji's IP put on the load balancer. and pointed at koji1
>> and koji2
> How will this affect people doing last minute rebuilds (I'm guessing it
> should be transparent if koji2 works fine)? Is it easy to revert/work
> around if something goes wrong?
ill shut down koji1 and make sure things work off of koji2, if koji2 doesnt
work right ill bring back koji1 and shut down koji2
Sounds good.
+1
-Toshio
2:26 p.m.
On 2008-11-04 10:48:11 AM, Dennis Gilmore wrote:
Id like to get started on load balancing koji. First step will be a
soc
request to have koji's IP put on the load balancer. and pointed at koji1 and
koji2
second step will be to rebuild koji1 as a 32 bit guest. this should be
transparent to users since the existing koji2 will be up and serving
builders/users.
+1
Thanks,
Ricky
10:48 a.m.
On Tuesday 04 November 2008 10:36:47 am Mike McGrath wrote:
The freeze doesn't technically end until tomorrow but because of
the small
window between this freeze and the next I'd like to get some bits done.
1) Change the smolt api to point to its new location in
/var/www/smolt-wiki/ instead of /usr/share/mediawiki/
2) fas-server update. This is a yum update with some testing.
-Mike
oh and +1
Dennis
12:37 p.m.
Mike McGrath wrote:
The freeze doesn't technically end until tomorrow but because of
the small
window between this freeze and the next I'd like to get some bits done.
1) Change the smolt api to point to its new location in
/var/www/smolt-wiki/ instead of /usr/share/mediawiki/
+1
2) fas-server update. This is a yum update with some testing.
+1
-Toshio
5645
days inactive
5645
days old
infrastructure@lists.fedoraproject.org
12 comments
6 participants
participants (6)
-
Dennis Gilmore -
Jeremy Katz -
Mike McGrath -
Ricky Zhou -
Toshio Kuratomi -
Xavier Lamien