From: cel@kernel.org
To: <kdevops@lists.linux.dev>
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: [RFC PATCH 0/2] Provisioning the AWS private network
Date: Fri, 8 Nov 2024 15:12:43 -0500 [thread overview]
Message-ID: <20241108201245.561269-1-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
Here are a couple of improvements to make terraform provision a
security group and DNS for handling NFS traffic between the test
nodes.
The DNS set-up here is what I'd like to see for libvirt as well,
rather than poking IP addresses into the target node's /etc/hosts
files. But that's for another day.
Chuck Lever (2):
aws: Permit inter-node network traffic
aws: Add each test instance to the local DNS service
terraform/aws/main.tf | 51 ++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 50 insertions(+), 1 deletion(-)
--
2.47.0
next reply other threads:[~2024-11-08 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 20:12 cel [this message]
2024-11-08 20:12 ` [RFC PATCH 1/2] aws: Permit inter-node network traffic cel
2024-11-08 20:12 ` [RFC PATCH 2/2] aws: Add each test instance to the local DNS service cel
2024-11-09 0:44 ` [RFC PATCH 0/2] Provisioning the AWS private network Luis Chamberlain
2024-11-09 17:19 ` Chuck Lever III
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=20241108201245.561269-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=kdevops@lists.linux.dev \
/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.