Dear José Antonio,

The spanish region has run out of resources, so it won't instanciate any VMs at this moment.

Best regards,
José Ignacio.

El 16/12/14 a las 20:23, José Alé escribió:
Dear helper
Currently I'm triying to launch a VM in order to test an IoT deployment over FiWare, but all instances tried to launch ends with "ERROR" status
I've tried in Seville, Trento, Lanion, Mexico... Some times some more information is given, others just "Error"

Could you plese help me?
I know Spain Region is "full", but is it possible to deploy any instance somewhere else?

Thank you

Dear Jose Antonio,
I tested Waterford, to me it seems working. There may be just some
issues still on SDC - central service - since I could not add software
to a VM. I opened a ticket for that issue.

Best,
Federico

Just tried on Waterford too, same problem.
from "instance->overview"
"

• *Name: * iotbroker
• *ID: * e282524c-74b9-4a46-b4fc-71ee1b4d673d
• *Status: * ERROR

"

I'll try again tomorrow

Thanks for your quick answers!

2014-12-16 21:50 GMT+01:00 Federico Michele Facca <

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

hi jose,
to be honest i tested a basic image but there should be no difference.

i suspect the issue may not be the node as such. nodes with neutron
network are a bit more complex to configure.

1. select the network pane and create a network including a subnet
(e.g. 192.168.12.0/24)
2. select the router pane and create a router
3. select the created router and set the default gateway
(XIFI-public-WIT-00) - unfortunately a bug in the portal will refresh
the whole app
4. click on the created router and select the interface pane; add as
interface the subnet of your network
5. click on security pane, select keypar panel, create a keypar
6. select floating ip panel, and allocate a public ip to the project
7. click on image pane, select iotbroker and click launch: settings
flavour m1, the keypair created, and the network create. (wait the vm
to be active)
8. click on the secutiry panel, select the floating IPs, and attach
the reserved IP to your vm

voilet

cheers,
federico

PS: also flavours matter, unfortunately openstack does not have a default
mechanism to map "minimal" requirements of an image to a flavour. so if
your vm to start needs 2Gb and you a flavour with 1GB, the vm may fail to
start without you really realising what is wrong. we surely need to improve
this.

Thank you very much for your very helpful answers

I think my notes are completely outdated, or simply wrong, as there were no
references to routers on them.

Now the VM is up and running.

Thanks for the help!

2014-12-16 23:58 GMT+01:00 Federico Michele Facca <

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