2020 Simulator User Group week #31 summary & the Blake Sea Cloud challenge

Auld Lang Syne, June 2020 – blog post

The following notes were taken during the Simulator User Group meeting of Tuesday, July 28th, 2020.

Simulator Deployments

Please refer to the server deployment thread for news and updates:

  • There was no deployment to the core SLS channel regions on Tuesday, July 28th, leaving the majority of the grid running on server maintenance update 544832, designed to resolve issues with some internal service updates, chat range improvements and capability improvements.
  • On Wednesday, July 29th, there should be a deployment to two of the RC channels (LeTigre and BlueSteel), primarily related to internal changes related to the cloud uplift.

SL Viewer

  • After being rolled back to RC status, the Tools Update viewer version 6.4.5.544639 was removed from the available viewer list on Monday, July 27th.
  • The Mesh uploader was promoted to RC status with the release of version 6.4.5.544027 on Monday, July 27th.

The remaining official viewer pipelines remain as follows:

  • Current release viewer version 6.4.4.543157, dated June 11th, promoted June 23rd, formerly the CEF RC viewer – ROLL BACK.
  • Release channel cohorts:
    • Arrack Maintenance RC viewer, version 6.4.5.544465, July 6th.
    • Love Me Render RC viewer, version 6.4.5.544028, June 30th.
  • Project viewers:
    • Custom Key Mappings project viewer, version 6.4.5.544079, June 30th.
    • Copy / Paste viewer, version 6.3.5.533365, December 9th, 2019.
    • Project Muscadine (Animesh follow-on) project viewer, version 6.4.0.532999, November 22nd, 2019.
    • Legacy Profiles viewer, version 6.3.2.530836, September 17th, 2019. Covers the re-integration of Viewer Profiles.
    • 360 Snapshot project viewer, version 6.2.4.529111, July 16th, 2019.

Blake Sea Cloud Challenge (Aditi)

As I was the first to report on July 21st, the Blake Sea regions have been cloned to the Aditi, the beta grid, and are running on AWS servers in the cloud (see: Blake Sea in the cloud on ADITI). At that time, region crossings for the regions were  – to say the least – unstable.

Since then, those regions (some 46 in total) have been further updated (Monday, July 27th), and to help with gathering data on cloud-based region crossings, Simon Linden has defined the Blake Sea Challenge:

We just did some updates this morning (Monday July 27th) that fixes a bunch of the region connectivity issues.    I just did a tour and didn’t hit any invisible walls.
Along those lines, I made a quick “Blake Sea Challenge”   Go to secondlife://Aditi/secondlife/Morris/200/207/34  on the BETA aditi grid, and click on the red egg-shaped thing to try it out.   It will give you the “Blake Sea Challenge”  … wear it and touch, and it’ll get you going.   Follow the instructions to sail / fly / motor around 46 regions without doubling back and see if you make it.   Have fun and keep letting us know how it goes!

– Simon Linden, Simulator User Group

Blake Sea is now on Aditi and running in the cloud for those wishing to test vehicle region crossings. If interested, try taking Simon’s challenge (above)

In Brief

  • There are renewed reports of delays to scripted object rezzing across many regions. see: BUG-228939 “on_rez action delayed for 2 to 3 seconds in many regions”.

2020 Simulator User Group week #30 summary

Frogmore, June 2020 – blog post

The following notes were taken during the Simulator User Group meeting of Tuesday, July 14th, 2020.

Simulator Deployments

Please refer to the server deployment thread for news and updates:

  • On Tuesday, July 21st, the majority of the grid was updated with server maintenance update 544832, designed to resolve issues with some internal service updates, chat range improvements and capability improvements.
  • On Wednesday, July 22nd, the should be a single RC deployment comprising “a few internal changes (mostly logging)”. At the time of writing, the server deployment thread had yet to be updated with the release notes reference.

SL Viewer

The Tools Update viewer, version 6.4.5.544639, was promoted to de facto release status, Friday, July 17th. This viewer uses the new viewer build tool chain, but does not include any user-facing updates outside of bug fixes.

The remaining official viewer pipelines remain as follows:

  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
    • Arrack Maintenance RC viewer, version 6.4.5.544465, July 6th.
    • Love Me Render RC viewer, version 6.4.5.544028, June 30th.
  • Project viewers:
    • Custom Key Mappings project viewer, version 6.4.5.544079, June 30th.
    • Mesh uploader project viewer, version 6.4.4.543141, June 11th.
    • Copy / Paste viewer, version 6.3.5.533365, December 9th, 2019.
    • Project Muscadine (Animesh follow-on) project viewer, version 6.4.0.532999, November 22nd, 2019.
    • Legacy Profiles viewer, version 6.3.2.530836, September 17th, 2019. Covers the re-integration of Viewer Profiles.
    • 360 Snapshot project viewer, version 6.2.4.529111, July 16th, 2019.

Further Regions in the Cloud

Following from the announcement concerning Ahern and Morris on Aditi, the beta grid, being in the cloud (see my previous Simulator User Group update),  most / all of Blake Sea has been cloned to Aditi and is now running in the cloud, specifically for the purposes of  region crossing tests with vehicles.

Again, just to emphasise, this is Aditi, the beta grid, only (at least one person has reported on region crossings on Agni (the main grid) in relation to this announcement). For more information, refer to my blog post Blake Sea in the cloud on ADITI.

Blake Sea is now on Aditi and running in the cloud for those wishing to test vehicle region crossings

What is Simulator “Sleep Time” and how are Scripts Processed?

The viewer provides a set of stats related to both itself and the simulator your user is on (CTRL-SHIFT-1). Most of the stats proved in this window are relatively self-explanatory, although some can cause confusion or can be misrepresented. One area of confusion  – what is simulator “sleep time”  – was raised in the forums recently, and Rider Linden took the time to explain it and a couple of other things in the stats panel. As his reply may help others, I’m including it in full here:

The short answer is that sleep time is the mean amount of time in ms per simulator frame that the simulator has spent idling over the last minute.
The long answer is that the simulators attempt to keep a constant number of processing frames (one cycle through the main loop) per second. This number is displayed in the statistics window as Sim FPS. This value is not the same as the Viewer’s FPS. When the Sim FPS starts to fall below 45 you will begin to see lag events like delayed movement and rubber banding, among other symptoms.
A single frame should take about 21ms. (21ms * 45) = ~1 second (less about 50ms overhead). If a single simulator frame takes less than that 21ms we need to add a few extra ms in order to maintain the constant rate. This extra time is reported as “Sleep Time” and tracks closely to “Spare Time”.
Every frame on the simulator is divided into a number of phases. The big ones are network message processing, advancing the state of the physics simulation, processing agents in the region and updating their interest lists, and executing scripts.
The amount of time allowed per frame to execute scripts is capped. The simulator will attempt to execute all the scripts in the region in that allotted time slice, if it can not make it all the way through the list it will stop and pick up where it left off on the next frame (this gives you the “Scripts Run %” statistic.) Since the time for script execution is capped you can see situations where the % of scripts executed per frame begins to fall even though there is idle time reported on the simulator.

Rider Linden, July 23rd, 2020

Blake Sea in the cloud on ADITI

Blake Sea is now on Aditi and running in the cloud for those wishing to test vehicle region crossings

Following from the announcement concerning Ahern and Morris on Aditi (the beta grid), being in the cloud – see my Simulator User Group update of July 14th, 2020 – it has been announced that most / all of Blake Sea has also now been cloned to Aditi, and is also running on AWS cloud servers.

The came via a forum post by Mazidox Linden on Monday, July 21st, and the move has been made so that those who use boats and aircraft can carry out region crossing tests.

We’ve now expanded the number of regions we’re running in the cloud on Aditi to include the entirety of the Blake Sea mainland regions. For those of you who aren’t familiar with Blake Sea, you can use the following entry points to log in on Aditi and rez a vehicle to start exploring:
Blake Sea – Japan (secondlife://Aditi/secondlife/Blake%20Sea%20-%20Japan/207/248/22)
Blake Sea – Beagle (secondlife://Aditi/secondlife/Blake%20Sea%20-%20Beagle/207/208/13)
Blake Sea – Mainbrace (secondlife://Aditi/secondlife/Blake%20Sea%20-%20Mainbrace/211/241/16)
Blake Sea – Atlantic (secondlife://Aditi/secondlife/Blake%20Sea%20-%20Atlantic/245/219/16)
Objectives:
Test region crossing code (particularly using vehicles) between cloud simulators on the same host, and cloud simulators on different hosts.

– Mazidox Linden, July 21st

Again, just to emphasise, this is Aditi, the beta grid, only (at least one person has responded to the thread referencing Blake Sea region crossings on Agni, the main grid).

Those wishing to try boat / aircraft region crossings can do so by logging-in to Aditi and teleporting to the locations given above. you can also use Blake Sea – Half Hitch on Aditi for rezzing boats and seaplanes can be rezzed.

When testing, be aware that crossings between these regions can be unpredictable – so please do report your experiences via the forum thread, and with the following points in mind, as also indicated by Mazidox:

  • Some regions can cause you to “bounce off an invisible wall” at the region border, even though you are able to see into them.
    • Please report instances of this occurring in the forum thread, including the name of the region you were in, the region you were trying to enter, the date, and the time.
  • Some regions will not show up at the edge of your current region, even though they are adjacent.
    • Again, please report instances of this occurring in the forum thread, including the name of the region you were in, the region that failed to appear, the date, and the time.
  • HTTP-out for LSL scripts is disabled on cloud-based regions, as is sending e-mails via LSL scripts. Please do not report either, as both are currently working as intended.

to Access Aditi

If you have not logged-into Aditi before, you should file a support ticket requesting access.

Once your ticket has been responded to, you can log-in to Aditi via any Second Life viewer using to SL account name and password:

  • Launch the viewer.
  • If the grid selection option is not displayed, press CTRL-SHIFT-G.
  • Select Beta Test Grid (Aditi) from the drop-down (see below).
  • Enter you log-in credentials.
Use the Grid selection option in any viewer to access the beta grid
  • To return to the Main Grid select Second Life Main Grid (Agni) at your next login

Note: when you log-in, your inventory may not reflect your inventory on the main grid (so you may not have your desired vehicle available, for example), and you’re need to wait for your inventory to be duplicated from Agni (the main grid).

The inventory copying process is automatic, and occurs at approximately 06:00 SLT daily. Simply by logging-in to Aditi you will have flagged your inventory to be updated the next time the copy process is run, so you should not need to wait more than 24-hours for your Aditi inventory to properly reflect your Agni inventory.

Further information on Aditi can be found on the Preview Grid page of the SL wiki.

2020 Simulator User Group week #29 summary

The Empire of Dreaming Books, May 2020 – blog post

The following notes were taken during the Simulator User Group meeting of Tuesday, July 14th, 2020.

Simulator Deployments

Please refer to the server deployment thread for news and updates:

  • On Tuesday, July 14th, the majority of the grid was updated with server release 544419, first deployed to the RC channels on Wednesday, July 8th. This should resolve issues with off-line inventory offers and group notice attachments, although a viewer-side update is also required, which is in the current Arrack RC viewer.
  • On Wednesday, July 15th, the RC channels should be updated with server maintenance update 544832, designed to resolve issues with some internal service updates, chat range improvements and capability improvements.

SL Viewer

There have been no official viewer updates to mark the start of the week, leaving the current pipelines as follows:

  • Current Release viewer version 6.4.3.543157, dated June 11, promoted June 23, formerly the CEF RC viewer – No Change.
  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
  • Project viewers:
    • Custom Key Mappings project viewer, version 6.4.5.544079, June 30.
    • Mesh uploader project viewer, version 6.4.4.543141, June 11.
    • Copy / Paste viewer, version 6.3.5.533365, December 9, 2019.
    • Project Muscadine (Animesh follow-on) project viewer, version 6.4.0.532999, November 22, 2019.
    • Legacy Profiles viewer, version 6.3.2.530836, September 17, 2019. Covers the re-integration of Viewer Profiles.
    • 360 Snapshot project viewer, version 6.2.4.529111, July 16, 2019.

Cloud Uplift

I don’t know if any of you have looked at AWS, but it’s a huge and complex system, so the learning curve on how to build servers, get them deployed, set up networks, security, etc etc etc is pretty tough … Not a surprise, just a lot of learning and work.

– Simon Linden, SUG Meeting, July 14th

Two publicly-accessible regions  – Morris and Ahern – on Aditi (the beta grid) are now running in the cloud. Aside from outbound HTTP messaging and e-mail, they should function with no discernible difference to regions within the Lab’s co-lo facility.

Ahern and Morris on Aditi (the beta grid) are now operating from the cloud

Commenting on the HTTP messaging / e-mail situation, Oz Linden stated:

There are abuse constraints in AWS that we need to make sure we don’t violate. Both outbound HTTP and Email are ways that scripts could cause problems. We have a way to regulate HTTP out that we’re pretty sure of, and which you should be able to test fairly soon on main grid simulators. llEmail may get some new constraints and/or more severe throttles … still studying that one. When we have some updates on that, we’ll post in the LSL forum.

– Oz Linden, SUG Meeting, July 14th

It is believed that the current HTTP / e-mail out issues should not affect HTTP / e-mail between regions. The issue also shouldn’t affect llTargetedEmail, since the caller cannot specify an arbitrary email address.

SL17B Meet Oz Linden – a summary with video and audio

via Linden Lab
On Wednesday, June 24th, 2020 at the SL17B celebrations, the third of five Meet the Lindens sessions was held, featuring Oz Linden, the Lab’s Vice President of Engineering.

The following is a summary of the session covering the core topics raised, with selected audio extracts. The notes provided have been taken directly from the official video of the session, which is embedded at the end of this article. Time stamps to the video are also provided for ease of reference.

Note that this is a summary, not a full transcript, and items have been grouped by topic, so may not be presented chronologically when compared to the video.

Table of Contents

Audio extracts, where included, have been cleaned-up and balanced to remove pauses, repetitions, etc.

In places, information that is supplementary to Oz’s comments is provided in square braces (.i.e. [ and ]) are used in the body text below to indicate where this is the case.

About Oz

  • Oz Linden

    Joined the company in 2010 specifically to take on the role of managing the open-source aspects of the Second Life viewer and managing the relationship with third-party viewers.

  • He came to Linden Lab out of a desire to do something “fun” after working in the telecommunication arena, notably with voice over IP systems (VOIP), which he defines as being “really interesting technology with some really fascinating challenge”, but in terms of it being fun, it really didn’t do what I wanted it to do.”
  • For the first two years of his time at the Lab, he was primarily focused on the open-source viewer work and in refining the overall viewer maintenance process, before his role started expanding to encompass more and more of the engineering side of Second Life.
  • When work on Sansar started in earnest, he pro-actively campaigned within the Lab for the role of  Technical Director for Second Life, working to build a team of technical staff around him who all shared a passion for Second Life.
  • In 2019 he was promoted to Vice President, Second Life Engineering (Vice President of Engineering following the sale of Sansar in early 2020), and joined the Lab’s management team alongside Grumpity and Patch Linden (see: Linden Lab’s management team expands: congrats to Grumpity, Patch and Oz).
  • Together with Grumpity and Patch, he forms what Grumpity calls the “troika” overseeing Second Life’s continued development.
  • Classifies his attraction to working with Second Life as perhaps falling into three core areas:
    • The open-source nature of the viewer and being directly involved with how SL users are using the viewer and what they do with it – which can often times take the Lab entirely by surprise.
    • The challenge of trying to implement new technologies alongside of (rather than simply replacing) older technologies.
    • Working with the operations team and others to ensure SL constantly evolves without (as far as is possible) breaking anything – a process he refers to and rebuilding the railway from a moving train.
  • Note that his avatar appears bald in the Meet the Lindens publicity shot at the top of this article, as he and his team participated in the 2020 Bid a Linden Bald event to raise money for RFL of SL, and has the team raising the least, that had to spend a month in-world sans hair.

Back to top

His Team

Has it Expanded Since the Sale of Sansar?

[Video: 4:47-5:48]

  • He did persuade a number of people to move back from Sansar to Second Life [those known to have moved back at the time were Runitai Linden (graphics) and Maestro Linden and Monty Linden (engineering), although they obviously may not be the only people to move / move back to work on Second Life].
  • Hiring of new staff has also continued [notable within this are Ptolemy Linden and Euclid Linden (graphics) and at least one Android development specialist].
  • At the time of the event, also looking to hire a further systems engineer working on the back-end Linux systems.

What Impact has the Pandemic Had?

[Video: 6:02-8:07]

  • “Pretty minimal”
  • The Engineering and Operations teams and his developers were already “pretty distributed”, with some of the teams working out of three of the Lab’s offices – Seattle, San Francisco and Boston – but around one-third to half of the total staff reporting to him (Oz included) have generally worked from home as “Moon Labbers” [the “Moon Lab” being LL’s term for remote working].
  • So teams already very familiar with remote working, operating across time zones and holding meetings in SL, as well as tools like video chat, and the transition for the rest has been “pretty much” seamless.
  • Probably the biggest impact is that the team isn’t getting together for their summer meet-up where they socialise and lay plans for future work on SL.

Back to top

Cloud Uplift

Why Is It Being Done?

[Video: 9:00-13:01]

  • Historically, Linden Lab has operated its systems and services the “traditional” way: dedicated hardware, and infrastructure running in dedicated facilities [at one time three data centres, but for the last several years a single co-location (co-lo) centre in Arizona].
  • Actually had to develop a lot of the methodologies the company now uses to manage all of the SL services simply as a result of the speed at which the platform initially grew, building capabilities for which there were no “standard” solutions.
  • Time has moved on, and Amazon and others have developed the means for systems and services to be run / provisioned through the cloud. These services allow Linden Lab to leverage a range of options and capabilities in a number of ways.
  • A particular aspect of the move is that LL no longer has to invest time, effort and money into hardware and infrastructure, but can essentially hand these off to AWS, allowing them to concentrate on SL’s operations and development.
  • With hardware in particular, it has been a number of years since the Lab upgraded their servers, so transitioning to the cloud avoids an expensive capital expenditure in new hardware, and similar expenditures in the future.  For example:
    • In the current environment, if the Bake Service [a collection of servers use by the Lab to generate and manage avatar appearances and ensure they are consistent across viewers] needed upgrading to more powerful servers, LL would have to acquire, test and implement that hardware, and then transition the Bake Service to it.
    • Running via the cloud means picking the required hardware from a catalogue provided by Amazon, who then take care of the heavy lifting to ensure the Bake Service works as required on the selected hardware.
  • Overall, the priority of the work is such that the three goals Oz has set himself : Uplift, Uplift, Uplift.

How is the Uplift Progressing?

[Video: 16:46-19:05]

  • It’s stressful but going well.
  • All of the inventory databases were successfully moved several months ago – twice, in fact: first to the cloud, then to a different type of cloud server. This work was completed so successfully, users were not even aware of any change.
  • The intermediary service sitting between the inventory database and the viewer was also successfully transitioned to AWS. It has also been running for “some time now”, again without users noting any difference.
  • A lot of the back-end services that users never directly interact with have also been successful transitioned
  • There is still a lot of work to do, but the plan is to have Second Life “out of the co-lo by the end of the year”.

Continue reading “SL17B Meet Oz Linden – a summary with video and audio”

SL17B Meet Ebbe Altberg- a summary with video and audio

via Linden Lab
On Monday, June 22nd, 2020 at the SL17B celebrations, the first of five Meet the Lindens sessions was held, featuring the Lab’s CEO, Ebbe Altberg, aka Ebbe Linden.

The following is a summary of the session covering the core topics raised, with  audio extracts where relevant. The notes provided have been taken directly from the official video of the session, which is embedded at the end of the article. Time stamps to the video are also provided for ease of reference. In addition, audio extracts are provided in places that may be of particular interest to readers.

Table of Contents

When reading this article, please note:

  • It is not a full transcript:
    • Discussion points have been grouped by topic, and not necessarily in the order raised during the session.
    • I have focused on those topics liable to be of the most interest to readers / generated the most informative answers, so this is not a summary of all comments, feedback, etc.
    • Topics are given as bullet-point highlights for ease of reference.
  • In places, information that is supplementary to Ebbe’s comments is provided, and square braces (.i.e. [ and ]) are used in the body text below to indicate where this is the case.
  • Audio extracts have been cleaned-up to remove repetition or pauses, etc.

About Ebbe

[Video: 3:44-6:21]

Note: the following is taken from both Ebbe’s comments and my own research into his background, carried out when he joined Linden Lab in 2014, and which also included input from Ebbe.

  • Swedish by birth and still by nationality – he is still working in the US on a green card.
  • Graduated from Tärnaby Skidhem in 1983. He had hoped to be a ski racer – with eyes on the Swedish national team and the world cup – but was prevented from pursuing this career due to a back injury.
  • Instead went to the USA to study at Middlebury College, Vermont, USA, where he spent a lot of time in the art studio and the computer lab in an extreme left brain / right brain type of education”, before graduating with a degree in Fine Arts and a concentration in Computer Applications.
Ebbe Linden, aka Ebbe Altberg. Credit: Strawberry Linden
    • He  “slipped into Microsoft on a random banana peel”, where he spent twelve years. He was particularly involved with the Office products (Word, Mac Office, etc.), and although he wasn’t directly responsible for Clippy! – he did oversee it being ported to Mac Office 98.
  • In 2000, he joined Ingenio, a company that created marketplaces for people to buy and sell information over the phone. As well as managing the engineering, program management, operations, and quality teams, he also served as both the company’s interim CEO its Chief Product Officer. He also “racked up quite a few patents there.”
  • Joined Yahoo! in 2008, filling out a number of senior roles, working in both Europe and the US.As the Senior Vice President for Media Engineering based in the USA, but with global responsibly for Media Engineering, managing  an organisation of more than 600 engineers, architects, program managers and quality engineering staff, and with dotted-line oversight of some 150 product managers and designers.
Linden Lab’s chairman of the Board, Jed Smith, is a long-time friend of Ebbe Altberg, and had previously tried to get Ebbe to join the company prior to his appointment as CEO in 2014. (image: Owl Ventures)
  • Moved from Yahoo! to San Francisco based BranchOut, a small company that had, prior to his joining built a 25 million user base for its professional networking app before seeing that number shrink to just 3 million. He was specifically responsible for pivoting the company to a new workplace messaging application called Talk.co, launched in October 2013.
  • Has had a long exposure with SL indirectly through his son Aleks, who initially joined the Teen Grid before moving to establish his own in-world business.
  • Has also been long-term friends with LL board Chair, Jed Smith, through whom he met Philip Rosedale. Smith had asked Ebbe to consider the LL CEO position previously to 2013/14, but “things “didn’t line up” .
  • Is immensely proud of the all that the company has achieved and continues to be drawn by both the rewards and challenges involved in running a platform that is so technically and socially diverse.

 

Back to top

Working at the Lab

Rewards and Challenges Working with SL

[Video: 6:23-10:20]

  • Loves the technical / product aspects of the platform and the diversity of potential use cases it can meet. Also loves the rich diversity of ways users make use of SL creatively, socially, etc., that mean the platform constantly offers unique opportunities and challenges.
  • Enjoys the fact that SL makes it possible to meet people from around the world and from all walks of life who find value in the platform for so many different reasons.
  • These aspects also, for him, present the challenges of working with SL: putting all the different technologies that make SL work together such that they can form a virtual world where people can create, socialise, earn income, etc.
  • There’s also the challenge of talking to a customer base that is not of a single mind in using the platform, but rather is a range of user communities, each of which has nuanced needs and requirements that need to be met.
  • Also likes the challenge of trying to extend and build a product set that no-one else has managed to develop to the same degree – such as with SL’s economic model and the development of Tilia Pay.
  • The strength with SL that he loves is the sheer diversity within the technology required or SL and the people that use is – which is also the platform’s most engaging challenge.

SARS-Cov-2 Impact

[10:22-12:04; 12:30-18:53]

  • Is appreciative of the power that SL has in bringing people together during the SARS-CoV-2 pandemic and providing a safe space for continued interaction, and that it can continue to help furnish those using it to generate an income to continue to do so.
  • From a business perspective, SL has seen significant increases in demand. However, this has been somewhat impacted by the “land shortage” [see The Cloud Uplift, below for more on this].
  • This increase is not just from “social” users; here has been “a lot” of demand from businesses wanting to host meetings through the platform, education institutions wanting to hold lessons, etc.
  • Company has been very fortunate in its operations because, while it does have offices in San Francisco, Seattle, Boston and Atlanta, many of the staff have always worked from home, so there has always been the assumption of remote working [even the Operations Team works remotely from LL’s co-location data centre in Arizona]. So, moving to that model of operations was less stressful than it might have been.
  • The real hamper in the move has been more the “knock-on” effect caused by the isolation – having children at home whilst trying to work, seeing to their needs, etc.
  • Overall is very pleased with how the company has been able to continue to manage SL and move ahead in plans and development.
  • Pandemic has also caused the media to re-examine SL, and Marketing has been via busy dealing the increased interest in how the platform and how it can be of use to people / organisations during the pandemic.
  • What has been particularly pleasing is the more positive view the media has of the platform, and the recognition of its maturity as a platform.
  • Like to point out to reporters that Second Life isn’t “old”, it is “mature”, which is not necessary a bad thing when talking about a platform.

Back to top

The Cloud Uplift

[Note: Cloud uplift is the term used for the project to transition all of the Second Life services from hosting in a single co-location data centre used by Linden Lab and using their own hardware, to provision it all via Amazon AWS cloud services.]

[Video: 19:51-23:25]

  • Likely to be around 3-4 months before new regions are once again available, although it is understandably hard to put a definite date on things.
  • The shortfall is due to LL wanting to cease any expenditure in hardware and supporting infrastructure for SL during the cloud transition, believing they had sufficient reserves to offer during the uplift period – but the SARS-CoV-2 pandemic resulted in an unexpected burn through of that reserve.
  • Provisioning and testing new hardware and infrastructure is being avoided, as this would effectively be “lost” capital expenditure.
  • The uplift work is the primary focus of the product, engineering and operations teams at the Lab, with many services have actually already been transitioned to AWS.
  • Details of which systems these might be are not generally given out by LL due to the fact users often make false assumptions on things like issues when aware of such information.
  • Region servers [aka simhosts] make up the majority of the Lab’s hardware, and the Lab now has a test region server successfully running within AWS, but there is still “quiet a bit more work to do” in terms of security and other elements before the Lab will be in a position to offer a region product running in AWS.

Back to top

Continue reading “SL17B Meet Ebbe Altberg- a summary with video and audio”