Hi Tero,
Stockholm support reads your reporting. So they will perform the needed
checks. Regarding DNS, I think this is the default behaviour when using
private networks: you need to define one yourself.

Best,
Federico

–
–
Future Internet is closer than you think!
http://www.fiware.org

Official Mirantis partner for OpenStack Training
https://www.create-net.org/community/openstack-training

–
Dr. Federico M. Facca

CREATE-NET
Via alla Cascata 56/D
38123 Povo Trento (Italy)

P +39 0461 408400 (2471)
M +39 334 6049758
E federico.facca@create-net.org
T @chicco785
W www.create-net.org

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

Hi Tero,

We have started to look into your problem. From what we can see, both of you VMs respond to ssh initiation requests (or at least the IPs do). We are aware that the VNC console service doesn't work in our environment yet. As for your problem with the DNS resolv, this is done when you create your subnet (there is a field for the DNS server that you want to use).

We'll get back to you once we have fully investigated your problem.

With Best Regards,

Stéphane Junique

Removing Prague from Cc, this appears to not be related to us.

Hi,

As the unclear situation troubled me and I once again compared settings
of working and unworking setup. For me configuration of instances and
networks looked similar, however I found one thing:

Not working setup didn't have dhcp entry in network/subnet/ports
(b609512c) 192.168.105.2 compute:None ACTIVE UP (d35dd92d) 192.168.105.1
network:router_interface ACTIVE UP

But working setup had.

(70bac380) 192.168.110.1 network:router_interface ACTIVE UP (9076f370)
192.168.110.3 compute:None ACTIVE UP (ac9fda2b) 192.168.110.2
network:dhcp ACTIVE UP

Checkbox for enabling DHCP was on on both networks.

I didn't have any idea how to resolve situation. Is there way to define
a new network for already created instance?

So I tried again creating network and instance from the beginning. And
this time 'network:dhcp' appeared to network/subnet/ports and I managed
to use floating IP and ssh to connect this new instance.

Regards, Tero Vuorela

I have got answer to my earlier post and I was instructed to use either
Budapest or Prague regions. I tested those:

• Budapest: Instance creation fails here too like I have described
  below. Deployment starts but ends to simple ERROR. No additional
  information.

• Prague: I managed successfully launch instance but I'm unable to
  allocate IP. There I get reasonable error message Error allocating IP
  address. Cause: 404 Error {"itemNotFound": {"message":
  "NoMoreFloatingIps: Zero floating ips available.", "code": 404}} How
  ever when "Allocate Floating IP" dialog is open quota said that there
  is one available.

I systematically went through all regions and (just for me?) all but
Poznan failed in away or another: either VM launching results to error
or floating IPs can't be assigned. On Poznan region I managed to connect
a launched VM with ssh.

I still wonder is this a general error situation, or is it just me who
is experiencing these problems.

Regards Tero Vuorela

----- Original message ----- From: Tero Vuorela <tero.vuorela@iki.fi>
To: fiware-lab-help@lists.fi-ware.org Subject: Failed to launch new
instances Date: Sat, 10 Jan 2015 10:30:43 +0200

Hi,

I trying to launch new instances in Fi-Lab but for some reason launching
fails every time and instance gets into error state. See attached
screenshot. I can't find any additional information for the error.

I tried different regions and different instances, but a result is
same: ERROR

I originally had a test instance running on Spain region, that was
launched in October but I deleted it as I couldn't anymore find
keypair, and understood that you can't associate new keypairs to
existing instance.

Is there a general problem in Fi-Lab, or am I just missing some step?

Regards, Tero Vuorela
Fiware-lab-help mailing list

Please update your address book with my new e-mail address:
miguel.carrillopacheco@telefonica.com

----------------------------------------------------------------------
/ _// Miguel Carrillo Pacheco _/ _/ _/ _/ Telefónica Distrito
Telefónica / _//_/ _/ _/ Investigación y Edifico Oeste 1, Planta
9 / _/ _/ _/ Desarrollo Ronda de la Comunicación S/N _/ _// 28050
Madrid (Spain) Tel: (+34) 91 483 26 77[3]

e-mail: miguel.carrillopacheco@telefonica.com

Follow FIWARE on the net

Website: http://www.fiware.org Facebook:
https://www.facebook.com/eu.fiware Twitter:
http://twitter.com/Fiware LinkedIn:
https://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
puede contener información privilegiada o confidencial y es para uso
exclusivo de la persona o entidad de destino. Si no es usted. el
destinatario indicado, queda notificado de que la lectura, utilización,
divulgación y/o copia sin autorización puede estar prohibida en virtud
de la legislación vigente. Si ha recibido este mensaje por error, le
rogamos que nos lo comunique inmediatamente por esta misma vía y proceda
a su destrucción.
The information contained in this transmission is privileged and
confidential information intended only for the use of the individual or
entity named above. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this communication is strictly prohibited. If you have
received this transmission in error, do not read it. Please immediately
reply to the sender that you have received this communication in error
and then delete it.
Esta mensagem e seus anexos se dirigem exclusivamente ao seu
destinatário, pode conter informação privilegiada ou confidencial e é
para uso exclusivo da pessoa ou entidade de destino. Se não é vossa
senhoria o destinatário indicado, fica notificado de que a leitura,
utilização, divulgação e/ou cópia sem autorização pode estar proibida em
virtude da legislação vigente. Se recebeu esta mensagem por erro,
rogamos-lhe que nos o comunique imediatamente por esta mesma via e
proceda a sua destruição

–
Tero Vuorela tero.vuorela@iki.fi

Links:

1. https://cloud.lab.fiware.org/#neutron/networks/9550acfc-e9e3-4b2b-9646-4d604582493b
2. https://forge.fi-ware.org/
3. tel:%28%2B34%29%2091%20483%2026%2077
4. tel:%2B39%200461%20408400
5. tel:%2B39%20334%206049758
6. tel:%2B39%200461%20408400
7. tel:%2B39%20334%206049758
8. tel:%2B39%200461%20408400
9. tel:%2B39%20334%206049758

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

Hi Tero,

It seems not to be a DHCP problem, if you still experience problems of the same nature please file a new ticket.

B.R
Roland Elverljung, Stockholm node