Step 1: Provision VMs for PCM

 

Page Navigation:

Page Navigation:

 

 


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.

 

We will provision the HySDS component images and then use terraform to deploy them onto cloud vendor-specific IaaS environment.

You should already have provisioned HySDS component instances (mozart, grq, metrics, factotum, and ci) each designated for a particular HySDS component. The suggested minimum CPU and memory requirements for each instance should at least be met (tables below).

Cloud vendor-specific packer scripts can be used to provision the 5 images.

  • packer templates for provisioning AWS images

  • packer templates for provisioning GCP images

Or, if they are not provisioned to you by an administrator, you can provision them yourself using our puppet modules:

  1. mozart - https://github.com/hysds/puppet-mozart

  2. metrics - https://github.com/hysds/puppet-metrics

  3. grq - https://github.com/hysds/puppet-grq

  4. factotum - https://github.com/hysds/puppet-factotum

  5. ci - https://github.com/hysds/puppet-cont_int

  • Recommended 20 GB of attached general purpose storage for each component's root volume

  • The following tables list the CPU and memory requirements for each component instance based on the scope of the HySDS cluster: minimal or optimal:



    • minimal - Uses instance types that cover the bare minimum CPU and memory requirements for running HySDS in a test or development environment such as this user guide, e.g. Hello World and Hello Dataset



    • optimal - Uses instance types that cover the CPU and memory requirements for running HySDS in an operational environment or at large scale (500-8000 verdi worker instances)



  • Ensure that the same SSH keypair is used for all 5 of the instances. You should be able to ssh into any of your instances using the PEM key file of this SSH keypair.

  • You should already have provisioned 2 buckets from a cloud vendor (e.g. AWS S3, Azure Blob, Google Cloud Storage)

Next Step

Now you can install the HySDS framework software layer onto the systems. Step 2: Install HySDS framework on VM instances

 

 


 

Related Articles:

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:

Page Information:

Was this page useful?

Yes No

Contribution History:

Subject Matter Expert:

@Gerald Manipon

Find an Error?

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

@Lan Dang

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