Disclaimer This presentation may contain product features that are currently under development. This overview of new technology represents no commitme

Size: px

Start display at page:

Download "Disclaimer This presentation may contain product features that are currently under development. This overview of new technology represents no commitme"

Silvester Mills
5 years ago
Views:

1 NET1405BU Power of NSX - Network Virtualization for Elastic Apps and Data Centers Andrew Babakian ababakian@vmware.com Dimitri Desmidt ddesmidt@vmware.com #VMworld

2 Disclaimer This presentation may contain product features that are currently under development. This overview of new technology represents no commitment from VMware to deliver these features in any generally available product. Features are subject to change, and must not be included in contracts, purchase orders, or sales agreements of any kind. Technical feasibility and market demand will affect final delivery. Pricing and packaging for any new technologies or features discussed or presented have not been determined. 2

3 Disclaimer This presentation may contain product features that are currently under development. This overview of new technology represents no commitment from VMware to deliver these features in any generally available product. Features are subject to change, and must not be included in contracts, purchase orders, or sales agreements of any kind. Technical feasibility and market demand will affect final delivery. Pricing and packaging for any new technologies or features discussed or presented have not been determined. 3

Amazing scale With power of distributed services Powerful Automation capabilities With

4 Set the scene NSX is a Software Platform which offers All Network & Security services Natively and/or with partners Ease of use Decoupled from hardware + central management Amazing scale With power of distributed services Powerful Automation capabilities With 100% of its capabilities available via public API This session is focusing on Automation VPN 4

5 Why Automation? NSX does NOT require automation! Many customers use NSX in production without any automation Without any automation customers do enjoy major benefits, such as Speed Deployment of new applications in minutes (versus days/weeks) Security Deeper security with micro-segmentation Ease of Operation / Management with Central Management UI Ease of Maintenance with Central Upgrade 5

applications in seconds Even Higher Availability Remove manual errors Allows

6 So Why Automation? Automation brings additional benefits Even Higher Speed Deployment of new applications in seconds Even Higher Availability Remove manual errors Allows High-Resiliency Can detect, avoid, heal and remediate any deviations from normal This session details specific use cases AND offers OpenSource tools for them 6

7 Agenda Automation for Fast Deployment of New Apps (NET NET1853) Automation for Existing Dynamic Apps (Elastic LB) Automation for Sites Availability with GSLB (Disaster Recovery with automatic DNS updates) Automation for Partial Failure (How to transparently manage and migrate traffic in the event of server farm failure) 7

8 Agenda Automation for Fast Deployment of New Apps (NET NET1853) Automation for Existing Dynamic Apps (Elastic LB) Automation for Sites Availability with GSLB (Disaster Recovery with automatic DNS updates) Automation for Partial Failure (How to transparently manage and migrate traffic in the event of server farm failure) 8

9 Automation for Fast Deployment of New Apps NET1305 NET1853 Covered in other dedicated sessions 9

10 Agenda Automation for Fast Deployment of New Apps (NET NET1853) Automation for Existing Dynamic Apps (Elastic LB) Automation for Sites Availability with GSLB (Disaster Recovery with automatic DNS updates) Automation for Partial Failure (How to transparently manage and migrate traffic in the event of server farm failure) 10

