InterWorx-CP 3.0 Release Candidate Available

I was referring to your post here: http://www.interworx.com/forums/showpost.php?p=11847&postcount=4

Backup/restore documents haven’t been synced to the site yet. They will be there before 3.0 goes final.

You translated some, but there were more that were added since the last time you sent us the translation file. You will probably have less to translate than others. :slight_smile:

[root@none ~]# rpm -Uvh http://updates.interworx.com/iworx/RPMS/noarch/v3/RC1/interworx-3.0.1-13.RC1.iworx.noarch.rpm
Retrieving http://updates.interworx.com/iworx/RPMS/noarch/v3/RC1/interworx-3.0.1-13.RC1.iworx.noarch.rpm
error: Failed dependencies:
interworx = 2.1.3-13.iworx is needed by (installed) interworx-siteworx-2.1.3-13.iworx.noarch

Why are you only running the one rpm update?

I think if you look back at Pauls post, there is \ at the end of each filename, thus putting it on a new line, but running on the same command.

I had done that also prior, but it did not work as well. I may have accidently done a “break” by mistake. Now it works. Thanks.

[quote=EverythingWeb;12181]Why are you only running the one rpm update?

I think if you look back at Pauls post, there is \ at the end of each filename, thus putting it on a new line, but running on the same command.[/quote]

Yes, for the clairification of anyone reading this interworx interworx-siteworx and interworx-nodeworx are dependancies of eachother and MUST be installed together (this the long install command).

OMG …

Scriptworx …

omg.

[QUOTE=JayBaen;12187]OMG …

Scriptworx …

omg.[/QUOTE]

I can’t tell if that’s a good or bad thing… :confused: :wink:

Oh – it’s a very good thing …

Cool, good to know. :slight_smile:

I have just mailed out the language changes for 3.0.0 to the list of translators I have on file. The email subject is “InterWorx-CP 3.0 Language Additions”, and I BCC’d everyone just in case anyone had any privacy concerns.

If you were creating a translation for us, and you did not receive an email from me, please contact me as soon as possible, either by forums PM or emailing me at socheat -at- interworx.com and put “translation” somewhere in the subject. I will then get you the information you need.

Dj-grobe, I also sent you the changes as you requested. :slight_smile:

[QUOTE=IWorx-Paul;12168]Hi Pascal,

Regarding the API, unfortunately we weren’t able to get the new API functionliaty in that we wanted to just yet, so no, the birthday / billing date is not setable - although - if you e-mail me what client code you’re currently using, I may be able to help in this area.

Yes, users can add subdomains and pointer domains now in clusters, that limitation has been removed.

Paul[/QUOTE]

Hi Paul

Thanks for the answer

Ok here is the code we use to create a new account using the API.


$message = array(
     'access_key'   => $access_key,
     'account_info' => array (
                  $ai_pseudo,
                  $ai_email,
                  $ai_passwd,
                  $ai_domaine,
                  $ai_ip),
     'features_list' => array (
                 'LG_OPT_STORAGE' => $LG_OPT_STORAGE,
                 'LG_OPT_BANDWIDTH' => $LG_OPT_BANDWIDTH,
                 'LG_OPT_EMAIL_ALIASES' => $LG_OPT_EMAIL_ALIASES,
                 'LG_OPT_EMAIL_AUTORESPONDERS' => $LG_OPT_EMAIL_AUTORESPONDERS,
                 'LG_OPT_EMAIL_BOXES' => $LG_OPT_EMAIL_BOXES,
                 'LG_OPT_EMAIL_GROUPS' => $LG_OPT_EMAIL_GROUPS,
                 'LG_OPT_FTP_ACCOUNTS' => $LG_OPT_FTP_ACCOUNTS,
                 'LG_OPT_MYSQL_DBS' => $LG_OPT_MYSQL_DBS,
                 'LG_OPT_MYSQL_DB_USERS' => $LG_OPT_MYSQL_DB_USERS,
                 'LG_OPT_POINTER_DOMAINS' => $LG_OPT_POINTER_DOMAINS,
                 'LG_OPT_SUBDOMAINS' => $LG_OPT_SUBDOMAINS,
                 'LG_OPT_CGI_ACCESS' => $LG_OPT_CGI_ACCESS,
                 'LG_OPT_CRONTAB' => $LG_OPT_CRONTAB,
                 'LG_OPT_RESOLVE_XFERLOG_DNS' => $LG_OPT_RESOLVE_XFERLOG_DNS,
                 'LG_OPT_SSL' => $LG_OPT_SSL,
                 'LG_OPT_BURSTABLE' => $LG_OPT_BURSTABLE,
                 'LG_OPT_SAVE_XFER_LOGS' => $LG_OPT_SAVE_XFER_LOGS)
                 );

