Difference between revisions of "Vnx-labo-openstack"

From VNX
Jump to: navigation, search
Line 11: Line 11:
 
</ul>
 
</ul>
  
<li>Openstack Ocata:</li>
+
<li>'''Openstack Ocata:'''</li>
 
<ul>
 
<ul>
 
<li>[[Vnx-labo-openstack-4nodes-classic-ovs-ocata|Four-nodes-classic-openvswitch]]: a basic scenario using Openstack Ocata made of four virtual machines: a controller, a network node and two compute nodes all based on LXC. The deployement scenario used is [http://docs.openstack.org/mitaka/networking-guide/scenario-classic-ovs.html Classic with Open vSwitch]</li>
 
<li>[[Vnx-labo-openstack-4nodes-classic-ovs-ocata|Four-nodes-classic-openvswitch]]: a basic scenario using Openstack Ocata made of four virtual machines: a controller, a network node and two compute nodes all based on LXC. The deployement scenario used is [http://docs.openstack.org/mitaka/networking-guide/scenario-classic-ovs.html Classic with Open vSwitch]</li>
 
</ul>
 
</ul>
  
<li>Openstack Mitaka:</li>
+
<li>'''Openstack Mitaka:'''</li>
 
<ul>
 
<ul>
 
<li>[[Vnx-labo-openstack-4nodes-classic-ovs-mitaka|Four-nodes-classic-openvswitch]]: a basic scenario using Openstack Mitaka made of four virtual machines: a controller based on LXC and a network and two compute nodes based on KVM. The deployement scenario used is [http://docs.openstack.org/mitaka/networking-guide/scenario-classic-ovs.html Classic with Open vSwitch]</li>
 
<li>[[Vnx-labo-openstack-4nodes-classic-ovs-mitaka|Four-nodes-classic-openvswitch]]: a basic scenario using Openstack Mitaka made of four virtual machines: a controller based on LXC and a network and two compute nodes based on KVM. The deployement scenario used is [http://docs.openstack.org/mitaka/networking-guide/scenario-classic-ovs.html Classic with Open vSwitch]</li>
 
</ul>
 
</ul>
  
<li>Openstack Liberty:</li>
+
<li>'''Openstack Liberty:'''</li>
 
<ul>
 
<ul>
 
<li>[[Vnx-labo-openstack-3nodes-basic-liberty|Liberty 3-nodes-basic]]: a basic scenario using Openstack Liberty made of three KVM virtual machines: a controller with networking capabilities and two compute nodes.</li>
 
<li>[[Vnx-labo-openstack-3nodes-basic-liberty|Liberty 3-nodes-basic]]: a basic scenario using Openstack Liberty made of three KVM virtual machines: a controller with networking capabilities and two compute nodes.</li>
Line 27: Line 27:
 
</ul>
 
</ul>
  
<li>Openstack Kilo:</li>
+
<li>'''Openstack Kilo:'''</li>
 
<ul>
 
<ul>
 
<li>[[Vnx-labo-openstack-4nodes-basic-kilo|Kilo 4-nodes-basic]]: a basic scenario using Openstack Kilo made of four virtual machines: a controller based on LXC and a network node and two compute nodes based on KVM.</li>
 
<li>[[Vnx-labo-openstack-4nodes-basic-kilo|Kilo 4-nodes-basic]]: a basic scenario using Openstack Kilo made of four virtual machines: a controller based on LXC and a network node and two compute nodes based on KVM.</li>

Revision as of 14:51, 26 August 2019

VNX Openstack laboratories

This is a set of Openstack tutorial scenarios designed to experiment with Openstack free and open-source software platform for cloud-computing.

Several tutorial scenarios are available covering Kilo, Liberty and Mitaka Openstack versions and several deployment configurations:

  • Openstack Stein:
    • Four-nodes-classic-openvswitch: a basic scenario using Openstack Stein (April 2019) made of four virtual machines: a controller, a network node and two compute nodes all based on LXC.
  • Openstack Ocata:
  • Openstack Mitaka:
  • Openstack Liberty:
    • Liberty 3-nodes-basic: a basic scenario using Openstack Liberty made of three KVM virtual machines: a controller with networking capabilities and two compute nodes.
    • Liberty 4-nodes-legacy-openvswitch: a basic scenario using Openstack Liberty made of four virtual machines: a controller based on LXC and a network and two compute nodes based on KVM. The deployement scenario used is Legacy with Open vSwitch
  • Openstack Kilo:
    • Kilo 4-nodes-basic: a basic scenario using Openstack Kilo made of four virtual machines: a controller based on LXC and a network node and two compute nodes based on KVM.