Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
Sender Email:
Description
Dear all,
now including fiware-lab-help@lists.fiware.org to create a respective
ticket in JIRA.
Please note that I mentioned several issues.
I tried to use various images (base_debian_7, base_ubuntu_12.04,
base_ubuntu_14.04).
Meanwhile, I terminated the instances since I did not use a dedicated
security group (issue 1) and the shared FIC2Lab key (issue 2) nor were
I'm able to configure the VM via ssh (issue 4 & 5).
Regards,
Stefan
On 11/4/2015 10:35 AM, Cristian CMECIU wrote:
> Dear Stefan,
>
> First of all, can you please open a ticket in Jira >> https://jira.fiware.org for a better tracking.
> Can you please there specify the image name and the id of the VM that you are using?
>
> BR,
> Cristian
>
> ----Message d'origine----
> De : Stefan Lemme stefan.lemme@dfki.de
> Envoyé : mardi 3 novembre 2015 23:54
> À : Dirk KRAUSE; Pierre FRANCOIS; Muryshkin, Peter; geoffroy.chollon@thalesgroup.com; Mario LOPEZ RAMOS; Riwal; Sergio MORANT
> Cc : Serge TRAVERT; Philipp Slusallek; pieter@vivitnet.com
> Objet : [engineering] [FIC2Lab] New VM for FIdoc (wiki pipeline)
>
>
> Dear all,
>
> I was just going to deploy a new VM for FIdoc (wiki pipeline) and experienced some issues while doing so:
>
> 1. I was unable to add rules to a newly created security group.
>
> 2. I didn't found the FIC2Lab-Key, thus created a personal one. Please send the files of the common key "fic2lab-lannion" to me.
>
> 3. Using an existing security group and my personal key enabled me to connect via ssh to the new VM. However, the login as "root" was responded with "please login as ubuntu" and the connection was closed.
>
> 4. Logging in as "ubuntu" worked, but I was not able to do much with this VM due to the lack of permissions.
>
> 5. sudo requires the password of "root" which I don't know and was unable to determine.
>
> Please let me know, how to address each of these issues.
>
> Best,
> Stefan
>
>
>
> ---------------------------------------------------------------------
> Desinscription: envoyez un message a: engineering-unsubscribe@imaginlab.fr
> Pour obtenir de l'aide, ecrivez a: engineering-help@imaginlab.fr
>
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: Stefan Lemme <stefan.lemme@dfki.de>]
Activity
Thanks a lot! Got a VM working and accessible.
I guess, I'm on the right track.
Best,
Stefan
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help
Cristian Cmeciu has just reported to me that the problem was resolved yesterday by the Lannion support team.
Ticket closed.
Hi Stefan,
Bellow, I replied in the order in which you putted the questions.
1. I was unable to add rules to a newly created security group.
> I have allocated additional resources for security_group_rules in Neutron, and now you can add new rules.
> don't forget to add ssh rule for ingress connections.
2. I didn't found the FIC2Lab-Key, thus created a personal one. Please send the files of the common key "fic2lab-lannion" to me. 3. Using an existing security group and my personal key enabled me to connect via ssh
to the new VM. However, the login as "root" was responded with "please login as ubuntu" and the connection was closed.
> I will send you a private mail avec "fic2lab-lannion" keypair
> To login you need a ssh connection with this keypair, using as user: ubuntu, coreos (depending of used image)
> After login in using the keypair, you can use “sudo su –“ to connect as root without password.
The your answers for the questions 4 and 5 in point 2.
If you have further question don't hesitate to contact me.
BR,
Cristian
----
Message d'origine----De : Stefan Lemme stefan.lemme@dfki.de
Envoyé : mercredi 4 novembre 2015 10:42
À : Cristian CMECIU; fiware-lab-help@lists.fiware.org
Cc : Dirk KRAUSE; Pierre FRANCOIS; Muryshkin, Peter; geoffroy.chollon@thalesgroup.com; Mario LOPEZ RAMOS; Riwal; Sergio MORANT; Serge TRAVERT; Philipp Slusallek; pieter@vivitnet.com
Objet : Re: [engineering] [FIC2Lab] New VM for FIdoc (wiki pipeline)
Dear all,
now including fiware-lab-help@lists.fiware.org<fiware-lab-help@lists.fiware.org
> to create a respective ticket in JIRA.
Please note that I mentioned several issues.
I tried to use various images (base_debian_7, base_ubuntu_12.04, base_ubuntu_14.04).
Meanwhile, I terminated the instances since I did not use a dedicated security group (issue 1) and the shared FIC2Lab key (issue 2) nor were I'm able to configure the VM via ssh (issue 4 & 5).
Regards,
Stefan
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help