Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
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 using this provider.
This provider is built on top of the RbVmomi Ruby interface to the vSphere API.
version: 1.5.0
vagrant-vsphere (version: 1.5.0) is available from RubyGems.org
Install using standard Vagrant plugin method:
vagrant plugin install vagrant-vsphere
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.
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:
tar cvzf dummy.box ./metadata.json
This can be installed using the standard Vagrant methods or specified in the Vagrantfile.
After creating the dummy box, make a Vagrantfile that looks like the following:
Vagrant.configure("2") do |config|
config.vm.box = 'dummy'
config.vm.box_url = './example_box/dummy.box'
config.vm.provider :vsphere do |vsphere|
vsphere.host = 'HOST NAME OF YOUR VSPHERE INSTANCE'
vsphere.compute_resource_name = 'YOUR COMPUTE RESOURCE'
vsphere.resource_pool_name = 'YOUR RESOURCE POOL'
vsphere.template_name = '/PATH/TO/YOUR VM TEMPLATE'
vsphere.name = 'NEW VM NAME'
vsphere.user = 'YOUR VMWARE USER'
vsphere.password = 'YOUR VMWARE PASSWORD'
end
end
And then run vagrant up --provider=vsphere
.
The bulk of this configuration can be included as part of a custom box. See the Vagrant documentation and the Vagrant AWS provider for more information and an example.
Currently the only implemented actions are up
, halt
, reload
, destroy
,
and ssh
.
up
supports provisioning of the new VM with the standard Vagrant provisioners.
This provider has the following settings, all are required unless noted:
host
- IP or name for the vSphere APIinsecure
- Optional verify SSL certificate from the hostuser
- user name for connecting to vSpherepassword
- password for connecting to vSphere. If no value is given, or the
value is set to :ask
, the user will be prompted to enter the password on
each invocation.data_center_name
- Optional datacenter containing the computed resource,
the template and where the new VM will be created, if not specified the first
datacenter found will be usedcompute_resource_name
- Required if cloning from template the name of the
host containing the resource pool for the new VMresource_pool_name
- the resource pool for the new VM. If not supplied, and
cloning from a template, uses the root resource poolclone_from_vm
- Optional use a virtual machine instead of a template as
the source for the cloning operationtemplate_name
- the VM or VM template to clone (including the full folder path)vm_base_path
- Optional path to folder where new VM should be created, if
not specified template's parent folder will be usedname
- Optional name of the new VM, if missing the name will be auto
generatedcustomization_spec_name
- Optional customization spec for the new VMdata_store_name
- Optional the datastore where the VM will be locatedlinked_clone
- Optional link the cloned VM to the parent to share virtual
disksproxy_host
- Optional proxy host name for connecting to vSphere via proxyproxy_port
- Optional proxy port number for connecting to vSphere via
proxyvlan
- Optional vlan to connect the first NIC tomemory_mb
- Optional Configure the amount of memory (in MB) for the new VMcpu_count
- Optional Configure the number of CPUs for the new VMmac
- Optional Used to set the mac address of the new VMcpu_reservation
- Optional Configure the CPU time (in MHz) to reserve for this VMmem_reservation
- Optional Configure the memory (in MB) to reserve for this VMaddressType
- Optional Configure the address type of the
vSphere Virtual Ethernet Cardcustom_attribute
- Optional Add a
custom attribute
to the VM upon creation. This method takes a key/value pair,
e.g. vsphere.custom_attribute('timestamp', Time.now.to_s)
, and may be called
multiple times to set different attributes.To clone from an existing VM rather than a template, set clone_from_vm
to
true. If this value is set, compute_resource_name
and resource_pool_name
are
not required.
template_name
setting would be:vsphere.template_name = "vagrant-templates/ubuntu-lucid-template"
vm_base_path
would be:vsphere.vm_base_path = "vagrant-machines"
To set a static IP, add a private network to your vagrant file:
config.vm.network 'private_network', ip: '192.168.50.4'
The IP address will only be set if a customization spec name is given. The customization spec must have network adapter settings configured with a static IP address(just an unused address NOT the address you want the VM to be). The config.vm.network line will overwrite the ip in the customization spec with the one you set. For each private network specified, there needs to be a corresponding network adapter in the customization spec. An error will be thrown if there are more networks than adapters.
The name for the new VM will be automagically generated from the Vagrant machine name, the current timestamp and a random number to allow for simultaneous executions.
This is useful if running Vagrant from multiple directories or if multiple machines are defined in the Vagrantfile.
This sets the addressType of the network adapter, for example 'Manual' to be able to set a manual mac address. This value may depend on the version of vSphere you use. It may be necessary to set this in combination with the mac field, in order to set a manual mac address. For valid values for this field see VirtualEthernetCard api documentation of vSphere.
vsphere.addressType = 'Manual'
To set a static MAC address, add a vsphere.mac
to your Vagrantfile
.
In some cases you must also set vsphere.addressType
(see above)
to make this work:
vsphere.mac = '00:50:56:XX:YY:ZZ'
Take care to avoid using invalid or duplicate VMware MAC addresses, as this can easily break networking.
ESXi is not supported. Make sure to connect to a vCenter server and not directly to an ESXi host. ESXi vs vCenter
If you have permission issues:
VAGRANT_INSTANCE_NAME = "vagrant-vsphere"
Vagrant.configure("2") do |config|
config.vm.box = 'vsphere'
config.vm.box_url = 'https://vagrantcloud.com/ssx/boxes/vsphere-dummy/versions/0.0.1/providers/vsphere.box'
config.vm.hostname = VAGRANT_INSTANCE_NAME
config.vm.define VAGRANT_INSTANCE_NAME do |d|
end
config.vm.provider :vsphere do |vsphere|
vsphere.host = 'vsphere.local'
vsphere.name = VAGRANT_INSTANCE_NAME
vsphere.compute_resource_name = 'vagrant01.vsphere.local'
vsphere.resource_pool_name = 'vagrant'
vsphere.template_name = 'vagrant-templates/ubuntu14041'
vsphere.vm_base_path = "vagrant-machines"
vsphere.user = 'vagrant-user@vsphere'
vsphere.password = '***************'
vsphere.insecure = true
vsphere.custom_attribute('timestamp', Time.now.to_s)
end
end
vagrant up --provider=vsphere
vagrant ssh
vagrant destroy
See
CHANGELOG.md
.
See
DEVELOPMENT.md
.
The Vagrant vSphere Provider is licensed under the MIT license. See LICENSE.txt.
This software was developed by the National Snow and Ice Data Center with funding from multiple sources.
FAQs
Unknown package
We found that wh-vagrant-vsphere demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.