# Pulplift on Mac Issues

Using virtualbox on an Intel MAC

* Provisioning takes 2 hours
* An hour to do the API provision
* An hour to do build the node modules (the UI)
* Possibly sshfs is slower on Mac. Possibly shared folders.
* DNS does not seem to be working
* The API page, can be accessed by localhost:8080
* But the content app is configured for the DNS entry
* Tried: https://github.com/devopsgroup-io/vagrant-hostmanager
* But the URLs and the IP address do not point to anything (gets an empty page like for an address that doesn't exist)
* Zita couldn't get virtualbox running on the mac at all

MacOS Big Sur/virtualbox - brew cask install virtualbox - errors - googling - dropping cask helped
Vagrant status doesn’t give me recommended fedora34
vagrant up --provider=virtualbox pulp3-source-fedora33 returns error /opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/lib/vagrant/action/builtin/mixin_synced_folders.rb:140:in `block in synced_folders': Internal error. Report this as a bug. Invalid: sshfs (RuntimeError) - googling - vagrant plugin install vagrant-sshfs - helped
==> pulp3-source-fedora33: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.


Command: ["startvm", "bd48e63d-aeaf-41d8-b6d8-233a72ed9e37", "--type", "headless"]


Stderr: VBoxManage: error: The virtual machine 'pulp_installer_pulp3-source-fedora33_1623678260487_19213' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine - googling - 

* probable fix: https://stackoverflow.com/a/52813517/2930194

* Galaxy NG vagrant instructions: https://github.com/ansible/galaxy_ng/wiki/Vagrant-dev-environment

## Mike's test case on a Big Sur Intel Macbook Pro (15-inch, 2017):
* Install [virtualbox 6.1.22 from dmg](https://download.virtualbox.org/virtualbox/6.1.22/VirtualBox-6.1.22-144080-OSX.dmg)
* Afterwards, went into macos security to enable it
* Note: [6.1.18 is the supposed BigSur release](https://www.virtualbox.org/wiki/Changelog-6.1#v22), but there could be addtl fixes since then
* Install [vagrant 2.2.16 from dmg](https://releases.hashicorp.com/vagrant/2.2.16/vagrant_2.2.16_x86_64.dmg)
* Afterwards:
* `vagrant plugin install vagrant-hostmanager`
* `vagrant plugin install vagrant-sshfs`
* Install brew
* Install pip3
* `pip3 install ansible`
* Got 4.2.0
* Exact local.dev-config.yml from https://github.com/ansible/galaxy_ng/wiki/Vagrant-dev-environment
* `git checkout 3.11`
* On vagrant up, prompted for sudo.
* /etc/hosts was updated
* Could probably eliminate this with vagrant-hostmanager instructions
* this loads just fine: http://pulp3-source-fedora33.mdepaulo-mac.example.com:8080/pulp/api/v3/status/
* about 10 minutes to get to the pulp-devel role
* about 9 minutes to build the UI
* About 6 minutes to the end
* About 25 minutes total
* Verified that the VM is using sshfs for /home/vagrant/devel , even during build
* http://pulp3-source-fedora33.mdepaulo-mac.example.com:8080/ui/ does not load
* p7zip benchmark:
* `sudo dnf install -y p7zip`
* `7za b`
* last line shows these last 2 numbers: 3154 (single) / 10903 (threaded)
* fio on sshfs:
* `/home/vagrant/devel`
* `fio --name=random-write --ioengine=posixaio --rw=randwrite --bs=4k --numjobs=1 --size=4g --iodepth=1 --runtime=60 --time_based --end_fsync=1`
* WRITE: bw=963KiB/s (986kB/s), 963KiB/s-963KiB/s (986kB/s-986kB/s), io=63.8MiB (66.9MB), run=67854-67854msec

## Mike's test case 2 on a Big Sur Intel Macbook Pro (15-inch, 2017):
* Switched to installing vbox via brew
* Switched to installing vagrant via brew
* Afterwards:
* `vagrant plugin install vagrant-sshfs`
* Switched to installing ansible via brew
* about 10 minutes to get to the pulp-devel role