Re: [vwrap] SimianGrid protocols and VWRAP

"Hurliman, John" <john.hurliman@intel.com> Mon, 14 June 2010 22:08 UTC

Return-Path: <john.hurliman@intel.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FC473A69F0 for <vwrap@core3.amsl.com>; Mon, 14 Jun 2010 15:08:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.998
X-Spam-Level:
X-Spam-Status: No, score=-3.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zrGTMNLjG-cg for <vwrap@core3.amsl.com>; Mon, 14 Jun 2010 15:08:13 -0700 (PDT)
Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by core3.amsl.com (Postfix) with ESMTP id E39E728C0E1 for <vwrap@ietf.org>; Mon, 14 Jun 2010 15:08:12 -0700 (PDT)
Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 14 Jun 2010 15:08:14 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos; i="4.53,416,1272870000"; d="scan'208,217"; a="288846499"
Received: from rrsmsx604.amr.corp.intel.com ([10.31.0.170]) by azsmga001.ch.intel.com with ESMTP; 14 Jun 2010 15:08:12 -0700
Received: from rrsmsx605.amr.corp.intel.com (10.31.1.129) by rrsmsx604.amr.corp.intel.com (10.31.0.170) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 14 Jun 2010 16:08:13 -0600
Received: from rrsmsx506.amr.corp.intel.com ([10.31.0.39]) by RRSMSX605.amr.corp.intel.com ([10.31.1.129]) with mapi; Mon, 14 Jun 2010 16:08:12 -0600
From: "Hurliman, John" <john.hurliman@intel.com>
To: "vwrap@ietf.org" <vwrap@ietf.org>
Date: Mon, 14 Jun 2010 16:08:12 -0600
Thread-Topic: [vwrap] SimianGrid protocols and VWRAP
Thread-Index: AcsKR2Rgpp5zlY/aS62A42f0mH4+4wBv+Jag
Message-ID: <62BFE5680C037E4DA0B0A08946C0933DDA50BA62@rrsmsx506.amr.corp.intel.com>
References: <AANLkTilv7aOo0E29iZGMSfwl797DMDXITHGJF2U-56Za@mail.gmail.com>
In-Reply-To: <AANLkTilv7aOo0E29iZGMSfwl797DMDXITHGJF2U-56Za@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_62BFE5680C037E4DA0B0A08946C0933DDA50BA62rrsmsx506amrcor_"
MIME-Version: 1.0
Subject: Re: [vwrap] SimianGrid protocols and VWRAP
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2010 22:08:22 -0000

I've recently been working closely with my team at Intel on systems scalability problems in virtual worlds and have not had as much time to focus on VWRAP implementation. I did finish up a bit of coding over the weekend though and added initial support for VWRAP launch documents[1] to SimianGrid[2]. A bit of background:

SimianGrid is a set of web services that provides critical backend components for a virtual world. These are the "grid services" in Second Life or OpenSim terminology, or Agent Domain in VWRAP terminology. The components include content storage and distribution (assets), user accounts/identity, user inventory, spatial mapping (region registration, map tiles), and a login service. This is enough to provide full support for the grid connector API in the upcoming release of OpenSim 0.7 (which will natively support SimianGrid), and is also compatible with the lightweight simulation platform we use for prototyping called Simian (which SimianGrid was named after). SimianGrid is written entirely in PHP, and also includes a web frontend named SimianGridFrontend using the CodeIgniter framework and a WebDAV inventory frontend named SimianGridWebDAV using the SabreDAV library.

A major hurdle that OpenSim-based virtual worlds have to overcome is the account creation, login process, and content import process for every world a user visits (and the myriad of issues surrounding each of those topics). While one of the ultimate goals of VWRAP is to solve all of those issues, VWRAP launch documents provide a solution for the login process and a stepping stone toward solving the account creation process. The plan is for SimianGrid to support two launch document methods: authenticated and unauthenticated. Either can optionally carry a starting location URI. Unauthenticated mode is as simple as telling the rich client where the login URL of the grid is. Authenticated mode carries identity information (agent name) and the login URL is actually a capability allowing direct login from web to world. This also functions as a successor to the GridInfo[3] protocol that OpenSim developed to inform viewers of various grid-specific URLs.

The original plan was for launch document support to go into Snowglobe, but with Snowglobe VWRAP development on hiatus I refitted my Cable Beach Launcher app into VWRAP Launcher that I will release in a few days. If a VWRAP teleport draft surfaces I can start on an implementation, but that won't get far without viewer support for it.

Meadhbh, I have a small number of refinement suggestions for the launch document spec (again) but I'll wait until we have a few experimental grids actually running the code before making any firm arguments.

[1] http://tools.ietf.org/html/draft-hamrick-vwrap-launch
[2] http://openmetaverse.googlecode.com/
[3] http://opensimulator.org/wiki/GridInfo

John


From: vwrap-bounces@ietf.org [mailto:vwrap-bounces@ietf.org] On Behalf Of Morgaine
Sent: Saturday, June 12, 2010 8:53 AM
To: vwrap@ietf.org
Subject: [vwrap] SimianGrid protocols and VWRAP

John, I know that you've been doing some very interesting work on the SimianGrid project, and that some parts of it are related to the standards effort in this Working Group.  Unfortunately your protocol work beyond LLSD has never been described to us here.

The IETF standards process operates through the mailing lists of its Working Groups, so if you want your work to have a direct bearing on our protocol discussions, you need to describe your protocol elements here.  Actual implementations are of course exceedingly important and non-optional, but the analysis, discussion and refinement of code into an IETF standards protocol happens here, not in individual project groups.

You've said before that more information is forthcoming.  I would very much welcome that.  While your code seems to be progressing nicely, we need any new protocol information described here to help the Working Group move along on the standards process.


Morgaine.






======================================
On Sat, Jun 12, 2010 at 12:35 AM, Hurliman, John <john.hurliman@intel.com<mailto:john.hurliman@intel.com>> wrote:
I cannot make it out to Maastricht. I would be interested in hearing from anyone who is still working on VWRAP though.
John

> -----Original Message-----
> From: vwrap-bounces@ietf.org<mailto:vwrap-bounces@ietf.org> [mailto:vwrap-bounces@ietf.org<mailto:vwrap-bounces@ietf.org>] On Behalf
> Of Joshua Bell
> Sent: Friday, June 11, 2010 1:28 PM
> To: vwrap@ietf.org<mailto:vwrap@ietf.org>
> Subject: [vwrap] Meeting in Maastricht/IETF78 ?
>
> Quick poll:
>
> Are any VWRAP participants planning to attend IETF78 in Maastricht and,
> if so, are there VWRAP issues you would like to have on the agenda for
> a face-to-face meeting?
>
> The chairs are trying to gauge whether or not we should request a
> session slot. You can reply to the list, or privately to me.
_______________________________________________
vwrap mailing list
vwrap@ietf.org<mailto:vwrap@ietf.org>
https://www.ietf.org/mailman/listinfo/vwrap