656715 - Upgrade Khan to latest PHP

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Brandon Savage [:brandon]]

Our version of PHP is 5.2.9; the latest PHP version is 5.3.6. However, the latest in the 5.2.x line should be fine, if there are objections to moving onto PHP 5.3.

Comment 1

[James Socol [:jsocol, :james]]

A lot of people use khan--well, maybe not so many anymore--as a development environment. Having 5.3 on the dev environment but 5.2 on prod is not helpful. I admit that I don't use it for much of anything, though.

Comment 2

[Justin Dow [:jabba]]

The reason I had brandon file this bug and cc everyone, is that rhel5 ships with 5.1.x and starting with rhel5.6 optionally 5.3.x, but never 5.2.x, so 5.2.x was a homebuilt RPM. It'd be easier for us to just bump to 5.3.x and upgrade to rhel5.6, but I'm not sure what or whose projects that will break ( I don't even know what y'all use khan for ), so didn't want to go upgrading stuff without givine everyone a chance to veto.

Comment 3

[Laura Thomson :laura]

I vote latest 5.2.x for now.  We'll need 5.3 at some point in Q3 though (for Socorro anyway).

Comment 4

[Jake Maul [:jakem]]

Justin, could we replace our home-grown php-5.2 RPMs with a 3rd party repo? I've had lots of good experience with the atomic repo (http://www.atomicorp.com/channels/). They currently have php-5.2.17 and php-5.3.6 in there... just need to exclude the 5.3 ones for now.

Comment 5

[James Socol [:jsocol, :james]]

(In reply to comment #2)
> It'd be easier for us to just bump to 5.3.x and
> upgrade to rhel5.6, but I'm not sure what or whose projects that will break
> ( I don't even know what y'all use khan for ), so didn't want to go
> upgrading stuff without givine everyone a chance to veto.

I think khan should match what we most frequently use in production--or what the people who use it for development use in production.

Comment 6

[Laura Thomson :laura]

(In reply to comment #5)
> (In reply to comment #2)
> > It'd be easier for us to just bump to 5.3.x and
> > upgrade to rhel5.6, but I'm not sure what or whose projects that will break
> > ( I don't even know what y'all use khan for ), so didn't want to go
> > upgrading stuff without givine everyone a chance to veto.
> 
> I think khan should match what we most frequently use in production--or what
> the people who use it for development use in production.

We want to upgrade so we can work to upgrade Socorro prod, basically.  The team largely uses khan for dev rather than local (because it's the only way to get access to an hbase with real data in it).

Comment 7

[Ryan Snyder [:ryansnyder] [:rsnyder] [:rysny]]

Socorro should not be a blocker for Khan.  It has already been updated to work with PHP 5.3.x per bug 618004.

Comment 8

[Wil Clouser [:clouserw]]

no objections for AMO or getpersonas

Comment 9

[Justin Dow [:jabba]]

Yeah, it is hard to make everyone happy. Socorro prod/stage/dev is on rhel6 and therefore 5.3. afaik sumo doesn't use php anymore, Amo and getpersonas are likely moving to rhel6 soon, so same applies. I don't think input uses php.

I'm inclined to upgrade to 5.3 in order to match what will "soon" be prod for "most" projects, but it's not my call, since I'm likely not aware of all the various webdev projects that might be floating around and depend on php 5.2.x...

(In reply to comment #4)
> Justin, could we replace our home-grown php-5.2 RPMs with a 3rd party repo?
> I've had lots of good experience with the atomic repo
> (http://www.atomicorp.com/channels/). They currently have php-5.2.17 and
> php-5.3.6 in there... just need to exclude the 5.3 ones for now.

I'm fine with upgrading it that way too, or cherrypick the RPMs and drop them into our repo, but we need to assess what other servers might be affected by something like that.

So far it sounds like there isn't anybody that still needs 5.2.x, but I could be missing something. CC'ing oremj, who likely has the best overview of what is using what where.

Comment 10

[Laura Thomson :laura]

(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #2)
> > > It'd be easier for us to just bump to 5.3.x and
> > > upgrade to rhel5.6, but I'm not sure what or whose projects that will break
> > > ( I don't even know what y'all use khan for ), so didn't want to go
> > > upgrading stuff without givine everyone a chance to veto.
> > 
> > I think khan should match what we most frequently use in production--or what
> > the people who use it for development use in production.
> 
> We want to upgrade so we can work to upgrade Socorro prod, basically.  The
> team largely uses khan for dev rather than local (because it's the only way
> to get access to an hbase with real data in it).

(In reply to comment #7)
> Socorro should not be a blocker for Khan.  It has already been updated to
> work with PHP 5.3.x per bug 618004.

It's not a blocker; we specifically *want* to upgrade.

Comment 11

[Justin Dow [:jabba]]

Also, Corey brought up a good point to me.. The "generic" cluster, where all the current production PHP apps are running is about to get moved to rhel6 in its entirety, making 5.3 a requirement, in which case I'm of the opinion that khan should definitely be on 5.3.

Comment 12

[Shyam Mani [:fox2mike]]

Should just upgrade khan to RHEL 6 :)

Comment 13

[Jeremy Orem [:oremj]]

Short term can we just upgrade it to 5.6 and install the rhel 5.3 rpms?

Comment 14

[Justin Dow [:jabba]]

Alright. sounds like no objections. I'd like to schedule a brief downtime for this, as upgrading to 5.6 will pull in a new kernel and it'd be best to reboot the box to pick up that change. Can I do that sometime tonight or this weekend?

Comment 15

[Wil Clouser [:clouserw]]

knock yourself out, just keep us updated

Comment 16

[Justin Dow [:jabba]]

Upgraded to rhel5.6 and php5.3.