-
Notifications
You must be signed in to change notification settings - Fork 36
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
Allow additional simplestream remotes via the ui #410
Comments
Thank you for the request. You can use a custom image server and select a custom image via the YAML input of the instance launch in the UI (see attached screen below). I understand that is not the "full support" one would expect from a UI. We are planning to add custom ISO image upload and usage for new instances in some weeks. I think it makes sense to address the custom simplestream support at the same time. Both touch the image selection on instance creation. One problem with custom image servers is they don't provide a list of images. So the UI can render two text inputs for 1. server address and 2. the image. I like the idea of using |
neat! I failed to realize that wasnt hard coded to the Canonical/Linux Containers simplestreams
From my understanding of how simplestreams works, it does in the Otherwise just another API endpoint on LXD itself to return the global remotes and allowing the UI to parse the simplestreams from that would make more sense in the long term I think of allowing configuring additional remotes |
Unfortunately in its current state, the web ui only allows for the Ubuntu and LinuxContainers simplestreams to be accessible via the web ui. It would be nice if there was some way to allow additional remotes to be used. This then could also expand to have a remote dropdown in the ui when selecting an image.
I had a few ideas. The first would be based on a
user.*
config setting on the current project the user is attempting to make the instance in. The config setting could be something similar touser.remote.0: https://mysimplestream.remote.com
where we can infinitely create additional remotes. You could also define a remote's name viauser.remote.0.name: mysimplestream
The other idea was to use the global remote's settings via the lxd api* so then the additional remotes could be accessed from the web ui.
*
- would have to be implemented to core lxd apiThe text was updated successfully, but these errors were encountered: