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

352 views
295 views

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
352
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

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

  1. 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

×