From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] [PATCH cluster 2/4] add get_remote_info
Date: Mon, 19 Apr 2021 09:48:34 +0200 [thread overview]
Message-ID: <1618818207.7v0hjv76ve.astroid@nora.none> (raw)
In-Reply-To: <e3974f3f-a801-da91-556d-aa66fc7d045b@proxmox.com>
On April 18, 2021 7:07 pm, Thomas Lamprecht wrote:
> On 13.04.21 14:16, Fabian Grünbichler wrote:
>> as a unified helper for talking to a remote node. if the requested node
>> has an entry in the remote config, the information from that entry is
>> used. else, the first locally defined node of the requested cluster is
>> used as proxy.
>>
>> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
>> ---
>> data/PVE/RemoteConfig.pm | 55 ++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 55 insertions(+)
>>
>> diff --git a/data/PVE/RemoteConfig.pm b/data/PVE/RemoteConfig.pm
>> index 23274de..7c395ba 100644
>> --- a/data/PVE/RemoteConfig.pm
>> +++ b/data/PVE/RemoteConfig.pm
>> @@ -3,6 +3,7 @@ package PVE::RemoteConfig;
>> use strict;
>> use warnings;
>>
>> +use PVE::APIClient::LWP;
>> use PVE::Cluster qw(cfs_register_file cfs_read_file cfs_write_file cfs_lock_file);
>> use PVE::JSONSchema qw(get_standard_option);
>> use PVE::Tools;
>> @@ -158,6 +159,60 @@ sub lock {
>> }
>> }
>>
>> +# will attempt to connect with node's locally defined endpoint if possible
>> +sub get_remote_info {
>> + my ($self, $cluster, $node, $network_cidr) = @_;
>> +
>> + my $cluster_info = $self->{ids}->{$cluster};
>> + die "Remote cluster '$cluster' is not defined!\n"
>> + if !defined($cluster_info) || $cluster_info->{type} ne 'pvecluster';
>> +
>> + my $host = $node;
>> +
>> + # fallback to random node/endpoint if $node is not locally defined
>> + if (!$cluster_info->{nodes}->{$node}) {
>> + my @defined_nodes = keys %{$cluster_info->{nodes}};
>> + $host = $defined_nodes[0];
>> + }
>> +
>> + my $api_node = $self->{ids}->{$host};
>> +
>> + my $api_token = $cluster_info->{token} // $api_node->{token};
>> +
>> + my $conn_args = {
>> + username => 'root@pam',
>> + protocol => 'https',
>> + host => $api_node->{endpoint},
>> + apitoken => $api_token,
>> + port => 8006,
>> + };
>> +
>> + if (my $fp = $api_node->{fingerprint}) {
>> + $conn_args->{cached_fingerprints} = { uc($fp) => 1 };
>> + } else {
>> + # FIXME add proper parameter to APIClient
>
> that should now work out of the box? I.e., if no FP is passed we default to
> verify_hostname = 1, and if verify_hostname is true we trust what openssl thinks
> about the validity of the connection.
I didn't test it (and the tunnel binary itself still lacks that
functionality for sure), but that comment is leftover (only slightly
moved/reworded) from last year's PoC, so it's possible that the LWP
client handles this well nowadays :)
>
>> + die "IMPLEMENT ME";
>> + my $ssl_opts = {
>> + verify_hostname => 1,
>> +# SSL_ca_path => '/etc/ssl/certs',
>> + SSL_verify_callback => 1,
>> + };
>> + }
>> +
>> + print "Establishing API connection with cluster '$cluster' node '$host'\n";
>> +
>> + my $conn = PVE::APIClient::LWP->new(%$conn_args);
>> +
>> +
>> + my $args = {};
>> + $args->{cidr} = $network_cidr if $network_cidr;
>> +
>> + print "Request IP information of node '$node'\n";
>> + my $res = $conn->get("/nodes/$node/addr", $args);
>> +
>> + return ($res, $conn_args);
>> +}
>> +
>> package PVE::RemoteConfig::Cluster;
>>
>> use PVE::RemoteConfig;
>>
>
>
next prev parent reply other threads:[~2021-04-19 7:49 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 12:16 [pve-devel] [RFC qemu-server++ 0/22] remote migration Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH proxmox 1/2] websocket: make field public Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH proxmox 2/2] websocket: adapt for client connection Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH proxmox-websocket-tunnel 1/2] initial commit Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH proxmox-websocket-tunnel 2/2] add tunnel implementation Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH access-control 1/2] tickets: add tunnel ticket Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH access-control 2/2] ticket: normalize path for verification Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH cluster 1/4] remote.cfg: add new config file Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH cluster 2/4] add get_remote_info Fabian Grünbichler
2021-04-18 17:07 ` Thomas Lamprecht
2021-04-19 7:48 ` Fabian Grünbichler [this message]
2021-04-13 12:16 ` [pve-devel] [PATCH cluster 3/4] remote: add option/completion Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH cluster 4/4] get_remote_info: also return FP if available Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH common 1/2] schema: pull out abstract 'id-pair' verifier Fabian Grünbichler
2021-04-16 10:24 ` [pve-devel] applied: " Thomas Lamprecht
2021-04-19 8:43 ` [pve-devel] [PATCH common] fixup: remove double braces Stefan Reiter
2021-04-19 9:56 ` [pve-devel] applied: " Thomas Lamprecht
2021-04-13 12:16 ` [pve-devel] [PATCH common 2/2] schema: add pve-bridge-id option/format/pair Fabian Grünbichler
2021-04-16 9:53 ` Thomas Lamprecht
2021-04-16 10:10 ` Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH guest-common] migrate: handle migration_network with remote migration Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH manager] API: add node address(es) API endpoint Fabian Grünbichler
2021-04-16 10:17 ` Thomas Lamprecht
2021-04-16 11:37 ` Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH storage] import: allow import from UNIX socket Fabian Grünbichler
2021-04-16 10:24 ` [pve-devel] applied: " Thomas Lamprecht
2021-04-13 12:16 ` [pve-devel] [PATCH qemu-server 1/7] migrate: factor out storage checks Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH qemu-server 2/7] refactor map_storage to map_id Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH qemu-server 3/7] schema: use pve-bridge-id Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH qemu-server 4/7] mtunnel: add API endpoints Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH qemu-server 5/7] migrate: refactor remote VM/tunnel start Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH qemu-server 6/7] migrate: add remote migration handling Fabian Grünbichler
2021-04-13 12:16 ` [pve-devel] [PATCH qemu-server 7/7] api: add remote migrate endpoint Fabian Grünbichler
2021-04-15 14:04 ` [pve-devel] [RFC qemu-server++ 0/22] remote migration alexandre derumier
2021-04-15 14:32 ` Fabian Grünbichler
2021-04-15 14:36 ` Thomas Lamprecht
2021-04-15 16:38 ` Moula BADJI
2021-05-05 6:02 ` aderumier
2021-05-05 9:22 ` Dominik Csapak
2021-04-16 7:36 ` alexandre derumier
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=1618818207.7v0hjv76ve.astroid@nora.none \
--to=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/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