willejs

Did Heptio do some consulting for Amazon AWS? They have a guest blog post from memory, and im wondering if they helped kickstart EKS? Obviously they built aws-iam-authenticator, and as a company worked with AWS services... I would have thought Amazon acquiring them would have made way more sense?

It is 30 T1s in theory, but the physical connectivity is RJ-48 for T1 and x2 coaxial for T3. Both can be channelized into voice, or un-channelized for data...

What hardware are you running pfsense on?

Aspera uses UDP to work around issues sending large files over long distances on big pipes, which TCP usually isn't great for (1). How does MASV handle this over TCP? Do you have some 'tcp accelerators' in between or it is just heavily chunked content?

1. https://paulgrevink.wordpress.com/2017/09/08/about-long-fat-...

FreeBSD jails it is then.

I've done this once, and only once.

I am using it as a secrets backend for concourse pretty extensively. It's just good enough for that if you lock down the parameters with IAM policies, allowing restrictive get and puts. I am a huge fan of vault, and have run it before when needed though.

This was posted a while back, and you can see the original thread with more comments here https://news.ycombinator.com/item?id=14031180

AWS SSM pretty decent as a middle ground.

Shut up Nathan Barley.

I think he makes some really great points here, and obviously has some pretty good experience at running data stores in the real world, at scale.

I think his comment about stateful sets is more focused about running data stores on distributed filesystems, or network attached storage. This isn't a good idea generally, and I am not going to go into why, but Cassandra and Etcd advise against this for a reason, its well documented. It wouldn't just be using a 'better' storage system, it would be designing and implementing a very complex operator as he mentions.

The real take away which I think we should all realise is that, this is shiny tech to run mission critical data stores on, unless you know what your doing and want to invest a lot of time and effort in to it. Right now it's probably better to use RDS/Cloud SQL, or just run a traditional postgres setup with a SAN and decent failover that is tried and tested.

You nearly had me there.

It is only a matter of time before someone here suggests you use self hosted gitlab/github enterprise. Ain't got time for that.

This could be quite useful to define the basic things a container should exhibit. A lot of the time you rely on certain files being present or a specific entrypoint and command combo when running containers under orchestration with sidecars or volume mapping etc. So this could help you define what is needed and why for others who will change your container build steps in future.

It could also compliment your Goss or Inspec integration tests quite nicely.

Here here.

You are correct. London has a few Sandwich places that most people know about, Obviously Pret, then maybe The Earl of Sandwich, and Birley Sandwiches. These are all pretty average at best. Max's Sandwich Shop in Stroud Green, or Monty's Deli are worth checking out. All the people below obviously haven't ever eaten a decent sandwich.

Gatling is great, and the best thing to use if you want performance and fine grained analysis. It's easy to use, great html output with graphs. You can also output to a bunch of other formats, and easily break out into scala. Don't let the scala put you off though, its mostly a really simple and clean dsl. The docs are good too!

Because a lot of organization use privately hosted CI/CD systems, such as concourse. :-)

Not really. Its quite straight forward and really just makes it easier to store your creds (on any platform) securely, and enables you to switch roles via profiles in your ~/.aws/config.

One thing I would point out is that by default it will timeout the session in 4h and the role in 15m. This means that every 15m you will need to exit your bash shell that aws-vault exec created, or replace the env vars you generated. Set the two env vars for session and role ttl to your desired values in your bash profile to avoid setting them on the cli on every invocation.

You just want to look at this file, as the env vars are not documented. https://github.com/99designs/aws-vault/blob/4acbb48b48b90555...

This is the best tool I've found so far to manage profiles securely and switching roles between the ~35 accounts im working with right now.

This.

Blockchain could fix a key problem in X

From what i have read from the bug report it fetches this asynchronously via a systemd unit. This is not so bad, originally it did it synchronously on login and would fail after 2 seconds if it couldn't fetch the url. Thats bad! My problem with it is that it is a slippery slope indeed!

I have witnessed all of this too. Using it for event based stuff seems the most sane, or small scripts...

I have heard that go will be supported in the next three months and theres a lot of improvements coming. Cant wait to ditch those js and python wrappers.

So, their breaking up the monolith? Hold on to your hat!

If anyone is considering this, consider fastly and custom VCLs too.

I'm a big fan. Ive been using it to do 'outside in' google type, expose services on the internet via oauth for ages. Its solid and great.

From the authors github, I presume its written in go. So its just going to be a binary with a config file. Thats great, and easy to deploy! I get your point, nothing is a 'production ready' deployment in 10 seconds. But, i think the author means it will 'just work' for most people. In reality, our version of production ready wouldnt take more than an our max to deploy that to ecs/kubernetes.

I had not one, but two given to me by a family friend in the mid ninties! I was young and it was epic. I could send faxes via a 14.4k serial modem with a PoqetPC to parallel, parallel to serial adaptor. I could play stunts on it, and write BASIC programs, what more would you want at age 7? Yes the battery lasted weeks, and the memory cards held a small watch battery in them. I've still got one somewhere, which I now want to dig out.