sciurus

A fantastic book! The first edition is a bit dated in places, but there's a second edition now: https://www.amazon.com/Release-Design-Deploy-Production-Read...

Here's the actual change:

> Starting with the upcoming Elastic 7.11 release, we will be moving the Apache 2.0-licensed code of Elasticsearch and Kibana to be dual licensed under SSPL and the Elastic License, giving users the choice of which license to apply.

So starting with 7.11 no parts of Elasticsearch will be released under an open source license.

They aren't making everything SSPL, though. Their paid features continue to be only available under the Elastic License.

Do you have goals outside of work that the additional money will help you accomplish?

Mozilla | Remote (US or Canada) | https://careers.mozilla.org/listings/

Mozilla exists to build the Internet as a public resource accessible to all because we believe that open and free is better than closed and controlled. Join us to work on the Web as the platform and help create more opportunity and innovation for everyone online. We're hiring for a number of operations roles right now, including

* Site Reliability Engineers

* Director of Site Reliability Engineering

* Senior Manager of Operations Security Engineering

If you have any questions about them, you can reach me at bpitts+whoshiring@mozilla.com

> We have operated this system with more than 1.5M concurrent connections and pushes over 250,000 messages per second.

1.5 million? I thought Uber would have more simultaneous active clients than that.

The feature I see missing here today I'm most excited about is searchable snapshots.

> While we've had support for backing up data to low-cost object stores for a long time, with searchable snapshots you can now use them as an active part of storing and searching your data.

https://www.elastic.co/blog/introducing-elasticsearch-search...

Wow, thanks for this comment. It hadn't occurred to me that you could interact with it. Neat!

I wonder if I'm just odd, or if people not realizing it's interactive is widespread.

I was pleasantly surprised that it's performing fine for me in firefox on a pixel 3a.

From another comment: https://www.geekwire.com/2020/retired-uw-computer-science-pr...

If you haven't seen it already, check out https://blog.mozilla.org/security/2020/01/09/crlite-part-1-a...

(Disclaimer: I work for Mozilla and have helped with the rollout of this)

I hadn't heard of WWFF before. In the US, Parks on the Air is pretty popular.

https://parksontheair.com/

LimeSDR is additional hardware.

https://limemicro.com/products/boards/limesdr/

> We are also collaborating with AWS on its new Amazon Managed Service for Prometheus, built on the Cortex project for running Prometheus at scale.

That's even more exciting news.

But this also must have major implications for Grafana Labs, since selling hosted prometheus is also a part of their business.

Edit: Found the announcement at https://aws.amazon.com/blogs/aws/join-the-preview-amazon-man...

> An Amazon Managed Service for Grafana Editor license costs $9 per active user per workspace... For customers who need only view access, an Amazon Managed Service for Grafana Viewer license costs $5 per active user per workspace

Yikes. Per-user pricing is tough for data visualization tools, since the audience for a dashboard could be really broad.

This affects GCP as well as Google's consumer services. I'm here because I was paged about low traffic for a service. Turns out to just be that I can't access any metrics at all from Google Cloud Monitoring (i.e. Stackdriver).

Did you comment on the wrong post? This seems unrelated to sops.

For anyone curious, the details on their OSS offering are at https://circleci.com/docs/2.0/oss/

They give you 10,000 minutes of build time on their 2cpu/4gb workers per week with a max of 4 concurrent workers.

The situation with Travis CI is confusing, has not been communicated well by them, and is definitely not getting enough coverage for the amount of disruption it might cause. Here's what I've been able to piece together:

? 2018: Travis CI announces they are starting the process of merging travis-ci.org, which provided free builds for OSS projects, into travis-ci.com, which until then was only for paying customers. They promise OSS builds will continue to be free.

? 2020: Travis CI announces they are shutting down travis-ci.org at the end of the year and all projects have to move to travis-ci.com. They promise OSS builds will continue to be free.

Early November 2020: travis-ci.com switches from providing unlimited builds for OSS to only providing 10k one-time credits by default. Projects that meet certain guidelines (e.g. no one paid to work on them) can apply for recurring credits.

Later in November 2020: CI for many OSS projects that had migrated to travis-ci.com starts to fail, as they've exhausted their 10K credits.

Dec 2020: If what is reported here is accurate, Travis CI stop providing any recurring OSS credits. CI breaks for the remaining OSS projects on travis-ci.com.

Jan 2021: travis-ci.org shuts down. CI will be broken for all projects using it. They'll have the option of migrating to travis-ci.com, but will soon break again as they exhaust their 10k credits.

I suspect that many, many projects haven't migrated from .org to .com and are going to be surprised when their CI breaks on January 1st. It looks like their only option is to start paying Travis CI or move to an alternate provider (like CircleCI or Github Actions, both of which have free tiers for OSS).

If Travis CI's new owners are no longer willing to provide free CI services to OSS projects, that's understandable. I just wish they'd communicate that clearly in ways that their users won't miss.

(BTW, if anyone from Travis CI is reading this, I reached out to your support team last week for help on a problem that is blocking us from potentially paying you. I haven't gotten an answer yet on ticket 23831. Any help is appreciated.)

This is a wiki, so if you know of some sites that should be listed add them!

Yep. I've edited the title to make that clearer.

Your complaint is that they require you to purchase a new annual contract after your first one ends? This really shouldn't come as a surprise.

And they'll let you roll over $9000 worth of unused credits by purchasing just $1000 new ones? This actually sounds like a pretty good deal.

I think your problem is that you purchased more than you needed via a contract you didn't understand.

Did they? I can't find that from a quick Google search.

Edit: They announced it today; see https://aws.amazon.com/blogs/aws/new-for-aws-lambda-containe...

Also, you can find a list of more public web sdrs at http://kiwisdr.com/public/

This depends on how you use it. It's pretty common to use something like statsd or a prometheus exporter to aggregate data before storing it in InfluxDB.

InfluxData is arguably playing catch-up with Thanos, Cortex, and other scale-out Prometheus backends for the metrics use case. Given that, I wonder why they decided to write a new storage backend from scratch instead of building on the work Thano and Cortex have done. Those two competing projects are successfully sharing a lot of code that allows all data to be stored in object storage like S3.

https://grafana.com/blog/2020/07/29/how-blocks-storage-in-co...

Announcement: https://www.influxdata.com/blog/influxdata-advances-possibil...

RIP https://www.cloudamqp.com/

> Being able to automatically provision a resource in AWS, then use results from that in a Kubernetes service (env var) in the same deployment, is not something I ever expected to be able to automate.

FWIW we do that with a small amount of glue code in our deployment tool that takes terraform outputs and passes then as values into helm.

Mozilla | Director of SRE | Full Time | Remote | https://grnh.se/0bb758871us

Mozilla is hiring a Director of Site Reliability Engineering. This is a new position overseeing the team I'm on plus two other teams in a recently-consolidated SRE organization. Come help us make the services behind Firefox and more better! I'm happy to answer any questions I can, just email me at bpitts+whoshiring @ mozilla.com