puppet enterprise node_vmware create vm from vm present on venter/vsphere with wait for boot option

[root@localhost ~]# puppet node_vmware list

Notice: Connecting ...
Notice: Connected to 192.168.0.105 as root (API version 4.1)
Notice: Finding all Virtual Machines ... (Started at 07:33:34 AM)
Notice: Control will be returned to you in 10 minutes at 07:43 AM if locating is unfinished.
Locating:          100% |oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo| Time: 00:00:12
Notice: Complete
/Datacenters/dc/vm/ans-db02
  powerstate: poweredOff
  name:       ans-db02
  hostname:   --------
  instanceid: 5013b6bf-be08-abd4-a742-361d94701471
  ipaddress:  ---.---.---.---
  template:   false

/Datacenters/dc/vm/ans-nginx01
  powerstate: poweredOff
  name:       ans-nginx01
  hostname:   --------
  instanceid: 5013c3dc-201e-ccd5-91e6-1b5b8c607876
  ipaddress:  ---.---.---.---
  template:   false

/Datacenters/dc/vm/ans-nginx02
  powerstate: poweredOff
  name:       ans-nginx02
  hostname:   --------
  instanceid: 5013ca38-52b6-f05b-6947-bc9cf01bd724
  ipaddress:  ---.---.---.---
  template:   false

/Datacenters/dc/vm/bootup
  powerstate: poweredOff
  name:       bootup
  hostname:   --------
  instanceid: 5013d3c3-2fd4-7ff3-8739-74408d4866d6
  ipaddress:  ---.---.---.---
  template:   false

/Datacenters/dc/vm/kde
  powerstate: poweredOff
  name:       kde
  hostname:   --------
  instanceid: 5013e8b4-5e0b-b27a-3ef8-23bfcb945a87
  ipaddress:  ---.---.---.---
  template:   false

/Datacenters/dc/vm/launch
  powerstate: poweredOn
  name:       launch
  hostname:   localhost
  instanceid: 5013cf29-85ec-bf6b-31a1-34413abfc3a8
  ipaddress:  192.168.0.107
  template:   false

/Datacenters/dc/vm/launch1
  powerstate: poweredOn
  name:       launch1
  hostname:   localhost
  instanceid: 501355c9-0096-4889-bfdf-f2815ffa7250
  ipaddress:  192.168.0.108
  template:   false

/Datacenters/dc/vm/new-vm
  powerstate: poweredOff
  name:       new-vm
  hostname:   --------
  instanceid: 50132383-d1fa-861a-f10b-dfe7c4fe6446
  ipaddress:  ---.---.---.---
  template:   false

/Datacenters/dc/vm/new-vm1
  powerstate: poweredOff
  name:       new-vm1
  hostname:   --------
  instanceid: 50130102-e8e5-a5f3-97b8-222e70c1cb77
  ipaddress:  ---.---.---.---
  template:   false

/Datacenters/dc/vm/newpuppetmaster
  powerstate: poweredOff
  name:       newpuppetmaster
  hostname:   --------
  instanceid: 501314a0-1aa8-76eb-0274-26c306fb099b
  ipaddress:  ---.---.---.---
  template:   false

/Datacenters/dc/vm/newpuppetmaster1
  powerstate: poweredOff
  name:       newpuppetmaster1
  hostname:   --------
  instanceid: 5013a603-7e94-673d-8f30-c52eec09efc4
  ipaddress:  ---.---.---.---
  template:   false

/Datacenters/dc/vm/nginx
  powerstate: poweredOff
  name:       nginx
  hostname:   --------
  instanceid: 501351f8-5ea7-cf11-2545-8f333407c9a0
  ipaddress:  ---.---.---.---
  template:   false

/Datacenters/dc/vm/nginx01
  powerstate: poweredOff
  name:       nginx01
  hostname:   --------
  instanceid: 50130ea9-1e47-5400-4ac7-caf710938bc0
  ipaddress:  ---.---.---.---
  template:   false

/Datacenters/dc/vm/nginx02
  powerstate: poweredOff
  name:       nginx02
  hostname:   --------
  instanceid: 50131351-2526-1bb7-6d61-74066091b654
  ipaddress:  ---.---.---.---
  template:   false

/Datacenters/dc/vm/nginx04
  powerstate: poweredOff
  name:       nginx04
  hostname:   --------
  instanceid: 5013a952-e0e6-5764-64cc-f57de838c5ab
  ipaddress:  ---.---.---.---
  template:   false

