Your SlideShare is downloading. ×
0
Use nix   cloud computing w. v-mware vcloud director (poster)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Use nix cloud computing w. v-mware vcloud director (poster)

217

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
217
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. vSphere Network Resources Any – Standard vSwitch Any – Distributed vSwitch VMware Standard Portgroup: Standard vSwitch VMware Standard Portgroup: Standard vSwitch VMware vDS Switch: Distributed vSwitch vSwitch Name: vSwitch3 vSwitch Name: vSwitch2 vSwitch Name: dvSwitch_Customer01 Portgroup Name: PG_Backed_vSw01 Portgroup Name: SP01_SNet01 Portgroups: Created automatically during Org Network creation VLAN ID: 99 VLAN ID: 88 ESX Hosts: All in the Cluster Physical Adapters: vmnic5, vmnic7 Physical Adapters: vmnic2, vmnic4 dvUplink Ports: 4 Network Pool – External Network vCloud Director Network Resources (Provider VDC) External Network – Standard vSwitch Any – Distributed vSwitch External Network: SP01 – ExternalNet01 Distributed vSwitch is also possible Static IP Pool: 192.168.1.150 – 192.168.1.160 Default Gateway: 192.168.1.1 vSwitch Type: vSS or vDS Primary DNS: 192.168.1.200 DNS Suffix: provider.com Network Pool: vCloud Director Network Isolation- Network Pool: vSphere Portgroup-backed Network Pool: VLAN-backed backed Raman Veeramraju Name: PG_Backed_NP01 Name: VLAN_Backed_NP01 Name: Fence_Backed_NP01 vSwitch Type: vSS or vDS Portgroup Type: vDS only Portgroup Type: vDS only vCenter: VC001 dvSwitch: dvSwitch_Customer01 dvSwitch: dvSwitch_Customer01 Portgroup: PG_Network_Pool01 VLAN ID Ranges: 100 – 110 Virtualyzation.com Number of vCloud isolated networks: 10 External Network: SP01-ExternalNet01 External Network: SP01-ExternalNet01 External Network: SP01-ExternalNet01 vCloud Director Network Resources (Use Cases) Mapping Organization Network Type  External Network Organization Network Type  Network Pool cloud01  name of the instance given during the initial configuration  Public network – direct connection  External Network Private network – routed (NAT) connection   vSphere Portgroup-backed Private network – routed (NAT) connection   VLAN-backed Private network – routed (NAT) connection   vCloud Network Isolated-backed Private network – isolated   vSphere Portgroup-backed Private network – isolated   VLAN-backed Private network – isolated  vCloud Network Isolated-backed• Network Specifications including Static IP Pool, DNS Suffix, Primary DNS are directly obtained from External Network • Choose External Network and Network Pool (Portgroup-backed) • Choose External Network and Network Pool (VLAN-backed) • Choose External Network and Network Pool (vCloud Network Isolated-backed) • Will be able to choose only Network Pool • Will be able to choose only Network Pool • Will be able to choose only Network Pool• When VMs in a vApp are assigned to this network, they have a choice of either DHCP, Static – IP Pool or Static – Manual • Network Specifications for the Network Pool (Internal) • Network Specifications for the Network Pool (Internal) • Network Specifications for the Network Pool (Internal) • Network Specifications for the Network Pool • Network Specifications for the Network Pool • Network Specifications for the Network Pool• There is no Network Pool in this case • Network Specifications for the External Network will be directly obtained from External Network • A VLAN will be automatically assigned to this Network Pool • A VLAN will be automatically assigned to this Network Pool • Under Network Services Configuration, only DHCP is enabled; since this is an isolated network, Firewall, Port Forwarding, • Under Network Services Configuration, only DHCP is enabled; since this is an isolated network, Firewall, Port Forwarding, • Under Network Services Configuration, only DHCP is enabled; since this is an isolated network, Firewall, Port Forwarding, • External Management IP address for additional Services such as DHCP, Firewall, Port Forwarding (+ IP Masquerade) • Network Specifications for the External Network will be directly obtained from External Network • Network Specifications for the External Network will be directly obtained from External Network External IP Management will be disabled External IP Management will be disabled External IP Management will be disabled Actions on vCenter during the creation of this network • When VMs in a vApp are assigned to this network, they have a choice of either DHCP, Static – IP Pool or Static – Manual • External Management IP address for additional Services such as DHCP, Firewall, Port Forwarding (+ IP Masquerade) • External Management IP address for additional Services such as DHCP, Firewall, Port Forwarding (+ IP Masquerade) • When VMs in a vApp are assigned to this network, they have a choice of either DHCP, Static – IP Pool or Static – Manual • When VMs in a vApp are assigned to this network, they have a choice of either DHCP, Static – IP Pool or Static – Manual • When VMs in a vApp are assigned to this network, they have a choice of either DHCP, Static – IP Pool or Static – Manual • No actions on vCenter • When VMs in vAPP are deployed, they will be assigned an Internal IP Address and an External IP Address from Org • When VMs in a vApp are assigned to this network, they have a choice of either DHCP, Static – IP Pool or Static – Manual • When VMs in a vApp are assigned to this network, they have a choice of either DHCP, Static – IP Pool or Static – Manual Actions on vCenter during the creation of this network Network, if deployed in fenced mode Actions on vCenter during the creation of this network Actions on vCenter during the creation of this network Actions on vCenter during the creation of this network Actions on vCenter during the creation of this network Actions on vCenter during the creation of this network • Added distributed virtual port group (vDS.VC100DVS1CM2-F2) to dvSwitch_Customer01 • • • Added distributed virtual port group (vDS.VC100DVS1CM2-V12) to dvSwitch_Customer01 Actions on vCenter when the VMs in a vApp are deployed (Direct) • Added distributed virtual port group (vDS.VC100DVS1CM2-V13) to dvSwitch_Customer01 – with a VLAN ID 101 Added distributed virtual port group (vDS.VC100DVS1CM2-F2) to dvSwitch_Customer01 Created a folder under Service VMs (00000029-vse-31) • Created a folder under Service VMs • Created a folder under Service VMs (00000029-vse-31) • • • Created a folder under Service VMs • • Created a folder under Service VMs (00000030-vse-34) Created a folder under Service VMs (00000030-vse-34) Registered the vShield Edge virtual machine in this folder (001629-vse_v29n31s2) Registered the vShield Edge virtual machine in this folder • Reconfigured and powered on the virtual machine • Registered the vShield Edge virtual machine in this folder (001629-vse_v29n31s2) • • • Registered the vShield Edge virtual machine in this folder • • Registered the vShield Edge virtual machine in this folder (001630-vse_v30n34s2) Registered the vShield Edge virtual machine in this folder (001630-vse_v30n34s2) Reconfigured the vShield Edge virtual machine under the Portgroup (vSS or vDS or Cisco Nexus 1KV) created by the admin Reconfigured the vShield Edge virtual machine • Assigned an IP Address from External Network Static – IP Pool • • • • Reconfigured the vShield Edge virtual machine • Reconfigured the vShield Edge virtual machine under the Portgroup (vSS or vDS or Cisco Nexus 1KV) created by the • Reconfigured the vShield Edge virtual machine Reconfigured the vShield Edge virtual machine Powered on the vShield Edge virtual machine Powered on the vShield Edge virtual machine • VM is placed under the folder structure  cloud01 / Org VDC / vApp / admin • • Powered on the vShield Edge virtual machine • • Powered on the vShield Edge virtual machine Powered on the vShield Edge virtual machine Port XYZ link was connected in the dvSwitch_Customer01 • Powered on the vShield Edge virtual machine • Actions on vCenter when the VMs in a vApp are deployed (Direct) • Port XYZ link was connected in the dvSwitch_Customer01 External Network • Port XYZ link was connected in the dvSwitch_Customer01 Port XYZ link was connected in the dvSwitch_Customer01 Static IP Address Pool: Actions on vCenter when the VMs in a vApp are deployed (Direct) Actions on vCenter when the VMs in a vApp are deployed (Direct) Actions on vCenter when the VMs in a vApp are deployed (Direct) Actions on vCenter when the VMs in a vApp are deployed (Direct) • Reconfigured and powered on the virtual machine 192.168.1.150 – 192.168.1.160 Actions on vCenter when the VMs in a vApp are deployed (Direct) • • Assigned an IP Address from Org Network Static – IP Pool • Reconfigured and powered on the virtual machine • Reconfigured and powered on the virtual machine vSS – SW01 Reconfigured and powered on the virtual machine Portgroup: PNET01 Org Network • Assigned an IP Address from Org Network Static – IP Pool • Reconfigured and powered on the virtual machine • Reconfigured and powered on the virtual machine • VM is placed under the folder structure  cloud01 / Org VDC / vApp • Assigned an IP Address from Org Network Static – IP Pool • Assigned an IP Address from Org Network Static – IP Pool (Public network – Direct connection) (External Network) Static IP Address Pool: • VM is placed under the folder structure  cloud01 / Org VDC / vApp • Assigned an IP Address from Org Network Static – IP Pool • Assigned an IP Address from Org Network Static – IP Pool • VM is placed under the folder structure  cloud01 / Org VDC / vApp • VM is placed under the folder structure  cloud01 / Org VDC / vApp External Network 192.168.112.150 – 192.168.112.160 • VM is placed under the folder structure  cloud01 / Org VDC / vApp • VM is placed under the folder structure  cloud01 / Org VDC / vApp Static IP Address Pool: External Network Not used in this case 192.168.1.150 – 192.168.1.160 External Network External Network Static IP Address Pool: External Network Admin-defined vSS or vDS Not used in this case Static IP Address Pool: Static IP Address Pool: 192.168.1.150 – 192.168.1.160 External Network Static IP Address Pool: Admin-defined Portgroup 192.168.1.150 – 192.168.1.160 192.168.1.150 – 192.168.1.160 vDS.VC100XYZ-F1 (Isolated) Not used in this case vSS – SW01 Admin-defined vSS or vDS Static IP Address Pool: 192.168.1.150 – 192.168.1.160 (Org Network) Not used in this case vSS – SW01 vDS.VC100XYZ-F1 (Isolated) Not used in this case Org Network vDS.VC100XYZ-V14 (VLAN) Not used in this case Portgroup: dVS01 Portgroup: PNET01 Admin-defined Portgroup vSS – SW01 vDS.VC100XYZ-V14 (VLAN) 192.168.1.150 – 192.168.1.160 Portgroup: PNET01 Portgroup: dVS01 (Private network – routed (NAT) connection) Portgroup: dVS01 (Org Network) Org Network VM1 – 192.168.1.151 (External Network) (Org Network) Portgroup: PNET01 Portgroup: dVS01 Not used in this case Org Network (External Network) (Org Network) Static IP Address Pool: (Org Network) Org Network Org Network (Private network – routed (NAT) connection) (Private network – routed (NAT) connection) (External Network) (Org Network) Org Network 192.168.112.150 – 192.168.112.160 (Private network – routed (NAT) connection) (Private network – routed (NAT) connection) (Private network – routed (NAT) connection) Static IP Address Pool: Static IP Address Pool: Static IP Address Pool: Static IP Address Pool: 192.168.112.150 – 192.168.112.160 vAPP 192.168.112.150 – 192.168.112.160 Static IP Address Pool: 192.168.112.150 – 192.168.112.160 192.168.112.150 – 192.168.112.160 192.168.112.150 – 192.168.112.160 192.168.112.1 192.168.1.150 192.168.112.1 Edge01 Step 1: VMs in the vApp are configured to connect Edge01 192.168.1.150 192.168.112.1 192.168.1.150 192.168.112.1 192.168.112.1 Edge01 Edge01 192.168.112.1 Edge01 directly to the External Network Portgroup and assigned with the IP Addresses of the Org Network VM1 – 192.168.112.150 Edge01 VM1 – 192.168.112.150 VM1 – 192.168.112.150 VM1 – 192.168.112.150 Step 0: This vShield Edge is created and powered VM1 – 192.168.112.150 Step 0: This vShield Edge is created and powered Step 0: This vShield Edge is created and powered on when the Org Network was created; however, VM1 – 192.168.112.150 Step 0: This vShield Edge is created and powered vAPP on when the Org Network was created; however, on when the Org Network was created; however, Step 0: This vShield Edge is created and powered Actions on vCenter when the VMs in a vApp are deployed (Fenced) it will not be used here vAPP vAPP on when the Org Network was created; however, vAPP it will not be used here Step 0: This vShield Edge is created and powered on when the Org Network was created; however, it will not be used here it will not be used here vAPP on when the Org Network was created; however, it will not be used here vAPP • Added a Distributed virtual port group based on Org VDC Network Pool that this vApp is registered to Step 1: VMs in the vApp are configured to connect Step 1: VMs in the vApp are configured to Step 1: VMs in the vApp are configured to connect Step 1: VMs in the vApp are configured to connect directly to it will not be used here directly to the Org Network Portgroup and assigned connect directly to the Org Network Portgroup • Created a folder under Service VMs and placed the vShield Edge under this folder and assigned with the IP Addresses of the Org directly to the Org Network Portgroup and assigned the Org Network Portgroup and assigned with the IP Step 1: VMs in the vApp are configured to connect directly to with the IP Addresses of the Org Network Addresses of the Org Network • Connected the vShield Edge to the External Network on one end and to the vApp Network (new vDS here) on the Network with the IP Addresses of the Org Network Step 1: VMs in the vApp are configured to connect directly to the Org Network Portgroup and assigned with the IP other end and powered it on the Org Network Portgroup and assigned with the IP Addresses of the Org Network Addresses of the Org Network • Connected the VMs in the vApp to the vApp Network and powered them on Actions on vCenter when the VMs in a vApp are deployed (Fenced) • Both interface IP addresses of the vShield Edge are assigned from the Static IP Pool (Network Specifications) of Actions on vCenter when the VMs in a vApp are deployed (Fenced) Actions on vCenter when the VMs in a vApp are deployed (Fenced) Actions on vCenter when the VMs in a vApp are deployed (Fenced) the External Network • Added a vDS group (Dynamic vApp Network) based on Org VDC Network Pool that this vApp is registered • Added a vDS portgroup (Dynamic vApp Network) based on Org VDC Network Pool that this vApp is • • Added a vDS portgroup (Dynamic vApp Network) based on Org VDC Network Pool that this vApp is registered to Actions on vCenter when the VMs in a vApp are deployed (Fenced) • Both Internal and External IP addresses for all the VMs in the vApp are assigned from the Static IP Pool to Added a vDS portgroup (Dynamic vApp Network) based on Org VDC Network Pool that this vApp is registered to Actions on vCenter when the VMs in a vApp are deployed (Fenced) registered to • Created a folder under Service VMs and placed the vShield Edge under this folder • Created a folder under Service VMs and placed the vShield Edge under this folder (Network Specifications) of the External Network • Created a folder under Service VMs and placed the vShield Edge under this folder • Added a vDS portgroup (Dynamic vApp Network) based on Org VDC Network Pool that this vApp is registered to • Connected the vShield Edge to the Org Network (vDS portgroup created during the creation of this Org Network) on • Created a folder under Service VMs and placed the vShield Edge under this folder • Connected the vShield Edge to the Org Network (vDS portgroup created during the creation of this Org Network) on one end and • Connected the vShield Edge to the Org Network (vDS portgroup created during the creation of this Org Network) on one end and • Added a vDS portgroup (Dynamic vApp Network) based on Org VDC Network Pool that this vApp is registered to • Connected the vShield Edge to the Org Network (vDS portgroup created during the creation of this Org Network) on • Created a folder under Service VMs and placed the vShield Edge under this folder External Network Org Network one end and to the vApp Network (new vDS here) on the other end and powered it on to the vApp Network (new vDS here) on the other end and powered it on to the vApp Network (new vDS here) on the other end and powered it on • Created a folder under Service VMs and placed the vShield Edge under this folder one end and to the vApp Network (new vDS here) on the other end and powered it on • Connected the vShield Edge to the Org Network (vDS portgroup created during the creation of this Org Network) on one end Static IP Address Pool: (Public network -Direct connection) • Connected the VMs in the vApp to the vApp Network and powered them on • Connected the VMs in the vApp to the vApp Network and powered them on • Connected the VMs in the vApp to the vApp Network and powered them on • Connected the vShield Edge to the Org Network (vDS portgroup created during the creation of this Org Network) on one end 192.168.1.150 – 192.168.1.160 Static IP Address Pool: • Connected the VMs in the vApp to the vApp Network and powered them on and to the vApp Network (new vDS here) on the other end and powered it on • Both interface IP addresses of the vShield Edge are assigned from the Static IP Pool (Network Specifications) of the • Both interface IP addresses of the vShield Edge are assigned from the Static IP Pool (Network Specifications) of the Org Network • Both interface IP addresses of the vShield Edge are assigned from the Static IP Pool (Network Specifications) of the Org Network and to the vApp Network (new vDS here) on the other end and powered it on 192.168.112.150 – 192.168.112.160 • Both interface IP addresses of the vShield Edge are assigned from the Static IP Pool (Network Specifications) of the • Connected the VMs in the vApp to the vApp Network and powered them on Not used in this case Org Network • Both Internal and External IP addresses for all the VMs in the vApp are assigned from the Static IP Pool (Network • Both Internal and External IP addresses for all the VMs in the vApp are assigned from the Static IP Pool (Network • Connected the VMs in the vApp to the vApp Network and powered them on Org Network • Both interface IP addresses of the vShield Edge are assigned from the Static IP Pool (Network Specifications) of the Org Network vSS – SW01 vDS – SW02 • Both Internal and External IP addresses for all the VMs in the vApp are assigned from the Static IP Pool Specifications) of the Org Network Specifications) of the Org Network • Both interface IP addresses of the vShield Edge are assigned from the Static IP Pool (Network Specifications) of the Org • Both Internal and External IP addresses for all the VMs in the vApp are assigned from the Static IP Pool • Both Internal and External IP addresses for all the VMs in the vApp are assigned from the Static IP Pool (Network Portgroup: PNET01 Portgroup: vDS.VCSXYZ-F10 (Network Specifications) of the Org Network • VMs can further be NATted to the External Network using vShield Edge (Edge01) • VMs can be further NATted to the External Network via vShield Edge (Edge01) Network (External Network) (Dynamic vApp Network) (Network Specifications) of the Org Network Specifications) of the Org Network • VMs can further be NATted to the External Network using vShield Edge (Edge01) • Both Internal and External IP addresses for all the VMs in the vApp are assigned from the Static IP Pool (Network • VMs can be further NATted to the External Network via vShield Edge (Edge01) Step 1: Created this vDS Portgroup • VMs can further be NATted to the External Network using vShield Edge (Edge01) External Network External Network Specifications) of the Org Network from the Org VDC’s Network Pool Static IP Address Pool: Static IP Address Pool: External Network External Network 192.168.1.150 – 192.168.1.160 192.168.1.150 – 192.168.1.160 • VMs can be further NATted to the External Network via vShield Edge (Edge01) External Network vSS – SW01 vDS.VC100XYZ-F1 Static IP Address Pool: Static IP Address Pool: Static IP Address Pool: vDS – SW03 Used for further NATting Admin-defined vSS or vDS Not used in this case – completely isolated (Isolated) vDS – SW03 External Network 192.168.1.150 – 192.168.1.160 192.168.1.150 – 192.168.1.160 192.168.1.150 – 192.168.1.160 Portgroup: PNET01 Portgroup: vDS.VCSXYZ-F4 vSS – SW01 Portgroup: dVS01 Admin-defined Portgroup Portgroup: vDS.VCSXYZ-F7 Static IP Address Pool: vSS – SW01 Admin-defined vSS or vDS vDS – SW03 Used for further NATting vDS.VC100XYZ-V14 (VLAN) vDS – SW03 Used for further NATting (External Network) (Dynamic vApp Network) Org Network vDS.VC100XYZ-F1 (Isolated) vDS – SW03 Not used in this case – completely isolated Portgroup: PNET01 (Org Network) (Org Network) (Dynamic vApp Network) Org Network 192.168.1.150 – 192.168.1.160 Portgroup: PNET01 Admin-defined Portgroup Portgroup: vDS.VCSXYZ-F4 Portgroup: dVS01 Portgroup: vDS.VCSXYZ-F4 (Private network – routed (NAT) connection) Portgroup: dVS01 Portgroup: vDS.VCSXYZ-F7 (External Network) Org Network (Private network – routed (NAT) connection) vDS.VC100XYZ-V14 (VLAN) vDS – SW03 Not used in this case – completely isolated Org Network 192.168.1.155 192.168.1.157 (External Network) Org Network (Org Network) (Dynamic vApp Network) Static IP Address Pool: (Org Network) (Dynamic vApp Network) (Org Network) (Dynamic vApp Network) Static IP Address Pool: Edge01 (Private network – routed (NAT) connection) (Private network – routed (NAT) connection) 192.168.112.150 – 192.168.112.160 Portgroup: dVS01 Portgroup: vDS.VCSXYZ-F7 (Private network – routed (NAT) connection) 192.168.112.150 – 192.168.112.160 (Org Network) (Dynamic vApp Network) Org Network Static IP Address Pool: Static IP Address Pool: Static IP Address Pool: (Private network – routed (NAT) connection) 192.168.112.150 – 192.168.112.160 192.168.112.150 – 192.168.112.160 192.168.112.150 – 192.168.112.160 VM1 – 192.168.1.151 192.168.112.1 192.168.112.155 Static IP Address Pool: 192.168.1.150 192.168.112.153 Edge01 Edge02 192.168.112.1 192.168.112.155 192.168.112.153 192.168.112.150 – 192.168.112.160 Step 2: Created this vShield Edge and attached to the 192.168.1.150 192.168.112.153 vAPP 192.168.1.150 192.168.112.1 192.168.112.155 192.168.112.153 192.168.112.1 192.168.112.155 Edge01 Edge02 192.168.112.1 192.168.112.155 192.168.112.153 External Network on one end and the vApp Edge01 Edge02 Edge01 Edge02 Network on the other end Edge01 Edge02 VM1 – 192.168.112.150 192.168.112.1 192.168.112.155 192.168.112.153 Step 3: Powered on the VMs in the VM1 – 192.168.112.150 Edge01 Edge02 VM1 – 192.168.112.150 VM1 – 192.168.112.150 vApp VM1 – 192.168.112.150 Step 0: This vShield Edge is created and Step 1: This vShield Edge is created and Step 0: This vShield Edge is created and Step 1: This vShield Edge is created and powered on when the Org Network was powered on vAPP Step 0: This vShield Edge is created and Step 1: This vShield Edge is created and VM1 – 192.168.112.150 Step 0: This vShield Edge is created and Step 1: This vShield Edge is created and created; this can be used to further NAT powered on when the Org Network was powered on Step 0: This vShield Edge is created and Step 1: This vShield Edge is created and powered on when the Org Network was powered on vAPP powered on when the Org Network was powered on vAPP the VMs to External Network created; however, it will not be used here Step 0: This vShield Edge is created and Step 1: This vShield Edge is created and powered on when the Org Network was powered on vAPP created; this can be used to further NAT vAPP created; this can be used to further NAT Step 2: VMs in the vApp are configured to connect powered on when the Org Network was powered on created; however, it will not be used here the VMs to External Network vAPP the VMs to External Network Step 2: VMs in the vApp are configured to connect directly to the Org Network Portgroup and created; however, it will not be used here Step 2: VMs in the vApp are configured to assigned with the IP Addresses of the Org Step 2: VMs in the vApp are configured to connect Step 2: VMs in the vApp are configured to connect directly to the Org Network Portgroup and connect directly to the Org Network Portgroup Network directly to the Org Network Portgroup and assigned with Step 2: VMs in the vApp are configured to connect directly to the Org Network Portgroup and assigned assigned with the IP Addresses of the Org and assigned with the IP Addresses of the Org the IP Addresses of the Org Network directly to the Org Network Portgroup and assigned with the IP Addresses of the Org Network Network Network with the IP Addresses of the Org Network

×