Difference between revisions of "PyOGP"

From Second Life Wiki
Jump to navigation Jump to search
(Added another archive)
 
(134 intermediate revisions by 12 users not shown)
Line 1: Line 1:
{{PyOGP/navigation}}
== Overview ==
== Overview ==
[[AWG]] ([[AW_Groupies|in-world discussion group page]]) and Linden Lab plan to share the effort in writing a [[Pyogp_Test_Harness|test harness]] which executes tests against implementations of the Open Grid Protocol [[SLGOGP_Draft_1|(OGP)]]. The intent is not to test SL or OpenSim (or gridX) themselves. Rather, the desire is to create a framework where the implementations of the protocols can be tested in any virtual environment implemented per the Open Grid Protocols as documented. We plan to be able to test at the smallest functional level possible, akin to unit testing, and to have the ability to use the framework to sequence steps to enable state specific tests to be run.


The longer term vision is essentially a [[Pyogp_Client_Lib|client library]], capable of navigating the grid and interacting with the various hosts, sitting next to a testing framework, happily running along telling us what works where, and where something needs a little attention to work according to specification...
=== What Is It? ===


For a smidge more detail on OGP, see a visual representation of the upcoming [[Open_Grid_Platform_Projects_Q2-Q3 | projects]] and a general [https://wiki.secondlife.com/wiki/Structural_Design_Overview introduction].
Pyogp is an open source project to explore a suite of python based Second Life client libraries and to produce an automated testing framework.
 
PyOGP is useful for:
* learning more about Second Life's client-server relationship
* prototyping client side features
* quickly writing tests for software which communicates using LLMessageSystem-like messages
* demonstrating protocol proposals
* building test suites which validate Second Life simulator and grid functionality
 
=== Getting Started ===
 
See [[PyOGP Client Library Development Sandbox]] for instructions on the mechanics of working with the PyOGP package suite.
 
For a more comprehensive overview of working within the structure of classes and event systems in PyOGP packages, take a look at [[PyOGP Client Library]].
 
=== How To Contribute ===
* Source: [[Pyogp/Client_Lib/The_Development_Sandbox | Checkout Instructions]]. See the [[Open_Source_Portal|Open Source Portal]] for details on being a contributor
* in-world group: pyogp (open enrollement)
* IRC: irc://irc.freenode.com/#pyogp
* Jira: http://jira.secondlife.com/browse/OPEN
* Related Meetings
** Enus Linden's office hours: Friday @ 1:00 http://slurl.com/secondlife/Longfellow/9/97/28


== Project Status ==
== Project Status ==
*June 26, 2008 - We have begun to write some code to prototype the client library framework. We have also discussed some of the details of the client lib and how we should begin to structure it.
== Project Tasks ==
These are tasks that need to be accomplished for the overall project. Each part of the project (library and harness) also has its own task list.
#Set up collaboration
#*Discussion Times - Despite Enus heading out for a 3 week vaca on the right coast of the usa, I'll set up an office hours time of sorts to meet with AWG and Lindens to chat about progress and next steps. Coming soon to a gcal near you.
#*Mailing list - should probably set this up to
#(complete?)Repository - So Mercurial, aka hg, was looking promising, but we decided internally that we aren't quite ready for that. There is a move toward Mercurial internally, but we need to work this out before moving forward with it on this effort. It is quite possible that this library and test harness work will become a guinea pig for hg with Linden Lab in the open source arena. Until then, I bring you pyogp on SVN: http://svn.secondlife.com/trac/linden/browser/projects/2008/pyogp.
#(complete?)Contributions - As we are going to be hosting the source code for this, contributions will be subject to Linden Lab's standard [http://secondlifegrid.net.s3.amazonaws.com/docs/SLVcontribution_agmt.pdf contributor's agreement]. I hope this doesn't prevent good work here...
#(complete?)License - The Apache V2 License has been selected as the license of choice for pyogp (or whatever name we agree upon, see next point).
#(complete?)Naming (I'd like to not debate for an hour on these. Tao had suggestions, I like em. Please speak up if you have strong reservations about the suggested naming).
#*Python client library name - pyogp
#*Python test framework (unittest/doctest) - ogptest
#Start planning structure for Client Lib (see client lib page tasks)
#Start planning structure for test harness (see test harness page tasks)


== Technical Detail ==
PyOGP has moved to https://bitbucket.org/account/user/lindenlab/projects/PYOG
#The beta grid has an agent domain login accessible at https://login1.aditi.lindenlab.com/cgi-bin/auth.cgi
 
#Currently available Regionuri list (log into the agent domain running on aditi, show up on vaak!). Use the regionuri parameter in viewers built from http://svn.secondlife.com/trac/linden/browser/branches/interop-2, or better yet for this effort, use a pyogp script!
client_proxy is now stable[https://lists.secondlife.com/pipermail/pyogp/2010-June/000255.html], though it's only logging things currently.  
#*Regionuri list (log into the agent domain running on aditi, show up on vaak!). Use the regionuri parameter in viewers built from http://svn.secondlife.com/trac/linden/browser/branches/agent-domain-2
#*#http://sim1.vaak.lindenlab.com:13000    Dore
#*#http://sim1.vaak.lindenlab.com:13001    Card
#*#http://sim1.vaak.lindenlab.com:13002    Grigiano
#*#http://sim1.vaak.lindenlab.com:12035    Island for Misfit Toys
#*#http://sim2.vaak.lindenlab.com:12035    Ahern
#*#http://sim2.vaak.lindenlab.com:13000    Miramare
#*#http://sim2.vaak.lindenlab.com:13001    Morris


== Collaboration ==
Note: I think the official repository got lost when bitbucket abandoned mercurial. I saved a copy of the 3 repositories: https://bitbucket.org/tapplek/ [[User:Tapple Gao|Tapple Gao]] ([[User talk:Tapple Gao|talk]])
Once we get a collaboration schedule determined it will be posted here.
=== Contributors ===
*Main Internal Contributors
** Enus -
**Infinity -
**Locklainn -
*Main AWG Contributors (subject to the contributor's agreement)
**Tao Takashi -
**Saijanai Kuhn -
=== Related Chat Logs ===
*April: [[AWGroupies-2008-04-29|AW Groupies 29 April]]
*May: [[AWGroupies-2008-05-20|AW Groupies 20 May]]  · [[User:Which_Linden/Office_Hours/2008_May_22| Which LInden Office Hours 22 May]]
*June: [[User:Zero_Linden/Office_Hours/2008_June_19|Zero Linden Office Hours 19 June]] [[AWGroupies-2008-06-24|AW Groupies 24 June]] [[User:Zero_Linden/Office_Hours/2008_June_24|Zero Linden Office Hours 24 June]]


== Links ==
Another archive of the repositories that were non-empty in [https://bitbucket-archive.softwareheritage.org/projects/li/lindenlab/ the softwareheritage.com capture]: https://github.com/orgs/SL-PyOGP/repositories [[User:Kadah Coba|Kadah Coba]] ([[User talk:Kadah Coba|talk]])
Please add to the list as you see fit. The more we throw in here, the better off we are in the long run.
 
=== Project pages ===
== Pic of the Moment ==
*[[Pyogp_Client_Lib|Python Client Library]] - dedicated page to the client library
[[Image:355571.jpg|900x835px|the EnusBots are coming!]]
*[[Pyogp_Test_Harness| Pyogp Test Harness]] - dedicated page to the test harness
 
*[[Pyogp/Roadmap| Pyogp Roadmap]] - the overall plan for pyogp. Each dedicated page, however, has its own roadmap
Image used with permission. Taken by [[User:Opensource_Obscure|Opensource Obscure]]. (thanks oo! <3)
*[[Pyogp/Specification| Pyogp Specification]] - the technical specifications and guidelines to follow when working on the code
*Internal jira tracking Linden Lb's involvement with the work: uh, I'll get back to you.
*Repository - http://svn.secondlife.com/trac/linden/browser/projects/2008/pyogp.
*License - The Apache V2 License has been selected as the license of choice for pyogp.
*Communication
**IRC: irc://irc.freenode.com/#pyogp
**mailing list: TBD
**[[AW_Groupies]] - AWG in-world discussion group


== Licensing ==
== Licensing ==
# The code written as part of this effort is subject to the Apache v2 license. Read more at http://opensource.org/licenses/apache2.0.php.
Contributions to Pyogp are subject to Linden Lab's [[Linden_Lab_Official:Contribution_Agreement|Contribution_Agreement]]. The Pyogp open source code is made available subject to the Apache v2 license. Read more at [http://opensource.org/licenses/apache2.0.php opensource.org] and [http://www.apache.org/licenses/LICENSE-2.0 apache.org].


   <excerpt>
   <excerpt>
Line 83: Line 61:
   </excerpt>
   </excerpt>


== Picture of the Moment ==
== History ==
# 05/29/08: Using quite nasty code, a first contact of sorts via python into the agent domain and onto a simulator:[[Image:Pyogp_roots.jpg|thumb|left| pyogp and ad enabled sl viewer on a vaak sim via aditi's agent domain]]
 
Linden Lab and the [[AWG]] ([[AW_Groupies|in-world discussion group page]]) worked together to develop a set of open protocols called the [[Open Grid Protocol]] that can be used to create a virtual world where regions are independently operated (not only by Linden Lab). The project aimed to allow people (organizations, individuals, and the like) to host their own regions in the virtual world and be able to interact and communicate with people in regions hosted elsewhere. In essence, the project's goal was to allow open-source region hosting.
 
AWG and Linden Lab plan to share the effort in writing a test harness that executes tests against implementations of the Open Grid Protocol.
 
The intent is not to test SL or OpenSim (or gridX) themselves. Rather, the desire is to create a framework where the implementations of the protocols can be tested in any virtual environment implemented per the Open Grid Protocols as documented. The goal is to use the test harness to test the implementations to make sure that the virtual environment is interoperable with the other virtual environments that have implemented the OGP. However, we also plan to test the current SL protocols (the Legacy protocols). We plan to be able to test at the smallest functional level possible, akin to unit testing, and to have the ability to use the framework to sequence steps to enable state specific tests to be run.
 
The longer-term vision is essentially a [[Pyogp_Client_Lib|client library]], capable of navigating the grid and interacting with the various hosts, sitting next to a testing framework, happily running along telling us what works where, and where something needs a little attention to work according to specification...
 
For more detail on OGP, see a visual representation of the upcoming [[Open Grid Platform Projects Q2-Q3|projects]] and a general [[Structural Design Overview|introduction]].
 
=== Notes from the kickoff meeting ===
 
At the AWG meeting held April 29, 2008, we discussed what a test harness could look like that would be used to test the agent-domain, rez-avatar, and overall work being done implementing the open grid protocols. I'd like to summarize, and continue the discussion on the mailing list, in-world, and on the wiki. See [[AWGroupies-2008-04-29|meeting chat log]].
 
How do we start?
 
Let's work on defining the test harness components (from the meeting):
# Login
# Caps (and while it's around the UDP pipe)
# Message Handlers (see chttp)
# Basic web server parts for the Agent, Region and grid bits (ideally a snap in framework)
# Test framework
# Test data (I put this here, not really as a component of the harness, more as a "i'm not telling you my test account's password and what are we gonna do about it" thing)
 
Python seems to be the flavor of choice here, with a requirement that it accommodate non-python components as needed. The repository for the code is proposed to be maintained by Linden Lab, distributed as an open source export, under the Apache v2 License (see http://opensource.org/licenses/apache2.0.php). The process and details here are tentative, and need more attention...
 
There is plenty to be figured out. How to start, who wants to play, details are all TBD. My role is primarily intended as one who will facilitate dialogue and contribute as much as possible, but this is intended as a joint effort.
 
-- Enus Linden


[[Category:Architecture Working Group]]
[[Category:Grid_Interoperability]]
[[Category: Pyogp|*]]
[[Category:Pyogp_Kitchen_Sink]]
[[Category: AW Groupies]]
[[Category: AW Groupies]]
[[Category:Automated Testing]]

Latest revision as of 03:19, 13 September 2022

Overview

What Is It?

Pyogp is an open source project to explore a suite of python based Second Life client libraries and to produce an automated testing framework.

PyOGP is useful for:

  • learning more about Second Life's client-server relationship
  • prototyping client side features
  • quickly writing tests for software which communicates using LLMessageSystem-like messages
  • demonstrating protocol proposals
  • building test suites which validate Second Life simulator and grid functionality

Getting Started

See PyOGP Client Library Development Sandbox for instructions on the mechanics of working with the PyOGP package suite.

For a more comprehensive overview of working within the structure of classes and event systems in PyOGP packages, take a look at PyOGP Client Library.

How To Contribute

Project Status

PyOGP has moved to https://bitbucket.org/account/user/lindenlab/projects/PYOG

client_proxy is now stable[1], though it's only logging things currently.

Note: I think the official repository got lost when bitbucket abandoned mercurial. I saved a copy of the 3 repositories: https://bitbucket.org/tapplek/ Tapple Gao (talk)

Another archive of the repositories that were non-empty in the softwareheritage.com capture: https://github.com/orgs/SL-PyOGP/repositories Kadah Coba (talk)

Pic of the Moment

the EnusBots are coming!

Image used with permission. Taken by Opensource Obscure. (thanks oo! <3)

Licensing

Contributions to Pyogp are subject to Linden Lab's Contribution_Agreement. The Pyogp open source code is made available subject to the Apache v2 license. Read more at opensource.org and apache.org.

 <excerpt>
 Copyright 2008, Linden Research, Inc.
 
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. </excerpt>

History

Linden Lab and the AWG (in-world discussion group page) worked together to develop a set of open protocols called the Open Grid Protocol that can be used to create a virtual world where regions are independently operated (not only by Linden Lab). The project aimed to allow people (organizations, individuals, and the like) to host their own regions in the virtual world and be able to interact and communicate with people in regions hosted elsewhere. In essence, the project's goal was to allow open-source region hosting.

AWG and Linden Lab plan to share the effort in writing a test harness that executes tests against implementations of the Open Grid Protocol.

The intent is not to test SL or OpenSim (or gridX) themselves. Rather, the desire is to create a framework where the implementations of the protocols can be tested in any virtual environment implemented per the Open Grid Protocols as documented. The goal is to use the test harness to test the implementations to make sure that the virtual environment is interoperable with the other virtual environments that have implemented the OGP. However, we also plan to test the current SL protocols (the Legacy protocols). We plan to be able to test at the smallest functional level possible, akin to unit testing, and to have the ability to use the framework to sequence steps to enable state specific tests to be run.

The longer-term vision is essentially a client library, capable of navigating the grid and interacting with the various hosts, sitting next to a testing framework, happily running along telling us what works where, and where something needs a little attention to work according to specification...

For more detail on OGP, see a visual representation of the upcoming projects and a general introduction.

Notes from the kickoff meeting

At the AWG meeting held April 29, 2008, we discussed what a test harness could look like that would be used to test the agent-domain, rez-avatar, and overall work being done implementing the open grid protocols. I'd like to summarize, and continue the discussion on the mailing list, in-world, and on the wiki. See meeting chat log.

How do we start?

Let's work on defining the test harness components (from the meeting):

  1. Login
  2. Caps (and while it's around the UDP pipe)
  3. Message Handlers (see chttp)
  4. Basic web server parts for the Agent, Region and grid bits (ideally a snap in framework)
  5. Test framework
  6. Test data (I put this here, not really as a component of the harness, more as a "i'm not telling you my test account's password and what are we gonna do about it" thing)

Python seems to be the flavor of choice here, with a requirement that it accommodate non-python components as needed. The repository for the code is proposed to be maintained by Linden Lab, distributed as an open source export, under the Apache v2 License (see http://opensource.org/licenses/apache2.0.php). The process and details here are tentative, and need more attention...

There is plenty to be figured out. How to start, who wants to play, details are all TBD. My role is primarily intended as one who will facilitate dialogue and contribute as much as possible, but this is intended as a joint effort.

-- Enus Linden