Bug 678394
Summary: | RFE: Addition of Power Management to default DB | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Timothy St. Clair <tstclair> |
Component: | condor-wallaby-base-db | Assignee: | Robert Rati <rrati> |
Status: | CLOSED ERRATA | QA Contact: | Luigi Toscano <ltoscano> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | Development | CC: | iboverma, ltoscano, matt, mhusnain, mkudlej, tstclair |
Target Milestone: | 2.0 | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | condor-wallaby-base-db-1.7-2 | Doc Type: | Enhancement |
Doc Text: |
C: MRG Grid 2.0 includes a Power Management feature
C: The user would have to manually configure wallaby to support Power Management
C: The base database for wallaby now includes Power Management
R: Users can easily configure Power Management through the remote configuration feature
Release Note Entry:
MRG Grid 2.0 now includes a Power Management feature, configurable manually via the wallaby component. Users can configure Power Management through the remote configuration feature.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2011-06-23 15:37:00 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 674161, 693778 |
Description
Timothy St. Clair
2011-02-17 19:22:39 UTC
Depends on ExecuteNode Conflicts with Scheduler, Collector, and Negotiator This still requires testing, but below are is the listing of updates: ################################################################### # PowerManagementNode # Depends on: ExecuteNode # Conflicts with: Scheduler, Collector, and Negotiator ################################# HIBERNATE_CHECK_INTERVAL = 300 ################################# # user should adjust TimeToWait on enabling feature TimeToWait = (2 * $(HOUR)) ShouldHibernate = ( (KeyboardIdle > $(StartIdleTime)) \ && $(CPUIdle) \ && ($(StateTimer) > $(TimeToWait)) ) ################################# # see http://www.cs.wisc.edu/condor/manual/v7.5/3_3Configuration.html#param:Hibernate # User should choose level of "hibernation" ################################# HIBERNATE = ifThenElse( $(ShouldHibernate), "RAM", "NONE" ) ################################################################### # Feature: PowerManagementCollector # Depends on: Collector # Notes: Doesn't work with view collectors so per collector there needs # To be local OfflineLogs and a rooster. #'d means defaulted in condor_config and should not be in the store. OFFLINE_LOG = $(LOG)/OfflineLog # use default # Set to a value of 20-days being offline. OFFLINE_EXPIRE_ADS_AFTER = 28800 # allow setting show default # The admin will likely want to craft this! UNHIBERNATE = MachineLastMatchTime =!= UNDEFINED # allow setting show defgault #### Rooster Specific ROOSTER = $(LIBEXEC)/condor_rooster.exe # use default DAEMON_LIST = $(DAEMON_LIST), ROOSTER # use default ROOSTER_INTERVAL = 300 # allow setting show default ROOSTER_UNHIBERNATE_RANK #allow setting (no default) ROOSTER_MAX_UNHIBERNATE = 0 # allow setting, no default ROOSTER_UNHIBERNATE = Offline && Unhibernate # use default ROOSTER_WAKEUP_CMD = "$(BIN)/condor_power -d -i" #use default ################################################################### # PowerManagementNode # Depends on: ExecuteNode # Conflicts with: Scheduler, Collector, and Negotiator ################################# HIBERNATE_CHECK_INTERVAL = 300 ################################# # user should adjust TimeToWait on enabling feature TimeToWait = (2 * $(HOUR)) ShouldHibernate = ( (KeyboardIdle > $(StartIdleTime)) \ && $(CPUIdle) \ && ($(StateTimer) > $(TimeToWait)) ) ################################# # see http://www.cs.wisc.edu/condor/manual/v7.5/3_3Configuration.html#param:Hibernate # User should choose level of "hibernation" ################################# HIBERNATE = ifThenElse( $(ShouldHibernate), "RAM", "NONE" ) ################################################################### # Feature: Collector # Update to include OFFLINE_LOG = $(SPOOL)/OfflineLog # use default # make sure preen doesn't destroy VALID_SPOOL_FILES = $(VALID_SPOOL_FILES), $(OFFLINE_LOG) # use default # Set to a value of 20-days being offline. OFFLINE_EXPIRE_ADS_AFTER = 28800 # allow setting show default ################################################################### # Feature: Rooster # Depends on: # Conflicts with: PowerManagementNode # Notes: Doesn't work with view collectors so per collector there needs # To be local OfflineLogs and a rooster. # The admin will likely want to craft this! UNHIBERNATE = MachineLastMatchTime =!= UNDEFINED # allow setting show defgault #### Rooster Specific ROOSTER = $(LIBEXEC)/condor_rooster.exe # use default DAEMON_LIST = $(DAEMON_LIST), ROOSTER # use default ROOSTER_INTERVAL = 300 # allow setting show default ROOSTER_MAX_UNHIBERNATE = 0 # allow setting, no default ROOSTER_UNHIBERNATE_RANK #allow setting (no default) expression used when ROOSTER_MAX_UNHIBERNATE is set ROOSTER_UNHIBERNATE = Offline && Unhibernate # use default ROOSTER_WAKEUP_CMD = "$(BIN)/condor_power -d -i" #use default Added in master. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: C: MRG Grid 2.0 includes a Power Management feature C: The user would have to manually configure wallaby to support Power Management C: The base database for wallaby now includes Power Management R: Users can easily configure Power Management through the remote configuration feature Corrected feature names and include info: ################################################################### # PowerManagementNode # Includes on: ExecuteNode # Conflicts with: Scheduler, Collector, and Negotiator ################################# HIBERNATE_CHECK_INTERVAL = 300 ################################# # user should adjust TimeToWait on enabling feature TimeToWait = (2 * $(HOUR)) ShouldHibernate = ( (KeyboardIdle > $(StartIdleTime)) \ && $(CPUIdle) \ && ($(StateTimer) > $(TimeToWait)) ) ################################# # see http://www.cs.wisc.edu/condor/manual/v7.5/3_3Configuration.html#param:Hibernate # User should choose level of "hibernation" ################################# HIBERNATE = ifThenElse( $(ShouldHibernate), "RAM", "NONE" ) ################################################################### # Feature: PowerManagementCollector # Include: Collector # Update to include OFFLINE_LOG = $(SPOOL)/OfflineLog # use default # make sure preen doesn't destroy VALID_SPOOL_FILES = $(VALID_SPOOL_FILES), $(OFFLINE_LOG) # use default # Set to a value of 20-days being offline. OFFLINE_EXPIRE_ADS_AFTER = 28800 # allow setting show default ################################################################### # Feature: PowerManagementSubnetManager # Depends on: # Conflicts with: PowerManagementNode # Notes: Doesn't work with view collectors so per collector there needs # To be local OfflineLogs and a rooster. # The admin will likely want to craft this! UNHIBERNATE = MachineLastMatchTime =!= UNDEFINED # allow setting show defgault #### Rooster Specific ROOSTER = $(LIBEXEC)/condor_rooster.exe # use default DAEMON_LIST = $(DAEMON_LIST), ROOSTER # use default ROOSTER_INTERVAL = 300 # allow setting show default ROOSTER_MAX_UNHIBERNATE = 0 # allow setting, no default ROOSTER_UNHIBERNATE_RANK #allow setting (no default) expression used when ROOSTER_MAX_UNHIBERNATE is set ROOSTER_UNHIBERNATE = Offline && Unhibernate # use default ROOSTER_WAKEUP_CMD = "$(BIN)/condor_power -d -i" #use default The new features (PowerManagementCollector, PowerManagementSubnetManager, PowerManagementNode) have been added to the database (PowerManagementSubnetManager has also a mandatory ROOSTER_SUBNET_MASK parameter). Verified on RHEL6.1 (nightly >=20110512), RHEL5.6: condor-wallaby-base-db-1.12-1 (noarch package). Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,4 +1,8 @@ C: MRG Grid 2.0 includes a Power Management feature C: The user would have to manually configure wallaby to support Power Management C: The base database for wallaby now includes Power Management -R: Users can easily configure Power Management through the remote configuration feature+R: Users can easily configure Power Management through the remote configuration feature + +Release Note Entry: + +MRG Grid 2.0 now includes a Power Management feature, configurable manually via the wallaby component. Users can configure Power Management through the remote configuration feature. Technical note can be viewed in the release notes for 2.0 at the documentation stage here: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2.0/html-single/MRG_Release_Notes/index.html#tabl-MRG_Release_Notes-GRID_Update_Notes-RHM_Known_Issues An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2011-0889.html |