Re: [opensuse-kubic] root login on Hyper-V image*s* of MicroOS KO
Hi, On Thu, Feb 28, Jimmy PIERRE wrote:
On Thu, 28 Feb 2019 at 12:51, Thorsten Kukuk <kukuk@suse.de> wrote:
That's described on the Kubic:Installation page: https://en.opensuse.org/Kubic:Installation# Images_for_x86_64_virtualisation_environments
You need to set a password or add your ssh keys with cloud-init. An example cloud-init config file can be found here: https://en.opensuse.org/Kubic:MicroOS/cloud-init# Example_configuration_for_openSUSE_Micro
Thanks for stepping in! I undersrand. If I create my own vm with the iso, is there a reason why the images would be better (size, tuning, updates etc.)?
If you create install your virtual machine or bare metal hardware with YaST, you are more flexible what and how to install and you don't need to fiddle around with cloud-init to be able to login. If you use the images, they are preconfigured, so faster to deploy, but you are less flexible and you need to play with cloud-init. If you use KVM or VMware, it shouldn't matter what you use, but since cloud-init is really slow, I would install with YaST and not install cloud-init. On OpenStack I would use the image.
And the documentation to survive do exist please?
Which documentation are you missing? There is the Kubic portal in the openSUSE wiki and were you can find many documentation (only look at the above examples), enough to setup a kubernetes cluster at your own. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org
-----Original Message----- From: Thorsten Kukuk [mailto:kukuk@suse.de] Sent: 01 March 2019 09:23 To: opensuse-kubic@opensuse.org Subject: Re: [opensuse-kubic] root login on Hyper-V image*s* of MicroOS KO Hi, On Thu, Feb 28, Jimmy PIERRE wrote:
On Thu, 28 Feb 2019 at 12:51, Thorsten Kukuk <kukuk@suse.de> wrote:
That's described on the Kubic:Installation page: https://en.opensuse.org/Kubic:Installation# Images_for_x86_64_virtualisation_environments
You need to set a password or add your ssh keys with cloud-init. An example cloud-init config file can be found here: https://en.opensuse.org/Kubic:MicroOS/cloud-init# Example_configuration_for_openSUSE_Micro
Thanks for stepping in! I undersrand. If I create my own vm with the iso, is there a reason why the images would be better (size, tuning, updates etc.)?
If you create install your virtual machine or bare metal hardware with YaST, you are more flexible what and how to install and you don't need to fiddle around with cloud-init to be able to login. If you use the images, they are preconfigured, so faster to deploy, but you are less flexible and you need to play with cloud-init. If you use KVM or VMware, it shouldn't matter what you use, but since cloud-init is really slow, I would install with YaST and not install cloud-init. On OpenStack I would use the image.
And the documentation to survive do exist please?
Which documentation are you missing? There is the Kubic portal in the openSUSE wiki and were you can find many documentation (only look at the above examples), enough to setup a kubernetes cluster at your own. Thorsten Hallo Thorsten, Thanks for this clarification. I figured out last night that I did not want to fiddle and downloaded the iso and launched a Hyper-V machine, where all is fine, installed Lynx for example. Also did transactional-update too. What does the project preconize for frontend management? Last thing, is Linode, DigitalOcean et al going to offer kubic as far as you know? Just to put you in the picture, our montly meeting is 30th March and I am attempting to get a lab together. Cheers, Jimmy nui.fr -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org
On Fri, Mar 01, jimmypierre.rouen.france@gmail.com wrote:
What does the project preconize for frontend management?
What do you want to manage? For kubernetes, I would recommend the kubernetes dashboard. For Kubic, there is not much to manage, updates should be done automatically after setup once, and for kubernetes we have kubeadm.
Last thing, is Linode, DigitalOcean et al going to offer kubic as far as you know?
No, I don't know. But more people asking them means higher chance they will do so. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org
On Fri, 1 Mar 2019 at 10:54, Thorsten Kukuk <kukuk@suse.de> wrote:
On Fri, Mar 01, jimmypierre.rouen.france@gmail.com wrote:
What does the project preconize for frontend management?
What do you want to manage? For kubernetes, I would recommend the kubernetes dashboard. For Kubic, there is not much to manage, updates should be done automatically after setup once, and for kubernetes we have kubeadm.
Last thing, is Linode, DigitalOcean et al going to offer kubic as far as you know?
No, I don't know. But more people asking them means higher chance they will do so.
Hetzner already offer Kubic in their ISO library -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org
participants (3)
-
jimmypierre.rouen.france@gmail.com
-
Richard Brown
-
Thorsten Kukuk