Suggested Setup:-
Setup Application on various application contexts in a Java Webserver (e.g. Tomcat) on URLs like

http://localhost:8080/application-version1

http://localhost:8080/application-version2

….
….

http://localhost:8080/application-versionN

in folders
/usr/local/java-webserver/webapps/application1
/usr/local/java-webserver/webapps/application2
….
….
/usr/local/java-webserver/webapps/applicationN

The application codebases can be directly updated via rsync from the local machine’s SVN working copies on a machine on client’s LAN by using the rsync over ssh transport.

Run via cron or manually the following
cd
rsync -e ‘ssh -i /id_rsa_application1′ –exclude=.svn -nzvrpoglHDIt –delete root@:/usr/local/java-webserver/webapps/application1

cd
rsync -e ‘ssh -i private_key_full_path/id_rsa_application2′ –exclude=.svn -nzvrpoglHDIt –delete root@:/usr/local/java-webserver/webapps/application2

….
….

cd
rsync -e ‘ssh -i private_key_full_path/id_rsa_application2′ –exclude=.svn -nzvrpoglHDIt –delete root@:/usr/local/java-webserver/webapps/applicationN

On Apache2 use mod_proxy to reverse proxy multiple application contexts on to various fully qualified host names as below:-

Production Version at a VirtualHost on Apache2 with ServerName www.
proxying http://localhost:8080/PRODUCTION

Version 1 at a VirtualHost on Apache2 with ServerName www.
proxying http://localhost:8080/application1
….
….
And so on.

Notes:-

As you see only 1 routable IP address is required for such a setup and a single server. The SVN doesn’t need to setup on the remote server outside the office LAN.
Database configuration management is similarly easy where each application context can use its own DB in MySQL/PerconaDB/MariaDB/PostgreSQL
Use of a separate private key for each version is suggested as it seems that each working copy version on the branches for an application codebase is being worked by an individual developer.

Terms:-

1. There is no guarantee that existing customers who buy this deal would be able to retain their existing IP addresses for use with this server.
2. There are no refunds.
3. Upto 2 servers per client
4. These are un-managed servers and there is no provision for daily backup which must be obtained separately
5. Offer expires 31st October 2011
6. Standard price of Rs. 12693/pm + 10.3% Service Tax ( = Rs. 14000/pm ) applies for monthly prepayment plan.
7. The offer can’t be combined with other offers.
8. Windows Web Server 2008 R2 shall also be bundled in the same price

Terms:-

1. Windows/SQL Server production licenses as applicable to the Websitespark members would only be applicable
2. Yearly pre-paid servers
3. Upto 2 servers per client
4. These are un-managed servers and have no provision for daily backup which must be obtained separately
5. Offer expires 31st October 2011

As per section 2(f) of the proposed rules, an intermediary is defined under clause (w) of sub-section (1) of section 2 of the IT Act, as amended by the IT (Amendment) Act 2008, which specifically includes “web hosting providers”.

Hosting providers do not (and cannot feasibly and comprehensively) monitor, decode, parse, translate and evaluate all data stored on or passing through their facilities (hardware, software and network-based) that they lease on temporary bases to their customers (hereinafter called infrastructure). In addition, hosting providers commonly deal with hundreds or even thousands of gigabytes of data every month. To put this in context, a gigabyte of data can easily contain about 10 years worth of emails (including emails containing pictures, music and videos) of a typical Internet user. It is in this context that point-by-point objections from the point of view of hosting providers with respect to the above-mentioned subclauses of Section 3(2) of the proposed Rules are appended below:

Section 3(3) read with Section 3(2) mandates that intermediaries such as hosting companies SHALL NOT host any information enumerated in Section 3(2), i.e., any information that:

(a) belongs to another person;
(b) is harmful, threatening, abusive, harassing, blasphemous,
objectionable, defamatory, vulgar, obscene, pornographic,
paedophilic, libellous, invasive of another’s privacy, hateful, or
racially, ethnically or otherwise objectionable, disparaging, relating or
encouraging money laundering or gambling, or otherwise unlawful in
any manner whatever;
(c) harm minors in any way;
(d) infringes any patent, trademark, copyright or other proprietary rights;
(e) violates any law for the time being in force;
(f) discloses sensitive personal information of other person or to which the
user does not have any right to;
(g) causes annoyance or inconvenience or deceives or misleads the
addressee about the origin of such messages or communicates any
information which is grossly offensive or menacing in nature;
(h) impersonate another person;
(i) contains software viruses or any other computer code, files or
programs designed to interrupt, destroy or limit the functionality of any
computer resource
(j) threatens the unity, integrity, defence, security or sovereignty of India,
friendly relations with foreign states, or or public order or causes
incitement to the commission of any cognisable offence or prevents
investigation of any offence or is insulting any other nation.

