Change Details

We'll be launching three net-new services, `wdqs-main-graph`, `wdqs-full-graph` and `wdqs-scholarly-articles` (real names TBD). Each service will be served on a single host respectively, and thus we probably don't need LVS/pybal. Servers are already available. Data load isn't part of this ticket. We will need additional static web sites for the UI, with their configuration. AC [] Talk to Traffic team and come up with a concrete list of steps to get these services ready from a routing point of view [] deploy UI for each endpoints [] SPARQL endpoints and UI are accessible to the internet

We'll be launching three net-new services, `wdqs-main-graph`, `wdqs-full-graph` and `wdqs-scholarly-articles` (real names TBD). Each service will be served on a single host respectively, and thus we probably don't need LVS/pybal. Servers are already available. Data load isn't part of this ticket. We will need additional static web sites for the UI, with their configuration. AC [x] Talk to Traffic team and come up with a concrete list of steps to get these services ready from a routing point of view [x] deploy UI for each endpoints [x] SPARQL endpoints and UI are accessible to the internet

We'll be launching three net-new services, `wdqs-main-graph`, `wdqs-full-graph` and `wdqs-scholarly-articles` (real names TBD). Each service will be served on a single host respectively, and thus we probably don't need LVS/pybal. Servers are already available. Data load isn't part of this ticket. We will need additional static web sites for the UI, with their configuration. AC [x] Talk to Traffic team and come up with a concrete list of steps to get these services ready from a routing point of view [x] deploy UI for each endpoints [x] SPARQL endpoints and UI are accessible to the internet