IPMI and Redfish Account Synchronization Method

Abstract

An IPMI and Redfish account synchronization method is implemented by a baseboard management control module. The baseboard management control module includes an account synchronization management unit. The account synchronization management unit stores a data correspondence table including a first data and a second data. The first data includes account information related to one of IPMI and Redfish, and the second data includes account information related to the other of IPMI and Redfish. The method includes the following steps: (A) When receiving a first setting request related to the setting process of the first data, parsing the first setting request to generate a first parsed data; (B) Performing a corresponding process on the first parsed data according to the data correspondence table to generate and store a corresponding data; and (C) Updating the first data and the second data according to the corresponding data.

Description

Technical Field

[0001] The present invention relates to a synchronization method, and more particularly to an IPMI and Redfish account synchronization method.

Background Art

[0002] Intelligent Platform Management Interface (IPMI) is a set of computer interface specifications for autonomous computer subsystems, which provides management and monitoring functions independent of the host system. Nowadays, most servers come with an IPMI system, which is independently installed on the motherboard chip. Users can remotely control the server, such as power on / off, install the system, enter the server terminal, etc.

[0003] However, the IPMI system can only manage a single server at a time, which does not meet the user's expectations. Usually, users expect to manage a large number of servers, such as installing the system for 100 servers at one time. And the IPMI operations of servers provided by different manufacturers are different. Therefore, the Redfish standard is needed to unify the basic operations of all servers.

[0004] The Redfish standard is a set of specifications that provides industry-standard protocols and RESTful interfaces for the management of servers, storage, networks, and converged infrastructure, enabling users to easily achieve automated management of a large number of servers using tools such as Ansible.

[0005] However, in the existing technology, IPMI and Redfish in a single server have their own accounts and passwords. When managing the server, users need to use different account passwords to log in to the IPMI and Redfish systems of the same server respectively, which is extremely inconvenient.

Summary of the Invention

[0006] Therefore, an object of the present invention is to provide an IPMI and Redfish account synchronization method that can synchronize IPMI and Redfish accounts.

[0007] Thus, the IPMI and Redfish account synchronization method of the present invention is implemented by a baseboard management control module. The baseboard management control module includes a processing unit related to one of IPMI and Redfish, and an account synchronization management unit. The account synchronization management unit stores a data correspondence table including a first data and a second data. The first data includes account information related to one of IPMI and Redfish, and the second data includes account information related to the other of IPMI and Redfish, and includes a step (A), a step (B), and a step (C).

[0008] In step (A), when a setting request related to the setting process of the first data from the processing unit is received, the account synchronization management unit parses the setting request to generate parsed data.

[0009] In step (B), the account synchronization management unit performs corresponding processing on the parsed data according to the data correspondence table to generate and store corresponding data related to the first data and the second data.

[0010] In step (C), the account synchronization management unit updates the first data and the second data according to the corresponding data.

[0011] Compared with the prior art, after the account synchronization management unit parses the setting request to generate the parsed data, according to the data correspondence table, the parsed data is subjected to corresponding processing, and the corresponding data is generated and synchronously stored, so as to integrate the IPMI and Redfish accounts, enabling the user to use the same set of accounts to operate on IPMI and Redfish, achieving the technical effect of improving the convenience of the user.

Description of the Drawings

[0012] Other features and effects of the present invention will be clearly presented in the embodiments with reference to the drawings, wherein:

[0013] Figure 1 is a block diagram illustrating a baseboard management control module of an embodiment for implementing the IPMI and Redfish account synchronization method of the present invention;

[0014] Figure 2 is a flowchart illustrating an IPMI account synchronization program of the embodiment of the IPMI and Redfish account synchronization method of the present invention; and

[0015] Figure 3 is a flowchart illustrating a Redfish account synchronization program of the embodiment of the IPMI and Redfish account synchronization method of the present invention.

Detailed Embodiments

[0016] Before the present invention is described in detail, it should be noted that in the following description, similar components are denoted by the same reference numerals.

