Fragalysis Stack (Kubernetes)
latest

Preparation

  • Installation

Architecture and development process

  • Development Architecture
  • Development Processes

Administration

  • Administration
    • Cloud Provider (STFC)
    • The Rancher Server
    • The NFS Servers
    • AWX (Adding Developers)
    • Related Repositories
      • Informatics Matters Repositories
      • XChem Repositories
      • 3rd Party Repositories
Fragalysis Stack (Kubernetes)
  • Docs »
  • Administration »
  • Related Repositories
  • Edit on GitHub

Related Repositories¶

A list of repositories related to Fragalysis and its deployment and management on Kubernetes.

Informatics Matters Repositories¶

Repositories hosted on the Informatics Matters GitHub account.

  • ansible-infrastructure
  • ansible-role-awx-composer
  • ansible-role-cert-manager
  • ansible-role-infrastructure-data
  • ansible-role-infrastructure-user
  • bandr
  • dls-fragalysis-stack-kubernetes
  • docker-neo4j
  • docker-neo4j-ansible
  • docker-volume-replicator
  • trigger-awx
  • trigger-travis

The following repositories are employed to generate neo4j-compliant fragmentation data: -

  • fragmentor

Cluster formation (using STFC OpenStack) resources are managed by the following repositories: -

  • ansible-bastion
  • ansible-galaxy-cloud [1]

XChem Repositories¶

Repositories hosted on the XChem GitHub account.

  • fragalysis
  • fragalysis-backend
  • fragalysis-frontend
  • fragalysis-loader
  • fragalysis-stack

3rd Party Repositories¶

Repositories hosted on GitHub that we rely on but have little or no control over: -

  • kubernetes/ingress-nginx

Footnotes

[1]This repository creates a Nextflow/Slurm/Munge/Pulsar cluster that can be used but it was not employed to create the existing Galaxy/Condor cluster, which created independently of our tools.
Previous

© Copyright 2020, Informatics Matters Ltd Revision ac3062bc.

Built with Sphinx using a theme provided by Read the Docs.