yahoo-eng-team team mailing list archive

[Harald Jensås <harald.jensas@xxxxxxxxx>]

Public bug reported:

With Neutron segments it is not possible to mix subnets with segment_id:
None and subnets with a segment_id. In some cases a network will be
created, a subnet added without creating a segment. tTen later this
network need to scale, and dividing it onto multiple routed segments is
required.

To be able to support migration from non-routed, to a routed network we
would like the ability to migrate current subnets on a network with no
segments to a segment. The migration can/should be limited to migrating
the subnet to a segment that use the same "provider:physical_network".

This feature woulb enable possibility to upgrade/migrate existing Triplo
deployments to neutron routed segments model.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: rfe

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1692490

Title:
  [RFE] Ability to migrate a non-Segment subnet to a Segment

Status in neutron:
  New

Bug description:
  With Neutron segments it is not possible to mix subnets with
  segment_id: None and subnets with a segment_id. In some cases a
  network will be created, a subnet added without creating a segment.
  tTen later this network need to scale, and dividing it onto multiple
  routed segments is required.

  To be able to support migration from non-routed, to a routed network
  we would like the ability to migrate current subnets on a network with
  no segments to a segment. The migration can/should be limited to
  migrating the subnet to a segment that use the same
  "provider:physical_network".

  This feature woulb enable possibility to upgrade/migrate existing
  Triplo deployments to neutron routed segments model.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1692490/+subscriptions