AIX operating system network installation method, system, device and medium

Abstract

The invention relates to the technical field of computers, and discloses an AIX operating system network installation method. The method comprises the following steps executed in a client environment: acquiring a network installation bootstrap program generated based on a first preset script from a target server, so as to create a memory file system in the client environment; executing a second preset script based on the network installation bootstrap program to obtain an environment variable, mounting a temporary remote NFS file system directory in the client environment based on the environment variable to generate a target file, and storing the target file in a memory file system; mounting a target remote NFS file system directory in a client environment based on the target file, and switching a memory file system into a remote NFS file system; an AIX operating system is installed in a client environment based on a remote NFS file system. According to the scheme of the invention, the problems of high hardware dependency, low efficiency, high error rate and high cost in the traditional network installation depending on the NIM server are solved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer technology, and particularly relates to an AIX operating system network installation method, system, device and medium. BACKGROUND

[0002] The AIX operating system (Advanced Interactive eXecutive, a UNIX operating system developed based on System V) is widely used in key databases and core applications of finance, government and enterprises due to its high stability, security and scalability, and the effectiveness of its installation configuration directly affects the stability, security and performance of the system environment. The installation methods of the AIX operating system include CD-ROM (Compact Disc Read-Only Memory), USB (Universal Serial Bus), magnetic tape installation, network installation and installation based on mksysb (system backup) backup files, among which, network installation can significantly improve efficiency in multi-server batch deployment scenarios and can complete installation without direct contact with the server, thus having important application value.

[0003] However, the traditional AIX network installation mainly relies on the NIM (Network Installation Management) server, which has obvious deficiencies: first, the NIM server needs to be deployed on the Power server and the AIX operating system, relying on a special hardware architecture, resulting in high deployment costs; second, the environment configuration of the NIM server is complex and requires professional maintenance, increasing the difficulty of operation and maintenance; third, the NIM server cannot be seamlessly integrated with x86 architecture Linux servers, limiting the flexibility of network installation in cross-platform environments and making it difficult to adapt to scenarios that provide remote NFS file system support based on x86 Linux servers.

[0004] In addition, in the AIX network installation process, the booting of the client environment, the mounting of the remote file system and the automated execution of the installation process all require efficient coordination mechanisms, and the traditional network installation method relying on the NIM server has limitations in the generation of network installation boot programs, the adaptation of the client environment and remote NFS (Network File System) file systems, and cannot meet the needs of simplifying the installation process and reducing dependence on special architectures.

[0005] The above problems make it difficult to effectively improve the network installation of the AIX operating system in terms of cost control, configuration efficiency and cross-platform compatibility, and therefore there is an urgent need for a new AIX operating system network installation method to solve the above problems. SUMMARY

[0006] Therefore, the present application provides an AIX operating system network installation method, system, device and medium, which solves the problems of strong hardware dependency, low efficiency, high cost and error-prone of the traditional network installation relying on NIM server, and optimizes the client environment installation process based on remote NFS file system and network installation boot program.

[0007] To achieve the above object, in one aspect, the present application provides an AIX operating system network installation method, which specifically includes the following steps in a client environment: obtaining a network installation boot program generated based on a first preset script from a target server to create a memory file system in the client environment; executing a second preset script based on the network installation boot program to obtain environment variables, mounting a temporary remote NFS file system directory in the client environment based on the environment variables to generate a target file and store it in the memory file system; mounting a target remote NFS file system directory in the client environment based on the target file, and switching the memory file system to a remote NFS file system; installing an AIX operating system in the client environment based on the remote NFS file system.

[0008] In some embodiments, the following steps are further included in the target server: adding system startup branch code in the first preset script to obtain the second preset script; generating the network installation boot program based on the first preset command and hosting it in the target server based on the second preset script.

[0009] In some embodiments, the step of obtaining a network installation boot program generated based on a first preset script from a target server to create a memory file system in the client environment includes: judging whether the client environment is configured with a DHCP service; if the client environment is configured with a DHCP service, directly starting the client environment and downloading the network installation boot program from the target server to the client environment based on the DHCP service; if the client environment is not configured with a DHCP service, starting the client environment based on an open firmware environment and a second preset command, and downloading the network installation boot program from the target server to the client environment according to the second preset command; loading the network installation boot program to start a kernel, creating the memory file system based on the kernel.

[0010] In some embodiments, the second preset script is executed based on the network installation boot program to obtain environment variables, including: In response to the network installation boot program starting, the second preset script is executed to execute the startup branch code therein; After the network configuration operation according to the startup branch code, an environment configuration file is obtained from the target server end; Based on the environment configuration file, the environment variables of the client environment are set.

[0011] In some embodiments, based on the environment variables, a temporary remote NFS file system directory is mounted in the client environment to generate target files and store them to the memory file system, including: A first remote NFS file system directory specified by a first variable in the environment variables is mounted in the client environment, and core files therein are copied to the memory file system; Hardware devices of the client environment are identified, and device information and configuration data of the hardware devices are stored to the memory file system; A second remote NFS file system directory specified by a second variable in the environment variables is mounted in the client environment, and the device information and the configuration data stored in the memory file system are synchronized to the second remote NFS file system directory; Based on the second remote NFS file system directory and the second remote NFS file system directory, the target files are generated and stored to the memory file system.

