Whats shocking to me is that the talk is not philosophical, rather its 1 hour 16 minutes of non-stop practical pointers, ideas and applications.

Randy Pausch Lecture: Time Management

I think my chief takeaway was that time is, and should be treated as, a precious commodity. If you are spending time, it should be on something worthy of that sacrifice. What this also implies is that if someone wants my time, I should ensure they are using my time wisely. Time is not an infinite resource.

This point is particularly key to me because I am a wanna-be perfectionist. I will drag on and on and on for days, weeks, months trying to think something through before truly devoting myself to it. For code this means that I want to be able to visualize all the logic before I start writting. Now, this is an entirely flawed concept, because any reasonably complex program is going to have more lines of code in it that you can keep in your head. Therefore, when I try to visualize everything I'm actually just moving from visualizing one small part to another, and loosing something during the mental context switch. I should instead just start writing the program and then deciding ahead of time to improve it later. This is essentially my version of "a working program today is better than a perfect program in a year".

I'm reminded of a phrase I cooked up with Tamarah (my wife, the lovely women above) several years ago. When discussing something emotional and complex, you can spend a lot of time thinking over and re-thinking the right way in which to phrase it to provide clarity. But this is exceptionally hard to do and very time consuming. Therefore, when we see eachother in this "I'm not sure how to put it..." pause, we will say: "Badly... and work from there." So we work in drafts, making it clear that the first draft is probably horrifically inaccurate and wrong, but we'll work towards clarity together and in doing so get a clearer picture of the topic than we'd ever get from the perfect one line explanation.

For sysadmins I find this really hard. It seems all we sysadmins are both perfections and ADHD at the same time. I wish I were exaggerating, but most of us really actually are clinically hyperactive... its a job qualification. The problem is that while we can keep a lot of plates spinning, we're very bad (on the whole) of providing timely delivery with high quality, unless an external force demands it. This is why sysadmins have to have managers. Geeks without overlords will do amazing things and deliver very few of them. (The description of a good overlord is an excessive left for the reader.)

I digress. I personally recommend watching this video repeatedly, say every 3 months. I re-watch David Allen's GTD talk at Google every couple months already. I always find something new in it and it's a great reminder to get back on the wagon. More importantly, personal management is dry and tedious, so hearing enthusiastic guys like David Allen or even Tony Robbins (say what you will, his TED talk was fantastic) can be a real pick-me-up.

6:45pm
274 Castro Street, Suite 204
Mountain View
above Meyer Appliance & Kitchens look for the OpenSolaris sign on the door 

Tonights guest will be Garrett D'Amore presenting Illumos and Anil Gulecha presenting Nexenta.

The discussion will really be in essence about the rebirth of OpenSolaris in a post-Oracle era.

If you can't attend in person, it will be webcast: http://www.ustream.tv/channel/svosug-feed2

Be there in person or attend the webcast, but don't miss it!

A big thanks goes out to Alta Elstad for keeping the faith and keeping SVOSUG alive! Alta rules!

Whereas Oracle has continued ignore requests to appoint a liaison to work with the OGB concerning the future of OpenSolaris development and our community, and Whereas Oracle distributed an email to its employees on Aug 13 2010 that set forth Oracle's decision to unilaterally terminate the development partnership between Oracle and the OpenSolaris Community, and Whereas, without the continued support and participation of Oracle in the open development of OpenSolaris, the OGB and the community Sun/Oracle created to support the open Solaris development partnership have no meaning, and Whereas the desire and enthusiasm for continuing open development of the OpenSolaris code base has clearly passed out of Oracle's (and thus this community's) hands into other communities,

Be it Resolved that the OpenSolaris Governing Board hereby collectively and individually resigns, noting that under the terms of the OpenSolaris Charter section 1.3.5 the responsibility to appoint an OGB passes to Oracle.

Also see the OGB Call Agenda.

Here is the short version: OpenSolaris is dead. No more real-time/nightly code pushes. OpenSolaris 2010.05 will not happen, nor will any in the future. Solaris 11 Express will be the new "developer" release which will be available through OTN. Solaris will remain open source, but code will only be released after the product ships, not before.

Now, lets go bit by bit.

Today we are announcing a set of decisions regarding the path to Solaris 11, and answering key pending questions on open source, open development, software and binary licenses, and how developers and early adopters will be able to use Solaris 11 technology before its release in 2011.

So, Solaris 11 is the new hotness and the "community" is reduced to "early adopters".

Solaris must stand alone as a best-of-breed technology for Oracle’s enterprise customers. We want all of them to think “If this has to work, then it runs on Solaris.” That’s the Solaris brand. That is where our scalability to more than a few sockets of CPU and gigabytes of DRAM matters.

This goes on for a while, but the message is clear. Solaris needs to not simply be another UNIX OS... it needs to be, as it was in the 90's, the enterprise platform of choice.

We will continue to grow a vibrant developer and system administrator community for Solaris. Delivery of binary releases, delivery of APIs in source or binary form, delivery of open source code, delivery of technical documentation, and engineering of upstream contributions to common industry technologies (such as Apache, Perl, OFED, and many, many others) will be part of that activity. But we will also make specific decisions about why and when we do those things, following two core principles: (1) We can’t do everything. The limiting factor is our engineering bandwidth measured in people and time. So we have to ensure our top priority is driving delivery of the #1 Enterprise Operating System, Solaris 11, to grow our systems business; and (2) We want the adoption of our technology and intellectual property to accelerate our overall goals, yet not permit competitors to derive business advantage (or FUD) from our innovations before we do.

This, really, isn't so bad. But again, no community, just end-users. A return to focus isn't a bad thing.

We will continue to use the CDDL license statement in nearly all Solaris source code files. We will not remove the CDDL from any files in Solaris to which it already applies, and new source code files that are created will follow the current policy regarding applying the CDDL (simply, that usr/src files will have the CDDL, and the very small minority of files in usr/closed might not have it).

Ok, so existing code will not be closed. So, no drastic change.

We will distribute updates to approved CDDL or other open source- licensed code following full releases of our enterprise Solaris operating system. In this manner, new technology innovations will show up in our releases before anywhere else. We will no longer distribute source code for the entirety of the Solaris operating system in real-time while it is developed, on a nightly basis.

So here is the killer... what I've been afraid of. No more nightly code. The upshot is that the code will still be available following releases to assist with DTracing, debugging, etc, but you won't get real-time updates. The biggest downside is that you can't see bug-fixes as they are put-back, and obviously anyone developing on Solaris is always playing catch up. It says "full release", so I can't expect that code will ship with each Express release. Maybe it will, I hope so.

It goes on to say that "technology partners" (such as Intel) will have full source access via OTN.

We will encourage and listen to any and all license requests for Solaris technology, either in part or in whole. All such requests will be evaluated on a case-by-case basis, but we believe there are many complementary areas where new partnership opportunities exist to expand use of our IP.

This is a sticky place. Code is shipped CDDL post-release, however they want to establish partnership opportunities. Clearly they are trying to ensure any businesses which rely upon Nevada will not escape from the partner programs and thus revenue opportunities for Oracle.

We will deliver technical design information, in the form of documentation, design documents, and source code descriptions, through our OTN presence for Solaris. We will no longer post advance technical descriptions of every single ARC case by default, indicating what technical innovations might be present in future Solaris releases. We can at any time make a specific decision to post advance technical information for any project, when it serves a particular useful need to do so.

Flush... there goes ARC. So the external view into Solaris development is now closing. We now only see what they wish us to see.

We will have a Solaris 11 binary distribution, called Solaris 11 Express, that will have a free developer RTU license, and an optional support plan. Solaris 11 Express will debut by the end of this calendar year, and we will issue updates to it, leading to the full release of Solaris 11 in 2011.

So, back to the old days.

All of Oracle’s efforts on binary distributions of Solaris technology will be focused on Solaris 11. We will not release any other binary distributions, such as nightly or bi-weekly builds of Solaris binaries, or an OpenSolaris 2010.05 or later distribution. We will determine a simple, cost-effective means of getting enterprise users of prior OpenSolaris binary releases to migrate to S11 Express.

There is the axe on OpenSolaris, present and future. The distro isn't coming. No nightly. No BFU's.

We will have a Solaris 11 Platinum Customer Program, including direct engineering involvement and feedback, for customers using our Solaris 11 technology. We will be asking all of you to participate in this endeavor, bringing with us the benefit of previous Sun Platinum programs, while utilizing the much larger megaphone that is available to us now as a combined company.

And here we see again, its "back to the future" . Pay to play.

The Verdict

Frankly, I'm not surprised by any of this. Saddened, certainly, but not shocked. The sleigh ride is officially over.

As far as the community and governance is concerned, the OGB played right into Oracle hand. It might as well have been engineered this way. On Monday, the 16th, the OGB will disband and default on the charter. Great work guys! Thanks for truly representing the needs and desires of Ora...I mean, the community.

As a governance, OpenSolaris has been a non-stop, end to end failure. Hands down. At every turn, it failed.

As an open source project, it was luke warm at best.

What I will miss is having full access to Solaris Engineering. What's happening, where we're going. That was amazing. An all access pass. I will truly miss that.

The plus side is, that for all the ups-and-downs, the code is out there. They can't take that back. And we have reasonable assurances that it will stay out there following "full releases". That's not ideal, but its something. Something very valuable.

As for me... Illumos will now carry the torch, and I'll participate in that with all the more gusto. This blog existed prior to OpenSolaris and it will continue to be a Solaris blog after. Solaris is the best platform on earth, it continues to be, in any given form.

There weren't any surprises. The key take-aways I think are:

• Roadmap for SPARC and Solaris out to 2015.
• SPARC will deliver "2x plus performance improvement every 2 years"
• Ultimate devotion to SPARC platform.
• 2 SPARC server lines: T-Series for lots of threads, M-Series for lots of sockets.
• "Niagara"/"UltraSPARC" branding isn't present at all... its all just "SPARC".
• Solaris 11 is coming in last 2011 with a beta/preview coming to "enterprise customers" soon

The presentation really boiled down to "technology will move fast in the next 5 years, Solaris and SPARC rule." Clearly Oracle has a plan and will execute strongly.

Maybe I have Sun-Purple colored glasses on, but it really felt like this lacked the kind of technical grit we were used to. There is no new exciting technology being introduced, no great innovation to look forward to, just steady incremental improvements in the technology. Feels a bit like HP really.

Solaris 11 was inevitable. You can't introduce IPS to Solaris 10, it breaks too much, so Solaris 11 has to happen, and will bring with it all the Nevada goodness. It looks like following its release we'll be seeing annual updates that will focus primarily on scalability (to optimize for expanding hardware capabilities) through 2015.

So, the good news is that finally have a roadmap and we know Solaris 11 is coming.

The bad news is that OpenSolaris wasn't mentioned at all. That was expected though. As soon as Oracle took over in January the word was quickly spread that "OpenSolaris" is a four-letter word.

So, anti-climatic, but glad we finally got a glimpse into the future. All eyes now turn to that first Solaris 11 preview to come "soon".

What is Illumos? A change to put "OpenSolaris" back on track. When this slay ride started, "OpenSolaris" wasn't a distribution, it was a community. It was users and developers and sysadmins gathering around a great operating systems code, now free to learn from, contribute to, and to innovate on. But that's not how it really went down... is it?

Illumos isn't a fork. There is no such desire. We're simply moving the code out into the community, where it belongs, and leaving the corporate red tape behind. Garrett D'Amore, who has spearheaded this and will serve as our benevolent dictator for the time being, has already invited Oracle to participate. I really hope that they do. We have here now a way for the community to contribute better than ever before, and a way to cross-pollinate with the Oracle gate in an orderly way. By keeping them in sync we can share between the two as we wish.

Whats best of all is that while Garrett is a Nexenta employee, this is not a Nexenta owned project. Nexenta will use it, as will Joyent, as will Belenix, as will anyone else who desires.

While I wish we didn't need to setup an external community repository, all other alternatives have been exhausted.

This isn't really even the first time this has happened. At Genunix there was for some time SVN Repostitories maintained... they simply didn't get much love. Whats different this time is that there are an increasing number of developers that depend on this codebase which can not be at the continous mercy of Oracle. We can find security in having our own community gate.

I personally applaud Garrett for his decisive leadership and Nexenta for allowing him to pursue this. The future is looking a lot more bright and I really hope that Oracle will join in and we can all work hard to innovate on this amazing platform, together.

If today is dragging, might want to refresh your memory of the great OddTodd... always a pick-me-up.

Teaching him has gotten me thinking back to my own youth. I had a box of Lego's but not a lot of sets. The one that I did get was in 1988, when my parents got me perhaps my favorite (but forgotten until recently) toy of youth: the Lego Technic 8865 "Test Car".

That set was amazing. I proudly displayed it on my shelf in my room, both because of my pride in building it as well as just how outright kool it is.

Since that time Technic has grown up as much as I have. Take a look at the Technic Lego 8421 Mobile Crane:

So tempted to buy that. I already have the Ferrari F1 set, which Tamarah bought for my birthday several years ago.

But most fun of all... this week Glenn is in a one-week Lego Pre-Engineering class. For 3 hours a day they geek out and build all manner of fun stuff.

One thing I'll throw out there for Dad's... Lego has an Education dept: Lego Education. Of particular interest to Tamarah and I, is that they have a complete Homeschool Curriculum and various kits, including robotics kits, for education. A really amazing resource for parents.

Whats interesting is that John & Damon really aware of an outcry from the community, that is: "How do all these devops shops do it!!" We want to emulate them, know what tools they have, how they use them, what works, what doesn't, etc. So to facilitate just that, they started a videocast sub-series called: Open Mic.

Open Mic 1: DevOps Metrics and Dashboards at Shopzilla from dev2ops.org on Vimeo.

In the first episode, they take us into Shopzilla, where Juan Paul Ramirez shows us their tools, metrics, and talks extensively about how they got to where they are. Excellent content!

If you haven't already seen, perhaps the most popular talk this year at Velocity, "A Day in the Life of Facebook", in which the Facebook Ops team introduces us to their tools and organization.

Whats really great here is that we're not share deeper information about how we're doing things, such that we can be a community of organizations. In the past, only a handful would really share and they were always far removed from useful pratice. I really hope this trend continues.

Big thanks to John and Damon for helping fuel that fire!

The OGB is keen to promote the uptake and open development of OpenSolaris and to work on behalf of the community with Oracle, as such the OGB needs Oracle to appoint a liaison by August 16, 2010, who has the the authority to talk about the future of OpenSolaris and its interaction with the OpenSolaris community otherwise the OGB will take action at the August 23 meeting to trigger the clause in the OGB charter that will return control of the community to Oracle.

That is to say, "start talking to us or we'll just shot ourselves in the head."

I made my opinion very clear via the IRC back-channel during the call. At least my call for a liaison was added into the resolution, but I am extremely opposed to this cowardly act.

What exactly do we have to gain or Oracle to loose? All Oracle does is runs out the clock, the entire OGB resigns, and then the one little bit of control the community has is gone. What motive, other than a benevolent act to garner press attention, does Oracle have to comply? We've just made their job easier.

I once advocated this kind of self-implosion tactic back in the Sun days. The reason was to re-organize the OpenSolaris leadership to be more engaged and industry focused. That was a good idea back in the days when I had faith that Sun would "do the right thing". However, those times have past. Oracle has made it clear that it either controls things or it doesn't... there is no give and take. I don't think we can demolish the structure and believe that Oracle will re-organize in such a way as to give the community more power. It was a long shot with Sun anyway.

Frankly, imho, this is just the OGB throwing its hands in the air. The body has been useless for a long time, but only because it has chosen to be. The majority of the OGB's life its wasted by trying to restrict its own authority by endlessly debating and re-writting the constitution. Its never lead anything, and it isn't now.

But the fact that its a wet rag doesn't mean we should simply throw in the towel. A weak seat of power is better than no seat at the table.

So where do we go from here? Who knows. At this point the die is cast and OGB is putting up their last stand. Maybe Oracle gets serious and does something, but I really doubt it. Not because they can't, but because its not in their best interest. Why kill something intent on killing itself.

My only concern as this point is to not loose regular code updates and access to the bug database. Yes, the existing code is "out there", but Oracle is still the biggest contributor, 99.999 to 1. Anyone can fork at any time right now, as is, so if your going to do that why would you risk cutting off the huge contributions continuously made by Oracle?

We're in no worse a position right now than we were during the Sun days. They didn't communicate, we had no visibility or impact on the OpenSolaris distribution, etc. Don't fall into the lie that things are now "worse" than they were... they aren't. Its status quo. The difference is that the OGB is no longer composed of Sun insiders who can get a sense of control from hallway conversations and are now as blind and weak as those of us in the community always have been.

The request for a liaison is a good one... I support it. But damnit, put the gun down. We don't need to act like irrational children having a tantrum. Ultimatums rarely workout the way you hope.

The bar is lower than the original resolution was, so we'll hope for the best and see.

UPDATE: OGB Member Peter Tribble has written a blog entry about this action, recommended reading. While I disagree with the action, Peter is a great guy whom I greatly respect.

I am partly responsible. Sorry to everyone that the blog has been so quiet lately. Given that state of Solaris right now, its unclear what is dead and what is alive. It feels futile to blog about features that may never really be viable. Couple that with OpenSolaris which still hasn't delivered and the fact that many of the features that need documenting are really pretty uninteresting to me (ie: IPS/AI).

The exodus still continues. Lots of engineers have left Sun and many more are considering leaving. I'm told by folks that its not a huge problem because while the big name guys are leaving, the real down in the trench do-ers are still there and working away. But it certainly is disheartening.

The most recent news out there was that Oracle yanked HP's OEM License, so if you run Solaris on HP Prolient servers, your hosed. See? Not a lot of positive stuff for me to blog about.

Personally, I've been more interested recently with the growing 'Devops' movement and IT standards. I've spent a lot of time in ITILv3, ISO 20K/27K, CobiT 4.1, COSO, NIST SP800-53, etc, etc, etc. A whole new and interesting world to me because I came to it instead of a company hoisting it on me against my will.

I have several articles to get out for SearchDataCenter which I'll plug here, and then will start rolling new content out here in a bit.

Simply it states the following:

On the "Solaris Near Term Roadmap", they state that Solaris 10 Update 9 will come some time in 2010 focusing on platform support and Oracle product integrations.

OpenSolaris is slated for an update in the "1st half CY2010". It will be based on snv_134 and be called OpenSolaris 2010.??.

No surprises here. But given the lack of information, no surprises isn't so bad.

This does cause me to think I might have been wrong in my belief that Solaris 11 would arrive this year. I still think it's not a bad assumption, but if it doesn't come I'll be really curious as to what the heck Solaris Engineering is so busy working on.