Custom Query (87 matches)
Results (13 - 15 of 87)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #98 | fixed | Automatically append Slice Name to Host name to generate resource ID | ||
| Description |
Currently, the problem is experimenters are required to enter their slice name multiple times to generate resource ID even after selecting their slice from drop down list. One possible solution:
1) Define a convention for host names in the OEDL script
E.g defProperty("resource<experimenter defined variable>", <hostname>, "Description")
2) In LabWiki, parse all properties beginning with the word "resource" separately
3) Append slice name selected by user from drop down list to the "resource" name to generate resource ID
4) Send new properties to EC for execution of experiment I will setup a prototype on emmy9 to test this out. |
|||
| #14 | fixed | Install the omf_sfa code on emmy9 for initial prototyping | ||
| Description |
The omf sfa provides a reference implementation of a data model and REST interface similar to what we need for the GIMI experiment registry on the GIMI server. To start, we should install the omf_sfa code located at https://github.com/mytestbed/omf_sfa (see README) to start testing against the existing REST interface. |
|||
| #15 | fixed | Define experiment registry REST API | ||
| Description |
The REST API including required resources, JSON responses, and authentication needs to be designed. |
|||
