端くれプログラマの備忘録 – ページ 78 – 最近はウェブ系アプリ中心、あとWindowsアプリちょっと

SSH鍵の生成

$ pwd
/c/Users/84kure
$ ssh-keygen -t rsa -C "you@homestead"
Generating public/private rsa key pair.
Enter file in which to save the key (/c/Users/84kure/.ssh/id_rsa):
Created directory '/c/Users/84kure/.ssh'.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /c/Users/84kure/.ssh/id_rsa.
Your public key has been saved in /c/Users/84kure/.ssh/id_rsa.pub.
The key fingerprint is:
85:d6:5b:dc:02:0c:0d:d8:ac:e7:be:c9:83:b3:7c:f1 you@homestead
The key's randomart image is:
+--[ RSA 2048]----+
|       +o=.      |
|      . oooo .   |
|       .o o + .  |
|      .... o .   |
|       oS .      |
|        o        |
|       o o       |
|     .o.+.E      |
|      o++o       |
+-----------------+

$

$ pwd

/c/Users/84kure

$ ssh-keygen -t rsa -C "you@homestead"

Generating public/private rsa key pair.

Enter file in which to save the key (/c/Users/84kure/.ssh/id_rsa):

Created directory '/c/Users/84kure/.ssh'.

Enter passphrase (empty for no passphrase):

Enter same passphrase again:

Your identification has been saved in /c/Users/84kure/.ssh/id_rsa.

Your public key has been saved in /c/Users/84kure/.ssh/id_rsa.pub.

The key fingerprint is:

85:d6:5b:dc:02:0c:0d:d8:ac:e7:be:c9:83:b3:7c:f1 you@homestead

The key's randomart image is:

+--[ RSA 2048]----+

| +o=. |

| . oooo . |

| .o o + . |

| .... o . |

| oS . |

| o |

| o o |

| .o.+.E |

| o++o |

+-----------------+

~/.sshディレクトリに鍵ファイルペアが生成される。

共有フォルダの作成

$ pwd
/c/Users/84kure
$ mkdir Code
$

$ pwd

/c/Users/84kure

$ mkdir Code

Homestead.yamlの編集

デフォルトのまま変更する必要は無さそう。

~/.homestead/Homestead.yaml

ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox             #Vagrantプロバイダの種類

authorize: ~/.ssh/id_rsa.pub     #SSH公開鍵の所在

keys:                            #SSH秘密鍵の所在
    - ~/.ssh/id_rsa

folders:                         #共有フォルダのマッピング
    - map: ~/Code
      to: /home/vagrant/Code

sites:                           #Nginxサイトのマッピング
    - map: homestead.app
      to: /home/vagrant/Code/Laravel/public

databases:
    - homestead

variables:
    - key: APP_ENV
      value: local

# blackfire:
#     - id: foo
#       token: bar
#       client-id: foo
#       client-token: bar

# ports:
#     - send: 93000
#       to: 9300
#     - send: 7777
#       to: 777
#       protocol: udp

ip: "192.168.10.10"

memory: 2048

cpus: 1

provider: virtualbox #Vagrantプロバイダの種類

authorize: ~/.ssh/id_rsa.pub #SSH公開鍵の所在

keys: #SSH秘密鍵の所在

- ~/.ssh/id_rsa

folders: #共有フォルダのマッピング

- map: ~/Code

to: /home/vagrant/Code

sites: #Nginxサイトのマッピング

- map: homestead.app

to: /home/vagrant/Code/Laravel/public

databases:

- homestead

variables:

- key: APP_ENV

value: local

# blackfire:

# - id: foo

# token: bar

# client-id: foo

# client-token: bar

# ports:

# - send: 93000

# to: 9300

# - send: 7777

# to: 777

# protocol: udp

ドメイン名の設定

エディタを管理者権限で実行してC:\Windows\System32\drivers\etc\hostsを編集。

192.168.10.10  homestead.app

1	192.168.10.10 homestead.app

これで設定は完了。

(次回へ続く)

[Laravel] WindowsへのHomesteadのセットアップ (1)

2015年7月19日2015年9月12日 @84kure

オンラインドキュメントを参照しながら、ローカルでのLaravelの開発環境を構築する。

Installation
http://laravel.com/docs/5.1

サーバー要件は以下の通り。

PHP >= 5.5.9
OpenSSL PHP Extension
PDO PHP Extension
Mbstring PHP Extension
Tokenizer PHP Extension

開発環境としてLaravel HomesteadというVagrant boxが用意されているようなので、ドキュメントの手順に従ってセットアップしてみよう。

Laravel Homestead
http://laravel.com/docs/5.1/homestead

HomesteadはVagrant 1.7でビルドされて動作検証済み。以下のソフトが含まれているとのこと。

Ubuntu 14.04
PHP 5.6
HHVM
Nginx
MySQL
Postgres
Node (With PM2, Bower, Grunt, and Gulp)
Redis
Memcached
Beanstalkd
Laravel Envoy
Blackfire Profiler

念のため手元のマシンのVagrantのバージョンをチェック。バージョンは問題ない。

> vagrant version
Installed Version: 1.7.2
Latest Version: 1.7.4
>

> vagrant version

Installed Version: 1.7.2

Latest Version: 1.7.4

Homestead Vagrant Boxのインストール

コマンドプロンプトから実行。

> vagrant box add laravel/homestead
==> box: Loading metadata for box 'laravel/homestead'
    box: URL: https://atlas.hashicorp.com/laravel/homestead
This box can work with multiple providers! The providers that it
can work with are listed below. Please review the list and choose
the provider you will be working with.

1) virtualbox
2) vmware_desktop

Enter your choice: 1
==> box: Adding box 'laravel/homestead' (v0.2.7) for provider: virtualbox
    box: Downloading: https://atlas.hashicorp.com/laravel/boxes/homestead/versio
ns/0.2.7/providers/virtualbox.box
    box: Progress: 100% (Rate: 2690k/s, Estimated time remaining: --:--:--)
==> box: Successfully added box 'laravel/homestead' (v0.2.7) for 'virtualbox'!

>

> vagrant box add laravel/homestead

==> box: Loading metadata for box 'laravel/homestead'

box: URL: https://atlas.hashicorp.com/laravel/homestead

This box can work with multiple providers! The providers that it

can work with are listed below. Please review the list and choose

the provider you will be working with.

1) virtualbox

2) vmware_desktop

Enter your choice: 1

==> box: Adding box 'laravel/homestead' (v0.2.7) for provider: virtualbox

box: Downloading: https://atlas.hashicorp.com/laravel/boxes/homestead/versio

ns/0.2.7/providers/virtualbox.box

box: Progress: 100% (Rate: 2690k/s, Estimated time remaining: --:--:--)

==> box: Successfully added box 'laravel/homestead' (v0.2.7) for 'virtualbox'!

Homesteadリポジトリのクローニング

シェルスクリプトを実行したいので、Git Bashから実行。

$ cd C:\Users\84kure
$ git clone https://github.com/laravel/homestead.git Homestead
Cloning into 'Homestead'...
remote: Counting objects: 1195, done.
remote: Compressing objects: 100% (5/5), done.
remote: Total 1195 (delta 0), reused 0 (delta 0), pack-reused 1190
Receiving objects: 100% (1195/1195), 183.34 KiB | 0 bytes/s, done.
Resolving deltas: 100% (706/706), done.
Checking connectivity... done.

$ cd Homestead
$ bash init.sh
Homestead initialized!
$

$ cd C:\Users\84kure

$ git clone https://github.com/laravel/homestead.git Homestead

Cloning into 'Homestead'...

remote: Counting objects: 1195, done.

remote: Compressing objects: 100% (5/5), done.

remote: Total 1195 (delta 0), reused 0 (delta 0), pack-reused 1190

Receiving objects: 100% (1195/1195), 183.34 KiB | 0 bytes/s, done.

Resolving deltas: 100% (706/706), done.

Checking connectivity... done.

$ cd Homestead

$ bash init.sh

Homestead initialized!

C:\Users\84kure\.homesteadにHomestead.yamlが作成される。

(次回へ続く)

[PHP] 配列から重複した値を削除する

2015年7月18日2015年9月11日 @84kure

array_unique関数を使う。キーは保持されることに注意。

サンプルコード

$ids = getIds();
print_r($ids);
$ids = array_unique($ids);
print_r($ids);

$ids = getIds();

print_r($ids);

$ids = array_unique($ids);

print_r($ids);

処理例

処理前

Array
(
[0] => 1
[1] => 21
[2] => 20
[3] => 23
[4] => 29
[5] => 34
[6] => 26
[7] => 25
[8] => 36
[9] => 22
[10] => 252
[11] => 243
[12] => 198
[13] => 210
[14] => 21
[15] => 20
[16] => 205
[17] => 23
[18] => 192
[19] => 29
[20] => 26
[21] => 195
[22] => 25
[23] => 200
[24] => 202
[25] => 22
[26] => 124
[27] => 34
[28] => 125
[29] => 36
[30] => 52
[31] => 55
[32] => 57
[33] => 54
[34] => 149
[35] => 36
)

Array

(

[0] => 1

[1] => 21

[2] => 20

[3] => 23

[4] => 29

[5] => 34

[6] => 26

[7] => 25

[8] => 36

[9] => 22

[10] => 252

[11] => 243

[12] => 198

[13] => 210

[14] => 21

[15] => 20

[16] => 205

[17] => 23

[18] => 192

[19] => 29

[20] => 26

[21] => 195

[22] => 25

[23] => 200

[24] => 202

[25] => 22

[26] => 124

[27] => 34

[28] => 125

[29] => 36

[30] => 52

[31] => 55

[32] => 57

[33] => 54

[34] => 149

[35] => 36

)

処理後(重複削除後)

Array
(
[0] => 1
[1] => 21
[2] => 20
[3] => 23
[4] => 29
[5] => 34
[6] => 26
[7] => 25
[8] => 36
[9] => 22
[10] => 252
[11] => 243
[12] => 198
[13] => 210
[16] => 205
[18] => 192
[21] => 195
[23] => 200
[24] => 202
[26] => 124
[28] => 125
[30] => 52
[31] => 55
[32] => 57
[33] => 54
[34] => 149
)

Array

(

[0] => 1

[1] => 21

[2] => 20

[3] => 23

[4] => 29

[5] => 34

[6] => 26

[7] => 25

[8] => 36

[9] => 22

[10] => 252

[11] => 243

[12] => 198

[13] => 210

[16] => 205

[18] => 192

[21] => 195

[23] => 200

[24] => 202

[26] => 124

[28] => 125

[30] => 52

[31] => 55

[32] => 57

[33] => 54

[34] => 149

)

参考サイト

PHP: array_unique – Manual
http://php.net/manual/ja/function.array-unique.php

[Unix] ioping – ディスクI/Oのレイテンシを測定する

2015年7月17日2015年9月11日 @84kure

レイテンシとは (latency)： – IT用語辞典バイナリ
http://www.sophia-it.com/content/%E3%83%AC%E3%82%A4%E3%83%86%E3%83%B3%E3%82%B7

レイテンシとは、データの転送要求などのリクエストを発してから、リクエストの結果が返ってくるまでにかかる遅延時間のことである。

インストール

$ wget https://ioping.googlecode.com/files/ioping-0.8.tar.gz
$ tar zxvf ioping-0.8.tar.gz
$ cd ioping-0.8
$ make
$ sudo make install
$

$ wget https://ioping.googlecode.com/files/ioping-0.8.tar.gz

$ tar zxvf ioping-0.8.tar.gz

$ cd ioping-0.8

$ make

$ sudo make install

使い方

Usage: ioping [-LABCDWRq] [-c count] [-w deadline] [-pP period] [-i interval]
               [-s size] [-S wsize] [-o offset] directory|file|device
        ioping -h | -v

      -c <count>      stop after <count> requests
      -w <deadline>   stop after <deadline>
      -p <period>     print raw statistics for every <period> requests
      -P <period>     print raw statistics for every <period> in time
      -i <interval>   interval between requests (1s)
      -s <size>       request size (4k)
      -S <wsize>      working set size (1m)
      -o <offset>     working set offset (0)
      -k              keep and reuse temporary working file
      -L              use sequential operations (includes -s 256k)
      -A              use asynchronous I/O
      -C              use cached I/O
      -D              use direct I/O
      -W              use write I/O *DANGEROUS*
      -R              seek rate test (same as -q -i 0 -w 3 -S 64m)
      -B              print final statistics in raw format
      -q              suppress human-readable output
      -h              display this message and exit
      -v              display version and exit

Usage: ioping [-LABCDWRq] [-c count] [-w deadline] [-pP period] [-i interval]

[-s size] [-S wsize] [-o offset] directory|file|device

ioping -h | -v

-c <count> stop after <count> requests

-w <deadline> stop after <deadline>

-p <period> print raw statistics for every <period> requests

-P <period> print raw statistics for every <period> in time

-i <interval> interval between requests (1s)

-s <size> request size (4k)

-S <wsize> working set size (1m)

-o <offset> working set offset (0)

-k keep and reuse temporary working file

-L use sequential operations (includes -s 256k)

-A use asynchronous I/O

-C use cached I/O

-D use direct I/O

-W use write I/O *DANGEROUS*

-R seek rate test (same as -q -i 0 -w 3 -S 64m)

-B print final statistics in raw format

-q suppress human-readable output

-h display this message and exit

-v display version and exit

実行例

