Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Hi and thanks for the questions.

1 ) Currently, the minimum number of nodes is 3x t2.xlarge instances or equivalent sized node (4 vcpu, 16gb mem per node). We are working to slim this down a bit to get everything to fit on 2 t2.xlarge instances.

2 ) 3 t2.xlarge or equivalent.

3 ) Ephemeral storage per node could prob be less than 80GB but I would stick with this.

4 ) The defaults should work fine, but if you are running a very large analysis, or this is a long running cluster you can increase these depending on how much data is being written to the volume.

As for your question about switching to t4g.xlarge, I don't see that as problem as far as helm/k8s is concerned, but I would make sure this is node instance type is compatible with EKS in AWS. If you post the AWS error I'd be happy tp help where I can. I am assuming that this is AWS related problem and not with the server-helm chart.