InterWorx-CP 3.0 Release Candidate Available

[IWorx-Paul]

NOTE: The RC1 testing period is now over. RC2 is now available here: http://interworx.com/forums/showthread.php?p=12316

This thread is now locked, and the RPMS below can no longer be downloaded, please use the RC2 thread an RPMS from this point forward.


We're happy to announce that InterWorx-CP 3.0 RC1 is now available for download and testing.

Some of the new features include:

* Improved Reseller support

* Improved ScriptWorx Script Management System

* New DNS Record template system

* Multi-domain management through SiteWorx (called Secondary Domains)

* New mail filter and Spam management tools in SiteWorx

* .htaccess file Directory Options interface in SiteWorx

* Supporting software updates (Horde, squirrelmail, phpMyAdmin)

For those of you who would like to help out by testing and reporting any problems you discover, the RC1 RPMS are available online here:

http://updates.interworx.com/iworx/RPMS/noarch/v3/RC1

You can upgrade an existing InterWorx 2.1.3 server with the following command:

rpm -Uvh http://updates.interworx.com/iworx/RPMS/noarch/v3/RC1/interworx-3.0.1-13.RC1.iworx.noarch.rpm \
http://updates.interworx.com/iworx/RPMS/noarch/v3/RC1/interworx-nodeworx-3.0.1-13.RC1.iworx.noarch.rpm \
http://updates.interworx.com/iworx/RPMS/noarch/v3/RC1/interworx-siteworx-3.0.1-13.RC1.iworx.noarch.rpm


Feel free to discuss any problems you run into here in this thread, or by e-mailing upgrade@interworx.com. If you need to get our attention as quickly as possible, opening a support ticket is the best method.

If you are installing this release on an InterWorx-CP cluster, the RPMS must be updated on all servers in the cluster. While not strictly necessary, we recommend you update the RPMS on the cluster manager server first, followed by each node in the cluster.

Note: This release (RC1) will NOT automatically update to your server. If you want to install and test it, manual intervention is required (see above).

Note: Upgrading to this release is not something you will be able to quickly or easily back out of. One of the worst things you could do if you run into a problem would be to panic and uninstall any or all of the InterWorx RPMS. Do not do this. If you have a critical problem, open a support ticket with us first.

Note: While we do feel this is a fairly stable release candidate, don't forget it is a release candidate release. It's possible you'll run into a problem here and there. However, we do not expect there to be any MAJOR issues that will affect the critical operations of your server. This release has undergone vigorous internal testing to squash virtually all medium- and large-sized bugs.


Thanks in advance to any and all testers!

Paul

[blahrus]

Ohhhhhh THANK YOU!!!!!!!!!!!!!!!!!!!!!!!

[pascal]

Hi

Really happy to know the V3 is released.

Few questions :
- What about the improvments about the API ? is there a new doc ? does all data of an accoount is now integrated in the API (birthday date, scriptworx, .etc) ?
- What about the improvments with the cluster manager ? with a "lan" cluster ? does the upgrade is special with a cluster on a Lan ?

Thanks for your answer

Pascal

[Dj-Grobe]

Exelent !!! :)
few questions.......

1 This its considered stable to install right now on production servers?

2 Sapnish langauge its available?

3 Its 100% compatible with modernbill iworx module?

4 I have pho 5.2 installed, this not create any interference?

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

6 install just need run this rpms? anyother task needed?

7 the backup its mproved? have interworx some feature for make complete bacup inluded resellers accounts and then restore all, without have create resllers manually?

8 its improved the way how iworx create on siteworx, the mail HD usage reports? improved for down the cpu usage that task create?

9 now interworx have dns tempate system available so i think can add in automatic way spf records, have some way to udate spf record in all sites already created?

10 how its improved the spam detection?


Please i apreciate if can repply this questions and if can make public more detailed info of this new version.

: )

[IWorx-Socheat]

Hi

Really happy to know the V3 is released.

Few questions :
- What about the improvments about the API ? is there a new doc ? does all data of an accoount is now integrated in the API (birthday date, scriptworx, .etc) ?

API documentation hasn't been updated. A lot of the things you saw from the API error codes are simply used by the current API functions, to improve error reporting, or are currently internal API functions used between boxes in a cluster.

- What about the improvments with the cluster manager ? with a "lan" cluster ? does the upgrade is special with a cluster on a Lan ?

Yes, you now have the option of putting the Quorum IP on a different primary interface. What this means is if you have two network cards, eth0 and eth1, you can choose to put the Quorum IP on eth1. However, the Quorum IP still *MUST* be the primary IP on the interface. It can not be placed on eth0:0 or eth1:4, it must be the IP on eth0 or eth1.

