with bonus points for information on who controls the protocol
(Inktank/RH or IETF) and if it offers any sort of extensibility (in other
words, is there any hope for us to add label information to the protocol).
--
paul moore
security and virtualization @ redhat
--
libvir-list mailing list
libvir
On Wednesday, August 07, 2013 04:25:04 PM Daniel P. Berrange wrote:
> On Wed, Aug 07, 2013 at 11:11:20AM -0400, Paul Moore wrote:
> > The virthread.h header file includes platform specific header files
> > that help define the thread implementation, see code snippet below.
> >
.h to virthread.h in an effort to help simplify
things.
Signed-off-by: Paul Moore
---
src/util/virthread.h |2 ++
1 file changed, 2 insertions(+)
diff --git a/src/util/virthread.h b/src/util/virthread.h
index 84d3bdc..091cdd0 100644
--- a/src/util/virthread.h
+++ b/src/util/virthrea
On Tuesday 28 October 2008 5:42:17 pm James Morris wrote:
> On Thu, 23 Oct 2008, Paul Moore wrote:
> > However, may I suggest that instead of representing the DOI as a
> > string we use a 32bit integer? I know that may sound a bit odd,
> > but in the networking worl
rstand that
using a plain integer is much more abstract than a human readable
string but it should make it easier to leverage existing and future*
DOI frameworks.
*An informal group/list just formed to start discussing DOI management
issues such as DOI formats, negotiation and translation.
--
paul moore
linux @ hp
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
virtual
> networking aspect in some way.
I think we could do some pretty cool things here with the new, well
2.6.25 new, network ingress/egress controls and restricting VM
instances to specific interfaces and/or networks. However, we would
need to settle the basic VM label management issues fir
