Working from Home – Tips from a remote worker

Working from Home – Tips from a remote worker

Working from Home – Tips from a remote worker

Disclaimer *This post is unlike most posts published on the {code} blog* In these unprecedented times, it will be an adjustment for all of us to start working remotely over the course of the next few weeks. As someone who works remotely most of the time, I wanted to put together some tips that have The post Working from Home – Tips from a remote worker appeared first on VMware {code}.


VMware Social Media Advocacy

Why Large Organizations Trust Kubernetes

Why Large Organizations Trust Kubernetes

Large enterprises clearly trust Kubernetes, according to our most recent State of Kubernetes survey, and are using it for applications in production. And while there are barriers to adoption, they’re worth it for the productivity and resilience benefits that using Kubernetes yields. Among the key highlights from the new survey: 59 percent of large organizations The post Why Large Organizations Trust Kubernetes appeared first on Cloud Native Apps Blog.


VMware Social Media Advocacy

Upgrade vCloud Director for Service Provider to 9.7

Upgrade to 9.7 is little bit more complicated, because you need to upgrade (if you are using it) PostgreSQL.

Step-by-step guide

  1. Put vCloud Director + PostgreSQL DB vm’s into maintenance in monitoring system.
  2. SSH to vCloud VM and shutdown services:

    /etc/init.d/vmware-vcd stop

  3. Start nginx or apache to show temporary web page (this needs to be configured ahead). It’s just for cases, that users are trying to connect and you don’t want to have a lot of calls/tickets why the vCloud is not running

    /etc/init.d/nginx start

  4. Check that the temporary page is visible.
  5. Do + check a vCloud vm + vCloud DB vm backup

    do a PostgreDB backup

    1. check free spacedf -hsu – postgrespg_dump vcloud > /var/lib/pgsql/vcloud-backup_20200202.sql

    2. check that backup is not zerols -la /var/lib/pgsql/vcloud-backup_20200202.sql

    3. output must look similar to this:-rw-r–r– 1 postgres postgres 4114824617 Feb 2 22:03 /var/lib/pgsql/vcloud-backup_20200202.sql

  6. Do snapshots on both  VMs “vCloud Director” + “PostgreSQL DB”
  7. Installation and upgrade PostgreSQL DB to v.10

    yum install postgresql10-server

    sudo systemctl stop postgresql-9.6.service && sudo systemctl stop postgresql-10.service

    systemctl stop postgresql-9.6.service

    su postgres

    /usr/pgsql-10/bin/initdb -E UTF8 –locale=en_US.UTF-8 -D /var/lib/pgsql/10/data/

    /usr/pgsql-10/bin/pg_upgrade –old-datadir /var/lib/pgsql/9.6/data/ –new-datadir /var/lib/pgsql/10/data/ –old-bindir /usr/pgsql-9.6/bin/ –new-bindir /usr/pgsql-10/bin/

    change /var/lib/pgsql/10/data/pg_hba.conf same as /var/lib/pgsql/9.6/data/pg_hba.conf

    # TYPE DATABASE USER ADDRESS METHOD
    # “local” is for Unix domain socket connections only
    local all all trust
    # IPv4 local connections:
    host all all 127.0.0.1/32 trust
    # IPv6 local connections:
    host all all ::1/128 trust
    # Allow replication connections from localhost, by a user with the
    # replication privilege.
    #local replication all trust
    #host replication all 127.0.0.1/32 trust
    #host replication all ::1/128 trust
    host all all 0.0.0.0/0 md5

    vi /var/lib/pgsql/10/data/postgresql.conf

    listen_addresses = ‘*’


    Disable PostgreSQL 9.6 and enable and start PostgreSQL 10

    systemctl disable postgresql-9.6.service
    systemctl enable postgresql-10.service
    systemctl start postgresql-10.service

    su postgres
    ./analyze_new_cluster.sh
    ./delete_old_cluster.sh

    Remove old PostgreSQL service

    yum remove postgresql96-server

  8. Check that vcloud DB user is owner of the DB in the postgress!!

    su postgres
    psql
    #list DB’s
    \l

    1. if not change owner of DB “vcloud” to user “vcloud” :ALTER DATABASE vcloud OWNER TO vcloud;
      \l
      \q

    2. optional you can do second DB backup on new PostgreSQL version
      pg_dump vcloud > /var/lib/pgsql/vcloud-backup_pg10_20190505.sql

  9. upgrade vCloud to 9.7
  10. Upload new version/patch to vCloud VM ( ./vmware-vcloud-director-distribution-9.7.0-14535248.bin )
    ensure that file is executable +x flag
    chmod a+x vmware-vcloud-director-distribution-9.7.0-14535248.bin
  11. Run the installation bin file
    ./vmware-vcloud-director-distribution-9.7.0-14535248.bin
  12. run upgrade script
    /opt/vmware/vcloud-director/bin/upgrade
  13. Dont start vCloudDriector services after upgrade DB. Manually started Nginx is running!
    /etc/init.d/nginx stop
    /etc/init.d/vmware-vcd start

  14. Reboot vCloud Director VM
    shutdown -r -t 1
  15. Check vCloud Director: https://_VCLOUD.DOMAIN/
  16. Run script for checking edge VM

    /opt/vmware/vcloud-director/bin/cell-management-tool edge-ip-allocation-updates –host vcloud.domain.xyz –user administrator –status/opt/vmware/vcloud-director/bin/cell-management-tool edge-ip-allocation-updates –host vcloud.domain.xyz –user administrator –update-ip-allocations
  17. After 1-2 business days delete snapshots + DB backup file.