[IWorx-Socheat]

1 This its considered stable to install right now on production servers?

It's a release candidate, so installing on a production server is at your own risk. See Paul's last note in his original post.

2 Sapnish langauge its available?

I will be sending out a language diff of the new 3.0 entries to our translators shortly.

3 Its 100% compatible with modernbill iworx module?

As Paul stated here, we don't foresee any compatibility issues:
http://www.interworx.com/forums/showthread.php?t=1986

4 I have pho 5.2 installed, this not create any interference?

No, it should not cause any troubles.

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

Yes, this is an Apache limit, and the limit remains.


6 install just need run this rpms? anyother task needed?

Following Paul's instructions is all you need. There is an upgrade script that automatically gets run when you follow his instructions.

7 the backup its mproved? have interworx some feature for make complete bacup inluded resellers accounts and then restore all, without have create resllers manually?

Yes, to both questions. Reseller info is now backed up into each account backup. When you import the account in NodeWorx, you have the option of choosing the reseller you want to import the account under, or tell NodeWorx to create the reseller that's stored in the backup file.

8 its improved the way how iworx create on siteworx, the mail HD usage reports? improved for down the cpu usage that task create?

Not exactly sure what you're asking about here?

9 now interworx have dns tempate system available so i think can add in automatic way spf records, have some way to udate spf record in all sites already created?

DNS templates have been added, to allow you to automatically create SPF records (and other DNS records) automatically for new accounts. There is *not* a means to go back and update already existing accounts.

10 how its improved the spam detection?

InterWorx doesn't directly have anything to do with spam detection, that's SpamAssassin's job. However, more spam control features have been added to SiteWorx (for example, allowing the SiteWorx account user to choose if mail should be tagged, delivered to a spam folder, or deleted automatically).

[Dj-Grobe]

Thankyou for your repply:

Forgot about answer 8 : )


well i just need the translation tos psanish, after that its not available, imagine i cant upgarde, at this moemnt all servers have spanish translation i cant quit that feature....some idea when spanish file be available?

i hoppe soon.

[IWorx-Socheat]

well i just need the translation tos psanish, after that its not available, imagine i cant upgarde, at this moemnt all servers have spanish translation i cant quit that feature....some idea when spanish file be available?

I will send out the language diffs today, but our translators are InterWorx clients who have graciously volunteered their time and knowledge, so it'll be done as soon as they each can complete it. Would you like me to send you the language diffs as well?

[Dj-Grobe]

Shure, sendme, please !! : )

[R-n-R]

Well this is good news! For those that do not have the equipment, nor the time to test the RC candidate, is there a demo install someplace so that we can look around and get familiar with the new features?

[docpeyer]

I agree, a demo site would be great... would answer a lot of questions for everybody I think. I have a few questions that I won't bore you with, but would be nice to check out for myself.

[Dj-Grobe]

yep demo site be cool : )

another question ineterworx have now choose screen when cusotmer sopen /webmail?
They now see the 2 options avilable? :)

[IWorx-Socheat]

InterWorx v.3 release candidate demo up! :)

https://demo-iworx3.interworx.com:2443/nodeworx/

NodeWorx login:
username: demo-iworx3@interworx.com
password: demo

SiteWorx login:
username: demo-iworx3@interworx.com
password: demo
domain: demo-iworx3.interworx.com

[WebXtrA]

I have installed the RC on a VPS and have a few questions:

1. is there a bandwidth history for siteworx accounts? (also the past month so I don't have to check every last day of the month if somebody went over his limit)
2. Related to #1: Does the reseller/server admin get an email when a siteworx account goes over his limit?
3. Scriptworx: I assume that the scripts come later ;)

That's it for now ;)

[IWorx-Paul]

I have installed the RC on a VPS and have a few questions:

1. is there a bandwidth history for siteworx accounts? (also the past month so I don't have to check every last day of the month if somebody went over his limit)
2. Related to #1: Does the reseller/server admin get an email when a siteworx account goes over his limit?
3. Scriptworx: I assume that the scripts come later ;)

That's it for now ;)

1. Yes, there's indeed bandwidth history for SiteWorx accounts (in Siteworx under Stats), and Bandwidth History for Resellers also (in NodeWorx under Resellers).
2. No, the admin doesn't get an e-mail at this point. But I agree they should.
3. Scripts should be listed in the ScriptWorx section of NodeWorx - you have to download and enable the scripts you want available to SiteWorx users.

Paul

[pascal]

API documentation hasn't been updated. A lot of the things you saw from the API error codes are simply used by the current API functions, to improve error reporting, or are currently internal API functions used between boxes in a cluster.


Sorry but I don't understand what you mean. I speak about API features, not error code (I don't see error code that I don't understand :) )

For example.

In the siteworx.createaccount there is no variable for the birthday date and to enable/disable scriptworx : Do these variables have been added ?

Today you can't modify an account from the API, is it possible now ?

See this post and what Chris told me about these questions
http://www.interworx.com/forums/showthread.php?t=1274

Pascal

[pascal]

About the V3 and the cluster :

-1- Does the users can add some subdomains from siteworx ?
-2- What about the domain pointers ?

Pascal

[pascal]

Quote:
Originally Posted by Dj-Grobe View Post
7 the backup its mproved? have interworx some feature for make complete bacup inluded resellers accounts and then restore all, without have create resllers manually?
Yes, to both questions. Reseller info is now backed up into each account backup. When you import the account in NodeWorx, you have the option of choosing the reseller you want to import the account under, or tell NodeWorx to create the reseller that's stored in the backup file.

Where could we find the doc for this ?

Also could you please send me the diff language file to allow me to add all V3 sentences in FR (I thought it what we've already done)

Thanks for everything

Pascal

[IWorx-Paul]

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.

-1- Does the users can add some subdomains from siteworx ?
-2- What about the domain pointers ?
Yes, users can add subdomains and pointer domains now in clusters, that limitation has been removed.

Paul

[IWorx-Paul]

I'm not sure if all the docs for the new backup params are completed yet, I'll let Socheat answer that one.

Paul

[IWorx-Socheat]

Sorry but I don't understand what you mean. I speak about API features, not error code (I don't see error code that I don't understand )
I was referring to your post here: http://www.interworx.com/forums/showpost.php?p=11847&postcount=4

Where could we find the doc for this ?

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

Also could you please send me the diff language file to allow me to add all V3 sentences in FR (I thought it what we've already done)

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. :)

[cabizeid]

[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

[EverythingWeb]

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.

[cabizeid]

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.

[IWorx-Tim]

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.

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).

[JayBaen]

OMG ...

Scriptworx ...

omg.

[IWorx-Socheat]

OMG ...

Scriptworx ...

omg.

I can't tell if that's a good or bad thing... :confused: ;)

[JayBaen]

Oh -- it's a *very good* thing ...

[IWorx-Socheat]

Oh -- it's a *very good* thing ...

Cool, good to know. :)

[IWorx-Socheat]

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. :)

[pascal]

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

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

[pascal]

.../...

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

Paul

So cool !!!!

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

Great !!!!

Pascal

[pascal]

Exelent !!! :)
few questions.......

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



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

[johnbrand]

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


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

[hubbadubba]

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?

[IWorx-Socheat]

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?

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.

[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

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

[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

[pascal]

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. :)

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

[IWorx-Paul]

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

[hubbadubba]

Thanks for the explanation, Socheat.

Yes, this is correct. Subdomains in InterWorx are done via mod_rewrite...
Can the new API be used to add a subdomain? If not, would a php script that edits the virtual host file with the appropriate mod_rewrite syntax and creates a folder for the subdomain be sufficient to automate the subdoamin proccess? Or is there more to it than that?

[Justec]

Glad to see the new maildrop file including non SMTP drop functionality that I had hacked into the 2.x version :)

One thing I was thinking about doing to this version is checking if IW_DEFAULT_TO = "delete" and if the email did not have a good IW_VHOME or IW_VALIAS then just exit?

Not sure how much more efficient it would be to do that in maildrop vs just letting vpop do it, but I get a lot of mail sent to fake domains and have turned of bounce for a few of the domains on my box.

[Sander]

Will this new release also support new operating systems like Fedora Core 6?

[iFLEXMEDIA]

Is there also an installation script available that we can use to install the RC1 on a clean system?

Regards,
Wesley

[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.


Great !!! thanks a ton !

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

Paul

Cool !

It's true that if it exists, siteworx accounts will be 100% manageable with the API, which is a great thing !

Thanks a lot Paul

Pascal

[pascal]

Hi Pascal,

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



'LG_OPT_SCRIPTWORX' => $XXX,


Paul

The 'LG_OPT_SCRIPTWORX' => $XXX takes the values : true / false ?

Pascal

[pascal]

Hi

Does Nodeworx send email alerts to sysadmin and/or siteworx accounts (when disk space reached, Bandwidth limit reached, etc ) ?

Do you have re-added the email alerts template (ths feature did exist in older version) ?

Pascal

[IWorx-Socheat]

Thanks for the explanation, Socheat.


Can the new API be used to add a subdomain? If not, would a php script that edits the virtual host file with the appropriate mod_rewrite syntax and creates a folder for the subdomain be sufficient to automate the subdoamin proccess? Or is there more to it than that?

There's a little more to it than that. You'll also need to create a DNS CNAME record for it, and we also populate an internal table of domains that were added via the SiteWorx interface (i.e., pointer domains, subdomains, secondary domains, etc) so that we know which domains are "managed" by SiteWorx. So, I wouldn't recommend adding subdomains in this manner.

[IWorx-Socheat]

The 'LG_OPT_SCRIPTWORX' => $XXX takes the values : true / false ?

Pascal

Yes, that is correct.

[IWorx-Socheat]

Hi

Does Nodeworx send email alerts to sysadmin and/or siteworx accounts (when disk space reached, Bandwidth limit reached, etc ) ?

Do you have re-added the email alerts template (ths feature did exist in older version) ?

Pascal

No, we have not re-added the email template system to v.3, bu, it's still there in the background (for example, for SpamAssassin emails and backup emails). It will be re-added at some point.

[pascal]

No, we have not re-added the email template system to v.3, bu, it's still there in the background (for example, for SpamAssassin emails and backup emails). It will be re-added at some point.

Ok Thanks Socheat.
Looks like there is less than I thought in this so waited release :-) but for me there is the most important (subdomains and pointer domains in the cluster; theme for reseler, api for reseler ? ; and the dns zone in siteworx)

Ok so I can enbale the alert in iworx.ini an change the template in the iworx database ?

Pascal

[pascal]

... but for me there is the most important (subdomains and pointer domains in the cluster and the dns zone in siteworx)


Oups there is no dns edit in siteworx.

About reselers and themes, It is now possible to define a theme for a reseler when we create a new reseler account, and it seems it is now possible for a reseler to define its own theme, right ?

I have also seen that now in the reseler panel there is an option for the key API. Does it means a reseler will be able to use the API ?
Could you please tell me more about this ?
Is there some restrictions ? security tests ?

I ask this because in the v3 demo it is impossible to test the reseler panel. Indeed when it asks for the dns server, even if you enter 2 dns server it always returns to this screen and always asks you to enter the dns server. So I can't see the theme/api, .. screen in the reseler panel

Pascal

[IWorx-Socheat]

Ok Thanks Socheat.
Looks like there is less than I thought in this so waited release :-)
:(

Ok so I can enbale the alert in iworx.ini an change the template in the iworx database ?

What iworx.ini setting are you referring to? And yes, you can edit the template in the database. Of all the iworx database changes, editing the templates should be the safest, as nothing else depends on them. Just be sure to keep all the template variables intact. They look like this: [[template_var]]

[WebXtrA]

Well I love the improvements that have been made.
I was wondering where the the DNS feature is for siteworx accounts, or will this be added later?

[EverythingWeb]

Hi Socheat/Paul,

I've run through the demo, but obviously it's quite heavily locked down, but from what I've seen there is quite a lot of improvements. Well done. :)

Are you in a position to say yet, whether it will run on FC4 "well enough"? ;)

Cheers,

[IWorx-Socheat]

Well I love the improvements that have been made.
I was wondering where the the DNS feature is for siteworx accounts, or will this be added later?

No, there isn't a DNS editing feature in SiteWorx yet. We agree it's useful and needed, so it will be added at some point.

[IWorx-Socheat]

I've run through the demo, but obviously it's quite heavily locked down, but from what I've seen there is quite a lot of improvements. Well done. :)

I'll add a reseller account to the box later today, so you guys can play with the new reseller changes. I'll also add a NodeWorx user (which is also a new feature).

Are you in a position to say yet, whether it will run on FC4 "well enough"? ;)
I'll let Paul answer this one. I know he has a FC4 box he's been testing on, and all the patches you have on your FC4 boxes were backported from our devel code.

[EverythingWeb]

I now see the Ability to Login to a Resellers Account from the master NodeWorx screen.... Fantastic!!! :D

[EverythingWeb]

Could we have a quick run-down on how the Reseller Theme works?

ie; does it apply that theme to domains under the reseller account, if they access their siteworx via theirdomain.com/siteworx ??

More Reseller limits... Perfect! :)

I see there is an OverSelling config option - what happens if say a resellers entire quota goes over... ?

[IWorx-Paul]

Can the new API be used to add a subdomain? If not, would a php script that edits the virtual host file with the appropriate mod_rewrite syntax and creates a folder for the subdomain be sufficient to automate the subdoamin proccess? Or is there more to it than that?

You could add a wildcard subdomain: *
in the control panel, and then the only thing you'd have to do to create a subdomain would be to create the html/subdomain-dir/ in the file system. In that case, http://subdomain-dir.domain.com would start working.

About reselers and themes, It is now possible to define a theme for a reseler when we create a new reseler account, and it seems it is now possible for a reseler to define its own theme, right ?

I have also seen that now in the reseler panel there is an option for the key API. Does it means a reseler will be able to use the API ?
Could you please tell me more about this ?
Is there some restrictions ? security tests ?

I ask this because in the v3 demo it is impossible to test the reseler panel. Indeed when it asks for the dns server, even if you enter 2 dns server it always returns to this screen and always asks you to enter the dns server. So I can't see the theme/api, .. screen in the reseler panel

Yes, the resellers can add their own themes, and then when creating SiteWorx accounts, they can specify the theme that the SiteWorx account uses.

Yes, resellers will be able to use the API. They get their own API key. Their access to the API is limited to their reseller account's abilities - they can only do what they'd be able to do if they were logged in like normal to their reseller account.

Well I love the improvements that have been made.
I was wondering where the the DNS feature is for siteworx accounts, or will this be added later?
That feature wasn't really on the table for this release, we have to determine exactly what DNS functionality should and should not be made available to the SiteWorx user.

What about FC4,5,6?
FC4 should be 100% solid with this release.

FC5 and 6 support will be coming very soon, now that the major development for this work has slowed down, we'll be able to get these supported.

Could we have a quick run-down on how the Reseller Theme works?

ie; does it apply that theme to domains under the reseller account, if they access their siteworx via theirdomain.com/siteworx ??
You'll see under the SiteWorx edit screen, there's a dropdown to specify the Theme now. This is the theme that SiteWorx account will use. There's also a theme drop down on the reseller edit page - this is the theme that Reseller uses when logged into his reseller control panel.

I see there is an OverSelling config option - what happens if say a resellers entire quota goes over... ?
If a reseller's bandwidth allocation or storage allocation (amounts that they have handed out to various SiteWorx accounts under their account) exceeds their limits, and overselling is disabled, they won't be able to create any new accounts until that situation is remedied.
The overselling option isn't related directly to "total current usage" so much as it is to "current total allocation" of features.

There's another feature I should mention since it's kind of related, if you go edit a reseller account and change their status to "Inactive", you can click a box to have all of that reseller's SiteWorx accounts get set Inactive also. This does not happen by default when the reseller account is over bandwidth for a month, for example - but we could add that feature if it was something folks really wanted.

I think that answered most the questions from the last few posts that Socheat didn't answer directly.

Paul

[EverythingWeb]

Thanks Paul :)

[IWorx-Socheat]

I now see the Ability to Login to a Resellers Account from the master NodeWorx screen.... Fantastic!!! :D

Another new, related feature, is that you can add accounts directly to a reseller now without having to log in to their account to do so. In the SiteWorx accounts list page, choose the reseller in the dropdown. This will pull up a list of that reseller's accounts. Now clicking "Add Account" will add the new account to the selected reseller.

[IWorx-Paul]

Oops, I missed a couple.

Glad to see the new maildrop file including non SMTP drop functionality that I had hacked into the 2.x version

One thing I was thinking about doing to this version is checking if IW_DEFAULT_TO = "delete" and if the email did not have a good IW_VHOME or IW_VALIAS then just exit?

Not sure how much more efficient it would be to do that in maildrop vs just letting vpop do it, but I get a lot of mail sent to fake domains and have turned of bounce for a few of the domains on my box.
I guess I'd argue that checking for valiases in the maildrop script isn't really much different than letting vpop do it - and is probably less efficient if an alias does exist, because then you're checking in the maildrop script, and checking again in vpop. Turning bounce on will check all these things at the SMTP level before it even gets to the maildrop script, so that's a good idea for these domains that get lots of fake user e-mail. (and this is now the default for new siteworx accounts in v3)

Is there also an installation script available that we can use to install the RC1 on a clean system?
At this point it's easiest to install the 2.x version, activate the license, and then upgrade to 3.0 as described in the first post.

Paul

[EverythingWeb]

And can we have a list of *every* account on the box, regardless of reseller, on one page? Or does the search now work across resellers, as sometimes wading through a resellers list of 60 accounts to find one, can be tedious ;)

[IWorx-Socheat]

And can we have a list of *every* account on the box, regardless of reseller, on one page? Or does the search now work across resellers, as sometimes wading through a resellers list of 60 accounts to find one, can be tedious ;)

You bet. :) When logged in as the master NodeWorx user, on the SiteWorx accounts page, there's a new dropdown next to the search box. Enter your search text, and select "All Resellers" to apply the search across all resellers. Or, leave the search box blank, and click Search. Voila, all accounts on the box listed. :)

It'll also remember your filtered settings, so if you do a search, then edit or delete an account, it will bring you back to the same filtered list. However, when you add an account, it will reset the search criteria back to the default, so that you can see the newly added account in the list.

[pascal]

Ok Thanks Socheat.
Looks like there is less than I thought in this so waited release :-)


:(



Arff, YOU DID A GREAT JOB !!! really.
I just find that the V2 has been a lot of major updates at a look level and function level, v3 has maybe less *visible* improvments but has great new features and I LIKE THESE and I just SAY : BRAVO !!!
ha ha ha you are victim of your success !
I surely thought there would be more and this is surely because you took near than 2 years to release this one. But don't doubt, I love this PANEL and personnaly I'am VERY VERY HAPPY of these new features :
- API (now just waiting for the edit one)
- Theme for reseler
- API for reseler
- Subdomains and domain pointer for cluster
- Lan cluster

These features is for me just GREAT

So Scoheat excuse me I have tell something bad

Is there others improvements for the cluster part ?
- failover ? (with 2 director/cluster manager)
- ???
- ...


Quote:
Originally Posted by pascal View Post
Ok so I can enbale the alert in iworx.ini an change the template in the iworx database ?

What iworx.ini setting are you referring to?



I refer to these ones. If I remember well on one of our old boxes we did set the email ="" and enabled=1 and then changed the template in the database
[monitor]
email=""
enabled="0"
loadavg_threshold_01="10"
loadavg_threshold_05="10"
loadavg_threshold_15="10"
storage_threshold="80"

Indeed, when a client reach the bandwidth limit their account is suspend. We'd like the sysadmin receive an email to know this and be able to ask to the client what he wants (pay, change his account, ...)

If I remember well if we set email et enabled to 1 it works ? no ?

Pascal

[IWorx-Socheat]

I've modified the demo reseller and added nameservers, so the demo reseller should be usable/testable now:

Demo Reseller:
login: demo-reseller@interworx.com
pass: demo

I've also added a few NodeWorx users. NodeWorx users are like SiteWorx (secondary) User accounts, but for NodeWorx. :) For those of you who are unfamiliar, SiteWorx secondary user accounts allow additional logins to the same SiteWorx account, but with the option to restrict access to parts of the interface. I've added the following NodeWorx users:

DNS admin (only has access to the DNS Zones page in NodeWorx):
login: demo-dns-admin@interworx.com
pass: demo

System Graphs admin (only has access to the System Graphs page in NodeWorx):
login: demo-graphs-admin@interworx.com
pass: demo

and this last one is for you, Pascal :)
French NodeWorx admin (has all the permissions as the master nodeworx user, but the language is set to French):
login: demo-fr@interworx.com
pass: demo

[EverythingWeb]

Is there any provision for Reseller-specific 'skeleton' directories?

[pascal]

About the reseler

When from the reseler panel you create a new siteworx account. The bandwidth field is different than the one in nodeworx ?

Bandwidth: [?]
Gigabytes / Month Limit: 100


There is the field then Limit: 100

If I understand well it means that a reseler can't set a bandwidth limit > at the limit set for this reseler ? true ?

So in this case the limit for this reseler is 100 ?

If yes, does this Limit:100 change everytime the reseler create a new account ? or does this limit shown here is always the max limit set to the reseler ?

Arff hopes you understand waht I mean :\

Thanks
Pascal

[IWorx-Paul]

I refer to these ones. If I remember well on one of our old boxes we did set the email ="" and enabled=1 and then changed the template in the database
Pascal, it's been so long since I looked at that stuff I'll have to investigate and get back to you.

Is there any provision for Reseller-specific 'skeleton' directories?
No, not at this time.

Paul

[pascal]

and this last one is for you, Pascal
French NodeWorx admin (has all the permissions as the master nodeworx user, but the language is set to French):
login: demo-fr@interworx.com
pass: demo


:D :D :D :D :D :D

LOVE YOU !

Pascal

[IWorx-Paul]

There is the field then Limit: 100

If I understand well it means that a reseler can't set a bandwidth limit > at the limit set for this reseler ? true ?

So in this case the limit for this reseler is 100 ?

If yes, does this Limit:100 change everytime the reseler create a new account ? or does this limit shown here is always the max limit set to the reseler ?
Yes, that's correct, and yes, it changes every time the reseller creates a new account. The Limit shown next to each section is the limit that can go into the text box right next to it.

Paul

[pascal]

Pascal, it's been so long since I looked at that stuff I'll have to investigate and get back to you.

Paul

Thanks Paul

Indeed these come from the old v1.3 when the email templates was present. ;)

But if I remember it should works.

Pascal

[EverythingWeb]

Pascal, it's been so long since I looked at that stuff I'll have to investigate and get back to you.


No, not at this time.

Paul

Paul, you wouldn't happen to know if this is a feature that you will be offering at some point.

We have some resellers who like to put their own holding pages in for new clients. I'm wondering if it's possible for, in the nodeworx -> edit siteworx page for there to be an option, which copies in a fileset as defined in the resellers preferences? Maybe in a future release :)

[pascal]

Yes, that's correct, and yes, it changes every time the reseller creates a new account. The Limit shown next to each section is the limit that can go into the text box right next to it.

Paul

GREAT !

Pascal

[IWorx-Paul]

Paul, you wouldn't happen to know if this is a feature that you will be offering at some point
You're referring to reseller specific skel directories still, right?

I agree, that's definately a feature we'll support, although not in this release.

[EverythingWeb]

You're referring to reseller specific skel directories still, right?

I agree, that's definately a feature we'll support, although not in this release.

Yup, so Resellers can have their own skel directories loaded into a 'new' account.

Glad to hear it will be considered. :)

[Justec]

Turning bounce on will check all these things at the SMTP level before it even gets to the maildrop scriptOh, that makes sense... if i get an email to bob@domain.com it will generate a bounce email at the qmail level before it even gets anywhere near the maildrop script.

Got another VERY minor thing I noticed. I have a SiteWorx account that exceeded their storage by about 200 MB and assume it was b/c it was a client that uses webmail versus downloading email via POP3.

So I went to see how big their mailboxes were, but in the mailbox screen I dont see where it list the mailbox size anymore. If you go to each account you can see it, but not in the mailbox list for the domain.

I suppose you did this to make the page more efficient, but just wanted to know if there was some other place to look for this.

[IWorx-Socheat]

:(
Arff, YOU DID A GREAT JOB !!! really.

Hahaha, I was just teasing you Pascal. :) We really do appreciate everyone's patience with InterWorx 3.0. :)

[IWorx-Paul]

Is there others improvements for the cluster part ?
- failover ? (with 2 director/cluster manager)
There are improvements in that there are a handful of bug fixes related to adding/removing cluster nodes, pointer/subdomains work, you can change IP addresses of clustered accounts now (you couldn't before).
But no high availablity / failover yet, just fixes and small improvements to the existing cluster system.

Paul

[IWorx-Paul]

Got another VERY minor thing I noticed. I have a SiteWorx account that exceeded their storage by about 200 MB and assume it was b/c it was a client that uses webmail versus downloading email via POP3.

So I went to see how big their mailboxes were, but in the mailbox screen I dont see where it list the mailbox size anymore. If you go to each account you can see it, but not in the mailbox list for the domain.

I suppose you did this to make the page more efficient, but just wanted to know if there was some other place to look for this.

We were forced to move the storage display to the edit screen. On accounts that had gigabytes of mail, it would cause the e-mail box list page to take 5 minutes+ to load, and would cause unccessary load on the box in the process. So, indeed it's a inconvience, but it's neccessary (and not so bad) :)

Paul

[pascal]

There are improvements in that there are a handful of bug fixes related to adding/removing cluster nodes, pointer/subdomains work, you can change IP addresses of clustered accounts now (you couldn't before).
But no high availablity / failover yet, just fixes and small improvements to the existing cluster system.

Paul

These fixes and small improvments are very cool !
change IP --> Too Great !
pointer/subdomains --> too great too !

Now I'm really waiting a new release and for some improvments in failover and mysql cluster (or at least external mysql server)

Hahaha, I was just teasing you Pascal. We really do appreciate everyone's patience with InterWorx 3.0.

;) :p

Thanks to the iworx team
Pascal

[MeddlePAL]

Small question. In 3.0 when you install, can you now select the Ethernet port to use for licensing? In the past it has been eth0, but some providers use eth0 as the private network, which obviously is no good.

