Informàtica / Computers

• enable 32-bit repositories
• urpmi libfreetype6

• on sda, /boot/grub/menu.lst
  • title mbr_on_second_disk
rootnoverify (hd1)
chainloader (hd1)+1
• on sdb, /boot/grub/menu.lst
  • make sure all entries point to (hd1,...) (bug on Mageia 1)

• repo_a

• mkdir /path/to/your/project
• cd /path/to/your/project
• git init
• without SSH identity
  • git remote add origin git@bitbucket.org:accountname_i/repo_a.git
• echo "My Name" >> contributors.txt
• git add contributors.txt
• git commit -m 'Initial commit with contributors'
• git push -u origin master

• cd /path/to/my/repo
• without SSH identity
  • git remote add origin git@bitbucket.org:accountname_i/repo_a.git
• with SSH identity
  • git remote add origin git@bitbucket-identity1:accountname_i/repo_a.git
• git push -u origin --all # pushes up the repo and its refs for the first time
• git push -u origin --tags # pushes up any tags

• AWS
  • AMIs
    • GitLab Enterprise Edition
    • GitLab Community Edition
      • ssh -i your_private_key.pem ubuntu@x.x.x.x
        • sudo gitlab-ctl status
        • sudo gitlab-ctl reconfigure
  • Manual installation

• Up to 1000 users

• from source
  • git-filter-repo
    • pip install git-filter-repo
• Mageia
  • ...

1. Purge files from repository history
2. (wait 30 minutes)
3. Repository cleanup

• variables:
  MY_FIRST_VAR: "my_first_var_value"

stages:
  - my_test_stage
  - my_build_stage

my_test_1.job:
  stage: my_test_stage
  image: python:3.x....
  before_script:
    - apt-get update && apt-get install make
  script:
    - make test

my_test_2.job:
  stage: my_test_stage
  image:
  before_script:
  script:

my_build_job:
  stage: my_build_stage
  services:
    - ...
  before_script:
  script:

• get an API token from: Profile / API Token

• put the API token from Pivotal into:
  • Project / Settings / Services / PivotalTracker
• commit your changes specifying the story ID:
  • git commit -m "[#story_id] your comments as usual"
  • git push
• check the activity for your stoy in Pivotal

• inotify-cxx

• incron
  • Scheduling jobs based on filesystem activity with incron (linux.com)
  • Pseudo Synchronous Replication to Amazon S3 (s3rep.sh)
  • Simple tools produce powerful results (Rob Searles)
  • Triggering Commands On File/Directory Changes With Incron
  • Which process was responsible for an event signalled by inotify?
  • command line
    • $$ - a dollar sign
    • $@ - the watched filesystem path
    • $# - the event-related file name
    • $% - the event flags (textually)
    • $& - the event flags (numerically)
• inotail - tail replacement using inotify
• inoticoming - trigger actions when files hit an incoming directory
• inotify-tools - command-line programs providing a simple interface to inotify
  • inotifywait
  • inotifywatch
• iwatch - realtime filesystem monitoring program using inotify

• Monitor Linux file system events with inotify

• yq -p json -o yaml toto.json >toto.yaml

• which automake
• which aclocal

• cd ~/src/automake-1.14
• sudo make uninstall
• sudo yum reinstall automake
• which automake
• automake --version # should return 1.13
• which aclocal
• aclocal --version # should return 1.13

• Mageia
  • urpmi intltool
• libosinfo >= 0.2.8
  • Dependencies
    • Mageia
      • urpmi lib64soup-devel lib64xslt-devel lib64check-devel
  • cd libosinfo-0.2.11
  • ./configure; make
  • make install

VERSION=1,0
add_bridge_mapping eth1 -1
add_bridge_mapping eth0 0
[...]

• dd if=/dev/zero of=/var/tmp/bigemptyfile bs=4096k ; rm /var/tmp/bigemptyfile
• telinit 1
mount -o remount,ro /dev/sda1
zerofree -v /dev/sda1

• /home/usuari

• toto

• echo "FROM hello-world:latest" >toto.Dockerfile
docker build -f toto.Dockerfile -t toto .
  • "fatal error: unexpected signal during runtime execution"
  • Solució:
    • actualitzeu-vos a Mageia 9 (docker 20.10.22)
    • instal·leu docker des de binari estàtic

• Install the Compose plugin
• Passos / Steps
  • sudo -i
  • mkdir -p /usr/local/lib/docker/cli-plugins
  • curl -SL https://github.com/docker/compose/releases/download/v2.23.1/docker-compose-linux-x86_64 -o /usr/local/lib/docker/cli-plugins/docker-compose
  • chmod +x /usr/local/lib/docker/cli-plugins/docker-compose
• Test
  • docker compose version
    

• aws ecr get-login-password --region eu-west-1 | docker login --username AWS --password-stdin <id>.dkr.ecr.<region>.amazonaws.com
  
• <id>.dkr.ecr.<region>.amazonaws.com

• si no troba el plugin docker-buildx farà servir el builder antic, que no és BuildKit, encara que es tingui una versió > 23 de docker
• install buildx
  • download bin, as plugin:
    • sudo -i
    • mkdir -p /usr/local/lib/docker/cli-plugins
      
    • cd /usr/local/lib/docker/cli-plugins
    • wget https://github.com/docker/buildx/releases/download/v0.12.1/buildx-v0.12.1.linux-amd64
    • chmod +x buildx-v0.12.1.linux-amd64
    • ln -s buildx-v0.12.1.linux-amd64 docker-buildx
  • Mageia
    • install it from bin
  • Fedora
    • ...
  • ...

• temporary solution:
  • DOCKER_BUILDKIT=1 docker build ...
• permanent solution:
  • /etc/docker/daemon.json
    • {
  "features": {
    "buildkit": true
  }
}
  • sudo systemctl resart docker

• se li passen les configuracions (declaratives, en yaml o json) dels components que es volen crear
  • parts:
    • apiVersion
    • kind:
      • quin tipus de component volem crear
    • metadata:
    • spec:
      • especificacions desitjades
      • són específics de cada kind
    • status:
      • afegit per kubernetes
      • emmagatzemat a etcd
• un fitxer de configuració normalment conté només la informació del component que es vol crear; en el cas d'un kind: Deployment i el seu associat kind: Service, es posen en el mateix fitxer, separats per ---
• a cada component se li pot aplicar una label (key/value)
• se sap que un pod pertany a un deplyomnet perquè al deployment s'especifiquen selector: matchLabels

• AWS Load Balancer Controller

• pod #1
  • container #1
  • container #2
  • ...
• pod #2
  • container #1
  • ...

• my-deployment.yml
  
  • metadata
      name: ...
      namespace: mynamespace