| *** persia has quit IRC | 03:30 | |
| *** persia has joined #baserock | 03:32 | |
| *** petefoth has quit IRC | 06:28 | |
| *** petefoth has joined #baserock | 06:29 | |
| *** zoli__ has joined #baserock | 08:01 | |
| *** toscalix__ has joined #baserock | 08:06 | |
| *** bashrc has joined #baserock | 08:07 | |
| *** bashrc has quit IRC | 08:09 | |
| *** bashrc has joined #baserock | 08:10 | |
| *** petefoth_ has joined #baserock | 08:27 | |
| *** petefoth has quit IRC | 08:29 | |
| *** petefoth_ is now known as petefoth | 08:29 | |
| *** pedroalvarez has quit IRC | 08:30 | |
| *** pedroalvarez has joined #baserock | 08:31 | |
| *** ChanServ sets mode: +v pedroalvarez | 08:31 | |
| *** rdale has joined #baserock | 08:33 | |
| *** mariaderidder has joined #baserock | 08:34 | |
| *** paulw has joined #baserock | 08:50 | |
| *** CTtpollard has quit IRC | 09:48 | |
| Kinnison | In cluster morphologies, can I refer to environment variables when defining values? | 10:45 |
|---|---|---|
| Kinnison | e.g. can I say INSTALL_FILES: $INSTALL_FILES some/manifest/always/wanted | 10:45 |
| pedroalvarez | Hmm.. I think morph will use your environment without specifying anything in the cluster morphology | 10:46 |
| pedroalvarez | I don't know about ybd | 10:47 |
| richard_maw | Kinnison: no | 10:47 |
| Kinnison | bha | 10:47 |
| richard_maw | variables aren't expanded like that | 10:47 |
| Kinnison | bah too | 10:47 |
| richard_maw | what do you need it for? | 10:48 |
| * Kinnison was thinking that it could be a good way to inject additional content into arbitrary deployments (e.g. for adding ssh keys for test deployments) without having to change cluster files or write scripting to read current values out for augmentation/replacement | 10:49 | |
| Kinnison | If INSTALL_FILES reacted to INSTALL_FILES_* in the environment then I suppose that'd be just as good | 10:49 |
| Kinnison | then I could add INSTALL_FILES_TESTING manifests | 10:49 |
| * Kinnison ponders | 10:50 | |
| Kinnison | the latter would be a fairly easy addition | 10:51 |
| * Kinnison may write a patch | 10:51 | |
| * richard_maw is annoyed that yaml only has a way to merge data into mappings, rather than sequences and scalars | 10:52 | |
| *** inara has quit IRC | 11:37 | |
| *** inara has joined #baserock | 11:49 | |
| *** toscalix__ has quit IRC | 12:37 | |
| *** toscalix__ has joined #baserock | 13:08 | |
| *** bashrc has quit IRC | 13:12 | |
| *** bashrc has joined #baserock | 13:14 | |
| *** tiagogomes_ has quit IRC | 13:28 | |
| *** tiagogomes has joined #baserock | 13:28 | |
| paulsherwood | i may be misunderstanding, but isn't ansible the weapon of choice for what you've described, Kinnison? i thought it allowed config etc | 13:30 |
| Kinnison | paulsherwood: pre-deployment configuration?! | 13:31 |
| * Kinnison thought ansible was post-deployment configuration and orchestration | 13:31 | |
| pedroalvarez | It might be possible to use it for pre-deployment configuration too, but we are not doing that at the moment | 13:32 |
| rjek | My impression of Ansible is that it expects a working booted system to work with | 13:32 |
| pedroalvarez | It can work with a chroot | 13:32 |
| richard_maw | pedroalvarez: of a compatible achitecture presumably | 13:32 |
| pedroalvarez | yes, that's why I didn't continue researching into it | 13:33 |
| *** tiagogomes has quit IRC | 13:59 | |
| *** tiagogomes_ has joined #baserock | 13:59 | |
| *** flatmush1 is now known as flatmush | 14:07 | |
| *** toscalix__ has quit IRC | 14:19 | |
| *** toscalix__ has joined #baserock | 14:25 | |
| *** tiagogomes_ has quit IRC | 14:41 | |
| *** tiagogomes_ has joined #baserock | 14:43 | |
| *** toscalix__ has quit IRC | 15:17 | |
| *** toscalix__ has joined #baserock | 15:17 | |
| *** inara has quit IRC | 15:35 | |
| *** paulw has quit IRC | 15:36 | |
| *** tiagogomes_ has quit IRC | 15:38 | |
| *** inara has joined #baserock | 15:41 | |
| *** tiagogomes_ has joined #baserock | 15:43 | |
| *** doffm_ is now known as doffm | 15:46 | |
| *** zoli__ has quit IRC | 16:07 | |
| *** tiagogomes_ has quit IRC | 16:09 | |
| *** tiagogomes_ has joined #baserock | 16:21 | |
| *** mariaderidder has quit IRC | 16:29 | |
| *** bashrc has quit IRC | 16:58 | |
| *** rdale has quit IRC | 17:06 | |
| *** lmackenzie75 has quit IRC | 17:29 | |
| *** toscalix__ has quit IRC | 17:54 | |
| *** Walkerdine_ has joined #baserock | 20:05 | |
| Walkerdine_ | I think that there might be a problem with the sata drivers on baserock for the jetson | 20:05 |
| paulsherwood | really? | 20:47 |
| paulsherwood | i think we've been ok for SSDs so far - not sure we've attached actual disks though | 20:48 |
| *** zoli__ has joined #baserock | 20:56 | |
| Walkerdine_ | paulsherwood: I've had a problem only with baserock installed | 21:07 |
| Walkerdine_ | Tested with 2 different jetsons and 2 different SSDs | 21:08 |
| Walkerdine_ | Attached with USB works fine though | 21:08 |
| Walkerdine_ | and more than one version of baserock | 21:09 |
| *** Walkerdine_ has quit IRC | 21:22 | |
| paulsherwood | sosons | 21:25 |
| paulsherwood | sounds like you must be right :/ | 21:25 |
| *** Walkerdine_ has joined #baserock | 21:53 | |
| Walkerdine_ | Unless I'm missing something | 22:14 |
| *** Walkerdine_ has quit IRC | 22:51 | |
| radiofree | you're probably missing something | 23:16 |
| radiofree | baserock doesn't have any "sata drivers" installed, it's all in the kernel | 23:16 |
| radiofree | are you powering the ssd device? does anything show up in /dev? | 23:20 |
| radiofree | /dev/sda should be there | 23:21 |
| paulsherwood | radiofree: fwiw i'm trying 5 ybd workers on 5 scaleway machines, as a dumb distbuild network - all pushing to http://212.47.249.244/artifacts/* | 23:56 |
| paulsherwood | will be interesting to see how it compares timewise | 23:56 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!