From: Jeremy Plsek <jplsek@iol.unh.edu>
To: ci@dpdk.org
Subject: [dpdk-ci] DPDK lab meeting agenda items 2018-08-14
Date: Mon, 13 Aug 2018 17:27:21 -0400 [thread overview]
Message-ID: <CA+xUZB48fVcEcxQMPPw_9VXwJy1LXTTgJm8j3WyO6g=_aGpS5w@mail.gmail.com> (raw)
Hi all,
For tomorrows meeting we'd like to talk about the following:
There's been a request about granting more direct access to the
database. If there is general agreement, we feel that the best way to
do this would be stabilizing our backend REST API for members to
directly access. The REST API closely mirrors the actual database but
with appropriate permission checks. In the mean time, we have given
them a blank database to use, but we'd like to avoid this in the
future.
There was another request to add a disclaimer for a specific platform
to the detailed results. Instead, we'd like a single general
disclaimer that covers all platforms instead of an individual
platform.
--
Jeremy Plsek
UNH InterOperability Laboratory
reply other threads:[~2018-08-13 21:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CA+xUZB48fVcEcxQMPPw_9VXwJy1LXTTgJm8j3WyO6g=_aGpS5w@mail.gmail.com' \
--to=jplsek@iol.unh.edu \
--cc=ci@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).