/Datacenters/dc/vm/nginx05
  powerstate: poweredOff
  name:       nginx05
  hostname:   --------
  instanceid: 5013d022-8179-2f4c-b58d-4949b44a1851
  ipaddress:  ---.---.---.---
  template:   false
[root@localhost ~]#

root@localhost ~]#  puppet node_vmware create  --vmname=launch --template="/Datacenters/dc/vm/ans-nginx02" --wait-for-boot
Notice: Connecting ...
Notice: Connected to 192.168.0.105 as root (API version 4.1)
Notice: Locating VM at /Datacenters/dc/vm/ans-nginx02 (Started at 06:04:43 AM)
Notice: Control will be returned to you in 10 minutes at 06:14 AM if locating (1/3) is unfinished.
Locating (1/3):    100% |oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo| Time: 00:00:12
Notice: Starting the clone process (Started at 06:04:55 AM)
Notice: Control will be returned to you in 10 minutes at 06:14 AM if starting (2/3) is unfinished.
Starting (2/3):    100% |oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo| Time: 00:01:11
Notice: Waiting for the machine to boot and obtain an IP address ... (Started at 06:06:07 AM)
Notice: Control will be returned to you in 10 minutes at 06:16 AM if booting (3/3) is unfinished.
Booting (3/3):     100% |oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo| Time: 00:07:16
---
  status: success
  id: "5013cf29-85ec-bf6b-31a1-34413abfc3a8"
  name: launch
  uuid: "421370f0-de3e-5b83-026a-7f450414320b"
  instance_uuid: "5013cf29-85ec-bf6b-31a1-34413abfc3a8"
  hostname: localhost
  operatingsystem: "Linux 3.10.0-957.el7.x86_64 CentOS Linux release 7.6.1810 (Core) "
  ipaddress: "192.168.0.107"
  power_state: poweredOn
  connection_state: connected
  hypervisor: "192.168.0.106"
  tools_state: toolsOk
  tools_version: guestToolsUnmanaged
  is_a_template: false
  memory_mb: 1040
  cpus: 1
  mo_ref: vm-422
  mac_addresses:
    "Network adapter 1": "00:50:56:93:74:27"
  path: /Datacenters/dc/vm
[root@localhost ~]#


[root@localhost ~]#  puppet node_vmware create  --vmname=launch1 --template="/Datacenters/dc/vm/ans-nginx02" --wait-for-boot
Notice: Connecting ...
Notice: Connected to 192.168.0.105 as root (API version 4.1)
Notice: Locating VM at /Datacenters/dc/vm/ans-nginx02 (Started at 06:16:48 AM)
Notice: Control will be returned to you in 10 minutes at 06:26 AM if locating (1/3) is unfinished.
Locating (1/3):    100% |oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo| Time: 00:00:09
Notice: Starting the clone process (Started at 06:16:58 AM)
Notice: Control will be returned to you in 10 minutes at 06:26 AM if starting (2/3) is unfinished.
Starting (2/3):    100% |oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo| Time: 00:00:18
Notice: Waiting for the machine to boot and obtain an IP address ... (Started at 06:17:17 AM)
Notice: Control will be returned to you in 10 minutes at 06:27 AM if booting (3/3) is unfinished.
Booting (3/3):     100% |oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo| Time: 00:07:01
---
  status: success
  id: "501355c9-0096-4889-bfdf-f2815ffa7250"
  name: launch1
  uuid: "4213f28f-2585-6031-4888-7e8184bd9270"
  instance_uuid: "501355c9-0096-4889-bfdf-f2815ffa7250"
  hostname: localhost
  operatingsystem: "Linux 3.10.0-957.el7.x86_64 CentOS Linux release 7.6.1810 (Core) "
  ipaddress: "192.168.0.108"
  power_state: poweredOn
  connection_state: connected
  hypervisor: "192.168.0.106"
  tools_state: toolsOk
  tools_version: guestToolsUnmanaged
  is_a_template: false
  memory_mb: 1040
  cpus: 1
  mo_ref: vm-423
  mac_addresses:
    "Network adapter 1": "00:50:56:93:1c:9e"
  path: /Datacenters/dc/vm


https://docs.google.com/document/d/e/2PACX-1vRkPh0MJApcfHJJ8K_93JbxX_1YtIEB3CAEESk1qmEw_aI7TvLRLeRNHYMTMhs84GQwkAPp-AHFSLMj/pub

Comments

Popular posts from this blog

ansible redhat cluster qorum qdevice

PE 3.9.0 on centos 6

gfs2 cluster