Archive for May, 2010

Red Hat’s virtualization strategy has redundancy – Quo vadis?

Thursday, May 27th, 2010

A couple of days there have been some reports that Red Hat will release a commercialized version of deltacloud, an abstraction layer for different kinds of virtualization technologies and clouds such as VMware, RHEV, Amazon EC2 etc.

Red Hat puts a lot of resources on virtualization, they maintain and/or sponsor multiple projects in parallel. The most important from my point of view is libvirt which is as well an abstraction layer for different virtulization technologies such as VMware, KVM, Xen and others. Libvirt and deltacloud are partially redundant.

It is not the only redundancy created by Red Hat. There is also O-virt “competing” with RHEV. Both are not tightly bound to RHN satellite or Spacewalk.

RHEV works with system templates similar to those at VMware. On the other hand: Koan, together with cobbler is a deployment software for virtual hosts and was recently bundled with RHN satellite.

Not all of those Red Hat virtualization projects are working well together. So the question arises: What is the strategy of having such redundancies of projects? Why not integrating all of this projects and glue them together?

Lots of questions…

Have fun!

Fedora 13 is released!

Wednesday, May 26th, 2010

I had my doubts that Fedora 13 get released. I was wrong, and that good!

I did not had the time yet to upgrade my F12 systems, according to a lot twitter users it is a smooth process.

Read the Release Notes. I’ll be happy to hear your feedback :-)

Have fun!

Luc

Will Fedora13 really be released on 2010-05-25?

Monday, May 24th, 2010

After being postponed twice, it seems that this time it can be postponed again due to some show stoppers.

As of today, three bugs are of status new. From my point of, none of them is a real show stopper. The gravest one is possibly #587627 which is of status ON_QA.

So there is still a chance to get F13 released tomorrow.

Have fun!

A brief test of OTRS::ITSM Changemanagement and the insanity of ITIL compliant software

Sunday, May 23rd, 2010

OTRS is known as best-of-breed in open source incident management systems. Since quite some time, OTRS made its product ITIL V3 compliant. Means: It also comes with a change management module.

At work we use a complex and extremely user-unfriedly software. This brought me to the idea to test the OTRS change management module in order to propose OTRS as a replacement for the currently used software for the Change- Incident- and Problem Management.

Incident- and Change Management integration
I was surprised how easy it is to change the ITIL type of a ticket from “Incident” to “RfC”. As soon as the ticket is of type RfC a new button appears: Create Change. The ticket gets automatically linked to the new change. Creating the change looks strait forward. Assigning people to the CAB was also quite easy. You also can generate a CAB-template with a few clicks. So far so good…

Where the trouble begins
The newly created change is now of status “Requested”. Whats next? Right! to approve it! But how? OTRS is using something they call “state engine”. You need to add “Workorders” and “Conditions” to your change. For a standard-change I made a template with a condition “If workorder-title=Standard-Change, set change to status approved“. In this case you just link a “workorder” to the change, call it “Standard-Change” and your change will be approved. Next Condition is to set the state of the change to “successful” when the “Workorder” is of state closed. At the end of the day three tasks and approx. 20 clicks for a simple standard-change. Not too bad.

Where it goes to insanity
Non-Standard-Changes usually have a CAB (Change Advisory Board). This makes sense because the change-requester usually does mot have the full overview about complex systems and services. Now, as I wrote further up, it is quite easy to create and assign a CAB to a change. So how works the process? Usually every single member of the CAB must approve a particular change. It should be easy to send all the CAB-Members a Email with a link where they can approve or reject the change. In OTRS this is a huge and very complex task.

The change manager or change creator has to create a “workworder” of type “Approval” for every single CAB-Member AND create a condition to it. If you plan a huge change such as upgrading Powerlines in a Datacenter, the CAB can grow to dozens of people. I tried with two CAB members and it was costing me about 20 minutes to create it (Without proper texts in the change and workorders). Think about a 20-people CAB. It will take hours just to create a proper change! This is so nuts!

Why are all ITIL compliant change mangement tools just crap?
ITIL processes are quite simple. One should think it is also easy to implement them in software and in companies. Wrong! The mind of People with ITIL-Roles such as “Change Manager”, “Problem Manager”, “Availability Manager” and “you-name-it-manager” works obviously different. It looks like they add as much complexity as possible even to every simple task. Obviously the ITIL-compliant software developers think the same way or got the orders to do so. I think this is the root cause of the completely unusable software OTRS::ITSM Changemanagement and others such as Remedy and Peregrine.

Conclusion
As there is no easy usable software on the market, companies should either write its own software or getting the less-crappiest software around. At the end of the day I’m tired of this and I’m not going to test similar software again.

Android 2.2 SDK released

Sunday, May 23rd, 2010

On 2010-05-20 Google released the SDK version 2.2 of its Android Linux OS for Mobile devices. It will take some time before the software will be available for the phones.

Main features enhancements is performance improvements due to the Dalvik JIT. Performance will be up by factor 2 to 5. This brings me to the question: Was is intentionally that slow before? Just to be able to announce a major breakthrough later on? Anyway: Good to know that the speed has improved.

The major new feature for me is the ability to install apps on SD-storage. Myself I’m using the CyanogenMod version 5.0.6 and already got this feature on my Nexus One. The tricky thing is to partition the SD Card. To be able to install apps on SD, there must be a partition with ext2, ext3 or ext4 filesystem. Search the internet for howto’s.

I’m also looking forward to test the better exchange support or if Touchdown pro is still needed to get it working.

Finally you can automatically update apps, plus the ability to update all application with a single tap without 3rd party software such as aTrackDog.

Have fun!