how to build PetaSAN source
Pages: 1 2
love_vicky
8 Posts
March 17, 2017, 2:02 amQuote from love_vicky on March 17, 2017, 2:02 amSorry to disturb ,our application was build on Centos 7 ,so I want compile PetaSAN on Centos. But I compile the kernel you offer ,and do the patch. Also deploy ceph jewel. But It doesn't work well, the OS can't identify the rbd as a same lun. There have any works I haven't done yet?or there is any doc could help ?
Sorry to disturb ,our application was build on Centos 7 ,so I want compile PetaSAN on Centos. But I compile the kernel you offer ,and do the patch. Also deploy ceph jewel. But It doesn't work well, the OS can't identify the rbd as a same lun. There have any works I haven't done yet?or there is any doc could help ?
admin
2,930 Posts
March 17, 2017, 6:14 amQuote from admin on March 17, 2017, 6:14 amHello there, in order to help....i need a lot more detail than this.
-First I understand you did build from source without error but the problem is when you replaced ubuntu with centos and added your application, the system is not working correctly...is this correct ?
-The problem you simply state as "the OS can't identify the rbd as a same lun", where and at what stage do you see this ? Does the Management Web UI report an error or is it working correctly ?
-How did you deploy the new build ? Did you rebuild the installer CD with the centos packages ? Did you then install from the CD and run the Deployment Wizard and all was well ?
-What does you centos application do ? does it access the storage via iSCSI ? do you really need to co-exist on the same PetaSAN installation ?
Hello there, in order to help....i need a lot more detail than this.
-First I understand you did build from source without error but the problem is when you replaced ubuntu with centos and added your application, the system is not working correctly...is this correct ?
-The problem you simply state as "the OS can't identify the rbd as a same lun", where and at what stage do you see this ? Does the Management Web UI report an error or is it working correctly ?
-How did you deploy the new build ? Did you rebuild the installer CD with the centos packages ? Did you then install from the CD and run the Deployment Wizard and all was well ?
-What does you centos application do ? does it access the storage via iSCSI ? do you really need to co-exist on the same PetaSAN installation ?
love_vicky
8 Posts
March 17, 2017, 7:12 amQuote from love_vicky on March 17, 2017, 7:12 amsorry , forgive my terrible expression.
what I want:
I want to use PetaSAN on centos.
what I have done:
first: I compile kernel come from your source and I change the kernel of my centos, deploy the jewel ceph. And use targetcli configure the target. In my option , I think these job have been done , the OS multipath could identify a lun which come from two path, but It could not.
second: After configure work correctly , I will migrate the PetaSAN web management system on centos.
But I failed on first stage
sorry , forgive my terrible expression.
what I want:
I want to use PetaSAN on centos.
what I have done:
first: I compile kernel come from your source and I change the kernel of my centos, deploy the jewel ceph. And use targetcli configure the target. In my option , I think these job have been done , the OS multipath could identify a lun which come from two path, but It could not.
second: After configure work correctly , I will migrate the PetaSAN web management system on centos.
But I failed on first stage
admin
2,930 Posts
March 17, 2017, 7:35 amQuote from admin on March 17, 2017, 7:35 amthanks for the clarifiations, things are clearer for me now. you are not using PetaSAN, just you are just using the kernel, the rest is pure centos. What i recommend is before using the kernel you built, first use the binary that came with PetaSAN just to prevent any built issues from your side. The Ceph Jewel from repo should be good for now but later you should apply the source patch to support VMWare.
thanks for the clarifiations, things are clearer for me now. you are not using PetaSAN, just you are just using the kernel, the rest is pure centos. What i recommend is before using the kernel you built, first use the binary that came with PetaSAN just to prevent any built issues from your side. The Ceph Jewel from repo should be good for now but later you should apply the source patch to support VMWare.
love_vicky
8 Posts
March 17, 2017, 7:41 amQuote from love_vicky on March 17, 2017, 7:41 amsorry , what do you mean by "use the binary that came with PetaSAN" , you mean the iso file?
sorry , what do you mean by "use the binary that came with PetaSAN" , you mean the iso file?
admin
2,930 Posts
March 17, 2017, 8:37 amQuote from admin on March 17, 2017, 8:37 amThe kernel. For your test you can use the binary kernel that came with Petasan instead of compiling the PetaSAN kernel yourself
The kernel. For your test you can use the binary kernel that came with Petasan instead of compiling the PetaSAN kernel yourself
Last edited on March 17, 2017, 8:41 am · #6
love_vicky
8 Posts
March 17, 2017, 8:52 amQuote from love_vicky on March 17, 2017, 8:52 amsorry , I don't know how to get the "binary kernel that came with Petasan" .
I didn't see the tar file or some thing. Could you tell me how to get it ?
sorry , I don't know how to get the "binary kernel that came with Petasan" .
I didn't see the tar file or some thing. Could you tell me how to get it ?
admin
2,930 Posts
March 17, 2017, 9:04 amQuote from admin on March 17, 2017, 9:04 amOK. You did build the kernel yourself and installed it and is running now. It installs the binary files you built in /boot and in /lib/modules.
You can (if you wish) copy the same files from a PetaSAN system ( installed from iso ) using a tool like scp.
This was just a suggestion to make things easier a this stage 🙂
OK. You did build the kernel yourself and installed it and is running now. It installs the binary files you built in /boot and in /lib/modules.
You can (if you wish) copy the same files from a PetaSAN system ( installed from iso ) using a tool like scp.
This was just a suggestion to make things easier a this stage 🙂
Last edited on March 17, 2017, 9:05 am · #8
admin
2,930 Posts
March 17, 2017, 11:46 amQuote from admin on March 17, 2017, 11:46 amAnother thing: better to test using the targetcli that is included in the PetaSAN CD and not use the one in the Centos distro. targetcli also depends on another file python-rtlib. So copy these 2 files to your Centos system ( overide existing ones), these are python source files that do not need building. Note we left targetcli in PetaSAN for advanced users using cli but we do not actually use it.
When you start integrating PetaSAN, you will need all the required python libraries. It may be possible just to use the equivalent python libs that come with Centos distro, in case you get issues, you may need to copy the files from the PetaSAN CD, they are all source and do not require building.
Good luck.
Another thing: better to test using the targetcli that is included in the PetaSAN CD and not use the one in the Centos distro. targetcli also depends on another file python-rtlib. So copy these 2 files to your Centos system ( overide existing ones), these are python source files that do not need building. Note we left targetcli in PetaSAN for advanced users using cli but we do not actually use it.
When you start integrating PetaSAN, you will need all the required python libraries. It may be possible just to use the equivalent python libs that come with Centos distro, in case you get issues, you may need to copy the files from the PetaSAN CD, they are all source and do not require building.
Good luck.
love_vicky
8 Posts
March 23, 2017, 8:01 amQuote from love_vicky on March 23, 2017, 8:01 am3q all, I have work it out. The iscsi HA seemed work properly. I just compile the kernel as I had done, and copy the python files from the PetaSAN. Thank you again my problem had been solved.
3q all, I have work it out. The iscsi HA seemed work properly. I just compile the kernel as I had done, and copy the python files from the PetaSAN. Thank you again my problem had been solved.
Pages: 1 2
how to build PetaSAN source
love_vicky
8 Posts
Quote from love_vicky on March 17, 2017, 2:02 amSorry to disturb ,our application was build on Centos 7 ,so I want compile PetaSAN on Centos. But I compile the kernel you offer ,and do the patch. Also deploy ceph jewel. But It doesn't work well, the OS can't identify the rbd as a same lun. There have any works I haven't done yet?or there is any doc could help ?
Sorry to disturb ,our application was build on Centos 7 ,so I want compile PetaSAN on Centos. But I compile the kernel you offer ,and do the patch. Also deploy ceph jewel. But It doesn't work well, the OS can't identify the rbd as a same lun. There have any works I haven't done yet?or there is any doc could help ?
admin
2,930 Posts
Quote from admin on March 17, 2017, 6:14 amHello there, in order to help....i need a lot more detail than this.
-First I understand you did build from source without error but the problem is when you replaced ubuntu with centos and added your application, the system is not working correctly...is this correct ?
-The problem you simply state as "the OS can't identify the rbd as a same lun", where and at what stage do you see this ? Does the Management Web UI report an error or is it working correctly ?
-How did you deploy the new build ? Did you rebuild the installer CD with the centos packages ? Did you then install from the CD and run the Deployment Wizard and all was well ?
-What does you centos application do ? does it access the storage via iSCSI ? do you really need to co-exist on the same PetaSAN installation ?
Hello there, in order to help....i need a lot more detail than this.
-First I understand you did build from source without error but the problem is when you replaced ubuntu with centos and added your application, the system is not working correctly...is this correct ?
-The problem you simply state as "the OS can't identify the rbd as a same lun", where and at what stage do you see this ? Does the Management Web UI report an error or is it working correctly ?
-How did you deploy the new build ? Did you rebuild the installer CD with the centos packages ? Did you then install from the CD and run the Deployment Wizard and all was well ?
-What does you centos application do ? does it access the storage via iSCSI ? do you really need to co-exist on the same PetaSAN installation ?
love_vicky
8 Posts
Quote from love_vicky on March 17, 2017, 7:12 amsorry , forgive my terrible expression.
what I want:
I want to use PetaSAN on centos.
what I have done:
first: I compile kernel come from your source and I change the kernel of my centos, deploy the jewel ceph. And use targetcli configure the target. In my option , I think these job have been done , the OS multipath could identify a lun which come from two path, but It could not.
second: After configure work correctly , I will migrate the PetaSAN web management system on centos.
But I failed on first stage
sorry , forgive my terrible expression.
what I want:
I want to use PetaSAN on centos.
what I have done:
first: I compile kernel come from your source and I change the kernel of my centos, deploy the jewel ceph. And use targetcli configure the target. In my option , I think these job have been done , the OS multipath could identify a lun which come from two path, but It could not.
second: After configure work correctly , I will migrate the PetaSAN web management system on centos.
But I failed on first stage
admin
2,930 Posts
Quote from admin on March 17, 2017, 7:35 amthanks for the clarifiations, things are clearer for me now. you are not using PetaSAN, just you are just using the kernel, the rest is pure centos. What i recommend is before using the kernel you built, first use the binary that came with PetaSAN just to prevent any built issues from your side. The Ceph Jewel from repo should be good for now but later you should apply the source patch to support VMWare.
thanks for the clarifiations, things are clearer for me now. you are not using PetaSAN, just you are just using the kernel, the rest is pure centos. What i recommend is before using the kernel you built, first use the binary that came with PetaSAN just to prevent any built issues from your side. The Ceph Jewel from repo should be good for now but later you should apply the source patch to support VMWare.
love_vicky
8 Posts
Quote from love_vicky on March 17, 2017, 7:41 amsorry , what do you mean by "use the binary that came with PetaSAN" , you mean the iso file?
sorry , what do you mean by "use the binary that came with PetaSAN" , you mean the iso file?
admin
2,930 Posts
Quote from admin on March 17, 2017, 8:37 amThe kernel. For your test you can use the binary kernel that came with Petasan instead of compiling the PetaSAN kernel yourself
The kernel. For your test you can use the binary kernel that came with Petasan instead of compiling the PetaSAN kernel yourself
love_vicky
8 Posts
Quote from love_vicky on March 17, 2017, 8:52 amsorry , I don't know how to get the "binary kernel that came with Petasan" .
I didn't see the tar file or some thing. Could you tell me how to get it ?
sorry , I don't know how to get the "binary kernel that came with Petasan" .
I didn't see the tar file or some thing. Could you tell me how to get it ?
admin
2,930 Posts
Quote from admin on March 17, 2017, 9:04 amOK. You did build the kernel yourself and installed it and is running now. It installs the binary files you built in /boot and in /lib/modules.
You can (if you wish) copy the same files from a PetaSAN system ( installed from iso ) using a tool like scp.
This was just a suggestion to make things easier a this stage 🙂
OK. You did build the kernel yourself and installed it and is running now. It installs the binary files you built in /boot and in /lib/modules.
You can (if you wish) copy the same files from a PetaSAN system ( installed from iso ) using a tool like scp.
This was just a suggestion to make things easier a this stage 🙂
admin
2,930 Posts
Quote from admin on March 17, 2017, 11:46 amAnother thing: better to test using the targetcli that is included in the PetaSAN CD and not use the one in the Centos distro. targetcli also depends on another file python-rtlib. So copy these 2 files to your Centos system ( overide existing ones), these are python source files that do not need building. Note we left targetcli in PetaSAN for advanced users using cli but we do not actually use it.
When you start integrating PetaSAN, you will need all the required python libraries. It may be possible just to use the equivalent python libs that come with Centos distro, in case you get issues, you may need to copy the files from the PetaSAN CD, they are all source and do not require building.
Good luck.
Another thing: better to test using the targetcli that is included in the PetaSAN CD and not use the one in the Centos distro. targetcli also depends on another file python-rtlib. So copy these 2 files to your Centos system ( overide existing ones), these are python source files that do not need building. Note we left targetcli in PetaSAN for advanced users using cli but we do not actually use it.
When you start integrating PetaSAN, you will need all the required python libraries. It may be possible just to use the equivalent python libs that come with Centos distro, in case you get issues, you may need to copy the files from the PetaSAN CD, they are all source and do not require building.
Good luck.
love_vicky
8 Posts
Quote from love_vicky on March 23, 2017, 8:01 am3q all, I have work it out. The iscsi HA seemed work properly. I just compile the kernel as I had done, and copy the python files from the PetaSAN. Thank you again my problem had been solved.
3q all, I have work it out. The iscsi HA seemed work properly. I just compile the kernel as I had done, and copy the python files from the PetaSAN. Thank you again my problem had been solved.