Thanks dietmar!
I write this code but there is something wrong:
use strict;
use PVE::Utils;
use PVE::ConfigServer;
use PVE::Cluster;
my $secret = PVE::Utils::load_auth_secret();
my $ticket = PVE::Utils::create_auth_ticket ($secret, 'root', 'root');
my $conn = PVE::ConfigClient::connect...
Yes it return the same id for 40-60 second after the creation of a new VE.
Yes it may be a solution, but i like better to use only Proxmox infrastructure to take decisions as new VE ids.
Is there a trick to force cluster update before call get_nextveid()?
Bye
Using perl code in this thread I've got the next free veid number:
use strict;
use PVE::Utils;
use PVE::ConfigServer;
use PVE::Cluster;
my $secret = PVE::Utils::load_auth_secret();
my $ticket = PVE::Utils::create_auth_ticket ($secret, 'root', 'root');
my $conn = PVE::ConfigClient::connect...
Using perl code in this thread I've got the next free veid number:
use strict;
use PVE::Utils;
use PVE::ConfigServer;
use PVE::Cluster;
my $secret = PVE::Utils::load_auth_secret();
my $ticket = PVE::Utils::create_auth_ticket ($secret, 'root', 'root');
my $conn = PVE::ConfigClient::connect...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.