[0017] Refer to Figure 1, which shows a baseboard management control module 1. The baseboard management control module 1 includes an IPMI processing unit 11 related to IPMI, an IPMI interface 12, a Redfish processing unit 13 related to Redfish, a Redfish interface 14, and an account synchronization management unit 15. The baseboard management control module 1 is used to implement an embodiment of the IPMI and Redfish account synchronization method of the present invention.

[0018] It should be noted that, in this embodiment, the baseboard management control module 1 is, for example, a Baseboard Management Controller (BMC), the IPMI processing unit 11 is, for example, an IPMI message handler, and the Redfish processing unit 13 is, for example, a Redfish request handler, but not limited thereto.

[0019] The IPMI processing unit 11 is electrically connected to the IPMI interface 12. The IPMI interface 12 can be implemented in ways such as, for example, a Keyboard Controller Style (KCS) interface, a Local Area Network (LAN), a Serial interface, a Universal Serial Bus (USB) interface, a System Management Bus (SMBus), and an Inter-Integrated Circuit (I 2 C) interface.

[0020] The Redfish processing unit 13 is electrically connected to the Redfish interface 14. The Redfish interface 14 is, for example, a Representational State Transfer Application Programming Interface (RESTful API).

[0021] The account synchronization management unit 15 is electrically connected to the IPMI processing unit 11 and the Redfish processing unit 13. The account synchronization management unit 15 stores a status flag and a data correspondence table including IPMI data and Redfish data. The IPMI data has IPMI account information, and the Redfish data has Redfish account information. The flag value of the status flag is one of a first predetermined value indicating that the account synchronization management unit 15 is in an access state, and a second predetermined value different from the first predetermined value and indicating that the account synchronization management unit 15 is not in the access state. The IPMI data includes an IPMI user unique identifier, an IPMI user name, an IPMI user status, and an IPMI user channel access permission / authentication. The Redfish data includes a Redfish user unique identifier corresponding to the IPMI user unique identifier, a Redfish user name corresponding to the IPMI user name, a Redfish user status corresponding to the IPMI user status, and Redfish authentication / lock / role / action and other information corresponding to the IPMI user channel access permission / authentication.

[0022] For example, the data correspondence table is as shown in Table 1 below. From the data correspondence table, it can be seen that the IPMI identifiers 2, 5, and 4 in the IPMI account information of the IPMI data respectively correspond to the Redfish identifiers 4, 8, and 9 in the Redfish account information of the Redfish data. The User, Operator, and Administrator statuses of IPMI Privilege in the IPMI account information of the IPMI data respectively correspond to the Read Only, Operator, and Administrator statuses of Redfish Role in the Redfish account information of the Redfish data.

[0023] Table 1

[0024]

[0025] Refer to Figure 1 、 Figure 2 、 Figure 3 to illustrate how the baseboard management control module 1 executes this embodiment of the IPMI and Redfish account synchronization method of the present invention. This embodiment includes an IPMI account synchronization program and a Redfish account synchronization program.

[0026] Refer to Figure 1 、 Figure 2 The following describes the IPMI account synchronization program.

[0027] In step 201, the IPMI processing unit 11 receives an IPMI command from the IPMI interface 12.

[0028] In step 202, the IPMI processing unit 11 determines whether the IPMI command is a specific command. The IPMI command has a command code. The IPMI processing unit 11 compares the IPMI command with at least one default command code. When the IPMI command matches one of the at least one default command codes, it is determined that the IPMI command is the specific command. The at least one default command code can be stored inside the baseboard management control module 1 or in a memory connected to the baseboard management control module 1, or can be stored in the firmware program code of the baseboard management control module 1 in the form of parameters. When the IPMI processing unit 11 determines that the IPMI command is the specific command, the process proceeds to step 203; when the IPMI processing unit 11 determines that the IPMI command is not the specific command, step 201 is repeated.

