Worked at a web property that took scrum, used it and found it lacking in certain cases for development. They Extend it And called the new creation beyond scrum, abbreviated as BS snickers.
Unrelated to the shortcomings
we found that Scrumm with the timeboxing concept did not work for infrastructure teams.
You cannot just time box most Infrastructure task and just ship whatever you have when you exceeded your initially planned timeframe.
We came up with Kanban as a way to document progress. The swimming lanes together with a limit on things that can be simultaneously in flight served to mirror reality as an operational team much better than pure Scrum.
Southwest Airlines Flight 1380 was a Boeing 737-700 that experienced an uncontained engine failure[a] in the left CFM56-7B engine after departing from New York–LaGuardia Airport en route to Dallas Love Field on April 17, 2018. […] One passenger was partially ejected from the aircraft and sustained fatal injuries[…]
If the person on the phone had said “Capone, Al” instead of “Uh…” he’d possibly not gone to jail.
Even ill gotten gains are taxable and the theory of one crime at a time suggests that even “other, unspecified” could be with paying taxes on to reduce the likelyhood of successful criminal persecution.
There are reasons for tools like https://github.com/ixs/kvm-cli. It seems like every operations team built their own version that logs into the web interfaces, downloads the java stuff and then runs it locally...
I was just fiddling around with a SuperMicro X8 IPMI the other day. The X8 IPMI stuff is terrible, e.g. the warning that your Java installation is outdated on opening the website etc.
Turns out, you can actually install X9 IPMI firmware on X8 boards as the platform files are still shipped.
Might be worth checking out, if this improves things for you. It did for me.
Check out https://github.com/devicenull/ipmi_firmware_tools for unpacking (and repacking) the SuperMicro firmware. The developer just merged my patches making it work with some of the X8 boards.
As long as your board is listed in /etc/defaults of the IPMI tree you should be good.
The distance from Paris to Berlin is longer than Berlin to Lviv in Ukraine. Something that is often forgotten it seems.
The European Union has legitimate territorial security interests and a expansionist empire right next door that is encroaching on your borders isn't something the EU leadership likes to have around.
Considering that I doubt passively waiting for Ukraine to fall was never on the menu. Instead I expect the military and financial help for Ukraine to further increase as it is way cheaper to finance someone else to fight the empire next door than having to beef up your own border security.
There are certainly enough useful idiots around that are clamoring for cheap gas at any price but I do not have the impression that they get a lot of traction.
I saw some numbers the other day that 70% of the German population agrees that supporting Ukraine is important, even if it means higher energy prices/colder times in winter. Only the voters of the far right party AfD thought it a sensible policy to drop Ukraine. Not surprising really for Moscow's fifth column.
I previously used MiniKeepass which has been shut down.
My grated to KyPass, which looks good on paper but syncing with Google Drive didn’t work in practice.
Now using KeePassium Pro. Very happy. Does everything I need, uses the file API for opening files and integrates well.
Much wider hardware support with OpenWRT. If the hardware is accessible and supports Linux, there is an OpenWRT target for it.
There’s even a x86 and a raspberry target.
If you’re happy with DD-WRT, no pressing need to change it.
But if you want more features or specific packages, OpenWRT is the thing to look at.
What I find so baffling is that these experiences do not match my own atall.
I've been running a non-profit ISP for about 23 years with a few friends. We've always been doing this from our own IP Space (/20) in RIPE.
Even when we had problems sending spam (compromised user accounts, compromised php websites) and we ended up on a blacklist, we usually could get removed pretty fast.
For a few years our mail system would sometimes generate late-bounces, that is accept a mail on the incoming MX only to then figure out that it actually cannot be delivered later on and generate a delivery failure notification mail.
Not a good situation.
That got us into some trouble here and there. But even that could easily be unblocked again.
When we finally managed to set up a new mail infrastructure (2 year project cause it's a hobby) we set up new outgoing SMTP servers which cycle through multiple IP addresses. There was exactly one ISP (Deutsche Telekom T-Online) that was not accepting mail from some of these IPs. One mail and a turnaround time of abour 12hrs later this was fixed.
Gmail or Hotmail/live.com/Outlook never had any problems with deliverability. Even with a few users forwarding all their email to their gmail accounts including the spam that slips through our filters.
That might mean that a single mail would not be deliverd, but other users never suffered as our outgoing IPs are not being blanket-banned.
There's one residential ADSL provider that has a blanket ban on one of our outgoing IPs. There's no way to get that resolved because their mail infrastructure is unmaintained and nobody is reading their mail. Common problem with that one ADSL provider, googling their name shows other people have the same problem. shrug We just use a different outgoing IP for them.
No DMARK or DKIM setup at all for outgoing mail.
So I wonder, what really makes the difference in experience? Is it just the fact that we have a decent sized IPv4 Network in our name as PI space?
I appreciate the nuanced view. Let me add a bit of color though and point out where the "rumors" are wrong.
Subscription management of RHEL has always been an issue. There were ample ways of getting an evaluation set up or a free developer subscription but the backend work needed to get these done seemed insanely complex. I remember at some point hearing that for every free eval subscription an actual "sale" was recorded in the backend ERP (SAP?) system at Red Hat. That made quick drive-by downloads not feasible.
The developer subscription was a bit of a "hack" to extend and required you to go to an incognito window without cookies, authenticate to the developer portal which would then drop in the dev subscription into your Red Hat account. This was documented in https://developers.redhat.com/articles/faqs-no-cost-red-hat-... point 14.
I cannot fathom what backend juggling necessitated this workflow.
For larger companies, managing subscription/entitlement keys was sometimes a hassle. I've heard of a handful of companies that paid for commercial RHEL subscriptions but most of the time just installed CentOS in prod as it was less of a hassle. There interesting thing here was that number of paid but unused RHEL subscriptions stayed mostly aligned with the number of machines in use.
Other companies had RHEL in prod but CentOS in non-prod policies simply because it enabled quicker turnarounds and deployments.
The rumor that CentOS was on the brink of ending is something I find _very_ hard to believe. The CentOS project was a small group of people which - to the best of my knowledge - were all gainfully employed in the Linux/Admin space or sucessfully self employed as consultants and did the CentOS work in their free time as a hobby. For the consultants the CentOS connection might even have been a door opener.
Bandwidth and hardware for mirrors, buildservers and webservers etc. were exclusively donations, as is very common for these projects.
Even with a minimum of financial contributions or not even any at all, keeping such a project alive isn't difficult. After all, nobody is depending on the money for their livelyhoods and it's a hobby after all.
In the past there were times where drama hit CentOS-land. In 2009 LWN reported on the CentOS project founder disappearing a while ago and donations not reaching the project: https://lwn.net/Articles/345028/. That article seems to support my impression that financial contributions are not really relevant to the success of a project suhc as CentOS.
The issues with CentOS seemed more around life happening to people in control and then the project suffering: https://lwn.net/Articles/460791/ is an article from 2011 about package builds and pushes happening with delays.
These issues however seemed to have been resolved some time later and delays seemed to be much less common. Interesting point: That article was contributed to LWN by the same author as the original post.
Now, considering these data points I wouldn't put a lot of faith into any rumors that CentOS was going to collapse and Red Hat came riding in to safe the day. I'd say it is much more likely that Red Hat had decided that RHEL was too restricted and fedora way to "fast and loose" to build an enterprise developer community around. Instead it might be a good idea to grab the CentOS and turn that into the development basis for ISVs, 3rd party commercial vendors and other open source projects.
The Xen 4 CentOS project was a great example for this. Taking into account that a lot of these projects and special interest groups were announced shortly after the acquisition, I'd say this view isn't far from the truth.
At the end of the day, the moaning about a free alternative going away is kinda ridiculous I think. I know large users of CentOS (hundreds of thousands of machines) that had a look at CentOS stream, did talk a little bit about it amongst their different departments and decided that Stream is fine for them. If it is fine for these kind of shops, it can't be that bad.
Having your fascist enforcers “monitor” the election, helping elderly people to the voting booths and “helping” them to vote correctly all seem to be indicators that the election is fishy.
And even then, the fascist party didn’t even get a majority…
Based on the comments here I did a quick look at Amazon and was surprised to not even see a single vacuum only robot from Evovacs. At least not prominently showcased.
Why are there only mixed models and what are the benefits?
If I look at my place the ground floor is tiled and the top floor is all carpet.
That means I would need two vacuums anyway as they haven’t learned yet to climb stairs.
Why wouldn’t I want a vacuum only model for upstairs?
For downstairs the universal model is great obviously. But upstairs?
Unrelated to the shortcomings we found that Scrumm with the timeboxing concept did not work for infrastructure teams. You cannot just time box most Infrastructure task and just ship whatever you have when you exceeded your initially planned timeframe.
We came up with Kanban as a way to document progress. The swimming lanes together with a limit on things that can be simultaneously in flight served to mirror reality as an operational team much better than pure Scrum.