View source for Use Cloudstack by Ikoula Panamax

<span data-link_translate_en_title="Use Cloudstack by Ikoula Panamax"  data-link_translate_en_url="Use Cloudstack by Ikoula Panamax"></span>[[:en:Use Cloudstack by Ikoula Panamax]][[en:Use Cloudstack by Ikoula Panamax]]
<span data-link_translate_he_title="השתמש Cloudstack על ידי Ikoula פנמקס"  data-link_translate_he_url="%D7%94%D7%A9%D7%AA%D7%9E%D7%A9+Cloudstack+%D7%A2%D7%9C+%D7%99%D7%93%D7%99+Ikoula+%D7%A4%D7%A0%D7%9E%D7%A7%D7%A1"></span>[[:he:השתמש Cloudstack על ידי Ikoula פנמקס]][[he:השתמש Cloudstack על ידי Ikoula פנמקס]]
<span data-link_translate_ro_title="Utilizarea Cloudstack de Ikoula Panamax"  data-link_translate_ro_url="Utilizarea+Cloudstack+de+Ikoula+Panamax"></span>[[:ro:Utilizarea Cloudstack de Ikoula Panamax]][[ro:Utilizarea Cloudstack de Ikoula Panamax]]
<span data-link_translate_ru_title="Использование Cloudstack по Ikoula Panamax"  data-link_translate_ru_url="%D0%98%D1%81%D0%BF%D0%BE%D0%BB%D1%8C%D0%B7%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5+Cloudstack+%D0%BF%D0%BE+Ikoula+Panamax"></span>[[:ru:Использование Cloudstack по Ikoula Panamax]][[ru:Использование Cloudstack по Ikoula Panamax]]
<span data-link_translate_pl_title="Użyj Cloudstack przez Ikoula Panamax"  data-link_translate_pl_url="U%C5%BCyj+Cloudstack+przez+Ikoula+Panamax"></span>[[:pl:Użyj Cloudstack przez Ikoula Panamax]][[pl:Użyj Cloudstack przez Ikoula Panamax]]
<span data-link_translate_ja_title="Ikoula パナマックスで Cloudstack を使用します。"  data-link_translate_ja_url="Ikoula+%E3%83%91%E3%83%8A%E3%83%9E%E3%83%83%E3%82%AF%E3%82%B9%E3%81%A7+Cloudstack+%E3%82%92%E4%BD%BF%E7%94%A8%E3%81%97%E3%81%BE%E3%81%99%E3%80%82"></span>[[:ja:Ikoula パナマックスで Cloudstack を使用します。]][[ja:Ikoula パナマックスで Cloudstack を使用します。]]
<span data-link_translate_ar_title="استخدام كلودستاك ببنما عكلة"  data-link_translate_ar_url="%D8%A7%D8%B3%D8%AA%D8%AE%D8%AF%D8%A7%D9%85+%D9%83%D9%84%D9%88%D8%AF%D8%B3%D8%AA%D8%A7%D9%83+%D8%A8%D8%A8%D9%86%D9%85%D8%A7+%D8%B9%D9%83%D9%84%D8%A9"></span>[[:ar:استخدام كلودستاك ببنما عكلة]][[ar:استخدام كلودستاك ببنما عكلة]]
<span data-link_translate_zh_title="使用由 Ikoula 巴拿马 Cloudstack"  data-link_translate_zh_url="%E4%BD%BF%E7%94%A8%E7%94%B1+Ikoula+%E5%B7%B4%E6%8B%BF%E9%A9%AC+Cloudstack"></span>[[:zh:使用由 Ikoula 巴拿马 Cloudstack]][[zh:使用由 Ikoula 巴拿马 Cloudstack]]
<span data-link_translate_de_title="Verwenden von Cloudstack von Ikoula Panamax"  data-link_translate_de_url="Verwenden+von+Cloudstack+von+Ikoula+Panamax"></span>[[:de:Verwenden von Cloudstack von Ikoula Panamax]][[de:Verwenden von Cloudstack von Ikoula Panamax]]
<span data-link_translate_nl_title="Cloudstack door Ikoula Panamax gebruiken"  data-link_translate_nl_url="Cloudstack+door+Ikoula+Panamax+gebruiken"></span>[[:nl:Cloudstack door Ikoula Panamax gebruiken]][[nl:Cloudstack door Ikoula Panamax gebruiken]]
<span data-link_translate_it_title="Utilizzare Cloudstack da Ikoula Panamax"  data-link_translate_it_url="Utilizzare+Cloudstack+da+Ikoula+Panamax"></span>[[:it:Utilizzare Cloudstack da Ikoula Panamax]][[it:Utilizzare Cloudstack da Ikoula Panamax]]
<span data-link_translate_pt_title="Usar o Cloudstack por Ikoula Panamax"  data-link_translate_pt_url="Usar+o+Cloudstack+por+Ikoula+Panamax"></span>[[:pt:Usar o Cloudstack por Ikoula Panamax]][[pt:Usar o Cloudstack por Ikoula Panamax]]
<span data-link_translate_es_title="Uso de Cloudstack por Ikoula Panamax"  data-link_translate_es_url="Uso+de+Cloudstack+por+Ikoula+Panamax"></span>[[:es:Uso de Cloudstack por Ikoula Panamax]][[es:Uso de Cloudstack por Ikoula Panamax]]
<span data-link_translate_fr_title="Utiliser Panamax sur Cloudstack by Ikoula"  data-link_translate_fr_url="Utiliser_Panamax_sur_Cloudstack_by_Ikoula"></span>[[:fr:Utiliser Panamax sur Cloudstack by Ikoula]][[fr:Utiliser Panamax sur Cloudstack by Ikoula]]
<br />

