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 > On 15 Sep 2015, at 09:36, Oscar Castro <oscar.castro at itech.expert> wrote: > > 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 [mailto:daniele.santoro at create-net.org] > Enviado el: lunes, 14 de septiembre de 2015 23:32 > Para: Oscar Castro > CC: fiware-lab-help at 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 > > >> On 14 Sep 2015, at 22:06, Oscar Castro <oscar.castro at itech.expert> wrote: >> >> FI-WARE Lab Identification data: >> User full name >> Jon Murcia >> User account >> artiamob at 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 at lists.fiware.org >> https://lists.fiware.org/listinfo/fiware-lab-help-new -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 204 bytes Desc: Message signed with OpenPGP using GPGMail URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20150915/12331d08/attachment.pgp>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy