I was asked today if it was possible to create a 2 host stretched cluster using a vSAN Standard license or a ROBO Standard license. First of all, from a licensing point of view the EULA states you are allowed to do this with a Standard license:
A Cluster containing exactly two Servers, commonly referred to as a 2-node Cluster, can be deployed as a Stretched Cluster. Clusters with three or more Servers are not allowed to be deployed as a Stretched Cluster, and the use of the Software in these Clusters is limited to using only a physical Server or a group of physical Servers as Fault Domains.
I figured I would give it a go in my lab. Exec summary: worked like a charm!
Loaded up the ROBO license:
Go to the Fault Domains & Stretched Cluster section under “Virtual SAN” and click Configure. And one host to “preferred” and one to “secondary” fault domain:
Select the Witness host:
Select the witness disks for the vSAN cluster:
And then the 2-node stretched cluster is formed using a Standard or ROBO license:
Of course I tried the same with 3 hosts, which failed as my license does not allow me to create a stretched cluster larger than 1+1+1. And even if it would succeed, the EULA clearly states that you are not allowed to do so, you need Enterprise licenses for that.
There you have it. Two host stretched using vSAN Standard, nice right?!
"Two host stretched vSAN cluster with Standard license?" originally appeared on Yellow-Bricks.com. Follow me on twitter - @DuncanYB.
Star Wars VIII has a name: The Last Jedi.
As is custom, we will now endlessly and thoroughly analyze a single image for as much signal as possible. My first thought: the typeface color is red. My second thought: in my head, each of the original trilogy movies is associated with a color.
Update: As Dan McClain points out on Twitter, the color matches the lightsaber of Luke, Vader, then Luke again.
I have two accounts on GitHub: Personal and work. How do I access both from the same computer without getting them confused? I have two different ssh keys and use
.ssh/config to do the right thing. Some bash aliases also help.
Why is it important to me that I keep these two accounts separate?
First, certain repos can only be accessed from one account or the other. Public repos can be accessed from either, but private repos are not so lucky.
Second, I want the commit logs for different projects should reflect whether I am "Tom the person" or "Tom the employee". My work-related repos shouldn't be littered with my personal email address. It is ugly and, more importantly, it would mean that someone searching for my commits would have to do two searches: one for each of my names. My username is different at my work account ("tlimoncelli" vs. "tal)... how could I expect a coworker to know that?.)
Lastly, when I contribute to a third-party project it is a very intentional decision whether I am contributing as a StackOverflow employee or as myself. I want bug reports and other notifications sent to one email address or the other depending on the situation. Also, this future-proofs things so that when I change jobs (no current plans, BTW), I'll stop receiving notifications from projects that I'm involved in for work-related reasons.
You can't upload the same SSH public key to GitHub two accounts. GitHub uses the key to determine which account you are accessing, so they must be unique. If you were able to upload the same key to both accounts, GitHub would have to guess your intention for each repo, and that guess would often be wrong. You can upload multiple keys to each account, but there may not be overlapping keys between the accounts.
I could simply decide that one machine will be only for work, and will have SSH keys associated with my work account. I would then have a different machine that I'd only use for personal stuff, and will have an SSH key there that is only associated with my personal account. However, expecting me to carry around 2 laptops is silly. That isn't to say that some companies should adopt such a policy, especially ones that have higher security requirements, but that's not my situation.
I set up a fake hostname in
.ssh/config to indicate which SSH key to use.
Here's an example:
git clone firstname.lastname@example.org:StackExchange/httpunit.git git clone email@example.com:StackExchange/httpunit.git ^^^^^^^^^^^^^^^ What??? That's not a thing!
There is no such thing as
work-github.com. However, if you look at my
.ssh/config file you'll find a "Host" entry that sets the actual hostname and sets a bunch of parameters, including which SSH key to use:
# Personal GitHub account: Host home-github.com HostName github.com User git IdentityFile ~/.ssh/id_ed25519-homegithub PreferredAuthentications publickey PasswordAuthentication no IdentitiesOnly yes # Work GitHub account: Host work-github.com HostName github.com User git IdentityFile ~/.ssh/id_ed25519-workgithub PreferredAuthentications publickey PasswordAuthentication no IdentitiesOnly yes
On any machine that I use git, I simply make sure that the filename points to the appropriate key.
When someone gives me an SSH-based Git URL, I manually doctor the hostname by adding the "home-" or "work-" prefix. After that, everything just works.
If I forget to edit the hostname, I have defaults set so that it uses my work key. Originally I set it up so that using the undoctored hostname fails. That way I'd get an error and remember to doctor the hostname. However I found that interfered with systems (usually install scripts) that didn't let me edit the hostname.
go get are unaffected by this system since they use anonymous HTTP, not Git.
The other problem I had was properly configuration git
user.email. My global
~/.gitconfig file sets
user.name because I am always Tom Limoncelli. However, I leave
user.email unset in that file to force me to set it per-repo.
I've set up Bash aliases to let me easily set the email address:
alias gitmeHome='git config user.email tal@REDACTED.org` alias gitmeWork='git config user.email tlimoncelli@REDACTED.com`
After I do "get clone", I need to remember to
cd into that repo and run either
gitmeWork. If I forget, I get this nice reminder:
$ git commit filename [master 5667341] yes Committer: Tom Limoncelli <firstname.lastname@example.org> Your name and email address were configured automatically based on your username and hostname. Please check that they are accurate. You can suppress this message by setting them explicitly: git config --global user.name "Your Name" git config --global user.email email@example.com After doing this, you may fix the identity used for this commit with: git commit --amend --reset-author 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 dirname/filename
By having the bash aliases, setting
user.email is without hassle.
I've found it greatly simplifies my life to have the exact same
~/.gitconfig file on all my machines.
Manually adding a new Host entry to
~/.ssh/config on the proper machines is a pain. It is easier to copy the entire master file (which I keep in git, of course) is easier. If a particular machine doesn't need that Host entry, who cares? Either I won't use it, or it will fail if I do use it. My Host entries are carefully constructed so that they work if the right keys are on the machine, and fail otherwise.
Having the same
~/.gitconfig on all my machines is a little more tricky. It contains the settings that are the same everywhere. Overrides are set in the repo-specific
.git/config file. As you saw above, a setting like
user.email is critical, so I have no default in the global file thus the per-repo setting is required.
Asimov wrote a lot:
To match the number of novels, letters, essays, and other scribblings Asimov produced in his lifetime, you would have to write a full-length novel every two weeks for 25 years.
The six tips:
The what use is a csci degree meme has been going around again, so I thought I'd interrogate what mine got me.
First, a few notes on my career journey:
Elapsed time: 20ish years.
As it happens, even though my career has been ops-focused I still got a lot out of that degree. Here are the big points.
“Death in the Gulf Stream,” as he called it, was Hemingway’s salve for 1937—a dark year marked by an economic recession in the US, Joseph Stalin’s wrenching Purge Trials, a new war between China and Japan, and the Spanish Civil War which he covered as a journalist for the North American Newspaper Alliance.
This tutorial will explain How to mount Virtualbox drive image(.vdi) on Ubuntu 16.10.First we need to install QEMU tools using the following command
Read the rest of How to mount Virtualbox drive image(vdi) on Ubuntu 16.10 (164 words)
ELOG is part of a family of applications known as weblogs . Their general purpose is :
to make it easy for people to put information online in a chronological fashion, in the form of short, time-stamped text messages ("entries") with optional HTML markup for presentation, and optional file attachments (images, archives, etc.)
to make it easy for other people to access this information through a Web interface, browse entries, search, download files, and optionally add, update, delete or comment on entries.
Read the rest of Install and configure Elog (Logbook system) on Ubuntu 16.10 Server (670 words)