[18:33] <blackboxsw> rharper: what's the best way to test this https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/328800
[18:33] <blackboxsw> kvms?
[18:33] <rharper> net-convert
[18:34] <rharper> basically what the unittest is doing
[18:34] <blackboxsw> true ok.
[18:34] <blackboxsw> I have a branch for net-convert as cloud-init devel subcommand that we can look at after I get that analyze in shape.
[18:35] <rharper> yeah, I really should see about doing v2 passthrough to targets that can render netplan
[18:35] <rharper> otherwise, I'll keep finding incompatiblities where we map v2 into v1 for network_state, but miss something
[18:35] <rharper> however, we still want the v2 to v1 mapping for v2 -> non-netplan rendering
[20:08] <blackboxsw> rharper: approved  https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/328800 take inline comments as you will.  :) onto curtin
[20:21] <rharper> blackboxsw: thanks, I'm going to push an update to that to handle passing through the original configuration if it's in v2 format when netplan is the renderer;  this avoids alot of v2 to v1 back to v2 conversion issues
[20:22] <blackboxsw> will watch for that
[22:21] <blackboxsw> rharper I don't see any readthedocs content from uson using cloud-init on the commandline. Am I missing something or is it worth a section describing cmdline client usage?
[22:21] <blackboxsw> which would pull in cloud-init analyze too
[22:21] <rharper> I don't think there are any, but things like running cloud-init single would be super useful
[22:22] <blackboxsw> Yeah, I thought so given we sometimes point folks (or some of our SRU validation scripts)  at using that as a test/validation framework
[22:22] <rharper> yeah