There’s a new release of BigV’s client software – hurrah! So you are now able to “log in” or regenerate your profile on more than one machine. You can change your password rather than have to copy your .bigv folder around when (re)installing. The SSH key management is back, so you shouldn’t keep getting those prompts about host keys. You can create a VM with a CD-ROM ready inserted to speed installations.
More significantly you can also now create and delete usernames for other people – this means:
- you can use those handy privilege delegation commands to share a BigV account with other people;
- any users you create can log in and create their own BigV accounts that are nothing to do with you.
So if you have friends who would like BigV accounts, you now have the power to provide them with one.
There were also a two things I’d forgotten to document: did you know you can incorporate bigv invocation into other programs through YAML and batch modes? Or that there is an interactive mode which saves you entering your password every time you run bigv? They were always sat there in the interactive help, but I’d not written them up until now.
Update instructions are as usual: if you’re using Debian or Ubuntu you can “apt-get update; apt-get install bigv”. Everyone else, go to http://bigv.io/download to grab the latest tarball or installer. There are some Redhat / Fedora / CentOS RPMs that I’ve not fully tested but I hope to post in the next fortnight. Thanks to Jamie Nguyen for doing this work for us.
Finally, Bytemark is turning 10 years old this year; I should soon have good news about the end of BigV’s beta period, and a launch this summer.
So does that mean that no more beta accounts are being given out? Or could a kind soul that already has one provide me with a new one through the new system?
There will be some more beta accounts, more frequent in fact, but they will be keyless. I am just preparing an announcement but making sure I am confident about the time line to a full commercial launch before that goes out
Excellent, I’m excited.
Thanks for updates Matthew. How “sure” are you in reliability of your setups nowdays? I am reffering to example disk outage other day and similar. I know you are ready to left Beta so you think issues are now minimized ?
A.
BTW, just downloaded lates client (as I recently reinstalled my OS and had no bigv at all) and I got this:
root@xubuntu:/home/amar# sh bigv_setup.sh
-e *** The ‘lsb_release’ command could not be found
-e *** Run ‘sudo apt-get install lsb’ on Debian/Ubuntu
-e *** Run ‘sudo yum install redhat-lsb’ on RHEL/CentOS/Fedora
This is on 11.10 Xubuntu. I do have lsb_release:
root@xubuntu:/home/amar# lsb_release
LSB Version: core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch:cxx-3.0-ia32:cxx-3.0-noarch:cxx-3.1-ia32:cxx-3.1-noarch:cxx-3.2-ia32:cxx-3.2-noarch:cxx-4.0-ia32:cxx-4.0-noarch:desktop-3.1-ia32:desktop-3.1-noarch:desktop-3.2-ia32:desktop-3.2-noarch:desktop-4.0-ia32:desktop-4.0-noarch:graphics-2.0-ia32:graphics-2.0-noarch:graphics-3.0-ia32:graphics-3.0-noarch:graphics-3.1-ia32:graphics-3.1-noarch:graphics-3.2-ia32:graphics-3.2-noarch:graphics-4.0-ia32:graphics-4.0-noarch:printing-3.2-ia32:printing-3.2-noarch:printing-4.0-ia32:printing-4.0-noarch:qt4-3.1-ia32:qt4-3.1-noarch
Is there any quick fix for this as it seems I cant access my BigV now at all : )
Sorry that was my fault for uploading a newer version of the setup script that wasn’t ready. Now reverted, should work again on Debian & Debian-alikes.