IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 4 September 2021 (all times are UTC)
| 00:07 | <vagrantc> hah!
| |
| 00:07 | kernel /path/to/vmlinuz initrd=initrd.img worked instead of passing the path in initrd= argument... wow.
| |
| 00:07 | nothing confusing about specifing the initrd twice in two different ways :)
| |
| 01:14 | thanks for rubber ducking everyone :)
| |
| 01:14 | * vagrantc waves | |
| 01:14 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b, Quit: leaving) | |
| 05:15 | <alkisg> Morning vagrantc! Yeah I've noticed this weird naming requirement. There's also a new initrd=magic alternative
| |
| 08:20 | woernie has joined IRC (woernie!~werner@p5dded1c5.dip0.t-ipconnect.de) | |
| 08:23 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 08:25 | jgee has left IRC (jgee!~jgee@186.80.49.20, Quit: Ping timeout (120 seconds)) | |
| 08:25 | jgee has joined IRC (jgee!~jgee@186.80.49.20) | |
| 09:10 | woernie has left IRC (woernie!~werner@p5dded1c5.dip0.t-ipconnect.de, Ping timeout: 256 seconds) | |
| 09:10 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
| 12:38 | superdad has joined IRC (superdad!~superdad@cpe7824af7d7910-cmf0f249403bc0.cpe.net.cable.rogers.com) | |
| 12:40 | <superdad> Hello, I'm just wondering do you have to boot LTSP images over NFS, or is it possible to generate an iso, and boot that iso file using ipxe over http? I can't seem to find any good instructions on generating an iso
| |
| 12:50 | <alkisg> superdad: sure, actually all ubuntu and debian isos can be netbooted automatically by ltsp kernel
| |
| 12:51 | Now, if you want to create an iso, that's a task that is unrelated to LTSP. AFTER you create it, LTSP will be able to boot it
| |
| 12:52 | But note that usually, iso files have .squashfs files inside them; and ltsp image creates .squashfs files; so the .iso part is just a wrapper to be able to dump them to CDs, that noone uses anymore
| |
| 12:52 | So it's strange why you'd want .iso instead of .squashfs
| |
| 12:52 | <superdad> hi alkisg
| |
| 12:54 | Thanks.I guess currently we are booting Centos 7/8 iso files via ipxe over http
| |
| 12:54 | <alkisg> You mean in live mode, not ltsp mode (no authentication and home directories), right?
| |
| 12:54 | <superdad> We use livemedia-creator to create the CentOS iso files. So I'm just trying to get my head around what is the best way to do this with Ubuntu.
| |
| 12:55 | Ya. So we have a bunch of servers, with no hard drives. What I want to do, is ipxe boot them, with a minimal server OS into memory, install docker-ce, and have them register with kubernetes.
| |
| 12:56 | <alkisg> OK, so you're not using LTSP at all, right?
| |
| 12:57 | <superdad> Not currently. But I'm interested in it.
| |
| 12:57 | Just learned about it yesterday :)
| |
| 12:57 | <alkisg> What you're saying would best be done with ltsp and ltsp images. For that, I could give advice,
| |
| 12:58 | but for "customizing the ubuntu.iso" this is really not the appropriate channel
| |
| 12:58 | In ltsp, you'd maintain a single server template, and you'd run `ltsp image`
| |
| 12:59 | That would create your template.squashfs image, similar to your customized iso, but in a more automated manner
| |
| 12:59 | <superdad> Ok.
| |
| 12:59 | <alkisg> And with ltsp you'd be able to netboot and dynamically configure it
| |
| 13:00 | <superdad> ok. sounds like what we need to do
| |
| 13:00 | Does it also support CentOS?
| |
| 13:01 | <alkisg> Not yet; there are some people that said they'd work on it
| |
| 13:03 | Of course, you can use the ltsp ipxe menu to netboot centos isos like you already do, in non-ltsp mode
| |
| 13:03 | This is an example: https://github.com/ltsp/ltsp/wiki/Non-LTSP-iPXE-entries
| |
| 13:03 | <superdad> Ok. That would be more of a nice to have. We should be able to keep our current process for booting CentOS in place along side this
| |
| 13:03 | <alkisg> I.e. you'd just add a couple of lines to ltsp.ipxe
| |
| 13:04 | If you haven't used ltsp before, I'd suggest that you'd do a quick installation: https://ltsp.org/docs/installation/
| |
| 13:04 | This will give you a quick demo of how ltsp is organized and what it can do
| |
| 13:04 | Then, you'd think how to adjust it to your purposes
| |
| 13:04 | <superdad> Ok. Ya have it install right now in a virtual box test environment
| |
| 13:05 | <alkisg> E.g. you may find that many things will be simpler now...
| |
| 13:05 | <superdad> and I have my network setup to ipxe chain boot
| |
| 13:05 | <alkisg> Great
| |
| 13:06 | <superdad> I was a little confused by the instructions. They seem to contradict what is mentioned at this link: https://github.com/ltsp/ltsp/wiki/chroots
| |
| 13:07 | <alkisg> Contradict, in what way?
| |
| 13:07 | <superdad> So do I need to do what is at https://github.com/ltsp/ltsp/wiki/chroots, and then run ltsp image /
| |
| 13:07 | and then generate my ipxe using ltsp ipxe?
| |
| 13:08 | <alkisg> If you prefer to manage chroots, then sure, but most people prefer to manage / (chrootless) and run: ltsp image /
| |
| 13:08 | In that method, you'd maintain a template server as your rootfs /
| |
| 13:08 | (or VMs, booted e.g. in virt-manager or virtualbox)
| |
| 13:09 | <superdad> Ok. I think we would probably want to manage a chroot, or vm. To keep it separate from the base OS
| |
| 13:09 | <alkisg> In any case, chrootless, VM or chroot, ltsp image will generate the squahsfs image and ltsp ipxe will update the menu
| |
| 13:09 | <superdad> I believe some or our networks would not allow NFS or NDB. Would be able to only boot over HTTP. So just wondering how I would do that
| |
| 13:10 | I know it is a strange requirement. Not normal...
| |
| 13:10 | <alkisg> A developer interested in kubernetes added support for IMAGE_TO_RAM
| |
| 13:10 | That, downloads an image from http to RAM, and boots it
| |
| 13:11 | He also configured his ipxe to download the kernel/initrd via http
| |
| 13:11 | So no tftp/nfs is involved at all
| |
| 13:11 | <superdad> Ok. Sounds very similar to what we might need to do on some setups
| |
| 13:12 | I think to get started in my test environment this seems like what I would want to do: https://github.com/ltsp/ltsp/wiki/chroots
| |
| 13:13 | <alkisg> Yeah it sounds like you're more familiar with chroots
| |
| 13:13 | If you can manage them, ltsp can boot them :)
| |
| 13:13 | <superdad> It is the way we are building custom CentOS images, so people are familiar with it
| |
| 13:14 | Is it possible to do this without a window manager installed? https://github.com/ltsp/ltsp/wiki/chroots
| |
| 13:15 | <alkisg> Sure, there's no requirement for xorg/dms
| |
| 13:15 | <superdad> And it shows at the bottom, "Booting the chroot with a client", but it only seems to talk about doing that in NFS read-write mode.
| |
| 13:15 | <alkisg> I've netbooted plain debootstrapped chroots, of just 200 mb
| |
| 13:16 | That one is "how to maintain a chroot graphically"
| |
| 13:16 | You can ignore it, you do know how to use the chroot command etc
| |
| 13:16 | <superdad> Is read-write mode required to boot it properly? I'm just wondering if read-write is required.
| |
| 13:17 | <alkisg> No. That paragraph is just an example on "how to maintain a chroot by booting it via nfs-rw mode"
| |
| 13:17 | The default mode is nfs-ro
| |
| 13:17 | And, you can use http via IMAGE_TO_RAM
| |
| 13:18 | <superdad> Ok. This is starting to come together in my head. Thanks for all of the help so far!
| |
| 13:18 | <alkisg> np
| |
| 13:20 | <superdad> I don't seem to see and documentation on http via IMAGE_TO_RAM, or booting kernel/initrd via http. Are those available?
| |
| 13:23 | <alkisg> You'd need to change a line in dnsmasq.conf to tell ipxe to locate ltsp.ipxe via http,
| |
| 13:23 | (manually)
| |
| 13:23 | while IMAGE_TO_RAM is documented in https://ltsp.org/man/ltsp.conf/
| |
| 13:25 | If you need more documentation about this, see the pull requests: https://github.com/ltsp/ltsp/issues/75
| |
| 13:26 | <superdad> Ok. Thank you
| |
| 15:59 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 16:00 | fottsia[m] has left IRC (fottsia[m]!~fottsiama@2001:470:69fc:105::48bb, Quit: You have been kicked for being idle) | |
| 16:23 | lucascastro has joined IRC (lucascastro!~lucascast@177-185-130-143.dynamic.isotelco.net.br) | |
| 20:32 | superdad has left IRC (superdad!~superdad@cpe7824af7d7910-cmf0f249403bc0.cpe.net.cable.rogers.com, Quit: Leaving) | |
| 22:11 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 22:15 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b) | |