Commit 89226390 authored by Sergio Gimenez's avatar Sergio Gimenez
Browse files

Update docs

parent f73e9d31

docs/quick-start.md

+8 −3
Original line number Diff line number Diff line
@@ -92,7 +92,6 @@ Then, install i2ede 
!!! warning

    This is playbook does many workarounds to be able to deploy i2edge on the cluster such as rsync the code to the VM and build the image and then add it to the cluster. This is ugly and needs to be fixed, but works for now.





```bash

ansible-playbook playbooks/02-deploy-i2edge.yml

```
@@ -116,7 +115,6 @@ ansible-playbook playbooks/02-deploy-harbor.yml 


## Deploy Artefact Manager





To deploy the artefact manager:



```
@@ -137,7 +135,6 @@ ansible-playbook playbooks/04-deploy-federation-manager.yml 
!!! success

    If everything went fine, federation manager API should be accessible directly in http://VM_IP:30989.





## Deploy a Second Federation Manager



Federation Manager needs another federation manager for almost all the operations, so it makes sense to deploy a second federation manager:
@@ -148,3 +145,11 @@ ansible-playbook playbooks/04-deploy-federation-manager.yml 


!!! success

    If everything went fine, federation manager API should be accessible directly in http://VM_IP:30990.



## Deploy a Dashboard



Since we are deploying many services, it comes very handy to have a dashboard to monitor them all in one place. So we provide a playbook to deploy the Operator Platform Dashboard. It will be deployed using Homer, a static homepage for your server. The dashboard will be accessible in http://VM_IP:30088.



```bash

ansible-playbook playbooks/05-deploy-homer.yml

```
 
 No newline at end of file