Roger Luethi c92207bba3 labs: remove Vagrant files
This patch removes the files used by Vagrant to use the labs scripts.

Vagrant support is currently broken. The most pressing issue is that
some OpenStack software needs the VM rebooted after the distro software
updates, but doing that with Vagrant would take an extra effort. Same
goes for adding snapshots.

The presence of Vagrant-specific files confused quite a few people who
gained the impression that it is a requirement when it has always been
an alternative to osbash.

If there is sufficient interest in Vagrant support, we can add it back
later.

Change-Id: I7edfac1bb7c657d30acda0605a078c39d5fa997a
2014-10-28 11:30:16 +01:00
..
2014-10-28 11:30:16 +01:00
2014-06-16 16:55:23 +05:30
2014-10-27 17:21:41 +01:00
2014-06-16 16:55:23 +05:30
2014-10-28 11:30:16 +01:00
2014-06-16 16:55:23 +05:30
2014-06-12 18:15:41 +05:30
2014-06-12 18:15:41 +05:30
2014-09-19 17:20:08 +02:00

Training Labs

About

Training Labs will provide scripts to automate the creation of the Training Environment.

Note: Training Labs are specifically meant for OpenStack Training and are specifically tuned as per Training Manuals repo.

Pre-requisite

How to run the scripts

  1. Clone the training-guides repo which contains scripts in the labs section that will install multi-node OpenStack automatically.

     $ git clone git://git.openstack.org/openstack/training-guides
    
  2. Go to the labs folder

     $ cd training-guides/labs
    
  3. Run the script:

     $ ./osbash -b cluster
    

This will do the complete installation for all the nodes - Controller, Compute and Network.

To build one node at a time you can run

    $ ./osbash -b <nodename>

Note The node names can be 'controller', 'compute', 'network'.

Note: The Controller node needs to be installed and running while building one of the other nodes.

Controller node VM: $ ./osbash -b controller

Network node VM: $ ./osbash -b network

Compute node VM: $ ./osbash -b compute

For more help you can check

    $ ./osbash --help

This will take some time to run the first time.

What the script installs

Running this will automatically spin up 3 virtual machines in VirtualBox:

  • Controller node
  • Network node
  • Compute node

Now you have a multi-node deployment of OpenStack running with the below services installed.

OpenStack services installed on Controller node:

  • Keystone

  • Horizon

  • Glance

  • Nova

    • nova-api
    • nova-scheduler
    • nova-consoleauth
    • nova-cert
    • nova-novncproxy
    • python-novaclient
  • Neutron

    • neutron-server
  • Cinder

Openstack services installed on Network node:

  • Neutron

    • neutron-plugin-openvswitch-agent
    • neutron-l3-agent
    • neutron-dhcp-agent
    • neutron-metadata-agent

Openstack Services installed on Compute node:

  • Nova

    • nova-compute
  • Neutron

    • neutron-plugin-openvswitch-agent

How to access the services

There are two ways to access the services:

  • OpenStack Dashboard (horizon)

You can access the dashboard at: http://192.168.100.51/horizon

Admin Login:

Username: admin

Password: admin_pass

Demo User Login:

Username: demo

Password: demo_pass

  • SSH

You can ssh to each of the nodes:

    $ ssh controller@10.10.10.51

    $ ssh compute@10.10.10.51

    $ ssh network@10.10.10.51

Credentials for all nodes:

Username: osbash

Password: osbash

After you have ssh access, you need to source the OpenStack credentials in order to access the services.

Two credential files are present on each of the nodes: demo-openstackrc.sh admin-openstackrc.sh

Source the following credential files

For Admin user privileges:

    $ source admin-openstackrc.sh

For Demo user privileges:

    $ source demo-openstackrc.sh

Now you can access the OpenStack services via CLI.

BluePrints

Mailing Lists, IRC

  • To contribute please hop on to IRC on the channel #openstack-doc on IRC freenode or write an e-mail to the OpenStack Manuals mailing list openstack-docs@lists.openstack.org.

NOTE: You might consider registering on the OpenStack Manuals mailing list if you want to post your e-mail instantly. It may take some time for unregistered users, as it requires admin's approval.

Sub-team leads

Feel free to ping Roger or Pranav on the IRC channel #openstack-doc regarding any queries about the Labs section.

  • Roger Luethi ** Email: rl@patchworkscience.org ** IRC: rluethi

  • Pranav Salunke ** Email: dguitarbite@gmail.com ** IRC: dguitarbite

Meetings

To follow the weekly meetings for OpenStack Training, please refer to the following link.

For IRC meetings, refer to the wiki page on training manuals. https://wiki.openstack.org/wiki/Meetings/training-manual

Wiki

Follow various links on OpenStack Training Manuals here: https://wiki.openstack.org/wiki/Training-guides