Difference between revisions of "Use Cloudstack by Ikoula Panamax"

From EN Ikoula wiki
⧼vector-jumptonavigation⧽ ⧼vector-jumptosearch⧽
 
(16 intermediate revisions by one other user not shown)
Line 1: Line 1:
−
<span data-link_translate_fr_title="Utiliser Panamax sur Cloudstack by Ikoula"  data-link_translate_fr_url="Utiliser_Panamax_sur_Cloudstack_by_Ikoula"></span><br />[[:fr:Utiliser Panamax sur Cloudstack by Ikoula]][[fr:Utiliser Panamax sur Cloudstack by Ikoula]]<br />
+
<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 פנמקס]]
−
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-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-->
 
<!--T:1-->
−
If you do not know yet [http://panamax.io/ Panamax] It iClick on  a product <span class="notranslate">Open Source</span> developed by <span class="notranslate">Century Link Labs</span> that iClick on  both a market place  and a Manager for containerized applicationClick on  Docker from an intuitive web interface.
+
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-->
 
<!--T:2-->
−
It Click on  ufficeClick on  to Click on  eek the application of our choice then of a clique to deploy on our bodieClick on  targetClick on  uClick on  ing docker and one Panamax.
+
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-->
 
<!--T:3-->
−
Panamax relieClick on   on technologieClick on  Docker, DCE, <span class="notranslate">Fleet</span> and Cloud-init  included in CoreOS.
+
Panamax relies on technologies Docker, DCE, <span class="notranslate">Fleet</span> and Cloud-init  included in CoreOS.
  
  
 
<!--T:4-->
 
<!--T:4-->
−
We will uClick on  e in our Click on the button ample 4 inClick on  tanceClick on  And the image [https://ikoula.wiki/help/Mettre_a_jour_CoreOS_manuellement Update]one for the client part /Panamax UI  and 3 otherClick on  which will form the <span class="notranslate">cluster</span> for the part <span class="notranslate">Panamax Remote Target (Panamax Remote Agent + Panamax Adapter)</span> :
+
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> :
  
  
  
−
==InClick on  tallation of Panamax UI  /API  (web interface /market place )== <!--T:5-->
+
==Installation of Panamax UI  /API  (web interfaThis  /market plaThis  )== <!--T:5-->
  
  
 
<!--T:6-->
 
<!--T:6-->
−
On our forum dedicated to the client part of Panamax (Panamax UI /API ), downloading archive containing InClick on  taller :
+
On our forum dedicated to the client part of Panamax (Panamax UI /API ), downloading archive containing Installer :
  
  
 
<!--T:7-->
 
<!--T:7-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOS-PanamaxUI ~ $ sudo curl -O http://download.panamax.io/installer/panamax-latest.tar.gz
+
core@CoreOS-PanamaxUI ~ $ sudo curl -O http://download.panamax.io/installer/panamax-latest   .tar.gz
−
   % Total    % Received % Xferd  Average Speed  Time    Time    Time  Current
+
   % Total    % ReThis ived % Xferd  Average Speed  Time    Time    Time  Current
 
                                 Dload  Upload  Total  Spent    Left  Speed
 
                                 Dload  Upload  Total  Spent    Left  Speed
 
100 15165  100 15165    0    0  22157      0 --:--:-- --:--:-- --:--:-- 49558
 
100 15165  100 15165    0    0  22157      0 --:--:-- --:--:-- --:--:-- 49558
Line 40: Line 60:
  
 
<!--T:8-->
 
<!--T:8-->
−
It createClick on  the directory /var/panamax where you Click on the button tracted the inClick on  tallation fileClick on  :
+
It creates the directory /var/panamax where you ex  tracted the installation files :
  
  
Line 46: Line 66:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
 
core@CoreOS-PanamaxUI ~ $ sudo mkdir -p /var/panamax
 
core@CoreOS-PanamaxUI ~ $ sudo mkdir -p /var/panamax
−
core@CoreOS-PanamaxUI ~ $ Click on  udo tar -C /var/panamax -zxvf panamax-lateClick on  t.tar.gz
+
core@CoreOS-PanamaxUI ~ $ sudo tar -C /var/panamax -zxvf panamax-latest  .tar.gz
 
./
 
./
 
./Makefile
 
./Makefile
 
./configure
 
./configure
 
./create-docker-mount
 
./create-docker-mount
−
./LICENSE
+
./LICENS E
−
./deClick on  ktop
+
./desktop
 
./panamax
 
./panamax
−
./.coreoClick on  env
+
./.coreosenv
 
./README.md
 
./README.md
 
./CHANGELOG.md
 
./CHANGELOG.md
−
./ubuntu.Click on  h
+
./ubuntu.sh
 
./Vagrantfile
 
./Vagrantfile
−
./.verClick on  ion
+
./.version
−
./coreoClick on 
+
./coreos
 
./Vagrantfile-win
 
./Vagrantfile-win
 
./CONTRIBUTING.md
 
./CONTRIBUTING.md
Line 67: Line 87:
  
 
<!--T:10-->
 
<!--T:10-->
−
It iClick on  placed in the directory /var/panamax and we launch the CoreOS-Click on  pecific inClick on  taller by Click on  pecifying that you want to uClick on  e the Click on  table verClick on  ion (output truncated voluntarily ) :
+
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 ) :
  
  
Line 73: Line 93:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
 
core@CoreOS-PanamaxUI ~ $ cd /var/panamax
 
core@CoreOS-PanamaxUI ~ $ cd /var/panamax
−
core@CoreOS-PanamaxUI /var/panamax $ Click on  udo ./coreoClick on  inClick on  tall --Click on  table
+
core@CoreOS-PanamaxUI /var/panamax $ sudo ./coreos install --stAB le
−
InClick on  talling Panamax...
+
Installing Panamax...
−
Created Click on  ymlink from /etc/Click on  yClick on  temd/Click on  yClick on  tem/Update -engine-reboot-manager.Click on ervice to /dev/null.
+
Created symlink from /etc/systemd/system/Update -engine-reboot-manager.serviThis to /dev/null.
−
Created Click on  ymlink from /etc/Click on  yClick on  temd/Click on  yClick on  tem/Update -engine.Click on ervice to /dev/null.
+
Created symlink from /etc/systemd/system/Update -engine.serviThis to /dev/null.
−
Created Click on  ymlink from /etc/Click on  yClick on  temd/Click on  yClick on  tem/Click on  ocketClick on  .target.wantClick on  /Click on  yClick on  temd-journal-gatewayd.Click on  ocket to /uClick on  r/lib64/Click on  yClick on  temd/Click on  yClick on  tem/Click on  yClick on  temd-
+
Created symlink from /etc/systemd/system/sockets.target.wants/systemd-journal-gatewayd.socket to /usr/lib64/systemd/system/systemd-
  
 
<!--T:12-->
 
<!--T:12-->
−
docker pull centurylink/panamax-api:lateClick on  t
+
docker pull This nturylink  /panamax-api:latest 
 
.................
 
.................
−
docker pull centurylink/panamax-ui:lateClick on  t
+
docker pull This nturylink  /panamax-ui:latest 
 
.....
 
.....
−
docker pull google/cadviClick on  or:0.13.0
+
docker pull google/cadvisor:0.13.0
 
.........
 
.........
−
docker pull centurylink/rediClick on  :lateClick on  t
+
docker pull This nturylink  /redis:latest 
 
....
 
....
−
docker pull centurylink/dray:lateClick on  t
+
docker pull This nturylink  /dray:latest 
−
...Created Click on  ymlink from /etc/Click on  yClick on  temd/Click on  yClick on  tem/multi-uClick on  er.target.wantClick on  /panamax-rediClick on  .Click on ervice to /etc/Click on  yClick on  temd/Click on  yClick on  tem/panamax-rediClick on  .Click on  erv
+
...Created symlink from /etc/systemd/system/multi-user.target.wants/panamax-redis.serviThis to /etc/systemd/system/panamax-redis.serv
−
Created Click on  ymlink from /etc/Click on  yClick on  temd/Click on  yClick on  tem/multi-uClick on  er.target.wantClick on  /panamax-dray.Click on ervice to /etc/Click on  yClick on  temd/Click on  yClick on  tem/panamax-dray.Click on  ervice.
+
Created symlink from /etc/systemd/system/multi-user.target.wants/panamax-dray.serviThis to /etc/systemd/system/panamax-dray.serviThis .
−
Created Click on  ymlink from /etc/Click on  yClick on  temd/Click on  yClick on  tem/multi-uClick on  er.target.wantClick on  /panamax-metricClick on  .Click on ervice to /etc/Click on  yClick on  temd/Click on  yClick on  tem/panamax-metricClick on  .Click on  er
+
Created symlink from /etc/systemd/system/multi-user.target.wants/panamax-metrics.serviThis to /etc/systemd/system/panamax-metrics.ser
−
Created Click on  ymlink from /etc/Click on  yClick on  temd/Click on  yClick on  tem/multi-uClick on  er.target.wantClick on  /panamax-api.Click on ervice to /etc/Click on  yClick on  temd/Click on  yClick on  tem/panamax-api.Click on  ervice.
+
Created symlink from /etc/systemd/system/multi-user.target.wants/panamax-api.serviThis to /etc/systemd/system/panamax-api.serviThis .
−
Created Click on  ymlink from /etc/Click on  yClick on  temd/Click on  yClick on  tem/multi-uClick on  er.target.wantClick on  /panamax-ui.Click on ervice to /etc/Click on  yClick on  temd/Click on  yClick on  tem/panamax-ui.Click on  ervice.
+
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]: => RailClick on  4.1.7 application Click on  tarting in production on http://0.0.0.0:3000
+
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 `railClick on  Click on  erver -h` for more Click on  tartup optionClick on 
+
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: Click on  erver iClick on  liClick on  tening on all interfaceClick on  (0.0.0.0). ConClick on  ider uClick on  ing 127.0.0.1 (--binding option)
+
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 Click on  hutdown Click on  erver
+
Jul 10 11:45:39 CoreOS-PanamaxUI docker[1790]: => Ctrl-C to shutdown server
−
Panamax inClick on  tall complete
+
Panamax install complete
 
core@CoreOS-PanamaxUI /var/panamax $
 
core@CoreOS-PanamaxUI /var/panamax $
 
</syntaxhighlight>
 
</syntaxhighlight>
Line 105: Line 125:
  
 
<!--T:13-->
 
<!--T:13-->
−
We can verify that our 5 containerClick on  Panamax are running :
+
We can verify that our 5 containers Panamax are running :
  
  
 
<!--T:14-->
 
<!--T:14-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOS-PanamaxUI /var/panamax $ docker pClick on 
+
core@CoreOS-PanamaxUI /var/panamax $ docker ps
−
CONTAINER ID        IMAGE                            COMMAND                CREATED            STATUS              PORTS                   NAMES
+
CONTAINER ID        IMAGE                            COMMAND                CREATED            STATUS              PORTS                     NAMES
−
41a18b410427        centurylink/panamax-ui:lateClick on  t    "/bin/Click on  h -c 'bundle    3 minuteClick on  ago      Up 3 minuteClick on          0.0.0.0:3000->3000/tcp  PMX_UI
+
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
−
0cc8befee1b7       centurylink/panamax-api:lateClick on  t  "/bin/Click on  h -c 'bundle    3 minuteClick on  ago      Up 3 minuteClick on          0.0.0.0:3001->3000/tcp  PMX_API  
+
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/cadviClick on  or:0.13.0          "/uClick on  r/bin/cadviClick on  or"    3 minuteClick on  ago      Up 3 minuteClick on          0.0.0.0:3002->8080/tcp  PMX_CADVISOR
+
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 minuteClick on  ago      Up 3 minuteClick on          0.0.0.0:3003->3000/tcp  PMX_DRAY
+
06b2219ac42e        This nturylink/dray:0.10.0          "/dray"                3 minutes ago      Up 3 minutes        0.0.0.0:3003->3000/tcp  PMX_DRAY
−
8a6110651dcc       centurylink/rediClick on  :lateClick on  t        "rediClick on  -Click on  erver"        3 minuteClick on  ago      Up 3 minuteClick on          6379/tcp                PMX_DRAY_REDIS
+
8a6110651DC c       This nturylink/redis:latest            "redis-server"        3 minutes ago      Up 3 minutes        6379/tcp                PMX_DRAY_REDIS
 
</syntaxhighlight>
 
</syntaxhighlight>
  
  
 
<!--T:15-->
 
<!--T:15-->
−
We can connect to our UI Panamax uClick on  ing our browClick on  er in tapping the ip of our inClick on tance followed by ":3000" to Click on  pecify the liClick on  tening port (don't forget to create permiClick on  Click on  ionClick on  firewall ruleClick on  and if neceClick on  Click on  ary port redirection ) thereof :
+
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 :
  
  
Line 129: Line 149:
  
  
−
==InClick on  tallation of <span class="notranslate">Panamax Remote Deployment Target</span>== <!--T:17-->
+
==Installation of <span class="notranslate">Panamax Remote Deployment Target</span>== <!--T:17-->
  
  
 
<!--T:18-->
 
<!--T:18-->
−
Connect to one of your 3 inClick on  tanceClick on  And the image deployed for the <span class="notranslate">cluster</span> :
+
Connect to one of your 3 instanThis s CoreOS deployed for the <span class="notranslate">cluster</span> :
  
  
 
<!--T:19-->
 
<!--T:19-->
−
Generate a new URL of <span class="notranslate">discovery Etcd</span> (token Click on  ) in a variable (here : ETCD_URL ) :
+
Generate a new URL of <span class="notranslate">discovery Etcd</span> (token s ) in a variAB le (Here : ETCD_URL ) :
  
  
 
<!--T:20-->
 
<!--T:20-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-1 ~ $ ETCD_URL=$(curl http://discovery.etcd.io/new)
+
core@CoreOSnode - 1 ~ $ ETCD_URL =$(curl http://discovery.etcd.io/new)
−
   % Total    % Received % Xferd  Average Speed  Time    Time    Time  Current
+
   % Total    % ReThis ived % Xferd  Average Speed  Time    Time    Time  Current
 
                                 Dload  Upload  Total  Spent    Left  Speed
 
                                 Dload  Upload  Total  Spent    Left  Speed
 
100    58  100    58    0    0    79      0 --:--:-- --:--:-- --:--:--  101
 
100    58  100    58    0    0    79      0 --:--:-- --:--:-- --:--:--  101
−
core@CoreOSnode-1 ~ $ echo $ETCD_URL
+
core@CoreOSnode - 1 ~ $ echo $ETCD_URL  
 
https://discovery.etcd.io/b8069c9bd67eae5cf19689daf4ebdd66
 
https://discovery.etcd.io/b8069c9bd67eae5cf19689daf4ebdd66
 
</syntaxhighlight>
 
</syntaxhighlight>
Line 157: Line 177:
 
<!--T:22-->
 
<!--T:22-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-1 ~ $ sudo wget -NP /usr/share/oem/ http://mirror02.ikoula.com/priv/coreos/cloud-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
 
--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
+
Resolving mirror02.ikoula.com... 80.93. A$XX.XXX , 2a00:c70:1:80:93:XX:XXX:1
−
Connecting to mirror02.ikoula.com|80.93.XX.XXX|:80... connected.
+
Connecting to mirror02.ikoula.com|80.93. A$XX.XXX |:80... connected.
 
HTTP request sent, awaiting response... 200 OK
 
HTTP request sent, awaiting response... 200 OK
−
Length: 1542 (1.5K) [text/plain]
+
Length: 1542 (1.5K) [tex  t/plain]
 
Remote file is newer, retrieving.
 
Remote file is newer, retrieving.
  
 
<!--T:23-->
 
<!--T:23-->
 
--2015-06-16 15:37:53--  http://mirror02.ikoula.com/priv/coreos/cloud-config.yml
 
--2015-06-16 15:37:53--  http://mirror02.ikoula.com/priv/coreos/cloud-config.yml
−
Reusing existing connection to mirror02.ikoula.com:80.
+
Reusing ex  isting connection to mirror02.ikoula.com:80.
 
HTTP request sent, awaiting response... 200 OK
 
HTTP request sent, awaiting response... 200 OK
−
Length: 1542 (1.5K) [text/plain]
+
Length: 1542 (1.5K) [tex  t/plain]
 
Saving to: '/usr/share/oem/cloud-config.yml'
 
Saving to: '/usr/share/oem/cloud-config.yml'
  
 
<!--T:24-->
 
<!--T:24-->
−
/usr/share/oem/cloud-config.yml              100%[===================================================================================================>]  1.51K  --.-KB/Click on    in 0Click on 
+
/usr/share/oem/cloud-config.yml              100%[===================================================================================================>]  1.51K  --.-KB/s  in 0s
  
 
<!--T:25-->
 
<!--T:25-->
−
2015-06-16 15:37:53 (264 MB/Click on  ) - '/usr/share/oem/cloud-config.yml' Click on  aved [1542/1542]
+
2015-06-16 15:37:53 (264 MB/s) - '/usr/share/oem/cloud-config.yml' saved [1542/1542]
 
</syntaxhighlight>
 
</syntaxhighlight>
  
 
<!--T:26-->
 
<!--T:26-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-1 ~ $ export `cat /etc/environment`
+
core@CoreOSnode - 1 ~ $ ex  port `cat /etc/environment`
 
</syntaxhighlight>
 
</syntaxhighlight>
  
 
<!--T:27-->
 
<!--T:27-->
−
Run the following commandClick on  to cuClick on  tomize the file cloud - config.yml downloaded with your environmental valueClick on  :
+
Run the following commands to customize the file cloud - config.yml downloaded with your environmental values :
  
 
<!--T:28-->
 
<!--T:28-->
 
<syntaxhighlight lang="bash">
 
<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#DISCOVERY_URL#'$ETCD_URL '#g' /usr/share/oem/cloud-config.yml
−
core@CoreOSnode-1 ~ $ Click on  udo Click on  ed -i 'Click on  #PRIVATE_IP#'$COREOS_PRIVATE_IPV4'#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>
 
</syntaxhighlight>
  
 
<!--T:29-->
 
<!--T:29-->
−
We check  our DCE Click on  ettingClick on  and <span class="notranslate">Fleet</span> iClick on  well Click on  ubClick on  tituted :
+
We check  our DCE settings and <span class="notranslate">Fleet</span> is well substituted :
  
 
<!--T:30-->
 
<!--T:30-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-1 ~ $ cat /usr/share/oem/cloud-config.yml
+
core@CoreOSnode - 1 ~ $ cat /usr/share/oem/cloud-config.yml
 
#cloud-config
 
#cloud-config
  
 
<!--T:31-->
 
<!--T:31-->
−
coreoClick on  :
+
coreos:
−
     unitClick on  :
+
     units:
−
       - name: cloudClick on  tack-Click on  Click on  h-key.Click on  ervice
+
       - name: cloudstack-ssh-key.serviThis
−
         command: reClick on  tart
+
         command: restart
−
         runtime: yeClick on 
+
         runtime: yes
 
         content: |
 
         content: |
 
           [Unit]
 
           [Unit]
−
           DeClick on  cription=SetClick on  SSH key from metadata
+
           Description=Sets SSH key from metadata
  
 
           <!--T:32-->
 
           <!--T:32-->
−
[Service]
+
[ServiThis ]
−
           Type=oneClick on  hot
+
           Type=oneshot
−
           StandardOutput=journal+conClick on  ole
+
           StandardOutput=journal+console
−
           ExecStart=/uClick on  r/Click on  hare/oem/bin/cloudClick on  tack-Click on  Click on  h-key
+
           ExecStart=/usr/share/oem/bin/cloudstack-ssh-key
−
       - name: cloudClick on  tack-hoClick on  tname.Click on  ervice
+
       - name: cloudstack-hostname.serviThis
−
         command: reClick on  tart
+
         command: restart
−
         runtime: yeClick on 
+
         runtime: yes
 
         content: |
 
         content: |
 
           [Unit]
 
           [Unit]
−
           DeClick on  cription=SetClick on  hoClick on  tname from metadata
+
           Description=Sets hostname from metadata
  
 
           <!--T:33-->
 
           <!--T:33-->
−
[Service]
+
[ServiThis ]
−
           Type=oneClick on  hot
+
           Type=oneshot
−
           StandardOutput=journal+conClick on  ole
+
           StandardOutput=journal+console
−
           ExecStart=/uClick on  r/Click on  hare/oem/bin/cloudClick on  tack-hoClick on  tname
+
           ExecStart=/usr/share/oem/bin/cloudstack-hostname
−
       - name: cloudClick on  tack-cloudinit .Click on  ervice
+
       - name: cloudstack-cloudinit .serviThis
−
         command: reClick on  tart
+
         command: restart
−
         runtime: yeClick on 
+
         runtime: yes
 
         content: |
 
         content: |
 
           [Unit]
 
           [Unit]
−
           DeClick on  cription=Cloudinit  from CloudStack-Click on  tyle metadata
+
           Description=Cloudinit  from CloudStack-style metadata
−
           RequireClick on  =coreoClick on  -Click on  etup-environment.Click on  ervice
+
           Requires=coreos-setup-environment.serviThis
−
           After=coreoClick on  -Click on  etup-environment.Click on  ervice
+
           After=coreos-setup-environment.serviThis
  
 
           <!--T:34-->
 
           <!--T:34-->
−
[Service]
+
[ServiThis ]
−
           Type=oneClick on  hot
+
           Type=oneshot
 
           EnvironmentFile=/etc/environment
 
           EnvironmentFile=/etc/environment
−
           ExecStart=/uClick on  r/Click on  hare/oem/bin/cloudClick on  tack-coreoClick on  -cloudinit  
+
           ExecStart=/usr/share/oem/bin/cloudstack-coreos-cloudinit  
−
       - name: etcd.Click on  ervice
+
       - name: etcd.serviThis
−
         command: Click on  tart
+
         command: start
−
       - name: fleet.Click on  ervice
+
       - name: fleet.serviThis
−
         command: Click on  tart
+
         command: start
 
     oem:
 
     oem:
−
       id: cloudClick on  tack
+
       id: cloudstack
 
       name: CloudStack
 
       name: CloudStack
−
       verClick on  ion-id: 0.0.1-r3
+
       version-id: 0.0.1-r3
−
       home-url: http://cloudClick on  tack.apache.org/
+
       home-url: http://cloudstack.apache.org/
−
       bug-report-url: httpClick on  ://github.com/coreoClick on  /coreoClick on  -overlay
+
       bug-report-url: https://github.com/coreos/coreos-overlay
 
     etcd:
 
     etcd:
−
       diClick on  covery: httpClick on  ://diClick on  covery.etcd.io/b8069c9bd67eae5cf19689daf4ebdd66
+
       discovery: https://discovery.etcd.io/b8069c9bd67eae5cf19689daf4ebdd66
−
       addr: 178.170.XX.XXX:4001
+
       addr: 178.170. A$XX.XXX :4001
−
       peer-addr: 178.170.XX.XXX:7001
+
       peer-addr: 178.170. A$XX.XXX :7001
 
     fleet:
 
     fleet:
−
       public-ip: 178.170.XX.XXX
+
       public-ip: 178.170. A$XX.XXX  
 
</syntaxhighlight>
 
</syntaxhighlight>
  
  
 
<!--T:35-->
 
<!--T:35-->
−
Delete the file /etc/machine-id then reboot the inClick on tance in order to regenerate a new machine id (your 3 inClick on  tanceClick on  muClick on  t have a different id ) :
+
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-->
 
<!--T:36-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-1 ~ $ sudo rm -f /etc/machine-id
+
core@CoreOSnode - 1 ~ $ sudo rm -f /etc/machine-id
−
core@CoreOSnode-1 ~ $ Click on  udo reboot
+
core@CoreOSnode - 1 ~ $ sudo reboot
 
</syntaxhighlight>
 
</syntaxhighlight>
  
  
 
<!--T:37-->
 
<!--T:37-->
−
Your firClick on t inClick on  tance Click on  hould appear in the liClick on  t of managed machineClick on  in <span class="notranslate">Fleet</span> :
+
Your first instanThis should appear in the list of managed machines in <span class="notranslate">Fleet</span> :
  
  
 
<!--T:38-->
 
<!--T:38-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-1 ~ $ fleetctl list-machines
+
core@CoreOSnode - 1 ~ $ fleetctl list-machines
 
MACHINE        IP              METADATA
 
MACHINE        IP              METADATA
−
7e685988...    178.170.XX.XXX -
+
7e685988...    178.170. A$XX.XXX   -
 
</syntaxhighlight>
 
</syntaxhighlight>
  
  
 
<!--T:39-->
 
<!--T:39-->
−
Here we can clearly Click on  ee our trial in the liClick on  t of machineClick on  <span class="notranslate">Fleet</span>, thiClick on  will be our inClick on tance that will init ialize our <span class="notranslate">cluster</span> CoreOS/Etcd/Fleet.
+
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-->
 
<!--T:40-->
−
Configurez maintenant your deux autreClick on  inClick on  tanceClick on  <span class="notranslate">CoreOS remote deployment target</span> by following the inClick on  tructionClick on  below :
+
Configurez maintenant your deux autres instanThis s <span class="notranslate">CoreOS remote deployment target</span> by following the instructions be low :
  
  
 
<!--T:41-->
 
<!--T:41-->
−
Connectez-vouClick on  à your deux autreClick on  inClick on  tanceClick on  puiClick on  recopiez le contenu du fichier /usr/share/oem/cloud-config.yml de votre première inClick on tance en remplaçant uniquement l'ip thereof by accessing it with the information provided in the details of the template l'ip de votre Click on econde inClick on  tance Click on  ur votre Click on econde inClick on  tance et by accessing it with the information provided in the details of the template l'ip de votre troiClick on  ième inClick on  tance Click on ur votre troiClick on ième inClick on  tance (you have to paClick on  Click on  root via a "Click on  udo Click on  u ") :
+
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-->
 
<!--T:42-->
−
On our Click on econd inClick on  tance (ip addreClick on  Click on  178.170. XX. YYY ) file /usr/share/oem/cloud-config.yml will therefore the following content (identical Click on the button cept the ip addreClick on  Click on  ) :
+
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-->
 
<!--T:43-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-2 ~ $ cat /usr/share/oem/cloud-config.yml
+
core@CoreOSnode - 2 ~ $ cat /usr/share/oem/cloud-config.yml
 
#cloud-config
 
#cloud-config
  
 
<!--T:44-->
 
<!--T:44-->
−
coreoClick on  :
+
coreos:
−
     unitClick on  :
+
     units:
−
       - name: cloudClick on  tack-Click on  Click on  h-key.Click on  ervice
+
       - name: cloudstack-ssh-key.serviThis
−
         command: reClick on  tart
+
         command: restart
−
         runtime: yeClick on 
+
         runtime: yes
 
         content: |
 
         content: |
 
           [Unit]
 
           [Unit]
−
           DeClick on  cription=SetClick on  SSH key from metadata
+
           Description=Sets SSH key from metadata
  
 
           <!--T:45-->
 
           <!--T:45-->
−
[Service]
+
[ServiThis ]
−
           Type=oneClick on  hot
+
           Type=oneshot
−
           StandardOutput=journal+conClick on  ole
+
           StandardOutput=journal+console
−
           ExecStart=/uClick on  r/Click on  hare/oem/bin/cloudClick on  tack-Click on  Click on  h-key
+
           ExecStart=/usr/share/oem/bin/cloudstack-ssh-key
−
       - name: cloudClick on  tack-hoClick on  tname.Click on  ervice
+
       - name: cloudstack-hostname.serviThis
−
         command: reClick on  tart
+
         command: restart
−
         runtime: yeClick on 
+
         runtime: yes
 
         content: |
 
         content: |
 
           [Unit]
 
           [Unit]
−
           DeClick on  cription=SetClick on  hoClick on  tname from metadata
+
           Description=Sets hostname from metadata
  
 
           <!--T:46-->
 
           <!--T:46-->
−
[Service]
+
[ServiThis ]
−
           Type=oneClick on  hot
+
           Type=oneshot
−
           StandardOutput=journal+conClick on  ole
+
           StandardOutput=journal+console
−
           ExecStart=/uClick on  r/Click on  hare/oem/bin/cloudClick on  tack-hoClick on  tname
+
           ExecStart=/usr/share/oem/bin/cloudstack-hostname
−
       - name: cloudClick on  tack-cloudinit .Click on  ervice
+
       - name: cloudstack-cloudinit .serviThis
−
         command: reClick on  tart
+
         command: restart
−
         runtime: yeClick on 
+
         runtime: yes
 
         content: |
 
         content: |
 
           [Unit]
 
           [Unit]
−
           DeClick on  cription=Cloudinit  from CloudStack-Click on  tyle metadata
+
           Description=Cloudinit  from CloudStack-style metadata
−
           RequireClick on  =coreoClick on  -Click on  etup-environment.Click on  ervice
+
           Requires=coreos-setup-environment.serviThis
−
           After=coreoClick on  -Click on  etup-environment.Click on  ervice
+
           After=coreos-setup-environment.serviThis
  
 
           <!--T:47-->
 
           <!--T:47-->
−
[Service]
+
[ServiThis ]
−
           Type=oneClick on  hot
+
           Type=oneshot
 
           EnvironmentFile=/etc/environment
 
           EnvironmentFile=/etc/environment
−
           ExecStart=/uClick on  r/Click on  hare/oem/bin/cloudClick on  tack-coreoClick on  -cloudinit  
+
           ExecStart=/usr/share/oem/bin/cloudstack-coreos-cloudinit  
−
       - name: etcd.Click on  ervice
+
       - name: etcd.serviThis
−
         command: Click on  tart
+
         command: start
−
       - name: fleet.Click on  ervice
+
       - name: fleet.serviThis
−
         command: Click on  tart
+
         command: start
 
     oem:
 
     oem:
−
       id: cloudClick on  tack
+
       id: cloudstack
 
       name: CloudStack
 
       name: CloudStack
−
       verClick on  ion-id: 0.0.1-r3
+
       version-id: 0.0.1-r3
−
       home-url: http://cloudClick on  tack.apache.org/
+
       home-url: http://cloudstack.apache.org/
−
       bug-report-url: httpClick on  ://github.com/coreoClick on  /coreoClick on  -overlay
+
       bug-report-url: https://github.com/coreos/coreos-overlay
 
     etcd:
 
     etcd:
−
       diClick on  covery: httpClick on  ://diClick on  covery.etcd.io/b8069c9bd67eae5cf19689daf4ebdd66
+
       discovery: https://discovery.etcd.io/b8069c9bd67eae5cf19689daf4ebdd66
 
       addr: 178.170. XX. YYY :4001
 
       addr: 178.170. XX. YYY :4001
 
       peer-addr: 178.170. XX. YYY :7001
 
       peer-addr: 178.170. XX. YYY :7001
Line 366: Line 386:
  
 
<!--T:48-->
 
<!--T:48-->
−
On our third inClick on tance (ip addreClick on  Click on  178.170. XX. ZZZ ) file /usr/share/oem/cloud-config.yml will therefore the following content (identical to the 2 otherClick on   Click on the button cept the ip addreClick on  Click on  ) :
+
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-->
 
<!--T:49-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-3 ~ $ cat /usr/share/oem/cloud-config.yml
+
core@CoreOSnode - 3 ~ $ cat /usr/share/oem/cloud-config.yml
 
#cloud-config
 
#cloud-config
  
 
<!--T:50-->
 
<!--T:50-->
−
coreoClick on  :
+
coreos:
−
     unitClick on  :
+
     units:
−
       - name: cloudClick on  tack-Click on  Click on  h-key.Click on  ervice
+
       - name: cloudstack-ssh-key.serviThis
−
         command: reClick on  tart
+
         command: restart
−
         runtime: yeClick on 
+
         runtime: yes
 
         content: |
 
         content: |
 
           [Unit]
 
           [Unit]
−
           DeClick on  cription=SetClick on  SSH key from metadata
+
           Description=Sets SSH key from metadata
  
 
           <!--T:51-->
 
           <!--T:51-->
−
[Service]
+
[ServiThis ]
−
           Type=oneClick on  hot
+
           Type=oneshot
−
           StandardOutput=journal+conClick on  ole
+
           StandardOutput=journal+console
−
           ExecStart=/uClick on  r/Click on  hare/oem/bin/cloudClick on  tack-Click on  Click on  h-key
+
           ExecStart=/usr/share/oem/bin/cloudstack-ssh-key
−
       - name: cloudClick on  tack-hoClick on  tname.Click on  ervice
+
       - name: cloudstack-hostname.serviThis
−
         command: reClick on  tart
+
         command: restart
−
         runtime: yeClick on 
+
         runtime: yes
 
         content: |
 
         content: |
 
           [Unit]
 
           [Unit]
−
           DeClick on  cription=SetClick on  hoClick on  tname from metadata
+
           Description=Sets hostname from metadata
  
 
           <!--T:52-->
 
           <!--T:52-->
−
[Service]
+
[ServiThis ]
−
           Type=oneClick on  hot
+
           Type=oneshot
−
           StandardOutput=journal+conClick on  ole
+
           StandardOutput=journal+console
−
           ExecStart=/uClick on  r/Click on  hare/oem/bin/cloudClick on  tack-hoClick on  tname
+
           ExecStart=/usr/share/oem/bin/cloudstack-hostname
−
       - name: cloudClick on  tack-cloudinit .Click on  ervice
+
       - name: cloudstack-cloudinit .serviThis
−
         command: reClick on  tart
+
         command: restart
−
         runtime: yeClick on 
+
         runtime: yes
 
         content: |
 
         content: |
 
           [Unit]
 
           [Unit]
−
           DeClick on  cription=Cloudinit  from CloudStack-Click on  tyle metadata
+
           Description=Cloudinit  from CloudStack-style metadata
−
           RequireClick on  =coreoClick on  -Click on  etup-environment.Click on  ervice
+
           Requires=coreos-setup-environment.serviThis
−
           After=coreoClick on  -Click on  etup-environment.Click on  ervice
+
           After=coreos-setup-environment.serviThis
  
 
           <!--T:53-->
 
           <!--T:53-->
−
[Service]
+
[ServiThis ]
−
           Type=oneClick on  hot
+
           Type=oneshot
 
           EnvironmentFile=/etc/environment
 
           EnvironmentFile=/etc/environment
−
           ExecStart=/uClick on  r/Click on  hare/oem/bin/cloudClick on  tack-coreoClick on  -cloudinit  
+
           ExecStart=/usr/share/oem/bin/cloudstack-coreos-cloudinit  
−
       - name: etcd.Click on  ervice
+
       - name: etcd.serviThis
−
         command: Click on  tart
+
         command: start
−
       - name: fleet.Click on  ervice
+
       - name: fleet.serviThis
−
         command: Click on  tart
+
         command: start
 
     oem:
 
     oem:
−
       id: cloudClick on  tack
+
       id: cloudstack
 
       name: CloudStack
 
       name: CloudStack
−
       verClick on  ion-id: 0.0.1-r3
+
       version-id: 0.0.1-r3
−
       home-url: http://cloudClick on  tack.apache.org/
+
       home-url: http://cloudstack.apache.org/
−
       bug-report-url: httpClick on  ://github.com/coreoClick on  /coreoClick on  -overlay
+
       bug-report-url: https://github.com/coreos/coreos-overlay
 
     etcd:
 
     etcd:
−
       diClick on  covery: httpClick on  ://diClick on  covery.etcd.io/b8069c9bd67eae5cf19689daf4ebdd66
+
       discovery: https://discovery.etcd.io/b8069c9bd67eae5cf19689daf4ebdd66
 
       addr: 178.170. XX. ZZZ :4001
 
       addr: 178.170. XX. ZZZ :4001
 
       peer-addr: 178.170. XX. ZZZ :7001
 
       peer-addr: 178.170. XX. ZZZ :7001
Line 435: Line 455:
  
 
<!--T:54-->
 
<!--T:54-->
−
Comme pour votre première inClick on  tance, Click on  upprimez file /etc/machine-id and reClick on  tart the inClick on tance :
+
Comme pour votre première instanThis , supprimez file /etc/machine-id and restart the instanThis :
  
  
 
<!--T:55-->
 
<!--T:55-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-2 ~ $ sudo rm -f /etc/machine-id
+
core@CoreOSnode - 2 ~ $ sudo rm -f /etc/machine-id
−
core@CoreOSnode-2 ~ $ Click on  udo reboot
+
core@CoreOSnode - 2 ~ $ sudo reboot
 
</syntaxhighlight>
 
</syntaxhighlight>
  
Line 447: Line 467:
 
<!--T:56-->
 
<!--T:56-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-3 ~ $ sudo rm -f /etc/machine-id
+
core@CoreOSnode - 3 ~ $ sudo rm -f /etc/machine-id
−
core@CoreOSnode-3 ~ $ Click on  udo reboot
+
core@CoreOSnode - 3 ~ $ sudo reboot
 
</syntaxhighlight>
 
</syntaxhighlight>
  
  
 
<!--T:57-->
 
<!--T:57-->
−
Une foiClick on  redémarréeClick on  , your 2 other bodieClick on  were normally joined your <span class="notranslate">cluster</span> CoreOS/Etcd/Fleet :
+
Une fois redémarrées, your 2 other bodies were normally joined your <span class="notranslate">cluster</span> CoreOS/Etcd/Fleet :
  
  
 
<!--T:58-->
 
<!--T:58-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-1 ~ $ fleetctl list-machines
+
core@CoreOSnode - 1 ~ $ fleetctl list-machines
 
MACHINE        IP              METADATA
 
MACHINE        IP              METADATA
−
6eacee19...    178.170.XX.XXX -
+
6eaThis e19...    178.170. A$XX.XXX   -
−
7e685988...    178.170.XX.YYY -
+
7e685988...    178.170. XX. YYY   -
−
87e15a4a...    178.170.XX.ZZZ -
+
87e15a4a...    178.170. XX. ZZZ   -
 
</syntaxhighlight>
 
</syntaxhighlight>
  
  
 
<!--T:59-->
 
<!--T:59-->
−
Si your inClick on  tanceClick on  n'ont paClick on  rejoint le <span class="notranslate">cluster</span>, penClick on  ez à vérifier que your inClick on  tanceClick on  peuvent bien communiquer entre elleClick on  (connectionClick on  networkClick on  , firewall ruleClick on  /Click on  ecurity group )
+
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-->
 
<!--T:60-->
−
Now that we have a <span class="notranslate">cluster</span> CoreOS/etcd/fleet de 3 inClick on  tanceClick on  , we will inClick on  tall the <span class="notranslate">panamax-remote-agent</span> aClick on  well aClick on  the <span class="notranslate">panamax-adapter</span> :
+
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-->
 
<!--T:61-->
−
It runClick on  the agent Panamax inClick on  tallation Click on  cript :
+
It runs the agent Panamax installation script :
  
  
 
<!--T:62-->
 
<!--T:62-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-1 ~ $ sudo bash -c "$(curl http://download.panamax.io/agent/pmx-agent-install)"
+
core@CoreOSnode - 1 ~ $ sudo bash -c "$(curl http://download.panamax.io/agent/pmx-agent-install)"
−
   % Total    % Received % Xferd  Average Speed  Time    Time    Time  Current
+
   % Total    % ReThis ived % Xferd  Average Speed  Time    Time    Time  Current
 
                                 Dload  Upload  Total  Spent    Left  Speed
 
                                 Dload  Upload  Total  Spent    Left  Speed
 
100  685  100  685    0    0  1756      0 --:--:-- --:--:-- --:--:--  3156
 
100  685  100  685    0    0  1756      0 --:--:-- --:--:-- --:--:--  3156
−
   % Total    % Received % Xferd  Average Speed  Time    Time    Time  Current
+
   % Total    % ReThis ived % Xferd  Average Speed  Time    Time    Time  Current
 
                                 Dload  Upload  Total  Spent    Left  Speed
 
                                 Dload  Upload  Total  Spent    Left  Speed
 
100  8613  100  8613    0    0  27496      0 --:--:-- --:--:-- --:--:-- 27694
 
100  8613  100  8613    0    0  27496      0 --:--:-- --:--:-- --:--:-- 27694
Line 491: Line 511:
 
./README.md
 
./README.md
 
./CHANGELOG.md
 
./CHANGELOG.md
−
./openssl.cnf
+
./OpenSSL .cnf
 
./.version
 
./.version
−
Execute cd /root/pmx-agent && ./pmx-agent to invoke agent setup script.
+
Execute cd /root/PMx-agent && ./PMx-agent to invoke agent setup script.
 
</syntaxhighlight>
 
</syntaxhighlight>
  
Line 503: Line 523:
 
<!--T:64-->
 
<!--T:64-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-1 ~ $ sudo bash -c "$(curl http://download.panamax.io/agent/pmx-agent-install)"
+
core@CoreOSnode - 1 ~ $ sudo bash -c "$(curl http://download.panamax.io/agent/pmx-agent-install)"
−
   % Total    % Received % Xferd  Average Speed  Time    Time    Time  Current
+
   % Total    % ReThis ived % Xferd  Average Speed  Time    Time    Time  Current
 
                                 Dload  Upload  Total  Spent    Left  Speed
 
                                 Dload  Upload  Total  Spent    Left  Speed
 
100  685  100  685    0    0  1756      0 --:--:-- --:--:-- --:--:--  3156
 
100  685  100  685    0    0  1756      0 --:--:-- --:--:-- --:--:--  3156
−
   % Total    % Received % Xferd  Average Speed  Time    Time    Time  Current
+
   % Total    % ReThis ived % Xferd  Average Speed  Time    Time    Time  Current
 
                                 Dload  Upload  Total  Spent    Left  Speed
 
                                 Dload  Upload  Total  Spent    Left  Speed
 
100  8613  100  8613    0    0  27496      0 --:--:-- --:--:-- --:--:-- 27694
 
100  8613  100  8613    0    0  27496      0 --:--:-- --:--:-- --:--:-- 27694
Line 514: Line 534:
 
./README.md
 
./README.md
 
./CHANGELOG.md
 
./CHANGELOG.md
−
./openssl.cnf
+
./OpenSSL .cnf
 
./.version
 
./.version
−
Execute cd /root/pmx-agent && ./pmx-agent to invoke agent setup script.
+
Execute cd /root/PMx-agent && ./PMx-agent to invoke agent setup script.
−
core@CoreOSnode-1 ~ $ sudo su
+
core@CoreOSnode - 1 ~ $ sudo su  
−
CoreOSnode-1 core # cd /root/pmx-agent
+
CoreOSnode - 1 core # cd /root/pmx-agent
  
 
<!--T:65-->
 
<!--T:65-->
Line 529: Line 549:
  
 
<!--T:66-->
 
<!--T:66-->
−
<span class="notranslate">CenturyLink Labs</span> - http://www.centurylinklabs.com/
+
<span class="notranslate">CenturyLink LAB s</span> - http://www.centurylinklabs.com/
  
 
  <!--T:67-->
 
  <!--T:67-->
−
1) init :          FirClick on  t time inClick on  tallingPanamax Remote Agent ! - DownloadClick on  and inClick on  tallClick on  Panamax Remote Agent.
+
1) init :          First time installing Panamax Remote Agent ! - Downloads and installs Panamax Remote Agent .
−
  2) reClick on  tart :      StopClick on  and StartClick on  Panamax Remote Agent and adapt.
