Ticket #89 (closed task: wontfix)

Opened 10 years ago

Last modified 9 years ago

Develop NLR Sherpa site policy

Reported by: ibaldin Owned by: ibaldin
Priority: major Milestone: GEC7
Component: ORCA: Policies and their components Version:
Keywords: Cc:

Description

Based on the driver/handler develop a site policy that can reserve X number of tags at startup and then creates a delegation to the broker with the returned IDs. The important thing to keep in mind is at startup we must check if we are already holding a reservation to these tags.

Change History

Changed 9 years ago by ibaldin

  • status changed from new to accepted

Changed 9 years ago by ibaldin

  • status changed from accepted to closed
  • resolution set to wontfix

The Sherpa workflow is as follows: reserve a vlan_id, provision a path with that vlan_id, release vlan resources (including the vlan_id). There is no way for a policy to hold on to specific vlan_ids in a guaranteed fashion. Therefore does not seem to make sense to develop a policy that tries to maintain a set of vlan tags that it gives out. The policy should continue to issue tickets for a tag (without specific tag) and the Sherpa handler is already built to (on 'join') acquire a tag and provision vlan in a single step.

Note: See TracTickets for help on using tickets.