Thursday Jun 28, 2012

Amazon AMIs and Oracle VM templates

I have worked with Oracle VM templates and most recently with Amazon Machine Images (AMI). The similarities in the functionality and capabilities they provide are striking. Just take a look a the definitions:

An Amazon Machine Image (AMI) is a special type of pre-configured operating system and virtual application software which is used to create a virtual machine within the Amazon Elastic Compute Cloud (EC2). It serves as the basic unit of deployment for services delivered using EC2. AWS AMIs

Oracle VM Templates provide an innovative approach to deploying a fully configured software stack by offering pre-installed and pre-configured software images. Use of Oracle VM Templates eliminates the installation and configuration costs, and reduces the ongoing maintenance costs helping organizations achieve faster time to market and lower cost of operations. Oracle VM Templates

Other things they have in common:
1. Both have 35 Oracle images or templates:
AWS AMI pre-built images Oracle pre-built VM Templates
2. Both allow to build your own images or templates: A. OVM template builder - OVM Template Builder - Oracle VM Template Builder, an open source, graphical utility that makes it easy to use Oracle Enterprise Linux “Just enough OS” (JeOS)–based scripts for developing pre-packaged virtual machines for Oracle VM.
B. AMI 'builder' - AMI builder
However, AWS has the added feature/benefit of adding your own AMI to the AWS AMI catalog: AMI - Adding to the AWS AMI catalog

Another plus with AWS and AMI is there are hundreds of MySQL AMIs (AWS MySQL AMIs ). A benefit of Oracle VM templates is they can run on any public or private cloud environment, not just AWS EC2.
However, with Oracle VM templates they first need to be images as AMIs before they can run in the AWS cloud.

Thursday Jun 14, 2012

Chargeback and billing across public and private clouds

Had a great conversation today regarding the need for metering, chargeback, and billing of cloud computing resources. The person I spoken with at a Fortune 1000 company increased the scope and magnitude of the issue of billing for cloud computing resources beyond what I had previously considered. I believed that doing any type of chargeback and billing for one public, private or hybrid installation was difficult. This person pointed out that the problem is even bigger in scope. The reality is many companies are using multiple public cloud vendors and have many different private cloud data centers. A customer may use AWS for some smaller public cloud applications, Salesforce.com (SaaS), Rackspace for IaaS, Savvis for colocation and a variety of Iaas and PaaS implementations for the private cloud. How does a company get a consolidated bill for all these different cloud environments? I am not sure their is an answer right now.

Friday May 25, 2012

Cloud open source standards and frameworks

Interesting article on cloud standards and frameworks for IaaS and PaaS:
Cloud IaaS and PaaS open standards

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.

Sunday Jun 26, 2011

Oracle's Sun Blade modular systems: Can they give VBlock a run for their money?

Check out these new hardware and software integrated solutions from Oracle Sun (they are not Exa* machines): http://www.oracle.com/us/products/servers-storage/servers/blades/index.html They offer a number of solutions not offered by VBlock: Oracle DB, Oracle WebLogic, OS and end to end management. Be interesting to see how much adoption these machines get given the long time VBlock has been around and the Exa* focused strategy at Oracle.

Wednesday Jun 15, 2011

Oracle Exalogic VBlock private cloud

The following high level steps (probably others) that would need to be performed to get a the application server software running on a VBlock platform. Because Oracle Exalogic is a hardware and software solution, these steps are not required: 1. Assess your application requirements. This includes what operating systems, database drivers, application server, SOA software, integration software, and application management software is required. 2. Research available component technologies and vendor products. Review the products and technologies from vendors that span operating systems to application management and monitor to application servers. 3. Identify all software components and evaluate their compatibility, required drivers, and vendor certifications. Ensure that the application’s middleware software will work with the hardware you have selected. 4. Obtain application server, management software, and database driver components from vendor(s) for trial use. This includes negotiating with all the vendors to obtain the software required to perform a Proof of Value (POV) or POC. 5. Assemble the software components, including the application software design. 6. Install the base software components sufficient for performing a network test. 7. Test the physical system, working with vendors to identify areas where they will need to supply changes or fixes. 8. Obtain and deploy patches and fixes from software vendors and deploy them to the test system. 9. Repeat steps 7 and 8 until the test environment is stable. 10. Finalize vendor price negotiations, support contracts, and vendor service-level agreements (SLAs). 11. Fully document the platform state and platform-specific operating/maintenance procedures, vendor support engagement practices, and internal triage protocols. 12. Move the system from testing/development to production. 13. Start over when someone changes the application requirements, when a key vendor product is discontinued or reaches end of life (EOL) prematurely, or when a key component vendor is no longer viable. More can be found on migrating to the cloud and how Oracle Exalogic can make migrating to the cloud easier in this book to be released at Oracle OpenWorld: http://www.barnesandnoble.com/w/migrating-to-the-cloud-tom-laszewski/1030832062?ean=9781597496476&itm=1&usri=tom%2blaszewski
About

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

Search

Categories
Archives
« July 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
  
       
Today