Angel Luis Moya Gonzalez e5e169932f F #3440: Initial NSX driver commit (#3549)
* F #3440: Create and delete NSX networks

This allows to create and delete from command line both
NSX-V netwoks and NSX-T networks.

* F #1256: Allow attach created Opaque Networks

This allows to attach a new created Opaque Network
to a instance.

* F #3440: Allows attach/detach created NSX-V networks

Changes included:
Allow attach and detach nics to a VM from nsx-v networks
created from OpenNebula.
Improve function to retrieve nsx-t network identifier on vc

* M #-: Change Network types as constants

Created new constans into Network class to identify
the different types of networks
Also changed order to detect Network avoiding incorrect
detections due to its parent Classes

* F #3440 #1256: Added NSX info to monitor

Added the following NSX info to host monitor:
NSX_MANAGER: "NSX Manager | NSX-T Manager"
NSX_TYPE: "NSX-V | NSX-T"
NSX_VERSION: "NSX-V or NSX-T version"
NSX_URL: NSX Manager url

* F #3440: Add Transport Zones to monitor host info

If the folowing attributes are correct, the transport
zones are listed into the host monitor information:

NSX_MANAGER
NSX_TYPE
NSX_USER
NSX_PASSWORD

* F #3440: Change NSX parameters to Host object

Some parameters created in first instance in vnet object for
testing purposes, has been changed to its definitive placement,
the Host object.

* F #3440: Added NSX_STATUS

Added NSX_STATUS attribute, checking the following:

- NSX_USER 	(Check if attribute is setted)
- NSX_PASSWORD	(Check if attribute is setted)
- NSX_TYPE	(Check if attribute is setted)
- NSX_MANAGER	(Check if attribute is setted)
- Check a correct connection with NSX Manager

The result is shown in the attribute NSX_STATUS, that
should be NSX_STATUS = "OK" if all is correct.

* F #3440: Refactor and clean

Refactor code into classes and clean.

* F #3440: Clean and rubocop

Set url as base_url + section + parameter
Correction to avoid rubocop warnings

* F #3440: Rubocop fixes

Corrected rubocop warnings

* F #3440: Fix rubocop warnings on hooks

Fixed rubocop warnings on network hooks

* F #3440: Fix rubocop warning on nsx_driver.rb

* F #3440: Forgotten sleep to timeout

Added a forgotten sleep into a timeout secuence.
Added cosmetic changes to minimize code lines.
2019-07-31 18:25:22 +02:00
2019-07-23 18:15:57 +02:00
2009-01-19 18:37:57 +00:00
2019-02-19 07:03:58 -05:00
2019-06-26 18:49:26 +02:00

OpenNebula

Build Status

Description

OpenNebula is an open-source project delivering a simple but feature-rich and flexible solution to build and manage enterprise clouds and virtualized data centers.

Complete documentation: https://docs.opennebula.org

How to contribute: https://github.com/OpenNebula/one/wiki/How-to-Contribute-to-Development

Installation

Requirements

This machine will act as the OpenNebula server and therefore needs to have installed the following software:

  • ruby >= 1.8.7
  • sqlite3 >= 3.5.2
  • xmlrpc-c >= 1.06
  • openssl >= 0.9
  • ssh
  • sqlite3-ruby gem

Additionally, to build OpenNebula from source you need:

  • Development versions of the sqlite3, xmlrpc-c and openssl packages, if your distribution does not install them with the libraries.
  • scons >= 0.97
  • g++ >= 4
  • flex >= 2.5 (optional, only needed to rebuild the parsers)
  • bison >= 2.3 (optional, only needed to rebuild the parsers)
  • libxml2-dev
  • libvncserver-dev (optional, only needed to build svncterm_server)

Ruby Libraries Requirements

A set of gem requirements are needed to make several components work. We include a handy script to install them and the requirements. It is located at share/install_gems/install_gems and you should use it to install the required gems. You have more information at:

https://docs.opennebula.org/stable/integration/references/compile.html

If you want to install them manually here are the list of required rubygems:

  • OpenNebula and clients (plus cloud interfaces)

    • sqlite3
    • json
    • sequel
    • mysql
    • net-ldap
    • amazon-ec2
    • rack
    • sinatra
    • thin
    • uuidtools
    • curb
    • nokogiri
  • Sunstone server

    • json
    • rack
    • sinatra
    • thin
    • sequel
    • nokogiri

Optional Packages

These packages are not needed to run or build OpenNebula. They improve the performance of the user-land libraries and tools of OpenNebula, nor the core system. You will probably experiment a more responsive CLI.

First install rubygems and ruby development libraries

  • ruby-dev
  • rubygems
  • rake
  • make

Then install the following packages:

  • ruby xmlparser, some distributions include a binary package for this (libxml-parser-ruby1.8). If it is not available in your distribution install expat libraries with its development files and install xmlparser using gem:

      $ sudo gem install xmlparser --no-ri --no-rdoc
    

    Note the extra parameters to gem install. Some versions of xmlparser have problems building the documentation and we can use it without documentation installed.

  • ruby ox, fast xml parsing library:

      $ sudo gem install ox --no-ri --no-rdoc
    

Building

Compilation is done using scons command:

    $ scons [OPTION=VALUE]

The argument expression [OPTIONAL] is used to set non-default values for:

    OPTION      VALUE
    sqlite_db   path-to-sqlite-install
    sqlite      no if you don't want to build sqlite support
    mysql       yes if you want to build mysql support
    xmlrpc      path-to-xmlrpc-install
    parsers     yes if you want to rebuild flex/bison files
    new_xmlrpc  yes if you have an xmlrpc-c version >= 1.31
    sunstone    yes if you want to build sunstone minified files
    systemd     yes if you want to build systemd support
    svncterm    no if you want to skip building vnc support for LXD drivers

Installation

OpenNebula can be installed in two modes: system-wide, or in self-contained directory. In either case, you do not need to run OpenNebula as root. These options can be specified when running the install script:

    $ ./install.sh install_options

where install_options can be one or more of:

OPTION  VALUE
-u      user that will run OpenNebula, defaults to user executing
        install.sh
-g      group of the user that will run OpenNebula, defaults to user
        executing install.sh
-k      keep current configuration files, useful when upgrading
-d      target installation directory. If defined, it will specified
        the path for the self-contained install. If not defined, the
        installation will be performed system wide
-c      only install client utilities: OpenNebula cli, occi and ec2
        client files
-r      remove Opennebula, only useful if -d was not specified,
        otherwise rm -rf $ONE_LOCATION would do the job
-p      do not install OpenNebula Sunstone non-minified files
-G      install only OpenNebula Gate
-f      install only OpenNebula Flow
-h      prints installer help

Deployment

You can find the documentation about OpenNebula architecture, installation, configuration and references to configuration files in this documentation chapter:

https://docs.opennebula.org/stable/deployment/index.html

The reference about the main configuration file is located here:

https://docs.opennebula.org/stable/deployment/references/oned_conf.html

Contact

OpenNebula web page: https://opennebula.org

Development and issue tracking: https://github.com/OpenNebula/one/issues

Support: https://opennebula.org/support

License

Copyright 2002-2019, OpenNebula Project, OpenNebula Systems (formerly C12G Labs)

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Languages
JavaScript 35.5%
Ruby 27.1%
C++ 24.1%
Shell 3.9%
Python 3.4%
Other 5.8%