Verdi Proxy Access

Confidence Level TBD  This article has not been reviewed for accuracy, timeliness, or completeness. Check that this information is valid before acting on it.

Confidence Level TBD  This article has not been reviewed for accuracy, timeliness, or completeness. Check that this information is valid before acting on it.


Intro

With recent cybersecurity requirements, Verdi compute nodes are locked down in private VPC/Security Groups. WebDAV from the verdi compute nodes are no longer accessible from operations teams. This establishes proxy to enable operators to access each compute node’s WebDAV service regardless if verdi is on private or internal VPC/SG.

Assumptions

  • Webdav into compute nodes is done for ops only and we do not need large-scalability with this feature

  • Would be ok to proxy via factotum

 

Use Cases

  • Baseline: WebDAV link to compute node on JPLnet

  • WebDAV proxying to private VPC (10.0.x.x)

  • WebDAV proxying into Pleiades

    • Defer for later

    • May require double proxying

 

Requirements

  • Proxy HTTP to browse html view (index-style CSS) served out of each verdi compute node

  •  

Desirements

  • Proxy WebDAV protocol  (extension beyond HTTP) → mount WebDAV over proxy onto compute node

Approaches (sorted in complexity involved)

User’s Guide

Developers Guide

Implementation Notes

References

 


Related Articles:

Have Questions? Ask a HySDS Developer:

Anyone can join our public Slack channel to learn more about HySDS. JPL employees can join #HySDS-Community

JPLers can also ask HySDS questions at Stack Overflow Enterprise

Search HySDS Wiki

Page Information:

Was this page useful?

Yes No

Contribution History:

Subject Matter Expert:

@Hook Hua

Find an Error?

Is this document outdated or inaccurate? Please contact the assigned Page Maintainer:

@Hook Hua

Note: JPL employees can also get answers to HySDS questions at Stack Overflow Enterprise: