I’m in San Diego attending LISA this week. LISA is, by far, the most useful conference I’ve ever attended. It also happens to be the best place in the world to meet the authors of one’s favorite O’Reilly books. So far I’ve seen Tom Limoncelli, Randal Schwartz, Elizabeth Zwicky and AEleen Frisch roaming the halls….
It’s easy to strike while the iron’s hot. It’s easy to leave a conference and decide that it’s time you really should implement that stable configuration management, or that full featured monitoring solution. I already have a dozen items that I want to get done, but will probably only accomplish 2 or 3(if I’m lucky)….
Alas, I am not at LISA, but others are. Derek J. Balling, co-author of the O’Reilly book High Performance MySQL: Optimization, Backups, Replication, Load Balancing & More, posts a decent summary of the recent USENIX/SAGE/LOPSA saga, putting a positive spin on it.
!! Introduction
Well, as I promised in my first installment, here’s the very beginning of an overview of why USENIX and newSAGE/LOPSA are complementary, probably need each other, yet cannot remain a single organization. Remember that this isn’t about right and wrong, or competition, or past mistakes. It’s just about differences in communities, services and goals.
There are lots of reasons that USENIX and newSAGE (LOPSA) had to eventually split, but the most important are:
* the continuum of research to operations – different communities
* trends in computer science, “Information Technology” and how USENIX and SAGE evolved in response to these trends
* incompatible goals of each organization – the need to serve different communities
In this entry, I want to concentrate on the different communities that are served by USENIX and LOPSA. Yes, there are some stereotypes here, but almost all of you will be able to determine very easily in which of these communities that you (and the people you know) belong. Most people are in multiple communities at different times in their careers, or even as they serve different roles in their work. Don’t get hung up on the details, just look at the broad brush strokes…
It was inevitable that USENIX and “newSAGE” (now LOPSA) split in some fashion. The process that started 16 months ago will run to completion, one way or another. If it doesn’t, it will only begin again at some time in the future.
The best we can do is make this transition as painless as possible for the community, and try to ensure that it is a win/win for both organizations.
This isn’t about “good vs. evil”, or “us vs. them”, or “who made the biggest/worst mistake” either.
It’s about differing visions, differing goals, and a difference in the communities.
Hi. My name is Tom, and I’m a system administrator, and I have been for a very long time, about 20 years so far. But more on that later.
I’m also the President of LOPSA, but that’s not what I’m really here to talk about.
Over the past few days, I’ve been asked a lot of questions about this new thing called “LOPSA”. Yeah, lots of people just ask about where the name came from, or make bunny jokes, but I just 🙂 and say “Isn’t it a lovely evening?”.
The other thing people have been asking about is “Why?” There are a few simple answers, and a lot of complex answers, but the themes that run though all the answers are “Because it is time, and because it is needed.”
Unfortunately, sound bite answers like that are really insufficient for difficult problems, no matter what politicians would have us believe. And this really is a more complex problem than most people have realized. I’ll get to the answer(s), but it will take some time. Bear with me.
!! Introduction
Well, as I promised in my first installment, here’s the very beginning of an overview of why USENIX and newSAGE/LOPSA are complementary, probably need each other, yet cannot remain a single organization. Remember that this isn’t about right and wrong, or competition, or past mistakes. It’s just about differences in communities, services and goals.
There are lots of reasons that USENIX and newSAGE (LOPSA) had to eventually split, but the most important are:
* the continuum of research to operations – different communities
* trends in computer science, “Information Technology” and how USENIX and SAGE evolved in response to these trends
* incompatible goals of each organization – the need to serve different communities
In this entry, I want to concentrate on the different communities that are served by USENIX and LOPSA. Yes, there are some stereotypes here, but almost all of you will be able to determine very easily in which of these communities that you (and the people you know) belong. Most people are in multiple communities at different times in their careers, or even as they serve different roles in their work. Don’t get hung up on the details, just look at the broad brush strokes…
I’ve been thinking a bit about how to foster volunteerism and developing some principles to make it vibrant and healthy. Things like: * Make realistic time committments. Saying that you can commit only 2 hours a week and delivering is better than saying you can commit 8 and delivering 4. In order to effectively divide…
Most people don’t realize the level of management information that you can get from a Netra (104 or 200 or v120). Sure, they are old and slow by modern standards, but they are extremely rugged and come in AC and DC varieties which is very handy when you are a telco shop or have telco…
We just got a (circa 2005) Dell PowerEdge 6850, on which I now want to run (circa 2002) Red Hat Advanced Server 2.1. The Red Hat Hardware Certification matrix shows the 6650 as the only certified 6000-class Dell server. This helps confirm why anaconda ends up giving me the “No valid devices were found on…
How does the old joke go? “Bored with work? Tired of toiling away? Have a meeting!” With most organizations today, we all too often fall prey to unproductive meetings. This leads to wasted time, frustration, and lower morale. This situation is so common, according to my anecdotal findings, that I wanted to find out if…