-
Notifications
You must be signed in to change notification settings - Fork 49
HOWTO: Running the tool for the first time
Marcio Silva edited this page Oct 19, 2018
·
36 revisions
The first time the tool is run, an experiment containing a simulated cloud, designated "MYSIMCLOUD" is automatically initiated. It is used just to confirm that the tool's main components (e.g., Object Store, Metric Store) are up and running before any interaction with a real cloud starts.
The tool reads all configuration parameters from a file name <your username>_cloud_definitions.txt (or cloud_definitions.txt, in case it does not find the former) located on the configs directory.
IMPORTANT: If, and only if, your CBTOOL Orchestrator Node has more than one network interface, please open your private configuration file and change the attribute MANAGER_IP = $IP_AUTO, under the section [USER-DEFINED], to the actual IP address of the interface that has access to the network that is used to contact the VMs that will be created.
To run the tool's CLI, type cb. The aforementioned file, will automatically "attach" the simulated cloud "MYSIMCLOUD", which means that the commands cldattach sim MYSIMCLOUD, to initialize the cloud and vmcattach all, to register 2 "cloud regions" (with 5 simulated hosts per region) is automatically executed.
Since the first execution includes might include the startup of both a Redis and MongoDB server (please check the FAQ for more details), it is not unusual that it takes a couple of minutes.
Here is an example execution:
cbuser@klinux:~/cbtool$ ~/cbtool/cb --soft_reset
Cbtool version is "55c720f"
Parsing "cloud definitions" file..... "/home/cbuser/cbtool/configs/cbuser_cloud_definitions.txt" opened and parsed successfully.
Checking "Object Store".....An Object Store of the kind "Redis" (shared) on node 127.0.0.1, TCP port 6379, database id "10" seems to be running.
Checking "Log Store".....A Log Store of the kind "rsyslog" (private) on node 127.0.0.1, UDP port 5114 seems to be running.
Checking "Metric Store".....A Metric Store of the kind "MongoDB" (shared) on node 127.0.0.1, TCP port 27017, database id "metrics" seems to be running.
Checking "File Store".....A File Store of the kind "rsync" (private) on node 127.0.0.1, TCP port 10000 seems to be running.
Executing "soft" reset: (killing all running toolkit processes and flushing Object store) before starting the experiment......
Killing all processes... done
Flushing Object Store... done
Checking for a running API service daemon.....API Service daemon was successfully started. The process id is ['17394'](http://127.0.0.1:7070).
Checking for a running GUI service daemon.....GUI Service daemon was successfully started. The process id is ['17478', '17479'], listening on port 8080. Full url is "http://127.0.0.1:8080".
############################# Executing command "cldattach sim MYSIMCLOUD" (specified on the configuration file)
status: VPN configuration for this cloud already generated: /home/cbuser/cbtool/configs/generated/MYSIMCLOUD_server-cb-openvpn.conf
status: Checking if the ssh key pair "cbuser_cbtool_rsa" is created on VMC simzone_b....
status: Checking if the security group "simsecgrp" is created on VMC simzone_b....
status: Checking if the network "private" can be found on VMC simzone_b...
status: Checking if the imageids associated to each "VM role" are registered on VMC "simzone_b"....
status: INFO Image id for VM roles "lb,tinyvm,yatinyvm" is "AE60094F-802B-531A-8EFB-CA5294990675" and it is already registered.
INFO Image id for VM roles "driver_tradelite,client_tradelite" is "C5F67B76-920D-5102-A7F8-80F83657CB06" and it is already registered.
INFO Image id for VM roles "mongos,redis,mongodb,mongo_cfg_server" is "F50D2E6B-8F80-5257-ADB0-C193BA618B1C" and it is already registered.
INFO Image id for VM roles "driver_netperf,netserver,netclient" is "38DC1010-76D8-5115-90D3-ED72E9C70E79" and it is already registered.
INFO Image id for VM roles "driver_coremark,coremark" is "B770C650-94D0-5192-93C2-E377A53139C3" and it is already registered.
INFO Image id for VM roles "giraphpmaster,giraphslave" is "F3E4E17E-7D1B-5305-AB28-DE9E7AF404CF" and it is already registered.
INFO Image id for VM roles "windows,client_windows" is "4322F915-BCBA-55FD-ADFE-A27D7FCC0D18" and it is already registered.
INFO Image id for VM roles "filebench,driver_filebench" is "91327B9B-AAED-5BD6-A67F-81E6A0304B32" and it is already registered.
INFO Image id for VM roles "btest" is "C4BA42BC-BEF3-539F-AF98-D10D95204902" and it is already registered.
INFO Image id for VM roles "hadoopslave,hadoopmaster" is "59240953-54E0-55FB-8BA3-31119ECE8E67" and it is already registered.
INFO Image id for VM roles "xpingsender,xpingreceiver" is "D4A581AE-F8E1-53A9-8F57-4B438BC42AE7" and it is already registered.
INFO Image id for VM roles "specjbb" is "3AE78C3F-EF6A-51FC-8B84-128FAD0BBD12" and it is already registered.
INFO Image id for VM roles "iperfserver,iperfclient" is "D8D19E07-9C0E-51D1-8229-FD86D2C79D48" and it is already registered.
INFO Image id for VM roles "willfail" is "C8B57F26-2AE8-557B-8C5E-F0C2B3D69035" and it is already registered.
INFO Image id for VM roles "fen_hpc,cn_hpc" is "E6430504-5399-5196-9713-9204C16D3476" and it is already registered.
INFO Image id for VM roles "parboil" is "86EE5102-EEC0-5FDE-9C9A-1AB2E0829AF4" and it is already registered.
INFO Image id for VM roles "ddgen" is "0FA56845-48B4-5A58-BA0B-BA96A1DAF785" and it is already registered.
INFO Image id for VM roles "driver_hadoop" is "CBAAD8F2-7FBE-5C46-8389-0129E31BF4D9" and it is already registered.
INFO Image id for VM roles "linpack" is "1102D5FD-B51A-5ED0-B0C7-D55BC1B00456" and it is already registered.
INFO Image id for VM roles "ycsb,seed,cassandra" is "575BE258-89D9-5B2D-9293-E94D11ED1E6A" and it is already registered.
INFO Image id for VM roles "nuttcpserver,nuttcpclient" is "ED1079FF-3A71-5F38-A14F-14BF1DF45E9F" and it is already registered.
INFO Image id for VM roles "db2,driver_daytrader,geronimo,mysql,client_daytrader,was" is "8121A98C-3E2C-57FB-A300-2BDAFFAB23EB" and it is already registered.
INFO Image id for VM roles "predictablevm,faildb2" is "77A8FB76-F3E8-56E2-BA27-6C2907F59B80" and it is already registered.
INFO Image id for VM roles "fio,unixbench,driver_fio" is "7B1C177F-2425-501A-BA4B-99AA94FADD15" and it is already registered
status: VMC "simzone_b" was successfully tested.
status: Checking if the ssh key pair "cbuser_cbtool_rsa" is created on VMC simzone_a....
status: Checking if the security group "simsecgrp" is created on VMC simzone_a....
status: Checking if the network "private" can be found on VMC simzone_a...
status: Checking if the imageids associated to each "VM role" are registered on VMC "simzone_a"....
status: INFO Image id for VM roles "lb,tinyvm,yatinyvm" is "AE60094F-802B-531A-8EFB-CA5294990675" and it is already registered.
INFO Image id for VM roles "driver_tradelite,client_tradelite" is "C5F67B76-920D-5102-A7F8-80F83657CB06" and it is already registered.
INFO Image id for VM roles "mongos,redis,mongodb,mongo_cfg_server" is "F50D2E6B-8F80-5257-ADB0-C193BA618B1C" and it is already registered.
INFO Image id for VM roles "driver_netperf,netserver,netclient" is "38DC1010-76D8-5115-90D3-ED72E9C70E79" and it is already registered.
INFO Image id for VM roles "driver_coremark,coremark" is "B770C650-94D0-5192-93C2-E377A53139C3" and it is already registered.
INFO Image id for VM roles "giraphpmaster,giraphslave" is "F3E4E17E-7D1B-5305-AB28-DE9E7AF404CF" and it is already registered.
INFO Image id for VM roles "windows,client_windows" is "4322F915-BCBA-55FD-ADFE-A27D7FCC0D18" and it is already registered.
INFO Image id for VM roles "filebench,driver_filebench" is "91327B9B-AAED-5BD6-A67F-81E6A0304B32" and it is already registered.
INFO Image id for VM roles "btest" is "C4BA42BC-BEF3-539F-AF98-D10D95204902" and it is already registered.
INFO Image id for VM roles "hadoopslave,hadoopmaster" is "59240953-54E0-55FB-8BA3-31119ECE8E67" and it is already registered.
INFO Image id for VM roles "xpingsender,xpingreceiver" is "D4A581AE-F8E1-53A9-8F57-4B438BC42AE7" and it is already registered.
INFO Image id for VM roles "specjbb" is "3AE78C3F-EF6A-51FC-8B84-128FAD0BBD12" and it is already registered.
INFO Image id for VM roles "iperfserver,iperfclient" is "D8D19E07-9C0E-51D1-8229-FD86D2C79D48" and it is already registered.
INFO Image id for VM roles "willfail" is "C8B57F26-2AE8-557B-8C5E-F0C2B3D69035" and it is already registered.
INFO Image id for VM roles "fen_hpc,cn_hpc" is "E6430504-5399-5196-9713-9204C16D3476" and it is already registered.
INFO Image id for VM roles "parboil" is "86EE5102-EEC0-5FDE-9C9A-1AB2E0829AF4" and it is already registered.
INFO Image id for VM roles "ddgen" is "0FA56845-48B4-5A58-BA0B-BA96A1DAF785" and it is already registered.
INFO Image id for VM roles "driver_hadoop" is "CBAAD8F2-7FBE-5C46-8389-0129E31BF4D9" and it is already registered.
INFO Image id for VM roles "linpack" is "1102D5FD-B51A-5ED0-B0C7-D55BC1B00456" and it is already registered.
INFO Image id for VM roles "ycsb,seed,cassandra" is "575BE258-89D9-5B2D-9293-E94D11ED1E6A" and it is already registered.
INFO Image id for VM roles "nuttcpserver,nuttcpclient" is "ED1079FF-3A71-5F38-A14F-14BF1DF45E9F" and it is already registered.
INFO Image id for VM roles "db2,driver_daytrader,geronimo,mysql,client_daytrader,was" is "8121A98C-3E2C-57FB-A300-2BDAFFAB23EB" and it is already registered.
INFO Image id for VM roles "predictablevm,faildb2" is "77A8FB76-F3E8-56E2-BA27-6C2907F59B80" and it is already registered.
INFO Image id for VM roles "fio,unixbench,driver_fio" is "7B1C177F-2425-501A-BA4B-99AA94FADD15" and it is already registered
status: VMC "simzone_a" was successfully tested.
The SIM cloud named "MYSIMCLOUD" was successfully attached to this experiment.
The experiment identifier is EXP-02-08-2017-09-27-24-PM-UTC
############################# Executing command "vmcattach all" (specified on the configuration file)
status: Removing all VMs previously created on VMC "simzone_a" (only VM names starting with "cb-cbuser-MYSIMCLOUD").....
status: VMC simzone_a (2596C294-4875-5242-83C9-29A4C2EF5BFA) was successfully registered on Cloudbench SimCloud "MYSIMCLOUD"
status: Removing all VMs previously created on VMC "simzone_b" (only VM names starting with "cb-cbuser-MYSIMCLOUD").....
status: VMC simzone_b (696B07A1-3C20-5A74-A40E-ACFFBA4B938D) was successfully registered on Cloudbench SimCloud "MYSIMCLOUD"
status: Attribute "collect_from_host" was set to "false". Skipping Host OS performance monitor daemon startup
All VMCs successfully attached to this experiment.
(MYSIMCLOUD)
At this point you can create some simple simulated VMs with the a command such as vmattach ycsb. Make sure all simulated VMs are created with the command vmlist.
(MYSIMCLOUD) vmattach ycsb
status: Starting instance "cb-cbuser-MYSIMCLOUD-vm1-ycsb" on Cloudbench SimCloud, using the image "cb_speccloud_cassandra" (575BE258-89D9-5B2D-9293-E94D11ED1E6A) and size "platinum64", connected to network "private", on VMC "simzone_a" (host "simhosta5"), under tenant "default", injecting the contents of the pub ssh key "cbuser_cbtool_rsa" (userdata is "None").
status: Waiting for vm_1 (7D7911EB-CD81-5968-BC55-BC09C2BA1116), to start...
status: Trying to establish network connectivity to vm_1 (7D7911EB-CD81-5968-BC55-BC09C2BA1116), on IP address 250.100.193.224 (using method "wait_for_0")...
status: Checking ssh accessibility on vm_1 (7D7911EB-CD81-5968-BC55-BC09C2BA1116): ssh -p 22 -i /home/cbuser/cbtool/lib/auxiliary//../../credentials/cbtool_rsa [email protected] "/bin/true"...
status: Bootstrapping vm_1 (7D7911EB-CD81-5968-BC55-BC09C2BA1116): creating file cb_os_paramaters.txt in "cbuser" user's home dir on IP address 250.100.193.224...
status: Sending a copy of the code tree to vm_1 (7D7911EB-CD81-5968-BC55-BC09C2BA1116), on IP address 250.100.193.224...
status: Performing generic VM post_boot configuration on vm_1 (7D7911EB-CD81-5968-BC55-BC09C2BA1116), on IP address 250.100.193.224...
VM object 7D7911EB-CD81-5968-BC55-BC09C2BA1116 (named "vm_1") sucessfully attached to this experiment. It is ssh-accessible at the IP addresses 250.100.193.224 and 225.198.171.76 (cb-cbuser-MYSIMCLOUD-vm1-ycsb).
(MYSIMCLOUD) vmlist
The following ATTACHED VMs are in this experiment (Cloud MYSIMCLOUD) :
|name |role |size |cloud_ip |host_name |vmc_pool |netname |ai |aidrs |uuid
|vm_1 |ycsb |platinum64 |225.198.171.76 |simhosta5
Now try to attach some "Virtual Applications" (VApps). The VApps are internally designated "Application Instances". For instance, here two new VApps are added, with aiattach cassandra_ycsb and aiattach netperf
(MYSIMCLOUD) aiattach cassandra_ycsb
status: ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E) was successfully defined on Cloudbench SimCloud "MYSIMCLOUD" (will now be fully deployed)
status: Starting instance "cb-cbuser-MYSIMCLOUD-vm4-seed-ai-1" on Cloudbench SimCloud, using the image "cb_speccloud_cassandra" (575BE258-89D9-5B2D-9293-E94D11ED1E6A) and size "platinum64", connected to network "private", on VMC "simzone_a" (host "simhostb12"), under tenant "default", injecting the contents of the pub ssh key "cbuser_cbtool_rsa" (userdata is "None").
status: Waiting for vm_4 (43F3D32A-4231-5477-A2C3-FFD436A4705B), part of ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E), to start...
status: Starting instance "cb-cbuser-MYSIMCLOUD-vm2-ycsb-ai-1" on Cloudbench SimCloud, using the image "cb_speccloud_cassandra" (575BE258-89D9-5B2D-9293-E94D11ED1E6A) and size "platinum64", connected to network "private", on VMC "simzone_a" (host "simhosta6"), under tenant "default", injecting the contents of the pub ssh key "cbuser_cbtool_rsa" (userdata is "None").
status: Starting instance "cb-cbuser-MYSIMCLOUD-vm3-seed-ai-1" on Cloudbench SimCloud, using the image "cb_speccloud_cassandra" (575BE258-89D9-5B2D-9293-E94D11ED1E6A) and size "platinum64", connected to network "private", on VMC "simzone_a" (host "simhosta3"), under tenant "default", injecting the contents of the pub ssh key "cbuser_cbtool_rsa" (userdata is "None").
status: Waiting for vm_2 (C42F2402-D7B0-507E-92A6-4C5E25EE06F1), part of ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E), to start...
status: Waiting for vm_3 (AA0457E2-EE36-519B-85D6-4F36ADF82452), part of ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E), to start...
status: Trying to establish network connectivity to vm_4 (43F3D32A-4231-5477-A2C3-FFD436A4705B), part of ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E), on IP address 65.114.194.140 (using method "wait_for_0")...
status: Trying to establish network connectivity to vm_2 (C42F2402-D7B0-507E-92A6-4C5E25EE06F1), part of ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E), on IP address 152.161.24.85 (using method "wait_for_0")...
status: Trying to establish network connectivity to vm_3 (AA0457E2-EE36-519B-85D6-4F36ADF82452), part of ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E), on IP address 216.57.244.160 (using method "wait_for_0")...
status: Checking ssh accessibility on vm_4 (43F3D32A-4231-5477-A2C3-FFD436A4705B), part of ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E): ssh -p 22 -i /home/cbuser/cbtool/lib/auxiliary//../../credentials/cbtool_rsa [email protected] "/bin/true"...
status: Bootstrapping vm_4 (43F3D32A-4231-5477-A2C3-FFD436A4705B), part of ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E): creating file cb_os_paramaters.txt in "cbuser" user's home dir on IP address 65.114.194.140...
status: Checking ssh accessibility on vm_2 (C42F2402-D7B0-507E-92A6-4C5E25EE06F1), part of ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E): ssh -p 22 -i /home/cbuser/cbtool/lib/auxiliary//../../credentials/cbtool_rsa [email protected] "/bin/true"...
status: Sending a copy of the code tree to vm_4 (43F3D32A-4231-5477-A2C3-FFD436A4705B), part of ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E), on IP address 65.114.194.140...
status: Bootstrapping vm_2 (C42F2402-D7B0-507E-92A6-4C5E25EE06F1), part of ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E): creating file cb_os_paramaters.txt in "cbuser" user's home dir on IP address 152.161.24.85...
status: Checking ssh accessibility on vm_3 (AA0457E2-EE36-519B-85D6-4F36ADF82452), part of ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E): ssh -p 22 -i /home/cbuser/cbtool/lib/auxiliary//../../credentials/cbtool_rsa [email protected] "/bin/true"...
status: Sending a copy of the code tree to vm_2 (C42F2402-D7B0-507E-92A6-4C5E25EE06F1), part of ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E), on IP address 152.161.24.85...
status: Bootstrapping vm_3 (AA0457E2-EE36-519B-85D6-4F36ADF82452), part of ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E): creating file cb_os_paramaters.txt in "cbuser" user's home dir on IP address 216.57.244.160...
status: Sending a copy of the code tree to vm_3 (AA0457E2-EE36-519B-85D6-4F36ADF82452), part of ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E), on IP address 216.57.244.160...
status: Starting a new "performance emitter" for ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E)
status: ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E) was successfully defined on Cloudbench SimCloud "MYSIMCLOUD" (will now be fully deployed)
status: Performing generic application instance post_boot configurationon all VMs belonging to ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E)...
status: Running application-specific "setup" configuration on all VMs belonging to ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E)...
status: QEMU Scraper will NOT be automatically started during the deployment of ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E)...
AI object 7199B821-3901-55ED-B5FC-6BA801CFAF9E (named "ai_1") sucessfully attached to this experiment. It is ssh-accessible at the IP address 32.242.20.245 (cb-cbuser-MYSIMCLOUD-vm2-ycsb-ai-1).
(MYSIMCLOUD) ailist
The following ATTACHED AIs are in this experiment (Cloud MYSIMCLOUD) :
|name |type |sut |cloud_ip |arrival |aidrs |uuid
|ai_1 |cassandra_ycsb |1_x_ycsb->2_x_seed |32.242.20.245 |1486589678 |none |7199B821-3901-55ED-B5FC-6BA801CFAF9E
(MYSIMCLOUD) vmlist
The following ATTACHED VMs are in this experiment (Cloud MYSIMCLOUD) :
|name |role |size |cloud_ip |host_name |vmc_pool |netname |ai |aidrs |uuid
|vm_1 |ycsb |platinum64 |225.198.171.76 |simhosta5 |SUT |private |none |none |7D7911EB-CD81-5968-BC55-BC09C2BA1116
|vm_3 |seed |platinum64 |177.97.195.138 |simhosta3 |SUT |private |ai_1 |none |AA0457E2-EE36-519B-85D6-4F36ADF82452
|vm_2 |ycsb |platinum64 |32.242.20.245 |simhosta6 |SUT |private |ai_1 |none |C42F2402-D7B0-507E-92A6-4C5E25EE06F1
|vm_4 |seed |platinum64 |146.241.38.202 |simhostb12 |SUT |private |ai_1 |none |43F3D32A-4231-5477-A2C3-FFD436A4705B
(MYSIMCLOUD) aiattach netperf
status: ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C) was successfully defined on Cloudbench SimCloud "MYSIMCLOUD" (will now be fully deployed)
status: Starting instance "cb-cbuser-MYSIMCLOUD-vm5-netclient-ai-2" on Cloudbench SimCloud, using the image "cb_netperf" (38DC1010-76D8-5115-90D3-ED72E9C70E79) and size "iron32", connected to network "private", on VMC "simzone_b" (host "simhosta4"), under tenant "default", injecting the contents of the pub ssh key "cbuser_cbtool_rsa" (userdata is "None").
status: Waiting for vm_5 (EE3F60D1-B16D-5AAF-BE8D-C08C35DC7E76), part of ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C), to start...
status: Starting instance "cb-cbuser-MYSIMCLOUD-vm6-netserver-ai-2" on Cloudbench SimCloud, using the image "cb_netperf" (38DC1010-76D8-5115-90D3-ED72E9C70E79) and size "iron32", connected to network "private", on VMC "simzone_a" (host "simhosta14"), under tenant "default", injecting the contents of the pub ssh key "cbuser_cbtool_rsa" (userdata is "None").
status: Waiting for vm_6 (ABE3299C-8B5A-5BBE-9A7C-628203622606), part of ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C), to start...
status: Trying to establish network connectivity to vm_5 (EE3F60D1-B16D-5AAF-BE8D-C08C35DC7E76), part of ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C), on IP address 83.87.223.76 (using method "wait_for_0")...
status: Trying to establish network connectivity to vm_6 (ABE3299C-8B5A-5BBE-9A7C-628203622606), part of ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C), on IP address 202.252.210.161 (using method "wait_for_0")...
status: Checking ssh accessibility on vm_5 (EE3F60D1-B16D-5AAF-BE8D-C08C35DC7E76), part of ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C): ssh -p 22 -i /home/cbuser/cbtool/lib/auxiliary//../../credentials/cbtool_rsa [email protected] "/bin/true"...
status: Bootstrapping vm_5 (EE3F60D1-B16D-5AAF-BE8D-C08C35DC7E76), part of ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C): creating file cb_os_paramaters.txt in "cbuser" user's home dir on IP address 83.87.223.76...
status: Sending a copy of the code tree to vm_5 (EE3F60D1-B16D-5AAF-BE8D-C08C35DC7E76), part of ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C), on IP address 83.87.223.76...
status: Checking ssh accessibility on vm_6 (ABE3299C-8B5A-5BBE-9A7C-628203622606), part of ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C): ssh -p 22 -i /home/cbuser/cbtool/lib/auxiliary//../../credentials/cbtool_rsa [email protected] "/bin/true"...
status: Bootstrapping vm_6 (ABE3299C-8B5A-5BBE-9A7C-628203622606), part of ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C): creating file cb_os_paramaters.txt in "cbuser" user's home dir on IP address 202.252.210.161...
status: Sending a copy of the code tree to vm_6 (ABE3299C-8B5A-5BBE-9A7C-628203622606), part of ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C), on IP address 202.252.210.161...
status: Starting a new "performance emitter" for ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C)
status: ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C) was successfully defined on Cloudbench SimCloud "MYSIMCLOUD" (will now be fully deployed)
status: Performing generic application instance post_boot configurationon all VMs belonging to ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C)...
status: Running application-specific "setup" configuration on all VMs belonging to ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C)...
status: QEMU Scraper will NOT be automatically started during the deployment of ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C)...
AI object E16C4E48-6C73-5F41-815E-50D7AD29D81C (named "ai_2") sucessfully attached to this experiment. It is ssh-accessible at the IP address 225.32.243.52 (cb-cbuser-MYSIMCLOUD-vm5-netclient-ai-2).
(MYSIMCLOUD) ailist
The following ATTACHED AIs are in this experiment (Cloud MYSIMCLOUD) :
|name |type |sut |cloud_ip |arrival |aidrs |uuid
|ai_1 |cassandra_ycsb |1_x_ycsb->2_x_seed |32.242.20.245 |1486589678 |none |7199B821-3901-55ED-B5FC-6BA801CFAF9E
|ai_2 |netperf |1_x_netclient->1_x_netserver |225.32.243.52 |1486589798 |none |E16C4E48-6C73-5F41-815E-50D7AD29D81C
(MYSIMCLOUD) vmlist
The following ATTACHED VMs are in this experiment (Cloud MYSIMCLOUD) :
|name |role |size |cloud_ip |host_name |vmc_pool |netname |ai |aidrs |uuid
|vm_1 |ycsb |platinum64 |225.198.171.76 |simhosta5 |SUT |private |none |none |7D7911EB-CD81-5968-BC55-BC09C2BA1116
|vm_3 |seed |platinum64 |177.97.195.138 |simhosta3 |SUT |private |ai_1 |none |AA0457E2-EE36-519B-85D6-4F36ADF82452
|vm_2 |ycsb |platinum64 |32.242.20.245 |simhosta6 |SUT |private |ai_1 |none |C42F2402-D7B0-507E-92A6-4C5E25EE06F1
|vm_4 |seed |platinum64 |146.241.38.202 |simhostb12 |SUT |private |ai_1 |none |43F3D32A-4231-5477-A2C3-FFD436A4705B
|vm_5 |netclient |iron32 |225.32.243.52 |simhosta4 |LG |private |ai_2 |none |EE3F60D1-B16D-5AAF-BE8D-C08C35DC7E76
|vm_6 |netserver |iron32 |243.50.59.121 |simhosta14
At this point, you can wait around 3 minutes, and check if any performance metrics are already reported (these simulated VApps do emit fake performance metrics) are already produced with the command monlist VM
(MYSIMCLOUD) monlist VM
The following VMs reported management metrics:
Name |Age (seconds) |Experiment id |Number of samples
vm_1 |164 |EXP-02-08-2017-11-00-56-PM-UTC |1
vm_2 |164 |EXP-02-08-2017-11-00-56-PM-UTC |1
vm_3 |164 |EXP-02-08-2017-11-00-56-PM-UTC |1
vm_4 |125 |EXP-02-08-2017-11-00-56-PM-UTC |1
vm_5 |125 |EXP-02-08-2017-11-00-56-PM-UTC |1
The following VMs reported runtime (OS) metrics:
Name |Age (seconds) |Experiment id |Number of samples
The following VMs reported runtime (Application) metrics:
Name |Age (seconds) |Experiment id |Number of samples
vm_1 |39 |EXP-02-08-2017-11-00-56-PM-UTC |2
vm_5 |39 |EXP-02-08-2017-11-00-56-PM-UTC |1
You should see one management metric sample for each of the six VMs, and one or more runtime (application) metric samples for at least two out the six VMs.
All *attach commands block the CLI during its execution. Since some commands (e.g., aiattach) can take quite a bit of time to complete, the keyword async can be appended at the end of the command to allow its execution in background. For instance, while deploying a Hadoop Virtual Application with the command ```aiattach hadoop```` would block the CLI for several minutes (depending on the cloud), the command aiattach hadoop async would return immediately, leaving a daemon executing the deployment in the background.
(MYSIMCLOUD) aiattach hadoop async
Background operation execution success. Operation "ai-attach" will be processed asynchronously, through the command ""/home/cbuser/cbtool/lib/operations//../../cbact" --procid=TEST_cbuser --osp=port:6379,experiment_inst:TEST_cbuser,host:9.2.208.21,pid:TEST_cbuser,dbid:10,timout:70,protocol:TCP,kind:redis,username:cbuser --msp=port:27017,password:cbpwdZ9,timeout:240,version:3,host:9.2.208.21,pid:TEST_cbuser,database:metrics,protocol:TCP,kind:mongodb,username:cbuser --oop=MYSIMCLOUD,hadoop,default,default,none,none,none,empty=empty --operation=ai-attach --cn=MYSIMCLOUD --uuid=55A0091B-BEC7-5C9D-BAB4-0D893987E511 --daemon". The process id is 26255.
(MYSIMCLOUD) ailist
The following ATTACHED AIs are in this experiment (Cloud MYSIMCLOUD) :
|name |type |sut |cloud_ip |arrival |aidrs |uuid
|ai_1 |cassandra_ycsb |1_x_ycsb->2_x_seed |32.242.20.245 |1486589678 |none |7199B821-3901-55ED-B5FC-6BA801CFAF9E
|ai_2 |netperf |1_x_netclient->1_x_netserver |225.32.243.52 |1486589798 |none |E16C4E48-6C73-5F41-815E-50D7AD29D81C
|ai_3 |hadoop |1_x_hadoopmaster->3_x_hadoopslave |152.193.194.83 |1486589890 |none |55A0091B-BEC7-5C9D-BAB4-0D893987E511
(MYSIMCLOUD) vmlist
The following ATTACHED VMs are in this experiment (Cloud MYSIMCLOUD) :
|name |role |size |cloud_ip |host_name |vmc_pool |netname |ai |aidrs |uuid
|vm_1 |ycsb |platinum64 |225.198.171.76 |simhosta5 |SUT |private |none |none |7D7911EB-CD81-5968-BC55-BC09C2BA1116
|vm_3 |seed |platinum64 |177.97.195.138 |simhosta3 |SUT |private |ai_1 |none |AA0457E2-EE36-519B-85D6-4F36ADF82452
|vm_2 |ycsb |platinum64 |32.242.20.245 |simhosta6 |SUT |private |ai_1 |none |C42F2402-D7B0-507E-92A6-4C5E25EE06F1
|vm_4 |seed |platinum64 |146.241.38.202 |simhostb12 |SUT |private |ai_1 |none |43F3D32A-4231-5477-A2C3-FFD436A4705B
|vm_5 |netclient |iron32 |225.32.243.52 |simhosta4 |LG |private |ai_2 |none |EE3F60D1-B16D-5AAF-BE8D-C08C35DC7E76
|vm_6 |netserver |iron32 |243.50.59.121 |simhosta14 |SUT |private |ai_2 |none |ABE3299C-8B5A-5BBE-9A7C-628203622606
|vm_7 |hadoopmaster |platinum64 |152.193.194.83 |simhosta12 |SUT |private |ai_3 |none |22BEEE8C-B61F-503E-B017-28E37933D8A9
|vm_8 |hadoopslave |platinum64 |86.60.172.230 |simhosta5 |SUT |private |ai_3 |none |7A4A07D3-39CE-5020-9112-57902D4C31C6
|vm_9 |hadoopslave |platinum64 |207.209.246.91 |simhostb7 |SUT |private |ai_3 |none |726654D1-9F49-5FAA-AA53-E8EE3F7C9265
|vm_10 |hadoopslave |platinum64 |55.250.53.62 |simhosta13
To exit, use the exit command. You can exit and restart the tool at any moment; the data/state is stored on an Object Store (Redis server) that is accessed by the CLI.
(MYSIMCLOUD) exit
cbuser@host:~/cbtool$ ~/cbtool/cb
Cbtool version is "55c720f"
Parsing "cloud definitions" file..... "/home/cbuser/cbtool/configs/cbuser_cloud_definitions.txt" opened and parsed successfully.
Checking "Object Store".....An Object Store of the kind "Redis" (shared) on node 127.0.0.1, TCP port 6379, database id "10" seems to be running.
Checking "Log Store".....A Log Store of the kind "rsyslog" (private) on node 127.0.0.1, UDP port 5114 seems to be running.
Checking "Metric Store".....A Metric Store of the kind "MongoDB" (shared) on node 127.0.0.1, TCP port 27017, database id "metrics" seems to be running.
Checking "File Store".....A File Store of the kind "rsync" (private) on node 127.0.0.1, TCP port 10000 seems to be running.
Executing "hard" reset: (killing all running toolkit processes and flushing stores) before starting the experiment......
Killing all processes... done
Flushing Object Store... done
Flushing Log Store... done
Flushing Metric Store... done
Checking for a running API service daemon.....API Service daemon was successfully started. The process id is ['17394'](http://127.0.0.1:7070).
Checking for a running GUI service daemon.....GUI Service daemon was successfully started. The process id is ['17478', '17479'], listening on port 8080. Full url is "http://127.0.0.1:8080".
############################# Executing command "cldattach sim MYSIMCLOUD" (specified on the configuration file)
The SIM cloud named "MYSIMCLOUD" was already attached to this experiment.
The experiment identifier is EXP-02-08-2017-09-27-24-PM-UTC
############################# Executing command "vmcattach all" (specified on the configuration file)
(MYSIMCLOUD) vmlist
The following ATTACHED VMs are in this experiment (Cloud MYSIMCLOUD) :
|name |role |size |cloud_ip |host_name |vmc_pool |netname |ai |aidrs |uuid
|vm_1 |ycsb |platinum64 |225.198.171.76 |simhosta5 |SUT |private |none |none |7D7911EB-CD81-5968-BC55-BC09C2BA1116
|vm_3 |seed |platinum64 |177.97.195.138 |simhosta3 |SUT |private |ai_1 |none |AA0457E2-EE36-519B-85D6-4F36ADF82452
|vm_2 |ycsb |platinum64 |32.242.20.245 |simhosta6 |SUT |private |ai_1 |none |C42F2402-D7B0-507E-92A6-4C5E25EE06F1
|vm_4 |seed |platinum64 |146.241.38.202 |simhostb12 |SUT |private |ai_1 |none |43F3D32A-4231-5477-A2C3-FFD436A4705B
|vm_5 |netclient |iron32 |225.32.243.52 |simhosta4 |LG |private |ai_2 |none |EE3F60D1-B16D-5AAF-BE8D-C08C35DC7E76
|vm_6 |netserver |iron32 |243.50.59.121 |simhosta14 |SUT |private |ai_2 |none |ABE3299C-8B5A-5BBE-9A7C-628203622606
|vm_7 |hadoopmaster |platinum64 |152.193.194.83 |simhosta12 |SUT |private |ai_3 |none |22BEEE8C-B61F-503E-B017-28E37933D8A9
|vm_8 |hadoopslave |platinum64 |86.60.172.230 |simhosta5 |SUT |private |ai_3 |none |7A4A07D3-39CE-5020-9112-57902D4C31C6
|vm_9 |hadoopslave |platinum64 |207.209.246.91 |simhostb7 |SUT |private |ai_3 |none |726654D1-9F49-5FAA-AA53-E8EE3F7C9265
|vm_10 |hadoopslave |platinum64 |55.250.53.62 |simhosta13
When the experiment is finished, use the command clddetach to make sure that no VMs were left behind on the cloud.
(MYSIMCLOUD) clddetach
status: Waiting for all active AIDRS daemons to finish gracefully....
status: All AIDRS (daemons and objects were removed).
status: Removing all VMCRS objects attached to this experiment.
status: Removing all FIRS objects attached to this experiment.
status: Removing all AI objects attached to this experiment.
status: Sending a termination request for instance cb-cbuser-MYSIMCLOUD-vm2-ycsb-ai-1 (cloud-assigned uuid F054C6F2-2CA6-5F69-B0FC-630D36117B87)....
status: Sending a termination request for instance cb-cbuser-MYSIMCLOUD-vm3-seed-ai-1 (cloud-assigned uuid 0A447501-36E2-509B-A5AB-6BF4FEDF6173)....
status: Sending a termination request for instance cb-cbuser-MYSIMCLOUD-vm4-seed-ai-1 (cloud-assigned uuid 4921665B-1581-5734-8FE1-7076B8F73B22)....
status: ai_1 (7199B821-3901-55ED-B5FC-6BA801CFAF9E) was successfully undefined on Cloudbench SimCloud "MYSIMCLOUD"
status: Sending a termination request for instance cb-cbuser-MYSIMCLOUD-vm10-hadoopslave-ai-3 (cloud-assigned uuid F1D98B23-89B0-5A47-B8E0-BEEE29409975)....
status: Sending a termination request for instance cb-cbuser-MYSIMCLOUD-vm7-hadoopmaster-ai-3 (cloud-assigned uuid 82207167-63A1-5418-922A-1D162EE7939F)....
status: Sending a termination request for instance cb-cbuser-MYSIMCLOUD-vm8-hadoopslave-ai-3 (cloud-assigned uuid 153710D8-AF90-5DB1-80C5-7ED0BACA747E)....
status: Sending a termination request for instance cb-cbuser-MYSIMCLOUD-vm9-hadoopslave-ai-3 (cloud-assigned uuid A18B560D-250A-5BBA-B394-CB0E69BBD6C3)....
status: ai_3 (55A0091B-BEC7-5C9D-BAB4-0D893987E511) was successfully undefined on Cloudbench SimCloud "MYSIMCLOUD"
status: Sending a termination request for instance cb-cbuser-MYSIMCLOUD-vm5-netclient-ai-2 (cloud-assigned uuid CD27475F-4F18-5502-86B3-DE1B5FCB930A)....
status: Sending a termination request for instance cb-cbuser-MYSIMCLOUD-vm6-netserver-ai-2 (cloud-assigned uuid 30A0B7A7-DF5B-5E17-8C0B-2B25DA7468D3)....
status: ai_2 (E16C4E48-6C73-5F41-815E-50D7AD29D81C) was successfully undefined on Cloudbench SimCloud "MYSIMCLOUD"
status: Done
status: Removing all VM objects attached to this experiment.
status: Sending a termination request for instance cb-cbuser-MYSIMCLOUD-vm1-ycsb (cloud-assigned uuid 497B0113-9924-52C0-B61C-5BFBACFE3837)....
status: Done
status: Removing all VMC objects attached to this experiment.
status: Removing all VMs previously created on VMC "simzone_a" (only VM names starting with "cb-cbuser-MYSIMCLOUD").....
status: VMC simzone_a (2596C294-4875-5242-83C9-29A4C2EF5BFA) was successfully unregistered on Cloudbench SimCloud "MYSIMCLOUD"
status: Removing all VMs previously created on VMC "simzone_b" (only VM names starting with "cb-cbuser-MYSIMCLOUD").....
status: VMC simzone_b (696B07A1-3C20-5A74-A40E-ACFFBA4B938D) was successfully unregistered on Cloudbench SimCloud "MYSIMCLOUD"
status: Done
status: Removing all contents from Object Store (GLOBAL objects,VIEWS, etc.)
Disassociating default cloud: MYSIMCLOUD
Cloud MYSIMCLOUD was successfully detached from this experiment.
()
After this, you will see an empty prompt, (), indicating that there is no cloud attached to this experiment.