$result = xmlrpc_request( $hostname, '2443', 'https', 'iworx.createaccount', $message, 0 );
        if ($result == "SUCCESS" )
        {
            do the job if success
        } else {
            do the job if unsuccess
        }

There is missing :

For the account_info :

  • Birthday date
  • Language
  • Theme

For the features_list

  • Account backup
  • scriptworx
  • Number of secondary domains

So everytime we create a new siteworx account using the API, we have to manually set the scriptworx option to enable it, define the birthday date. Since the V2 it has been added new features but the API has not been updated. So our self made tool is not completly automatized. With the V3 we will have to manually set the backup option and the secondary domain ?

Maybe it is possible to define a default value in the iworx.ini file ?

Also, Today our self made payment controls tool allow us to automaticly :

  • Create the new account if the payment is OK
  • Suspend an account when a payment failed
  • Unsuspend an account if the payment is done after a failed payment
  • Delete an account 30 days after a deletion ask from the user himself

We also have an automatized process for every users whom upgrade their hosting accounts. The problem is that, yet, there is no API to update an account (features_list). So we have to do this manualy, which take time for us.
Do you plan to add the Update feature to the API ? when ?

I think it is a very important feature and a lot of 3rd party tool like modernbill would like to use it

Thanks

Pascal

[QUOTE=IWorx-Paul;12168]

…/…

Yes, users can add subdomains and pointer domains now in clusters, that limitation has been removed.

Paul[/QUOTE]

So cool !!!

I had too much questions like “the subdomains menu has deasepears !”

Great !!!

Pascal

[QUOTE=Dj-Grobe;12144]Exelent !!! :slight_smile:
few questions…

…/…
5 Iworx site limits continue at 512 sites due apache limits etc etc?

[/QUOTE]

There is a solution for this.

If in you cluster you have few nodes you could define a load balancing for http/https request for only one node.

I mean

You could set only 400 hosts per IP then load balanced every http/https request for one IP to one node only

ie :
All http/https request for IP .001 --> to node 01 (for only 400 hosts)
All http/https request for IP .002 --> to node 02 (for only 400 hosts)
All http/https request for IP .003 --> to node 03 (for only 400 hosts)

etc…

Like this Apache on every nodes will only use 400 file descriptor

(it is what we plan)

Pascal

Pascal, when you use this method. Why would you invest in a loadbalancing system then. The only advantage would be email and mysql on the cluster manager. But for http/https you still use dedicated servers.

-John

Another API question…

In order to automate creation of subdomains in the 2.x API, we had to provision a separate siteworx account using the full subdomain name.

Will the new API allow us to create a subdomain of an existing siteworx account?

The posts above about site limits started me thinking- am I correct in assuming if we can provision these subdomains as part of an existing siteworx account, they will not count towards the 512 site limit?

[QUOTE=hubbadubba;12200]In order to automate creation of subdomains in the 2.x API, we had to provision a separate siteworx account using the full subdomain name.

Will the new API allow us to create a subdomain of an existing siteworx account?

The posts above about site limits started me thinking- am I correct in assuming if we can provision these subdomains as part of an existing siteworx account, they will not count towards the 512 site limit?[/QUOTE]

Yes, this is correct. Subdomains in InterWorx are done via mod_rewrite, so they will all use the same error log/transfer log as the siteworx account they belong to. What this means then is that subdomains added in this manner (in the SiteWorx subdomain menu) won’t have separate stats calculations, bandwidth monitoring, separate quotas etc. It’s all shared/merged with the SiteWorx account they belong to (shares a vhost, shares a docroot, shares log files).

Subdomains that are added as a SiteWorx account are, for all intents and purposes, considered an entirely different site. So, “subdomains” added in this manner will have separate stats, bandwidth monitoring, quotas, docroot, etc, and more importantly, it’s own vhost conf file, which means it will contribute towards the number of open files Apache uses.

[QUOTE=johnbrand;12199]Pascal, when you use this method. Why would you invest in a loadbalancing system then. The only advantage would be email and mysql on the cluster manager. But for http/https you still use dedicated servers.

-John[/QUOTE]

What I say it per server you can have up to 500 siteworx accounts. You can load balance these requests over few nodes. We personaly use the cluster manager as mysql server only and load balanced the email through all nodes and http request to few nodes, but in fact no more than 400 per node. Like this we have a central point of management, so a central point of backups. We work on a solution to also create a load balanced for mysql (mysql cluster).
Also it allows us to repartitate the accounts that use a lot of ressources to a special node.