[0029] It should be noted that in this embodiment, the specific command is one of a set user name command, a set user password command, a set user access permission command, etc., which respectively correspond to multiple contents for modifying user account information, but is not limited thereto.

[0030] In step 203, the IPMI processing unit 11 generates and transmits an IPMI setting request related to the setting process of the IPMI data to the account synchronization management unit 15.

[0031] In step 204, the account synchronization management unit 15 determines whether the flag value of the status flag is the first predetermined value. When the account synchronization management unit 15 determines that the flag value is the first predetermined value, the process proceeds to step 205; when the account synchronization management unit 15 determines that the flag value is the second predetermined value, the process proceeds to step 206.

[0032] In step 205, the account synchronization management unit 15 generates and transmits an access warning message indicating that access is in progress to the IPMI processing unit 11, and ends the IPMI synchronization program.

[0033] In step 206, the account synchronization management unit 15 updates the flag value to the first predetermined value.

[0034] In step 207, the account synchronization management unit 15 analyzes the IPMI setting request to generate IPMI analysis data.

[0035] In step 208, the account synchronization management unit 15 performs corresponding processing (ID mapping, Hash) on the IPMI parsing data according to the data correspondence table to generate and store corresponding data related to the IPMI data and the Redfish data.

[0036] In step 209, the account synchronization management unit 15 updates the IPMI data and the Redfish data according to the corresponding data.

[0037] For example, the IPMI data and the Redfish data before synchronization are shown in Table 2 and Table 3 respectively. The IPMI instruction is, for example, a set user name instruction. The IPMI parsing data includes an IPMI identifier 2 and a set user name (NewUserName1). The account synchronization management unit 15 performs corresponding processing according to the data correspondence table, that is, finds a Redfish identifier 4 corresponding to the IPMI identifier 2, and generates the corresponding data including the IPMI and the Redfish set user names. The account synchronization management unit 15 updates the IPMI data and the Redfish data according to the corresponding data, as shown in Table 4 and Table 5.

[0038] Table 2

[0039] IPMI Identifier User Name Password IPMI Privilege 2 UserName1 123456 User

[0040] Table 3

[0041] Redfish Identifier User Name Password Redfish Role 4 UserName1 123456 Read Only

[0042] Table 4

[0043] IPMI Identifier User Name Password IPMI Privilege 2 New UserName1 123456 User

[0044] Table 5

[0045] Redfish Identifier User Name Password Redfish Role 4 New UserName1 123456 Read Only

[0046] Continuing from the above, the IPMI data and the Redfish data before synchronization are shown in Table 2 and Table 3 respectively. If the IPMI instruction is, for example, to set user access permissions, the IPMI parsed data packet includes an IPMI identifier 2 and a set user access permission (Operator). The account synchronization management unit 15 performs corresponding processing according to the data correspondence table, that is, finds a Redfish identifier 4 corresponding to the IPMI identifier 2 and finds the Operator status of the Redfish Role corresponding to the Operator status of IPMI Privilege, and generates the corresponding data including the IPMI and Redfish set user access permissions. The account synchronization management unit 15 updates the IPMI data and the Redfish data according to the corresponding data, as shown in Table 6 and Table 7.

[0047] Table 6

[0048] IPMI Identifier User Name Password IPMI Privilege 2 UserName1 123456 Operator

[0049] Table 7

[0050] Redfish Identifier User Name Password Redfish Role 4 UserName1 123456 Operator

[0051] In step 210, the account synchronization management unit 15 updates the flag value to the second predetermined value and ends the IPMI synchronization program.

[0052] Refer to Figure 1 、 Figure 3 , the following describes the Redfish synchronization program.

[0053] In step 301, the Redfish processing unit 13 receives a Redfish request including a Uniform Resource Locator (URL) from the Redfish interface 14.

[0054] In step 302, the Redfish processing unit 13 determines whether the URL of the Redfish request is a specific URL. When the Redfish processing unit 13 determines that the URL of the Redfish request is the specific URL, the process proceeds to step 303; when the Redfish processing unit 13 determines that the URL of the Redfish request is not the specific URL, step 301 is repeated.

[0055] It should be noted that, in this embodiment, the specific URL includes a specific string, and the specific string is, for example, the string

[0056] 「https: / / {{bmc_ip}} / redfish / v1 / AccountService / Accounts」, but not limited thereto.

[0057] In step 303, the Redfish processing unit 13 generates and transmits a Redfish setting request related to the setting process of the Redfish data to the account synchronization management unit 15.

[0058] In step 304, the account synchronization management unit 15 determines whether the flag value of the status flag is the first predetermined value. When the account synchronization management unit 15 determines that the flag value is the first predetermined value, the process proceeds to step 305; when the account synchronization management unit 15 determines that the flag value is the second predetermined value, the process proceeds to step 306.

[0059] In step 305, the account synchronization management unit 15 generates and transmits an access warning message indicating that access is in progress to the Redfish processing unit 13, and ends the Redfish synchronization program.

[0060] In step 306, the account synchronization management unit 15 updates the flag value to the first predetermined value.

[0061] In step 307, the account synchronization management unit 15 parses the Redfish setting request to generate a Redfish parsing data.

[0062] In step 308, the account synchronization management unit 15 performs a corresponding process on the Redfish parsing data according to the data correspondence table to generate and store a corresponding data related to the IPMI data and the Redfish data.

[0063] For example, the IPMI data and the Redfish data before synchronization are shown in Table 2 and Table 3 respectively. The website is related to setting the user name, for example. The Redfish parsing data includes a Redfish identifier 4 and a set user name (New UserName1). The account synchronization management unit 15 performs a corresponding process according to the data correspondence table, that is, finds an IPMI identifier 2 corresponding to the Redfish identifier 4, and generates the corresponding data including the IPMI and the set user name of Redfish. The account synchronization management unit 15 updates the IPMI data and the Redfish data according to the corresponding data, as shown in Table 4 and Table 5.

[0064] For another example, the IPMI data and the Redfish data before synchronization are shown in Tables 6 and 7 respectively. If the website is related to setting user access permissions, for example, the Redfish parsed data includes a Redfish identifier 4 and a set user access permission (Read Only). The account synchronization management unit 15 performs corresponding processing according to the data correspondence table, that is, finds an IPMI identifier 2 corresponding to the Redfish identifier 4 and finds the User state of the IPMI Privilege corresponding to the Read Only state of the Redfish Role, and generates the corresponding data including the IPMI and the set user access permission after Redfish setting. The account synchronization management unit 15 updates the IPMI data and the Redfish data according to the corresponding data, as shown in Tables 2 and 3.

[0065] In step 309, the account synchronization management unit 15 updates the IPMI data and the Redfish data according to the corresponding data.

[0066] In step 310, the account synchronization management unit 15 updates the flag value to the second predetermined value and ends the Redfish synchronization program.

[0067] In summary, for the IPMI and Redfish account synchronization method of the present invention, in a system environment where the IPMI processing unit 11 and the Redfish processing unit 13 respectively have user information stored in different memory blocks, the account synchronization management unit 15 determines the flag value of the status flag to prevent simultaneous access to data from the IPMI processing unit 11 and the Redfish processing unit 13, which may cause inconsistent accessed data. After parsing the setting request to generate the parsed data, the parsed data is automatically processed according to the data correspondence table, and the corresponding data is generated and synchronously stored to integrate the IPMI and Redfish accounts. No matter what content in the user account information (information in the User Profile) of any interface is modified, the system will automatically synchronously update the corresponding content of the user account information of other interfaces, enabling the user not to log in through different interfaces one by one and modify the user account information corresponding to each interface one by one. For example, after the user modifies the password of Redfish to a new password through the Redfish interface 14 and then logs out, the user can directly log in to the IPMI interface 12 with the new password just modified through the Redfish interface 14, without having to modify the password again on the IPMI interface 12 and can directly use the new password on the IPMI interface 12. That is to say, as long as the user modifies the user account information once on any interface, the system will automatically synchronously modify the user account information corresponding to each interface respectively, and the user can use the same set of account information to operate on IPMI and Redfish through different interfaces, achieving the technical effect of improving the convenience of the user. Therefore, the object of the present invention can be truly achieved.

[0068] As described above, the above is only the specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present invention can easily think of changes or substitutions, which should all be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims

1. An IPMI and Redfish account synchronization method is implemented by a baseboard management control module. The baseboard management control module includes a processing unit related to one of IPMI and Redfish, and an account synchronization management unit. Among them, The system environment of the processing unit related to IPMI and the processing unit related to Redfish respectively have user information stored in different memory blocks. The account synchronization management unit stores a data correspondence table including a first data and a second data. The first data includes account information related to one of IPMI and Redfish, and the second data includes account information related to the other of IPMI and Redfish. It is characterized in that the method includes the following steps: (A) When receiving a setting request for the setting process of the first data of the account information related to one of IPMI and Redfish from the processing unit, the account synchronization management unit parses the setting request to generate a parsed data; (B) The account synchronization management unit performs a corresponding process on the parsed data according to the data correspondence table to generate a corresponding data related to the first data and the second data; and (C) The account synchronization management unit updates the first data of the account information related to one of IPMI and Redfish according to the corresponding data and synchronously updates the second data of the corresponding account information related to the other of IPMI and Redfish, so that the account information of the first data is consistent with the account information of the second data.

2. The IPMI and Redfish account synchronization method according to claim 1, wherein the account synchronization management unit further stores a status flag, and a flag value of the status flag is one of a first predetermined value indicating that the account synchronization management unit is in an access state and a second predetermined value different from the first predetermined value and indicating that the account synchronization management unit is not in the access state. It is characterized in that, Step (A) includes the following sub-steps: (A-1) When receiving the setting request, the account synchronization management unit determines whether the flag value of the status flag is the first predetermined value; (A-2) When it is determined that the flag value of the status flag is the first predetermined value, the account synchronization management unit generates and transmits an access warning message indicating that access is in progress to the processing unit; (A-3) When it is determined that the flag value of the status flag is the second predetermined value, the account synchronization management unit updates the flag value to the first predetermined value; and (A-4) The account synchronization management unit parses the setting request to generate the parsed data, After step (C), the following steps are further included: (D) The account synchronization management unit updates the flag value to the second predetermined value.

3. The IPMI and Redfish account synchronization method according to claim 1, wherein the processing unit and the account information of the first data are related to IPMI, and the account information of the second data is related to Redfish, characterized in that , Before step (A), the following steps are further included: (E) The processing unit receives an IPMI instruction from an IPMI interface; (F) The processing unit determines whether the IPMI instruction is a specific instruction; (G) When the processing unit determines that the IPMI instruction is the specific instruction, the processing unit generates and transmits the setting request to the account synchronization management unit; and (H) When the processing unit determines that the IPMI instruction is not the specific instruction, step (E) is repeatedly executed.

4. The IPMI and Redfish account synchronization method according to claim 3, wherein In step (F), the specific instruction is one of a set user name instruction, a set user password instruction, and a set user access permission instruction.

5. The IPMI and Redfish account synchronization method according to claim 1, wherein the account information of the processing unit and the first data is related to Redfish, and the account information of the second data is related to IPMI, characterized in that, Before step (A), the following steps are further included: (I) The processing unit receives a Redfish request including a website address from a Redfish interface; (J) The processing unit determines whether the website address of the Redfish request is a specific website address; (K) When the processing unit determines that the URL of the Redfish request is the specific URL, the processing unit generates and transmits the setting request to the account synchronization management unit; and (L) When the processing unit determines that the URL of the Redfish request is not the specific URL, step (H) is repeatedly executed.

6. The IPMI and Redfish account synchronization method according to claim 5, wherein, In step (I), the specific URL includes a specific string.

Images