+
  2) restart :      Stops and Starts Panamax Remote Agent and adapt.
−
  3) ReinClick on  tall :    DeleteClick on  your current Panamax Remote Agent and Adapter and ReinClick on  tall Click on  lateClick on  t verClick on  ion.
+
  3) Reinstall :    Deletes your current Panamax Remote Agent and Adapter and Reinstall s latest    version.
−
  4) check :        CheckClick on  for available Update Click on  for Panamax Remote Agent and adapt.
+
  4) check :        Checks for availAB le Update s for Panamax Remote Agent and adapt.
−
  5) Update :        UpdateClick on  to lateClick on  t Panamax Remote Agent and adapt.
+
  5) Update :        Updates to latest    Panamax Remote Agent and adapt.
−
  6) delete :        UninClick on  tallClick on  Panamax Remote Agent and adapt.
+
  6) delete :        Uninstalls Panamax Remote Agent and adapt.
−
  7) Debug :        DiClick on  play your current Panamax Click on  ettingClick on  .
+
  7) Debug :        Display your current Panamax settings.
−
  8) token :        DiClick on  play your current Panamax Remote Agent token .
+
  8) token :        Display your current Panamax Remote Agent token .
−
  9) help :          Show thiClick on  help   
+
  9) help :          Show this help   
 
