Saturday Oct 01, 2011
This entry along with the next three will be about the key attributes of cloud computing. Cloud computing is not virtualization, putting your computing resources on the internet or consolidating IT resources. There are four key atributes that you must have to really be 'on the cloud'. Metering and chargeback – Metering and chargeback are mechanisms for gathering compute resource usage (metering) and then charging back the user, department, or company for the computing cycle that they consume. In the client/server model, metering and chargeback were not necessary because each user had their own personal computer and typically each department or customer had their own database server. Today, most cloud services are offered on flat pricing model structured upon usage of computing resources for fixed unit of time (month or days). Although this model reduces the cost of using IT infrastructure, end users and developers pay a price regardless of actual usage. If a user subscribes for a compute infrastructure for a month and even if they actively use it for only 10 or 15 days, they still have to pay for entire month. This pricing model is typically derived by calculating the overall cost of the infrastructure (acquisition cost + operational cost + margin) and then dividing the amount by a fixed unit of time such as months, days, or years. Using sophisticated metering and chargeback tools provide both public and private cloud providers the ability to monitor actual usage of resources by the users and then charge them accordingly. Accurate resource usage information (metering) up to the minute or second in time can lead to a true pay as you go model which is a key premise cloud computing. Oracle Enterprise Managers captures very detailed information about the resource usage and stores it in its repository that can be later used for chargeback purposes.
Saturday Sep 17, 2011
By llaszews on Sep 17, 2011
What really defines a cloud as opposed to running a consolidated system in a private or public accessible network environment are these four characteristics: 1. Provisioning – Dynamic and self-service provisioning. Application provisioning involves deploying applications to your cloud infrastructure with a few mouse clicks. So, when moving to the cloud, application provisioning will be made easier since there are not hundreds or thousands of client machines to deploy too. 2. Metering and chargeback – Metering and chargeback are mechanisms for gathering compute resource usage (metering) and then charging back the user, department, or company for the computing cycle that they consume. In the client/server model, metering and chargeback where not necessary because each user had their own personal computer and typically each department or customer had their own database server. 3. Multi-tenancy – Multitenancy, or running multiple customers or departments on the same central hardware and software infrastructure, is not an issue for client/server applications since each user has her own instance of the application, and most likely each department or customer has its own dedicated database server. In cloud environments, the application, database, and hardware infrastructure are shared among departments or even companies. 4. Elastic – Elasticity refers being able to dynamically provision, migrate, and allocate computing resources to users, departments or customers. It includes the infrastructure to easy set up and ‘tear down’ applications. One of the first areas that customers focus on when moving to the cloud is developer and User Acceptance Testing (UAT) environments. The ability to quick set up a new test environment and then delete it once the testing is done is a cost effective and time saving exercise when done using cloud computing.
Migrating legacy client/server and mainframe technologies to the Oracle cloud.
- Migrating blog entries
- Middleware and Cloud Computing Book
- Oracle Enterprise Manager with AWS Database Instance
- AWS EC2 Overview book
- AWS EC2 Oracle RDB - Storing and managing my data
- AWS CloudFormations, Oracle Assembly Builder, Chef and Puppet
- IBM DB2 AIX RISC to Oracle Linux Sun x86
- Amazon CloudFormations and Oracle Virtual Assembly Builder
- Amazon AMIs and Oracle VM templates
- Migrating RISC to x86 - endianess 'issue'