Friday Feedback

DC Clean Up

X has been melting down over the federal government using the Constitution to take control of local law enforcement in D.C.

Wolf Blitzer stepped in it by posting a picture of a HUMVEE at Union Station. He implied it was an affront.

He got ratioed badly. There were many personal comments about how people were feeling safe to be outside at night. One woman talked about how this was the first time in years she’d been able to walk through Union Station without being verbally and sometimes physically harassed.

Another reporter visited a homeless encampment, expecting the standard anti-Trump screeching. Instead, they were told how much better it was now that the criminal element, drug users, and those in need of mental help are gone. One homeless person’s statement was to the effect, “It is the first good sleep I’ve had in months.”

Pushing Back

I do remember Ronald Reagan as our President. He was one of the most skillful orators I’ve had the pleasure to listen to. He was quick-witted and used that skill to zing the media. He did it so well that most of the media laughed at themselves for being zinged.

Trump is not as articulate. He speaks at a 6th grade level, if I recall correctly. I don’t like listening to him speak. What he does is connect with The People.

What is a greater strength is his ability to troll the media and Democrats. He trolls, whereas Reagan cast zingers.

What is most noticeable is just how hard he pushes back on the media and narrative.

What is the massive win, in my opinion, is that his administration uses the same method of pushing back. They don’t get upset with the lies and narratives; they just call it out. And many times make fun of those who have idiotic stances.

According to Reddit, I Live in a Racist State

I don’t engage on Reddit. I have more than enough on my plate as it is. Today’s joy was an “ICE” warning. The top comments all misrepresented facts. “Immigrants,” “neighbors,” “friends” were used to describe the criminal aliens that ICE was looking for.

The kicker for me: “My daily reminder of just how racist this state is.” I live in New Hampshire. There are blacks in this state. There are people of color in the state. The blacks seem to gather in the cities, as per normal. But I can’t find racists anywhere except within the black community.

But they have defined “racist” to mean anybody who doesn’t accept every third world alien that comes into our country.

For them, it is racist that people are upset about the Indian who killed a family of three by making an illegal U-turn. The Florida cops administered a simple test: English proficiency and road signs. He got 2 out of 12 right on the English portion and 1 or none of the road signs.

This monster with a CDL from California killed a family of three, and I’m racist for being upset that he entered my country illegally and was given, given, not earned, a CDL.

OpenStack

I like doing things the old-fashioned way. I like knowing what the hell is going on inside my network. Having software magically do things bothers me.

Unfortunately, none of the documentation for Open Virtual Network (OVN) talks about manually configuring OVN. It all uses OpenStack. In addition, I’ve become unhappy with my Docker Swarm solution. Since I’m not hosting anything locally anymore, it is time to “upgrade” to OpenStack.

What the heck will I break? I’ll know next week.

AI Code Generation

I’ve started using Grok for code generation. There are issues, but I’m working through it.

First, Grok is not a programmer. It is a piece of software that does a particular task. You have to spend the time to define the task.

In this particular case, I’m interested in creating network maps in a cleaner way. Grok gave me that starting point.

No matter how smart it appears, it is stupid. My latest example is that there is an input field for interfaces. There is a example prompt, provided by Grok.

That example prompt leaves out an entire part of the syntax using a different set of symbols.

This reminds me of the discussion about secretaries back when word processors became a thing.

The director of the lab and the directors of the lab divisions all had secretaries. The secretaries did most of the writing. They typed out letters to be sent by snail mail, and they often wrote the email sent over their boss’s signature.

When word processors came out, the directors were expected to write their correspondence. The result was substandard grammar and English. Not because these guys were dumb, but because their skillset didn’t include touch typing at 80 WPM and all the rest that a secretary brings to the mix.

Can the average person use AI to write programs? Maybe. In a year, yes.

Will it be good? No.

Just like we went from having electrical engineering to computer science to information technology, I expect to see classes in creating AI prompts showing up in colleges in the next couple of years.

Until AI makes the next leap, it will take real programmers, coders, and systems people to create fully functional software.

On the plus side, Grok has shown me several patterns that I’m copying.

What Happens When You Use 78% of Your 100 TB of storage?

Alarms start going off. I had a Ceph node die on me. I have the parts to replace it. I haven’t had the time nor incentives to do so.

The nice part was that I was able to physically move most of the drives to different nodes. This led to the great rebalancing.

Ceph uses a layout called a “CRUSH tree” or “CRUSH map.” The idea is to define a set of rules for how data blocks should be distributed to different drives (OSDs).

Ceph provides resilience with two methods: one is via redundancy, and the other is by error codes.

Using redundancy, you specify how many copies of each block of data you want. Three is the smallest safe number. This means that every byte written is duplicated twice. When you retrieve the block, it is pulled from the “closest” node.

A redundancy of 3 means three copies. With error codes, the cost is better. Something closer to 1.6 instead of 3 at the expense of more work calculating the error codes.

If you had all 3 copies of the block on the same drive, if that drive (OSD) fails, you’ve lost that block of data. The CRUSH map tells Ceph how to protect duplicate blocks from single points of failure.

In the simplist configuration, you do OSD isolation. No two copies of the same block are ever stored on the same OSD.

You can expand this to the node/host. You can make the same rule that no one host can hold two copies of the same block.

My CRUSH configuration is attempting data closet isolation. No two copies of the same block can exist in the same data closet.

If I had moved the physical drives to a host in the same data closet, then some rebalancing would happen. I moved the drives to hosts in different closets.

Ceph then proceeded to rebalance 70 TB. Which is why networks had to be reworked. I managed to eliminate most of the bottlenecks.

Unfortunately, it also meant that I had OSDs and Placement Groups go “near full,” slowing down the rebalancing. More drives to the rescue.

Question of the week?

For years, if a Democrat or leftist started yapping about this or that, regurgitating CNN talking points, I kept my mouth shut and just moved on.

Except if it was gun-related, then I spoke up.

Today, I’m much more likely to speak up. To attempt to bring facts and logic to the discussion. I no longer sit silently for their lies.

Do you feel it is safer to speak up about your political stance today?