Dear FIWARE coach,
we forward you an update from a CreatiFI applicant we are not able to solve.
Starting from today, the CreatiFI companies will show their final prototype
in order to get the last money trance in the CreatiFI accelerator project ,
so ask FIWARE owner to fix the issue ASAP, please.
Please let us know if you need direct contact with the submitter.
Thanks.

**************************

Dear,

We have found our instances in Images section and have redeployed them in
FILAB (with new security rules and keypair). We have also set our private
network the same way as before (using provided new floating IP as external
network on the router).

However, we cannot SSH into the VM with associated IP. We get same errors.
Seems that router, DNS setting or something else is not working properly.
But, I have also tried associating IP to VM that is deployed in default
(node-int-net-02) network, and I get same errors.

When IP is associated with VM in newly made private network I get this from
specs:

IP Addresses
reactifi: 192.168.21.6
reactifi: 193.205.211.***

When IP is on different VM within default network it says:

IP Addresses
node-int-net-02: 192.168.111.18
node-int-net-02: 193.205.211.***

My guess is that floating IP is faulty, but I'm by no means expert in this.

What could be done?

**************************

On Mon, Aug 24, 2015 at 8:37 AM, Andrea Maestrini <amaestrini@create-net.org

_______________________________________________
Fiware-creatifi-coaching mailing list
Fiware-creatifi-coaching@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-creatifi-coaching

Dear,
any news about this issue?

BR

On Tue, Aug 25, 2015 at 2:18 PM, Andrea Maestrini <amaestrini@create-net.org

_______________________________________________
Fiware-creatifi-coaching mailing list
Fiware-creatifi-coaching@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-creatifi-coaching

The issues afflicting the vms reachability have been restored..
The user has been notified. Waiting for feedback

Dear,
following an update from the applicant:

********************************

Dear,

I have tried reaching the IP provided in the Lab (from public-ext-net-01
pool) but get "no route to host" as before. If I release IP and assign new
one from public-ext-net-02 I get timeout request.

Right now, I have assigned new IP from pool 01 and still get no route to
host each time. Maybe it is the case because we have private network, but
as far as I can tell we have set everything as it was before when it worked.

Tnx.

********************************

On Wed, Sep 2, 2015 at 8:46 AM, Andrea Maestrini <amaestrini@create-net.org>

_______________________________________________
Fiware-creatifi-coaching mailing list
Fiware-creatifi-coaching@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-creatifi-coaching

Dear Andrea,

Which is the affected node?

Ciao
Stefano
Il 07/Set/2015 08:28, "Andrea Maestrini" <amaestrini@create-net.org> ha

_______________________________________________
Fiware-creatifi-coaching mailing list
Fiware-creatifi-coaching@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-creatifi-coaching

This ticket can be closed (user gave positive feedback).