Archive for Interesting

Are DevOps practitioners really Sysadmin or coding ninjas or just plain Grey?

Within my time working and researching DevOps, I started seeing a clear pattern that some very, very switched on people were doing a lot of really cool things and this was something that really inspired me to bring #DevOps to the SAP world. At the start of the journey, I looked at the practitioners of DevOps and saw this crack team of people who are able to move mountains with their exceptional skills and processes. Despite everything these people tell us, about it being about a complete organisational and conceptual change about the management of the IT landscape, you still see these exceptional people. Being a big fan of Babylon 5, the practitioners of DevOps initially started out in my head as being like the Rangers or the Anla-shok. The deeper down the rabbit hole you go though the more you realise that this is a complete and dangerous fallacy, because it is not about small band of special forces fighting from outside the system.

People traditionally identify with things more readily if they can relate them to their own experiences or to something that means something to them. Which is why when I discounted the Anla-shok equivalence I had wrongly applied, I couldn’t shake the Babylon 5 connotations. Upon reflection, through my knowledge of the B5 Universe, I came across something which started to make sense. The Grey Council of the Minbari, which seemed a much closer approximation for a number of reasons.

1. They have several castes, Worker, Religious and Warrior. IT also has many castes which can be defined, in fact probably 1000s of them, but an easy one for me is Development, Applications and Infrastructure.

2. The Council speaks as one to the outside world, despite internal disagreements. When IT departments speak externally, it should be with a unified voice – transparency is important and can be reflected without detracting from the decision being communicated.

3. Each caste has it’s own language, but in order to communicate effectively in everyday life, all 3 languages must be used. The same way in IT, each of the 3 areas of IT I listed above have their own languages, but to understand the full breadth, depth and scope of IT within a company, you must use and understand all 3 languages.

4. Technology is a tool to be used appropriately, it is not the end. The Minbari are the most technologically advanced of the ‘younger’ races, they live in harmony with their technology. They recognise that technology drives a great many things but also that there are times when technology is not appropriate. People should look to use the right technology to fit their purpose, for example, the Minbari use a fighting staff, the Denn’Bokto great effect when other races use plasma or laser or projectile based weapons in close quarters. A similar example in IT is the use of administration scripts to quickly pull a snapshot view of things. Like the fighting staff, it is easier than manually finding the information (like fighting with fists) or using a complex monitoring system (like a laser cannon).

5. They do their presenting in the style of a Stand-up/Morning Prayers. Not a big one, but I like the parallel that information is presented, judged and decided upon as a standing exercise.

This is not a perfect analogy and there are places where it lets itself down, mostly because Babylon 5 is a fictional series and we live in the real world which is much more complex and rich in experiences, but I think it works pretty well as a basic illustration. The only problem is finding non-IT people who liked Babylon 5 to try this analogy out on :-)

Let me know what you think in the comments section – I am happy to be told I am completely wrong as long as you offer a counter argument :-)

FacebookDeliciousPosterousDiggTwitterStumbleUponShare

#SAPAdmin or #DevOp – either or both

My last blog post explored my desire to increase my skill set to become more of a DevOp to help me to support current systems and also the new hybrid architectures which are entering our workplaces. I started a 2nd post to describe to people unfamiliar with DevOps what it is and what it is not – during the post I realised that I should really be describing in terms of #SAPAdmin, hence the title.

#SAPAdmin was 1st described, as far as I am aware, by Tom Cenens as a way of connecting the various Administrators within the SAP community – by reputation we are not the most social of bunches in the world :-). Although it is a great idea, I know that it has not seen as much traction as either Tom, Martin English and I would have liked.  I think that part of the problem has been a lack of direction in terms of what it stands for, and I feel that using the core concepts of #DevOps – we can bring that direction and purpose into the #SAPAdmin  ethos and provide a more coherent entity for admins to get behind.

So lets get stuck in with a quick breakdown of what #DevOps is and what it is not

1.  DevOps is noun which describes a person and a philosophy/methodology of supporting an IT landscape.

As a person, it is an individual who understands both infrastructure and code to enable them to support their applications and also bridge the gaps created by support silos.

As a methodology, it aligns itself with Lean and Agile and so embeds with the smaller team and faster deployment model of projects as opposed to the traditional waterfall life cycle support model.

2. DevOps has a useful memonic – CAMS

  •  Culture – this is critical to the whole thing, the culture of the participating teams must embrace openess
  • Automation – Why spend an hour on a daily task when you can spend two and have the results e-mailed to you every day
  • Measurements – how can you improve if you do not measure, everything!
  • Sharing – why write a script to check if your SAP system is up, go on the internet and find one. If one does not exist, then write it – but you MUST put it on the internet for others to find, pay it forward.

3. DevOps is not about just automation

Although automation plays a massive role in DevOps, through it’s emphasis on Event processing, KPI measurement etc… The real benefit in DevOps is for people to bridge the gaps in the Silos, something Basis admins/consultants traditionally do very well. This does however exact a price upon the practitioner, the requirement to keep learning and keep applying what they have learnt – it does not, will not and cannot stop.

4. DevOps is not a job title

DevOps is way of thinking and working, through sharing and collaboration you and the teams you work with create a culture that brings the best from yourselves and because you share as a team, it enriches the ecosystem in which you work.

5. It is not handing Developer keys to Basis admins, or giving Root access to developers

We each have a skill set with strengths and weaknesses, a DevOp is a person who is an all rounder with most technologies and is able/willing to work in the grey areas to get the work done. So Developers do not usually get Root access without a good reason or the proven ability to actually be trusted. Similarly a Basis admin does not get the right to deploy code to Production for the same reasons and the same validation requirements. DevOps work in the grey spaces between the silos

6. DevOps is not an end run around IT

DevOps is not a way for guerilla IT to enable people to bypass process, I would say that the use of measurement and automation enables IT departments to make better use of it’s information in Structured and Unstructured data sets to create things like Change controls and documentation. You know the things that are necessary to run a good solid service, that take forever to create and get approved and then never really get updated again. DevOps uses the principles of Lean and Agile applies them to process and documentation.

7. DevOps is not a reaction to a technology problem but a business problem

DevOps enable businesses and core IT to move faster in implementing and support technology/applications as quickly as Agile projects deliver them. This is absolutely vital in this age of outsourcing, a good solid DevOps team can run and support a service for a client ensuring that the contextual information that so often gets lost when working remotely is maintained.

We have all seen SAP embrace and encourage the principles of Lean and Agile, providing accelerators and advice to adopters. I believe that this is a great time to start to apply the lessons our organisations have learnt in terms of Agile and Lean projects to our staid and overly complicated silo’d support structures.

As DevOps we have a massive advantage over other software/systems administrators – we have 2 products that are open, extensible, stable and free to build a DevOps service around

  • Solution Manager 7.1 – the structured data component of the landscape providing all measures and KPIs and something which can be closely aligned to the business and it’s processes
  • SAP Streamworks – the collaboration tool which through Web Services can/should be able to be extended to work with Solution Manager

Let me know what you think of applying the concepts of DevOps to the SAPAdmin community

Reference Links

What is the DevOps thing anyway

What Devops means to me 

 DevOps and Agile Operations

What DevOps is not

FacebookDeliciousPosterousDiggTwitterStumbleUponShare

DevOp and why I want to be one

Over the last year I have had a number of adventures, some good and some bad – but all of them experiences. Last month I read about a term for the 1st time that really spoke to me, it encapsulated a concept which had been brewing in my head for a while – a DevOp, Developer Operator.

In November last year I was in Madrid attending SAP TechEd, and you could not move for people talking about various platforms and Developers being the new kingmakers – being an Basis guy specialising in infrastructure it may have been boring for many people, but for me the lightbulb was turning on. I was very interested in how to connect technologies together, not just how to build the infrastructure and let other people worry about that stuff.

