Putting Our Ages On Shards

[Zrax]

Zib:
The server specs look pretty good, but what's really most important for hosting a content server is your upload speed... My server only gets about 384 kbits/s, which is good for some things, but can be *really* slow for hosting lots of new ages for people to download when they first get on Volcano -- especially if multiple people try to get it at the same time . If you don't know your connection speed and you're in the US, Speakeasy has a pretty good and reliable speed test...

Starfyre:
Ok, well I thought I'd ask at least . I'm still looking at various options, but if no better ones come up, I may be able to help you some with the cost of another server... I guess we'll just have to see how it goes...

Robert:
The main idea of Volcano is that it *is* specifically for the UU client and server... The only modifications to the server involve adding the .age and .sdl files, as well as some vault nodes to tell the client it's allowed to use the Volcano code, and the only real modifications to the client is the new age data. Well, and the configurations to tell it where to find said data .

For the public ages, that's completely handled by the Python code (with a little help from the server's plsdb). In some of the unstable Volcano stuff we've done, we've even set the Watcher's Sactuary as a public age like the city, and gotten the hoods set up so that you can use either Bevin or Kirel for your hood, and the two will work interchangeably... So, if what you're asking is if ages like Ahra Pahts can be set public like the city, the answer is yes, with a bit of Python work and some plsdb additions .

EDIT: Oops, see what happens when I wait till I get to work to finish typing my post? Oh well, the post still applies, so I'll leave it

[Robert The Rebuilder]

Fantastic, Zrax! If you don't mind, perhaps you could provide a write-up of the technical details of what a shard owner and player would need to do. If you or someone on the team is writing a Volcano user manual/tutorial, this would suffice. Then we would just reference that document in section 4 of the proposal we send to Cyan.

And sorry for editing out my question! I happened to see a separate thread on that topic, and thought that I should refocus this thread on the drafting of a proposal.

[zib_redlektab]

[quote="Zrax"] Zib:
The server specs look pretty good, but what's really most important for hosting a content server is your upload speed... My server only gets about 384 kbits/s, which is good for some things, but can be *really* slow for hosting lots of new ages for people to download when they first get on Volcano -- especially if multiple people try to get it at the same time . If you don't know your connection speed and you're in the US, Speakeasy has a pretty good and reliable speed test...

[Kedri]

WOHBA! Impressive upload speed!

My dowload was higher though.

[Tsar Hoikas]

I'm thinking that it would be best if there was a AgeBuilder/Volcano commitee for dataserver integration and changes to Cyan's python code. Members of this commitee would need to be very python fluent and know the Plasma Python API better than the back of their hand. Things like making the Ahra Pahts age public, additions to the Nexus, bookshelf, etc. would be handled by this proposed commitee. Lemme know what you think!

[Robert The Rebuilder]

Adam: Yes - I think that such a committee would definitely be needed, once the shard is up. That way, when a modification is proposed, the committee can determine whether it affects the fan-created data or Cyan data. In the case of Cyan data, they would request permission from Cyan for the modification. This would be anything that was beyond what was originally requested for the initial setup of the shard.

I've put together a draft of the UU Shard Proposal that I'm planning on submitting to Cyan. Once I receive feedback from the Volcano group, it will contain the details of configuring the UU shard to support fan-created ages, along with what changes are made to the client.

In the meantime, feel free to make comments/suggestions. I modified my initial post to contain the link to the draft.

[Tsar Hoikas]

That is looking good, perhaps the members of volcano would care to comment on this seeing how it seems that Volcano is going to be how AgeBuilder content is mainly redistributed. Also, I should mention that the current Phase 2 (where we implement new Cyan content), atm only a special non-UU client can be used. I am working on fixing this but am waiting for comments from other Volcano members. Seeing as how Zrax is busy trying to get the Phase 1 stuff ready for release, I am the only person actively working on P2 (and even now, I'm not doing much since I'm trapped in hell aka school). Perhaps soon, we should take nominations to who should be on the proposed "commitee' soon (not atm though). I will of course post some general ideas to keep in mind when nominating someone (when the time comes). As always, I am open for suggestions and you may IM me with any questions or comments whenever you please (which is why my IM addies are public).

/me awaits comments

[Kedri]

Don't look at me! I'm just a beta tester! :unsure:

Ask ShadowDude.


(By the way, I already commented in the thread on TDS forums)

[ShadowDude]

[quote="AdamJohnso"] I am the only person actively working on P2 (and even now, I'm not doing much since I'm trapped in hell aka school).

[Zrax]

Robert: Here's the extra info you need for the Volcano project:

Server Additions:
1) A copy of all custom ages' .age and .sdl files to be added to the existing set.
2) The following additions to the Vault by an admin (e.g. via the Vault Manager): (note, for those that have seen this already, I changed some of the names to be more descriptive)

GlobalInbox folder
... \-- Text Node: [ServerInfo]
......... |-- Chronicle: VolcanoEnabled = 1
......... \-- Chronicle: VolcanoAges = (List of ages available on this shard, separated by spaces)

Client modifications:
1) The dataserver for the client is pointed to the Volcano Dataserver, which contains all of the new ages but no modified Cyan data files.
2) All available fan-made ages, downloaded either from the Dataserver or included in the patch program (depending on what version of the patcher is downloaded and how new the age is).
3) Python\Volcano.pak file containing python modifications for the Relto Bookshelf to enable clients to visit the new ages from the Volcano book
4) Python\VolcanoAges.pak file containing all of the python files for the custom ages together in one file (for simplicity).
5) (incomplete) An extra Age with (currently) one Global PRP file, containing the link panel images for the Volcano book.


The current version of the Volcano Dataserver is also updated to work with the recent data updates from Cyan's data server, so those will not have to be re-downloaded or replaced.


On another note, about the shards: I never meant to imply that AgeBuilders would be the "primary" shard for Volcano or anything... The volcano project is actually fully ready for release right now, save for a few things we need to finish up, and it works just fine on the existing shards too... Volcano isn't really "homed" to any one specific shard, but rather is designed to work on as many shards as are wanting to participate, even with the option of individual shards having different sets of ages available. When I was asking, I was mainly asking about a faster HTTP host for serving the dataserver, and what else the shard does is really up to the shard owner and isn't a direct part of Volcano... Had I known it would stir up so much confusion and stuff, I probably wouldn't have asked publically like I did. However, Starfyre, if you do get a server and want to host the volcano Dataserver, I'd be happy to, at that point, contribute to its cost... I hope this part doesn't come off negatively, because it really isn't meant to -- just to clear some things up before they start getting out of hand.

Thanks!
- Zrax