Mantis Bug Tracker

View Revisions: Issue #8217 All Revisions ] Back to Issue ]
Summary 0008217: Add functionality to handle Estates through Regions.ini
Revision 2017-07-26 21:46 by tampa
Description OpenSim out of the box does not provide a solution to pre-configure estates other than DefaultEstate in OpenSim.ini or direct SQL. Especially for multiple regions per instance user-interaction is required. This results in the need for dealing with the console, which scares some users for fear or bricking their installation.

Proposal:

Add EstateID line to Regions.ini for local or remote estates to link individual regions to.

If EstateID is not supplied, but EstateName, EstateOwnerFirstName and EstateOwnerLastName is supplied create the estate locally or remotely and link the region to it.

If neither is supplied or the supplied configuration mismatches the entries in the estate_settings and estate_map either local or remote, give an error and default to user interaction to resolve the conflict. Same goes if the remote estate cannot be created for some reason.

Alternatively if DefaultEstate is set the regions with conflicts could default to that instead.

This functionality should not disrupt any estate handling already present, it merely would allow the pre-configuration of standalones and simulators before initial startup. Removing the need for user-interaction out of the box.

With local and remote I mean either the simulators or standalones own database and remote for grid-managed estates using the remoteestate connector.

Example:

[My Region]
RegionUUID = 0521b16d-165e-4873-90d4-80127508868b
EstateID = 102
[Other Region]
RegionUUID = 67564553-e9f1-4bdd-beb4-a3bc135bbf19
EstateID = 104
[Nother Region]
RegionUUID = 56103720-6c9a-43a2-9873-5d18acfd28fd
EstateName = Mine
EstateOwnerFirstName = Test
EstateOwnerLastName = Resident
Revision 2017-07-26 21:42 by tampa
Description OpenSim out of the box does not provide a solution to pre-configure estates other than DefaultEstate in OpenSim.ini or direct SQL. Especially for multiple regions per instance user-interaction is required. This results in the need for dealing with the console, which scares some users for fear or bricking their installation.

Proposal:

Add EstateID line to Regions.ini for local or remote estates to link individual regions to.

If EstateID is not supplied, but EstateName, EstateOwnerFirstName and EstateOwnerLastName is supplied create the estate locally or remotely and link the region to it.

If neither is supplied or the supplied configuration mismatches the entries in the estate_settings and estate_map either local or remote, give an error and default to user interaction to resolve the conflict. Same goes if the remote estate cannot be created for some reason.

Alternatively if DefaultEstate is set the regions with conflicts could default to that instead.

This functionality should not disrupt any estate handling already present, it merely would allow the pre-configuration of standalones and simulators before initial startup. Removing the need for user-interaction out of the box.

With local and remote I mean either the simulators or standalones own database and remote for grid-managed estates using the remoteestate connector.

Example:

[My Region]
RegionUUID = 0521b16d-165e-4873-90d4-80127508868b
EstateID = 100
[Other Region]
RegionUUID = 67564553-e9f1-4bdd-beb4-a3bc135bbf19
EstateID = 104
[Nother Region]
RegionUUID = 56103720-6c9a-43a2-9873-5d18acfd28fd
EstateName = Mine
EstateOwnerFirstName = Test
EstateOwnerLastName = Resident


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker