All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>, xen-devel@lists.xenproject.org
Cc: Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
	Keir Fraser <keir@xen.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH 4/4] docs: Document xenstore paths for domain network address information
Date: Fri, 6 Nov 2015 18:16:43 +0000	[thread overview]
Message-ID: <563CEE8B.4090102@citrix.com> (raw)
In-Reply-To: <1446830507-4233-6-git-send-email-paul.durrant@citrix.com>

On 06/11/15 17:21, Paul Durrant wrote:
> It is useful to be able to see the network addresses in use by a domain
> for a particular vif in xenstore, for example so that ssh can be invoked
> by a toolstack to log into the guest domain.
>
> This patch documents paths to allow a domain to advertise MAC (unicast
> and multicast) and IP (versions 4 and 6) address information.
>
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
> Cc: Ian Campbell <ian.campbell@citrix.com>
> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> Cc: Jan Beulich <jbeulich@suse.com>
> Cc: Keir Fraser <keir@xen.org>
> Cc: Tim Deegan <tim@xen.org>
> ---
>  docs/misc/xenstore-paths.markdown | 29 +++++++++++++++++++++++++++++
>  1 file changed, 29 insertions(+)
>
> diff --git a/docs/misc/xenstore-paths.markdown b/docs/misc/xenstore-paths.markdown
> index 9e98d6f..68d3dbf 100644
> --- a/docs/misc/xenstore-paths.markdown
> +++ b/docs/misc/xenstore-paths.markdown
> @@ -39,6 +39,8 @@ before regexp expansion:
>  * $UUID -- a UUID in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
>  * $NAME -- a string identifying an object within a domain. Typically
>    comprising only alphanumeric characters.
> +* $INDEX -- an integer used as part of a path when listing a set of
> +            values. Typically these integers are contiguous.
>  
>  VALUES are strings and can take the following forms:
>  
> @@ -56,6 +58,13 @@ VALUES are strings and can take the following forms:
>  * VERSION -- 2 or 3 integers, in decimal form separated by ".",
>               specifying major version, minor version, and then
>  	     (optionally) micro version.
> +* MAC_ADDRESS -- 6 integers, in hexadecimal form, separated by ':',
> +                 specifying an ethernet MAC address.
> +* IPV4_ADDRESS -- 4 integers, in decimal form, separated by '.',
> +                  specifying an IP version 4 address.
> +* IPV6_ADDRESS -- 8 integers, in hexadecimal form, separated by ':',
> +                  specifying an IP version 6 address. (There should
> +                  be strictly 8 integers i.e. '::' compression).

Given the "strictly", I presume you mean no "::" compression?

But why enforce that restriction? "::" compression is unambiguous and
typically makes the addresses rather more human readable.

~Andrew

  reply	other threads:[~2015-11-06 18:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 17:21 [PATCH 0/4] docs: Document xenstore paths Paul Durrant
2015-11-06 17:21 ` [PATCH 1/4] docs: Document control features the can be advertised by guests Paul Durrant
2015-11-09 10:44   ` Jan Beulich
2015-11-09 11:01     ` Paul Durrant
2015-11-06 17:21 ` [PATCH 2/4] docs: Document a path for PV driver version information Paul Durrant
2015-11-06 17:25   ` Paul Durrant
2015-11-06 17:21 ` [PATCH 2/4] docs: Document a xenstore " Paul Durrant
2015-11-06 18:05   ` Andrew Cooper
2015-11-06 17:21 ` [PATCH 3/4] docs: Document xenstore paths for domain hotplug features Paul Durrant
2015-11-06 18:08   ` Andrew Cooper
2015-11-09  9:51     ` Paul Durrant
2015-11-09 10:50       ` Jan Beulich
2015-11-09 11:01         ` Paul Durrant
2015-11-06 17:21 ` [PATCH 4/4] docs: Document xenstore paths for domain network address information Paul Durrant
2015-11-06 18:16   ` Andrew Cooper [this message]
2015-11-09  9:55     ` Paul Durrant

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=563CEE8B.4090102@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=paul.durrant@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.