----- Oryginalna wiadomość -----
> Od: "Roberto De Ioris" <[email protected]>
> Do: "uWSGI developers and users list" <[email protected]>
> Wysłane: niedziela, 6 marzec 2011 19:34:06
> Temat: Re: [uWSGI] uWSGI 0.9.7-beta1 - emperor
> 
> Adding those kind of variables (based on the content of the file
> itself)
> it will be very hard. But i understand your problem.
> 
> I have added the %v variable (it point to the vassals dir).
> 
> The "id" concept is already used in xml files, i would like to find a
> way
> to use it in emperor.
> 
> Another useful feature (i will add it in 0.9.7.1 for sure) will be a
> "glob" style vassal dir
> 
> ./uwsgi --emperor /home/*/www/*/wsgi.ini

digging through recursive directories such as ini files is a problem that often 
I copy these files, and there are more than enough. It seems to me that better 
control is to be a directory of configuration files is different from the 
project files.

> 
> Whenever a user put a wsgi.ini in a special directory in his/her home
> the
> emperor will spawn a new instance. (problem 1 of hosting/clouding
> services
> is solved).
> 
> Another set of features will be limiting new instances to avoid
> unprivileged users to do all sort of mess.
> 
> Something like:
> 
> --emperor-uidgid (this will set uid and gid based on the config file
> owner)
> 
> --emperor-limit-as (will limit the address space of instances)
> 
> (problem 2 solved)

These functions are a good idea and all of which are already implemented. I 
only need a better transmission of the variables.

> 
> But the real killer feature will be remote spawn of instances.
> 
> On a server (for example the server where you run a kind of control
> panel
> for your users) you write the config files. The emperor on this
> server see
> them and talk with a "emperor-agent" running on another node that
> will
> spawn it (obviously you can run the agent on multiple servers to
> allow
> auto-clustering).
> 

Even a little bit and You do the whole cloud software :]

Interesting concept. You can practically do it already:
If the worker will overwrite its own configuration file will be restarted with 
more or fewer workers.
Just transmit a message between servers.

A little afraid that uWSGI getting too complicated.
I acknowledge the principle of KISS (keep it simple...).
And I'm not talking about a multitude of options available.


-- 
Łukasz Wróblewski
http://www.nri.pl/ - Nowoczesne Rozwiązania Internetowe
http://www.hostowisko.pl/ - Profesjonalny i tani hosting
http://www.katalog-polskich-firm.pl/ - Najlepszy darmowy katalog firm
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to