91d437f0fb56cfb5b64de81b60bd6738

91d437f0fb56cfb5b64de81b60bd6738 ->

$ echo “a man on linux” | openssl dgst

or

$ echo “a man on linux” | md5sum

The debate occurs quite often on how to stack software in Cloud Computing solution (specifically Development & Test Cloud), amongst Service, Software & STG. I don’t complain the variety of software stack, as I like the more choices. I’m going to write out how my architectural solution looks.

I have one philosophy: When I could use OpenSource + Pure Blue software in my solution, I will do it without any hesitation.

IBM Development & Test Cloud solution is based upon Tivoli Service Automation Manager v7.2 for now. There’re 3 types machines in its Cloud environment. 2 of 3, in Managing environment , are Management Server & Administrative Server. The last one, in Managed environment, is the managed system(s).

My only rule to follow is to check the product infocenter, which tells the truth of technology & product. The one is http://tinyurl.com/tivsam (I talk about x only for my current engaged case @ one Telco customer in Beijing)

For Management Server, we have 2 choices on 64 bits x – RHEL5.4 or SLES10.2

For Administrative Server, SLES10.2 is ONLY our choice for Linux. Obviously Microsoft Windows isn’t in my list either. The reason is clear.

For Managed environment on x, we get rid of VMware and we have RHEL5.4 and SLES10.2 (CentOS isn’t in my list, due to lack testing & support)

To combine the above consideration, I use SuSE Linux Enterprise 10.2 in management environment and Redhat Enterprise Linux 5.4 in managed environment.