Petasan with Openstack
Ste
125 Posts
January 7, 2022, 12:21 pmQuote from Ste on January 7, 2022, 12:21 pmHi, I'm testing using my Petasan cluster with Openstack, I created a dedicated rbd pool and three dedicated users for glance, cinder and nova. At present time it seems to work fine, openstack nodes connect to Petasan and volumes are successfully created via RBD. What I find curious is that I see the openstack volumes listed in the iSCSI page of Petasan UI, because iSCSI protocol is not used at all in the Openstack cluster. In fact they are not attached to anything.
Another question is: is it normal that the openstack nodes want to talk to petasan nodes on the backend network instead of the management network ? As they need the file "ceph.conf", and in that file the monitors are listed with their backend IP addresses.
Thanks, Ste.
Hi, I'm testing using my Petasan cluster with Openstack, I created a dedicated rbd pool and three dedicated users for glance, cinder and nova. At present time it seems to work fine, openstack nodes connect to Petasan and volumes are successfully created via RBD. What I find curious is that I see the openstack volumes listed in the iSCSI page of Petasan UI, because iSCSI protocol is not used at all in the Openstack cluster. In fact they are not attached to anything.
Another question is: is it normal that the openstack nodes want to talk to petasan nodes on the backend network instead of the management network ? As they need the file "ceph.conf", and in that file the monitors are listed with their backend IP addresses.
Thanks, Ste.
Last edited on January 7, 2022, 12:25 pm by Ste · #1
admin
2,930 Posts
January 7, 2022, 7:25 pmQuote from admin on January 7, 2022, 7:25 pmThe non-iSCSI images in rbd pool(s) will be listed in the iSCSI disks page as "detached", you can if you wish, attach the rbd images and make them accessible to iSCSI, or the other way, detach iSCSI images and access them directly with rbd from Openstack or any other client.
Yes if you wish to access the rbd images on PetaSAN directly, use the backend network. Management is only for system administration, not for i/o.
The non-iSCSI images in rbd pool(s) will be listed in the iSCSI disks page as "detached", you can if you wish, attach the rbd images and make them accessible to iSCSI, or the other way, detach iSCSI images and access them directly with rbd from Openstack or any other client.
Yes if you wish to access the rbd images on PetaSAN directly, use the backend network. Management is only for system administration, not for i/o.
Ste
125 Posts
January 12, 2022, 11:22 amQuote from Ste on January 12, 2022, 11:22 amOk, got it. Thanks
Ok, got it. Thanks
Petasan with Openstack
Ste
125 Posts
Quote from Ste on January 7, 2022, 12:21 pmHi, I'm testing using my Petasan cluster with Openstack, I created a dedicated rbd pool and three dedicated users for glance, cinder and nova. At present time it seems to work fine, openstack nodes connect to Petasan and volumes are successfully created via RBD. What I find curious is that I see the openstack volumes listed in the iSCSI page of Petasan UI, because iSCSI protocol is not used at all in the Openstack cluster. In fact they are not attached to anything.
Another question is: is it normal that the openstack nodes want to talk to petasan nodes on the backend network instead of the management network ? As they need the file "ceph.conf", and in that file the monitors are listed with their backend IP addresses.
Thanks, Ste.
Hi, I'm testing using my Petasan cluster with Openstack, I created a dedicated rbd pool and three dedicated users for glance, cinder and nova. At present time it seems to work fine, openstack nodes connect to Petasan and volumes are successfully created via RBD. What I find curious is that I see the openstack volumes listed in the iSCSI page of Petasan UI, because iSCSI protocol is not used at all in the Openstack cluster. In fact they are not attached to anything.
Another question is: is it normal that the openstack nodes want to talk to petasan nodes on the backend network instead of the management network ? As they need the file "ceph.conf", and in that file the monitors are listed with their backend IP addresses.
Thanks, Ste.
admin
2,930 Posts
Quote from admin on January 7, 2022, 7:25 pmThe non-iSCSI images in rbd pool(s) will be listed in the iSCSI disks page as "detached", you can if you wish, attach the rbd images and make them accessible to iSCSI, or the other way, detach iSCSI images and access them directly with rbd from Openstack or any other client.
Yes if you wish to access the rbd images on PetaSAN directly, use the backend network. Management is only for system administration, not for i/o.
The non-iSCSI images in rbd pool(s) will be listed in the iSCSI disks page as "detached", you can if you wish, attach the rbd images and make them accessible to iSCSI, or the other way, detach iSCSI images and access them directly with rbd from Openstack or any other client.
Yes if you wish to access the rbd images on PetaSAN directly, use the backend network. Management is only for system administration, not for i/o.
Ste
125 Posts
Quote from Ste on January 12, 2022, 11:22 amOk, got it. Thanks
Ok, got it. Thanks