[opensuse-arm] cloud-init for JeOS
Hi, What do you think about adding cloud-init for ARM JeOS images? Currently, configuration way after deploying brand-new JeOS image is always similar to the following: login with root:linux requisites by serial console and do `ip addr` (or directyl ssh if it is possible to guess DHCP address), then create users, deploy ssh keys, disable ssh root login, etc. I think cloud-init could be helpful here to configure users and networking. Initial configuration can be deployed to the board by network using kernel command line options. -- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sun, Jan 26, Matwey V. Kornilov wrote:
Hi,
What do you think about adding cloud-init for ARM JeOS images?
If it is not public cloud: nothing. We tried that in the past, the side effects of cloud-init, if it runs but you do not provide a config for every listed module, are really bad. For MicroOS we are using ignition for that reason now. Thorsten
Currently, configuration way after deploying brand-new JeOS image is always similar to the following: login with root:linux requisites by serial console and do `ip addr` (or directyl ssh if it is possible to guess DHCP address), then create users, deploy ssh keys, disable ssh root login, etc.
I think cloud-init could be helpful here to configure users and networking. Initial configuration can be deployed to the board by network using kernel command line options.
-- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
26.01.2020 14:27, Thorsten Kukuk пишет:
On Sun, Jan 26, Matwey V. Kornilov wrote:
Hi,
What do you think about adding cloud-init for ARM JeOS images?
If it is not public cloud: nothing. We tried that in the past, the side effects of cloud-init, if it runs but you do not provide a config for every listed module, are really bad. For MicroOS we are using ignition for that reason now.
I have never heard about ignition before. But it seems to have the similar purpose as cloud-init.
Thorsten
Currently, configuration way after deploying brand-new JeOS image is always similar to the following: login with root:linux requisites by serial console and do `ip addr` (or directyl ssh if it is possible to guess DHCP address), then create users, deploy ssh keys, disable ssh root login, etc.
I think cloud-init could be helpful here to configure users and networking. Initial configuration can be deployed to the board by network using kernel command line options.
-- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi,
-----Original Message----- From: Matwey V. Kornilov <matwey.kornilov@gmail.com> Sent: 26 January 2020 13:04 To: opensuse-arm@opensuse.org Subject: [opensuse-arm] Re: cloud-init for JeOS
26.01.2020 14:27, Thorsten Kukuk пишет:
On Sun, Jan 26, Matwey V. Kornilov wrote:
Hi,
What do you think about adding cloud-init for ARM JeOS images?
If it is not public cloud: nothing. We tried that in the past, the side effects of cloud-init, if it runs but you do not provide a config for every listed module, are really bad. For MicroOS we are using ignition for that reason now.
I have never heard about ignition before. But it seems to have the similar purpose as cloud-init.
You also have jeos-firstboot or YaST2-firstboot. YaST2-firstboot is pre-installed, just add an empty /var/lib/YaST2/reconfig_system file and reboot to have start it. If you prefer jeos-firstboot, uninstall YaST2-firstboot first, install jeos-fisrtboot and also add an empty /var/lib/YaST2/reconfig_system file and reboot to have start it. If you are over ssh only, install jeos-firstboot, and: * update the script to avoid to loose Ethernet connection: sed -i 's/ip link set down \"\$d\" #/if [ \"eth0\" != \"\$d\" ]; then ip link set down \"\$d\"; fi; #/' /usr/lib/jeos-firstboot * start it manually: /usr/lib/jeos-firstboot And follow the configuration steps. Cheers, Guillaume
Thorsten
Currently, configuration way after deploying brand-new JeOS image is always similar to the following: login with root:linux requisites by serial console and do `ip addr` (or directyl ssh if it is possible to guess DHCP address), then create users, deploy ssh keys, disable ssh root login, etc.
I think cloud-init could be helpful here to configure users and networking. Initial configuration can be deployed to the board by network using kernel command line options.
-- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
participants (3)
-
Guillaume Gardet -
Matwey V. Kornilov -
Thorsten Kukuk