Feature Overview 

Introduce new flags to os-net-config to help with a number of scenarios:

• current-config
  • be able to remove interfaces without using the overliy disruptive --cleanup option
  • pass os-net the existing conifguraiton file as well as the new one so that a delta may be calculated and applied accordingly
• rollback
  • in the event of failure to apply the network, revert back to the previous configuration
• no-abort
  • current behavior is that if one entity is failed, the flow is aborted mid operation, this may result in loss of connectivity
  • with --no-abort (name pending), continue to try and apply the rest of the conifgurtion, even if one entity fails, os-net-config should exit with a specail return code in this case
• detect ip duplicates on --noop
  • even on dry run try to see if there is an ip duplicate (90% of failed config applies are caused by this)
  • consider broadcasting an arp, but verify we dont detect our own address, if already present

Requirements (mandatory -_ Complete while in Refinement status):
A list of specific needs, capabilities, or objectives that a Feature must deliver to satisfy the Feature. Some requirements will be flagged as MVP. If an MVP gets shifted, the Feature shifts. If a non MVP requirement slips, it does not shift the feature.

Done—Acceptance Criteria

• the new flags shall be supported for all provider options

Documentation Considerations 

User Guide update with description of new flags

Release notes

Background and Strategic Fit 

Tactical incremental enhnancement

Customer Considerations __(Initial completion while in Refinement status):
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
<your text here>

Team Sign Off (Completion while in Planning status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone

• …