HNHacker News
TopNewBestAskShowJobs

gabrtv

652 karma · joined December 30, 2010

vp, microsoft developer division. serverless functions, aPaaS, messaging, workflow engines, api management, and some of the internal systems and open source that makes it all possible.

deis co-founder. cncf board member.

submissionscomments
gabrtv··on Show HN: konfd – Manage Kubernetes secrets and configmaps with Go templates
More great stuff from Kelsey...

My tldr; konfd writes out k8s configmaps based on other k8s resources like secrets, configmaps, etc. Really useful for writing out complete config files into a pod namespace without relying on external config backends.

Question: While looping on a syncInterval is certainly clean and understandable, it feels suboptimal when all the templates sources are themselves watchable with a k8s client. Benefits of switching to a watch model:

1. Speed: It'd be nice to have the template rendering fire immediately after a source secret changed versus waiting for syncInterval.

2. Resource Utilization: Switching from syncInterval to a watch should save significant cycles by avoiding reprocessing templates when config hasn't changed.

gabrtv··on Deis Workflow, Now Stable
Hi folks, I'm Gabriel the CTO at Deis and author of the blog post. Happy to answer any questions!
gabrtv··on Ballparking Ello's active user statistics
I'd say the niche is "creatives". Designers, artists, musicians, hipsters, etc.
gabrtv··on Rearchitecting GitHub Pages
I had no idea. That's great news!
gabrtv··on Rearchitecting GitHub Pages
I was hoping to see something about optional SSL/TLS. I'm even willing to pay for it.
gabrtv··on Ask HN: Any successful startups that is founded by a designer?
Ello, the popular social network, was founded by designers: https://ello.co/wtf/post/founders
gabrtv··on Building Microservices the Lean Way, part 2
> The services are considered to be in a trusted network and are accessed by a private token passed in the ‘Authorization' header plus the user id of the requester in an ‘X-USER’ header.

This reads like the user ID is exposed in a header without any sort of encryption.

gabrtv··on Ask HN: Documentation before starting a software project?
I'm a big believer in "Readme driven development" [1]. It's critical you go through the exercise of 1) explaining what the software will do and 2) how it will be used with concrete examples. The value of this documentation will always outweigh the time spent writing it.

[1]: http://tom.preston-werner.com/2010/08/23/readme-driven-devel...

gabrtv··on Now available: auto-scaling PostgreSQL deployments
Not many PostgreSQL DBaaS offerings out there. This is great news.
gabrtv··on Is Docker ready for production?
Deis maintainer here. We understand Deis can be a bit heavy for those who don't want a multi-node HA setup. For the 'humble web developer' we strongly recommend Dokku. In fact, we're now sponsoring that project: http://deis.io/deis-sponsors-dokku/
gabrtv··on Deis v1.0 – Production Ready
This is exactly why we sponsor Dokku: http://deis.io/deis-sponsors-dokku/ Go Dokku! :)
gabrtv··on Deis v1.0 – Production Ready
No. As a PaaS designed to run enterprise workloads with high availability, Deis has a 3-node minimum.

If you're looking for a similar workflow but with a smaller footprint, Deis now sponsors the Dokku project: http://deis.io/deis-sponsors-dokku/

gabrtv··on Deis v1.0 – Production Ready
Short answer: Deis is easier to install/operate and it's designed to leverage Docker from the ground up. You won't be promoting Docker images through a CI/CD pipeline with Cloud Foundry any time soon.

Email me for a longer answer: gabriel@opdemand.com. ;)

gabrtv··on Deis v1.0 – Production Ready
Your point is taken: some of the underlying technologies we use are still under active development. That said, we've worked with enough production Deis deployments to know that etcd and fleet (for example) run much better than some might think.

As early adopters of these technologies, we have strong relationships (and often formal L3 support) with the teams involved. We are often the first to report issues as well as the first to test fixes. You can view this announcement as a vote of confidence in those projects and our ability to roll out fixes as bugs surface.

Hope to see you back in the #deis channel soon!

gabrtv··on Deis v1.0 – Production Ready
Deis and Kubernetes are solving different problems. Deis is a PaaS that provides a developer self-service capability a la Heroku. Kubernetes is a declarative container manager that provides lower-level orchestration features. Both are complimentary. For example, Red Hat is using Kubernetes to deliver their OpenShift v3 PaaS. We've explored a similar integration with Kubernetes but are currently more focused on integrating with Mesos a next step.
gabrtv··on Deis v1.0 – Production Ready
Project creator here. It's been a fun 16 months getting to this point. Happy to answer questions.
gabrtv··on Deis Announces High Availability Backed by Ceph
There's lots of smart teams working on these problems. We believe working with them is better for our users and for the community as a whole. :)
gabrtv··on Goodbye Heroku
Deis is for software teams who need to operate their own servers (for a variety of reasons). If you're a "regular developer with little real world Ops experience", I personally recommend sticking with Heroku or equivalent hosted services despite the occasional outages.
gabrtv··on Goodbye Heroku
Deis has quite a few successful deployments in the wild. Most of the work being done today is around automated testing, platform hardening, HA/failure modes, etc. A stable release is not far away.
gabrtv··on Docker container breakout?
Docker image to test if your host is vulnerable to this particular open_by_handle_at() container breakout: https://registry.hub.docker.com/u/gabrtv/shocker/

Remember to always audit the source code before running something like this. Origin repo is here: https://github.com/gabrtv/shocker

gabrtv··on SkyDNS 2.0 with a new etcd backend
Great to see an etcd backend. Nice work.

One feature I'd love to see is support for an etcd discovery URL (versus having to provide an explicit list of peers). See: http://coreos.com/docs/cluster-management/setup/etcd-cluster...

gabrtv··on Command-line interface description language
We've found docopt to a great fit for complex subcommands. Create a simple global usage string `command <subcommand> [options]` and call docopt again with the subcommand's specific usage.
gabrtv··on Deis 0.9.0 – Dockerfiles, Domains, and HA Routing
shykes is right on. :) We view Docker as the key point of interoperability and will have more to share on that front soon.
gabrtv··on Deis 0.9.0 – Dockerfiles, Domains, and HA Routing
> So, looking at the architecture, it seems like you have some design components that overlap with pieces design components in CoreOS. I'm not clear as to what components are really application components vs. platform operations components, so maybe that's it.

Deis was architected before the CoreOS integration. While we love CoreOS, architecturally we need to remain scheduler agnostic. Probably a good opportunity for a blog post...

> the use of rsyslog in lieu of systemd seems like really going against the CoreOS grain

We view platform logging as separate from application-level logging. Aggregating logs through the systemd journal is possible, but it would tie us a little too closely to systemd. Using log sidekick containers (as we do) is more portable and easier to funnel to end developers.

gabrtv··on Link shorteners hurt the user experience and destroy the Web
Bog standard permalinks to the rescue: company.com/some-promotion
gabrtv··on Zero Downtime Frontend Deploys with Vulcand on CoreOS
Come find us in #deis on Freenode and we'll see if we can help.
gabrtv··on Zero Downtime Frontend Deploys with Vulcand on CoreOS
Top notch technical writeup. We've had our eyes on Vulcand for some time now, though we'd really like to see native TCP support.
gabrtv··on Deis 0.8.0 – CoreOS Integration
You can do everything you mentioned with Deis 0.8.0.

- Process management is handled the same way it is on Heroku, with a `deis scale` command. The fleet scheduler ensures processes are automatically restarted on host failure.

- How you secure network traffic is done differently depending on your environment (EC2, metal, etc). It's just a matter of configuration.

- Environment variables are managed using the `deis config` command, which creates new Docker images under the hood. We also support rollbacks of new builds and configuration changes using `deis rollback`.

- Log management is handled automatically for deployed applications. Developers can see their app's aggregated logs with `deis logs`. For platform/host logs, you can configure `journalctl` on CoreOS to drain whereever you like (Logstash, Splunk, etc)

- Server monitoring is often done at the hosting provider level (EC2 CloudWatch, etc). You can also configure agent-style host monitoring at the CoreOS level. We're currently working on some packaged solutions in this area.

There are some gaps in our documentation re: things like firewalling/SSL, monitoring, and draining platform logs. We are working to fill those documentation holes. But like I said, everything you mentioned is possible with Deis today. If you have further questions, hit me up at gabriel _at_ opdemand.com.

gabrtv··on Deis 0.8.0 – CoreOS Integration
We are grateful for the Flynn project's emphasis on modular, reusable components that can be leveraged by those building platforms. I suspect we will collaborate more in the future :)
gabrtv··on Deis 0.8.0 – CoreOS Integration
I think the biggest difference is that Flynn is building a scheduler modeled after Google's Omega paper (what they call Layer-0) along with the Heroku-style platform components (which they call Layer-1) -- all written from scratch in Go.

Deis, on the other hand, is laser focused on the platform problem. We're also not shy about using off-the-shelf components where they make sense. For example, we believe the distributed scheduler/init system is best left to others like CoreOS/Fleet.

← PreviousPage 2 of 5Next →