You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SSH key that will be recognized by coreos will be put in the cloud-init file built by plumbery. So remote connection can become as easy as if it was regular operating system setup.
With this approach, the MBR is staying on /dev/sda, that cannot be removed after the setup. Therefore the need to consider the smallest image available.
Any suggestion guys?
The text was updated successfully, but these errors were encountered:
hey bernard. this has already been done. it's on a USB stick on my desk. Come and collect it!
jk. The process is automated, we still need to figure out the best way to 'upload' or 'download' the OVF files into CaaS as part of a deployment process.
it is great news that you have experience in such things. As you have seen the scenario with plumbery woud not be based on an .ova but rather on bare disk install as suggested by the coreos team. thanks in advance for the presentation :-)
It is not so easy to install coreos on top of an existing operating system, and it is not easy to pass the right cloud-config file as well
The use case would be based on following action items:
The SSH key that will be recognized by coreos will be put in the cloud-init file built by plumbery. So remote connection can become as easy as if it was regular operating system setup.
With this approach, the MBR is staying on /dev/sda, that cannot be removed after the setup. Therefore the need to consider the smallest image available.
Any suggestion guys?
The text was updated successfully, but these errors were encountered: