Live data from Hacker News

Joyent Public Cloud EOL

docs.joyent.com

61–70 of 289 posts

Re: Joyent Public Cloud EOL

#61

Can anyone explain Joyent to me? My understanding always was that they're some special kind of hosting provider. But I never really got it. They sponsor Node.js, they sponsor all kinds of ex-Sun Solaris-related stuff, employing high profile people from both communities. What does supporting (and, at a time in the past, basically running) Node.js get a hosting provider? What about Joyent's products is related to Node…

Yes I'm interested to know if this affects what they were doing with VPC control plane for FreeBSD and the subsequent integration with Vagrant and VMWare.

The FreeBSD/VPC hypervisor efforts ran into a few “corporate speed bumps.” A few folks, myself included, are working to merge this code and make it generally available. The FreeBSD hypervisor effort certainly was the best systems work I’ve seen in my life, especially in such a short amount of time and given the resources at our disposal. My favorite anecdote was that the internal first-pass review of the benchmark data was that we had cheated because we had “exceeded the laws of computer science physics” when we saturated 100GE with VXLAN encap’ed guest traffic with no hardware acceleration, and we were only using a half a CPU core. If someone asked me to do this type of work again I’d use FreeBSD as the base again in a heartbeat. Good systems engineers are invaluable. Working from a solid technical foundation is equally critical, so is the community.

The control plane work likely won’t be made available (it was Linux specific, anyway). :-/

As for both the FreeBSD work and control plane work, it was good times, good memories, and a great team while it lasted.

Re: Joyent Public Cloud EOL

#62
post #26

Earlier quoted context omitted.

Source? I've not heard that take and would be curious to read more about it.

https://techcrunch.com/2008/01/31/twitter-and-joyent-split-a...

This article makes it sound more like Twitter left the relationship because Joyent wasn't delivering on performance and stability.

Re: Joyent Public Cloud EOL

#63
post #61

Earlier quoted context omitted.

Yes I'm interested to know if this affects what they were doing with VPC control plane for FreeBSD and the subsequent integration with Vagrant and VMWare.

The FreeBSD/VPC hypervisor efforts ran into a few “corporate speed bumps.” A few folks, myself included, are working to merge this code and make it generally available. The FreeBSD hypervisor effort certainly was the best systems work I’ve seen in my life, especially in such a short amount of time and given the resources at our disposal. My favorite anecdote was that the internal first-pass review of the benchmark da…

Are there any blog posts/email threads you'd point people to if they want to read more about the work that was done?

I'd love to see and read about some of the things you ran into, and how you accomplished some of those high speed transfers.

Re: Joyent Public Cloud EOL

#64

Can anyone explain Joyent to me? My understanding always was that they're some special kind of hosting provider. But I never really got it. They sponsor Node.js, they sponsor all kinds of ex-Sun Solaris-related stuff, employing high profile people from both communities. What does supporting (and, at a time in the past, basically running) Node.js get a hosting provider? What about Joyent's products is related to Node…

My understanding is that Joyent is comprised primarily of Sun refugees who've attempted to compete in the same OS/server space that Solaris operated upon way back when. They were acquired by Samsung in 2016-ish iirc. Solaris/illumos has failed to gain traction and the already-tiny community has only dwindled over the last few years with the expiry of OmniTI and other major illumos users. The death knell really being…

> My understanding is that Joyent is comprised primarily of Sun refugees

This is by far the best explanation I have heard. Suddenly Joyent makes sense to me after all these years. They have been continuing to do what Sun did.

In a very similar way to how Sun followed the fatal strategy of simultaneously trying to make money selling proprietary Unix hardware, while also making their software open source and porting it to more popular architectures, while simultaneously developing Java as a portable programming language intending to erase all differentiation in underlying architecture/OS differences …

Yes: Joyent is (was) a hosting company trying to compete with AWS, claiming technical superiority in the software stack. Yes they also make an OpenStack competitor. And had their own programming language runtime, node.js, which seemed to be an odd implementation choice for their classic old-school unix tech. All of the above.

Re: Joyent Public Cloud EOL

#65
post #61

Earlier quoted context omitted.

Yes I'm interested to know if this affects what they were doing with VPC control plane for FreeBSD and the subsequent integration with Vagrant and VMWare.

The FreeBSD/VPC hypervisor efforts ran into a few “corporate speed bumps.” A few folks, myself included, are working to merge this code and make it generally available. The FreeBSD hypervisor effort certainly was the best systems work I’ve seen in my life, especially in such a short amount of time and given the resources at our disposal. My favorite anecdote was that the internal first-pass review of the benchmark da…

Thanks for the info! Yeah, I'd been lurking and reviewing what if any of it I could grok since I heard about it over a live session of BSDCan. Looking forward to it becoming GA you've got my blessings for sure.

Re: Joyent Public Cloud EOL

#66

Earlier quoted context omitted.

My understanding is that Joyent is comprised primarily of Sun refugees who've attempted to compete in the same OS/server space that Solaris operated upon way back when. They were acquired by Samsung in 2016-ish iirc. Solaris/illumos has failed to gain traction and the already-tiny community has only dwindled over the last few years with the expiry of OmniTI and other major illumos users. The death knell really being…

While I appreciate your thoughts and prayers for my future endeavors, know that you will likely be disappointed: the beauty of open source is that it endures on the strength of its ideas alone -- and telling a group of people to stop working on a technology simply because you find alternatives scary is unlikely to be convincing. One of the most important lessons I have drawn from the many open source communities that…

> So if by asking me to "turn in" you are asking me to forsake my own engineering values for purposes of your comfort, well, no, I'm afraid that isn't going to happen.

Of course I'm not suggesting that you forsake your values. I'm sure anyone who has followed you for any amount of time knows that will never happen. There is no stronger advocate for the principles upon which your work is based, and your fervor and commitment is extremely admirable.

My suggestion is merely that it's perhaps time to acknowledge that the market is not going to adopt illumos in a major way. An outflow of that is considering the possibility that the considerable engineering resources at your command may be better deployed in attempting to instill and carry forth the same crucial, badly-needed principles and values into projects that have more realistic prospects, to the extent possible, rather than remaining 1000% committed to a lost cause, where the principles and values will flare out in obscurity. "If a tree falls in the forest..."

illumos is an immense contribution to our collective engineering heritage and I entertain no illusion that it should be totally iced. Personally I would consider it a glorious resurgence to see it more widely adopted, and to see it become the basis of a new generation of systems. SmartOS is simply a joy compared to the train wreck that passes for systems management in today's mainstream, and I sincerely hope that the wheels turn to make it a more viable option. The ongoing open-source contributions of the faithful volunteer keepers of the flame will be invaluable in leaving that possibility open.

While there is no doubt that illumos's open-source heritage ensures it will live on, we must be realistic and admit that for all practical intents and purposes, the sun has set on the project's general commercial viability (at least for the time being -- the thing about sunsets is, they're followed by sunrises).

The question I pose is whether your advocacy may be more effective in bringing the values and contributions of yourself and your team in force to more active venues, than by continuing to toil in the last fleeting fragments of the twilight of Solaris's commercial viability.

I personally know many young engineers who admire your talks but have no exposure to the actual process of working with you directly. What would change if they got that? Would there be a Cantrill Youth? What's the likelihood of passing on that flame within illumos v. expanding your horizons to other groups?

Re: Joyent Public Cloud EOL

#67
post #24
post #21

Earlier quoted context omitted.

Yeah how can you compete against AWS / x86 / Linux on that space not sure.

With technology which is an order of magnitude more concerned with reliability and easier to use than any competition out there, that's how.

Apparently not.

Re: Joyent Public Cloud EOL

#68
post #61

Earlier quoted context omitted.

The FreeBSD/VPC hypervisor efforts ran into a few “corporate speed bumps.” A few folks, myself included, are working to merge this code and make it generally available. The FreeBSD hypervisor effort certainly was the best systems work I’ve seen in my life, especially in such a short amount of time and given the resources at our disposal. My favorite anecdote was that the internal first-pass review of the benchmark da…

Are there any blog posts/email threads you'd point people to if they want to read more about the work that was done? I'd love to see and read about some of the things you ran into, and how you accomplished some of those high speed transfers.

The best talk I gave on this wasn’t recorded (and had another section on the details of the new MBUF struct that mmacy came up with), but here are a few pointers for the time being:

https://youtu.be/La4ekkKbM5o

https://github.com/joyent/freebsd/tree/projects/VPC

https://www.slideshare.net/mobile/SeanChittenden/freebsd-vpc...

Re: Joyent Public Cloud EOL

#69
post #61

Earlier quoted context omitted.

Yes I'm interested to know if this affects what they were doing with VPC control plane for FreeBSD and the subsequent integration with Vagrant and VMWare.

The FreeBSD/VPC hypervisor efforts ran into a few “corporate speed bumps.” A few folks, myself included, are working to merge this code and make it generally available. The FreeBSD hypervisor effort certainly was the best systems work I’ve seen in my life, especially in such a short amount of time and given the resources at our disposal. My favorite anecdote was that the internal first-pass review of the benchmark da…

Wow pushing 100gbps on half a core without hardware acceleration is an incredible feat. Can you provide more information on how this was done?

Re: Joyent Public Cloud EOL

#70

Earlier quoted context omitted.

My understanding is that Joyent is comprised primarily of Sun refugees who've attempted to compete in the same OS/server space that Solaris operated upon way back when. They were acquired by Samsung in 2016-ish iirc. Solaris/illumos has failed to gain traction and the already-tiny community has only dwindled over the last few years with the expiry of OmniTI and other major illumos users. The death knell really being…

While I appreciate your thoughts and prayers for my future endeavors, know that you will likely be disappointed: the beauty of open source is that it endures on the strength of its ideas alone -- and telling a group of people to stop working on a technology simply because you find alternatives scary is unlikely to be convincing. One of the most important lessons I have drawn from the many open source communities that…

You are the guy who warned about anthropomorphizing Larry Ellison, right? So true and so fun.
Post reply on HN