{{#seo:
|title=Use Cloudstack by Ikoula Panamax
|title_mode=append
|keywords=these,are,your,keywords
|description=Use Cloudstack by Ikoula Panamax
|image=Uploaded_file.png
|image_alt=Wiki Logo
}}

This article has been created by an automatic translation software. You can view the article source [[:fr:Utiliser Panamax sur Cloudstack by Ikoula|here]].<br /><span data-translate="fr"></span>

<!--T:1-->
If you do not know yet [http://panamax.io/ Panamax] It is a product <span class="notranslate">Open Source</span> developed by <span class="notranslate">Century Link Labs</span> that is both a market plaThis    and a Manager for containerized applications  Docker from an intuitive web interfaThis .


<!--T:2-->
It suffiThis s to seek the application of our choiThis  then of a clique to deploy on our bodies targets using docker and one Panamax.


<!--T:3-->
Panamax relies on technologies Docker, DCE, <span class="notranslate">Fleet</span> and Cloud-init  included in CoreOS.


<!--T:4-->
We will use in our ex   ample 4 instanThis s CoreOS [https://ikoula.wiki/help/Mettre_a_jour_CoreOS_manuellement Update], one for the client part /Panamax UI  and 3 others which will form the <span class="notranslate">cluster</span> for the part <span class="notranslate">Panamax Remote Target (Panamax Remote Agent + Panamax Adapter)</span> :



==Installation of Panamax UI  /API  (web interfaThis  /market plaThis  )== <!--T:5-->


<!--T:6-->
On our forum dedicated to the client part of Panamax (Panamax UI /API ), downloading archive containing Installer :


<!--T:7-->
<syntaxhighlight lang="bash">
core@CoreOS-PanamaxUI ~ $ sudo curl -O http://download.panamax.io/installer/panamax-latest   .tar.gz
  % Total    % ReThis ived % 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-->
It creates the directory /var/panamax where you ex   tracted the installation files :


<!--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
./LICENS E
./desktop
./panamax
./.coreosenv
./README.md
./CHANGELOG.md
./ubuntu.sh
./Vagrantfile
./.version
./coreos
./Vagrantfile-win
./CONTRIBUTING.md
</syntaxhighlight>


<!--T:10-->
It is plaThis d in the directory /var/panamax and we launch the CoreOS-specific installer by specifying that you want to use the stAB le version (output truncated voluntarily ) :


<!--T:11-->
<syntaxhighlight lang="bash">
core@CoreOS-PanamaxUI ~ $ cd /var/panamax
core@CoreOS-PanamaxUI /var/panamax $ sudo ./coreos install --stAB le
Installing Panamax...
Created symlink from /etc/systemd/system/Update -engine-reboot-manager.serviThis  to /dev/null.
Created symlink from /etc/systemd/system/Update -engine.serviThis  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 This nturylink   /panamax-api:latest   
.................
docker pull This nturylink   /panamax-ui:latest   
.....
docker pull google/cadvisor:0.13.0
.........
docker pull This nturylink   /redis:latest   
....
docker pull This nturylink   /dray:latest   
...Created symlink from /etc/systemd/system/multi-user.target.wants/panamax-redis.serviThis  to /etc/systemd/system/panamax-redis.serv
Created symlink from /etc/systemd/system/multi-user.target.wants/panamax-dray.serviThis  to /etc/systemd/system/panamax-dray.serviThis .
Created symlink from /etc/systemd/system/multi-user.target.wants/panamax-metrics.serviThis  to /etc/systemd/system/panamax-metrics.ser
Created symlink from /etc/systemd/system/multi-user.target.wants/panamax-api.serviThis  to /etc/systemd/system/panamax-api.serviThis .
Created symlink from /etc/systemd/system/multi-user.target.wants/panamax-ui.serviThis  to /etc/systemd/system/panamax-ui.serviThis .
...
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]: => NotiThis : server is listening on all interfaThis s (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-->
We can verify that our 5 containers Panamax are running :


<!--T:14-->
<syntaxhighlight lang="bash">
core@CoreOS-PanamaxUI /var/panamax $ docker ps
CONTAINER ID        IMAGE                            COMMAND                CREATED             STATUS              PORTS                     NAMES
41a18b410427        This nturylink/panamax-ui:latest       "/bin/sh -c 'bundle    3 minutes ago       Up 3 minutes        0.0.0.0:3000->3000/tcp   PMX_UI
0cc8be fee1b7        This nturylink/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        This nturylink/dray:0.10.0          "/dray"                3 minutes ago       Up 3 minutes        0.0.0.0:3003->3000/tcp   PMX_DRAY
8a6110651DC c        This nturylink/redis:latest            "redis-server"         3 minutes ago       Up 3 minutes        6379/tcp                 PMX_DRAY_REDIS
</syntaxhighlight>


<!--T:15-->
We can connect to our UI Panamax using our browser in tapping the ip of our instanThis  followed by ":3000" to specify the listening port (don't forget to create permissions firewall rules and if neThis ssary port redirection ) thereof :


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



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


<!--T:18-->
Connect to one of your 3 instanThis s CoreOS deployed for the <span class="notranslate">cluster</span> :


<!--T:19-->
Generate a new URL of <span class="notranslate">discovery Etcd</span> (token s ) in a variAB le (Here : ETCD_URL ) :


<!--T:20-->
<syntaxhighlight lang="bash">
core@CoreOSnode - 1 ~ $ ETCD_URL =$(curl http://discovery.etcd.io/new)
  % Total    % ReThis ived % 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-->
Then download the following cloud - config.yml template file :


<!--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. A$XX.XXX , 2a00:c70:1:80:93:XX:XXX:1
Connecting to mirror02.ikoula.com|80.93. A$XX.XXX |:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1542 (1.5K) [tex   t/plain]
Remote file is newer, retrieving.

<!--T:23-->
--2015-06-16 15:37:53--  http://mirror02.ikoula.com/priv/coreos/cloud-config.yml
Reusing ex   isting connection to mirror02.ikoula.com:80.
HTTP request sent, awaiting response... 200 OK
Length: 1542 (1.5K) [tex   t/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 ~ $ ex   port `cat /etc/environment`
</syntaxhighlight>

<!--T:27-->
Run the following commands to customize the file cloud - config.yml downloaded with your environmental values :

<!--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-->
We check  our DCE settings and <span class="notranslate">Fleet</span> is well substituted :

<!--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.serviThis 
        command: restart 
        runtime: yes
        content: |
          [Unit]
          Description=Sets SSH key from metadata

          <!--T:32-->
[ServiThis ]
          Type=oneshot
          StandardOutput=journal+console
          ExecStart=/usr/share/oem/bin/cloudstack-ssh-key
      - name: cloudstack-hostname.serviThis 
        command: restart 
        runtime: yes
        content: |
          [Unit]
          Description=Sets hostname from metadata

          <!--T:33-->
[ServiThis ]
          Type=oneshot
          StandardOutput=journal+console
          ExecStart=/usr/share/oem/bin/cloudstack-hostname
      - name: cloudstack-cloudinit .serviThis 
        command: restart 
        runtime: yes
        content: |
          [Unit]
          Description=Cloudinit  from CloudStack-style metadata
          Requires=coreos-setup-environment.serviThis 
          After=coreos-setup-environment.serviThis 

          <!--T:34-->
[ServiThis ]
          Type=oneshot
          EnvironmentFile=/etc/environment
          ExecStart=/usr/share/oem/bin/cloudstack-coreos-cloudinit 
      - name: etcd.serviThis 
        command: start
      - name: fleet.serviThis 
        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. A$XX.XXX :4001
      peer-addr: 178.170. A$XX.XXX :7001
    fleet:
      public-ip: 178.170. A$XX.XXX 
</syntaxhighlight>


<!--T:35-->
Delete the file /etc/machine-id then reboot the instanThis  in order to regenerate a new machine id (your 3 instanThis s must have a different id ) :


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


<!--T:37-->
Your first instanThis  should appear in the list of managed machines in <span class="notranslate">Fleet</span> :


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


<!--T:39-->
Here we can clearly see our trial in the list of machines <span class="notranslate">Fleet</span>, this will be  our instanThis  that will init ialize our <span class="notranslate">cluster</span> CoreOS/Etcd/Fleet.


<!--T:40-->
Configurez maintenant your deux autres instanThis s <span class="notranslate">CoreOS remote deployment target</span> by following the instructions be low :


<!--T:41-->
Connectez-vous à your deux autres instanThis s puis recopiez le contenu du fichier /usr/share/oem/cloud-config.yml de votre première instanThis  en remplaçant uniquement l'ip thereof par l'ip de votre seconde instanThis  sur votre seconde instanThis  et par l'ip de votre troisième instanThis  sur votre troisième instanThis  (you have to pass root via a "sudo su ") :


<!--T:42-->
On our second instanThis  (ip address 178.170. XX. YYY ) file /usr/share/oem/cloud-config.yml will therefore the following content (identical ex   This pt the ip address ) :


<!--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.serviThis 
        command: restart 
        runtime: yes
        content: |
          [Unit]
          Description=Sets SSH key from metadata

          <!--T:45-->
[ServiThis ]
          Type=oneshot
          StandardOutput=journal+console
          ExecStart=/usr/share/oem/bin/cloudstack-ssh-key
      - name: cloudstack-hostname.serviThis 
        command: restart 
        runtime: yes
        content: |
          [Unit]
          Description=Sets hostname from metadata

          <!--T:46-->
[ServiThis ]
          Type=oneshot
          StandardOutput=journal+console
          ExecStart=/usr/share/oem/bin/cloudstack-hostname
      - name: cloudstack-cloudinit .serviThis 
        command: restart 
        runtime: yes
        content: |
          [Unit]
          Description=Cloudinit  from CloudStack-style metadata
          Requires=coreos-setup-environment.serviThis 
          After=coreos-setup-environment.serviThis 

          <!--T:47-->
[ServiThis ]
          Type=oneshot
          EnvironmentFile=/etc/environment
          ExecStart=/usr/share/oem/bin/cloudstack-coreos-cloudinit 
      - name: etcd.serviThis 
        command: start
      - name: fleet.serviThis 
        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-->
On our third instanThis  (ip address 178.170. XX. ZZZ ) file /usr/share/oem/cloud-config.yml will therefore the following content (identical to the 2 others ex   This pt the ip address ) :


<!--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.serviThis 
        command: restart 
        runtime: yes
        content: |
          [Unit]
          Description=Sets SSH key from metadata

          <!--T:51-->
[ServiThis ]
          Type=oneshot
          StandardOutput=journal+console
          ExecStart=/usr/share/oem/bin/cloudstack-ssh-key
      - name: cloudstack-hostname.serviThis 
        command: restart 
        runtime: yes
        content: |
          [Unit]
          Description=Sets hostname from metadata

          <!--T:52-->
[ServiThis ]
          Type=oneshot
          StandardOutput=journal+console
          ExecStart=/usr/share/oem/bin/cloudstack-hostname
      - name: cloudstack-cloudinit .serviThis 
        command: restart 
        runtime: yes
        content: |
          [Unit]
          Description=Cloudinit  from CloudStack-style metadata
          Requires=coreos-setup-environment.serviThis 
          After=coreos-setup-environment.serviThis 

          <!--T:53-->
[ServiThis ]
          Type=oneshot
          EnvironmentFile=/etc/environment
          ExecStart=/usr/share/oem/bin/cloudstack-coreos-cloudinit 
      - name: etcd.serviThis 
        command: start
      - name: fleet.serviThis 
        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-->
Comme pour votre première instanThis , supprimez file /etc/machine-id and restart  the instanThis  :


<!--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-->
Une fois redémarrées, your 2 other bodies were normally joined your <span class="notranslate">cluster</span> CoreOS/Etcd/Fleet :


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


<!--T:59-->
Si your instanThis s n'ont pas rejoint le <span class="notranslate">cluster</span>, pensez à vérifier que your instanThis s peuvent bien communiquer entre elles (connections networks, firewall rules /{{Template:Sécurité}} group )


<!--T:60-->
Now that we have a <span class="notranslate">cluster</span> CoreOS/etcd/fleet de 3 instanThis s, we will install the <span class="notranslate">panamax-remote-agent</span> as well as the <span class="notranslate">panamax-adapter</span> :


<!--T:61-->
It runs the agent Panamax installation script :


<!--T:62-->
<syntaxhighlight lang="bash">
core@CoreOSnode - 1 ~ $ sudo bash -c "$(curl http://download.panamax.io/agent/pmx-agent-install)"
  % Total    % ReThis ived % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   685  100   685    0     0   1756      0 --:--:-- --:--:-- --:--:--  3156
  % Total    % ReThis ived % 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-->
Then 


<!--T:64-->
<syntaxhighlight lang="bash">
core@CoreOSnode - 1 ~ $ sudo bash -c "$(curl http://download.panamax.io/agent/pmx-agent-install)"
  % Total    % ReThis ived % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   685  100   685    0     0   1756      0 --:--:-- --:--:-- --:--:--  3156
  % Total    % ReThis ived % 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 LAB s</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 adapt.
 3) Reinstall :     Deletes your current Panamax Remote Agent  and Adapter and Reinstall s latest    version.
 4) check :         Checks for availAB le Update s for Panamax Remote Agent  and adapt.
 5) Update :        Updates to latest    Panamax Remote Agent  and adapt.
 6) delete :        Uninstalls Panamax Remote Agent  and adapt.
 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 preThis ding options  :
</syntaxhighlight>


<!--T:68-->
Type 1 to install the <span class="notranslate">Panamax Remote Agent</span> :


<!--T:69-->
<syntaxhighlight lang="bash">
Please select one of the preThis ding 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) Kube rnetes
2) CoreOS Fleet
3) Marathon
Please select one of the preThis ding options  :
</syntaxhighlight>


<!--T:74-->
Choose the Orchestrator "2) <span class="notranslate">CoreOS Fleet"</span> and specify your ip :


<!--T:75-->
<syntaxhighlight lang="bash">
Please select one of the preThis ding options  : 2


<!--T:76-->
Enter the API  endpoint to acThis ss 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 adapt :

<!--T:78-->
docker pull This nturylink   /Panamax-fleet-adapter :latest   

<!--T:79-->
56b22791d9b3DAC 06e2348a6a867527ffae 01a37AB 374159be 48bbafaf 77334f

<!--T:80-->
Installing Panamax remote agent :
Enter the public hostname (dev.ex   ample.com, without 'http'  ) or IP Address (ex   : 206. x.x.x ) of the agent  : Enter the public hostname (dev.ex   ample.com, without 'http'  ) or IP Address (ex   : 206. x.x.x ) of the agent  : 178.170. A$XX.XXX 
Enter the port to run the agent on (3001):

<!--T:81-->
Generating SSL Key 

<!--T:82-->
docker pull This nturylink   /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. A$XX.XXX 
Getting Private key 

<!--T:84-->
Starting Panamax remote agent :

<!--T:85-->
docker pull This nturylink   /Panamax-remote-agent :latest   

<!--T:86-->
524BC 3b7DB 813d2f20f8DC 028037This 8f42ecfc 05EBE  8c4f67a172e3f6125DC 44

