I had a lot of catching up to do this week. Due to the VCDX Defenses in Munich I did not have a lot of time to read blog articles during the week. Normally I take 30 minutes every day, at least, to catch up and read the interesting articles my favourite bloggers wrote. This week I had to prep next days sessions. We had eleven candidates and each of them handed in at least 100 pages of documentation(Design, Test Plans, Ops, etc). But I did manage to catch up yesterday and today, after doing this I came up with the following top 5:
Scott Lowe - Understanding Network Interface Virtualization As the proliferation of virtualization continues, this trend toward increased complexity also continues unabated. How, then, are we supposed to address this? NIV is intended to help address this problem. NIV seeks to remove the complexity from the edge—the NICs and vNICs—and drive that complexity toward the bridges. That is a key underlying principle behind NIV. Look back at the definitions: one characteristic of an IV-capable bridge is that the IV-capable bridge and all of its associated IVs appear to the outside world as a single bridge.
Vaughn Stewart - Transparent Storage Cache Sharing– Part 1: An Introduction The enabling components of TSCS is the ability within Data ONTAP to deduplicate storage objects (files, LUNs, volumes) and to create zero costs clones of storage objects (files, LUNs, volumes). These storage savings technologies often get 'parroted' quite regularly by some of the vendors offering traditional storage array platforms. For the sake of this discussion I’d like to differ any comparisons around storage savings technologies for a future post where we can spend the appropriate attention required to discuss these technologies inn greater detail.
Alan Renouf - Dell ESXi Management To help reduce the system footprint and to simplify deployment, the ESXi software does not have a traditional service console management interface where Dell OpenManage agents are installed. Instead, to provide the required hardware manageability, VMware has incorporated the standard Common Information Model (CIM) management profiles into the ESXi software. The CIM framework is an open standard framework that defines how managed hardware elements in a system are represented.The CIM framework consists of CIM providers developed by hardware vendors to enable monitoring and managing of the hardware device. By representing the hardware elements using standard CIM, ESXi provides any management tool (that implements the same open standards) the ability to manage the system.
Nicholas Weaer - FCoE Multi-hop: Why Wait? Let me visualize it for you. I want you to picture a FedEx Express truck. It has a simple job. It is given packages (frames) and it delivers them to addresses (FC address). Now, the FedEx Company prides itself on reliable delivery. It has all kinds of processes and methods(Flow Control, Classes of service) for ensuring that the truck reaches the address and delivers the packages on time. These methods have been finely tuned specifically for this job.
Duncan Epping - Scale Up Now it’s not only the associated cost with the impact of a host failure it is also for instance the ability of DRS to load balance the environment. The less hosts you will have the smaller the chances are DRS will be able to balance the load. Keep in mind DRS uses a deviation to calculate the imbalance and simulates a move to see if it results in a balanced cluster. Another thing to keep in mind is HA. When you design for N+1 redundancy and need to buy an extra host the costs associated for redundancy is high for a scale up scenario. Not only the costs associated are high, the load when the fail-over needs to occur will also increase immense. If you only have 4 hosts and 1 host fails the added load on the 3 hosts will have a higher impact than it would have on for instance 9 hosts in a scale out scenario.
26.09.2013 The End of the Google Summer of Code The GSoC coding period has ended last Monday. In this blog post, I will summarize what I have done during the summer, to give a general idea of what you can expect from a future version of Nepomuk, if my work is accepted by the Nepomuk maintainers. The source code of the first two projects is available in the steckdenis-gsoc2013 branches of the nepomuk-core and nepomuk-widgets Git repositories. The browser plugin can be found in the scratch/dsteckelmacher/nepomukintegration.git scratch repository. The Nepomuk Query Parser The first part of my GSoC project was to implement a new ...02.04.2009 Milian Wolff (milianw): KDevelop Hack Sprint Huzza! The KDevelop Hack Sprint 09 is now official. Thanks to the huge engagement of Alexander Dymo we will meet from the 19th to 26th April 2009. The meeting will take place at Alexander’s university, the national university of shipbuilding in Odessa, Ukraine. Thanks to the people there responsible for making this sprint possible by providing us with the premises, internet, power etc. Since this is my very first Hack Sprint and considering that I only recently started contributing to KDE in general and KDevelop in particular I am very excited. The topics I will plan to hack on include (...14.07.2010 Mario Fux (unormal): KDE work day 1 - xml and nepomuk I’m sitting in the train from Zurich to Burgdorf (Switzerland) and want to report, dear reader, about my first week of KDE (or atm qt) development. It was not really as I planned it, I did not work a whole day on qt and kde, but several hours during the week. As I told you last week my first week was about an xml indenter. Some years ago when I started to track routes for OpenStreetMap.org my Garmin GPS device spat out bad formatted xml (GPX) files. Bad means here that all of the content was on one line and as I sometimes wanted to extract single tracks me and the dear editor (Kwrite or ...15.01.2009 Aaron Seigo (aseigo): building a community around your F/OSS project Today has turned into another writing day for me. Huzzah! I started going through my list of blog-posts-I've-not-yet-written and decided to punctuate the day with a couple of them. So let's talk a bit about building a community around your F/OSS project.Usual disclaimers apply: this is what works for me, it may not work for you; I could be completely insane and talking about my posterior; I probably am just repeating what other people have said elsewhere; I'm going to be hypocritical in places by giving advice that I don't follow overly well myself. So there.Onwards!Why It MattersIt is not unc...27.01.2010 Troy Unrau: Camp KDE coverage summary Hi guys, I was preparing this summary of blogs and other coverage of Camp KDE to forward to our sponsors to show the activity occurring at the event. I figured I'd share it with the planet, if you folks are interested. If blogging is a measure of productivity, we certainly set the bar high. :) Dot.kde.org Posts (during and around the event only):http://dot.kde.org/2010/01/16/camp-kde-about-starthttp://dot.kde.org/2010/01/17/day-one-camp-kde-2010http://dot.kde.org/2010/01/21/camp-kde-2010-continues-more-talkshttp://dot.kde.org/2010/01/21/camp-kde-day-three-technical-talks-summarieshttp://dot.kd...16.02.2010 Aurelien Gateau: A week in Portland, Oregon I spent the first week of February in Portland, where I attended Canonical Platform Sprint for Ubuntu Lucid. We got some good work done on the DBusMenu front. You can read about it on Jono and Jorge blog posts. 18.05.2008 Michael Pyne (mpyne): Usability in interfaces So on an article on a programming weblog. The topic of the article was a group that decided to make a copy of Funpidgin and was essentially created because the people making the copy feel the Pidgin development team are not listening to the needs of their users. Celeste Lyn Paul, one of the KDE team’s usability designers (the group that tries to make the software we make actually usable by the end user) a comment about the amount of issues that people bring in the name of usability. He then later posted a S5W nuclear reactor plant. This plant was very old by the time I qualified on it (M...01.03.2008 Niels van Mourik (nielsvm): Re-entering the blogosphere Hello there blogosphere, It has been almost one year ago the last time I wrote a entry in this dusty blog. And since then, a lot of things changed in my life and on the web. And one of those is that I got a new, and my first serious job back in June last year. So, back in June ‘07 I started working at the funny called company FOSDEM took place at the free university of Brussels, Belgium. After some bad experiences with hostels the previous years I subscribed to the organised KDE accomodation by Lydia Pintscher (Quassel). Before the event started the FOSDEM people organised the ‘Fri...08.05.2010 Ronny Yabar (ronnyml): First steps with Grantlee and my KDE PIM GSoC project Well, coding officially starts on May 24, now is time supposed to read documentation, know your mentor(s) and discuss the project ideas, needs, requirements, difficulties, etc. but as many other GSoCers I couldn’t resist to code something. My goal for the last week was to write a very simple Qt application showing the power of Grantlee. The idea was to simulate that I am reading a message in Kmail and I want to change the theme again and again. You can take a look at the code in the soc-pim branch or: svn co svn://anonsvn.kde.org/home/kde/branches/work/soc-pim/kdepim/examples/mail_grantl...05.03.2008 Mike Arthur (mikearthur): Where is the love? I realise I’m probably going to get lynched for this but I think it needs to be said. If you, as a KDE developer, get annoyed with a KDE feature you didn’t write and feel like blogging about your bad interaction with a part of KDE or a spat with another KDE developer then please don’t. You have every right to do so but it isn’t good for you, it isn’t good for the other developer and it is really bad for KDE. The problem with a community like KDE doing the majority of their work online is that sometimes we forget basic social rules of interaction. If your blog is o...