Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Component/s: FI-C3
-
Labels:None
Description
Hi,
After having successfully install, configure and use the different GEs locally we are now trying and having difficulties to setup a environment on the cloud storage.
You can find below an email of our main developper with explanations.
Thank you for your help.
Sanawar Syed
Operating Partner
site web
email
phone www.m4ke.it <http://www.m4ke.it/>
sanawar.syed@m4ke.it <sanawar.syed@m4ke.it>
+32 (0) 484 74 04 44 <phone:0484740444>
> Begin forwarded message:
>
> From: Robin Poncin <robin.poncin@gmail.com <robin.poncin@gmail.com>>
> Subject: Fiware - Questions
> Date: 18 March 2016 at 12:15:01 GMT+1
> To: Sanawar Syed <sanawar.syed@m4ke.it <sanawar.syed@m4ke.it>>
>
>
> 1) PEP Proxy Wilma
>
> After installing successfully the PEP Proxy <http://catalogue.fiware.org/enablers/pep-proxy-wilma> in a local environment (and testing it with Oauth2 token from https://account.lab.fiware.org/oauth2/token <https://account.lab.fiware.org/oauth2/token>), we wanted to implement it in the cloud storage of Fiware.
> According to the documentation, the GE should be installed from the "pep-proxy-image" :
> <install-pep.png>
>
> The problem is that the image seems to be missing from the images list in the cloud portal :
> <pep-missing.png>
> 2) Cloud storage
>
> Since we only have one floating IP to allocate to one of our instance, it seems that we should use networks and subnets to be able to install multiple GE in the cloud storage.
> Unfortunately, we're unable to create either a new network or to add another subnet in the already existing networks :
>
> <cant-create-network.png>
>
> <cant-create-subnet.png>
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-fic3-coaching@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-fic3-coaching mailing list
Fiware-fic3-coaching@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-fic3-coaching
[Created via e-mail received from: Sanawar Syed Azor Ali <sanawar.syed@m4ke.it>]
Dear Robin, Syed,
I checked with my colleagues. Here are the answers:
*Cloud Storage Problem : *
As far as we know, the creation of network in the Fiware cloud options never worked in any node
There is one way to use one IP address for many VMs. Take a look at this link, a user has encountered the same problem and offers a great solution :
http://joseignaciocarretero.blogspot.com.es/2014/09/fiware-lab-only-one-single-ip-per-user.html
To summarize, it is just port forwarding from one machine to the machines that are in the same local network (ex : Fiware Spain node)
*PEP Proxy : *
The instances of PEP on the FIWARE cloud are not necessarily given.
Depending on the node that you are working on present images can be outdated/missing.
What we recommend is to go from a clean Base OS like Ubuntu or Centos, and install the PEP Proxy following those instructions : http://fiware-pep-proxy.readthedocs.org/en/latest/admin_guide/#system-installation
Kind regards
Franck