Nocloud/OVF seedfrom vendordata #570
Conversation
cloudinit/util.py
Outdated
| try: | ||
| vd_resp = url_helper.read_file_or_url(vd_url, timeout=timeout, | ||
| retries=retries) | ||
| except url_helper.UrlError: |
There was a problem hiding this comment.
I think we should log here that there was an url error when reading the vendor-data
| except url_helper.UrlError: | ||
| pass | ||
| else: | ||
| if vd_resp.ok(): |
There was a problem hiding this comment.
same thing here in case we receive a response that is not ok
jqueuniet
force-pushed
the
nocloud_seedfrom_vendordata
branch
from
2fdf55f
to
a5fd244
Compare
|
I added some basic logging, but not sure if the messages are good enough, or if I can add something else. |
Test that we can add optional vendor-data to the seedfrom file in a NoCloud environment
Test that we can add optional vendor-data to the seedfrom file in a NoCloud environment
|
As it doesn't seem nocloud can parse meta-data for network, would it be also possible to have NoCloud also pull the network-config file from url as well? |
|
This is probably not the right place to talk about this as this PR is long closed, but a functional network is a prerequisite for URL fetching. This was an issue for us as we use iPXE network boot on diskless bare-metal, and in the end the only feasible option in this scenario is passing the network-config as a kernel cmdline argument. |
|
Agreed regarding the place, but I couldn't find where to send an email to bring it up offline. :) Happy to talk about it elsewhere. I can be reached at yahoo, same name. Thanks |
well... other datasources can and do get networking information over the network. They assume "dhcp on first network devcie" and then get the fuller network config. |
|
FYI, I'd love to have just put this in as an issue instead of tagging a relevant PR, but that tab seems to be missing on this github project. @smoser Hey Scott. Haven't talked with you since working on lxc/lxd. Currently using vmware ovf to install a seedfrom. The method of using a cd passed with meta-data, etc is doable, but sloppy, even with bash/govc/cloud-init, and is certainly slower than over the net. Seedfrom does work decently for grabbing user and vendor, but networking has to resort to a write-files of the network config, as well as a network: config-disabled to remain persistent across reboots. Sadly VMware really hasn't put any effort into making cloud-init work well through vsphere. I've looked a lot, but any straight forward methods that don't require create an ISO and attaching has eluded me to date. Current setup: Ideal |
|
It would definitely be doable to have NoCloud operate entirely at "local" timeframe and just do the it'd be neat. |
|
@smoser if I understand what you're saying correctly, its the feature of adding a static route through the dhcp.py(?) for an address such as 169.254.169.254 to reach a web server. I could certainly see this working. The things that come to mind are, in an environment like EC2, etc, the local router is actually a software router with additional services, that captures the requests, and by querying IPAM, knows who the client is supposed to be and forwards it to an instance that provides the host specific data. Unless running on a cloud-stack, or it looks like nsx-t might also provide that service, then the issue is how to know which device it is from vsphere(I include the host name as part of the seedfrom url, with mod_rewrite redirect to a generic user-data if not found) and route to the correct meta/user/vendor instance, and of course, the formatting for network config per the environment. My current method does work decently, it's just that hang up of write_files for config that seems so kludgy. My python is extremely limited, as I just started learning it for some basic scripting. (I used python to automate a remote-trigger blackhole with exaBGP, to update bogons, martians, known c&c networks etc from online sources like team cymru, etc). |
Issues for cloud-init are tracked on Launchpad |
This PR modifies the
util.seedfromhelper function to query optional vendor-data. I started with the idea of implementing for NoCloud, but as OVF is using the same helper, I figured it would be easier to do it for both.