Automation for Existing Dynamic Apps (NSXLBAutoScale) Use Case Presentaton Pool servers (Web

pool members are created Web-01 10.0.1.0/24 App-01 10.0.2.0/24.1.2.1.2.1 Transit-01 172.16.1.0/24.1 External 20.

0.3.0/24 web-01 web-02 web-xx App-01 App-02 DB-01.11.12.

11 Automation for Existing Dynamic Apps (NSXLBAutoScale) Use Case Presentaton Pool servers (Web Frontend and App Middleend) are dynamically adjusted based on load Based on the load on the VIP, new pool members are created Web /24 App / Transit /24.1 External /24 VIP-Web: :80 (Web-01:80+Web-02:80) VIP-App: :80 (App-01:80+App-02:80) DB /24 web-01 web-02 web-xx App-01 App-02 DB xx AutoScale Pool of servers Increase/Decrease based on load AutoScale Pool of servers Increase/Decrease based on load 11

Automation for Existing Dynamic Apps (NSXLBAutoScale) What does the NSXLBAutoScale Automation Tool do Automation Tool Check load of pool members (vcenter VMs) When load is above a threshold on any

12 Automation for Existing Dynamic Apps (NSXLBAutoScale) What does the NSXLBAutoScale Automation Tool do Automation Tool Check load of pool members (vcenter VMs) When load is above a threshold on any pool member vcenter: "Clone new VM" NSX: "Add new VM to LB pool" When load is below a threshold on all VMs NSX: "Delete VM from pool" (optionally VM moved in Drain mode for graceful server shutdown) vcenter: Delete 1 VM Let's see the OpenSource NSXLBAutoScale code! web-01 web Lower Heavy Traffic Check Load of Pool Members web-xx.xx 12

13 Automation for Existing Dynamic Apps (NSXLBAutoScale) Demo Demo AverageLoad Low High Web / Transit /24 External /24 VIP-Web: :80 (Pool-Web) web-01 web-02 web xx AutoScale Pool of servers Increase/Decrease based on load 13

14 Automation for Existing Dynamic Apps (NSXLBAutoScale) More Information (1/3) More information on automation tool used: Available on VMware PowerNSX Github: 14

15 Automation for Existing Dynamic Apps (NSXLBAutoScale) More Information (2/3) More information on PowerNSX: VMworld 2017 VMworld

16 Automation for Existing Dynamic Apps (NSXLBAutoScale) More Information (3/3) More information on NSX LB: VMworld

17 Agenda Automation for Fast Deployment of New Apps (NET NET1853) Automation for Existing Dynamic Apps (Elastic LB) Automation for Sites Availability with GSLB (Disaster Recovery with automatic DNS updates) Automation for Partial Failure (How to transparently manage and migrate traffic in the event of server farm failure) 17

18 What is Site Availability Application is available in multiple sites Application needs to be mirrored Storage needs to be Asych vs Synch Clients reach the Application to Primary site In case of failure, route to Secondary site DC1 DC2 APP_1 APP_1 18

19 What is Site Availability Application is available in multiple sites Application needs to be mirrored Storage needs to be Asynch vs Synch In case of failure, secondary site offers the service DNS: store.example.com = IP1 DC1 IP1 advertised DC2 Multiple techniques are available to offer that service: Route Health-Injection / Anycast IP1 advertised with higher cost APP_1 APP_1 19

20 What is Site Availability Application is available in multiple sites Application needs to be mirrored Storage needs to be Asynch vs Synch In case of failure, secondary site offers the service DNS: store.example.com = IP1 IP2 DC1 IP1 DC2 VMworld 2017 Content: Not for Multiple techniques are available to offer that service: Route Health-Injection / Anycast GSLB publication IP2 APP_1 APP_1 20

Project Remora Based on GSLB Does not take Authoritative

entries DC1 IP1 DC2 VMworld 2017 Content: Not for

store = A NS IP1 NSX-Remora-IP@ Authoratative DNS for

21 Project Remora Based on GSLB Does not take Authoritative DNS servers for entire domain Only in charge of specific entries DC1 IP1 DC2 VMworld 2017 Content: Not for Authorative Authoritative DNS for for example.com. store = A NS IP1 NSX-Remora-IP@ Authoratative DNS for store.example.com. store = A IP1 (or IP2 if IP1 dead) publication IP2 APP_1 APP_1 21

Automating Availability across Data Centers with GSLB Handling Preliminary DNS Responses Authoritative Control for records of interest Routing Clients to

e.!= 200 OK Rewrite Record IP Address to the correct VIP GSLB DomainName = Example.com TimeToLive = 5 * 1 RecordKeys() = store.example.

22 Automating Availability across Data Centers with GSLB Handling Preliminary DNS Responses Authoritative Control for records of interest Routing Clients to Available Nodes Shortened TTL Records. DNS Records Health Check Validate Load-balancer health i.e. 200 OK Record binding to Load balancer VIP Storing Backup feasible VIP s Site Recovery Load-balancer not available i.e.!= 200 OK Rewrite Record IP Address to the correct VIP GSLB DomainName = Example.com TimeToLive = 5 * 1 RecordKeys() = store.example.com RecordValues() = A([ ]) HTTP/HTTPS Monitor: Primary = A([ )] Standby= A([ )] LB DC1 LB DC2 LB DCn 22

Secondary VIP addresses stored in remote backend Accounting for Failure Probability of partial failure > full failure.

23 Introducing Project Remora - Active/Standby (NSX GSLBv) VMware Fling GSLB Active/Standby Re-routing client queries in the event of failure Network Virtualization aware NSX Extensions via API s Validate NSX Load-balancer health i.e. 200 OK API Integration to validate health of server farm. Secondary VIP addresses stored in remote backend Accounting for Failure Probability of partial failure > full failure. Monitoring Server Farm Event of Partial failure > Accepted Threshold, Rewrite record. 23

24 24

25 25

26 Agenda Automation for Fast Deployment of New Apps (NET NET1853) Automation for Existing Dynamic Apps (Elastic LB) Automation for Sites Availability with GSLB (Disaster Recovery with automatic DNS updates) Automation for Partial Failure (How to transparently manage and migrate traffic in the event of server farm failure) 26

27 27

28 DEMO 28

Disclaimer This presentation may contain product features that are currently under development. This overview of new technology represents no commitme

NET1192BE Multisite Networking & Security with Cross-vC NSX Josh Coulling Networking & Security Senior System Engineer #VMworld #NET1192BE Disclaimer This presentation may contain product features that