SysAdmin and DevOps

How to enable syntax highlighting for YAML files in Nano

Fri, 14 Feb 2020 14:00:43 +0000

Description

Nano is a simple terminal-based text editor. Though not as powerful as Emacs or Vim, it is easy to learn and use. A lot of developers prefer this editor as it’s very simple to use and pretty useful when you only want to edit a single file quickly on your server.

One of those files that you need to change often in this kind of editor are configuration file, like yaml files. Nano offers syntax highlighting for many file types, however not for yaml files. If you want to highlight this kind of files as well, you will need to follow an extra step.

1 List available Nano Syntax Highlight Files

 [root@ansible]:[~]# ls /usr/share/nano/
asm.nanorc       changelog.nanorc  css.nanorc      elisp.nanorc    go.nanorc     html.nanorc        json.nanorc      man.nanorc   nanohelp.nanorc  objc.nanorc   perl.nanorc  postgresql.nanorc  ruby.nanorc  spec.nanorc     tex.nanorc
autoconf.nanorc  cmake.nanorc      debian.nanorc   fortran.nanorc  groff.nanorc  java.nanorc        lua.nanorc       mgp.nanorc   nanorc.nanorc    ocaml.nanorc  php.nanorc   pov.nanorc         rust.nanorc  tcl.nanorc      xml.nanorc
awk.nanorc       c.nanorc          default.nanorc  gentoo.nanorc   guile.nanorc  javascript.nanorc  makefile.nanorc  mutt.nanorc  nftables.nanorc  patch.nanorc  po.nanorc    python.nanorc      sh.nanorc    texinfo.nanorc  
[root@ansible]:[~]#

2 Create YAML Nano Syntax Highlighting File In order to provide syntax highlighting to your file, if the default file doesn’t exist, you need to create the syntax highlighting file for this language. This file is the yaml.nanorc file and you need to create it in the mentioned directory. Run nano to create the file:

nano /usr/share/nano/yaml.nanorc

and paste the following content:

# Supports `YAML` files
syntax "YAML" "\.ya?ml$"
header "^(---|===)" "%YAML"

## Keys
color magenta "^\s*[\$A-Za-z0-9_-]+\:"
color brightmagenta "^\s*@[\$A-Za-z0-9_-]+\:"

## Values
color white ":\s.+$"
## Booleans
icolor brightcyan " (y|yes|n|no|true|false|on|off)$"
## Numbers
color brightred " [[:digit:]]+(\.[[:digit:]]+)?"
## Arrays
color red "\[" "\]" ":\s+[|>]" "^\s*- "
## Reserved
color green "(^| )!!(binary|bool|float|int|map|null|omap|seq|set|str) "

## Comments
color brightwhite "#.*$"

## Errors
color ,red ":\w.+$"
color ,red ":'.+$"
color ,red ":".+$"
color ,red "\s+$"

## Non closed quote
color ,red "['\"][^['\"]]*$"

## Closed quotes
color yellow "['\"].*['\"]"

## Equal sign
color brightgreen ":( |$)"

Visit the official repository of Nano Highlight , a spiffy collection of nano syntax highlighting files for more information and languages available for nano. This file will be automatically added into nano and will highlight yaml files. Save changes and proceed with the last step.

3 Create Test Yaml File to see results As final step, you need to test wheter the highlight works or not. Proceed to create a test file with nano and write some YAML on it, for example:

- hosts: updates
  gather_facts: False
  tasks:
    - name: Check Dist Version
      shell: cat /etc/os-release
      register: response

    - debug: msg=''

Save the file, edit it again and you will now see the YAML code highlighted.

Watch your Ansible deployments in Grafana!

Fri, 14 Feb 2020 14:00:43 +0000

Description

От интерес търсих начин как да мониторирам използването на ansible, и попаднах на това поразрових се и намерих страхотно поне за мен решемние.

Създаваме директория с име “callback_plugins” за предпочитане в самата директория на ansible скриптовете

 cd <your_playbook_dir>
 mkdir callback_plugins

И изтегляме този плъгин.

cd /callback_plugins
wget https://raw.githubusercontent.com/ansible-collections/grafana/master/plugins/callback/grafana_annotations.py

разрешаваме на ansible да изпозлва този плъгин чрез ansible.cfg.

[...]
callback_whitelist = grafana_annotations

След като конфигурацията е готова ще трябва да зададем няколко параметъра за връзка

$ export GRAFANA_SERVER=<your_grafana_server_address>
$ export GRAFANA_PORT=<your_grafana_server_port>
$ export GRAFANA_SECURE=0                           # 0 for HTTP, 1 for HTTPS
$ export GRAFANA_API_TOKEN=<your_grafana_api_token>

За да си генерираме тоукън трябва да изпълним няколко стъпки:

curl -XPOST <your_grafana_server_address>:<your_grafana_server_port>/api/auth/keys --user "admin:admin --data '{"name": "ansible-callback", "role": "Editor"}' -H "Content-Type: application/json"

Може да заложите конфигурацията директно в ansible.cfg файла:

grafana_url = "<your_grafana_server_address>:<your_grafana_server_port>/api/annotations"
validate_grafana_certs = 1
http_agent = 'Ansible (grafana_annotations callback)'
grafana_user = <grafana user>
grafana_password = <paasword>

Създаваме си нов панел в графан (Create a dashboard), от настройките избираме подменюто “annotations”

Аз лично съм си направим таг за всеки ansible-playbook в разлизен цвят за да си ги следя по-лесно визуално

Enable PSK Encryption for Zabbix Agent on Linux

Wed, 04 Dec 2019 12:37:43 +0000

Description

By default, agent communication is done in clear text. For encryption we have an option to use PSK-based encryption. PSK means pre shared key. The PSK option consists of two important values, the PSK identity and the PSK Secret. The secret should be minimum a 128-bit (16-byte PSK, entered as 32 hexadecimal digits) up to 2048-bit (256-byte PSK, entered as 512 hexadecimal digits)

You can generate a 256 bit PSK secret with openssl using the command:

openssl rand -hex 32

I will save it directly to the zabbix directory

cd /etc/zabbix

I then run,

openssl rand -hex 32 > secret.psk

I also make sure that only the Zabbix user can read the file.

chown zabbix:zabbix secret.psk && chmod 640 secret.psk

I then edit the Zabbix agent configuration file.

nano /etc/zabbix/zabbix_agentd.conf

and change the options near the bottom,

TLSConnect=psk
TLSAccept=psk
TLSPSKFile=secret.psk
TLSPSKIdentity=[my secret pass]

I then restart the agent

service zabbix-agent restart

The configuration of the zabbix server is as follows

Configuration > Host > we choose the host for which to put psk and we click on it > Encryption > I select the :

‘Connections to host’ = PSK

‘Connections from host’ = PSK

‘PSK Identity’ = [what ever you used in the Zabbix agent config]

‘PSK’ = [the long hex string generated from the OpenSSL command above]

After a minute or two, the Zabbix Server and Agent will successfully communicate using PSK encryption.

Инсталация на Command-line interface for Hetzner Cloud

Mon, 04 Nov 2019 14:20:43 +0000

Създаваме API Token

За целта е необходимо да посетим следният сайт Hetzner
Създаваме/Избираме проект
Отиваме на Access > API tokens и големият червен бутон GENERATE API TOKEN
Слагаме описание и копираме тоукъна

Инсталация на hcloud: Command-line interface for Hetzner Cloud

1) За MacOS и Linux или разбира може да свалим сорса от Github.

$ brew install hcloud
Updating Homebrew...
==> Auto-updated Homebrew!
Updated 2 taps (homebrew/core and homebrew/cask).
==> New Formulae
manticoresearch
==> Updated Formulae
git ✔          ack            cmake          dcmtk          deark          gmt            harfbuzz       hydra          jsvc           libssh         offlineimap    php-cs-fixer   qt             siril          sourcedocs     tile38         ucloud         yafc

==> Downloading https://homebrew.bintray.com/bottles/hcloud-1.13.0.catalina.bottle.tar.gz
==> Downloading from https://akamai.bintray.com/45/45162c76dbf09c5ccf2d8be86382b5c1c81d90740b1b42b3d4ef4e0cb8a421d1?__gda__=exp=1572869911~hmac=cc20d712b07ed3f460a1b4e86aad1a3fda98358bb3f48b90b665f1f4617a1a14&response-content-disposition=attachment%3Bfilename%3D%22hcloud-
######################################################################## 100.0%
==> Pouring hcloud-1.13.0.catalina.bottle.tar.gz
==> Caveats
Bash completion has been installed to:
  /usr/local/etc/bash_completion.d

zsh completions have been installed to:
  /usr/local/share/zsh/site-functions
==> Summary
🍺  /usr/local/Cellar/hcloud/1.13.0: 8 files, 9.4MB

може да проверим версията

$ hcloud version
hcloud v1.13.0

HELP командата

$ hcloud context
Usage:
  hcloud context [FLAGS]
  hcloud context [command]

Available Commands:
  active      Show active context
  create      Create a new context
  delete      Delete a context
  list        List contexts
  use         Use a context

създаме context и въвеждаме тоукъна

$ hcloud context create r.panev
Token:    <<<<<TOKEN>>>>>
Context r.panev created and activated

Създвана на клауд сървър

Проверяваме кой от предоставяните сървъри ще ни трябва

$ hcloud server-type list
ID   NAME        CORES   MEMORY     DISK     STORAGE TYPE
1    cx11        1       2.0 GB     20 GB    local
2    cx11-ceph   1       2.0 GB     20 GB    network
3    cx21        2       4.0 GB     40 GB    local
4    cx21-ceph   2       4.0 GB     40 GB    network
5    cx31        2       8.0 GB     80 GB    local
6    cx31-ceph   2       8.0 GB     80 GB    network
7    cx41        4       16.0 GB    160 GB   local
8    cx41-ceph   4       16.0 GB    160 GB   network
9    cx51        8       32.0 GB    240 GB   local
10   cx51-ceph   8       32.0 GB    240 GB   network
11   ccx11       2       8.0 GB     80 GB    local
12   ccx21       4       16.0 GB    160 GB   local
13   ccx31       8       32.0 GB    240 GB   local
14   ccx41       16      64.0 GB    360 GB   local
15   ccx51       32      128.0 GB   600 GB   local

Вдигаме сървъра

$ hcloud server create --image centos-8 --type cx11 --name panev-hcloud
   2s [====================================================================] 100%
Waiting for server 3578313 to have started... done
Server 3578313 created
IPv4: 78.47.127.86
Root password: AUkgv44dmqaFAX7K4Xbr

И вече си имаме сървърче :)

$ hcloud server list
ID        NAME                 STATUS    IPV4           IPV6                     DATACENTER
3578313   panev-hcloud         running   78.47.127.86   2a01:4f8:c2c:cfb8::/64   nbg1-dc3

Как да използваме terraform за aws

Wed, 16 Oct 2019 12:48:43 +0000

Инсталация от source

1) Ъпдейт на репозиторито

yum update -y

2) Отваряме страницата на проекта Terraform и сваляме последната катуална версия

https://releases.hashicorp.com/terraform/0.12.10/terraform_0.12.10_linux_amd64.zip

3) Разахивираме приложението

unzip ./terraform_0.12.10_linux_amd64.zip -d /usr/local/bin/

4) Един бърз тест:

$ terraform -v
Terraform v0.12.10

5) Създаваме си файл aws-vps.tf

touch aws-vps.tf

6) Попълваме нужната информация за вдигане на VPS, без много екстри

provider "aws" {
  region     = "eu-central-1"
  access_key = "accesskey"
  secret_key = "secretkey"
}

resource "aws_instance" "panev_test_terraform" {
  ami = "ami-9a183671"
  instance_type = "t2.micro"
}

7) След това трябва да инициализираме Terraform:

$ terraform init

Initializing provider plugins...
- Checking for available provider plugins...
- Downloading plugin for provider "aws" (hashicorp/aws) 2.32.0...

The following providers do not have any version constraints in configuration,
so the latest version was installed.

To prevent automatic upgrades to new major versions that may contain breaking
changes, it is recommended to add version = "..." constraints to the
corresponding provider blocks in configuration, with the constraint strings
suggested below.

* provider.aws: version = "~> 2.32"


Warning: Skipping backend initialization pending configuration upgrade

The root module configuration contains errors that may be fixed by running the
configuration upgrade tool, so Terraform is skipping backend initialization.
See below for more information.


Terraform has initialized, but configuration upgrades may be needed.

Terraform found syntax errors in the configuration that prevented full
initialization. If you've recently upgraded to Terraform v0.12, this may be
because your configuration uses syntax constructs that are no longer valid,
and so must be updated before full initialization is possible.

Terraform has installed the required providers to support the configuration
upgrade process. To begin upgrading your configuration, run the following:
    terraform 0.12upgrade

To see the full set of errors that led to this message, run:
    terraform validate

8) Валидираме нашият код

terraform validate

При грешка ще ни каже къде е проблема :

$ terraform validate

Error: Unsupported block type

  on vps.tf line 1:
   1: cat aws-vps.tf

Blocks of type "cat" are not expected here. Did you mean "data"?


Error: Invalid block definition

  on aws-vps.tf line 1:
   1: cat aws-vps.tf

Either a quoted string block label or an opening brace ("{") is expected here.

Когато всичко е както трябва :

$ terraform validate
Success! The configuration is valid.

9) Може да изпозлваме комнадата terraform plan и така, ще направим симулация без да направим нищо в aws:

$ terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.


