Sunday Jul 01, 2012

AWS CloudFormations, Oracle Assembly Builder, Chef and Puppet

I blogged about the difference and similarities between AWS CloudFormations and Oracle Assembler builder to package your software stack for deployment/provisioning to the cloud. However, these tools do not deal with software stack versioning and configuration management. This is where tools like Chef and Puppet come into play.
Puppet and Chef points of interest:
1. Can be used in any cloud environment (rackspace, private cloud etc).
2. There is a debate between which is better. I am not going to get into this debate other then to say Puppet is more mature.
3. AWS CloudFormations can integration with both Chef and Puppet.

A good blog on AWS CloudFormations and the need for something more:
AWS CloudFormation

Friday Jun 29, 2012

Amazon CloudFormations and Oracle Virtual Assembly Builder

Yesterday I blogged about AWS AMIs and Oracle VM templates. These are great mechanisms to stand up an initial cloud environment. However, they don't provide the capability to manage, provision and update an environment once it is up and running. This is where AWS Cloud Formations and Oracle Virtual Assembly Builder comes into play. In a way, these tools/frameworks pick up where AMIs and VM templates leave off.
Once again, there a similar offers from AWS and Oracle that compliant and also overlap with each other. Let's start by looking at the definitions:
AWS CloudFormation gives developers and systems administrators an easy way to create and manage a collection of related AWS resources, provisioning and updating them in an orderly and predictable fashion.
AWS CloudFormations

Oracle Virtual Assembly Builder - Oracle Virtual Assembly Builder makes it possible for administrators to quickly configure and provision entire multi-tier enterprise applications onto virtualized and cloud environments.
Oracle VM Builder

As with the discussion around should you use AMI or VM Templates, there are pros and cons to each:
1. CloudFormation is JSON, Assembly Builder is GUI and CLI
2. VM Templates can be used in any private or public cloud environment. Of course, CloudFormations is tied to AWS public cloud

Tuesday May 15, 2012

AWS Elastic Cloud set up

Signing, setting up and configuring EC2 cloud is easy. These instructions were very useful:
AWS EC2 Word Press Set up
Now have a Tomcat and MySQL configuration running WordPress blog:
WordPress Blog on AWS
It is so slow but I guess this is normal:
AWS EC2 Micro Instance Slow
Because it is a free micro tier virtual server

Monday Apr 02, 2012

Cloud consolidation handling multi databases

I have spoken about virtualization and the different types of virtualization. Which includes OS zones, application server domains, database schemas, VLANS and other approaches. Another approach is to create a virtually federated database in the cloud. DBSpaces is a company that has a technology to created a virtually federated database in the cloud. DBSpaces is a Virtual Database technology that allows an organisation thru a single Virtual Database access multiple data sources (or database spaces) in real-time. Additionally dbSpaces can be configured to access an organisations data internally using a remote gateway so that their dbSpace is seamless across the Public and Private cloud.

Monday Nov 07, 2011

Physical Vs Virtual in enterprise data centers / private cloud

Interesting article that discusses physical Vs. virtual enterprise data centers. The article discusses physical (Oracle Exadata) data centers. May companies deciding dedicated physical appliances are the best choice for big data applications.

Wednesday Sep 14, 2011

Virtual Desktop Infrastructure Vs. Virtual Server in the cloud

Virtual Desktop Infrastructure (VDI) has become the latest buzzword in the cloud computing arena. VDI is very similar to Virtual Server (referred to as SBC - Server Based Computing). Both offer virtualization and both holding the virtual environment on a centralized server. This is where the similarities end. VDI provides a full desktop experience while SBC offers terminal service based access to a centralized/shared operating environment. There are pros and cons to each: VDI Pros: 1. Offers a full desktop experience to the user 2. Actual desktop including the OS are available to the user Cons: 1. There is one copy of the desktop/OS for each user 2. There are potentially gigabytes of storage (and associated CPU) required to store each virtual user desktop SBC Pros 1. Less server storage, CPU and RAM required 2. Shared environment for users so easy to provision, management, monitor, and deploy applications Cons 1. User does not get full desktop experience 2. May have to create a portal or mashup so users can see all of their cloud applications in a centralized location There is no right or wrong answer as to what is best for you. Most companies that offer SBC also offer VDI (Oracle, Citrix, VMWare, etc.).

Migrating legacy client/server and mainframe technologies to the Oracle cloud.


« April 2014