Ticket #370 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

WSU ORCA5 upgrade

Reported by: ibaldin Owned by: ibaldin
Priority: major Milestone:
Component: Don't Know Version: baseline
Keywords: Cc: vjo, jonmills, ckh, ttoll, anirban

Description (last modified by ibaldin) (diff)

Upgrade to ORCA5 (mysql, code, RDF description of the site, DAR)

Add to site description the stitching VLAN information

* Link ID: (TBD by configuration you all will do)
* Remote Link ID:
urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.clev.net.internet2.edu:e3/2:wsu-eg
* VLAN IDs: 1831-1840

Add wsuNet vlan delegation to config.xml

Create a security association with new GENI portal

Attachments

cacert.pem (0.9 kB) - added by ttoll 5 years ago.
cacert file to be placed on idp for portal testing

Change History

  Changed 5 years ago by ibaldin

Fix RDF topology so path-finding works

  Changed 5 years ago by yxin

I also need following information:

1. Port assignment between OF and Vlan mode for both bare-metal and VM;

2. GENI meso-scale VLAN: 1853?

  Changed 5 years ago by ibaldin

  • cc ckh added

  Changed 5 years ago by ckh

Wrt #1, I was under the impression that we currently don't support OpenFlow? to traditional Ethernet slices with the same rack.
Wrt #2, at WSU, the mesoscale Vlan range includes 1831-1840.

  Changed 5 years ago by yxin

site RDF are ready for test, need to confirm the hybrid port assignment, right now:
1. BM: of-data:9, 13; vlan-data: 49-50
2. worker: of-data: 23-30; clan-data: 41-48
3. GENI meso-scale VLAN: 1853 (chris, just want to make sure: are vlan 1831-1840 for Instageni stitching? are they the same thing for mess-scale clans which are supposed to be static?)

  Changed 5 years ago by ckh

Vlans 1831-1840 will be used for stitching. I received clarification from Tim at GPO and there will not be a Mesoscale Vlan for WSU. It's unlikely there will be anymore (for UMass and UAF), but stay tuned. They're resource constrained.

  Changed 5 years ago by ibaldin

Needs an update of RDF from the repo (r6886) and testing for connectivity to the rest of ExoGENI.

Needs upgrade to ORCA5.

Our own native stitching will use

urn:ogf:network:domain=al2s.net.internet2.edu:node=sdn-sw.clev.net.internet2.edu:port=e3/2:link=*

Vlans: 1821-1830

Both geni stitching and our stitching appear to be in RDF.

  Changed 5 years ago by ibaldin

Needs RDF update from r6898

  Changed 5 years ago by ibaldin

  • cc ttoll added
  • description modified (diff)

Create a security association between WSU and the new GENI Portal. The trusted jks in WSU's controller configuration (geni-trusted.jks) requires adding a certificate from the portal. This jks is read once when the controller is started.

  Changed 5 years ago by ibaldin

  • cc anirban added

  Changed 5 years ago by ibaldin

1831-1840 is GENI stitching
1821-1830 is our stitching.

config.xml should be changed to have 20 vlans in net am pool. 10 of them should be delegated to ndl-broker, 10 to local broker.

  Changed 5 years ago by ibaldin

this rack does not have mesoscale or other static vlans

follow-up: ↓ 14   Changed 5 years ago by ibaldin

Current state:

  1. TODO: Quantum plugin on worker nodes is not configured for the new network names (vlan-data, of-data, vlan-storage).
  1. TODO: /etc/orca/am+broker/config/xcat.site.properties does not have the correct network names assigned to interfaces.
  1. TODO: quantum seems to have vlan 1853 - there is no mesoscale vlan in this rack (even though it is also defined in the RDF). Not really a problem, but we should unconfigure quantum
  1. TODO: we need the certificate from the new portal to add it to geni-trusted.jks on the controller (from Tim)
  1. DONE: I added the delegation of GENI stitching vlans to local broker from net am in config.xml
  1. TODO: Switch may not yet be properly configured for the hybrid

in reply to: ↑ 13   Changed 5 years ago by jonmills

Replying to ibaldin:

Current state:

1. TODO: Quantum plugin on worker nodes is not configured for the new network names (vlan-data, of-data, vlan-storage).

Fixed.


2. TODO: /etc/orca/am+broker/config/xcat.site.properties does not have the correct network names assigned to interfaces.

Fixed.


3. TODO: quantum seems to have vlan 1853 - there is no mesoscale vlan in this rack (even though it is also defined in the RDF). Not really a problem, but we should unconfigure quantum

Fixed.


4. TODO: we need the certificate from the new portal to add it to geni-trusted.jks on the controller (from Tim)

5. DONE: I added the delegation of GENI stitching vlans to local broker from net am in config.xml

6. TODO: Switch may not yet be properly configured for the hybrid

  Changed 5 years ago by ibaldin

Chris,

Is there anything that needs to be done to the rack dataplane switch?

Currently the OF port range is defined as 9, 13, 23-30 and traditional vlans are on 49,50, 41-48 and egress port is 64.

Changed 5 years ago by ttoll

cacert file to be placed on idp for portal testing

  Changed 5 years ago by ibaldin

I added the cert to the geni-trusted.jks on wsu-hn for the controller config. Waiting for switches to be unwedged (ckh working on it) before testing.

  Changed 5 years ago by ckh

The port assignments are very different. Hopefully, it'll work.

  Changed 5 years ago by ibaldin

Does your sense of the port assignment from the infrastructure match what I said in the ticket?

Is the dataplane switch unwedged?

  Changed 5 years ago by ckh

Yes, but port 37 (openflow side) is connected to port 38 (Ethernet side). And, the upstream port is port 64.

  Changed 5 years ago by ckh

The switches are ready to test.

  Changed 5 years ago by ibaldin

Ports 37,38 currently aren't reflected in the topo description. Starting things up to test.

  Changed 5 years ago by ibaldin

VMs don't come up. Worth looking at /var/log/orca/handler-vm.log

  Changed 5 years ago by ibaldin

OK, vms come up, links (VLANs) come up. Ready for more testing. Not yet delegated to exo-sm pending more thorough intra-rack testing.

  Changed 5 years ago by ibaldin

Updated RDF to change the name of storage network to vlan-storage. This will likely same issues with storage as TAMU, described in #374 and #375

  Changed 5 years ago by ibaldin

Need to check the amount of sliverable storage vs. RDF and correct the latter if necessary

  Changed 5 years ago by ibaldin

Having OSCARS issues (URN issue?)

Reservation 8fcb4fa7-6d81-4e8c-812e-21a092cd0a0e (Slice pruth.dumbell.1) is in state [Failed,None]

Last lease update: all units failed priming: Error code 1 during join for unit: B8E9F47B with message: Unable to create circuit: start-oscars-v06.sh: OSCARS did not return a GRI to createReservation request due to: "Error: Generic exception: OSCARSA reservation failed with status FAILED due to There are no VLANs available on link al2s.net.internet2.edu:sdn-sw.clev.net.internet2.edu:e3/2:lab-idc on reservation al2s.net.internet2.edu-35251 in VLAN PCE ", exiting

  Changed 5 years ago by yxin

The urn in ref is the one told by Chris, (......link=*), however,
from the log, there was an urn remap on the WSU side: from ...:link=* to ...:link=lab-idc:

[echo] after remap from urn:ogf:network:domain=al2s.net.internet2.edu:node=sdn-sw.houh.net.internet2.edu:port=e7/1:link=*/881 to urn:ogf:network:domain=al2s.net.internet2.edu:node=sdn-sw.clev.net.internet2.edu:port=e3/2:link=lab-idc/1821 for 86400 (sec) with bw=10000000

  Changed 5 years ago by ibaldin

Yes, the URN is already taken care of. Chris thinks they did not define our VLAN range on that interface properly.

  Changed 5 years ago by ibaldin

  • status changed from new to closed
  • resolution set to fixed

Connectivity added, closing ticket.

Note: See TracTickets for help on using tickets.