There's a major NVMe effort underway but it's not even merged to
master yet, so I'm not sure how docs would have ended up in the Reef
doc tree. :/ Zac, any idea? Can we pull this out?
-Greg
On Thu, May 30, 2024 at 7:03 AM Robert Sander
wrote:
>
> Hi,
>
> On 5/30/24 14:18, Frédéric Nass wrote:
>
Hi,
On 5/30/24 14:18, Frédéric Nass wrote:
ceph config set mgr mgr/cephadm/container_image_nvmeof
"quay.io/ceph/nvmeof:1.2.13"
Thanks for the hint. With that the orchestrator deploys the current container
image.
But: It suddenly listens on port 5499 instead of 5500 and:
# podman run -it q
I've never used this feature, but I wanted to point out your command versus
the error message; gateway-name / gateway_name (dash versus underscore)
On Thu, May 30, 2024 at 5:07 AM Robert Sander
wrote:
> Hi,
>
> I am trying to follow the documentation at
> https://docs.ceph.com/en/reef/rbd/nvmeof
On Thursday, May 30, 2024 7:03:44 AM EDT Robert Sander wrote:
> Hi,
>
> On 5/30/24 11:58, Robert Sander wrote:
>
>
> > I am trying to follow the documentation at
> > https://docs.ceph.com/en/reef/rbd/nvmeof-target-configure/ to deploy an
> > NVMe over Fabric service.
>
>
> It looks like the
Hello Robert,
You could try:
ceph config set mgr mgr/cephadm/container_image_nvmeof
"quay.io/ceph/nvmeof:1.2.13" or whatever image tag you need (1.2.13 is current
latest).
Another way to run the image is by editing the unit.run file of the service or
by directly running the container with pod
Hi,
On 5/30/24 11:58, Robert Sander wrote:
I am trying to follow the documentation at
https://docs.ceph.com/en/reef/rbd/nvmeof-target-configure/ to deploy an
NVMe over Fabric service.
It looks like the cephadm orchestrator in this 18.2.2 cluster uses the image
quay.io/ceph/nvmeof:0.0.2 whic
