vagrant-nfs_guest 1.0.0 → 1.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 66cdfd9f758ab3bc1e50e9ea5d4343947c7fe997
-  data.tar.gz: de8345cf62d07dc961fd16ac526ee5d51088e5f7
+  metadata.gz: f52967e02fc94ba4d117547cc137677bc1de3ab5
+  data.tar.gz: bf88cca048c195f8badc8b6073261668b2e7aa04
 SHA512:
-  metadata.gz: 2b9e37681172389e4e1e4f0e32fd3aabd16301aeba887899a170bea43f510663ab30840d59d40548a9f4001b911cc9f898ebd2e97630f6f36586b8eabe25acba
-  data.tar.gz: f9f80edd7590c1e1f7f784fdd367bdcf2f6cc371e62de03da28522343c8ad26599d3097209e185aea1e733b269173818111030e60a5b7d3253a98afcb6e22261
+  metadata.gz: e60fd214879b914bae527a3081e043fe7d3c8f28d8d61cba3c4ea1e29ab79e88dbf3302d74705f0adf779d82582ab66db17d572d3ab4f66acac271d5c425f098
+  data.tar.gz: 11d291a12f596f24fc04640038f6ffcc31edf71abd5ac5d2054e9da4f0367be8cc2d281ad50efd793dc815d7b5e5779ebdc93b6a484446718dfa09a58e765d85

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at opensource@learnosity.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/CONTRIBUTING.md

@@ -0,0 +1,37 @@
+## How can I contribute?
+
+#### I think I've found a bug
+
+* Firstly cool! We can hopefully make the project better by your discovery.
+
+* Before you submit an **Issue** please have a scan through any existing or closed Issues to make sure you've found something unique and unreported.
+  
+* If your issue seems unique and unreported, you should open a GitHub **Issue**.
+
+    * In your Issue report, please include as much information as you can.
+        * A detailed summary of the error you are seeing, and any information you think is relevant.
+        * A snippet of your Vagrantfile showing your `vagrant-nfs_guest` share, and the network settings used.
+        * The version of Vagrant, the host and guest operating system, which VM provider and it's version.
+        * A simple example Vagrantfile that demonstrates the error (this would be super useful if possible).
+        
+    * [You should then create a new issue](https://github.com/Learnosity/vagrant-nfs_guest/issues/new)
+        
+#### I've found a bug and I've fixed it!
+
+* Wow, awesome! This will help greatly!
+
+* Open a new GitHub pull request with the patch.
+
+* Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
+
+* **Please send us a PR, all input and suggestions welcome. All assistance greatfully accepted and appreciated.**
+
+#### I have an idea for a feature, can you please add it?
+
+`vagrant-nfs_guest` is used daily by our in-house team and is well used and tested. So any new feature that doesn't impact our daily usage or is very specific to your use-case probably won't get the investment in time you might require.
+
+We don't want to disappoint you, but the facts of life are sometimes _"if you want it done, you have to do it yourself"_. We will happily help you where we can, and we will joyfully accept any PRs you come up with, but we will not just add any feature that's requested.
+
+#### But it's a really really good idea!
+
+Again, if it's a world beating idea, put something together (even if it's pseudo-code) and a good document on the problem you're trying to fix and the value of your feature. Then submit a PR.

data/Gemfile

@@ -4,7 +4,7 @@ group :development do
   # We depend on Vagrant for development, but we don't add it as a
   # gem dependency because we expect to be installed within the
   # Vagrant environment itself using `vagrant plugin`.
-  gem "vagrant", :git => "git://github.com/mitchellh/vagrant.git"
+    gem "vagrant", :git => "https://github.com/mitchellh/vagrant.git", :tag => "v2.1.2"
 end
 
 group :plugins do

data/README.md

@@ -5,6 +5,7 @@
 - NEW: moved to version v1.0.0 as it's no longer a "beta" plugin, it's been well used and tested. So figured now is a good time.
 - NEW: `disabled` flag on shares now are properly respected
 - UPDATED: share directories on guest are no longer recursively `chown`.
+- NEW: Added VMware Fusion provider support.
 - Added untested support for Docker providers (Please raise any issues if they don't work!).
 - Added Parallels provider support
 - Redhat/CentOS guest support added.

data/example_box/Vagrantfile

@@ -7,8 +7,8 @@ VAGRANTFILE_API_VERSION = "2"
 Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
 
   # Every Vagrant virtual environment requires a box to build off of.
-  config.vm.box = "ubuntu/trusty64"           # ubuntu
-  #config.vm.box = "centos/7"                 # centos/7
+  #config.vm.box = "ubuntu/trusty64"           # ubuntu
+  config.vm.box = "centos/7"                 # centos/7
   #config.vm.box = "nrel/CentOS-6.5-x86_64"   # centos/6.5
 
   # Create a private network, which allows host-only access to the machine

data/lib/vagrant-nfs_guest/guests/linux/cap/nfs_server.rb

@@ -56,14 +56,16 @@ module VagrantPlugins
             machine.guest.capability(:nfs_check_command)
           end
 
-          def self.nfs_export(machine, ip, folders)
+          def self.nfs_export(machine, ips, folders)
             if !nfs_capable?(machine)
                 raise Errors::NFSServerMissing
             end
 
             if machine.guest.capability?(:nfs_setup_firewall)
               machine.ui.info I18n.t("vagrant_nfs_guest.guests.linux.nfs_setup_firewall")
-              machine.guest.capability(:nfs_setup_firewall, ip)
+              ips.each do |ip|
+                machine.guest.capability(:nfs_setup_firewall, ip)
+              end
             end
 
             nfs_exports_template = machine.guest.capability(:nfs_exports_template)
@@ -73,7 +75,7 @@ module VagrantPlugins
             output = Vagrant::Util::TemplateRenderer.render(
               nfs_exports_template,
               uuid: machine.id,
-              ips: [ip],
+              ips: ips,
               folders: folders,
               user: Process.uid)
 

data/lib/vagrant-nfs_guest/guests/redhat/cap/nfs_server.rb

@@ -8,6 +8,14 @@ module VagrantPlugins
             machine.communicate.test("test $(ps -o comm= 1) == 'systemd'")
           end
 
+          def self.firewalld?(machine)
+            machine.communicate.test("test $(command -v firewall-cmd)")
+          end
+
+          def self.firewalld_enabled?(machine)
+            machine.communicate.test("test $(firewall-cmd --state) == 'running'")
+          end
+
           def self.nfs_server_install(machine)
             machine.communicate.sudo("yum -y install nfs-utils nfs-utils-lib")
 
@@ -39,6 +47,19 @@ module VagrantPlugins
 
               nfs_start_command(machine)
             end
+
+            puts("*******************************")
+            puts(firewalld?(machine))
+            puts(firewalld_enabled?(machine))
+            puts("*******************************")
+
+            if firewalld?(machine) #and firewalld_enabled?(machine)
+              # add nfs rules if we have firewalld and it's enabled
+              machine.communicate.sudo("firewall-cmd --permanent --add-service=nfs")
+              machine.communicate.sudo("firewall-cmd --permanent --add-service=mountd")
+              machine.communicate.sudo("firewall-cmd --permanent --add-service=rpc-bind")
+              machine.communicate.sudo("firewall-cmd --reload")
+            end
           end
 
           def self.nfs_server_installed(machine)

data/lib/vagrant-nfs_guest/plugin.rb

@@ -20,6 +20,7 @@ require_relative "providers/virtualbox/plugin"
 require_relative "providers/parallels/plugin"
 require_relative "providers/docker/plugin"
 require_relative "providers/lxc/plugin"
+require_relative "providers/vmware_fusion/plugin"
 
 module VagrantPlugins
   module SyncedFolderNFSGuest

data/lib/vagrant-nfs_guest/providers/vmware_fusion/cap/nfs_settings.rb

@@ -0,0 +1,19 @@
+module VagrantPlugins
+  module SyncedFolderNFSGuest
+    module ProviderVMwareFusion
+      module Cap
+        def self.read_host_ip
+          # In practice, we need the host's IP on the vmnet device this VM uses.
+          # It seems a bit tricky to get the right one, so let's allow all.
+          return `for N in $(ifconfig | awk -F: '/vmnet/ { print $1; }'); do ifconfig $N | awk '/inet / { print $2; }'; done`.split("\n")
+        end
+
+        def self.nfs_settings(machine)
+          host_ip = self.read_host_ip
+          machine_ip = machine.provider.driver.read_ip
+          return host_ip, machine_ip
+        end
+      end
+    end
+  end
+end

data/lib/vagrant-nfs_guest/providers/vmware_fusion/plugin.rb

@@ -0,0 +1,15 @@
+require "vagrant"
+
+module VagrantPlugins
+  module SyncedFolderNFSGuest
+    class Plugin < Vagrant.plugin("2")
+      name "vmware_fusion-provider"
+      description "vagrant-vmware_fusion provider"
+
+      provider_capability(:vmware_fusion, :nfs_settings) do
+        require_relative "cap/nfs_settings"
+        ProviderVMwareFusion::Cap
+      end
+    end
+  end
+end

data/lib/vagrant-nfs_guest/synced_folder.rb

@@ -59,7 +59,7 @@ module VagrantPlugins
         end
 
         machine.ui.info I18n.t("vagrant_nfs_guest.actions.vm.nfs.exporting")
-        machine.guest.capability(:nfs_export, host_ip, mount_folders)
+        machine.guest.capability(:nfs_export, Array(host_ip), mount_folders)
       end
 
       protected

data/lib/vagrant-nfs_guest/version.rb

@@ -1,5 +1,5 @@
 module VagrantPlugins
   module SyncedFolderNFSGuest
-    VERSION = "1.0.0"
+    VERSION = "1.0.2"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-nfs_guest
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.2
 platform: ruby
 authors:
 - Alan Garfield
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-05-02 00:00:00.000000000 Z
+date: 2018-08-15 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -47,6 +47,8 @@ extra_rdoc_files: []
 files:
 - ".gitignore"
 - ".ruby-version"
+- CODE_OF_CONDUCT.md
+- CONTRIBUTING.md
 - Gemfile
 - LICENSE.txt
 - README.md
@@ -81,6 +83,8 @@ files:
 - lib/vagrant-nfs_guest/providers/parallels/plugin.rb
 - lib/vagrant-nfs_guest/providers/virtualbox/cap/nfs_settings.rb
 - lib/vagrant-nfs_guest/providers/virtualbox/plugin.rb
+- lib/vagrant-nfs_guest/providers/vmware_fusion/cap/nfs_settings.rb
+- lib/vagrant-nfs_guest/providers/vmware_fusion/plugin.rb
 - lib/vagrant-nfs_guest/synced_folder.rb
 - lib/vagrant-nfs_guest/version.rb
 - templates/locales/en.yml