summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSachin Prabhu <sprabhu@redhat.com>2021-03-27 23:45:10 +0000
committerAnoop C S <anoopcs@cryptolab.net>2021-04-14 16:36:35 +0530
commitb955c7a4ea0e48cffefc2b7b957ffed49ae525fb (patch)
treed7f5cc2fc0008ce00db92ee8e71c1689a7dce0b5
parentfae1e877585c4dc2e6cb364d8f195399a12ec54e (diff)
downloadsamba-integration-b955c7a4ea0e48cffefc2b7b957ffed49ae525fb.tar.gz
samba-integration-b955c7a4ea0e48cffefc2b7b957ffed49ae525fb.tar.xz
samba-integration-b955c7a4ea0e48cffefc2b7b957ffed49ae525fb.zip
Add instructions for setting up a Fedora environment
Instructions for a freshly installed Fedora 33 environment. Signed-off-by: Sachin Prabhu <sprabhu@redhat.com>
-rw-r--r--README-FEDORA.md50
1 files changed, 50 insertions, 0 deletions
diff --git a/README-FEDORA.md b/README-FEDORA.md
new file mode 100644
index 0000000..9ff5783
--- /dev/null
+++ b/README-FEDORA.md
@@ -0,0 +1,50 @@
+The following instructions are for fresh install of Fedora 33.
+I will be running all the commands as a non-privileged user part of groups
+libvirt - to allow user to create virtual machines using libvirtd
+and wheel - to allow sudo access.
+
+Modify the steps accordingly for your setup.
+
+Ensure the following packages are installed
+> $ sudo dnf install qemu-kvm qemu-img git vagrant vagrant-libvirt ansible make libvirt-client
+
+Download and cache vagrant centos7 image.
+```
+$ vagrant box add "https://vagrantcloud.com/centos/7" --provider "libvirt"
+```
+
+For Fedora 33, we have to enable the use_session variable for vagrant libvirt vms to run properly. To do this, create a file ~/.vagrant.d/Vagrantfile with the following content
+```
+Vagrant.configure("2") do |config|
+ config.vm.provider :libvirt do |libvirt|
+ libvirt.qemu_use_session = false
+ end
+end
+```
+
+Git clone the samba-integration git repository.
+```
+$ git clone https://github.com/gluster/samba-integration.git
+```
+
+Build the test environment with the following command
+```
+$ cd samba-integration/
+$ make
+```
+
+If you encounter failures bringing up the vagrant vms, you can check for more details by switching into the vagrant directory and manually bring up the machine.
+```
+$ cd samba-integration/vagrant
+$ vagrant up
+```
+Clean up with a 'vagrant destroy -f' command when done.
+
+The most common fault seen is because of the location of the default storage pool which could lead to permission issues. In this case, edit the default storage pool and switch to a directory which can be accessed by your user.
+
+Before you can reinstall the cluster setup, you will want to clear up the existing machines. To do this, we will need to use the vagrant command to destroy the created vms.
+```
+$ cd samba-integration/vagrant
+$ vagrant destroy -f
+```
+This clears up all the vms created by the tool and the system is ready for a rebuild