Teach you how to create an ooRexx Build Environment on Linux KVM

In today's society, Linux systems are becoming more and more mainstream. Do you know about Linux systems? Are you an application of Linux? This article describes in detail how to create an ooRexx Build Environment on Linux KVM, which plays a role in learning to create an ooRexx Build Environment on Linux KVM.

OoRexx is used to develop on-demand software build services, and ooRexx uses Linux kernel Virtual Machine KVM to improve performance. KVM acts as the host of the customer's operating system and builds the target software for the user. The Apache Web server controls the construction and storage of results for users to retrieve results later. This article describes how to set up a server and create a client, customize a build request, and organize and access the build results.

Recently, the Open Object Rexx project moved its old On-Demand software build system from a VMware-hosted client operating system to a client hosted by Linux Kernel Virtual Machine (KVM. This change provides a more efficient building environment and reduces the build time for users.

The ooRexx software build system allows developers to build ooRexx software packages for multiple x86-based platforms and operating systems. Currently, supported client operating systems include Windows®XP (i386), Fedora 10i386 and x86_64), and Ubuntu 8.04i386 ). These customer operating systems generate ooRexx installation and documentation packages for Windows (EXE), Fedora, openSUSE (RPM), and Ubuntu (DEB. Other x86 operating systems will also be supported based on the needs of ooRexx developers and users.

This article will show you how to create your own software build system, use ooRexx Development Team settings as an example, and provide skills and guidance for ooRexx, Apache, and Linux developers. You can download the server and client scripts at the end of this article. This system is used to build ooRexx software, but its concept can be applied to general software build systems.

The system includes the following requirements:

◆ A Web interface is required to generate a build request.

◆ A Web interface is required to retrieve the building result.

◆ Multi-customer operating systems must be supported.

◆ The customer's operating system must be fully automated.

◆ At the end of construction, an email should be generated and sent to the requesting user.

To meet these requirements, the development team and I used a quad-core Xeon-based server. The server contains 4 GB memory and 250 GB disk. We chose the Fedora 10 x86_64 release as the main operating system, mainly considering that the KVM used in the release has good stability and is the latest version. The selected hardware and software may be different, but the main hardware standard is that your processor should have hardware virtualization features-this is necessary to use KVM.

Set Server

The first step in setting up the server building is to determine the partition mode. We decided to separate the Web storage and images of the customer's operating system into separate partitions. We allocate a 50 GB hard disk for Web storage and a 150 GB hard disk for the/var partition of the customer's operating system image. The remaining hard disk space is allocated to the/home partition and/root partition.

Next, we will use the ora 10 x86_64 release to install the main operating system. If you want to set up your own system, the following operations can avoid a lot of trouble:

◆ Enable hardware virtualization through the BIOS of the machine before the installation is started. In this way, Fedora will find that KVM is available.

◆ Execute the customized installation of software components so that you can select the Fedora virtualization option.

After the server operating system is installed, we configure it to be accessible by the customer's operating system. This includes enabling Samba for Windows clients and NFS for Linux clients. This allows the client to access the build result partition and store the Build File for user access. Main Samba shares and major NFS exports direct to the same location for all clients.

Next, we will configure the Apache Web server to provide access to the build request system I will explain in the build request) and build the result library.

A configuration decision to be determined is related to the client's network options. By default, the installation is configured to apply a private intranet to all clients. Class C network and DHCP server are provided together to provide IP addresses for clients. Another option is to set up the system to use one of the network devices as the bridge to the external network of the server. This requires manual configuration. You can find an example of how to configure this option for the server in libvirt Wiki.

In this way, you can create an ooRexx Build Environment on Linux KVM.

1. Measure the test taker's knowledge about Linux system performance indicators.
2. Detailed introduction to Linux grep commands
3. How to obtain the file size in Linux
4. Operation notes: Linux system time viewing
5. How to modify the PATH of the environment variable in Linux