$ ioping .
4.0 KiB from . (ext4 /dev/mapper/VolGroup-lv_root): request=1 time=6.8 ms
4.0 KiB from . (ext4 /dev/mapper/VolGroup-lv_root): request=2 time=256 us
4.0 KiB from . (ext4 /dev/mapper/VolGroup-lv_root): request=3 time=420 us
4.0 KiB from . (ext4 /dev/mapper/VolGroup-lv_root): request=4 time=227 us
4.0 KiB from . (ext4 /dev/mapper/VolGroup-lv_root): request=5 time=299 us
4.0 KiB from . (ext4 /dev/mapper/VolGroup-lv_root): request=6 time=353 us
4.0 KiB from . (ext4 /dev/mapper/VolGroup-lv_root): request=7 time=362 us
4.0 KiB from . (ext4 /dev/mapper/VolGroup-lv_root): request=8 time=265 us
^C
--- . (ext4 /dev/mapper/VolGroup-lv_root) ioping statistics ---
8 requests completed in 7.8 s, 886 iops, 3.5 MiB/s
min/avg/max/mdev = 227 us / 1.1 ms / 6.8 ms / 2.2 ms
$ ioping -R -s 4k .
--- . (ext4 /dev/mapper/VolGroup-lv_root) ioping statistics ---
24.7 k requests completed in 3.0 s, 8.4 k iops, 32.7 MiB/s
min/avg/max/mdev = 60 us / 119 us / 7.5 ms / 74 us
$ ioping -R -s 256k .
--- . (ext4 /dev/mapper/VolGroup-lv_root) ioping statistics ---
7.9 k requests completed in 3.0 s, 2.8 k iops, 696.7 MiB/s
min/avg/max/mdev = 230 us / 358 us / 8.0 ms / 98 us
$

$ ioping .

4.0 KiB from . (ext4 /dev/mapper/VolGroup-lv_root): request=1 time=6.8 ms

4.0 KiB from . (ext4 /dev/mapper/VolGroup-lv_root): request=2 time=256 us

4.0 KiB from . (ext4 /dev/mapper/VolGroup-lv_root): request=3 time=420 us

4.0 KiB from . (ext4 /dev/mapper/VolGroup-lv_root): request=4 time=227 us

4.0 KiB from . (ext4 /dev/mapper/VolGroup-lv_root): request=5 time=299 us

4.0 KiB from . (ext4 /dev/mapper/VolGroup-lv_root): request=6 time=353 us

4.0 KiB from . (ext4 /dev/mapper/VolGroup-lv_root): request=7 time=362 us

4.0 KiB from . (ext4 /dev/mapper/VolGroup-lv_root): request=8 time=265 us

--- . (ext4 /dev/mapper/VolGroup-lv_root) ioping statistics ---

8 requests completed in 7.8 s, 886 iops, 3.5 MiB/s

min/avg/max/mdev = 227 us / 1.1 ms / 6.8 ms / 2.2 ms

$ ioping -R -s 4k .

--- . (ext4 /dev/mapper/VolGroup-lv_root) ioping statistics ---

24.7 k requests completed in 3.0 s, 8.4 k iops, 32.7 MiB/s

min/avg/max/mdev = 60 us / 119 us / 7.5 ms / 74 us

$ ioping -R -s 256k .

--- . (ext4 /dev/mapper/VolGroup-lv_root) ioping statistics ---

7.9 k requests completed in 3.0 s, 2.8 k iops, 696.7 MiB/s

min/avg/max/mdev = 230 us / 358 us / 8.0 ms / 98 us

参考サイト

ioping – simple disk I/0 latency measuring tool – Google Project Hosting
https://code.google.com/p/ioping/

ioping で I/O レイテンシーを計ってみた 08th SE’s Blog
http://08thse.blog87.fc2.com/blog-entry-350.html

[Unix] lspci – PCIデバイスを一覧する

2015年7月16日2015年9月11日 @84kure

リモートサーバーのハードウェア構成やネットワークカードの種類などを知るのに役立つ。

$ lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter
00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)
00:04.0 System peripheral: InnoTek Systemberatung GmbH VirtualBox Guest Service
00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08)
00:08.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)
00:0d.0 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] (rev 02)
$

$ lspci

00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)

00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]

00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter

00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)

00:04.0 System peripheral: InnoTek Systemberatung GmbH VirtualBox Guest Service

00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08)

00:08.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)

00:0d.0 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] (rev 02)

参考サイト

Linuxコマンド集 – 【lspci】PCIデバイスを表示する：ITpro
http://itpro.nikkeibp.co.jp/article/COLUMN/20140303/540546/

[Unix] lsblk – ブロックデバイス一覧を表示する

2015年7月15日2015年9月10日 @84kure

ハードドライブのデバイス名やマウントポイントなどを一覧できる。

$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sdb      8:16   0    68G  0 disk
|-sdb1   8:17   0    52G  0 part /
|-sdb2   8:18   0     1K  0 part
`-sdb5   8:21   0    16G  0 part [SWAP]
sr0     11:0    1  1024M  0 rom
sr1     11:1    1  1024M  0 rom
$

$ lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT

sdb 8:16 0 68G 0 disk

|-sdb1 8:17 0 52G 0 part /

|-sdb2 8:18 0 1K 0 part

`-sdb5 8:21 0 16G 0 part [SWAP]

sr0 11:0 1 1024M 0 rom

sr1 11:1 1 1024M 0 rom

TYPEの意味

disk = a disk
part = a partition within a disk
rom = read only memory

参考サイト

How To Use Lsblk To List Block Device Information In Linux
http://linoxide.com/linux-command/linux-lsblk-command/

Ubuntu Manpage: lsblk – list block devices
http://manpages.ubuntu.com/manpages/raring/man8/lsblk.8.html

[Unix] cpuinfo – CPU情報を表示する

2015年7月14日2015年9月10日 @84kure

$ cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Xeon(R) CPU           L5420  @ 2.50GHz
stepping        : 10
microcode       : 0xa07
cpu MHz         : 2500.097
cache size      : 6144 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 4
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 xsave lahf_lm dtherm tpr_shadow vnmi flexpriority
bogomips        : 5000.19
clflush size    : 64
cache_alignment : 64
address sizes   : 38 bits physical, 48 bits virtual
power management:
$

$ cat /proc/cpuinfo

processor : 0

vendor_id : GenuineIntel

cpu family : 6

model : 23

model name : Intel(R) Xeon(R) CPU L5420 @ 2.50GHz

stepping : 10

microcode : 0xa07

cpu MHz : 2500.097

cache size : 6144 KB

physical id : 0

siblings : 4

core id : 0

cpu cores : 4

apicid : 0

initial apicid : 0

fpu : yes

fpu_exception : yes

cpuid level : 13

wp : yes

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 xsave lahf_lm dtherm tpr_shadow vnmi flexpriority

bogomips : 5000.19

clflush size : 64

cache_alignment : 64

address sizes : 38 bits physical, 48 bits virtual

power management:

[ホスティング] よさげな米国VPSプラン

2015年7月13日2015年9月10日 @84kure

もしVPSプラン使うならどのホスティング会社を選ぶか思案してみた。費用は月額$30ぐらいまで、条件はSelf-Managedプラン、非EIGホスティング会社。

ウェブマスター向けフォーラムなどで口コミ情報を漁ったところ、以下の３社が候補に残った。

Namecheapは元々はレジストラなんだけど、ホスティングは後発にも関わらず意外に評判が良かった。Media Templeは他社の同等のプランと比べて若干割高なゆえに、おそらく顧客の質が良いのではないかと予想。口コミで最も評価が高そうなのはFuture Hostingだったので、マジで使ってみようかと真剣に思案中。

Namecheap

https://www.namecheap.com/hosting/vps.aspx

VPS Hosting (Self Managed)

Choice of Operating Systems installed and tuned
Root Access
Reboot Access
Server Reinstalls: Free Operating System / cPanel reinstallation

VPS Lite – Xen

$19.95/mo
RAM 512 MB (+512 MB burst)
1 CPU core
15 GB HDD (SAS RAID 10)
100 GB Bandwidth
1 Dedicated IP

VPS 1 – Xen

$29.95/mo
RAM 1 GB (+1 GB burst)
1 CPU core
30 GB HDD (SAS RAID 10)
250 GB Bandwidth
2 Dedicated IPs

Namecheap VPS review | Web Hosting Talk
http://www.webhostingtalk.com/showthread.php?t=1287042

Future Hosting

https://www.futurehosting.com/virtual-servers/unmanaged-vps-hosting/

Unmanaged VPS Hosting

CentOS 6 with cPanel or Plesk. Your choice of CentOS, Fedora, Ubuntu or Debian with any other server
Easy Upgrades
VPS Servers are Secured Upon Delivery
Choice of 5 locations on 3 continents: Chicago (Illinois – US Central), Santa Clara (California – US West), Miami (Florida – US East), London (United Kingdom), Brisbane (Australia)
Future Protect™ Backups
Full Root Access
Redundant Future Hosting DNS Servers or Private DNS Servers

NOCP 1