Open reith opened 3 years ago
I pushed some unpolished work you can see here. I have no idea about codes trying to handle legacy and new API and my code lacking those. It works for Windows server 2019 at least.
Hi,
I would appreciate any thoughts or suggestions about this. Is it totally out of scope of this project? in that case it would be nice to document that cloudbase-init does not handle static routes, except for default gateway. Do you think it's good to cover static routes like cloud-init do?
I love to have this functionality in cloudbase-init rather than our private fork that would diverge us from upcomming developments and I should reach a decision at some point.
Hello,
Thank you for the contribution. Currently, we use the OpenStack review/gating for the patches, and Github for issue management. Can you add the patch to https://review.opendev.org/?
Here is a good how to for achieving this: https://www.openstack.org/blog/submit-your-first-openstack-patch-in-three-steps/ https://docs.openstack.org/zaqar/latest/contributor/first_patch.html - you need to replace zaqar with cloudbase-init.
I would gladly get the code that you wrote and put it to gerrit, but because of how licensing works, you are required to sign the CLA.
Thank you,
Hi,
I'm provisioning a Windows image by ConfigDrive with bellow
openstack/latest/network_data.json
:I expect a route to
172.19.2.0/24
being set, but it's all I'd get in Windows:I read openstack and configdrive tests and looks
routes
being parsed correctly but I don't see any test targeting routes incloudbaseinit/tests/osutils/test_windows.py
and they are all about static network address setting. Further investigation showedNetworkConfigPlugin
itself just set network interface IP addresses and consequently just local routes. There isadd_static_route
function but looks it's unrelated to my case which datasource is ConfigDrive.So IIUC ConfigDrive Network Routes are being ignored now. Am I right?