These thoughts fermented a little more, I continued to experiment with Ruby, C# and my Microsoft Kinect – gaining some more skills as time would allow. At Teched I met the excellent James Governor and Tom Rafferty, two analysts from Redmonk who I have a great deal of time and admiration for. After following them on Twitter for a while, I found out about Monkigras, a developer conference in London. I glanced at the attendee list and booked my ticket, paying for it myself as I figured “why would my employer pay for me to go to something so far outside my day job”, took 2 days leave and arranged to stay at my friend’s house.

Despite knowing only 1 other attendee,  Monkigras would turn out to be an amazing conference, I heard lots and lots of new words, understood perhaps about 20% of them and had to make copious notes of the others. The thing that I took away from it the most was the developers and APIs are the future, infrastructure is a commodity that just needs to exist – the real value is in the data and it’s manipulation. “It always has been” I hear you cry – well that is correct but instead of putting it into Excel and making stupid graphs or putting it into PowerPoint, lets use applications to perform transformations, link it to other data attributes from another data set through an API and turn it into something amazing – this link is from a speaker who used GitHub and LastFm to create a music map of developers

For me my true love is not code, I like the idea of it and messing with it, but if you tried to get me to write as a job, one of us would be dead in about a week – so I thought some more about what the perfect balance would be. My good friend Simon McCartney came to mind, an exceptional infrastructure administrator and someone who is comfortable working with code, he calls himself a digital carpenter, Hugh MacLeod would call him a digital crofter. The ability to continue to work as an infrastructure person along with the ability to work with scripts and code is a powerful combination which provides a great deal of value to your business and the team.

DevOps Manifesto

We are uncovering better ways of running
systems by doing it and helping others do it.
Through this work we have come to value:

Individuals and interactions over processes over tools
Working systems over comprehensive documentation
Customer and developer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on
the right, we value the items on the left more

There are a number of reasons why I am drawn to the way of the DevOp, most of them are encapsulated above, and perhaps I will explore these personal areas in more detail in public and risk the wrath of various people, then again perhaps not. The one of the main attractions being that with shorter life cycles and products becoming easier to deploy, a multi-talented person who is a solid ‘all-rounder’ will be in greater demand than the 2 or 3 niche people you would have hired previously, as software lifecycles are shorter – living with your mistake is not as long as it used to be.

Another thing I like about development, it the ability to do really smart things with data like this visualisation of Facebook relationships – how totally cool is that picture which is derived from the most basis data which can be queried form the Facebook social graph

So for now I am going to continue down the road of becoming a DevOp, taking every opportunity to deploy a code or script solution to improve my effectiveness and provide increased value for my clients.

Ultimately I want to build things, real, virtual and data based. I want those things to mean something, to me and my clients – As Hugh MacLeod would say – I have the Hunger and I am damn well going to use it

 

FacebookDeliciousPosterousDiggTwitterStumbleUponShare

Identity or Identification

I was recently asked by a friend why my nickname was BoobBoo, I explained that it was a long story which would take a while to explain – she then remarked that perhaps it was time for a change, which I thought was a little unusual but let it simmer a while in my head. BoobBoo is a name I have been known as for about 15 years now, it started as a bit of a joke but as the years have gone on, it has become a very clear part of who I am – I have attached an identity to it.

This concept is very important when thinking about how people are identified in both their real life and their online life, something that has become very important with the whole Google+ real name fiasco. For me identity and identification are two different things both semantically and spiritually. Identity is a name or title that you place upon yourself, an identification is the name or title that someone associates with an object based upon it’s characteristics – they are not mutually exclusive. I have several identities in my life, if you look at my biography, I am husband, a son, a brother, an in-law, an uncle etc… within all of these identities I have two names, Chris and BoobBoo. Granted most people I know call me Chris when we are talking in person and BoobBoo when communicating online, but for me there is no difference as I am the same person within both realms of my life. Although for people like Google this is not the natural state of affairs for online identities, I have looked at the arguements for why they are pursuing this line of thinking, I think they are dead wrong and below are some reasons why I think they are.

