{5} Assigned, Active Tickets by Owner (Full Description) (6 matches)

List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.

ibaldin@renci.org (5 matches)

Ticket Summary Component Milestone Type Created
Description
#41 RSpecs: Add component_manager and property to link Ads AM task 05/29/12

Add <component_manager> and <property> sub-elements on <link> elements.

<property> as in the ad RSpec schema:

 <xs:complexType name="LinkPropertyContents">
    <xs:group ref="rspec:AnyExtension"/>
    <xs:attributeGroup ref="rspec:AnyExtension"/>
    <xs:attribute name="source_id" use="required"/>
    <xs:attribute name="dest_id" use="required"/>
    <xs:attribute name="capacity"/>
    <xs:attribute name="latency"/>
    <xs:attribute name="packet_loss"/>
  </xs:complexType>

Where source_id and dest_id are the component_ids of the interfaces at the end points.

component_manager as in: manifest-request.xsd:

  <xs:element name="component_manager">
    <xs:complexType>
      <xs:attribute name="name" use="required"/>
    </xs:complexType>
  </xs:element>

#39 RSpecs: ExoSM Ad includes external references AM task 05/29/12

ExoSM (not individual racks) advertisement RSpec should include external references - show links to non-ExoGENI resources. EG to the mesoscale, NLR, Internet2, etc.

These connections should follow the stitching guidelines:

-there must be a link element for each connection to an External Aggregate.
-these link elements will each have two interface_ref component_id
-one of the interface_ref component_id references a local node->interface component_id
-the other interface_ref component_id is equal to a  link--->interface_ref component_id  in a link element of the External Aggregate 
-both of the peering Aggregates need to point to each other in consistent manner within their mainBody:link elements

Note the relation to ticket #37


#37 RSpecs: ExoSM Ad includes proper stitching extension AM task 05/29/12

ExoSM (not individual racks) should include a propert stitching extension - once, with a single aggregate.

Per Ilia, this is hard and possibly not possible.

Stitching extension rules:

-Identify all mainBody:link elements which have a link->interface_ref component_id which is for an External Aggregate.'
-A stitch:node element must be created for each of the nodes associated with the above identified mainBody:link elements
    Note:  only the mainBody:node elements which are part of a connection to an External Aggregate must be included
                in the Stitching Extension.  However, Aggregates may include other mainBody:node elements if they desire.
-The stitch:node elements are populated as follows described below:
   --stitch:node id==mainBody:node component_id
   --stitch:port id==mainBody:link->interface_ref component_id (which equals a node->interface component_id)
   --stitch:link id==stitch:portid with ":some-descriptive-term" appended
   --stitch:remoteLinkId==the stitch:link id from the External Aggregate stitching extension
-both of the peering Aggregates need to point to each other in consistent manner with  their stitch:link and stitch:remoteLinkId elements

#38 RSpecs: Rack Ads include external references AM task 05/29/12

Individual rack (not ExoSM) advertisement RSpecs should include external references - show links to non-local resources (whether they are Orca controlled or not). EG to the mesoscale, NLR, Internet2, etc.

These connections should follow the stitching guidelines:

-there must be a link element for each connection to an External Aggregate.
-these link elements will each have two interface_ref component_id
-one of the interface_ref component_id references a local node->interface component_id
-the other interface_ref component_id is equal to a  link--->interface_ref component_id  in a link element of the External Aggregate 
-both of the peering Aggregates need to point to each other in consistent manner within their mainBody:link elements

Note the relation to ticket #36


#72 RSpecs: preserve shared-vlan info in manifest AM task 07/19/12

manifest RSpecs should preserve the shared-vlan elements from the request, if any.

That is, the allocated links in the manifest should be marked as on the shared vlan. In particular, this allows the experimenter to see, in the manifest, the name of the shared VLAN that the link is on. This will also be useful for monitoring and GMOC data integration.

Note that this is a single instance of a larger rule: manifests should preserve elements from the request. But each such element requires (a) a model in NDL, and (b) explicit code to convert in both directions in the RSpec converter. So we will take these on a case by case basis.


jaipuria@cs.duke.edu (1 match)

Ticket Summary Component Milestone Type Created
Description
#87 User credentials incorrectly sufficient for local sliver creator AM defect 07/31/12

User credential is sufficient to allow the local sliver creator to do any operation. That is wrong.

Our test scenario:

  • user1 creates slice1
  • user1 creates sliver at ExoGENI
  • user1 gets user1's user credential file
  • user1 uses user1's user credential file as a slice credential file to access AM API options for slice1: -listresources, sliverstatus, deletesliver, createsliver, renewsliver, and shutdown
  • That is, as user1:

./omni.py listresources slice1 --slicecredfile user1_usercred.cred

This test incorrectly works. The ExoGENI AM allows the user who created the local slivers to do any operation, using just a valid user credential - one that does not reference the slice at all.


Note: See TracReports for help on using and creating reports.