likewise Active Directory - black list of domain controllers

 1. Set the black listed DCs
/opt/likewise/bin/lwregshell set_value '[HKEY_THIS_MACHINE\Services\netlogon\Parameters]' BlacklistedDCs ip1,ip2 Eg # /opt/likewise/bin/lwregshell set_value '[HKEY_THIS_MACHINE\Services\netlogon\Parameters]' BlacklistedDCs 10.108.124.21,10.108.124.23 

2. Restart the lwregistry.
# /opt/likewise/bin/lwsm restart lwreg

Meeting Minutes format

Dear Team, 

 

Thank you for attending today’s regular bi-weekly call. As always, we really appreciate your update regarding the current status of all on-going activities connected with XXXXXXX.

 

Below you can find my very short meeting minutes: 

 

Meeting: TBD

Participants: @

Recording: URL

Agenda / discussed topics: 

• Topic 1: description
• Topic 2: description
  

 

Next steps / follow-ups: 

• step1
• step2
• step3

 

Thank you and have a great evening! 

 

Kind Regards,

Google Cloud : TerraForm

Google Terraform Provider initialization

file provider.tf

    provider "google" {}

In shell, run:

terraform init

 

NOW YOU CAN WORK ON TERRAFORM LOGICAL SPECIFICATIONS. 

SEE EXAMPLE BELOW IN THE BOTTOM OF PAGE.

Other commands ...

To rewrite the Terraform configuration files to a canonical format and style, run the following command:

terraform fmt

To initialize Terraform, run the following command

terraform init

 To create an execution plan, run the following command:

terraform plan

To apply the desired changes, run the following command:

terraform apply 

RESOURCE TEMPLATE

 TerraForm Google RESOURCE TEMPLATE

# Create the mynetwork network
resource [RESOURCE_TYPE] "mynetwork" {
name = [RESOURCE_NAME]
#RESOURCE properties go here
}

DOCUMENTATION

Google Cloud TerraForm provider documentation

https://registry.terraform.io/providers/hashicorp/google/latest/docs

Terraform Module variables

https://learn.hashicorp.com/tutorials/terraform/aws-variables

 

EXAMPLE OF GOOGLE INFRASTRUCTURE AS A CODE

mynetwork.tf

# Create the mynetwork network
resource "google_compute_network" "mynetwork" {
name = "mynetwork"
#RESOURCE properties go here
auto_create_subnetworks = "true"
}

# Add a firewall rule to allow HTTP, SSH, RDP and ICMP traffic on mynetwork
resource "google_compute_firewall" "mynetwork-allow-http-ssh-rdp-icmp" {
name = "mynetwork-allow-http-ssh-rdp-icmp"
#RESOURCE properties go here
network = google_compute_network.mynetwork.self_link
allow {
    protocol = "tcp"
    ports    = ["22", "80", "3389"]
    }
allow {
    protocol = "icmp"
    }
}

# Create the mynet-us-vm instance
module "mynet-us-vm" {
  source           = "./instance"
  instance_name    = "mynet-us-vm"
  instance_zone    = "us-central1-a"
  instance_network = google_compute_network.mynetwork.self_link
}

# Create the mynet-eu-vm" instance
module "mynet-eu-vm" {
  source           = "./instance"
  instance_name    = "mynet-eu-vm"
  instance_zone    = "europe-west1-d"
  instance_network = google_compute_network.mynetwork.self_link
}

instance/main.tf

variable "instance_name" {}
variable "instance_zone" {}
variable "instance_type" {
  default = "n1-standard-1"
  }
variable "instance_network" {}

resource "google_compute_instance" "vm_instance" {
  name         = "${var.instance_name}"
  zone         = "${var.instance_zone}"
  machine_type = "${var.instance_type}"
  boot_disk {
    initialize_params {
      image = "debian-cloud/debian-9"
      }
  }
  network_interface {
    network = "${var.instance_network}"
    access_config {
      # Allocate a one-to-one NAT IP to the instance
    }
  }
}

 

Google Cloud - how to get my IP address

Here is the command

curl -H "Metadata-Flavor: Google" http://169.254.169.254/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip && echo

Generate a CSEK key

AES-256 base-64 key.

Run the following command to create a key: 

python3 -c 'import base64; import os; print(base64.encodebytes(os.urandom(32)))'

How to monitor / report UNMAP bandwidth for particular datastore

The following command brings the correct information by using UnmapBandwidthSpec instead of UnmapGranularity.

Get-Datastore LCD002_001 | % {$_.ExtensionData.Info.Vmfs.UnmapBandwidthSpec | Select Policy,FixedValue}

What are the available pciSlotNumbers for RHEL8 VMs?

 

Summary

What are the available pciSlotNumbers for RHEL8 VMs?

Cause

All normally created Virtual Machines with Virtual Hardware version 7 to 19 will have the same configuration:

pciBridge0: pciBridge, 1 function

pciBridge4: pcieRootPort, 8 functions

pciBridge5: pcieRootPort, 8 functions

pciBridge6: pcieRootPort, 8 functions

pciBridge7: pcieRootPort, 8 functions

VMs with this configuration can have up to 32 PCIe devices with the slot number sequence.

 160, 192, 224, 256,

1184, 1216, 1248, 1280,

2208, 2240, 2272, 2304,

3232, 3264, 3296, 3328,

4256, 4288, 4320, 4352,

5280, 5312, 5344, 5376,

6304, 6336, 6368, 6400,

7328, 7360, 7392, 7424,

Resolution

It is possible to manually configure a VM to have a different pciBridge configuration, and therefore different pciSlotNumbers but this should only be performed in cooperation with VMware Engineering.