Changes between Version 5 and Version 6 of Software/eAM/aInventory/fScheduler


Ignore:
Timestamp:
Jun 24, 2013, 3:08:04 PM (11 years ago)
Author:
seskar
Comment:

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 ====
    33
    44Currently, 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.
     
    1414There is also file testbed_attributes.yaml to define necessary testbed information.
    1515
    16 === Make testbed inactive ===
     16==== Make testbed inactive ====
    1717To remove testbed from scheduler page just mark it inactive into both databases.
    1818
     
    2828
    2929
    30 === Updating testbed information ===
     30==== Updating testbed information ====
    3131To change testbed name, make it active and change list of nodes do the following:
    32 ==== Scheduler database ====
     32===== Scheduler database =====
    3333 * Make domain active in scheduler database i.e set status to 'a':
    3434{{{
     
    4545}}}
    4646
    47 ==== Inventory database ====
     47===== Inventory database =====
    4848* Change name
    4949It'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:
     
    6161}}}
    6262
    63 ==== Define list of nodes ====
     63===== Define list of nodes =====
    6464
    6565* Delete old list of nodes  - currently, there is no possibility to do it trough service, it has to be done into database directly