OpenSolaris Governing Board Dissolves Itself
mysidia writes "Last month, it was mentioned that the OpenSolaris governing board issued an ultimatum to Oracle. It turns out that Oracle continued to ignore requests to appoint a liaison after the governing board's demands. This morning, the board unanimously passed a resolution to dissolve itself. Source code changes are no longer available, and it would appear that OpenSolaris and community involvement in the development of Solaris have been killed as rumored. We recently discussed a 'Spork' of OpenSolaris called Illumos. Perhaps now, this will have a chance at becoming a true fork."
With so much core OS work going to Linux and most of the remainder going to *BSD, which also has already ZFS well underway... What do theyhave to attract devs?
Has Netcraft confirmed it?
I have to use opensolaris on my intel boxes because I have to use gcc-2.95.3 to compile some ancient software I use for research, and not because of some fancy file system or dtrace. I can't help but wonder if other people are in the same boat. Anybody?
If you give a liberal an enema, he'll turn transparent.
Does this mean you won't spork me tonight?
The Open Solaris council will no longer be of any concern to us! I've just received word that Emperor Ellison has dissolved the council permanently. The last remnants of Sun have been swept away.
From now on, fear will keep potentially traitorous Solaris users in line. Fear of our software patents - and our new super death-ray powered ELAs!
When will we get an Ellison/Borg icon for /. ?
I think Oracle are jolly rotten. I wish the very best to the Illumos team the very best of luck, and the continuation of development.
This is pivotal, as ZFS is just spiffing although its license is less than optimal.
I'd join in if I could program in C.
Good day!
This move by Oracle reminds me yahoo in the .com era. Open Solaris was not a revenue source but it was important as the means to get developers interested in Solaris. I don't think there will be much development or support for solaris from the open source community from now on.
Wicked Witch was not available for comment.
I think this is a good thing for everyone. Hear me out, I'm not an idiot, or at least I'm trying not to be!
Solaris, unlike the other big two open source operating systems - Linux & BSD - has always had the problem of the double edged sword because it always had to serve Sun, which in turn supported it. Now with Oracle punting Solaris to the curb, the community can really see what it's made of. Whether Solaris is an also-ran or if the community can really go full tilt and go in directions that it couldn't because of it's omnipresent master is entirely up to the people who support it. The future is bright for smaller form factors, as well as servers (again) so now it's time to see if they are big time players or another name to the pile of failed OSes.
I wish them well.
I call it 'The Aristocrats'
So what? OpenSolaris was a bad joke anyway.
In the true spirit of OSS, they packed up their bags, stuck out their tongues and said 'fuck it, we're done dealing with you guys, we're going home' ... and thats perfectly within their rights.
It should be noted however, since they were about the only ones using OpenSolaris, no one is really going to notice they are gone.
Using OpenSolaris is roughly the same as running Darwin instead of OS X. Roughly, not really the same, but both are pretty much pathetic bases of the what the person actually WANTS to run, which is the full version. Anyone who would consider running OpenSolaris will just pay the tiny little fee and run the real deal which has slightly (not much mind you) more spit and polish on it.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
I know that a portion of the Open Solaris code is closed source. Will this hamper any effort to actually fork it? I'm asking from a place of ignorance, as I just know that "some code" is closed, but I'm not sure if it's the code that would be essential to actually forking the project.
Oracle didn't care, because Oracle has said that they are no longer interested in having an open development model for Solaris. In fact, the fact that Oracle doesn't care is why they're dissolving in the first place. Solaris users don't care because, let's face it... does anybody actually use OpenSolaris? I work for a huge Solaris shop, and we use stock, Sun-supported Solaris. If we wanted an Open Source operating system, we'd use Linux. We use Solaris for huge database servers that are too big to run Linux (mostly Oracle DB.)
So, that leaves OpenSolaris developers. Look, this is the risk you take when you work on a project dominated by one company, especially when you have a license like the CDDL. I feel bad that you're in this position, but it was kind of predictable, and I really think you're missing the boat with Illumos. You're unlikely to get enough interest to ever make a go of it with Oracle being disinterested. Go work on making Linux better instead!
"He who would learn astronomy, and other recondite arts, let him go elsewhere. " -- John Calvin, commenting on Genesis 1
Buy your competition and then kill their products. This seems familiar. Where have I heard this one before....
...and why the GPL is superior. With the GPL, it is prohibited to take work private that has been built by the community. The BSD license /* encourages */ it. I see on the website of an deeply involved OpenSolaris developer where he is complaining about Oracle not adhering to the spirit of the open source license. I suggest that there is only the /* letter */ of an agreement whenever "push comes to shove." Spirit goes out the window.
http://xkcd.com/419/
If anyone asks for me, i am in my room with some candles, a Larry Ellison doll and tons of needles.....
The CDDL killed it as much as anything else. That license sucked. If Ellison really wanted to make some blood vessels burst in Redmond, he'd put all CDDL material out as GPLv3.
I'm retired now, but at my last job we had 20,000+ UNIX servers. My projects - I was a technical architect - had about 300 of those servers. Trying to compare the throughput for most x86 servers to a P590 or HP Superdome or Sun E25K just shows your ignorance of the larger UNIX system capabilities. From a compute standpoint, Intel CPUs are hard to beat, but when you need 10 fibre connections to storage and 20 10GigE connections and have 10,000 concurrent DB users, RH stuff ain't gonna cut it. Sorry, but those are the facts. These servers aren't for a website.
Then you have the issue of getting a vendor that only certifies their program on HP systems to bother with RedHat. The $3M that the DB server HW costs is nothing compared to the software costs for another platform to be supported by some vendors. The software ran on HP-UX - that's all. The software cost $25M for 2 prod instances and 5 non-prod instances (DR, Test1, Test2, pre-prod ... ) This is software you run your business on AND not very well designed. Bigger hardware is always the answer over system design changes. It is cheaper. Our prod DB servers were 64-way with 108GB of RAM. We had 4 of them - 2 production locations with 2 DB srvs each. An active/failover cluster model. We had 4 DR servers that were almost as large located in another data center that got data updates nightly. There were about 20 app servers inside data centers, about 40 app/GIS servers located in the same building as the users who were spread all over the USA for this project. Another 20 servers were used for the dev, test, pre-prod, test2, test3 environments. It was not possible to run all the software on the say system, at least 3 systems were required for each environment. Crap, I know. Back when I worked on it, VPARS were specifically not supported by the vendor, so we didn't use them - anywhere.
Just because RH claims to run on 20+ way systems, doesn't mean any of the software will. BTW, Oracle RAC was not supported by the sw vendor, so lots of small Oracle Nodes wasn't gonna work.
Anyway, you wanted some background on why anyone uses non-RH machines. Oh - we were seeing about 4k TPS on each production system during business hours. Transactions came from client tools, app servers, reporting tools, and ad hoc queries from blackberries and other portable devices.
We had an outage 1 day for about 6 hours around 2004 due to DB corruption - over 10,000 people couldn't do their jobs (half the users). It wasn't good. I'm glad only 1 production site was impacted.
THe first time that SUN went OSS, I fully supported them. When they burned everybody, I KNEW that it was easy for Sun or any buyers to screw over OSS world. And I have spoken out against Sun's opening of the code, even though LOADS of Sun fanbois were pushing them. And in this case, Sun did not disappoint.
I prefer the "u" in honour as it seems to be missing these days.
when you're down to your last piece of tableware, you just have to make do with what's left, unless it's a butter knife and the meal is soup...
(if it was a real knife, you could at least carve a spoon out of something)
The CDDL is not a BSD license. It's more like an MPL or NPL style license, in that it privileges a particular company (in this case, Sun) to a special status with regard to derivative works.
"He who would learn astronomy, and other recondite arts, let him go elsewhere. " -- John Calvin, commenting on Genesis 1
Thanks, i needed a good laugh after a day like today.
---- Booth was a patriot ----
iBCS was not maintained because there was no real need for it anymore. 15 years ago, you often needed to run stuff that just would not exist on Linux, and today that's just not going to happen, except for very specific, very propietary stuff. And if you want propietary stuff, you will most likely pay for it. And the OS it runs on, becomes basically an afterthought.
It takes aeons to build up a reputation, but it takes a few days to totally destroy it. oracle should watch its standing with open source community.
Read radical news here
i posted in this thread. cant use points.
Read radical news here
this was kind of scary; and I think it was *my* last nail in the coffin for zfs. for me, that is (ymmv).
I had a freebsd 8.0 system up for quite a long time (over 100 days). I often keep the /usr/src area current via cvsup but had no reason to reboot until the system hung under heavy load. when it rebooted, I found I was 'half 8.1' and half 8.0, still. this threw zfs out of sync and the pool would not be mounted! what a scare, let me tell you (I had all my valuable stuff on that 6TB pool).
had to reboot to kernel.old, do a zfs scrub (took overnight), then rebuild World, reboot to have World be seen, then rebuild kernel to 8.1. then reboot again. finally zfs and the kernel saw eye to eye and my 6TB pool was mountable again.
I know that 'better sysadmin' might have avoided this, but I don't think I've ever had anything on linux be this way. I've used reiser, jfs, xfs - all the fs's. don't think I've ever had to do things this drastic just to mount my 'raid' set like this. it was scary.
now, given the fact that opensolaris was the nearest upstream to freebsd for zfs and that opensolaris pretty much is no more, I have very little actual confidence in zfs and support, going forward. its scary enough with all the new concepts, as it is; but I need to feel good about it; now and years from now. this version incompatibility worries me! its fine to have new features be ignored if you run older systems but this 'we wont mount you AT ALL' stuff is just for the birds! why on earth would a fs be designed like that? its not real-world and I'm not sure I like this idea, to be honest.
I did think about going with pure opensolaris instead of freebsd8.* but I'm just not sure that there's a good compelling reason to stay with bsd anymore and zfs seems like a non-starter for me, given my experience with it.
(plus, on the same exact hardware, linux md-raid and freebsd zfs compared, linux keeps up (no pauses) and is overall faster on nfs and samba than bsd/zfs is. and zfs really 'wants' at least 4gb to run. that's asking too much, too, I think).
--
"It is now safe to switch off your computer."
As someone who has tested out ZFS on both BSD and Solaris, and is familiar with the subject, I can tell you quite plainly: The Solaris implementation is good and generally, the BSD / FreeBSD implementation sucks, is buggy, missing features (or key features are buggy).
The OpenSolaris implementation is mature, well maintained, performs well, and is up to date. The FreeBSD implementation is immature, lags way behind OSol development, and seems to be unstable.
If you want a mission critical system running ZFS, FreeBSD is not an option, period.
ZFS is Stable on Solaris, and to a great extent on OpenSolaris and NexentaCore. There may be some gotchas, in OSol, particularly if you use new advanced features such as dedup.
There may also be some performance gotchas with certain hardware in all implementations (e.g. 32-bit proc, less than 2GB of RAM), and if you use gzip compression.
Just because work has been done to port the filesystem to BSD, does not mean it has the same stability or performance characteristics. It might have similar ones in the future, right now it does not. I would call it "Alpha" quality, even if it is in stable versions of BSD, at this point.
Why do you think Oracle bought Sun in the first place? It was for their presence in the "enterprise server market." Yes, some people are using Oracle RAC and the like, but there are still plenty of applications for that 64-way box running Oracle.
"He who would learn astronomy, and other recondite arts, let him go elsewhere. " -- John Calvin, commenting on Genesis 1
.. I have very little actual confidence in zfs and support ..
ZFS as it is today, even without any further feature additions, is miles ahead of any other FOSS filesystem in features and stability. As far as support goes, there is enough community and kernel expertize outside Oracle to atleast maintain the code (my employer Nexenta has made code contributions back into ZFS : the in-kernel iscsi code). So there is no reason for the doom and gloom.. that's the beauty of FOSS, you cant take back what you've provided.
~Anil
http://dilemma.gulecha.org - My philospohical short film.
OpenSolaris is dying!
(plus, on the same exact hardware, linux md-raid and freebsd zfs compared, linux keeps up (no pauses) and is overall faster on nfs and samba than bsd/zfs is. and zfs really 'wants' at least 4gb to run. that's asking too much, too, I think).
That's because linux mdraid doesn't provide you anything like checksumming amongst whatever other features you might be using.
So yeah, I'm sure ext3 and fat32 are plenty fast compared to ZFS, but if you're running ZFS, fast wasn't the point, was it?
(I'm using ZFS on 2GB of ram over gigE (EON Solaris NAS distro), works fine for me)
ZFS is used in production on FreeBSD by some people and I generally like the ZFS features, but I don't view ZFS as really production ready on any OS.
This is because ZFS on any OS does sometimes lose all access to the zpool (i.e. you lose the entire set of RAID volumes and filesystems on them, all at once) due to ZFS bugs, and there is no fsck. I can't think of another filesystem where you can (a) lose all access to your files and (b) there is no fsck. Same goes for RAID - even if you use RAID-1 with ZFS you can still lose your entire zpool due to a ZFS bug.
Given that the "no data loss by design" (can't find the reference for this, perhaps Sun/Oracle has stopped saying this) hasn't really worked out for ZFS on Solaris or FreeBSD, there is still a need to have a complete backup of any ZFS zpool (as with any other RAID / filesystem). The checksumming, COW, snapshots, and self-healing data (for RAID) are very nice, but losing your whole pool due to a ZFS bug means it isn't really a high availability solution. On the plus side, it does make it very easy to snapshot in order to take a backup, and makes incremental backups easy with zfs send.
Here are a few samples of complete zpool loss:
http://opensolaris.org/jive/thread.jspa?threadID=132089&tstart=120
http://superuser.com/posts/130822/revisions - FreeBSD
http://www.mail-archive.com/zfs-discuss@opensolaris.org/msg39578.html
My point is not that ZFS is a bad idea, but it really needs an fsck (see http://www.osnews.com/story/22423/Should_ZFS_Have_a_fsck_Tool_ ) and anyone using ZFS must have full backups onto another server of the whole zpool, perhaps into a non-ZFS filesystem to avoid software bugs that hit both the main and backup zpool. The need for backups isn't unique to ZFS but I haven't seen other filesystems/RAID implementations promising "no data loss by design"
http://breden.org.uk/2009/05/01/home-fileserver-a-year-in-zfs/ has some good info on using ZFS for a home NAS, with a separate backup server also using ZFS.
btrfs isn't mature yet, but its designer has said he will always make fsck a priority over new features: http://lkml.indiana.edu/hypermail/linux/kernel/0706.2/1284.html
My entire enterprise is now moving away from Oracle products.