1. Anonymity encourages people to act in ways they would not do if their identity was known – I assume that means people are emboldened by the fact that people do not know who they are and so can say or post things that will cause harm or offence to others which they would never have the stones to say if their actual name was attached to it. I actually see some logic in this, but ultimately a lot of people who have built an identity around their online life have basically been told that your name – your identity online is less important than your real-life one, which is surprising as people are spending so much time linking both of them!

2. You should have a centrally controlled identity which will identify you to online goods and services -this follows on from the 1st point, if Google, Apple and Amazon are going to get into the banking or money business then they need to be able to identify who you are. This is a vital part of any business transaction, the ability of both parties to be able to trust each other to honour a contract, if they cannot be trusted then there can be no contract. As a human being, knowing the identity of the other party is important as, for many, it forms the basis of trust. It is an interesting fact that I can have as many identities as I want, for example I can obtain a credit card in the name of Dr John Kernaghan. If I am not using the identity to defraud someone, then I call myself anything I want and obtain money, credit, good and services, it is up to the issuer if they want to trust me as that identity. I have traded with Amazon and E-bay for over 10 years as BoobBoo, and sent packages all over the world and paid with many different methods not always in my name but each transaction has been honoured by both parties – surely that counts for something.

Ultimately I am identified by government documentation, like my biometric passport or my driving license, which I cannot legally obtain in any other name. According to Google, my name, something I did not choose is to become my complete identity managed by a private company with whom I hold no real social contract, something that is going to become less equitable to users given Sony’s gambit to change it’s T&Cs so that people who opt-in will loose the ability to take legal action against them if Sony is hacked again and that precious identification data is lost to hackers, I suspect that soon other online service providers will change their T&Cs to match. I cannot blame them, these companies are always under attack by people to gain personal details of their users and like counter-terrorist organisations, they have to be lucky all the time – the hackers only need to be lucky once.

So where has all this left us, I am secure that I have many identities and have 2 names with which I live my life and I try to live my life equally and with the same rules independent of the medium. Companies like Facebook, Google, Apple and Amazon are desperate to capture your social graph, which will eventually morph into your identity graph. They want data to ensure they can target you as accurately as a Tomahawk Cruise missile targets enemy infrastructure and in order to link that data to you they have to be able to identify you, and the easiest way to do that is to tie your characteristics to a single identity. It feels like analog thinking in a digital world, which I think might be generous – deep down I think it is small minded and petty for someone to think they can tell me to chose my identity especially when they want me to trust them with that identity without a social contract that has penalties for each participant.

 

 

 

FacebookDeliciousPosterousDiggTwitterStumbleUponShare

@Eliza_Newfie playing with her new toy for a while, then finding the much more interesting kitchen roll

FacebookDeliciousPosterousDiggTwitterStumbleUponShare

Attending my first lecture in 10 years without being on the course #educatingrita

Image

FacebookDeliciousPosterousDiggTwitterStumbleUponShare

Just had a G+ Hangout with a half naked @dahowlett – I think he might need to read this http://bit.ly/r1UyCz

Dennis_topless

FacebookDeliciousPosterousDiggTwitterStumbleUponShare

Non-fiction shelves filling up nicely, now to re-arrange the fiction & then sit and osmose the books

Image

FacebookDeliciousPosterousDiggTwitterStumbleUponShare

New bookshelves built now just to populate with tomes of knowledge as these are the non-fiction shelves

Image

FacebookDeliciousPosterousDiggTwitterStumbleUponShare

Picture of the day – the Shuttle as seen from the ISS :-) Taken from the BBC website – http://bbc.in/nNLQ1B

Bbc_shuttle_pic

FacebookDeliciousPosterousDiggTwitterStumbleUponShare

Switch to our mobile site