Introduction

ArgoCD

Argo CD is an open-source continuous delivery tool for Kubernetes that automates the deployment of your applications and infrastructure as code. With Argo CD, you can define your Kubernetes application manifests as declarative YAML files and store them in a version control system like Git. Argo CD then continuously monitors your Git repository for changes to your application manifests, and automatically deploys them to your Kubernetes cluster as needed.

Argo CD also provides a web-based user interface that allows you to view the status of your applications and infrastructure, and roll back to previous versions if needed. In addition, Argo CD can integrate with your existing CI/CD pipelines and GitOps workflows, providing a seamless and automated deployment experience.

ArgoCD Image Updater

Argo CD Image Updater is an optional component of Argo CD that automates the updating of container images in your Kubernetes deployments. It continuously scans your container image registry for new versions of your images and updates your Kubernetes deployment manifests with the latest image tags.

Argo CD Image Updater uses customizable strategies to perform image updates, including simple tag updates, canary releases, and blue-green deployments. You can configure it to work with a variety of image registries, including Docker Hub, Google Container Registry, and Amazon Elastic Container Registry.

Argo CD Image Updater simplifies the process of updating container images in your Kubernetes deployments and allows you to maintain a consistent and up-to-date application environment. By automating image updates, you can reduce the risk of manual errors and improve the efficiency of your DevOps processes.

Why?

argocd-image-updater is alternative way to combine CI pipeline and CD proses if you’re using ArgoCD. In another way, strategy to combine ArgoCD with CI pipeline is add new pipeline stages that will Pull -> Write -> Push deployment manifest to repository, after that it will trigger sync process ArgoCD for checking new version of deployment app.

Argo CD Image Updater provides a number of benefits over other ways of combining CI pipelines and Argo CD for image updates:

1. Automated image updates: With Argo CD Image Updater, you can automate the process of updating container images in your Kubernetes deployments, which reduces the need for manual intervention and minimizes the risk of human error.
2. Flexibility: Argo CD Image Updater supports a variety of image update strategies, including simple tag updates, canary releases, and blue-green deployments, so you can choose the strategy that works best for your specific use case.
3. Integration with Argo CD: Argo CD Image Updater is designed to work seamlessly with Argo CD, so you can use a single tool to manage your Kubernetes deployments and image updates.
4. Scalability: Argo CD Image Updater is designed to handle large-scale deployments with thousands of images and provides a number of performance optimizations to ensure that image updates are performed quickly and efficiently.

How?

Prerequisites

• Kubernetes with argocd has installed
• Account docker hub

Step-by-step

1. Install argocd-image-updater as plugin for existing argocd. You can install Argo CD Image Updater by running the following command:

helm install argocd-image-updater argo/argocd-image-updater — namespace argocd — set image.repository=<image_repo>

Replace <image_repo> with the image repository where you want to pull container images from, such as docker.io. This command installs the Image Updater pod and sets up the necessary RBAC permissions.

2. Configure your container image registry: You need to configure Argo CD Image Updater with the credentials for your container image registry, so it can pull the latest image versions. You can create a Kubernetes secret containing the registry credentials by running the following command:

kubectl create secret docker-registry <secret_name> --docker-server=<registry_url> --docker-username=<username> --docker-password=<password> --docker-email=<email>

Replace <secret_name> with a name for the secret, <registry_url> with the URL of your container image registry, <username> with your registry username, <password> with your registry password, and <email> with your email address.

then, you must add new ConfigMap for argocd-image-updater

apiVersion: v1
kind: ConfigMap
metadata:
  name: argocd-image-updater-config
data:
  registries.conf: |
    registries:
    - name: Docker Hub
      prefix: docker.io
      api_url: https://registry-1.docker.io
      credentials: secret:<secret_name>
      defaultns: library
      default: true

3. Configure your image update policy: You can configure your image update policy by adding an annotations section to your Argo CD application manifests. Here is an example annotations section that performs simple tag updates:

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: myapp
  namespace: myapp
annotations:
  argocd-image-updater.argoproj.io/image-list: myimage=some/image:latest
  argocd-image-updater.argoproj.io//myimage.update-strategy: digest
  argocd-image-updater.argoproj.io/write-back-method: git
  argocd-image-updater.argoproj.io/git-branch: master
spec:
  project: default
  source:
    repoURL: <repo_url>
    path: myapp
  destination:
    server: https://kubernetes.default.svc
    namespace: myapp
  syncPolicy:
    automated:
      prune: true
      selfHeal: true

Replace <repo_url> with the URL of your Git repository

4. Monitor and troubleshoot: Once you have set up Argo CD Image Updater, you can monitor its activity and troubleshoot any issues by checking the logs of the Image Updater pod and the Argo CD application controller pod. You can use kubectl to view the logs:

kubectl logs -f <pod_name>

Replace <pod_name> with the name of the pod you want to view logs for. You can also use the Argo CD UI to view the status of your applications and image updates.

Closing

implementing Argo CD Image Updater involves installing and configuring the Image Updater pod, configuring your image update policy, and configuring your container image registry. With Argo CD Image Updater, you can automate the updating of container images in your Kubernetes deployments, which simplifies the process of maintaining an up-to-date application environment

Automation ArgoCD with CI Pipeline Using Image Updater was originally published in btech-engineering on Medium, where people are continuing the conversation by highlighting and responding to this story.

Introduction

Wazuh is a popular open-source security platform that provides an extensive range of threat detection, visibility, and response capabilities. It is designed to help organizations to monitor and manage their security posture more effectively by collecting, analyzing, and correlating security-related data from various sources across their network infrastructure. The platform leverages a combination of host-based intrusion detection (HIDS), log analysis, and security event correlation to detect, identify, and respond to potential security incidents.

At its core, Wazuh consists of three primary components: the Wazuh server, agents, and the Wazuh app. The Wazuh server is responsible for collecting and analyzing security data from various sources, while the agents are installed on the monitored endpoints to collect security-relevant data such as system events, network traffic, and file integrity. The Wazuh app provides a web-based user interface that allows security analysts to view and analyze security events, configure rules, and manage the Wazuh infrastructure. With its robust feature set and flexible architecture, Wazuh has become a popular choice for security professionals who seek to improve their organization’s security posture while minimizing the risk of security breaches.

Preparing for the Installation

Operating System

Wazuh can be installed on various operating systems, including CentOS, Debian, Ubuntu, Windows, and macOS.

Hardware Specifications

Hardware requirements highly depend on the number of protected endpoints and cloud workloads.

Software Dependencies

Wazuh requires several software components, including Elastic Stack, Filebeat, and Wazuh Manager. Elastic Stack is a set of open-source tools for data processing and analysis, including Elasticsearch, Logstash, and Kibana. Filebeat is a lightweight agent that collects log data from different sources and forwards it to Elasticsearch. Wazuh Manager is the central component of the Wazuh architecture, which receives data from the Wazuh Agents and processes it to generate alerts and notifications.

Step-by-Step Installation

Install Wazuh

apt install -y curl apt-transport-https unzip wget libcap2-bin software-properties-common lsb-release gnupg
curl -s https://packages.wazuh.com/key/GPG-KEY-WAZUH | apt-key add -
echo "deb https://packages.wazuh.com/4.x/apt/ stable main" | tee -a /etc/apt/sources.list.d/wazuh.list
apt-get update

Install Wazuh Manager

apt install -y wazuh-manager

systemctl daemon-reload
systemctl enable --now wazuh-manager
systemctl status wazuh-manager

Install Elasticsearch

Install Elasticsearch

apt install -y elasticsearch-oss opendistroforelasticsearch

curl -so /etc/elasticsearch/elasticsearch.yml https://packages.wazuh.com/resources/4.2/open-distro/elasticsearch/7.x/elasticsearch_all_in_one.yml
curl -so /usr/share/elasticsearch/plugins/opendistro_security/securityconfig/roles.yml https://packages.wazuh.com/resources/4.2/open-distro/elasticsearch/roles/roles.yml
curl -so /usr/share/elasticsearch/plugins/opendistro_security/securityconfig/roles_mapping.yml https://packages.wazuh.com/resources/4.2/open-distro/elasticsearch/roles/roles_mapping.yml
curl -so /usr/share/elasticsearch/plugins/opendistro_security/securityconfig/internal_users.yml https://packages.wazuh.com/resources/4.2/open-distro/elasticsearch/roles/internal_users.yml

Create certificate

rm /etc/elasticsearch/esnode-key.pem /etc/elasticsearch/esnode.pem /etc/elasticsearch/kirk-key.pem /etc/elasticsearch/kirk.pem /etc/elasticsearch/root-ca.pem -f

curl -so ~/wazuh-cert-tool.sh https://packages.wazuh.com/resources/4.2/open-distro/tools/certificate-utility/wazuh-cert-tool.sh
curl -so ~/instances.yml https://packages.wazuh.com/resources/4.2/open-distro/tools/certificate-utility/instances_aio.yml

bash ~/wazuh-cert-tool.sh

mkdir /etc/elasticsearch/certs/
mv ~/certs/elasticsearch* /etc/elasticsearch/certs/
mv ~/certs/admin* /etc/elasticsearch/certs/
cp ~/certs/root-ca* /etc/elasticsearch/certs/

mkdir -p /etc/elasticsearch/jvm.options.d
echo '-Dlog4j2.formatMsgNoLookups=true' > /etc/elasticsearch/jvm.options.d/disabledlog4j.options
chmod 2750 /etc/elasticsearch/jvm.options.d/disabledlog4j.options
chown root:elasticsearch /etc/elasticsearch/jvm.options.d/disabledlog4j.options

systemctl daemon-reload
systemctl enable elasticsearch
systemctl start elasticsearch

export JAVA_HOME=/usr/share/elasticsearch/jdk/ && /usr/share/elasticsearch/plugins/opendistro_security/tools/securityadmin.sh -cd /usr/share/elasticsearch/plugins/opendistro_security/securityconfig/ -nhnv -cacert /etc/elasticsearch/certs/root-ca.pem -cert /etc/elasticsearch/certs/admin.pem -key /etc/elasticsearch/certs/admin-key.pem

Install Filebeat

Install Filebeat

apt install -y filebeat

Config Filebeat

curl -so /etc/filebeat/filebeat.yml https://packages.wazuh.com/resources/4.2/open-distro/filebeat/7.x/filebeat_all_in_one.yml

curl -so /etc/filebeat/wazuh-template.json https://raw.githubusercontent.com/wazuh/wazuh/4.2/extensions/elasticsearch/7.x/wazuh-template.json
chmod go+r /etc/filebeat/wazuh-template.json

Install Module Filebeat

curl -s https://packages.wazuh.com/4.x/filebeat/wazuh-filebeat-0.1.tar.gz | tar -xvz -C /usr/share/filebeat/module

Copy certs

mkdir /etc/filebeat/certs
cp ~/certs/root-ca.pem /etc/filebeat/certs/
mv ~/certs/filebeat* /etc/filebeat/certs/

Restart Daemon

systemctl daemon-reload
systemctl enable filebeat
systemctl start filebeat

Configure Filebeat

filebeat test output

Install Kibana

Install package

apt install -y opendistroforelasticsearch-kibana

Download kibana config

curl -so /etc/kibana/kibana.yml https://packages.wazuh.com/resources/4.2/open-distro/kibana/7.x/kibana_all_in_one.yml

Prepare directory

mkdir /usr/share/kibana/data
chown -R kibana:kibana /usr/share/kibana/data

Kibana plugin

cd /usr/share/kibana
sudo -u kibana /usr/share/kibana/bin/kibana-plugin install https://packages.wazuh.com/4.x/ui/kibana/wazuh_kibana-4.2.6_7.10.2-1.zip

Elasticsearch certificates

mkdir /etc/kibana/certs
cp ~/certs/root-ca.pem /etc/kibana/certs/
mv ~/certs/kibana* /etc/kibana/certs/
chown kibana:kibana /etc/kibana/certs/*

Configure netcap

setcap 'cap_net_bind_service=+ep' /usr/share/kibana/node/bin/node

Configure systemd

systemctl daemon-reload
systemctl enable kibana
systemctl start kibana

Add Wazuh Agent (Linux)

Get setup agent commnad

Open Wazuh Manager https://<ip_wazuh_manager>

Set Wazuh Manager Address

curl -so wazuh-agent-4.2.6.deb https://packages.wazuh.com/4.x/apt/pool/main/w/wazuh-agent/wazuh-agent_4.2.6-1_amd64.deb && sudo WAZUH_MANAGER='172.100.1.11' WAZUH_AGENT_GROUP='default' dpkg -i ./wazuh-agent-4.2.6.deb

Setup Agent

Setup Repo

curl -s https://packages.wazuh.com/key/GPG-KEY-WAZUH | apt-key add -
echo "deb https://packages.wazuh.com/4.x/apt/ stable main" | tee -a /etc/apt/sources.list.d/wazuh.list
apt-get update

Install and register agent

curl -so wazuh-agent-4.2.6.deb https://packages.wazuh.com/4.x/apt/pool/main/w/wazuh-agent/wazuh-agent_4.2.6-1_amd64.deb && sudo WAZUH_MANAGER='172.100.1.11' WAZUH_AGENT_GROUP='default' dpkg -i ./wazuh-agent-4.2.6.deb

Enable and start agent service

sudo systemctl daemon-reload
sudo systemctl enable wazuh-agent
sudo systemctl start wazuh-agent

Verification

Conclusion

In summary, Wazuh is a comprehensive security platform that provides organizations with the necessary tools to detect and respond to security threats in real-time.

Documentation By Aji Arya

Our Tagline

#ContinuousLearning

Reference

Wazuh documentation

Getting started with Wazuh: Installation and Configuration Guide was originally published in btech-engineering on Medium, where people are continuing the conversation by highlighting and responding to this story.

Intro

Kubevirt provides a seamless solution for integrating microservices with virtual machines in a Kubernetes cluster. To get started, install Kubevirt onto your cluster using the Kubevirt Operator, and then use the Kubevirt API to define and create virtual machines. With Kubevirt, you can manage virtual machines just like any other Kubernetes resource, using tools like kubectl to monitor and modify them.

In addition to Kubernetes features such as RBAC and network policies, Kubevirt also provides a user-friendly web-based interface for managing virtual machines. This allows you to easily create and configure VMs, as well as monitor their performance and resource usage. By deploying your VMs in Kubernetes with Kubevirt, you can enjoy the scalability and reliability of containerized microservices, while also leveraging the versatility and power of virtual machines for your application infrastructure.

Purpose

This scenario walks through the creation of a Virtual Machine Instance (VMI) on Kubernetes and then how virtctl is used to interact with its console. This tutorial based on Kubevirt Documentation.

Practical

Pre-requisites

• Kubernetes Cluster
• Kubevirt already installed on Kubernetes Cluster

Installation

Create VM

nano vm.yaml
...
apiVersion: kubevirt.io/v1alpha3
kind: VirtualMachine
metadata:
  name: testvm
spec:
  running: false
  template:
    metadata:
      labels:
        kubevirt.io/size: small
        kubevirt.io/domain: ubuntu-bionic
    spec:
      domain:
        cpu:
          cores: 1
        devices:
          disks:
            - name: containervolume
              disk:
                bus: virtio
            - name: cloudinitvolume
              disk:
                bus: virtio
          interfaces:
          - name: default
            masquerade: {}
        resources:
          requests:
            memory: 2048M
      networks:
      - name: default
        pod: {}
      volumes:
        - name: containervolume
          containerDisk:
            image: tedezed/ubuntu-container-disk:20.0
        - name: cloudinitvolume
          cloudInitNoCloud:
            userData: |-
              #cloud-config
              chpasswd:
                list: |
                  ubuntu:ubuntu
                  root:toor
                expire: False

Apply the manifest to Kubernetes

kubectl create ns vm
kubectl apply -f vm.yaml -n vm
...output...
virtualmachine.kubevirt.io "testvm" created
  virtualmachineinstancepreset.kubevirt.io "small" created

Manage Virtual Machines

To get a list of existing Virtual Machines

kubectl get vms -n vm
...output...
NAME     AGE    STATUS    READY
testvm   117s   Stopped   False
............
kubectl get vms -o yaml testvm -n vm

To start a Virtual Machine you can use:

virtctl start testvm -n vm
...output...
VM testvm was scheduled to start
............

kubectl get vms -n vm
...output...
NAME     AGE     STATUS    READY
testvm   4m27s   Running   True

After start we can check status VM

kubectl get vmis -n vm
NAME     AGE    PHASE     IP              NODENAME           READY
testvm   2m6s   Running   10.10.101.140   kubevirt-worker1   True

Controlling the State of the VM

To shut it down:

virtctl stop testvm -n vm

To delete a Virtual Machine:

kubectl delete vm testvm -n vm

Conclusion

In conclusion, Kubevirt is a powerful tool for deploying virtual machines in a Kubernetes cluster. By integrating microservices and virtual machines in this way, you can take advantage of the scalability and flexibility of containerized applications, while also leveraging the power and versatility of virtualization. With Kubevirt, you can manage virtual machines just like any other Kubernetes resource, using familiar tools and interfaces such as kubectl and web-based dashboards.

In addition, Kubevirt offers a range of features to help you get the most out of your virtual machines, including support for various operating systems, virtualized hardware devices, and high-performance networking. Whether you’re running a complex enterprise application or a simple development environment, Kubevirt can provide a seamless and integrated solution for all your virtualization needs. So, if you’re looking to deploy virtual machines in Kubernetes, be sure to check out Kubevirt and see how it can help you streamline your infrastructure and improve your application performance.

Our Tagline

#ContinuousLearning

Reference

Use KubeVirt | KubeVirt.io

Getting KubeVirt and K0s to play nicely on Ubuntu 20.04 LTS | by Joseph Bironas | Medium

Tedezed/kubevirt-images-generator: Easy Kubevirt images generator — Public images repository 💿 (github.com)

Deploy your VM in Kubernetes Cluster using Kubevirt was originally published in btech-engineering on Medium, where people are continuing the conversation by highlighting and responding to this story.

Intro

OpenIO is designed to be flexible, scalable, and modular, allowing users to deploy it on-premise, in the cloud, or in a hybrid environment. With its unique architecture, OpenIO provides seamless horizontal scaling, making it an ideal solution for organizations that require a large storage capacity. In this article we will show you our research about deployment OpenIO Multi Nodes.

Whether you’re a small business looking for a cost-effective storage solution or a large enterprise that requires scalable and secure data storage, OpenIO can cater to your needs. By the end of this blog post, you will have a better understanding of how OpenIO can help you manage your data storage needs and how you can deploy it in your organization. So, let’s dive into the world of OpenIO object storage and explore its deployment options and benefits.

Architecture

Practical

System Requirement

• Root privileges are required (using sudo).
• SELinux or AppArmor must be disabled.
• All nodes must have different hostnames.
• All nodes must have a version of python greater than 2.7.
• The node used to run the deployment must have a version of python greater than 3.6
• All mounted partitions used for data/metadata must support extended attributes. XFS is recommended

Environment

• Ubuntu 18.04
• 3 Computes with (4 CPU, 8G RAM, 100GB Storage)
• OpenIO Version, OpenIO 20.04 oiosds

Pre-Installation

Disable AppArmor & UFW (All Nodes)

sudo echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT apparmor=0"' > /etc/default/grub.d/apparmor.cfg
sudo update-grub
sudo ufw disable
sudo systemctl disable ufw.service
sudo reboot

Format Disk to xfs (All Nodes)

for i in 3 2 1; do ssh server0$i /bin/bash << 'EOF'

parted -a optimal /dev/vdb -s mklabel gpt unit TB mkpart primary 0% 100%
parted -a optimal /dev/vdc -s mklabel gpt unit TB mkpart primary 0% 100%
parted -a optimal /dev/vdd -s mklabel gpt unit TB mkpart primary 0% 100%

mkfs.xfs -f -L HDD-1 /dev/vdb1
mkfs.xfs -f -L HDD-2 /dev/vdc1
mkfs.xfs -f -L HDD-3 /dev/vdd1

cat >>/etc/fstab <<EOL
LABEL=HDD-1 /mnt/data1 xfs defaults,noatime,noexec 0 0
LABEL=HDD-2 /mnt/data2 xfs defaults,noatime,noexec 0 0
LABEL=HDD-3 /mnt/metadata1 xfs defaults,noatime,noexec 0 0
EOL

mkdir /mnt/{data1,data2,data3,metadata1}
mount -a

reboot

EOF

done

Update Package (All Nodes)

for i in {1..3}; do
    ssh server0${i} sudo apt-get install python-netaddr python3-dev libffi-dev gcc libssl-dev python3-selinux python3-setuptools  python3-venv -y
done

Clone the OpenIO ansible playbook deployment repository

git clone https://github.com/open-io/ansible-playbook-openio-deployment.git --branch 20.04 oiosds
cd oiosds/products/sds

Create Virtual Environment & install ansible

python3 -m venv riset
source riset/bin/activate
pip install -r ansible.pip

Installation

First, configure the inventory according to your environment: Change the IP addresses and SSH user in the inventory.yml file.

nano inventory.yml

---
all:
  hosts:
    node1:
      ansible_host: 10.70.70.110
      openio_data_mounts:
        - mountpoint: /mnt/data1
          partition: /dev/vdb1
        - mountpoint: /mnt/data2
          partition: /dev/vdc1
      openio_metadata_mounts:
        - mountpoint: /mnt/metadata1
          partition: /dev/vdd1
          meta2_count: 2
    node2:
      ansible_host: 10.70.70.111
      openio_data_mounts:
        - mountpoint: /mnt/data1
          partition: /dev/vdb1
        - mountpoint: /mnt/data2
          partition: /dev/vdc1
      openio_metadata_mounts:
        - mountpoint: /mnt/metadata1
          partition: /dev/vdd1
          meta2_count: 2
    node3:
      ansible_host: 10.70.70.112
      openio_data_mounts:
        - mountpoint: /mnt/data1
          partition: /dev/vdb1
        - mountpoint: /mnt/data2
          partition: /dev/vdc1
      openio_metadata_mounts:
        - mountpoint: /mnt/metadata1
          partition: /dev/vdd1
          meta2_count: 2

Configure for SSH Access

for i in {1..3}; do ssh-copy-id -i ~/.ssh/id_rsa.pub root@server0$i; done

Then, you can check that everything is configured correctly using this command

## On Ubuntu
ansible all -i inventory.yml -bv -m ping -e 'ansible_python_interpreter=/usr/bin/python3'

Finally, run these commands:

## To Download & Install requirements
./requirements_install.sh

## To deploy and initialize the cluster:
./deploy_and_bootstrap.sh

Post-Installation

All the nodes are configured to use openio-cli and aws-cli. Run this check script on one of the nodes in the cluster Verify

sudo /usr/bin/openio-basic-checks.

Sample output

#### OpenIO status.
Check the services.
KEY                         STATUS      PID GROUP
OPENIO-account-0            UP        19406 OPENIO,account,0
OPENIO-beanstalkd-0         UP        19290 OPENIO,beanstalkd,0
OPENIO-conscienceagent-0    UP        24145 OPENIO,conscienceagent,0
OPENIO-ecd-0                UP        21021 OPENIO,ecd,0
OPENIO-memcached-0          UP        21816 OPENIO,memcached,0
OPENIO-meta0-0              UP        21342 OPENIO,meta0,0
OPENIO-meta1-0              UP        21361 OPENIO,meta1,0
OPENIO-meta2-0              UP        19739 OPENIO,meta2,0
OPENIO-meta2-1              UP        19861 OPENIO,meta2,1
OPENIO-oio-blob-indexer-0   UP        20320 OPENIO,oio-blob-indexer,0
OPENIO-oio-blob-indexer-1   UP        20331 OPENIO,oio-blob-indexer,1
OPENIO-oio-blob-rebuilder-0 UP        20638 OPENIO,oio-blob-rebuilder,0
OPENIO-oio-event-agent-0    UP        20751 OPENIO,oio-event-agent,0
OPENIO-oio-event-agent-0.1  UP        20713 OPENIO,oio-event-agent,0
OPENIO-oio-meta2-indexer-0  UP        19960 OPENIO,oio-meta2-indexer,0
OPENIO-oioproxy-0           UP        16854 OPENIO,oioproxy,0
OPENIO-oioswift-0           UP        24100 OPENIO,oioswift,0
OPENIO-rawx-0               UP        20122 OPENIO,rawx,0
OPENIO-rawx-1               UP        20140 OPENIO,rawx,1
OPENIO-rdir-0               UP        20532 OPENIO,rdir,0
OPENIO-rdir-1               UP        20533 OPENIO,rdir,1
OPENIO-redis-0              UP        16358 OPENIO,redis,0
OPENIO-redissentinel-0      UP        16641 OPENIO,redissentinel,0
OPENIO-zookeeper-0          UP        18865 OPENIO,zookeeper,0
Task duration: 5ms
--
Check the cluster.
+------------+-------------------+--------------------------------------+------------------------------------+----------------+------------+------+-------+--------+
| Type       | Addr              | Service Id                           | Volume                             | Location       | Slots      | Up   | Score | Locked |
+------------+-------------------+--------------------------------------+------------------------------------+----------------+------------+------+-------+--------+
| account    | 10.70.70.111:6009 | n/a                                  | n/a                                | server02.0 | account    | True |    99 | False  |
| account    | 10.70.70.112:6009 | n/a                                  | n/a                                | server03.0 | account    | True |    99 | False  |
| account    | 10.70.70.110:6009 | n/a                                  | n/a                                | server01.0 | account    | True |    99 | False  |
| beanstalkd | 10.70.70.111:6014 | n/a                                  | /mnt/metadata1/OPENIO/beanstalkd-0 | server02.0 | beanstalkd | True |    99 | False  |
| beanstalkd | 10.70.70.112:6014 | n/a                                  | /mnt/metadata1/OPENIO/beanstalkd-0 | server03.0 | beanstalkd | True |    99 | False  |
| beanstalkd | 10.70.70.110:6014 | n/a                                  | /mnt/metadata1/OPENIO/beanstalkd-0 | server01.0 | beanstalkd | True |    99 | False  |
| meta0      | 10.70.70.111:6001 | n/a                                  | /mnt/metadata1/OPENIO/meta0-0      | server02.0 | meta0      | True |    99 | False  |
| meta0      | 10.70.70.112:6001 | n/a                                  | /mnt/metadata1/OPENIO/meta0-0      | server03.0 | meta0      | True |    99 | False  |
| meta0      | 10.70.70.110:6001 | n/a                                  | /mnt/metadata1/OPENIO/meta0-0      | server01.0 | meta0      | True |    99 | False  |
| meta1      | 10.70.70.111:6110 | n/a                                  | /mnt/metadata1/OPENIO/meta1-0      | server02.0 | meta1      | True |   100 | False  |
| meta1      | 10.70.70.112:6110 | n/a                                  | /mnt/metadata1/OPENIO/meta1-0      | server03.0 | meta1      | True |   100 | False  |
| meta1      | 10.70.70.110:6110 | n/a                                  | /mnt/metadata1/OPENIO/meta1-0      | server01.0 | meta1      | True |   100 | False  |
| meta2      | 10.70.70.111:6121 | n/a                                  | /mnt/metadata1/OPENIO/meta2-1      | server02.1 | meta2      | True |   100 | False  |
| meta2      | 10.70.70.111:6120 | n/a                                  | /mnt/metadata1/OPENIO/meta2-0      | server02.0 | meta2      | True |   100 | False  |
| meta2      | 10.70.70.112:6120 | n/a                                  | /mnt/metadata1/OPENIO/meta2-0      | server03.0 | meta2      | True |   100 | False  |
| meta2      | 10.70.70.112:6121 | n/a                                  | /mnt/metadata1/OPENIO/meta2-1      | server03.1 | meta2      | True |   100 | False  |
| meta2      | 10.70.70.110:6120 | n/a                                  | /mnt/metadata1/OPENIO/meta2-0      | server01.0 | meta2      | True |   100 | False  |
| meta2      | 10.70.70.110:6121 | n/a                                  | /mnt/metadata1/OPENIO/meta2-1      | server01.1 | meta2      | True |   100 | False  |
| oioproxy   | 10.70.70.111:6006 | n/a                                  | n/a                                | server02.0 | oioproxy   | True |    98 | False  |
| oioproxy   | 10.70.70.112:6006 | n/a                                  | n/a                                | server03.0 | oioproxy   | True |    98 | False  |
| oioproxy   | 10.70.70.110:6006 | n/a                                  | n/a                                | server01.0 | oioproxy   | True |    98 | False  |
| oioswift   | 10.70.70.110:6007 | 90ce65f2-4bd8-5423-9326-3674df9ebc04 | n/a                                | server01.0 | oioswift   | True |    99 | False  |
| oioswift   | 10.70.70.111:6007 | 673b517b-4ceb-56ae-90fc-cd8715359db4 | n/a                                | server02.0 | oioswift   | True |    99 | False  |
| oioswift   | 10.70.70.112:6007 | 5cd8ad2c-f516-5183-8d3a-767639663b45 | n/a                                | server03.0 | oioswift   | True |    99 | False  |
| rawx       | 10.70.70.111:6201 | 10.70.70.111:6201                    | /mnt/data2/OPENIO/rawx-1           | server02.1 | rawx       | True |   100 | False  |
| rawx       | 10.70.70.111:6200 | 10.70.70.111:6200                    | /mnt/data1/OPENIO/rawx-0           | server02.0 | rawx       | True |   100 | False  |
| rawx       | 10.70.70.112:6200 | 10.70.70.112:6200                    | /mnt/data1/OPENIO/rawx-0           | server03.0 | rawx       | True |   100 | False  |
| rawx       | 10.70.70.112:6201 | 10.70.70.112:6201                    | /mnt/data2/OPENIO/rawx-1           | server03.1 | rawx       | True |   100 | False  |
| rawx       | 10.70.70.110:6201 | 10.70.70.110:6201                    | /mnt/data2/OPENIO/rawx-1           | server01.1 | rawx       | True |   100 | False  |
| rawx       | 10.70.70.110:6200 | 10.70.70.110:6200                    | /mnt/data1/OPENIO/rawx-0           | server01.0 | rawx       | True |   100 | False  |
| rdir       | 10.70.70.111:6300 | n/a                                  | /mnt/data1/OPENIO/rdir-0           | server02.0 | rdir       | True |    99 | False  |
| rdir       | 10.70.70.111:6301 | n/a                                  | /mnt/data2/OPENIO/rdir-1           | server02.1 | rdir       | True |    99 | False  |
| rdir       | 10.70.70.112:6301 | n/a                                  | /mnt/data2/OPENIO/rdir-1           | server03.1 | rdir       | True |    99 | False  |
| rdir       | 10.70.70.112:6300 | n/a                                  | /mnt/data1/OPENIO/rdir-0           | server03.0 | rdir       | True |    99 | False  |
| rdir       | 10.70.70.110:6301 | n/a                                  | /mnt/data2/OPENIO/rdir-1           | server01.1 | rdir       | True |    99 | False  |
| rdir       | 10.70.70.110:6300 | n/a                                  | /mnt/data1/OPENIO/rdir-0           | server01.0 | rdir       | True |    99 | False  |
+------------+-------------------+--------------------------------------+------------------------------------+----------------+------------+------+-------+--------+
Task duration: 548ms

---
---

*** Commands summary ***

*** OpenIO status ***
Check the services                                                                OK
Check the cluster                                                                 OK
*** OpenIO directory consistency ***
directory status                                                                  OK
reverse directory status                                                          OK
meta0 status                                                                      OK
meta1 status                                                                      OK
*** OpenIO API ***
Upload the /etc/passwd file to the bucket MY_CONTAINER of the project MY_ACCOUNT  OK
Get some information about your object                                            OK
List object in container                                                          OK
Find the services involved for your container                                     OK
Save the data stored in the given object to the '--file' destination              OK
Compare local file against data from SDS                                          OK
Show the account informations                                                     OK
Delete your object                                                                OK
Delete your empty container                                                       OK
*** AWS API ***
Create a bucket 'mybucket'                                                        OK
Upload the '/etc/passwd' file to the bucket 'mybucket'                            OK
List your buckets                                                                 OK
Save the data stored in the given object to the given file                        OK
Compare local file against data from SDS                                          OK
Delete your object                                                                OK
Delete your empty bucket                                                          OK
-------------------
Overall check result                                                              OK

++++
 AWS S3 summary from (/root/.aws/credentials):
  endpoint: http://10.70.70.110:6007
  region:  us-east-1
  access key:  demo:demo
  secret key:  DEMO_PASS
  ssl: false
  signature_version: s3v4
  path style: true

Our Tagline

#ContinuousLearning

Deploy OpenIO Multi Nodes was originally published in btech-engineering on Medium, where people are continuing the conversation by highlighting and responding to this story.

Kiali.io is an open-source observability platform that offers real-time monitoring and visualization of microservices topology and interactions. It is a powerful tool that simplifies the management and monitoring of microservices, enabling users to identify and troubleshoot issues more efficiently. In this article, we will provide a step-by-step guide to installing Kiali.io and exploring its features.

Overview of Kiali.io

Kiali.io provides a comprehensive observability platform that enables users to manage, monitor, and secure their microservices environment more efficiently. With its advanced features and integration capabilities, Kiali.io simplifies the management and monitoring of microservices, enabling users to focus on developing and deploying new services. Some of the key features of Kiali.io include microservices topology visualization, traffic management, metrics and tracing, security, and integration with popular service mesh technologies.

Benefits of Kiali.io

Kiali.io offers numerous benefits for developers and operators working with microservices. Some of these benefits include improved visibility, enhanced performance, better security, and increased productivity. By providing real-time visibility into the microservices environment, Kiali.io enables users to monitor and troubleshoot issues more efficiently. It also provides detailed metrics and tracing information for microservices, enabling users to optimize resource allocation and improve the overall performance of their services. With its advanced security features, Kiali.io helps users secure their microservices environment and detect potential security threats. By simplifying the management and monitoring of microservices, Kiali.io enables users to focus on developing and deploying new services.

Step-by-Step

Pre-Installation

For requirements, please visit https://kiali.io/docs/installation/installation-guide/prerequisites/

Installation

in this article, we will install kiali as an addons on istio

1. Download & Install Istio

curl -L https://istio.io/downloadIstio | ISTIO_VERSION=1.6.14 TARGET_ARCH=x86_64 sh -

vi .bashrc
....
export ISTIO_HOME=~/istio-1.6.14
export PATH=$ISTIO_HOME/bin:$PATH
export KUBECONFIG=/etc/kubernetes/admin.conf
...

source .bashrc
istioctl install --set profile=demo -y

For production, we recommend using the default profile

2. Install kiali addons(profile default)

istioctl install --set profile=default -y
kubectl apply -f samples/addons/kiali.yaml

Check list profile in istio: This Link

Expose Kiali

Port forward(manual)

screen -R forward
kubectl port-forward svc/kiali --address 10.6X.6X.100 20001:20001 -n istio-system
# hit ctrl + A + D

Create gateway dan virtual service

kubectl apply -f - <<EOF
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: kiali-gateway
  namespace: istio-system
spec:
  selector:
    istio: ingressgateway 
  servers:
  - port:
      number: 80
      name: http-kiali
      protocol: HTTP
    hosts:
    - "*"
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: kiali
  namespace: istio-system
spec:
  hosts:
  - "*"
  gateways:
  - kiali-gateway
  http:
  - match:
    - uri:
        prefix: /kiali
    route:
    - destination:
        port:
          number: 20001
        host: kiali
---
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: kiali
  namespace: istio-system
spec:
  host: kiali
  trafficPolicy:
    tls:
      mode: DISABLE
---
EOF

Deploy Simple Microservice for testing

Download Microservice Customer

wget https://github.com/redhat-scholars/istio-tutorial/archive/1.4.x.zip
tar -xvzf 1.4.x.zip
cd istio-tutorial-1.4.x/

Create namespace tutorial

kubectl create namespace tutorial

Deploy customer service

kubectl apply -f <(istioctl kube-inject -f customer/kubernetes/Deployment.yml) -n tutorial
kubectl create -f customer/kubernetes/Service.yml -n tutorial

Expose customer

kubectl create -f customer/kubernetes/Gateway.yml -n tutorial
kubectl get pods -w -n tutorial
kubectl get svc istio-ingressgateway -n istio-system
GATEWAY_URL=$(kubectl get svc istio-ingressgateway -n istio-system|awk '{print $3}'|grep -iv cluster)

Deploy preference service

kubectl apply -f <(istioctl kube-inject -f preference/kubernetes/Deployment.yml)  -n tutorial
kubectl create -f preference/kubernetes/Service.yml -n tutorial
kubectl get pods -w -n tutorial

Deploy preference service

kubectl apply -f <(istioctl kube-inject -f preference/kubernetes/Deployment.yml)  -n tutorial
kubectl create -f preference/kubernetes/Service.yml -n tutorial
kubectl get pods -w -n tutorial

Deploy recommendation service

kubectl apply -f <(istioctl kube-inject -f recommendation/kubernetes/Deployment.yml) -n tutorial
kubectl create -f recommendation/kubernetes/Service.yml -n tutorial
kubectl get pods -w -n tutorial

Testing

curl $GATEWAY_URL/customer

Test loop akses

while true; do sleep 1; curl http://$GATEWAY_URL:32722/customer;done

Kiali dashboard

1. Akses pada browser ke http://10.6X.6X.100:20001/kiali
2. check pada “Graph”, lalu sesuaikan dengan namespace
3. check pada Applications > Namespace: tutorial/bookinfo > customer > inbound Metrics

Conclusion

Kiali.io is an essential tool for developers and operators working with microservices. It provides a comprehensive observability platform that enables users to manage, monitor, and secure their microservices environment more efficiently. By simplifying the management and monitoring of microservices, Kiali.io enables users to focus on developing and deploying new services. With its advanced features and integration capabilities, Kiali.io is a powerful tool that can help users optimize their microservices environment and improve the overall performance of their services.

Our Tagline

#ContinuousLearning

A Step-by-Step Guide to Installing and Using Kiali.io for Microservices Observability was originally published in btech-engineering on Medium, where people are continuing the conversation by highlighting and responding to this story.

OpenIO SDS is a scalable open-source object storage solution.

Overview

Intro

In today’s world, businesses need to store and manage an ever-increasing amount of data. Traditional storage solutions are often expensive and inflexible, leading to a need for more innovative solutions. OpenIo is an open-source object storage solution that has gained popularity in recent years due to its flexibility, scalability, and affordability.

OpenIo is an open-source object storage solution that allows businesses to store, manage, and retrieve large amounts of data with ease. It is based on the Object Storage Device (OSD) concept and is designed to be highly scalable and reliable. It is built on top of Ceph, a distributed storage system, which allows OpenIo to be deployed across multiple servers and data centers, providing redundancy and fault tolerance.

Benefits

One of the key benefits of OpenIO is its flexibility. It can be deployed on-premise, in the cloud, or in a hybrid environment, depending on your needs. This makes it a versatile solution that can adapt to different use cases and workloads.

OpenIO also provides a number of advanced features, including erasure coding, data compression, and data tiering. These features help to optimize storage efficiency, reduce costs, and improve data durability.

Another important aspect of OpenIO is its simplicity. The platform is designed to be easy to use, with a user-friendly web interface and a comprehensive set of APIs. This makes it accessible to a wide range of users, from developers to IT administrators.

OpenIO Compatible with AWS S3 and Swift OpenStack?

OpenIO is compatible with Amazon S3 and OpenStack Swift APIs. This means that you can use OpenIO as a drop-in replacement for these object storage systems, without having to make any changes to your applications or workflows.

OpenIO’s compatibility with these APIs also means that you can take advantage of the many tools, libraries, and applications that are already built to work with Amazon S3 and OpenStack Swift. This can help to simplify the migration process and reduce the learning curve for new users.

In addition to S3 and Swift, OpenIO also provides its own RESTful API, which offers additional features and functionality beyond what is available in S3 and Swift. This API can be used to manage objects, buckets, and policies, as well as to perform advanced operations such as data tiering and erasure coding.

Conclusion

In conclusion, OpenIo is a highly scalable, flexible, and cost-effective object storage solution that can be used to store and retrieve large amounts of unstructured data. Its distributed architecture, support for multiple data access protocols, and highly secure environment make it an ideal choice for developers who need a reliable and flexible storage platform. With its open-source nature, OpenIo also provides developers with the freedom to customize the platform to meet their specific needs, making it a valuable tool for any organization that needs to store and manage large amounts of data.

Our Tagline

#ContinuousLearning

Reference

https://www.openio.io/

https://www.redhat.com/en/topics/storage/object-storage-beginners-guide

https://www.digitalocean.com/community/tutorials/an-introduction-to-object-storage-and-cdn-technology

What is OpenIO ? Object Storage Infrastructure was originally published in btech-engineering on Medium, where people are continuing the conversation by highlighting and responding to this story.

Intro

JumpServer is an open-source, web-based SSH (Secure Shell) and RDP (Remote Desktop Protocol) gateway that provides secure access to remote servers and network devices.

JumpServer acts as a centralized management system that allows administrators to control and audit access to critical IT infrastructure. It provides a unified platform for managing remote access and includes features such as user and session management, activity logging, and two-factor authentication.

JumpServer is built on Python and Django, and is available as a Docker container or can be installed on a Linux server. The platform integrates with various authentication systems, including Active Directory, LDAP, and SAML, and supports a range of protocols, including SSH, RDP, and Telnet.

JumpServer is designed for use by IT professionals, system administrators, and DevOps teams, and can be used to manage access to servers, networking devices, and other critical infrastructure. It is particularly useful for organizations that require strict security and compliance standards, as it provides granular control over access and activity tracking.

Practical

Installation

The following are the steps to install JumpServer:

• Download jumpserver files

mkdir jumpserver
cd jumpserver
wget https://github.com/jumpserver/installer/releases/download/v2.28.5/jumpserver-installer-v2.28.5.tar.gz
tar -xf jumpserver-installer-v2.28.5.tar.gz
cd jumpserver-installer-v2.28.5/

• Install jumpserver, will be install an mariadb and redis as container in server

./jmsctl.sh install

docker ps

• Change configuration of web container from default port (80) to other port (8099). This step is optional if default port used by other app or service

vi compose/docker-compose-app.yml
...
web:
    image: jumpserver/web:${VERSION}
    container_name: jms_web
    ulimits:
      core: 0
    restart: always
    tty: true
    environment:
      HTTP_PORT: ${HTTP_PORT:-80}
      USE_IPV6: ${USE_IPV6:-0}
      CLIENT_MAX_BODY_SIZE: ${CLIENT_MAX_BODY_SIZE:-4096m}
    ports:
      - 8099:80
...

• Start Jumpserver, this step will create other services of jumpserver, like web, koko, lion, core, and magnus

./jmsctl.sh start

docker ps

• List container for jumpserver app

• Web UI Jumpserver

Web Modification

1. Login page text and forward link

• Go inside jms_core container

docker exec -it jms_core bash

• To edit login page text

vi apps/jumpserver/context_processor.py
...
default_interface = dict((
    ('logo_logout', static('img/logo.png')),
    ('logo_index', static('img/logo_text.png')),
    ('login_image', static('img/login_image.jpg')),
    ('favicon', static('img/facio.ico')),
    ('login_title', _('{EDIT_THIS_SECTION}')),
    ('theme', 'classic_green'),
    ('theme_info', {}),
))
...

• To edit forward link

vi apps/authentication/templates/authentication/login.html
...
        <a href="{% if not XPACK_ENABLED %}https://{EDIT_THIS_LINK}/{% endif %}">
            <img src="{{ INTERFACE.login_image }}" class="right-image" alt="screen-image"/>
        </a>
...

• Restart service (the static file of jumpserver will updated to default)

./entrypoint.sh restart web

2. Login page image

• Copy Image to jms_web container static file

docker cp login_image.jpg jms_web:/opt/jumpserver/data/static/img/login_image.jpg

3. Logo and favicon

• Copy image logo and favicon file to jms_web container static file

#favicon
docker cp adinusa-logo-color.png jms_web:/opt/jumpserver/data/static/img/facio.ico

#logo
docker cp adinusa-logo-color.png jms_web:/opt/jumpserver/data/static/img/logo.png

4. Logo Text

• Copy image logo text to jms_web container static file

docker cp logo-acad-trans.png jms_web:/opt/jumpserver/data/static/img/logo_text.png

5. Chinese Text, when user will connect to assets

• Edit assets in jms_web container

docker ps | grep jms_web
docker exec -it jms_web bash

cd /opt/luna/assets/i18n
cp zh.json zh.json.bkp
cp en.json zh.json

exit

• Edit locale LC_MASSAGES in jms_web container

docker ps | grep koko
docker exec -it jms_koko bash
cp locale/zh_CN/LC_MESSAGES/koko.po locale/zh_CN/LC_MESSAGES/koko.po.bkp
cp locale/en_US/LC_MESSAGES/koko.po locale/zh_CN/LC_MESSAGES/koko.po

exit

docker stop jms_koko
docker start jms_koko

By Razzaaq Arditian, Research Team Btech

Our Tagline

# Together is Better & Continuous Learning

Reference:

• JumpServer
• JumpServer 文档

Modifying Jumpserver UI was originally published in btech-engineering on Medium, where people are continuing the conversation by highlighting and responding to this story.

Kubevirt is an open-source virtualization platform that allows users to deploy virtual machines (VMs) in a Kubernetes cluster. It provides a powerful solution for integrating microservices and virtual machines, enabling users to take advantage of the benefits of both technologies. In this article, we will provide an overview of Kubevirt and guide you through the process of deploying a VM in a Kubernetes cluster using Kubevirt.

Overview

Kubevirt extends the Kubernetes API to provide a platform for managing virtual machines alongside containers. It enables users to deploy, run, and manage VMs as Kubernetes objects, leveraging Kubernetes’ advanced scheduling, networking, and storage capabilities. Kubevirt supports a range of hypervisors, including KVM, QEMU, and VirtualBox, and provides features such as live migration, snapshots, and storage management.

Kubevirt Components

Kubevirt consists of several components that work together to provide a platform for managing VMs in a Kubernetes cluster. These components include:

1. API Server: The Kubevirt API server extends the Kubernetes API to support VMs as a first-class object. It provides a RESTful API for creating, updating, and deleting VMs and their associated resources.
2. Virtual Machine Controller: The Virtual Machine Controller (VMC) is responsible for creating and managing VMs. It interacts with the Kubernetes API server to create VMs and their associated resources, such as virtual disks, networks, and interfaces.
3. Virtual Machine Instance Controller: The Virtual Machine Instance Controller (VMIC) is responsible for managing the lifecycle of VMs. It interacts with the VMC to create and start VMs, and monitors their status to ensure they are running correctly.
4. CDI: The Containerized Data Importer (CDI) is a Kubernetes-native tool for managing the import and export of data between VMs and containers. It enables users to import data into VMs from container images and export data from VMs to container images.
5. Virt-Handler: Virt-Handler is a lightweight, secure runtime for running VMs. It runs as a privileged container in the Kubernetes cluster and provides a secure execution environment for VMs.

Installation

Lab Environment

• Kubernetes Cluster 1 Master 2 Node, 1 Nfs Storage
• Each Node 8 CPU, 16GB Ram
• Kubernetes Version 1.26.3

Step-by-Step

Deploy Kubevirt

KubeVirt can be installed using the KubeVirt operator, which manages the lifecycle of all the KubeVirt core components.

• Use kubectlto deploy the KubeVirt operator:

export VERSION=$(curl -s <https://api.github.com/repos/kubevirt/kubevirt/releases> | grep tag_name | grep -v -- '-rc' | sort -r | head -1 | awk -F': ' '{print $2}' | sed 's/,//' | xargs) echo $VERSION kubectl create -f <https://github.com/kubevirt/kubevirt/releases/download/${VERSION}/kubevirt-operator.yaml>

• Again use kubectl to deploy the KubeVirt custom resource definitions:

kubectl create -f <https://github.com/kubevirt/kubevirt/releases/download/${VERSION}/kubevirt-cr.yaml>

Verify Components

• Check the deployment:

kubectl get kubevirt.kubevirt.io/kubevirt -n kubevirt -o=jsonpath="{.status.phase}"  

... 
Deployed

• Check the components:

kubectl get all -n kubevirt
...
Warning: kubevirt.io/v1 VirtualMachineInstancePresets is now deprecated and will be removed in v2.
NAME                                   READY   STATUS    RESTARTS   AGE
pod/virt-api-9db4877f9-ts4f7           1/1     Running   0          8m24s
pod/virt-api-9db4877f9-v4krt           1/1     Running   0          8m24s
pod/virt-controller-6b69b5b887-29gqs   1/1     Running   0          7m59s
pod/virt-controller-6b69b5b887-kvjkw   1/1     Running   0          7m59s
pod/virt-handler-28rrj                 1/1     Running   0          7m59s
pod/virt-handler-c487h                 1/1     Running   0          7m59s
pod/virt-operator-7848c6bbc7-8zwxp     1/1     Running   0          9m15s
pod/virt-operator-7848c6bbc7-dxn5r     1/1     Running   0          9m15s

NAME                                  TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)   AGE
service/kubevirt-operator-webhook     ClusterIP   10.100.18.217    <none>        443/TCP   8m27s
service/kubevirt-prometheus-metrics   ClusterIP   None             <none>        443/TCP   8m27s
service/virt-api                      ClusterIP   10.105.255.140   <none>        443/TCP   8m27s
service/virt-exportproxy              ClusterIP   10.107.196.14    <none>        443/TCP   8m27s

NAME                          DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
daemonset.apps/virt-handler   2         2         2       2            2           kubernetes.io/os=linux   7m59s

NAME                              READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/virt-api          2/2     2            2           8m24s
deployment.apps/virt-controller   2/2     2            2           7m59s
deployment.apps/virt-operator     2/2     2            2           9m15s

NAME                                         DESIRED   CURRENT   READY   AGE
replicaset.apps/virt-api-9db4877f9           2         2         2       8m24s
replicaset.apps/virt-controller-6b69b5b887   2         2         2       7m59s
replicaset.apps/virt-operator-7848c6bbc7     2         2         2       9m15s

NAME                            AGE     PHASE
kubevirt.kubevirt.io/kubevirt   8m53s   Deployed

Virtctl

KubeVirt provides an additional binary called virtctl for quick access to the serial and graphical ports of a VM and also handle start/stop operations.

• virtctlcan be retrieved from the release page of the KubeVirt github page.

VERSION=$(kubectl get kubevirt.kubevirt.io/kubevirt -n kubevirt -o=jsonpath="{.status.observedKubeVirtVersion}")
ARCH=$(uname -s | tr A-Z a-z)-$(uname -m | sed 's/x86_64/amd64/') || windows-amd64.exe
echo ${ARCH}
curl -L -o virtctl https://github.com/kubevirt/kubevirt/releases/download/${VERSION}/virtctl-${VERSION}-${ARCH}
chmod +x virtctl
sudo install virtctl /usr/local/bin

Check Version

~# virtctl version
Client Version: version.Info{GitVersion:"v0.59.0-alpha.2", GitCommit:"6f97adc2fd3144cb9813363e3bb147c39c2260af", GitTreeState:"clean", BuildDate:"2023-01-03T16:07:04Z", GoVersion:"go1.19.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{GitVersion:"v0.59.0-alpha.2", GitCommit:"6f97adc2fd3144cb9813363e3bb147c39c2260af", GitTreeState:"clean", BuildDate:"2023-01-03T16:07:04Z", GoVersion:"go1.19.2", Compiler:"gc", Platform:"linux/amd64"}

Conclusion

Kubevirt is a powerful solution for integrating microservices and virtual machines, enabling users to take advantage of the benefits of both technologies. By deploying VMs in a Kubernetes cluster, users can leverage Kubernetes’ advanced features for managing containers and build hybrid applications that combine microservices and traditional applications. Kubevirt also simplifies the management of VMs, providing a single interface for managing both VMs and containers. With its advanced features and integration capabilities, Kubevirt is an essential tool for users looking to build and manage complex workloads that include both microservices and virtual machines.

By Fauzan Rafi, Research Team Btech

Our Tagline

#ContinuousLearning

Reference

KubeVirt quickstart with cloud providers | KubeVirt.io

Deploy your VM in Kubernetes Cluster using Kubevirt was originally published in btech-engineering on Medium, where people are continuing the conversation by highlighting and responding to this story.

Intro

OpenStack Dashboard, also known as Horizon, is a web-based graphical user interface (GUI) that allows users and administrators to manage and monitor OpenStack cloud environments. It provides a centralized dashboard for managing compute, storage, and networking resources, as well as other OpenStack services like Keystone (identity management), Neutron (networking), and Glance (image management).

Horizon provides a user-friendly interface for common OpenStack operations, such as launching instances, creating volumes, configuring networks, and managing security groups. It also allows users to create custom dashboards and widgets for their specific needs.

Horizon is extensible and customizable, and provides APIs for integrating with other tools and services. It supports multiple authentication backends, including OpenStack’s own identity service (Keystone), LDAP, and external identity providers like Google and GitHub.

Overall, Horizon is a powerful tool for managing OpenStack environments, especially for users who prefer a GUI over command-line tools.

Yuyu is a plugin in openstack that makes it easy for you to manage your openstack bills.

Yuyu have two components for running bellow :

1. Yuyu Server

Yuyu server provide ability to manage openstack billing by listening to every openstack event. Yuyu server is a required component to use Yuyu Dashboard. There are 3 main component in Yuyu server: API, Cron, Event Monitor. More detail about Yuyu server at https://github.com/btechpt/yuyu

• Yuyu API : Main component to communicate with Yuyu Dashboard.
• Yuyu Cron : Provide invoice calculation and rolling capabilities that needed to run every month.
• Yuyu Event Monitor : Monitor event from openstack to calculate billing spent.

2. Yuyu Dashboard

Yuyu dashboard is a panel at openstack dashboard that is used to manage your openstack bills. More detail about Yuyu server at https://github.com/btechpt/yuyu_dashboard

Containerize refers to the process of creating a container image that includes an application and its dependencies, which can be run in a containerized environment.

Containers are a lightweight, standalone executable package that includes everything needed to run an application, including code, runtime, system tools, libraries, and settings. By containerizing an application, it can be easily moved between different environments without worrying about compatibility issues, and it can be run consistently across different infrastructure, from development to production.

Containerization is often used in DevOps and cloud computing to improve deployment speed, scalability, and portability. By containerizing applications, organizations can quickly build, deploy, and manage applications at scale, and they can more easily adopt new technologies and infrastructure changes. Popular containerization tools include Docker, Kubernetes, and container orchestration platforms like Amazon ECS and Google Kubernetes Engine (GKE).

Practical

1. Containerize an Horizon

The following are the steps to containerize an horizon service or Openstack Dashboard:

• Install docker on machine or server, for this section we will use docker as tool to containerize an app

sudo apt update
sudo apt install docker.io

• Clone horizon file to machine, we will use zed version of horizon openstack

git clone https://opendev.org/openstack/horizon -b stable/zed --depth=1
ls

• Modified local_settings.py on horizon directory to new configuration of horizon. The os.environ.get will read value from docker-compose.yml later

cp horizon/openstack_dashboard/local/local_settings.py.example horizon/openstack_dashboard/local/local_settings.py
vi horizon/openstack_dashboard/local/local_settings.py
...
DEBUG = False

ALLOWED_HOSTS = ['*']

CACHES = {
    'default': {
        'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
        'LOCATION': '127.0.0.1:11211',
    },
}

OPENSTACK_HOST = os.environ.get('OPENSTACK_HOST')
OPENSTACK_KEYSTONE_URL = "http://%s/v3" % OPENSTACK_HOST

AVAILABLE_THEMES = [
    ('default', 'Default', 'themes/default'),
    ('material', 'Material', 'themes/material'),
    ('example', 'Example', 'themes/example'),
]
...

• Edit requirements file, add horizon and memcached version

vi horizon/requirements.txt
...
horizon===23.0.0
python-memcached===1.59
...

• Create Dockerfile, to create an container image of app, with base ubuntu image and apache2 app to run an horizon

vi Dockerfile
...
FROM ubuntu:jammy

COPY horizon/ /var/www/html/horizon/

WORKDIR /var/www/html/horizon/

RUN apt-get update && apt install python3-pip -y \
    && pip3 install -r requirements.txt \
    && apt install apache2 libapache2-mod-wsgi-py3 -y

RUN python3 ./manage.py collectstatic --no-input \
    && python3 ./manage.py make_web_conf --wsgi --force \
    && python3 ./manage.py make_web_conf --apache > /etc/apache2/sites-available/horizon.conf \
    && rm /etc/apache2/sites-enabled/000-default.conf

RUN a2ensite horizon

RUN chown -R www-data:www-data openstack_dashboard/local/.secret_key_store \
    && chown -R www-data:www-data static/ \
    && chmod a+x openstack_dashboard/horizon_wsgi.py

EXPOSE 80

CMD service memcached start && apachectl -D FOREGROUND
...

• Create an image from Dockerfile

docker build -t horizon:zed .

• Verify an new image on machines

docker image ls

• Test running horizon image with docker-compose.yml file

vi docker-compose.yml
...
version: "3.9"

services:
  horizon:
    image: horizon:zed
    ports:
      - "80:80"
    volumes:
      - /var/log/horizon/:/var/log/apache2:rw
    environment:
      OPENSTACK_HOST: 172.168.22.100:5000 ##Edit with your openstack keystone API
...

docker-compose up -d
docker ps

• Verifiy horizon / openstack dashboard, access with machine IP Address

2. Add yuyu-dashboard on horizon image container

The following are the steps to add yuyu-dashboard on horizon image container:

• Clone yuyu-dashboard file

git clone https://github.com/Yuyu-billing/yuyu_dashboard.git

• Edit local_settings.py to add yuyu api configuration, YUYU_URL is filled by IP and port of YUYU_API

vi horizon/openstack_dashboard/local/local_settings.py
...
#add this line
YUYU_URL= os.environ.get('YUYU_SERVER')
CURRENCIES = ('IDR',)
DEFAULT_CURRENCY = "IDR"
...

• Create an Dockerfile to creating horizon yuyu dashboard image with base image horizon:zed we are creating before.

vi Dockerfile
...
FROM horizon:zed

RUN pip3 install django-money==2.0.1 && pip3 install python-dateutil==2.8.2 && pip3 install Pillow>=6.2.0

COPY horizon/openstack_dashboard/local/local_settings.py /var/www/html/horizon/openstack_dashboard/local/local_settings.py

RUN mkdir /var/www/html/horizon/openstack_dashboard/dashboards/yuyu/
COPY yuyu_dashboard/yuyu/ /var/www/html/horizon/openstack_dashboard/dashboards/yuyu/
COPY yuyu_dashboard/yuyu/local/enabled/_6100_yuyu.py /var/www/html/horizon/openstack_dashboard/local/enabled/_6100_yuyu.py
COPY yuyu_dashboard/yuyu/local/enabled/_6101_admin_billing_panel_group.py /var/www/html/horizon/openstack_dashboard/local/enabled/_6101_admin_billing_panel_group.py
COPY yuyu_dashboard/yuyu/local/enabled/_6102_admin_billing_overview.py /var/www/html/horizon/openstack_dashboard/local/enabled/_6102_admin_billing_overview.py
COPY yuyu_dashboard/yuyu/local/enabled/_6103_admin_billing_price_configuration.py /var/www/html/horizon/openstack_dashboard/local/enabled/_6103_admin_billing_price_configuration.py
COPY yuyu_dashboard/yuyu/local/enabled/_6104_admin_billing_setting.py /var/www/html/horizon/openstack_dashboard/local/enabled/_6104_admin_billing_setting.py
COPY yuyu_dashboard/yuyu/local/enabled/_6104_admin_billing_setting.py /var/www/html/horizon/openstack_dashboard/local/enabled/_6104_admin_billing_setting.py
COPY yuyu_dashboard/yuyu/local/enabled/_6105_admin_billing_projects_invoice.py /var/www/html/horizon/openstack_dashboard/local/enabled/_6105_admin_billing_projects_invoice.py
COPY yuyu_dashboard/yuyu/local/enabled/_6106_admin_notification_center.py /var/www/html/horizon/openstack_dashboard/local/enabled/_6105_admin_notification_center.py
COPY yuyu_dashboard/yuyu/local/enabled/_6107_admin_billing_projects_balance.py /var/www/html/horizon/openstack_dashboard/local/enabled/_6107_admin_billing_projects_balance.py

COPY yuyu_dashboard/yuyu/local/enabled/_6111_project_billing_panel_group.py /var/www/html/horizon/openstack_dashboard/local/enabled/_6111_project_billing_panel_group.py
COPY yuyu_dashboard/yuyu/local/enabled/_6112_project_billing_overview.py /var/www/html/horizon/openstack_dashboard/local/enabled/_6112_project_billing_overview.py
COPY yuyu_dashboard/yuyu/local/enabled/_6113_project_billing_usage_cost.py /var/www/html/horizon/openstack_dashboard/local/enabled/_6113_project_billing_usage_cost.py
COPY yuyu_dashboard/yuyu/local/enabled/_6114_project_billing_invoice.py /var/www/html/horizon/openstack_dashboard/local/enabled/_6114_project_billing_invoice.py
COPY yuyu_dashboard/yuyu/local/enabled/_6115_project_billing_setting.py /var/www/html/horizon/openstack_dashboard/local/enabled/_6115_project_billing_setting.py
COPY yuyu_dashboard/yuyu/local/enabled/_6116_project_balance.py /var/www/html/horizon/openstack_dashboard/local/enabled/_6116_project_balance.py

CMD service memcached start && apachectl -D FOREGROUND
...

• Build image with this Dockerfile, and list image on machine

docker build -t yuyu-horizon:v1 .

• Verify an new image on machines

docker image ls

• Test running horizon image with docker-compose.yml file

vi docker-compose.yml
...
version: "3.9"
services:
  yuyu_dashboard:
    image: yuyu-horizon:v1
    ports:
      - "80:80"
    volumes:
      - /var/log/horizon/:/var/log/apache2:rw
    environment:
      OPENSTACK_HOST: 172.168.22.100:5000  ##Edit with your openstack keystone API
      YUYU_SERVER: http://172.168.22.10:8182 ##Edit with your YUYU Server API
...

docker-compose up -d
docker ps

• Verify horizon and yuyu dashboard, open with browser and access with machine IP Address

By Razzaaq Arditian, Research Team Btech

Our Tagline

# Together is Better & Continuous Learning

Reference:

• Manual installation
• Yuyu - Yuyu.io

Containerize Horizon and Yuyu Dashboard was originally published in btech-engineering on Medium, where people are continuing the conversation by highlighting and responding to this story.

Intro

Prometheus Libvirt Exporter is an open-source software used for monitoring and collecting metrics from virtual machines (VMs) that are running using the Libvirt virtualization toolkit.

Libvirt is a toolkit that is used for managing virtualization on Linux operating systems. In this context, the Prometheus Libvirt Exporter allows system administrators to monitor VM performance in real-time and collect data such as CPU usage, memory usage, disk I/O, and network I/O.

The exporter works by accessing the Libvirt API to extract information about the VMs and then exposing the information as Prometheus metrics. The Prometheus server can then scrape these metrics and store them in its time-series database for later querying and visualization using tools such as Grafana.

Using Prometheus Libvirt Exporter, administrators can gain insights into the performance of their VMs and identify potential bottlenecks or issues that could affect their application or workload. By monitoring and analyzing this data, administrators can take proactive measures to optimize VM performance and ensure that their applications are running smoothly.

Practical

How to install Prometheus Libvirt Exporter on server?

1. CentOS

If the OS used on the server is not using the release-stream version, then the OS must be changed to the release-stream version using the following method.

sudo dnf update
cat /etc/centos-release

sudo dnf in centos-release-stream
sudo dnf swap centos-linux-repos centos-stream-repos

sudo dnf repolist
sudo dnf distro-sync
sudo dnf update

cat /etc/centos-release

Installation of prometheus-libvirt-exporter with the following steps.

# install snapd
sudo yum install epel-release
sudo yum install snapd
sudo systemctl enable --now snapd.socket
sudo ln -s /var/lib/snapd/snap /snap

# install libvirt_exporter
sudo snap install prometheus-libvirt-exporter

# verify
systemctl status snap.prometheus-libvirt-exporter.daemon.service
netstat -tupln | grep 9177
curl localhost:9177

2. Ubuntu

Installation of prometheus-libvirt-exporter on Ubuntu Operation System with the following steps.

# install snapd
sudo apt update
sudo apt install snapd

# install libvirt-exporter
sudo snap install prometheus-libvirt-exporter
sudo systemctl status snap.prometheus-libvirt-exporter.daemon.service
snap connect prometheus-libvirt-exporter:libvirt

# verify
systemctl status snap.prometheus-libvirt-exporter.daemon.service
netstat -tupln | grep 9177
curl localhost:9177

By Razzaaq Arditian, Research Team Btech

Our Tagline

# Together is Better & Continuous Learning

Reference:

Install prometheus-libvirt-exporter on Linux | Snap Store

• https://www.cyberciti.biz/howto/upgrade-migrate-from-centos-8-to-centos-stream-conversion/

Prometheus Libvirt Exporter was originally published in btech-engineering on Medium, where people are continuing the conversation by highlighting and responding to this story.