tjfontaine
Joined 13 years ago
Karma
188
Submissions
25
Member since
Jul 4
Recent submissions
Comment · 2 years ago
Looks like it’s to only have one completion running at a time currently, https://github.com/distantmagic/paddler/blob/main/loadbalanc... I was curious if there was any other cache tracking happening
Comment · 2 years ago
I enjoyed using this app and will be sad to see my current 217 day streak end.
While it's far from the only app that offered a reader mode, its implementation handled some of the more esoteric news sources (with disruptive layouts) better than the others I've tried. But the feature I will miss the most is title rewriting ("mark as clickbait") which I now hope to see as a feature on all my "reader" class apps (news, email, etc).
Great work, and kudos to the team.
Comment · 3 years ago
In my experience, because it is documented that’s the behavior I would expect.
That being said, I went to look[0] and it turns out it wasn’t a lie. [0]https://github.com/illumos/illumos-gate/blob/master/usr/src/...
Comment · 5 years ago
My first thought was https://en.wikipedia.org/wiki/WinFS
Comment · 6 years ago
I understand your position, but often the memory leaks in your runtime are not your fault — https://www.joyent.com/blog/walmart-node-js-memory-leak
It’s difficult to find and diagnose these types of issues, so anyone looking into RAII style leaks, or long lived closures, need tools to help them understand their allocations and their life cycle to be able to solve their problems.
Comment · 7 years ago
You can use eBPF tooling to attach to User SDT probes; this library is a way to instrument your code once and have those probes available via the appropriate tracing infrastructure on the running platform
Comment · 7 years ago
I can say without a doubt, if it weren’t for Joyent, my fantastic coworkers, and the experience and opportunity they granted me I wouldn’t be where I am today. I fondly remember debugging issues and learning so much with my talented coworkers. Congratulations Joyeurs on everything you’ve done to forward the Public Cloud and Systems Engineering.
Comment · 7 years ago
I believe some of the thinking has shifted toward virtio-fs[1] instead of the 9p/network oriented models. Though this requires hypervisor locality for sharing among VMs.
Comment · 7 years ago
So essentially you just need to put your gRPC agent in a linuxkit image with access to the containerd socket? That’s how the docker in docker/kubernetes examples already work for LinuxKit.
I am not sure what exactly you mean by “does not allow host level access”, the benefit of linuxkit is you can configure the software that needs to run in the root namespace, or not, aside from every process generally having a mount namespace.
The real benefit (imo) of LinuxKit is the familiar declarative manifest model for image definition, and container configuration. As a by product, it’s really straight forward to have reproducible builds.
Comment · 7 years ago
I’m all for more people using immutable machine images for their base system images, and think more environments should be built this way.
However, I’m not sure what the difference is here from say https://github.com/linuxkit/linuxkit which also has an example for how to use LinuxKit to build Kubernetes environments https://github.com/linuxkit/kubernetes
Comment · 8 years ago
Precisely, the dependency we're talking about here is "just" leveraging Kubernetes as a generic extensible control plane which makes it quite convenient to plug into for management of resources.
Comment · 8 years ago
Both crossplane[1] and CNAB are attempting to play in similar spaces, understanding that deploying an application for the cloud (public or private) is more than just dumping your software into an image and giving it to a provider (be it K8s or some other IaaS/PaaS stack). There's more associated with the application, specifically what it means to orchestrate IaaS/PaaS/SaaS to realize your application.
But I see CNAB falling into the same trap as Helm, and many of the package managers before them (including newer variants with things like charm/juju), an archive with some notion of lifecycle events is not enough. Even though it's cute that lifecycle events are encapsulated in containers making it easier to manage their runtime dependencies.
What I think makes Crossplane's model more attractive is the notion of building on top of Kubernetes design and leveraging things like the operator pattern[2]. Now application stacks can do more interesting actions during their lifecycle, which can work to preserve availability during an event (like upgrading your application stack). Crossplane is about expanding the management of resources beyond just containers running in your cluster, but to any resource you can model in the K8s control plane and writing software that can react to events related to those resources.
[1] https://blog.upbound.io/introducing-crossplane-open-source-m... [2] https://coreos.com/operators/
Comment · 8 years ago
LinuxKit is a way to build immutable machine images by stitching multiple containers together.
You could use the resulting container from a buildpack in an image built by LinuxKit.
Comment · 9 years ago
Note: Oracle is my employer, the following statements are my own — (insert Safe Harbor notification)
Good news regarding any trepidation on the differencesa between the runtimes — recently we announced that there will no longer be a difference between OpenJDK and OracleJDK [1]
To quote: “The Oracle JDK will primarily be for commercial and support customers once OpenJDK binaries are interchangeable with the Oracle JDK (target late 2018)”
[1] https://blogs.oracle.com/java-platform-group/faster-and-easi...
Comment · 9 years ago
Here's a different reason (jbergstroem also alludes to [1]) why Docker (the company) would rename Docker (the open source project) to a name that cannot be confused with Docker (the product): Trademark (Enforcement).
How do you (a for profit company built on open source) enable your community, to build and sell (their own) products, as well as enforce your trademark? If anyone (everyone?) can build and distribute and call their build `docker`, it becomes really hard to protect your investment (as a company and their fiduciary responsibility to their stock holders) from dilution of TheBrand(tm).
This is not cynicism and I don't fault Docker (the company) at all, it's just the reality of doing business. It's why Canonical requires a contractual relationship for infrastructure clouds to distribute Ubuntu images, it's why you have things like Firefox and IceWeasel, so on and so forth.