compufreakI have a script that pulls the machine name from /var/lib/hyperv/.kvp_pool_3 and I'd like to use that as the hostname during cloud-init-local step. What's a normal place to put this? cloud-init pulls regular user-data from a network service01:39
compufreakseems like maybe vendor-data but not sure where to put it01:41
Odd_Blokemeena: Yeah, AFAIK NoCloud is a cloud-init thing.13:20
Odd_Blokecompufreak: vendor-data comes from the same source as user-data; it is intended to handle the case where there is cloud-config that a cloud vendor would like applied to every instance (e.g. mirror configuration, NTP, etc.) while still allowing the user to (a) specify user-data, and (b) _disable_ vendor-data if they want.13:22
Odd_BlokeSo probably not what you're looking for in this instance.13:23
Odd_Blokecompufreak: Your best bet may be to configure cloud-init with `preserve_hostname: true` (https://cloudinit.readthedocs.io/en/latest/topics/modules.html#set-hostname) and a bootcmd (https://cloudinit.readthedocs.io/en/latest/topics/modules.html#bootcmd) which runs your script.13:29
compufreakhmm, thanks, I'll take a look!13:41
smosercompufreak: is that hyperv but not azure (or azure on-prem)?13:45
smoserif its azure, then we should make azure datasource do the right thing.13:46
smoserif its something else, then Odd_Bloke did a good job of describing a solution.13:46
compufreakyeah this isn't azure but has some similar mechanics--it's running directly on hyperv (just a pet project)13:50
compufreakafaik azure hypervisor is a customized version of hyper-v13:51
compufreakalthough hyper-v key-value pair through the data exchange integration could be an interesting data source13:52
compufreaknot sure if there's much interest in hyper-v, but here's some notes https://gist.github.com/nijave/f323eb1756933b968b70f0cb951ea619 (the altaro link has a lot of details)13:54
compufreakyou can actually create a socket through vmbus hyper-v provides so you could make a psuedo-network service that works without the VM having a network connection13:55
Odd_BlokeOh, that's cool.13:56
smosercompufreak: i'm pretty sure cloud-init uses that on azure to post logs.14:05
smoseryeah, see push_log_to_kvmp/report_compressed_event14:07
Odd_Blokecompufreak: How are the key/value pairs in .kvp_pool_3 determined, do you know?14:59
amansi26blackboxsw:I need to clarification about: https://bugs.launchpad.net/cloud-init/+bug/1894839    I am using preserve_hostname: false and did a capture deploy, the VM hostname is expected as the name associated with IP, or the name using which we deployed the VM15:05
ubot5Ubuntu bug 1894839 in cloud-init "hostname not getting set as per the dns" [Undecided,New]15:05
compufreakOdd_Bloke: see https://www.altaro.com/hyper-v/key-value-pair-data-exchange-3-linux/15:25
compufreakOdd_Bloke: basically there's 4 "pools" host->guest (read-only) host->guest rw, and vica-versa and the files are fixed field size kv pairs with nul byte padding15:26
rs_goyal__I am using centos7/8 standard images(https://cloud.centos.org/centos/) to created an instance and openstack is the datasource. I am trying to push a shell script  via vendor data, the script gets copied in `/var/lib/cloud/instance/scripts/vendor/script` but does not get run on the boot up. The same works for other distributions like ubuntu/fedora etc. From the cloud-init logs I was able to see that, it did not15:39
rs_goyal__run the script in final stage. Let me know if someone has any idea on this.15:39
blackboxswamansi26: preserve_hostname: false means cloud-init will set hostname to whatever metadata says the hostname should be. If True, it means it'll leave the hostname whatever it is already configured to in the image.16:08
Odd_Blokecompufreak: Right, I read through that; my questions are more: what determines the contents of pool 3 on the host side?  Is it reliably similar across Hyper-V deployments?  Does it change across versions of Hyper-V?  Can admins modify (all of?) it?16:13
Odd_Blokers_goyal__: Are you able to pastebin cloud-init.log?16:15
blackboxsw#startmeeting cloud-init status meeting16:18
meetingologyMeeting started Tue Sep  8 16:18:47 2020 UTC.  The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:18
meetingologyAvailable commands: action commands idea info link nick16:18
blackboxsw#chairs smoser Odd_Bloke rharper falcojr lucasmoura16:19
blackboxswhey folks. welcome to another public cloud-init status meeting16:19
blackboxswdisclaimer: interruptions and side conversations are welcome16:19
blackboxswWe use this platform/channel to discuss latest and greatest cloud-init, as well as ensuring that there are a couple of upstream developers present to field questions or discussion as needed.16:19
blackboxswWe gather here in this IRC channel every 2 weeks to discuss current development tasks and progress on cloud-init.16:20
blackboxswPrevious meeting minutes are here;16:20
blackboxsw#link https://cloud-init.github.io/status-2020-08-25.html#status-2020-08-2516:20
blackboxsw The topics we'll cover today: Previous Actions, Recent Changes, In-progress Development, Community Charter, Office Hours (~30 mins).16:20
blackboxswI expect today will be short as the entire Canonical team is involved in cloud-init SRU verification for Ubuntu at the moment16:21
blackboxsw#topic Previous Actions16:21
blackboxswlast meeting had an action item we needed to resolve16:22
blackboxsw bbsw add workitem to SRU release process to announce to mailinglist estimated next SRU timeframe.16:22
blackboxswthis item can be resolved as I've added the content requested to our email template which will be sent out once this SRU completes.16:24
blackboxswI see no other actions from last meeting16:24
blackboxsw#topic Recent Changes16:25
blackboxswThe following are upstream commits landed in cloud-init's master branch:16:26
blackboxsw#link https://paste.ubuntu.com/p/NgqncRMG9c/16:26
blackboxswIn the last couple of weeks we cut the upstream 20.3 release (thanks everyone for all the help there).  Queued SRU uploads for ubuntu/xenial, bionic and focal release testing.16:28
amansi26blackboxsw: metadata here will be the configdrive, if my understanding is right?16:28
blackboxswAnd added some goodness to systemd units and ordering (sort systemd cloud-init-local.service hv_kvp_daemon and systemd: add Before=shutdown.target when Conflicts=shutdown.target is16:30
blackboxsw      used )16:30
blackboxswthanks paride and robjo for those commits16:30
blackboxswamansi26: +1 you can see the metadata configured hostname from cloud-init query local-hostname I think16:30
blackboxswamansi26: +1 you can see the metadata configured hostname from `cloud-init query local-hostname` I think16:30
blackboxswamansi26: I was just starting to respond to your bug you linked too16:30
blackboxswI think preserve_hostname: false (which is cloud-init's default behavior )  means cloud-init will read that hostname from metadata and apply it to the system16:31
amansi26Sure. there is another bug which I observed on a RHEL8 environment: https://bugs.launchpad.net/cloud-init/+bug/189483716:31
ubot5Ubuntu bug 1894837 in cloud-init "RHEL8 ipv4 IPs not getting set" [Undecided,New]16:31
blackboxswamansi26: sorry cloud-init query local_hostname   (# not with a hyphen)16:35
blackboxswchecking 2nd bug16:35
blackboxswso amansi26 you'd like the ability to override the iface_defaults on rhel systems for NM_CONTROLLED to set  True instead of false for cloud-init interfaces?16:38
blackboxswgenerally if cloud-init is rendering network configuration on an instance, it tries to avoid using network manager by default. I think it's worth requesting logs on  your bug16:40
blackboxswthose cloud-init logs can be obtained using cloud-init collect-logs (which generates a tar.gz file in the current working directory). then attach that to the bug16:40
amansi26yes, since I was reading the documentation for RHEL8 network configuration, I found that NM_CONTROLLED = yes should be there. but we are passing the value as No.  Sure I will attach the logs to the defect16:41
blackboxswthanks amansi26 I responded on that bug too16:43
blackboxswOk, per the meeting,  that wraps #recent-changes topic I believe16:46
blackboxsw#topic In-progress Development16:46
blackboxswCurrently the Canonical team is working hard on SRU verification so we can release cloud-init v. 20.3 to Xenial, Bionic and Focal. It looks like we are done with most major cloud verification and walking through individual verification items.16:48
blackboxswI believe falcojr mentioned this morning we are about 5 of 30ish verification items complete.16:50
blackboxswwe are continuing to work this verification as our top priority16:50
blackboxswfolks interested should subscribe to updates on our SRU bug16:50
blackboxsw#link https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/189306416:51
ubot5Ubuntu bug 1893064 in cloud-init (Ubuntu) "sru cloud-init (20.2-45 to 20.3-2) Xenial, Bionic, and Focal" [Undecided,In progress]16:51
blackboxswthat bug will transition to verification-complete once all verification is done16:53
blackboxsw #topic Community Charter16:54
blackboxswThe following topics are still topics for ongoing community development anyone new to cloud-init, or with a bit of time could easily grab one of these bitesized tasks:16:54
blackboxsw JSON schema extensions to validate user-data before instance launch: https://bugs.launchpad.net/cloud-init/?field.tag=bitesize16:54
blackboxsw- cloudinit.net refactor into distro-specific networking subclasses cloudinit.distros.networking: https://bugs.launchpad.net/cloud-init/+bugs?field.tag=net-refactor16:54
blackboxswIf anyone would like to be involved more than they currently are, please feel free to contact us here in IRC #cloud-init on Freenode or on the mailing list cloud-init@lists.launchpad.net and we can see how best we can get you "set up"16:54
blackboxsw#topic Office Hours (next ~30 mins)16:54
blackboxswthis time of the meeting is really just an open door for any discussions, concerns, bugs, questions or general prodding of upstream devs to make sure existing development work is unblocked where possible.16:55
blackboxswin absence of discussions. We actually will be focused on SRU verification tasks today.16:55
blackboxsweach of these verification logs and scripts are pushed as pull requests  to https://github.com/cloud-init/ubuntu-sru/pulls16:56
blackboxswok I think that about wraps today's session. Next meeting will be in two weeks, but we'll likely see you in channel earlier.17:13
=== blackboxsw changed the topic of #cloud-init to: pull-requests https://git.io/JeVed | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting Sept 22 16:15 UTC | 20.3 (Aug 25) | https://bugs.launchpad.net/cloud-init/+filebug
meetingologyMeeting ended Tue Sep  8 17:13:31 2020 UTC.17:13
meetingologyMinutes:        http://ubottu.com/meetingology/logs/cloud-init/2020/cloud-init.2020-09-08-16.18.moin.txt17:13
blackboxswok just published minutes17:14
blackboxswthe should show up here in a few mins: https://cloud-init.github.io/17:14
lucasmouraHey everyone, I am trying to manually test the following PR, but it seems that I will need to pass a custom datasource to set the region in a way that ec2 regex will match. Is there an easy way to provide a custom datasource using cloudinit ?17:23
lucasmouraI have looked at the NoCloud datasource, but it seems even using it I would need to pass a kernel cmdline to pass a location where cloudinit will download the metadata files17:24
lucasmouraSo maybe there is a more straightforward approach on this situation17:24
meenaOdd_Bloke: if we're responsible for NoCloud… then we should document it… i wanted to write better… but given how poorly it is documented right now, anything would be better. We should also provide canonical ;))) tooling for it.18:02
meenajust a thought18:02
minimalmeena: Hi, just caught the end of your conversation. What's the documentation issue with NoCloud? I've been using it quite a bit and don't remember noticing any omissions in the docs18:18
blackboxswfalcojr: just put up focal openstack https://github.com/cloud-init/ubuntu-sru/pull/15419:47
blackboxswSRU verification19:47
blackboxswI'll hit the open reviews now19:47
lucasmouraIs anyone having any trouble with the cloud-init-dev/proposed ppa ? I am trying to add it, I get the following error: ERROR: '~cloud-init-dev' user or team does not exist20:30
lucasmouraBut looking at the ppa page, it seems fine20:30
blackboxswno ~ I think20:30
blackboxswyeah  ppa:cloud-init-dev/proposed20:31
blackboxswlucasmoura: but also, we should be using -proposed directly20:31
lucasmouraNo error when you run add-apt-repository ppa:cloud-init-dev/proposed -y ?20:31
blackboxswhttps://paste.ubuntu.com/p/wpW3RtMCMZ/ not for me20:32
lucasmouraForget it, I think I now what is happening. I doing a manual verification that messes the network-config. That is the reason :facepalm:20:32
blackboxswlucasmoura: https://github.com/cloud-init/ubuntu-sru/pull/153#discussion_r485169456 is what I was referring to20:33
blackboxswisntead of the cloud-init-dev/ppa20:33
lucasmourablackboxsw, ack20:34
Odd_Blokeblackboxsw: falcojr: lucasmoura: paride: FYI I just accidentally pushed to ubuntu-sru master and force-pushed back to the correct HEAD of master.  (You should be fine if you haven't fetched in the last ~3 minutes.)20:45
meenaminimal: i don't know what to tell ya, for something that documents a standard / protocol, i find it lacking. same with the tooling. we don't provide any.20:51
minimalmeema: for tooling that's what cloud-utils is for21:09

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