I start to understand your problem. Rather than using the poorly supported serial console (which seems to have the additional inconvenience of removing the console log), allow me to propose alternatives:
Not quite. You create a separate file that contains a script and starts with #!/bin/bash. Other languages like Python or Perl work as well, as long as there is an interpreter for them on the image. Then --user-data scriptfile.sh.
If however you create the instance via a Heat template, you can write the scripts directly into the server definition. No need for a separate file.
Hi, yes I am creating two instances on different compute nodes but in same physnet to check connectivity between them. Right now I have the heat template which works with VM creation. But when I tried with user-data say a simple script to create a file. its not working
Asked: 2018-07-18 18:32:24 -0600
Seen: 233 times
Last updated: Jul 20 '18
You telnet to the hypervisor to enter the instance? And you provide a serial port parameter (e.g. COM1)? This doesn't conform to telnet syntax, and telnetting to the hypervisor doesn't connect you to the instance. I doubt this makes sense in Liberty either.
Hi, Thank you for your reply. To be more precise I want to obtain the serial port from driver.py file which can be added to xml file while creating an instance and can be used to telnet into the Openstack VM
Do you mean the serial console? It doesn’t involve a driver.py file, but it’s still supported afaik.
Can the serial console be interactive as telnet sessions to send command like ping between VM to test connectivity among physnets ?
Yes, the serial console is interactive. However, I am certain that there are other, less complicated ways to check connectivity between VMs.