Etchification Rolling Retart 2009/02/17-2009/02/20

I'm not familiar with the acronym, but I did clearly understand everything else that PatrickJ said.

Arguing semantics and ignoring direct questions appear to be the LL party line. I also understand precisely now what Prospero is saying. SecondLife is a game and not a business platform.

You might want to make sure that M, the other top guys, and the PR folks are brought up to speed. They keep making these comments on the blog and elsewhere, alluding to SL being about business and education.


Personally, this quote sums up very nicely what I have failed to convey myselff course all of SL is not unreliable, but any one particular sim *is* for those hours when the restart is scheduled.

-Atashi

Going somewhere else is easy to say, but not always easy to do when tp's fail, or worse, you pick a region that is also about to restart and end up getting kicked off the grid anyway. Not a complaint, just an observation.

I'm all for anything that makes the grid more stable.

But it's *not* "sometime during a 2-3 day period." It's "sometime between 7 and 11am Tuesday or Wednesday." A 2 day period is 48 hours long. That's very different from two four hour blocks.

That would create a host of secondary problems... on the whole, it would lead to less grid stability. As we are right now, we're very resilient if a host dies. Yes, some regions have to restart because their host died, but they can start on any other host. At the very least, if they were locked to hosts, then they would require manual intervention, and would not come up as fast.

Good luck with that I wouldn't like to be in a situation where someone goes "uh-oh, MySQL is not starting with the sim database under Etch"

... you *did* test it out on the Preview Grid first, right?

Without private grids behind corporate firewalls, or making the whole SL protocol firewall-friendly so it can be used through a reasonably secure firewall, it really doesn't matter.

The SL viewer works just fine through a hardware firewall.

Things rezzed out in regions should survive a rolling restart. That being said, rarely, yes, changes made within the last hour before a restart do get lost when the region restarts. Regions save their contents every hour, so that we have backups, and so that we don't lose more than that. They also save their contents on shutdown. However, if something goes wrong on shutdown (which, in the vast majority of cases, it does not), then we will have to revert to the previous autosave.

During a regular roll restart, you get 5min of warning before the restart hits a given region. With this etchification rolling restart, you will have 8min of warning.

You do not describe something I recognize.

A typical rolling restart has a pilot roll announced with a 2-hour window, and then a full rolling restart up to a week later with two 4-hour windows, during which each region will get restarted. Not three days; not even two days. Two 4-hour windows, one on one day, one on the next day.

I keep saying this, but people keep insisting that they want to view Second Life as being completely unreliable over the entire time from the beginning of the first window to the end of the last window. Why?

I'm Innovation Manager for a well established ITSM consulting and training organisation. We are taking the first steps to using SL as a vehicle for extending our business reach. The months that I have been in SL have shown me a textbook example of a company attempting to deliver an IT service from very low on the ITSM maturity scale.

This isn't too surprising, most IT organisations start out like that. For a while it is innovation, innovation, growth, innovation and all the while paddle like hell to try to keep it afloat. It takes time and experience for organisations to move beyond that and to realise that stability, service and delivering business value to the customer are the real game, without losing the ability to innovate. And the term "maturity model" gives us at least a hint that organisations, like people, start out with a low level of maturity. Some IT organisations (like some people) don't make it to maturity, they die first.

In any event it looks likely that it will be a while before LL gets the level of maturity necessary to see eye to eye with the likes of Atashi Toshihiko who see predictability and business value as the drivers. A hard won lesson from helping organisations improve ITSM maturity is that it is VERY HARD to make big leaps in maturity in a short time. From where LL is today (let's call it CMM level 1) to get to where Atashi is asking (CMM level 3) won't happen over night. I just hope that LL survives long enough to gain that maturity.

Lindens, feel free to give us a call, we can help!

In psychology its called the primary/recency effect: People tend to remember things that they percieve at beginning and at end of a communication better than whats in the middle.

The usual 5 minute warning (8 minutes in this case) is a usually a ton of time to teleport to another SIM and do some shopping, or pay a visit to a friend, or simply log out, wait 5 minutes (make a coffee) and log back in to previous location. We even did this at a wedding once and it was no big catastrophe - everyone rezzed in the exact same location as they were before logging out.

As I mentioned in a previous post, the countdown notification warnings are not necessary as they disrupt viewer operation. They interrupt mouse control and generate lag.

every rolling restart hurts in world business, and so the less this has to happen the better.

Heres to hopeing that Ecchi will go good!!!
o wait that would be etchi heh

I keep saying this, but people keep insisting that they want to view Second Life as being completely unreliable over the entire time from the beginning of the first window to the end of the last window. Why?

Ah, yes of course, the Primacy and Recency effect. Thanks Armin.