[ceph-users] Re: RBD as a boot image [was: libceph: get_reply osd2 tid 1459933 data 3248128 > preallocated 131072, skipping]

2021-05-17 Thread Markus Kienast
Am Mo., 17. Mai 2021 um 20:28 Uhr schrieb Nico Schottelius < nico.schottel...@ungleich.ch>: > > > Markus Kienast writes: > > > Hi Nico, > > > > we are already doing exactly that: > > > > Loading initrd via iPXE > > which contains the necessary modules and scripts to boot an RBD boot dev. > >

[ceph-users] Re: RBD as a boot image [was: libceph: get_reply osd2 tid 1459933 data 3248128 > preallocated 131072, skipping]

2021-05-17 Thread Nico Schottelius
Markus Kienast writes: > Hi Nico, > > we are already doing exactly that: > > Loading initrd via iPXE > which contains the necessary modules and scripts to boot an RBD boot dev. > Works just fine. Interesting and very good to hear. How do you handle kernel differences (loaded kernel vs.

[ceph-users] Re: RBD as a boot image [was: libceph: get_reply osd2 tid 1459933 data 3248128 > preallocated 131072, skipping]

2021-05-17 Thread Kees Meijs | Nefos
Hi, This is a chicken and egg problem I guess. The boot process (albeit UEFI or BIOS; given x86) should be able to load boot loader code, a Linux kernel and initial RAM disk (although in some cases a kernel alone could be enough). So yes: use PXE to load a Linux kernel and RAM disk. The RAM

[ceph-users] Re: RBD as a boot image [was: libceph: get_reply osd2 tid 1459933 data 3248128 > preallocated 131072, skipping]

2021-05-16 Thread Markus Kienast
Hi Nico, we are already doing exactly that: Loading initrd via iPXE which contains the necessary modules and scripts to boot an RBD boot dev. Works just fine. And Ilya just helped to work out the last show stopper, thanks again for that! We are using a modified LTSP system for this. We have