pmoranga

Checking your Raspberry Pi's view of its power supply

Sometimes it seems like the first (and sometimes only) advice you get offered for almost any problem with a Raspberry Pi is "check your power supply". You think something like:

"hey, I'm using an official power supply sold as being matched with my Pi so how can there be any problem?"

You look up the specs then stick a controlled load across your supply and confirm that it can deliver the required number of Watts.

Yet your problems persist…

pmoranga

db.getCollection('Flights').aggregate([
    { $match: {"airport_code" : "AMS"}}
      ,{"$group": {"_id": 
            { $dateToString: {
                date: {"$add": [new Date(0), 
                    {"$multiply": ["$created_at",1000 ]} 
                ] } ,
                format: "%Y-%m"} 
            }
    , "count": {"$sum": 1}}}

pmoranga

#!/bin/sh
# Run as user `ubuntu` from the Ubuntu Desktop installer's live environment.

sudo apt-add-repository universe
sudo apt update
passwd ubuntu
sudo apt install --yes openssh-server screen vim
ip addr show scope global | grep inet

pmoranga

## Example using https://pre-commit.com/
repos:
  - repo: local
    hooks:
    - id: dontship
      name: DONTSHIP check - Block words
      entry: '\bdie\b'
      language: pygrep  # https://pre-commit.com/#pygrep
      types: [php]

pmoranga

apiVersion: apps/v1
kind: Deployment
spec:
  template:
    metadata:
      annotations:
        co.elastic.logs/enabled: "true"
        co.elastic.logs/processors.0.decode_json_fields.fields: message
        co.elastic.logs/processors.0.decode_json_fields.target: ""
        co.elastic.logs/processors.1.dissect.field: request_Authorization

pmoranga

kubectl get nodes -o custom-columns='NAME:.metadata.name,InternalIP:.status.addresses[?(@.type=="InternalIP")].address'

pmoranga

Using ArgoCD together with Kapitan is actually pretty easy and only requires the kapitan binary in the argo-repo-server and a ConfigManagement plugin in ArgocD (https://argoproj.github.io/argo-cd/user-guide/config-management-plugins/)

1. Edit argocd-cm configmap and add :

  configManagementPlugins: |
    - name: kapitan
      init:
        command: [sh]
        args: ["kapitan-base-compile.sh"]

pmoranga

Using ArgoCD together with Kapitan is actually pretty easy and only requires the kapitan binary in the argo-repo-server and a ConfigManagement plugin in ArgocD (https://argoproj.github.io/argo-cd/user-guide/config-management-plugins/)

1. Edit argocd-cm configmap and add :

  configManagementPlugins: |
    - name: kapitan
      init:
        command: [sh]
        args: ["kapitan-base-compile.sh"]

pmoranga

init_config:
  mibs_folder: /mibs
  profiles:
    generic:
      definition_file: _generic-host-resources.yaml

instances:
  - ip_address: $REPLACE_WITH_SYNOLOGY_IP_ADDRESS
    community_string: public
    snmp_version: 2

pmoranga

init_config:
  mibs_folder: /mibs
  profiles:
    generic:
      definition_file: _generic-host-resources.yaml

instances:
  - ip_address: $REPLACE_WITH_SYNOLOGY_IP_ADDRESS
    community_string: public
    snmp_version: 2