admin
2,930 Posts
Quote from admin on January 20, 2023, 9:53 am
Hello all,
Thought to give you an update on upcoming PetaSAN 3.2 release and some cool screenshots 🙂.
PetaSAN v 3.2 main feaures:
- Take manual and automated snaphots for iSCSI, CIFS/SMB, NFS.
- Configure schedule and lifecycle for automated snapshots.
- Export snaphots for read only access.
- Roll-back current disk, share or export to a particular snapshot.
- Genetal UI improvements, bug fixes.
- Ceph Quincy 17.2.5 or Octopus 15.2.17 (based on current testing).
- Kernel 5.14 based on latest SUSE SLE 15 SP4.
Disk Snapshots
Disk Snapshots
Configure Automated Schedule
Configure Automated Schedule
Rollback/Export Snapshot
Hello all,
Thought to give you an update on upcoming PetaSAN 3.2 release and some cool screenshots 🙂.
PetaSAN v 3.2 main feaures:
- Take manual and automated snaphots for iSCSI, CIFS/SMB, NFS.
- Configure schedule and lifecycle for automated snapshots.
- Export snaphots for read only access.
- Roll-back current disk, share or export to a particular snapshot.
- Genetal UI improvements, bug fixes.
- Ceph Quincy 17.2.5 or Octopus 15.2.17 (based on current testing).
- Kernel 5.14 based on latest SUSE SLE 15 SP4.
Disk Snapshots
Disk Snapshots
Configure Automated Schedule
Configure Automated Schedule
Rollback/Export Snapshot
gb.123
4 Posts
Quote from gb.123 on January 20, 2023, 8:47 pm
Nice!
Octopus is already out of active release and now under archive release. Going with Quincy would be better. Performance hiccups (if any can be ironed out later)
Is there any chance that the user can update the underlying Ceph without upgrading the PetaSAN? eg. if PetaSAN includes Octopus, then the user can update to Quincy without updating PetaSAN? Or is the PetaSAN software too closely tied up making upgradation of underlying Ceph not possible  ?
Nice!
Octopus is already out of active release and now under archive release. Going with Quincy would be better. Performance hiccups (if any can be ironed out later)
Is there any chance that the user can update the underlying Ceph without upgrading the PetaSAN? eg. if PetaSAN includes Octopus, then the user can update to Quincy without updating PetaSAN? Or is the PetaSAN software too closely tied up making upgradation of underlying Ceph not possible  ?
admin
2,930 Posts
Quote from admin on January 20, 2023, 10:01 pm
Yes going with Quincy is our preference for 3.2 but just in case we decide to delay it, we will support Octopus ourselves.
We do have slight changes to Ceph and kernel changes to support things like active/active iSCSI, so you should not use regular upstream Ceph, it will work in most cases but not some special cases we support. You could choose to upgrade the PetaSAN builds of Ceph and kernel from our online repo without updating PetaSAN UI and services, you could but it is not something we test and there should be little reason to want to do this.
Yes going with Quincy is our preference for 3.2 but just in case we decide to delay it, we will support Octopus ourselves.
We do have slight changes to Ceph and kernel changes to support things like active/active iSCSI, so you should not use regular upstream Ceph, it will work in most cases but not some special cases we support. You could choose to upgrade the PetaSAN builds of Ceph and kernel from our online repo without updating PetaSAN UI and services, you could but it is not something we test and there should be little reason to want to do this.
X1M
5 Posts
Quote from X1M on January 24, 2023, 11:28 am
NICE, thank you for your hard work! Looking forward to installing the new version. 🙂
NICE, thank you for your hard work! Looking forward to installing the new version. 🙂
wluke
66 Posts
Quote from wluke on January 25, 2023, 10:35 pm
Great news, excited for the new release, thanks for all the work!
Great news, excited for the new release, thanks for all the work!
gb.123
4 Posts
Quote from gb.123 on January 29, 2023, 7:49 pm
Quote from admin on January 20, 2023, 10:01 pm
Yes going with Quincy is our preference for 3.2 but just in case we decide to delay it, we will support Octopus ourselves.
We do have slight changes to Ceph and kernel changes to support things like active/active iSCSI, so you should not use regular upstream Ceph, it will work in most cases but not some special cases we support. You could choose to upgrade the PetaSAN builds of Ceph and kernel from our online repo without updating PetaSAN UI and services, you could but it is not something we test and there should be little reason to want to do this.
I agree with you... Upgrading from PetaSAN build of Ceph without upgrading UI won't make sense. However, getting latest upstream Ceph (eg. if PetaSAN launches with Octopus, one could update to Quincy before PetSAN ) was the basic idea of asking the question.
Quote from admin on January 20, 2023, 10:01 pm
Yes going with Quincy is our preference for 3.2 but just in case we decide to delay it, we will support Octopus ourselves.
We do have slight changes to Ceph and kernel changes to support things like active/active iSCSI, so you should not use regular upstream Ceph, it will work in most cases but not some special cases we support. You could choose to upgrade the PetaSAN builds of Ceph and kernel from our online repo without updating PetaSAN UI and services, you could but it is not something we test and there should be little reason to want to do this.
I agree with you... Upgrading from PetaSAN build of Ceph without upgrading UI won't make sense. However, getting latest upstream Ceph (eg. if PetaSAN launches with Octopus, one could update to Quincy before PetSAN ) was the basic idea of asking the question.
admin
2,930 Posts
Quote from admin on January 29, 2023, 9:28 pm
Yes that could also occur, it is possible we could do that.
Yes that could also occur, it is possible we could do that.
