I’ve spent more than my usual amount of time in an around airports this week – Travelling to and from the Tech Field Day event in Boston , then hung around with a few of the other delegates before their flights back.


It seems that one of the other delegates flights had a pretty severe delay on it due to the incoming flight being late. We realised the only way his flight would be on time would be if they used a different aircraft. My mind immediately went off on a bit of a tangent to Cisco UCS ( as you do ! )


The flight plan consists of a number  , a given size and model of Aircraft and a source / destination. With me so far ? The flight plan is given to a particular aircraft , so plane #767-4001 becomes Delta Flight DL270 going from Boston to Heathrow – and will be known as DL270 while that Flight is in use. If for some reason there is a problem with 767-4001 , the airline can opt to use a different plane , for example 777-4002 , which is not quite the same model and in fact has a few more seats & flies a little faster. The plane is still able to take of and land under the identity of DL270.


This is very much like a service profile – its not fixed to the hardware ( plane ) and can be associated with different hardware ( which may not be of quite the same specification ) should you require. Its is purely a definition of what would make up that profile just in the same way that we have defined flight DL270 to fly me from Boston back to London.


Now if I could only persuade my UCS Chassis to serve complimentary drinks…..