vagrant-vsphere | VMware vSphere provider for Vagrant | Plugin library

by nsidc Ruby Version: v1.13.4 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | vagrant-vsphere Summary

vagrant-vsphere is a Ruby library typically used in Plugin applications. vagrant-vsphere has no bugs, it has no vulnerabilities and it has low support. However vagrant-vsphere has a Non-SPDX License. You can download it from GitHub.

This is a Vagrant 1.6.4+ plugin that adds a vSphere provider to Vagrant, allowing Vagrant to control and provision machines using VMware. New machines are created from virtual machines or templates which must be configured prior to using this provider. This provider is built on top of the RbVmomi Ruby interface to the vSphere API.

Support

Quality

Security

License

Reuse

Support

vagrant-vsphere has a low active ecosystem.

It has 597 star(s) with 163 fork(s). There are 55 watchers for this library.

It had no major release in the last 12 months.

There are 101 open issues and 76 have been closed. On average issues are closed in 173 days. There are 12 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of vagrant-vsphere is v1.13.4

Quality

vagrant-vsphere has 0 bugs and 8 code smells.

Security

vagrant-vsphere has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

vagrant-vsphere code analysis shows 0 unresolved vulnerabilities.

There are 2 security hotspots that need review.

License

vagrant-vsphere has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

vagrant-vsphere releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

vagrant-vsphere saves you 896 person hours of effort in developing the same functionality from scratch.

It has 2048 lines of code, 118 functions and 42 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of vagrant-vsphere

Get all kandi verified functions for this library.

vagrant-vsphere Key Features

No Key Features are available at this moment for vagrant-vsphere.

vagrant-vsphere Examples and Code Snippets

No Code Snippets are available at this moment for vagrant-vsphere.

Community Discussions

Trending Discussions on vagrant-vsphere

How to run ansible task based on the Vagrant provider

vagrant-vsphere: how to create a .box file?

QUESTION

How to run ansible task based on the Vagrant provider

Asked 2018-Dec-19 at 00:32

I have a vagrant job to create new VMs. Depending on the provider I pass to it, this could be created locally on Virtualbox, or on a Vsphere cluster with the vagrant-vsphere plugin.

Because of this, there are times when I want to run certain tasks on Virtualbox, and certain tasks on Vsphere. I figured the easiest way to do so would be to just pass a variable from Vagrant to ansible based on the provider. Roughly, this is what I have in my Vagrantfile so far.

...

ANSWER

Answered 2018-Dec-19 at 00:32

For this specific case, I think there is an easier way of achieving what you want. Ansible creates a series of facts for each host it runs against, which includes collecting virtualisation information for guests.Try adding the following task in one of your playbooks to see what I mean:

Source https://stackoverflow.com/questions/53842146

QUESTION

vagrant-vsphere: how to create a .box file?

Asked 2018-Mar-12 at 20:55

I want to use vagrant-vsphere and went through the steps described in https://github.com/nsidc/vagrant-vsphere/blob/master/README.md

Installation went fine. Now I am at this step:

After installing the plugin, you must create a vSphere box. The example_box directory contains a metadata.json file that can be used to create a dummy box with the command:

...

ANSWER

Answered 2018-Mar-12 at 20:55

Go to: https://github.com/nsidc/vagrant-vsphere/tree/master/example_box and download the metadata.json file. Move this file to your vagrant project directory and run the following command in your terminal:

Source https://stackoverflow.com/questions/49066021

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install vagrant-vsphere

Install using standard Vagrant plugin method:. This will install the plugin from RubyGems.org. Alternatively, you can clone this repository and build the source with gem build vSphere.gemspec. After the gem is built, run the plugin install command from the build directory.
The requirements for Nokogiri must be installed before the plugin can be installed. See the Nokogiri tutorial for detailed instructions. The plugin forces use of Nokogiri ~> 1.5 to prevent conflicts with older versions of system libraries, specifically zlib.

Support

Currently the only implemented actions are up, halt, reload, destroy, and ssh. up supports provisioning of the new VM with the standard Vagrant provisioners.

Find more information at: