CN111930290B

CN111930290B - Resource deployment method and device

Info

Publication number: CN111930290B
Application number: CN202010986027.8A
Authority: CN
Inventors: 董明骏; 吴昕; 孟方
Original assignee: Alibaba Cloud Computing Ltd
Current assignee: Alibaba Cloud Computing Ltd
Priority date: 2020-09-18
Filing date: 2020-09-18
Publication date: 2021-04-27
Anticipated expiration: 2040-09-18
Also published as: CN111930290A

Abstract

One or more embodiments of the present specification provide a resource deployment method and apparatus, where the method may include: displaying a resource configuration interface, wherein the resource configuration interface comprises configuration components corresponding to available resources; in response to a configuration operation implemented by at least one configuration component selected by a user, determining a configuration parameter specified by the configuration operation and aiming at a target resource; and generating a resource deployment file based on the configuration parameters and submitting the resource deployment file to a server so that the server generates a resource deployment script for deploying the target resource according to the resource deployment file.

Description

Resource deployment method and device

Technical Field

One or more embodiments of the present disclosure relate to the field of cloud computing, and in particular, to a resource deployment method and apparatus.

Background

When building a network project, it is often necessary to deploy project-related application resources. For example, when a user builds a cloud project, a basic resource architecture diagram can be drawn first, and then, operation and maintenance personnel of the cloud resource deploy the application resources on each resource control console in sequence according to the resource architecture diagram. Or, the user may manually configure the resource interface through the script editor, thereby implementing editing of the resource deployment script.

Disclosure of Invention

In view of this, one or more embodiments of the present disclosure provide a resource deployment method and apparatus.

To achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions:

according to a first aspect of one or more embodiments of the present specification, there is provided a resource deployment method, including:

displaying a resource configuration interface, wherein the resource configuration interface comprises configuration components corresponding to available resources;

in response to a configuration operation implemented by at least one configuration component selected by a user, determining a configuration parameter specified by the configuration operation and aiming at a target resource;

and generating a resource deployment file based on the configuration parameters and submitting the resource deployment file to a server so that the server generates a resource deployment script for deploying the target resource according to the resource deployment file.

According to a second aspect of one or more embodiments of the present specification, there is provided a resource deployment method, including:

receiving a resource deployment file submitted by a client, wherein the resource deployment file is generated by the client according to configuration operation carried out by a user aiming at least one configuration component, and the resource configuration component is displayed in a resource configuration interface by the client;

and generating a resource deployment script according to the resource deployment file, wherein the resource deployment script is used for deploying the target resource corresponding to the at least one configuration component.

According to a third aspect of one or more embodiments of the present specification, there is provided a resource deployment apparatus, including:

the interface display unit is used for displaying a resource configuration interface, and the resource configuration interface comprises configuration components corresponding to available resources;

the parameter determining unit is used for responding to the configuration operation carried out by at least one configuration component selected by a user, and determining the configuration parameters which are specified by the configuration operation and aim at the target resource;

and the file generation unit is used for generating a resource deployment file based on the configuration parameters and submitting the resource deployment file to a server so that the server generates a resource deployment script for deploying the target resource according to the resource deployment file.

According to a fourth aspect of one or more embodiments of the present specification, there is provided a resource deployment apparatus, including:

the file receiving unit is used for receiving a resource deployment file submitted by a client, the resource deployment file is generated by the client according to configuration operation carried out by a user aiming at least one configuration component, and the resource configuration component is displayed in a resource configuration interface by the client;

and the script generating unit is used for generating a resource deployment script according to the resource deployment file, and the resource deployment script is used for deploying the target resource corresponding to the at least one configuration component.

According to a fifth aspect of one or more embodiments herein, there is provided an electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the method of any of the first or second aspects by executing the executable instructions.

According to a sixth aspect of one or more embodiments of the present description, there is provided a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method according to any one of the first or second aspects.

Drawings

FIG. 1 is an architectural diagram of a resource deployment system according to an exemplary embodiment.

FIG. 2 is a flowchart of a method for resource deployment in accordance with an illustrative embodiment.

FIG. 3 is a flowchart of another method for resource deployment provided by an exemplary embodiment.

FIG. 4 is an interaction flow diagram of a method for resource deployment in accordance with an illustrative embodiment.

5-9 (b) are presentation effect diagrams of one or more resource configuration interfaces provided by one or more exemplary embodiments.

Fig. 10 is a schematic diagram of an apparatus according to an exemplary embodiment.

FIG. 11 is a block diagram of a resource deployment apparatus provided in an example embodiment.

FIG. 12 is a block diagram of another resource deployment apparatus provided in an example embodiment.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.

It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described herein. In some other embodiments, the method may include more or fewer steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.

FIG. 1 is an architectural diagram of a resource deployment system according to an exemplary embodiment. As shown in fig. 1, the system may include a network 10, a server 11, a number of electronic devices, such as a computer 12, a computer 13, a computer 14, and so on.

The server 11 may be a physical server comprising a separate host, or the server 11 may be a virtual server carried by a cluster of hosts. During the operation, the server 11 may run a server-side program of an application to implement a relevant application function of the application, for example, when the server 11 runs a program of a resource deployment system, the server may be implemented as a server of the resource deployment system, where the resource deployment system may control or deploy a callable application resource. In the technical solution of one or more embodiments of the present specification, the server 11 may cooperate with the client running on the computers 12 to 14 to implement a technical solution for automatically deploying the application resources that can be invoked.

In this embodiment, the resource deployment system may not only implement the resource deployment function, but also be used as an integrated functional platform of many other functions, such as displaying a resource configuration interface, detecting a user configuration operation, dynamically and statically verifying the user configuration operation, generating a deployment file, verifying a target resource, and generating a resource deployment script, which is not limited in one or more embodiments of the present specification.

Computers 12-14 are but one type of electronic device that a user may use. In fact, it is obvious that the user can also use electronic devices of the type such as: a mobile phone, a tablet device, a notebook computer, a pda (Personal Digital assistants), a wearable device (such as smart glasses, a smart watch, etc.), etc., which are not limited by one or more embodiments of the present disclosure. During operation, the electronic device may run a client-side program of an application to implement a relevant application function of the application, for example, when the electronic device runs a program of a resource deployment system, the electronic device may be implemented as a client of the resource deployment system.

In addition, an application program of a resource deployment system client can be pre-installed on the electronic device, so that the client can be started and run on the electronic device; of course, when an "online client" such as HTML5 technology is employed, the client can be obtained and run without installing a corresponding application on the electronic device.

And the network 10, which interacts between the computers 12-14 and the server 11, may include various types of wired or wireless networks.

