| Section | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
What is Resource?
Resources are defined as hardware or software entities which are needed to provide application service. Ethernet adapter, IP Address, Process, Service, Storage, etc are resources and MCCS manage these to ensure service availability.
There are two categories of these, one is on-off resource, another is persistent resource. Most resources are normal which means MCCS online or offline them as their state. The other hands, a persistent resource cannot be brought online or taken offline, just only monitor them by MCCS.
Resource action is divided into regular resource(OnOff) and monitor resource(None).
Most of the resources are regular resources that goes Online or Offline according to the resource state.
Monitor resources are only able to monitor and does not go online or offline like regular resources.
For an instance, network interface card cannot be brought online or taken offline as its state. But it is essential resource to attach IP address on that.
Agents for each type of resource are in-charge of giving command and monitoring.
Resource Attribute
리소스 속성은 리소스가 동작을 취하거나 상태를 판단할 때 참조하는 값입니다.
Resource attribute can be identified from Resource Attributes view of MCCS web console. From the group management view of MCCS web console, select the resource, then select ‘Resource Attributes’ tab located on the top of detailed information panel.
The values of gray colored are read only. They just contain and show the information of resource state. The values of white colored are configurable by user definition. Below is description of some of them.
[Figure] Resource Attribute View
...
It is used when deciding whether to manage the resource.
Resource Enable : true
Resource Disable: false
...
리소스의 에이전트 상태를 나타냅니다.
사용자가 임의로 수정할 수 없으며, MCCS엔진에서 모든 노드의 에이전트 상태를 수집한 후에 나타냅니다.
...
BatchAfterOffline
...
| Section | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Resource Attribute
Resource attribute is a reference value used when the resource takes some actions or determines the status.
Resource attribute can be identified from Resource Attributes view of MCCS web console. From the group management view of MCCS web console, select the resource, then select ‘Resource Attributes’ tab located on the top of detailed information panel.
The values of gray colored are read only. They just contain and show the information of resource state. The values of white colored are configurable by user definition. Below is description of some of them.
[Figure] Resource Attribute View
| Attribute | Description | Type | Default | Edit | Note | |||
|---|---|---|---|---|---|---|---|---|
| Key Attribute | *Critical | When a failure occurs in the resource it indicated whether to failover the whole group. | BOOLEAN | X | ||||
| *Enabled | It is used when deciding whether to manage the resource. | BOOLEAN | X | |||||
| General Attribute | AgentState | It indicates the agent state of the resource. | STRING | X | ||||
*BatchAfterOffline | This is a batch command to be executed after a resource is taken offline. | FILE | O | |||||
*BatchAfterOnline | This is a batch command to be executed after a resource is brought online. | FILE | O | |||||
| *BatchBeforeOffline | This is a batch command to be executed before a resource is brought online. | FILE | O | |||||
| *BatchBeforeOnline | This is a batch command to be executed before a resource is taken offline. | FILE | O | |||||
| *BatchTimeout | It is the waiting time until execution of batch command completes. If execution result is over this time, it is considered as a failure. | INTEGER | 300sec | O | ||||
| CleanProgram | This program is executed to initialize related resources and state when a failure occurs to a resource. This program must be written separately. | FILE | O | BatchAfterOnline | 이 리소스를 시작한 후에 실행 할 배치 명령입니다. | FILE | ||
EnableTimeout | It is the waiting time until the execution of Enable completes. If the execution result is over this time, it is considered as a failure. (unit = second) | INTEGER | 60 sec | O | ||||
| BatchBeforeOffline | 이 리소스를 종료하기 전에 실행 할 배치 명령입니다. | FILE | O | |||||
| BatchBeforeOnline | 이 리소스를 시작하기 전에 실행 할 배치 명령입니다. | FILE | O | |||||
| BatchTimeout | 배치 파일을 실행하면 완료 될 때까지 대기하는 시간입니다. | INTEGER | 300초 | O | ||||
| *CleanProgram | 리소스에 장애가 발생하여 다른 노드로 페일오버 하기 전에 | FILE | O | |||||
| Failoverable | 리소스가 페일 오버 할 수 있는 상태인지를 알려줍니다. | BOOLEANFailoverable | It indicates whether the resource is in the state to be failover. | BOOLEAN | X | |||
| Group | It is the name of the group which the resource belongs | STRING | X | |||||
| LastOnline | It is name of the node on which state of the resource is online lastly. | STRING | ||||||
| Monitored | Depending on the 'MonitorTimeout', attribute values for the resource types, it record periodically whether each node's monitoring is finished. | BOOLEAN | X | |||||
| NoAction | It represents the action attribute of the resource. | BOOLEAN | X | |||||
| ResName | It is the name of the resource. | NAME | X | |||||
| *Group | 리소스가 속한 그룹입니다. | STRING | X | |||||
| LastOnline | 마지막으로 온라인이었던 노드명을 알려줍니다.Restartlimit | It shows the number to restart before failover when the resource is determined as a failure. | INTEGER | 0 | O | |||
| State | It is the resource state of each node. | STRING | X | *Monitored | ||||
리소스타입 속성값인 '모니터링 시간 제한'(MonitorTimeout) 설정값에 따라 | BOOLEANType | It is the name of the agent type of the resource. | STRING | X | ||||
*
...
리소스의 동작(Action) 속성을 나타냅니다.
이 속성이 true라면 리소스는 온라인, 오프라인 같은 명령을 내릴 수 없고
감시 기능만 가능한 모니터전용리소스 입니다. 네트워크 카드의 경우가 false 입니다.
...
리소스가 장애로 판단되었을 때,
페일 오버하기 전에 재시작 할 수 있는 횟수를 나타냅니다.
...
※ 위의 표에서 '네트워크카드 리소스' 는 ' * ' 표시 되어있는 속성값만 사용합니다.
*Critical
This attribute shows to failover (true) or not (false) when failure has occured.
Default is set as true, and most of the resources are set as a true value. For resources that is not as important or resources that cannot be failover are set as false.
Critical values affects failover mode group only, does not affect parallel mode group. Critical attribute can be considered alone but there are many things to be considered if it has linked dependency among resources.
For an example, none critical resource on which critical resource(parent) depends, group failover will be occurred because one of critical resource cannot be provide proper service.
*Enabled
It shows resources are enabled which can be monitored, online and offline as state.
A resource cannot be used right after it has been created, and it must be checked ‘enable’, when has been successful configured to be used.
Agent, a MCCS component is in detached state when create a resource for the first time. In this state, Resource and group is disabled which cannot be managed like online, offline, switch and etc.If you check 'enable' after completing the configuration, agent executes the probing stage in which flaws in the configuration are detected. If it is considered normally configured, both the resource and agent turn into offline state.
*BatchAfterOffline / BatchAfterOnline / BatchBeforeOnline / BatchBeforeOffline
It is used when there is additional command to be sent before the resource is online or after the resource is offline. Name of the user created batch or script file with path name is registered as value.
For an example, if an application that leads many child processes has gone offline by command, but child processes were not terminated normally. When this happens, a script file is needed to be used so that child processes can be all terminated.
This command does not affect group Online/Offline of MCCS. In other words, MCCS does the group online even though the command has failed. Only result of the command execution write in the log.
*BatchTimeout
BatchTimeout can be defined the timeout value of the result of batch execution.
It avoids a deadlock when exceptional situation occurs during the execution of scripts and other resources cannot be controlled.
If the script is not executed when offline or online attempts are made, stop further procedures and wait for the control of the administrator.
Resource State
[Figure] Resource State View
The resource state can be checked on resource state view of MCCS console.
From the group management view of MCCS console, select the resource and select ‘Resource Status’ tab from detailed information panel. The resource status will be shown.
Resource states are as below;
Online
Resource is running.
Offline
Resource has been stopped.
Fault
Resource has been failed.
Unknown
Resource is not being monitored since it is not enabled.
Resource Control
[Figure] Resource Control Menus
MCCS에서 리소스를 다루기 위한 명령은 관리 콘솔에서 왼쪽 뷰의 리소스를 선택한 후에 마우스의 오른쪽 클릭으로 생성된 팝업 화면에서 선택할 수 있습니다.
또 다른 곳은 그룹을 선택한 후에 '리소스 의존성' 탭에서 해당 리소스에 마우스의 오른쪽을 클릭하면 리소스와 같은 팝업 화면을 생성시킬 수 있습니다.
이 외에도 콘솔의 메뉴 항목이나 툴 바 메뉴에서 명령을 내릴 수 있으며 CLI 로도 가능합니다.
Enable Resource
This can be checked by checking of there is a enabled check mark in front of the command. This can also be checked by checking on the Enabled value in the Resource Attribute. If the resource is disabled, resource state cannot be monitored.
If the attribute value is incorrect, this will be failed. For example, when type a wrong path name in the process of application, monitoring whether it is online or offline is impossible. Therefore, whenever this is failed, attribute value should be checked first.
Group Failover for failure
This is about Critical attribute, and this can be checked through the check mark in front of this.
If this value is checked, that means when failure occurs, group will failover to the other node. This is not the case for the parallel group.
Probe Now
When an agent monitors the resource state, it probes that periodically. But when you use ‘Probe Now’, the agent probes the resource right away that this is ready to use. When you modify a value of resource attribute, this may not be applied right away. But you can verify this modification is applied by using this right away.
Online
You can bring a resource online by using this.
From here, there are sub menus per node so that nodes to be online can be selected. Sub menus can be 'Enabled' or 'Disabled' according to the resource state per node. For example, failover mode group cannot send enabled command when it is online in the temporary node. This is because failover mode group should only have one node online and if there is one node that is already online, online menu is not enabled. However, in case of parallel mode group, it is all enabled if it is not in an online state.
Failover mode group should only have one node online and so node that is online can start the Online command. When this is selected, you can choose appropriate node from the sub menu which shows nodes list. When the resource is already online state, all of the node icons will be disabled at failover mode group. But the node will be enabled which the resource isn’t online state at parallel mode group.
If there is a fault mark in the resource, in which that has been failed, it should be cleared first before sending the that is online. This is because MCCS regards cause of the fault is not identified yet.
There are some considerations for dependency as well. To online a resource, if there is a child resource, child resource should be online state first. Since there is a dependency, if the child resource is not online state, parent resource cannot be online as well. When the child resource exists, you should check that is online state before the resource bring online.
Offline
You can take a resource offline by using this.
Similar to Online, you can choose appropriate node from the sub menu.
One thing that has to be careful when offline is when there is a parent resourceCritical
This attribute shows to failover (true) or not (false) when failure has occured.
Default is set as true, and most of the resources are set as a true value. For resources that is not as important or resources that cannot be failover are set as false.
Critical values affects failover mode group only, does not affect parallel mode group. Critical attribute can be considered alone but there are many things to be considered if it has linked dependency among resources.
For an example, none critical resource on which critical resource(parent) depends, group failover will be occurred because one of critical resource cannot be provide proper service.
*Enabled
It shows resources are enabled which can be monitored, online and offline as state.
A resource cannot be used right after it has been created, and it must be checked ‘enable’, when has been successful configured to be used.
Agent, a MCCS component is in detached state when create a resource for the first time. In this state, Resource and group is disabled which cannot be managed like online, offline, switch and etc.
If you check 'enable' after completing the configuration, agent executes the probing stage in which flaws in the configuration are detected. If it is considered normally configured, both the resource and agent turn into offline state.
*BatchAfterOffline / BatchAfterOnline / BatchBeforeOnline / BatchBeforeOffline
It is used when there is additional command to be sent before the resource is online or after the resource is offline. Name of the user created batch or script file with path name is registered as value.
For an example, if an application that leads many child processes has gone offline by command, but child processes were not terminated normally. When this happens, a script file is needed to be used so that child processes can be all terminated.
This command does not affect group Online/Offline of MCCS. In other words, MCCS does the group online even though the command has failed. Only result of the command execution write in the log.
*BatchTimeout
BatchTimeout can be defined the timeout value of the result of batch execution.
It avoids a deadlock when exceptional situation occurs during the execution of scripts and other resources cannot be controlled.
If the script is not executed when offline or online attempts are made, stop further procedures and wait for the control of the administrator.
Resource State
[Figure] Resource State View
The resource state can be checked on resource state view of MCCS console.
From the group management view of MCCS console, select the resource and select ‘Resource Status’ tab from detailed information panel. The resource status will be shown.
Resource states are as below;
Online
Resource is running.
Offline
Resource has been stopped.
Fault
Resource has been failed.
Unknown
Resource is not being monitored since it is not enabled.
Resource Control
[Figure] Resource Control Menus
If you want to use the resource handling commands in MCCS, go to the management console and select the resource in the left view and right click with your mouse button to launch the pop up window.
Alternatively, select group and right click with your mouse button on the resource in the 'Resource Dependency' tab to launch the same pop up as resource.
Also, you can use the commands in the console menu or tool bar. CLI can be used as well.
Enable Resource
This can be checked by checking of there is a enabled check mark in front of the command. This can also be checked by checking on the Enabled value in the Resource Attribute. If the resource is disabled, resource state cannot be monitored.
If the attribute value is incorrect, this will be failed. For example, when type a wrong path name in the process of application, monitoring whether it is online or offline is impossible. Therefore, whenever this is failed, attribute value should be checked first.
Group Failover for failure
This is about Critical attribute, and this can be checked through the check mark in front of this.
If this value is checked, that means when failure occurs, group will failover to the other node. This is not the case for the parallel group.
Probe Now
When an agent monitors the resource state, it probes that periodically.
But when you use ‘Probe Now’, the agent probes the resource right away that this is ready to use. When you modify a value of resource attribute, this may not be applied right away.
But you can verify this modification is applied by using this right away.
Online
You can bring a resource online by using this.
From here, there are sub menus per node so that nodes to be online can be selected. Sub menus can be 'Enabled' or 'Disabled' according to the resource state per node.
For example, failover mode group cannot send enabled command when it is online in the temporary node. This is because failover mode group should only have one node online and if there is one node that is already online, online menu is not enabled.
However, in case of parallel mode group, it is all enabled if it is not in an online state.
Failover mode group should only have one node online and so node that is online can start the Online command.
When this is selected, you can choose appropriate node from the sub menu which shows nodes list. When the resource is already online state, all of the node icons will be disabled at failover mode group.
But the node will be enabled which the resource isn’t online state at parallel mode group.
If there is a fault mark in the resource, in which that has been failed, it should be cleared first before sending the that is online. This is because MCCS regards cause of the fault is not identified yet.
There are some considerations for dependency as well. To online a resource, if there is a child resource, child resource should be online state first. Since there is a dependency, if the child resource is not online state, parent resource cannot be online as well.
When the child resource exists, you should check that is online state before the resource bring online.
Offline
The resource goes offline.
Just like the start command, there is a sub menu where you can select a node.
The command is activated when there exists an online node.
You should note whether there are the parent resources online. The parent resource depends on the selected resource when it uses the Terminate command.
So, when you use the Terminate command, you should first terminate the parent resource which is in the reverse order of Start command.
Thus, when MCCS runs the Terminate command, if the online parent resource exists, it will first check whether to terminate the parent resource first.
Offline Propagation
You can take a resource offline by using this.
Similar to Online, you can choose appropriate node from the sub menu.
You can take a resource including parent resources offline by using this.
Clear Fault
장애가 발생한 리소스는 장애 표시를 남겨두고 관리자의 조치가 있기 전까지는 그 노드 내에서 해당 리소스를 시작할 수 없습니다.
다시 말해 관리자의 처리를 기다리는 상태로 남겨지게 되는데, 장애 해결을 한 후에 다시 MCCS 운영을 하기 위해서는 장애 표시를 제거해야 하며 이때에 이 명령을 사용합니다.
리소스 장애 표시 제거는 하나의 리소스만 해당되지만 그룹의 장애 표시 제거는 그룹 내의 모든 장애 표시를 제거할 수 있습니다this.
Clear Fault
The sign of failure is still displayed for the failed resource. Until the manager takes necessary actions, you cannot start the resource in the node.
In other words, it is waiting for the manager's actions. After troubleshooting, if you want to resume MCCS operation, the sign of failure should be removed.
Use the command for this purpose. 'Remove Sign of Resource Failure' is applicable to one resource but 'Remove Sign of Group Failure' is applicable to all the resources in the group.
Delete
You can delete a resource by using this.
리소스 복사 및 붙여넣기
새로운 리소스를 생성 할 때 필수 입력이 되어야 하는 속성 값을 매번 새로 입력하기가 번거롭습니다.
기존에 존재하는 리소스와 유사한 설정 값을 대부분 유지한 상태에서 리소스를 추가 하기 위해서는 관리 콘솔 화면에서 리소스 복사 및 붙여넣기 기능을 사용하여 손쉽게 리소스를 추가할 수 있습니다.
리소스 복사의 대상은 개별 리소스이며, 붙여넣기의 대상은 해당 그룹 또는 타 그룹입니다.
| Warning |
|---|
리소스 붙여넣기의 속성값은 기본적으로 복사한 리소스의 속성값을 유지합니다. 따라서 붙여넣는 리소스의 속성을 상황에 맞게 변경해야 복사한 리소스의 속성과 중복되지 않습니다. |
리소스 복사하기
...
리소스 붙여넣기
새로 추가 할 리소스의 네트워크 어댑터를 선택하시고 리소스 이름을 명명하면 됩니다.
| Info |
|---|
기본적으로 붙여넣기한 리소스 이름은 복사한 리소스의 이름에 "_1" 이 접미어로 제공됩니다. |
ex> 네트워크카드 붙여넣기 화면
[그림] 네트워크 카드 리소스 붙여넣기 화면
CLI 사용(mcres 명령)
리소스에 관한 명령을 전달 합니다. 리소스에 대해 추가, 삭제, 온라인, 오프라인, 속성 편집 등의 명령을 내릴 수 있습니다.
...
Copy and Paste Resource
It is an annoyance if attribute value is entered whenever a new resource is created.
When you add a new resource same as type of resource which is already exist, you can use this function.
Copied resource maintain same values as original one and can be pasted on any group.
After paste the resource, you can edit the values.
| Warning |
|---|
Attribute values that is copied resource are basically same as original resource. |
Resource Copy
- Right click on the resource to be copy and select "Copy Resource".
- Right click on the group to be paste and select "Paste Resource".
Resource Paste
Select the network adaptor for the resource to newly add and name the resource.
| Info |
|---|
Copied resource name is defined which '_number'is added from original name by default and this can be editable. Depending on the resource type, you need to enter extra information if necessary. |
CLI Use (mcres command)
It sends MCCS resources related commands. Commands such as add, delete, online, offline, edit of resource can be done.
| Info |
|---|
When you install MCCS, the initial user account ID is set to 'admin' and the password is set to 'password'. |
Syntax
mcres [-u userid -pw password] [-n ip node_ip_address] [-p port] -command [ resource ] [ -g group ] [ -n node]mcres [-u userid -pw password] [-n ip node_ip_address] [-p port] -add [ resource ] [ -t resource_type ] [ -g group ]mcres [-u userid -pw password] [-n ip node_ip_address] [-p port] -monitor [ group_name ] [ -t interval(seconds)]mcres [-u userid -pw password] [-n ip node_ip_address] [-p port] -modify [ resource ] [-a attribute attribute_value] [ -g group ] [ -n node] |
Options
| Option | 설명Description |
-h | 도움말을 출력합니다It prints help menu. |
| -u | 사용자 ID를 지정합니다Designate the user account ID. |
| -pw-u 옵션의 사용자 Password를 지정합니다 | Enter the user password. |
-n명령을 실행하기 위해 접근할 노드를 지정합니다. 생략시 로컬 노드에 대해서 명령을 실행하기 위해 접근합니다ip | It defines the node to access to execute command. If omitted, it will access to execute command for local node. |
-p명령을 실행하기 위해 접근할 포트를 지정합니다. 생략시 기본 포트로 접근하며, 핫빗 포트가 변경이 되면 명령실행시 포트를 지정해 주어야 합니다 | It defines the port to access to execute command. If omitted, it will access to the default value which is 4321, and when you define specific port number as heartbeat, enter this followed by --p. |
-resourcecommand | 리소스에 내릴 명령을 지정합니다It defines resource command. (add, delete, enable, disable, monitor, modify, link, unlink, local, Global, Online, Offline, Offlineprop, Probe, clear, list) |
resource | 작업할 리소스명을 입력합니다It enters resource name. |
-a | [list] 명령일 경우 나열할 속성값을 지정합니다. [modify] 명령일 경우 변경할 속성과 속성값을 나열해 줍니다. |
-t | It defines resource type when it is [-add] 명령일 경우 리소스 타입을 지정합니다. command. It specifies time interval when it is [-monitor] 명령일 경우 시간 주기를 지정합니다command. |
-g | 작업할 그룹을 지정합니다It defines group name to be managed. |
-n | 작업할 노드를 지정합니다. |
...
It defines node name to be managed. |
Example
add
testGroup그룹에 복합 응용 타입으로 testResource 를 생성합니다. Add testResource of application resource type on testGroup.
mcres -u admin -pw password -add testResource -t |
resourceType -g testGroup |
delete
Delete testResource 리소스를 삭제합니다.
mcres -u admin -pw password -delete testResource |
enable
Enable testResource 리소스를 활성화시킵니다.
mcres -u admin -pw password -enable testResource |
disable
Disable testResource 리소스를 비활성화 시킵니다.
mcres -u admin -pw password -disable testResource |
monitor
testGroup 에 속한 모든 리소스를 interval 간격으로 모니터링 합니다. 주기가 지정되지 않은 경우에는 3초가 기본값으로 지정됩니다. It monitors a resource in every interval. If the period is not set, 3 sec is a default value.
mcres -u admin -pw password -monitor [testGroup] [-t interval(seconds)] |
testGroup을 10초 간격으로 모니터링 합니다It monitors testResource every 10 seconds.
mcres -u admin -pw password -monitor testGroup -t 10 |
modify
testResource 리소스의 attribute를 value 값으로 수정합니다Modify a value of attribute of testResource in a node.
mcres -u admin -pw password -modify testResource -a attribute attribute_value [ -n node ] |
testGroup의 testResource 리소스의 User속성 값을 administrator로 수정합니다Modify a value of ‘User’ attribute of testResource to administrator in testNode.
mcres -u admin -pw password -modify testResource -a User administrator -n testGroup |
link
리소스 간의 의존 관계를 생성합니다.
...
link
Make a dependency link among resources.
Make a dependency link between the resource1 as parent and the resource2 as child.
mcres -u admin -pw password -link resource1 resource2 |
unlink
리소스 의존 관계를 삭제합니다Delete a dependency link between the resource1 and the resource2.
mcres -u admin -pw password -unlink resource1 resource2 |
local
testResource 속성 값을 모든 노드들의 속성값에 대하여 서로 다른 값을 입력할 수 있도록 지역화 합니다.
(실제 속성 값 수정은 modify 명령을 통해 수정해 주어야 합니다Set a value of attribute of the resource per node.
It is used locally so that other values can be inserted for attribute values of all the nodes.
(Modify command should be used to change the value.)
mcres -u admin -pw password -local |
-r testResource -a attribute |
global
testResource 의 속성을 모든 노드들의 속성값에 대하여 공통된 값을 입력할 수 있도록 공용화 합니다Set a value of attribute of the testResource to all node.
It is used publicly so that values can be inserted with common values for all nodes.
mcres -u admin -pw password -global -r testResource -a attribute [value] |
testResource 의 속성 User를 전체 속성으로 값을 administrator로 설정합니다Set a User’ attribute of the testResource to administrator.
mcres -u admin -pw password -global |
-r testResource -a User administrator |
...
online
testNode에 있는 testResource 리소스를 온라인 시킵니다Bring online testResource on testNode.
mcres -u admin -pw password -online testResource -n testNode |
...
offline
testNode의 testResource 리소스를 오프라인 시킵니다Take offline testResource on testNode.
mcres -u admin -pw password -offline testResource -n testNode |
Offlineprop
...
offlineprop
Take offline the resource including its parent resource(s) of testResource on testNode.
mcres -u admin -pw password -offlineprop testResource -n testNode |
probe
testNode의 Probe
...
testResource 리소스를 탐색합니다 on testNode.
mcres -u admin -pw password -probe testResource -n testNode |
clear
testNode의 testResource 리소스의 에러를 제거합니다Remove fault mark on testResource of testNode.
mcres -u admin -pw password -clear testResource [ -n testNode ] |
list
현재 리소스 상태를 출력합니다Print current resource state.
mcres -u admin -pw password -list [resource [ -a attribute]] | [-g group [-a attribute]] |