On (Fri) Jan 28 2011 [11:28:55], Perry Myers wrote:
(for reference we're talking about making changes to libvirt
default
configurations to always include virtio-serial channels so that Matahari
can use it w/o asking end users to add these themselves)
...
Ok. So what we'd want here is to by default add a virtio-serial
channel
in virtinst and vdsm with a name like 'org.matahari-project.port' (or if
we want to be more generic to this just being a qpid transport it could
be org.apache.qpid.port)
I'd prefer org.matahari-project.qpid. This channel is used by the
Matahari project, not the Apache qpid project, right?
> We can't add a channel without knowing exactly how the
application
> that will use it, needs it to be configured which isn't something
> we can reliably guess ahead of it being written.
What sort of configuration things need to be decided? Looking at the
channel snippet above it doesn't look unreasonable to decide what it
should look like and then implement the AMQP/virtio-serial transport to
use a preset configuration (assuming the important config info to decide
on is the channel name)
Configurable items are the name and the host-side backend for the port,
like unix socket, tcp socket, etc. The name has to be unique to avoid
confusion between multiple runs as well as multiple projects. The
host-side backend has to be suited to the host-side daemons.
Amit