When building a network project, it is often necessary to deploy project-related application resources. For example, when a user uses a cloud resource to build a cloud project, a basic resource architecture diagram can be drawn first, and then, operation and maintenance personnel of the cloud resource deploy the application resource on each resource control console in sequence according to the resource architecture diagram. Or, the user may manually configure the resource interface through the script editor, thereby implementing editing of the resource deployment script.

However, no matter the operation and maintenance personnel configure the resources on the resource console or compile the resource deployment script according to the reference manual, and then implement the resource deployment by executing the script, or the user manually configures the resource interface by using the script editor to edit the resource deployment script, the operation and maintenance personnel and the user are faced with the underlying script or interface, and implement the deployment of the application resources by manual editing, so the workload of the resource deployment is large, and the deployment efficiency is low.

In order to solve the above technical problems in the related art, the present specification provides a resource deployment method, in which a client provides a configuration component corresponding to an available resource for a user according to a resource visualization principle, and automatically generates a resource deployment file according to a configuration operation performed on the configuration component by the user, and a server automatically generates a script for deploying an application resource based on the resource deployment file submitted by the client, so that the user can obtain the resource deployment script automatically generated by the server only by completing simple configuration of the configuration component in a visualized resource configuration interface, thereby simplifying the configuration operation of the user, and facilitating implementation of efficient deployment of the application resource.

FIG. 2 is a flowchart of a method for resource deployment in accordance with an illustrative embodiment. As shown in fig. 2, the method applied to the client may include the following steps:

step 202, a resource configuration interface is displayed, wherein the resource configuration interface comprises configuration components corresponding to available resources.

In this embodiment, the architecture diagram drawing and the automatic generation of the resource deployment script are completed through data interaction between the client and the server. The resource configuration application may be run in the client, and the resource configuration application may be an independent application program, or may also be an "online application" displayed and implemented by a browser, which is not limited in this specification. The user can control the resource configuration application running in the client to display the resource configuration interface, and further implement corresponding control operation on the relevant interface elements displayed in the interface, such as drawing a resource architecture diagram and the like, so as to realize the configuration of the resource, namely drawing the resource architecture diagram.

In this embodiment, the resource types of the available resource and the target resource may be cloud resources corresponding to the cloud service, for example, the resource types may be a storage resource, a network resource, a security resource, a control resource, and the like; of course, the resource may also be a local resource, which is not limited in this application. For available resources for users, corresponding configuration components may be generated in advance, for example, providers of the available resources may respectively make corresponding configuration components according to available resources such as storage resources, network resources, security resources, control resources, and the like. The configuration component is used for being displayed in the resource configuration interface for a user to select and carry out corresponding configuration, and can be subjected to pseudo-materialization processing on the appearance of the configuration component in order to facilitate the user to identify and select the configuration component corresponding to the application function of the user, so that the user can visually know the corresponding available resource through the configuration component, the learning cost of the user is reduced, and the use experience of the user is improved.

In this embodiment, the generation of the configuration component may be completed by the server, or may be provided and stored in the server after being generated by other devices, or may be stored in other storage devices for the server to call. Correspondingly, for a client in the form of an independent application program, the client can complete acquisition of the configuration component while installing the resource configuration application, for example, the configuration file corresponding to the configuration component is integrated in the installation package of the resource configuration application; or, after the resource configuration application is installed, the configuration component may be acquired from the server, or the configuration component may be periodically acquired from the server, so as to update the local configuration component; for a client in an online application form, the configuration component may be requested to be acquired from a server when the client is run or the resource configuration interface is opened in the client, and the acquisition manner of the configuration component is not limited in this specification. After the configuration component is obtained, the server can be correspondingly displayed in a preset area of the resource configuration interface according to a preset format, so that a user can conveniently select the required configuration component from the configuration component.

In an embodiment, a client may display component prompt information in a resource display interface, where the component prompt information may be used to indicate whether a configuration component is available, so that a user may select only an available configuration component to draw a resource architecture diagram, thereby avoiding rework caused by a drawing error; it can be understood that whether the configuration component is available is whether the resource corresponding to the configuration component is available, and because the available resource corresponding to the configuration component can be simultaneously used by multiple users, in order to ensure the accuracy of the available state of the configuration component, the client may obtain the available state of the resource corresponding to the client from the server when the configuration component is displayed or periodically. Or, the component prompt information may prompt an association relationship between a plurality of available resources corresponding to the configuration component, so that the user selects a plurality of configuration components to draw the resource architecture diagram according to the association relationship, and the difficulty of identifying the interrelation between the plurality of configuration components by the user is simplified, thereby further simplifying the user operation. Of course, the component prompt message may also prompt the two messages or other messages at the same time, and is not described again.

Step 204, in response to the configuration operation implemented by the at least one configuration component selected by the user for the configuration component, determining the configuration parameters specified by the configuration operation for the target resource.

In this embodiment, a user may select a configuration component required by an application from the configuration components shown in the resource configuration interface, and perform a configuration operation on the configuration component. In fact, the process of implementing the configuration operation for the configuration component is a process of processing the configuration component through actions of dragging, pulling, connecting, and the like to draw the resource architecture diagram.

In one embodiment, a deployment flow diagram or other form of descriptive information may be automatically presented to a user in a resource configuration interface to facilitate the user drawing a resource architecture diagram, given that the user may be a novice user who is not yet familiar with the resource deployment flow. In addition, a preset optimal configuration scheme may also be automatically recommended for the user, for example, a resource configuration template in multiple scenes may be generated in advance, so that a corresponding resource configuration template is recommended for the user to select according to an application scene corresponding to a resource architecture diagram to be drawn by the user, and the user may draw his or her resource architecture diagram according to the resource configuration template, or may modify the resource configuration template to obtain his or her resource architecture diagram.

In an embodiment, during the process of implementing the configuration operation by the user, the client may perform dynamic verification on the configuration operation and the target resource corresponding to the configuration operation. For example, the client may verify whether the configuration operation satisfies a preset resource configuration rule, and in a case that the configuration operation does not satisfy the resource configuration rule, display correction prompt information about the configuration operation, so that the user may perform the configuration operation again according to the correction prompt information, thereby ensuring that the drawn resource architecture diagram satisfies the resource configuration rule. By continuing the dynamic verification in the process of implementing the configuration operation by the user, the method is beneficial to timely correcting the error operation of the user, and avoids the complex operation caused by correcting the error after the user draws the resource architecture diagram, thereby further improving the resource configuration efficiency. The resource allocation rule may be preset according to resource characteristics of each available resource and a data transmission relationship between each available resource, and the correction prompt information may further include corresponding illegal reasons, modification suggestions, and the like, which are not described again.

Further, the configuration operation may include a connection operation of connecting a plurality of configuration components to draw the resource architecture diagram. Correspondingly, in the implementation process of the connection operation, the client detects whether a plurality of available resources corresponding to the plurality of configuration components meet a preset association rule (dynamic verification) or not, so as to correspondingly display and correct the prompt information according to the detection result. For example, the RDS (Relational Database) cannot connect to the EIP (Elastic IP Address), when detecting that the user performs a connection operation between the RDS and the EIP, the client may display a correction prompt message to prompt the user that the current connection operation does not satisfy the association rule. After the connection operation is completed, the resource architecture diagram drawn by the user is obtained correspondingly, and at this time, the client can detect whether the target resource included in the resource architecture diagram meets a preset legitimacy rule (static verification). Of course, for any resource architecture diagram drawn by the user, the client may also perform the above dynamic verification during the drawing process, and perform the above static verification after the drawing is completed; in addition, the verification rules of the dynamic verification and the static verification may further include preset rules thereof, which are not described in detail.

In an embodiment, in addition to the connection operation, the configuration operation performed by the user for the configuration component may also carry a specified parameter value for the configuration component, so that the parameter value for the configuration component is specified in the process of implementing the configuration operation. Correspondingly, under the condition that the configuration operation has the corresponding specified parameter value, the client can set the resource parameter of the target resource corresponding to the configuration operation as the specified parameter value; and/or, in the case that the specified parameter value does not exist in the configuration operation, the client may set the resource parameter of the target resource corresponding to the configuration operation as a preset default parameter. Through the method, the user is allowed to perform user-defined setting on the parameter values with finer granularity, so that the resource architecture diagram which better meets the actual application requirements of the user can be drawn conveniently, and finally the resource deployment script which can meet the actual application requirements of the user is generated. For example, in the case where the configuration component is a database, a user may set a storage capacity, a data maximum throughput, an access interface, and the like for the database to specify parameter values; in the case where the configuration component is a network port, the user may set parameter values such as an access address, a network bandwidth, a port protocol, and the like for the network port. For any configuration component, the user can perform the above-mentioned custom setting, and certainly, under the condition that the user does not perform the above-mentioned custom setting, the client can automatically set preset default parameters for the user; of course, the user may be further reminded that a custom setting will be made for the parameter value that must be set by the user.

In an embodiment, a user may implement an auxiliary configuration operation for a target resource corresponding to a configuration component to establish an edge relationship between the target resources, that is, an association relationship for implementing an auxiliary deployment function. Correspondingly, when detecting an auxiliary configuration operation performed by a user for a target resource, the client may set an auxiliary deployment parameter specified by the auxiliary configuration operation for the target resource, so that the server generates an auxiliary deployment script corresponding to the target resource based on the auxiliary deployment parameter, where the auxiliary deployment script is used to implement a preset auxiliary deployment function. For example, a user may configure a monitoring port on a connection between an SLB (Server Load Balancer) and an ECS (electronic computer Service, cloud Server), or configure parameters such as an access rule and an IP segment on a connection between an NAT (Network Address Translation) device and an ECS or in an NAT, which is not described in detail. Through the implementation of the auxiliary configuration operation, a user can automatically establish a dependency relationship among the designated target resources, so that resource linkage among all the target resources is realized.

Step 206, generating a resource deployment file based on the configuration parameters and submitting the resource deployment file to a server, so that the server generates a resource deployment script for deploying the target resource according to the resource deployment file.

In this embodiment, after determining the configuration parameters, the client may generate a corresponding resource deployment file. The process of generating the resource deployment file is a process of generating a file frame meeting a preset rule according to a resource architecture diagram drawn by a user, and filling configuration parameters corresponding to each configuration component in the resource architecture diagram into the file frame to generate the resource deployment file. The file format of the resource deployment file may take various forms, for example, xml (eXtensible Markup Language) format or json (Java Script Object Notation) format, which is not limited in this specification.

In an embodiment, the resource deployment file generated by the client according to the configuration parameters corresponds to a target resource architecture, and at this time, the user may perform an architecture merging operation for a plurality of resource architectures. Correspondingly, the client may determine the resource architecture to be merged in response to the architecture merging operation performed by the user for the target resource architecture, and then generate a merged deployment file according to the resource deployment files respectively corresponding to the target resource architecture and the resource architecture to be merged, where the merged deployment file is used to generate a merged resource deployment script for the merged resource architecture corresponding to the target resource architecture and the resource architecture to be merged, and the merged resource deployment script is used to deploy all target resources corresponding to the target resource architecture and the resource architecture to be merged. Through the merging process, the client can merge a plurality of resource frameworks including the target resource framework and the resource framework to be merged to obtain the merged resource framework, so that the server can generate corresponding merged resource deployment scripts according to the merged deployment files corresponding to the merged resource framework, and can integrally deploy all target resources, thereby rapidly expanding new resources on the basis of the original resource framework no matter whether the original resource framework deploys corresponding resources, realizing rapid and efficient expansion of the framework or functions, and reducing the difficulty in framework expansion.

Further, the resource architecture to be merged may be specified by a user, so that the user may perform architecture adjustment according to actual application changes, and at this time, the client may correspondingly determine the resource architecture to be merged specified by the user. Or, in the case that any resource architecture is added with an architecture classification identifier in advance, the client may also determine a resource architecture whose architecture classification identifier is the same as the architecture classification identifier of the target resource architecture as the resource architecture to be merged, so as to merge resource architectures of the same type, where the architecture classification identifier may be added according to a resource type, an application type, and the like. In fact, the resource architecture to be merged may be a new resource architecture that has not been deployed, or may be a resource architecture that has been deployed,

further, the client may generate the merged deployment file by: the method comprises the steps of firstly determining a first target resource corresponding to a target resource architecture and a second target resource corresponding to a resource architecture to be merged, then generating a public deployment file according to the same part of the first target resource and the second target resource, respectively generating a special deployment file according to different parts of the first target resource and the second target resource, and finally merging the public deployment file and the special deployment file according to a preset rule, thereby obtaining a merged deployment file. The merged deployment file merged by the method can simultaneously generate deployment scripts corresponding to all target resources corresponding to the two resource architectures, so that the architecture merging operation of a user is effectively simplified, and the architecture merging and script generating efficiency is improved.

Meanwhile, the client can submit the resource deployment file generated in the above manner to the server for generating a corresponding resource deployment script. Of course, before submission, further rule verification may be performed on the file and the target resource corresponding to the file to ensure that the file meets the preset rule. In addition, the user may also be prompted by detection after the verification is passed, and the resource deployment file may be submitted to the server after the submission operation performed by the user is detected, which is not described in detail again in the specific process.

FIG. 3 is a flowchart of another method for resource deployment provided by an exemplary embodiment. As shown in fig. 3, the method applied to the client may include the following steps:

step 302, receiving a resource deployment file submitted by a client, where the resource deployment file is generated by the client according to a configuration operation performed by a user for at least one configuration component, and the resource configuration component is displayed in a resource configuration interface by the client.

In an embodiment, after receiving the resource deployment file, the server may determine a resource type and/or a resource demand of the target resource, and then access a resource management interface corresponding to the resource collection to verify whether an available resource in the resource collection meets the resource type and/or meets the resource demand. The resource type and the resource demand can be configured by the user when configuring the parameters. Correspondingly, under the condition that the available resources are verified to be in accordance with the resource types and the resource demand, the server side can generate corresponding resource deployment scripts according to the resource deployment files, and certainly, verification results can be returned to the client side and the resource deployment scripts can be generated after the user confirms; and under the condition that the available resources are not in accordance with the resource types or the resource demand, the server side can return a verification result and/or a modification suggestion to the client side, so that the user can modify the configuration parameters according to the modification suggestion until the resource deployment file is in accordance with the resource types and the resource demand. Of course, besides the resource type and the resource demand, the server may also perform other verification on the target resource, and details are not repeated.

Step 304, generating a resource deployment script according to the resource deployment file, wherein the resource deployment script is used for deploying the target resource corresponding to the at least one configuration component.

In an embodiment, the server may first convert the resource deployment file into a DAG (Directed Acyclic Graph) corresponding to the target resource, and then generate the resource deployment script according to the Directed Acyclic Graph.

In an embodiment, when the resource deployment file includes an auxiliary deployment parameter corresponding to the target resource, the server may further generate an auxiliary deployment script corresponding to the target resource based on the auxiliary deployment parameter, where the auxiliary deployment script is used to implement a preset auxiliary deployment function, so as to implement an effective response to an auxiliary deployment operation performed by a user. Through the implementation of the auxiliary configuration operation, a user can automatically establish a dependency relationship among the designated target resources, so that resource linkage among all the target resources is realized.

In this embodiment, the resource deployment script generated in the above manner may be run on the server, or may also be sent to other devices by the server and run. The resource deployment script in the running state is used for deploying a target resource for which a configuration operation implemented by a user aims, and the deployed target resource is used for realizing an application function of the user.

Through the embodiment, a user can perform configuration operation on the configuration component in the client to set the configuration parameters for the target resource, correspondingly, the client generates the resource configuration file according to the configuration parameters and submits the resource configuration file to the server, and the server generates the resource deployment script for the target resource by using the resource configuration file to realize the application function of the user. Therefore, the user only needs to simply perform parameter configuration on the visual configuration component in the resource configuration interface to draw the resource architecture diagram, and the configuration component corresponds to the target resource, so that the configuration component in the resource configuration component presents the display effect of 'what you see is what you get' on the target resource to the user, and the user experience is better; and the subsequent file and script generation process is automatically completed by the client and the server, so that the resource deployment operation of the user is greatly simplified, and the resource deployment efficiency of the user is effectively improved.

The following describes in detail the process of completing the architecture diagram drawing and the automatic generation of the resource deployment script by the client and the server through data interaction, with reference to the interaction flowchart of the resource deployment method shown in fig. 4 and the display effect schematic diagrams of the resource configuration interfaces shown in fig. 5 to fig. 9 (b). As shown in fig. 4, the process is implemented by the interaction between the client and the server, and the process includes the following steps:

at step 402, the client exposes a resource configuration interface that includes a configuration component.

In this embodiment, a resource configuration application runs in the client, and the resource configuration application may be an independent application program or an "online application" displayed and implemented through a browser, which is not limited in this specification. Furthermore, the user client may display a resource configuration interface to the user after receiving a preset trigger operation of the user, where the interface includes a configuration component corresponding to an available resource. The configuration component can be generated in advance by other equipment at the server side according to available resources, and the appearance of the configuration component can be subjected to pseudo-materialization processing in the generation process, so that a user can visually know the corresponding available resources through the configuration component, the learning cost of the user is reduced, and the use experience of the user is improved.

The available resources are resources that can be called by a user for deployment, such as storage resources, network resources, security resources, control resources, and the like, and certainly, available members corresponding to different users may be different, for example, the user U may obtain corresponding available resources in a manner of getting or purchasing, so that when the user U logs in a client and opens a corresponding resource configuration interface, a configuration component displayed in the interface is an available resource that can be used by the user U.

For example, after a user performs preset trigger operations such as clicking and touching on display controls such as buttons and icons of a resource configuration interface in a client, the client responds to the preset trigger operations to correspondingly display the resource configuration interface and display a configuration component in the resource configuration interface. The configuration component may be acquired by the client after detecting the preset trigger operation and then acquired by the server (not shown in the figure), or acquired by the client in advance at one time or periodically.

Taking fig. 5 as an example, a configuration component candidate area 501 is displayed in the resource configuration interface, a configuration component to be selected by the user is displayed in the area, and the configuration component may be respectively displayed in different display areas according to the component type, such as a plurality of folding display areas of storage resources, network resources, security resources, control resources, and the like in the drawing. Of course, the user may expand the configuration component area of the folded display by triggering the expansion icon in any folded display area, thereby displaying the configuration components contained in the folded display area in detail. An architecture drawing area 502 is shown on the right side of the interface, and a user can place the configuration component shown in the left configuration component candidate area 501 in a suitable position of the right architecture drawing area 502 by dragging or clicking.

As shown in FIG. 5, when the user triggers the expansion icon in the "storage component" corresponding to the folded display area, the folded display area is expanded to display the configuration component 601, and the display effect is as shown in FIG. 6. The client may display component prompt information in the resource display interface, where the component prompt information may be used to indicate whether the configuration component is available (not shown in the figure), so that the user only selects an available configuration component to draw the resource architecture diagram, and rework caused by a drawing error is avoided to a certain extent. It can be understood that whether the configuration component is available is whether the resource corresponding to the configuration component is available, and because the available resource corresponding to the configuration component can be simultaneously used by multiple users, in order to ensure the accuracy of the available state of the configuration component, the client may obtain the available state of the resource corresponding to the client from the server when the configuration component is displayed or periodically. The component prompt information may have a plurality of display forms, for example, the configuration component corresponding to the resource in the unavailable state may be displayed as a gray image, and the configuration component corresponding to the resource in the available state may be displayed as a color image; or showing the | in a specific position, such as the upper right corner of the configuration component corresponding to the resource in the unavailable state! "etc., to inform the user. Or, the component prompt information may prompt an association relationship between a plurality of available resources corresponding to the configuration component, so that the user selects a plurality of configuration components to draw the resource architecture diagram according to the association relationship, and the difficulty of identifying the interrelation between the plurality of configuration components by the user is simplified, thereby further simplifying the user operation. For example, the configuration component a and the configuration component B in fig. 6 have a preset association relationship therebetween, and accordingly, the association relationship between the configuration component a and the configuration component B may be labeled by the association area boundary 602. Of course, the component prompt message may also prompt the two messages or other messages at the same time, and is not described again.