------------------------------------------------------------------------

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # aws_instance.panev_test_terraform will be created
  + resource "aws_instance" "panev_test_terraform" {
      + ami                          = "ami-9a183671"
      + arn                          = (known after apply)
      + associate_public_ip_address  = (known after apply)
      + availability_zone            = (known after apply)
      + cpu_core_count               = (known after apply)
      + cpu_threads_per_core         = (known after apply)
      + get_password_data            = false
      + host_id                      = (known after apply)
      + id                           = (known after apply)
      + instance_state               = (known after apply)
      + instance_type                = "t2.micro"
      + ipv6_address_count           = (known after apply)
      + ipv6_addresses               = (known after apply)
      + key_name                     = (known after apply)
      + network_interface_id         = (known after apply)
      + password_data                = (known after apply)
      + placement_group              = (known after apply)
      + primary_network_interface_id = (known after apply)
      + private_dns                  = (known after apply)
      + private_ip                   = (known after apply)
      + public_dns                   = (known after apply)
      + public_ip                    = (known after apply)
      + security_groups              = (known after apply)
      + source_dest_check            = true
      + subnet_id                    = (known after apply)
      + tenancy                      = (known after apply)
      + volume_tags                  = (known after apply)
      + vpc_security_group_ids       = (known after apply)

      + ebs_block_device {
          + delete_on_termination = (known after apply)
          + device_name           = (known after apply)
          + encrypted             = (known after apply)
          + iops                  = (known after apply)
          + kms_key_id            = (known after apply)
          + snapshot_id           = (known after apply)
          + volume_id             = (known after apply)
          + volume_size           = (known after apply)
          + volume_type           = (known after apply)
        }

      + ephemeral_block_device {
          + device_name  = (known after apply)
          + no_device    = (known after apply)
          + virtual_name = (known after apply)
        }

      + network_interface {
          + delete_on_termination = (known after apply)
          + device_index          = (known after apply)
          + network_interface_id  = (known after apply)
        }

      + root_block_device {
          + delete_on_termination = (known after apply)
          + encrypted             = (known after apply)
          + iops                  = (known after apply)
          + kms_key_id            = (known after apply)
          + volume_id             = (known after apply)
          + volume_size           = (known after apply)
          + volume_type           = (known after apply)
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

------------------------------------------------------------------------

Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.

10) След като се убедим в това което искаме изпълняваме terraform apply и потвърждаме на въпроса с yes

$ terraform apply

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # aws_instance.panev_test_terraform will be created
  + resource "aws_instance" "panev_test_terraform" {
      + ami                          = "ami-9a183671"
      + arn                          = (known after apply)
      + associate_public_ip_address  = (known after apply)
      + availability_zone            = (known after apply)
      + cpu_core_count               = (known after apply)
      + cpu_threads_per_core         = (known after apply)
      + get_password_data            = false
      + host_id                      = (known after apply)
      + id                           = (known after apply)
      + instance_state               = (known after apply)
      + instance_type                = "t2.micro"
      + ipv6_address_count           = (known after apply)
      + ipv6_addresses               = (known after apply)
      + key_name                     = (known after apply)
      + network_interface_id         = (known after apply)
      + password_data                = (known after apply)
      + placement_group              = (known after apply)
      + primary_network_interface_id = (known after apply)
      + private_dns                  = (known after apply)
      + private_ip                   = (known after apply)
      + public_dns                   = (known after apply)
      + public_ip                    = (known after apply)
      + security_groups              = (known after apply)
      + source_dest_check            = true
      + subnet_id                    = (known after apply)
      + tenancy                      = (known after apply)
      + volume_tags                  = (known after apply)
      + vpc_security_group_ids       = (known after apply)

      + ebs_block_device {
          + delete_on_termination = (known after apply)
          + device_name           = (known after apply)
          + encrypted             = (known after apply)
          + iops                  = (known after apply)
          + kms_key_id            = (known after apply)
          + snapshot_id           = (known after apply)
          + volume_id             = (known after apply)
          + volume_size           = (known after apply)
          + volume_type           = (known after apply)
        }

      + ephemeral_block_device {
          + device_name  = (known after apply)
          + no_device    = (known after apply)
          + virtual_name = (known after apply)
        }

      + network_interface {
          + delete_on_termination = (known after apply)
          + device_index          = (known after apply)
          + network_interface_id  = (known after apply)
        }

      + root_block_device {
          + delete_on_termination = (known after apply)
          + encrypted             = (known after apply)
          + iops                  = (known after apply)
          + kms_key_id            = (known after apply)
          + volume_id             = (known after apply)
          + volume_size           = (known after apply)
          + volume_type           = (known after apply)
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

aws_instance.panev_test_terraform: Creating...
aws_instance.panev_test_terraform: Still creating... [10s elapsed]
aws_instance.panev_test_terraform: Still creating... [20s elapsed]
aws_instance.panev_test_terraform: Still creating... [30s elapsed]
aws_instance.panev_test_terraform: Creation complete after 34s [id=i-0aae21339de0060c2]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

11) За да премахнем инстанцията пишем terraform destroy и потвърждаме на въпроса с yes

$ terraform destroy
aws_instance.panev_test_terraform: Refreshing state... [id=i-084ff7c42ceb73240]

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  - destroy

Terraform will perform the following actions:

  # aws_instance.panev_test_terraform will be destroyed
  - resource "aws_instance" "panev_test_terraform" {
      - ami                          = "ami-9a183671" -> null
      - arn                          = "arn:aws:ec2:eu-central-1:918488250450:instance/i-084ff7c42ceb73240" -> null
      - associate_public_ip_address  = true -> null
      - availability_zone            = "eu-central-1b" -> null
      - cpu_core_count               = 1 -> null
      - cpu_threads_per_core         = 1 -> null
      - disable_api_termination      = false -> null
      - ebs_optimized                = false -> null
      - get_password_data            = false -> null
      - id                           = "i-084ff7c42ceb73240" -> null
      - instance_state               = "running" -> null
      - instance_type                = "t2.micro" -> null
      - ipv6_address_count           = 0 -> null
      - ipv6_addresses               = [] -> null
      - monitoring                   = false -> null
      - primary_network_interface_id = "eni-0ae9762298a6f00bc" -> null
      - private_dns                  = "ip-172-31-36-173.eu-central-1.compute.internal" -> null
      - private_ip                   = "172.31.36.173" -> null
      - public_dns                   = "ec2-18-185-69-50.eu-central-1.compute.amazonaws.com" -> null
      - public_ip                    = "18.185.69.50" -> null
      - security_groups              = [
          - "default",
        ] -> null
      - source_dest_check            = true -> null
      - subnet_id                    = "subnet-7a391307" -> null
      - tags                         = {} -> null
      - tenancy                      = "default" -> null
      - volume_tags                  = {} -> null
      - vpc_security_group_ids       = [
          - "sg-57d0ac36",
        ] -> null

      - credit_specification {
          - cpu_credits = "standard" -> null
        }

      - root_block_device {
          - delete_on_termination = false -> null
          - encrypted             = false -> null
          - iops                  = 100 -> null
          - volume_id             = "vol-0ac02fec6b74e9030" -> null
          - volume_size           = 8 -> null
          - volume_type           = "gp2" -> null
        }
    }

Plan: 0 to add, 0 to change, 1 to destroy.

Do you really want to destroy all resources?
  Terraform will destroy all your managed infrastructure, as shown above.
  There is no undo. Only 'yes' will be accepted to confirm.

  Enter a value: yes

aws_instance.panev_test: Destroying... [id=i-084ff7c42ceb73240]
aws_instance.panev_test: Still destroying... [id=i-084ff7c42ceb73240, 10s elapsed]
aws_instance.panev_test: Still destroying... [id=i-084ff7c42ceb73240, 20s elapsed]
aws_instance.panev_test: Still destroying... [id=i-084ff7c42ceb73240, 30s elapsed]
aws_instance.panev_test: Destruction complete after 30s

Destroy complete! Resources: 1 destroyed.

Как да инсталираме и конфигурираме Prometheus на Linux VM

Wed, 11 Sep 2019 18:57:43 +0000

Инсталация от source

Ъпдейт на репозиторито

yum update -y

Отваряме страницата на проекта Prometheus и сваляме последната катуална версия
Сваляме нужнитя ни пакет

cd /opt/
curl -LO https://github.com/prometheus/prometheus/releases/download/v2.12.0/prometheus-2.12.0.linux-amd64.tar.gz
tar -xvf prometheus-2.3.2.linux-amd64.tar.gz
mv prometheus-2.3.2.linux-amd64 prometheus-files

Създаваме потребител prometheus, нужните директории и техните права

useradd --no-create-home --shell /bin/false prometheus
mkdir /etc/prometheus
mkdir /var/lib/prometheus
chown prometheus:prometheus /etc/prometheus
chown prometheus:prometheus /var/lib/prometheus

Копираме бинарните файлове от директория prometheus-files във /usr/bin/

cp prometheus-files/prometheus /usr/local/bin/
cp prometheus-files/promtool /usr/local/bin/
chown prometheus:prometheus /usr/local/bin/prometheus
chown prometheus:prometheus /usr/local/bin/promtool

Преместваме директориите consoles и console_libraries в /etc/prometheus

cp -r prometheus-files/consoles /etc/prometheus
cp -r prometheus-files/console_libraries /etc/prometheus
chown -R prometheus:prometheus /etc/prometheus/consoles
chown -R prometheus:prometheus /etc/prometheus/console_libraries

Конфигурация на prometheus

Необходимата конфигурация се намира във файла /etc/prometheus/prometheus.yml.

Създаваме фйала prometheus.yml

touch /etc/prometheus/prometheus.yml

Копирайте следните редове във вашият prometheus.yml файл.

global:
  scrape_interval: 10s
 
scrape_configs:
  - job_name: 'prometheus'
    scrape_interval: 5s
    static_configs:
      - targets: ['localhost:9090']

Оправяме правата на файла:

chown prometheus:prometheus /etc/prometheus/prometheus.yml

Създаваме Prometheus Service файл

Създаваме фйала /etc/systemd/system/prometheus.service

touch /etc/systemd/system/prometheus.service

Копирайте следните редове във вашият prometheus.service файл.

[Unit]
Description=Prometheus
Wants=network-online.target
After=network-online.target
 
[Service]
User=prometheus
Group=prometheus
Type=simple
ExecStart=/usr/local/bin/prometheus \
    --config.file /etc/prometheus/prometheus.yml \
    --storage.tsdb.path /var/lib/prometheus/ \
    --web.console.templates=/etc/prometheus/consoles \
    --web.console.libraries=/etc/prometheus/console_libraries
 
[Install]
WantedBy=multi-user.target

Презареждаме systemd service и стартираме prometheus

systemctl daemon-reload
systemctl start prometheus

Access Prometheus Web UI

Достъп до Web UI може да направите на вашият IP и порт 9090

http://prometheus-ip>:9090/graph

Черен екран при събуждане на Mac

Mon, 19 Aug 2019 09:30:43 +0000

Наложи ми се да си преинсталирам лаптопа macbook pro но лаптопа влезе в режим sleep и не можех да го събудя. При натискна не power бутона видимо не се случваше нищо, просветката не светеше, капслока също, няма звук, няма картина…демек тухла за 3000 лева 🙂 След като го оставих малко на страни и да си събера мислите забелязах, че лаптопа работи. ГРЕЕ. Ураааа има живот все още в него

Не се паникьосвайте!

В случай, че изпаднете в подобно състояние изпробвайте следните стъпи, при мене имаше моментален ефект. Трябва да се рестартира управлението на захранването и NVRAM.

ко имате някакви проблеми със своя MacBook, MacBook Air, MacBook Pro или с операционната системата или устройството, свързано към Mac, един от начините за решаване на проблема е да се изчисти паметта на компютъра на данни (NVRAM и PRAM), която се съхранява на твърдия диск. Тези данни не могат да бъдат изтрити, когато изключите своя компютър.

**
Дефиниции:**

NVRAM – Енергонезависима памет с произволен достъп, енергонезависима памет, която е в близост до RAM, но продължава да съществува дори и без външен източник на захранване.

PRAM – Параметър оперативна памет която съдържа най-вече обаче данни на операционната система. Наред с другите неща,се съхраняват данни за MacOS, шрифта който се използва, алармени настройки, дисков кеш, и т.н.

SMC – Контролер система за управление, чип на дънната платка на вашияt Mac или MacBook, Отговаря за управлението на захранването, функциите на хардуера, включително USB устройства и Bluetooth.

**
Тази памет NVRAM и PRAM съхранява тези настройки, като:**

данни за диска;
виртуална памет;
настройки на монитора и високоговорителите;
системни шрифтове;
други настройки.

За да нулирате NVRAM и PRAM:

Стъпка 1 – Изключете своя Mac;
Стъпка 2 – Включете своя Mac;

Стъпка 3 – След като чуете стартовия сигнал, задръжте натиснат клавиша ⌥Option (Alt) + ⌘Cmd + P + R и го задръжте;

Стъпка 4 – Компютърът ще се рестартира и отново ще чуете стартовия сигнал, след което можете да освободите клавишите.

Нулиране на настройките на SMC контролера

Ако забележите проблеми, които са свързани със:

реакция при натискане на бутона за захранване;
реакция при отваряне и затваряне на капака на дисплея на Mac;
управление на батерийни ресурси;
температурен контрол;
сензор за внезапно движение (SMS)
сензор за околна светлина;
подсветката на клавиатурата;
контрол на индикатора за състояние;
индикатори за състояние на батерията;

Избиране на външен (вместо вътрешен) видео източник за отделните дисплеи на iMac, или други проблеми, то тогава е необходимо да нулирате SMC параметрите на вашият MacBook, MacBook Air, MacBook Pro.

За да нулирате SMC параметрите:

Стъпка 1 – Изключете компютъра и го свържете към мрежата чрез захранващия адаптер MagSafe или USB-C

Стъпка 2 – Задръжте натиснатите клавиши ⇧Shift + ^ Ctrl + ⌥Option (Alt) и, без да ги пускате, натиснете бутона за включване

Стъпка 3 – Освободете клавишите и отново натиснете бутона за включване

«center> </center>

Upload ssh key through ansible

Tue, 23 Jul 2019 11:15:41 +0000

Upload ssh key through ansible
Create a file named ssh-key-setup.yml in directory name /etc/ansible/playbooks.

---

  - hosts: all

    become: yes

    #To start  ansible-playbook ssh-key-setup.yml -u panev --ask-pass


    tasks:



      - name: Creates destination directory

        file: state=directory mode=0700 dest=/root/.ssh/ 

        #file: state=directory mode=0700 owner=panev group=panev dest=/home/panev/.ssh/ #FOR USERS



      - name: Pushes user's rsa key to root's users box (it's ok if this TASK fails)

        copy: src=~/.ssh/id_rsa.pub dest=/root/.ssh/authorized_keys owner=root mode=0600

        #copy: src=~/.ssh/id_rsa.pub dest=/home/panev/.ssh/authorized_keys owner=panev group=panev mode=0600 #FOR USERS



 #     - name: Set authorized key for user X copying it from current user

 #       authorized_key:

 #         user: panev

 #         state: present

 #         key: ""



      - name: Change SSH port

        lineinfile:

          dest: /etc/ssh/sshd_config

          regexp: "^Port"

          line: "Port 2222"

          state: present


          #Remove root login

 #     - name: Remove root SSH access

 #       lineinfile:

 #        dest: /etc/ssh/sshd_config

 #        regexp: "^PermitRootLogin"

 #        line: "PermitRootLogin no"

 #        state: present



      - name: Remove password SSH access

        lineinfile:

          dest: /etc/ssh/sshd_config

          regexp: "^PasswordAuthentication"

          line: "PasswordAuthentication no"

          state: present


      - name: restart ssh

        service: name=ssh state=restarted

To start ansible-playbook ssh-key-setup.yml -u root –ask-pass

Инсталация на AWX на CentOS 7

Sat, 15 Jun 2019 17:19:56 +0000

AWX е безплатна алтернатива на Red Hat Ansible Tower.

Следвайте стъпките по-долу за инсталация върху CentOS 7 минимална инсталация

# Insall EPEL repository
yum -y install epel-release

# Спиране на защитната стена (firewall) и SELinux
systemctl disable firewalld
systemctl stop firewalld
sed -i 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/selinux/config
setenforce 0
reboot

# Инсталиране на нужните ни пакети
yum -y install git gettext ansible docker nodejs npm gcc-c++ bzip2
yum -y install python-docker-py

#  Start and enable docker service
systemctl start docker
systemctl enable docker

# Клониране на хранилището и инсталацията му (ще отнеме около 20 минути)
git clone https://github.com/ansible/awx.git
cd awx/installer/
ansible-playbook -i inventory install.yml

# Monitor migrations status (it will take about 10 minutes)
docker logs -f awx_task

Вече имате достъп до уеб сървъра на AWX http://IP. Потребителското име по подразбиране на администратора е admin, а паролата е password.

Повече за проекта може да намерите на следният линк.

Install Redis and Redis PHP on cPanel

Wed, 05 Jun 2019 05:13:17 +0000

Install EPLE repository

yum install epel-release
yum update
yum install redis
systemctl restart redis
systemctl enable redis

Install the Redis PHP Extension EasyApache 4

EasyApache 4 supports multiple versions of PHP so we need to install the Redis PHP extension on each PHP version. Run the following commands to install and enable the Redis PHP extension on each PHP version you have installed on your server:

yes | /opt/cpanel/ea-php71/root/usr/bin/pecl install igbinary igbinary-devel redis 
/opt/cpanel/ea-php71/root/usr/bin/php -m | grep redis

yes | /opt/cpanel/ea-php70/root/usr/bin/pecl install igbinary igbinary-devel redis 
/opt/cpanel/ea-php70/root/usr/bin/php -m | grep redis

yes | /opt/cpanel/ea-php56/root/usr/bin/pecl install igbinary igbinary-devel redis 
/opt/cpanel/ea-php56/root/usr/bin/php -m | grep redis