I use EC2 instances for test, development, demo and also for deployment to production. Amazon offers different types of instances, ranging from a micro instance (613 MB Ram and 2 CPU units) to a full fledge Cluster Compute Quadruple Extra Large Instance (60GB RAM and 33 CPU units). Of course a different price and paid per hour usage, available anytime.
All on demand Linux instances (Singapore):
Micro instance: U$ 0.02 per hour
Medium instance: U$ 0.34 per hour
High Mem/CPU instance: U$ 2.024 per hour
On top of this there are 3 different categories of instances (in contractual terms)
Some price comparison for a m1.Large instance we use for testing (7,5GB RAM and 4 CPU units)
On Demand (any time without any contractual obligations, we are using them currently) $0.340 per Hour > 1 month U$ 244.80 (fulltime 24h)
Reserved Instance (1 year term, one time payment U$ 276.00) U$ 0.196 per Hour > 1 month U$ 141.12 (3 months: U$ 699.36 vs on-demand U$ 734.40, 12 months: U$ 1969.44 vs. on-demand U$ 2937.60 = ~30% savings )
Spot Instance (depends on availability, you bid on a price range, if price exceeds your limit your instance shuts down) U$ 0.04 per Hour (as of December 5th 2012) > 1 month U$ 28.80
The spot instance, almost at 10% of the on-demand price, is extremely attractive and I am using it as test server.
Not suitable for production or demo purpose though.
The reserved instance starts to break even after 3 months full-time usage !
In order not to pay for instances running idle (at night, weekend) they auto-shutdown and the user can start them in a self provision fashion (for test, demo or training).
Interesting enough, the price fluctuation is very different in the AWS regions. Lets look at a m1.large instance type in the Ireleand versus Singapore datacentre.
Obviously Singapore customers are not into this bidding concept, it remains permanently at 4cts while for Ireland the price jumps up to several Dollars !
Note: you need to re-deploy the resource adapter with version 5.7 and check all connector settings.
It works fine with Glassfish 18.104.22.168 and Java JDK 1.7.07
I had issues with the firewall due to fact ActiveQM uses a fix registration port for JMX but dynamic ports for the communication port. The web-console was not accessible. “Exception occurred while processing this request, check the log for more information!”
[#|2012-10-18T07:42:09.249+0000|WARNING|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=73;_ThreadName=Thread-2;|StandardWrapperValve[jsp]: PWC1406: Servlet.service() for servlet jsp threw exception
java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
There are ways to configure this for a standalone ActiveMQ instance with the parameters connectorPort and rmiServerPort but I didnt find out yet how to do this with the embedded version.
As a workaround I changed this setting -Djava.rmi.server.hostname from my hostname to localhost. -Djava.rmi.server.hostname=localhost
We use a couple of EC2 servers which are not permanently running, rather on user-demand only. Without wasting money for elastic ip addresses (you are charged while they are NOT attached), we make use of the random public IP provided by AWS and update our Dyndns addess for this server.
Create a DynDNS account if you dont have one
Create a hostname (eg. sample.mydomain.net)
Install Inadyn sudo apt-get install inadyn (for Ubuntu or debian)
Add this line to a start-up script inadyn –username myuser –password mypwd –iterations 1 –alias sample.mydomain.net ( with iterations the command is executed only once)
inadyn makes use of http://checkip.dyndns.com/ to retrieve the ip address
On top of it the server switches off automatically at nighttime (see blog entry) and the user uses a little web frontend to start the server again on his/her own.
About once a year I revisit (link) this topic again (usually when the plugin causes trouble). Now I get this signature error
AWS Error Code: SignatureDoesNotMatch, AWS Error Message: The request signature we calculated does not match the signature you provided. Check your key and signing method., S3 Extended Request ID:..
The good news first:
The S3 plugin became mainstream, you can install it from the plugin page under Jenkins Administration | Plugin Manager. You dont need to build the plugin any longer by yourself and can skip the rest of this entry.
The long version:
It seems the error is caused by a ‘+’ sign in the access key troubling the encoding function used (see issue). The latest build (Sep 2012) should fix this problem.
If you want to build by yourself, you need to get the sourcecode from git and build the plugin file, beware as it requires Maven 3 now. Below instructions apply fro Ubuntu.
or ‘How to cut (even more) cost while running EC2 instances‘
I am running a FTP server on an EC2 instance (micro if you want), but we dont use it all the time. The server is run on-demand only and auto-shutdown every night. The challenge: on every new start of the instance you will get a new public ip which screws your passive ip address configuration in vsftpd.conf.
Remaining challenge: If you dont want to spend money on an elastic (permanent) IP which costs you while the instance is NOT running, you need a DNS service like dyndns.com and update the dyndns entry on every start too. This can easily done by a shell script using ddclient or Ubuntu’s dyndns command.
About one year back I found this plugin, that saves your build artifacts to Amazon S3 storage. Unfortunately the plugin does not properly work with the current Jenkins versions and the original plugin is not maintained. Luckily someone forked and updated the plugin at github. You need to build the plugin by yourself with the help of maven, you still can refer to my original post, just one change is required to make it work, the settings for your ~/.m2/settings/xml need to be changed according to the plugin page description. Please be patient, maven is going to download a lot !
<!-- Give access to Jenkins plugins -->
<activeByDefault>true</activeByDefault> <!-- change this to false, if you don't like to have it on per default -->
Otherwise you get errors like
[INFO] Scanning for projects...
[INFO] Unable to find resource 'org.jenkins-ci.plugins:plugin:pom:1.434' in repository java.net2 (http://download.java.net/maven/2)
[INFO] Unable to find resource 'org.jenkins-ci.plugins:plugin:pom:1.434' in repository central (http://repo1.maven.org/maven2)
[ERROR] FATAL ERROR
[INFO] Error building POM (may not be this project's POM).