Opened 9 years ago

Closed 9 years ago

#24 closed (wontfix)

Ad Rspec: same component_manager_id throughout

Reported by: ahelsing@bbn.com Owned by: ibaldin@renci.org
Priority: minor Milestone:
Component: AM Version: SPIRAL4
Keywords: Cc:
Dependencies:

Description

The Ad RSpec should use the same component_manager_id throughout, as this is the same AM.

Generally, component_manager_id == AM URN, and is of the form "<prefix>+<name>+authority+am". So I suggest you use "<prefix>+<SM site name>+authority+am"

Change History (4)

comment:1 Changed 9 years ago by ibaldin@renci.org

Owner: changed from somebody to ibaldin@renci.org
Status: newassigned

This one should be relatively fixable, although internally in ORCA they are not under a control of a single aggregate. It is true that a single SM is responsible for them, so we need to fix it for RSpec.

comment:2 Changed 9 years ago by ibaldin@renci.org

I think this has been fixed. I've also improved the look/format of component ids, however I know they still contain characters not accepted by other tools.

Give it a try, the converter has been updated.

comment:3 Changed 9 years ago by ahelsing@bbn.com

type: taskenhancement

I can confirm that on the BBN rack, both Nodes have the same component_manager_id, of the form described above.

The ExoSM rack Ad RSpec however lists many component_manager_ids. I can understand why that would be true, and I suspect tools will understand the RSpec just fine. So fixing this is pretty low priority. I just think it's a little misleading - the management of all of the resources you are describing here is happening at the ExoBroker?. And I think the component_manager_id should reflect that.

comment:4 Changed 9 years ago by ahelsing@bbn.com

Resolution: wontfix
Status: assignedclosed

Per Ilia, this is something we won't fix at the ExoSM. If this causes problems later, we'll revisit it.

Note: See TracTickets for help on using tickets.