VMware PowerCLI 101 - part7 - Working with vROps

This article explains how to work with vROps resources using PowerCLI. The following diagram shows the relationship between adapters, resource kinds, and resources. There can be multiple adapters installed on the vROps instance. Each adapter kind will have multiple resource kinds and each resource kind will have multiple resources. And each resource will have its own badges and badge scores.

Note I am using the following versions:
PowerShell: 5.1.14393.3383
VMware PowerCLI: 11.3.0.13990089
vROps: 7.0

Connect to vROps:
Connect-OMServer <IP of vROps>

Get the list of all installed adapters:
Get-OMResource | select AdapterKind -Unique

Get all resource kinds of a specific adapter:
Get-OMResource -AdapterKind VMWARE | select ResourceKind -Unique

Get the list of resources of a specific resource kind:
Get-OMResource -ResourceKind Datacenter

Another example:
Get-OMResource -ResourceKind ClusterComputeResource

Get details of a specific resource:
Get-OMResource -Name Cluster01 | select *

Get badge details of a selected resource:
(Get-OMResource -Name Cluster01).ExtensionData.Badges

List all resources of an adapter kind where health is not green:
Get-OMResource -AdapterKind VMWARE | select AdapterKind,ResourceKind,Name,Health,State,Status | where health -ne Green | ft

Get the list all objects of an adapter kind that have collection issues:
Get-OMResource -AdapterKind VMWARE | select AdapterKind,ResourceKind,Name,Health,State,Status | where {($_.Status -ne "DataReceiving") -or ($_.State -ne "Started")} | ft

Get the list of all active critical alerts from a specific adapter type:
Get-OMResource -AdapterKind VMWARE | Get-OMAlert -Criticality Critical -Status Active

Hope it was helpful. Cheers!

Related posts

VMware PowerCLI 101 Blog Series

How to manually add multiple NICs to the vROps 8.x appliance

Important note: This is officially NOT supported by vROps. I've had a specific one off use case in my lab. It is just a quick workaround and is not recommended in production environment as this solution is not supported by VMware.

 

This article explains how to add multiple network interfaces to a vROps 8.0 and 8.1 appliance. Recently we had a scenario where the vROps appliance needs access to different networks that are isolated/ not routed with the primary network management interface of vROps. In my case, the vROps instance needed access to 3 different networks.

Initially while installing the vROps there will be only one interface (10-eth0.network) and its the default interface for vROps appliance. 

For configuring additional interfaces follow the steps below:

• Add a network card and connect to the respective port group by editing VM settings
• Login to vROps with root creds
• cd /etc/systemd/network/
• Create an entry for the new interface 10-eth1.network (as it will not be present!)
• vi 10-eth1.network
• Provide all necessary IP details and save
  

• Restart network service systemctl restart systemd-networkd
• Verify /opt/vmware/share/vami/vami_config_net

• Similarly, follow the above steps if you require more interfaces 

Note: This solutions is NOT officially supported by vROps. It is not recommended in production environment.

Related post 

How to manually add multiple NICs to the vROps 7.x appliance

References

https://vmware.github.io/photon/assets/files/html/3.0/photon_admin/managing-the-network-configuration.html

Kubernetes 101 - Part2 - Basic operations

In this article, I will walk you through basic kubectl commands for working with K8s clusters.

kubectl cluster-info

kubectl version --short

kubectl get namespaces

kubectl get nodes -o wide

kubectl get pods -o wide --all-namespaces

kubectl get pods --show-labels

kubectl get nodes --show-labels

Deploy a pod

Following is a sample yaml file for deploying a CentOS pod:

apiVersion: v1

kind: Pod

metadata:

 name: centos-pod

 labels:

  zone: test

  version: v1

spec:

 containers:

 - name: centos-pod

   image: centos:latest

   command: ["sleep"]

   args: ["1d"]

 nodeSelector:

    kubernetes.io/hostname: w2

To deploy the pod:

kubectl create -f centos-pod.yml

kubectl describe pod centos-pod

SSH into the pod:

kubectl exec -it centos-pod sh

kubectl delete pod centos-pod

Hope it was useful. Cheers!

Kubernetes 101 - Part1 - Create K8s cluster with kubeadm

Deploy 3 CentOS 7 VMs. One will be the master and the other two will be workers/ slaves.

Master is "m1" and workers are "w1" and "w2".

Plan IP address

192.168.105.100 - m1
192.168.105.101 - w1
192.168.105.102 - w2

Step1: on all 3 nodes

vi /etc/hosts

192.168.105.100 m1
192.168.105.101 w1
192.168.105.102 w2

Step2: on all 3 nodes

#Disable firewall

sudo firewall-cmd --state
sudo systemctl stop firewalld
sudo systemctl disable firewalld
sudo systemctl status firewalld

setenforce 0
sed -i --follow-symlinks 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/sysconfig/selinux

Step3: on all 3 nodes

#Configure iptables for Kubernetes
cat <<EOF > /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
sysctl --system

Step4: on all 3 nodes

#Disable swap

swapoff -a
vi /etc/fstab (Edit fstab file and comment(#) swap partition)

reboot all 3 nodes

Step5: on all 3 nodes

#configure kubernetes repo

cat <<EOF > /etc/yum.repos.d/kubernetes.repo

[kubernetes]

name=Kubernetes

baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64

enabled=1

gpgcheck=1

repo_gpgcheck=1

gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg

EOF

Step6: Install docker on all 3 nodes

yum install docker -y

Step7: on all 3 nodes

yum install -y kubeadm kubectl kubelet --disableexcludes=kubernetes

systemctl daemon-reload
systemctl restart docker && systemctl enable --now docker
systemctl restart kubelet && systemctl enable --now kubelet

Step8: on master

kubeadm init --pod-network-cidr 10.244.0.0/16

Step9: on master

$ mkdir -p $HOME/.kube

$ sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config

$ sudo chown $(id -u):$(id -g) $HOME/.kube/config

Step10: on master

kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml

Step11: on all worker nodes

Use the join token from master to join worker nodes to the K8s cluster.

Example:

kubeadm join 192.168.105.100:6443 --token 4j1cjv.gcj2hx9suq5akc7v \

--discovery-token-ca-cert-hash sha256:b2ead930d772d8af2e45ca8c86c3895b092484c10f8034e52f917e71dc4c3fea

Hope it was useful. Cheers!

References

Why K8s on VMs?

https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/