For a production cluster I would actually recommend two physically separated
networks for corosync.
https://pve.proxmox.com/wiki/Separate_Cluster_Network#Redundant_Ring_Protocol
Cheers
Stefan
On Dec 5, 2018, at 13:55, Eneko Lacunza
mailto:elacu...@binovo.es>> wrote:
Hi Stefan,
Thanks a lot
Hello Eneko,
On Mon, Dec 17, 2018 at 09:23:36AM +0100, Eneko Lacunza wrote:
> Hi,
>
> El 16/12/18 a las 17:16, Frank Thommen escribió:
> > > > I understand that with the new PVE release PVE hosts
> > > > (hypervisors) can be
> > > > used as Ceph servers. But it's not clear to me if (or when)
On 17.12.2018 11:52, Frank Thommen wrote:
Hi Alwin,
On 12/16/18 7:47 PM, Alwin Antreich wrote:
On Sun, Dec 16, 2018 at 05:16:50PM +0100, Frank Thommen wrote:
Hi Alwin,
On 16/12/18 15:39, Alwin Antreich wrote:
Hello Frank,
On Sun, Dec 16, 2018 at 02:28:19PM +0100, Frank Thommen wrote:
Hi,
On 12/17/18 9:23 AM, Eneko Lacunza wrote:
Hi,
El 16/12/18 a las 17:16, Frank Thommen escribió:
I understand that with the new PVE release PVE hosts (hypervisors)
can be
used as Ceph servers. But it's not clear to me if (or when) that makes
sense. Do I really want to have Ceph MDS/OSD on the
Hi Alwin,
On 12/16/18 7:47 PM, Alwin Antreich wrote:
On Sun, Dec 16, 2018 at 05:16:50PM +0100, Frank Thommen wrote:
Hi Alwin,
On 16/12/18 15:39, Alwin Antreich wrote:
Hello Frank,
On Sun, Dec 16, 2018 at 02:28:19PM +0100, Frank Thommen wrote:
Hi,
I understand that with the new PVE release
Hi Alwin,
El 17/12/18 a las 10:22, Alwin Antreich escribió:
b) depends on the workload of your nodes. Modern server hardware has
enough power to be able to run multiple services. It all comes down to
have enough resources for each domain (eg. Ceph, KVM, CT, host).
I recommend to use a simple
for import, you can do it with command line only.
for an ovf:
qm importovf[OPTIONS]
for only 1disk:
qm importdisk[OPTIONS]
For export, they are no command line currently.
(but you can use "qemu-img convert ..." to convert disk to vmdk or other
format.)
- Mail original -