TW201328246A - Method and system for managing cloud server system - Google Patents
Method and system for managing cloud server system Download PDFInfo
- Publication number
- TW201328246A TW201328246A TW100147603A TW100147603A TW201328246A TW 201328246 A TW201328246 A TW 201328246A TW 100147603 A TW100147603 A TW 100147603A TW 100147603 A TW100147603 A TW 100147603A TW 201328246 A TW201328246 A TW 201328246A
- Authority
- TW
- Taiwan
- Prior art keywords
- node
- microcontroller
- electronic device
- information
- related information
- Prior art date
Links
Landscapes
- Small-Scale Networks (AREA)
Abstract
Description
本發明是有關於一種雲端伺服系統，且特別是有關於一種雲端伺服系統的管理方法及管理系統。The present invention relates to a cloud server system, and more particularly to a cloud server system management method and management system.
目前伺服器(server)廣為各企業所使用，發展的範圍除了結合網際網路(internet)與電信業的應用外，也更深入到一般人的生活中，例如金融、財經、網路銀行、網路***的使用等等，這些都必需靠著伺服器強大的運算能力，才能做到資料高度保密且不易被破解之程度。At present, the server is widely used by various enterprises. The development scope is not only combined with the application of the internet and the telecom industry, but also deepens into the lives of ordinary people, such as finance, finance, online banking, and the Internet. The use of credit cards, etc., all rely on the powerful computing power of the server to achieve a high degree of confidentiality and difficulty in being cracked.
現今雲端伺服系統的種類有很多種，比較常見的有機架式伺服器(rack server)與塔式伺服器(tower server)。其中，機架伺服器是一種優化結構的塔式伺服器，它的設計宗旨主要是為了盡可能減少空間的佔用。很多專業網路設備都是採用機架式的結構(例如交換機、路由器、硬體防火牆等等)，其多為扁平式，就如同抽屜一般。一般而言，機架伺服器的寬度為19英寸，高度以U為單位(1U=1.75英寸=44.45毫米)，通常有1U，2U，3U，4U，5U，7U幾種標準的伺服器。There are many types of cloud-based servo systems today. The more common ones are rack servers and tower servers. Among them, the rack server is an optimized structure of the tower server, which is designed to minimize space occupation. Many professional network devices are rack-mounted (such as switches, routers, hardware firewalls, etc.), which are mostly flat, just like drawers. In general, the rack server has a width of 19 inches and a height in U (1U = 1.75 inches = 44.45 mm). There are usually 1U, 2U, 3U, 4U, 5U, 7U standard servers.
而在組裝完雲端伺服系統之後，便是要對雲端伺服系統部署(deploy)作業系統。而在進行雲端作業系統的部署之前，要知道所有機櫃(container)上節點的相關資訊，包括機櫃的實體佈局(physical layout)，方能進行雲端作業系統部署之工作。目前是採用人工以手動方式來輸入各個節點的相關資訊。然而，在節點數量不多時尚可利用此作法，一但節點數量相當龐大時(例如500個以上的節點)，手動作法就會顯得非常沒效率，並且容易出錯。After assembling the cloud servo system, it is necessary to deploy the operating system to the cloud servo system. Before deploying the cloud operating system, you need to know the information about all the nodes on the container, including the physical layout of the cabinet, in order to deploy the cloud operating system. Currently, manual information is manually entered for each node. However, this method can be used in a small number of nodes. Once the number of nodes is quite large (for example, more than 500 nodes), the hand motion method is very inefficient and error-prone.
本發明提供一種雲端伺服系統的管理方法及管理系統，自動找出機櫃(container)上每一個節點的節點相關資訊，以便能將雲端作業系統自動部署至此機櫃。The invention provides a management method and a management system for a cloud server system, which automatically finds node-related information of each node on a container, so that the cloud operation system can be automatically deployed to the cabinet.
具體而言，本發明提出一種雲端伺服系統的管理方法，適於透過管理伺服器來管理雲端伺服系統。在此，雲端伺服系統包括多個節點，每一節點設置有一電子裝置，而此電子裝置包括中央處理單元以及微控制器。此管理方法中，管理伺服器自電子裝置接收到微控制器的硬體位址之後，會分配網路位址給電子裝置的微控制器。並且，管理伺服器會依據網路位址傳送指令給微控制器。而當微控制器接收到上述指令時，將中央處理單元重新開機，以在重新開機的過程中，透過微控制器取得電子裝置的節點相關資訊。而微控制器回應上述指令，而傳送節點相關資訊至管理伺服器，使得管理伺服器依據節點相關資訊來管理電子裝置。Specifically, the present invention provides a management method of a cloud server system, which is adapted to manage a cloud server system through a management server. Here, the cloud servo system includes a plurality of nodes, each node is provided with an electronic device, and the electronic device includes a central processing unit and a microcontroller. In this management method, after the management server receives the hardware address of the microcontroller from the electronic device, the network address is assigned to the microcontroller of the electronic device. Also, the management server sends instructions to the microcontroller based on the network address. When the microcontroller receives the above instruction, the central processing unit is restarted to obtain node related information of the electronic device through the microcontroller during the restarting process. The microcontroller responds to the above instructions and transmits the node related information to the management server, so that the management server manages the electronic device according to the node related information.
在本發明之一實施例中，上述當微控制器接收到上述指令時，透過韌體將中央處理單元重新開機至指令介面殼層。而在重新開機至指令介面殼層的過程中，更可透過韌體來動態取得節點相關資訊中的動態資訊。並且，透過系統管理韌體結構來取得節點相關資訊中的靜態資訊。之後，再將節點相關資訊傳送至微控制器。In an embodiment of the invention, when the microcontroller receives the above instruction, the central processing unit is rebooted to the command interface shell through the firmware. In the process of rebooting to the command interface shell, the dynamic information in the node related information can be dynamically obtained through the firmware. Moreover, the system manages the firmware structure to obtain static information in the node related information. After that, the node related information is transmitted to the microcontroller.
在本發明之一實施例中，上述節點相關資訊包括處理器資訊、網路卡資訊、記憶體資訊、硬碟資訊、節點位置、節點高度資訊、節點置法資訊、節點類型資訊、韌體資訊以及微控制器資訊至少其中之一。In an embodiment of the present invention, the node related information includes processor information, network card information, memory information, hard disk information, node location, node height information, node method information, node type information, and firmware information. And at least one of the microcontroller information.
在本發明之一實施例中，上述在微控制器回應上述指令，而傳送節點相關資訊至管理伺服器的步驟之後，管理伺服器還可依據節點相關資訊得知電子裝置位於雲端伺服系統中的節點位置，藉以獲得電子裝置於雲端伺服系統中的位置順序。並且，依據位置順序，重新分配微控制器以及系統網卡的網路位址。In an embodiment of the present invention, after the step of the microcontroller responding to the instruction and transmitting the node related information to the management server, the management server may further learn, according to the node related information, that the electronic device is located in the cloud servo system. The location of the node is used to obtain the position order of the electronic device in the cloud servo system. Also, the microcontroller and the network address of the system NIC are reassigned according to the location order.
在本發明之一實施例中，上述在微控制器回應上述指令，而傳送節點相關資訊至管理伺服器的步驟之後，管理伺服器便可依據節點相關資訊來決定電子裝置所欲部署(deploy)的服務，並且將節點相關資訊傳送至雲端部署程序，以進行雲端作業系統的部署。In an embodiment of the present invention, after the step of the microcontroller responding to the instruction and transmitting the node related information to the management server, the management server may determine the deployment of the electronic device according to the node related information. Service, and transfer node related information to the cloud deployment program for deployment of the cloud operating system.
另一方面，本發明提出一種管理系統，透過管理伺服器來管理雲端伺服系統。其中，雲端伺服系統包括一機櫃，機櫃中包括交換機以及多個節點，每一個節點中設置有一電子裝置。而此電子裝置包括中央處理單元及微控制器，且中央處理單元耦接至微控制器。管理伺服器耦接至交換機，以透過交換機來管理雲端伺服系統。其中，管理伺服器自電子裝置接收微控制器的硬體位址，以分配網路位址給電子裝置的微控制器，並且，管理伺服器依據網路位址傳送指令給微控制器。另外，當微控制器在接收到上述指令時，將中央處理單元重新開機，以在重新開機的過程中，透過微控制器取得電子裝置的節點相關資訊，並且，微控制器回應上述指令，而傳送節點相關資訊至管理伺服器，使得管理伺服器依據節點相關資訊來管理電子裝置。In another aspect, the present invention provides a management system for managing a cloud servo system through a management server. The cloud servo system includes a cabinet, the switch includes a switch and a plurality of nodes, and each node is provided with an electronic device. The electronic device includes a central processing unit and a microcontroller, and the central processing unit is coupled to the microcontroller. The management server is coupled to the switch to manage the cloud servo system through the switch. The management server receives the hardware address of the microcontroller from the electronic device to allocate the network address to the microcontroller of the electronic device, and the management server transmits the instruction to the microcontroller according to the network address. In addition, when the microcontroller receives the above instruction, the central processing unit is restarted to obtain node related information of the electronic device through the microcontroller during the restarting process, and the microcontroller responds to the above instruction. The node related information is transmitted to the management server, so that the management server manages the electronic device according to the node related information.
在本發明之一實施例中，上述機櫃包括r個機架，每一個機架包括一機架編號模組及s個插槽；每一個插槽包括一插槽編號模組及n個節點；而每一個節點包括一節點編號模組。上述r、s及n為大於或等於1的正整數。其中，插槽i包括一擴展器，其耦接至插槽i中的n個節點各自的節點編號模組、插槽i的插槽編號模組以及插槽i所在的機架的機架編號模組，使得設置在每一個節點中之電子裝置透過擴展器而得知其所在的節點位置。而上述i為1~s。In an embodiment of the present invention, the cabinet includes r racks, each rack includes a rack number module and s slots; each slot includes a slot numbering module and n nodes; Each node includes a node numbering module. The above r, s and n are positive integers greater than or equal to 1. The slot i includes an expander coupled to the node number module of each of the n nodes in the slot i, the slot number module of the slot i, and the rack number of the rack where the slot i is located. The module enables the electronic device disposed in each node to know the location of the node where it is located through the expander. The above i is 1~s.
在本發明之一實施例中，上述電子裝置更包括控制晶片以及韌體晶片。控制晶片耦接至中央處理單元及微控制器。韌體晶片儲存一韌體，此韌體晶片耦接至控制晶片。其中，當微控制器接收到指令時，透過韌體將中央處理單元重新開機至指令介面殼層，並在重新開機至指令介面殼層的過程中，由韌體取得節點相關資訊並將節點相關資訊傳送至微控制器。In an embodiment of the invention, the electronic device further includes a control wafer and a firmware wafer. The control chip is coupled to the central processing unit and the microcontroller. The firmware wafer stores a firmware that is coupled to the control wafer. Wherein, when the microcontroller receives the instruction, the central processing unit is rebooted to the instruction interface shell through the firmware, and in the process of rebooting to the instruction interface shell, the firmware obtains node related information and correlates the node. Information is transferred to the microcontroller.
在本發明之一實施例中，上述管理伺服器依據節點相關資訊得知電子裝置位於機櫃中的節點位置，藉以獲得電子裝置於機櫃中的位置順序，而依據此位置順序，重新分配微控制器以及電子裝置的系統網卡的網路位址。In an embodiment of the present invention, the management server learns that the electronic device is located at a node position in the cabinet according to the information about the node, and obtains the position sequence of the electronic device in the cabinet, and redistributes the microcontroller according to the position sequence. And the network address of the system network card of the electronic device.
基於上述，本發明透過設置在各個節點中之電子裝置的微控制器來取得電子裝置的節點相關資訊，並傳送回管理伺服器，藉此便能夠自動找出機櫃上每一個節點的節點相關資訊，以便能將雲端作業系統自動部署至此機櫃。Based on the above, the present invention acquires node-related information of the electronic device through the microcontroller of the electronic device disposed in each node, and transmits the information to the management server, thereby automatically finding the node-related information of each node on the cabinet. In order to automatically deploy the cloud operating system to this cabinet.
為讓本發明之上述特徵和優點能更明顯易懂，下文特舉實施例，並配合所附圖式作詳細說明如下。The above described features and advantages of the present invention will be more apparent from the following description.
圖1是依照本發明第一實施例的管理系統的方塊圖。請參照圖1，管理系統100包括管理伺服器110及雲端伺服系統120。雲端伺服系統120中包括節點130_1~節點130_N，並且每一個節點設置有一電子裝置。在此，以節點130_1的電子裝置140為例，電子裝置140包括中央處理單元141以及微控制器143。其中，中央處理單元141耦接至微控制器143。另外，節點130_2~節點130_N的電子裝置亦與上述電子裝置140相似，具有中央處理單元以及微控制器。1 is a block diagram of a management system in accordance with a first embodiment of the present invention. Referring to FIG. 1 , the management system 100 includes a management server 110 and a cloud server system 120 . The cloud servo system 120 includes nodes 130_1~130_N, and each node is provided with an electronic device. Here, taking the electronic device 140 of the node 130_1 as an example, the electronic device 140 includes a central processing unit 141 and a microcontroller 143. The central processing unit 141 is coupled to the microcontroller 143. In addition, the electronic devices of the nodes 130_2 to 130_N are similar to the electronic device 140 described above, and have a central processing unit and a microcontroller.
管理伺服器110用以管理雲端伺服系統120中設置在節點130_1~節點130_N中的電子裝置。例如，透過管理伺服器110自節點130_1~節點130_N的電子裝置來取得其節點相關資訊，方能夠來管理這些節點130_1~節點130_N，並且進一步部署(deploy)作業系統至雲端伺服系統120。The management server 110 is configured to manage the electronic devices disposed in the node 130_1~the node 130_N in the cloud server system 120. For example, the management server 110 can obtain the node related information from the electronic devices of the node 130_1~the node 130_N to manage the nodes 130_1~130_N, and further deploy the operating system to the cloud servo system 120.
進一步地說，雲端伺服系統120包括至少一機櫃(container)，機櫃中包括多個機架(rack)，每一個機架中包括多個插槽(slot)，每一個插槽包括多個節點。並且，機櫃中設置有一交換機(switch)，此交換機與各個節點中所設置的電子裝置耦接，使得管理伺服器110透過交換機來管理這些電子裝置。Further, the cloud servo system 120 includes at least one container, and the rack includes a plurality of racks, each of which includes a plurality of slots, each of which includes a plurality of nodes. Moreover, a switch is disposed in the cabinet, and the switch is coupled to the electronic devices disposed in the respective nodes, so that the management server 110 manages the electronic devices through the switch.
底下即搭配上述管理系統100來說明雲端伺服系統120的管理方法。圖2是依照本發明第一實施例的雲端伺服系統的管理方法流程圖。為了方便說明，在本實施例中以節點130_1的電子裝置140為例，而其他節點130_2~節點130_N的作動亦與節點130_1相同，故在此不詳述。The management method of the cloud servo system 120 will be described below with the above management system 100. 2 is a flow chart of a method for managing a cloud server system according to a first embodiment of the present invention. For convenience of description, in the embodiment, the electronic device 140 of the node 130_1 is taken as an example, and the operations of the other nodes 130_2 to 130_N are also the same as those of the node 130_1, and therefore will not be described in detail herein.
請同時參照圖1及圖2，在步驟S205中，管理伺服器110自電子裝置140接收微控制器143的硬體位址，以分配網路位址給電子裝置140的微控制器143。具體而言，管理伺服器110具有動態主機組態協定(Dynamic Host Configuration Protocol，DHCP)伺服(Server)功能，當接收到電子裝置140的微控制器143的硬體位址時，便會自動分配一個網路位址給微控制器143。同時，會將此硬體位址與網路位址記錄在管理伺服器110中。在此，硬體位址例如為媒體存取控制(Media Access Control，MAC)位址，網路位址例如為網際網路通訊協定(Internet Protocol，IP)位址。Referring to FIG. 1 and FIG. 2 simultaneously, in step S205, the management server 110 receives the hardware address of the microcontroller 143 from the electronic device 140 to allocate the network address to the microcontroller 143 of the electronic device 140. Specifically, the management server 110 has a Dynamic Host Configuration Protocol (DHCP) Servo (Server) function. When the hardware address of the microcontroller 143 of the electronic device 140 is received, an automatic assignment is automatically assigned. The network address is given to the microcontroller 143. At the same time, the hardware address and the network address are recorded in the management server 110. Here, the hardware address is, for example, a Media Access Control (MAC) address, and the network address is, for example, an Internet Protocol (IP) address.
接著，在步驟S210中，管理伺服器110依據網路位址傳送一指令給微控制器143，以要求微控制器143去取得節點相關資訊。上述指令例如為智慧平台管理介面(Intelligent Platform Management Interface)的OEM(Original Equipment Manufacturer)指令。Next, in step S210, the management server 110 transmits an instruction to the microcontroller 143 according to the network address to request the microcontroller 143 to obtain the node related information. The above instructions are, for example, an OEM (Original Equipment Manufacturer) instruction of the Intelligent Platform Management Interface.
在步驟S215中，當微控制器143接收到上述指令時，會將中央處理單元141重新開機，以在重新開機的過程中，透過微控制器143取得電子裝置140的節點相關資訊。節點相關資訊包括處理器資訊、網路卡資訊、記憶體資訊、硬碟資訊、節點位置、節點高度資訊、節點置法資訊、節點類型資訊、韌體資訊以及微控制器資訊至少其中之一。In step S215, when the microcontroller 143 receives the above instruction, the central processing unit 141 is turned back on to obtain the node related information of the electronic device 140 through the microcontroller 143 during the reboot. The node related information includes at least one of processor information, network card information, memory information, hard disk information, node position, node height information, node setting information, node type information, firmware information, and microcontroller information.
上述處理器資訊包括處理器型號以及頻率。網路卡資訊包括頻寬(bandwidth)與MAC位址。記憶體資訊包括記憶體模組的數量及容量。硬碟資訊包括托架(carrier)編號、硬碟類型、硬碟容量、硬碟轉速(Revolution Per Minute，RPM)以及硬碟快取(cache)容量。節點位置包括機架編號、插槽編號以及節點編號。節點高度資訊以U為單位(1U=1.75英寸=44.45毫米)，通常有1U，2U，3U，4U，5U，7U幾種標準。節點置法資訊包括垂直放置或水平放置。節點類型資訊用以表示此節點屬於服務資源池(service pool)、計算資源池(computing pool)或是儲存資源池(storage pool)。韌體資訊包括系統韌體版本號。微控制器資訊包括微控制器的韌體版本號。The above processor information includes the processor model and frequency. Network card information includes bandwidth and MAC address. Memory information includes the number and capacity of memory modules. Hard disk information includes carrier number, hard disk type, hard disk capacity, Revolution Per Minute (RPM), and hard disk cache capacity. The node location includes the rack number, slot number, and node number. Node height information is in U (1U = 1.75 inches = 44.45 mm), usually 1U, 2U, 3U, 4U, 5U, 7U standards. Node-based information includes vertical placement or horizontal placement. The node type information is used to indicate that the node belongs to a service resource pool, a computing resource pool, or a storage pool. The firmware information includes the system firmware version number. The microcontroller information includes the firmware version number of the microcontroller.
而上述處理器資訊、網路卡資訊、記憶體資訊、硬碟資訊以及節點位置為動態取得。也就是說，在執行開機自我測試(Power On Test Self，POST)時由韌體去取得。在此，韌體例如為基本輸入輸出系統(Basic Input Output System，BIOS)。而節點高度資訊、節點置法資訊、節點類型資訊以及韌體資訊為靜態資料，例如寫在SMBIOS(System Management BIOS)結構裡面，亦是透過BIOS去取得。另外，微控制器資訊為靜態資料，儲存在微控制器143中，其則是透過微控制器143去取得。The above processor information, network card information, memory information, hard disk information, and node location are dynamically obtained. In other words, it is obtained by the firmware when performing Power On Test Self (POST). Here, the firmware is, for example, a Basic Input Output System (BIOS). Node height information, node-based information, node type information, and firmware information are static data, such as written in the SMBIOS (System Management BIOS) structure, which is also obtained through the BIOS. In addition, the microcontroller information is static data, which is stored in the microcontroller 143, which is obtained through the microcontroller 143.
詳細地說，將中央處理單元141重新開機至一指令介面殼層(shell)。在此，指令介面殼層例如為可延伸韌體介面(Extensible Firmware Interface，EFI)殼層，其是一種用來啟動應用程式、載入EFI協定與裝置驅動程式以及執行簡易程式碼的主控台介面。據此，便可在BIOS執行開機自我測試時，由BIOS動態取得上述節點相關資訊中的動態資訊，並且透過SMBIOS取得節點相關資訊中的靜態資訊，再傳送至微控制器143。In detail, the central processing unit 141 is rebooted to an instruction interface shell. Here, the command interface shell is, for example, an Extensible Firmware Interface (EFI) shell, which is a console for launching an application, loading EFI protocols and device drivers, and executing simple code. interface. According to this, when the BIOS performs the boot self-test, the BIOS dynamically obtains the dynamic information in the node-related information, and obtains the static information in the node-related information through the SMBIOS, and then transmits the static information to the microcontroller 143.
之後，在步驟S220中，微控制器143回應上述指令，而傳送節點相關資訊至管理伺服器110。據此，管理伺服器110便能夠依據節點相關資訊來管理電子裝置140。Thereafter, in step S220, the microcontroller 143 responds to the above command and transmits node related information to the management server 110. Accordingly, the management server 110 can manage the electronic device 140 in accordance with the node related information.
而其他節點130_2~節點130_N的節點相關資訊的取得方法與上述相同。也就是說，管理伺服器110會依據各節點的微控制器的硬體位址來分配一網路位址。之後，依據此網路位址下達一IPMI OEM指令，使得各節點的電子裝置開機至EFI殼層，以在開機至EFI殼層的途中，透過例如BIOS之類的韌體來取得節點相關資訊而傳送給微控制器。之後，微控制器再將各節點的節點相關資訊傳送給管理伺服器110。The method for obtaining the node related information of the other nodes 130_2 to 130_N is the same as described above. That is to say, the management server 110 allocates a network address according to the hardware address of the microcontroller of each node. After that, an IPMI OEM command is issued according to the network address, so that the electronic devices of each node are booted to the EFI shell to obtain node-related information through firmware such as BIOS on the way to booting to the EFI shell. Transfer to the microcontroller. Thereafter, the microcontroller transmits node-related information of each node to the management server 110.
圖3是依照本發明第二實施例的管理系統架構的方塊圖。在本實施例中，列舉10個節點來說明。請參照圖3，在管理系統300中，透過管理伺服器310來管理機櫃320。機櫃320包括交換機321、機架323以及機架325。機架323及機架325的機架編號分別為0與1。3 is a block diagram of a management system architecture in accordance with a second embodiment of the present invention. In the present embodiment, ten nodes are listed for explanation. Referring to FIG. 3, in the management system 300, the cabinet 320 is managed by the management server 310. The cabinet 320 includes a switch 321, a rack 323, and a rack 325. The rack numbers of the rack 323 and the rack 325 are 0 and 1, respectively.
機架323包括插槽330，其具有節點331與節點333；插槽340，其具有節點341與節點343；插槽350，其具有節點351與節點353；以及插槽360，其具有節點361。上述插槽330、340、350及360的插槽編號分別為0~3。機架325包括插槽370，其具有節點371與節點373；以及插槽380，其具有節點381。Rack 323 includes slot 330 having node 331 and node 333; slot 340 having node 341 and node 343; slot 350 having node 351 and node 353; and slot 360 having node 361. The slot numbers of the slots 330, 340, 350, and 360 are 0 to 3, respectively. Rack 325 includes a slot 370 having a node 371 and a node 373; and a slot 380 having a node 381.
上述每一節點中分別設置有一電子裝置。而交換機321耦接至各個電子裝置，例如耦接至各個電子裝置的系統網卡，或是耦接至各個電子裝置的微控制器的網卡。An electronic device is disposed in each of the above nodes. The switch 321 is coupled to each electronic device, such as a system network card coupled to each electronic device, or a network card coupled to a microcontroller of each electronic device.
底下即舉例來說明電子裝置的各構件。圖4是依照本發明第二實施例的電子裝置的方塊圖。在本實施例中，微控制器例如為基板管理控制器(以下簡稱BMC)、韌體晶片例如為儲存BIOS的BIOS晶片。The components of the electronic device are exemplified below. 4 is a block diagram of an electronic device in accordance with a second embodiment of the present invention. In this embodiment, the microcontroller is, for example, a substrate management controller (hereinafter referred to as BMC), and the firmware chip is, for example, a BIOS chip that stores a BIOS.
請參照圖4，在此假設電子裝置400設置在節點331中。電子裝置400包括中央處理單元410、控制晶片420、BIOS晶片430、BMC 440、記憶體模組450、節點編號模組460以及系統網卡470。BMC 440還包括BMC網卡441以及一儲存空間442。儲存空間442例如為非揮發性隨機存取記憶體(Non-Volatile Random Access Memory，NVRAM)。其中，中央處理單元410耦接至記憶體模組450並且透過控制晶片420耦接至BIOS晶片430、BMC 440、節點編號模組460以及系統網卡470。在此，請同時參照圖3及圖4，交換機321耦接至系統網卡470及BMC網卡441。Referring to FIG. 4, it is assumed here that the electronic device 400 is disposed in the node 331. The electronic device 400 includes a central processing unit 410, a control chip 420, a BIOS chip 430, a BMC 440, a memory module 450, a node number module 460, and a system network card 470. The BMC 440 also includes a BMC network card 441 and a storage space 442. The storage space 442 is, for example, a Non-Volatile Random Access Memory (NVRAM). The central processing unit 410 is coupled to the memory module 450 and coupled to the BIOS chip 430, the BMC 440, the node number module 460, and the system network card 470 through the control chip 420. Here, please refer to FIG. 3 and FIG. 4 at the same time, the switch 321 is coupled to the system network card 470 and the BMC network card 441.
中央處理單元410用以執行電子裝置400中的硬體、韌體以及處理軟體中的資料。控制晶片420為中央處理單元410對外訊息交換的橋梁。在本實施例中，控制晶片420包括北橋晶片與南橋晶片。而在其他實施例中，控制晶片420例如為南橋晶片，而北橋晶片可與中央處理單元410互相整合。The central processing unit 410 is configured to execute data in the hardware, the firmware, and the processing software in the electronic device 400. Control chip 420 is a bridge for external processing of central processing unit 410. In the present embodiment, the control wafer 420 includes a north bridge wafer and a south bridge wafer. In other embodiments, the control wafer 420 is, for example, a south bridge wafer, and the north bridge wafer can be integrated with the central processing unit 410.
而記憶體模組450例如為雙列記憶體模組(Dual In-line Memory Module，DIMM)。節點編號模組460用以儲存電子裝置400所在的節點編號。另外，在控制晶片420中設置了暫存器來儲存機架編號、插槽編號以及節點編號。例如，設置三個暫存器來儲存。而BIOS或BMC 440便可自控制晶片420來取得電子裝置400在機櫃中的節點位置。The memory module 450 is, for example, a dual in-line memory module (DIMM). The node number module 460 is used to store the node number where the electronic device 400 is located. In addition, a register is provided in the control wafer 420 to store the rack number, the slot number, and the node number. For example, set up three scratchpads to store. The BIOS or BMC 440 can control the wafer 420 from the control chip 420 to obtain the node position of the electronic device 400 in the cabinet.
底下再舉一例來說明如何取得節點位置。圖5是依照本發明第二實施例的機架架構的方塊圖。在本實施例中，以上述管理系統300的機架323為例。請參照圖5，機架323中包括機架編號模組510，用以儲存機架編號。在本實施例中，機架編號模組510中儲存的機架編號為0。Let's take another example to show how to get the node location. Figure 5 is a block diagram of a rack architecture in accordance with a second embodiment of the present invention. In the embodiment, the rack 323 of the management system 300 is taken as an example. Referring to FIG. 5, the rack 323 includes a rack number module 510 for storing the rack number. In this embodiment, the rack number stored in the rack number module 510 is 0.
插槽330中包括擴展器(expander)520以及插槽編號模組530。而在節點331中設置有電子裝置400，在節點333中設置有電子裝置550。在此，僅繪示出電子裝置400的部分構件，而電子裝置550的構件與電子裝置400相似，並且為了方便說明，亦僅繪示出部分構件。The slot 330 includes an expander 520 and a slot number module 530. The electronic device 400 is provided in the node 331 and the electronic device 550 is provided in the node 333. Here, only some of the components of the electronic device 400 are illustrated, and the components of the electronic device 550 are similar to the electronic device 400, and only some of the components are illustrated for convenience of explanation.
在插槽330中，擴展器520耦接至機架編號模組510、插槽編號模組530、電子裝置400的控制晶片420以及電子裝置550的控制晶片551。在節點331中，電子裝置400的控制晶片420透過擴展器520取得電子裝置400所在的機架編號0與插槽編號0，並且，由節點編號模組460得知其所在的節點編號為0。另外，在節點333中，電子裝置550的控制晶片551亦透過擴展器520取得電子裝置550所在的機架編號0與插槽編號0，並且，由節點編號模組553得知其所在的節點編號為1。In the slot 330, the expander 520 is coupled to the rack number module 510, the slot number module 530, the control chip 420 of the electronic device 400, and the control chip 551 of the electronic device 550. In the node 331, the control chip 420 of the electronic device 400 acquires the rack number 0 and the slot number 0 where the electronic device 400 is located through the expander 520, and the node number module 460 knows that the node number where it is located is 0. In addition, in the node 333, the control chip 551 of the electronic device 550 also obtains the rack number 0 and the slot number 0 where the electronic device 550 is located through the expander 520, and the node number of the node number 553 is known by the node number module 553. Is 1.
假設以(r,s,n)來表示節點位置，r代表機架編號，s代表插槽編號，n代表節點編號。據此，電子裝置400的節點位置即為(0,0,0)，而電子裝置550的節點位置即為(0,0,1)。以此類推，設置在各個節點中的電子裝置的控制晶片的暫存器中便儲存有節點位置，使得BIOS或BMC得以去取得節點位置。據此，每一個電子裝置中利用其控制晶片，再搭配擴展器520，便可以獲得每一個電子裝置的節點位置，也就是在機櫃中的實體位置。Assume that the node position is represented by (r, s, n), r represents the rack number, s represents the slot number, and n represents the node number. Accordingly, the node position of the electronic device 400 is (0, 0, 0), and the node position of the electronic device 550 is (0, 0, 1). By analogy, the node location is stored in the register of the control chip of the electronic device disposed in each node, so that the BIOS or BMC can obtain the node location. Accordingly, each of the electronic devices utilizes its control chip, and in conjunction with the expander 520, the node position of each electronic device, that is, the physical position in the cabinet, can be obtained.
在此，擴展器520例如是透過通用輸入(General Purpose Input，GPI)接口耦接至機架編號模組510與插槽編號模組530，並且透過內部整合電路(Inter-Integrated Circuit，I2C)匯流排耦接至電子裝置400的控制晶片420以及電子裝置550的控制晶片551。另外，控制晶片420與控制晶片551例如亦是透過GPI接口分別耦接至節點編號模組460與節點編號模組553。也就是說，可透過GPI接口來取得機架編號模組510、插槽編號模組530、節點編號模組460以及節點編號模組553中的編號。Here, the expander 520 is coupled to the rack number module 510 and the slot number module 530 via a General Purpose Input (GPI) interface, and through an internal integrated circuit (Inter-Integrated Circuit, I 2 C). The bus bar is coupled to the control wafer 420 of the electronic device 400 and the control wafer 551 of the electronic device 550. In addition, the control chip 420 and the control chip 551 are also coupled to the node number module 460 and the node number module 553 via the GPI interface, for example. That is to say, the numbers in the rack number module 510, the slot number module 530, the node number module 460, and the node number module 553 can be obtained through the GPI interface.
底下再進一步來說明管理雲端伺服系統的各步驟。圖6是依照本發明第二實施例的雲端伺服系統的管理方法流程圖。請同時參照圖3、圖4及圖6，在本實施例中，假設機櫃320中的各個節點皆設置有電子裝置400。Further steps to manage the cloud servo system are described below. 6 is a flow chart of a method for managing a cloud server system according to a second embodiment of the present invention. Referring to FIG. 3, FIG. 4 and FIG. 6, in the embodiment, it is assumed that each node in the cabinet 320 is provided with an electronic device 400.
在步驟S605中，判斷機櫃320的電源是否關閉。若未關閉，執行步驟S610，將機櫃320的電源關閉，再執行步驟S615，開啟電源。而倘若電源已關閉，則執行步驟S615。開啟電源，使得所有節點的BMC 440重新啟動。斷電再復電的目的是為了讓BMC 440重新執行其初始程式碼而送出MAC位址。也就是說，BMC 440在斷電再復電之後會廣播其BMC網卡441的MAC位址出去。In step S605, it is determined whether the power of the cabinet 320 is turned off. If it is not closed, step S610 is executed to turn off the power of the cabinet 320, and then step S615 is performed to turn on the power. And if the power is off, step S615 is performed. Turn on the power and restart the BMC 440 of all nodes. The purpose of powering down and re-powering is to have the BMC 440 re-execute its initial code and send the MAC address. That is to say, the BMC 440 broadcasts the MAC address of its BMC network card 441 after power-off and power-on.
接著，在步驟S620中，管理伺服器310自電子裝置400接收到BMC 440的MAC位址，便會分配IP位址給此MAC位址。並且，管理伺服器310亦會將MAC位址與其對應的IP位址記錄下來。Next, in step S620, the management server 310 receives the MAC address of the BMC 440 from the electronic device 400, and assigns an IP address to the MAC address. Moreover, the management server 310 also records the MAC address and its corresponding IP address.
舉例來說，圖7A是依照本發明第二實施例的MAC位址表格的示意圖。圖7B是依照本發明第二實施例的MAC位址與IP位址表格的示意圖。本實施例是以圖3的10個節點為例。也就是說，圖7A的表格710所記錄為節點331、333、341、343、351、353、361、371、373、381所傳送的MAC位址。另外，當管理伺服器310在分別指派一IP位址給各MAC位址之後，便將其記錄在圖7B的表格720中。For example, FIG. 7A is a schematic diagram of a MAC address table in accordance with a second embodiment of the present invention. 7B is a schematic diagram of a MAC address and an IP address table in accordance with a second embodiment of the present invention. This embodiment takes the 10 nodes of FIG. 3 as an example. That is, the table 710 of FIG. 7A records the MAC addresses transmitted by the nodes 331, 333, 341, 343, 351, 353, 361, 371, 373, 381. In addition, when the management server 310 assigns an IP address to each MAC address, it is recorded in the table 720 of FIG. 7B.
返回圖6，在指派IP位址之後，在步驟S625中，管理伺服器310便可依據IP位址傳送指令(例如為IPMI OEM指令)給BMC 440，以要求BMC 440去取得節點相關資訊。之後，步驟S630中，當BMC 440在接收到指令時，BMC 440會將中央處理單元410重新開機到EFI殼層。據此，在重新開機到EFI殼層的過程中，便可執行步驟S635~步驟S645。在步驟S635中，透過BIOS取得節點相關資訊中的動態資訊。動態資訊包括處理器資訊、網路卡資訊(系統網卡470的MAC位址)、記憶體資訊、硬碟資訊以及節點位置。值得注意的是，節點位置亦可由BMC 440自控制晶片420的暫存器來取得，而節點位置的取得方法請參照圖5。Returning to Figure 6, after assigning the IP address, in step S625, the management server 310 can transmit an instruction (e.g., an IPMI OEM instruction) to the BMC 440 in accordance with the IP address to request the BMC 440 to obtain node related information. Thereafter, in step S630, when the BMC 440 receives the instruction, the BMC 440 will reboot the central processing unit 410 to the EFI shell. Accordingly, in the process of rebooting to the EFI shell, steps S635 to S645 can be performed. In step S635, the dynamic information in the node related information is obtained through the BIOS. Dynamic information includes processor information, network card information (MAC address of system network card 470), memory information, hard disk information, and node location. It should be noted that the node position can also be obtained by the BMC 440 from the register of the control chip 420, and the method of obtaining the node position is shown in FIG. 5.
另外，在步驟S640中，透過SMBIOS結構取得節點相關資訊中的靜態資訊，包括節點高度資訊、節點置法資訊、節點類型資訊以及韌體資訊。In addition, in step S640, the static information in the node related information is obtained through the SMBIOS structure, including node height information, node setting information, node type information, and firmware information.
然後，在步驟S645中，BIOS將節點相關資訊傳送給BMC 440。例如，傳送至BMC 440的儲存空間442。另外，BMC 440亦可取得其自身的BMC資訊(如BMC韌體版本號、BMC網卡441的頻寬)。之後，在步驟S650中，BMC 440回應上述指令，而將節點相關資訊傳送至管理伺服器310。管理伺服器310會針對所得到之節點相關資訊之系統網卡470的MAC位址配置其IP位址，當然於雲端作業系統安裝(Cloud OS deployment)時，系統網卡470透過網路啟動(Network Boot)其才會得到此IP位址，再者，雲端作業系統安裝是透過網路啟動機制來達成。Then, in step S645, the BIOS transmits the node related information to the BMC 440. For example, it is transferred to the storage space 442 of the BMC 440. In addition, the BMC 440 can also obtain its own BMC information (such as the BMC firmware version number and the bandwidth of the BMC network card 441). Thereafter, in step S650, the BMC 440 responds to the above instruction and transmits the node related information to the management server 310. The management server 310 configures its IP address for the MAC address of the system network card 470 of the obtained node related information. Of course, when the cloud OS deployment is performed, the system network card 470 is booted through the network (Network Boot). It will get this IP address. Furthermore, the cloud operating system installation is achieved through the network boot mechanism.
圖8A及圖8B是依照本發明第二實施例的節點相關資訊表格的示意圖。當管理伺服器310接收到雲端伺服系統320中各個節點的節點相關資訊，便將其記錄在圖8A及圖8B的表格800中。其中，圖8A記錄六筆節點相關資訊，8B記錄另四筆節點相關資訊。在此，假設表格800所記錄的10筆節點相關資訊分別取自圖3的節點331、333、341、343、351、353、361、371、373、381。表格800包括9個欄位，分別記錄BMC網卡的MAC位址、BMC網卡的IP位址及頻寬、系統網卡的MAC位址、系統網卡的IP位址及頻寬、處理器資訊、記憶體資訊、硬碟資訊、節點位置以及節點類型資訊。8A and 8B are schematic diagrams of a node related information table in accordance with a second embodiment of the present invention. When the management server 310 receives the node related information of each node in the cloud servo system 320, it is recorded in the table 800 of FIGS. 8A and 8B. Among them, Figure 8A records the information about the six-node node, and 8B records the information about the other four nodes. Here, it is assumed that the ten pieces of node related information recorded in the table 800 are taken from the nodes 331, 333, 341, 343, 351, 353, 361, 371, 373, 381 of FIG. 3, respectively. The table 800 includes nine fields, respectively recording the MAC address of the BMC network card, the IP address and bandwidth of the BMC network card, the MAC address of the system network card, the IP address and bandwidth of the system network card, processor information, and memory. Information, hard drive information, node location, and node type information.
以節點331的節點相關資訊而言，並且假設圖4的電子裝置400設置在節點331中，BMC網卡441的MAC位址為“00:A0:D1:EC:F8:B1”，所分配到的BMC網卡441的IP位址為“10.1.0.1”，且BMC網卡441的頻寬為100Mbps(bps=bits per second)。而節點331的系統網卡470的MAC位址為“00:A0:D1:EA:34:E1”、IP位址為“10.1.0.11”以及頻寬為1000Mbps。另外，節點331的中央處理單元410的型號為“Intel(R) Xeon(R) CPU E5540”，其頻率為“2530MHz”。而節點331包括4個記憶體模組450，DIMM1~DIMM4，且每一個記憶體模組450的容量皆為8G。此外，節點331的硬碟的托架(carrier)編號為1、硬碟類型為SAS(Serial Attached SCSI，SCSI=Small Computer System Interface)、硬碟容量為1TB、硬碟轉速為7200 RPM(Revolution Per Minute)以及硬碟快取(cache)容量為16MB。In terms of the node related information of the node 331 and assuming that the electronic device 400 of FIG. 4 is disposed in the node 331, the MAC address of the BMC network card 441 is "00: A0: D1: EC: F8: B1", which is assigned The IP address of the BMC network card 441 is "10.1.0.1", and the bandwidth of the BMC network card 441 is 100 Mbps (bps=bits per second). The system NIC 470 of the node 331 has a MAC address of "00: A0: D1: EA: 34: E1", an IP address of "10.1.0.11", and a bandwidth of 1000 Mbps. In addition, the model of the central processing unit 410 of the node 331 is "Intel(R) Xeon(R) CPU E5540", and its frequency is "2530 MHz". The node 331 includes four memory modules 450, DIMM1~DIMM4, and each of the memory modules 450 has a capacity of 8G. In addition, the carrier number of the hard disk of the node 331 is 1, the hard disk type is SAS (Serial Attached SCSI, SCSI = Small Computer System Interface), the hard disk capacity is 1 TB, and the hard disk rotation speed is 7200 RPM (Revolution Per Minute) and the hard disk cache capacity is 16MB.
值得注意的是，管理伺服器310還可依據節點相關資訊得知各個電子裝置位於雲端伺服系統320中的節點位置，藉以獲得各個電子裝置於雲端伺服系統中的位置順序。並且，依據位置順序，來重新分配BMC網卡以及系統網卡的網路位址。It should be noted that the management server 310 can also learn the location of each electronic device in the cloud servo system 320 according to the node related information, so as to obtain the position sequence of each electronic device in the cloud servo system. And, according to the location order, redistribute the BMC network card and the network address of the system network card.
舉例來說，圖9A及圖9B是依照本發明第二實施例的重新分配網路位址後的節點相關資訊表格的示意圖。請參照圖9A及圖9B，其是以圖8A及圖8B重新分配BMC網卡以及系統網卡的IP位址所獲得之。For example, FIG. 9A and FIG. 9B are schematic diagrams of a node related information table after reallocating a network address according to a second embodiment of the present invention. Please refer to FIG. 9A and FIG. 9B, which are obtained by reassigning the BMC network card and the IP address of the system network card in FIG. 8A and FIG. 8B.
另外，管理伺服器310還可依據節點相關資訊來決定每一個電子裝置所欲部署的服務，並且將節點相關資訊傳送至雲端部署程序，以進行雲端作業系統的部署。In addition, the management server 310 can also determine the service to be deployed by each electronic device according to the node related information, and transmit the node related information to the cloud deployment program for deployment of the cloud operating system.
舉例來說，在決定所欲部署的服務之後，可在節點資訊相關表格中新增一欄位來記錄相對應的服務類型，如圖10所示。圖10是依照本發明第二實施例的決定部署的服務類型後的節點相關資訊表格的示意圖。請參照圖10，圖10為在決定部署的服務類型後，可於圖9A及圖9B的表格中新增一欄位所獲得之。在此僅繪示出部分欄位來說明之。其中，節點331、333、341、343、351、353是用來作為服務資源池。節點331的服務類型為實體安裝(physical installer)、實體管理(physical manager)以及記錄管理(LOG)。節點333的服務類型為虛擬管理(Virtual Manager)以及應用程式介面(Application Programming Interface，API)。節點341的服務類型為虛擬資源供應(virtual resource provisioning)。節點343的服務類型為資料庫。節點351的服務類型為儲存管理(storage manager)。而節點353的服務類型為負載平衡(load balance)以及安全機制(security)。For example, after deciding which service to deploy, a new field can be added to the node information related table to record the corresponding service type, as shown in FIG. FIG. 10 is a schematic diagram of a node related information table after determining a deployed service type according to a second embodiment of the present invention. Please refer to FIG. 10. FIG. 10 is obtained by adding a field in the table of FIG. 9A and FIG. 9B after deciding the type of service to be deployed. Only some of the fields are shown here to illustrate. Among them, the nodes 331, 333, 341, 343, 351, and 353 are used as a service resource pool. The service types of the node 331 are a physical installer, a physical manager, and a record management (LOG). The service type of the node 333 is virtual management (Virtual Manager) and an application programming interface (API). The service type of node 341 is virtual resource provisioning. The service type of node 343 is a database. The service type of the node 351 is a storage manager. The service type of node 353 is load balance and security.
綜上所述，本發明透過設置在各個節點中之電子裝置的微控制器來取得電子裝置的節點相關資訊，並傳送回管理伺服器，藉此便能夠自動找出機櫃上每一個節點的節點相關資訊，以便能將雲端作業系統自動部署至此機櫃。In summary, the present invention acquires node-related information of an electronic device through a microcontroller of an electronic device disposed in each node, and transmits the information to the management server, thereby automatically finding a node of each node on the cabinet. Relevant information so that the cloud operating system can be automatically deployed to this cabinet.
雖然本發明已以實施例揭露如上，然其並非用以限定本發明，任何所屬技術領域中具有通常知識者，在不脫離本發明之精神和範圍內，當可作些許之更動與潤飾，故本發明之保護範圍當視後附之申請專利範圍所界定者為準。Although the present invention has been disclosed in the above embodiments, it is not intended to limit the invention, and any one of ordinary skill in the art can make some modifications and refinements without departing from the spirit and scope of the invention. The scope of the invention is defined by the scope of the appended claims.
100、300．．．管理系統100, 300. . . Management system
110、310．．．管理伺服器110, 310. . . Management server
120．．．雲端伺服器系統120. . . Cloud server system
130_1~130_N、331、333、341、343、351、353、361、371、373、381．．．節點130_1~130_N, 331, 333, 341, 343, 351, 353, 361, 371, 373, 381. . . node
140、400、550．．．電子裝置140, 400, 550. . . Electronic device
141、410．．．中央處理單元141, 410. . . Central processing unit
143．．．微控制器143. . . Microcontroller
320．．．機櫃320. . . Cabinet
321．．．交換機321. . . switch
323、325．．．機架323, 325. . . frame
330、340、350、360、370、380．．．插槽330, 340, 350, 360, 370, 380. . . Slot
420、551．．．控制晶片420, 551. . . Control chip
430．．．BIOS晶片430. . . BIOS chip
440．．．BMC440. . . BMC
441．．．BMC網卡441. . . BMC network card
442．．．儲存空間442. . . storage space
450．．．記憶體模組450. . . Memory module
460、553．．．節點編號模組460, 553. . . Node number module
470．．．系統網卡470. . . System NIC
510．．．機架編號模組510. . . Rack number module
520．．．擴展器520. . . Expander
530．．．插槽編號模組530. . . Slot number module
710、720、800．．．表格710, 720, 800. . . form
S205~S220．．．本發明第一實施例管理方法各步驟S205~S220. . . Each step of the management method of the first embodiment of the present invention
S605~S650．．．本發明第二實施例管理方法各步驟S605~S650. . . Steps of the management method of the second embodiment of the present invention
圖1是依照本發明第一實施例的管理系統的方塊圖。1 is a block diagram of a management system in accordance with a first embodiment of the present invention.
圖2是依照本發明第一實施例的雲端伺服系統的管理方法流程圖。2 is a flow chart of a method for managing a cloud server system according to a first embodiment of the present invention.
圖3是依照本發明第二實施例的管理系統架構的方塊圖。3 is a block diagram of a management system architecture in accordance with a second embodiment of the present invention.
圖4是依照本發明第二實施例的電子裝置的方塊圖。4 is a block diagram of an electronic device in accordance with a second embodiment of the present invention.
圖5是依照本發明第二實施例的機架架構的方塊圖。Figure 5 is a block diagram of a rack architecture in accordance with a second embodiment of the present invention.
圖6是依照本發明第二實施例的雲端伺服系統的管理方法流程圖。6 is a flow chart of a method for managing a cloud server system according to a second embodiment of the present invention.
圖7A是依照本發明第二實施例的MAC位址表格的示意圖。7A is a schematic diagram of a MAC address table in accordance with a second embodiment of the present invention.
圖7B是依照本發明第二實施例的MAC位址與IP位址表格的示意圖。7B is a schematic diagram of a MAC address and an IP address table in accordance with a second embodiment of the present invention.
圖8A及圖8B是依照本發明第二實施例的節點相關資訊表格的示意圖。8A and 8B are schematic diagrams of a node related information table in accordance with a second embodiment of the present invention.
圖9A及圖9B是依照本發明第二實施例的重新分配網路位址後的節點相關資訊表格的示意圖。9A and 9B are diagrams showing a node related information table after reallocating a network address according to a second embodiment of the present invention.
圖10是依照本發明第二實施例的決定部署的服務類型後的節點相關資訊表格的示意圖。FIG. 10 is a schematic diagram of a node related information table after determining a deployed service type according to a second embodiment of the present invention.
S205~S220．．．本發明第一實施例管理方法各步驟S205~S220. . . Each step of the management method of the first embodiment of the present invention
Claims (10)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| TW100147603A TW201328246A (en) | 2011-12-21 | 2011-12-21 | Method and system for managing cloud server system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| TW100147603A TW201328246A (en) | 2011-12-21 | 2011-12-21 | Method and system for managing cloud server system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| TW201328246A true TW201328246A (en) | 2013-07-01 |
Family
ID=49225342
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| TW100147603A TW201328246A (en) | 2011-12-21 | 2011-12-21 | Method and system for managing cloud server system |
Country Status (1)
| Country | Link |
|---|---|
| TW (1) | TW201328246A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TWI499918B (en) * | 2014-05-21 | 2015-09-11 | Nat Univ Tsing Hua | Cloud management systems and methods for executing applications of android systems |
| TWI582612B (en) * | 2013-09-24 | 2017-05-11 | 慧與發展有限責任合夥企業 | Slot based management controller address |
| TWI665604B (en) * | 2018-02-27 | 2019-07-11 | 其陽科技股份有限公司 | Computer system and method with credible verification and fault tolerant transfer of boot-up |
-
2011
- 2011-12-21 TW TW100147603A patent/TW201328246A/en unknown
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TWI582612B (en) * | 2013-09-24 | 2017-05-11 | 慧與發展有限責任合夥企業 | Slot based management controller address |
| US10067902B2 (en) | 2013-09-24 | 2018-09-04 | Hewlett Packard Enterprise Development Lp | Slot based management controller address |
| TWI499918B (en) * | 2014-05-21 | 2015-09-11 | Nat Univ Tsing Hua | Cloud management systems and methods for executing applications of android systems |
| TWI665604B (en) * | 2018-02-27 | 2019-07-11 | 其陽科技股份有限公司 | Computer system and method with credible verification and fault tolerant transfer of boot-up |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7467295B2 (en) | Determining a boot image based on a requesting client address | |
| WO2021253854A1 (en) | Method and apparatus for remotely updating firmware in batches, and computer-readable storage medium | |
| US20230004508A1 (en) | Managing a smart network interface controller (nic) of an information handling system | |
| US7895428B2 (en) | Applying firmware updates to servers in a data center | |
| US7953830B2 (en) | Automatic network reconfiguration upon changes in DHCP IP addresses | |
| US8141094B2 (en) | Distribution of resources for I/O virtualized (IOV) adapters and management of the adapters through an IOV management partition via user selection of compatible virtual functions | |
| US9531668B2 (en) | Micro server, method of allocating MAC address, and computer readable recording medium | |
| US8108667B2 (en) | System and method for configuring option ROM | |
| US20080294933A1 (en) | Fail-over method, computer system, management server, and backup server setting method | |
| US10372639B2 (en) | System and method to avoid SMBus address conflicts via a baseboard management controller | |
| US20090276773A1 (en) | Multi-Root I/O Virtualization Using Separate Management Facilities of Multiple Logical Partitions | |
| TW201729123A (en) | Method and server for remote launching deployment utility | |
| US8380971B2 (en) | Information handling systems including network adapters and methods of booting the information handling systems using boot configuration information from remote sources | |
| US20040193867A1 (en) | Configurabel network boot management for hetergenous boot options | |
| CN103188091A (en) | Management method of cloud service system and management system | |
| US9423958B2 (en) | System and method for managing expansion read-only memory and management host thereof | |
| US20190182110A1 (en) | Raid configuration | |
| US9537822B2 (en) | UEFI and operating system driver methods for updating MAC address in LAN-based NIC | |
| US20160371107A1 (en) | System and Method to Discover Virtual Machines from a Management Controller | |
| CN111857956A (en) | Virtual machine starting method and equipment | |
| US11144326B2 (en) | System and method of initiating multiple adaptors in parallel | |
| JP5876149B2 (en) | Computer system, method, server computer, management station and use for starting a server computer | |
| US11226755B1 (en) | Core dump in a storage device | |
| TW201328246A (en) | Method and system for managing cloud server system | |
| CN112328312A (en) | Method and equipment for realizing diskless startup of bare computer equipment |