Colin Charles Agenda

I paid great attention to Ian Murdock’s talk at LugRadio Live USA 2008, as he’s an important person at Sun in terms of the open source community, and I’m community facing as well. It was also the first time I got to meet Ian (after his talk), and we hit off a conversation really quickly. I look forward to working alongside Ian more… Now to the talk notes.

A Bit About Ian
- Linux user, developer, and advocate since 1993
- Founder of Debian, co-founder of Progeny
- Joined Sun in March 2007, Chief OS strategist (launched Project Indiana), and now since February 2008 is VP Developer and Community Marketing

What’s a Linux guy doing at Sun?
- When people say they want Linux… they don’t actually mean that they want Linux. You don’t only want the kernel, but you want the userspace as well. You really want a distribution, not Linux itself. Ian is more of an open source guy. So create a business model behind OpenSolaris?
- Solaris ships all userland utilities you’d expect from Linux. GNU Utilities vs. UNIX Utilities. Where the real differentiation is, is Linux Kernel vs. Solaris Kernel.
- Its the kernel where you drive change for the OS. Look at ZFS, Dtrace, containers, etc.
- Linux has multiple configurable platforms with expanding ecosystems. OpenSolaris, is an integrated operating system, with binary compatibility.
- Where Sun wants to go with OpenSolaris? Have binary compatibility in the core platform, and have the expanding ecosystem in it.
- Project Indiana has Solaris innovation with the “distribution” model of the Linux world, i.e. have package repositories. Also, to close the “familiarity gap” so that there is a GNU userland, a package management system, etc. And of course, focus on the unique Solaris capabilities - upgrade rollback via ZFS snapshots, AMP stack with integrated DTrace probes (MySQL in OpenSolaris Developer Preview 2 already has this capability), binary compatibility, etc.
- Remember, people deploy what’s accessible to them. This is a whole new deployment model. This is how Linux got into the Enterprise. This is the reasoning behind OpenSolaris… Solaris itself is great in the Enterprise, but lacks a user community. Follow the Linux (and largely, Microsoft) model…
- One Solaris Platform, two delivery mechanisms - Solaris: enterprise class, support, long release cycle (3-5 years); OpenSolaris: latest Solaris innovations, short release cycle (6 months), much easier to use, network economy, support from Sun also
- Adoption-Led Market is what its at now. Users become customers. Give users something of value. That’s the basic business model at Sun, around open source.
- Volume drives value! New consumers/communities on the network will drive infrastructure demand. Reach the developer community through massive volume, get it in use as many places as possible, then sell software/storage/servers/services/etc.
- Just spent $1 billion on MySQL. Databases are often deployed on other middleware, say identity management. Sun sells identity management software.
- Developer platforms of choice are moving up the stack. Traditional Sun platforms are increasingly invisible infrastructure. New platforms remove barriers to entry and hide complexity so developers can focus on getting to market quickly.
- Remember, no one “owns” the web. The Web 2.0 world is like open source in the 90s.
- Hot new platforms are silos - you write your application to Google APIs or Amazon APIs and there’s only one place to deploy it. Sun is a leader in open standards for 25 years, how do you take this leadership into the new platform world? One needs the ability to deploy on a number of different platforms, and take your application from one to another. Sun strategy?
- Where do down the stack technologies, like operating systems, fit? Do they still matter? Yes.
- Solaris 10 is free today (you just have to register to get it)

On the packaging system
- OpenSolaris package system is new. Needed to build own for a few reasons, despite studying apt/yum/conary.
1) platform is very different from Linux; use ZFS and you get rollback, and this is Solaris specific
2) zones/containers, single shared kernel, multiple application environments, which is intelligent for resource sharing, and the package system is fundamentally aware of zones
3) an opportunity to innovate; Sun’s all about innovation. Package managers haven’t changed much in over 10 years (apt, yum)
4) the notion of customisation, i.e. have a version control like facility for patches, etc. so that changes can be reconciled when you rebase with upstream, is something the new package management system can use. This is kind of like Conary?
5) All customers tend to customise, even (especially) in Enterprises. IPS helps them (refer to 4)

Questions & Answers
- OpenSolaris and Solaris, how is it in sync? Codebase is in sync, generally. Solaris 10 is one codebase, and there’s a development version (i.e. the next release). There is a Solaris “train” and an OpenSolaris train now. How will these two trains come together? Solaris Next based on OpenSolaris? OpenSolaris with Enterprise support? Questions that are being asked now, and there’s no real decision yet. Wait till 2-3 OpenSolaris releases first, before finding out more.
- What is Sun doing to make OpenSolaris work better in a virtualized environment? I.e. working better in Xen, QEMU, VMWare, etc. Linux naturally has better device support than OpenSolaris, so virtualization is very important. Mentions the innoTek purchase, so that VirtualBox could be used for bundle delivery.
- Is Linux and OpenSolaris in par, security wise? Solaris has a slight edge at this point… They’re fairly comparable, but there’s more maturity in the Solaris product.
- OpenSolaris on PowerPC - unknown status, there’s been some work at Sun Labs to port it to PPC, you can boot it and do some basic things, but unsure if its ready for users or not.

