CN112733101A - Cloud server management method, device, storage medium and server terminal - Google Patents
Cloud server management method, device, storage medium and server terminal Download PDFInfo
- Publication number
- CN112733101A CN112733101A CN202110022605.0A CN202110022605A CN112733101A CN 112733101 A CN112733101 A CN 112733101A CN 202110022605 A CN202110022605 A CN 202110022605A CN 112733101 A CN112733101 A CN 112733101A
- Authority
- CN
- China
- Prior art keywords
- user
- login
- cloud server
- login request
- type
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 36
- 238000000034 method Methods 0.000 claims description 28
- 238000012795 verification Methods 0.000 claims description 10
- 238000011156 evaluation Methods 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims description 3
- 238000004891 communication Methods 0.000 description 19
- 238000010586 diagram Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 10
- 238000012545 processing Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 6
- 230000007474 system interaction Effects 0.000 description 4
- 239000002699 waste material Substances 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013500 data storage Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 210000001747 pupil Anatomy 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a cloud server management method, a cloud server management device, a storage medium and a server terminal, and relates to the technical field of servers. Firstly, acquiring a login request of a user, and determining the user type of the user according to the login request; then determining a login mode corresponding to the user according to the user type, and verifying the login request of the user according to the login mode; and finally, if the login request of the user is successfully verified according to the login mode, distributing the login request to a cloud server and server resources corresponding to the user according to the user type. Because the user type can be determined according to the login request of the user, the corresponding cloud server and the server resources can be distributed according to the user type after the login request of the user is successfully verified, the cloud server resources can be conveniently managed by the server terminal, and the utilization rate of the server resources by the server terminal is effectively improved.
Description
Technical Field
The present application relates to the technical field of servers, and in particular, to a cloud server management method, an apparatus, a storage medium, and a server terminal.
Background
With the development of science and technology, people have more and more great use requirements on terminals, a cloud server is a computing service which is simple, efficient, safe, reliable and flexible in processing capacity, the management mode of the cloud server is simpler and more efficient than that of a physical server, and a user can quickly create or release any plurality of cloud servers without purchasing hardware in advance, so that the management method industry related to the cloud servers becomes one of the key points of research of technicians in the field.
The entity device for creating the cloud server can be regarded as a server terminal, a large number of data storage and processing service users can be provided, the users can apply for creating the cloud server and connecting the cloud server to the server terminal through the client, but when a plurality of users create the cloud servers of a plurality of operating systems in the server terminal, in the related art, the server terminal cannot effectively utilize resources, and the cloud server used by the users may be jammed.
Disclosure of Invention
The application provides a cloud server management method, a cloud server management device, a storage medium and a server terminal, which can solve the technical problems that in the related art, when a plurality of users create a plurality of cloud servers of operating systems in the terminal, the terminal cannot effectively utilize resources, and the users may be stuck when using the cloud servers.
In a first aspect, an embodiment of the present application provides a cloud server management method, where the method includes:
acquiring a login request of a user, and determining the user type of the user according to the login request;
determining a login mode corresponding to the user according to the user type, and verifying a login request of the user according to the login mode;
and if the login request of the user is successfully verified according to the login mode, distributing the login request to a cloud server and server resources corresponding to the user according to the user type.
In a second aspect, an embodiment of the present application provides a cloud server management apparatus, where the apparatus includes:
the system comprises a user type determining module, a user type determining module and a user type determining module, wherein the user type determining module is used for acquiring a login request of a user and determining the user type of the user according to the login request;
the user request verification module is used for determining a login mode corresponding to the user according to the user type and verifying the login request of the user according to the login mode;
and the cloud server allocation module is used for allocating the cloud server and the server resources corresponding to the user according to the user type if the login request of the user is successfully verified according to the login mode.
In a third aspect, an embodiment of the present application provides a computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to execute steps implementing the above-mentioned method.
In a fourth aspect, embodiments of the present application provide a terminal, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the computer program to implement the steps of the method described above.
The beneficial effects brought by the technical scheme provided by some embodiments of the application at least comprise:
the application provides a cloud server management method, firstly, a login request of a user is obtained, and the user type of the user is determined according to the login request; then determining a login mode corresponding to the user according to the user type, and verifying the login request of the user according to the login mode; and finally, if the login request of the user is successfully verified according to the login mode, distributing the login request to a cloud server and server resources corresponding to the user according to the user type. Because the user type can be determined according to the login request of the user, the corresponding cloud server and the server resources can be distributed according to the user type after the login request of the user is successfully verified, the cloud server resources can be conveniently managed by the server terminal, and the utilization rate of the server resources by the server terminal is effectively improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is an exemplary system architecture diagram of a cloud server management method according to an embodiment of the present disclosure;
fig. 2 is a system interaction diagram of a cloud server management method according to an embodiment of the present application;
fig. 3 is a schematic flowchart of a cloud server management method according to another embodiment of the present application;
fig. 4 is a schematic flowchart of a cloud server management method according to another embodiment of the present application;
fig. 5 is a schematic structural diagram of a cloud server management apparatus according to another embodiment of the present application;
fig. 6 is a schematic structural diagram of a cloud server management apparatus according to another embodiment of the present application;
fig. 7 is a schematic structural diagram of a server terminal according to an embodiment of the present application.
Detailed Description
In order to make the features and advantages of the present application more obvious and understandable, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the application, as detailed in the appended claims.
Fig. 1 is an exemplary system architecture diagram of a cloud server management method according to an embodiment of the present disclosure.
As shown in fig. 1, the system architecture may include at least one paid user 110, one general user 120, one client 130, a server terminal 150 including a plurality of cloud servers 140, and a communication link 160 for providing a medium of communication link between the client 130 and the server terminal 150. Communication link 160 may include various types of wired or wireless communication links, such as: the wired communication link comprises an optical fiber, a twisted pair wire or a coaxial cable, and the wireless communication link comprises a Bluetooth communication link, a near field communication link, a Wi-Fi communication link or a microwave communication link, etc.
The client may be disposed in various electronic devices, such that a user may interact with the cloud server in the server terminal through the client in the electronic device, where the electronic device may be various electronic devices, including but not limited to a wearable device, a smartphone, a tablet computer, a laptop portable computer, a desktop computer, and the like.
It should be understood that the number of paid users, ordinary users, clients, cloud servers, server terminals, and communication links in fig. 1 is merely illustrative, and any number of paid users, ordinary users, clients, cloud servers, server terminals, and communication links may be used, as desired.
It should be noted that the execution subject in the embodiment of the present application may be, for example, a processor or other integrated circuit chip in a server terminal in terms of hardware, and may be, for example, a service related to a cloud server management method in the server terminal in terms of software, which is not limited to this. For convenience of description, the following description will be given taking the execution subject as a processor in the server terminal as an example.
Referring to fig. 2, fig. 2 is a system interaction diagram of a cloud server management method according to an embodiment of the present application, and a system interaction process in the cloud server management method will be described with reference to fig. 1 and fig. 2.
As shown in fig. 2, the system interaction process includes:
s201, a server terminal obtains a login request of a user, and determines the user type of the user according to the login request.
Optionally, the obtaining a login request of a user, and determining a user type of the user according to the login request includes: acquiring user identity information carried in a login request of a user; and determining the user type of the user according to the user identity information, wherein the user type at least comprises a paid user and a common user.
S202, the server terminal determines a login mode corresponding to the user according to the user type, and verifies the login request of the user according to the login mode.
Optionally, the determining, according to the user type, a login manner corresponding to the user includes: if the user type is a payment user, determining that the login mode corresponding to the user is a first login mode, wherein the first login mode is password authentication login; and if the user type is a common user, determining that the login mode corresponding to the user is a second login mode, wherein the second login mode is connection resource evaluation login.
Optionally, the verifying the login request of the user according to the login manner includes: if the login mode is a first login mode, acquiring account information and password information of the user, wherein the password information comprises at least one of a plaintext password, biological identification information and equipment identity information, and verifying the account information and the password; if the account information and the password are the same as locally stored authentication information, the login request of the user is determined to be successfully authenticated, and if the account information and the password are not the same as locally stored authentication information, the login request of the user is determined to be failed to be authenticated.
Optionally, the verifying the login request of the user according to the login manner includes: if the login mode is a second login mode, acquiring the current user connection number of the server terminal, and comparing the current user connection number with a user connection number threshold; if the current user connection number is less than or equal to the user connection number threshold, determining that the login request of the user is successfully verified, and if the current user connection number is greater than the user connection number threshold, determining that the login request of the user is failed to be verified.
And S203, if the login request of the user is successfully verified according to the login mode, the server terminal allocates the cloud server and the server resources corresponding to the user according to the user type.
Optionally, the allocating, according to the user type, to the cloud server and the server resource corresponding to the user includes: if the user type is a paid user, allocating the user type to a first cloud server of the user, wherein the first cloud server has at least one fixed authority, and the fixed authority at least comprises: fixed use time, fixed internet protocol address and fixed storage space; if the user type is a common user, allocating the user type to a second cloud server of the user, wherein the second cloud server has at least one temporary authority, and the temporary authority at least comprises: temporary connection time, temporary internet protocol address and temporary storage space.
Wherein the first cloud server assigned to the user comprises: acquiring a first operating system selected by the user, and allocating a first cloud server pre-installed with the first operating system to the user; the second cloud server assigned to the user includes: and acquiring a second operating system selected by the user, and distributing a second cloud server pre-installed with the second operating system to the user.
In the embodiment of the application, firstly, a login request of a user is obtained, and the user type of the user is determined according to the login request; then determining a login mode corresponding to the user according to the user type, and verifying the login request of the user according to the login mode; and finally, if the login request of the user is successfully verified according to the login mode, distributing the login request to a cloud server and server resources corresponding to the user according to the user type. Because the user type can be determined according to the login request of the user, the corresponding cloud server and the server resources can be distributed according to the user type after the login request of the user is successfully verified, the cloud server resources can be conveniently managed by the server terminal, and the utilization rate of the server resources by the server terminal is effectively improved.
Referring to fig. 3, fig. 3 is a schematic flowchart illustrating a cloud server management method according to another embodiment of the present application.
As shown in fig. 3, the method includes:
s301, obtaining a login request of a user, and determining the user type of the user according to the login request.
In the embodiment of the application, the execution subject is a server terminal, the server terminal can be regarded as an entity device, and an administrator can create or release any plurality of cloud servers in the server terminal, so that a user can log in the cloud servers through a client and perform related operations in the cloud servers. The server terminal may be a computer-type server terminal, or may also be a mobile terminal-type server terminal, for example, the mobile terminal may be an electronic device such as a mobile phone, and for convenience of description, a specific real-time process of the cloud server management method is described below by taking the mobile terminal-type server terminal as an example.
In order to conveniently manage the cloud server, the users of the cloud server can be classified, wherein in a feasible mode, the classification is carried out according to whether the users use the cloud server for compensation, and the users can select whether to pay for the cloud server according to the requirements because the cloud server for compensation can have more authorities and functions.
The specific method for classifying the users is that the server terminal receives a request of using the cloud server for compensation of the users according to the selling webpages corresponding to the cloud server or the login clients corresponding to the cloud server, after the successful payment of the users is determined, the user identity information corresponding to the users is marked as the payment users, and the user identity information is unique information for marking the user identities.
Therefore, when a user needs to log in the server terminal and further operates the corresponding cloud server in the server terminal, the login request corresponding to the user can be sent through the client corresponding to the cloud server, and then the server terminal can obtain the login request of the user and determine the user type of the user according to the user identity information in the login request, namely determine that the user is a paid user for paid use or determine that the user is a common user for free use.
S302, determining a login mode corresponding to the user according to the user type, and verifying the login request of the user according to the login mode.
Because the paying user can have more rights and functions when using the cloud server for compensation, in order to avoid resource waste in the server terminal caused by malicious use of resources of the paying user in the cloud server terminal, different login modes corresponding to different types of users can be preset, so that a common user cannot log in the corresponding cloud server of the paying user at will.
Then, the login mode corresponding to the user can be further determined according to the user type determined in the above step, wherein the login mode corresponding to the paid user is more complicated than the login mode corresponding to the ordinary user so as to improve the security. After the login mode corresponding to the user is determined, the login request of the user can be verified according to the login mode corresponding to the user.
And S303, if the login request of the user is successfully verified according to the login mode, distributing the login request to a cloud server and server resources corresponding to the user according to the user type.
After the login request of the user is successfully verified according to the login mode corresponding to the user, the identity of the user is successfully verified, and if the user logs in the server terminal for the first time, cloud servers and server resources corresponding to the user can be allocated, namely if the user type corresponding to the user is a payment user, payment cloud servers and payment server resources corresponding to the payment user are allocated; if the user type corresponding to the user is a common user, the user type is allocated to a common cloud server and common server resources corresponding to the common user, optionally, the payment cloud server has higher performance than the common cloud server, and the payment server resources have more rights than the common server resources and can realize more functions.
If the user does not log in the server terminal first, that is, the server terminal configures the corresponding cloud server and server resources for the user before logging in, the cloud server and server resources that have been configured before may be allocated to the user after the login request of the user is successfully verified according to the login manner.
In the embodiment of the application, firstly, a login request of a user is obtained, and the user type of the user is determined according to the login request; then determining a login mode corresponding to the user according to the user type, and verifying the login request of the user according to the login mode; and finally, if the login request of the user is successfully verified according to the login mode, distributing the login request to a cloud server and server resources corresponding to the user according to the user type. Because the user type can be determined according to the login request of the user, the corresponding cloud server and the server resources can be distributed according to the user type after the login request of the user is successfully verified, the cloud server resources can be conveniently managed by the server terminal, and the utilization rate of the server resources by the server terminal is effectively improved.
Referring to fig. 4, fig. 4 is a schematic flowchart illustrating a cloud server management method according to another embodiment of the present application.
As shown in fig. 4, the method includes:
s401, user identity information carried in a login request of a user is obtained.
Optionally, after obtaining the login request of the user, the user type of the user needs to be determined according to the login request of the user, and a feasible implementation manner is that user identity information carried in the login request of the user is obtained first, where the user identity information is unique information for identifying the user identity.
S402, determining the user type of the user according to the user identity information, wherein the user type at least comprises a paid user and a common user.
After the user identity information carried in the login request of the user is obtained, the user type of the user can be determined according to whether the user identity information carries the payment identifier, namely when the payment identifier exists in the user identity information carried in the login request of the user, the user type of the user can be determined to be the payment user; when the user identity information carried in the login request of the user does not have the payment identifier, the user type of the user can be determined to be a common user.
And S403, if the user type is a paid user, determining that the login mode corresponding to the user is a first login mode, wherein the first login mode is password authentication login.
Because the paying user can have more rights and functions when using the cloud server for compensation, in order to avoid resource waste in the server terminal caused by malicious use of resources of the paying user in the cloud server terminal, different login modes corresponding to different types of users can be preset, so that a common user cannot log in the corresponding cloud server of the paying user at will.
When the user type of the user is a paying user, the login mode corresponding to the user can be determined to be a first login mode, wherein the first login mode can be used for password authentication login, namely, the paying user can directly log in a cloud server in a server terminal according to account information and a password, and the security of a cloud server account of the paying user can be improved through password authentication login.
S404, if the user type is a common user, determining that the login mode corresponding to the user is a second login mode, wherein the second login mode is connection resource evaluation login.
When the user type is a common user, determining that the login mode corresponding to the user is a second login mode, wherein the second login mode is connection resource evaluation login, since the common user is not a paid user, in order to improve the utilization rate of the common user to the server resources and prevent the common user from applying for the cloud server at will and causing the waste of the server resources, the current cloud server connection resources of the server terminal can be obtained firstly after the user type of the user is determined to be the common user, wherein the cloud server connection resources may include the number of all cloud servers in the server terminal that are powered on and the resource occupancy rates of the cloud servers in the server terminal, and evaluating according to the current cloud server connection resource of the server terminal, and if the server terminal is judged to be capable of continuously operating the cloud server, allowing a common user to log in the cloud server in the server.
S405, if the login mode is a first login mode, acquiring account information and password information of the user, wherein the password information comprises at least one of a plaintext password, biological identification information and equipment identity information, and verifying the account information and the password.
Specifically, when it is determined that the login mode corresponding to the user is the first login mode according to the user type, the client may send an authentication request to the user based on the login request, so that the server terminal obtains account information and password information input by the user through the client, and the password information includes at least one of a plaintext password, biometric information, and device identity information, and authenticates the account information and the password. The biometric information may be fingerprint information, face information, pupil information, or the like.
S406, if the account information and the password are the same as locally stored authentication information, determining that the login request of the user is successfully authenticated, and if the account information and the password are not the same as locally stored authentication information, determining that the login request of the user is unsuccessfully authenticated.
After acquiring account information and password information input by a user through a client, a server terminal can verify the account information and the password with locally stored authentication information of the user, and if the account information and the password are the same as the locally stored authentication information, a login request for successfully authenticating the user can be determined, so that the user can log in the server terminal, and a corresponding cloud server is distributed in the server terminal; if the account information and the password are different from locally stored authentication information, it is determined that the login request for authenticating the user fails, and then the user cannot log in the server terminal and cannot allocate a corresponding cloud server in the server terminal.
S407, if the login mode is the second login mode, acquiring the current user connection number of the server terminal, and comparing the current user connection number with a user connection number threshold.
For convenience of description, a process of verifying a login request of a user according to a second login manner is described by taking the current cloud server connection resource of the server terminal as the current user connection number of the server terminal as an example, and then after the current user connection number of the server terminal is obtained, the current user connection number may be compared with a user connection number threshold.
S408, if the current user connection number is less than or equal to the user connection number threshold, determining that the login request of the user is successfully verified, and if the current user connection number is greater than the user connection number threshold, determining that the login request of the user is unsuccessfully verified.
Because the resources of the server terminal are fixed, when the current connection number of the server terminal is more, the resource occupancy amount of the server terminal is more, the current user connection number is less than or equal to the user connection number threshold value, the resources of the server terminal are temporarily sufficient, the user can be allowed to connect and use the cloud server, and the login request of the user can be successfully verified, so that the user can log in the server terminal and the corresponding cloud server is distributed in the server terminal; if the current user connection number is larger than the user connection number threshold, it is determined that the login request of the user is verified to be failed, the user cannot log in the server terminal, and the corresponding cloud server cannot be allocated in the server terminal.
S409, if the user type is a payment user, allocating the user type to a first cloud server of the user, wherein the first cloud server has at least one fixed authority, and the fixed authority at least comprises: fixed time of use, fixed internet protocol address, and fixed memory space.
When the user type is a paying user and after the login request of the paying user is successfully verified, the user can be allocated to a first cloud server of the user, and the first cloud server can have at least one fixed authority because the paying user is a paid user, and the fixed authority at least comprises: fixed time of use, fixed internet protocol address, and fixed memory space. The fixed use time is also the time limit that the paying user can use the first cloud server distributed in the server terminal, and the time limit is longer; the fixed internet protocol address is also a fixed IP address, is a uniform address format provided by an IP protocol, and distributes a logic address for each network and each host on the internet so as to shield the difference of physical addresses, wherein the fixed IP address is only an IP address which cannot be changed; the fixed storage space is a storage space which is reserved for the paying user independently in the server terminal, data generated when the user uses the first cloud server can be stored in the fixed storage space, even if the fixed use time of the user expires, the user can have a keep-alive function of a specified year, the data can still be stored in the fixed storage space, and the first cloud server and related data can be recovered from the fixed storage space at any time within the specified year.
Optionally, when the first operating system is distributed to the first cloud server of the payment user, specifically, the first operating system selected by the user may be obtained through a client, the first operating system may be an android system, an IOS system, a linux system, or a Windows system, and the first cloud server preinstalled with the first operating system is distributed to the user.
In addition, the proportion of various operating systems preinstalled in the idle first cloud server can be dynamically adjusted according to the use amount of the selected system of the user, so that the full utilization of resources is achieved; meanwhile, the first operating system can be cleaned or restarted periodically according to the current state of the first cloud server and the user operation condition, and the fluency experience of the user is guaranteed.
S410, if the user type is a common user, allocating the user type to a second cloud server of the user, wherein the second cloud server has at least one temporary authority, and the temporary authority at least comprises: temporary connection time, temporary internet protocol address and temporary storage space.
When the user type is a common user and after the login request of the common user is successfully verified, the user is allocated to a second cloud server of the user, and as the common user does not pay, only basic resources need to be provided for the common user, so that the second cloud server has at least one temporary authority, wherein the temporary authority at least comprises: temporary connection time, temporary internet protocol address and temporary storage space. The temporary connection time, the temporary internet protocol address and the temporary storage space are opposite to the fixed use time, the fixed internet protocol address and the fixed storage space, and are not described herein again.
Optionally, when the second cloud server is allocated to a second cloud server of an ordinary user, specifically, the second operating system selected by the user may be obtained through a client, the second operating system may be an android system, an IOS system, a linux system, or a Windows system, and the second cloud server preinstalled with the second operating system is allocated to the user.
In addition, the proportion of preassembling various operating systems in the idle second cloud server can be dynamically adjusted according to the use amount of the selected system of the user, so that the full utilization of resources is achieved; meanwhile, the second operating system can be cleaned or restarted periodically according to the current state of the second cloud server and the user operation condition, and the fluency experience of the user is guaranteed.
Optionally, in a general case, a client of one login terminal may only log in one cloud server through one account, but when the server terminal detects that the login terminal corresponding to the client has multiple display screens, for example, the login terminal is a folding screen, a multi-screen, or the like, the login terminal may be allowed to log in multiple accounts to respectively connect multiple cloud servers in the server terminal, so as to meet the needs of different users.
Compared with the management method in the prior art, the cloud server management method provided in the embodiment of the application is more humanized: the operating system of the user can be customized according to different user requirements, and different user requirements are met. In addition, compared with the management method in the prior art, the resource is fully utilized, for example, some users only need to use a large number of cloud servers for temporary emergency needs (for example, large-batch application tests and the like), only temporary common account operation needs to be applied at the moment, short-term needs are met, and resource waste is avoided.
Referring to fig. 5, fig. 5 is a schematic structural diagram of a cloud server management device according to another embodiment of the present application.
As shown in fig. 5, the cloud server management apparatus 500 includes:
the user type determining module 510 is configured to obtain a login request of a user, and determine a user type of the user according to the login request.
And a user request verification module 520, configured to determine a login manner corresponding to the user according to the user type, and verify the login request of the user according to the login manner.
The cloud server allocation module 530 is configured to, if the login request of the user is successfully verified according to the login manner, allocate a cloud server and server resources corresponding to the user according to the user type.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a cloud server management device according to another embodiment of the present application.
As shown in fig. 6, the cloud server management apparatus 600 includes:
the identity information obtaining module 610 is configured to obtain user identity information carried in a login request of a user.
A user type determining module 620, configured to determine a user type of the user according to the user identity information, where the user type includes at least a paid user and a general user.
A first login manner determining module 630, configured to determine that the login manner corresponding to the user is a first login manner if the user type is a paid user, where the first login manner is password authentication login.
A second login manner determining module 640, configured to determine that the login manner corresponding to the user is a second login manner if the user type is an ordinary user, where the second login manner is connection resource evaluation login.
The first verification module 650 is configured to, if the login manner is a first login manner, obtain account information and password information of the user, where the password information includes at least one of a plaintext password, biometric information, and device identity information, and verify the account information and the password.
A first verification result module 660, configured to determine that the login request of the user is successfully verified if the account information and the password are the same as locally stored verification information, and determine that the login request of the user is failed to be verified if the account information and the password are not the same as locally stored verification information.
And the second verification module 670 is configured to, if the login manner is the second login manner, obtain the current user connection number of the server terminal, and compare the current user connection number with a user connection number threshold.
A second verification result module 680, configured to determine that the login request of the user is successfully verified if the current user connection number is less than or equal to the user connection number threshold, and determine that the login request of the user is failed to be verified if the current user connection number is greater than the user connection number threshold.
A first allocating module 690, configured to allocate, if the user type is a paid user, to a first cloud server of the user, where the first cloud server has at least one fixed right, and the fixed right at least includes: fixed time of use, fixed internet protocol address, and fixed memory space.
Wherein the first cloud server assigned to the user comprises: and acquiring the first operating system selected by the user, and distributing the first cloud server pre-installed with the first operating system to the user.
A second allocating module 6100, configured to allocate, if the user type is an ordinary user, to a second cloud server of the user, where the second cloud server has at least one temporary permission, and the temporary permission at least includes: temporary connection time, temporary internet protocol address and temporary storage space.
Wherein the second cloud server assigned to the user comprises: and acquiring a second operating system selected by the user, and distributing a second cloud server pre-installed with the second operating system to the user.
In an embodiment of the present application, a cloud server management apparatus includes: the system comprises a user type determining module, a user type determining module and a user type determining module, wherein the user type determining module is used for acquiring a login request of a user and determining the user type of the user according to the login request; the user request verification module is used for determining a login mode corresponding to the user according to the user type and verifying the login request of the user according to the login mode; and the cloud server allocation module is used for allocating the cloud server and the server resources corresponding to the user according to the user type if the login request of the user is successfully verified according to the login mode. Because the user type can be determined according to the login request of the user, the corresponding cloud server and the server resources can be distributed according to the user type after the login request of the user is successfully verified, the cloud server resources can be conveniently managed by the server terminal, and the utilization rate of the server resources by the server terminal is effectively improved.
Embodiments of the present application also provide a computer storage medium that may store a plurality of instructions adapted to be loaded by a processor and to perform the steps of the method according to any of the above embodiments.
Referring to fig. 7, fig. 7 is a schematic structural diagram of a server terminal according to an embodiment of the present application. As shown in fig. 7, the server terminal 700 may include: at least one processor 701, at least one network interface 704, a user interface 703, memory 705, at least one communication bus 702.
Wherein a communication bus 702 is used to enable connective communication between these components.
The user interface 703 may include a Display screen (Display) and a Camera (Camera), and the optional user interface 703 may also include a standard wired interface and a standard wireless interface.
The network interface 704 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), among others.
The Memory 705 may include a Random Access Memory (RAM) or a Read-Only Memory (ROM). Optionally, the memory 705 includes a non-transitory computer-readable medium. The memory 705 may be used to store instructions, programs, code sets, or instruction sets. The memory 705 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described above, and the like; the storage data area may store data and the like referred to in the above respective method embodiments. The memory 705 may optionally be at least one memory device located remotely from the processor 701. As shown in fig. 7, the memory 705, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a cloud server management program.
In the server terminal 700 shown in fig. 7, the user interface 703 is mainly used to provide an input interface for a user to obtain data input by the user; and the processor 701 may be configured to call the cloud server management program stored in the memory 705, and specifically perform the following operations:
acquiring a login request of a user, and determining the user type of the user according to the login request;
determining a login mode corresponding to the user according to the user type, and verifying a login request of the user according to the login mode;
and if the login request of the user is successfully verified according to the login mode, distributing the login request to a cloud server and server resources corresponding to the user according to the user type.
In an embodiment, when the processor 701 executes the login request of the obtaining user and determines the user type of the user according to the login request, the following steps are specifically executed: acquiring user identity information carried in a login request of a user; and determining the user type of the user according to the user identity information, wherein the user type at least comprises a paid user and a common user.
In an embodiment, when the processor 701 determines the login mode corresponding to the user according to the user type, specifically, the following steps are performed: if the user type is a payment user, determining that the login mode corresponding to the user is a first login mode, wherein the first login mode is password authentication login; and if the user type is a common user, determining that the login mode corresponding to the user is a second login mode, wherein the second login mode is connection resource evaluation login.
In an embodiment, when the processor 701 executes the login request for authenticating the user according to the login manner, the following specific steps are executed: if the login mode is a first login mode, acquiring account information and password information of the user, wherein the password information comprises at least one of a plaintext password, biological identification information and equipment identity information, and verifying the account information and the password; if the account information and the password are the same as locally stored authentication information, the login request of the user is determined to be successfully authenticated, and if the account information and the password are not the same as locally stored authentication information, the login request of the user is determined to be failed to be authenticated.
In an embodiment, when the processor 701 executes the login request for authenticating the user according to the login manner, the following specific steps are executed: if the login mode is a second login mode, acquiring the current user connection number of the server terminal, and comparing the current user connection number with a user connection number threshold; if the current user connection number is less than or equal to the user connection number threshold, determining that the login request of the user is successfully verified, and if the current user connection number is greater than the user connection number threshold, determining that the login request of the user is failed to be verified.
In an embodiment, when the processor 701 executes the cloud server and the server resource corresponding to the user allocated according to the user type, specifically, the following steps are executed: if the user type is a paid user, allocating the user type to a first cloud server of the user, wherein the first cloud server has at least one fixed authority, and the fixed authority at least comprises: fixed use time, fixed internet protocol address and fixed storage space; if the user type is a common user, allocating the user type to a second cloud server of the user, wherein the second cloud server has at least one temporary authority, and the temporary authority at least comprises: temporary connection time, temporary internet protocol address and temporary storage space.
In an embodiment, when the processor 701 executes the first cloud server allocated to the user, the following steps are specifically executed: acquiring a first operating system selected by the user, and allocating a first cloud server pre-installed with the first operating system to the user; when executing the second cloud server allocated to the user, the processor 701 specifically executes the following steps: and acquiring a second operating system selected by the user, and distributing a second cloud server pre-installed with the second operating system to the user.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is merely a logical division, and in actual implementation, there may be other divisions, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.
The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It should be noted that, for the sake of simplicity, the above-mentioned method embodiments are described as a series of acts or combinations, but those skilled in the art should understand that the present application is not limited by the described order of acts, as some steps may be performed in other orders or simultaneously according to the present application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In view of the above description of the cloud server management method, apparatus, storage medium and server terminal provided by the present application, those skilled in the art will appreciate that there may be variations in the specific implementation and application scope according to the concepts of the embodiments of the present application, and in summary, the content of the present specification should not be construed as limiting the present application.
Claims (10)
1. A cloud server management method, the method comprising:
acquiring a login request of a user, and determining the user type of the user according to the login request;
determining a login mode corresponding to the user according to the user type, and verifying a login request of the user according to the login mode;
and if the login request of the user is successfully verified according to the login mode, distributing the login request to a cloud server and server resources corresponding to the user according to the user type.
2. The method of claim 1, wherein obtaining a login request of a user and determining a user type of the user according to the login request comprises:
acquiring user identity information carried in a login request of a user;
and determining the user type of the user according to the user identity information, wherein the user type at least comprises a paid user and a common user.
3. The method according to claim 2, wherein the determining the login manner corresponding to the user according to the user type includes:
if the user type is a payment user, determining that the login mode corresponding to the user is a first login mode, wherein the first login mode is password authentication login;
and if the user type is a common user, determining that the login mode corresponding to the user is a second login mode, wherein the second login mode is connection resource evaluation login.
4. The method of claim 3, wherein said authenticating the user's login request based on the login type comprises:
if the login mode is a first login mode, acquiring account information and password information of the user, wherein the password information comprises at least one of a plaintext password, biological identification information and equipment identity information, and verifying the account information and the password;
if the account information and the password are the same as locally stored authentication information, the login request of the user is determined to be successfully authenticated, and if the account information and the password are not the same as locally stored authentication information, the login request of the user is determined to be failed to be authenticated.
5. The method of claim 3, wherein said authenticating the user's login request based on the login type comprises:
if the login mode is a second login mode, acquiring the current user connection number of the server terminal, and comparing the current user connection number with a user connection number threshold;
if the current user connection number is less than or equal to the user connection number threshold, determining that the login request of the user is successfully verified, and if the current user connection number is greater than the user connection number threshold, determining that the login request of the user is failed to be verified.
6. The method according to claim 3, wherein the allocating to the cloud server and the server resource corresponding to the user according to the user type comprises:
if the user type is a paid user, allocating the user type to a first cloud server of the user, wherein the first cloud server has at least one fixed authority, and the fixed authority at least comprises: fixed use time, fixed internet protocol address and fixed storage space;
if the user type is a common user, allocating the user type to a second cloud server of the user, wherein the second cloud server has at least one temporary authority, and the temporary authority at least comprises: temporary connection time, temporary internet protocol address and temporary storage space.
7. The method of claim 6, wherein the assigning to the user the first cloud server comprises:
acquiring a first operating system selected by the user, and allocating a first cloud server pre-installed with the first operating system to the user;
the second cloud server assigned to the user includes:
and acquiring a second operating system selected by the user, and distributing a second cloud server pre-installed with the second operating system to the user.
8. A cloud server management apparatus, the apparatus comprising:
the system comprises a user type determining module, a user type determining module and a user type determining module, wherein the user type determining module is used for acquiring a login request of a user and determining the user type of the user according to the login request;
the user request verification module is used for determining a login mode corresponding to the user according to the user type and verifying the login request of the user according to the login mode;
and the cloud server allocation module is used for allocating the cloud server and the server resources corresponding to the user according to the user type if the login request of the user is successfully verified according to the login mode.
9. A computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the steps of the method according to any of claims 1 to 7.
10. A server terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method of any of claims 1 to 7 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110022605.0A CN112733101A (en) | 2021-01-07 | 2021-01-07 | Cloud server management method, device, storage medium and server terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110022605.0A CN112733101A (en) | 2021-01-07 | 2021-01-07 | Cloud server management method, device, storage medium and server terminal |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112733101A true CN112733101A (en) | 2021-04-30 |
Family
ID=75591268
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110022605.0A Pending CN112733101A (en) | 2021-01-07 | 2021-01-07 | Cloud server management method, device, storage medium and server terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112733101A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115118760A (en) * | 2022-06-24 | 2022-09-27 | 深圳证券信息有限公司 | Session connection control method, session connection control device, and computer storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105871862A (en) * | 2016-04-19 | 2016-08-17 | 杭州华三通信技术有限公司 | Network resource accessing method and device |
| CN106407830A (en) * | 2015-07-29 | 2017-02-15 | 阿里巴巴集团控股有限公司 | Detection method and device of cloud-based database |
-
2021
- 2021-01-07 CN CN202110022605.0A patent/CN112733101A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106407830A (en) * | 2015-07-29 | 2017-02-15 | 阿里巴巴集团控股有限公司 | Detection method and device of cloud-based database |
| CN105871862A (en) * | 2016-04-19 | 2016-08-17 | 杭州华三通信技术有限公司 | Network resource accessing method and device |
Non-Patent Citations (1)
| Title |
|---|
| 刘邦奇 等: "《数字化校园理念、设计与实现》", vol. 1, 中国科学技术大学出版社, pages: 174 - 175 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115118760A (en) * | 2022-06-24 | 2022-09-27 | 深圳证券信息有限公司 | Session connection control method, session connection control device, and computer storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11012455B2 (en) | Modifying a user session lifecycle in a cloud broker environment | |
| US11489671B2 (en) | Serverless connected app design | |
| US20180109549A1 (en) | Securing services in a networked computing environment | |
| US9225744B1 (en) | Constrained credentialed impersonation | |
| US10796001B2 (en) | Software verification method and apparatus | |
| US8811944B2 (en) | Authentication request management | |
| CN107911352B (en) | Authorization method of cloud mobile phone | |
| CN112653681B (en) | Multi-feature fusion user login access method, device and system | |
| US11570035B2 (en) | Techniques for accessing logical networks via a virtualized gateway | |
| CN110493239B (en) | Authentication method and device | |
| US20150244705A1 (en) | Implementing single sign-on in a transaction processing system | |
| CN103975567A (en) | Dual-factor authentication method and virtual machine device | |
| CN114139135B (en) | Equipment login management method, device and storage medium | |
| US11366883B2 (en) | Reflection based endpoint security test framework | |
| US9760412B2 (en) | Client server communication system | |
| CN114186206A (en) | Login method and device based on small program, electronic equipment and storage medium | |
| CN112733101A (en) | Cloud server management method, device, storage medium and server terminal | |
| CN111666590A (en) | Distributed file secure transmission method, device and system | |
| CN113656169A (en) | Task request processing method and device, management server and storage medium | |
| CN116018580A (en) | Techniques for instance persistence data across cloud shells | |
| CA2850114C (en) | Techniques for accessing logical networks via a programmatic service call | |
| CN111259369A (en) | Man-machine identity verification method and system | |
| CN112929162B (en) | Password management method and system, electronic equipment and readable storage medium | |
| CN114079925A (en) | Binding method and binding system of intelligent device and terminal | |
| CN117459245A (en) | Method, device and system for accessing identity data |
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 |