vLab at TEI Piraeus using OpenStack

680 views

Published on

Athens OpenStack User Group #OSATH
6th Meetup, 29th January 2014

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

  • Be the first to like this

No Downloads
Views
Total views
680
On SlideShare
0
From Embeds
0
Number of Embeds
28
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • The answer, apart from technological advancement is basically cost reduction.
    And all of these have cost reduction as a side effect.
    But I am going to talk about these more in a minute.
    What is a virtual lab?
  • From the end-user scope not much change. Basically, instead of using a computer, he logins on a remote computer.
    From the openstack scope, it is a project. Which means a private network for this set of virtual computers, a specific amount of administrators and moderators that have access to this lab. The virtualized network of an openstack project can benefit from additional features like a firewall or a load balancer if needed.
    If it's a repeating lab, for instance a semester. It is very helpful that you can create a semester reset button if you will. This will reset everything to the lab state before the start of a semester. User's work can be saved on a virtualized storage resource.
    If a lab requires special software or servers it can be included in the automations.
  • Join a class remotely if you ...
  • vLab at TEI Piraeus using OpenStack

    1. 1. vLab at TEI Piraeus using OpenStack Athens OpenStack User Group #OSATH 6th Meetup, 29th January 2014 Stefanos Kalantzis stef@nullstack.eu
    2. 2. vLab at TEI Piraeus using OpenStack OpenStack // Meet vLabs Why virtualize lab courses?  Cost reduction  Unified management  Automations osath6
    3. 3. vLab at TEI Piraeus using OpenStack vLab // What it is  A “tenant” inside OpenStack  Many single user VMs or one multi user VM  Required isolated services running for the vLab  Automate lab setup processes osath6
    4. 4. vLab at TEI Piraeus using OpenStack vLab // Cost  Consolidate labs on the same hardware  Provide ad-hoc remote access  Control hardware resources usage  Reuse or duplicate an existing vLab environment  Old lab equipment becomes useful as thin-clients osath6
    5. 5. vLab at TEI Piraeus using OpenStack osath6 vLab // Automations   Automations on provisioning, networking, VM instances and storage. Use of “templates” to provision VMs for each courses requirements (openstack-heat)  Easy initialization of a vLab  Only required vLabs are active based on schedules.
    6. 6. vLab at TEI Piraeus using OpenStack vLab // Unified management  Monitor usage on all vLabs (ceilometer)  Manage virtual networks (neutron)  Manage storage (Swift, Cinder, Glance)  One authentication service (keystone)  Easy control and mapping of acquired licenses to VMs osath6
    7. 7. vLab at TEI Piraeus using OpenStack OpenStack // Hardware osath6
    8. 8. vLab at TEI Piraeus using OpenStack OpenStack // Hardware  4x Primergy RX100 s7p ( 4 cores Intel Xeon @ 3.1GHz, 8GB ram, 2x 500GB hdd in raid1 )  1x Proliant DL145 (2x 2 cores AMD Opteron @ 2.2GHz, 4GB ram, 2x 200GB hdd in raid1)  1x V1910-48G layer 3 managed switch (48 gigabit ports)  other old equipment (PCs, switches, routers) osath6
    9. 9. vLab at TEI Piraeus using OpenStack osath6 teipir OpenStack // Physical Network proliant DL145 Link Aggregation V1910 (switch) n1 n2 primergy rx100 n1 n2 primergy rx100 n1 n2 primergy rx100 n1 n2 primergy rx100
    10. 10. vLab at TEI Piraeus using OpenStack osath6
    11. 11. vLab at TEI Piraeus using OpenStack osath6 OpenStack // Logical Network openstack internal network openstack external network oam network net-bios network 10 11 ovs 13 controller network compute teipir 12 router 10 10 11 ovs 13 compute 12 99 (switch) 10 10 99 vlan 13 - 10.30.0.0/24 vlan 10 - 10.0.0.0/24 vlan 11 - 10.10.0.0/24 vlan 12 - 10.20.0.0/24 VPN - oam 11 12 11 ovs 13 compute 12 10 11 13 12 ovs compute
    12. 12. vLab at TEI Piraeus using OpenStack osath6 OpenStack // network physical example 172.16.135.140 172.16.128.0/17 teipir router 10.0.0.1 switch link-aggregation eth0 eth1 bond0 10.0.0.11 bond0.13 br-ex network-node
    13. 13. vLab at TEI Piraeus using OpenStack osath6 172.16.135.140 router 10.0.0.1 teipir 172.16.128.0/17 OpenStack // openstack + physical example switch link-aggregation eth0 L3 - agent (NAT + iptables + dnsmasq) eth1 bond0 phy-br-ex int-br-ex 10.30.0.11 10.0.0.11 br-int bond0.10 br-ex bond0 int-br-inst L2 - agent (vlans + flow tables) bond0.13 phy-br-inst br-inst
    14. 14. vLab at TEI Piraeus using OpenStack Thank you for your attention! Stefanos Kalantzis stef@nullstack.eu osath6

    ×