Hi Vuk, please find below the responses from two of the nodes. I saw that Lannion node already contacted you directly. I hope that these answers will help you. If the other nodes will still reply I’ll forward the answers to you. I’ll close this ticket now. If you need further help don’t hesitate to send an email to helpdesk again. Best regards, Uwe -------------------------------- Info from Prague node: creating VMs in Prague works fine according to our tests. There is the long-standing inability to allocate public IPv4 address, but that's expected because they are all allocated to tenants or VMs most of the time. It's unfortunate, but it's a direct result of a policy decision which was to allow tenants to allocate up to one IPv4 address on a self-service basis, with no prior justification. The user appears to have troubles deploying blueprints form the Cloud Portal. We do not have access to error logs from the Cloud Portal, and as such we cannot really help troubleshoot problems that users might have with it. To the best of our knowledge, API calls to our OpenStack controller result in VMs being created and deployed, so the problem is apparently elsewhere. I'd also like to point out that I filed a ticket [1] about the central Keystone being unreachable earlier today; that might be related to the issue at hand. ------------------------------ Info from Budapest node: In the Budapest node there were some issues with nfs on Monday (as reported to the help desk), and we also noticed that there were no free IPs in the shared network, resulting in error during the instance creation. Both issues have been solved by now. So, Budapest node is back again. ------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20150114/7f4c3915/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy