From: Yannis Milios <yannis.milios@gmail.com>
To: PVE User List <pve-user@pve.proxmox.com>
Subject: Re: [PVE-User] Temporary add a node to a cluster...
Date: Sat, 25 Jul 2020 18:38:56 +0100 [thread overview]
Message-ID: <CAFiF2Opc5Lt20wcDT=RmWa=gVkbBtsnE+9=d32FKNbFeaWibHA@mail.gmail.com> (raw)
In-Reply-To: <20200725125208.GA24275@lilliput.linux.it>
Are you trying to convert (P2V) a physical server into a VM and then after
repurpose the same server into a standalone PVE host?
If so, then definitely it won't be quick, especially without some kind of
shared storage.
You could potentially reduce the time needed by following these steps...
- P2V your physical server into a VM at your test PVE cluster.
- Shutdown original server and then start its VM version on your test
cluster. Leave it running there for some days and see if everything
is working properly.
- Repurpose original server into a PVE host but do _not_ add it as a new
cluster member on your test cluster. Just connect it to the same physical
network.
- Start copying the running VM onto this standalone PVE host. You could use
rsync for example or zfs send/recv if you are using ZFS at both sides.
- Once transfer is finished, shutdown the VM on the test cluster and then
immediately do a final rsync or zfs send/receive so that the latest changes
are replicated on the target server.
- Create a new VM on standalone server and attach the VM disk onto it.
- Start the VM on standalone server and delete it from your test cluster.
Yannis
On Sat, 25 Jul 2020 at 14:00, Marco Gaiarin <gaio@sv.lnf.it> wrote:
>
> I need to do a P2V 'in place' for a server, and i can use for that a
> 'test cluster' (two HP Microserver) i own.
> But the final result would be two different clusters.
>
> Also, i don't have too much space or time, so my idea is (as just done
> before):
>
> 1) P2V the server in my test cluster
>
> 2) reinstall the server with pve, join to the cluster
>
> 3) migrate the VM to the server.
>
> 4) 'detach' the cluster, eg, following:
>
> https://pve.proxmox.com/wiki/Cluster_Manager
>
> delete from server my test cluster and delete from test cluster my
> server.
>
>
> But is this way the server will belong to my 'test cluster', and
> clusters cannot be renamed, right?
>
> There's some way to 'uncluster' a server?
>
>
> Thanks.
>
> --
> dott. Marco Gaiarin GNUPG Key ID:
> 240A3D66
> Associazione ``La Nostra Famiglia''
> http://www.lanostrafamiglia.it/
> Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento
> (PN)
> marco.gaiarin(at)lanostrafamiglia.it t +39-0434-842711 f
> +39-0434-842797
>
> Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
> http://www.lanostrafamiglia.it/index.php/it/sostienici/5x1000
> (cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
> --
Sent from Gmail Mobile
next prev parent reply other threads:[~2020-07-25 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-25 12:52 Marco Gaiarin
2020-07-25 17:38 ` Yannis Milios [this message]
2020-08-04 12:22 ` Marco Gaiarin
2020-08-04 16:08 ` Yannis Milios
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='CAFiF2Opc5Lt20wcDT=RmWa=gVkbBtsnE+9=d32FKNbFeaWibHA@mail.gmail.com' \
--to=yannis.milios@gmail.com \
--cc=pve-user@pve.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