Hey,

Actually concerning getting a SSH daemon running on systems while 
running was quite easy... (This comes in very handy for us with systems 
that don't have remote console access or local access... handy way to 
diagnose issues with the imaging if they fail as si_monitor can only do 
that.. monitor. Would be cool to have this in the Virtual Console)

Here's what I've done, I've extracted the 
/usr/share/systemimager/boot/i386/standard/boel_binaries.tar.gz file and 
made some of my own modifications and anybody could do the same if they 
desire the same functionality... After modifying the contents, I just 
compress it back up and replace it in that directory.

this is required to start sshd:

mkdir var/empty

this is required to connect as root user.. password is welcome - can 
always use your own existing shadow file with your own credentials:

echo "root:$1$BaJP0SOv$452iJT862e01qxXzTlR5m0:13530:0:99999:7:::" > 
etc/shadow

the next thing I did was copy my existing rsa and dsa keys from our 
environment in the etc/ssh directory. You could create your own with 
ssh-keygen if you don't have your own. I also modified my sshd_config 
conf file in etc/ssh as well to my environment.

cp ssh_host_dsa_key | cp ssh_host_rsa_key | cp ssh_host_key and make 
sure permissions are 0600

Next I've edited my master files under /var/lib/systemimager/scripts and 
the template file under /etc/systemimager/ - the autoinstallscript.template

The very first thing I've done, even before ". /tmp/variables.txt" is 
add these lines:

# Start SSHD
/bin/mount /dev/pts
/sbin/sshd

And that's it... since my hosts are assigned IP's from DHCPD STATICALLY, 
I can then just ssh into the hostname of the system that is being 
reimaged. I guess that this is something fairly simple to integrate into 
the systemimager suite if you so choose (as a option or whatnot) .. let 
me know if I can assist any further.

Jason

Andrea Righi wrote:
> Jason Knudsen wrote:
>   
>> That's fantastic news!!!
>>
>> Thanks to everyone who has made this possible!
>>
>> So what exactly does si_psh do? is it a method to connect to the console 
>> of systems that are reimaging?
>>
>>     
>
> No, it's a simple distributed shell (a wrapper to ssh) to run a command
> on ranges or lists of nodes, _after_ they've been installed. For the
> future we could consider to start sshd on the imaging clients (this
> should be a point of the TODO list). In this case you'll be able to use
> si_psh also to run commands on the imaging nodes... at the moment the
> only way to see the remote console of the nodes while they are
> installing it's the virtual console in si_monitortk...
>
> Regards,
> -Andrea
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sisuite-users mailing list
> Sisuite-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sisuite-users
>
>   


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to