User Tools

Site Tools


openstack_kth

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
openstack_kth [2014/04/03 11:16]
carbone
openstack_kth [2014/04/03 11:18] (current)
carbone
Line 10: Line 10:
  
 There are two controller nodes in this cloud to allow better load balancing and decoupling. The decoupling is achieved by separating network related management components with the rest.The first controller serves as an Image, Identity and Compute manager and the latter runs all network related services (Neutron virtual dhcp and layer 3 services). A VPN network has also been created to cover the management network isolation requirements of OpenStack. OpenStack Compute (Nova) is configured to use KVM as a hypervisor. In the initial prototype two low-end compute nodes have been added for experimentation purposes. There are two controller nodes in this cloud to allow better load balancing and decoupling. The decoupling is achieved by separating network related management components with the rest.The first controller serves as an Image, Identity and Compute manager and the latter runs all network related services (Neutron virtual dhcp and layer 3 services). A VPN network has also been created to cover the management network isolation requirements of OpenStack. OpenStack Compute (Nova) is configured to use KVM as a hypervisor. In the initial prototype two low-end compute nodes have been added for experimentation purposes.
-Network virtualisation is managed by standard OpenStack-Network (Neutron) components (Neutron l3-metadata-dhcp agents) built on OpenVSwitch technologies. Virtual network components (eg routers, networks) can be placed in all hosts since they are synced through Neutron-OVS agents running in each one respectively. Several network architectures can be achieved by using OpenStack-Network (multi-tier tenant networks) however, in our current configuration we assume by default a flat network (Guifi.net IPs) for the VMs. As seen in the figure, for this purpose, a virtual router has been placed in the Neutron Controller node that routes all inbound/​outbound traffic to/from any tenant networks. The plan is to upgrade ​tto Docker Hypervisor to enable supported container based virtualisation+Network virtualisation is managed by standard OpenStack-Network (Neutron) components (Neutron l3-metadata-dhcp agents) built on OpenVSwitch technologies. Virtual network components (eg routers, networks) can be placed in all hosts since they are synced through Neutron-OVS agents running in each one respectively. Several network architectures can be achieved by using OpenStack-Network (multi-tier tenant networks) however, in our current configuration we assume by default a flat network (Guifi.net IPs) for the VMs. As seen in the figure, for this purpose, a virtual router has been placed in the Neutron Controller node that routes all inbound/​outbound traffic to/from any tenant networks. The plan is to upgrade ​to Docker Hypervisor to enable supported container based virtualisation
  
 ==KTH-2 Cloud== ​ ==KTH-2 Cloud== ​
openstack_kth.txt ยท Last modified: 2014/04/03 11:18 by carbone