Hi, Thank you very much for the prompt reply. Best, Stratos On 2/17/14 11:45 AM, "José Ignacio Carretero Guarde" <jicg at tid.es> wrote: >Hi, > >You simply can't use our DNS. You could ask us for a name and we would >study if your requirement can be accomplished. > >You can consider your floating IPs to be yours, as they are part of the >resources of your project, hence, as long as you don't release the >floating IP it is yours and you can use it in any VM you want. But >please, use the IP or it might be removed from your project as a "leak" >in the resources. > >The public IPs are "static" in the life of your VM. As soon as you >destroy your VM, you may or may not get the same ip for anohter VM. > >Best regards, >José Ignacio. > >El 17/02/14 10:34, Efstratios Tzoannos escribió: >> Hi Jose, >> >> Thank you very much for your help. One more question: can we assure that >> the ip given to the instances is static? >> >> Alternatively, is there a DNS to associate domain names to floating IPs >> inside the fil-lab cloud? How can we use it? >> >> Best, >> Stratos >> >> On 2/14/14 2:03 PM, "Thanasis Dalianis" <T.Dalianis at atc.gr> wrote: >> >>> Hi Jose, >>> >>> Thank you for your assistance, now it works fine. >>> >>> Best >>> Athanasios >>> >>> On 2/14/14, 1:30 PM, "José Ignacio Carretero Guarde" <jicg at tid.es> >>>wrote: >>> >>>> Hi, >>>> >>>> Thank you for your feedback. >>>> >>>> The image is repository-image-R3.2 is simply wrong -- Please delete >>>>the >>>> instance you've created using that image and try >>>> "repository-image-R3.2-2" which I've dove solving the problem the >>>> previous one has. >>>> >>>> Best regards, >>>> José Ignacio. >>>> >>>> El 14/02/14 10:48, Thanasis Dalianis escribió: >>>>> Hi Jose, >>>>> >>>>> You were right, opening ports in the security group and the >>>>>certificate >>>>> did the trick. I have successfully created two instances of different >>>>> generic enablers and I can connect to them through ssh and http. >>>>> >>>>> I have an issue though with a specific instance/image. I have also >>>>> created >>>>> a repository instance (repository-image-R3.2) following the same >>>>> instructions,I use the same key_pairs and the same security group as >>>>> for >>>>> the rest of my instances but it seems that I can’t even connect to it >>>>> (root user). The ip of this instance is 130.206.83.132. >>>>> >>>>> Any ideas what maybe wrong with this one? >>>>> >>>>> Regarding the name resolutions are there any guidelines that we need >>>>>to >>>>> follow? Do we contact you when everything is ready and you handle it? >>>>> >>>>> Thank you >>>>> >>>>> Best >>>>> Athanasios >>>>> >>>>> >>>>> >>>>> On 2/13/14, 12:50 PM, "José Ignacio Carretero Guarde" <jicg at tid.es> >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> The problem is you have skipped the steps in the "Security groups", >>>>>>so >>>>>> no port is opened for your instances. I would suggest you to delete >>>>>> your >>>>>> VMS and start again following the steps in the video-demo: >>>>>> http://lab.fi-ware.org >>>>>> >>>>>> You first click in cloud, then in Instances and then watch the >>>>>>video. >>>>>> >>>>>> Anyway, as a quick tip, you need not only to assign Public IPs but >>>>>> also >>>>>> to create your own Keypairs (public/private keys) and to set some >>>>>> firewall rules to your instance. >>>>>> >>>>>> The user for every instance is ROOT. >>>>>> >>>>>> Best regards, >>>>>> José Ignacio. >>>>>> >>>>>> El 13/02/14 11:35, Thanasis Dalianis escribió: >>>>>>> Hi Jose >>>>>>> >>>>>>> Thank you for the quick reply. >>>>>>> >>>>>>> I have created two instances, one from the marketplace image and >>>>>>>one >>>>>>> from >>>>>>> the ubuntu one. The ubuntu instance uses a key pair, but it makes >>>>>>>no >>>>>>> difference. >>>>>>> The first one has public ip 130.206.83.65 and the second one >>>>>>> 130.206.83.80. >>>>>>> >>>>>>> I have a mac so I am using the terminal program. The command is >>>>>>>'ssh >>>>>>> 130.206.83.65’ and it gives me a time out error before it asks for >>>>>>> user >>>>>>> name or password. By the way the instances have an empty password >>>>>>> (Actions->change password). >>>>>>> >>>>>>> The same thing happens when using the ‘cyber duck’ program (similar >>>>>>> to >>>>>>> Winscp) even if I use my fi-lab credentials or anonymous access. >>>>>>> >>>>>>> Thank you for any help you can give me. >>>>>>> >>>>>>> Best >>>>>>> Athanasios >>>>>>> >>>>>>> On 2/13/14, 11:59 AM, "José Ignacio Carretero Guarde" <jicg at tid.es> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Athanasios, >>>>>>>> >>>>>>>> Thanks for testing our infrastructure. >>>>>>>> >>>>>>>> Ir order to do our own testing, Please, send us the ssh command >>>>>>>>you >>>>>>>> are >>>>>>>> using to connect to your public IP. >>>>>>>> >>>>>>>> About names, yes, I think some names resolution could be added to >>>>>>>> some >>>>>>>> IPs >>>>>>>> >>>>>>>> Best regards, >>>>>>>> José Ignacio. >>>>>>>> >>>>>>>> El 13/02/14 10:51, Thanasis Dalianis escribió: >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I am working for an EU project called ‘OPTET’ and we are >>>>>>>>> considering >>>>>>>>> in the context of the project to use the fi-lab infrastructure. >>>>>>>>> >>>>>>>>> I have created a test instance in fi-lab using the marketplace >>>>>>>>> image >>>>>>>>> and have assigned a public ip to it. >>>>>>>>> When I try though to connect to the instance through ssh I get >>>>>>>>> timeout >>>>>>>>> error. Also I can’t connect by clicking the VM display button. >>>>>>>>> >>>>>>>>> Could you please check it and let me know? >>>>>>>>> >>>>>>>>> Another thing I would like to ask is if it is possible to assign >>>>>>>>>to >>>>>>>>> instances static IPs or use a domain name for them instead of the >>>>>>>>> floating IP. >>>>>>>>> >>>>>>>>> Thank you for your assistance >>>>>>>>> >>>>>>>>> Best >>>>>>>>> >>>>>>>>> Athanasios Dalianis >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Fiware-lab-help mailing list >>>>>>>>> Fiware-lab-help at lists.fi-ware.eu >>>>>>>>> https://lists.fi-ware.eu/listinfo/fiware-lab-help >>>>>>>> ________________________________ >>>>>>>> >>>>>>>> Este mensaje se dirige exclusivamente a su destinatario. Puede >>>>>>>> consultar >>>>>>>> nuestra política de envío y recepción de correo electrónico en el >>>>>>>> enlace >>>>>>>> situado más abajo. >>>>>>>> This message is intended exclusively for its addressee. We only >>>>>>>>send >>>>>>>> and >>>>>>>> receive email on the basis of the terms set out at: >>>>>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx >>>>>> ________________________________ >>>>>> >>>>>> Este mensaje se dirige exclusivamente a su destinatario. Puede >>>>>> consultar >>>>>> nuestra política de envío y recepción de correo electrónico en el >>>>>> enlace >>>>>> situado más abajo. >>>>>> This message is intended exclusively for its addressee. We only send >>>>>> and >>>>>> receive email on the basis of the terms set out at: >>>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx >>>> >>>> ________________________________ >>>> >>>> Este mensaje se dirige exclusivamente a su destinatario. Puede >>>>consultar >>>> nuestra política de envío y recepción de correo electrónico en el >>>>enlace >>>> situado más abajo. >>>> This message is intended exclusively for its addressee. We only send >>>>and >>>> receive email on the basis of the terms set out at: >>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > >________________________________ > >Este mensaje se dirige exclusivamente a su destinatario. Puede consultar >nuestra política de envío y recepción de correo electrónico en el enlace >situado más abajo. >This message is intended exclusively for its addressee. We only send and >receive email on the basis of the terms set out at: >http://www.tid.es/ES/PAGINAS/disclaimer.aspx
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy