Vizualizare sursă pentru „Utilizarea Cloudstack de Ikoula Panamax”

<br />

Acest articol este rezultatul unei traduceri automate efectuate de către software-ul. Puteți vizualiza sursa articol [[:fr:Utiliser Panamax sur Cloudstack by Ikoula|aici]].<br /><span data-translate="fr"></span>












<!--T:1-->
Dacă nu ştiţi încă  [http://panamax.io/ Panamax] Este un produs  <span class="notranslate">Open Source</span> dezvoltat de  <span class="notranslate">Century Link Labs</span> care este atât un loc de piaţă   şi un Manager pentru aplicaţii containerizată Docker de o interfaţă intuitivă web.


<!--T:2-->
Este sufAici ent să caute aplicarea nostru de alegere, apoi de o clică să implementaţi pe noastre obiective de organisme folosind docker și unul Panamax.


<!--T:3-->
Panamax se bazează pe tehnologii Docker, DCE,  <span class="notranslate">Fleet</span> şi nor-init incluse în CoreOS.


<!--T:4-->
În ex emplul nostru vom folosi  4 cazuri CoreOS  [https://ikoula.wiki/help/Mettre_a_jour_CoreOS_manuellement Actualizare], unul pentru partea clientului /Panamax UI  şi  3 alţii care vor forma  <span class="notranslate">cluster</span> pentru partea  <span class="notranslate">Panamax Remote Target (Panamax Remote Agent + Panamax Adapter)</span> :



==Instalarea de Panamax UI /API  (interfaţă web /locul de piaţă )== <!--T:5-->


<!--T:6-->
Pe forumul nostru dedicat de partea clientului de Panamax  (Panamax UI/API), descărcarea Arhiva ce contine Installer  :


<!--T:7-->
<syntaxhighlight lang="bash">
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
</syntaxhighlight>


<!--T:8-->
Acesta creează directorul  /var/panamax în cazul în care aţi extras fişierele instalarea  :


<!--T:9-->
<syntaxhighlight lang="bash">
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
</syntaxhighlight>


<!--T:10-->
Acesta este plasat în directorul  /var/panamax şi vom lansa programul de instalare CoreOS specifice specificând că doriţi să utilizaţi versiunea stabilă  (ieşire trunchiate voluntar ) :


<!--T:11-->
<syntaxhighlight lang="bash">
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 $
</syntaxhighlight>


<!--T:13-->
Putem verifica că nostru  5 containere Panamax se execută  :


<!--T:14-->
<syntaxhighlight lang="bash">
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
</syntaxhighlight>


<!--T:15-->
Ne putem conecta la noastre UI Panamax folosind browser-ul nostru în atingerea ip nostru instanţă urmată de  ":3000" pentru a specifica portul de ascultare  (nu uitaţi să creeze permisiunile regulile firewall-ului şi dacă necesar portul redirecţionare ) acestora  :


<!--T:16-->
[[File:panamax-ui.png]]



==Instalarea  <span class="notranslate">Panamax Remote Deployment Target</span>== <!--T:17-->


<!--T:18-->
Conecta la unul dintre dumneavoastră  3 cazuri CoreOS implementat pentru  <span class="notranslate">cluster</span> :


<!--T:19-->
Genera un URL-ul nou de  <span class="notranslate">discovery Etcd</span> (token-uri ) într-o variabilă  (ici: ETCD_URL ) :


<!--T:20-->
<syntaxhighlight lang="bash">
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
</syntaxhighlight>


<!--T:21-->
Apoi, descărcaţi următorul nor - config.yml şablon fişier  :


<!--T:22-->
<syntaxhighlight lang="bash">
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]
</syntaxhighlight>

<!--T:26-->
<syntaxhighlight lang="bash">
core@CoreOSnode-1 ~ $ export `cat /etc/environment`
</syntaxhighlight>

<!--T:27-->
Executaţi următoarele comenzi pentru a personaliza nor fişier - config.yml descarcat cu valorile tale mediului  :

<!--T:28-->
<syntaxhighlight lang="bash">
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
</syntaxhighlight>

<!--T:29-->
Vom verifica noastre DCE setările şi  <span class="notranslate">Fleet</span> este bine de înlocuit  :

<!--T:30-->
<syntaxhighlight lang="bash">
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
</syntaxhighlight>


<!--T:35-->
Ştergeţi fişierul  /etc/machine-id apoi reboot-ați instanţă pentru a regenera un id nou maşină  (dumneavoastră  3 instanţele trebuie să aibă un id diferit ) :


<!--T:36-->
<syntaxhighlight lang="bash">
core@CoreOSnode-1 ~ $ sudo rm -f /etc/machine-id
core@CoreOSnode-1 ~ $ sudo reboot
</syntaxhighlight>


<!--T:37-->
Al tău primul rând ar trebui să apară în lista de gestionat de maşini în  <span class="notranslate">Fleet</span> :


<!--T:38-->
<syntaxhighlight lang="bash">
core@CoreOSnode-1 ~ $ fleetctl list-machines
MACHINE         IP              METADATA
7e685988...     178.170.XX.XXX  -
</syntaxhighlight>


<!--T:39-->
Aici putem vedea în mod clar noastre proces în lista de maşini  <span class="notranslate">Fleet</span>, acest lucru va fi noastre instanţă care va iniţializa nostru  <span class="notranslate">cluster</span> CoreOS/Etcd/Fleet.


<!--T:40-->
Configurați acum alte dumneavoastră de două instanţe  <span class="notranslate">CoreOS remote deployment target</span> urmând instrucţiunile de mai jos  :


<!--T:41-->
Conecta la dumneavoastră alte două cazuri şi apoi copiaţi conţinutul de dosar  /usr/share/oem/cloud-config.yml proces dumneavoastră prin înlocuirea doar ip de dumneavoastră a doua instanţă pe ip-ul a doua instanţă şi ip ta treia instanţă dumneavoastră treia instanțe  (va trebui să treci rădăcină prin intermediul unui  "sudo su ") :


<!--T:42-->
Pe noastre a doua instanţă  (adresa IP  178.170. XX. YYY ) fişier  /usr/share/oem/cloud-config.yml va, prin urmare, urmatorul continut  (identice, cu excepţia adresa ip ) :


<!--T:43-->
<syntaxhighlight lang="bash">
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
</syntaxhighlight>


<!--T:48-->
Pe noastre treia instanţă  (adresa IP  178.170. XX. ZZZ ) fişier  /usr/share/oem/cloud-config.yml va, prin urmare, urmatorul continut  (identic  2 alţii, cu excepţia adresa ip ) :


<!--T:49-->
<syntaxhighlight lang="bash">
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
</syntaxhighlight>


<!--T:54-->
Pentru al tău primul rând, ştergeţi fişierul  /etc/machine-id şi reporniţi instanţă  :


<!--T:55-->
<syntaxhighlight lang="bash">
core@CoreOSnode-2 ~ $ sudo rm -f /etc/machine-id
core@CoreOSnode-2 ~ $ sudo reboot
</syntaxhighlight>


<!--T:56-->
<syntaxhighlight lang="bash">
core@CoreOSnode-3 ~ $ sudo rm -f /etc/machine-id
core@CoreOSnode-3 ~ $ sudo reboot
</syntaxhighlight>


<!--T:57-->
O dată repornit, dumneavoastră  2 alte organisme în mod normal, s-au alăturat vă  <span class="notranslate">cluster</span> CoreOS/Etcd/Fleet :


<!--T:58-->
<syntaxhighlight lang="bash">
core@CoreOSnode-1 ~ $ fleetctl list-machines
MACHINE         IP              METADATA
6eacee19...     178.170.XX.XXX  -
7e685988...     178.170.XX.YYY  -
87e15a4a...     178.170.XX.ZZZ  -
</syntaxhighlight>


<!--T:59-->
În cazul în care dumneavoastră instanţe nu s-au alăturat  <span class="notranslate">cluster</span>, asiguraţi-vă că vă instanţe pot comunica bine cu fiecare alte  (reţelele de conexiuni, reguli firewall /Grupul de securitate )


<!--T:60-->
Acum, că avem o  <span class="notranslate">cluster</span> CoreOS/etcd/fleet de 3 cazuri, vom instala  <span class="notranslate">panamax-remote-agent</span> precum şi  <span class="notranslate">panamax-adapter</span> :


<!--T:61-->
Se ruleaza agentul script de instalare Panamax  :


<!--T:62-->
<syntaxhighlight lang="bash">
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.
</syntaxhighlight>


<!--T:63-->
Apoi 


<!--T:64-->
<syntaxhighlight lang="bash">
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:
</syntaxhighlight>


<!--T:68-->
Tipul  1 pentru a instala  <span class="notranslate">Panamax Remote Agent</span> :


<!--T:69-->
<syntaxhighlight lang="bash">
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:
</syntaxhighlight>


<!--T:74-->
Alege Orchestrator  "2) <span class="notranslate">CoreOS Fleet"</span> şi specificaţi ip-ul  :


<!--T:75-->
<syntaxhighlight lang="bash">
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
============================== SFÂRŞITUL  ==============================


<!--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 #
</syntaxhighlight>


<!--T:91-->
Conform indicațiilor de la sfârşitul de instalare, aveţi nevoie pentru a copia - pastă  (fără aceste Tag-uri START rânduri /END) cheia privată a ta panamax agent de la distanţă în Panamax UI în timpul crearea de dumneavoastră  <span class="notranslate">Panamax Remote Deployment Target</span>.


==Adauga dumneavoastră  <span class="notranslate">Panamax Remote Deployment Target</span> pentru a vă Panamax UI == <!--T:92-->


<!--T:93-->
Pentru a adăuga dumneavoastră  <span class="notranslate">Panamax Remote Deployment Target</span> în dumneavoastră Panamax UI, conecta la acesta prin intermediul browser-ul dumneavoastră  :


<!--T:94-->
- Du-te în  <span class="notranslate">"MANAGE"</span>


<!--T:95-->
[[File:Panamax-ui-manage.png]]


<!--T:96-->
- Faceţi clic pe numele unui şablon indiferent care pentru moment  (ex: "WordPress cu MySQL ")


<!--T:97-->
[[File:Panamax-ui-search-tmplt.png]]


<!--T:98-->
- Faceţi clic pe butonul  <span class="notranslate">"Run Template" </span>


<!--T:99-->
[[File:Panamax-ui-fleche.png]]


<!--T:100-->
- Faceţi clic pe  <span class="notranslate">"Deploy to Target"</span> :


<!--T:101-->
[[File:Panamax-ui-deploytotarget.png]]


<!--T:102-->
- Faceţi clic pe  <span class="notranslate">"Add a New Remote Deployment Target"</span>


<!--T:103-->
[[File:Panamax-ui-remotedeploymenttarget.png]]


<!--T:104-->
- Faceţi clic pe  <span class="notranslate">"Enter your token here."</span> (partea de jos dreapta paginii )


<!--T:105-->
[[File:Panamax-ui-entertokens.png]]


<!--T:106-->
- Introduceţi adresa ip a dvs  <span class="notranslate">Panamax Remote Agent </span>(setat în timpul instalării sale în domeniile  <span class="notranslate">"Name"</span>) apoi copiaţi - lipiţi agentul cheie privată s-a întors la sfârşitul instalării  <span class="notranslate">Panamax Remote Agent</span> (fără linii de Tag-uri  <span class="notranslate">START/END</span>).


<!--T:107-->
[[File:Panamax-ui-tokens.png]]


<!--T:108-->
- Faceţi clic pe  <span class="notranslate">"Save Remote Deployment Target"</span>


<!--T:109-->
Trebuie să aveţi următoarele ieşire  :


<!--T:110-->
[[File:Panamax-ui-remotedeploytarget-added.png]]


<!--T:111-->
- Faceţi clic pe săgeata verde din stânga numelui tău <span class="notranslate"> Remote Deployment Target</span> apoi vigoare o prima actualizare  :


<!--T:112-->
[[File:Panamax-ui-remotedeploymenttarget-update.png]]


<!--T:113-->
După actualizare, informaţii despre dumneavoastră  <span class="notranslate">Remote Deployment Targets</span> cum ar fi versiunea dvs  <span class="notranslate">Panamax Remote Agent</span>, tipul de dumneavoastră  <span class="notranslate">Panamax Adapter</span> şi versiunea  :


<!--T:114-->
[[File:Panamax-ui-remotedeploymenttarget-informations.png]]

==Implementarea o cerere prin intermediul Panamax UI == <!--T:115-->


<!--T:116-->
Acum este posibil pentru a implementa o aplicaţie disponibile în piaţă  <span class="notranslate">"Panamax Templates & Docker Repositories"</span> Deoarece vă Panamax UI pe dumneavoastră  <span class="notranslate">Panamax Remote Deployment Target</span> :


<!--T:117-->
- Localiza numele aplicaţiei pe care doriţi să implementaţi. Vom alege şablonul  <span class="notranslate">Century Link "Wordpress with  MySQL"</span>


<!--T:118-->
- Faceţi clic pe  "Mai multe detalii " Pentru mai multe informaţii despre şablonul pe care le-aţi selectat. De asemenea, puteţi vedea cât de mult imagine (s) Docker şablon constă  (în cazul nostru  2 imagini )


<!--T:119-->
[[File:Panamax-ui-template-details.png]]


<!--T:120-->
- Faceţi clic pe  <span class="notranslate">"Run Template" pour déployer le menu et cliquez sur "Deploy to Target"</span> :


<!--T:121-->
[[File:Panamax-ui-deploytotarget-wordpress.png]]


<!--T:122-->
- Faceţi clic pe  <span class="notranslate">"Select this Target"</span> pentru a selecta ţi  <span class="notranslate">Remote Deployment Target</span>


<!--T:123-->
[[File:Panamax-ui-select-target.png]]


<!--T:124-->
- Completaţi toate câmpurile de  <span class="notranslate">"Deployment Settings"</span> aplicaţie care vă desfăşurate  (parola, variabile de mediu, etc.)  apoi faceţi clic pe butonul  <span class="notranslate">"Deploy to Target"</span>  mai jos pentru a valida 


<!--T:125-->
[[File:Panamax-ui-deployment-settings.png]]


<!--T:126-->
- Trebuie să aveţi următoarele ieşire  :


<!--T:127-->
[[File:Panamax-ui-deployment-triggered.png]]


<!--T:128-->
Dacă vă conectaţi la instanţe dumneavoastră la dumneavoastră  <span class="notranslate">cluster</span> CoreOS, veţi vedea că Panamax a alocat containere Docker pe diferite noduri /cazuri de dumneavoastră  <span class="notranslate">cluster</span> CoreOS :


<!--T:129-->
- Putem vedea că imaginea  <span class="notranslate">centurylink/wordpress</span> a fost dislocat pe noastre CoreOS proces  :


<!--T:130-->
<syntaxhighlight lang="bash">
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
</syntaxhighlight>


<!--T:131-->
- Şi imaginea  <span class="notranslate">centurylink/mysql</span> pe noastre treia instanţă de nostru  <span class="notranslate">cluster</span> :


<!--T:132-->
<syntaxhighlight lang="bash">
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
</syntaxhighlight>


<!--T:133-->
- Avem, de asemenea, unele informaţii pe implementările de aplicaţii prin intermediul Panamax UI prin managerul de  <span class="notranslate">cluster</span> Etcd :


<!--T:134-->
Gasim noastre  2 aplicatii <span class="notranslate"> (Wordpress "WP" et MySQL "DB")</span> :


<!--T:135-->
<syntaxhighlight lang="bash">
core@CoreOSnode-1 ~ $ etcdctl ls --recursive /app
/app/DB
/app/DB/DB_SERVICE_HOST
/app/WP
/app/WP/WP_SERVICE_HOST
</syntaxhighlight>


<!--T:136-->
De asemenea, puteţi vedea pe ce instanţă de membru al nostru  <span class="notranslate">cluster</span> cererea a fost dislocat  :


<!--T:137-->
<syntaxhighlight lang="bash">
core@CoreOSnode-1 ~ $ etcdctl get /app/DB/DB_SERVICE_HOST
178.170.XX.XXX
</syntaxhighlight>


<!--T:138-->
<syntaxhighlight lang="bash">
core@CoreOSnode-1 ~ $ etcdctl get /app/WP/WP_SERVICE_HOST
178.170.XX.ZZZ
</syntaxhighlight>


<!--T:139-->
- Avem, de asemenea, statutul de aplicaţiile noastre cluster de  <span class="notranslate">Fleet</span> Cererile care Manager în nostru  <span class="notranslate">cluster</span> :


<!--T:140-->
<syntaxhighlight lang="bash">
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
</syntaxhighlight>


<!--T:141-->
- Putem verifica buna funcţionare a noastră  <span class="notranslate">Wordpress</span> accesând-o cu informaţiile furnizate în detaliile de şablon  (în cazul nostru pe portul  8080 deschis la nivel de firewall-ul anterior, am putea face un port înainte de  8080 portul  80 publice în cazul organismelor cu nerăbdare ) :


<!--T:142-->
[[File:Panamax-application-wordpress.png]]

<!--T:143-->
Acest articol părea să fie util ? <vote />


[[Category:cloudstack]]
[[Category:publice_nor]]
[[Category:privat_nor]]
<br />
<comments />