Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
HD-Node:Budapest
Description
Dear Fiware Lab team,
I would like to ask whether the FI-Lab is fully functional, since in
the past days (today and yesterday) I was not able to set up a virtual
machine and associate an IP address so that it would result in a
reachable VM.
I was trying in different regions marked as healthy (Spain2,
Berlin2, Budapest2), with a MiWi-POI instance. I followed the various
technical tutorials regarding the process (security group, open ports
20, 80, 8080, keypair generation, launch instance, allocate IP,
associate IP, reboot). (It is worth mentioning that I was able to
execute the process previously.) In the Spain2 region I got 503, and
various other errors at almost every step. At Berlin2 and Budapest2 I
did not get any errors, but the associated floating IP cannot be pinged,
not even from mobile internet. Both public and federation pool adresses
were checked. The account is registered as jmarias@loginet.hu.
It is always possible that I missed something important, but it
starts to feel like there is a problem beyond my reach.
Kind regards,
Bence Horváth, [Loginet Systems Kft.]
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
[Created via e-mail received from: bhorvath@loginet.hu]
Issue Links
- clones
-
HELP-3143
FIWARE.Request.Lab.Budapest.Fiware Lab status.
-
- Closed
-
Activity
Already answered on 29th May 2015:
Dear Sándor,
thank You for your quick and specific answer. The suggested solution works flawlessly. It looks like the problem was caused by my lack of FI-Lab related knowledge after all, thus I wish to apologize for the inconvenience.
Kind regards,
Bence
2015-05-29 15:29 időpontban Sándor Laki ezt írta:
> Dear Bence,
>
> I have just forwarded your reply to the operators of Spain and Berlin
> nodes.
>
> With respect to Budapest, I checked your instance and I see the
> problem:
>
> 1. Your instance looks like:
> | 954a5229-ea8b-4345-a10f-73f95cf8afcf | test
> | ACTIVE | - | Running |
> node-int-net-02=192.168.2.15, 10.0.207.13
>
> 2. the problem is that the used 10.0.207.13 is not a public IP, it
> belongs to a VPN spanned between various FIWARE Lab sites. So through
> this network you can interconnect VMs deployed in different regions
> via this private network.
> 3. How to solve the issue:
> First of all, use node-int-net-01 for public domains, or create your
> own network. Note node-int-net-02 cannot be connected to the Internet.
> Secondly, choose a floating IP from public-ext-net-01 that can be
> assigned to network interfaces from node-int-net-01 or private
> network.
> After that you can reach your VM.
>
> Sorry for the confusion. We will rename this second vpn network to
> avoid such problems.
>
> If you have any further issues, please do not hesitate to contact us.
> Best,
> Sandor
As far as I can see you have the trial user status. Referring to the internal policies, trial users want get a public IP anymore on the Berlin node because of limited resources. You can apply to become a community user. Please have a look at the Terms & Conditions.
http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_LAB_Terms_and_Conditions
Sorry for any inconvenience this might cause.