chologrande

6 ms·

1.
by chologrande 2y ago
why yaml plus real code? why not just real code? does yaml ever actually provide benefits in testing like this?
2.
by chologrande 3y ago
I can simply run `helm install cert-manager` or `kubectl operator install cert-manager -n cert-manager --channel stable --approval Automatic --create-operator-group ` - both have dependency resolution. Not trying to be negative here, trying
3.
by chologrande 3y ago
How is this any smaller than OLM or the Operator pattern? Having trouble seeing the differentiator other than "it's different"
4.
by chologrande 3y ago
I work at a recently IPO'd tech company. Oxide was a strong consideration for us when evaluating on prem. The pitch lands among folks who still think "on prem.... ew". Looks like a cloud like experience on your own hardware.
5.
by chologrande 3y ago
> Had to do a lot of work to get node utilization ... higher than 50% How is this the schedulers fault? Is this not just your resource requests being wildly off? Mapping directly to a "fly machine" just means your "fly mac
6.
by chologrande 3y ago
oh that's nice I didn't know that! Still a stickler on yaml for code though
7.
by chologrande 3y ago
The blog perfectly sums up the feelings of anyone who has worked deep in jenkins. It works, but goddamn it's hard not to hate. Dagger is the answer to jenkins woes. It's saved my sanity and made CI development tolerable again. * R
8.
by chologrande 3y ago
How is Gitlab CI materially different from the jenkins model? I find that the only difference is that it's YAML - so even harder to debug, and maintains the same model where you must re run an entire pipeline every commit to test funct
9.
by chologrande 3y ago
wow I can't facepalm any harder, I hadn't seen the architecture docs etc in the top level repo... and they're at the top level.
10.
by chologrande 3y ago
I'm just skimming, but it looks like the docs are fantastic. I've spent some time with terraform internals, and this seems like a significant improvement for a dev looking to work with this codebase. Gives a great overview to get
11.
by chologrande 3y ago
1. I mean aging as a paradigm. 2. I mean I don't use ansible with any cloud, only with hardware or legacy on prem stacks - older versions of Cisco, Netapp, Vmware. I prefer a stateful system like terraform to a stateless one like ansib
12.
by chologrande 3y ago
Hate to only shill hashi stack but packer if you must. All you need is a container runtime and linux kernel. After that you shouldn't have to think about the core node. If you're _really_ bare metal - build the base image, boot px
13.
by chologrande 3y ago
Ansible is great, but (imo) aged. Sure it's good for dealing with legacy hardware that cannot support terraform like state, but (imo) untyped yaml and excessive playbook runtimes turn into significant development drain as you scale. An
14.
by chologrande 3y ago
100% - having to submit code server side to just get compilation results is the worst development loop I've ever experienced.
15.
by chologrande 3y ago
Sure - but where's the revenue come from?
16.
by chologrande 3y ago
just wait for the GPS Log 2.0 release. that thing will probably only get about 30 snags
17.
by chologrande 3y ago
What exactly is a "shadow IT app" ? How in the heck is _Evernote_ the top shadow IT app or related to automation and aI?
18.
by chologrande 3y ago
You're assuming you know the use case. We do more than serve LAMP stack. It takes more than a few playstations I can assure you.
19.
by chologrande 3y ago
I'm definitely not google scale, but we're global, in over 300 cities spanning ~30 countries. On an avg day we process well over 25k rps on multiple services. Simple architecture and IaC like terraform is exactly how we manage the
20.
by chologrande 3y ago
Mandated peer review, planned actions, and automated risk evaluation are part of our infra pipeline. This typically doesn't exist outside of software dev style pipeline.
21.
by chologrande 3y ago
After reading this post, I've browsed the site. I'm not sure how this is anything but significantly worse than the current model? I've been around long enough to know that any "no code" style interface or GUI are ty
22.
by chologrande 3y ago
Lots of comments here chiding OP for running or talking about this; I think there's something to learn here. This is just a hobbyist prompt and api. If nothing else, I'd say at minimum this highlights that there are likely much la
23.
by chologrande 3y ago
It does seem like they just moved all of their infra components, and got rid of autoscaling. Load balancing, logging, and other associated components are all still there. Almost nothing changed in the actual architecture, just how it was ho
24.
by chologrande 4y ago
I can't help but wonder if non-profit makes it easier to get access to or train on certain datasets/models.
25.
by chologrande 4y ago
Any time I see a nodejs tool aimed at systems tasks (general infrastructure, IaC, etc) I immediately disregard it. While, to be honest, I'm not sure that's a fair way to look at tools like this, it's the reality. I always won
26.
by chologrande 4y ago
Storage, Virtualization, and general UX are just completely different. Standard unix utilities are either not available or just different enough to make life hard.
27.
by chologrande 4y ago
At the risk of sounding like a tesla fanboy, this seems crazy to me. NHTSA investing significant resources into 36 crashes over the past 6 years? This seems like an impossibly low number of crashes. Intuition tells me there must be _many_ m
28.
by chologrande 4y ago
written in javascript... noooooope
29.
by chologrande 4y ago
3 days later a response. We have extensive jenkins pipelines, and the "platform team" supports multiple types of build/release models. Most of the infrastructure is written in TF. * 3 languages * 5 "types" (http&#x2
30.
by chologrande 4y ago
you _can_. but _should_ you? Ansible / Terraform are great when you're declarative, but once you start adding too much logic, things get hairy.

More ›