After thinking little bit more, a way could be to update the actual API to let it to pass an arguement port-number and add a new API to return a list of serial-port created.
An other way would be to have a way to set a new attribute to the connection info which can be used to understand if yes or no the port for this connection is used and then store it to the database. The current code store the connection_info in memory or in memcached if available.
Looking at the code, we need to update Console classes to use the objects framework and let them handle the connection_info also remove the way that we use to store it in memory to use a real database. This is more than a but and a spec needs to spec provided for lemming.
After thinking little bit more, a way could be to update the actual API to let it to pass an arguement port-number and add a new API to return a list of serial-port created.
An other way would be to have a way to set a new attribute to the connection info which can be used to understand if yes or no the port for this connection is used and then store it to the database. The current code store the connection_info in memory or in memcached if available.
Looking at the code, we need to update Console classes to use the objects framework and let them handle the connection_info also remove the way that we use to store it in memory to use a real database. This is more than a but and a spec needs to spec provided for lemming.
I will work on it.