cocampbe

Found this info here: http://blog.ls-al.com/oracle-vm-ovm-rest-api/

Had trouble finding the rest calls to create a vm clone from a template.

## CloneVM failing
## The value for the argument "serverPoolId" was found to be null
def cloneVm(s,baseUri,templateVm,vmName):
  repo_id=get_id_from_name(s,baseUri,'Repository','ovs1')
  sp_id=get_id_from_name(s,baseUri,'ServerPool','ovs-home')
  template_id=get_id_from_name(s,baseUri,'Vm',templateVm)

cocampbe

- hosts: server123
  gather_facts: no
  become: yes
  name: change network config prior to failover
  tasks:
    - block:
       - nmcli:
           type: ethernet
           conn_name: 'eth0'
           ip4: '192.168.99.34/24'

cocampbe

---
- hosts: all
  gather_facts: false
  become: no
  tasks:
    - name: copy ssh key public key
      lineinfile:
        line: 'your_public key string'
        path: /home/your_home_directory/.ssh/authorized_keys
        create: yes

cocampbe

# Install Docker CE
## Set up the repository
### Install required packages.
yum install -y yum-utils device-mapper-persistent-data lvm2

### Add Docker repository.
yum-config-manager \
  --add-repo \
  https://download.docker.com/linux/centos/docker-ce.repo

cocampbe

#!/usr/bin/env python3

'''
create_ansible_hosts_file.py
create ansible inventory file from servers in spacewalk and satellite
by: @cocampbe
'''

from subprocess import run,PIPE

cocampbe

This is a short guide to using helm3 to deploy the isilon csi in rancher RKE. I have tested it in RKE k8s versions 1.16 and 1.17. 

NOTE: EMC should be your main source for updates. 

1. Edit your custom cluster. This is best done ny editing the YAML for the cluster. You need to add the feature gates 
   to the api, controller, scheduler, and kubelet.
   
   Here is sample yaml you can use as a guide.

```

cocampbe

These are my observations related to oracle weblogic 12c nodemanagers.

1. The nodemanager (NM) username and password are note related to the admin console (AC) and enterprise manager usernames and passwords.
2. You can change the NM username and password via wlst in offline mode.
3. Once changed, you need to restart NM.
4. If you have a cluster, the node manager on the other nodes is not update with the new passsword. You need to copy the $DOMAIN_HOME/config/nodemanager/nm_password.properties file to the other machines in the cluster.
5. If you do not want to have to supply the NM username and password in WLST scripts, you need to run the storeUserConfig command and save the config and key files in a directory called .wlst in the home folder of the user running the wlst command. You must also the nm to "true". This in an example: