On Tue, Feb 21, 2017 at 10:08:54AM -0500, David Medberry wrote:
> Doesn't the virtio solution assume/require a libvirt or more exactly a
> QEMU/KVM based hypervisor?
>
> What about the N-1 other hypervisors?
vsock is an equivalent of UNIX domain sockets, for host<->guest communication
that was in
Doesn't the virtio solution assume/require a libvirt or more exactly a
QEMU/KVM based hypervisor?
What about the N-1 other hypervisors?
I think the idea of a "hot remove, hot add" of the configdrive has some
merit (but remember it is not always ISO-9660 but could be VFAT as well to
aid in some mi
On Tue, Feb 21, 2017 at 01:09:43PM +, Jeremy Stanley wrote:
> On 2017-02-21 06:24:20 -0500 (-0500), Clint Byrum wrote:
> [...]
> > Why not just make it a virtual USB drive that ejects and
> > re-attaches on changes?
> [...]
>
> Is there a graceful way to trigger that from the host so that the
On 2017-02-21 06:24:20 -0500 (-0500), Clint Byrum wrote:
[...]
> Why not just make it a virtual USB drive that ejects and
> re-attaches on changes?
[...]
Is there a graceful way to trigger that from the host so that the
guest knows to unmount it prior to ejection? Or is that not actually
necessary
Excerpts from Daniel P. Berrange's message of 2017-02-21 10:40:02 +:
> On Mon, Feb 20, 2017 at 02:36:15PM -0500, Clint Byrum wrote:
> > What exactly is the security concern of the metadata service? Perhaps
> > those concerns can be addressed directly?
> >
> > I ask because anything that requir
On Mon, Feb 20, 2017 at 02:36:15PM -0500, Clint Byrum wrote:
> What exactly is the security concern of the metadata service? Perhaps
> those concerns can be addressed directly?
>
> I ask because anything that requires special software on the guest is
> a non-starter IMO. virtio is a Linux thing, s
On Mon, Feb 20, 2017 at 08:08:00PM +, Jeremy Stanley wrote:
> On 2017-02-20 14:36:15 -0500 (-0500), Clint Byrum wrote:
> > What exactly is the security concern of the metadata service? Perhaps
> > those concerns can be addressed directly?
> [...]
>
> A few I'm aware of:
>
> 1. It's something
Excerpts from Jeremy Stanley's message of 2017-02-20 20:08:00 +:
> On 2017-02-20 14:36:15 -0500 (-0500), Clint Byrum wrote:
> > What exactly is the security concern of the metadata service? Perhaps
> > those concerns can be addressed directly?
> [...]
>
> A few I'm aware of:
>
Thanks!
> 1.
On 2017-02-20 14:36:15 -0500 (-0500), Clint Byrum wrote:
> What exactly is the security concern of the metadata service? Perhaps
> those concerns can be addressed directly?
[...]
A few I'm aware of:
1. It's something that runs in the control plane but needs to be
reachable from untrusted server i
What exactly is the security concern of the metadata service? Perhaps
those concerns can be addressed directly?
I ask because anything that requires special software on the guest is
a non-starter IMO. virtio is a Linux thing, so what does this do for
users of Windows? FreeBSD? etc.
Excerpts from
We've been having a discussion [1] in openstack-dev about how to best
expose dynamic metadata that changes over a server's lifetime to the
server. The specific use case is device role tagging with hotplugged
devices, where a network interface or volume is attached with a role
tag, and the guest wou
11 matches
Mail list logo
