Hey All,
I finally got this working, it was a bit tricky getting sshd to stay open
and allow connections in the Ubuntu preseed environment. Here is what
worked for me;
d-i preseed/late_command string in-target wget
http://$http_server/xenial-sources.list
-O /etc/apt/sources.list ; \
mkdir -p
Hello,
Thank you for the replies! I tried to replicate your setup with the
following;
[root@cobbler ~]# cat /var/lib/cobbler/triggers/install/post/chef-key.sh
#!/bin/bash
/usr/bin/scp -i /root/.ssh/id_rsa -o "StrictHostKeyChecking no" -p
/root/chef.key ${3}:/root/chef.key
Using Ubuntu 16.04
On 10/25/2016 09:49 PM, Tyler Wilson wrote:
Hey All,
New Cobbler user here. What is the best method of ensuring deployed
nodes have sensitive keys (chef keys, ssh, etc) securely uploaded when
completed? Am I able to send them securely from the cobbler host somehow?
Thanks for any and all tips!
Look into koan, --template-files and --update-files
Http://fedorahosted.org/cobbler/wiki//BuiltinConfigManagement
On Oct 25, 2016 10:50 PM, "Tyler Wilson" wrote:
> Hey All,
>
> New Cobbler user here. What is the best method of ensuring deployed nodes
> have sensitive keys
Hi Tyler,
In your kickstart file, create a post install step that set up a management
account called chef and also upload chef ssh authorization key
You can then push any sensitives file to the deployed system using ssh tunnel
between chef and system x at account chef
Regards,
William
From: