| *** vmrod25 has joined #starlingx | 14:27 | |
| *** vmrod25 has quit IRC | 14:30 | |
| *** vmrod25 has joined #starlingx | 15:01 | |
| *** TxGirlGeek has joined #starlingx | 15:19 | |
| *** vmrod25 has quit IRC | 15:21 | |
| *** rcw has joined #starlingx | 17:36 | |
| sgw | dpenney_: slittle1: what's the status of jenkins mods for the pike removal? | 19:17 |
|---|---|---|
| slittle1 | Haven't started. t appears in aprox 8 jenkins job, always in conjunction with paths such as .... centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/ ... | 19:27 |
| slittle1 | trying to find/copy initrd.img, vmlinuz, squashfs.img | 19:29 |
| sgw | So, this will be another early 4.x item I was just trying to kill off the reference as we move to train. | 19:29 |
| slittle1 | Which touches on another issue. distinguishing the installers from the different cantos releases | 19:30 |
| slittle1 | CentOS | 19:30 |
| sgw | Yeah, I was starting to think about that also, not just centos releases but OSes in general. | 19:32 |
| sgw | dpenney_: does the update-iso also fix up the pxe installer? | 21:55 |
| dpenney_ | fix how? | 21:59 |
| dpenney_ | it updates the syslinux.cfg and grub.cfg boot menu, as well as updating the grub.cfg in the EFI boot image | 22:00 |
| dpenney_ | for initial installation of controller-0 from USB/ISO | 22:00 |
| sgw | Right that's for the controller-0 install, but what about controller-1 and other nodes? | 22:01 |
| dpenney_ | that would be unrelated. There are installation parameters for the host in sysinv for setting specific parameters in the generated pxelinux.cfg files for nodes installed from the active controller | 22:02 |
| sgw | Ah, I did not see that in the docs, granted I did not look hard | 22:03 |
| dpenney_ | I described it in my reply to starlingx-discuss on Friday titled "RE: RC2.0 - Change install device" | 22:06 |
| dpenney_ | http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006969.html | 22:07 |
| sgw | dpenney_: so no documentation anywhere else? | 22:13 |
| dpenney_ | not sure | 22:13 |
| dpenney_ | it would have been in documents at one point | 22:14 |
| sgw | what about changing the kernel cmd line, I want to add another option (net.ifnames=0) for these NUCs that I am testing with | 22:15 |
| dpenney_ | there's no support for adding custom kernel parameters via sysinv that I'm aware of | 22:18 |
| dpenney_ | you could update the pxelinx template file that's used for generating the cfg file for a specific host | 22:18 |
| dpenney_ | that would allow you to specify something to the install-time kernel cmdline | 22:19 |
| dpenney_ | at runtime, you'd find those templates under /pxeboot/pxelinux.cfg.files/ on the controller | 22:20 |
| dpenney_ | in the repo: https://opendev.org/starlingx/metal/src/branch/master/installer/pxe-network-installer/pxe-network-installer | 22:22 |
| sgw | Yeah, found that stuff, giving it a try. There is a way to add custom options but it's buired in sysinv/conductor/manager.py and used only for security | 22:34 |
| *** vmrod25 has joined #starlingx | 23:56 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!