-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define iso storage on CloudInit #119
Comments
the cloud init func takes care of this for you: https://github.com/luthermonson/go-proxmox/blob/main/virtual_machine.go#L143-L146 |
i guess im also confused as to what youre trying to even do, are you naming your iso storage "templates" some how? there is no support for any storage types besides |
@luthermonson |
can you show me the contents of |
so it's not random by the way, it loops over storage results returned from this endpoint and chooses the first one which is allows the content type of "iso", the logic is here: https://github.com/luthermonson/go-proxmox/blob/main/nodes.go#L202-L211 we could allow for allowing the storage to be passed in or filtered differently... show me the output and let's see what we can work with |
The "qnap" and "templates" storages can store iso in my case. But for store cloud-init isos I prefer to use only storage named "templates" because that storage is more reliable than "qnap".
Some temporary storages may store the iso for some maintenance/debugging. There is another problem here. Sometimes CloudInit tries to use storage "local" or "cephfs", which is disabled.
|
oh ya i could imagine it might appear random is the proxmox api sometimes return results in different orders. it's only picking storage that CAN have isos and it just so happens you have 2 that are disabled and the one it tries it never gets too... let me think about this for a bit and try and get a local setup that looks similar |
Hi!
How to define storage for CloudInit function?
I'm trying to use context.WithValue something like
but without success.
What am I doing wrong?
The text was updated successfully, but these errors were encountered: