The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

    Mastodon

  • Twitter Updates

  • My Flickr Stream

    20140508-Delphi-2007--Project-Options--Cannot-Edit-Application-Title-HelpFile-Icon-Theming20140430-Fiddler-Filter-Actions-Button-Run-Filterset-now20140424-VMware-Fusion-6.0.3.-no-reclaimable
    More Photos

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,854 other subscribers

Archive for the ‘Infrastructure’ Category

« Previous Entries
Next Entries »

Sometimes clouds vaporise: the Docker Cloud shuts down in ~8 weeks.

Posted by jpluimers on 2018/03/26

From [WayBack] Docker – Docker Cloud Migration Notification and FAQs:

The services on Docker Cloud that provide application, node, and swarm cluster management will be shutting down on May 21.

…

If you do not migrate by May 21, your applications running on the Docker node cluster management service will cease to operate.

Swarms will continue to function; however, if you do not retrieve your SSH keys for the Swarms being managed by our swarm cluster management service, you will be unable to access your swarms using your Docker ID. For instructions on how to retrieve and access your Swarms with SSH keys, please refer to the Docker docs.

So soon, no more [WayBack] Docker Cloud – Build, Ship and Run any App, Anywhere.

Remember: still the cloud is other peoples computers, so be sure you can move when needed.

–jeroen

Posted in Cloud, Cloud Development, Containers, Development, Docker, Infrastructure, Power User | Leave a Comment »

EmbarcaderoMonitoring – monitoring the Embarcadero internet related services

Posted by jpluimers on 2018/03/15

Over time, there are lots of complaints about Embarcadero related internet services (like forums, QC, Appanalytics, docwiki, blogs, web site, maintenance, …) so to track uptime, I’ve created a set of EmbarcaderoMonitoring pages:

This is preliminary work based on my own lists of Embarcadero endpoints combined with some research like [WayBack] dnsdumpster embarcadero.com.png and [WayBack] IdentIPSpy

Underneath, they run on the uptimerobot.com infrastructure which has a limit of 50 free monitors.

It means I have to:

  • trim this down for relevancy
  • better document the endpoint
  • find correct endpoint targets for the black (disabled) and red (down) entries as a few of them might need tweaking
  • maybe split off an insecure and secure version (now most subdomains have both http and https monitored)

Any ideas on improving this are welcome: please post a comment here on on the resulting G+ thread.

Note it likely won’t show cases like when the website was hacked or TLS certificate issues like in SSLLabs security reports for some embarcadero subdomains. I need to think about a means for those, as it will certainly help monitoring my own infrastructure in a similar way.

–jeroen

Read the rest of this entry »

Posted in *nix, Cloud, Development, DevOps, Infrastructure, Monitoring, Power User, Software Development, Uptimerobot | Leave a Comment »

Scott Hanselman on Witter: “Why should I care about Kubernetes, Docker, and Container Orchestration?”

Posted by jpluimers on 2018/02/08

An important question for many people, so if you want to know more or get started: [WayBack] Scott Hanselman on Twitter: “Why should I care about Kubernetes, Docker, and Container Orchestration?” followed by:

Yes, AKS is Azure Container Services (go figure!).

Notes

  • For burning, Scott recommends [WayBack] Etcher: Burn images to SD cards & USB drives, safely and easily (which is now also available as experimental [WayBack] Etcher CLI), I tended to use a script like below since I’m a command-line person, but since Etcher does write and verify in one run, I’m considering switching:
    1. find where the SD card is mounted on your Mac: diskutil list
    2. sudo su -
    3. execute this from the directory where you downloaded filling in targetDevice with the value from diskutil list

    targetDevice="disk9"
    imageName="2017-11-29-raspbian-stretch-lite"
    unzip -o ${imageName}.zip
    diskutil umount "/dev/${targetDevice}s1"; \
    dd bs=1m of="/dev/r${targetDevice}" if=${imageName}; \
    sync; \
    diskutil list; \
    diskutil eject "/dev/${targetDevice}"

–jeroen

Posted in Cloud, Containers, Docker, Infrastructure, Kubernetes (k8n), Power User | Leave a Comment »

Happy “check your backups day”; does your restore process work? And how is the rest of your admin process doing?

Posted by jpluimers on 2018/02/01

Today is [WayBack] Check your backups Day! started by @CyberShambles in dedication of the @Gitlab outage on 20170201.

Please check your restoration process now. As people screw up and accidents happen (I know first hand from a client).

Why isn’t this date on January 31st? Long short story: the failure started that date, but restoration took most of 20170201. So February 1st it is.

Others will follow and GitLab wasn’t alone, as a few days before soup.io had to restore a 2015 database backup.

It all comes back to

Nobody wants backup.

Everybody wants restore.

which made it to the 2008 [WayBack] adminzen.org – The Admin Zen and has been attributed to various people including [WayBack] to Kristian Köhntopp and [WayBack] to Martin Seeger who told Kristian Köhntopp that it was coined by Sun’s Michael Nagorsnik at one of the early [WayBack] NuBIT. Martin was there; he knows (:

The oldest mention of the phrase I could find was in 2006 by Volker Bir at [WayBack] Spy Sheriff – so how do people get infected w/ this thing?.

Keeping clients in the loop

Since soup.io hosts their updates blog on their own platform, the restore resulted in the post prior to [Archive.is] Update after crash ;) – Soup Updates sort of ironically being the mid-2015 [WayBack] Give us your money! – Soup Updates. Usually dogfooding is a good thing though.

During such a downtime, it is crucial to stay in touch through alternative channels. Soup.io didn’t do a good job on their twitter account: they only announced the “update after crash”, not being down, why or progress.

They also deny the WayBack machine access to updates.soup.io because of [WayBack] robots.txt because how they redirect through /remotes, but luckily Archive.is doesn’t care about that and has less old updates.soup.io archived as recent as end of 2015.

GitLab did a much better job on their GitLabStatus account.

Postmortems and organisation culture.

Everybody can screw up, and usually a severe outage happens even when everybody tries to do the right thing. The only way to learn from it is to have [WayBack] Blameless PostMortems and a Just Culture – Code as Craft.

Read the rest of this entry »

Posted in DevOps, Power User | Leave a Comment »

What happens when a huge number of people share a single grocery store loyalty card? – The Old New Thing

Posted by jpluimers on 2018/01/12

[WayBack] What happens when a huge number of people share a single grocery store loyalty card? – The Old New Thing

An interesting discussion in the comments besides this interesting article observation:

What messes up their data analysis is when two people with different lifestyles swap cards. The system sees that somebody who used to buy yogurt and bulk brewer’s yeast is now buying potato chips and frozen pizzas, and it can’t figure out what is going on.

–jeroen

Posted in Cloud, Development, Fun, Infrastructure, LifeHacker, Software Development, The Old New Thing, Windows Development | Leave a Comment »

jessie frazelle on Twitter: “Hire the people who will automate themselves out of a job, then just keep giving them jobs.”

Posted by jpluimers on 2017/12/31

This is what DevOps is all about: [WayBack] jessie frazelle on Twitter: “Hire the people who will automate themselves out of a job, then just keep giving them jobs.”

I had seen the tweet before, but forgot to save it. Jonas Bandi reminded me of it at [WayBack] Weekend Reader: End of Year Edition – reality-loop.

Jessie is doing great work. For instance, she developed and published contained.af, and nobody captured the flag yet: [WayBack] jessie frazelle on Twitter: «A year ago I made contained.af and it’s launched over 128,000 containers & no one has retrieved the flag».

The game runs in a container, gives you console access and has a bunch of questions. Still need to dig deeper in it, as it is a fascinating set-up. If you like to try it:

Wishing you a year where nobody captures your flags (:

–jeroen

via [WayBack] I just published my “Weekend Reader: End of Year Edition” – Jonas Bandi – Google+

Read the rest of this entry »

Posted in Agile, Cloud, Containers, Development, DevOps, Docker, Infrastructure, Kubernetes (k8n), LifeHacker, Power User, Software Development | Leave a Comment »

Time to Grow Up: Counterproductive Security Behaviors That Must End // Speaker Deck

Posted by jpluimers on 2017/12/29

Good end-of-year re-reading (hopefully there is a video link by now) by Chris Eng (@chriseng) [WayBack] Time to Grow Up: Counterproductive Security Behaviors That Must End // Speaker Deck

via: [WayBack] Thats a decent keynote – G+ Kristian Köhntopp.

Read the rest of this entry »

Posted in Development, Infrastructure, Security, Software Development | Leave a Comment »

On the Docker-Kubernetes announcement: if Kubernetes does so much, do you still use Docker?

Posted by jpluimers on 2017/12/03

Must read: [WayBack] Some Thoughts on the Docker-Kubernetes Announcement – Scott’s Weblog – The weblog of an IT pro specializing in cloud computing, virtualization, and networking, all with an open source view

Via a thread with great comments: [WayBack] Two weeks ago, Scott Lowe mused about the Docker-Kubernetes announcement. https://blog.scottlowe.org/2017/10/17/some-thoughts-on-docker-kubernetes-anno… – Kristian Köhntopp – Google+

–jeroen

Posted in Cloud, Containers, Docker, Infrastructure, Kubernetes (k8n) | Leave a Comment »

iptables debugging « \1

Posted by jpluimers on 2017/11/28

Using the TRACE target: [WayBack] iptables debugging « \1 via [WayBack] iptables Debugging using the TRACE chain – Kristian Köhntopp – Google+

Docs:

TRACE
This target marks packes so that the kernel will log every rule which match the packets as those traverse the tables, chains,
rules. (The ipt_LOG or ip6t_LOG module is required for the logging.) The packets are logged with the string prefix: “TRACE:
tablename:chainname:type:rulenum ” where type can be “rule” for plain rule, “return” for implicit rule at the end of a user
defined chain and “policy” for the policy of the built in chains.
It can only be used in the raw table.

Way more details in the linked article.

–jeroen

Posted in *nix, *nix-tools, Firewall, Infrastructure, iptables, Power User | Leave a Comment »

Microsoft live/passport account Security settings URL

Posted by jpluimers on 2017/11/13

For my link archive:

Microsoft live/passport account Security settings are at https://account.live.com/proofs/Manage

–jeroen

Posted in Cloud, Infrastructure, Microsoft Live, Power User | Leave a Comment »

« Previous Entries
Next Entries »