HN user

snw

337 karma
Posts37
Comments42
View on HN
wiedi.frubar.net 6y ago

Profiling Django with DTrace and CProfile

snw
20pts0
ptribble.blogspot.com 7y ago

Setting up an Etcd cluster on Tribblix

snw
1pts0
omniosce.org 7y ago

OmniOS Community Edition r151028 released

snw
2pts0
blog.netbsd.org 8y ago

=?iso-8859-8-i?Q? Handling Non-UTF-8 Hebrew Email

snw
1pts0
blog.koehntopp.info 9y ago

Getting out of the cloud…

snw
204pts93
kyleisom.net 9y ago

Unix processes in illumos

snw
3pts0
pythonsweetness.tumblr.com 9y ago

Deploying modern Python apps to ancient infrastructure with pkgsrc

snw
4pts0
alexeremin.blogspot.com 9y ago

Meet v9os, a minimalist Illumos-based SPARC distro

snw
2pts0
blog.netbsd.org 10y ago

Pkgsrc 50th release interviews: Jonathan Perkin

snw
2pts0
blog.netbsd.org 10y ago

Pkgsrc-2016Q1 – the 50th pkgsrc Release

snw
1pts0
robotpkg.openrobots.org 10y ago

Robotpkg – compilation framework and packaging system for robotics software

snw
3pts0
www.schmonz.com 10y ago

Cross-Platform Full-Stack Deployment

snw
2pts0
www.pkgsrc.org 10y ago

PkgsrcCon 2016 in Kraków

snw
1pts0
github.com 10y ago

DTrace for Windows

snw
4pts0
blog.netbsd.org 10y ago

First reproducible builds conference in Athens

snw
2pts0
masnun.com 10y ago

Python: Generators, Coroutines, Native Coroutines and Async/Await

snw
147pts30
www.geeklan.co.uk 10y ago

Adventures in Open Source Software: Dealing with Security

snw
1pts0
ptribble.blogspot.com 10y ago

On Keeping Your Stuff to Yourself

snw
12pts0
reverse.put.as 10y ago

Rootfool – dynamically disable and enable SIP in El Capitan

snw
1pts0
paperswelove.org 10y ago

Memory by the Slab: The Tale of Bonwick's Slab Allocator [video]

snw
24pts3
paperswelove.org 10y ago

Memory by the Slab: The Tale of Bonwick's Slab Allocator [video]

snw
1pts0
thshaw.blogspot.com 10y ago

Putting the Joy(ent) back into Docker

snw
2pts0
pkgsrc.org 11y ago

PkgsrcCon 2015 recordings are online

snw
1pts0
blog.netbsd.org 11y ago

NetBSD 7.0 RC1

snw
3pts0
blahg.josefsipek.net 11y ago

Tail Call Optimization

snw
2pts0
pkgsrc.org 11y ago

PkgsrcCon 2015 in Berlin

snw
2pts0
pkgsrc.joyent.com 11y ago

Pkgsrc – Portable Package Management

snw
2pts0
mail-index.netbsd.org 11y ago

The pkgsrc-2014Q3 Release

snw
1pts0
project-fifo.net 11y ago

Project FiFo – SmartOS Cloud Orchestration

snw
4pts0
queue.acm.org 12y ago

Bringing Arbitrary Compute to Authoritative Data

snw
2pts0

Probably someone from the unleashed project can give a better answer, but my understanding is mostly unhappiness about the illumos contribution process.

The illumos RTI (request to integrate) process is designed to ensure a certain quality of contributions. The downside of this is that it sometimes takes a long time to contribute a change.

For illumos there is also pretty high expectation of backwards compatibility. What unleashed now offers is a place to do more radical changes and quickly iterate on new ideas.

While the small illumos community is already pretty fragmented my personal hope is that in the future work done by both projects keeps getting merged from time to time. Maybe this also serves as a wakeup call to the illumos project to make some improvements to the contribution process itself.

Dtrace for Linux 8 years ago

The new OpenSolaris is called illumos.

And the CDDL is actually fine. Give it a try :)

Oh yes, the wikis definitly do need some love. Documentation is beeing worked on as far as I know.

A lot more of activity is going on in irc on freenode, so if you start playing with your lab server or are just interested in general you might want to drop by in #illumos or #smartos.

In my case illumos provided two things:

- zones allowed for a much higher deployment density and better utilisation of our hardware than other virtualization technology would have.

- zfs snapshots. We've integrated those into our product and when a customer messes up they now have button to instantly restore to a known good state.

Doing both of these things would have been a lot harder on another os.

There seems to be a lot of odd nostalgia for Solaris in the comments here and on twitter. I think that's missing the point of the article. Yes, Oracle Solaris is dead. But illumos is better, open source, alive and here to stay.

You can use illumos today, right now, and have your ZFS, mdb, DTrace and zones. It really is open source and we're a community using and improving it. For 7 years now already.

As illumos is only the basic building block of the operating system (but unlike linux includes kernel + basic userland) one usually runs one of the distributions:

- SmartOS, developed by Joyent as a cloud hypervisor. Supports zones, KVM and lx-branded linux containers. [1]

- OmniOS CE, a minimal distribution targeted for bare metal server installations [2]

- OpenIndiana, similar to the traditional opensolaris. If you care about GUI this is probably the one. [3]

- Tribblix, modern components with retro style [4]

Sure, the user base is smaller than Linux. But that is also true for FreeBSD which is used by Netflix and Whatsapp. Running a different OS than most other people can give your company an advantage and I know that ZFS and zones have done that for mine.

[1] https://wiki.smartos.org/display/DOC/Download+SmartOS

[2] http://www.omniosce.org

[3] https://www.openindiana.org

[4] http://www.tribblix.org

Linux distributions are very similar to each other. Having package management as the main thing that sets them apart.

In illumos land these different distributions exist because they have very different design goals and visions.

But I agree that the illumos community is also a lot smaller and maybe (sadly) too small for each distribution to be commercially successfull. I'm extremly sad about this announcement as OmniOS is a great operating system and the team behind it did a fantastic job. As a user I like the minimal setup and clear stable releaes.

From what I've read the community is now thinking of possibly consolidating with OpenIndiana for that usecase. So while having less commercial supporters is a pity the community is determined to keep pushing forward.

The Oracle docs are not really the reference documentation for the open-source stuff, since illumos and Oracle Solaris have diverged quite a bit by now. Some things are implemented in different ways. OpenZFS in illumos has many features not in the closed oracle zfs.

The real reference docs are the man pages [1]. Depending on the illumos distribution there are more task-oriented guides for OmniOS [2], OpenIndiana [3] or the SmartOS Wiki [4]. In-depth information (driver development, MDB, DTrace) is written down in the "illumos books" [5]. These are not in danger from oracle.

Sadly a lot of good historical documentation is already gone since oracle broke all the sun.com links and not even archive.org has those. :(

[1] https://illumos.org/man/

[2] https://omnios.omniti.com/wiki.php/GeneralAdministration

[3] http://docs.openindiana.org/handbook/getting-started/

[4] https://wiki.smartos.org/display/DOC/SmartOS+Users+Guide

[5] http://illumos.org/books/

Oracle Solaris might be dying, and Linux sure has a large market share, but illumos as the open source continuation of OpenSolaris is doing very well.

If you enjoyed ZFS, Zones, DTrace and so on in the past there is a good chance that you'd like OmniOS, one of the illumos distributions for classic server environments.

There are more distributions like SmartOS that tkae a more innovative approach as cloud-hypervisor that is just a slim live system.

Most of the original ZFS Developers are now working on OpenZFS in illumos. Beeing open source also means collaborations with other OS projects like FreeBSD (bootloader and more), NetBSD (pkgsrc) is happening.

This is all independent of Oracle.

As an biased illumos user, I believe that: yes, you might be missing out. ;-)

To give a quick overview on the ecosystem: everything is based around illumos as the upstream repository. There are different distributions similar what you have with linux on kernel.org and distros like ubuntu, suse, rhel, slackware. Instead of just the kernel the illumos repository also includes some libs and core system tools for userspace. The illumos distributions differentiate a bit more on use case than the linux ones.

- SmartOS is designed as a cloud hypervisor. It is probably the most radical distribution in that it is a complete live system that boots from usb/network and runs in ram. With traditional zones, KVM and lx-branded zones it's a great system for virtualization.

- OmniOS is a minimalistic server distribution. It best fits for bare metal installations.

- NexentaStor is a storage appliance built on ZFS delivering unified file (NFS and SMB) and block (FC and iSCSI) storage

- OpenIndiana continuation in the spirit of the original OpenSolaris, including a full GNOME desktop environment

- tribblix gives you "retro style and modern components"

There are a few more but these should give you a good intro.

Besides a variety of community contributors there are some bigger companies involved. Joyent, a cloud provider, is doing most work on SmartOS. Nexenta has NexentaStor, OmniOS is build by OmniTI which does consulting. Delphix is a database company that mostly contributes to ZFS parts. Pluribus has a SDN product based on illumos. Lucera, financial service provider also runs on illumos and contributes.

So even without oracle there is a very healthy mix of different commercial and community contributors.

Features like advanced filesystem support (ZFS), systems tracing (dtrace), fully fledged containers (Zones), and software defined networking (Crossbow) make it a very interesting system.

New drivers are developed and many features evolve in illumos. The focus is mostly on x86 server hardware but I know folks also using openindiana on laptops.

In many companies the IPv6 migration has already happened. For those that have not started yet it will be more expensive if they wait even longer.

The hardest part seems to be training people. IPv6 is different - it is more than just "longer addresses". It is a newer protocol that fixes many more problems with IPv4 than just address exhaustion. So this "ipv6 migration" is actually an opportunity to leverage those new features.

Designing IT infrastructure IPv6 first and IPv4 second allows for so much simpler designs. You can have your complete network IPv6 only and do IPv4 on the edge for legacy clients. (Maybe doing outgoing NAT for v4 where required) The results are a much cleaner layout (because of the larger address space), simpler firewall rules, and so on.

It is not complicated or hard to do (in contrary I think that e.g. just setting up SLAAC is much simpler than managing DHCP) but the engineers need to know how it is different. They need training for that. People are often used to the old ways, once they have seen and worked with IPv6 it is no problem.

I've helped larger and smaller companies since ~2004 with those migrations. One observation I've made is that here in europe IPv6 is a basic fact of networking where as in the US it appears as if many companies are in denial. That cloud providers like AWS don't do native v6 is absolutely ridiculous.

When you write code or security rules today that is not designed with IPv6 in mind they are outdated today. Don't do it ;-)

it's a nice linux distribution. The packages are usually very stable and well tested. It does the job on the desktop and on the server.

In that sense it is practical, not sure if "notable" as there are many other more popular distributions these days.

pkgsrc is brilliant for containers!

Not using docker but zones as a container solution here, but what we do is bake images containing: pkgsrc + static config files + small scripts.

To provision we take the image + metadata containing dynamic configuration values (network details, keys & certs, etc.) and execute that.

This allows us to make very stable releases containig all our software. Pkgsrc is the most important part of this. It already contains very recent versions of packages as it is released quarterly. But sometimes we need to run a very specific version in production, or maybe add a patch to fix some bugs. This is super easy with pkgsrc.

I've given a talk last year about some parts of this at a local meetup: http://up.frubar.net/3165/deploy-zone.pdf

The solaris forks are definitly not dead. What became of opensolaris is now known as illumos and there are quite a few specialized illumos distributions around like SmartOS, OmniOS, OpenIndiana, Nexenta Stor and a few more.

I agree that you need a community of users and developers for a successful open-source project. Luckily in addition to the companies like Joyent, OmniTI, Nexenta, Lucera, Delphix (who all actually do a lot of drivers development) there is a friendly and growing community of volunteers that contribute.

What is sadly sometimes lacking a bit is marketing. After oracle went closed again many assumed opensolaris died, but in fact a lot of interesting systems development is happening in illumos land. Of course all open source. I wish a few more people would recognize what a great system and community SmartOS and OmniOS have.

For those who don't know pkgsrc yet: It is a portable framework for building over 14,000 open source software packages. Besides NetBSD pkgsrc is the native package manager on SmartOS and Minix. It is portable across 22 different operating systems including Linux and Mac OS X.

This event will be a weekend of fun around making open-source software work across platforms. I look forward to meeting other pkgsrc enthusiasts there!

as mentioned elsewhere in the discussion most open source folk that have not moved to linux seem to put their energy into illumos now.

At least for illumos (SmartOS and OmniOS, ...) there is a lot of work happening for web services.

SmartOS offers two ways to host VMs: Zones & KVM. Zones is os-virtualization, so you run SmartOS zones on SmartOS but it uses the same kernel. KVM is hardware virtualization and allows you to run other operating systems on top. So you can have Linux, FreeBSD, Windows or even nested SmartOS with a different kernel running inside.

So zones make running nested SmartOS with KVM a bit uncommen. While possible there are not that many use cases besides development on the system itself.

I've come to the illumos ecosystem about three years ago. First for SmartOS and ZFS. Now i know more about the great tech if offers like zones, dtrace and so on and use it nearly on all our servers.

I know others are joining the community as well as hanging around on irc shows. It definitly is a smaller community than linux or the BSDs but it is growing.

Also a lot of interesting systems development is happening (lx-branded zones, overlay networking, ...) in illumos and it is the upstream of openzfs.

Besides SmartOS a more classical server distribution to consider would be OmniOS [1]. For a storage appliance one might want nexentastor.

Distributions of illumos are more purpose-built than linux distributions. They differentiate more by use-case than by package management. Yet they all consume and contribute to illumos and what might look fragemented is not much of an issue for the community itself.

[1] http://omnios.omniti.com