all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
|||||||||
|
|||||||||
|
|
|
Notes:
|
|
-When going to the platform level… Make sure and keep users greater than corporations or worlds. This may require a master user list on the admin adilas world. Each user needs to be tied to a home planet or world. -It might be funny to treat users as if they were space or cloud travelers. They need a home base or home planet. They could also gain virtual passports or visas to go and visit or work on other worlds. Once again, keep and/or make users be bigger than corporations or worlds. -I am thinking for this first round of splitting up the adilas system, that we need to move off all traffic from the main adilas.biz server. My initial cluster will be the main adilas.biz server, D1 (data one), D2 (data two) and MC1 (media/content one). -So in other words… Cluster 1 (cluster one) will have three (or more) data servers and one content server. It will look like this: (see sketch in photo gallery) o CL1 = Cluster one o MC1 = Media/content one o D1 = Data one o D2 = Data two o D3 = Data three o Main adilas = special mother ship data server -As an additional note… The different pieces could also have an alias or nickname. We could use either the cryptic names or the alias names. Treat it like a neighborhood or town. Cryptic might be “1200 North 200 East”, the alias may be “Hill Haven” or “Ranch of the Rockies” or something like that. Think physical address or general subdivision (area). -If we allow world traveling… do we want to monitor who goes where? Is this shown, searchable, or hidden? -Plan that many businesses may end up being interconnected and/or related in one way or another. Set it up so that the different worlds can view who has access to what and what has been done. Take adilas out of the picture… Let world “A: do business with world “T” without having to ask the adilas world if that is okay. Think of easy interchange options like Legos or different building blocks. If you make some standard connections, virtually anything could be bolted on, snapped on, or used as an add-on piece. -Small note about platform and space… We draw clusters as if they live right next to each other. In real life, we could use virtually any configuration. Think in all different directions (space). As I think about this… the only real cluster is actually the data boxes or data servers. Those are a single physical box or computer server. The thing that make a “cluster” is which data servers are tied to which media/content servers. So maybe, we need to say “data clusters” and “media/content clusters”. Anyway, just trying to figure out some naming conventions. -Trying to figure out the general structure and what to call things…. Internet – Web or Cloud Level Adilas – Universe Level Media/Content Server Clusters Data Server Clusters Database(s) Level (at least one is required) Corporation(s) Level – world level Location(s) Level – geographic areas or virtual areas Sub Classifications – optional Departments – optional -Working on the structure of how to organize the adilas worlds. This is a semi expanded list. This could be expanded to super techy levels. (See sketch in photo gallery) 1. Internet – Web – Cloud – Beyond??? 2. Adilas Admin Level – Universe Level 3. Media/Content Server Cluster – optional and light relationship 4. Domain – Data Server Cluster – Independent piece – Requires an SSL, domain name, a box or a server. This is the start of the data server cluster or DSL. App server. 5. Databases – At least one but possible to have many on the same data or app server. 6. Corporations – World Level – At least two per database. One as a dummy and one as real value. There may also be a controller corporation per database (depending). 7. Locations – Areas – way of divvying up a corporation. At least one location per corporation is required. 8. Sub Locations – Optional sub category of the locations. This piece is not yet done. 9. System Player Groups – 12 main groups. Most of these may be tied to allocation. Some exist outside of the location scope but still under the corp or corporation scope. 10. Departments – optional sub under users. |