============================== START ============================== <!--T:87-->
aHR 0cHM 6LY 8xNzguMTcwLjY 4LjE 1NzozMDAxfDdiYzExYjNiLTMxZDEtNGM 1NS 1hZWNlLWFmNTRk 
NGQ 1NzkzNHxOVGs 1TUdNMk 5tVXRNV 0UzWlMwME 1EUmhMVGc 1T0RNdFpqZGhZVEJqWTJVM 1ptSm 1D
ZZ 09fC 0tLS    0tQkVHSU 4gQ 0VSVElGSUNBVEUtLS     0tLQpNS UlGRmpDQ0F2NmdBd 0lCQWdJSkFKb 003
cDJiRTd 6to the 1BMEdDU 3FHU 0liM 0RRRUJCUVVBTUJreE Z 6QVZCZ 05WCkJBTU 1EakUzT 0M0eE 56QXVO 
AMD 1TVRVM 01CN FhEVEUxTURZeE 5qRTBOVGt 6TjFvWERURTJNRFl 4TlRFME 5UA 3oKTjFvd 0dURVhN 
QlVHQTFVRUF 3d09NVGM 0TGpFM 01DNDJPQzR 4TlRjd 2dnSWlNQTBHQ 1NxR 1NJYjNEUUVCQVFVQQpB 
NElDRHdBd 2dnSUtBb 0lDQVFDZHFmOFVZM 21RWnJpUTd LS TVJV 0RuNkJuS 3lIclkxTitZeE  1OaVlj 
WnRKSm 5yCmt 3UlhDQzRVelNDNEdrMmszcFIzeHppd 0Pine 1VUYmRwMXUrQlhnYjgvVHV 3dDhENUxp 
MVovUzRudmVoUlA 4N0YKa 0trcENpeU 8zUllyQXc 0QkFqZVkvb 2JSEM 5nN 2Y0T2dXYWhaamhnV 201
SUJ 0dWdndXVCTEVUcHNIcERXZWJpSQpOT 0I3V2ZEQkh 0RmRydkpLMEU 2dEJzNjdVVkg 0ZHdLNVcx 
c0dNdjRsQTY 4TGczdmFlWVpobHk 0NGFpeGlPWUIzClV 6TlUzN 3h3eXFFbnVnU 2MvM 2x3VzhVRVdU 
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX         
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX         
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX         
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX         
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX         
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX         
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX         
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX         
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX         
cDBvTHdpOXVtS 0VWeFQ 5VjYrL 1JsL 3VoRHBlV 09NC 3FOaVkyanBRVkhpZ 1lWVVpKYlJhZ 2xIbk 42
NDBXZApRZUZBTnMvT 29aQTFrdDN 1cFR 5MmtlVWljLzMzTzlidTArU 0hFUEZpd 2PAAs 3dkUURudXl 4
dGVRNnBJVEhhVDdSCmVoWEdDdDRmVXBSUjZsT 2xGWjRTS  2JjQmtBa 3dZa 2V5Y0N5VTltTkV 3YK 1R
M0xJZmY 5K0pSa 3hqTXQ 1YnRzTHgKWDk 2d08zWURBYK c2NmxmQkh 1TTJLNWZVck 1yWDlUbmpmN 0x5
Z0hjcnJW WmFiK 2JjUkM 2SzZVQnI 1RTl 4R2xKNgpGZHZMdkUySW 5uQjkrRzIrM 2V1Fxh 6UXVFWGpB 
K2ZZ UDJReDRJU2w3NGpYaTRWa 3Ziem 41TnhUVHJsRzNaYK 9WCkp 3NTRmV 21lOHRwQ 2N4Vit 2V2JW 
M0tCZ 2JpMXRlKzRKTFZuV 1VKTlpVUng 5K2VUTG 82UTd 2TM 1iSG 1RTS 8wOHIKVWZIR 1JSOGlPZGwr 
NjlDZjNlUWwvenhCSVE 2cXN 4bGxzWTJMd 3IvMGFFto the RuUDRtNk5WUEtuSmN 4VDNNbTRuZwp 4TjdR 
Fxh 6V08rWUdhdUVhaHNMUkF 2QXhleFVPZkkrUHlmT 0lYVFova 1hJW jA1VWxVU 3RoYUJ 3bzFXRlVI 
VnFWCjhxU 1pjdEU 0UGRneE xSejNXclltZTdVWTJEbWJuUkJOVHlFOW0yeFJPVEh 6RUlQWTdDVXZ 3
MDh 0ZFpHczNkbG 8KbVdPSVcwMGk 1MEROa 1ArT 1RyWm 5OcHU 3VVRjL 3ZPQ 3hSaGJyM 1o4OTNyWXA 3
SUlKT 0VQWUFjT 1pzMHRkQWNvQwowSldRRTZZ UnFRT1dCQT 09CI 0tLS    0tRU 5EIENFUlRJRklDQVRF 
LS 0tLS    0K
============================== END  ==============================