The objections to each sub-sub-clause are respectively:

(a) – Hosting providers are not competent or equipped to legally ascertain rightful title and ownership of every piece of information that is hosted or transmitted, especially when the information that is transmitted through or stored on their IT infrastructure.

(b) – Hosting providers are not legally competent to ascertain whether information stored on or transmitted through their infrastructure is defamatory, vulgar, obscene, pornographic, libellous or contravenes any other law. Further, they are charged with ensuring that information stored on or transmitted through their infrastructure is not harmful, threatening, abusive, harassing, blasphemous, paedophilic, invasive of another’s privacy, hateful, or racially, ethnically or otherwise objectionable. These terms are vague and undefined and hosting providers are not competent to decide on them, even if they were able to monitor, decode, parse, translate and evaluate all data stored on or passing through their infrastructure. Further, hosting providers cannot determine if information stored on or passing through their infrastructure is “objectionable” or “encourages money laundering or gambling”

(c) – Hosting providers are not competent to determine and ensure that information stored on or passing through their infrastructure can “harm minors in any way”.

(d) – It is not possible for hosting providers to ensure that information stored on or passing through their infrastructure does not legally infringe any patent, trademark, copyright or other proprietary right;

(e) – Hosting providers are not competent to ensure that information stored on or passing through their infrastructure does not violate any other law in force.

(f) – Hosting providers cannot ensure that sensitive personal information (which implies information that is not freely available) of third parties is not revealed, transmitted, published or stored by clients using the hosting provider’s infrastructure.

(g) – It is impossible for hosting providers to determine if any information stored on or passing through their infrastructure is capable of causing annoyance or inconvenience or deceives or misleads the addressee about the origin of such messages or communicates any information which is grossly offensive or menacing in nature. Further, the terms “grossly offensive”, annoying, inconveniencing are over-wide, vague and ambiguous.

(h) – It is impossible for hosting providers to determine if any information stored on or passing through their infrastructure is actually furthers the impersonation of some person other than the actual sender.

(i) – As viruses or other computer contaminants are commonly encrypted and their existence obfuscated or otherwise hidden in non-contaminant data, it is impossible for hosting providers to ensure that information stored on or passing through their infrastructure is free of computer contaminants including viruses.

(j) – Hosting providers are not competent to ensure that information stored on or passing through their infrastructure does not threaten the unity, integrity, defense, security or sovereignty of India, friendly relations with foreign states, or or public order or causes incitement to the commission of any cognizable offense or prevents investigation of any offence or is insulting any other nation. It is further submitted that certain strictures in this sub-sub-section, particularly, the stricture against “insulting to any other nation” are so broad as to violate the Constitutional right of freedom of speech. Under this provision, the hosting provider would be culpable for hosting a patriotic website that discussed the conduct of Pakistan or any other nation that harbored terrorists who attacked India.

E2E Networks provides the most high powered servers in India with highest monthly bandwidth quotas in its price range.

Let us know if you want to test drive our cloud servers by emailing us at sales@e2enetworks.com

Based on our bandwidth graphs, there was at one point of time user traffic loss up to the extent of 10%(90% of the visitors to the sites hosted with us were able to use the websites just fine) but now the bandwidth graph is now nearly normal.

Things seem to be under control now. Please email us your concerns regarding the issues to support@e2enetworks.com

It all seems fine for now. Hope it stays that way.

UPS maintenance task will be carried out on Saturday 20th Nov between 6:30AM-8:30AM

While we don’t expect any downtime due the same, under extremely rare circumstances some of the machines might be rebooted when the switchover between the two redundant power supplies happens atleast twice during the activity.

Please email us at support@e2enetworks.com for any concerns regarding the activity

Update:-
Nov 20, 2010 8:41AM: The critical part of maintenance is over, there was no downtime due to it and none is expected now while the maintenance would last another 10 minutes.
Nov 20, 2010 8:50AM: The maintenance activity is over.

The root cause analysis is awaited but it happened due to high CPU utilization at the ISP’s router.

Timeline:
5:08 PM: First observed from our NMS in Delhi Zone – II and Mumbai Zone – I
5:10 PM: ISP informed of downtime
5:20 PM: ETA received from ISP 10-15 minutes
5:38 PM: Finally all back to ‘normal’

Incase you are a customer with facilities at Delhi Zone – I and wish to migrate to Delhi Zone – II get in touch with us at support@e2enetworks.com