Rolling Restart for Server 1.30

Update 9, 2009-09-19: The rolling restart is complete.

Update 8, 2009-09-18: Due to an important security fix, the 1.30 release is being expedited. It will go out to a set of ~1800 sim hosts tonight and the remaining hosts tomorrow morning.

Update 7, 2009-09-18: Friday's pilot roll is complete.

Update 6, 2009-09-18: Friday's pilot roll is about to being.

Update 5, 2009-09-17: The pilot roll exposed an issue that caused a significant number of sims to crash. We've got a fix in place, and to ensure that the full deploys next week go smoothly, are going to do another pilot tomorrow of appx 200 sims.

Update 4, 2009-09-17: Today's work is done.

Update 3, 2009-09-17: Today's pilot roll is about to begin.

Update 2, 2009-09-16: Added link to release notes.

Update 1, 2009-09-04: During testing, some regressions were discovered that need to be fixed and re-tested. Consequently, the 1.30 deployment has been pushed back by a week. The new times are reflected below.

We will be deploying server version 1.30.0 to Second Life during the weeks of September 14th and September 21st. The rolling restart is scheduled to look like the following:

* Thurs Sept. 17th: 1.30 deploy to pilot regions
* Weds Sept. 18th: 1.30 deploy to ~1800 sim hosts (18:00 PDT - 21:00)
* Thurs Sept. 19th: 1.30 deploy to the rest of agni (05:00 PDT - 12:00)

As with all of our server deploys, each region will be restarted once during one of the rolling restart periods. Most regions should be down no more than 5-10 minutes, although some fraction of the regions will take 20-30 minutes to upgrade. If your region stays down for more than 30 minutes, please contact support. Each region will receive warnings starting 5 minutes before that region is restarted.

Full release notes are here:

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/1.30

The Beta release notes are here:

http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Beta_Server/1.30

Even partial release notes would be helpful. What's changing?

Especially since you are jumping version numbers, which implies something big is changing.

I agree, a big jump in release numbers, nothing at all in theRelease Candidate Notes does not give residents confidence. Or to put it another way.... testing, what testing?

- Clarke

/me will not complain about the lack of release notes if she gets a bear from Lil...

It would be great Customer Service to post release notes at the same time as posting the update announcement. Alas, Engineers are not Customer Service Reps.

1.30 is up on the Aditi beta grid, alas I have no idea what to test for, since we have no release notes.

Disclaimer: I have no inside knowledge.

I would guess that 1.30 includes such changes as allow wider adaptation of HTTP texture download, changes necessary to support the Plug-in API, and hopefully a buttload of bug-fixes.

I'd still give my left forearm attachment point for A)more groups, B) case/switch; C) "import" functions in scripts.

Hi all! I'm the new (read: 36 hour old) Release Manager, taking over for Dante. I do have a year & half of Ops work behind me at Linden, so hopefully I'll be up to speed sooner than later.

I can see you have a desire for release notes! We'll get those to you as soon as possible. In the future I'll try to make them available on the date of the announcement. Just because we're engineers doesn't mean we don't have hearts

I look forward to working with you!

PS. Linden bear available on request, in-world IMs work best.

Though it might seem that way, nothing big is changing. We've just changed our server versioning approach. We're using even-numbered minor release numbers for production releases and odd-numbered minor release numbers for internal, development versions.

/me waves to lil and Dante.

I finds this deep in the wiki. It at least gives us a general idea where to look for issues.

http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Beta_Server/1.30_Beta_Test

Okay, got it

ETA on release notes?

Also, is the same version numbering system going to be applied to client releases?

And... Can I have a bear?

What?? We have to train another release engineer???

edit:

If I understand correctly the jump in version numbers is because of a new numbering scheme.

We never got the last one completely trained...

Hope it fixes http://jira.secondlife.com/browse/SVC-4632

This issue has come up before, but the reason there are no release notes at this time is because the code hasn't been finalized yet. I've touched on this before here:

/348/b2/331456/2.html#post2508374

