Changes between Version 5 and Version 6 of Software/eAM/aInventory/fScheduler
- Timestamp:
- Jun 24, 2013, 3:08:04 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Software/eAM/aInventory/fScheduler
v5 v6 1 == Domain management==2 === Adding new testbed===1 === Domain management === 2 ==== Adding new testbed ==== 3 3 4 4 Currently, information about resources i.e. testbeds are kept into 2 databases, scheduler database (newScheduler) and inventory database (inventory54). To add new virtual domain we need to update both databases. … … 14 14 There is also file testbed_attributes.yaml to define necessary testbed information. 15 15 16 === Make testbed inactive===16 ==== Make testbed inactive ==== 17 17 To remove testbed from scheduler page just mark it inactive into both databases. 18 18 … … 28 28 29 29 30 === Updating testbed information===30 ==== Updating testbed information ==== 31 31 To change testbed name, make it active and change list of nodes do the following: 32 ==== Scheduler database====32 ===== Scheduler database ===== 33 33 * Make domain active in scheduler database i.e set status to 'a': 34 34 {{{ … … 45 45 }}} 46 46 47 ==== Inventory database====47 ===== Inventory database ===== 48 48 * Change name 49 49 It's not possible to change resource name using inventory service. This can be done directly into database. Anytime you can delete resource with <old_name> and create new one. To change resource name run flowing script: … … 61 61 }}} 62 62 63 ==== Define list of nodes====63 ===== Define list of nodes ===== 64 64 65 65 * Delete old list of nodes - currently, there is no possibility to do it trough service, it has to be done into database directly