russell_h · HackerTrans

25 days agodiscuss

MCP auth has been a huge pain point for us at C1 - both for our own internal MCP use and in our in-product MCP Gateway - so very glad to see this landing.

We launched support today for C1 to act as an EMA identity provider (we mint the short-lived scoped tokens), so I'm excited to hook this up for Linear and some of the other MCPs we use, and get out of the business of constant OAuth flows. Claude has been doing this magically for some of their built-in connectors (at least Slack I think) and the experience is pretty great.

Disclosure: VPE at C1. We wrote up how we’re approaching it here if anyone’s in the weeds on this: https://www.c1.ai/docs/product/admin/enterprise-managed-auth...

russell_h

4 months agodiscuss

I think the argument would go that if people are clicking through certificate errors and you're in a position to MITM their traffic, you can just serve them a different certificate and they'll click through the error without noticing or understanding the specifics.

russell_h

8 months agodiscuss

ConductorOne | ONSITE (SF / PDX) | Full-Time

ConductorOne is building the platform for identity security and least privilege automation — helping companies secure access to everything, without slowing people down. Our engineering culture emphasizes small, high-ownership teams that deliver measurable impact and move quickly.

We’re hiring across many areas:

  - Software Engineers – We’re growing our product development teams in SF and Portland.

  - Site Reliability Engineering – We’re looking for SREs and a hands-on SRE manager (SF or Portland) to own reliability, performance, and infrastructure as we scale.

  - Forward Deployed Engineering (FDE) – We’re building a brand-new customer-facing engineering org: we're looking for engineers who want to work closely with customers to modernize and automate identity operations, and a Manager, FDE to lead the team.

  - Governance, Risk & Compliance (GRC) – We’re building a new GRC function and hiring our first Compliance Engineer to help scale our security and audit programs.

We work primarily in Go and TypeScript, on AWS + Kubernetes.

Apply here: https://www.conductorone.com/careers

russell_h

9 months agodiscuss

https://en.wikipedia.org/wiki/PlayStation_3_cluster

russell_h

2 years agodiscuss

I don't share OP's hostility to VC-funded databases, but PingCAP is definitely VC-funded: https://www.pingcap.com/press-release/pingcap-the-company-be...

russell_h

12 years agodiscuss

We are running these in OnMetal: http://www.lsi.com/products/flash-accelerators/pages/nytro-w...

Reliability is similar to an SSD. The underlying storage tech is basically the same: some flash chips, with a controller that handles wear leveling and so on. Just that instead of running operations through a SATA controller it uses the PCIe bus, which offers higher bandwidth and lower latency.

Interestingly, Apple is shipping PCIe flash in all (I think) of their latest laptops.

russell_h

12 years agodiscuss

Our IO flavor has 2x 1.6TB PCIe flash cards, this is how we see most users running databases or otherwise persisting "hot" data. I've gotten to play with these over the last few months, and its really incredible how fast they are - they totally crush even high end SSDs. People have traditionally used these in a tiered setup to accelerate spinning disks, but the costs have come down to where it hardly makes sense to use anything else for low latency persistent storage.

We're working to hook this up to our existing block storage offering as well, which will offer more flexibility to attach SSD or spinning disk backed block devices to any flavor.

russell_h

12 years agodiscuss

That's basically correct, we were trying to balance a few factors:

  - Total cost
  - Cost per core
  - Clock speed (this actually matters a lot for, say, a Python webapp)

We chose to run only a single CPU in this box to keep the total cost of the box low. This slightly increase the cost per core (switch ports, the chassis, rack space, etc being basically fixed overhead per node), but by selling in smaller increments we think it we can keep the total cost lower for most users.

We'll be gathering feedback on the resource balance, and iterating as we go.

russell_h

12 years agodiscuss

Engineering manager on OnMetal here.

Our first iteration, you'll get two networks: "ServiceNet" is our intra-DC network, which is unmetered (ie, free bandwidth) and "PublicNet" which is the internet and will be billed just like we bill for other cloud server bandwidth. Collectively you get 10Gb/s across these, which you can break down however you want. To you these just show up as VLANs which will be configured on build.

We're working on hooking these boxes up to our "Cloud Networks", which are per-tenant software defined networks. If this sounds like a fun project, hit me up, contact info is in my profile.

comments