To leverage the community's help in developing code for the indexer's back-end and front-end, GCentral needs to identify and document how and where the different parts of the infrastructure are to be implemented.
For example:
Is the indexer meant to run on a single authoritative server (GCentral) or should it also run be able to run on mirrored public servers or even private servers? If distributed, what is the replication strategy envisioned?
What is the Geographic server load balancing strategy?
Where are the packages stored and what is the access priority? For example, should the database point to a single package stored on GCentral's server or should it point to an array of locations including the original source, GCentral's store and other mirror sites?
What is the configuration management backbone and how is it implemented? There will be one or more databases used to store packages info, user accounts, package statistics, etc. What does the API look like to access this information? Which information is publicly available (packages info, package stats, etc.), which info is private (user accounts, internal configs).
To leverage the community's help in developing code for the indexer's back-end and front-end, GCentral needs to identify and document how and where the different parts of the infrastructure are to be implemented.
For example:
Is the indexer meant to run on a single authoritative server (GCentral) or should it also run be able to run on mirrored public servers or even private servers? If distributed, what is the replication strategy envisioned?
What is the Geographic server load balancing strategy?
Where are the packages stored and what is the access priority? For example, should the database point to a single package stored on GCentral's server or should it point to an array of locations including the original source, GCentral's store and other mirror sites?
What is the configuration management backbone and how is it implemented? There will be one or more databases used to store packages info, user accounts, package statistics, etc. What does the API look like to access this information? Which information is publicly available (packages info, package stats, etc.), which info is private (user accounts, internal configs).