Hey Sajesh, Each public cloud vendor provides a standard way to create a virtual private network in their infrastructure and connect that private network to your existing private network for your cluster. The devil is in the networking details.
So in that case, you can just treat it as a new rack of nodes that just happens to be at the far end of whatever your network link is. E.g. if you have a 1Gbps VPN into your AWS network, that's your bottleneck. It may be sufficient for some workloads. Or you can have a separate fileserver there... lots of options. Regards, Alex On Tue, Dec 15, 2020 at 12:05 PM Sajesh Singh <ssi...@amnh.org> wrote: > We are currently investigating the use of the cloud scheduling features > within an on-site Slurm installation and was wondering if anyone had any > experiences that they wish to share of trying to use this feature. In > particular I am interested to know: > > > > https://slurm.schedmd.com/elastic_computing.html > > > > 1) Recommendations for staging the data that was needed by the nodes in > cloud > > 2) How did you handle name resolution > > 3) Any resources/documentation in particular that proved helpful while > setting up the environment > > 4) Any bits of advise or horror stories that may be helpful in avoiding > pitfalls. > > > > > > Regards, > > > > -SS- >
