Changes between Version 9 and Version 10 of Software/eAM/aInventory/fScheduler

Timestamp:

Jan 24, 2016, 11:58:21 PM (9 years ago)

Author:

seskar

Comment:

—

Software/eAM/aInventory/fScheduler

@@ -1 @@
-[[TOC(Software/eAM/aI*, depth=3)]]
+[[TOC(Software/eAM/aI*, depth=4)]]
+
 === Domain management ===
+
 ==== Adding new testbed ====
 
@@ -31 +33 @@
 ==== Updating testbed information ====
 To change testbed name, make it active and change list of nodes do the following:
+
 ===== Scheduler database =====
  * Make domain active in scheduler database i.e set status to 'a':
@@ -46 +49 @@
 }}}
 
-===== Inventory database =====
-* Change name
-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:
-{{{
-UPDATE inventory54.resource SET name='<new_name>' where name='<old_name>';
-}}}
+===== Inventory database initialization and management =====
 
-* Make it active, i.e set INF_status to 1 if domain should appear on status page
-{{{
- wget -qO- 'http://new.orbit-lab.org:5054/attribute_modify?name=<new_name&attribute=INF_status&value=1
-}}}
-Domain have to have INF_x_max and INF_y_max attributes. It is necessary to restart status service after these changes.
-* Change description 
-{{{
- wget -qO- 'http://new.orbit-lab.org:5054/attribute_modify?name=<new_name>&attribute=INF_description&value=<new_description>
-}}}
-
-===== Define list of nodes =====
-
-* Delete old list of nodes  - currently, there is no possibility to do it trough service, it has to be done into database directly
-{{{
-DELETE FROM inventory54.relations WHERE subject_id=(SELECT id FROM inventory54.resources where name='<new_name>');
-}}}
-Pay attention, <new_name> is used because name is already changed. If you this before changing the name, than use <old_name>.
-* Add nodes  - do the flowing for each node that belongs to resource i.e. testbed
-{{{
- wget -qO- 'http://new.orbit-lab.org:5054/relation_add?parent=<new_name>&child=<node_name>
-}}}