[Fiware-lab-help] R: Can't access VM from outside

Cipriani Marco marco2.cipriani at telecomitalia.it
Thu May 7 17:24:53 CEST 2015


Dear Laszlo,
about the password issue, as reported in the mail sent to all users to remind the installation of the new Idm component (scheduled for today), “during the deployment of the new IdM GE, we have to reset all the user passwords. So please, in order to continue using your account, you have to use the “Forgot password” option in the log in page of the FIWARE Lab Account Portal".

About the other points, the same mail sent to the FIWARE users said:
“On the official FIWARE Lab cloud environment based on the new IdM GE deployed on May 7th, only the "default" organization linked to a given FIWARE account will be visible as "projects" (i.e., tenants) in the cloud environment.  Organizations created through the Account Portal of the FIWARE Lab will not be mapped into "projects" in the cloud of the FIWARE Lab.   The name of the default organization linked to your account will be "<your username> cloud" (for instance “user1 cloud") although you will be able to modify it.   Take into account that other organizations will not be mapped to "projects" on the Cloud Portal anymore and, in their case, this will mean that the associated resources will be lost.   Therefore, VERY IMPORTANT, you should migrate all the cloud resources (VMs, etc) you may have defined linked to organizations different than the organization linked as default to your account and do it before May 7 (name of the default organization linked to your account should currently map to your account user name).  After that date, FIWARE Lab providers will not be responsible for the loss of any data.”

So, it seems exactly the behavior that you are experiencing.
I’m very sorry for the inconvenience.

Best regards
Marco



Da: atleta at atleta.hu [mailto:atleta at atleta.hu] Per conto di László Márai
Inviato: giovedì 7 maggio 2015 16:37
A: Cipriani Marco
Cc: fiware-lab-help
Oggetto: Re: [Fiware-lab-help] Can't access VM from outside

  Hi Marco,
Something really strange happened. When trying to log in to my account to get my project ID, the website was asking for a password again (I should have had a valid session). Then it didn't accept my password (the password was saved in both the browser and my password manager, so no way I have 'forgotten it'). Then after changing my password and logging in it asked in I authorize the cloud application (which I have used before), then I'm not seeing my instances and the only region I see is Spain2. Also, I can't see our organization (PsychAsk) I created before (like months ago). Now I'm only member of a project that is the same as my name ( project laszlo-marai cloud (ID 00000000000000000000000000009481)  ). I don't know what it is, but it doesn't look right.
  Thanks for your help,
    Laszlo

On Thu, May 7, 2015 at 4:11 PM, Cipriani Marco <marco2.cipriani at telecomitalia.it<mailto:marco2.cipriani at telecomitalia.it>> wrote:
Dear Laszlo,
please could you provide us your project ID (your email account is not enough)?  It can be found selecting your project name and looking at the info bar in the bottom of the page, something like <project-name> (ID 00000000000000000000000000000xyz).

Meanwhile, I will forward your request to the Budapest support team.

Best regards
Marco


Da: fiware-lab-help-bounces at lists.fi-ware.org<mailto:fiware-lab-help-bounces at lists.fi-ware.org> [mailto:fiware-lab-help-bounces at lists.fi-ware.org<mailto:fiware-lab-help-bounces at lists.fi-ware.org>] Per conto di László Márai
Inviato: giovedì 7 maggio 2015 15:51
A: fiware-lab-help
Oggetto: [Fiware-lab-help] Can't access VM from outside

   Hi,

I've created a few VM instances on the Budapest node and access them from the outside (tried to do so in other regions as well, with less success) without any luck. Here's what I did:
1., created a security group with port 22 open (among others)
2., launched an instance using one of the images, adding it to the above security group
3., associated a floating IP to one of the internal interfaces (tried both 10.10.xxx and 10.20.xxx)
4., tried to connect from my machine, and received a "no route to host" error
I also tried setting up my own network (it's not clear whether it's necessary or not):
1., create a new network (192.168.x.x/24)
2., create a router and set the external network to the one that contains my public IP ( public-ext-net-01)
3., launch a new VM instance and the network created in step 1 to it
4., associate floating IP
5., try to ssh -> no route to host
My filab user id is the same as I'm sending this email from (I don't know if it's a requirement for getting a feedback for the reports or not).

  Thanks,
    Laszlo
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

[rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20150507/019f4ca5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo Ambiente_foglia2.jpg
Type: image/jpeg
Size: 677 bytes
Desc: logo Ambiente_foglia2.jpg
URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20150507/019f4ca5/attachment.jpg>


More information about the Fiware-lab-help mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy