Skip to main content

Cloud Computing and ITIL: Do it right this time!

And take a training before you do the standardization.

Workshop program:

DAY 1:

Cloud Language: The Taxonomy of On-Demand Computing
Clouds.
Grids. PaaS. There are dozens of names to describe on-demand computing, and lots of confusion. This block brings some order to the chaos, offering a comparison of different on-demand computing models including hardware-as-a-service, custom platforms, and large-scale compute infrastructures..

Cloud SLAs
How reliable is the cloud?
Enterprises demand predictable service levels, reliable delivery, and committed availability. This block will look at what level of service we should demand - and can expect - from cloud computing infrastructure, as well as tools and best practices for measuring it.

Running Clouds: What the Big Guys Know
A very small number of companies generate the vast majority of today's web pages, from Facebook applications to hosted sites. With compelling economics, they may be running most of the world's computing in a short while. This block gets behind the scenes of some of the world's Big Cloud operators for a look at what they know about running large-scale computing.

DAY 2:

The Big Migration: Moving the Data Centre to On-Demand
There's a slow, inexorable exodus going on. First bursty seasonal computing, then storage, then eventually all but specialized tasks are moving out of the corporate data centre and into the cloud. But this big migration is a gradual one. There are times when it doesn't yet make sense to embrace on-demand computing. We'll chart the course of a migration into the cloud to enable you to become innovators in on-demand provisioning and deployment.

Managing Applications in the Cloud
When it's your application on their infrastructure, you have a hard time knowing what's happening. On-demand computing environments often hide details from application operators as a result of their virtualization. New computing means new management. This block looks at emerging best practices for managing applications when they're running in the cloud.

Platform-as-a-Service: Building Business Processes in the Cloud
Cloud computing is often referred to as hardware-as-a-service, implying openness and complexity. At the other end of the spectrum, SaaS does not offer much room for customization. But there's a middle ground, where providers offer an on-demand platform, often with its own coding and conventions. This block looks at how companies can build custom applications that run in the cloud, letting the platform provider worry about operations and data integration.

Program inclusions:

- Courseware

- V3 Benchmarking guide

- Cloud computing book

- Morning tea, executive style lunch and afternoon tea

Register now to attend this program, U.S and Australia BTW!

Comments

  1. Hi Tarry, thanks for the post, the course runs in Los Angeles, Sydney, Melbourne and Brisbane - btw the link in the post goes somewhere else, here's the correct link:


    http://theartofservice.net/index.php?option=com_content&task=section&id=11&Itemid=56&trumbaEmbed=eventid%3D79168036%26view%3Devent

    ReplyDelete

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op