/srv/irclogs.ubuntu.com/2012/06/13/#maas.txt

=== Aaton is now known as Aaton_off
jtvbigjools: could you sanity-check my updated tftp directory layout at the bottom of this document?  https://docs.google.com/a/canonical.com/document/d/1lpaxXmABGz7ytfc7TrXHCwin7B08EJBEHVyG92KO2qw/edit#03:56
bigjoolsjtv: yup03:56
jtvThanks.03:56
bigjoolsjtv: we have a call shortly, we can discuss?03:57
jtvYes03:59
bigjoolsjtv: ok waiting for you on skype04:01
jtvComing04:01
=== Aaton_off is now known as Aaton
bigjools*cobblerrage*05:41
bigjoolsjtv: have you seen cobbler just suddenly decide to stop authenticating on the web ui?05:45
bigjoolsthe log says:05:45
bigjoolsWed Jun 13 05:39:20 2012 - INFO | REMOTE invalid token; user(???)05:45
=== matsubara_ is now known as matsubara
jtvbigjools: you get that exact authentication failure if your token has expired — or for any other kind of problem with the token IIRC.06:48
bigjoolsjtv: yes I know, but I am logging in to the web ...06:48
jtvAh06:48
=== Aaton is now known as Aaton_off
Davieyrbasak: Hey, jtc mentioned that you said pxelinux.cfg/default cannot be customised for different architectures10:45
DavieyI'm missing your concern.10:45
Davieyjtv*10:45
rbasakYou need to serve a different pxelinux.cfg/default for each architecture, eg. by having different pxelinux.cfg directories10:45
rbasakOtherwise you'll end up serving the wrong arch kernel10:46
jtvHi rbasak10:46
rbasakHello!10:46
rbasakDoes that make sense?10:46
Davieyrbasak: I thought we were looking to make them arch named?10:46
rbasakYou could for example have pxelinux.cfg/amd64/default and pxelinux.cfg/armhf/highbank/default10:46
rbasakSet DHCP "filename" to pxelinux.cfg/amd64/pxelinux.010:47
rbasakOr pxelinux.cfg/armhf/highbank/pxelinux.0 if the highbank vendor string is detected10:47
rbasakBut the default files need to be distinct, and pointed to by the dirname part of the DHCP filename entry10:47
Davieyrbasak: hwhat is wrong with dhcp 209?10:48
jtvIsn't pxelinux.cfg assumed to be in the same directory as the DHCP filename?10:48
rbasakYes, exactly10:48
rbasakDaviey: dhcp 209: https://bugs.launchpad.net/ubuntu/+source/u-boot-linaro/+bug/927781/comments/210:48
ubot5`Ubuntu bug 927781 in u-boot-linaro (Ubuntu) "PXELINUX implementation doesn't respect dhcp ConfigFile or PathPrefix values" [Undecided,In progress]10:48
rbasakDaviey: ie. no dhcp 20910:49
Davieyrbasak: 209 = pxelinux.cfg/default-armhf-highbank ?10:49
Davieyrbasak: i thought we were getting that bug fixed10:49
rbasakDaviey: AIUI, it's a wontfix because the feature is already supported via the filename dirname10:49
rbasakJustin did implement the 209 feature, but I don't think it went anywhere after that10:50
Davieyrbasak: before Justin left, he wrote a patch for 20910:50
Davieyhah10:50
rbasakjhobbs pointed out in comment 2 that the existing support is sufficient10:50
rbasakIt's just a question of how we arrange the pxelinux.cfg directory10:51
rbasakAnd this is only really necessary for the default files10:51
rbasakYou could for example only serve a subarchdirectory filename entry for unknown MACs, and for known MACs just make the MAC-based config file correct for the architecture that we know it is10:51
rbasakAssuming that we know the architecture as soon as we know the MAC10:51
Davieywell default file handling is a PITA10:52
Davieywe'd need /var/lib/tftpboot/pxelinux.cfg/$arch/$flavour/default10:53
rbasakIt isn't nice, but getting U-Boot support for 209 into every vendor firmware isn't really practical AFAICT10:53
Davieyrbasak: can you investigate if we can at least get that patch in trunk?10:53
rbasakThat's a pretty big task to pick up10:54
rbasakI didn't even write the patch remember10:54
rbasakI'm not sure it's worth it given our current priorities10:54
Davieyrbasak: Yeah, i asked Justin to write the patch.. but i suspect he won't follow through with it now :)10:55
Davieyrbasak: current priority is pretty clear from #8.. we are still doing it wrong.10:55
rbasakI think we need to assume that the patch won't be present in vendor firmwares10:55
jtvIf it helps, the question that's blocking us now is what would be a sensible directory structure for the files we need to serve on tftp.10:56
rbasakI'm not sure I understand what #8 means10:56
Davieyrbasak: it's a big task to submita pull request for this patch?10:56
rbasakWe need to have a different kernel for every subarch10:56
rbasakDaviey: it's a big task to follow it through and potentially fix future bugs found in relation to the patch10:57
Davieyok, fine, i'll just do it myself.10:57
=== matsubara_ is now known as matsubara-lunch
rbasakIf we need to have a different kernel for every subarch, we need to have a mapping from vendor class identifiers to our subarch names10:57
rbasakThe mapping is within each default file10:58
rbasakApart from the specific paths in use, I don't see how we could do it differently10:59
rbasakjtv: I think a sensible directory structure would be:10:59
rbasakpxelinux.cfg/amd64/{pxelinux.0,default}10:59
rbasakpxelinux.cfg/armhf/{armadaxp,highbank}/default11:00
rbasakpxelinux.cfg/combined/<mac>11:00
rbasakor if you don't like combined, just put each <mac> entry in the correct arch/subarch directory11:00
jtvActually I wasn't expecting to be able to rearrange things inside the pxelinux.cfg directory… how do we tell clients what to look for in there?11:00
rbasakThey look for their mac address in the directory that pxelinux.0 came from, which is specified by the DHCP filename field11:01
jtvSo pxelinux.0 is inside the pxelinux.cfg?11:02
rbasakOh, good point11:03
jtv(Stupid perpetual unity crashes…)11:03
rbasakI'm wrong. The pxelinux.cfg directory is expected to be in the same directory as pxelinux.011:03
jtvThat's what I thought.11:03
rbasakLet me try again11:03
jtvHave a look at the updated google doc.11:03
rbasakamd64/pxelinux.011:04
jtvhttps://docs.google.com/a/canonical.com/document/d/1lpaxXmABGz7ytfc7TrXHCwin7B08EJBEHVyG92KO2qw/edit#11:04
jtvNear the bottom11:04
rbasakamd64/pxelinux.cfg/default11:04
rbasakarmhf/{armadaxp,highbank}/pxelinux.cfg/default11:04
jtvThe examples in the doc don't include release name yet though.11:04
jtvrbasak: the example you give is included there11:04
jtvISTM we can create subdirectories for the initrds and kernels per release, and keep everything else as in the doc?11:05
* jtv fiddles11:07
jtvThere.  That's assuming that a node's specific config file will contain a reference to the right initrd/kernel, with its path.11:09
jtvOoo, comments are flowing.  Thanks Robie.11:09
rbasakjtv, Daviey: would a quick G+ be worth it? I think it's important we get this right, I haven't made any mistakes and we're all clear on how this wil work :)11:11
jtvSure.11:13
jtvWho wants to set up a hangout?11:13
* rbasak does one11:14
rbasakDaviey: ?11:18
Davieyrbasak: I think 209 is the /right/ fix TBH11:19
rbasakDaviey: I agree, but I'm being pragmatic. It's never gonna happen.11:19
rbasakSince some vendors will never have caught up11:19
Davieyrbasak: you know we are stakeholders in defining this stuff, right?11:20
Davieyrbasak: we may well need to chainload into 'someting smarter' regardless.. Depending on embedded firmware for anything is a limitation we need to be careful folding into.11:21
jtvDaviey: coming into the hangout?11:22
rbasakDaviey: can you join our G+?11:22
=== matsubara-lunch is now known as matsubara
=== Aaton_off is now known as Aaton
=== Aaton is now known as Aaton_off
=== matsubara is now known as matsubara-afk
=== hazmat is now known as kapilt
=== Aaton_off is now known as Aaton
=== kapilt is now known as hazmat
kurt_Can anyone tell me what the mechanism is in maas that copies ssh keys from ~/.ssh/id_rsa.pub to the boot image?22:30
=== Aaton is now known as Aaton_off

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!