+1 , we need these new servers tested in production use by multiple 
people/grids for a reasonable lenght of time. Before we actually remove the old 
servers from SVN.

Once they have been tested and there is full documentation then I'm +1 to 
removing the old ones.

Maybe a starting point would be to set up the configs so by default everything 
was configured for the new servers.

I also would rather a different name than BUST, and also before any protocol 
changes are done, see full documentation about the plans. 

We have just gone through a extended period of a lot of refactoring and rapid 
changes. I think now is the time to slow the changes down a bit and take a bit 
of time to reflect on things and test them and get any new bugs out of the 
system.

--- On Wed, 8/7/09, Charles Krinke <[email protected]> wrote:

From: Charles Krinke <[email protected]>
Subject: Re: [Opensim-dev] Deprecate OpenSim.Grid.InventoryServer and 
OpenSim.Grid.AssetServer?
To: [email protected]
Date: Wednesday, 8 July, 2009, 4:18 PM

Well, this may or may not be, Melanie. But, I would feel a whole lot more 
comfortable about the whole proposal *after* at least two different groups 
report success in configuring BUST and that it is not busted.

At that point, we need enough clear and concise documentation on the wiki to 
allow others running grids to be able to change. After a half dozen different 
grids have adopted the notion of BUST and determined it is not busted, then we 
could consider deprecating our existing UGAIM.

Charles

From: Melanie <[email protected]>
To: [email protected]
Sent: Wednesday, July 8, 2009 8:13:04 AM
Subject: Re: [Opensim-dev] Deprecate OpenSim.Grid.InventoryServer and 
OpenSim.Grid.AssetServer?


B.U.S.T. is Basic Universal Server Technology. The prompt can be 
changed in the configuration file, though, for those without a sense 
of humor. I fully expect things to get renamed before 1.0. On the 
other hand, the server is named OpenSim.Server.exe, no body parts there!

As soon as connectors are available for the other services, it will 
be able to run them. Part of this is getting the old servers out of 
the way, since the new servers use different web protocols and 
keeping compatibility with the old servers will not be possible. At 
this point, the presence of the old servers blocks evolution.

Melanie


Sean Dague wrote:
> Melanie wrote:
>> The CB version we have in trunk is another implementation of similar 
>> concepts. It has some hooks for some features, which were never 
>> implemented, that the new system doesn't have yet, but the modular 
>> system make
 them entirely possible.
>> 
>> At this point, the CB in trunk is stagnant. It's a stripped down 
>> version that is already incompatible with upstream CB and 
>> essentially unmaintained. I doubt anyone uses it and would think it 
>> could also be dropped or moved.
> 
> I'm definitely in favor of getting stuff out of trunk that we think
> isn't getting used at all, eliminates confusion in the code.
> 
> Can we come up with a name better than BUST though, as that doesn't
> really mean anything to me? :)  Unrelated question, is it possible to
> run all the grid services (not just inv & asset) via that 1 process?
> That would simplify things for smaller (< 50 region) grids that probably
> put all those on the same machine anyway.
> 
>     -Sean
> 
> 
> 
>
 ------------------------------------------------------------------------
> 
> _______________________________________________
> Opensim-dev mailing list
> [email protected]
> https://lists.berlios.de/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-dev

-----Inline Attachment Follows-----

_______________________________________________
Opensim-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-dev



      
_______________________________________________
Opensim-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-dev

Reply via email to