You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@@ -22,7 +22,7 @@ GeneStack (Genesis+OpenStack) is the code name for our latest OpenStack implemen
### Networking
The Rackspace OpenStack Flex cloud differs from the legacy OpenStack Public Cloud (OSPC) in many ways, but especially when it comes to networks. Rackspace has adopted a leaf/spine architecture along with BGP eVPN to provide scale that could not be achieved with the traditional core-aggr-tor design. Rather than virtual machine instances being connected to a front-end PUBLICNET and back-end SERVICENET network by default, users within a project are now able to easily define a network architecture that consists of a virtual router connected to an external 'public' provider network and one or more inside 'tenant' networks. No longer will instances be configured with a public IP directly, rather, they will utilize a user-defined network address space and leverage source NAT (SNAT) and destination NAT (DNAT) where required. In OpenStack parlance, this is NAT functionality is known as Floating IP - or Elastic IP if you're coming from AWS.
The Rackspace OpenStack Flex cloud differs from the legacy OpenStack Public Cloud (OSPC) in many ways, but especially when it comes to networks. Rackspace has adopted a leaf/spine architecture along with BGP eVPN to provide scale that could not be achieved with the traditional core-aggr-tor design. Rather than virtual machine instances being connected to a front-end PUBLICNET and back-end SERVICENET network by default, users within a project are now able to easily define a network architecture that consists of a virtual router connected to an external 'public' provider network and one or more inside 'tenant' networks. No longer will instances be configured with a public IP directly, rather, they will utilize a user-defined network address space and leverage source NAT (SNAT) and destination NAT (DNAT) where required. In OpenStack parlance, this NAT functionality is known as Floating IP - or Elastic IP if you're coming from AWS.
