Skip to content
Menu
e-lo [IT Engineer life]
  • Home
    • Notes
    • Important notes
  • Database
    • T-SQL
    • SQL Server quick
    • SQL server docs
    • MySql quick sheet
    • Postgre
    • InfluxDB
  • Programming
    • MS Azure Powershell
    • MS Azure Command-Line Interface (CLI) doc
    • Python Docs
    • Python Logging
    • Python-cheat-sheet
    • Git-guide
  • Azure
    • MS Windows virtual machines in Azure
    • MS ARM Docs
    • MS ARM Template Docs
    • MS ARM Functions
    • MS Bicep+ARM
    • MS ARM Tutorial
    • MS Deployment scripts (intern/extern)
    • MS Virtual Network
  • Az-nutshell
    • ms-technology-choices-compute-decision-tree
    • ms-data-store-decision-tree
    • ms-data-explorer
    • ms-storage-explorer
    • ms-azure-sql
    • ms-common-data-services
    • ms-azure-mysql-daas
    • ms-sla
    • az paas
    • az glossary-quicksheet
    • az-test-vm-script-quickguide
  • Linux
    • Top CMD’s
    • Useful CMD Linux
    • ss64 Linux
    • Ubuntu
    • 30 things Ubuntu 18.04
    • Bootable Ubuntu USB
    • LinuxFilesystemTreeOverview
  • Sys Admin
    • System Administrator
    • Sys News
    • Packet Sniffers
  • Zen
    • Not thinking about anything is Zen
e-lo [IT Engineer life]

Important notes

FOCUS:

  • Try to always use Python, Powershell and Github for “things”
    • Most of the code should be focused on Python and Powershell
    • Best practise:
      • quickguides/python at main · spawnmarvel/quickguides · GitHub
    • TODO notes, write them in Python
    • Think automation
  • AZ-104 (VM, network and storage)
  • PaaS
  • RabbitMQ
  • Montitoring automation
  • Embrace the 5 min TODO

NOTE:

Some of the things I have done or not done, spent time on or not spent time, liked or not liked, tested or not tested, used hours on or just minutes on, changed or not changed, started to enjoy or changed my mind about, started and finished or started but not finished, found out or not found out yet, could be stored here.

CODE:

Usually it has been done before and / or there is best practices, the key is to dismantle it and understand its’s pieces.

spawnmarvel (Espen Kl) (github.com)

spawnmarvel/quickguides: quickguides, markdown, nutshell reference (github.com)

#checklistriskmanagement: muda #wastefulness, mura #imbalance, muri #overload

  • What are the top risks, how severe is their impact and how likely are they to occur? THEY WILL HAPPEN.
  • How often do we refresh its assessment of the top risks?
  • Who owns the top risks and is accountable for results, and to whom do they report?
  • Always use LTS version of software, dlls, libs etc (TEST, TEST AND TEST AGAIN)

Set up general
VSC Py, ARM, Ps1
Python
Extensions:
1 Magic Python (MagicStack Inc.), syntax highlighter
2 Python, IntelliSense
3 Azure Resource Manager (ARM) Tools for Visual Studio Code (MS)
Azure Resource Manager (ARM) Tools – Visual Studio Marketplace
4 PowerShell
5 TODO highlights
Tools1 Git Bash: GIT, Curl, SSH (or with Putty), BASH, NANO
2 Azure Cli or Powershell: Install-Module -Name Az
3 Greenshot
4 Np++, Plugin: XML Tools, Compare
5 BareTail
6 NSSM
Tips A space at the end can ruin your day (either strip() | ” ” replace “” np+
pip(3) –version
python –version
import sys
print(sys.version)

Linux (Linux System Admin Command):

https://www.javatpoint.com/linux-system-admin-commands

BASH101

https://devhints.io/bash

https://help.ubuntu.com/community/LinuxFilesystemTreeOverview

ss64

https://ss64.com/convert.html

https://ss64.com/

SSL

https://certlogik.com/decoder/

MS SQL:

https://docs.microsoft.com/en-us/sql/?view=sql-server-ver15

Game or fun:

https://xkcd.com/1335/

https://sudoku.com

VM

Azure “good-to-know” about any VM, with example on SKU:General purpose virtual machine sizes:

https://docs.microsoft.com/en-us/azure/virtual-machines/sizes-general


Ever wondered why?

A factor is considered the root cause of a problem if removing it prevents the problem from recurring. A causal factor, conversely, is one that affects an event’s outcome, but is not the root cause. Although removing a causal factor can benefit an outcome, it does not prevent its recurrence with certainty.
The causal factor isn’t the single factor that drove the event. Instead, a causal factor was one of a few influences. The event could still occur again, or would have happened without the causal factor.

Identify Possible Causes:

This can be done in a brainstorm session. Start with the problem definition and ask “why?” it happened. Keep on asking “why?” repetitively until you have found the root cause.

RSS Azure

  • MLOps Blog Series Part 3: Testing scalability of secure machine learning systems using MLOps June 30, 2022

RSS RabbitMQ

  • RabbitMQ 3.8.15 release

RSS Python

  • PEP 694: Upload 2.0 API for Python Package Repositories June 11, 2022

Tags

5 min (29) Ansible (1) ARM (10) azure (41) cmd (3) Django (4) Docker (1) e-lo (2) Flask (2) Github (9) Grafana (2) Information (7) Information Retrieval (13) JAVA (1) kivy (2) Kotlin (6) linux (15) mobile (2) Natural Language Prossesing (NLP) (2) Net.Core (1) Networking and Security (9) OPC (2) PEP8 (1) Philosophy (3) Python (48) Python Networking and Security (5) Reason (2) RMQ (3) Solr (11) Sql (10) Uncategorized (2) VSC (1) Warframe (2) WMVARE (4) Zabbix (7)

Recent Posts

  • 401 access denied win server (iis), Local Security Policy
  • Callback
  • Share-level permissions IAM Azure AD
  • Packet Sniffers
  • MSA Account

Archives

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

Photo by Markus Spiske from Pexels "Matrix"

©2022 e-lo [IT Engineer life] | Powered by WordPress & Superb Themes