apache/cloudstack
1
0
Fork 0
mirror of https://github.com/apache/cloudstack.git synced 2025-10-26 08:42:29 +01:00
Code Issues Packages Projects Releases Wiki Activity
cloudstack/tools/devcloud4
History
John Burwell 8d11511b1f Adds support for four position versions and optional db upgrades 
Often, patch and security releases do not require schema migrations or
data migrations.  However, if an empty upgrade class and associated
scripts are not defined, the upgrade process will break.  With this
change, if a release does not have an upgrade, a noop DbUpgrade is added
to the upgrade path.  This approach allows the upgrade to proceed and
for the database to properly reflect the installed version.  This change
should make the release process simpler as RMs no longer need to
rememeber to create this boilerplate code when starting a new release.

Beginning with the 4.8.2.0 and 4.9.1.0 releases, the project will
formally adopt a four (4) position release number to properly accomodate
rekeases that contain only CVE fixes.  The DatabaseUpgradeChecker and
Version classes made assumptions that they would always parse and
compare three (3) position version numbers.  This change adds the
CloudStackVersion value object that supports both three (3) and four (4)
version numbers.   It encapsulates version comparsion logic, as well as,
the rules to allow three (3) and four (4) to interoperate.

  * Modifies DatabaseUpgradeChecker to handle derive an upgrade path for
  a version that was not explicitly specified.  It determines the
  releases the first release before it with database migrations and uses
  that list as the basis for the list for version being calculated.  A
  noop upgrade is then added to the list which causes no schema changes
  or data migrations, but will update the database to the version.
  * Adds unit tests for the upgrade path calculation logic in
  DatabaseUpgradeChecker
  * Removes dummy upgrade logic for the 4.8.2.0 introduced in previous
  versions of this patch
  * Introduces the CloudStackVersion value object which parses and
  compares three (3) and four (4) position version numbers.  This class
  is intended to replace com.cloud.maint.Version.
  * Adds the junit-dataprovider dependency -- allowing test data to be
  concisely generated separately from the execution of a test case.
  Used extensively in the CloudStackVersionTest.

Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
2016-08-30 13:32:32 +05:30
..
advanced
Fixed box location on vagrant files
2015-09-22 15:04:01 -04:00
basic
Fixed box location on vagrant files
2015-09-22 15:04:01 -04:00
binary-installation-advanced
Added fix to binary installation vagrant files (CLOUDSTACK-8898)
2015-09-23 09:15:40 -04:00
binary-installation-basic
Added fix to binary installation vagrant files (CLOUDSTACK-8898)
2015-09-23 09:15:40 -04:00
common
Move Devcloud4 into main repository
2015-04-11 16:17:02 +01:00
.gitignore
Move Devcloud4 into main repository
2015-04-11 16:17:02 +01:00
pom.xml
Adds support for four position versions and optional db upgrades
2016-08-30 13:32:32 +05:30
prefill.sql
Move Devcloud4 into main repository
2015-04-11 16:17:02 +01:00
README.md
Move Devcloud4 into main repository
2015-04-11 16:17:02 +01:00

README.md

Devcloud 4

Introduction

The follow project aims to simplify getting a full Apache CloudStack environment running on your machine. You can either take the easy ride and run vagrant up in either one of the 'binary installation' directories or compile CloudStack yourself. See for instructions in the 'basic' and 'advanced' directories.

The included VagrantFile will give you:

  • Management

    • NFS Server
    • MySQL Server
    • Router
      • Cloudstack Management Server * (Only given in binary installation)

  • XenServer 6.2

Getting started

  1. Due to the large amount of data to be pulled from the Internet, it's probably not a good idea to do this over WiFi or Mobile data.

  2. Given the amount of virtual machines this brings up it is recommended you have atleast 8gb of ram before attempting this.

  3. Ensure your system has git installed.

  4. When on Windows, make sure you've set the git option autocrlf to false:

    git config --global core.autocrlf false

  5. Clone the repository:

    git clone https://github.com/imduffy15/devcloud4.git

  6. Download and Install VirtualBox

    On Windows7, the Xenserver VM crashed immediately after booting with a General Protection Fault. Installing VirtualBox version 4.3.6r91406 (https://www.virtualbox.org/wiki/Download_Old_Builds_4_3) fixed the problem, but only downgrade if the latest version does not work for you.

  7. Download and install Vagrant

  8. Ensure all Vagrant Plugins are installed:

    vagrant plugin install vagrant-berkshelf vagrant-omnibus

  9. Download and install ChefDK

Configure virtualbox

  1. Open virtualbox and navigate to its preferences/settings window.

  2. Click onto the network tab and then onto the host only network tab.

  3. Configure your adapters as follows:

    • On Windows, the adapternames are different, and map as follows:
      • vboxnet0: VirtualBox Host-Only Ethernet Adapter
      • vboxnet1: VirtualBox Host-Only Ethernet Adapter 2
      • vboxnet2: VirtualBox Host-Only Ethernet Adapter 3

    For Basic Networking you only need:

    vboxnet0
    • IPv4 IP address of 192.168.22.1
    • Subnet of 255.255.255.0
    • DHCP server disabled

    For Advanced Networking you will need:

    vboxnet1
    • IPv4 IP address of 192.168.23.1
    • Subnet of 255.255.255.0
    • DHCP server disabled
    vboxnet2
    • IPv4 IP address of 192.168.24.1
    • Subnet of 255.255.255.0
    • DHCP server disabled

Defaults

Management Server

  • IP: 192.168.22.5
  • Username: vagrant or root
  • Password: vagrant

Hypervisor

  • IP: 192.168.22.10
  • Username: root
  • Password: password