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: [email protected] > To contact the owner, e-mail: [email protected] -- 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: [email protected] To contact the owner, e-mail: [email protected]
