puppet enterprise node_vmware start / stop vms

-
[root@localhost ~]# puppet node_vmware stop /Datacenters/dc/vm/launch
Notice: Connecting ...
Notice: Connected to 192.168.0.105 as root (API version 4.1)
Notice: Locating VM at /Datacenters/dc/vm/launch (Started at 07:48:54 AM)
Notice: Control will be returned to you in 10 minutes at 07:58 AM if locating is unfinished.
Locating:          100% |oooooooooooooooooooooooooooooooooooooo| Time: 00:00:07
Notice: Stopping Virtual Machine /Datacenters/dc/vm/launch (Started at 07:49:02 AM)
Notice: Control will be returned to you in 10 minutes at 07:59 AM if stopping is unfinished.
Stopping:          100% |oooooooooooooooooooooooooooooooooooooo| Time: 00:00:17
power_off_type  "shutdown_guest"
task_state      "running"
[root@localhost ~]# puppet node_vmware stop /Datacenters/dc/vm/launch1
Notice: Connecting ...
Notice: Connected to 192.168.0.105 as root (API version 4.1)
Notice: Locating VM at /Datacenters/dc/vm/launch1 (Started at 07:51:37 AM)
Notice: Control will be returned to you in 10 minutes at 08:01 AM if locating is unfinished.
Locating:          100% |oooooooooooooooooooooooooooooooooooooo| Time: 00:00:16
Notice: Stopping Virtual Machine /Datacenters/dc/vm/launch1 (Started at 07:51:54 AM)
Notice: Control will be returned to you in 10 minutes at 08:01 AM if stopping is unfinished.
Stopping:          100% |oooooooooooooooooooooooooooooooooooooo| Time: 00:00:03
power_off_type  "shutdown_guest"
task_state      "running"
[root@localhost ~]#


[root@localhost ~]# puppet node_vmware start /Datacenters/dc/vm/launch
Notice: Connecting ...
Notice: Connected to 192.168.0.105 as root (API version 4.1)
Notice: Locating VM at /Datacenters/dc/vm/launch (Started at 07:56:35 AM)
Notice: Control will be returned to you in 10 minutes at 08:06 AM if locating is unfinished.
Locating:          100% |oooooooooooooooooooooooooooooooooooooo| Time: 00:00:01
Notice: Starting Virtual Machine /Datacenters/dc/vm/launch (Started at 07:56:36 AM)
Notice: Control will be returned to you in 10 minutes at 08:06 AM if starting is unfinished.
Starting:          100% |oooooooooooooooooooooooooooooooooooooo| Time: 00:00:24
task_state  "success"
[root@localhost ~]# puppet node_vmware start /Datacenters/dc/vm/launch1
Notice: Connecting ...
Notice: Connected to 192.168.0.105 as root (API version 4.1)
Notice: Locating VM at /Datacenters/dc/vm/launch1 (Started at 07:57:10 AM)
Notice: Control will be returned to you in 10 minutes at 08:07 AM if locating is unfinished.
Locating:          100% |oooooooooooooooooooooooooooooooooooooo| Time: 00:00:03
Notice: Starting Virtual Machine /Datacenters/dc/vm/launch1 (Started at 07:57:14 AM)
Notice: Control will be returned to you in 10 minutes at 08:07 AM if starting is unfinished.
Starting:          100% |oooooooooooooooooooooooooooooooooooooo| Time: 00:00:07
task_state  "success"
[root@localhost ~]#


Comments

Post a Comment

Popular posts from this blog

ansible redhat cluster qorum qdevice

-
- hosts: localhost   user: root   become: yes   become_method: sudo   tasks:   - name: high availability is removed/installed     yum: name='@High Availability' state=present   - name: resilent storage is removed/installed     yum: name='@Resilient Storage' state=present   - name: install pcs pacemaker fence-agent-all     command: yum install pcs pacemaker fence-agents-all   - name: pcsd is running and enabled     service:      name=pcsd      state=started      enabled=yes   - firewalld:       service: high-availability       permanent: yes       state: enabled [root@localhost ~]#  pcs cluster setup --start --name cluster cluster1 cluster2 --force Destroying cluster on nodes: cluster1, cluster2... cluster1: Stopping Cluster (pacemaker)... cluster2: Stopping C...
Read more

PE 3.9.0 on centos 6

-
[localhost/puppet.kiran.com] mktemp -d -t pe-installer-XXXXXXXX /tmp/pe-installer-0Tf3iTLy [localhost/puppet.kiran.com] chmod 700 '/tmp/pe-installer-0Tf3iTLy' [localhost/puppet.kiran.com] mkdir -p /var/log/pe-installer [localhost/puppet.kiran.com] chmod 700 '/var/log/pe-installer' [localhost/puppet.kiran.com] mkdir -p /etc/puppetlabs/installer/ [localhost/puppet.kiran.com] chmod 700 '/etc/puppetlabs/installer' Copying /opt/puppet/share/installer/installer to puppet.kiran.com:/tmp/pe-installer-0Tf3iTLy/install. Copying /tmp/installer-content20191004-8962-6nw7c9 to puppet.kiran.com:/tmp/pe-installer-0Tf3iTLy/puppet.kiran.com.answers. [localhost/puppet.kiran.com] /tmp/pe-installer-0Tf3iTLy/install/puppet-enterprise-installer -D -a /tmp/pe-installer-0Tf3iTLy/puppet.kiran.com.answers ======================================================================== Puppet Enterprise v3.7.0 installer Puppet Enterprise documentation can be found at http://docs.puppetlabs.com/pe/...
Read more

gfs2 cluster

-
WARNINGS: No stonith devices and stonith-enabled is not false Stack: corosync Current DC: NONE Last updated: Sat Oct 26 22:32:30 2019 Last change: Sat Oct 26 22:19:04 2019 by root via cibadmin on cluster2 2 nodes configured 1 resource configured Node cluster1: UNCLEAN (offline) Node cluster2: UNCLEAN (offline) Full list of resources:  Resource Group: halvmfs      halvm (ocf::heartbeat:LVM): Stopped Daemon Status:   corosync: active/disabled   pacemaker: active/disabled   pcsd: active/enabled [root@cluster1 ~]# mkdir /xfs [root@cluster1 ~]# clear [root@cluster1 ~]# pcs resource create xfsfs filesystem device="/dev/vg/cluster" directory="/xfs" Assumed agent name 'ocf:heartbeat:Filesystem' (deduced from 'filesystem') Error: required resource option 'fstype' is missing, use --force to override [root@cluster1 ~]# pcs status^C [root@cluster1 ~]#  pcs resource create xfsfs filesystem device="/dev/vg/cluster...
Read more