[0012] In some embodiments, based on the target files, a target remote NFS file system directory is mounted in the client environment, and the memory file system is switched to a remote NFS file system, including: The temporary remote NFS file system directory is unmounted; Based on the target files, NFS directory paths corresponding to each local mount point in the client environment are determined; Based on each of the NFS directory paths, the target remote NFS file system directory corresponding to each of the local mount points is mounted in the client environment; After the memory file system is switched to the remote NFS file system, the environment variables are updated based on the target remote NFS file system directory.

[0013] In some embodiments, the installing the AIX operating system in the client environment based on the remote NFS file system comprises: calling a third preset script in the remote NFS file system, and obtaining hardware and software information of a hardware device in the client environment based on the third preset script; querying a parameter matching the hardware and software information in a preset knowledge base, and injecting the parameter into a system configuration in the client environment; checking integrity of a backup file in the remote NFS file system based on the third preset script; restoring the backup file in the remote NFS file system to a local hard disk in the client environment after the injection according to a checking result; setting the local hard disk as a default boot device, and restarting the client environment to load the AIX operating system from the local hard disk.

[0014] Another aspect of the embodiment of the application further provides an AIX operating system network installation system, comprising: a client processing unit configured to obtain a network installation boot program generated based on a first preset script from a target server to create a memory file system in the client environment; a client generating unit configured to execute a second preset script based on the network installation boot program to obtain an environment variable, mount a temporary remote NFS file system directory in the client environment based on the environment variable to generate a target file and store the target file to the memory file system; a client mounting unit configured to mount a target remote NFS file system directory in the client environment based on the target file, and switch the memory file system to the remote NFS file system; a client installing unit configured to install the AIX operating system in the client environment based on the remote NFS file system.

[0015] Still another aspect of the embodiment of the application further provides a computer device, comprising at least one processor, and a memory storing a computer program capable of running on the processor, wherein the computer program is executed by the processor to implement steps of the above method.

[0016] Still another aspect of the embodiment of the application further provides a computer readable storage medium storing a computer program capable of being executed by a processor to implement steps of the above method.

[0017] The application has at least the following beneficial technical effects: The AIX operating system network installation method provided by the application generates a network installation boot program based on a first preset script, thereby breaking away from the dependence on the NIM server, without the need for a dedicated Power server and AIX operating system deployment installation management tool, reducing the dependence on a dedicated software and hardware architecture, thereby reducing the deployment cost. The client environment downloads the boot program and creates a memory file system, thereby providing a temporary and efficient running space for subsequent installation operations, simplifying the building process of the initial environment of the client. The second preset script is executed based on the boot program to obtain environment variables, mount a temporary remote NFS file system directory, and generate a target file stored in the memory file system, thereby realizing the accurate connection between the client and the remote resource, and providing a reliable basis for the subsequent standard mounting of the remote file system through the generation and storage of the target file, thereby improving the configuration efficiency. After the temporary directory is uninstalled, the target remote NFS file system directory is mounted based on the target file and switched to the system, thereby optimizing the adaptation process of the client and the remote NFS file system, supporting seamless integration with the NFS service provided by the x86 architecture Linux server, and enhancing the flexibility of cross-platform deployment. Finally, the installation is completed based on the remote NFS file system, thereby realizing the automation of the installation process, further simplifying the operation steps, reducing manual intervention, and reducing the operation and maintenance difficulty, effectively solving the problems of high deployment cost, high operation and maintenance difficulty, poor cross-platform compatibility, and complex installation process in the traditional network installation method depending on the NIM server, and significantly improving the efficiency, flexibility and applicability of the network installation of the AIX operating system. BRIEF DESCRIPTION OF DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description only some embodiments of the application, and for those skilled in the art, other embodiments can be obtained without creative labor based on these drawings.

[0019] Figure 1 The block diagram of an embodiment of the AIX operating system network installation method provided by the application; Figure 2 The flowchart of an embodiment of the AIX operating system network installation method provided by the application; Figure 3 The schematic diagram of an embodiment of the AIX operating system network installation system provided by the application; Figure 4 The structural schematic diagram of an embodiment of the computer equipment provided by the application; Figure 5 The structural schematic diagram of an embodiment of the computer readable storage medium provided by the application. DETAILED DESCRIPTION

[0020] In order to make the objects, technical solutions and advantages of the present application clearer, the embodiments of the present application are further described in detail below with reference to the drawings.

[0021] It should be noted that all the expressions of "first" and "second" in the embodiments of the present application are used to distinguish two same name non-same entities or non-same parameters. It can be seen that "first" and "second" are only for the convenience of description and should not be understood as a limitation of the embodiments of the present application. The subsequent embodiments will not be described one by one.

