2015 2016 - herefordshire and ludlow...
TRANSCRIPT
2015‐2016
Phil Smith
Learning outcomesOn successful completion of this unit you will:
1. Understand the commercial impact and potential of virtualisation. (Assignment 1)
LO1 Understand the commercial impact and potential of virtualisation. Understand the commercial impact and potential of virtualisation.
1. Week 12. Scalability3. Redundancy4. Support5. Environmental6. Week 27. Solutions8. Technology9. environments for developers 10. Cost
LO1 Solutions. Solutions: desktop based
Parallels (Apple) QEMU (Apple) virtual PC VM‐Ware Player VMWare fusion Virtualbox
LO1 Solutions. Solutions:
server based VMWare ESXi ESX Citrix
LO1 Technology. hypervisor; abstraction; virtual drivers; network connection eg NAT, bridged;
LO1 Technology. Hypervisor
We already know this is the name given to VM hosts i.evirtualbox.
Abstraction = Not really a VM. A typical abstract machine consists of a definition in terms of input, output, and the set of allowable operations used to turn the former into the latter. The best‐known example is the Turing machine.
virtual drivers; Using widely available tools called free virtual drive software orDisk Emulators, it’s easy to mount an ISO file (or a disk for that matter) and use it as one would with a disk loaded in the CD tray.
LO1 Network (Virtualbox) Which virtualized NIC‐type is exposed to the Guest. Examples include: Intel PRO/1000 MT Server (82545EM), AMD PCNet FAST III (Am79C973, the default) or a Paravirtualized network adapter (virtio‐net).
How the NIC operates with respect to your Host's physical networking. The main modes are: Network Address Translation (NAT) Bridged networking Internal networking Host‐only networking NAT with Port‐forwarding
LO1 Network NAT (Network Address Translation ) when the guest OS boots, it typically uses DHCP to get an IP address. VirtualBox will field this DHCP request and tell the guest OS its assigned IP address and the gateway address for routing outbound connections. In this mode, every vm is assigned the same IP address (10.0.2.15) because each vm thinks they are on their own isolated network. And when they send their traffic via the gateway (10.0.2.2) VirtualBox rewrites the packets to make them appear as though they originated from the Host, rather than the Guest (running inside the Host).
This means that the Guest will work even as the Host moves from network to network (e.g. laptop moving between locations), and from wireless to wired connections too.
LO1 Network Bridged
Bridged Networking is used when you want your vm to be a full network citizen, i.e. to be an equal to your host machine on the network.
In this mode, a virtual NIC is "bridged" to a physical NIC on your host.
The effect of this is that each VM has access to the physical network in the same way as your host. It can access any service on the network such as external DHCP services, name lookup services, and routing information just as the host does
LO1 Network Internal
When you configure one or more vm's to sit on an Internal network, VirtualBox ensures that all traffic on that network stays within the host and is only visible to vm's on that virtual The internal network is a totally isolated network and so is very "quiet". This is good for testing when you need a separate, clean network, and you can create sophisticated internal networks with vm's that provide their own services to the internal network. (e.g. Active Directory, DHCP, etc).
LO1 Network Host only
Host‐only Networking is like Internal Networking in that you indicate which network the Guest sits on.
This looks very similar to Internal Networking but the host is now on "vboxnet0" and can provide DHCP services.
LO1 Network NAT with Port-forwarding What if you cart around a mobile‐demo or dev environment on, say, a
laptop and you have one or more vm's that you need other machines to connect into? And you are continually hopping onto different (customer?) networks.
In this scenario: NAT ‐ won't work because external machines need to connect in. Bridged ‐ possibly an option, but does your customer want you eating
IP addresses and can your software cope with changing networks? Internal ‐ we need the vm(s) to be visible on the network, so this is no
good. Host‐only ‐ same problem as above, we want external machines to
connect in to the vm's. Enter Port‐forwarding to save the day! Configure your vm's to use NAT networking; Add Port Forwarding rules; External machines connect to "host":"port number" and connections
are forwarded by VirtualBox to the guest:port number specified.
LO1 Network Task 1
How would you connect a vm guest to a network when running on a host using a wificonnection?
LO1 Environments. Environments for developers
Desktop server
arrays of servers cloud computing server solutions web servers
LO1 Costs reduction of hardware cost of ownership reduction of upgrade costs larger platforms for many servers
LO1 Task 2 Check to see if virtualbox is installed on your PC, If not download and install (When prompted for an admin login – use HND with a password of “G65D16123456”)
This is preparation for the next session.
LO1 Finally You can now do Assignment 1
What have we learnt today? Over to you?