Shulou(Shulou.com)06/01 Report--

This article is about how to create an ooRexx build environment on Linux KVM. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

OoRexx is used to develop on-demand software build services, and ooRexx uses the Linux kernel virtual machine (KVM) to improve performance. KVM acts as the host of the guest operating system, building the target software for the user. The Apache Web server controls the build and stores the results for users to retrieve later. Learn how to set up a build server and create a client, customize build requests, and organize and access build results.

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

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

This article shows you how to create your own software build system, uses the settings of the ooRexx development team as an example, and provides tips and guidance for ooRexx, Apache, and Linux developers. You can download server and client scripts at the end of this article. The system is designed to build ooRexx software, but the concepts can be applied to general software construction systems.

The system includes the following requirements:

◆ requires a Web interface to generate build requests.

◆ needs a Web interface to retrieve the build results.

◆ needs to support multi-guest operating systems.

The ◆ guest operating system must perform a fully automated build.

At the end of the build, ◆ should generate an email and send it to the requesting user.

To meet these requirements, the development team and I used a quad-core Xeon-based server. The server contains 4GB memory and 250GB disks. We chose the Fedora 10 x86x64 distribution as the main operating system, mainly because the KVM used in this distribution has good stability and is a * * version. The hardware and software you choose may vary, but the main hardware standard is that your processor should be hardware virtualized-a necessary condition for using KVM.

Set up the server

The step in setting up the build server is to determine the partition mode. We decided to separate the Web storage and images of the guest operating system into separate partitions. We assign 50GB's hard disk to Web storage and 150GB hard drive to the / var partition where the guest operating system image is located. The rest of the hard disk space is allocated to the / home partition and / root partition.

Next, we will install the main operating system using the Fedora 10 x86x64 distribution. If you want to set up your own system, you can avoid a lot of trouble by doing the following:

◆ enables hardware virtualization through the machine's BIOS before starting the installation, so Fedora will find that KVM is available.

◆ performs a custom installation of the software components so that the Fedora virtualization option can be selected.

Once the server operating system is installed, we configure it to be accessible by the guest operating system. This includes enabling Samba for the Windows client and enabling NFS for the Linux client. This allows the client to access the build result partition so that the build file can be stored for user access. The primary Samba share and the primary NFS export point to the same location for all clients.

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

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

This allows you to create an ooRexx build environment on Linux KVM.

Thank you for reading! This is the end of this article on "how to create an ooRexx build environment on Linux KVM". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.