Homelab 2020

Still in progress… not all HW is in the list.. for now just the CORE HW is in the list… and new homeDC building is being build ..

DC5

Networking:

  • Internet 500Mbit
  • Cisco 2970G
  • Zyxel GS1920

Compute:

DELL R710

  • 2x Xeon
  • 192 GB RAM
  • iDRAC
  • 4x NIC

DELL R710

  • 1x Xeon
  • 92GB RAM
  • 4x NIC

DELL R710

  • 1x Xeon
  • 92GB RAM
  • 4x NIC

NUC1 – Test & Dev

  • i3-6100U @ 2.3GHz
  • 32GB RAM
  • 256GB NVMe
  • 500GB SATA 2,5″
  • 2x 1Gbit NIC (one of them is USB TP-LINK U300)

VSAN ROBO:

ESX2 (whitebox)

  • Intel G4560 @ 3.5GHz
  • MB: B250M-D3H
  • 64GB RAM
  • 500GB NVMe Samsung 970EVO
  • 1TB SSD SATA Samsung 860EVO
  • 2x 256GB SSD SATA Kingston
  • 4x 1Gbit NIC
  • 2x 10Gbit NIC (intel X540-AT2) Base-T

ESX5

  • Xeon D-2123IT @ 2.2GHz
  • MB: Supermicro SYS-E300-9D-4CN8TB
  • 128GB RAM
  • 500GB NVMe Samsung 970EVO
  • 1TB SSD SATA Samsung 860EVO
  • IPMI
  • 4x 1Gbit NIC
  • 2x 10Gbit NIC (intel X722) Base-T
  • 2x 10Gbit NIC (intel X722) SFP+

Storage:

NearStore

  • Xeon E3-1220L @2.3GHz (4core)
  • MB: Supermicro X9SCM
  • Case: Nanoxia Deep Silence 6, Rev. B
  • 32GB RAM
  • 16x 2TB SATA
  • 3x 3TB SATA
  • IPMI
  • 2x 1Gbit NIC (82574LM + 82574L)
  • 2x 10Gbit NIC (intel X540-AT2) Base-T
  • 1x 10Gbit Asus

QNAP 653Pro

  • 6x 3TB SATA
  • 4x 1Gbit

DC 1

Networking:

  • Internet 100Mbit

Compute:

GOLEM – ESXi 6.5.0 – Build 10719125

  • Xeon X3450 @ 2.67GHz
  • MB: S3420GP
  • Case: 1U
  • 24GB RAM
  • 5x 1Gbit NIC
  • 2x 1TB HDD SATA
  • 2x 512GB SSD SATA

D&R Site

Networking:

  • Internet 50Mbit

Compute:

ESX

  • Xeon E3-1220L @2.3GHz (4core)
  • MB: Supermicro X9SCM
  • 32GB RAM
  • 2TB SATA
  • 2x 1Gbit NIC (82574LM + 82574L)

Storage:

Synology DS210j

  • 2x 3TB SATA
  • 2x 1Gbit