Cleanup of example configurations

Author: oravirt

LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2014 Mikael Sandström
+Copyright (c) 2014 Mikael Sandström ([email protected], http://oravirt.wordpress.com)
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

delete-db.yml

@@ -1,8 +1,9 @@
+#!/usr/bin/env ansible-playbook
 ---
 
 
  - name: Delete Database(s)
-   hosts: oraem
+   hosts: "{{ hostgroup }}"
    user: ansible
    sudo: yes
    sudo_user: oracle

full-rac-install.yml

@@ -1,10 +1,3 @@
 ---
-# The master_node variable is mostly relevant during RAC-installs, where certain tasks only have to performed on 1 node in the cluster, e.g dealing with shared storage, the actual installations,
-# both GI and DB. So in the case of RAC you pick one node to be the 'master_node' (master_node: true) during the installations. All other nodes should be set to master_node: false.
-# When installing Grid Infrastructure in a stand-alone configuration (or even when not installing GI), each server belonging to the hostgroup you're running against should have master_node: true.
-# It is also the default setting.
-  master_node: false
+  master_node: true
 
-# The following parameter can be used here as well as in group_vars. If you already have a specified ip that should be used it hould probably be put in host_vars instead
-# Using oracle_ic_net in group_vars is probably more likely to be ok if this is being run in a lab-environment
-#  oracle_ic_net: 3.3.3.{{ ansible_all_ipv4_addresses[0].split(.)[-1] }} # Picks the last octet from the public ip to use for cluster-interconnect ip (e.g 3.3.3.51)

group_vars/orafs

@@ -1,10 +1,2 @@
 ---
-# The master_node variable is mostly relevant during RAC-installs, where certain tasks only have to performed on 1 node in the cluster, e.g dealing with shared storage, the actual installations,
-# both GI and DB. So in the case of RAC you pick one node to be the 'master_node' (master_node: true) during the installations. All other nodes should be set to master_node: false.
-# When installing Grid Infrastructure in a stand-alone configuration (or even when not installing GI), each server belonging to the hostgroup you're running against should have master_node: true.
-# It is also the default setting.
-  master_node: true
-
-# The following parameter can be used here as well as in group_vars. If you already have a specified ip that should be used it hould probably be put in host_vars instead
-# Using oracle_ic_net in group_vars is probably more likely to be ok if this is being run in a lab-environment
-#  oracle_ic_net: 3.3.3.{{ ansible_all_ipv4_addresses[0].split(.)[-1] }} # Picks the last octet from the public ip to use for cluster-interconnect ip (e.g 3.3.3.51)
+  master_node: false

host_vars/orarac03

@@ -1,10 +1,3 @@
 ---
-# The master_node variable is mostly relevant during RAC-installs, where certain tasks only have to performed on 1 node in the cluster, e.g dealing with shared storage, the actual installations,
-# both GI and DB. So in the case of RAC you pick one node to be the 'master_node' (master_node: true) during the installations. All other nodes should be set to master_node: false.
-# When installing Grid Infrastructure in a stand-alone configuration (or even when not installing GI), each server belonging to the hostgroup you're running against should have master_node: true.
-# It is also the default setting.
   master_node: false
 
-# The following parameter can be used here as well as in group_vars. If you already have a specified ip that should be used it hould probably be put in host_vars instead
-# Using oracle_ic_net in group_vars is probably more likely to be ok if this is being run in a lab-environment
-#  oracle_ic_net: 3.3.3.{{ ansible_all_ipv4_addresses[0].split(.)[-1] }} # Picks the last octet from the public ip to use for cluster-interconnect ip (e.g 3.3.3.51)