Posts by Nuxwin

    The main problem with the current version is that all objects (domain, dns, mail) are considered as an unique entity. We shouldn't redo the same error here. So, when a domain is added, if setup of one object (DNS, mail...) that compose the entity fail, the recovery process should only take care of what that was failed... For that we will have to provide a error management per object (Mail, DNS ...) status. Since the data in GUI are normalized, that will change nothing the main database. Only error notification will be sent to the administrator/reseller. And then, the administrator have to take care only about errors per object and not to regenerate all the configuration.... Sure, an specific per object debug interface should be provided too.

    Note: Sorry for my poor english here, Hard for me to explain who I see the concept.

    Hello friends ,

    First, sorry for the delay:

    I post here a little discussion that is linked to the both Joximu and kassah proposals:

    <nuxwin> I'm very tired with the current version
    <nuxwin> very shit
    <nuxwin> we will adopt joximu idea to start new version from scratch
    <nuxwin> to resume
    <nuxwin> data are added in GUI database but
    <sci2tech> engine do shit, gui just write in database?
    <nuxwin> GUI do nothing more
    <nuxwin> yes
    <nuxwin> with event handler for queue job
    <nuxwin> sound like scheduled tasks for each servers
    <sci2tech> ok from me. but there are some problems with this ftp as sql management. but can be done
    <nuxwin> I explain to you, imagine the following:
    <nuxwin> I've only GUI and database on one server
    <nuxwin> on other server, I've services such as Apache, php, ftp..
    <nuxwin> and on other, I've Database server for customers
    <nuxwin> and on other, I've mail service ....
    <nuxwin> Imagine now I adds a mail account from the GUI
    <nuxwin> then, the GUI will just adds the relevant data in GUI in normalized way
    <nuxwin> and will add ADD_MAIL event in queue
    <nuxwin> and then, he will notify all servers
    <nuxwin> then, all servers will look at the queue to see if he have awaiting task
    <nuxwin> and do it if yes
    <nuxwin> So, what you think about that ?
    <nuxwin> Hard to explain but I think you got the idea
    <nuxwin> so on, for example, the mail server will run this own engine part for mail
    <sci2tech> yes
    <nuxwin> take the data in the database
    <nuxwin> and then, will add the account data like he want
    <nuxwin> About customer Database now
    <nuxwin> the GUI will only add relevant data for new database and user in normalized way too
    <nuxwin> but will not create the database and user
    <nuxwin> instead of that, he will adds event in queue
    <nuxwin> such as ADD_SQLD and will notify the servers for event
    <nuxwin> and then, the server for database will do the job
    <nuxwin> but ok, still the problem of SQL users linked to the databases
    <nuxwin> BTW, we should fin a way to link user to customers databases
    <nuxwin> but you got the idea ?
    <nuxwin> by doing like this, for example, if one user want not use the daemon at all, h ecan!
    <nuxwin>I mean, he can just add cron task on each servers to look at event queue sometime, and then do the job if one is scheduled...
    <nuxwin> you got the idea ?
    <sci2tech> yes
    <sci2tech> but for service
    <nuxwin> what you don't understand ?
    <sci2tech> Mysql will be same for all servers?
    <nuxwin> in fact Mysql for the ispCP GUI database yes
    <nuxwin> but with the idea we can have more than one mysql server for customer's databases and also, service such as Proftpd can have this own database on main Mysql server or another server..
    <nuxwin> but right all services server will take data and see queue from same SQL server
    <nuxwin> btw: (The Mysql server that host the GUI database)
    <sci2tech> if all servers take data from same server for ftp
    <nuxwin> what about ftp
    <sci2tech> ftp read data directly from db for connection
    <nuxwin> ok I explain
    <nuxwin> for ftp
    <sci2tech> why wait engine to add this data when GUI can do it faster?
    <nuxwin> because with that user can use easily other ftp server than proftpd
    <nuxwin> I explain
    <nuxwin> 1. The GUI will only store username and password and mount_point for ftp account in normalized way
    <nuxwin> and will add event such as ADD_FTP in queue
    <nuxwin> then, the server in charge of FTP service will look at the queue and see a task for him and then, he will launch this own script to adding ftp account
    <nuxwin> he will transform data FROM GUI like he want. He can store it in flat file or in specific database (like he want...). That allow also to use other Ftp server than proftpd as long plugin for engine is provided. Same concept for all other services sucha as postfix, courier....
    <sci2tech> ah ok
    <sci2tech> right
    <sci2tech> this way we can use server that do not use Mysql ;)
    <nuxwin> yes
    <sci2tech> this way we can use ftp server that do not use Mysql ;) but plain file
    <sci2tech> ok agree with that
    <nuxwin> yes
    <sci2tech> also we can split databases over multiple Mysql servers
    <nuxwin> yes
    <sci2tech> ok. joximu proposal has my support
    <nuxwin> hehe
    <nuxwin> Will report our discussion
    <nuxwin> in the forum to show joxi
    <sci2tech> great
    <nuxwin> we have understand
    <nuxwin> I've only add the kassah event handler proposal here
    <sci2tech> great
    <sci2tech> love this 2 guys
    <nuxwin> yeah