Hacker Newsnew | past | comments | ask | show | jobs | submit | punkrex's commentslogin

The DIY part of the solar market and now most none Tesla options have moved towards Lithium Phosphate batteries, particularly in rack mount format. They're denser and way easier to handle then lead acid.

30kwh of batteries is about $10k wholesale, and inverters run about $1500, although most of the time you need 2 if you want to supply 240v.

Sample system: https://signaturesolar.com/off-grid-eg4-system-13kw-120-240v...


What's being skipped over in a lot of reporting is that Southwest has serious issues maintaining ground staff staffing, and has been struggling with that the entire pandemic because they refuse to pay market rate. This means that planes can't be unloaded and turned around in any reasonable amount of time. I gave up completely on southwest after I was stuck on a plane for 4 hours this summer, because of lack of ground crew to unload the planes, and thus planes were stuck on the tarmac.

Add on to that the latest technology woes, the storm was just the thing that tipped over a company that had cut operational capacity to the bone.


A few days ago they declared a "state of emergency" in a few airports, which they're pretty transparently using to squeeze staff.

I don't see any non-bogus reason to, for example, stop accepting doctor's letters from telehealth visits only in cities where they're particularly short staffed.


This is gonna be hard, I’d honestly look at fly.io.

But argocd hooked up to each provider along with provider specific overrides should work with enough tweaking.


A lot of the “finops” practitioners I’ve seen are myopically focused on tagging of AWS resources; and that falls to pieces with kubernetes because AWS can’t see inside the kubernetes clusters.

I’m not surprised they don’t like it.


I just had a meeting with a 'finops' manager where i showed him how kubernetes has a similar tagging structure (labels) and how we can break down per team pricing based on cpu/memory utilization.

It's not hard, you just need the tools (kubecost, etc)


pod A uses 2 cores, pod B uses 1 core. Machine has 4 cores and all remaining unscheduled pods require 2 cores.

How do you attribute the partial usage of the node? Is it 2 cores billed to pod A, 1 core billed to pod B, and 1 core billed to some random team?

Or do you have 2/3 of Node billed to pod A and 1/3 of Node billed to Pod B.

Now deal with this permutation across all the various variables.


You do it roughly based on the deployment requests and the average HPA values throughout a time slice.

Most k8s workloads run on a homogenous set of node types, so you can have an hourly cost per gb and per vcpu without digging too much into it.


Yup. Particularly because k8s scales based on whole system load, not single app load. It's harder to predict because it's better at optimizing resource utilization and ultimately lowering costs.


You can scale load on many things in more recent versions of K8s. for example, pubsub depth of un-acked messages, or custom metrics in prometheus format.

https://cloud.google.com/kubernetes-engine/docs/tutorials/au...


My FiL works in the industry on large projects, and the word from suppliers is that in Jan, prices should drop 50% from where ever Dec ends up, as there is going to be a ton of supply.


They were repeatedly warned by local groups, international NGOs and the US State Department that the speech was inciting violence. They refused to do anything and it escalated into a pogrom.


Not defending FB here - it looks like they have acknowledged their faults in this issue specifically.

That said, this argument structure sounds a lot like "US leadership was warned about the attacks on Pearl Harbor". It looks like FB under reacted to these warnings, probably because they didn't realize how bad the outcome would be. How can info/escalations be presented so as to break out of the noise? (I'm assuming here that FB also has been warned of a lot of really bad things that never came to pass, which isn't something we can know - but it's an interesting thought experiment.)

What is the expectation in terms of separate the signal from the noise? How can the critical factors be identified ahead of time? Was it foreseeable that the targeted hate speech would turn into violence? What level of reaction is appropriate, given the uncertainty of hate speech -> violence?

Apologies for the brain dump - not expecting answers to all of them. And not defending FB here. I just think these types of questions are very interesting (plus I just read Superforecasters, which examines similar decision making w/r/t the decision to kill bin Laden).


While it's not exactly the same as ITAR, NZ already allows citizens of five eye countries to get security clearances without any ties to NZ.

So I would imagine that from NZs perspective it wouldn't be a big deal to let foreigners work on export controlled projects.


Honestly to explain the nuance of the situation would take too long and isn't super easy to reduce to right and wrong. The background required to understand how syria came to be is not something that can be sufficiently and succinctly explained in a comment thread.

Attempts to simplify it run into the exact issues you've noticed above. You're bias comes into play which conflicts with various other peoples PoV, and it all devolves into a shouting match.

Also the pipeline/Syke-Picot people will interject themselves into any conversation about the middle east because "this one simple event explains everything" is appealing to a ton of folks.


> Also the pipeline/Syke-Picot people will interject themselves into any conversation about the middle east because "this one simple event explains everything" is appealing to a ton of folks.

Do the "Sykes-Picot people" attribute everything to that agreement or just view it as a logical starting point for many of the current political problems seen in the Middle East that can not be attributed to other factors (geography, sectarian conflict, control of natural resources, migrant populations that defy modern borders, a history of historical conflicts/slavery, and/or pressure from environmental, political, and cultural changes)?

Sykes-Picot isn't exactly a fringe internet theory.... any textbook on the modern Middle East is going to devote substantial time to it.


I dislike it personally because it robs any agency on the part of the locals and ascribes everything happening because of Westerners. I think the simplistic view presented in textbooks is wrong. Sykes-Picot never really came into effect and as much as the British/French tried to control the area their attempts at control were co-opted by savvy local nationalist parties to establish local nation states after the collapse of the Ottoman empire.

The map of the modern day middle east has more in common with Ottoman Provinces then it does with the Lines of Control that Sykes-Picot proposed. Now I am not trying to absolve the west of all it's guilt, it did a number of shitty and horrific things, but I think the narrative that the West screwed up the Middle East ignores both a significant history of conflict in the area over land and resources, as well as the political situation on the ground being influenced more by locals then outsiders. I am also not saying that colonialism is not a horrific thing, I think that efforts elsewhere(Africa, Asia) started earlier and were more heavy handed.

The reason why Sykes-Picot appeals to so many people is that it provides a simplistic political narrative for why the region is so messed up, and allows blame to be shifted on a politically convenient scapegoat. Hopefully as we shift away from the "Great Man"(and I think Westerners trying to impose their will on the Middle East were bad folks) theory of history we will come to view these simple theories as useless and try to understand the nuance of how the modern Middle East came to be as not something that two Westerners in 1917 could ever hope to dictate.


Fair enough - as you indicate, nuance is important and sadly it's often lacking from many media articles and debate these days.


Location: Baltimore

Remote: Heavily Prefer

Willing to relocate: Theoretically in short term but leaning towards no, but was already looking to move in year

Technologies: Mesos(including overlay networks and persistent data), AWS, Containers, General Linux, Ansible, MongoDB

Résumé/CV: https://www.linkedin.com/in/andrew-lewis-95799610/

Email: me (at] andrewlew.is

Looking for a Devops/SRE role. Currently doing all things Mesos(including running MongoDB in mesos), with some exposure to kubernetes. Looking primarily for a remote position, but onsite isn't out of the question. Also have experience with networking, VPNs and a bunch of other stuff.


Yo, is your DNS server down? I get no responses for either the US or EU endpoints when I try to query for A records.


Sorry, I should update it. All of those public endpoints went down a long time ago. People were donating the endpoint machines and they eventually just disappeared.

You'll have to set your own up on a server somewhere.


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

Search: