CN117149352A - Cloud platform implementation method and device based on different architectures - Google Patents
Cloud platform implementation method and device based on different architectures Download PDFInfo
- Publication number
- CN117149352A CN117149352A CN202311085410.6A CN202311085410A CN117149352A CN 117149352 A CN117149352 A CN 117149352A CN 202311085410 A CN202311085410 A CN 202311085410A CN 117149352 A CN117149352 A CN 117149352A
- Authority
- CN
- China
- Prior art keywords
- cloud platform
- target architecture
- cloud
- target
- agent
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 51
- 230000006978 adaptation Effects 0.000 claims abstract description 21
- 238000012545 processing Methods 0.000 claims abstract description 17
- 238000012360 testing method Methods 0.000 claims abstract description 17
- 238000012795 verification Methods 0.000 claims abstract description 14
- 238000007499 fusion processing Methods 0.000 claims description 10
- 238000012986 modification Methods 0.000 claims description 4
- 230000004048 modification Effects 0.000 claims description 4
- 230000015654 memory Effects 0.000 description 17
- 238000007726 management method Methods 0.000 description 16
- 230000008569 process Effects 0.000 description 10
- 230000006870 function Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 6
- 238000004590 computer program Methods 0.000 description 4
- 230000005291 magnetic effect Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 238000009434 installation Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 239000004744 fabric Substances 0.000 description 2
- 238000011900 installation process Methods 0.000 description 2
- 230000004807 localization Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- 241000531315 Avahi Species 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 239000000725 suspension Substances 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 230000003936 working memory Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45591—Monitoring or debugging support
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application aims to provide a cloud platform implementation method and equipment based on different architectures, which are used for installing the dependence required by a cloud platform in the environment of a target architecture server through a dependence list based on the cloud platform; adding a target architecture server to the cloud platform; creating a cloud host corresponding to a target architecture server on a cloud platform, so that different processing logics are correspondingly configured for different architectures on the cloud platform Agent; initial adaptation of a target architecture is carried out on the cloud platform Agent; verifying whether each related function of the cloud platform is normally used or not one by one through the test case list, and if the verification is passed, indicating that the cloud platform can normally operate on the target architecture; if the verification is not passed, analyzing and repairing are carried out aiming at different test scenes so as to complete the realization of the target architecture on the cloud platform, and realizing the realization of the cloud platform on different architectures so as to ensure that the cloud platform supports the normal operation on chips of different target architecture servers.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for implementing a cloud platform based on different architectures.
Background
In the prior art, a cloud platform is mainly an X86 chip supporting the main stream and a foreign open source operating system. With the trend of the localization transformation of various industries in recent years, a cloud platform needs to be operated on a localization chip and an operation system.
On chip, most cloud platforms only support the common X86 architecture: intel chip and AMD chip. The domestic X86 architecture comprises: sea light chip, megacore chip, ARM framework has: the MIPS/LoongArch architecture comprises a Feiteng chip and a spread-Peng chip: loongson chip, SW framework has: shenwei chips, the mainstream chips have been fully supported. Operating systems such as Galaxy kylin, union UOS, openEuler, centOS and Rocky Linux are supported on HostOS.
Disclosure of Invention
The application aims to provide a cloud platform realization method and device based on different architectures, which realize the realization of the cloud platform on different architectures so as to ensure that the cloud platform supports the normal operation on chips of different target architecture servers.
According to one aspect of the application, a cloud platform implementation method based on different architectures is provided, wherein the method comprises the following steps:
based on the dependency list of the cloud platform, installing the dependencies required by the cloud platform in the environment of the target architecture server;
adding the target architecture server to the cloud platform, so that fusion processing of indistinguishable architectures is performed in a management node of the cloud platform;
creating a cloud host corresponding to the target architecture server on the cloud platform, so that different processing logics are correspondingly configured for different architectures on the cloud platform Agent;
initial adaptation of a target architecture is carried out on the cloud platform Agent;
verifying whether each related function of the cloud platform is normally used one by one through a test case list, and if the verification is passed, indicating that the cloud platform can normally run on the target architecture; if the verification is not passed, analyzing and repairing are carried out aiming at different test scenes so as to complete the realization of the target architecture on the cloud platform.
Further, in the above method, the installing dependencies required by the cloud platform in the environment of the target architecture server based on the dependency list of the cloud platform includes:
determining whether the cloud platform supports an operating system of the target architecture server,
if yes, based on the dependency list of the cloud platform, executing relevant operations of the dependencies required by the cloud platform to be installed in the environment of the target architecture server;
if the related operation of deployment is executed successfully, starting the management node service;
and if the management node service is successfully started normally, finishing the dependence required by the target architecture server for installing the cloud platform.
Further, in the above method, adding the target architecture server to the cloud platform, so that a fusion process of indistinguishable architectures is performed in a management node of the cloud platform, including:
determining whether the cloud platform has supported an operating system on the target physical host,
if yes, executing the operations of software installation, software configuration and Agent deployment;
and if the executed operations are successful, completing the addition of the target architecture server to the cloud platform.
Further, in the above method, the creating, on the cloud platform, a cloud host corresponding to the target architecture server, so that, on a cloud platform Agent, different processing logic is configured correspondingly for different architectures, including:
configuring a cloud host;
judging whether hardware resources of the cloud platform meet preset resource conditions or not;
if yes, the cloud platform defines a description file of the corresponding cloud host according to user configuration;
according to the well-defined description file, matching the alternative physical machine in the hardware resource of the cloud platform;
if the alternative physical machine supports the starting of the cloud host, the alternative physical machine supporting the starting of the cloud host is used as a matched target physical machine, and the cloud host is started on the matched target physical machine;
and if the started cloud host operates normally, completing the operation of creating the cloud host corresponding to the target architecture server on the cloud platform.
Further, in the above method, the performing initial adaptation of the target architecture on the cloud platform Agent includes:
compiling Agent codes in a target architecture when the cloud platform Agent distinguishes the architecture;
if the compiling is successful, completing the adaptation of the cloud platform Agent;
if the compiling is problematic, corresponding debugging modification is performed on the problem codes in the compiling to complete adaptation of the cloud platform Agent.
According to another aspect of the present application, there is also provided a non-volatile storage medium having stored thereon computer readable instructions which, when executed by a processor, cause the processor to implement a cloud platform implementation method based on different architecture as described above.
According to another aspect of the present application, there is also provided a cloud platform implementation device based on different architecture, where the device includes:
one or more processors;
a computer readable medium for storing one or more computer readable instructions,
the one or more computer-readable instructions, when executed by the one or more processors, cause the one or more processors to implement the different architecture-based cloud platform implementation method as described above.
Compared with the prior art, the method has the advantages that the dependence required by the cloud platform is installed in the environment of the target architecture server through the dependence list based on the cloud platform; adding the target architecture server to the cloud platform, so that fusion processing of indistinguishable architectures is performed in a management node of the cloud platform; creating a cloud host corresponding to the target architecture server on the cloud platform, so that different processing logics are correspondingly configured for different architectures on the cloud platform Agent; initial adaptation of a target architecture is carried out on the cloud platform Agent; verifying whether each related function of the cloud platform is normally used one by one through a test case list, and if the verification is passed, indicating that the cloud platform can normally run on the target architecture; if the verification is not passed, analyzing and repairing are carried out aiming at different test scenes so as to complete the realization of the target architecture on the cloud platform, and realizing the realization of the cloud platform on different architectures so as to ensure that the cloud platform supports the normal operation on chips of different target architecture servers.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the accompanying drawings in which:
FIG. 1 illustrates a flow diagram of a cloud platform implementation method based on different architectures in accordance with an aspect of the present application;
FIG. 2 illustrates a schematic diagram of a fusion process of indistinguishable fabrics in a management node of a platform in a cloud platform implementation method based on different fabrics, according to one aspect of the present application;
FIG. 3 illustrates a framework diagram of different architectures in a cloud platform implementation based on different architectures to correspondingly configure different processing logic in accordance with an aspect of the present application;
FIG. 4 illustrates a schematic diagram of a cloud platform deployment of multiple agents in a cloud platform implementation approach based on different architectures, in accordance with an aspect of the present application;
FIG. 5 illustrates a flow diagram of dependencies required to install a cloud platform in an environment of a target architecture server in a different architecture-based cloud platform implementation method in accordance with one aspect of the application;
FIG. 6 illustrates a flow diagram of adding the target architecture server to the cloud platform in a different architecture-based cloud platform implementation method in accordance with an aspect of the present application;
fig. 7 is a schematic flow chart of creating a cloud host corresponding to the target architecture server on the cloud platform in a cloud platform implementation method based on different architectures according to an aspect of the present application.
The same or similar reference numbers in the drawings refer to the same or similar parts.
Detailed Description
The application is described in further detail below with reference to the accompanying drawings.
In one exemplary configuration of the application, the terminal, the device of the service network, and the trusted party each include one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer readable media, as defined herein, does not include non-transitory computer readable media (transmission media), such as modulated data signals and carrier waves.
As shown in fig. 1, a flow chart of a cloud platform implementation method based on different architectures according to an aspect of the present application is provided, and a computer language implemented by the method depends on a development language of the cloud platform itself, for example Java, python, golang and Shell. The method comprises the steps of S11, S12, S13, S14 and S15, wherein the method specifically comprises the following steps:
step S11, based on the dependency list of the cloud platform, installing the dependencies required by the cloud platform in the environment of the target architecture server;
it should be noted that the target architecture includes, but is not limited to, an X86 architecture, an ARM architecture, a MIPS architecture, a LoongArch architecture, an SW architecture, and the like.
Step S12, adding the target architecture server to the cloud platform, so that fusion processing of indistinguishable architectures is performed in a management node of the cloud platform;
step S13, creating a cloud host corresponding to the target architecture server on the cloud platform, so that different processing logics are correspondingly configured for different architectures on the cloud platform Agent;
step S14, initial adaptation of a target architecture is carried out on the cloud platform Agent;
step S15, verifying whether each related function of the cloud platform is normally used or not one by one through a test case list, and if the verification is passed, indicating that the cloud platform can normally operate on the target architecture; if the verification is not passed, analyzing and repairing are carried out aiming at different test scenes so as to complete the realization of the target architecture on the cloud platform.
In step S11, preparation work before deployment is performed, and the dependency list of the cloud platform is specific to the dependency list, which includes but is not limited to the following, where the dependency is necessary for installing the cloud platform in the environment of the target architecture server, that is, on the pre-installed operating system of the target architecture server:
audit
autoconf
autogen
avahi
avahi-tools
bash-completion
bpftool
bridge-utils
bzip2
chrony
collectd-disk
collectd-virt
conntrack-tools
createrepo
curl
cyrus-sasl-md5
device-mapper-multipath
dmidecode
dnsmasq
expect
exfat-utils
fuse-exfat
fuse-sshfs
exfat-utils
fuse-exfat
gc
gcc
gnutls-utils
grafana
guile
gzip
httpd
hwdata
ipmitool
iproute
ipset
iptables
iptables-services
iputils
iscsi-initiator-utils
java-1.8.0-openjdk
java-1.8.0-openjdk-devel
keepalived
kernel
kernel-core
kernel-devel kernel-headerskernel-moduleskernel-modules-extrakernel-toolslibffi-devellibselinux-pythonlibselinux-utilslighttpdlibtool-ltdllsoflvm2lvm2-dbusd
lvm2-libs lvm2-lockdmariadbmariadb-servermcelogmegacliMySQL-python
net-toolsnfs-utilsnginxnmapnodejsnvme-cliOpenIPMI-modaliasopensshopenssh-clientsopenssh-server
openssl-devel
pciutils
perf
psmisc
pv
python2-crypto
python2-pip
python2-pyudev
python2-pyparted
python3-libselinux
python3-perf
python-backports-ssl_match_hostname
python-devel
python-pip
python-setuptools
redis
rpcbind
rsync
sanlock
sed
sg3_utils
smartmontools
sshpass
storcli
sudo
sysfsutils
systemd
tar
tuned
unbound-libs
unzip
usbredir-server
usbutils
vconfig
vim
wget
qemu
qemu-block-rbd
libvirt
libvirt-client
libvirt-python
in this embodiment, in the process of performing the fusion processing of the indistinguishable architecture in the management node of the platform, as shown in fig. 2, after the user issues the operation instruction, the management node (corresponding to mn in fig. 2) issues an API request corresponding to the operation instruction to an Agent on the target physical host, so that the Agent on the target physical host performs corresponding processing on the API request, and after the processing is completed, returns a processing result to the management node in a form of a response body, thereby completing an operation closed loop of the fusion processing.
Further, in the process of correspondingly configuring different processing logics for different architectures on the cloud platform Agent, as shown in fig. 3, after the Agent is compiled into a bin packet, the bin packet is used for creating a corresponding service in the cloud platform deployment process, and finally, an API request on the Agent is issued from a management node, and the Agent has corresponding codes to process the processing logics of different architectures. Heretofore, the cloud platform has supported, for example, an X86 architecture and an ARM architecture, and the supporting manner of the longarch architecture may be processed according to the manners of the X86 architecture and the ARM architecture. The architecture is not distinguished in the Agent service of the cloud platform, and different processing logic corresponding to different architectures exists; once the Agent service is triggered, the corresponding processing logic can be called according to the target architecture carried by the API request.
Next, in the above embodiment of the present application, the step S14 performs initial adaptation of the target architecture for the cloud platform Agent, including:
compiling Agent codes in a target architecture when the cloud platform Agent distinguishes the architecture;
if the compiling is successful, completing the adaptation of the cloud platform Agent;
if the compiling is problematic, corresponding debugging modification is performed on the problem codes in the compiling to complete adaptation of the cloud platform Agent.
For example, in the deployment process of the cloud platform, as shown in fig. 4, different agents respectively manage different corresponding modules, for example, are responsible for creating a cloud host, a mirror server, a SharedBlock and the like in a KVM physical machine, and some agents do not distinguish between the architectures, and some agents distinguish between the architectures. Part of agents need to adapt to the architecture in the compiling process due to the difference of development languages, more modules of language software packages caused by different architecture characteristics or caused by the fact that the existing modules of the current version do not support the current architecture, so that a cloud platform runs on a CPU chip of a target architecture (such as a LoongArch architecture), and most importantly, the adaptation of ZStack Cloud Agent relates to modules of a physical machine, a network, a storage and the like. The method involves compiling an open source component and compiling a ZSTAck internal Agent warehouse. When cloud platform agents distinguish the frameworks, compiling Agent codes in a target framework (such as a LoongArch framework), if compiling is successful (i.e. no problem exists), adapting is successful, and adapting of the cloud platform agents is completed; if the compiling is problematic, corresponding debugging modification is required to be performed on the problem code in the compiling so as to complete the adaptation of the cloud platform Agent. Here, the cloud platform support of the CPU chip of the LoongArch architecture requires a server of a model number of 3C5000L, 3C5000, or the like, for example.
After the steps S11 to S14 are completed, in step S15, relevant content required by the cloud platform (such as a tool software package required in the cloud platform installation process, a cloud platform installation package and a file relied on in the cloud platform installation process) is packaged and encapsulated, so that initial adaptation is completed. The method comprises the steps that an adaptation work is used for defining initial adaptation, a finally output compressed package ISO file can meet a user use deployment manual, initialization can be completed from installation of a cloud platform to access of a cloud platform UI through a browser, creation of a cloud host is carried out, and no error exists in the access process of a cloud host console. And then verifying through a test case list, wherein the test case list is a completed list of testers aiming at cloud platform functions, and the verification process after adaptation is that the testers need to verify the test case list one by one to verify whether each related function of the cloud platform is normally used, and if the problem exists (namely that verification is not passed), analyzing and repairing are carried out aiming at different test scenes so as to complete the realization of a target architecture on the cloud platform. For example, the problem found by the cloud platform of the current target architecture in the testing process of the testers is firstly confirmed whether the operation steps are correct, then the research and development is carried out to confirm whether the problem is not supported by the current target architecture, if not, the problem environment is restored by the research and development after the Issue is submitted, and therefore the realization of the target architecture in the cloud platform is completed.
Next to the above embodiment of the present application, step S11 is a flowchart of a specific implementation of the dependencies required for installing the cloud platform in the environment of the target architecture server based on the dependency list of the cloud platform, as shown in fig. 5, and specifically includes:
firstly, judging whether the cloud platform supports an operating system of a target architecture server, and if not, directly ending;
if so (i.e., if supported), performing dependent related operations, such as software package installation and basic software configuration, of the dependencies required for installing the cloud platform in the environment of the target architecture server, based on the dependency list of the cloud platform;
then judging whether the related operation has errors in the deployment process, and if so (namely, the related operation fails to be executed, directly ending;
if the related operation of deployment is executed successfully, the management node service (corresponding to the management node service in fig. 5) is started;
finally, judging whether the management node service is started normally, if not, directly ending; and if the management node service is successfully started normally, finishing the dependence required by the target architecture server for installing the cloud platform.
Next to the above embodiment of the present application, a flowchart of a specific implementation of adding the target architecture server to the cloud platform in the step S12 is shown in fig. 6, and specifically includes:
firstly, judging whether the cloud platform supports an operating system on a target physical host, if not, directly ending the step 2;
if so, executing the operations of software installation, software configuration, agent deployment and the like in the deployment flow;
then judging whether the operation for executing deployment has failure or not, if so, directly ending;
and if the operation of executing the deployment is successful, completing the operation of adding the target architecture server to the cloud platform.
Next, in the foregoing embodiment of the present application, in the step S13, a cloud host corresponding to the target architecture server is created on the cloud platform, so that a specific implementation flowchart of configuring different processing logic correspondingly for different architectures on a cloud platform Agent is shown in fig. 7, and specifically includes:
firstly, configuring a cloud host;
secondly, judging whether hardware resources of the cloud platform meet preset resource conditions or not; here, the hardware resources of the cloud platform include, but are not limited to, a CPU remaining quota, a memory remaining quota, a main storage remaining capacity, a mirror server remaining space, and the like, and then the preset resource conditions also correspond to preset conditions such as a CPU quota, a memory quota, a main storage capacity, a mirror server space, and the like.
If the corresponding preset resource condition is not met, directly ending;
if the preset resource condition is met, the cloud platform defines a description file (such as a file of an xml suffix and the like) of the corresponding cloud host according to user configuration; here, the description file (xml suffix) of the cloud host is finally used by the virtualization component Qemu/Libvirt (software for creating and managing the cloud host) at the bottom layer of the cloud platform, and the virtualization component creates a cloud host with a corresponding configuration for parameters (such as a specific configuration of the cloud host) defined in the description file.
Then, according to the defined description file, matching the alternative physical machine in the hardware resource of the cloud platform, namely searching the proper physical machine in the hardware resource of the platform;
then, judging whether an alternative physical machine (corresponding to the proper physical machine in fig. 6) supports the starting of the cloud host, and if not, directly ending;
if an alternative physical machine (corresponding to the proper physical machine in fig. 6) supports the starting of the cloud host, taking the alternative physical machine supporting the starting of the cloud host as a matched target physical machine, and starting the cloud host on the matched target physical machine;
finally, judging whether the started cloud host operates normally, and if the started cloud host cannot operate normally (such as abnormal operation or operation suspension, etc.), directly ending;
and if the started cloud host operates normally, completing the operation of creating the cloud host corresponding to the target architecture server on the cloud platform.
According to another aspect of the present application, there is also provided a non-volatile storage medium having stored thereon computer readable instructions, which when executed by a processor, cause the processor to implement a cloud platform implementation method based on different architecture as described above.
According to another aspect of the present application, there is also provided a cloud platform implementation device based on different architectures, where the device includes:
one or more processors;
a computer readable medium for storing one or more computer readable instructions,
the one or more computer-readable instructions, when executed by the one or more processors, cause the one or more processors to implement the different architecture-based cloud platform implementation method as described above.
For details of each embodiment in the cloud platform implementation device based on the different architecture, refer to the corresponding portion of the cloud platform implementation method embodiment based on the different architecture, and will not be described herein.
In summary, according to the application, the dependence required by the cloud platform is installed in the environment of the target architecture server through the dependence list based on the cloud platform; adding the target architecture server to the cloud platform, so that fusion processing of indistinguishable architectures is performed in a management node of the cloud platform; creating a cloud host corresponding to the target architecture server on the cloud platform, so that different processing logics are correspondingly configured for different architectures on the cloud platform Agent; initial adaptation of a target architecture is carried out on the cloud platform Agent; verifying whether each related function of the cloud platform is normally used one by one through a test case list, and if the verification is passed, indicating that the cloud platform can normally run on the target architecture; if the verification is not passed, analyzing and repairing are carried out aiming at different test scenes so as to complete the realization of the target architecture on the cloud platform, and realizing the realization of the cloud platform on different architectures so as to ensure that the cloud platform supports the normal operation on chips of different target architecture servers.
It should be noted that the present application may be implemented in software and/or a combination of software and hardware, e.g., using Application Specific Integrated Circuits (ASIC), a general purpose computer or any other similar hardware device. In one embodiment, the software program of the present application may be executed by a processor to perform the steps or functions described above. Likewise, the software programs of the present application (including associated data structures) may be stored on a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. In addition, some steps or functions of the present application may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various steps or functions.
Furthermore, portions of the present application may be implemented as a computer program product, such as computer program instructions, which when executed by a computer, may invoke or provide methods and/or techniques in accordance with the present application by way of operation of the computer. Program instructions for invoking the inventive methods may be stored in fixed or removable recording media and/or transmitted via a data stream in a broadcast or other signal bearing medium and/or stored within a working memory of a computer device operating according to the program instructions. An embodiment according to the application comprises an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions, when executed by the processor, trigger the apparatus to operate a method and/or a solution according to the embodiments of the application as described above.
It will be evident to those skilled in the art that the application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is evident that the word "comprising" does not exclude other elements or steps, and that the singular does not exclude a plurality. A plurality of units or means recited in the apparatus claims can also be implemented by means of one unit or means in software or hardware. The terms first, second, etc. are used to denote a name, but not any particular order.
Claims (7)
1. A cloud platform implementation method based on different architectures, wherein the method comprises the following steps:
based on the dependency list of the cloud platform, installing the dependencies required by the cloud platform in the environment of the target architecture server;
adding the target architecture server to the cloud platform, so that fusion processing of indistinguishable architectures is performed in a management node of the cloud platform;
creating a cloud host corresponding to the target architecture server on the cloud platform, so that different processing logics are correspondingly configured for different architectures on the cloud platform Agent;
initial adaptation of a target architecture is carried out on the cloud platform Agent;
verifying whether each related function of the cloud platform is normally used one by one through a test case list, and if the verification is passed, indicating that the cloud platform can normally run on the target architecture; if the verification is not passed, analyzing and repairing are carried out aiming at different test scenes so as to complete the realization of the target architecture on the cloud platform.
2. The method of claim 1, wherein the cloud platform-based dependency list, installing dependencies required by a cloud platform in an environment of a target architecture server, comprises:
determining whether the cloud platform supports an operating system of the target architecture server,
if yes, based on the dependency list of the cloud platform, executing relevant operations of the dependencies required by the cloud platform to be installed in the environment of the target architecture server;
if the related operation of deployment is executed successfully, starting the management node service;
and if the management node service is successfully started normally, finishing the dependence required by the target architecture server for installing the cloud platform.
3. The method of claim 1, wherein adding the target architecture server to the cloud platform such that a fusion process of indistinguishable architectures is performed in a management node of the cloud platform comprises:
determining whether the cloud platform has supported an operating system on the target physical host,
if yes, executing the operations of software installation, software configuration and Agent deployment;
and if the executed operations are successful, completing the addition of the target architecture server to the cloud platform.
4. The method of claim 1, wherein the creating, on the cloud platform, a cloud host corresponding to the target architecture server such that, on a cloud platform Agent, different processing logic is configured for different architecture correspondence, comprises:
configuring a cloud host;
judging whether hardware resources of the cloud platform meet preset resource conditions or not;
if yes, the cloud platform defines a description file of the corresponding cloud host according to user configuration;
according to the well-defined description file, matching the alternative physical machine in the hardware resource of the cloud platform;
if the alternative physical machine supports the starting of the cloud host, the alternative physical machine supporting the starting of the cloud host is used as a matched target physical machine, and the cloud host is started on the matched target physical machine;
and if the started cloud host operates normally, completing the operation of creating the cloud host corresponding to the target architecture server on the cloud platform.
5. The method of claim 1, wherein the initial adaptation of the target architecture for the cloud platform Agent comprises:
compiling Agent codes in a target architecture when the cloud platform Agent distinguishes the architecture;
if the compiling is successful, completing the adaptation of the cloud platform Agent;
if the compiling is problematic, corresponding debugging modification is performed on the problem codes in the compiling to complete adaptation of the cloud platform Agent.
6. A non-volatile storage medium having stored thereon computer readable instructions which, when executed by a processor, cause the processor to implement the method of any of claims 1 to 5.
7. Cloud platform implementation device based on different architectures, wherein the device comprises:
one or more processors;
a computer readable medium for storing one or more computer readable instructions,
when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311085410.6A CN117149352A (en) | 2023-08-25 | 2023-08-25 | Cloud platform implementation method and device based on different architectures |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311085410.6A CN117149352A (en) | 2023-08-25 | 2023-08-25 | Cloud platform implementation method and device based on different architectures |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117149352A true CN117149352A (en) | 2023-12-01 |
Family
ID=88898077
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311085410.6A Pending CN117149352A (en) | 2023-08-25 | 2023-08-25 | Cloud platform implementation method and device based on different architectures |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117149352A (en) |
-
2023
- 2023-08-25 CN CN202311085410.6A patent/CN117149352A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9811360B2 (en) | Dynamic determination of application server runtime classloading | |
| US7735078B1 (en) | System and method for software patching for cross-platform products | |
| CN110187914B (en) | Application development method, system and device | |
| US7519630B2 (en) | Method and system for automated testing of versioned information handling system applications | |
| US9823909B1 (en) | Program code conversion for cross-platform compatibility | |
| US7739698B2 (en) | Multiplatform API usage tool | |
| CN110673924B (en) | Multi-architecture container cloud mirror image selection method, device, equipment and storage medium | |
| US20080196004A1 (en) | Apparatus and method for developing component-based software | |
| US20020059561A1 (en) | Software package verification | |
| US7941792B2 (en) | System and method for compiling program code ahead of time | |
| CN111767226B (en) | Cloud computing platform resource testing method, system and equipment | |
| US7185235B2 (en) | Test and verification framework | |
| US20050086640A1 (en) | Initiating execution of application programs on a data processing arrangement | |
| US11200048B2 (en) | Modification of codified infrastructure for orchestration in a multi-cloud environment | |
| US20150074657A1 (en) | Runtime detection of software configurations and upgrades | |
| CN112764766B (en) | Method, device and equipment for butting k8s cluster and storage medium | |
| CN104137062A (en) | Dynamic injection of code into running process | |
| US9779014B2 (en) | Resilient mock object creation for unit testing | |
| US20210141632A1 (en) | Automated software patching for versioned code | |
| CN114546819A (en) | Code processing method and device, electronic equipment and readable medium | |
| CN117149352A (en) | Cloud platform implementation method and device based on different architectures | |
| WO2017039588A1 (en) | Software patch fix based on checksums | |
| CN112860552B (en) | Keyword mechanism operation method and device | |
| CN111367796A (en) | Application program debugging method and device | |
| CN117171037A (en) | Patch testing method and device based on heterogeneous cloud platform |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |