| [09:42] <alocer> hello guys. | |
| [09:42] <alocer> how do you predict NIC names, in order to set an IP on them ? | |
| [09:43] <alocer> one VM is enp0s3 and my laptop is enp0s25 | |
| [09:43] <alocer> i can not predict the names ! | |
| [09:48] <meena> alocer: i thought that *is* the predictable naming?! | |
| [09:49] * meena is used to Solaris and FreeBSD where the names are weird but at least they are predictably weird | |
| [09:50] <meena> alocer: but you can activate renaming and then it'll be eth0 | |
| [15:09] <Odd_Bloke> The predictability referred to here means that they will predictably be named the same thing across boots of the same instance, not that they will be predictably named across different instances. | |
| [15:10] <Odd_Bloke> The eth* names are assigned by the kernel in the order in which network interfaces become available; this order is not stable across boots, so "eth0" is not reliably the same interface if you have multiple network interfaces in a machine. | |
| [15:11] <Odd_Bloke> alocer: I'm curious what cloud-init configuration you're trying to do across a VM and a laptop? If this is more of a general Ubuntu question, then #ubuntu (or, perhaps, #ubuntu-server) would be better places to look for assistance. (If this _is_ a cloud-init thing, then please ask away!) | |
| [15:44] <meena> how on track is the release? | |
| [15:45] <meena> I'm considering to prepare a patch for ports for the new release | |
| [16:10] <Odd_Bloke> meena: What do you mean by "on track"? | |
| [16:15] <meena> is it happening… today? | |
| [16:40] <Odd_Bloke> meena: We're aiming for Tuesday. | |
| [16:48] <alocer> Odd_Bloke: nope but it's kinda related. how community do static ip for multiple nic's and multiple oses. | |
| [17:06] <Odd_Bloke> alocer: I'm still not 100% sure what you're asking, but if you aren't using cloud-init then this isn't the appropriate venue; we won't be able to answer your Qs effectively.# | |
| [17:10] <alocer> (y) | |
| [17:18] <meena> Odd_Bloke, aye. I'll prep a ports patch then | |
| === ijohnson is now known as ijohnson|lunch | |
| [17:54] <Odd_Bloke> blackboxsw: falcojr: I wrote you a little essay, it turns out: https://github.com/canonical/cloud-init/pull/679#issuecomment-731317815 | |
| [17:58] <falcojr> I always love me a good essay | |
| [18:01] <meena> Nice | |
| [18:29] <asakkurr> Thanks again @Odd_Bloke for detailed review on #613. I've addressed the comments from you and johnsonshi and sent an update. Feel free to let me know if you have more comments. | |
| [19:03] <Odd_Bloke> asakkurr: Thanks for the update! I've just got back from lunch, and my first pm task is to re-review. :) | |
| [19:16] <Odd_Bloke> johnsonshi: "This is my last comment on `report_diagnostic_event` for this PR" <-- me except about autospec'd mocks :D | |
| [19:36] <asakkurr> 😃 I don't mind addressing all the nits and diagnostics changes as long as I don't miss the SRU 😊 | |
| [19:41] * blackboxsw grabs last remaining PR for review tagged for upstream 20.4 release https://github.com/canonical/cloud-init/pull/660 | |
| [19:45] <Odd_Bloke> asakkurr: Just submitted my review: a couple of missing tests (and a minor functional bug which one of those tests should catch) but otherwise we're looking good. :) | |
| [19:45] <blackboxsw> sounds like #613 may be considered for upstream. I'll defer to others on that thought. if we miss upstream release cut (which is just a point in time for a tag), it would still be easy to squeeze trailing commits in pre-SRU | |
| [19:46] <asakkurr> Awesome, thanks Odd_Bloke . Looking at them now. Will request re-review once I update. | |
| [19:46] <blackboxsw> as we take tip of master when we start the SRU process (and that could very well be a couple of commits past the 20.4 upstream release tag | |
| [19:47] <alocer> can i change partition to lvm ? is it recommended ? | |
| [20:01] <Odd_Bloke> alocer: Again, not sure this is the best place to be asking. What Linux distro are you using? | |
| [20:09] <alocer> ubuntu cloud images comes with 10G disk available in them. lets say i want to deploy them to vsphere. how can i make it LVM so that i can increase it later? disk_setup and fs_setup is for adding another disk. but could'nt figure out how yet. | |
| === ijohnson|lunch is now known as ijohnson | |
| [20:25] <Odd_Bloke> alocer: I don't believe there is support for using LVM as the root of instances based on those images: the general expectation in clouds is that you'll attach separate disks in order to expand the default storage, and those would be what you would use LVM for. | |
| [20:25] <Odd_Bloke> cloud-init will handle expanding the image to fill the disk, so if you want a larger root disk, you should just be able to create your VM with a larger disk and see that happen. | |
| [20:26] <Odd_Bloke> (But there isn't support for /-on-LVM.) | |
| [20:27] <alocer> Odd_Bloke: thank you, i wasn't sure. i will make additional storage and work on that. (y) | |
| [20:27] <Odd_Bloke> alocer: :) | |
| [20:41] <johnsonshi> Odd_Bloke: Really awesome and thanks for the efforts on reviewing #613! | |
| [20:44] * blackboxsw read up on ssh host certs on https://github.com/canonical/cloud-init/pull/660 thanks for the attention there falcojr on review. | |
| [20:44] <blackboxsw> awaiting CI there and will land | |
| [21:00] <blackboxsw> https://github.com/canonical/cloud-init/pull/660 merged | |
| [21:02] <blackboxsw> community-notice: && Odd_Bloke falcojr lucasmoura smoser rharper are there any other PRs that folks are aware of that we might want to target toward 20.4 upstream release cut? | |
| [21:05] <blackboxsw> rharper, we bumped #647 out of inclusion in 20.4 release to get some bake time in ubuntu/devel first : (use cached datasource when can't re-detect orig DS on "dirty" boot) | |
| [22:06] <asakkurr> Odd_Bloke Addressed the issue you pointed out with nl_sock (thanks!) and added test for networking changes. | |
| [22:17] <Odd_Bloke> asakkurr: Excellent, thank you! It's pretty much the weekend for me, so I'll get to that first thing on Monday. :) | |
| [22:23] <asakkurr> Can we still take it in the release if it gets checked in on Monday? Just making sure 😊 | |
| [22:43] <blackboxsw> asakkurr: given how late-ish it is Friday; I don't think we are cutting the upstream release 20.4 until we circle wagons monday and make sure all that is intended has been included. since it's being looked a Monday, I expect it's probably fine. | |
| [22:45] <asakkurr> Great, thanks for confirming blackboxsw | |
| [23:50] <meena> i'm getting ahead of y'all: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251280 | |
| [23:50] <ubot5> bugs.freebsd.org bug 251280 in Individual Port(s) "net/cloud-init: prepare for 20.4 release" [Affects only me,New] | |
| [23:51] <blackboxsw> schweet meena !!! | |
| [23:52] <meena> so happy i'm getting rid of dmidecode dependency | |
| [23:52] <meena> we can now finally run FreeBSD aarch64 and MIPS on clouds :P | |