"I" == Ian Kaufman ikaufman@eng.ucsd.edu writes:
I> I tried to change the IP, but it wouldn't let me overwrite "172" I> in the initial installer.
Ah, Ok, I didn't remember that. You'll really have to change the number of nodes to change it. E.g. 64 nodes will give you 192.168.xxx, 128 nodes 172.xxx and 512 nodes 10.xxx
I> However, I logged into the console and made the change in the I> interfaces file. I'll see if it carries through. I can always I> reinstall if needed.
That will require some hand-work later on with the risk of causing unnecessary trouble if some things are not changed. Better to reinstall at this stage.
I> On Wed, May 22, 2019 at 2:39 PM Roland Fehrenbacher I> rf@q-leap.de wrote:
>>>>>> "I" == Ian Kaufman ikaufman@eng.ucsd.edu writes:
I> I> Yep, that was it ... the installer didn't like the I> existing sw I> RAID. And using dd I was able to reboot I> from the cli.
I> Good news, glad it worked.
I> I> One feature request ... allow the end user to pick I> their own I> private IP space. I prefer using I> 192.168.X.X as campus here uses I> 172 and 10 around I> campus.
I> You can already choose that freely. The suggested and I> initially displayed private network IP space is just I> determined by the number of compute nodes you select (this I> number is otherwise irrelevant) but can be changed to a I> different one in the 'IP address' field below 'Cluster I> network adapter'. This should also be explained when you I> press F1.
I> Best,
I> Roland