Agenda

  • Project updates

WhoPlan for the week (Monday)Accomplished (Friday)

Jing Ge (KnowEng)

  • Continue working on building two docker images for two pipelines separately.
  • Create automatic build for docker images
  • Start working on data cleaning pipeline
    • Create repository
    • Merge code and refactor code
    • Adding unit tests
    • Create build related files
  • Finished building two docker images for two pipelines and they have been tested by several people.
  • Finished creating an example automated build for docker images whenever there is changes from github repository.

Rob Kooper (TERRA)

  • Rob
    • migrate vm
  • Max
    • cleanup database
  • Yan++
    • extract lat/lon insert into clowder database
 

Sara Lambert

Development:

  • NDS-245 - Getting issue details... STATUS
  • NDS-478 - Getting issue details... STATUS
  • NDS-467 - Getting issue details... STATUS
  • NDS-443 - Getting issue details... STATUS
  • NDS-456 - Getting issue details... STATUS
  • NDS-488 - Getting issue details... STATUS
  • NDS-475 - Getting issue details... STATUS
  • NDS-469 - Getting issue details... STATUS
  • NDS-480 - Getting issue details... STATUS

Discussion:

  • NDS-325 - Getting issue details... STATUS

Review:

  • NDS-454 - Getting issue details... STATUS
    • NDS-487 - Getting issue details... STATUS
  • NDS-459 - Getting issue details... STATUS
  • NDS-308 - Getting issue details... STATUS
  • NDS-488: 503 error when starting Cloud Commander - Resolved
  • NDS-480: RStudio service - Resolved
  • NDS-479: Girder service - Resolved
  • NDS-475: FileManager breaks "helper-text" on NDS Labs Dashboard - Resolved
  • NDS-473: Add support email to inventory - In Review
  • NDS-469: Odd capitalization on account name header - Resolved
  • NDS-461: Ingress returns 404 if service name too long - In Review
  • NDS-456: UI only displays endpoint link if NodePort present - Closed
  • NDS-443: Revisit stack vs standalone - Resolved
  • NDS-437: Review and finalize official specs - In Review
  • NDS-430: Enable authentication on stack - Resolved
  • NDS-428: Fedora Commons service - Resolved
  • NDS-337: Unopinionated Java Developer Environment - In Progress
  • NDS-325: Review LaTiS Pull Request - In Progress
  • NDS-296: Create a set of kube-system ingress rules for accessing cluster LMA tools - Closed
  • NDS-245: UI does not indicate when it is loading data - Resolved
  • NDS-191: Define multinode cluster requirements - Closed
  • NDS-183: User should be able to provide feedback for NDS Labs - In Review
Kenton McHenry
  • TAC meeting
  • NDS Report followup
  • NDSC community engaginment/announcments
  • TAC meeting
  • NDS Report followup
  • Mailing list cleanup
  • EZID follow up

Michal Ondrejcek (MDF)

  • continue with an e-mail and print template with MDF description, data ingestion, screenshots
  • contact faculty on the NDS/MDF list
  • working on handout template, data ingestion done, screenshots done

David Raila (Psi TerraFusion)

  • resolve gluster bug, harden and stress/perf test it - critical to beta
  • PSi - integrate with matt/kacpers jupyter, assist with RPC support for integration
  • TerraFusion - Duplicate Guangyu's HDF experiments on roger and BW, evaluate the code and make techincal notes
  • NDS-395: Starting Mongo with GFS quota enabled crashes GFS - In Progress
  • NDS-343: Implement local docker hub cache in-cluster - In Progress
  • NDS-262: Stress-testing on prototype GlusterFS - In Progress

Kandace Turner

  • Out of the office Monday-Wednesday at XSEDE Quarterly
  • Continue working on NDSC6
  • Continue planning for Christine's visit
 

Craig Willis (TERRA)

 
  • NDS-490: Ability to submit feedback through API Server - Closed
  • NDS-489: Add ndslabsctl to API server build - Closed
  • NDS-487: Permission errors with Jupyter images - Closed
  • NDS-486: Confirm that we can customize services by mapping data volumes - Closed
  • NDS-474: Server ambiguity in approval e-mails - In Review
  • NDS-471: Create preliminary demo video of beta NDS Labs - In Review
  • NDS-467: Account Approval Feedback - Resolved
  • NDS-459: Vocabulary/semantic services - Closed
  • NDS-454: Jupyter Services - Closed
  • NDS-453: Create new tags for system components - Closed
  • NDS-439: API server/spec should support running "privileged" services - Closed
  • NDS-435: API server images should have policy "always pull" - Closed
  • NDS-434: User can SSH tunnel to access TCP services - Closed
  • NDS-431: Make Docker image paths/tags configurable in ansible - Closed
  • NDS-424: DSpace service - In Progress
  • NDS-423: API server should generate Kubernetes volume names - Closed
  • NDS-417: Add timeout for services that are never ready - In Progress
  • NDS-416: Add NDSLABS_HOME env var to containers - Closed
  • NDS-410: Setup security review meeting - Closed
  • NDS-408: Prototype letsencrypt support for ingress rules - Closed
  • NDS-407: Request wildcard cert for test cluster - Closed
  • NDS-403: Get Nebula team to configure NDSLabs and NDSLabsDev projects - Closed
  • NDS-402: Service enters error state and refuses to provide logs containing the reason - Closed
  • NDS-396: Swagger spec missing new tags endpoint - Closed
  • NDS-394: Editing a stack's label while it is running causes desynchronized state - Closed
  • NDS-384: API server should start K8s service during add not start/stop - Closed
  • NDS-381: Update NDS Labs documentation, images, repos for pilots - Closed
  • NDS-380: SharedConfig no longer makes sense with new Dashboard - Closed
  • NDS-374: Opinionated Python extractor development environment - Closed
  • NDS-371: API server throws HTTP 500 when deleting spec via CLI from system catalog - Closed
  • NDS-367: Revisit Eclipse Che - Closed
  • NDS-356: API server should support personal catalog - Closed
  • NDS-351: End-to-end Docker build/tag/push prototype - Job/Pod - Closed
  • NDS-350: User's home directory is mounted in containers - Closed
  • NDS-340: Unopinionated Go Developer Environment - Closed
  • NDS-338: Unopinionated PHP Developer Environment - Closed
  • NDS-336: Vocabulary for service labels/tags - Closed
  • NDS-335: Service spec changes - Closed
  • NDS-317: Stack service resource limit defaults are too high - In Progress
  • NDS-315: API server missing volume configuration - Closed
  • NDS-314: Add default resource limits - API - Closed
  • NDS-308: User is prompted to authenticate when accessing their services - Closed
  • NDS-292: iRODS federate service can't have two servers registered with the same zone - Closed
  • NDS-288: Stack name collisions cause stacks to move when auto refresh is enabled - Closed
  • NDS-287: Stacks disappear after clicking launch - Closed
  • NDS-274: Dataverse does not index in Solr - Closed
  • NDS-271: On-site verification at IASSIST - Closed
  • NDS-270: Multinode preview install for IASSIST workshop - Closed
  • NDS-269: Add Kubernetes resource status information to "logs" - Closed
  • NDS-267: Add load balancer deployment to ansible provisioning scripts - Closed
  • No labels