We've been testing 1.30, made an educated guess about when we think that testing will be completed, and scheduled the next release accordingly. As I said in that comment referenced above, "announcing our intended schedule is an effort to give advanced notice to residents so they can plan around our work as best as possible."

If we waited until we had code finalized before announcing our schedule, you would either not get advanced notice ("we're deploying tomorrow!", or we'd wait a week between 1) finishing testing and giving advanced notice about the deployment and 2) deploying the code, which would unnecessarily slow down the release process.

If you want to get a good idea of what will be in the final release notes for 1.30, you can follow the progress of the 1.30 beta release notes, which will continue to be updated as we deploy new code to Aditi throughout the week:

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Beta_Server/1.30

Hopefully that helps add some clarity around why we don't have finalized release notes when we announce our deploy schedule.

ETA on final, non-beta server release notes is probably around Sept 9th, as long as the deploy schedule doesn't change. As I mentioned in my last comment on this thread, you can follow along with the beta release notes to see what's new on Aditi (the beta grid).

I'm not sure if the same numbering system will be applied to the viewer. Lil or I can find out and get back to you.

I told you I was temporary! =)

/348/a9/328529/3.html#post2490302

Sooooooo.....

WELCOME to Lil and good luck in your new position!

BYE and a happy future in your new job to Dante!

Bears to be sent to Wolwaner Jervil please

"Intra-region TP was blocked by inter-region TP throttle"

can someone elaborate on this? what will the throttle be for *intra-region* TP?

Ok I am a rl fine artist and have discovered a great number of the builders and creators in SL are being ripped off by copy thieves. While LL says it is doing the legal requirements concerning copyrighted materials I do not actually see results.

My comment is if the copying third party program is requiring people to alter the SL folders game dll files why have SL programmers set into place simple security solutions such as a check file to see if the .dll is the correct size or other simple security measures deployed on the internet by other virtual environments with multiple mass users?

Before my brain injury Dec 4,1999 I was an internet security specialist by profession. While my knowledge is scrambled I still remember things at times that could be very helpful to LL. OGLE requires dll alteration it can be stopped when SL exe begins as a check file ok just my 2 cents not sure where else to put it

I was reading the IM testing procedure. What I am hoping is that the procedure on the Wiki is not the current Procedure.

[0100] Tester 2: Leave the IM session.

[0110] Verify both Tester 1 and Tester 3: see "Tester 2: has left the session" message

[0120] Tester 2: IM's group X, says hi.

[0130] Verify both Tester 1 and Tester 3 see a message announcing Tester 2 joining the session.

The user X: has left the session was a complete disaster for large groups, one message and then 200 lines of user X: has left the session. Please confirm that this misfeature has NOT been reinstated.

Oh, yes one more thing. Thank you Dante and Welcome Lil.

Thank you, Dante. I for one do appreciate the amount of work you and your team are dealing with and I also appreciate the 'unstable' nature of the information that might be included in the release notes.

However, in order to 'plan around' your work a little more information is really kind of required and here is what I mean:

If a message comes through that a sim is restarting in 5-minutes, you teleport to another region ... done. That 5-minutes is all the heads-up anyone really needs. Even if in the middle of a build, 5-minutes is considerably more than ample time to save one's work and take a ten-minute break.

However, in order to better "plan around" your work, it would be those who deal with scripts when your 'work' involves changes to the server code. The main fear obviously being when scripts break or computational results change and the unexpected occurs.

But you know that already.

So even an "anticipated" changes; bug-fix; new features; defunct features... list would be helpful. Simply place a caveat at the beginning that states "This list may and likely will change as we get closer to final code release" ... or something.

But at least then we would have a basic, albeit fuzzy idea of anything 'coming down the pike' then we really should watch for with regard to our creations.

No, I am not whining or trying to talk you into releasing such a list. But rather just trying to justify why such a list is strongly, and I mean very strongly desired.

I know I speak for many when I say I hope your work goes smoothly and the result is as planned.