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.

Thursday Jun 07, 2012

Oracle Cloud offering - What makes it unique ?

Three things that make Oracle cloud offering unique:
1. SaaS, PaaS and IaaS offerings
2. Private and Public cloud offerings
3. Ability to seamlessly move between private and public cloud

Friday Mar 30, 2012

What does private cloud Daas or DBaaS really mean ?

Just had meeting with Fortune 1000 company regarding their private DBaaS or DaaS offering. Interesting to see what DBaaS really means to them:
1. Automated Database provisioning - Being able to 'one button' provision databases and database objects. This
includings creating the database instance, creating database objects, network configuration and security
provisioning. It is estimated that just being able to provision a new DB table in automated fashion will reduce time
required to create a new DB table from 60 hours down to 8 hours.
2. Virtualization and blades - DBaaS infrastructure is all based upon VMs and blades.
3. Consolidation of database vendors - Moving from over ten database vendors down to three.

Saturday Feb 25, 2012

Bringing Cloud 1.0 in house - Is moving to private cloud from the public cloud already happening ?

Visiting with a major corporation that is bringing all their managed services in house. Granted, most of the infrastructure is on cloud 1.0 (the mainframe), but is this something we will see with cloud 2.0 a few years from now? Certainly, the reasons the company is doing this - lack of innovation, not having easy access to data that belongs to them, being held hostage to the business and technical models of the service provider, and raising costs because the vendor feels the customer is stuck with them - are all items that folks are not hearing are things to beware when moving to SaaS or public cloud DaaS. Could be something to watch.

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 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
« April 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
   
       
Today