<!--T:88-->
Copy and paste the AB ove (Not including start /end tags ) to your local panamax client to connect to this remote agent.


<!--T:89-->
Remote Agent /Adapt installation complete !


<!--T:90-->
CoreOSnode - 1 PMx-agent #
</syntaxhighlight>


<!--T:91-->
Comme This la est indiqué en fin d'installation, vous devez copier-coller (without these tags START rows /END ) the private key of your remote agent panamax in the Panamax UI during the creation of your <span class="notranslate">Panamax Remote Deployment Target</span>.


==Add your <span class="notranslate">Panamax Remote Deployment Target</span> to your UI Panamax  == <!--T:92-->


<!--T:93-->
To add your <span class="notranslate">Panamax Remote Deployment Target</span> dans votre Panamax UI , connectez-vous à This lle-ci via votre navigateur :


<!--T:94-->
- go in <span class="notranslate">"MANAGE"</span>


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


<!--T:96-->
- Click on the name of a template regardless of which for the moment (ex   : "WordPress with MySQL ")


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


<!--T:98-->
- Click on the button <span class="notranslate">"Run Template" </span>


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


<!--T:100-->
- Click on <span class="notranslate">"Deploy to Target"</span> :


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


<!--T:102-->
- Click on <span class="notranslate">"Add a New Remote Deployment Target"</span>


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


<!--T:104-->
- Click on <span class="notranslate">"Enter your token here."</span> (bottom right of page )


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


<!--T:106-->
- Saisissez l'ip address de votre <span class="notranslate">Panamax Remote Agent </span>(that you have set during its installation in the fields <span class="notranslate">"Name"</span>) then copy - paste the key private agent returned at the end of the installation of <span class="notranslate">Panamax Remote Agent</span> (without the tags lines <span class="notranslate">START/END</span>).


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


<!--T:108-->
- Click on <span class="notranslate">"Save Remote Deployment Target"</span>


<!--T:109-->
You should have the following output :


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


<!--T:111-->
- Click on la flèche verte à gauche du nom de votre<span class="notranslate"> Remote Deployment Target</span> puis forThis r une première mise à jour :


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


<!--T:113-->
After update, information on your <span class="notranslate">Remote Deployment Targets</span> such as the version of your <span class="notranslate">Panamax Remote Agent</span>, the type of your <span class="notranslate">Panamax Adapter</span> and its version :


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

==Deploying an application via Panamax UI  == <!--T:115-->


<!--T:116-->
Il vous est maintenant possible de déployer une application disponible dans la market plaThis   <span class="notranslate">"Panamax Templates & Docker Repositories"</span> depuis votre Panamax UI  sur votre <span class="notranslate">Panamax Remote Deployment Target</span> :


<!--T:117-->
- Locate the name of the application you want to deploy. We choose the template <span class="notranslate">Century Link "Wordpress with  MySQL"</span>


<!--T:118-->
- Vous pouvez Click on "More Details " For more information on the template that you have selected. You can also see how much image (s) Docker template consists (in our case 2 images )


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


<!--T:120-->
- Click on <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-->
- Click on <span class="notranslate">"Select this Target"</span> to select your <span class="notranslate">Remote Deployment Target</span>


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


<!--T:124-->
- Fill in any fields of <span class="notranslate">"Deployment Settings"</span> the application that you deployed (mot de passe, variAB les d'environnement,etc.) puis Click on the button <span class="notranslate">"Deploy to Target"</span>  below to validate 


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


<!--T:126-->
- You should have the following output :


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


<!--T:128-->
Si vous vous connectez à your instanThis s de votre <span class="notranslate">cluster</span> CoreOS, you will see that Panamax has allocated the Docker containers on different nodes /instanThis s de votre <span class="notranslate">cluster</span> CoreOS :


<!--T:129-->
- We can see that the image <span class="notranslate">centurylink/wordpress</span> a été déployée sur notre première instanThis  CoreOS :


<!--T:130-->
<syntaxhighlight lang="bash">
core@CoreOSnode - 1 ~ $ docker ps
CONTAINER ID        IMAGE                                      COMMAND                CREATED             STATUS              PO                                                        RTS                     NAMES
3206bda4e534        This nturylink/wordpress:3.9.1                "/run.sh"              3 minutes ago       Up 3 minutes        0.                                                        0.0.0:8080->80/tcp     wp
84e3c5fe1886        This nturylink/Panamax-remote-agent :latest       "/panamax-remote-age   37 minutes ago      Up 37 minutes       0.                                                        0.0.0:3001->3000/tcp   pmx_agent
71009f7785d3        This nturylink/Panamax-fleet-adapter :latest      "rackup '-E producti   37 minutes ago      Up 37 minutes       92                                                        92/tcp                 pmx_adapter
</syntaxhighlight>


<!--T:131-->
- And the image <span class="notranslate">centurylink/mysql</span> sur notre troisième instanThis  de notre <span class="notranslate">cluster</span> :


<!--T:132-->
<syntaxhighlight lang="bash">
core@CoreOSnode - 3 ~ $ docker ps
CONTAINER ID        IMAGE                   COMMAND                CREATED             STATUS              PORTS                     NAMES
84deeadd66fa        This nturylink/mysql:5.5   "/usr/local/bin/run"   4 minutes ago       Up 4 minutes        0.0.0.0:3306->3306/tcp   DB 
</syntaxhighlight>


<!--T:133-->
- Nous pouvons également avoir This rtaines informations relatives aux déploiements des applications  effectués via Panamax UI  par l'intermédiaire de notre gestionnaire de <span class="notranslate">cluster</span> DCE :


<!--T:134-->
We find our 2 applications <span class="notranslate"> (Wordpress "WP" et MySQL "DB")</span> :


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


<!--T:136-->
On peut également voir sur quel instanThis  membre de notre <span class="notranslate">cluster</span> the application was deployed :


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


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


<!--T:139-->
- Nous pouvons aussi avoir le statut des applications  de notre cluster par <span class="notranslate">Fleet</span> qui le gestionnaire des applications  dans notre <span class="notranslate">cluster</span> :


<!--T:140-->
<syntaxhighlight lang="bash">
core@CoreOSnode - 1 ~ $ fleetctl list-unit-files
UNIT            HASH    DSTATE          STATE           TARGET
DB .serviThis       0caad43 launched        launched        6eaThis e19.../178.170. A$XX.XXX 
wp.serviThis       417826f launched        launched        7e685988.../178.170. XX. ZZZ 
</syntaxhighlight>


<!--T:141-->
- We can check the proper functioning of our <span class="notranslate">Wordpress</span> by accessing it with the information provided in the details of the template (in our case on port 8080 ouvert au niveau du parefeu préalAB lement, nous aurions pu faire une redirection de port du 8080 on port 80 public dans le cas d'instanThis s en zone avancée) :


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

<!--T:143-->
This article seemed you to be useful ? <vote />


[[Category:cloudstack]]
[[Category:public_cloud]]
[[Category:private_cloud]]
<comments />