Launch a instance using a ServerTemplate with user data

@xiaohua-guan

Could you please check a /var/log/cloud-init-output.log file in your launched instance? ... uh, launch itself would fail.. sorry..

@xiaohua-guan

Thank you for providing the patch. I found that the launch confirmation page has redundant <br /> in each line in User Data field. If possible, can you remove <br />?

FYI, the following is the screenshot:

@xiaohua-guan

Use this one for the testing:

#cloud-config
timezone: 'Asia/Tokyo'
hostname: cloud-orchestrator
preserve_hostname: true
manage_etc_hosts: true
package_update: true
package_upgrade: true
runcmd:
  - [ sed, -i, -e, 's/localhost/localhost cloud-orchestrator cloud-orchestrator/g', /etc/hosts ]
  - [ sh, -c, 'hostname cloud-orchestrator' ]
  - [ sh, -c, 'echo cloud-orchestrator > /etc/hostname' ]
  - [ sh, -c, 'echo "LC_ALL=en_US.UTF-8" >> /etc/environment' ]
  - [ sh, -c, 'echo "LANG=en_US.UTF-8" >> /etc/environment' ]
  - [ apt, update ]
  -
    - sh
    - -c
    - |+
      cat << 'PS' >> /home/ubuntu/.bashrc
      export txt1='\[\033[38;05;75m\]'  # Cyan Dark
      export txt2='\[\033[38;05;122m\]' # Green light
      export txt3='\[\033[38;05;81m\]'  # Cyan
      export txt4='\[\033[01;38m\]'     # White
      export txtrst='\[\033[00m\]'      # Reset
      # Cyan

      PS
  - [ sh, -c, 'echo "PS1=\"\${txt1}[\${txt2}\\\$(date +%m/%d) \\\$(date +%H:%M)\${txt1}][\${txt3}\\\u\${txt1}@\${txt3}\\\h\${txt1}:\${txt4}\\\w\${txt1}]\${txt4}\\\$ \${txtrst}\"" >> /home/ubuntu/.bashrc' ]

@xiaohua-guan

What I want to expect is that it displays the user-data as it is including the white spaces to keep the indents. In my css, I wanted to apply something like this:

.field--item {
  white-space: pre-wrap;
}

Since User Data field is special, so if you can put <pre>...</pre> in that User Data field in the confirmation screen, that would be great. Is that possible?

@xiaohua-guan

Thank you for the updated patch. This is sooo fantastic!

@baldwinlouie
@masami

What do you think?

@all, this one looks good.

@baIdwinlouie

Thank you for your review. Then, I'll merge the patch to 8.x-1.x and 8.x-2.x and close this issue as Fixed.

Here is the screenshot for the comment #15