__group__,ticket,summary,component,version,type,owner,status,created,_changetime,_description,_reporter
Release,425,Milestone S2.b completion,CRON,SPIRAL2,task,pkondi1@lsu.edu,new,2010-04-21T00:19:01-04:00,2010-04-21T00:19:01-04:00,"LONI network has established a 10Gbps connection to Internet2 since the end of 2009.[[BR]]
To manage connectivity between LONI and Internet2, the user should login to OSCAR Inter Domain Controller (IDC). While creating a new reservation, user should specify the following parameters: Source and Destination hosts may be specified (e.g. by a DNS host name, IP address or as a topology link identifier), Bandwidth (in Mbps), start date, start time and end date, end time. [[BR]]
Here is a limitation that one reservation can be made for maximum 24 hour i.e. that reservation will be cancelled automatically after 23 hour and 59 minute and 59 second. As we are using layer 2 connection, user should provide layer 2 parameters such as vlan tag while reserving a new connection. It is suggested to use numbers within range of 3000-4000 as vlan tag number to avoid conflict with existing vlans (as common vlan numbers are in the range of 1000).
Note: User should not reserve the bandwidth if s/he is not currently using the resource to ensure better utilization.",Seung-Jong Park
Release,426,milestone S2.c completion,CRON,SPIRAL2,task,pkondi1@lsu.edu,new,2010-04-21T00:34:29-04:00,2010-04-21T00:34:29-04:00,"An optical fiber between CRON testbed (which was deployed at the first floor of the Frey building inside Louisiana State University) and a switch of LONI has been deployed. The LONI switch is connected to the internet2 network through Internet2 ION service. Our connection between CRON testbed and the ION is done using the IDC server. This connection can be maintained and operated through this IDC server. This has been successfully tested by LONI administrators. Through this IDC interface, bandwidth can be reserved in the internet2 for the experiment. Right now, LONI cannot handle dynamic setting up of different control parameters through scripts. So they should be set up manually by using GUI and login
After that, we have completed a test of the ION connection between the temporary Vlan assignment for CRON on the LONI switch (www.loni.bato.dcn.internet2.edu) and BBN (POC of BBN: Heidi Dempsey) successfully. BBN has also tested the Vlan (the information that was used for the test).
Description: BBN/LONI test 1 (minimal connectivity)[[BR]]
Source: bbn.bost.dcn.internet2.edu[[BR]]
Destination: loni.bato.dcn.internet2.edu[[BR]]
Start Date: 2/26/2010[[BR]]
Start Time: 10:27[[BR]]
End Date: 2/26/2010[[BR]]
End Time: 11:27[[BR]]
Duration: 1 hour[[BR]]
Bandwidth: 50 Mbps[[BR]]
Source VLAN: 3726[[BR]]
Source VLAN type: Tagged[[BR]]
Destination VLAN: 2999[[BR]]
Destination VLAN type: Tagged[[BR]]
Since there were only few GENI sites which have the Internet2 ION service, we could not perform the connection test from CRON testbed to other ProtoGENI sites. This test will be done to confirm end to end connectivity.
To build a circuit to Layer 2 connection one should select [http://loni.bato.dcn.internet2.edu "" Select URN""] as the local URN and set the system to a predefined/allocated tagged vlan. The system will translate vlans, so users have to make sure that s/he has the correct Vlan set on his/her side. It does not have to match the remote Vlan Number. Users have to keep in mind that this is an allocation reservation system and s/he has to make sure that his/her requests fit the bandwidth and time slots available
",Seung-Jong Park
Release,427,milestone S2.d completion,CRON,SPIRAL2,task,pkondi1@lsu.edu,new,2010-04-21T00:49:36-04:00,2010-04-21T00:49:36-04:00,"Rspec allows advertising, Request and describing the resources used in CRON project. The format used in describing the Rspect is referred from Protogeni. Rspec is divided into three categories based on the purpose
1. Advertisements – Used to describe the resources available on a Component Manager. They contain information used by clients to choose resources (components). Other kinds of information (MAC addresses, hostnames, etc.) which are not used to select resources should not be in the Advertisement.[[BR]]
2. Requests - specify which resources a client is selecting from Component Managers. They contain a (perhaps incomplete) mapping between physical components and abstract nodes and links[[BR]]
3. Manifests - provide useful information about the slivers actually allocated by a Component Manager to a client. This involves information that may not be known until the sliver is actually created (i.e. dynamically assigned IP addresses, hostnames), or additional configuration options provided to a client.[[BR]]
The resources offered by CRON are,[[BR]]
—PCs with 10G interface (Sun X4240)[[BR]]
—10G switch (Cisco Nexus 5000 series switch)[[BR]]
—10G hardware Emulator (Anue XGEM)[[BR]]
We have defined the advertisement Rspec for all the above resources as below.
truetruetruetruetruetrue1000000000
[[BR]]
Few aspects of hardware emulator Rspec needs to be finalized
",Seung-Jong Park
Release,490,LEARN S2.k Recommendations for Measurement Handlers on GENI,LEARN,SPIRAL2,task,hmussman@bbn.com,new,2010-07-19T10:29:04-04:00,2010-07-19T10:29:04-04:00,"This is the milestone report for LEARN S2.k - Recommendations for Measurement Handlers on GENI:
[http://groups.geni.net/geni/attachment/wiki/LEARN/GENI_MS2K_LEARN_Jul20.pdf]",dgurkan@uh.edu
Release,519,Milestone 1 completed,ATTRIB,SPIRAL2,task,Vic Thomas,new,2010-08-25T21:42:05-04:00,2010-10-05T13:46:45-04:00,The outline for the report has been delivered to the GPO and posted to the Wiki.,bishop@cs.ucdavis.edu
Release,673,Move SPP node in Washington D.C. from current rack to new rack,SPP,SPIRAL2,task,matt@internet2.edu,new,2010-10-07T09:09:01-04:00,2010-10-20T17:43:51-04:00,"The Internet2 engineers want to move the SPP in Washington D.C. to a new rack from the rack it was originally installed in, which also housed the now-defunct Ciena connection to I2.
This work is currently scheduled for 10/19. John Dehart of WUSTL has asked I2 to notify him when the move is done and to stay onsite until John finishes testing to verify that the node still works.
Hans Addleman addlema@grnoc.iu.edu is coordinating the install from the GMOC side.
Dependency on OpenFlow install ticket because both activities are scheduled for the same I2 team, but there is no technical dependencies to OpenFlow.",hdempsey@bbn.com
COGRADIO: S2.e Stand-alone system available to GENI users Release,533,Milestone S2.e completion,COGRADIO,SPIRAL2,task,Ivan Seskar,new,2010-08-31T10:05:44-04:00,2010-08-31T10:16:48-04:00,"Per Seskar on 8/25:
Two nodes are available for remote access as part of ORBIT*.
The platform is also available for purchase from Radio Technology Systems.
Mussman on 8/31:
BUT, we need to understand the nature of the available systems, whether they are always available, and how they would be accessed via OMF in ORBIT.
Seskar on 8/25:
Main issue to date is the use of licensed software (namely Xilinx and Matlab) that is required for FPGA code development. This is especially troublesome for deployments in remotely accessible testbeds not only because it requires that each user have a valid license, but because most academic licenses require that the actual development be done on the machines that belong to the licensee (rather than on the infrastructure machines that the testbed provides). Same issue exists for other FPGA based solutions (like NetFPGA)
Specification tools like BlueSpec reduce some of these issues (matlab/simulink), but don’t get around basic Xilinx license issue
Outreach to Xilinx Research at Colorado to explore options
Mussman on 8/31: Need to resolve these issues!",hmussman@bbn.com
COGRADIO: S2.f Release design information for stand-alone system kit Release,534,Milestone S2.f completion,COGRADIO,SPIRAL2,task,Ivan Seskar,new,2010-08-31T10:09:35-04:00,2010-08-31T10:09:35-04:00,"Per Seskar on 8/25:
Framework as well as all of the technical information is continuously released at http://crkit.orbit-lab.org
Mussman on 8/31:
Need much more complete view of design, and step-by-step method for building FPGA load, etc.",hmussman@bbn.com
COGRADIO: S2.g Contribution to GENI outreach Release,535,Milestone S2.g completion,COGRADIO,SPIRAL2,task,Ivan Seskar,new,2010-08-31T10:12:03-04:00,2010-08-31T10:12:03-04:00,"Seskar on 8/25:
wo undergraduate students were involved in framework testing and verifications as part of the WINLAB Summer Internship",hmussman@bbn.com
GMOC: S2.d Revised Concept of Operations document Release,530,Get feedback and Revise Concept of Operations Document,GMOC,SPIRAL2,task,jph@grnoc.iu.edu,new,2010-08-31T09:04:01-04:00,2010-08-31T09:04:01-04:00,"No significant feedback from mailing list on Concept of Operations document yet. Jon Paul Herron has prepared a presentation on the Concept of Operations to try to solicit information during OMIS meetings, but the topic has been postponed due to lack of time for two meetings. Based on informal conversatons, we believe the draft document will need revisions. Jon Paul investigating other ways to get feedback for the revision. Please update ticket with current plan.",hdempsey@bbn.com
KANSEI: S2.f Connections from Kansei and NetEye to Internet2 Release,372,Milestone S2.f completion,KANSEI,SPIRAL2,task,hzhang@cs.wayne.edu,assigned,2010-03-19T01:24:03-04:00,2010-03-19T01:24:25-04:00,Completed connection plan for connecting Kansei and NetEye to Internet2; Have actively participated in Cluter-D wide connection discussion.,hzhang@cs.wayne.edu
LAMP: S2.a Requirements and design doc - Release,675,Milestone S2.a completion,LAMP,SPIRAL2,task,Vic Thomas,new,2010-10-21T00:29:17-04:00,2010-10-21T00:31:53-04:00,The requirements and design document was posted on LAMP's main trac page on 08/30/10. This document also includes the prospectus of integration (last section) informed by the I&M WG meetings and discussions with other projects.,fernande@cis.udel.edu
LAMP: S2.c Updated prospectus - Release,676,Milestone S2.c completion,LAMP,SPIRAL2,task,Vic Thomas,new,2010-10-21T00:33:01-04:00,2010-10-21T12:16:47-04:00," The requirements and design document was posted on LAMP's main trac page
on 08/30/10. This document also includes the prospectus of integration
(last section) informed by the I&M WG meetings and discussions with other
projects.",fernande@cis.udel.edu
LAMP: S2.e V1.0 of perfSONAR on ProtoGENI - Release,677,Milestone S2.e completion,LAMP,SPIRAL2,task,Vic Thomas,new,2010-10-21T00:38:57-04:00,2010-10-21T12:16:33-04:00,"The initial LAMP software that was presented on GEC8 was not released to the public. There was a demo, but the system relied on too many manual steps and was not user friendly. We decided instead to concentrate on improving this and releasing the first version as the LAMP I&M System RC1. This version was released on 09/22/2010. So LAMP 1.0 (milestone S2.e) and LAMP 1.1 (milestone S2.f) have been conflated into LAMP I&M System RC1. Information about the LAMP I&M System can be found on the LAMP trac page.",fernande@cis.udel.edu
LAMP: S2.f V1.1 of perfSONAR on ProtoGENI - Release,678,Milestone S2.f completion,LAMP,SPIRAL2,task,Vic Thomas,new,2010-10-21T00:39:56-04:00,2010-10-21T12:16:08-04:00,"The initial LAMP software that was presented on GEC8 was not released to the public. There was a demo, but the system relied on too many manual steps and was not user friendly. We decided instead to concentrate on improving this and releasing the first version as the LAMP I&M System RC1. This version was released on 09/22/2010. So LAMP 1.0 (milestone S2.e) and LAMP 1.1 (milestone S2.f) have been conflated into LAMP I&M System RC1. Information about the LAMP I&M System can be found on the LAMP trac page.",fernande@cis.udel.edu
LAMP: S2.g Demonstration of perfSONAR on ProtoGENI Release,679,Milestone S2.g completion,LAMP,SPIRAL2,task,Vic Thomas,new,2010-10-21T00:44:27-04:00,2010-10-21T12:15:52-04:00,There was a demo of the LAMP I&M System at GEC8. The poster for the demo can be found on our trac page.,fernande@cis.udel.edu
OFI2: S2.c Deploy OpenFlow switches to five POPs Release,562,Install NEC OpenFlow switch in Internet2 Atlanta,OFI2,SPIRAL2,task,matt@internet2.edu,new,2010-09-17T14:36:30-04:00,2010-10-18T14:23:00-04:00,"This would remove the HP 3500 currently installed in Atlanta, and replace it with a new NEC switch.
Current target: 4-Oct-2010
Depends on arrival of NEC switches (ordered, 30 day lead time)
and current usage of the HP Atlanta switch.
After the switches arrive, we'll re-evaluate and see if we want to take the risk in changing the switch in Atlanta from HP to NEC before GEC9.",matt@internet2.edu
OFI2: S2.c Deploy OpenFlow switches to five POPs Release,564,"Install Internet2 OpenFlow switch in Washington, DC",OFI2,SPIRAL2,task,matt@internet2.edu,new,2010-09-17T14:40:51-04:00,2010-10-07T08:58:00-04:00,"Deploy NEC switch in Washington, DC
Target date: 18-Oct-2010",matt@internet2.edu
OFI2: S2.c Deploy OpenFlow switches to five POPs Release,565,Install Internet2 OpenFlow switch in Los Angeles,OFI2,SPIRAL2,task,matt@internet2.edu,new,2010-09-17T14:44:28-04:00,2010-10-31T09:50:03-04:00,"Deploy NEC switch in Los Angeles
Target date: 25-Oct-2010
",matt@internet2.edu
OKGEMS: S2.e Plan to integrate robotic nodes Release,499,Milestone S2.e Completion,OKGEMS,SPIRAL2,task,andyli,new,2010-08-05T17:28:04-04:00,2010-10-11T12:45:07-04:00,We have completed a detailed plan for integrating robots into the ORCA control framework. We demonstrated our preliminary work to enable remote virtual lab for robotics at GEC8.,andyli
WIMXUCLA: S2.a Begin deployment of dual-mode vehicular nodes (WiFi and WiMax) Release,543,Started installation on Nodes and Base Station,WIMXUCLA,SPIRAL2,task,Giovanni Pau,new,2010-09-01T05:45:35-04:00,2010-09-01T05:46:48-04:00,Started WiMax Installation on Nodes and Base Station Installation.,Giovanni Pau
WIMXUCLA: S2.a Begin deployment of dual-mode vehicular nodes (WiFi and WiMax) Release,549,Milestone S2.a completion,WIMXUCLA,SPIRAL2,task,gerla@cs.ucla.edu,new,2010-09-01T17:49:14-04:00,2010-09-01T17:49:14-04:00,"9/1:
Task is late due to late arrival of equipments and late signature of the contract with GPO.
Waiting for tower, and WiMAX NIC
Is possible to envision the first WiMax?-WiFi? vehicular node to be up and running by OCT/10.",hmussman@bbn.com
Kansei: S3.e Demonstration at GEC11 and Experimenter Outreach Release,781,Completed Spiral 3 Tasks,KANSEI,SPIRAL3,task,hmussman@bbn.com,new,2011-08-30T17:43:37-04:00,2011-08-30T17:43:37-04:00,"Dear Harry,
I am writing to report that we have completed task ""Kansei: S3.e Demonstration at GEC11 and Experimenter Outreach"".
Thanks and best,
Hongwei
",hzhang@cs.wayne.edu
Kansei: S3.f Final report and code release Release,782,Completed Spiral 3 Tasks,KANSEI,SPIRAL3,task,hmussman@bbn.com,new,2011-08-30T17:46:18-04:00,2011-08-30T17:46:18-04:00,"Dear Harry,
I am writing to report that we have completed the task ""nsei: S3.f Final report and code release"". The final report is available at http://groups.geni.net/geni/attachment/wiki/KanseiSensorNet/KanseiGenie_FinalReport.pdf, and the released KanseiGenie package is available at http://kansei.cse.ohio-state.edu/KanseiGenie/Downloads/index.php.
Thanks and best,
Hongwei
",hzhang@cs.wayne.edu
Release,845,"improve the GMOC SNAPP, Portal, and protected UI interfaces to meet current experimenter needs",GMOC,SPIRAL4,task,mrmccrac@grnoc.iu.edu,new,2011-12-22T16:49:14-05:00,2012-03-20T15:40:36-04:00,Make improvements to the GMOC SNAPP user interface to support current use cases for mesoscale operators and experimenters.,chaos@bbn.com
WIMXWAYNE: S4.a Demonstration at GEC12 and Experimenter Outreach Release,894,"Completion of miltesone ""MilWIMXWAYNE: S4.a Demonstration at GEC12 and Experimenter Outreach""",WIMXWAYNE,SPIRAL4,task,hmussman@bbn.com,new,2012-04-29T00:39:33-04:00,2012-04-29T00:39:33-04:00,Please see status report http://groups.geni.net/geni/attachment/wiki/WIMXWAYNE/Status%20report%20-%20GEC13.pdf,hzhang@cs.wayne.edu
WIMXWAYNE: S4.b Documentation and Code Release Release,895,"Completion of milestone ""WIMXWAYNE: S4.b Documentation and Code Release""",WIMXWAYNE,SPIRAL4,task,hmussman@bbn.com,new,2012-04-29T00:42:48-04:00,2012-04-29T00:42:48-04:00,Please see status report http://groups.geni.net/geni/attachment/wiki/WIMXWAYNE/Status%20report%20-%20GEC13.pdf,hzhang@cs.wayne.edu
WIMXWAYNE: S4.c Demonstration at GEC13 and Experimenter Outreach Release,896,"Completion of milestone ""WIMXWAYNE: S4.c Demonstration at GEC13 and Experimenter Outreach""",WIMXWAYNE,SPIRAL4,task,hmussman@bbn.com,new,2012-04-29T00:44:12-04:00,2012-04-29T00:44:12-04:00,Please see status report http://groups.geni.net/geni/attachment/wiki/WIMXWAYNE/Status%20report%20-%20GEC13.pdf,hzhang@cs.wayne.edu
WIMXWAYNE: S4.d Documentation and Code Release Release,897,"Completion of milestone ""WIMXWAYNE: S4.d Documentation and Code Release""",WIMXWAYNE,SPIRAL4,task,hmussman@bbn.com,new,2012-04-29T00:46:06-04:00,2012-04-29T00:46:06-04:00,Please see status report http://groups.geni.net/geni/attachment/wiki/WIMXWAYNE/Status%20report%20-%20GEC13.pdf,hzhang@cs.wayne.edu
Release,1039,Stitching slivers with Utah InstaGENI end point requires that capacity must be specified for link,STITCHING,SPIRAL5,defect,duerig@flux.utah.edu,new,2013-06-06T14:03:56-04:00,2013-08-01T11:30:08-04:00,"In stitching scenarios where Utah InstaGENI is the endpoint, requesting a sliver to any other remote (ex GPO IG, KY PG, etc) will result in the following create sliver failure:
{{{
*** ERROR: vtopgen: Cannot mix trivial_ok|emulated with * bw
}}}
This is due to not specifying capacity in the link properties when the endpoint in the stitched sliver is at InstaGENI Utah (not an issue when the endpoints are at PG Utah).
This issue was reported via email and remains unresolved, so it is now being tracked.
On 5/31/13 1:00 PM, Jonathon Duerig wrote:
{{{
This seems nontrivial to me. I've cc'ed geni-dev-utah
to see if others have input.
The problem here is transit stitching. One endpoint
is at IG Utah, the other is at another rack and
Utah PG sits in the middle.
If there is no specified bandwidth for the piece
that flows across Utah PG, it doesn't seem like
we can have a reasonable default. The enforcement
of bandwidth limitations is at the endpoints so
they are the ones who determine what the bandwidth is.
So we are left with either the user explicitly
specifying bandwidth so we have some confidence
that the endpoints are shaping it according to
that bandwidth, or we need a behind the scenes
agreement on defaults which seems tricky to do.
Or am I missing something?
}}}
On 5/31/13 2:53 PM, Robert Ricci wrote:
{{{
This is probably where the mismatch lies;
we make the assumption that limits are enforced
by the endpoints, whereas other circuit
services (ION comes to mind) enforce bandwidth
limits themselves, within the network.
}}}
",lnevers@bbn.com
Release,1044,Duplicate IP addresses configured in Utah PG to InstaGENI Utah sliver with multiple links,STITCHING,SPIRAL5,defect,duerig@flux.utah.edu,new,2013-06-07T09:11:22-04:00,2013-08-01T11:30:35-04:00,"This problem was reported on 5/23 and is now being tracked in this ticket.
When a stitched sliver is created that includes 1 VM @PG Utah and 1 VM @IG Utah with two links between the VMs, the resulting VM interfaces include duplicate IP addresses.
The RSpec requests 2 interface for each VM:
- PG (if0=192.168.4.1,if1=192.168.5.1)
- IG (if0=192.168.4.2,if1=192.168.5.2)
The allocated VMs have 2 interface configured as follows:
- PG (if0=192.168.4.1,if1=192.168.1.1)
- IG (if0=192.168.4.2,if1=192.168.4.2)
The RSpec request:
{{{
}}}
Interfaces found on pg-utah VM:
{{{
[lnevers@pg-utah ~]$ /sbin/ifconfig
eth775 Link encap:Ethernet HWaddr 02:60:B3:63:20:C3
inet addr:192.168.4.1 Bcast:192.168.4.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:26 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1192 (1.1 KiB) TX bytes:0 (0.0 b)
eth885 Link encap:Ethernet HWaddr 02:66:81:E5:78:A2
inet addr:192.168.4.1 Bcast:192.168.4.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:26 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1192 (1.1 KiB) TX bytes:0 (0.0 b)
}}}
Interfaces found on ig-utah VM:
{{{
[lnevers@ig-utah ~]$ /sbin/ifconfig
eth775 Link encap:Ethernet HWaddr 02:A5:7E:F3:2A:CA
inet addr:192.168.4.2 Bcast:192.168.4.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1328 (1.2 KiB) TX bytes:0 (0.0 b)
eth885 Link encap:Ethernet HWaddr 02:C8:71:39:14:45
inet addr:192.168.4.2 Bcast:192.168.4.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1328 (1.2 KiB) TX bytes:0 (0.0 b)
}}}
",lnevers@bbn.com
Release,1048,Requesting link below minimumReservableCapacity does not generate error and allocates default,STITCHING,SPIRAL5,defect,duerig@flux.utah.edu,new,2013-06-10T12:47:02-04:00,2013-06-10T12:47:02-04:00,"The following is the supported range of reservable link capacity via listresources at InstaGENI:
{{{
1000000 1000
}}}
In a scenario where the RSpec requests a value below the configured minimumReservableCapacity, there is '''NO''' error reported and the request is set up with 100000 links. This is the link request used:
{{{
}}}
The Manifest RSpec that show that the links that are assigned to the stitched sliver are not using the requested bandwidth.
{{{
10
100000
l2sc
ethernet
9000
805
805
false
2
10
100000
l2sc
ethernet
9000
805
805
false
null
}}}
Attaching the full log of the createsliver.
",lnevers@bbn.com
Release,1101,"stitching raw-pc at PG or IG requires capacity to be defined unlike xen and openvz, which do not",STITCHING,SPIRAL5,defect,duerig@flux.utah.edu,new,2013-09-06T10:47:05-04:00,2013-09-06T10:47:05-04:00,"
Stitching slivers that includes any raw-pc at PG Utah and IG Utah faila with
""Cannot verify topo"", this is because the raw-pc require a capacity to be defined.
The capacity is not required if Xen or OpenVZ VMs are used.
On 9/6/13 10:35 AM, Jonathon Duerig wrote:
> I will have to look into this and get back to you. Thinking about it further, there is something odd here. ",lnevers@bbn.com
Release,1022,Support openflow controlled VLANs,MAXSCS,SPIRAL5,enhancement,tlehman@maxgigapop.net,new,2013-05-01T09:46:53-04:00,2013-05-01T09:46:53-04:00,"Support VLANs that use the openflowl2sc stitching extension - that is, VLANs that require an Openflow controller for local routing decisions.
How will this interact with the ION AM? With VLANs it must cross at switches that don't do Openflow?
",Aaron Helsinger
Release,1023,Add a call to query the SCS for interconnected AMs,MAXSCS,SPIRAL5,enhancement,tlehman@maxgigapop.net,new,2013-05-01T09:47:57-04:00,2013-05-01T09:47:57-04:00,Add a call to the SCS allowing a tool to discover which aggregates can be connected with a given stitching type.,Aaron Helsinger
Release,1024,Support AM API v3 and negotiation,MAXSCS,SPIRAL5,enhancement,tlehman@maxgigapop.net,new,2013-05-01T09:48:44-04:00,2013-05-01T09:48:44-04:00,"Add support in the stitching service for AM API v3 and full VLAN negotiation. This includes working out the suggested/required workflow for tools and aggregates.
",Aaron Helsinger
Release,1012,Expand the SCS wiki with basic design details,MAXSCS,SPIRAL5,task,tlehman@maxgigapop.net,new,2013-04-11T13:28:49-04:00,2013-06-25T17:38:00-04:00,"The SCS wiki page should be expanded with details to support a review:
- design (key components, algorithms)
- implementation (required software, language, pointer to SW in version control)
- known issues
- etc
",Aaron Helsinger
Release,1025,Require some form of authentication?,MAXSCS,SPIRAL5,task,xyang@maxgigapop.net,assigned,2013-05-01T09:50:20-04:00,2013-05-02T12:24:54-04:00,"Should the Stitching service require authentication with a GENI certificate?
Since the SCS effectively exposes Ad RSpecs, which are currently only available given a valid certificate and user credential from aggregates, it seems the SCS should at least require client authentication with SSL certificates.",Aaron Helsinger
Release,1038,Manifest rspec for PG and IG does not pass rspeclint,STITCHING,SPIRAL5,defect,duerig@flux.utah.edu,new,2013-06-06T12:21:25-04:00,2014-07-16T09:10:55-04:00,"Running rspeclint on a stitched sliver manifest reports failures for PG and IG:
{{{
$ rspeclint stitch-gpo-utah-manifest-rspec-www-emulab-net-protogeni.xml
Line 28: Failed validation with root at element: Schemas validity error :
Element '{http://hpn.east.isi.edu/rspec/ext/stitch/0.1/}capabilities':
This element is not expected. Expected is ( {http://hpn.east.isi.edu/rspec/ext/stitch
/0.1/}switchingCapabilityDescriptor ).Schemas validity error : Element
'{http://hpn.east.isi.edu/rspec/ext/stitch/0.1/}capabilities':
This element is not expected. Expected is ( {http://hpn.east.isi.edu/rspec/ext/stitch
/0.1/}switchingCapabilityDescriptor ).
: stitching
$ rspeclint stitch-gpo-utah-manifest-rspec-geni-am-net-internet2-edu.xml
lnevers@arendia:~/gcf-2.3.1/stitch-test/adman$ rspeclint stitch-gpo-utah-manifest-rspec-utah-geniracks-net-protogeni.xml
Ignoring node rs:vnode with unknown namespace http://www.protogeni.net/resources/rspec/ext/emulab/1
Line 28: Failed validation with root at element: Schemas validity error :
Element '{http://hpn.east.isi.edu/rspec/ext/stitch/0.1/}capabilities':
This element is not expected. Expected is ( {http://hpn.east.isi.edu/rspec/ext/stitch
/0.1/}switchingCapabilityDescriptor ). Schemas validity error : Element
'{http://hpn.east.isi.edu/rspec/ext/stitch/0.1/}capabilities': This element
is not expected. Expected is ( {http://hpn.east.isi.edu/rspec/ext/stitch
/0.1/}switchingCapabilityDescriptor ).
: stitching
}}}
Attaching both manifests.",lnevers@bbn.com
Release,1033,SCS should implement Getversion,MAXSCS,SPIRAL5,task,xyang@maxgigapop.net,assigned,2013-05-30T13:35:19-04:00,2013-06-24T14:17:17-04:00,"The SCS should implement a method !GetVersion, that advertises its version. This can also be used by GENI monitoring to check that the SCS is up and running",Aaron Helsinger
Release,1139,OESS notifications should include id user for provisioned and decommissioned operations,STITCHING,SPIRAL6,defect,luke@grnoc.iu.edu,new,2013-10-09T12:06:39-04:00,2014-06-26T23:09:37-04:00,"Current notification for provisioning a circuit:
{{{
Circuit urn:publicid:IDN+ch.geni.net:ln-prj+slice+wash-2-ny-nobkup:
eb6c8abe-13f3-440e-a0b1-61b6665c230d has been provisioned by
}}}
Current notification for decommissioning a circuit:
{{{
Greetings workgroup GENI-FOAM,
The circuit urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+oessnew:
f3b579e1-a34e-4510-a682-88b12abeeae5 has been decommissioned by
}}}
both shoudl include a user id for the operation.",lnevers@bbn.com
Release,1156,Unable to stitch multiple link from GPO ExoGENI rack,STITCHING,SPIRAL6,defect,lnevers@bbn.com,new,2013-11-22T11:05:42-05:00,2015-05-06T15:58:38-04:00,"When creating a stitched sliver from EG GPO to IG Utah with 2 links between the 2 nodes, the following error is reported:
{{{
10:07:24 INFO stitch.Aggregate: Stitcher doing createsliver at https://bbn-hn.exogeni.net:11443/orca/xmlrpc
10:07:28 ERROR omni: {'output': 'ERROR: Exception encountered:
orca.ndl.NdlException: Interface bbnNet.rdf#BbnNet/IBM/G8052/GigabitEthernet
/1/2/ethernet should be owned by exactly two entities (a node and a connection/vlan),
instead: 4', 'code': {'geni_code': 2}}
10:07:28 INFO stitch.Aggregate: Got AMAPIError doing createsliver lndivy at
: AMAPIError: Error
from Aggregate: code 2: ERROR: Exception encountered: orca.ndl.NdlException: Interface
bbnNet.rdf#BbnNet/IBM/G8052/GigabitEthernet/1/2/ethernet should be owned by exactly
two entities (a node and a connection/vlan), instead: 4.
}}}
The original RSpec (stitch-eg-gpo-ig-gpo-2l.rspec) and the request generated by the stitcher and submitted to EG aggregate (ndivy-createsliver-request-11-exogeni-net-bbnvmsite.xml) are attached to this ticket.
",lnevers@bbn.com
Release,1163,SCS exception for lines topology,STITCHING,SPIRAL6,defect,xyang@maxgigapop.net,new,2014-01-31T08:21:01-05:00,2014-01-31T08:22:48-05:00,"Stitching Computation Service exception reported for the Stitching Confirmation test IG-ST-3 (New Site 3 node linear topology) with the following topology:
GPO IG<-link-> MAX IG<-link-> Utah IG
Creating the above sliver resulted in the following failure:
{{{
ERROR
14:36:08 ERROR stitcher: Exception from slice computation service:
SCS gave error:
}}}
The exception above caused the SCS to crash and be restarted by its watchdog.
A partial solution is available:
On 1/30/14 5:21 PM, Xi Yang wrote:
> I made a temporary patch. Please try again.
> This is not the ultimate solution as I found some deeper issue with the code when
> dealing with multiple point requests.
> It will take me a while to figure it out. But at least it won’t crash again for
> your requests.
Writing ticket to track issue to full resolution
",lnevers@bbn.com
Release,1197,MAX and ION aggregates report Internal API error for out-of-sync credentials sometimes,STITCHING,SPIRAL6,defect,xyang@maxgigapop.net,new,2014-02-11T09:09:19-05:00,2014-02-11T10:46:35-05:00,"Both ION and MAX aggregates have reported the following type of exception:
{{{
14:24:26 INFO stitch.Aggregate: Writing to '/tmp/ig-nyse-ig-miss-createsliver-request-11-ion-internet2-edu.xml'
14:24:26 INFO stitch.Aggregate: Stitcher doing createsliver at http://geni-am.net.internet2.edu:12346
14:24:26 ERROR omni: {'output': ""Internal API error: 'NoneType' object is not iterable"", 'geni_api': 2, 'code': {'am_type': 'sfa', 'geni_code': 5, 'am_code': 5}, 'value': ''}
14:24:26 INFO stitch.Aggregate: Got AMAPIError doing createsliver ig-nyse-ig-miss at : AMAPIError: Error from Aggregate: code 5. sfa AM code: 5: Internal API error: 'NoneType' object is not iterable.
}}}
There is no manifest files for the above failure. The problem does not occur on the next try.
On 2/10/14 4:53 PM, Xi Yang wrote:
{{{
> I looked back into the sfa.log at MAX AM. The trace stack is below:
> 2014-02-06 13:25:17,573 - ERROR - XmlrpcApi.handle has caught Exception BEG TRACEBACK
> Traceback (most recent call last):
> File ""/usr/lib/python2.5/site-packages/sfa/server/xmlrpcapi.py"", line 153, in handle
> result = self.call(source, method, *args)
> File ""/usr/lib/python2.5/site-packages/sfa/server/xmlrpcapi.py"", line 125, in call
> return function(*args)
> File ""/usr/lib/python2.5/site-packages/sfa/util/method.py"", line 79, in __call__
> result = self.call(*args, **kwds)
> File ""/usr/lib/python2.5/site-packages/sfa/methods/CreateSliver.py"", line 58, in call
> result = self.api.manager.CreateSliver(self.api, slice_xrn, creds, rspec, users, options)
> File ""/usr/lib/python2.5/site-packages/sfa/managers/aggregate_manager_max.py"", line 380, in CreateSliver
> ret = self.create_slice(api, slice_xrn, creds, rspec_string, users)
> File ""/usr/lib/python2.5/site-packages/sfa/managers/aggregate_manager_max.py"", line 247, in create_slice
> self.prepare_slice(api, xrn, cred, users)
> File ""/usr/lib/python2.5/site-packages/sfa/managers/aggregate_manager_max.py"", line 175, in prepare_slice
> site = slices.verify_site(hrn, slice_record, peer, sfa_peer)
> File ""/usr/lib/python2.5/site-packages/sfa/plc/plslices.py"", line 288, in verify_site
> sites = self.driver.shell.GetSites(login_base)
> File ""/usr/lib/python2.5/site-packages/sfa/plc/plshell.py"", line 83, in func
> result=getattr(self.proxy, actual_name)(self.plauth, *args, **kwds)
> File ""/usr/share/plc_api/PLC/Shell.py"", line 52, in __call__
> return self.func(*args, **kwds)
> File ""/usr/share/plc_api/PLC/Method.py"", line 97, in __call__
> result = self.call(*args, **kwds)
> File ""/usr/share/plc_api/PLC/Methods/GetSites.py"", line 33, in call
> return Sites(self.api, site_filter, return_fields)
> File ""/usr/share/plc_api/PLC/Sites.py"", line 274, in __init__
> self.selectall(sql)
> File ""/usr/share/plc_api/PLC/Table.py"", line 426, in selectall
> for row in self.api.db.selectall(sql, params):
> File ""/usr/share/plc_api/PLC/PostgreSQL.py"", line 208, in selectall
> labels = [column[0] for column in self.description]
> TypeError: 'NoneType' object is not iterable
>
> This problem is similar to what I have seen with first-timer project. It is an SFA-MyPLC problem that I have no idea how it happens.
> Looks like SFA has some issue when out-of-sync site credential between the Portal clearing house and MyPLC in some rare cases.
> I have no clue on either the cause or the pattern.
}}}
",lnevers@bbn.com
Release,1207,Repeated AddPersonToSite errors,I2AM,SPIRAL6,defect,xyang@maxgigapop.net,new,2014-03-18T07:05:40-04:00,2014-05-21T17:03:58-04:00,"Some people run into repeated instances of the error message ""`AddPersonToSite: Invalid argument: No such site`"" in the same project and slice. And then it stops. And some people do not see this at all, in the same project.
For example, in the GEC19 project (after it had been used repeatedly), people saw this - usually with slice names like 'iastitch2' or 'stitch-9'.",Aaron Helsinger
Release,1157,dragon.maxgigapop.net stitching aggregate url has myplc aggregate_url,STITCHING,SPIRAL6,enhancement,xyang@maxgigapop.net,new,2013-12-03T12:58:38-05:00,2013-12-03T14:10:28-05:00,"This is an enhancement request, which has been previously discussed and is being recorded for the MAX IG Stitching Confirmation Tests.
The current MAX stitching aggregate (dragon.maxgigapop.net) has the aggregate_url http://max-myplc.dragon.maxgigapop.net:12346/.
The Stitching computation service returns the following when stitching through MAX stitching aggregate:
{{{
{ 'aggregate_url': 'http://max-myplc.dragon.maxgigapop.net:12346', <=== here
'aggregate_urn': 'urn:publicid:IDN+dragon.maxgigapop.net+authority+am',
'hop_urn': 'urn:publicid:IDN+dragon.maxgigapop.net+interface+clpk:1-1-2:*',
'import_vlans': False}],
}}}
This is what the user will see from the Stitcher:
{{{
12:47:22 INFO stitcher: Stitched reservation will include resources from these aggregates:
12:47:22 INFO stitcher:
12:47:22 INFO stitcher:
12:47:22 INFO stitcher:
12:47:22 INFO stitcher:
12:47:22 INFO stitch.Aggregate: Writing to '/tmp/IG-ST-1-createsliver-request-11-dragon-maxgigapop-net.xml'
12:47:22 INFO stitch.Aggregate:
Stitcher doing createsliver at http://max-myplc.dragon.maxgigapop.net:12346
12:48:08 INFO stitch.Aggregate: DCN AM : must wait for status ready....
}}}}
This naming may be confusing to experimenter who will see a MyPLC aggregate when stitching to the MAX IG rack. Should consider renaming this URL to avoid confusion.
",lnevers@bbn.com
Release,1200,Preserve schemas in Manifest,I2AM,SPIRAL6,task,xyang@maxgigapop.net,new,2014-03-05T10:43:37-05:00,2014-03-05T12:30:20-05:00,"The ION AM uses a fixed set of schemas in the manifest RSpec it returns. It also preserves elements in the request body that it is ignoring.
The problem is that this means that a request with elements defined in custom schemas will still have the custom elements, without the proper schema declarations.
Reproducable using the request RSpec at http://trac.gpolab.bbn.com/gcf/attachment/ticket/548/excl-of-stitching.xml
Here, the request starts:
{{{
#!xml
}}}
And the ION manifest that comes back starts:
{{{
#!xml
}}}
",Aaron Helsinger
Release,1258,Limit reservations to slice expiration,I2AM,SPIRAL6,,xyang@maxgigapop.net,new,2014-06-05T15:42:38-04:00,2014-06-05T15:42:38-04:00,"The ION / MAX AMs should get the slice expiration from the 'expires' attribute of the slice credential, and limit reservations to be no later than that time.",Aaron Helsinger
Release,1259,SCS should detect bad Ads and skip them,MAXSCS,SPIRAL6,,xyang@maxgigapop.net,new,2014-06-05T17:08:15-04:00,2014-06-05T17:08:15-04:00,"If the SCS gets a 'bad' Ad RSpec, it currently crashes. Instead, catch the exception and skip that topology.
",Aaron Helsinger
Release,1263,AL2S OESS aggregate should support sitching request for `any` VLAN,STITCHING,SPIRAL6,,luke@grnoc.iu.edu,new,2014-06-13T14:28:34-04:00,2014-10-22T06:39:15-04:00,The AL2S OESS Aggregate should support stitching requests for any.,lnevers@bbn.com
Release,1266,Move MOXI CIC network aggregate to production status,GPO,SPIRAL6,,hdempsey@bbn.com,accepted,2014-06-17T10:04:22-04:00,2014-06-17T12:23:55-04:00,"
The GPO has completed OpenFlow testing on the MOXI CIC aggregate.
The common short name for this aggregate will be moxi-of. The common name is used for the GENI portal, Clearinghouse, OMNI (in the GCF), and GPO-configured monitoring displays. It may be used by other tools for consistency.
The GPO will update this ticket after final checks are completed. We will announce this aggregate in a group announcement with other new aggregates before GEC20. ",hdempsey@bbn.com
Release,1272,Advertisement Rspec does not pass rspeclint due to routable_addresses error,PROTOGENI,SPIRAL6,,somebody,new,2014-06-26T22:26:46-04:00,2014-06-26T22:26:46-04:00,"{{{
$ rspeclint rspec-emulab-net.xml
Line 70: Failed validation with root at element: Schemas validity
error : Element '{http://www.protogeni.net/resources/rspec
/ext/emulab/1}rspec_routable_addresses': No matching global
declaration available for the validation root.
: rspec_routable_addresses
}}}",lnevers@bbn.com
Release,1276,AL2S OESS aggregate request for specific link capacity is ignored,STITCHING,SPIRAL6,,luke@grnoc.iu.edu,new,2014-07-22T10:47:20-04:00,2014-10-22T06:35:05-04:00,"Requests for specific link capacity are ignored by AL2S OESS aggregate. Regardless of the capacity requested, the link capacity=""100000"" is always allocated.
Capacity values requests tested:
|| Requested Capacity|| Allocated Capacity||
|| 20000 || 100000 ||
|| 200000 || 100000 ||
|| 100000000(*) || 100000 ||
(*) Maximum reservable according to Advertisement RSpec.",lnevers@bbn.com
Release,1277,AL2S OESS aggregate request for link client_id is ignored,STITCHING,SPIRAL6,,luke@grnoc.iu.edu,new,2014-07-22T10:53:31-04:00,2014-07-22T10:53:31-04:00,"Requests for specific link client_id name are ignored by AL2S OESS aggregate. Regardless of the name requested, the link allocated is always ""link0"".
Example request:
{{{
}}}
Link name allocated from manifest:
{{{
}}}",lnevers@bbn.com
Release,1278,"AL2S OESS getversion does not return geni_am_type, geni_am_urn, and supported extensions",STITCHING,SPIRAL6,,luke@grnoc.iu.edu,reopened,2014-07-22T11:15:25-04:00,2015-06-03T15:58:38-04:00,"The AL2S OESS aggregate returns the following for the getversion command:
{{{
11:07:15 INFO : Substituting AM nickname oess with URL https://foam-oess-stage.grnoc.iu.edu:3626/foam/gapi/2, URN unspecified_AM_URN
11:07:15 INFO : AM oess URN: unspecified_AM_URN (url: https://foam-oess-stage.grnoc.iu.edu:3626/foam/gapi/2) has version:
11:07:15 INFO : { 'foam_version': '000000000000+-default',
'geni_ad_rspec_versions': [ { 'extensions': [ 'http://www.geni.net/resources/rspec/ext/openflow/3'],
'namespace': 'http://www.geni.net/resources/rspec/3',
'schema': 'http://www.geni.net/resources/rspec/3/ad.xsd',
'type': 'GENI',
'version': '3'}],
'geni_api': 2,
'geni_api_versions': { '1': 'https://140.182.44.166:3626/foam/gapi/1',
'2': 'https://140.182.44.166:3626/foam/gapi/2'},
'geni_request_rspec_versions': [ { 'extensions': [ 'http://www.geni.net/resources/rspec/ext/openflow/3'],
'namespace': 'http://www.geni.net/resources/rspec/3',
'schema': 'http://www.geni.net/resources/rspec/3/request.xsd',
'type': 'GENI',
'version': '3'}],
'site_info': { 'admin-email': 'luke@grnoc.iu.edu'}}
11:07:15 INFO : ------------------------------------------------------
}}}
The ""'foam_version': '000000000000+-default'"" does not give any insight into the version of FOAM in use.
Also there is no ""geni_am_type"" information
",lnevers@bbn.com
Release,1280,"AL2S OESS aggregate does not handle the listresources ""--available"" option",STITCHING,SPIRAL6,,luke@grnoc.iu.edu,new,2014-07-24T15:42:15-04:00,2014-10-22T06:41:00-04:00,The listresources option --available is not handled by the AL2S OESS aggregate. When --available is used the aggregate should return only the available resources.,lnevers@bbn.com
Release,1281,Some excludehop combinations can crash SCS,STITCHING,SPIRAL6,,xyang@maxgigapop.net,new,2014-07-30T16:57:33-04:00,2014-07-30T17:02:45-04:00,"This problem was found by Tim.
The following command crashed the SCS:
{{{
tupty@weentop-work:~/rspecs/request/tuptystitch$ stitcher createsliver tuptystitch2 rutgers-ig-bbn-ig.rspec --useSliceMembers --excludehop urn:publicid:IDN+ion.internet2.edu+interface+rtr.wash:xe-0/2/2:*=3730-37327,3734-3739
14:21:29 INFO : Configured logging from file /home/tupty/gcf/gcf-2.6/src/gcf/stitcher_logging.conf
14:21:30 INFO : Reading slice tuptystitch2 credential...
14:21:30 INFO : Slice urn:publicid:IDN+ch.geni.net:gpo-infra+slice+tuptystitch2 expires on 2014-08-15 00:00:00 UTC
14:21:30 INFO : Calling SCS...
14:21:30 ERROR : Exception from slice computation service: [Errno 111] Connection refused
SCS gave error: [Errno 111] Connection refused
}}}
",lnevers@bbn.com
Release,1282,PG/IG aggregates ignore the stitching availVLANRange if the suggested is 'any',STITCHING,SPIRAL6,,duerig@flux.utah.edu,new,2014-07-31T16:31:06-04:00,2014-10-06T09:51:48-04:00,"This problem shows in various test scenarios. Currently is stitcher asks for 'any' from the available VLAN range and the IG (and PG) aggregates ignore the request. Problem has been discussed by Aaron and Johnathan Duerig. Opening ticket to track to resolution.
",lnevers@bbn.com
Release,1286,OpenGENI pages need updates,OPENGENI,SPIRAL6,,somebody,new,2014-09-02T09:48:25-04:00,2014-09-08T08:51:04-04:00,"NOTE: writing as ""GPO"" ticket, but will move to ""OPENGENI"" components as soon as it is created.
The page
http://groups.geni.net/geni/wiki/GENIRacksHome/OpenGENIRacks/DellRackDetails
show rack domain as ""bbn.com"", this is not the case the domain is ""gpolab.bbn.com"".
On the page http://groups.geni.net/geni/wiki/GENIRacksHome/OpenGENIRacks
the link ""GPO OpenGENI Rack Details"" goes to a page titled
""BBN-CAM OpenGENI Rack Installation and Configuration"" the name ""BBN-CAM"" is used through out the pge rather than the site name ""GPO OpenGENI"". Replace all instance of ""BBN-CAM"" with ""GPO"" to be consistent with other aggregate pages.
",lnevers@bbn.com
Release,1294,AL2S OESS aggregate reports wrong sliver_urn in sliverstatus output,STITCHING,SPIRAL6,,luke@grnoc.iu.edu,new,2014-09-11T14:34:00-04:00,2014-10-03T07:50:08-04:00,"The AL2S OESS aggregate sliverstatus returns the following:
{{{
""geni_urn"": ""urn:publicid:IDN+ch.geni.net:ln-test+slice+ig-chic-ig-gpo:b8e51c9a-5213-445f-81ff-d838cf8225c9"",
}}}
The above sliver urn is incorrect, a sliver urn shold use the format:
urn:publicid:IDN++sliver+
Here is an example of what could be used:
urn:publicid:IDN+al2s.internet2.edu+sliver+b8e51c9a-5213-445f-81ff-d838cf8225c9
",lnevers@bbn.com
Release,1295,AL2S OESS manifest does not include any slivers.,STITCHING,SPIRAL6,,luke@grnoc.iu.edu,new,2014-09-11T14:39:28-04:00,2014-09-11T14:39:28-04:00,"The OESS manifest does not list any slivers.
According to Aaron, the problem is that Omni looks for slivers in the manifest RSpec so it can tell the clearinghouse that you have a reservation at this aggregate. But AL2S does not add any sliver_id attribute on the link where it has allocated VLAN tags.
For comparison, here is what MAX sends back in a manifest:
{{{
.....
....
.endpoints' must have length greater than or equal to 2
while trying to validate: {u'selfRef':
u'https://192.1.243.2/info/link/urn_publicid_IDN_bbn-cam-ctrl-1.gpolab.bbn.com_sliver_link7db04f88-0a40-4a7b-9984-0f6836995c69',
u'urn': u'urn:publicid:IDN+bbn-cam-ctrl-1.gpolab.bbn.com+sliver+link7db04f88-0a40-4a7b-9984-0f6836995c69',
u'ts': 1409764638564179L, u'$schema':
u'http://www.gpolab.bbn.com/monitoring/schema/20140501/link#',
u'endpoints': [{u'urn':
u'urn:publicid:IDN+bbn-cam-ctrl-1.gpolab.bbn.com+sliver+interfacea2f6093e-bdc7-4ffa-a30c-493f85c8e7d2',
u'href': u'https://192.1.243.2/info/interfacevlan/urn_publicid_IDN_bbn-cam-ctrl-1.gpolab.bbn.com_sliver_interfacea2f6093e-bdc7-4ffa-a30c-493f85c8e7d2'}],
u'id': u'urn_publicid_IDN_bbn-cam-ctrl-1.gpolab.bbn.com_sliver_link7db04f88-0a40-4a7b-9984-0f6836995c69'}
}}}
3. Once Marshall changes the Clemson OG URL, the monitoring team needs to update ops-monitoring/config/opsconfig.json file",lnevers@bbn.com
Release,1405,SCS is ignoring link type egre,STITCHING,SPIRAL7,,xyang@maxgigapop.net,reopened,2015-02-03T17:30:04-05:00,2015-12-10T11:12:27-05:00,"The topology UCLA -> AL2S -> ION -> NPS was used with a gre tunnel connecting the UCLA and NPS xen hosts:
{{{
}}}
The SCS interprets the link as stitched rather 'egre'. Stitcher should try to:
a) only look at SCS workflow for links that it thinks are stitched links
b) Ignore any stitching extension path for any links that it thinks are not stitched links
This issues is causing failure for all slivers that include gre tunnels that go across ION and AL2S. ION only topologies work.",lnevers@bbn.com
Release,1341,"OpenGENI stitching advertisment should not use V3 URL, not supported by stitching",OPENGENI,SPIRAL7,,somebody,new,2014-10-03T12:47:12-04:00,2014-10-03T12:47:12-04:00,"The current stitching advertisement for GPO OG and Clemson OG uses the V3 AM URL, but V3 is not supported for stitching. This results in the stitching requests generating warning every time about the AM not supporting V3 and switching to V2:
{{{
09:38:32 WARNING : Requested API version 2, but AM https://clemson-clemson-control-1.clemson.edu:5001
uses version 3. Same aggregate talks API v2 at a different URL:
https://clemson-clemson-control-1.clemson.edu:5002
}}}
The current ad from the two sites:
GPO OG:
{{{
}}}
Clemson OG:
{{{
rspec-bbn-cam-ctrl-1-gpolab-bbn-com.xml:
}}}
",lnevers@bbn.com
Release,1342,Move University of Kansas InstaGENI rack to production,GPO,SPIRAL7,,hdempsey@bbn.com,assigned,2014-10-03T13:12:06-04:00,2015-02-18T17:08:59-05:00,"The GPO has completed site confirmation testing on the Kansas InstaGENI rack, and the site administrator has agreed to open the site to experimenters.
The common short name for this rack will be kansas-ig. The common name is used for the GENI portal, clearinghouse, OMNI (in the GCF), and GPO-configured monitoring displays. It may be used by other tools for consistency.
This rack was already listed at Utah, but had not completed production release.
The GPO will update this ticket after when final checks are done. We will announce this rack to GENI mailing lists as part of a group email.
",hdempsey@bbn.com
Release,1346,MAX and ION aggregates do not deletesliver even though success is returned for deletesliver,STITCHING,SPIRAL7,,xyang@maxgigapop.net,accepted,2014-10-09T12:58:18-04:00,2015-05-19T15:39:50-04:00,"In a 9 node grid scenario the MAX aggregate reports to have deleted a sliver, but on the next stitcher createsliver attempt the command fails due to a reservation already existing at MAX for the slice:
Problem is reproducible.
{{{
$ stitcher.py createsliver 9grid
/home/lnevers/gcf-test/stitch-test/9grid/stitch-9grid.rspec
...
10:59:31 INFO : Using SCS at
http://nutshell.maxgigapop.net:8081/geni/xmlrpc
10:59:31 INFO : Calling SCS...
10:59:41 INFO : Multi-AM reservation will include resources from
these aggregates:
10:59:41 INFO :
10:59:41 INFO :
10:59:41 INFO :
10:59:41 INFO :
10:59:41 INFO :
10:59:41 INFO :
10:59:41 INFO :
10:59:41 INFO :
10:59:41 INFO :
10:59:41 INFO :
10:59:41 INFO :
10:59:41 INFO :
10:59:41 INFO :
10:59:41 INFO : Stitcher doing createsliver at ...
11:00:03 INFO : ... Allocation at complete.
11:00:03 INFO : Stitcher doing createsliver at ...
11:00:34 INFO : ... Allocation at complete.
11:00:34 INFO : Stitcher doing createsliver at ...
11:01:12 INFO : ... Allocation at complete.
11:01:13 INFO : Stitcher doing createsliver at ...
11:01:49 INFO : ... Allocation at complete.
11:01:49 INFO : Stitcher doing createsliver at ...
11:02:41 INFO : DCN AM : must wait for status ready....
11:02:41 INFO : Pausing 30 seconds to let circuit become ready...
11:03:19 INFO : Pausing 30 seconds to let circuit become ready...
11:03:59 WARNING : sliverstatus: 4084 is (still) failed at . Delete and retry.
11:03:59 WARNING : sliverstatus: 4085 is (still) changing at . Delete and retry.
11:03:59 WARNING : sliverstatus: 4086 is (still) changing at . Delete and retry.
11:04:07 WARNING : says requested VLAN was unavailable
at
11:04:07 INFO : Will put back in the pool to
allocate. Got: VLAN was unavailable. Retry 2nd time with
new suggested 3108 (not 3214)
11:04:07 INFO : Pausing for 600 seconds for Aggregates to free up
resources...
11:14:07 INFO : Stitcher doing createsliver at ...
11:14:13 INFO : ... Allocation at complete.
11:14:13 INFO : Stitcher doing createsliver at ...
11:14:24 ERROR : {'output': ': CreateSliver: Existing record:
urn:publicid:IDN+ch.geni.net:ln-test+slice+9grid, ', 'geni_api': 2,
'code': {'am_type': 'sfa', 'geni_code': 7, 'am_code': 7}, 'value': ''}
11:14:24 WARNING : Stitching failed but will retry: Reservation request
impossible at . You already have a reservation here in
this slice: AMAPIError: Error from Aggregate: code 7. sfa AM code: 7: :
CreateSliver: Existing record: urn:publicid:IDN+ch.geni.net:...
11:14:24 INFO : Deleting existing reservations...
11:14:24 INFO : Doing deletesliver at ...
11:15:20 INFO : Deleted reservation at .
11:15:20 INFO : Doing deletesliver at ...
11:15:42 INFO : Deleted reservation at .
11:15:42 INFO : Doing deletesliver at ...
11:16:37 INFO : Deleted reservation at .
11:16:37 INFO : Doing deletesliver at ...
11:17:32 INFO : Deleted reservation at .
11:17:32 INFO : Doing deletesliver at ...
11:18:28 INFO : Deleted reservation at .
11:18:28 INFO : Calling SCS for the 2nd time...
11:18:29 ERROR : Root cause error: Reservation request impossible at
. You already have a reservation here in this slice:
AMAPIError: Error from Aggregate: code 7. sfa AM code: 7: :
CreateSliver: Existing record: urn:publicid:IDN+ch.geni.net:...
Reservation request impossible at . You already have a
reservation here in this slice: AMAPIError: Error from Aggregate: code
7. sfa AM code: 7: : CreateSliver: Existing record:
urn:publicid:IDN+ch.geni.net:... which caused
StitchingServiceFailedError: Error from Stitching Service: code 3: MxTCE
ComputeWorker return error message '
Action_ProcessRequestTopology_MP2P::Finish() Cannot find the set of
paths for the RequestTopology. '.
}}}
Attaching stitcher log and request rspec for MAX",lnevers@bbn.com
Release,1348,Handle OSCARS transient states,I2AM,SPIRAL7,,xyang@maxgigapop.net,new,2014-10-10T11:06:56-04:00,2014-10-10T11:06:56-04:00,"Found a case where sliverstatus
- is missing 1 of 2 circuits
- says that 1 circuit failed, but says the overall status succeeded.
Attaching some relevant documents",Aaron Helsinger
Release,1354,SCS checks for capacity return the same error as unknown paths.,STITCHING,SPIRAL7,,xyang@maxgigapop.net,new,2014-11-13T17:01:37-05:00,2014-11-13T17:01:37-05:00,"Writing ticket to track issue discussed in email:
On Nov 13, 2014, at 4:47 PM, Luisa Nevers wrote:
{{{
The SCS returns the error 'Cannot find the set of paths for the
RequestTopology ' when an unreasonable link capacity is requests
(ex. capacity=""20000000"").
}}}
On 11/13/14 4:51 PM, Xi Yang wrote:
{{{
The path computation is a fairly complex process. The constraints
are tangled together. It is not always possible to tell which
constraint kills the request.
In some cases, we may be able to do that. But it is non-trivial.
So I will not bother for now.
}}}",lnevers@bbn.com
Release,1355,SCS hang with timed out threads when a request is submitted with large number of nodes,STITCHING,SPIRAL7,,xyang@maxgigapop.net,accepted,2014-11-17T13:01:27-05:00,2014-12-12T08:40:45-05:00,"In a scenario where an 11 node Al2S star topology is submitted, the SCS becomes unresponsive and subsequent requests are not addressed.
Here is an example where the initial request is submitted:
{{{
10:11:32 INFO : Using SCS at
http://nutshell.maxgigapop.net:8081/geni/xmlrpc
10:11:32 INFO : Calling SCS...
StitchingServiceFailedError: Error from Stitching Service: code 2:
Timeout: no response received from computing core!
}}}
and a subsequent requests fail:
{{{
10:16:30 INFO : Using SCS at
http://nutshell.maxgigapop.net:8081/geni/xmlrpc
10:16:30 INFO : Calling SCS...
ERROR
}}}
According to Xi:
{{{
On 11/17/14 12:46 PM, Xi Yang wrote:
When this happens, SCS has become unstable. This is usually because
of a number of timed out compute threads stuck internally.
I need to fix this as a bug. Or monitor this and try restart SCS when this occurs.
}}}",lnevers@bbn.com
Release,1356,Deleting a failed slivers at ION does not clean up circuits that had successed,STITCHING,SPIRAL7,,xyang@maxgigapop.net,new,2014-12-09T10:01:38-05:00,2015-02-09T12:49:45-05:00,"Hello,
While working on reproducing ticket #1353, noticed a problem with OSCAR circuits not being deleted. The sequence used to see the problem:
1. In GENI portal, create stitched sliver ""iozcelik1"" and leave it running.
2. With omni create a stitched sliver ""lnilker"" using the same RSpec as portal.
3. The omni sliver fails due to lack of resources at GPO, stitcher request delete at all sites.
4. Deleted portal sliver ""iozcelik1""
5. Create the omni sliver again ""lnilker"", at this point I can see that ION has the old sliver record for the sliver that should have been deleted.
6. Checked sliver status for the ION ""lnilker"" sliver:
{{{
""geni_urn"": ""urn:publicid:IDN+ion.internet2.edu+sliver+lnilker_vlan_ion.internet2.edu-143451"",
""geni_error"": """",
""geni_status"": ""ready""
""geni_urn"": ""urn:publicid:IDN+ion.internet2.edu+sliver+lnilker_vlan_ion.internet2.edu-143461"",
""geni_error"": ""VLAN cancelled by rollback from contingent failure"",
""geni_status"": ""failed""
""geni_urn"": ""urn:publicid:IDN+ion.internet2.edu+sliver+lnilker_vlan_ion.internet2.edu-143471"",
""geni_error"": ""VLAN PCE(PCE_CREATE_FAILED): 'There are no VLANs available on link ion.internet2.edu:rtr.newy:et-5/0/0:gpo-ig on reservation ion.internet2.edu-143471 in VLAN PCE'"",
""geni_status"": ""failed""
""geni_urn"": ""urn:publicid:IDN+ion.internet2.edu+sliver+lnilker_vlan_ion.internet2.edu-143481"",
""geni_error"": ""VLAN cancelled by rollback from contingent failure"",
""geni_status"": ""failed""
""geni_urn"": ""urn:publicid:IDN+ion.internet2.edu+sliver+lnilker_vlan_ion.internet2.edu-143491"",
""geni_error"": ""VLAN cancelled by rollback from contingent failure"",
""geni_status"": ""failed""
}}}
7. Checked OSCAR web interface and found the active GRI ion.internet2.edu-143451.
8. Issued a deletesliver for ""lnilker"" at ion aggregate.
9. Issues sliverstatus at ION to verify sliver cleanup. Result ""No existing record"" as expected.
10. Checked OSCAR, and the GRI ion.internet2.edu-143451 is still active and not deleted.
Looking at 6-10 above, one can see if the a sliver has an overall status of ""failed"" but some of the circuits are ""ready"" requesting the deletion of the sliver does not clean up the circuit which was active.
Assigning it to Xi, please re-assign if this is an ION problem disagree.
Luisa
",lnevers@bbn.com
Release,1357,SCS does not suggest the same VLAN tag for cross-connect hops that connect AL2S to ION,STITCHING,SPIRAL7,,xyang@maxgigapop.net,accepted,2014-12-10T14:34:18-05:00,2015-01-20T11:57:24-05:00,"The SCS does not suggest the same VLAN tag for hops that connect AL2S to ION. This problem was first found by Tim, and is reproducible (2 out of 5 requests show this problem).
Following is an Email from Aaron which describes the problem.
On 12/10/14 12:58 PM, Aaron Helsinger wrote:
I believe there is a bug in the SCS, in the way it calculates dependencies when a circuit has an AL2S/ION connection.
First, I'm assuming that if 2 routers both support VLAN translation and are connected to each other, that it remains true that they must agree on the VLAN tag that will be used for the connection between them.
More concretely:
When an AL2S hop connects to an ION hop both must use the same VLAN tag.
Therefore, one of those hops should import VAN tags from the other. One should depend on the other.
But that is not what the SCS does. The SCS makes each of those hops independent of the other. As a result, the SCS sometimes picks different VLAN tags for those 2 hops. Even if it happens to pick matching VLAN tags for those 2 hops, when stitcher has to retry a reservation at one of those AMs because that VLAN tag failed, stitcher does not know that the other AM needs to change. As a result, the 2 hops end up with different VLAN tags. And traffic cannot flow on the circuit.
For example:
Luisa requested a single circuit from IG GPO via AL2S to IG Missouri
{{{
12/10 11:07:30 DEBUG stitchhandler.py:1405 Calling SCS with options
{'geni_workflow_paths_merged': True, 'geni_routing_profile': {'Olink':
{'hop_exclusion_list': ['urn:publicid:IDN+instageni.rnet.missouri.edu+interface+procurve2:1.19',
'urn:publicid:IDN+ion.internet2.edu+interface+rtr.atla:xe-0/3/0:al2s',
'urn:publicid:IDN+ion.internet2.edu+interface+rtr.chic:et-10/0/0:al2s',
'urn:publicid:IDN+ion.internet2.edu+interface+rtr.clev:et-5/0/0:al2s',
'urn:publicid:IDN+ion.internet2.edu+interface+rtr.hous:xe-0/1/3:al2s',
'urn:publicid:IDN+ion.internet2.edu+interface+rtr.kans:xe-0/0/3:al2s',
'urn:publicid:IDN+ion.internet2.edu+interface+rtr.losa:et-10/0/0:al2s',
'urn:publicid:IDN+ion.internet2.edu+interface+rtr.newy:et-5/0/0:al2s',
'urn:publicid:IDN+ion.internet2.edu+interface+rtr.salt:xe-0/1/1:al2s',
'urn:publicid:IDN+ion.internet2.edu+interface+rtr.seat:et-5/0/0:al2s']}}}
}}}
The SCS return shows a circuit in 2 separate segments: ION to GPO IG and AL2S to Missouri IG.
{{{
12/10 11:07:31 DEBUG stitchhandler.py:1649 SCS gave hop urn:publicid:IDN+instageni.gpolab.bbn.com+interface+procurve2:5.24.gpo-ig suggested VLAN 3721, avail: '3706-3732,3746-3749'
12/10 11:07:31 DEBUG stitchhandler.py:1649 SCS gave hop urn:publicid:IDN+ion.internet2.edu+interface+rtr.newy:et-5/0/0:gpo-ig suggested VLAN 3721, avail: '3706-3732,3746-3749'
12/10 11:07:31 DEBUG stitchhandler.py:1649 SCS gave hop urn:publicid:IDN+ion.internet2.edu+interface+rtr.wash:et-9/0/0:al2s suggested VLAN 3930, avail: '3900-4000'
12/10 11:07:31 DEBUG stitchhandler.py:1649 SCS gave hop urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.wash.net.internet2.edu:eth5/2:* suggested VLAN 3995, avail: '3950-4000'
}}}
The above 2 lines indicate the bug.
These 2 hops face each other, but the SCS picked a different VLAN tag for each.
Tim: I also see that the available range does not agree. This is a little surprising.
{{{
12/10 11:07:31 DEBUG stitchhandler.py:1649 SCS gave hop urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.colu4.net.internet2.edu:eth1/2:missouri-ig suggested VLAN 1165, avail: '1161-1165'
12/10 11:07:31 DEBUG stitchhandler.py:1649 SCS gave hop urn:publicid:IDN+instageni.rnet.missouri.edu+interface+procurve2:1.19.al2s suggested VLAN 1165, avail: '1161-1165'
}}}
The bug is further seen in the workflow/dependencies from the SCS:
{{{
12/10 11:07:31 DEBUG stitchhandler.py:1664 SCS workflow:
{ '##all_paths_merged##': { 'dependencies': [ { 'aggregate_url': 'http://geni-am.net.internet2.edu:12346',
'aggregate_urn': 'urn:publicid:IDN+ion.internet2.edu+authority+am',
'dependencies': [ { 'aggregate_url': 'https://boss.instageni.gpolab.bbn.com:12369/protogeni/xmlrpc/am',
'aggregate_urn': 'urn:publicid:IDN+instageni.gpolab.bbn.com+authority+cm',
'hop_urn': 'urn:publicid:IDN+instageni.gpolab.bbn.com+interface+procurve2:5.24.gpo-ig',
'import_vlans': False}],
'hop_urn': 'urn:publicid:IDN+ion.internet2.edu+interface+rtr.newy:et-5/0/0:gpo-ig',
'import_vlans': True},
{ 'aggregate_url': 'http://geni-am.net.internet2.edu:12346',
'aggregate_urn': 'urn:publicid:IDN+ion.internet2.edu+authority+am',
'hop_urn': 'urn:publicid:IDN+ion.internet2.edu+interface+rtr.wash:et-9/0/0:al2s',
'import_vlans': False},
{ 'aggregate_url': 'http://foam-oess-stage.grnoc.iu.edu:3626/foam/gapi/2',
'aggregate_urn': 'urn:publicid:IDN+al2s.internet2.edu+authority+am',
'hop_urn': 'urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.wash.net.internet2.edu:eth5/2:*',
'import_vlans': False},
}}}
Above we see that the ION hop facing AL2S does not import VLANs from anyone. This tells stitcher that it is free to change the VLAN tag used here independent of what tag is used by any other hop whatsoever. Similarly, the AL2S hop facing ION has no dependencies and picks its own VLAN tag. This seems wrong.
{{{
{ 'aggregate_url': 'http://foam-oess-stage.grnoc.iu.edu:3626/foam/gapi/2',
'aggregate_urn': 'urn:publicid:IDN+al2s.internet2.edu+authority+am',
'dependencies': [ { 'aggregate_url': 'https://www.instageni.rnet.missouri.edu:12369/protogeni/xmlrpc/am',
'aggregate_urn': 'urn:publicid:IDN+instageni.rnet.missouri.edu+authority+cm',
'hop_urn': 'urn:publicid:IDN+instageni.rnet.missouri.edu+interface+procurve2:1.19.al2s',
'import_vlans': False}],
'hop_urn': 'urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.colu4.net.internet2.edu:eth1/2:missouri-ig',
'import_vlans': True}]},
}}}
Now, there remains a question of what heuristics we should use to decide which AM's hop imports VLANs from which other. Presumably we would use some rule based on the size of the available VLAN tag range, or the # of hops being requested at that AM, or whether other AMs depend on that AM?
I leave that to you.",lnevers@bbn.com
Release,1416,Move MOXI InstaGENI rack to production,GPO,SPIRAL7,,hdempsey@bbn.com,accepted,2015-02-18T17:18:50-05:00,2015-02-18T17:19:09-05:00,"
The GPO has completed site confirmation testing on the MOXI InstaGENI rack, and the site administrator has agreed to open the site to experimenters.
The common short name for this rack will be moxi-ig. The common name is used for the GENI portal, clearinghouse, OMNI (in the GCF), and GPO-configured monitoring displays. It may be used by other tools for consistency.
The GPO will update this ticket after final checks are done. ",hdempsey@bbn.com
Release,1417,Move Stanford InstaGENI rack to production,GPO,SPIRAL7,,hdempsey@bbn.com,accepted,2015-02-18T17:22:41-05:00,2015-02-18T17:53:13-05:00,"The GPO has completed site confirmation testing on the Stanford InstaGENI rack, and the site administrator has agreed to open the site to experimenters.
The common short name for this rack will be stanford-ig. The common name is used for the GENI portal, clearinghouse, OMNI (in the GCF), and GPO-configured monitoring displays. It may be used by other tools for consistency.
The GPO will update this ticket after final checks are done.
",hdempsey@bbn.com
Release,1418,Move University of Kentucky InstaGENI rack to production,GPO,SPIRAL7,,hdempsey@bbn.com,accepted,2015-02-18T17:27:40-05:00,2015-02-18T17:30:20-05:00,"The GPO has completed site confirmation testing on the University of Kentucky InstaGENI rack, and the site administrator has agreed to open the site to experimenters.
The common short name for this rack will be uky-ig. The common name is used for the GENI portal, clearinghouse, OMNI (in the GCF), and GPO-configured monitoring displays. It may be used by other tools for consistency.
The GPO will update this ticket after final checks are done.
",hdempsey@bbn.com
Release,1419,Move CENIC InstaGENI rack to production,GPO,SPIRAL7,,hdempsey@bbn.com,accepted,2015-02-18T17:33:10-05:00,2015-02-18T17:33:25-05:00,"the GPO has completed site confirmation testing on the CENIC InstaGENI rack, and the site administrator has agreed to open the site to experimenters.
The common short name for this rack will be cenic-ig. The common name is used for the GENI portal, clearinghouse, OMNI (in the GCF), and GPO-configured monitoring displays. It may be used by other tools for consistency.
The GPO will update this ticket after final checks are done.",hdempsey@bbn.com
Release,1420,Move U Chicago InstaGENI rack to production,GPO,SPIRAL7,,hdempsey@bbn.com,accepted,2015-02-18T17:36:42-05:00,2015-02-18T17:36:48-05:00,"The GPO has completed site confirmation testing on the University of Chicago InstaGENI rack, and the site administrator has agreed to open the site to experimenters.
The common short name for this rack will be uchicago-ig. The common name is used for the GENI portal, clearinghouse, OMNI (in the GCF), and GPO-configured monitoring displays. It may be used by other tools for consistency.
The GPO will update this ticket after final checks are done.
",hdempsey@bbn.com
Release,1421,Move Clemson OpenGENI rack to production,GPO,SPIRAL7,,hdempsey@bbn.com,accepted,2015-02-18T17:39:25-05:00,2015-03-10T14:53:57-04:00,"The GPO has completed site confirmation testing on the Clemson OpenGENI rack, and the site administrator has agreed to open the site to experimenters.
The common short name for this rack will be clemson-og. The common name is used for the GENI portal, clearinghouse, OMNI (in the GCF), and GPO-configured monitoring displays. It may be used by other tools for consistency.
The GPO will update this ticket after final checks are done.
",hdempsey@bbn.com
Release,1422,Move GPO OpenGENI rack to production,GPO,SPIRAL7,,hdempsey@bbn.com,accepted,2015-02-18T17:41:31-05:00,2015-02-18T17:41:35-05:00,"The GPO has completed site confirmation testing on the GPO OpenGENI rack, and the site administrator has agreed to open the site to experimenters.
The common short name for this rack will be gpo-og. The common name is used for the GENI portal, clearinghouse, OMNI (in the GCF), and GPO-configured monitoring displays. It may be used by other tools for consistency.
The GPO will update this ticket after final checks are done.
",hdempsey@bbn.com
Release,1456,SCS mxtce daemon memory leak,STITCHING,SPIRAL7,,xyang@maxgigapop.net,accepted,2015-03-20T11:07:03-04:00,2015-06-29T15:45:40-04:00,"As reported by Chad Kotil:
There appears to be a memory leak in the SCS service.
Today we received a low memory alarm for the host running SCS.
[ckotil@geni-scs ~]$ ps aux | grep mxt
ckotil 5901 0.0 0.0 103248 840 pts/2 S+ 12:55 0:00 grep mxt
root 8873 19.2 85.6 4375164 3351352 ? Ssl Mar18 477:43
/usr/local/geni-scs//src/main/mxtce -d
The host only has 4gb of memory, and the SCS was using about 85% of that.
After restart:
[ckotil@geni-scs ~]$ ps aux | grep mxt
root 5971 33.0 3.5 563308 137288 ? Ssl 12:56 0:00
/usr/local/geni-scs/src/main/mxtce -d
ckotil 5978 0.0 0.0 103248 840 pts/2 S+ 12:56 0:00 grep mxt
10 minutes later:
[ckotil@geni-scs ~]$ ps aux | grep mxt
root 5971 19.1 6.8 760044 268248 ? Ssl 12:56 1:36
/usr/local/geni-scs/src/main/mxtce -d
ckotil 6486 0.0 0.0 103248 840 pts/2 S+ 13:04 0:00 grep mxt
",xyang@maxgigapop.net
Release,1457,AL2S aggregate does not return updated expiration date for listresources command,STITCHING,SPIRAL7,,luke@grnoc.iu.edu,new,2015-03-31T10:50:58-04:00,2015-06-03T15:59:31-04:00,"When a sliver is renewed at the al2s aggregate the change is applied and all commands show the new date (ex. sliverstatus).
There is one exception, the listresources command returns the original date and not the updated expiration date. Here is an example that show how the command show different expiration dates for a slice:
The sliverstatus output show the renew date ""2015-05-30""
{{{
$ stitcher sliverstatus triangle -a al2s
.....
10:46:04 INFO : {
""geni_status"": ""ready"",
""geni_urn"": ""urn:publicid:IDN+ch.geni.net:ln-test+slice+triangle:1bc9e85e-146c-4991-a4e9-96c5f3a5dee9"",
""foam_pend_reason"": [],
""foam_expires"": ""2015-05-30 00:00:00+00:00"",
""geni_resources"": [
{
""geni_urn"": ""urn:publicid:IDN+ch.geni.net:ln-test+slice+triangle:1bc9e85e-146c-4991-a4e9-96c5f3a5dee9"",
""geni_error"": """",
""geni_status"": ""ready""
}
],
""foam_status"": ""approved""
}
Slice urn:publicid:IDN+ch.geni.net:ln-test+slice+triangle expires on 2015-05-30 00:00:00 UTC
Slice triangle at AM al2s has overall SliverStatus: ready.
}}}
While the listresources on same sliver shows the expiration date of ""2015-03-11"":
{{{
$ stitcher listresources triangle -a al2s
....
10:47:34 INFO : Reservation at al2s in slice triangle expires at 2015-03-11 18:08:33 (UTC).
Queried resources for slice triangle from 1 of 1 aggregate(s).
Reservation at al2s in slice triangle expires at 2015-03-11 18:08:33 (UTC).
}}}
Note that 2015-03-11 was the initial expiration date for the sliver, the sliver has been renewed twice and neither of those expiration dates show.
This is only a problem with the AL2S FOAM aggregate.",lnevers@bbn.com
Release,1459,Move University of Tennessee at Chattanooga InstaGENI rack to production,GPO,SPIRAL7,,somebody,new,2015-04-24T14:36:02-04:00,2015-04-24T14:36:02-04:00,"The GPO has completed site confirmation testing on the University of University of Tennessee at Chattanooga InstaGENI rack, and the site administrator has agreed to open the site to experimenters.
The common short name for this rack will be utc-ig, and utc-ig-of is the common short name for the OpenFlow aggregate in the rack. The common name is used for the GENI portal, clearinghouse, OMNI (in the GCF), and GPO-configured monitoring displays. It may be used by other tools for consistency.
This rack as already been listed at Utah, and the GPO is adding it to the portal.
The GPO will update this ticket after final checks are done.
",hdempsey@bbn.com
Release,1482,Wisconsin CloudLab missing Advertisement for --available resources,CLOUDLAB,SPIRAL7,,somebody,new,2015-05-20T17:00:35-04:00,2015-05-20T17:00:35-04:00,"Wisconsin !CloudLab fails to return an Advertisement when --available option is uses with listresources. Here are the errors reported:
{{{
16:27:03 INFO : (PG log url - look here for details on any failures:
https://www.wisc.cloudlab.us/spewlogfile.php3?logfile=ffa96ff1fe7fc91db205859e592de300)
16:27:03 WARNING : No valid RSpec returned: Invalid RSpec? Starts:
}}}
The above failure is probably due to these failures:
{{{
$ rspeclint rspec-wisc-cloudlab-us.xml
Failed to parse XML document at location rspec-wisc-cloudlab-us.xml: rspec-wisc-cloudlab-us.xml:4: parser error : Comment not terminated