| 2016-03-28 21:48:30 |
Nischal Sheth |
bug |
|
|
added bug |
| 2016-03-28 21:48:37 |
Nischal Sheth |
nominated for series |
|
juniperopenstack/trunk |
|
| 2016-03-28 21:48:37 |
Nischal Sheth |
bug task added |
|
juniperopenstack/trunk |
|
| 2016-03-28 21:48:46 |
Nischal Sheth |
juniperopenstack/trunk: milestone |
|
r3.1.0.0-fcs |
|
| 2016-03-28 21:49:15 |
Nischal Sheth |
description |
Control node changes are tracked via bug 1552952.
UI changes are tracked via bug 1558168. |
Control node and schema changes are tracked via bug 1552952.
UI changes are tracked via bug 1558168. |
|
| 2016-03-28 21:51:56 |
Nischal Sheth |
juniperopenstack/trunk: assignee |
Sachin Bansal (sbansal) |
Nischal Sheth (nsheth) |
|
| 2016-03-28 22:13:35 |
Nischal Sheth |
description |
Control node and schema changes are tracked via bug 1552952.
UI changes are tracked via bug 1558168. |
Control node and schema changes are tracked via bug 1552952.
UI changes are tracked via bug 1558168.
Following changes need to be implemented in ST:
o The gateway-address and ipv6-gateway-address properties of the bgpaas
client bgp-router need to be set to the inet and inet6 default gateway
addresses of the inet/inet6 subnets from which the client VMI has got
addresses. This should be done by default - note that this intentionally
changes pre-existing sessions to be bidirectional.
o The inet6-gateway-address in the bgpaas client bgp-router should be set
to the ipv4-mapped ipv6 address (instead of the actual inet6 GW address)
if the bgpaas-ipv4-mapped-ipv6-nexthop property in bgp-as-a-service object
is set.
o The gateway-address and ipv6-gateway-address properties shouldn't be set
if bgpaas-suppress-route-advertisement property is set in bgp-as-a-service
object. This provides users with a way to get older behavior if required.
o If the as-override field in bgpaas-session-attributes property of the
bgp-as-aservice object is not set, it should be considered to be true when
creating/updating BgpSessionAttributes in BgpSession between the client
and server bgp-router objects. This enables as-override functionality by
default for pre-existing bgpaas sessions.
o If the as-override field in bgpaas-session-attributes property of the
bgp-as-aservice object is set to false, it should honored when creating
or updating BgpSessionAttributes in BgpSession between the client and
server bgp-router objects. This allows users to not set as-override. |
|
| 2016-03-28 22:13:45 |
Nischal Sheth |
juniperopenstack/trunk: assignee |
Nischal Sheth (nsheth) |
Sachin Bansal (sbansal) |
|
| 2016-03-28 22:23:52 |
Nischal Sheth |
description |
Control node and schema changes are tracked via bug 1552952.
UI changes are tracked via bug 1558168.
Following changes need to be implemented in ST:
o The gateway-address and ipv6-gateway-address properties of the bgpaas
client bgp-router need to be set to the inet and inet6 default gateway
addresses of the inet/inet6 subnets from which the client VMI has got
addresses. This should be done by default - note that this intentionally
changes pre-existing sessions to be bidirectional.
o The inet6-gateway-address in the bgpaas client bgp-router should be set
to the ipv4-mapped ipv6 address (instead of the actual inet6 GW address)
if the bgpaas-ipv4-mapped-ipv6-nexthop property in bgp-as-a-service object
is set.
o The gateway-address and ipv6-gateway-address properties shouldn't be set
if bgpaas-suppress-route-advertisement property is set in bgp-as-a-service
object. This provides users with a way to get older behavior if required.
o If the as-override field in bgpaas-session-attributes property of the
bgp-as-aservice object is not set, it should be considered to be true when
creating/updating BgpSessionAttributes in BgpSession between the client
and server bgp-router objects. This enables as-override functionality by
default for pre-existing bgpaas sessions.
o If the as-override field in bgpaas-session-attributes property of the
bgp-as-aservice object is set to false, it should honored when creating
or updating BgpSessionAttributes in BgpSession between the client and
server bgp-router objects. This allows users to not set as-override. |
Control node and schema changes are tracked via bug 1552952.
UI changes are tracked via bug 1558168.
Following changes need to be implemented in ST:
o The gateway-address and ipv6-gateway-address properties of the bgpaas
client bgp-router need to be set to the inet and inet6 default gateway
addresses of the inet/inet6 subnets from which the client VMI has got
addresses. This should be done by default - note that this intentionally
changes pre-existing sessions to be bidirectional.
o The inet6-gateway-address in the bgpaas client bgp-router should be set
to the ipv4-mapped ipv6 address (instead of the actual inet6 GW address)
if the bgpaas-ipv4-mapped-ipv6-nexthop property in bgp-as-a-service object
is set.
o The gateway-address and ipv6-gateway-address properties shouldn't be set
if bgpaas-suppress-route-advertisement property is set in bgp-as-a-service
object. This provides users with a way to get older behavior if required.
o If the as-override field in bgpaas-session-attributes property of the
bgp-as-aservice object is not set, it should be considered to be true when
creating/updating BgpSessionAttributes in BgpSession between the client
and server bgp-router objects. This enables as-override functionality by
default for pre-existing bgpaas sessions.
o If the as-override field in bgpaas-session-attributes property of the
bgp-as-aservice object is set to false, it should be honored when creating
or updating BgpSessionAttributes in BgpSession between the client and
server bgp-router objects. This allows users to not set as-override. |
|
| 2016-03-28 22:25:32 |
Nischal Sheth |
description |
Control node and schema changes are tracked via bug 1552952.
UI changes are tracked via bug 1558168.
Following changes need to be implemented in ST:
o The gateway-address and ipv6-gateway-address properties of the bgpaas
client bgp-router need to be set to the inet and inet6 default gateway
addresses of the inet/inet6 subnets from which the client VMI has got
addresses. This should be done by default - note that this intentionally
changes pre-existing sessions to be bidirectional.
o The inet6-gateway-address in the bgpaas client bgp-router should be set
to the ipv4-mapped ipv6 address (instead of the actual inet6 GW address)
if the bgpaas-ipv4-mapped-ipv6-nexthop property in bgp-as-a-service object
is set.
o The gateway-address and ipv6-gateway-address properties shouldn't be set
if bgpaas-suppress-route-advertisement property is set in bgp-as-a-service
object. This provides users with a way to get older behavior if required.
o If the as-override field in bgpaas-session-attributes property of the
bgp-as-aservice object is not set, it should be considered to be true when
creating/updating BgpSessionAttributes in BgpSession between the client
and server bgp-router objects. This enables as-override functionality by
default for pre-existing bgpaas sessions.
o If the as-override field in bgpaas-session-attributes property of the
bgp-as-aservice object is set to false, it should be honored when creating
or updating BgpSessionAttributes in BgpSession between the client and
server bgp-router objects. This allows users to not set as-override. |
Control node and schema changes are tracked via bug 1552952.
UI changes are tracked via bug 1558168.
Following changes need to be implemented in ST:
o The gateway-address and ipv6-gateway-address properties of the bgpaas
client bgp-router need to be set to the inet and inet6 default gateway
addresses of the inet/inet6 subnets from which the client VMI has got
addresses. This should be done by default - note that this intentionally
changes pre-existing sessions to be bidirectional.
o The inet6-gateway-address in the bgpaas client bgp-router should be set
to the ipv4-mapped ipv6 address (instead of the actual inet6 GW address)
if the bgpaas-ipv4-mapped-ipv6-nexthop property in bgp-as-a-service object
is set.
o The gateway-address and ipv6-gateway-address properties shouldn't be set
if bgpaas-suppress-route-advertisement property is set in bgp-as-a-service
object. This provides users with a way to get older behavior if required.
o If the as-override field in bgpaas-session-attributes property of the
bgp-as-aservice object is not set, it should be considered to be true when
creating/updating BgpSessionAttributes in BgpSession between the client
and server bgp-router objects. This enables as-override functionality by
default for pre-existing bgpaas sessions.
o If the as-override field in bgpaas-session-attributes property of the
bgp-as-aservice object is set to false, it should be honored when creating
or updating BgpSessionAttributes in BgpSession between the client and
server bgp-router objects. This allows users to not set as-override.
Note that UI will set the as-override field in bgpaas-session-attributes
property of the bgp-as-aservice object to true by default. |
|
| 2016-03-30 20:50:12 |
Sachin Bansal |
juniperopenstack/trunk: assignee |
Sachin Bansal (sbansal) |
Ignatious Johnson Christopher (ijohnson-x) |
|
| 2016-04-09 00:06:32 |
OpenContrail Admin |
juniperopenstack/trunk: status |
New |
In Progress |
|
| 2016-04-21 17:24:21 |
Nischal Sheth |
description |
Control node and schema changes are tracked via bug 1552952.
UI changes are tracked via bug 1558168.
Following changes need to be implemented in ST:
o The gateway-address and ipv6-gateway-address properties of the bgpaas
client bgp-router need to be set to the inet and inet6 default gateway
addresses of the inet/inet6 subnets from which the client VMI has got
addresses. This should be done by default - note that this intentionally
changes pre-existing sessions to be bidirectional.
o The inet6-gateway-address in the bgpaas client bgp-router should be set
to the ipv4-mapped ipv6 address (instead of the actual inet6 GW address)
if the bgpaas-ipv4-mapped-ipv6-nexthop property in bgp-as-a-service object
is set.
o The gateway-address and ipv6-gateway-address properties shouldn't be set
if bgpaas-suppress-route-advertisement property is set in bgp-as-a-service
object. This provides users with a way to get older behavior if required.
o If the as-override field in bgpaas-session-attributes property of the
bgp-as-aservice object is not set, it should be considered to be true when
creating/updating BgpSessionAttributes in BgpSession between the client
and server bgp-router objects. This enables as-override functionality by
default for pre-existing bgpaas sessions.
o If the as-override field in bgpaas-session-attributes property of the
bgp-as-aservice object is set to false, it should be honored when creating
or updating BgpSessionAttributes in BgpSession between the client and
server bgp-router objects. This allows users to not set as-override.
Note that UI will set the as-override field in bgpaas-session-attributes
property of the bgp-as-aservice object to true by default. |
Control node and schema changes are tracked via bug 1552952.
UI changes are tracked via bug 1558168.
Following changes need to be implemented in ST:
o The gateway-address and ipv6-gateway-address properties of the bgpaas
client bgp-router need to be set to the inet and inet6 default gateway
addresses of the inet/inet6 subnets from which the client VMI has got
addresses. This should be done by default - note that this intentionally
changes pre-existing sessions to be bidirectional.
o The inet6-gateway-address in the bgpaas client bgp-router should be set
to the ipv4-mapped ipv6 address (instead of the actual inet6 GW address)
if the bgpaas-ipv4-mapped-ipv6-nexthop property in bgp-as-a-service object
is set.
o The gateway-address and ipv6-gateway-address properties shouldn't be set
if bgpaas-suppress-route-advertisement property is set in bgp-as-a-service
object. This provides users with a way to get older behavior if required. |
|
| 2016-04-21 17:27:24 |
Nischal Sheth |
juniperopenstack/trunk: status |
In Progress |
Fix Committed |
|
