Opened 12 years ago
Closed 11 years ago
#114 closed (fixed)
the database should contain a direct link between aggregates and resources
| Reported by: | sedwards@bbn.com | Owned by: | somebody |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Database | Version: | |
| Keywords: | Cc: | ||
| Dependencies: |
Description (last modified by )
The gmoc.py client and XML schema serialize and submit resources with a direct link between a resource and an aggregate, e.g.:
<resource aggregate="foam5.gpolab.bbn.com:3626" description="" name="urn:publicid:IDN+openflow:foam:foam5.gpolab.bbn.com+datapath+04:4d:00:12:e2:b8:a5:d0" organization="urn:publicid:IDN+gmoc.geni.net+organization+BBN" pop="urn:publicid:IDN+gmoc.geni.net+pop+gpolab" state="Unknown" type="datapath"/>
However, this link is not encoded in the database. It should be.
Change History (9)
comment:1 Changed 12 years ago by
| Priority: | major → critical |
|---|
comment:2 Changed 12 years ago by
| Priority: | critical → major |
|---|
comment:3 Changed 12 years ago by
| Component: | Infrastructure → Database |
|---|---|
| Description: | modified (diff) |
| Summary: | If submit Resources without Slivers they aren't linked to an Aggregate → the database should contain a direct link between aggregates and resources |
comment:4 Changed 12 years ago by
| Owner: | changed from somebody to Kevin Bohan |
|---|
comment:5 Changed 12 years ago by
| Description: | modified (diff) |
|---|
comment:6 Changed 12 years ago by
| Milestone: | gmoc.py data submission debugging |
|---|---|
| Owner: | changed from Kevin Bohan to somebody |
comment:7 Changed 11 years ago by
It appears the UI (and the backend database schema for that matter) will only show resources associated to an aggregate if there is at least one sliver tied to that resource. The relationship is resource -> sliver -> aggregate and there is no direct resource -> aggregate association in the database schema. That was a little odd for me to discover considering the XML has you send <resource aggregate='…' /> which would make you think a resource has a direct aggregate mapping without the need of a sliver.
comment:8 Changed 11 years ago by
Mitch implemented this link today, and we tested it, finding a minor bug (GMT 155), but it seems okay otherwise.
We still need to implement the link in gmoc.py download, hopefully tomorrow.
comment:9 Changed 11 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
The resource/aggregate link has been implemented and tested in gmoc.py, so this can now be closed. Sorry, i don't have the version handy in which this was fixed, but it's definitely fixed in some version prior to 1.2.10, so i'll say it was fixed before or during 1.2.10.
We discussed this further this morning and decided that it is not a blocker. We've known we didn't have this functionality for a long time, and we still want it, but it's not a GEC15 blocker.