At step 404, the client detects a configuration operation performed by a user with respect to the configuration component.

The user can implement configuration operation aiming at the configuration component shown in the resource configuration interface so as to set corresponding resource parameters for the target resource through the operation. The configuration operation may have various forms, for example, a drag action of dragging the configuration component from the left display area to the right drawing area, a double-click operation of opening a parameter configuration detail page corresponding to any configuration component in the drawing area, an input operation or a selection operation corresponding to inputting or selecting a parameter value for any parameter item in the parameter detail page, and the like, which are not described again.

As illustrated in FIG. 6, the user may drag configuration component D in the presentation area on the left side of the interface with the mouse, placing it at location 603 in the drawing area on the right side of the interface. The method supports the user to draw the resource architecture diagram in a simple drawing mode, so that the user does not need to pay attention to the bottom layer script details corresponding to the configuration assembly, and only needs to draw, connect and configure parameters of the whole configuration assembly, thereby effectively simplifying the drawing operation of the resource architecture diagram and the deployment operation of the target resource by the user, and being beneficial to improving the resource deployment efficiency.

At step 406, the client dynamically verifies the configuration operation.

For any configuration operation implemented by a user, the client can verify whether the operation meets a preset resource configuration rule in real time, and display correction prompt information about the configuration operation under the condition that the configuration operation does not meet the resource configuration rule, so that the user can implement the configuration operation again according to the correction prompt information, and the drawn resource architecture diagram is ensured to meet the resource configuration rule. The resource allocation rule may be preset according to resource characteristics of each available resource and a data transmission relationship between each available resource, and the correction prompt information may further include an illegal reason, a modification suggestion, and the like, which is not described in detail. The dynamic verification is carried out on the configuration operation implemented by the user, so that the target resources related to the resource architecture diagram and the architecture rationality of the target resources are automatically checked, the target resources can be automatically ensured to meet the preset relation, constraint and attribute characteristics without paying attention to the bottom layer relevance of each target resource by the user, and the rationality and the effectiveness of the finally generated resource deployment script are further ensured.

As shown in fig. 7, after the user places the ECS 701 and the SLB 703 in the drawing interface, a connection line 702 is drawn therebetween by a connection operation. In the process of the user performing the connection operation, the client may correspondingly detect whether the ECS 701 and the SLB 703 satisfy a preset association rule, and further display the correction prompt information according to the detection result. In this implementation, direct connection (i.e., meeting a preset association rule) is generally allowed between the ECS 701 and the SLB 703, so that the user can draw the connection 702 between the ECS 701 and the SLB normally. Assuming that the user performs the connection operation between the RDS and the EIP, because the RDS and the EIP generally cannot be directly connected (i.e. do not satisfy the preset association rule), the client may display the correction prompt information to prompt the user that the current connection operation does not satisfy the association rule after detecting that the user performs the connection operation between the RDS and the EIP.

In step 408, the client sets the resource parameters of the target resource according to the configuration operation.

In an embodiment, the user may also open a parameter detail page of the ECS 701 or the SLB 703 by double-clicking (or other preset operations), and then set each parameter of the ECS 701 and/or the SLB 703 in the page by selecting or inputting, etc. As shown in fig. 8(a), the user can set the number of servers, the server capacity, the storage space size, the number of CPU cores, the access address, the number of nodes, the IP address field, and the like in the parameter detail page of the ECS 701. Alternatively, as shown in fig. 8(b), the user may also open the parameter detail page of the connection 702 in the above manner, and configure the communication parameters, such as an interface protocol, a transmission rate, a network bandwidth, an IP address field, and the like, of the connection (where the connection represents a data transmission channel between the ECS 701 and the SLB 703) accordingly, which are not described in detail any more.

After the user completes the parameter configuration for a certain configuration component, the available resource corresponding to the configured component is the corresponding target resource.

In an embodiment, the client may automatically set preset parameters for the target resource according to a configuration operation performed by the user for the target resource. Because ECS is generally used to store and process user application data with high security requirements, in fig. 7, when detecting that the user places the ECS 701 in the drawing area, the client checks whether a security group is currently set, and automatically sets the security group and configures default parameters if the security group is not set, thereby effectively avoiding data leakage and other security problems that may be caused by the user forgetting to set the security group; the user may be further informed of the settings of the security group so that the user may check or change configuration parameters. For another example, after the user draws the connection 702, the client may automatically add the IP address of the ECS 701 to the backserver list of the SLB 703 to further simplify the parameter configuration operation of the user.

In step 410, the client detects the auxiliary configuration operation performed by the user and sets auxiliary deployment parameters.

In an embodiment, a user may perform an auxiliary configuration operation on a target resource corresponding to a configuration component, and accordingly, when the auxiliary configuration operation performed on the target resource by the user is detected, a client may set an auxiliary deployment parameter specified by the auxiliary configuration operation for the target resource, so that a server generates an auxiliary deployment script corresponding to the target resource based on the auxiliary deployment parameter, where the auxiliary deployment script is used to implement a preset auxiliary deployment function. For example, in fig. 7, a user may trigger a connection 702 to configure a listening port on the connection 702, so as to automatically establish a dependency relationship between the ECS 701 and the SLB 703 specified by the user, so as to implement a listening function for data transmission between the ECS 701 and the SLB 703. Or, in the case that the NAT is connected to the ECS, the user may configure parameters such as an access rule and an IP address field on the connection between the NAT and the ECS or in the NAT, which is not described in detail.

In addition, the client may also automatically set the auxiliary deployment parameter, for example, in a scenario where the ECS and the RDS are connected to each other, after detecting a connection operation performed by the user for the ECS and the RDS, the client may automatically add the IP address of the ECS to a white list of the RDS, thereby further simplifying the setting operation of the user. By the method, the client can automatically supplement the necessary resources or the resource relation missing in the resource architecture diagram, so that the script generation failure or function missing caused by misoperation or forgetting drawing of a user is avoided, and the deployability of the resource architecture diagram is effectively ensured.

In step 412, the client detects the architecture merging operation performed by the user and determines the resource architecture to be merged.

In an embodiment, the resource deployment file generated by the client according to the configuration parameters may correspond to the target resource architecture, and at this time, the user may perform an architecture merging operation for multiple resource architectures. Accordingly, the client may determine the resource architecture to be merged in response to the architecture merging operation performed by the user for the target resource architecture. Specifically, the resource architecture to be merged may be specified by a user, so that the user may adjust the architecture according to actual application changes, and at this time, the client may correspondingly determine the resource architecture to be merged specified by the user. Or, in the case that any resource architecture is added with an architecture classification identifier in advance, the client may also determine a resource architecture whose architecture classification identifier is the same as the architecture classification identifier of the target resource architecture as the resource architecture to be merged, so as to merge resource architectures of the same type, where the architecture classification identifier may be added according to a resource type, an application type, and the like.

In addition, the resource architecture to be merged may be a new resource architecture that has not been deployed, or may be a resource architecture that has been deployed. By the method, a user can realize integrated deployment among a plurality of resource architectures, so that new resources can be rapidly expanded on the basis of the original resource architecture (whether corresponding resources are deployed or not), rapid and efficient expansion of the architecture or functions is realized, and the difficulty in architecture expansion is reduced.

In the above embodiment, the inevitable sequence between the steps 404 and 408 and the steps 410 and 412 may be sequentially executed according to the sequence of the steps 404 and 408, 410 and 412 as shown in fig. 4, or may be executed according to the sequence of the steps 410, 404 and 408 or the sequence of the steps 410, 412 and 404 and 408, that is, the sequence of the above steps may be adjusted according to the actual situation, and the description does not limit this.

In step 414, the client generates a resource deployment file.

The process of generating the resource deployment file by the client is a process of generating a file frame meeting a preset rule according to a resource architecture diagram drawn by a user, and filling configuration parameters corresponding to each configuration component in the resource architecture diagram into the file frame to generate the resource deployment file. The file format of the resource deployment file may take various forms, for example, may be in an xml format or a json format, which is not limited in this specification.

In an embodiment, corresponding to the architecture merging operation in the foregoing embodiment, the client may generate a merged deployment file accordingly: the method comprises the steps of firstly determining a first target resource corresponding to a target resource architecture and a second target resource corresponding to a resource architecture to be merged, then generating a public deployment file according to the same part of the first target resource and the second target resource, respectively generating a special deployment file according to different parts of the first target resource and the second target resource, and finally merging the public deployment file and the special deployment file according to a preset rule, thereby obtaining a merged deployment file. The merged deployment file merged by the method can simultaneously generate deployment scripts corresponding to all target resources corresponding to the two resource architectures, so that the architecture merging operation of a user is effectively simplified, and the architecture merging and script generating efficiency is improved.

In an embodiment, before generating the resource deployment file, a file generation query message may be presented to the user, and the file generation step of step 414 may be executed after receiving a preset operation performed by the user on the message (e.g., clicking a "confirm file generation" control presented in association with the message). Further, after the user confirms, static verification can be performed on the resource parameters set by the user through a preset rule, so that the parameter setting of the resource can be further confirmed to meet the rule, and the effectiveness of the generated resource deployment script is preliminarily ensured.

In step 416, the client submits the resource deployment file to the server.

After the client generates the resource deployment file, the resource deployment file can be submitted to the server. In an embodiment, the client may submit the resource deployment file to the server after receiving a submission instruction issued by a user through a file submission operation. Or, the client may also submit an inquiry message to the user presentation file, and submit the resource deployment file to the server after detecting a preset operation performed by the user for the message (e.g., clicking a "confirm submission file" control presented in association with the message). Or, the client may automatically submit the resource deployment file to the server after generating the file, which is not limited in this specification.

In step 418, the server converts the resource deployment file into a DAG graph.

After receiving the resource deployment file submitted by the client, the server can convert the resource deployment file into a DAG graph so as to generate a corresponding resource deployment script according to the DAG graph. The specific process of generating the DAG graph according to the resource deployment file in the xml format or the json format may refer to the content disclosed in the related art, and is not described herein again.

In step 420, the server verifies the target resource involved in the DAG graph.

In an embodiment, after receiving the resource deployment file, the server may determine a resource type and/or a resource demand of the target resource, and then access a resource management interface corresponding to the resource collection to verify whether an available resource in the resource collection meets the resource type and/or meets the resource demand.

For example, when a user specifies 10S-type servers in a certain range (region) as target resources with respect to resource parameters set by an ECS, a server may correspondingly check whether at least 10S-type servers in the region are currently in an unoccupied idle state (to-be-used state), and if so, it indicates that the resource specification and inventory in the specified range meet the conditions specified by the user; otherwise, if the resource specification and the inventory in the specified range do not meet the conditions specified by the user, the resource specification and the inventory in the specified range do not meet the conditions specified by the user. Of course, the server may perform the above verification on all target resources involved in the resource deployment file, or perform necessary verification of other rules, and determine that the resource deployment file passes the verification when all target resources satisfy the verification condition. At this point, step 428 may be performed directly to generate a component deployment script, which proceeds to step 422.

In step 422, the server returns the resource verification result to the client.

In step 424, the client displays the resource verification result.

In step 426, the client sends a script generation instruction to the server.

The server side can return the verification result to the client side, and correspondingly, the client side can display a prompt message corresponding to the verification result to the user. As shown in fig. 9(a), in the case that the verification is successful, the client may display a script generation prompting message 901a to the user, and after the user triggers a preset "determine" control, step 426 is performed to send a script generation instruction to the server, so that the server generates a resource deployment script in response to the message. Of course, the client may only show the user the verification passing message to inform that the user passes the verification, and does not show the script generation prompting message (not shown in the figure), and accordingly, the server may perform step 428 to generate the resource deployment script directly after returning the verification result to the client.

Or as shown in fig. 9(b), under the condition that the verification fails, the client may display a framework modification prompt message 901b to the user, where the message includes verification failure information, and continue to display the resource configuration interface after the user triggers a preset "modify framework" control, so that the user can modify the target framework. Furthermore, the target resource with the error can be highlighted (for example, in a way of thickening, marking red and the like) in the resource configuration interface, so that the user can conveniently find and modify the target resource. Of course, if the user triggers the "abandon drawing" control, the drawing process of the current architecture diagram can be exited, and the drawn architecture diagram is automatically saved or the user is asked whether to save the drawn architecture diagram, and the subsequent processing is correspondingly performed.

In step 428, the server generates a resource deployment script according to the DAG graph.

Based on the DAG graph that has been generated corresponding to the target resource, the server may generate a resource deployment script corresponding to the target resource. Corresponding to the foregoing embodiment, in the case that the resource deployment file includes the auxiliary deployment parameter corresponding to the target resource, the server may further generate an auxiliary deployment script corresponding to the target resource based on the auxiliary deployment parameter, where the auxiliary deployment script is used to implement a preset auxiliary deployment function, so as to implement an effective response to the auxiliary deployment operation implemented by the user.

It can be understood that, in the case that the user does not set the auxiliary deployment parameter, the generated resource deployment script only includes the basic deployment script for the target resource. And under the condition that the user is provided with the auxiliary deployment parameters, the generated resource deployment script also comprises an auxiliary deployment script for realizing an auxiliary deployment function besides the basic deployment script of the target resource. The basic deployment script and the auxiliary deployment script can be generated at one time, so that the script generation efficiency is improved.

It can be appreciated that because the DAG graph is generated based on the resource deployment file created by the user for the parameters set by the target resource, the resource deployment script generated based on the DAG graph can be used to implement the deployment of the target resource. The resource deployment script generated in the above manner may be run on the server, or may also be sent to other devices by the server and run. The resource deployment script in the running state is used for deploying a target resource for which a configuration operation implemented by a user aims, and the deployed target resource is used for realizing an application function of the user.

FIG. 10 is a schematic block diagram of an apparatus provided in an exemplary embodiment. Referring to fig. 10, at the hardware level, the apparatus includes a processor 1002, an internal bus 1004, a network interface 1006, a memory 1008, and a non-volatile memory 1010, although other hardware required by other applications may be included. The processor 1002 reads a corresponding computer program from the non-volatile memory 1010 into the memory 1008 and then runs the computer program, thereby forming a resource deployment apparatus on a logical level. Of course, besides software implementation, the one or more embodiments in this specification do not exclude other implementations, such as logic devices or combinations of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.

Referring to fig. 11, in a software implementation, the resource deployment apparatus may include:

the interface display unit 1101 is configured to display a resource configuration interface, where the resource configuration interface includes configuration components corresponding to available resources;

a parameter determining unit 1102, configured to determine, in response to a configuration operation performed by at least one of the configuration components selected by a user for the configuration component, a configuration parameter specified by the configuration operation for a target resource;

a file generating unit 1103, configured to generate a resource deployment file based on the configuration parameter and submit the resource deployment file to a server, so that the server generates a resource deployment script for deploying the target resource according to the resource deployment file.

Optionally, the method further includes:

an information displaying unit 1104, configured to display component prompt information on the resource display interface, where the component prompt information is used to indicate whether the configuration component is available and/or an association relationship between multiple available resources corresponding to the configuration component.

Optionally, the method further includes:

an operation verifying unit 1105, configured to verify whether the configuration operation meets a preset resource configuration rule;

a correction prompting unit 1106, configured to, in a case that the configuration operation does not satisfy the resource configuration rule, present correction prompting information about the configuration operation.

Optionally, the configuration operation includes a connection operation of connecting a plurality of configuration components to draw a resource architecture diagram, and the operation verification unit 1105 is further configured to:

in the implementation process of the connection operation, detecting whether a plurality of available resources corresponding to the plurality of configuration components meet a preset association rule; and/or the presence of a gas in the gas,

and after the connection operation is finished, detecting whether target resources contained in the resource architecture diagram meet preset legitimacy rules or not according to the drawn resource architecture diagram.

Optionally, the parameter determining unit 1102 is further configured to:

under the condition that the configuration operation has a corresponding specified parameter value, setting a resource parameter of the target resource corresponding to the configuration operation as the specified parameter value; and/or the presence of a gas in the gas,

and under the condition that the designated parameter value does not exist in the configuration operation, setting the resource parameter of the target resource corresponding to the configuration operation as a preset default parameter.

Optionally, the method further includes:

an auxiliary parameter setting unit 1107, configured to set, when an auxiliary configuration operation performed by a user for the configuration component is detected, an auxiliary deployment parameter specified by the auxiliary configuration operation for the target resource, so that the service end generates an auxiliary deployment script corresponding to the target resource based on the auxiliary deployment parameter, where the auxiliary deployment script is used to implement a preset auxiliary deployment function.

Optionally, the resource deployment file corresponds to a target resource architecture, and the apparatus further includes:

a to-be-merged architecture determining unit 1108, configured to determine a resource architecture to be merged in response to an architecture merging operation performed by the user for the target resource architecture;

a merged file generating unit 1109, configured to generate, according to the resource deployment files corresponding to the target resource architecture and the resource architecture to be merged, a merged deployment script for a merged resource architecture corresponding to the target resource architecture and the resource architecture to be merged, where the merged deployment script is used to deploy all target resources corresponding to the target resource architecture and the resource architecture to be merged.

Optionally, the to-be-merged framework determining unit 1108 is further configured to:

determining the resource architecture to be merged specified by the user; alternatively, the first and second electrodes may be,

and under the condition that any resource architecture is added with an architecture classification identifier in advance, determining the resource architecture with the architecture classification identifier same as that of the target resource architecture as the resource architecture to be merged.

Optionally, the merged file generating unit 1109 is further configured to:

determining a first target resource corresponding to the target resource architecture and a second target resource corresponding to the resource architecture to be merged;

generating a public deployment file according to the same part of the first target resource and the second target resource, and respectively generating a special deployment file according to different parts of the first target resource and the second target resource;

and merging the public deployment file and the special deployment file according to a preset rule to obtain the merged deployment file.

Referring to fig. 12, in another software embodiment, the resource deployment apparatus may include:

a file receiving unit 1201, configured to receive a resource deployment file submitted by a client, where the resource deployment file is generated by the client according to a configuration operation performed by a user on at least one configuration component, and the resource configuration component is displayed in a resource configuration interface by the client;

a script generating unit 1202, configured to generate a resource deployment script according to the resource deployment file, where the resource deployment script is used to deploy a target resource corresponding to the at least one configuration component.

Optionally, the script generating unit 1202 is further configured to:

converting the resource deployment file into a directed acyclic graph corresponding to the target resource;

and generating the resource deployment script according to the directed acyclic graph.

Optionally, the method further includes:

a resource information determining unit 1203, configured to determine a resource type and/or a resource demand of the target resource;

a target resource verifying unit 1204, configured to access a resource management interface corresponding to a resource collection, so as to verify whether an available resource in the resource collection conforms to the resource type and/or whether the resource requirement is met.

Optionally, the method further includes:

an auxiliary script generating unit 1205, configured to generate, based on the auxiliary deployment parameter, an auxiliary deployment script corresponding to the target resource when the resource deployment file includes the auxiliary deployment parameter corresponding to the target resource, where the auxiliary deployment script is used to implement a preset auxiliary deployment function.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

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 computer storage media 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 disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments herein. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

The above description is only for the purpose of illustrating the preferred embodiments of the one or more embodiments of the present disclosure, and is not intended to limit the scope of the one or more embodiments of the present disclosure, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the one or more embodiments of the present disclosure should be included in the scope of the one or more embodiments of the present disclosure.

Claims

1. A method for deploying resources, comprising:

responding to the configuration operation carried out by the configuration component selected by the user, and determining the configuration parameters specified by the configuration operation and aiming at the target resource and the connection relation among the configuration components;

generating a resource deployment file based on the configuration parameters and the connection relation and submitting the resource deployment file to a server so that the server generates a resource deployment script for deploying the target resource according to the resource deployment file;

in response to an architecture merging operation performed by the user for a target resource architecture, determining a resource architecture to be merged, the resource deployment file corresponding to the target resource architecture;

and generating a merged deployment file according to the resource deployment files respectively corresponding to the target resource architecture and the resource architecture to be merged, wherein the merged deployment file is used for generating a merged resource deployment script aiming at the merged resource architecture corresponding to the target resource architecture and the resource architecture to be merged, and the merged resource deployment script is used for deploying all target resources corresponding to the target resource architecture and the resource architecture to be merged.

2. The method of claim 1, further comprising:

and displaying component prompt information on the resource configuration interface, wherein the component prompt information is used for indicating whether the configuration component is available and/or the incidence relation among a plurality of available resources corresponding to the configuration component.

3. The method of claim 1, further comprising:

verifying whether the configuration operation meets a preset resource configuration rule;

in the case that the configuration operation does not satisfy the resource configuration rule, displaying correction prompt information about the configuration operation.

4. The method of claim 3, wherein the configuration operation comprises a connection operation for connecting a plurality of configuration components to draw a resource architecture diagram, and wherein the verifying whether the configuration operation satisfies a preset resource configuration rule comprises:

5. The method of claim 1, wherein the determining the configuration parameters for the target resource specified by the configuration operation comprises:

and under the condition that the designated parameter value does not exist in the configuration operation, setting the resource parameter of the target resource corresponding to the configuration operation as a preset default parameter value.

6. The method of claim 1, further comprising:

in the case of detecting an auxiliary configuration operation implemented by a user for the configuration component, setting an auxiliary deployment parameter specified by the auxiliary configuration operation for the target resource, so that the server generates an auxiliary deployment script corresponding to the target resource based on the auxiliary deployment parameter, wherein the auxiliary configuration operation is different from the configuration operation, the auxiliary deployment parameter is different from the configuration parameter, and the auxiliary deployment script is used for realizing a preset auxiliary deployment function.

7. The method of claim 1, wherein the determining the resource architecture to be merged comprises:

8. The method of claim 1, wherein generating the merged deployment file comprises:

9. A method for deploying resources, comprising:

receiving a resource deployment file submitted by a client, wherein the resource deployment file is generated by the client according to configuration parameters aiming at target resources and connection relations among the configuration components, which are specified by configuration operations carried out by a user aiming at the configuration components, and the configuration components are displayed in a resource configuration interface by the client;

generating a resource deployment script according to the resource deployment file, wherein the resource deployment script is used for deploying target resources corresponding to the configuration components;

receiving a merged deployment file submitted by a client, wherein the merged deployment file is generated by the client according to resource deployment files respectively corresponding to a target resource architecture and a resource architecture to be merged, the resource deployment file corresponds to the target resource architecture, and the resource architecture to be merged is determined by the client in response to architecture merging operation carried out by the user on the target resource architecture;

and generating a merged resource deployment script aiming at the merged resource architecture corresponding to the target resource architecture and the resource architecture to be merged according to the merged deployment file, wherein the merged resource deployment script is used for deploying all target resources corresponding to the target resource architecture and the resource architecture to be merged.

10. The method of claim 9, wherein generating a resource deployment script from the resource deployment file comprises:

11. The method of claim 9, further comprising:

determining the resource type and/or the resource demand of the target resource;

accessing a resource management interface corresponding to a resource collection to verify whether available resources in the resource collection conform to the resource type and/or meet the resource demand.

12. The method of claim 9, further comprising:

and under the condition that the resource deployment file contains auxiliary deployment parameters corresponding to the target resources, generating an auxiliary deployment script corresponding to the target resources based on the auxiliary deployment parameters, wherein the auxiliary configuration operation is different from the configuration operation, the auxiliary deployment parameters are different from the configuration parameters, and the auxiliary deployment script is used for realizing a preset auxiliary deployment function.

13. A resource deployment apparatus, comprising:

the parameter determining unit is used for responding to the configuration operation carried out by the configuration component selected by the user, and determining the configuration parameters which are specified by the configuration operation and are aimed at the target resource and the connection relation among the configuration components;

the file generation unit is used for generating a resource deployment file based on the configuration parameters and the connection relation and submitting the resource deployment file to a server so that the server generates a resource deployment script for deploying the target resource according to the resource deployment file;

a resource architecture to be merged determining unit, configured to determine a resource architecture to be merged in response to an architecture merging operation performed by the user for a target resource architecture, where the resource deployment file corresponds to the target resource architecture;

a merged file generating unit, configured to generate a merged deployment file according to resource deployment files respectively corresponding to the target resource architecture and the resource architecture to be merged, where the merged deployment file is used to generate a merged resource deployment script for a merged resource architecture corresponding to the target resource architecture and the resource architecture to be merged, and the merged resource deployment script is used to deploy all target resources corresponding to the target resource architecture and the resource architecture to be merged.

14. A resource deployment apparatus, comprising:

the system comprises a file receiving unit, a resource deployment unit and a resource configuration unit, wherein the file receiving unit is used for receiving a resource deployment file submitted by a client, the resource deployment file is generated by the client according to configuration parameters aiming at target resources and connection relations among all configuration components, the configuration parameters are specified by configuration operations of a user aiming at the configuration components, and the configuration components are displayed in a resource configuration interface by the client;

a script generating unit, configured to generate a resource deployment script according to the resource deployment file, where the resource deployment script is used to deploy a target resource corresponding to the configuration component;

a merged deployment file receiving unit, configured to receive a merged deployment file submitted by a client, where the merged deployment file is generated by the client according to resource deployment files corresponding to a target resource architecture and a resource architecture to be merged, where the resource deployment file corresponds to the target resource architecture, and the resource architecture to be merged is determined by the client in response to an architecture merging operation performed by the user for the target resource architecture;

and a merged script generating unit, configured to generate a merged resource deployment script for the merged resource architecture corresponding to the target resource architecture and the resource architecture to be merged according to the merged deployment file, where the merged resource deployment script is used to deploy all target resources corresponding to the target resource architecture and the resource architecture to be merged.

15. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the method of any one of claims 1-12 by executing the executable instructions.

16. A computer-readable storage medium having stored thereon computer instructions, which, when executed by a processor, carry out the steps of the method according to any one of claims 1-12.