IDCフロンティアのセルフタイプでUnixBenchしてみた。

IDCフロンティアのセルフタイプクラウドのM4でベンチを計測


[code language=”bash”]
make[1]: Leaving directory `/root/UnixBench’
sh: 3dinfo: command not found

# # # # # # # ##### ###### # # #### # #
# # ## # # # # # # # ## # # # # #
# # # # # # ## ##### ##### # # # # ######
# # # # # # ## # # # # # # # # #
# # # ## # # # # # # # ## # # # #
#### # # # # # ##### ###### # # #### # #

Version 5.1.3 Based on the Byte Magazine Unix Benchmark
Multi-CPU version Version 5 revisions by Ian Smith,
Sunnyvale, CA, USA
January 13, 2011 johantheghost at yahoo period com
1 x Dhrystone 2 using register variables 1 2 3 4 5 6 7 8 9 10
1 x Double-Precision Whetstone 1 2 3 4 5 6 7 8 9 10
[/code]

しばらく放置・・・


[code language=”bash”]
========================================================================
BYTE UNIX Benchmarks (Version 5.1.3)

System: i-****-****-VM: GNU/Linux
OS: GNU/Linux — 2.6.32-358.18.1.el6.x86_64 — #1 SMP Wed Aug 28 17:19:38 UTC 2013
Machine: x86_64 (x86_64)
Language: en_US.utf8 (charmap="UTF-8", collate="UTF-8")
CPU 0: Intel(R) Xeon(R) CPU X5675 @ 3.07GHz (6133.6 bogomips)
x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET
CPU 1: Intel(R) Xeon(R) CPU X5675 @ 3.07GHz (6133.6 bogomips)
x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET
17:17:04 up 2 days, 22:15, 1 user, load average: 0.61, 0.19, 0.06; runlevel 3

————————————————————————
Benchmark Run: 月 9月 30 2013 17:17:04 – 17:45:12
2 CPUs in system; running 1 parallel copy of tests

Dhrystone 2 using register variables 28367253.0 lps (10.0 s, 7 samples)
Double-Precision Whetstone 3530.8 MWIPS (10.0 s, 7 samples)
Execl Throughput 3441.7 lps (29.8 s, 2 samples)
File Copy 1024 bufsize 2000 maxblocks 817480.5 KBps (30.0 s, 2 samples)
File Copy 256 bufsize 500 maxblocks 249981.9 KBps (30.0 s, 2 samples)
File Copy 4096 bufsize 8000 maxblocks 1689691.9 KBps (30.0 s, 2 samples)
Pipe Throughput 1776811.1 lps (10.0 s, 7 samples)
Pipe-based Context Switching 321488.6 lps (10.0 s, 7 samples)
Process Creation 9456.1 lps (30.0 s, 2 samples)
Shell Scripts (1 concurrent) 5336.2 lpm (60.0 s, 2 samples)
Shell Scripts (8 concurrent) 747.7 lpm (60.0 s, 2 samples)
System Call Overhead 2036710.3 lps (10.0 s, 7 samples)

System Benchmarks Index Values BASELINE RESULT INDEX
Dhrystone 2 using register variables 116700.0 28367253.0 2430.8
Double-Precision Whetstone 55.0 3530.8 642.0
Execl Throughput 43.0 3441.7 800.4
File Copy 1024 bufsize 2000 maxblocks 3960.0 817480.5 2064.3
File Copy 256 bufsize 500 maxblocks 1655.0 249981.9 1510.5
File Copy 4096 bufsize 8000 maxblocks 5800.0 1689691.9 2913.3
Pipe Throughput 12440.0 1776811.1 1428.3
Pipe-based Context Switching 4000.0 321488.6 803.7
Process Creation 126.0 9456.1 750.5
Shell Scripts (1 concurrent) 42.4 5336.2 1258.5
Shell Scripts (8 concurrent) 6.0 747.7 1246.1
System Call Overhead 15000.0 2036710.3 1357.8
========
System Benchmarks Index Score 1287.8

————————————————————————
Benchmark Run: 月 9月 30 2013 17:45:12 – 18:14:24
2 CPUs in system; running 2 parallel copies of tests

Dhrystone 2 using register variables 35991606.7 lps (10.0 s, 7 samples)
Double-Precision Whetstone 3866.8 MWIPS (15.8 s, 7 samples)
Execl Throughput 4974.5 lps (30.0 s, 2 samples)
File Copy 1024 bufsize 2000 maxblocks 703626.0 KBps (30.0 s, 2 samples)
File Copy 256 bufsize 500 maxblocks 196495.1 KBps (30.0 s, 2 samples)
File Copy 4096 bufsize 8000 maxblocks 1632889.8 KBps (30.0 s, 2 samples)
Pipe Throughput 2232317.3 lps (10.0 s, 7 samples)
Pipe-based Context Switching 420895.9 lps (10.0 s, 7 samples)
Process Creation 15183.9 lps (30.0 s, 2 samples)
Shell Scripts (1 concurrent) 5627.4 lpm (60.0 s, 2 samples)
Shell Scripts (8 concurrent) 748.7 lpm (60.1 s, 2 samples)
System Call Overhead 2325012.8 lps (10.0 s, 7 samples)

System Benchmarks Index Values BASELINE RESULT INDEX
Dhrystone 2 using register variables 116700.0 35991606.7 3084.1
Double-Precision Whetstone 55.0 3866.8 703.1
Execl Throughput 43.0 4974.5 1156.9
File Copy 1024 bufsize 2000 maxblocks 3960.0 703626.0 1776.8
File Copy 256 bufsize 500 maxblocks 1655.0 196495.1 1187.3
File Copy 4096 bufsize 8000 maxblocks 5800.0 1632889.8 2815.3
Pipe Throughput 12440.0 2232317.3 1794.5
Pipe-based Context Switching 4000.0 420895.9 1052.2
Process Creation 126.0 15183.9 1205.1
Shell Scripts (1 concurrent) 42.4 5627.4 1327.2
Shell Scripts (8 concurrent) 6.0 748.7 1247.9
System Call Overhead 15000.0 2325012.8 1550.0
========
System Benchmarks Index Score 1450.9
[/code]

今回のスペックM4は2CPU(1.6GHz)の4GBというスペック


CloudStackでXenServerがUnable to add the hostで追加できない。

CloudStackで構築していたら、host(コンピューティングノード)の追加で「Unable to add the host」とエラーになってしまいました。
エラー[Unable to add host]



今回のCloudStack環境

Management Server、Database Server、Storage共通
  • CentOS release 6.3 (Final)
  • CloudStack-oss-3.0.2-1-rhel6.2
Computing Node
  • XenServer release 6.0.2-53456p (xenenterprise)


注意点として、CloudStackでXenを利用するにはバージョンに注意する必要があります。
XenServer6.0.2の場合、CloudStack3.0.1を利用し、XenServer6.0場合、CloudStack3.0.0を使用する必要があるので注意しましょう。
また、Xenのライセンス(license.xslic)やインストール時点でのパッチ(今回はXS602E003.zip)は適応させておきましょう。

CloudStack[Unable to add host/Unable to add the host]を解決

Unable to add the hostを解決するにはデータベースの修正とXenCenterでの操作が必要でした。

Unable to add host/Unable to add the hostを解決(XenCenter)

CloudStack側でホストの追加を行う前に、XenCenterで事前Poolの作成を行います。

Unable to add host/Unable to add the hostを解決(mysql)

CloudStackのデータベースを修正します。

[sourcecode language=”sql”]
mysql>
mysql> use cloud
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql>
mysql> INSERT INTO `cloud`.`configuration` (`category`, `instance`, `component`, `name`, `value`, `description`) VALUES (‘Advanced’, ‘DEFAULT’, ‘management server’, ‘xen.check.hvm’, ‘false’, ‘Shoud we allow only the XenServers support HVM’);
Query OK, 1 row affected (0.05 sec)
mysql>
mysql> commit
-> ;
Query OK, 0 rows affected (0.00 sec)
mysql>
[/sourcecode]

これでUnable to add host/Unable to add the hostが出ていましたが、無事CloudStackへXenServerを追加することができました。