[0022] Based on the above purpose, the first aspect of the embodiments of the present application proposes an embodiment of an AIX operating system network installation method. As shown in the figure, it includes the following steps in the client environment: Figure 1 Step S100, obtaining a network installation boot program generated based on a first preset script from a target server to create a memory file system in the client environment; Step S200, executing a second preset script based on the network installation boot program to obtain an environment variable, based on the environment variable, mounting a temporary remote NFS file system directory in the client environment to generate a target file and store it to the memory file system; Step S300, mounting a target remote NFS file system directory in the client environment based on the target file, and switching the memory file system to the remote NFS file system; Step S400, installing the AIX operating system in the client environment based on the remote NFS file system.

[0023] In some embodiments, the present application specifically designs an AIX automatic network installation and automatic optimization AIX operating system network installation method, which can manage the automatic network installation of AIX system through x86 architecture Linux server, and on this basis, integrates the automatic optimization function of AIX parameter configuration. Without relying on NIM server, the deployment cost is reduced and the cross-platform compatibility is improved.

[0024] In some embodiments, the present application specifically designs an AIX automatic network installation and automatic optimization AIX operating system network installation method, which can manage the automatic network installation of AIX system through x86 architecture Linux server, and on this basis, integrates the automatic optimization function of AIX parameter configuration. Without relying on NIM server, the deployment cost is reduced and the cross-platform compatibility is improved. Figure 2 ​To illustrate the installation optimization process of AIX operating system. In the existing AIX environment, the rc.boot script is the original boot script of the system, which belongs to the core boot component of the default installation of the AIX operating system. The first preset script is the rc.boot script in the existing AIX operating system. Its main function is to complete the key boot operations such as hardware initialization, file system mounting, basic service starting, etc. in the AIX operating system startup process, which is an important intermediate link for AIX system from kernel loading to entering multi-user mode. The second preset script is the rc.boot script modified based on the first preset script. The network installation boot image is an executable file containing AIX kernel, basic configuration script and necessary drivers, which provides boot support for the client environment and ensures that the client can obtain the required resources for installation through the network and complete initialization.

[0025] In some embodiments, a client partition is created in the HMC (Hardware Management Console, graphical interface management software) and the CPU, memory quantity and IO (Input / Output) device are set, obtaining a client environment, wherein the IO device at least contains a network card and a hard disk. The client environment is connected to the x86 architecture Linux server (i.e. target server end) storing the network installation boot image through the network, and the network installation boot image is downloaded to the client environment. After the download is completed, the AIX kernel in the network installation boot image is loaded by the client environment, and the RAMFS (i.e. memory file system) is automatically created in the memory of the client by the AIX kernel. The memory file system is a temporary file system based on memory, which has the characteristics of fast read and write speed, and can provide temporary running space and file storage area for subsequent installation operations when the local operating system of the client environment has not been installed. For example, the memory file system will be divided into " / bin", " / lib", " / etc" directories, respectively used to store temporary executable files, library files and configuration files.

[0026] In some embodiments, after the network installation boot program is started, a second preset script is automatically called, which first performs network configuration. After the network is ready, the second preset script downloads an environment configuration file from the target server end, parses the file to obtain environment variables, including the IP address of the NFS server, the shared directory path, the SPOT (i.e. installation base file directory) path, the ROOTFS (i.e. system root directory) path, and other key information. Based on these environment variables, the specified remote NFS file system directory (i.e. temporary remote NFS file system directory) is mounted to the client environment. The temporary remote NFS file system directory stores the basic resources required to generate the target file, such as executable files, lib (library file) files, driver program files, etc. The target file is the filesystems file. After the target file is generated, it is copied to the memory file system so that subsequent steps can quickly access the file.

[0027] In some embodiments, after the target file is generated and stored in the memory file system, the client environment unmounts the temporary remote NFS file system directory that was previously mounted to avoid interference with subsequent operations. Subsequently, the target file in the memory file system is read, and according to the configuration information recorded in the target file, the target remote NFS file system directory on the remote NFS server is mounted to the corresponding local path of the client environment. The target remote NFS file system directory is a remote NFS file system directory that is remounted according to the filesystems file. It precisely corresponds the remote NFS directory to the local file system mount point according to the standard file system structure of the AIX system, ensuring that the system can access the resources under each directory as expected, and providing a standardized environment for subsequent installation processes. After mounting is complete, the running root directory of the client environment needs to be switched from the memory file system to the remote NFS file system. All operation paths of the client environment are based on the remote NFS file system directory. At this time, the memory file system is no longer the main running environment and only remains as a temporary cache.

[0028] In some embodiments, after the client environment switches to the remote NFS file system, the system automatically invokes an automated installation script stored in the file system, such as autoinstall.sh. The script first checks the status of the local hard disk of the client environment, such as whether the hard disk exists, whether there is sufficient storage space, etc., and checks whether the specified mksysb backup file in the remote NFS file system exists and is complete. If the check passes, the script restores the mksysb backup file to the local hard disk of the client environment, rebuilds the root directory, user directory, system library, and other key partitions of the AIX system on the local hard disk. After the restoration is complete, the script modifies the default boot device settings of the client environment, sets the local hard disk as the preferred boot device, and finally executes a restart command. After the client environment restarts, the installed AIX operating system is loaded from the local hard disk, and the entire network installation process is completed.

[0029] The AIX operating system network installation method of the present application generates and uses an AIX network installation boot program that does not depend on a NIM server, combines phased script execution with a remote NFS file system mounting switching mechanism, realizes smooth transition from an in-memory file system to a remote NFS file system in a client environment, and then completes automated installation of an AIX operating system based on the remote NFS file system, thereby eliminating dependence on a Power architecture and a dedicated NIM environment, and realizing AIX network installation on a cross-platform such as an x86 architecture Linux server.

[0030] In some embodiments, the method further includes executing the following steps on the target server side: adding system startup branch code in the first preset script to obtain a second preset script; and generating a network installation boot program based on the first preset command and hosting the network installation boot program on the target server side.

[0031] In some embodiments, the first preset script needs to be modified to adapt to network installation requirements. When modifying, the original basic boot logic of the script needs to be retained, and a system startup branch, i.e., an NFS Install branch, needs to be newly added. At this time, the modified rc.boot script is the second preset script. After modification, the bosboot -ad / dev / ent0 -b / tmp / net.bootimage command (i.e., the first preset command) is used to generate an AIX network installation boot program that does not depend on a NIM server. The network installation boot program contains the modified rc.boot script and is used to automatically execute the script during the boot process of the client environment.

[0032] In some embodiments, the work of configuring network, obtaining environment configuration file, performing environment configuration file to set current environment variable, and mounting specified remote NFS file system based on environment variable and calling rc.nfs_install script in the file system is completed in system startup branch code.

[0033] In some embodiments, the Linux server with x86 architecture is taken as target server, and standard services such as TFTP (Trivial File Transfer Protocol) service, NFS service or DHCP (Dynamic Host Configuration Protocol) service are configured in the Linux server. The TFTP service is configured to host AIX network boot program and environment configuration file. The NFS service is configured to host remote NFS file system required by installation process, mksysb backup file, automation installation script autoinstall.sh, and to host automatic optimization knowledge base and automation parameter adjustment script autotuning.sh. The DHCP service is configured to support client to automatically obtain IP and load corresponding AIX boot program and environment configuration file, and to inform client of download location of network installation boot program of environment through next-server and filename parameters in configuration file / etc / dhcp / dhcpd.conf.

[0034] In some embodiments, the network installation boot program generated based on the first preset script is obtained from the target server to create memory file system in the client environment, including: judging whether the client environment is configured with DHCP service; if the client environment is configured with DHCP service, starting the client environment directly, and downloading the network installation boot program from the target server to the client environment based on the DHCP service; if the client environment is not configured with DHCP service, starting the client environment based on open firmware environment and second preset command, and downloading the network installation boot program from the target server to the client environment according to the second preset command; and loading the network installation boot program to start kernel and creating memory file system based on the kernel.

[0035] In some embodiments, the DHCP service is a service for automatically allocating network parameters such as IP address, subnet mask, gateway, etc., and whether the client environment is configured with the DHCP service determines the starting mode and network parameter obtaining logic when the client environment obtains the network installation boot program. The judgment process can be realized by checking preset configuration information of the client environment, for example, if there is a parameter or mark pointing to DHCP server in the startup configuration data of the client environment, it is determined that the DHCP service is configured, otherwise, it is determined that the DHCP service is not configured.

[0036] In some embodiments, when the client environment configures the DHCP service, its startup process does not need to manually specify network parameters. When the client environment is started in the HMC, after the client environment is started, it automatically sends a request to the DHCP server in the network to obtain network configuration information including IP address, target server address, boot program file name, etc. After obtaining the information, the client environment connects to the target server through the TFTP protocol, and downloads the network installation boot program from the specified path of the target server to the local temporary storage area according to the obtained boot program file name.

[0037] In some embodiments, the open firmware environment is the underlying firmware interface at the initial stage of the client environment startup, which supports the configuration of startup parameters through commands. When the DHCP service is not configured, the network parameters need to be manually specified in this environment. The second preset command is the BOOT_FROM_SEQ [ADDPARMS] command, where the ADDPARMS parameter provides related network configurations such as the TFTP server IP address and the required AIX boot program name. After inputting and executing this command in the open firmware environment, the client environment completes network initialization based on the static network parameters in the command, and connects to the target server through the TFTP protocol to download the network installation boot program to the local temporary storage area according to the path specified in the command.

[0038] In some embodiments, after the client environment successfully downloads the network installation boot program, it automatically loads the program, and the bootloader in the program parses the program content to start the AIX kernel. After the kernel is started, a block of memory is allocated in the memory of the client environment to create a memory file system.

[0039] In summary, by adapting to the configuration state of the DHCP service, the corresponding startup and download strategies are adopted to ensure the reliable acquisition of the network installation boot program. At the same time, by creating a memory file system after the kernel is started, a necessary temporary running environment is provided for subsequent environment variable acquisition, remote NFS file system mounting, etc. operations, effectively supporting the early preparation process of AIX operating system network installation, and improving the adaptability and stability of the installation process.

[0040] In some embodiments, a second preset script is executed based on the network installation boot program to obtain environment variables, including: in response to the startup of the network installation boot program, executing the second preset script to execute the startup branch code therein; after performing the network configuration operation according to the startup branch code, obtaining the environment configuration file from the target server; and based on the environment configuration file, setting the environment variables of the client environment.

[0041] In some embodiments, the network installation boot program is a core program loaded when the client environment starts, which contains the AIX kernel and basic boot logic. When the client environment starts through the network and loads the boot program, the execution of the second preset script is automatically triggered. The second preset script includes the start branch code for network installation, which contains key instructions such as network configuration and remote resource acquisition. After the boot program starts, the boot process of the client environment is introduced into the network installation track through the script.

[0042] In some embodiments, after the network configuration operation according to the start branch code is performed, the environment configuration file is obtained from the target server end. The start branch code first performs the network configuration operation, which aims to establish the network communication link between the client environment and the target server end. The environment configuration file is usually downloaded from the specified path through the TFTP protocol, and saved to the memory file system of the client environment.

[0043] In some embodiments, the content in the environment configuration file includes the information required for mounting the remote NFS file system, the script name to be automatically executed in the system boot process, the mksysb backup file name, the HOSTS file content, etc. For example: export SPOT=10.128.11.159: / home / inst_resource / usr export ROOTFS=10.128.11.159: / home / inst_resource / root export TMP=10.128.11.159: / home / inst_resource / tmp export TUNING=10.128.11.159: / home / inst_resource / tuning export RC_CONFIG=rc.nfs_install export MKSYSB_FILE= / tmp / aix720505.mksysb export CLIENT_HOSTS=" 127.0.0.1:loopback:localhost10.128.11.119:client10.128.11.159:nfsserver " By executing the environment configuration file, the client environment variable setting can be completed, which is used in the subsequent script execution process.

[0044] In summary, the automatic network configuration is realized by starting the branch code for directional execution, the accurate setting of environment variables is realized by obtaining and parsing the environment configuration file from the target server, the effective association between the client environment and the remote installation resource is ensured, which lays a solid foundation for the subsequent process of AIX operating system network installation, and avoids the complex configuration of traditional NIM server, and improves the automation degree and flexibility of the installation process.

[0045] In some embodiments, based on the environment variables, a temporary remote NFS file system directory is mounted in the client environment to generate a target file and store it in the memory file system, including: mounting a first remote NFS file system directory specified by a first variable in the environment variables in the client environment, copying the core file therein to the memory file system; identifying the hardware device of the client environment, storing the device information and configuration data of the hardware device to the memory file system; mounting a second remote NFS file system directory specified by a second variable in the environment variables in the client environment, synchronizing the device information and configuration data stored in the memory file system to the second remote NFS file system directory; generating a target file based on the second remote NFS file system directory and the second remote NFS file system directory and storing it in the memory file system.

[0046] In some embodiments, this step involves a sub-script rc.nfs_install called by the rc.boot script, which realizes the transition of the client environment from the temporary memory file system to the remote NFS file system by performing remote NFS directory mounting, file copying, device configuration, file system configuration generation, and environment switching, etc., and provides environment support for AIX operating system network installation.

[0047] In some embodiments, the first environment variable is SPOT and the second environment variable is ROOTFS. The sub-script first mounts the first remote NFS file system directory specified by the environment variable SPOT to the current client environment, and copies the key files to the memory file system of the client environment. Among them, the environment variable SPOT points to the installation base file directory on the remote NFS server, which stores the key files required for AIX installation, such as basic executable tools, lib library files, and hardware drivers. After successful mounting, the sub-script copies the key files to the memory file system. Provide basic running dependency resources for RAMFS, ensure that subsequent device configuration, script execution, and other operations can be performed normally.

[0048] In some embodiments, the sub-script executes basic device configuration commands of the client environment, ensures that the infrastructure is correctly set up, and saves device information to the in-memory file system. Specifically, the sub-script scans and initializes the client hardware, automatically identifies basic devices such as network cards, hard disks, bus controllers, generates corresponding device nodes and configures device attributes. After configuration is complete, the sub-script copies device information and related configuration data to the in-memory file system. The saving of this information provides basic data for subsequent remote NFS file system adaptation to client hardware.

[0049] In some embodiments, the sub-script mounts the second remote NFS file system directory specified by the environment variable ROOTFS, and synchronizes the device information and ODM information in the in-memory file system to this directory. The environment variable ROOTFS points to the system root directory on the second remote NFS server, which simulates the root structure of the AIX system and contains subdirectories such as “ / root”, “ / usr”, “ / tmp”, etc. The purpose of the synchronization operation is to adapt the remote system root directory to the hardware environment of the client, ensuring that it can recognize and manage the client devices.

[0050] In some embodiments, the sub-script generates the filesystems file according to the environment configuration file and saves it to the first remote NFS file system directory and the second remote NFS file system directory specified by the ROOTFS. The sub-script will perform an unmount operation to remove the currently mounted first remote NFS file system directory and second remote NFS file system directory, and then remount according to the filesystems file to avoid conflicts between old mount paths and standard paths, and to ensure that each local file system mount point is accurately mapped to the corresponding target remote NFS file system directory. After completing the above operations, the sub-script switches the client environment from RAMFS to the remote NFS file system. After switching, all operation paths of the client point to the target remote NFS file system, and RAMFS only exists as a temporary cache. After the sub-script is executed, the rc.boot script is awakened from the waiting state and continues to execute the remaining boot process, preparing for the subsequent call of the automated installation script.

[0051] In summary, the sub-script realizes the smooth transition of the client environment from the temporary in-memory file system to the remote NFS file system by sequentially executing operations such as mounting, copying, configuring, generating files, and environment switching, and breaks away from the dependence on the NIM server, ensuring the continuity and automation of the AIX operating system network installation process.

[0052] In some embodiments, based on the target file, mounting the target remote NFS file system directory in the client environment and switching the in-memory file system to the remote NFS file system, comprising: unmounting the temporary remote NFS file system directory; based on the target file, determining the NFS directory path corresponding to each local mount point in the client environment; based on each NFS directory path, mounting the target remote NFS file system directory corresponding to each local mount point in the client environment; after switching the in-memory file system to the remote NFS file system, updating the environment variable based on the target remote NFS file system directory.

[0053] In some embodiments, based on the remote NFS file system, installing the AIX operating system in the client environment, comprising: calling a third preset script in the remote NFS file system, obtaining the hardware and software information of the hardware device in the client environment based on the third preset script; querying the parameters matched with the hardware and software information in the preset knowledge base, and injecting the parameters into the system configuration in the client environment; checking the integrity of the backup file in the remote NFS file system based on the third preset script; according to the checking result, restoring the backup file in the remote NFS file system to the local hard disk in the client environment after injection; setting the local hard disk as the default boot device, and restarting the client environment to load the AIX operating system from the local hard disk.

[0054] In some embodiments, the operations of obtaining hardware and software information, parameter optimization, backup file verification and restoration, boot device configuration, etc. are completed by scripts, realizing the automatic deployment of the AIX operating system from the remote storage to the local hard disk, and ensuring that the system after installation is adapted to the client hardware and can run independently.

[0055] In some embodiments, the autoinstall.sh script is automatically executed after the client environment booting is successful, the autoinstall.sh script is stored in the remote NFS file system directory, and is called by / etc / rc.local, and the AIX operating system is finally deployed from the remote NFS environment to the local hard disk by performing local hard disk checking, backup file verification, system recovery, boot configuration and restart operations. The autoinstall.sh script first checks the local hard disk information and its state of the client environment. The local hard disk is the target storage device for the client environment to finally install the AIX operating system, and its availability directly determines whether the installation can be completed. The script identifies the local hard disk available for installing the system by calling system commands to obtain hard disk information, and checks the path state of the hard disk to confirm that it is connected normally, obtains hard disk capacity, speed and other parameters, and judges whether the storage space required for mksysb backup file recovery is met. If the check finds that the local hard disk does not exist, the capacity is insufficient, or there is a hardware failure, the script will output error information and terminate execution, waiting for manual intervention. The script checks whether the mksysb backup file specified in the environment configuration file exists. The mksysb backup file is a compressed file containing a complete AIX operating system image, stored in the specified path of the remote NFS file system, and its location is determined by the preset parameter (such as MKSYSB_PATH) in the environment configuration file. If the environment is correct, the mksysb backup file will be restored to the local hard disk of the client environment. The correct environment means that the local hard disk is in normal state and the mksysb backup file is complete and available, at which time the script starts the recovery process. The script sets the default boot device of the client environment to the local hard disk, in order to ensure that the client environment can be started from the local hard disk after restart, rather than continuing to rely on the remote NFS file system, the script needs to modify the boot order configuration. After completing the local hard disk recovery and boot device configuration, the script triggers the client environment to restart. During the restart process, the client firmware reads the boot order configuration, loads the restored AIX kernel and system files from the local hard disk, and the startup process no longer relies on the remote NFS file system. After the restart is completed, the client environment will run as an independent AIX system, and all applications and services are started based on local hard disk data, thus completing the entire network installation process.

[0056] In some embodiments, the autotuning.sh script is executed after the autoinstall.sh script correctly completes the AIX operating system native recovery, i.e., the third preset script. The autotuning.sh script realizes the automatic optimization of the system parameters of the client environment by collecting the hardware and software information of the client environment, backing up the current parameters, matching the optimal parameters and automatically modifying, checking and restarting the system, to ensure that the system is adapted to the hardware characteristics and reaches the best running state. The autotuning.sh script first collects the system hardware and software information of the client environment. The collected information is the basis for subsequent parameter optimization and needs to comprehensively reflect the hardware configuration and software environment of the client. The hardware information includes but is not limited to CPU model, core number and main frequency, memory capacity, type and channel number, local hard disk model, capacity and interface type, network adapter model and bandwidth. The software information includes but is not limited to AIX operating system version, installed core components and preset application load type. The script organizes the collected information into a temporary file in the key-value pair format, which is used for subsequent matching with the knowledge base. The purpose of backup is to restore to the original state when parameter modification abnormally occurs, to ensure system stability. After backup is completed, the script checks the integrity of the backup file to ensure that it can be normally restored when needed. The script matches the optimal parameters in the knowledge base according to the hardware and software information and automatically modifies them. The knowledge base is a parameter set stored in a remote NFS file system, the path of which is specified by the environment variable TUNING, and contains optimal parameter configurations corresponding to different hardware combinations. These parameters are based on hardware manufacturer recommendations, performance test data and industry best practices. The script restarts the system after checking that the parameter modification is correct. The purpose of checking is to ensure that the parameters have been correctly applied and have not caused system abnormalities.

[0057] It should be noted that the knowledge base file and the autotuning.sh script are stored in the remote NFS file system directory defined by the environment variable TUNING. Before executing autotuning.sh, the client environment automatically reads the environment variable TUNING to obtain the remote path, mounts the knowledge base file system to the local, and then loads the autotuning.sh script from the mounted directory and executes it, without the need for manual intervention to complete the acquisition of resources required for parameter optimization. The knowledge base is provided in the form of a configuration file, which includes: best practices for system general parameters (such as ioo, no, vmo, schedo, etc.), best practices for user environment variables, best practices for parameters of various hardware (such as network cards, HBA cards, hdisk devices, etc.), and best practices for specific parameters of various application scenarios (such as Oracle, DB2, GPFS, etc.).

[0058] In summary, through the automatic execution of the third preset script, the full-process connection of the software and hardware information acquisition, parameter optimization, backup verification, local recovery and boot configuration is realized. The method not only ensures that the installed AIX operating system is adapted to the hardware environment of the client through parameter optimization, but also enables the client to finally run independently from the remote environment through backup file recovery and boot device configuration, effectively solves the problems of complex parameter configuration and dependence on special tools in the traditional installation mode, and improves the automation degree and reliability of the network installation of the AIX operating system.

[0059] Based on the same inventive concept, according to another aspect of the present application, as shown in Figure 3 The embodiment of the present application also provides an AIX operating system network installation system, which comprises: The client processing unit 110 is used for obtaining the network installation boot program generated based on the first preset script from the target server, so as to create a memory file system in the client environment; The client generating unit 120 is used for executing the second preset script based on the network installation boot program, so as to obtain an environment variable, mount a temporary remote NFS file system directory in the client environment based on the environment variable, generate a target file and store the target file into the memory file system; The client mounting unit 130 is used for mounting a target remote NFS file system directory in the client environment based on the target file, and switching the memory file system to the remote NFS file system; The client installing unit 140 is used for installing the AIX operating system in the client environment based on the remote NFS file system.

[0060] The AIX operating system network installation system of the present application generates and uses the AIX network installation boot program which does not depend on the NIM server, combines the phased script execution and the remote NFS file system mounting and switching mechanism, realizes the smooth transition from the memory file system to the remote NFS file system in the client environment, and then completes the automatic installation of the AIX operating system based on the remote NFS file system, so as to get rid of the dependence on the Power architecture and the special NIM environment, and realize the AIX network installation under the cross-platform such as the x86 architecture Linux server.

[0061] Based on the same inventive concept, according to another aspect of the present application, as shown in Figure 4 The embodiment of the present application also provides a computer device 30, which comprises a processor 310 and a memory 320, the memory 320 stores a computer program 321 which can run on the processor, and the processor 310 executes the steps of the method as above when executing the program.

[0062] Based on the same inventive concept, according to another aspect of the present application, as shown in FIG. 10, embodiments of the present application also provide a computer readable storage medium 40, which stores a computer program 410 for performing the above method when executed by a processor. Figure 5

[0063] Finally, it should be noted that those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by a computer program to instruct relevant hardware, and the program can be stored in a computer readable storage medium. When the program is executed, it can include the processes of the above-mentioned embodiments. The storage medium of the program can be a magnetic disc, an optical disc, a read-only memory (ROM) or a random access memory (RAM), etc. The above-mentioned computer program embodiments can achieve the same or similar effects as any of the above-mentioned method embodiments.

[0064] Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present embodiments.

[0065] The above is the exemplary embodiment disclosed by the present application, but it should be noted that various changes and modifications can be made without departing from the scope of the present embodiments disclosed by the claims. The functions, steps and / or acts of the method claims according to the disclosed embodiments described herein need not be performed in any particular order. The above-mentioned embodiment numbers of the present embodiments are only for description and do not represent the advantages and disadvantages of the embodiments. In addition, although the elements of the present embodiments disclosed can be described or claimed in singular form, they can also be understood as plural, unless clearly limited to singular.

[0066] It should be understood that, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises", "comprising", "includes" and / or "including", as used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0067] ​Those skilled in the art should understand that the above discussion of any embodiment is only exemplary, and is not intended to mean that the scope of the embodiments disclosed by the present application (including claims) is limited to these examples; under the idea of the embodiments of the present application, the above embodiments or technical features in different embodiments can also be combined, and there are many other changes of different aspects of the embodiments of the present application as above. In order to be brief, they are not provided in details. Therefore, any omission, modification, equivalent replacement, improvement, etc. made in the spirit and principle of the embodiments of the present application shall be included in the protection scope of the embodiments of the present application.

Claims

1. A method for network installation of the AIX operating system, characterized in that, This includes performing the following steps in the client environment: Obtain a network installation bootloader generated based on a first preset script from the target server to create a memory file system in the client environment; The second preset script is executed based on the network installation bootloader to obtain environment variables. Based on the environment variables, a temporary remote NFS file system directory is mounted in the client environment to generate target files and store them in the memory file system. Based on the target file, the target remote NFS file system directory is mounted in the client environment, and the memory file system is switched to the remote NFS file system; The AIX operating system is installed in the client environment based on the remote NFS file system.

2. The AIX operating system network installation method according to claim 1, characterized in that, This also includes performing the following steps on the target server: Add system startup branch code to the first preset script to obtain the second preset script; Based on the first preset command, the second preset script generates the network installation boot program and hosts it on the target server.

3. The AIX operating system network installation method according to claim 2, characterized in that, The step of obtaining the network installation bootloader generated based on the first preset script from the target server to create a memory file system in the client environment includes: Determine whether the client environment is configured with DHCP service; If the client environment is configured with DHCP service, the client environment is started directly, and the network installation bootloader is downloaded from the target server to the client environment based on the DHCP service; If the client environment is not configured with DHCP service, the client environment is started based on the open firmware environment and the second preset command, and the network installation boot program is downloaded from the target server to the client environment according to the second preset command; The network installation bootloader is loaded to start the kernel, and the memory file system is created based on the kernel.

4. The AIX operating system network installation method according to claim 2, characterized in that, The step of executing a second preset script based on the network installation bootloader to obtain environment variables includes: In response to the startup of the network installation bootloader, the second preset script is executed to execute the startup branch code therein; After performing network configuration operations according to the startup branch code, the environment configuration file is obtained from the target server. Based on the environment configuration file, the environment variables of the client environment are set.

5. The AIX operating system network installation method according to claim 1, characterized in that, The step of mounting a temporary remote NFS file system directory in the client environment based on the environment variables to generate target files and store them in the memory file system includes: Mount the first remote NFS file system directory specified by the first variable in the environment variables in the client environment, and copy the core files therein to the memory file system; Identify the hardware devices in the client environment, and store the device information and configuration data of the hardware devices in the memory file system; Mount the second remote NFS file system directory specified by the second variable in the environment variables in the client environment, and synchronize the device information and configuration data stored in the memory file system to the second remote NFS file system directory; The target file is generated based on the second remote NFS file system directory and stored in the memory file system.

6. The AIX operating system network installation method according to claim 1, characterized in that, The step of mounting the target remote NFS file system directory in the client environment based on the target file and switching the memory file system to the remote NFS file system includes: Unload the temporary remote NFS file system directory; Based on the target file, determine the NFS directory path corresponding to each local mount point in the client environment; Based on each of the NFS directory paths, mount the target remote NFS file system directory corresponding to each of the local mount points in the client environment; After switching the memory file system to the remote NFS file system, the environment variables are updated based on the target remote NFS file system directory.

7. The AIX operating system network installation method according to claim 1, characterized in that, The installation of the AIX operating system in the client environment based on the remote NFS file system includes: Call the third preset script in the remote NFS file system, and obtain the hardware and software information of the hardware devices in the client environment based on the third preset script; The system queries a preset knowledge base for parameters that match the hardware and software information, and then injects these parameters into the system configuration of the client environment. The integrity of backup files in the remote NFS file system is checked based on the third preset script. Based on the inspection results, the backup files in the remote NFS file system are restored to the local hard drive in the injected client environment; Set the local hard drive as the default boot device and restart the client environment to load the AIX operating system from the local hard drive.

8. A network installation system for the AIX operating system, characterized in that, include: The client processing unit is used to obtain a network installation bootloader generated based on a first preset script from the target server, so as to create a memory file system in the client environment; The client generation unit is used to execute a second preset script based on the network installation bootloader to obtain environment variables, and based on the environment variables, mount a temporary remote NFS file system directory in the client environment to generate target files and store them in the memory file system. The client mounting unit is used to mount the target remote NFS file system directory in the client environment based on the target file, and switch the memory file system to the remote NFS file system; The client installation unit is used to install the AIX operating system in the client environment based on the remote NFS file system.

9. A computer device, comprising: At least one processor; as well as A memory storing a computer program executable on the processor, characterized in that the processor executes the program by performing the steps of the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it performs the steps of the method as described in any one of claims 1 to 7.

Images