User Tools

Site Tools


openstack_upc

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
openstack_upc [2014/04/03 11:09]
carbone
openstack_upc [2014/04/03 11:16] (current)
carbone
Line 1: Line 1:
  
-{{:upc-openstack_1_.png|}}+{{:upc-OpenStack_1_.png|}}
  
-==== UPC Openstack ​Cloud ====+==== UPC OpenStack ​Cloud ====
  
-**Purpose**:​ //The UPC OpenStack cloud currently runs OpenStack version Havana and its purpose is to provide compute and network resources required for experimentally driven research in the context of services in Clommunity. Furthermore,​ it is part of the federated ​Openstack ​multi-cloud in Clommunity along with [[:Openstack_KTH|KTH-1 Community Cloud]]. The current state of federation that has been achieved is in the Identity level (authentication).//​+**Purpose**:​ //The UPC OpenStack cloud currently runs OpenStack version Havana and its purpose is to provide compute and network resources required for experimentally driven research in the context of services in Clommunity. Furthermore,​ it is part of the federated ​OpenStack ​multi-cloud in Clommunity along with [[:OpenStack_KTH|KTH-1 Community Cloud]]. The current state of federation that has been achieved is in the Identity level (authentication).//​
  
-There is currently one Controller node that serves as a manager for both Compute and Network and two Compute nodes. Since the management network has to be private between all cloud hosts a VPN network has been created (using OpenVPN) as seen in the figure above. ​Openstack ​Compute (Nova) is configured to use libvirt-lxc,​ however, this adds a few restrictions to the operations that can be used such us stopping and restarting VMs among others due to lack of support.+There is currently one Controller node that serves as a manager for both Compute and Network and two Compute nodes. Since the management network has to be private between all cloud hosts a VPN network has been created (using OpenVPN) as seen in the figure above. ​OpenStack ​Compute (Nova) is configured to use libvirt-lxc,​ however, this adds a few restrictions to the operations that can be used such us stopping and restarting VMs among others due to lack of support.
  
-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 Controller node that routes all inbound/​outbound traffic to/from any tenant networks.+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 Controller node that routes all inbound/​outbound traffic to/from any tenant networks.
  
 The Hardware used in UPC-Cloud so far is the following: The Hardware used in UPC-Cloud so far is the following:
Line 16: Line 16:
     * **Specs**: 4x Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz - 8 GB RAM - 500 GB disk.     * **Specs**: 4x Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz - 8 GB RAM - 500 GB disk.
     * **OS**: Ubuntu 12.04 LTS     * **OS**: Ubuntu 12.04 LTS
-    * **Purpose**:​ 1)Openstack ​Compute Manager, 2)Openstack ​Network Manager ​+    * **Purpose**:​ 1)OpenStack ​Compute Manager, 2)OpenStack ​Network Manager ​
     ​     ​
  
Line 23: Line 23:
     * **Specs**: 4x Intel(R) Core(TM) i7-3770 CPU @ 3,40GHz - 16 GB RAM - 1 TB disk.     * **Specs**: 4x Intel(R) Core(TM) i7-3770 CPU @ 3,40GHz - 16 GB RAM - 1 TB disk.
     * **OS**: Ubuntu 12.04 LTS     * **OS**: Ubuntu 12.04 LTS
-    * **Purpose**:​ 1)Openstack ​Compute ​ 2) VPN Server+    * **Purpose**:​ 1)OpenStack ​Compute ​ 2) VPN Server
  
   * **Cloud9**   * **Cloud9**
Line 29: Line 29:
     * **Specs**: 4x Intel(R) Core(TM) i7-3770 CPU @ 3,40GHz - 16 GB RAM - 1 TB disk.     * **Specs**: 4x Intel(R) Core(TM) i7-3770 CPU @ 3,40GHz - 16 GB RAM - 1 TB disk.
     * **OS**: Ubuntu 12.04 LTS     * **OS**: Ubuntu 12.04 LTS
-    * **Purpose**: ​Openstack ​Compute+    * **Purpose**: ​OpenStack ​Compute
        
  ​**Plans**:​ Upgrade to Docker Hypervisor to enable supported container based virtualisation  ​**Plans**:​ Upgrade to Docker Hypervisor to enable supported container based virtualisation
openstack_upc.txt ยท Last modified: 2014/04/03 11:16 by carbone