$ vagrant up prod-worker01 ... Copy iso file /usr/share/virtualbox/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso Mounting Virtualbox Guest Additions ISO to: /mnt mount: /mnt: WARNING: device write-protected, mounted read-only. Installing Virtualbox Guest Additions 6.0.24 - guest version is 5.2.0 Verifying archive integrity... All good. Uncompressing VirtualBox 6.0.24 Guest Additions for Linux........ VirtualBox Guest Additions installer Copying additional installer modules ... Installing additional modules ... VirtualBox Guest Additions: Starting. VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules. This may take a while. VirtualBox Guest Additions: To build modules for other installed kernels, run VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup <version> VirtualBox Guest Additions: or VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup all VirtualBox Guest Additions: Building the modules for kernel 4.19.0-10-amd64. update-initramfs: Generating /boot/initrd.img-4.19.0-10-amd64 VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted An error occurred during installation of VirtualBox Guest Additions 6.0.24. Some functionality may not work as intended. In most cases it is OK that the "Window System drivers" installation failed. Unmounting Virtualbox Guest Additions ISO from: /mnt Got different reports about installed GuestAdditions version: Virtualbox on your host claims: 5.2.0 VBoxService inside the vm claims: 6.0.24 Going on, assuming VBoxService is correct... Got different reports about installed GuestAdditions version: Virtualbox on your host claims: 5.2.0 VBoxService inside the vm claims: 6.0.24 Going on, assuming VBoxService is correct... ==> prod-worker01: Setting hostname... ==> prod-worker01: Configuring and enabling network interfaces... ==> prod-worker01: Installing NFS client... ==> prod-worker01: Exporting NFS shared folders... ==> prod-worker01: Preparing to edit /etc/exports. Administrator privileges will be required... ==> prod-worker01: Mounting NFS shared folders... The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Sep 28 2020
This was now just a matter of doing the clickity click on all hosts. They're now using the dedicated vlan.
Build is green
I've added a bridge vmbr443 to all hypervisors.
Build is green
Build is green
Explicit a bit the checks
rework commit message
Build is green
Build is green
Build is green
Rebase
Rebase
Rebase
Build is green
I wanted to rename the bridges on the proxmox hosts to something clearer (like vmbr-staging) but it turns out that proxmox only supports bridges named /vmbr\d+/. Ugh.
Should be a little more detailed.
Can you also remove the xmlns declaration in the "empty" XML data file?
If whatever component before BPS has its flush called with no object_types, it depends on the impl of this component how it chains well. As is, it should either chain down the arg unprocessed (from *args/**kwargs for example, what I have done for all proxies before I understood the getattr hooks), call it without this arg or give it a valid value like OBJECT_TYPES (which could be shared). In short intermediate should not have an invalid default passed down verbatim.
The case of concrete storage is not clear, because they don't chain call it nor need it in the first place. So any value is OK.
We have no other component than BPS that would do something with this (buffering) interface though, and it maybe would not make sense to have another.
(I'll note that the buffer storage usually comes *before* the RPC client, so the actual concern is probably moot. But the apparent mismatch in default arguments between different implems might lead to surprising behavior in the future.)
What happens when we have the following layering:
Build is green
Build is green
Tested on storage and loader-core as seen with mr grep '\.flush('.
Build is green
- rebase
- add the vagrant configuration
I forgot to mention: sharding archive/ and meta/ as archive/XX/ and meta/XX/ is also an important one, but probably not a blocker for an initial merge into master.
However, it might be more convenient to implement it right away rather than having to add it later. Up to you.
This is amazing, I didn't expect it to reach this level of functionality so quickly, kudos! :-)
rebase
Switch the default test branch to staging
- Add a script to avoid to commit each change before being able to test it (watch-vagrant-conf)
- Update the documentation accordingly
- Declare the admin-inventory server
Build is green
Change the commit message according to the diff's feedback
Build is green
Build is green
- rebase
- Remove the now useless CASS_DRIVER_NO_CYTHON option
fix typo on the commit message
Rebase
Please improve the wording on the README commit message: