You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current biocache test infrastructure is only setup for a single server for ala-hub and a single server for biocache-service and a load balancer. It relies on access to the production databases/indexes. This makes it impossible to test any changes to the other components, such as Zookeeper, Solr, Cassandra, Biocache-store and Jenkins.
Issues for this project include:
Create biocache-service test instance. Ansible definition in ansible-inventories as test-bws-b5. Also gave biocache-service instance access to auth.ala.org.au in authorised systems. This currently points at the production cassandra/solr/zookeeper due to lack of budget for setting up those parts of the biocache test infrastructure.
Create ala-hub test instance. Ansible definition in ansible-inventories as test-bhub-b5. Also gave ala-hub instance access to auth.ala.org.au using authorised systems.
Setup biocache-test.ala.org.au/biocache-ws-test.ala.org.au shared load balancer. biocache-test.ala.org.au and biocache-ws-test.ala.org.au point to the same load balancer, with two separate target groups for /ws and /. Unlike production biocache-which has multiple targets, biocache-ws-test queries all go to a single server, so downloads are not sent to a different dedicated server as in production. This would need to be changed to match production if stress tests were part of the accepted requirements for the biocache test infrastructure.
The current biocache test infrastructure is only setup for a single server for
ala-hub
and a single server forbiocache-service
and a load balancer. It relies on access to the production databases/indexes. This makes it impossible to test any changes to the other components, such as Zookeeper, Solr, Cassandra, Biocache-store and Jenkins.Issues for this project include:
test-bws-b5
. Also gave biocache-service instance access to auth.ala.org.au in authorised systems. This currently points at the production cassandra/solr/zookeeper due to lack of budget for setting up those parts of the biocache test infrastructure.test-bhub-b5
. Also gave ala-hub instance access to auth.ala.org.au using authorised systems.biocache-test.ala.org.au
andbiocache-ws-test.ala.org.au
point to the same load balancer, with two separate target groups for/ws
and/
. Unlike production biocache-which has multiple targets, biocache-ws-test queries all go to a single server, so downloads are not sent to a different dedicated server as in production. This would need to be changed to match production if stress tests were part of the accepted requirements for the biocache test infrastructure.Data load related issues are currently being debugged in production in the absence of this infrastructure being available.
The text was updated successfully, but these errors were encountered: