- Set iDrac settings using System Boot Menu
- Set Static IP:
F2
>iDrac settings
>Network
- Set Username / Password:
F2
>iDrac settings
>Access
- Set Static IP:
- Flash iDRAC7_LocalLicense_Installation_Tool_A00_1.0.iso using
dd
to USB - 30 day evaluation license and enabled dedicated iDrac NIC
#!/bin/bash | |
echo | |
echo "*******************" | |
echo "* Pull New Images *" | |
echo "*******************" | |
echo | |
docker-compose pull | |
echo |
#!/bin/bash | |
set -e | |
#imports | |
. /etc/default/backup | |
# config | |
NAME=$1 |
#!/bin/bash | |
set -e | |
. /etc/default/backup | |
INSTANCE=$1 | |
case $INSTANCE in |
package main | |
import ( | |
"fmt" | |
"time" | |
"sync" | |
) | |
func main() { | |
wg := &sync.WaitGroup{} |
using System; | |
using System.Net; | |
using System.Net.Security; | |
using System.Net.Sockets; | |
using System.Security.Cryptography.X509Certificates; | |
using System.Text; | |
using System.Threading.Tasks; | |
namespace X509Test | |
{ |
- Configure the Network Protocol Profile on the vCenter according to: https://www.virtualthoughts.co.uk/2020/03/29/rancher-vsphere-network-protocol-profiles-and-static-ip-addresses-for-k8s-nodes/
- Ensure to create a service user with the regarding global and folder specific permissions: https://rancher.com/docs/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/vsphere/provisioning-vsphere-clusters/creating-credentials/
- Beside the vCenter role permissions from the official Rancher documentation, the following ones need to be provided in order to configure the Nodes via vApp options:
- Content Library: Read storage
- Extension: Register extension
- Beside the vCenter role permissions from the official Rancher documentation, the following ones need to be provided in order to configure the Nodes via vApp options:
- vSphere Tagging: Assign or Unassign vSphere Tag on Object
#!/bin/bash | |
target=${1:-http://example.com} | |
while true # loop forever, until ctrl+c pressed. | |
do | |
for i in $(seq 100) # perfrom the inner command 100 times. | |
do | |
curl $target > /dev/null & # send out a curl request, the & indicates not to wait for the response. | |
done | |
wait # after 100 requests are sent out, wait for their processes to finish before the next iteration. |
public class DistributedMutex { | |
private readonly string key; | |
private readonly string storageConnectionString; | |
private readonly string storageContainerName; | |
private CloudBlobClient blobClient; | |
private string leaseId; | |
public DistributedMutex(string storageConnectionString, string storageContainerName, string key) | |
{ | |
this.key = key; |
If you hate git submodule
, then you may want to give git subtree
a try.
When you want to use a subtree, you add the subtree to an existing repository where the subtree is a reference to another repository url and branch/tag. This add
command adds all the code and files into the main repository locally; it's not just a reference to a remote repo.
When you stage and commit files for the main repo, it will add all of the remote files in the same operation. The subtree checkout will pull all the files in one pass, so there is no need to try and connect to another repo to get the portion of subtree files, because they were already included in the main repo.
Let's say you already have a git repository with at least one commit. You can add another repository into this respository like this: