From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>, xen-devel@lists.xenproject.org
Subject: Re: [OSSTEST PATCH 15/13] Plan reporting: Provide get-last-plan queuedaemon command
Date: Thu, 3 Sep 2015 14:05:11 +0100 [thread overview]
Message-ID: <1441285511.26292.368.camel@citrix.com> (raw)
In-Reply-To: <1441280951-8076-2-git-send-email-ian.jackson@eu.citrix.com>
On Thu, 2015-09-03 at 12:49 +0100, Ian Jackson wrote:
> This allows retrieval, by monitoring clients which are not
> participating in the planning queue, of the finished projection, or
> the unfinished plan as it was at the time of last restart.
>
> Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
> ---
> README.planner | 11 +++++++++++
> ms-queuedaemon | 8 ++++++++
> 2 files changed, 19 insertions(+)
>
> diff --git a/README.planner b/README.planner
> index c1b2bf6..8231812 100644
> --- a/README.planner
> +++ b/README.planner
> @@ -224,6 +224,17 @@ ms-queuedaemon commands
>
> > thought-done | thought-wait
>
> + > get-last-plan projection|plan
> + Retrieve the last fully completed plan (`projection'),
> + or the most recent short-term information used for
> + actual resource allocation (`plan').
> +
> + For monitoring tools, not participants in the resource
> + allocation process. Response is as for get-plan:
> +
> + < OK get-plan BYTES
> + PLAN-DATA
> +
>
> Plan is:
> Start time_t used for "now" *
> diff --git a/ms-queuedaemon b/ms-queuedaemon
> index 222b687..97dff85 100755
> --- a/ms-queuedaemon
> +++ b/ms-queuedaemon
> @@ -292,6 +292,7 @@ proc report-plan {w wo} {
> } emsg]} {
> log "INTERNAL ERROR showing $w html: $emsg"
> } else {
> + file copy -force data-$w.pl data-$wo-final.pl
IIRC there was code earlier which did smth like "cp data-plan.pl data
-projection.pl" during the take over and that if no resources come
available during a plan walk then no projection walk would happen.
IOW a user needs to do something like try get-last-plan on projection, then
if that doesn't work try again with plan.
But with that the last projection walk might be out of data WRT a more
recently completed plan walk.
So I think a client would need to get both and compare the timestamps or
something. It might be nicer to arrange for data-plan-final.pl to be copied
to data-projection-final.pl at the same time as data-plan.pl becomes data
-projection.pl?
> log "$w report-plan OK"
> }
> }
> @@ -366,6 +367,13 @@ proc cmd/get-plan {chan desc} {
> set plan [return-plan-to-client $chan $w]
> }
>
> +proc cmd/get-last-plan {chan desc w} {
> + global walkers
> + if {[lsearch -exact $walkers $w] < 0} { error "unknown last-plan
> ($w)" }
> + if {![file exists data-$w-final.pl]} { error "no last-plan $w" }
> + return-plan-data-to-client $w-final
> +}
> +
> proc cmd/book-resources {chan desc bytes} {
> read-chan-data $chan $bytes do-book-resources $w
> }
next prev parent reply other threads:[~2015-09-03 13:06 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 15:45 [OSSTEST RFC PATCH 00/13] Planner: Performance improvement Ian Jackson
2015-09-02 15:45 ` [OSSTEST PATCH 01/13] Tcl: Use lshift instead of open-coding with lrange Ian Jackson
2015-09-03 10:44 ` Ian Campbell
2015-09-03 10:50 ` Ian Jackson
2015-09-02 15:45 ` [OSSTEST PATCH 02/13] Planner: docs: Minor fixes Ian Jackson
2015-09-03 10:47 ` Ian Campbell
2015-09-03 12:04 ` Ian Jackson
2015-09-02 15:45 ` [OSSTEST PATCH 03/13] Planner: docs: Document set-info command Ian Jackson
2015-09-03 10:48 ` Ian Campbell
2015-09-02 15:45 ` [OSSTEST PATCH 04/13] Planner: Fix indefinite holdoff Ian Jackson
2015-09-03 10:51 ` Ian Campbell
2015-09-02 15:45 ` [OSSTEST PATCH 05/13] Planner: client side: $mayalloc parameter to $resourcecall->() Ian Jackson
2015-09-03 10:52 ` Ian Campbell
2015-09-02 15:45 ` [OSSTEST PATCH 06/13] Planner: client side: New `!OK think noalloc' protocol Ian Jackson
2015-09-03 10:53 ` Ian Campbell
2015-09-02 15:45 ` [OSSTEST PATCH 07/13] Planner: ms-planner support -w option Ian Jackson
2015-09-03 11:25 ` Ian Campbell
2015-09-02 15:45 ` [OSSTEST PATCH 08/13] Planner: ms-queuedaemon: Prep for multiple walkers Ian Jackson
2015-09-03 12:05 ` Ian Campbell
2015-09-03 15:42 ` Ian Jackson
2015-09-02 15:45 ` [OSSTEST PATCH 09/13] Planner: ms-queuedaemon: Synchronise thinking " Ian Jackson
2015-09-03 12:06 ` Ian Campbell
2015-09-02 15:45 ` [OSSTEST PATCH 10/13] Planner: ms-queuedaemon: Break out queuerun-finished/<walker> Ian Jackson
2015-09-03 12:43 ` Ian Campbell
2015-09-02 15:45 ` [OSSTEST PATCH 11/13] Planner: ms-queuedaemon: Break out notify-to-think Ian Jackson
2015-09-03 12:44 ` Ian Campbell
2015-09-02 15:45 ` [OSSTEST PATCH 12/13] Planner: ms-queuedaemon: Make report-plan take output walker name Ian Jackson
2015-09-03 12:44 ` Ian Campbell
2015-09-02 15:45 ` [OSSTEST PATCH 13/13] Planner: ms-queuedaemon: Restart planning when resources become free Ian Jackson
2015-09-03 12:59 ` Ian Campbell
2015-09-03 11:49 ` [OSSTEST PATCH 14/13] Planning reports: Break out return-plan-to-client Ian Jackson
2015-09-03 11:49 ` [OSSTEST PATCH 15/13] Plan reporting: Provide get-last-plan queuedaemon command Ian Jackson
2015-09-03 13:05 ` Ian Campbell [this message]
2015-09-03 15:51 ` Ian Jackson
2015-09-03 15:52 ` Ian Jackson
2015-09-03 16:12 ` Ian Campbell
2015-09-03 13:01 ` [OSSTEST PATCH 14/13] Planning reports: Break out return-plan-to-client Ian Campbell
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=1441285511.26292.368.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--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.