Somehow have the ability to save previous configuration about lxd-webgui HOT 7 OPEN

If i understand correctly: You have multiple LXD server, and you use LXD-WEBGUI to access "all" of them. But then you have to change the configuration each time?

I can add support for multiple LXD server, each with their own settings, and make it possible to quickly switch between them.

In the mean-time as a quick fix, you can just start multiple LXD-WEBGUI's (e.g. start one python http server on port :8080, one on :8081, one on :8082, ...). The configuration should be unique for each port/instance, so if you access :8080, you it is configured for LXD server 1, on :8081 it is configured for LXD server 2 etc.

from lxd-webgui.

On a side note: You had troubles/problems with setting up lxd-webgui? Can you elaborate? Is it certificate related? I'd like to make installation as easy and straight forward as possible.

from lxd-webgui.

I'll try to explain the context in which we use both lxd and lxd-webui, so that you can understand the use-case and the problems I faced concerning the install of lxd-webui.
We have three network zones, each one has it's own purpose. Our setup include 7 hosts to serve different things.
There are 2 machines per zone, which work in balanced mode.
If I take the example of one of these machines, it hosts an apache2 webserver running as a reverse proxy for each lxc container.
And each container has it's own production environment to serve what it has to serve (own version of apache/php/tomcat/whatever is required).
The 7th machine is on top of all the 6 previous ones and is here for administration/setup.
Exemple taken for lxd-webui :
I set up a lxc container on the administration machine, to make a full install. Your documentation was much appreciated, even though I finaly fall down to have lxd-webui served by apache rather than the simple http-server you present in the readme.
So, on the host, I have the main apache that serves just as a reverse proxy for the lxc container serving lxd-webui.
Since lxd-webui is here to have an overview of all that is running on all machines, it will stay as it is on this "admin" machine.

Now, when I setup a production application, I do the same, and when everything is fine, I use lxc copy to deploy the container on the two machines of the concerned zone, copy the apache2 config files of the host-admin to the apaches that serves as reverse proxy on the two production hosts and the load balancing is configured accordingly to access these two hosts and finaly the two lxd containers.

So, we have 7 lxd hosts machines to manage. lxd-webui is handy and very promising for this purpose.

The only problem I faced, is that on each lxd host I had to create a certificate and add it to the trusted certificate of the lxd process.

I hope my explanations are clear enough :-s

from lxd-webgui.

Wow that's quite a setup you have there, but i'm not sure i understand 100%. But maybe this is already a use-case for enterprise-grade software, like Kubernetes, or other container orchestration software.

Concerning the client certificate: You can create one client certificate (the self-signed cert you have to import in the browser), and add this cert to all LXD hosts as trusted cert. There should be one client certificate per administrator (it is the equivalent to username+password).

Anyway, what you would need is the ability to specify different LXD hosts, and lxd-webgui should use them all at the same time. This way, you can see the state of all containers of the different LXD hosts. E.g. in the container overview: "webserver-1-container @ lxd-zone-1", "webserver-1-container @ lxd-zone2", where lxd-zone1 and lxd-zone2 are two different LXD servers. Is this correct?

from lxd-webgui.

You have fully understood our setup. And indeed, either have each container displayed as you suggest or have the ability to chose the host in a select box would be great !

from lxd-webgui.

I'm also running into this requirement (managing of different LXD hosts) right now. I think i will implement this feature, but it requires quite a bit of work. May take me a few weeks until its done.

from lxd-webgui.

sounds nice feature to have. If i have multiple LXD hosts, it would be nice to use one control panel to show an aggregate of all containers and its associated host with basic filter option to i can limit output to specific host.

from lxd-webgui.