/srv/irclogs.ubuntu.com/2018/06/20/#cloud-init.txt

blackboxswsmoser: rharper release 18.3 branch00:24
blackboxswhttps://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/34825400:24
blackboxswthen I can push an MP for cosmic00:24
blackboxswwill check back in a couple hours00:25
smoserblackboxsw: ah. ok. i had thought throw snapshot into cosmic01:08
smoserand then tomorrow do a release.01:08
smoserblackboxsw: i think if the goal is just to upload to cosmic with a 18.3, then lets wait til morning before we tag.01:14
smoserthat will get us a nightly c-i run on trunk also.01:14
smoserblackboxsw: i went ahead and kicked off a 'Build Now' for each recipe01:24
smoser https://code.launchpad.net/~cloud-init-dev/+recipes01:24
smoserso we'll have daily archive up to date shortly with master (a670eb81)01:24
smoserwith fingers crossed that there are no keyserver demons lurking01:24
smoseralright. landing https://code.launchpad.net/~cloud-init-dev/+archive/ubuntu/daily/+packages01:26
smoserand i'm going to take off on that note.01:26
blackboxswsounds good scott02:30
=== shardy is now known as shardy_afk
=== shardy_afk is now known as shardy
smoserok... as a form of version control http://paste.ubuntu.com/p/tcj3QhSmGD/15:05
smoserthat is skip_by_date as a decorator, i plan to try to put it into curtin soon.15:05
smoserrharper: https://code.launchpad.net/~smoser/curtin/+git/curtin/+merge/34828216:03
smoseroops.16:03
rharperhehe16:06
blackboxswsmoser: so SRU and https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/34825416:15
blackboxswshall I push an 18.3 tag to upstream to get CI to work there and get that landed?16:15
blackboxswand we cut a cosmic, xenial artful bionic set of merges?16:16
blackboxswhttps://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/34825416:48
blackboxswhrm ok smoser rharper , I've bungled/missed something with pushing my tags and trying to push 18.3 to origin(upstream).17:27
smoserok17:27
blackboxswI think I've pushed 18.3 tag to our common repo for cloud-init17:27
blackboxswgit tags --list shows it when I have master checked out. yet git log --decorate doesn't decorate the proper commit with the tag name17:27
smoseri think a rebase happened or something....17:28
blackboxswI do see the tag decorating my specific branch release/18.317:28
smoserprobably in your merge review thing17:29
smoserupstream/master is differant than the tag17:29
smoseri can fix or you can, but essentially17:29
smosergit checkout master17:29
smosergit reset --hard 18.317:29
smosergit push upstream master --force17:29
smoseror probalby that is just17:30
smosergit push upstream 18.3:master --force17:30
smoseror something17:30
blackboxswok worked. I'll sort what review-mps did/does as it merges the branch locally (giving us a different commitish I think).17:31
smoserright17:31
smoserwhat it could do is17:31
smosergit merge --ff-only17:31
blackboxswright, I think.17:31
smoserif there was 1 new commit and that worked, it could do that.17:32
smoserother wise, it woudl rebase and squash like it does.17:32
blackboxswyeah multicommits we'd have a problem as we are squashing17:32
blackboxswyeah17:32
blackboxswok will add that to review-mps today. single commit --ff-only option17:32
smoseri think i'd just have it do it if it could17:33
blackboxswhttps://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/348300 is up17:36
smoserok. before we do that lets get the release into launchpad17:38
smoserblackboxsw: can you take a quick glance at changelog for highlights ?17:38
smoserah. i knwo. hackmd link coming.17:38
smoserhttps://hackmd.io/lIMTEWtaSpGgrleLM0pJBQ17:39
smoserblackboxsw: ^17:39
blackboxswchecking17:52
smoserblackboxsw: just sent.17:54
smoseryou were too slow :)17:54
smoserno big deal.17:54
blackboxswheh, nice. my coffee machine was too slow you mean17:55
blackboxswis it worth me scripting all bugs mentioned in changelog to the given milestone?17:55
smoser?17:56
blackboxswper the "35 launchpad.net issues" fixed17:56
smoseroh. i did that sort of17:56
smoserand updated that doc17:56
blackboxswwe could target them to https://launchpad.net/cloud-init/+milestone/18.317:56
blackboxswso they'd show there17:56
blackboxswtoo17:56
smoserwe could do that. and i guess do that in lp-bugs-released.... i dont know.17:57
blackboxswas a point of reference in the future for stuff that was fixed17:57
blackboxswyeah I was thinking lp-bugs-released extension17:57
smoseri'm going to run the lp-bugs-released script now.17:57
smoseris that ok ?17:57
blackboxsw+117:57
smoserk17:57
blackboxswI have a tweak for specific bug series task. I think which might help as the SRU progresses17:57
blackboxswa tweak to only target the specific bug distro-series task rather.17:58
smoser?17:58
smoserthe lp-bugs-released only does upstream17:59
smoserright?17:59
blackboxswright, but it could do individual series tasks too per something like https://launchpad.net/cloud-init/+milestone/18.317:59
blackboxswWIP patch obviously. I was just peeking at it.18:00
blackboxswoops bad paste18:00
blackboxswhttp://paste.ubuntu.com/p/k6tTxnzTrN/18:00
smoseri just fixed the "version "18:01
* blackboxsw gets merge proposals for xenial,artful, bionic together now (and filing an SRU bug)18:01
blackboxswsmoser: you haven't filed an SRU bug yet have you?18:01
smoserno.18:03
blackboxswok filing18:04
smoserbug mail coming in 5....18:05
smoser4, 3, 2, 118:05
smoserblackboxsw: ok. on that note, i have to run. i'll be back in later and can do uploads for sru then.18:06
blackboxswok thanks man18:06
smoseri think release is all done now.18:06
blackboxswdragging the trello card18:07
=== r-daneel_ is now known as r-daneel
blackboxswsmoser: I pushed minor changes into new-upstream-snapshot19:16
blackboxswto account for debian/changelog containing xenial-proposed instead of xenial19:17
blackboxsw3 branchs for SRU upload review tied to this card smoser https://trello.com/c/8jshO6oa/847-sru-183-to-xenial-artful-and-bionic19:32
blackboxsw*branches*19:32
* blackboxsw needs to tweak artful and xenial branches there. we need to disable OpenstackLocal.network_config by default19:47
blackboxswas it is configurable to "apply_network_config: true" in datasource config19:48
blackboxswand we don't want to change artful/xenial behavior... maybe bionic too? WDYT rharper smoser19:48
rharperright, I think we played some games with the names in the datasource class when we did this with AzureDatasource19:49
blackboxswrharper: the way I wrote DataSourceOpenstack.network_config property we now check if ds_cfg.get('apply_network_config') == False: return None. This renders fallback config (which is what xenial->bionic do today)19:50
blackboxswquestion I have is, should bionic continue to only render fallback config :/?19:51
rharperyes19:51
blackboxswok will apply a patch for those releases19:51
blackboxswto adjust the default behavior to fallback for all 3 series19:51
rharperlet me think on it a bit too;  IIUC, we could run "faster" but only render fallback config19:52
rharperwhich wouldn't change functionality, just the speed, right ?19:52
rharperwhere as in cosmic, we could read network_data.json over metadata service at local and render that instead of fallback19:52
blackboxswcorrect on all counts. we could either patch to remove DataSourceOpenstack.network_config subclassed property altogether (to run faster and retain exact current behavior).   OR -19:54
blackboxswwe could patch Openstack.network_config to default to apply_network_config == False  if not provided, thereby allowing someone to override that and react to network_data.json if they want (a little slower as we check a config option value before rendering fallback config)19:54
blackboxswI think we want the 2nd choice on Xenial-Bionic as it is a useful feature to turn on if someone wants it19:55
blackboxswthough I think they'd have to turn it on in their images, not user-data19:55
rharperyes; I'm included to keep fallback rendering for OS metadata service in Xenial -> Bionic, but run at local if we can19:56
blackboxswok good deal19:56
rharperthat produces a speedup ( \o/ ) without a change in function19:56
rharperlet's see if smoser agrees19:56
blackboxswyeah exactly, local timeframe == speedup19:56
robjoblackboxsw: I was going to take a look at lp#1733226 and thought this may not lead too far down the rabbit hole, but turns out that dhclient stuff appears to be splattered across data sources and other parts of the code20:29
robjoso I need some guidance and maybe this is too big of a project to start on late Wednesday afternoon and better wait for THursday morning20:29
blackboxswbug #1733226, yeah that's a not easy to start late Wedneday robjo : /20:46
ubot5bug 1733226 in cloud-init "cloud-init-local service fails on SUSE distros" [Undecided,New] https://launchpad.net/bugs/173322620:46
blackboxswyeah the context hander and sandboxed environment with dhclient vs wicked is potentially a bit of a dig20:47
robjoOK, I'll ping you another day20:48
blackboxswhrm, so was this Openstack  robjo ?20:49
blackboxswcould you cloud-init collect-logs and add the tarfile?20:49
robjoI do not know, I can ask in the bug report I do not know the reporter20:49
blackboxswor Ec2/Azure maybe? those are the 3 major datasources that use it currently20:50
robjoLets see if we get an answer20:51
blackboxswit may be as simple as just replaceing dhclient with wicked, but there is lease processing etc.. and I haven't looked at how wicked stores dhcp-related conf etc. (I'm guessing that's in my immediate future)20:52
blackboxswsounds good robjo, yeah we need to fix this for SLES it seems as this EphemeralDHCPv4 context manager is the direction most datasources are oging20:56
blackboxsw*are going20:56
robjoWell, I'll do leg work, but the idea of having to change 3 data sources and then doing so for others potentially in the future is not very appealing, seems there should be an abstraction ;)20:56
blackboxswrobjo: yeah it's all in cloudinit.net.dhcp maybe_perform_dhcp_discovery20:57
blackboxswmight want to extend it to accept network_util='dhclient' default20:57
blackboxswwhich could be overridden with wicked I suppose20:57
robjoFound that file, but also saw in the azure datasource I think (via grep) what looked like hard coded info about lease info20:58
blackboxswohh yeah, yuck right. hardcoded dhcp lease path20:59
robjogiven the we're "special" :rolling_eyes: maybe this should not be distro independent, but I suspect major surgery is required to make this distro dependent20:59
blackboxswthough that datasource already does a switch on util.is_FreeBSD to tweak expected lease_file path on different distros21:00
blackboxswhrm maybe distro could announce default network_cmd, we also have to solve this for a netplan-only world too, as dhclient is not really a mandatory command in newer ubuntu series.21:03
blackboxswso this is a type fix that is on our radar, just hadn't tried tackling it yet because we didn't need to... yet.21:04
robjonetwork_cmd would probably be a dict then if we want to support the lease monitoring part we'd need at least dhcp_client_cmd,dhcp_client_options, lease_info21:04
robjoand interface21:07
blackboxswcould be, I'm kindof leaning toward the idea that maybe_perform_dhcp_discovery should be smart enough to detect valid dhclient commands and make a sane choice based on present of the utility so that we don't continue to bloat the Distro classes. but it'll require a bit more thought for the use-cases21:07
blackboxsw*based on presence/absence of the utility*21:07
blackboxswI liked what you did w/ ifconfig vs ip stuff21:08
blackboxswit feels like it contains that logic in a single place local to where it is being used (even though it's kindof distro related)21:08
blackboxswbut again, I'm not certain this EphemeralDHCPv4 solution is strictly compatible with a systemd networkd -only world.21:10
blackboxswone idea we were tossing around was to write our own tiny python dhclient which opens a socket to do the dhcp discovery21:10
blackboxswall we are attempting to do is sniff a lease on the primary nic if available.21:11
blackboxswthis may be time for us to queue that work :21:11
blackboxswthis may be time for us to queue that work :/21:11
* blackboxsw and socket programming from python. not a well used muscle. 21:12
robjoThe advantage of ifconfig/ip transition is that ip options are universal, but for the dhcp stuff distros, staring with SLES have clearly diverged and it appears there may be further drift, so having "smart" handling in one place may lead to lots of if-elif-elif code21:12
robjowell getting a dhcp request out in and off itself is not all that difficult, what I don't know what effect that has on subsequent requests21:13
robjoFor example when AWS added ipv6 and wicked sent out options the dhcp server didn't understand they just didn't respond21:14
robjoso no lease :(21:15
robjopresumably a cloud-init implementation of get_dhcp_lease() would not send any option or only a minimal set21:15
robjobut then what does the dhcp server do when the next request comes from the same origin, does it just return what it already handed out and ignore other options that might be sent along?21:16
robjoI have no idea how that works21:16
robjoAnd maybe this topic is too big for IRC and e-mail and we should beat on it during the summit21:18
blackboxswcorrect, cloud-init's get_dhcp_lease()  would be a dumb/simple dhcp-discovery packet without any custom options. It'd blindly return a dict of whatever lease options the response gave.   Generally the dhcp server ends up giving out the same IPs on previous discovery if the lease time hadn't expired I believe. (as it's how it's currently working in ec2/openstack.21:18
blackboxswagreed, it's a big topic. I think you are right.21:18
blackboxswI'll add it to the list of potential topics21:19
blackboxswcurrently I have the following:21:19
blackboxswtopic ideas:21:19
blackboxsw - move SLES & openSUSE to sysconfig renderer21:19
blackboxsw - hotplug network stuff (one-shot stuff)21:19
blackboxsw - cloud-init as a daemon for repeatable calls, expedited boot runs21:19
blackboxsw - wicked support for EphemeralDCHPv421:19
blackboxswas we get closer that list will probably grow into a hackmd doc we can all comment on that we will send to the mailinglist21:20
robjoDavid already had a preliminary agenda, I take it you'll coordinate with that ;)21:21
blackboxswyeah if I have to ;)21:23
rharperblackboxsw: another alternative that we've discussed multiple times but never dig to the bottom is replacing dhclient with cloud-init dhcp client in python itself; then Ephemeral would not have to depend on dhclient which may or maynot be present, etc21:33
rharperso, in the agenda, maybe replace wicked string with 'EphermalDHCP alternatives to isc-dhcp client'21:33
rharperwe've the same issue in Artful/Bionic/Cosmic though we pull the dhclient in now; really that shouldn't be in there as networkd procides a dhcp client as well21:34
robjoI added a short summary to bug #173322621:42
ubot5bug 1733226 in cloud-init "cloud-init-local service fails on SUSE distros" [Undecided,New] https://launchpad.net/bugs/173322621:42
robjohaving a cloud-init get_dhcp_lease() is included as option 421:42
smoserblackboxsw: thanks for remembering about the datasource local in bionic.22:04
smoseri think we should bite the bullet there.22:04
blackboxswyeah a quick grep of RELEASE_BLOCKER22:04
blackboxswwe need to retire/remove the snap modules too :/22:05
blackboxswthe old snappy etc.22:05
blackboxswbut not critical22:05
smoseryeah, that snot a big deal.22:05
smoserhm...22:05
* blackboxsw is wondering how best to cherry pick the ubuntu/xenial/debian/patch/openstack* into ubuntu/artful which has no patches dir...22:05
blackboxswwas trying ./debian/cherry-pick, but it falls over because there is no existing debian/patches/series file22:06
blackboxswwondering if I manually do the work in artful and then cherry pick to bionic (which also has no patches subdir/series22:06
smoserhttps://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/34830922:08
smoserthat has fail build right now22:08
smosershoot.22:08
blackboxswbah have to fix unit tests too :/22:09
smoserlets think.22:11
smoserone thing we generally want to do is update the ubuntu/ branches right after we land something like this22:12
smoserso that our daily builds would have been doing this sense it weent in.22:12
* smoser shoudl have remembered that and done something then22:13
blackboxswthe following would work for ubuntu/xenial I think http://paste.ubuntu.com/p/mNNQgwTPcT/22:20
blackboxswit tweaks the unit test which will fail (after debian/patch applied) to present the right ds_config setting True22:20
smoserblackboxsw: i'll give this a good think tomorrow. would like to get an sru upload in, but want to think it though.22:28
blackboxswyeah I was thinking there's probably not enough time to talk through the options.22:29
blackboxswI'll fix xenial so we have a strawman on the approach, to shoot down if need be22:29
blackboxswartful/bionic are bogus, so I'll pull them,22:29
blackboxswok pushed xenial again, will let CI run it's course22:32
blackboxswgotta take a break22:33
blackboxswok xenial mp is at least in good enough shape for discussion about the approach for patching desired openstack behavior https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/34830922:53
blackboxswrharper: do we need to change behavior of ntp/chrony on xenial->bionic with this upcoming SRU?23:21
blackboxswper bug #174972223:21
ubot5bug 1749722 in systemd (Ubuntu) "NTP: take into account systemd-timesyncd where present" [Undecided,New] https://launchpad.net/bugs/174972223:21
blackboxswI think not, but wanted to be sure23:22

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