Hi,
As I read the documentation[1] the "count: 1" handles that so what I
have is a placement pool from which only one is selected for
deployment?
you're probably right, when using your example command with multiple
hosts it automatically sets "count:1" (don't mind the hostnames, it's
an
On 31/01/2024 09:52, Eugen Block wrote:
I deployed the nfs with ceph version 17.2.7 and then upgraded to 18.2.1
successfully, the ingress service is still present. Can you tell if it
was there while you were on quincy? To fix it I would just apply the
nfs.yaml again and see if the ingress ser
I deployed the nfs with ceph version 17.2.7 and then upgraded to
18.2.1 successfully, the ingress service is still present. Can you
tell if it was there while you were on quincy? To fix it I would just
apply the nfs.yaml again and see if the ingress service is deployed.
To know what happene
I believe so, I just deployed it with the same command as you did, but
on a single-node cluster (hence only one host):
ceph:~ # ceph orch ls
NAME PORTS RUNNING REFRESHED AGE PLACEMENT
crash 1/1 3m ago 44m *
ingress.nfs.
On 31/01/2024 09:36, Eugen Block wrote:
Hi,
if I understand this correctly, with the "keepalive-only" option only
one ganesha instance is supposed to be deployed:
If a user additionally supplies --ingress-mode keepalive-only a
partial ingress service will be deployed that still provides a
On 31/01/2024 08:38, Torkil Svensgaard wrote:
Hi
Last week we created an NFS service like this:
"
ceph nfs cluster create jumbo "ceph-flash1,ceph-flash2,ceph-flash3"
--ingress --virtual_ip 172.21.15.74/22 --ingress-mode keepalive-only
"
Worked like a charm. Yesterday we upgraded from 17.2.
Hi,
if I understand this correctly, with the "keepalive-only" option only
one ganesha instance is supposed to be deployed:
If a user additionally supplies --ingress-mode keepalive-only a
partial ingress service will be deployed that still provides a
virtual IP, but has nfs directly bindin