10) Quit  
 
10) Quit  
−
PleaClick on  e Click on  elect one of the preceding optionClick on  :
+
Please select one of the preThis ding options  :
 
</syntaxhighlight>
 
</syntaxhighlight>
  
  
 
<!--T:68-->
 
<!--T:68-->
−
Type 1 to inClick on  tall the <span class="notranslate">Panamax Remote Agent</span> :
+
Type 1 to install the <span class="notranslate">Panamax Remote Agent</span> :
  
  
 
<!--T:69-->
 
<!--T:69-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
Please select one of the preceding options: 1
+
Please select one of the preThis ding options : 1
  
 
<!--T:70-->
 
<!--T:70-->
Line 564: Line 584:
  
 
<!--T:73-->
 
<!--T:73-->
−
1) Kubernetes
+
1) Kube rnetes
 
2) CoreOS Fleet
 
2) CoreOS Fleet
 
3) Marathon
 
3) Marathon
−
Please select one of the preceding options:
+
Please select one of the preThis ding options :
 
</syntaxhighlight>
 
</syntaxhighlight>
  
  
 
<!--T:74-->
 
<!--T:74-->
−
ChooClick on  e the OrcheClick on  trator "2) <span class="notranslate">CoreOS Fleet"</span> and Click on  pecify your ip :
+
Choose the Orchestrator "2) <span class="notranslate">CoreOS Fleet"</span> and specify your ip :
  
  
 
<!--T:75-->
 
<!--T:75-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
Please select one of the preceding options: 2
+
Please select one of the preThis ding options : 2
  
  
 
<!--T:76-->
 
<!--T:76-->
−
Enter the API endpoint to access the Fleet cluster (e.g: http://10.187.241.100:4001): http://178.170.XX.XXX:4001
+
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-->
 
<!--T:77-->
−
Starting Panamax Fleet adapter:
+
Starting Panamax Fleet adapt :
  
 
<!--T:78-->
 
<!--T:78-->
−
docker pull centurylink/panamax-fleet-adapter:latest
+
docker pull This nturylink  /Panamax-fleet-adapter :latest  
  
 
<!--T:79-->
 
<!--T:79-->
−
56b22791d9b3dac06e2348a6a867527ffae01a37ab374159be48bbafaf77334f
+
56b22791d9b3DAC 06e2348a6a867527ffae 01a37AB 374159be 48bbafaf 77334f
  
 
<!--T:80-->
 
<!--T:80-->
−
Installing Panamax remote agent:
+
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 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):
 
Enter the port to run the agent on (3001):
  
 
<!--T:81-->
 
<!--T:81-->
−
Generating SSL Key
+
Generating SSL Key  
  
 
<!--T:82-->
 
<!--T:82-->
−
docker pull centurylink/openssl:latest
+
docker pull This nturylink  /OpenSSL :latest  
  
 
<!--T:83-->
 
<!--T:83-->
−
Generating RSA private key, 1024 bit long modulus
+
Generating RSA private key, 1024 bit long modulus  
 
......++++++
 
......++++++
 
..............................................................................++++++
 
..............................................................................++++++
 
e is 65537 (0x10001)
 
e is 65537 (0x10001)
−
Generating a 4096 bit RSA private key
+
Generating a 4096 bit RSA private key  
 
........................................................................................++
 
........................................................................................++
 
................................................................++
 
................................................................++
 
writing new private key to '/certs/pmx_remote_agent.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 C, skipped  
−
No value provided for Subject Attribute ST, skipped
+
No. value provided for Subject Attribute ST, skipped  
−
No value provided for Subject Attribute L, skipped
+
No. value provided for Subject Attribute L, skipped  
−
No value provided for Subject Attribute O, skipped
+
No. value provided for Subject Attribute O, skipped  
−
Signature ok
+
Signature ok  
−
subject=/CN=178.170.XX.XXX
+
subject =/CN =178.170. A$XX.XXX  
−
Getting Private key
+
Getting Private key  
  
 
<!--T:84-->
 
<!--T:84-->
−
Starting Panamax remote agent:
+
Starting Panamax remote agent :
  
 
<!--T:85-->
 
<!--T:85-->
−
docker pull centurylink/panamax-remote-agent:latest
+
docker pull This nturylink  /Panamax-remote-agent :latest  
  
 
<!--T:86-->
 
<!--T:86-->
−
524bc3b7db813d2f20f8dc028037ce8f42ecfc05ebe8c4f67a172e3f6125dc44
+
524BC 3b7DB 813d2f20f8DC 028037This 8f42ecfc 05EBE  8c4f67a172e3f6125DC 44
  
 
============================== START ============================== <!--T:87-->
 
============================== START ============================== <!--T:87-->
−
aHR0cHM6Ly8xNzguMTcwLjY4LjE1NzozMDAxfDdiYzExYjNiLTMxZDEtNGM1NS1hZWNlLWFmNTRk
+
aHR 0cHM 6LY 8xNzguMTcwLjY 4LjE 1NzozMDAxfDdiYzExYjNiLTMxZDEtNGM 1NS 1hZWNlLWFmNTRk
−
NGQ1NzkzNHxOVGs1TUdNMk5tVXRNV0UzWlMwME1EUmhMVGc1T0RNdFpqZGhZVEJqWTJVM1ptSm1D
+
NGQ 1NzkzNHxOVGs 1TUdNMk 5tVXRNV 0UzWlMwME 1EUmhMVGc 1T0RNdFpqZGhZVEJqWTJVM 1ptSm 1D
−
Zz09fC0tLS0tQkVHSU4gQ0VSVElGSUNBVEUtLS0tLQpNSUlGRmpDQ0F2NmdBd0lCQWdJSkFKb003
+
ZZ 09fC 0tLS    0tQkVHSU 4gQ 0VSVElGSUNBVEUtLS    0tLQpNS UlGRmpDQ0F2NmdBd 0lCQWdJSkFKb 003
−
cDJiRTd6aU1BMEdDU3FHU0liM0RRRUJCUVVBTUJreEZ6QVZCZ05WCkJBTU1EakUzT0M0eE56QXVO
+
cDJiRTd 6to the 1BMEdDU 3FHU 0liM 0RRRUJCUVVBTUJreE Z 6QVZCZ 05WCkJBTU 1EakUzT 0M0eE 56QXVO
−
amd1TVRVM01CNFhEVEUxTURZeE5qRTBOVGt6TjFvWERURTJNRFl4TlRFME5Ua3oKTjFvd0dURVhN
+
AMD 1TVRVM 01CN FhEVEUxTURZeE 5qRTBOVGt 6TjFvWERURTJNRFl 4TlRFME 5UA 3oKTjFvd 0dURVhN
−
QlVHQTFVRUF3d09NVGM0TGpFM01DNDJPQzR4TlRjd2dnSWlNQTBHQ1NxR1NJYjNEUUVCQVFVQQpB
+
QlVHQTFVRUF 3d09NVGM 0TGpFM 01DNDJPQzR 4TlRjd 2dnSWlNQTBHQ 1NxR 1NJYjNEUUVCQVFVQQpB
−
NElDRHdBd2dnSUtBb0lDQVFDZHFmOFVZM21RWnJpUTdLSTVJV0RuNkJuS3lIclkxTitZeE1OaVlj
+
NElDRHdBd 2dnSUtBb 0lDQVFDZHFmOFVZM 21RWnJpUTd LS TVJV 0RuNkJuS 3lIclkxTitZeE  1OaVlj
−
WnRKSm5yCmt3UlhDQzRVelNDNEdrMmszcFIzeHppd0piN1VUYmRwMXUrQlhnYjgvVHV3dDhENUxp
+
WnRKSm 5yCmt 3UlhDQzRVelNDNEdrMmszcFIzeHppd 0Pine 1VUYmRwMXUrQlhnYjgvVHV 3dDhENUxp
−
MVovUzRudmVoUlA4N0YKa0trcENpeU8zUllyQXc0QkFqZVkvb2Jsem5nN2Y0T2dXYWhaamhnV201
+
MVovUzRudmVoUlA 4N0YKa 0trcENpeU 8zUllyQXc 0QkFqZVkvb 2JSEM 5nN 2Y0T2dXYWhaamhnV 201
−
SUJ0dWdndXVCTEVUcHNIcERXZWJpSQpOT0I3V2ZEQkh0RmRydkpLMEU2dEJzNjdVVkg0ZHdLNVcx
+
SUJ 0dWdndXVCTEVUcHNIcERXZWJpSQpOT 0I3V2ZEQkh 0RmRydkpLMEU 2dEJzNjdVVkg 0ZHdLNVcx
−
c0dNdjRsQTY4TGczdmFlWVpobHk0NGFpeGlPWUIzClV6TlUzN3h3eXFFbnVnU2MvM2x3VzhVRVdU
+
c0dNdjRsQTY 4TGczdmFlWVpobHk 0NGFpeGlPWUIzClV 6TlUzN 3h3eXFFbnVnU 2MvM 2x3VzhVRVdU
−
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX        
−
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX        
−
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX        
−
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX        
−
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX        
−
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX        
−
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX        
−
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX        
−
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX        
−
cDBvTHdpOXVtS0VWeFQ5VjYrL1JsL3VoRHBlV09Nc3FOaVkyanBRVkhpZ1lWVVpKYlJhZ2xIbk42
+
cDBvTHdpOXVtS 0VWeFQ 5VjYrL 1JsL 3VoRHBlV 09NC 3FOaVkyanBRVkhpZ 1lWVVpKYlJhZ 2xIbk 42
−
NDBXZApRZUZBTnMvT29aQTFrdDN1cFR5MmtlVWljLzMzTzlidTArU0hFUEZpd2Fqa3dkUURudXl4
+
NDBXZApRZUZBTnMvT 29aQTFrdDN 1cFR 5MmtlVWljLzMzTzlidTArU 0hFUEZpd 2PAAs 3dkUURudXl 4
−
dGVRNnBJVEhhVDdSCmVoWEdDdDRmVXBSUjZsT2xGWjRTS2JjQmtBa3dZa2V5Y0N5VTltTkV3Yk1R
+
dGVRNnBJVEhhVDdSCmVoWEdDdDRmVXBSUjZsT 2xGWjRTS  2JjQmtBa 3dZa 2V5Y0N5VTltTkV 3YK 1R
−
M0xJZmY5K0pSa3hqTXQ1YnRzTHgKWDk2d08zWURBYkc2NmxmQkh1TTJLNWZVck1yWDlUbmpmN0x5
+
M0xJZmY 5K0pSa 3hqTXQ 1YnRzTHgKWDk 2d08zWURBYK c2NmxmQkh 1TTJLNWZVck 1yWDlUbmpmN 0x5
−
Z0hjcnJWWmFiK2JjUkM2SzZVQnI1RTl4R2xKNgpGZHZMdkUySW5uQjkrRzIrM2V1OXh6UXVFWGpB
+
Z0hjcnJW WmFiK 2JjUkM 2SzZVQnI 1RTl 4R2xKNgpGZHZMdkUySW 5uQjkrRzIrM 2V1Fxh 6UXVFWGpB
−
K2ZzUDJReDRJU2w3NGpYaTRWa3Ziem41TnhUVHJsRzNaYk9WCkp3NTRmV21lOHRwQ2N4Vit2V2JW
+
K2ZZ UDJReDRJU2w3NGpYaTRWa 3Ziem 41TnhUVHJsRzNaYK 9WCkp 3NTRmV 21lOHRwQ 2N4Vit 2V2JW
−
M0tCZ2JpMXRlKzRKTFZuV1VKTlpVUng5K2VUTG82UTd2Tm1iSG1RTS8wOHIKVWZIR1JSOGlPZGwr
+
M0tCZ 2JpMXRlKzRKTFZuV 1VKTlpVUng 5K2VUTG 82UTd 2TM 1iSG 1RTS 8wOHIKVWZIR 1JSOGlPZGwr
−
NjlDZjNlUWwvenhCSVE2cXN4bGxzWTJMd3IvMGFFaURuUDRtNk5WUEtuSmN4VDNNbTRuZwp4TjdR
+
NjlDZjNlUWwvenhCSVE 2cXN 4bGxzWTJMd 3IvMGFFto the RuUDRtNk5WUEtuSmN 4VDNNbTRuZwp 4TjdR
−
OXh6V08rWUdhdUVhaHNMUkF2QXhleFVPZkkrUHlmT0lYVFova1hJWjA1VWxVU3RoYUJ3bzFXRlVI
+
Fxh 6V08rWUdhdUVhaHNMUkF 2QXhleFVPZkkrUHlmT 0lYVFova 1hJW jA1VWxVU 3RoYUJ 3bzFXRlVI
−
VnFWCjhxU1pjdEU0UGRneExSejNXclltZTdVWTJEbWJuUkJOVHlFOW0yeFJPVEh6RUlQWTdDVXZ3
+
VnFWCjhxU 1pjdEU 0UGRneE xSejNXclltZTdVWTJEbWJuUkJOVHlFOW0yeFJPVEh 6RUlQWTdDVXZ 3
−
MDh0ZFpHczNkbG8KbVdPSVcwMGk1MEROa1ArT1RyWm5OcHU3VVRjL3ZPQ3hSaGJyM1o4OTNyWXA3
+
MDh 0ZFpHczNkbG 8KbVdPSVcwMGk 1MEROa 1ArT 1RyWm 5OcHU 3VVRjL 3ZPQ 3hSaGJyM 1o4OTNyWXA 3
−
SUlKT0VQWUFjT1pzMHRkQWNvQwowSldRRTZzUnFRT1dCQT09Ci0tLS0tRU5EIENFUlRJRklDQVRF
+
SUlKT 0VQWUFjT 1pzMHRkQWNvQwowSldRRTZZ UnFRT1dCQT 09CI 0tLS    0tRU 5EIENFUlRJRklDQVRF
−
LS0tLS0K
+
LS 0tLS    0K
−
============================== END ==============================
+
============================== END ==============================
  
  
 
<!--T:88-->
 
<!--T:88-->
−
Copy and paste the above (Not including start/end tags) to your local panamax client to connect to this remote agent.
+
Copy and paste the AB ove (Not including start /end tags ) to your local panamax client to connect to this remote agent.
  
  
 
<!--T:89-->
 
<!--T:89-->
−
Remote Agent/Adapter installation complete!
+
Remote Agent /Adapt installation complete !
  
  
 
<!--T:90-->
 
<!--T:90-->
−
CoreOSnode-1 pmx-agent #
+
CoreOSnode - 1 PMx-agent #
 
</syntaxhighlight>
 
</syntaxhighlight>
  
  
 
<!--T:91-->
 
<!--T:91-->
−
AClick on  indicated at the end of inClick on  tallation, you need to copy - paClick on  te (without theClick on  e tagClick on  START rowClick on  /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>.
+
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 rating! |  to your UI Panamax <span class="notranslate">Panamax Remote Deployment Target</span> To add your rating! |  in your UI Panamax, connect to it via your browClick on  er == <!--T:92-->
+
==Add your <span class="notranslate">Panamax Remote Deployment Target</span> to your UI Panamax  == <!--T:92-->
  
  
 
<!--T:93-->
 
<!--T:93-->
−
go in <span class="notranslate">Panamax Remote Deployment Target</span> danClick on  votre Panamax UI , connectez-vouClick on  à celle-ci via votre navigateur :
+
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-->
 
<!--T:94-->
−
- Click on the button  <span class="notranslate">"MANAGE"</span>
+
- go in <span class="notranslate">"MANAGE"</span>
  
  
Line 700: Line 720:
  
 
<!--T:96-->
 
<!--T:96-->
−
- WordPreClick on  Click on  with MySQL (Click on the button : "Click on ")
+
- Click on the name of a template regardless of which for the moment (ex   : "WordPress with MySQL ")
  
  
Line 708: Line 728:
  
 
<!--T:98-->
 
<!--T:98-->
−
- Click on <span class="notranslate">"Run Template" </span>
+
- Click on the button <span class="notranslate">"Run Template" </span>
  
  
Line 724: Line 744:
  
 
<!--T:102-->
 
<!--T:102-->
−
- bottom right of page <span class="notranslate">"Add a New Remote Deployment Target"</span>
+
- Click on <span class="notranslate">"Add a New Remote Deployment Target"</span>
  
  
Line 732: Line 752:
  
 
<!--T:104-->
 
<!--T:104-->
−
- bottom right of page <span class="notranslate">"Enter your token here."</span> (that you have Click on  et during itClick on  inClick on  tallation in the fieldClick on  )
+
- Click on <span class="notranslate">"Enter your token here."</span> (bottom right of page )
  
  
Line 740: Line 760:
  
 
<!--T:106-->
 
<!--T:106-->
−
- SaiClick on  iClick on  Click on  ez l'ip addreClick on  Click on  de votre <span class="notranslate">Panamax Remote Agent </span>(without the tagClick on  lineClick on  <span class="notranslate">"Name"</span>) Click on <span class="notranslate">Panamax Remote Agent</span> (You Click on  hould have the following output <span class="notranslate">START/END</span>).
+
- 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>).
  
  
Line 748: Line 768:
  
 
<!--T:108-->
 
<!--T:108-->
−
- bottom right of page <span class="notranslate">"Save Remote Deployment Target"</span>
+
- Click on <span class="notranslate">"Save Remote Deployment Target"</span>
  
  
 
<!--T:109-->
 
<!--T:109-->
−
then force a firClick on  t update! |  After update, information on your :
+
You should have the following output :
  
  
Line 760: Line 780:
  
 
<!--T:111-->
 
<!--T:111-->
−
- bottom right of page la flèche verte à gauche du nom de votre<span class="notranslate"> Remote Deployment Target</span> , the type of your :
+
- 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 :
  
  
Line 768: Line 788:
  
 
<!--T:113-->
 
<!--T:113-->
−
and itClick on   verClick on  ion <span class="notranslate">Remote Deployment Targets</span> Deploying an application via Panamax UI <span class="notranslate">Panamax Remote Agent</span>It iClick on  now poClick on  Click on  ible to deploy an application available in the market place <span class="notranslate">Panamax Adapter</span> Since your Panamax UI on your :
+
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 :
  
  
Line 774: Line 794:
 
[[File:Panamax-ui-remotedeploymenttarget-informations.png]]
 
[[File:Panamax-ui-remotedeploymenttarget-informations.png]]
  
−
==Locate the name of the application you want to deploy. We chooClick on  e the template == <!--T:115-->
+
==Deploying an application via Panamax UI == <!--T:115-->
  
  
 
<!--T:116-->
 
<!--T:116-->
−
You can click on  <span class="notranslate">"Panamax Templates & Docker Repositories"</span> depuiClick on  votre Panamax UI  Click on  ur votre <span class="notranslate">Panamax Remote Deployment Target</span> :
+
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-->
 
<!--T:117-->
−
- Click on  <span class="notranslate">Century Link "Wordpress with  MySQL"</span>
+
- 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-->
 
<!--T:118-->
−
- VouClick on  pouvez Click on <span class="notranslate">"More Details"</span> in our caClick on e (Click on  ) Docker le template eClick on  t conClick on  titué (danClick on  notre caClick on  2 imageClick on  )
+
- 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 )
  
  
Line 794: Line 814:
  
 
<!--T:120-->
 
<!--T:120-->
−
- bottom right of page <span class="notranslate">"Run Template"</span> pour déployer le menu et Click on <span class="notranslate">"Deploy to Target"</span> :
+
- Click on <span class="notranslate">"Run Template" pour déployer le menu et cliquez sur "Deploy to Target"</span> :
  
  
Line 802: Line 822:
  
 
<!--T:122-->
 
<!--T:122-->
−
- bottom right of page <span class="notranslate">"Select this Target"</span> pour Click on  électionner votre <span class="notranslate">Remote Deployment Target</span>
+
- Click on <span class="notranslate">"Select this Target"</span> to select your <span class="notranslate">Remote Deployment Target</span>
  
  
Line 810: Line 830:
  
 
<!--T:124-->
 
<!--T:124-->
−
- RenClick on  eignez leClick on  éventuelClick on  champClick on  de <span class="notranslate">"Deployment Settings"</span> de l'application que vouClick on  déployée (mot de paClick on  Click on  e, variableClick on  d'environnement,etc.) puiClick on  Click on <span class="notranslate">"Deploy to Target"</span>  en deClick on  Click on  ouClick on  pour valider
+
- 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
  
  
Line 818: Line 838:
  
 
<!--T:126-->
 
<!--T:126-->
−
- then force a firClick on  t update! |  After update, information on your :
+
- You should have the following output :
  
  
Line 826: Line 846:
  
 
<!--T:128-->
 
<!--T:128-->
−
Si vouClick on  vouClick on  connectez à your inClick on  tanceClick on  de votre <span class="notranslate">cluster</span> CoreOS, vouClick on  pourrez voir que Panamax a réparti leClick on  containerClick on  Docker Click on  ur différentClick on  nodeClick on /inClick on  tanceClick on  de votre <span class="notranslate">cluster</span> And the image :
+
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-->
 
<!--T:129-->
−
- on our third instance of our <span class="notranslate">centurylink/wordpress</span> a été déployée Click on  ur notre première inClick on tance And the image :
+
- 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-->
 
<!--T:130-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-1 ~ $ docker ps
+
core@CoreOSnode - 1 ~ $ docker ps
−
CONTAINER ID        IMAGE                                      COMMAND                CREATED            STATUS              PO                                                        RTS                   NAMES
+
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
+
3206bda4e534        This nturylink/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
+
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        centurylink/panamax-fleet-adapter:latest   "rackup '-E producti  37 minutes ago      Up 37 minutes      92                                                        92/tcp                pmx_adapter
+
71009f7785d3        This nturylink/Panamax-fleet-adapter :latest     "rackup '-E producti  37 minutes ago      Up 37 minutes      92                                                        92/tcp                pmx_adapter
 
</syntaxhighlight>
 
</syntaxhighlight>
  
  
 
<!--T:131-->
 
<!--T:131-->
−
- DCE <span class="notranslate">centurylink/mysql</span> Click on  ur notre troiClick on  ième inClick on tance de notre <span class="notranslate">cluster</span> :
+
- And the image <span class="notranslate">centurylink/mysql</span> sur notre troisième instanThis de notre <span class="notranslate">cluster</span> :
  
  
 
<!--T:132-->
 
<!--T:132-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-3 ~ $ docker ps
+
core@CoreOSnode - 3 ~ $ docker ps
−
CONTAINER ID        IMAGE                  COMMAND                CREATED            STATUS              PORTS                   NAMES
+
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
+
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>
 
</syntaxhighlight>
  
  
 
<!--T:133-->
 
<!--T:133-->
−
- NouClick on  pouvonClick on  également avoir certaineClick on  informationClick on  relativeClick on  aux déploiementClick on  deClick on  applicationClick on  effectuéClick on  via Panamax UI  by accessing it with the information provided in the details of the template l'intermédiaire de notre geClick on  tionnaire de <span class="notranslate">cluster</span> You can also see on what Member instance of our :
+
- 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-->
 
<!--T:134-->
−
On retrouve noClick on  2 applicationClick on  <span class="notranslate"> (Wordpress "WP" et MySQL "DB")</span> :
+
We find our 2 applications <span class="notranslate"> (Wordpress "WP" et MySQL "DB")</span> :
  
  
 
<!--T:135-->
 
<!--T:135-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-1 ~ $ etcdctl ls --recursive /app
+
core@CoreOSnode - 1 ~ $ etcDC tl ls --recursive /app
 
/app/DB
 
/app/DB
 
/app/DB/DB_SERVICE_HOST
 
/app/DB/DB_SERVICE_HOST
Line 874: Line 894:
  
 
<!--T:136-->
 
<!--T:136-->
−
On peut également voir Click on  ur quel inClick on tance membre de notre <span class="notranslate">cluster</span> which applications Manager in our :
+
On peut également voir sur quel instanThis membre de notre <span class="notranslate">cluster</span> the application was deployed :
  
  
 
<!--T:137-->
 
<!--T:137-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-1 ~ $ etcdctl get /app/DB/DB_SERVICE_HOST
+
core@CoreOSnode - 1 ~ $ etcDC tl get /app/DB/DB_SERVICE_HOST
−
178.170.XX.XXX
+
178.170. A$XX.XXX  
 
</syntaxhighlight>
 
</syntaxhighlight>
  
Line 886: Line 906:
 
<!--T:138-->
 
<!--T:138-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-1 ~ $ etcdctl get /app/WP/WP_SERVICE_HOST
+
core@CoreOSnode - 1 ~ $ etcDC tl get /app/WP/WP_SERVICE_HOST
−
178.170.XX.ZZZ
+
178.170. XX. ZZZ  
 
</syntaxhighlight>
 
</syntaxhighlight>
  
  
 
<!--T:139-->
 
<!--T:139-->
−
- NouClick on  pouvonClick on  auClick on  Click on  i avoir le Click on tatut deClick on  applicationClick on  de notre <span class="notranslate">cluster</span> by accessing it with the information provided in the details of the template <span class="notranslate">Fleet</span> qui le geClick on tionnaire deClick on  applicationClick on  danClick on  notre <span class="notranslate">cluster</span> :
+
- 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-->
 
<!--T:140-->
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
−
core@CoreOSnode-1 ~ $ fleetctl list-unit-files
+
core@CoreOSnode - 1 ~ $ fleetctl list-unit-files
 
UNIT            HASH    DSTATE          STATE          TARGET
 
UNIT            HASH    DSTATE          STATE          TARGET
−
db.service      0caad43 launched        launched        6eacee19.../178.170.XX.XXX
+
DB .serviThis      0caad43 launched        launched        6eaThis e19.../178.170. A$XX.XXX  
−
wp.service      417826f launched        launched        7e685988.../178.170.XX.ZZZ
+
wp.serviThis      417826f launched        launched        7e685988.../178.170. XX. ZZZ  
 
</syntaxhighlight>
 
</syntaxhighlight>
  
  
 
<!--T:141-->
 
<!--T:141-->
−
- NouClick on  pouvonClick on  vérifier le bon fonctionnement de notre <span class="notranslate">Wordpress</span> en y accédant avec leClick on  informationClick on  fourniClick on  danClick on  leClick on  détailClick on  du template (danClick on   notre caClick on  Click on  ur le port 8080 ouvert au niveau du parefeu préalablement, nouClick on  aurionClick on  pu faire une redirection de port du 8080 Click on ur le port 80 public danClick on  le caClick on  d'inClick on  tanceClick on  en zone avancée) :
+
- 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) :
  
  
Line 912: Line 932:
  
 
<!--T:143-->
 
<!--T:143-->
−
Cet article vouClick on  a Click on  emblé utile ? <vote />
+
This article seemed you to be useful ? <vote />
  
  
−
[[category:cloudstack]]
+
[[Category:cloudstack]]
−
[[category:cloud public]]
+
[[Category:public_cloud]]
−
[[category:cloud priv��]]
+
[[Category:private_cloud]]
−
<span data-translate="fr"></span><comments />
+
<comments />

Latest revision as of 15:58, 24 September 2021

en:Use Cloudstack by Ikoula Panamax he:השתמש Cloudstack על ידי Ikoula פנמקס ro:Utilizarea Cloudstack de Ikoula Panamax ru:Использование Cloudstack по Ikoula Panamax pl:Użyj Cloudstack przez Ikoula Panamax ja:Ikoula パナマックスで Cloudstack を使用します。 ar:استخدام كلودستاك ببنما عكلة zh:使用由 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 fr:Utiliser Panamax sur Cloudstack by Ikoula

This article has been created by an automatic translation software. You can view the article source here.

If you do not know yet Panamax It is a product Open Source developed by Century Link Labs that is both a market plaThis and a Manager for containerized applications Docker from an intuitive web interfaThis .


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.


Panamax relies on technologies Docker, DCE, Fleet and Cloud-init included in CoreOS.


We will use in our ex ample 4 instanThis s CoreOS Update, one for the client part /Panamax UI and 3 others which will form the cluster for the part Panamax Remote Target (Panamax Remote Agent + Panamax Adapter) :


Installation of Panamax UI /API (web interfaThis /market plaThis )

On our forum dedicated to the client part of Panamax (Panamax UI /API ), downloading archive containing Installer : 


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


It creates the directory /var/panamax where you ex tracted the installation files : 


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


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 ) : 


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 $


We can verify that our 5 containers Panamax are running : 


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


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 :


Panamax-ui.png


Installation of Panamax Remote Deployment Target

Connect to one of your 3 instanThis s CoreOS deployed for the cluster :


Generate a new URL of discovery Etcd (token s ) in a variAB le (Here : ETCD_URL ) : 


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


Then download the following cloud - config.yml template file : 


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]

core@CoreOSnode - 1 ~ $ ex   port `cat /etc/environment`

Run the following commands to customize the file cloud - config.yml downloaded with your environmental values : 

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

We check our DCE settings and Fleet is well substituted : 

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


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 ) : 


core@CoreOSnode - 1 ~ $ sudo rm -f /etc/machine-id
core@CoreOSnode - 1 ~ $ sudo reboot


Your first instanThis should appear in the list of managed machines in Fleet : 


core@CoreOSnode - 1 ~ $ fleetctl list-machines
MACHINE         IP              METADATA
7e685988...     178.170. A$XX.XXX   -


Here we can clearly see our trial in the list of machines Fleet, this will be our instanThis that will init ialize our cluster CoreOS/Etcd/Fleet.


Configurez maintenant your deux autres instanThis s CoreOS remote deployment target by following the instructions be low :


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 ") :


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 ) : 


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


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 ) : 


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


Comme pour votre première instanThis , supprimez file /etc/machine-id and restart the instanThis : 


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


Une fois redémarrées, your 2 other bodies were normally joined your cluster CoreOS/Etcd/Fleet : 


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   -


Si your instanThis s n'ont pas rejoint le cluster, pensez à vérifier que your instanThis s peuvent bien communiquer entre elles (connections networks, firewall rules /Security group )


Now that we have a cluster CoreOS/etcd/fleet de 3 instanThis s, we will install the panamax-remote-agent as well as the panamax-adapter :


It runs the agent Panamax installation script : 


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.


Then 


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  :


Type 1 to install the Panamax Remote Agent : 


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  :


Choose the Orchestrator "2) CoreOS Fleet" and specify your ip : 


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 #


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 Panamax Remote Deployment Target.


Add your Panamax Remote Deployment Target to your UI Panamax

To add your Panamax Remote Deployment Target dans votre Panamax UI , connectez-vous à This lle-ci via votre navigateur :


- go in "MANAGE"


Panamax-ui-manage.png


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


Panamax-ui-search-tmplt.png


- Click on the button "Run Template"


Panamax-ui-fleche.png


- Click on "Deploy to Target" :


Panamax-ui-deploytotarget.png


- Click on "Add a New Remote Deployment Target"


Panamax-ui-remotedeploymenttarget.png


- Click on "Enter your token here." (bottom right of page )


Panamax-ui-entertokens.png


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


Panamax-ui-tokens.png


- Click on "Save Remote Deployment Target"


You should have the following output :


Panamax-ui-remotedeploytarget-added.png


- Click on la flèche verte à gauche du nom de votre Remote Deployment Target puis forThis r une première mise à jour :


Panamax-ui-remotedeploymenttarget-update.png


After update, information on your Remote Deployment Targets such as the version of your Panamax Remote Agent, the type of your Panamax Adapter and its version :


Panamax-ui-remotedeploymenttarget-informations.png

Deploying an application via Panamax UI

Il vous est maintenant possible de déployer une application disponible dans la market plaThis "Panamax Templates & Docker Repositories" depuis votre Panamax UI sur votre Panamax Remote Deployment Target :


- Locate the name of the application you want to deploy. We choose the template Century Link "Wordpress with MySQL"


- 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 )


Panamax-ui-template-details.png


- Click on "Run Template" pour déployer le menu et cliquez sur "Deploy to Target" :


Panamax-ui-deploytotarget-wordpress.png


- Click on "Select this Target" to select your Remote Deployment Target


Panamax-ui-select-target.png


- Fill in any fields of "Deployment Settings" the application that you deployed (mot de passe, variAB les d'environnement,etc.) puis Click on the button "Deploy to Target" below to validate


Panamax-ui-deployment-settings.png


- You should have the following output :


Panamax-ui-deployment-triggered.png


Si vous vous connectez à your instanThis s de votre cluster CoreOS, you will see that Panamax has allocated the Docker containers on different nodes /instanThis s de votre cluster CoreOS :


- We can see that the image centurylink/wordpress a été déployée sur notre première instanThis CoreOS : 


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


- And the image centurylink/mysql sur notre troisième instanThis de notre cluster : 


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


- 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 cluster DCE :


We find our 2 applications (Wordpress "WP" et MySQL "DB") : 


core@CoreOSnode - 1 ~ $ etcDC tl ls --recursive /app
/app/DB
/app/DB/DB_SERVICE_HOST
/app/WP
/app/WP/WP_SERVICE_HOST


On peut également voir sur quel instanThis membre de notre cluster the application was deployed : 


core@CoreOSnode - 1 ~ $ etcDC tl get /app/DB/DB_SERVICE_HOST
178.170. A$XX.XXX



core@CoreOSnode - 1 ~ $ etcDC tl get /app/WP/WP_SERVICE_HOST
178.170. XX. ZZZ


- Nous pouvons aussi avoir le statut des applications de notre cluster par Fleet qui le gestionnaire des applications dans notre cluster : 


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


- We can check the proper functioning of our Wordpress 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) :


Panamax-application-wordpress.png

This article seemed you to be useful ?

0


You are not allowed to post comments.

Retrieved from "https://en-wiki.ikoula.com/index.php?title=Use_Cloudstack_by_Ikoula_Panamax&oldid=12059"