Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-4107

Re: [Fiware-lab-help] FIWARE Lab Assistance

        Details

        • Type: extRequest
        • Status: Closed
        • Priority: Major
        • Resolution: Done
        • Fix Version/s: 2021
        • Component/s: FIWARE-LAB-HELP
        • Labels:
          None
        • HD-Chapter:
          Ops
        • HD-Enabler:
          Ops - Deploy

          Description

          Dear,

          You could try to setup a cloud-init script with specific configuration for your instance. Here you have an example: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/4/html/End_User_Guide/user-data.html on how to write it.

          You should be able to inject the configuration to your instance from the section under tab “4. Post-Creation” in the instance launch window.

          Best,
          Daniele

          > On 14 Sep 2015, at 22:06, Oscar Castro <oscar.castro@itech.expert> wrote:
          >
          > FI-WARE Lab Identification data:
          > User full name
          > Jon Murcia
          > User account
          > artiamob@gmail.com
          > Accelerator submission name
          > Artiamob
          > FIWARE Lab Node
          > Spain
          >
          > Help request about changing the hostname of the VM instances/nodes launched on the Lab.
          >
          > I built the node without blueprint, template or any other assistance; just launched an instance of a CentOS 6.5 based image. It seems that when you do it in this way, the cloud environment sets the hostname automatically with a name based on the image name itself. Later, when I try to modify the hostname following the CentOS typical procedures (hostnames file, hostname command, etc) the image seems to do it correctly but if I reboot the machine the hostname is reverted to the original one. ¿How could I prevent this to happen?.
          >
          > Regards,
          >
          > - Oscar Castro
          > _______________________________________________
          > Fiware-lab-help mailing list
          > Fiware-lab-help@lists.fiware.org
          > https://lists.fiware.org/listinfo/fiware-lab-help-new

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

          1. File
            signature.asc
            0.2 kB
            Daniele Santoro
          2. File
            signature.asc
            0.2 kB
            Daniele Santoro

            Activity

            Ascending order - Click to sort in descending order
            danieles Daniele Santoro created issue -
            danieles Daniele Santoro made changes -
            Field Original Value New Value
            Assignee Daniele Santoro [ danieles ]
            danieles Daniele Santoro made changes -
            Component/s FIWARE-LAB-HELP [ 10279 ]
            danieles Daniele Santoro made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            danieles Daniele Santoro made changes -
            Status In Progress [ 3 ] Answered [ 10104 ]
            danieles Daniele Santoro made changes -
            Resolution Done [ 10000 ]
            Status Answered [ 10104 ] Closed [ 6 ]
            Hide
            Permalink
            fw.ext.user FW External User added a comment -

            Thanks Daniele,

            Does it mean that I can only do that when creating the instance? Is there
            any procedure to modify it once created?.

            • Oscar Castro

            ----Mensaje original----
            De: Daniele Santoro daniele.santoro@create-net.org
            Enviado el: lunes, 14 de septiembre de 2015 23:32
            Para: Oscar Castro
            CC: fiware-lab-help@lists.fiware.org; Jon Murcia; Pasquale Vitale
            Asunto: Re: [Fiware-lab-help] FIWARE Lab Assistance

            Dear,

            You could try to setup a cloud-init script with specific configuration for
            your instance. Here you have an example:
            https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenS
            tack_Platform/4/html/End_User_Guide/user-data.html on how to write it.

            You should be able to inject the configuration to your instance from the
            section under tab “4. Post-Creation” in the instance launch window.

            Best,
            Daniele

            launched on the Lab.
            launched an instance of a CentOS 6.5 based image. It seems that when you do
            it in this way, the cloud environment sets the hostname automatically with
            a name based on the image name itself. Later, when I try to modify the
            hostname following the CentOS typical procedures (hostnames file, hostname
            command, etc) the image seems to do it correctly but if I reboot the machine
            the hostname is reverted to the original one. ¿How could I prevent this to
            happen?.

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

            Show
            fw.ext.user FW External User added a comment - Thanks Daniele, Does it mean that I can only do that when creating the instance? Is there any procedure to modify it once created?. Oscar Castro ---- Mensaje original ---- De: Daniele Santoro daniele.santoro@create-net.org Enviado el: lunes, 14 de septiembre de 2015 23:32 Para: Oscar Castro CC: fiware-lab-help@lists.fiware.org; Jon Murcia; Pasquale Vitale Asunto: Re: [Fiware-lab-help] FIWARE Lab Assistance Dear, You could try to setup a cloud-init script with specific configuration for your instance. Here you have an example: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenS tack_Platform/4/html/End_User_Guide/user-data.html on how to write it. You should be able to inject the configuration to your instance from the section under tab “4. Post-Creation” in the instance launch window. Best, Daniele launched on the Lab. launched an instance of a CentOS 6.5 based image. It seems that when you do it in this way, the cloud environment sets the hostname automatically with a name based on the image name itself. Later, when I try to modify the hostname following the CentOS typical procedures (hostnames file, hostname command, etc) the image seems to do it correctly but if I reboot the machine the hostname is reverted to the original one. ¿How could I prevent this to happen?. _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fiware.org https://lists.fiware.org/listinfo/fiware-lab-help-new
            Hide
            Permalink
            danieles Daniele Santoro added a comment -

            I’m 99% sure you can’t modify the cloud-init script already associated with an instance from the UI. An idea could be to see in the vm this folder (if present): /etc/cloud/, probably you can modify some scripts from there. Also be aware that the cloud-init script is started with an upstart job present in /etc/init.d/cloud-init*.

            Anyway, my suggestion is: try to create a snapshot of your instance and then boot up a new instance from the image/snapshot previously created. Before booting the image you can configure your cloud-init script from the UI.

            Best,
            Daniele

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

            Show
            danieles Daniele Santoro added a comment - I’m 99% sure you can’t modify the cloud-init script already associated with an instance from the UI. An idea could be to see in the vm this folder (if present): /etc/cloud/, probably you can modify some scripts from there. Also be aware that the cloud-init script is started with an upstart job present in /etc/init.d/cloud-init*. Anyway, my suggestion is: try to create a snapshot of your instance and then boot up a new instance from the image/snapshot previously created. Before booting the image you can configure your cloud-init script from the UI. Best, Daniele _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fiware.org https://lists.fiware.org/listinfo/fiware-lab-help-new
            danieles Daniele Santoro made changes -
            Attachment signature.asc [ 18039 ]
            fla Fernando Lopez made changes -
            HD-Enabler Ops - Deploy [ 10907 ]
            HD-Chapter Ops [ 10843 ]
            fla Fernando Lopez made changes -
            Fix Version/s 2021 [ 12600 ]
            Transition Time In Source Status Execution Times Last Executer Last Execution Date
            Open Open In Progress In Progress
            		6m 36s 1 Daniele Santoro 14/Sep/15 11:39 PM
            In Progress In Progress Answered Answered
            		4s 1 Daniele Santoro 14/Sep/15 11:39 PM
            Answered Answered Closed Closed
            		4s 1 Daniele Santoro 14/Sep/15 11:39 PM

              People

              • Assignee:
                danieles Daniele Santoro
                Reporter:
                danieles Daniele Santoro
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: