Hacker News new | past | comments | ask | show | jobs | submit | knite's comments login

Systems administration and operations are tightly scoped. DevOps is, in my opinion, an umbrella term representing all non-core engineering work: servers, build pipelines, on-call response, infrastructure, and more.

The tricky part is that a lot of these areas are relatively new, and the older ones like server admin have changed dramatically over the past two decades.

DevOps hasn't failed. DevOps is in its infancy and is going through technical, strategic, and philosophical growing pains.


DevOps has pivoted I think from the more original goal of having Devs do a lot of Ops things. This isn't really a viable solution as almost every compliance system mandates the people writing code and the people deploying/running systems are different.

What we have now is Ops that use things like source control. Write scripts that are more modular, reusable and composable. A new application can have cloud resources created and allocated in a day rather than a month of tickets to several other teams. This is also granting visibility to things that Ops may have been doing, but it was scripts on a PC or build server that only Ops had access to.


You literally wrote: "the story is almost a word for word translation of a story that's been circulating for years in Chinese".


Is it not?

There's a story that has been circulating for years in Chinese. CHECK.

This story is almost a word for word translation of that. CHECK.

What is wrong with that statement? At the same time, A story that has been circulating for years in Chinese would also almost be a word for word translation of this story.


This a great point, surprised you received no follow-up comments!


There are too many different tools in the space. I've been heavily researching workflow / ETL frameworks this week, and even after culling the ones that seemed like poor fits, I'm still left with:

- https://github.com/getpopper/popper

- https://docs.pachyderm.com/

- https://github.com/lyft/flyte

- https://aws.amazon.com/step-functions/

- https://github.com/spotify/luigi

- https://docs.metaflow.org/

- https://github.com/dagster-io/dagster

- https://github.com/argoproj/argo

- https://github.com/prefecthq/prefect


I'm about to book a LV visit for late March, which hotel offered you free nights?


Location: San Francisco (no east/south bay)

Remote: open

Willing to relocate: open, especially New York

Technologies: devops, Python, Terraform, Ansible, architecture, infrastructure, SRE

Resume: https://www.linkedin.com/in/pikeas

Email: pikeas@gmail.com

Experienced devops lead looking for eng manager / director opportunities.


It sounds like NLB passes through source IP - does that mean outbound flows are through the IGW?


There must be some magic happening somewhere, because otherwise outgoing packets would have the wrong source address.


You can use direct server return to manipulate the Ethernet frames so that packets don't travel back through the load balancer on the way to the parent switch.


That generally requires config on the serving hosts, which wasn't mentioned in the setup. I think I saw a reference to adding hosts with a different port number than the service port as well. For people in EC2-VPC (not classic), all their traffic is going through an Amazon NAT anyway, perhaps this new service is setting up translations there. (Note all the references to VPC, and never a mention of EC2-classic)


Direct Server Return works at layer 3 not layer 2, its routing and encapsulation - IP in IP, GRE etc.


You can do it at layer 2 as well, but it requires that the load balancer have an interface on the same broadcast domains as the hosts.


I am confused at how this would work. Can you elaborate? Also broadcast domain is a layer 3 construct.


As a former Cognitive and Inscape employee, @mikeryan is largely correct. Note that fingerprinting happens on the TV - no actual content was sent back to us. Still absolutely creepy.*

* Not the opinion of my (former) employer.


Once the data is sold, the cat is out of the bag. The service might not send sensitive info by itself but the DBs of the buyers might contain enough data for cross-referencing to personally identify you without a shadow of doubt.

As another poster here asked: were there any ethical discussions in the organization?


Individually yes, organizationally not that I know of.


This is my old company! Cognitive Networks, acquired by VIZIO and rebranded VIZIO Inscape.


What sort of bulk work is this? If margins are this good, it sounds like a real market opportunity!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: