[GENIUS-250] Move IdManager based VNI Carving to a centralized module Created: 19/Nov/18 Updated: 19/Dec/18 Resolved: 19/Dec/18 |
|
| Status: | Verified |
| Project: | genius |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Neon |
| Type: | Story | Priority: | Medium |
| Reporter: | Faseela K | Assignee: | Faseela K |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | COE |
| Description |
|
Currently this logic is inside NAT, and this needs to move outside to a common place, as it is needed by L2GW and COE |
| Comments |
| Comment by Faseela K [ 19/Nov/18 ] |
|
shague : How do I change the project for a story inside netvirt. some of these tasks are to be done in Genius, while some others in COE |
| Comment by Sam Hague [ 29/Nov/18 ] |
|
There is a More->Move option to move this sub-task. The only problem is you also have to have a parent in the project it is moved to. So create a similar parent in genius and then move this to that. Or convert this to a user-story and just move the story over to genius. This latter method is probably easier unless you need a parent story in genius. Either way, then link the moved jira back to the root jira here since it is part of that story. |