Versions Compared

Old Version 8

changes.mady.by.user Manan Shah

Saved on

compared with

New Version Current

changes.mady.by.user Manan Shah

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

Req #

Requirement

Priority

2.1

Combine VR and VPC VR Code-base and feature set

P1

2.2

Load Balancing on all Tiers

P1

2.3

Deployment on VM on a VPC Tier + 1 or more Shared Networks

P1

2.4

Support for physical devices to do FW & LB

P1

2.5

KVM Hypervisor support

P1

2.6

Blacklist of Routes

P1

2.7

Support for 8 VPN connections using the same Public IP of VR

P1

2.8

Static routes to VPN Gateway

P2

2.9

Remote access VPN to VPC

P1

2.10

Users from different Accounts should be able to deploy to a VPC

P2

2.11

Ability to give isolated any IP network, not just
unique from super-net Don't require user to input the super CIDR

P1

2.12

Use same public IP for static NAT, PF and LB in VPC

P1

2.13

Meter IPSEC data separate from other data

P1

2.14

Allow ACL on all layer 4 protocols

P1

2.15

Support guest networks outside of RFC 1918 addresses

P1

2.16

Support ACL deny rules

P1

2.17

Redundant Virtual Router for VPC

P2

2.18

Assign a VLAN id to a network

P1

2.19

Add more than one Private GW to a VPC

P1

2.20

NAT on private GW

P1

2.21

ACL on Private GW

P1

...

2.9 Remote access VPN to VPC

This should also get addressed as part of requirement 2.1. This would enable remote-users to login to their VPC networkIsolated Networks allows Remote-access VPN capability for remote users to VPN into the Isolated Network. Similar functionality needs to be provided via the VPC VR.

2.10 Users from different Accounts should be able to deploy to a VPC

This is a P2 requirement to allow users to share a VPC between different accounts.

2.11 Don't ask the user to provide super CIDR as part of VPC creation

(Ability to give isolated network any IP network, not just unique from super-net)

Users want flexibility in defining the IP Network for each of their tiers. Users can specify a sub-network out of the VPC super-net for any specific tier and they are limited to specifying only a network out of the super-net defined while creating a VPC.

...

Similar to requirement 2.7

2.20 NAT on private GW

Allow NAT service on private gateway. Currently, only a private gateway can be defined and then static routes can be defined for that private gateway.

Customer might want to deploy multiple VPCs (with the same super CIDR) and/or guest Tier CIDR. So, there could be a possibility that multiple guest VM (from different VPCs) having the same IP need to reach a enterprise DC via the Private GW. In these cases, NAT service is needed on the private GW.

Only SourceNAT service is a requirement for this release.

2.21 ACL on private GW

Allow NAT and ACL services on private gateway. Currently, only a private gateway can be defined and then static routes can be defined for that private gateway.

...