使用由 Ikoula 巴拿马 Cloudstack
ro:Utilizarea Cloudstack de Ikoula Panamax
ru:Использование Cloudstack по Ikoula Panamax
pl:Użyj Cloudstack przez Ikoula Panamax
ja:Ikoula パナマックスで Cloudstack を使用します。
de:Verwenden von Cloudstack von Ikoula Panamax
nl:Cloudstack door Ikoula Panamax gebruiken
it:Utilizzare Cloudstack da Ikoula Panamax
pt:Usar o Cloudstack por Ikoula Panamax
es:Uso de Cloudstack por Ikoula Panamax
en:Use Cloudstack by Ikoula Panamax
ar:استخدام كلودستاك ببنما عكلة
fr:Utiliser Panamax sur Cloudstack by Ikoula
这篇文章是从由软件进行自动翻译。你可以看到这篇文章的源代码
如果你还不知道 巴拿马 它是一个产品 Open Source 由开发 Century Link Labs 那是两个市场的地方 和一个经理申请集装箱码头从直观的 web 界面。
它足以寻求我们的选择然后集团要部署应用程序上使用码头和一个巴拿马我们机构目标。
巴拿马型依赖技术码头，DCE， Fleet 和云 init 包含在 CoreOS 中。
我们将在我们的例子中使用 4 实例 CoreOS 更新一个用于客户端部分 /巴拿马型 UI 和 3 别人会形成 cluster 为部件 Panamax Remote Target (Panamax Remote Agent + Panamax Adapter) :
巴拿马型用户界面安装 /API (web 界面 /市场 )
在我们的论坛专用于客户端部分的巴拿马型船上 (巴拿马型 UI /API)下载存档文件包含安装程序 :
core@CoreOS-PanamaxUI ~ $ sudo curl -O http://download.panamax.io/installer/panamax-latest.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 15165 100 15165 0 0 22157 0 --:--:-- --:--:-- --:--:-- 49558
它创建的目录 /var/panamax 在那里你将安装文件解压缩 :
core@CoreOS-PanamaxUI ~ $ sudo mkdir -p /var/panamax
core@CoreOS-PanamaxUI ~ $ sudo tar -C /var/panamax -zxvf panamax-latest.tar.gz
./
./Makefile
./configure
./create-docker-mount
./LICENSE
./desktop
./panamax
./.coreosenv
./README.md
./CHANGELOG.md
./ubuntu.sh
./Vagrantfile
./.version
./coreos
./Vagrantfile-win
./CONTRIBUTING.md
它放置在目录 /var/panamax 和我们启动 CoreOS 特定安装程序通过指定您想要使用的稳定版本 (输出被截断自愿 ) :
core@CoreOS-PanamaxUI ~ $ cd /var/panamax
core@CoreOS-PanamaxUI /var/panamax $ sudo ./coreos install --stable
Installing Panamax...
Created symlink from /etc/systemd/system/update-engine-reboot-manager.service to /dev/null.
Created symlink from /etc/systemd/system/update-engine.service to /dev/null.
Created symlink from /etc/systemd/system/sockets.target.wants/systemd-journal-gatewayd.socket to /usr/lib64/systemd/system/systemd-
<!--T:12-->
docker pull centurylink/panamax-api:latest
.................
docker pull centurylink/panamax-ui:latest
.....
docker pull google/cadvisor:0.13.0
.........
docker pull centurylink/redis:latest
....
docker pull centurylink/dray:latest
...Created symlink from /etc/systemd/system/multi-user.target.wants/panamax-redis.service to /etc/systemd/system/panamax-redis.serv
Created symlink from /etc/systemd/system/multi-user.target.wants/panamax-dray.service to /etc/systemd/system/panamax-dray.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/panamax-metrics.service to /etc/systemd/system/panamax-metrics.ser
Created symlink from /etc/systemd/system/multi-user.target.wants/panamax-api.service to /etc/systemd/system/panamax-api.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/panamax-ui.service to /etc/systemd/system/panamax-ui.service.
...
Jul 10 11:45:39 CoreOS-PanamaxUI docker[1790]: => Rails 4.1.7 application starting in production on http://0.0.0.0:3000
Jul 10 11:45:39 CoreOS-PanamaxUI docker[1790]: => Run `rails server -h` for more startup options
Jul 10 11:45:39 CoreOS-PanamaxUI docker[1790]: => Notice: server is listening on all interfaces (0.0.0.0). Consider using 127.0.0.1 (--binding option)
Jul 10 11:45:39 CoreOS-PanamaxUI docker[1790]: => Ctrl-C to shutdown server
Panamax install complete
core@CoreOS-PanamaxUI /var/panamax $
我们可以验证我们 5 巴拿马型集装箱正在运行 :
core@CoreOS-PanamaxUI /var/panamax $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
41a18b410427 centurylink/panamax-ui:latest "/bin/sh -c 'bundle 3 minutes ago Up 3 minutes 0.0.0.0:3000->3000/tcp PMX_UI
0cc8befee1b7 centurylink/panamax-api:latest "/bin/sh -c 'bundle 3 minutes ago Up 3 minutes 0.0.0.0:3001->3000/tcp PMX_API
0929e65f6d55 google/cadvisor:0.13.0 "/usr/bin/cadvisor" 3 minutes ago Up 3 minutes 0.0.0.0:3002->8080/tcp PMX_CADVISOR
06b2219ac42e centurylink/dray:0.10.0 "/dray" 3 minutes ago Up 3 minutes 0.0.0.0:3003->3000/tcp PMX_DRAY
8a6110651dcc centurylink/redis:latest "redis-server" 3 minutes ago Up 3 minutes 6379/tcp PMX_DRAY_REDIS
我们可以连接到使用我们的浏览器在攻丝跟着我们实例的 ip 我们 UI 巴拿马 ":3000" 若要指定的侦听端口 (别忘了创建防火墙规则的权限，如果必要端口重定向 ) 其中 :
安装 Panamax Remote Deployment Target
连接到其中一个你 3 实例为部署的 CoreOS cluster :
生成一个新的 URL 的 discovery Etcd (令牌 ) 在变量中 (在这里 : ETCD_URL ) :
core@CoreOSnode-1 ~ $ ETCD_URL=$(curl http://discovery.etcd.io/new)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 58 100 58 0 0 79 0 --:--:-- --:--:-- --:--:-- 101
core@CoreOSnode-1 ~ $ echo $ETCD_URL
https://discovery.etcd.io/b8069c9bd67eae5cf19689daf4ebdd66
然后下载以下云-config.yml 模板文件 :
core@CoreOSnode-1 ~ $ sudo wget -NP /usr/share/oem/ http://mirror02.ikoula.com/priv/coreos/cloud-config.yml
--2015-06-16 15:37:53-- http://mirror02.ikoula.com/priv/coreos/cloud-config.yml
Resolving mirror02.ikoula.com... 80.93.XX.XXX, 2a00:c70:1:80:93:XX:XXX:1
Connecting to mirror02.ikoula.com|80.93.XX.XXX|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1542 (1.5K) [text/plain]
Remote file is newer, retrieving.
<!--T:23-->
--2015-06-16 15:37:53-- http://mirror02.ikoula.com/priv/coreos/cloud-config.yml
Reusing existing connection to mirror02.ikoula.com:80.
HTTP request sent, awaiting response... 200 OK
Length: 1542 (1.5K) [text/plain]
Saving to: '/usr/share/oem/cloud-config.yml'
<!--T:24-->
/usr/share/oem/cloud-config.yml 100%[===================================================================================================>] 1.51K --.-KB/s in 0s
<!--T:25-->
2015-06-16 15:37:53 (264 MB/s) - '/usr/share/oem/cloud-config.yml' saved [1542/1542]
core@CoreOSnode-1 ~ $ export `cat /etc/environment`
运行以下命令以自定义文件云-config.yml 下载与您环境的值 :
core@CoreOSnode-1 ~ $ sudo sed -i 's#DISCOVERY_URL#'$ETCD_URL'#g' /usr/share/oem/cloud-config.yml
core@CoreOSnode-1 ~ $ sudo sed -i 's#PRIVATE_IP#'$COREOS_PRIVATE_IPV4'#g' /usr/share/oem/cloud-config.yml
我们检查我们的 DCE 设置和 Fleet 好取代 :
core@CoreOSnode-1 ~ $ cat /usr/share/oem/cloud-config.yml
#cloud-config
<!--T:31-->
coreos:
units:
- name: cloudstack-ssh-key.service
command: restart
runtime: yes
content: |
[Unit]
Description=Sets SSH key from metadata
<!--T:32-->
[Service]
Type=oneshot
StandardOutput=journal+console
ExecStart=/usr/share/oem/bin/cloudstack-ssh-key
- name: cloudstack-hostname.service
command: restart
runtime: yes
content: |
[Unit]
Description=Sets hostname from metadata
<!--T:33-->
[Service]
Type=oneshot
StandardOutput=journal+console
ExecStart=/usr/share/oem/bin/cloudstack-hostname
- name: cloudstack-cloudinit.service
command: restart
runtime: yes
content: |
[Unit]
Description=Cloudinit from CloudStack-style metadata
Requires=coreos-setup-environment.service
After=coreos-setup-environment.service
<!--T:34-->
[Service]
Type=oneshot
EnvironmentFile=/etc/environment
ExecStart=/usr/share/oem/bin/cloudstack-coreos-cloudinit
- name: etcd.service
command: start
- name: fleet.service
command: start
oem:
id: cloudstack
name: CloudStack
version-id: 0.0.1-r3
home-url: http://cloudstack.apache.org/
bug-report-url: https://github.com/coreos/coreos-overlay
etcd:
discovery: https://discovery.etcd.io/b8069c9bd67eae5cf19689daf4ebdd66
addr: 178.170.XX.XXX:4001
peer-addr: 178.170.XX.XXX:7001
fleet:
public-ip: 178.170.XX.XXX
删除文件 /etc/machine-id 然后重新启动该实例重新生成一个新的机器 id (你 3 实例都必须具有一个不同的 id ) :
core@CoreOSnode-1 ~ $ sudo rm -f /etc/machine-id
core@CoreOSnode-1 ~ $ sudo reboot
你的第一个实例应该出现在列表中管理机在 Fleet :
core@CoreOSnode-1 ~ $ fleetctl list-machines
MACHINE IP METADATA
7e685988... 178.170.XX.XXX -
在这里我们可以清楚地看到我们的审判在列表中的机器 Fleet这将是我们将初始化的实例我们 cluster CoreOS/Etcd/Fleet.
配置现在你其他的两个实例 CoreOS remote deployment target 通过下面的说明 :
连接到您的其他两个实例，然后将复制该文件的内容 /usr/share/oem/cloud-config.yml 您的试用版，只需更换 ip 它由你在你第二个实例 ip 和你第三个实例在你第三个实例上的 ip 的第二个实例 (你必须通过通过根 "sudo su ") :
在我们第二个实例上 (ip 地址 178.170.XX。YYY ) 文件 /usr/share/oem/cloud-config.yml 因此将以下内容 (相同，只是 ip 地址 ) :
core@CoreOSnode-2 ~ $ cat /usr/share/oem/cloud-config.yml
#cloud-config
<!--T:44-->
coreos:
units:
- name: cloudstack-ssh-key.service
command: restart
runtime: yes
content: |
[Unit]
Description=Sets SSH key from metadata
<!--T:45-->
[Service]
Type=oneshot
StandardOutput=journal+console
ExecStart=/usr/share/oem/bin/cloudstack-ssh-key
- name: cloudstack-hostname.service
command: restart
runtime: yes
content: |
[Unit]
Description=Sets hostname from metadata
<!--T:46-->
[Service]
Type=oneshot
StandardOutput=journal+console
ExecStart=/usr/share/oem/bin/cloudstack-hostname
- name: cloudstack-cloudinit.service
command: restart
runtime: yes
content: |
[Unit]
Description=Cloudinit from CloudStack-style metadata
Requires=coreos-setup-environment.service
After=coreos-setup-environment.service
<!--T:47-->
[Service]
Type=oneshot
EnvironmentFile=/etc/environment
ExecStart=/usr/share/oem/bin/cloudstack-coreos-cloudinit
- name: etcd.service
command: start
- name: fleet.service
command: start
oem:
id: cloudstack
name: CloudStack
version-id: 0.0.1-r3
home-url: http://cloudstack.apache.org/
bug-report-url: https://github.com/coreos/coreos-overlay
etcd:
discovery: https://discovery.etcd.io/b8069c9bd67eae5cf19689daf4ebdd66
addr: 178.170.XX.YYY:4001
peer-addr: 178.170.XX.YYY:7001
fleet:
public-ip: 178.170.XX.YYY
在我们第三个实例上 (ip 地址 178.170.XX。ZZZ ) 文件 /usr/share/oem/cloud-config.yml 因此将以下内容 (与相同 2 其他人除了 ip 地址 ) :
core@CoreOSnode-3 ~ $ cat /usr/share/oem/cloud-config.yml
#cloud-config
<!--T:50-->
coreos:
units:
- name: cloudstack-ssh-key.service
command: restart
runtime: yes
content: |
[Unit]
Description=Sets SSH key from metadata
<!--T:51-->
[Service]
Type=oneshot
StandardOutput=journal+console
ExecStart=/usr/share/oem/bin/cloudstack-ssh-key
- name: cloudstack-hostname.service
command: restart
runtime: yes
content: |
[Unit]
Description=Sets hostname from metadata
<!--T:52-->
[Service]
Type=oneshot
StandardOutput=journal+console
ExecStart=/usr/share/oem/bin/cloudstack-hostname
- name: cloudstack-cloudinit.service
command: restart
runtime: yes
content: |
[Unit]
Description=Cloudinit from CloudStack-style metadata
Requires=coreos-setup-environment.service
After=coreos-setup-environment.service
<!--T:53-->
[Service]
Type=oneshot
EnvironmentFile=/etc/environment
ExecStart=/usr/share/oem/bin/cloudstack-coreos-cloudinit
- name: etcd.service
command: start
- name: fleet.service
command: start
oem:
id: cloudstack
name: CloudStack
version-id: 0.0.1-r3
home-url: http://cloudstack.apache.org/
bug-report-url: https://github.com/coreos/coreos-overlay
etcd:
discovery: https://discovery.etcd.io/b8069c9bd67eae5cf19689daf4ebdd66
addr: 178.170.XX.ZZZ:4001
peer-addr: 178.170.XX.ZZZ:7001
fleet:
public-ip: 178.170.XX.ZZZ
至于你的第一个实例，删除文件 /etc/machine-id 并重新启动该实例 :
core@CoreOSnode-2 ~ $ sudo rm -f /etc/machine-id
core@CoreOSnode-2 ~ $ sudo reboot
core@CoreOSnode-3 ~ $ sudo rm -f /etc/machine-id
core@CoreOSnode-3 ~ $ sudo reboot
重新启动后，你 2 其他机构通常加入你 cluster CoreOS/Etcd/Fleet :
core@CoreOSnode-1 ~ $ fleetctl list-machines
MACHINE IP METADATA
6eacee19... 178.170.XX.XXX -
7e685988... 178.170.XX.YYY -
87e15a4a... 178.170.XX.ZZZ -
如果您的实例尚未加入 cluster请确保您的实例可能愉快的交流，彼此 (连接网络、 防火墙规则 /安全组 )
现在，我们有 cluster CoreOS/etcd/fleet de 3 情况下，我们将安装 panamax-remote-agent 以及 panamax-adapter :
它运行代理巴拿马安装脚本 :
core@CoreOSnode-1 ~ $ sudo bash -c "$(curl http://download.panamax.io/agent/pmx-agent-install)"
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 685 100 685 0 0 1756 0 --:--:-- --:--:-- --:--:-- 3156
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 8613 100 8613 0 0 27496 0 --:--:-- --:--:-- --:--:-- 27694
./
./pmx-agent
./README.md
./CHANGELOG.md
./openssl.cnf
./.version
Execute cd /root/pmx-agent && ./pmx-agent to invoke agent setup script.
然后
core@CoreOSnode-1 ~ $ sudo bash -c "$(curl http://download.panamax.io/agent/pmx-agent-install)"
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 685 100 685 0 0 1756 0 --:--:-- --:--:-- --:--:-- 3156
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 8613 100 8613 0 0 27496 0 --:--:-- --:--:-- --:--:-- 27694
./
./pmx-agent
./README.md
./CHANGELOG.md
./openssl.cnf
./.version
Execute cd /root/pmx-agent && ./pmx-agent to invoke agent setup script.
core@CoreOSnode-1 ~ $ sudo su
CoreOSnode-1 core # cd /root/pmx-agent
<!--T:65-->
███████╗ ██████╗ █████████╗ ██████╗ ██████████╗ ██████╗ ██╗ ██╗
██╔══██║ ╚═══██╗ ███╗ ███║ ╚═══██╗ ██║ ██╔ ██║ ╚═══██╗ ╚██╗██╔╝
██ ██║ ███████║ ███║ ███║ ███████║ ██║╚██║ ██║ ███████║ ╚███╔╝
███████╝ ███████║ ███║ ███║ ███████║ ██║╚██║ ██║ ███████║ ██╔██╗
██║ ███████║ ███║ ███║ ███████║ ██║╚██║ ██║ ███████║ ██╔╝ ██╗
╚═╝ ╚══════╝ ╚══╝ ╚══╝ ╚══════╝ ╚═╝ ╚═╝ ╚═╝ ╚══════╝ ╚═╝ ╚═╝
<!--T:66-->
<span class="notranslate">CenturyLink Labs</span> - http://www.centurylinklabs.com/
<!--T:67-->
1) init: First time installing Panamax Remote Agent! - Downloads and installs Panamax Remote Agent.
2) restart: Stops and Starts Panamax Remote Agent and Adapter.
3) reinstall: Deletes your current Panamax Remote Agent and Adapter and reinstalls latest version.
4) check: Checks for available updates for Panamax Remote Agent and Adapter.
5) update: Updates to latest Panamax Remote Agent and Adapter.
6) delete: Uninstalls Panamax Remote Agent and Adapter.
7) debug: Display your current Panamax settings.
8) token: Display your current Panamax Remote Agent token.
9) help: Show this help
10) quit
Please select one of the preceding options:
类型 1 若要安装 Panamax Remote Agent :
Please select one of the preceding options: 1
<!--T:70-->
Installing panamax remote agent/adapter...
<!--T:71-->
Installing Panamax adapter:
<!--T:72-->
Select the ochestrator you want to use:
<!--T:73-->
1) Kubernetes
2) CoreOS Fleet
3) Marathon
Please select one of the preceding options:
选择是主谋 "2) CoreOS Fleet" 并指定您的 ip :
Please select one of the preceding options: 2
<!--T:76-->
Enter the API endpoint to access the Fleet <span class="notranslate">cluster</span> (e.g: http://10.187.241.100:4001): http://178.170.XX.XXX:4001
<!--T:77-->
Starting Panamax Fleet adapter:
<!--T:78-->
docker pull centurylink/panamax-fleet-adapter:latest
<!--T:79-->
56b22791d9b3dac06e2348a6a867527ffae01a37ab374159be48bbafaf77334f
<!--T:80-->
Installing Panamax remote agent:
Enter the public hostname (dev.example.com, without 'http') or IP Address (ex: 206.x.x.x) of the agent: Enter the public hostname (dev.example.com, without 'http') or IP Address (ex: 206.x.x.x) of the agent: 178.170.XX.XXX
Enter the port to run the agent on (3001):
<!--T:81-->
Generating SSL Key
<!--T:82-->
docker pull centurylink/openssl:latest
<!--T:83-->
Generating RSA private key, 1024 bit long modulus
......++++++
..............................................................................++++++
e is 65537 (0x10001)
Generating a 4096 bit RSA private key
........................................................................................++
................................................................++
writing new private key to '/certs/pmx_remote_agent.key'
-----
No value provided for Subject Attribute C, skipped
No value provided for Subject Attribute ST, skipped
No value provided for Subject Attribute L, skipped
No value provided for Subject Attribute O, skipped
Signature ok
subject=/CN=178.170.XX.XXX
Getting Private key
<!--T:84-->
Starting Panamax remote agent:
<!--T:85-->
docker pull centurylink/panamax-remote-agent:latest
<!--T:86-->
524bc3b7db813d2f20f8dc028037ce8f42ecfc05ebe8c4f67a172e3f6125dc44
============================== START ============================== <!--T:87-->
aHR0cHM6Ly8xNzguMTcwLjY4LjE1NzozMDAxfDdiYzExYjNiLTMxZDEtNGM1NS1hZWNlLWFmNTRk
NGQ1NzkzNHxOVGs1TUdNMk5tVXRNV0UzWlMwME1EUmhMVGc1T0RNdFpqZGhZVEJqWTJVM1ptSm1D
Zz09fC0tLS0tQkVHSU4gQ0VSVElGSUNBVEUtLS0tLQpNSUlGRmpDQ0F2NmdBd0lCQWdJSkFKb003
cDJiRTd6aU1BMEdDU3FHU0liM0RRRUJCUVVBTUJreEZ6QVZCZ05WCkJBTU1EakUzT0M0eE56QXVO
amd1TVRVM01CNFhEVEUxTURZeE5qRTBOVGt6TjFvWERURTJNRFl4TlRFME5Ua3oKTjFvd0dURVhN
QlVHQTFVRUF3d09NVGM0TGpFM01DNDJPQzR4TlRjd2dnSWlNQTBHQ1NxR1NJYjNEUUVCQVFVQQpB
NElDRHdBd2dnSUtBb0lDQVFDZHFmOFVZM21RWnJpUTdLSTVJV0RuNkJuS3lIclkxTitZeE1OaVlj
WnRKSm5yCmt3UlhDQzRVelNDNEdrMmszcFIzeHppd0piN1VUYmRwMXUrQlhnYjgvVHV3dDhENUxp
MVovUzRudmVoUlA4N0YKa0trcENpeU8zUllyQXc0QkFqZVkvb2Jsem5nN2Y0T2dXYWhaamhnV201
SUJ0dWdndXVCTEVUcHNIcERXZWJpSQpOT0I3V2ZEQkh0RmRydkpLMEU2dEJzNjdVVkg0ZHdLNVcx
c0dNdjRsQTY4TGczdmFlWVpobHk0NGFpeGlPWUIzClV6TlUzN3h3eXFFbnVnU2MvM2x3VzhVRVdU
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
cDBvTHdpOXVtS0VWeFQ5VjYrL1JsL3VoRHBlV09Nc3FOaVkyanBRVkhpZ1lWVVpKYlJhZ2xIbk42
NDBXZApRZUZBTnMvT29aQTFrdDN1cFR5MmtlVWljLzMzTzlidTArU0hFUEZpd2Fqa3dkUURudXl4
dGVRNnBJVEhhVDdSCmVoWEdDdDRmVXBSUjZsT2xGWjRTS2JjQmtBa3dZa2V5Y0N5VTltTkV3Yk1R
M0xJZmY5K0pSa3hqTXQ1YnRzTHgKWDk2d08zWURBYkc2NmxmQkh1TTJLNWZVck1yWDlUbmpmN0x5
Z0hjcnJWWmFiK2JjUkM2SzZVQnI1RTl4R2xKNgpGZHZMdkUySW5uQjkrRzIrM2V1OXh6UXVFWGpB
K2ZzUDJReDRJU2w3NGpYaTRWa3Ziem41TnhUVHJsRzNaYk9WCkp3NTRmV21lOHRwQ2N4Vit2V2JW
M0tCZ2JpMXRlKzRKTFZuV1VKTlpVUng5K2VUTG82UTd2Tm1iSG1RTS8wOHIKVWZIR1JSOGlPZGwr
NjlDZjNlUWwvenhCSVE2cXN4bGxzWTJMd3IvMGFFaURuUDRtNk5WUEtuSmN4VDNNbTRuZwp4TjdR
OXh6V08rWUdhdUVhaHNMUkF2QXhleFVPZkkrUHlmT0lYVFova1hJWjA1VWxVU3RoYUJ3bzFXRlVI
VnFWCjhxU1pjdEU0UGRneExSejNXclltZTdVWTJEbWJuUkJOVHlFOW0yeFJPVEh6RUlQWTdDVXZ3
MDh0ZFpHczNkbG8KbVdPSVcwMGk1MEROa1ArT1RyWm5OcHU3VVRjL3ZPQ3hSaGJyM1o4OTNyWXA3
SUlKT0VQWUFjT1pzMHRkQWNvQwowSldRRTZzUnFRT1dCQT09Ci0tLS0tRU5EIENFUlRJRklDQVRF
LS0tLS0K
============================== 结束 ==============================
<!--T:88-->
Copy and paste the above (Not including start/end tags) to your local panamax client to connect to this remote agent.
<!--T:89-->
Remote Agent/Adapter installation complete!
<!--T:90-->
CoreOSnode-1 pmx-agent #
如在安装的结尾，您需要复制-粘贴 (没有这些标记开始行 /END) 你远程代理巴拿马巴拿马 UI 创建期间中的私有密钥你 Panamax Remote Deployment Target.
添加你 Panamax Remote Deployment Target 对你的 UI 巴拿马
若要添加您 Panamax Remote Deployment Target 在你的 UI 巴拿马，连接到它通过您的浏览器 :
- 走在 "MANAGE"
- 目前无论哪个模板的名称，单击 (ex: "与 MySQL WordPress ")
文件:Panamax-ui-search-tmplt.png
- 单击按钮 "Run Template"
- 单击 "Deploy to Target" :
文件:Panamax-ui-deploytotarget.png
- 单击 "Add a New Remote Deployment Target"
文件:Panamax-ui-remotedeploymenttarget.png
- 单击 "Enter your token here." (底部右页 )
- 输入的 ip 地址，您 Panamax Remote Agent (那您在其安装过程中设置的字段 "Name") 然后复制-粘贴在安装结束时返回的关键私人代理 Panamax Remote Agent (无标记线 START/END).
- 单击 "Save Remote Deployment Target"
你应该有以下输出 :
文件:Panamax-ui-remotedeploytarget-added.png
- 单击绿色箭头左边的名称你 Remote Deployment Target 然后强制第一更新 :
文件:Panamax-ui-remotedeploymenttarget-update.png
更新，资料后你 Remote Deployment Targets 如的版本你 Panamax Remote Agent的类型你 Panamax Adapter 和它的版本 :
文件:Panamax-ui-remotedeploymenttarget-informations.png
部署应用程序通过巴拿马 UI
它现在是可能部署的应用程序在市场上可用 "Panamax Templates & Docker Repositories" 自 Panamax UI 上你 Panamax Remote Deployment Target :
- 找到您要部署的应用程序的名称。我们选择的模板 Century Link "Wordpress with MySQL"
- 你可以点击 "更多详细信息 " 您选择的模板的详细信息。您还可以看到多少图像 (s) 码头工人模板包含 (在我们的案例 2 图像 )
文件:Panamax-ui-template-details.png
- 单击 "Run Template" pour déployer le menu et cliquez sur "Deploy to Target" :
文件:Panamax-ui-deploytotarget-wordpress.png
- 单击 "Select this Target" 若要选择你 Remote Deployment Target
文件:Panamax-ui-select-target.png
- 填写的任何字段 "Deployment Settings" 部署应用程序你 (密码、 环境变量等�) 然后点击按钮 "Deploy to Target" 下面来验证
文件:Panamax-ui-deployment-settings.png
- 你应该有以下输出 :
文件:Panamax-ui-deployment-triggered.png
如果您连接到您的实例从你 cluster CoreOS，您将看到巴拿马已分配在不同节点上的码头集装箱 /实例的你 cluster CoreOS :
- 我们可以看到，图像 centurylink/wordpress 已部署在我们审判的 CoreOS :
core@CoreOSnode-1 ~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PO RTS NAMES
3206bda4e534 centurylink/wordpress:3.9.1 "/run.sh" 3 minutes ago Up 3 minutes 0. 0.0.0:8080->80/tcp wp
84e3c5fe1886 centurylink/panamax-remote-agent:latest "/panamax-remote-age 37 minutes ago Up 37 minutes 0. 0.0.0:3001->3000/tcp pmx_agent
71009f7785d3 centurylink/panamax-fleet-adapter:latest "rackup '-E producti 37 minutes ago Up 37 minutes 92 92/tcp pmx_adapter
- 图像 centurylink/mysql 在我们第三个实例上我们 cluster :
core@CoreOSnode-3 ~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
84deeadd66fa centurylink/mysql:5.5 "/usr/local/bin/run" 4 minutes ago Up 4 minutes 0.0.0.0:3306->3306/tcp db
- 我们也有一些关于通过巴拿马 UI 的应用程序部署的信息，通过我们的经理 cluster Etcd :
我们发现我们 2 应用程序 (Wordpress "WP" et MySQL "DB") :
core@CoreOSnode-1 ~ $ etcdctl ls --recursive /app
/app/DB
/app/DB/DB_SERVICE_HOST
/app/WP
/app/WP/WP_SERVICE_HOST
您还可以查看哪些成员实例上我们 cluster 应用程序的部署 :
core@CoreOSnode-1 ~ $ etcdctl get /app/DB/DB_SERVICE_HOST
178.170.XX.XXX
core@CoreOSnode-1 ~ $ etcdctl get /app/WP/WP_SERVICE_HOST
178.170.XX.ZZZ
- 我们也有我们的群集应用程序的状态 Fleet 哪些应用程序管理器在我们 cluster :
core@CoreOSnode-1 ~ $ fleetctl list-unit-files
UNIT HASH DSTATE STATE TARGET
db.service 0caad43 launched launched 6eacee19.../178.170.XX.XXX
wp.service 417826f launched launched 7e685988.../178.170.XX.ZZZ
- 我们可以检查正常的我们 Wordpress 通过使用模板的详细信息中提供的信息访问 (在我们的案例在端口上 8080 以前打开防火墙一级，我们能做的端口转发 8080 在端口上 80 公共团体期待 ) :
文件:Panamax-application-wordpress.png
这篇文章似乎你要有用 ?
开启评论自动刷新