Technorati Tags: lugradio, lugradio live usa, ian murdock, sun, opensolaris, linux, distributions, IPS, packaging system

No, its not alphabet soup. Just some notes from the session at the Sun Tech Days. I’ve not looked at DTrace much (my only look into instrumentation, has been from SystemTap, which doesn’t deal with applications), but plan on doing so soon… I’ve managed to get OpenSolaris Developer Preview 2 installed in VirtualBox, so it can only start being more fun from here…

Want to learn more about DTrace and MySQL? Then come to the MySQL Conference & Expo 2008, in Santa Clara, California, because on Thursday, Ben Rockwood, from Joyent, will be presenting a session on DTrace and MySQL (read the abstract, its good). The talk covers the fact that you can get useful information currently, even without the embedded probes in current versions of MySQL. For more DTrace and MySQL tips, don’t hesitate to read Joyeur, Joyent’s weblog.

DtTace, Web 2.0, Java, AJAX, PHP and the rest (notes from the talk)
by Peter Karlsson, Solaris Technology Evangelist

DTrace now has providers for a large number of languages: JavaScript, Java, PHP, Python, Ruby. Perl is on the way.

MySQL 6.0 will have DTrace support; PostgreSQL already has this in Solaris currently. If building from source, there’s a flag that needs to be enabled. A lot of work was done thanks to a community member.

You need a Solaris kernel. Ported to OS X and FreeBSD. Supports “dynamic instrumentation”. D is the dynamic language, used to script instrumentation

Very common request? Find how much time is spent in a given function. The thread local variable (self->variable = expression;) - nowadays, you can be running two threads coming down in the same function call. DTrace - so this is great for multi-threaded debugging.

PHP doesn’t have DTrace integrated, so, get the Coolstack PHP.

DTrace probes have been added to Mozilla to help debug JavaScript applications. This is available in Firefox 3 (in beta now). There is also a generic DTrace framework, that isn’t just JavaScript only - the networking parts of Firefox, to look at how DNS lookups work, etc. all can be instrumented via DTrace.

Further reading? DTrace and PHP, demonstrated.

Technorati Tags: dtrace, php, javascript, mysql

The great Internet is littered with some really useful MySQL-related articles, that I think you’ll enjoy reading just as much as I did.

• I’ve not given Google Gears too much of a look yet, but its definitely interesting and the tutorials at O’Reilly’s ONLamp site help one play with it: The Power of Google Gears (Part 1) and The Power of Google Gears (Part 2). Looks like the series is complete, and Part 2 concentrates on using Gears for offline data entry, then syncing it with a MySQL server once the application is online. Looks like the future of desktop software might end up being like this…
• While browsing a magazine store, I picked up the SysAdmin magazine that was months old, but contained an interesting article on MySQL 5 Cluster with Solaris 10 Zones/ZFS/Resource Control. Its a very much step-by-step kind of article, and I’m excited to learn more about Zones and ZFS.
• If you’re after a basic introduction to MySQL Cluster, go no further than reading MySQL 5.0 Cluster: Architecture, Implementation and Management. Couldn’t resist browsing the rest of the samag.com website, and I’d encourage you to do the same if time permits - they’ve got quite a number of useful articles there. Incidentally, the article is a bit old (linked to MySQL 5.0.16 - cluster has had marked changes in the current 5.0.45).
• From Derek Crudgington (who wrote about Cluster and Zones), is a blog posting about the SAMP stack - A Guide to SAMP (Solaris Apache MySQL PHP). Of course for those lazy, just get the CoolStack from Sun, which allows the simple use of pkgadd.

Technorati Tags: mysql, cluster, solaris, zones, zfs, samp, google gears, gears

Like many out there, I’ve got an itch to check out what OpenSolaris has to offer. With DTrace (something I’ve played with extensively in OS X Leopard betas), ZFS (something that might show up in OS X for file system storage), Zones, and a whole bunch of other features, I’d be a luddite not to check it out.

But I must admit, Sun has got a way of confusing you. Going to the Downloads page tells you that their main intent is to confuse users. How am I supposed to choose between Solaris Express Community or Developer edition? The former is updated every other Friday, does that necessarily turn me on? Then there’s NexentaOS and the like.

Who distributes operating systems in segments? Sun do!

An OpenSolaris newbie like me, ended up picking the Community edition as well as NexentaOS. I think I’ll get them to dual-boot on my soon-to-be-dedicated Solaris box. Now, once you’re done getting their Community edition (the Sun download system doesn’t allow you to get all 3 segments at once as well, mind you - you’re limited), all 3 1GB zip files, you get the pleasure of unzipping each and every one of them, and then (get this, its really funny), use cat to make them into one large DVD ISO.

Apparently I’m not the only one who thinks this sucks. Ian Murdock has adressed this (or well, is open to comments on how to address this). Glynn Foster has also spoken about building the community mojo - Ubuntu’s ShipIt program was a great success, maybe Sun should consider this for OpenSolaris? Time-based releases are better than “builds every other Friday”. Take a cue from Ubuntu’s download page. Redmonk’s Stephen O’Grady has his traditional Q&A on Project Indiana - a must read.

Technorati Tags: opensolaris, sun, download, community, silly download mechanism