Prepare the environment to install the ISO image in the Hyper-V

In my Bare-Metal the Hyper-V hypervisor is already installed. Here you can find the method of installing it:

https://learn.microsoft.com/en-us/training/modules/configure-manage-hyper-v/2-define-hyper-v

So, you need to enable the Hyper-V feature in Windows by executing the command in PowerShell:

PS C:\WINDOWS\system32> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

After we have successfully installed Hyper-V, it is important to create and configure the virtual network. To prepare the environment to be able to install SUSE, I used Windows PowerShell to create network adapter using commands:

• Get-NetAdapter

• Import-Module Hyper-V

• $ethernet = Get-NetAdapter -Name "Ethernet"

• New-VMSwitch -Name "virtuelles Netzwerk" -NetAdapterName $ethernet.Name -AllowManagementOS $true -Notes "Geteiltes virtuelles Netzwerkinterface

The other step is to dedicate the storage space for the SUSE VM. Steps I followed are:

 Create the directory for the SLES:

I have dedicated 50GB of storage:

After the environment preparation, we downloaded the SUSE SLE-15-SP6-Full-x86_64-GM-Media1.iso iso image from the SUSE official website: https://www.suse.com/download/sles/ and saved locally:

Then we continued to install the SUSE over Hyper-V Manager following the steps:

Select new and then Virtual Computer

Name the VM and continue.

Select Generation 1 and continue.

Setting the memory. In our case we have dedicated 4096MB.

Setting the memory. In our case we have dedicated 4096MB.

Naming the virtual storage connection, select the path and setting the amount of storage.

After the configurations above, we started via PowerShell the VM with the command Start-VM -Name “sles”, and the installation began. The starting installation is shown in this picture below:

In this image is shown the beginning of the installation.

Initializing Network Configuration.

It will be updating the Installer…

Here we need to set the language and to select the Product.

We selected German language and the SUSE Linux Enterprise Server 15 SP6.

Selecting the License agreement and continue.

Here are some modules I have selected for the late use.

Installation the Add-On-Products.

In this case I have selected the HA-Node.

This is how the partitioning looks like.

Setting the time zone and continue.

Setting the local username and password.

Continue with installation.

Confirming the installation.

Installation process…

To be able to start with a new SUSE VM, we have selected the Boot Linux System.

Activating the SUSE GNOME Desktop

To be able to use SUSE GUI we need to install the GNOME desktop packages showing below:

Then installing GNOME desktop pattern:

And we need to system target to graphical.target

SUSE GUI image Is shown below:

Register the SUSE VM for accessing repositories including Package Hub

To be able to install the packages we need, it is important to register our system on SUSE Customer Center and get the registration code. SUSE offers a two-month free subscription code.

In the image below showing the repositories which are not activated:

After Subscription evaluation we can find the registration code to be able to access the SUSE repository.

Now we can follow the steps of how to register our system with the registration using the command:

Then we can enable the Base-system Module repository:

And after enabling the repositor, we refresh them to update the metadata:

All repositories have been refreshed

With the command we can see repositories status.

zypper repos | egrep -E “Yes”

Ansible installation in SLES 15 SP6

We can install ansible in SLES 15 SP6 using package-hub repository:

https://packagehub.suse.com/search/?q=ansible

Before going to install it, possible we need to check which SUSE service-pack version is installed in our environment.

And then finding the right ansible release version in the web-page https://packagehub.suse.com/packages/ansible/

Check for the connection status.

Zypper-Update

We need to check if the Package_Hub is activated with the command shown below:

zypper lr -u | egrep -E “Package_Hub”

If it’s not, we can do it as it is shown:

We can search for ansible with the command in the image above.

Here we can see that ansible with the status “not installed”

Starting the ansible installation. After the installation we can check the version:

And, like this to see the Status:

Conclusion

This article provides a comprehensive guide for IT administrators seeking to streamline their operations and improve efficiency by integrating SUSE Linux Enterprise Server (SLES) and Ansible in virtualized environments. By leveraging the powerful automation capabilities of Ansible, IT teams can automate various tasks, such as provisioning, configuration, and deployment, significantly reducing manual effort and potential human error. The article delves into specific use cases and best practices, making it a valuable resource for enterprises of all sizes looking to modernize their IT infrastructure and achieve greater agility.

The post Installation von SUSE SLES 15 SP6 in Hyper-V und anschließende Installation von Ansible appeared first on Rhein-Ruhr-Informatik.

Overview

Prior to commencing the expansion process, it is imperative to comprehend that extending a virtual disk within the Hyper-V environment entails augmenting its allocated capacity. This action does not inherently result in the automatic population of the supplementary space with data. To effectively utilize the additional storage, it is necessary to manually extend the virtual machine's partitions and file systems, thereby enabling them to occupy the newly allocated space.

Before we dive into the steps, let's clarify why we might want to expand a Hyper-V VM's hard disk. This action is typically necessary when the virtual machine's existing storage capacity is insufficient to accommodate growing data or applications.

Access Hyper-V Manager

Windows 10/11: Search for "Hyper-V Manager" in the Start menu and open it.

First we need to shutdown the server:

On the virtual computer we click on the settings to configure the disk:

Under the Hardware menu we select the storage and on the right hand side we click on the Edit button to be able to continue this the next steps.

On the left hand side screen we select the Action, select Expand and then Continue:

As we see in the picture below under the Configure Data in the right-hand side there are 50GB. Here we can increase the size of the storage.

It is increased to 60GB as shown in the picture below:

After clickin OK, we have this picture in which we click again OK.

I have started the virtual machine:

After this steps in Hyper-V Manager, we start the virtual machine and going to extend LVM.

Via Putty tool we have to access our virtual machine:

Start by checking your root filesystem free space with df -hT. Our root disc is 62%. Now we gonna follow the steps to allocate 10 more GB to increase the percentage of our filesystem.

We enter the following commands parted -l adm type Fix to display the list of disks and partitions:

In the picture below we see that there is an error named: GPT PMBR size mismatchFirst we can fix it by typing the command correctin the error.

Now everything sims to be fine.

Now we can continue to extend our logical volume on /dev/sda3 filesystem as shown below:

First we use the command fdisk /dev/sda and continue with the other command showing below.

Now it is required to reboot the system

To check for existing free space on your Volume Group (where it is left by the installer default settings), run the command vgdisplay and lvdisplay check for free space.

After the computer has been restarted, we can use the command
lvextend -l +100%FREE /dev/ubuntu-vg/ubuntu-lv
to extend the partition.

At this point you have increased the size of the block volume where your root filesystem resides, but you still need to extend the filesystem on top of it. First, run lsblk aus:

To verify our root file system, then run
resize2fs /dev/mapper/ubuntu--vg-ubuntu--lv
to extend our filesystem:

Now as we see our LVM's size has increased to 48GB.

Conclusion

Overall, this guide provides a step-by-step process for expanding a Hyper-V VM's disk, addressing common challenges and ensuring optimal storage utilization

The post Standard-Ubuntu-virtuelles LVM in Hyper-V erweitern appeared first on Rhein-Ruhr-Informatik.

Overview

Jenkins is a highly popular open-source web application designed to streamline and automate the software development process. It's a cornerstone tool for Continuous Integration (CI) and Continuous Delivery (CD) pipelines, allowing developers and DevOps teams to build, test, and deploy applications efficiently..

Installing Jenkins     

There are many methods to install Jenkins in Ubuntu. Before we go to install Jenkins, we need to have already installed Java JRE (Java Runtime Environment). OpenJDK is an open-source implementation of the Java Platform It provides the core components necessary for running Java applications.

We will work on Ubuntu-22.04 version:

Let’s install OpenJDK-11 release. The steps to install this distribution in our system via putty interface. We going to download the file OpenJDK-11 as archived file from the official website [https://jdk.java.net/archive/] locally,

Then via WinSCP app we can access our Linux (Ubuntu) environment to transfer it as Binary file.

After we have the archive file in our environment, we need first to extract it via cli.

tar -xvzf openjdk-17.0.1_linux-x64_bin.tar.gz

As we have the file in just read and write permission, we are going to give it the execute permission like:

Then when we list, it gives:

Jetzt können wir OpenJDK-17 mit dem folgenden Befehl installieren:

sudo apt install openjdk-17-jdk -y

Da jedoch OpenJDK-17 bereits in meiner Umgebung installiert ist, wird die neueste Version angezeigt.

After Installation we check if the Jenkins service is active.

  
  root@master:/home/bekber1# systemctl
  status jenkins
  ● jenkins.service
  - Jenkins Continuous Integration Server
      
  Loaded: loaded (/lib/systemd/system/jenkins.service; enabled; vendor
  preset: enabled)
      
  Active: active (running) since Tue 2024-09-03 06:34:13 UTC; 2h 58min
  ago
    
  Main PID: 18413 (java)
      
   Tasks: 63 (limit: 2178)
      
  Memory: 791.1M
      
  CGroup: /system.slice/jenkins.service
               └─18413 /usr/bin/java
  -Djava.awt.headless=true -jar /usr/share/java/jenkins.war
  --webroot=/var/cache/jenkins/war --httpPort=xxx
  

So, we can see that Jenkins service is Active. Now to be able to access the Jenkins from the web browser we need to setting up the default UFW firewall.

Open port 8080 by running the following commands:

 
  root@master:/home/bekber1#
  ufw allow 8080
  Rule
  added
  Rule
  added (v6)
   
  root@master:/home/bekber1#
  ufw status
  Status:
  active
 

In the putty cli we use the command to get the admin password:

We copy the password provided by default and paste it in the filed shown in the picture above and then click Continue button. After this we getting started:

After the installation and configuration, we must create our first Admin user as show in the picture below:

Now we can click Save and Continue and then getting the Jenkins URL as shown below:

Now Jenkins is ready, and we can start and using it.

How to change Jenkins Administrator password if we lost it:

If we forget the Jenkins Admin password for web browser, to reset it we should follow the steps as below:

First, we need to find where is the config.xml file is located in:

root@master:/home/bekber1# cd /var/lib/jenkins/ 

First, we need to find where is the config.xml file is located in:

root@master:/var/lib/jenkins# vim config.xml

So, concatonating this file in cli you can see inside the line named: "<useSecurity>true</useSecurity>" We change it fromtruetofalseand we restart the Jenkins service afterwards like:

systemctl restart jenkins 

After these steps we refresh the web browser page and we will get inside the Jenkins page to make the changes because it is unsecured.

First step is to choose theManage Jenkinsand after we click onSecurity Realm“ „Jenkins‘ own user database. We save it and close.

After this we can go to the underManage Jenkins“ -> „Security“ -> „Userswe click onSettingsclick and underPasswordwe change the password.

How-create-agent-for-built-in-node

In Jenkins, agents are essential for executing build jobs. Steps that we should follow are:

We have to configuring .ssh inside the /var/lib/jenkins/.ssh/known_host

- we create the folder named .ssh

root@master:/var/lib/jenkins#mkdir -p /var/lib/jenkins/.ssh
root@master:/var/lib/jenkins# chown -R jenkins:jenkins .ssh
root@master:/var/lib/jenkins#ssh-keyscan -H agent1 >> /var/lib/jenkins/.ssh/known_host

If doesn't work as e.g.

root@master:/etc/ssh# ssh-keyscan -H agent1 >> /var/lib/jenkins/.ssh/known_hosts
getaddrinfo agent1: Temporary failure in name resolution
getaddrinfo agent1: Temporary failure in name resolution
getaddrinfo agent1: Temporary failure in name resolution
getaddrinfo agent1: Temporary failure in name resolution
getaddrinfo agent1: Temporary failure in name resolution

we need to add agent1 server ip in the /etc/hosts-Datei hinzufügen. 

To find the agent1 ip address, we use the command:

root@master:/etc/ssh# dig agent1
 
; <<>> DiG 9.16.48-Ubuntu <<>> agent1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 15329
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
 
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;agent1.                                IN      A
 ;; Query time: 0 msec
;; SERVER: <MyIpAddress>#53(<MyIpAddress>)
;; WHEN: Sun Mar 10 10:33:06 UTC 2024
;; MSG SIZE  rcvd: 35

and edit the /etc/hosts with the nano editor like:

root@master:/etc# cat hosts
<MyIpAddress>localhost
<MyIpAddress>linux-0
<MyIpAddress>master
<MyIpAddress>node1
<MyIpAddress>node2
<MyIpAddress> agent1    ----------> mit dem Nano- oder Vim-Editor müssen wir die IP-Adresse von agent1 hinzufügen.
/etc/hosts
# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

Nach Ausführung des Befehls ssh-keyscan -H agent1 >> /var/lib/jenkins/.ssh/known_hosts erhalten wir die Auflösung:

root@master:/etc# ssh-keyscan -H agent1 >> /var/lib/jenkins/.ssh/known_hosts
# agent1:22 SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.11
# agent1:22 SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.11
# agent1:22 SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.11
# agent1:22 SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.11
# agent1:22 SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.11

Jenkins agent1 in port 22 is resolved:

root@master:/etc# cd /var/lib/jenkins/.ssh/
root@master:/var/lib/jenkins/.ssh# ll
total 12
drwxr-xr-x  2 jenkins jenkins 4096 Mar 10 10:11 ./
drwxr-xr-x 15 jenkins jenkins 4096 Mar 10 10:05 ../
-rw-r--r--  1 jenkins jenkins  978 Mar 10 10:36 known_hosts

root@master:/var/lib/jenkins/.ssh# cat known_hosts
|1|UMnpRmZeDMTxf8bAmPYanyzeE54=|C7tpVgwzVbu7FDJG4fUiDVN3L4I= ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBAunO9x3A5IInM2Qqqf4wwWBEokfH8pRiMVcrjNTNn7hCZrgi75hbRbV+dG8hy2xhUtDlywP0k0S/+qpSwoVd7E=
|1|nPGx2tNNjsRAU6ZYf7UqlI1iGcM=|TqWQT18KAS56FgREOVEfVUvvILQ= ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDTy0gPfw8tQ7T2VkFlp82regznVnrZx7tlsgLqlOWVqzhCPrA4/V0DlOsHRjDKUFNnrH+LgOSSAmZwqRrHYyy6Oe+BkmXU4v5a8oZPA1xYRSL/Q1YDYhiMeySilDDzUQwy6HqcmlpPHdPFsl/S/vQIoCAlP5PbS9/GYXILJJj2bxVjqq/nWeC3QywDsoch02XxPpQORk3qFPKDAbc8AWn26v/zHXFgjEig0vW+el1gjkKe8scNTvjVhRot31gD3SdM39SpEspD+Unkw0EhI60hnQeZjiunRUM9/Za2sw3cFGOCXOySDPrkZ2mm10geTZVDF4JTm+pdsv8cmLOUSooRWg+t8R6MK7ZDmeW1aRScpy5R8je0fuGU7XX/P+RNs27TFJQevE0EwWcTYMtBMQunuuqGFBVUBIOMZzwKeipojx9mGXhDp+TiHsQRXq/9nIOdiDfrub658RUJBgZsaX7fAsnnMMbjf0qBSXdikNoQHm+SrvxI4I7L7XawidSqWkU=
|1|1JIhNCOumg+yjaTgMMYtcGAkC6o=|B/ZgF81ZU+t+8AbByBU3hwp68X0= ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIFLr95lmAUl1k0+zxfhzG4B9fvrvPtddpxOCII+abRfO

root@master:/var/lib/jenkins/.ssh#

Jenkins-Logs:

Warning: no key algorithms provided; JENKINS-42959 disabled
SSHLauncher{host='agent1', port=22, credentialsId='linux-0', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=60, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.KnownHostsFileKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}
[03/10/24 10:43:30] [SSH] Opening SSH connection to agent1:22.
Searching for agent1 in /var/lib/jenkins/.ssh/known_hosts
Searching for agent1:22 in /var/lib/jenkins/.ssh/known_hosts
[03/10/24 10:43:30] [SSH] SSH host key matches key in Known Hosts file. Connection will be allowed.
[03/10/24 10:43:31] [SSH] Authentication successful.
[03/10/24 10:43:32] [SSH] The remote user's environment is:
BASH=/usr/bin/bash
.
.
.
<===[JENKINS REMOTING CAPACITY]===>channel started
Remoting version: 3206.vb_15dcf73f6a_9
Launcher: SSHLauncher
Communication Protocol: Standard in/out
This is a Unix agent
Agent successfully connected and online

Conclusion

Jenkins is a valuable tool for automating software development processes. By understanding its core features, installation, configuration, security, and agent management, you can effectively leverage Jenkins to improve your CI/CD pipelines and deliver high-quality software.

Referenz:

https://community.jenkins.io/t/can-i-create-agent-for-built-in-node/1183

https://jdk.java.net/archive

The post Jenkins auf Ubuntu 22.04 LTS installieren und einige Administrationsaufgaben appeared first on Rhein-Ruhr-Informatik.