=== rangerpbzzzz is now known as rangerpb === jroll is now known as jrollinhatin [15:13] Reading the docs there is a "preserve_source_list" option to prevent sources.list from being modified. However, it looks like it does not have any effect. [15:13] Then I looked at a modified sources.list and at the top there is a comment about "apt_preserve_source_list", which is different thant he docs [15:13] 1) which "verb" should I use? 2) can I use it to prevent any changes? or only some? [15:43] powersj, i'm far from knowledgeable.. but the docs do say "only extra source specifications will be written into /etc/apt/sources.list.d/* " even when preserve_source_list is true. WRT you're question #2 (looks like only 'some' is the answer) [15:45] powersj: jgrimm: recall that the base /etc/apt/sources.list is generated from a template [15:45] there's a default template built-in to cloud-init; or you have to provide your own template [15:46] combined with jgrimm comment, the preserve would only be for .d/ entries IIUC [15:46] cpaelzer might know more; powersj also looking at curtin's vmtest for apt may be informative [15:46] rharper, good idea wrt curtin tests [15:48] powersj, i'm curious to know more by what you mean " there is a comment about "apt_preserve_source_list", which is different thant he docs" .. sounds peculiar [15:48] rharper: jgrimm thanks, from the note in the docs made me think it would preserve sources.list not the .d/* [15:49] ah [15:49] if you think some clarification could improve things, please do submit fixup. :) [15:49] jgrimm: here is from a cloud-init generated source.list: https://paste.ubuntu.com/23324063/ [15:50] so that mentions apt_preserve... but I don't see that mentioned anywhere else in the docs [15:51] i think cloud-init should follow 'preserve_sources_list'. in cc_apt_configure.py at line 300 it checks if that's there before generating [15:51] powersj: that's if you snapshot and boot it in a different instance [15:51] then cloud-init won't re-create the templated file [15:51] powersj: are you seeing that sources.list is re-written when you switch instances ? [15:52] rharper: haven't tried that, just trying to understand all the options and which to actually use. [15:53] gotcha [15:53] powersj: the apt_preserve_sources_list is rewritten to preserve_sources_list in cc_apt_configure.convert_v2_to_3_apt_format [15:55] magicalChicken: ah! so it is a legacy name so to speak [15:55] ah, apt_* version is old, so indeed maybe useful to fix up [15:55] yeah [15:55] "Convert old to new keys..." [15:55] powersj: yeah, the new format is everything under a general apt: key [15:56] so looks like a minor cleanup bug for the emitted text === shardy is now known as shardy_afk [16:22] smoser did u ever get my cla email ? [16:24] where did you send ? more contexst ? [16:24] godaddy never got a copy of theres [16:25] let me figure out where i sent it [16:25] somewhere [16:25] lol [16:25] (canonical ccla for godaddy) [16:26] Scott Moser [16:26] that one [16:26] sent again :-P [16:27] k [16:47] smoser so mdorman may have some resources for VMs :) [16:47] if we can just figure out what we want :) [16:47] we/canonical/us ... [16:49] hello o/ [16:51] o/ [16:54] smoser is https://public.etherpad-mozilla.org/p/cloud-init-centos-unittest still the idea for rhel? [16:55] so i am not totally up to speed with the whole discussion here, but we should be able to provide you N VMs to help with this. but if you need an openstack api endpoint to hit as a way to dynamically spin up/down vms, that’s a little more complex and i’m not sure we can accommodate that (we don’t have an OS api exposed publically today) [16:55] smoser is the one up to speed :-P [16:56] haha [16:57] see the 'mostly now' [16:57] https://gist.github.com/smoser/19e65095b342e98fd4d6466e4d4fa1ac [16:57] that works last i checked [16:58] so with that kind of stuff just VMs with LXC would be fine [16:58] no need for API acccess [16:58] just some VMs with ability to login (for certain keys) [16:58] (perhaps?) [16:58] actually.. so using lxc i can npretty easily run unit tests as seen there. [16:59] and we can do that on existing canonical hardware. [16:59] k [16:59] can/should [16:59] canonical orange boxes? [16:59] :) [16:59] or whatever they were called :-P [16:59] so at the moment i guess i dont need anything [16:59] right, all our boxen are orange. [16:59] just like the next president! [16:59] lol [16:59] ehe [17:00] alright, cool. well if that’s something we can assist with, feel free to reach out to me and/or via josh. it’s pretty easy for us to stand up [17:00] ok. [17:01] wfm === nacc_ is now known as nacc === natorious_ is now known as natorious === rangerpb is now known as rangerpbzzzz === mgagne_ is now known as mgagne