We prefer to have a cluster than x nodeworx that manage their accounts.
We just hope that in a next release it will be possible to have an external mysql server (and create a mysql cluster). Like this we will be able to grow and have a “coherent architectur”.

With this architecture you have some boxes that only do HTTP/HTTPS, others that only do Email and others that will do MySQL only.

For example today on our nodes we have a load average of 1.00-1.50 with http requests only, on the node we have a load average of 2.00 2.50 with mysql and NFS only. If we didn’t have a cluster we would have to buy more boxe that now (most of this it’s because some accounts have a very intensive usage of the ressources. With this solution it has been easy for us to repartitate these accounts on some nodes, and others accounts on others)

Also the cluster allow us to set off a node without set off the uptime. We just have to load balanced the requests of the maintenance node to another node

Pascal

Paul or socheat

About this http://www.interworx.com/forums/showpost.php?p=12195&postcount=31 :

Do you plan to add these missing params in the API ?

At least, is there a way to define a default value for these params in iworx.ini ?

About secondary domains, by default if we create a new account using the API will it be set to 0 ? And for existing accounts, secondary domains is set to 0 by default ?

Thanks

Pascal

[QUOTE=IWorx-Socheat;12191]I have just mailed out the language changes for 3.0.0 to the list of translators I have on file. The email subject is “InterWorx-CP 3.0 Language Additions”, and I BCC’d everyone just in case anyone had any privacy concerns.

If you were creating a translation for us, and you did not receive an email from me, please contact me as soon as possible, either by forums PM or emailing me at socheat -at- interworx.com and put “translation” somewhere in the subject. I will then get you the information you need.

Dj-grobe, I also sent you the changes as you requested. :)[/QUOTE]

Socheat

Could you please PM the the languages changes for 3.0.0.

I have a mail problem and I didn’t receive it

Thanks

Pascal

Hi Pascal,

There is actually a new API interface to the createaccount function.

You should be able to use either of these two examples to get what you want in the createaccount feature. Note that in the below example the section for secondary domains is referred to as LG_OPT_SLAVE_DOMAINS.

The other interface (that you’re currently using) still works also.


$message = array(
    'apikey' => $access_key,
    '_client_version' = 2.0,
    'account' => array( 
        'domain' => $ai_domaine,
        'ipaddr' => $ai_ip,
        'billing_day' => $ai_birthday,
        'nickname' => $ai_pseudo,
        'email' => $ai_email,
        'password1' => $ai_passwd,
        'language' => 'fr',
        'theme' => 'interworx',
        'package_name' => 'package name'
    )
);

OR

$message = array(
    'apikey' => $access_key,
    '_client_version' = 2.0,
    'account' => array( 
        'domain' => $ai_domaine,
        'ipaddr' => $ai_ip,
        'billing_day' => $ai_birthday,
        'nickname' => $ai_pseudo,
        'email' => $ai_email,
        'password1' => $ai_passwd,
        'language' => 'fr',
        'theme' => 'interworx',
        'options' => array(
            'LG_OPT_STORAGE' => $XXX,
            'LG_OPT_BANDWIDTH' => $XXX,
            'LG_OPT_EMAIL_ALIASES' => $XXX,
            'LG_OPT_EMAIL_AUTORESPONDERS' => $XXX,
            'LG_OPT_EMAIL_BOXES' => $XXX,
            'LG_OPT_EMAIL_GROUPS' => $XXX,
            'LG_OPT_FTP_ACCOUNTS' => $XXX,
            'LG_OPT_MYSQL_DBS' => $XXX,
            'LG_OPT_MYSQL_DB_USERS' => $XXX,
            'LG_OPT_POINTER_DOMAINS' => $XXX,
            'LG_OPT_SLAVE_DOMAINS' => $XXX,
            'LG_OPT_SUBDOMAINS' => $XXX,
            'LG_OPT_BACKUP' => $XXX,
            'LG_OPT_CGI_ACCESS' => $XXX,
            'LG_OPT_CRONTAB' => $XXX,
            'LG_OPT_RESOLVE_XFERLOG_DNS' => $XXX,
            'LG_OPT_SCRIPTWORX' => $XXX,
            'LG_OPT_SSL' => $XXX,
            'LG_OPT_BURSTABLE' => $XXX,
            'LG_OPT_SAVE_XFER_LOGS' => $XXX
        )
    )
);


The edit account feature you describe doesn’t exist yet, but I agree it’s important, and it’s high on my list.

Paul