Page History

...

• Gluster services under Kubernetes (in labeled data nodes)
  • Volume declarations, automation, and operational integration
  • Startup, provisioning in IAAS, initialization, and operations/mgmt
  • Related ticket: 

    Jira
    server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-223

• Ability to assign quotas to project directories
  • Option 1: Manual process with documentation
  • Option 2: Ability to call some Pod
  • Related tickets

    • Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-210

• Container to mount Gluster volumes on nodes

  • Jira
    server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-227

  • Yaml to create daemon set to mount volumes
  • Run on each compute node
  • Testing
• Unified Ansible Deployment scripts
  • Openstack and kubernetes with NDSLabs reproducible deploy
    • Add OpenStack provisioning playbook/roles
      • currently lives in ndslabs-deploy-tools?

    • Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-235

  • GlusterFS

    • Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-209

    • Jira
      server JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-237

  • Jira
    server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-236

  • System boot process:
    
    • Add systems-level services - monitoring, admin-tools, introspection tools ... cadvisor, 

    • Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-238

  • Related ticket:

    • Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-191

    • Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-209

• Resource limits
  • Project spec, resource quotas, service spec

    • Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-202

    • Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-205

    • Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-204

  • Optional: UI 

    • Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-207

    • Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-197

• Test multinode with realistic Dataverse deploy
  
  • OOM, High CPU process testing
  • Understand dataverse resource requirements, update specs
• Cluster admin tools for monitoring
• Console access

  • Jira
    server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-174

  • Jira
    server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-175

• Load balancer

  • Jira
    server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-234

  • TLS
• New: TLS HTTPS/WSS support in UI and Apiserver
• Feedback

  • Jira
    server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-183

Cluster boot sequence:

1. 1. Decide on cluster size. How many of each type of node?
      • kubernetes etcd
      • kubernetes master
      • kubernetes compute
      • kubernetes ingress
      • gluster storage
Allocate desired OpenStack instances / volumes

2. 1. Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-243

       - Allocate desired nodes with Ansible playbook.
Instances (which are now Kubernetes nodes)
3. 1. Nodes should now be online with Kubernetes running.
   2. Label all nodes with their associated role/type from above
      • kubectl label nodes <nodeName> ndslabs-role=<nodeType>

   3. Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-223

       - Deploy GlusterFS server Kubernetes service on nodes with ndslabs-role=storage

   4. Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-223

       - Deploy GlusterFS client Kubernetes service on nodes with ndslabs-role=compute

   5. Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-214

       - Deploy "default" Kubernetes LoadBalancer / Ingress rules for UI / API / cluster-wide services (i.e. TERRA toolserver)

   6. Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-244

       - Deploy kube-system Kubernetes services
      • Grafana, dashboard, ELK, etc

   7. Jira
      server JIRA serverId b14d4ad9-eb00-3a94-88ac-a843fb6fa1ca key NDS-238

       - Depoy NDS Labs Kubernetes services
      • UI / API
      • TERRA toolserver?
   8. Create any necessary NDS Labs projects using the API
      • Do we need a script to create these in bulk?
      • Each project needs:
        • Public IP / CNAME
        • Kubernetes Namespace
        • Kubernetes LoadBalancer
        • Kubernetes Ingress ruleset

2016-04-29

Completed?:

• Console Access

...