• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 211
  • Last Modified:

Implementing Rocks Linux with public IPs possible?

I'm pretty new to the IT world as far as the heavy duty stuff goes...so scrolling through the vast pages of EE (just registered yesterday) has been pretty overwhelming for me.  Continue to keep this in mind while you answer please :)

I've recently started a research position as a SysAdmin for a cluster of machines running Linux here at my university.  Our goal is to try to automate the kickstart process as much as possible as well as have some way to monitor all the machines effectively.  After a bit of research I figure Rocks Linux (www.rocksclusters.org) might be a good way to go, seeing as how it's based from Redhat which wouldn't change much of our implementation.  However to my dismay, but team leader explains that we won't be able to use it since our machines have public IPs as opposed to a private network connected through a frontend to the internet.

I'm a "little" familar with what he said, but is this true?   Do you absolutely need to have private IPs to implement such a thing, in which case we'd have to revamp our entire network infrastructure (highly unlikely).  If so, is there some other solution we could look into?  I know Ganglia is something Univ. of California - Berkely is working with, and that's now implemented into the Rocks kernel, but how about using it standalone?

Any suggestions about the automation of the kickstart process, or even large-scale node monitoring would be highly helpful.
1 Solution
I'm not that familiar with Rocks, but I seriously doubt that it won't work over public IP addresses.

On the other hand, you definitely want to make sure that the network traffic it sends is secure, so maybe your team leader was thinking more about private networks from this sense...

You should sign up for the "Rocks discussion list" (https://lists.sdsc.edu/mailman/listinfo.cgi/npaci-rocks-discussion) and ask your question there.
NubsicleAuthor Commented:
I believe my team leader mentioned something about having to establish each node as a frontend, which undoubtedly takes away from the idea since each frontend would be monitoring itself - making us have to monitor each frontend...

Thank you for your answer though.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

A proven path to a career in data science

At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science  with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now