05.11.10
Posted in Hosting Thoughts, Work at 8:39 am by JohnB
It used to be so easy – if you were a techie – to describe an environment. You’d simply list out the numbers and types of server, the OS versions running and the server-side apps they’ve been dedicated to. We’d even call them “The SQL server, the Exchange Server, the AD controller…” These physical devices were know by the service they were running.
And if you wanted to add another service you’d, more than likely, add another server or two to run it. This was the easy way, the most trusted and risk free way because we knew that the requirements would only ever increase and we were building in future-proofing. We had to because these things had to last, to run and perform for 3-5 years! This was really about money, IT departments speculated at the start of each financial year as to what would need to be replaced, upgraded and what new systems or services would be required. They got their budget, or a part thereof, and then did what needed to be done, perhaps picking up a few ‘goodies’ along the way – because that’s what we did!
So corporate server rooms and datacenters and even small businesses with the typical too-hot, under-powered cupboards had server hardware spinning away just waiting, ever waiting, for the time when their capacity would be realised. Of course the reality is that, that time never really came. Servers went end-of-life and were retired, re-purposed and ultimately scrapped (or sold on eBay), budgets were re-negotiated to replace them with the newest models because “they will provide significant future-proofing” and the cycle of speculation began again.
The times they are a-changing though and the move is away from the old server-per-service model and we are now starting to talk about workloads. The Database workload, the Exchange workload, the Web workload, the Application workload… All are the new expressions of what needs to be done and none talk about the hardware underneath – and neither should they!
The correct and only way to deliver services is in the most resilient and efficient method possible. This means taking a number of physical resources sufficient to provide service continuity in the event of failure and making them run these workloads. If that sounds kind of wooly and fluffy, well that’s because it is! Server hardware should not, now, be the definition of a service infrastructure it should simply be the mechanisms upon which the services are built.
Infrastructure-as-a-Service (“IaaS”), one of the three main “Cloud” definitions, means that I can define what I want in terms of workload and get it, I don’t need to worry about the numbers, the networking configuration, the will-it/won’t-it nature of any fail-over I’m expecting or speculate upon the “future-proofing” my hardware spend is assuring. This is because I have no hardware spend.
If my requirements are for a database and application workload I can simply buy the horsepower I need to support that DB/Application combination and use it, usually within a few hours. OK I don’t have the fun of specc’ing up a server set and un-boxing the kit when it arrives but they were short-lived pleasure anyway!
For smaller businesses and organisation there is the issue that this is going to be a hosted service, out there in “The Cloud” or simply on-line if you’re me! And this might pose something if an initial barrier to adoption. That’s OK! Really it is, there’s no-one telling you that you have to move your “stuff” out there today, or even tomorrow. IDC has predicted that we’re in the first phase of an adoption cycle which may last up to 30 years! It’s fine to hang back, make the most of your current investment, make sure you understand what it means to adopt an on-line/hybrid service model and make sure your strategies – both technical and business – are in place and ready for when you make the move.
For larger enterprise businesses though, it’s perfectly possible to build an IaaS infrastructure in-house. The technologies are available today and, depending upon the age of your kit, you might not need to spend a huge amount on server hardware to make it happen. The keys to delivery are virtualisation and automation and the tools are ready now to help you deliver this “Private Cloud”. It’s a change in thought processes for any IT Team but it’s also the right way to think about your technology services and how you consume them.
Remember the word is Workload, the method is up to you!
Permalink
01.20.10
Posted in Work at 10:30 am by JohnB
I got this through on am email today and, although I don’t usually share stuff that comes through that medium, this kinda worked for me…
No one can make you serve customers well…. that’s because great service is a choice.
Harvey Mackay, tells a wonderful story about a cab driver that proved this point.
He was waiting in line for a ride at the airport. When a cab pulled up, the first thing Harvey noticed was that the taxi was polished to a bright shine.. Smartly dressed in a white shirt, black tie, and freshly pressed black slacks, the cab driver jumped out and rounded the car to open the back passenger door for Harvey .
He handed my friend a laminated card and said: ‘I’m Wally, your driver. While I’m loading your bags in the trunk I’d like you to read my mission statement.’
Taken aback, Harvey read the card.. It said: Wally’s Mission Statement: To get my customers to their destination in the quickest, safest and cheapest way possible in a friendly environment….
This blew Harvey away. Especially when he noticed that the inside of the cab matched the outside. Spotlessly clean!
As he slid behind the wheel, Wally said, ‘Would you like a cup of coffee? I have a thermos of regular and one of decaf.’ My friend said jokingly, ‘No, I’d prefer a soft drink.’ Wally smiled and said, ‘No problem. I have a cooler up front with regular and Diet Coke, water and orange juice..’ Almost stuttering, Harvey said, ‘I’ll take a Diet Coke.’
Handing him his drink, Wally said, ‘If you’d like something to read, I have The Wall Street Journal, Time, Sports Illustrated and USA Today..’
As they were pulling away, Wally handed my friend another laminated card, ‘These are the stations I get and the music they play, if you’d like to listen to the radio.’
And as if that weren’t enough, Wally told Harvey that he had the air conditioning on and asked if the temperature was comfortable for him. Then he advised Harvey of the best route to his destination for that time of day. He also let him know that he’d be happy to chat and tell him about some of the sights or, if Harvey preferred, to leave him with his own thoughts…
‘Tell me, Wally,’ my amazed friend asked the driver, ‘have you always served customers like this?’
Wally smiled into the rear view mirror. ‘No, not always. In fact, it’s only been in the last two years. My first five years driving, I spent most of my time complaining like all the rest of the cabbies do. Then I heard the personal growth guru, Wayne Dyer, on the radio one day.
He had just written a book called You’ll See It When You Believe It. Dyer said that if you get up in the morning expecting to have a bad day, you’ll rarely disappoint yourself.. He said, ‘Stop complaining! Differentiate yourself from your competition. Don’t be a duck. Be an eagle. Ducks quack and complain. Eagles soar above the crowd.’
‘That hit me right between the eyes,’ said Wally. ‘Dyer was really talking about me. I was always quacking and complaining, so I decided to change my attitude and become an eagle. I looked around at the other cabs and their drivers.. The cabs were dirty, the drivers were unfriendly, and the customers were unhappy. So I decided to make some changes. I put in a few at a time. When my customers responded well, I did more.’
‘I take it that has paid off for you,’ Harvey said.
‘It sure has,’ Wally replied. ‘My first year as an eagle, I doubled my income from the previous year. This year I’ll probably quadruple it. You were lucky to get me today. I don’t sit at cabstands anymore. My customers call me for appointments on my cell phone or leave a message on my answering machine. If I can’t pick them up myself, I get a reliable cabbie friend to do it and I take a piece of the action.’
Wally was phenomenal. He was running a limo service out of a Yellow Cab. I’ve probably told that story to more than fifty cab drivers over the years, and only two took the idea and ran with it. Whenever I go to their cities, I give them a call. The rest of the drivers quacked like ducks and told me all the reasons they couldn’t do any of what I was suggesting.
Wally the Cab Driver made a different choice. He decided to stop quacking like ducks and start soaring like eagles.
How about us? Smile, and the whole world smiles with you…. The ball is in our hands!
A man reaps what he sows. Let us not become weary in doing good, for at the proper time we will reap a harvest if we do not give up… let us do good to all people.
Ducks Quack, Eagles Soar.
Permalink
01.13.10
Posted in Work at 12:52 pm by JohnB
Most, if not all, organisations have in some form an “Internet Policy” which would typically describe what is acceptable to do with your browser during office hours. I’ve seen these range from ‘anything as long as it’s legal and you don’t waste time’ to ‘these 3 sites for these 5 people ONLY’.
And this is fine if you expect people to leave their brains at the door on the way out of the building and their mobile devices at the door on their way in. The problem is that neither of these are practical in the world today (OK certain security-sensitive organisations do actually require that you NOT bring mobile devices into the building but they kind of fall outside of my scope of general business here). So even if the strict policies of the organisation are enforced at the desktop, folks are still able to access Facebook, twitter, blog-spaces and the like from their “mobile phones”. I’m quoting here because as time passes these devices have become so much more than phones and the name increasing doesn’t fit. These are the the small screens which make up the screen triumvirate of most of our lives; small screens = mobile devices, mid-screens = desktop systems (PCs, Macs etc) and large screens being our TVs which are also becoming a source of rich media and not just TV broadcast.
But I digress, the point here is that very few organisations have put in place policies and guidelines to help the individual employees understand what they should and should not share outside of the company, how they communicate what they are doing and who that communication is available too. An example of this would be the Facebook invitation to ‘Friends’ to attend a party. The intent was honest but the method and audience hadn’t been properly considered, the result was several hundred people turning up and a seriously wrecked house. Translate that into Business terms and you get my point.
I’m not any sort of advocate of nannying at all, and I believe that in the majority of cases common sense prevails and individuals are reasonable sensible. HOWEVER, we live in a statistical universe and given enough people, someone will do something stupid and potentially damaging unless strongly advised otherwise, simply out of ignorance or lack of thought.
So policies ARE necessary to help to mitigate these statistical certainties and to enable businesses to protect themselves. As an employer, ask yourself these simple questions:
- If someone blogged about their working day, could they unintentionally reveal sensitive information?
- Could someone updating their Facebook status as “This place sucks, no-one EVER listens!” reflect poorly on you as an employer?
- Could a Twitter update of “Another meeting, I wonder what bad news is coming now?!” impact your business confidence?
While it’s true that the comments of one person may not even register, it’s also true that it only takes one person to start a rumor.
Being able to identify and address ANY sort of communications channel and how it could be used or mis-used is vital. Those forward thinking businesses have adopted social media as a marketing medium and done so with great success, so it MUST hold true that bad news has the same, if not greater, impact.
Permalink
« Previous entries Next Page » Next Page »