[IWorx-Paul]

Hi Phil,

Yes, that patch we developed for you that addresses this issue during install is included in the 3.0 release.

Paul

[thinksmart12]

The SSH server page in Nodeworx has some problems. :(
If you start or stop the SSH service, the configuration file at /etc/ssh/sshd_config gets messed up. You have to manually change it.

[IWorx-Socheat]

Can you be a little more descriptive? Exactly what gets messed up (i.e., what do you have to change to get it back to working order)? Also, what distribution are you using?

Thanks!

[thinksmart12]

I'm using CentOS 4.4. Two extra entries get added to the configuration file. They are both the number 22, on two separate lines. Of course, SSH won't start because the file is invalid, so you just have to delete both of the 22s. I'm not sure if this has anything to do with it, but now I cannot login to SSH with root. I think this is because I played around with the option allow root to login. I changed it a few times, and the configuration file was invalid again.

[Justec]

Turning bounce on will check all these things at the SMTP level before it even gets to the maildrop scriptForgot to ask, does SpamAssassin Options
SMTP Level Scanning: have to be on to make this happen? I have had this turned off for a while now to avoid the double scan.

[IWorx-Paul]

No, SMTP Level Scanning doesn't need to be enabled for for "bounce on" to reject invalid recipients at the SMTP level.

Paul

[bear]

Hi

just installed using you upgrade instructions but i dont think it has installed correctly, nodeworx can no longer be accessed.
if i try service iworx restart i get an error iworx: unrecognized service.

Whats the bet way to run the upgrade again to make sure its installed correctly.
thank you

[IWorx-Paul]

Hi Gary,

Please open a support ticket right away.

Thanks,

Paul

[bear]

ticket submited
thank you


Thanks for your help Paul, all sorted

[IWorx-Socheat]

I'm using CentOS 4.4. Two extra entries get added to the configuration file. They are both the number 22, on two separate lines. Of course, SSH won't start because the file is invalid, so you just have to delete both of the 22s. I'm not sure if this has anything to do with it, but now I cannot login to SSH with root. I think this is because I played around with the option allow root to login. I changed it a few times, and the configuration file was invalid again.

This bug has been confirmed and has now been fixed for the release. Thanks for the bug report!

[thinksmart12]

Sure, glad I could be of assistance.

I think this is a dumb question :), but there will be update scripts to the final version, right?

[IWorx-Socheat]

Yes, definitely. :)

[bear]

I'm using CentOS 4.4. Two extra entries get added to the configuration file. They are both the number 22, on two separate lines. Of course, SSH won't start because the file is invalid, so you just have to delete both of the 22s. I'm not sure if this has anything to do with it, but now I cannot login to SSH with root. I think this is because I played around with the option allow root to login. I changed it a few times, and the configuration file was invalid again.

I have the same problem ssh is now offline and i cannot login to shh with root.

[Henrik]

Is it possible to migrate individual 2.1.3 siteworx accounts (domains) to a 3.x siteworx account and have these 2.1.3 siteworx accounts as subdomains of the 3.x account?

This would mean that instead of having several siteworx logins for different domain names like in 2.1.3, the client could use one single login for several domain names under 3.x.

(I hope I wasn't too confusing in describing this issue.)

[IWorx-Socheat]

If I understand you correctly, what you want to do is take several existing SiteWorx accounts and make them secondary domains of another SiteWorx account? If so, this is not possible. We (or maybe just I ;)) call it "demoting" the account, which we don't allow.

[Henrik]

Yeah, exactly. Instead of having a gazillion logins for several domains (I am mainly talking about web/email hosting), it would be easier to have one single login and then see these domains for web/email hosting under this "master domain".

I was under the impression that this would be a feature added for v3, but perhaps I misunderstood.

As in other CPs you can share a total storage and traffic amount between many different sites/domains and with full functionality for these. As it looks now under v2.x the master domains has their own allocated bandwidth and storage quota.

[IWorx-Paul]

Hi Henrik. The feature you describe does exist - but you can't automatically convert a SiteWorx account into a secondary domain under another SiteWorx account. The conversion would have to be done manually - that is, you'd have to set up a new InterWorx 3.x box, create the main SiteWorx account, and then manually add the other domains as slave domains under that account, and then move the contents from the other server to the approriate places on the new server. It's a very manual process.

Paul

[IWorx-Paul]

This thread is now locked, InterWorx-CP 3.0-RC2 is now available. See this thread and update your RC1 servers: http://interworx.com/forums/showthread.php?p=12316