Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

PetaSAN 3.0 Released!

Pages: 1 2
Happy to announce our latest release PetaSAN 3.0!
New Features:
  • Ubuntu 20.04 Focal
  • S3 enhanced multisite management
    • Pull master zone configuration.
    • Promote zone.
    • Edit remote endpoints.
    • Subuser support.
    • User stats: size/number of objects used.
  • PG Autoscaling
  • Replace Node support in Deployment Wizard (Management or Storage nodes).
  • Write Cache enhancements.
  • NVME SMART metrics.

Notes:

-Upgrade from 2.8.X via upgrade script,see latest Online Upgrade Guide for more details.

Tried to upgrade and getting "authentication timed out after 300" on 3 of the 4 nodes.
Then times out with "RADOS timed out (error connecting to the cluster)"

I upgraded from 2.8.1 to 3.0 rebooting after the upgrade.

I lost the 4th node due to hardware failure.

Not sure how to fix this but since its a lab its not that big a deal, but I am about to deploy into production and this is the sort of thing that is bad.

Anyone else upgrade without issues or with this issue?

It seems my backend networking is not loading on reboot.
I assume that since my backend network is offline, the cluster is going to remain offline.

I just successfully upgraded my brand new cluster from 2.8.1 to 3.0.0. I only experienced a "clock skew" issue on 2 monitors, but it was easily fixed.

But I have a question regarding the upgrade: at the and of the script it says "...to run apt update when possible to update repository database". After the  apt command, 99 package can be upgraded. Shell I perform an "apt upgrade" for these packages to complete the overall upgrading process, or this action should never be performed because the script takes care to upgrade only the needed packages ?

Reading package lists... Done
Building dependency tree
Reading state information... Done
99 packages can be upgraded. Run 'apt list --upgradable' to see them.

Thanks and bye. Ste

Hi tried to install on DL380p sdcard but do not boot after instalation complete.

you can run apt update/upgrade after the script completes but it is optional. it will update any Ubuntu base OS packages, if you run the update/upgrade commands a few days later you will get other updated packages. Note that unlike prev PetaSAN upgrades, the current script sets up a local offline repository to make sure we have all packages prior to starting since going from 18.04 to 20.04 a lot files need to be changes, the offline repository will always be behind the latest online base OS changes similar to installing from iso.

Quote from admin on December 15, 2021, 9:37 pm

if you run the update/upgrade commands a few days later you will get other updated packages.

Exactly, I just want to be sure that I don't break any dependancy if I update OS packages in a different petasan upgrade time...

Thanks.

Hello,

just fresh installed PetaSan 3.0. Unfortunately i can't add OSDs. Error says "Make sure all selected disks are equal or larger than 64 GB". I have 10x 1,7TB ssd drives. On 2.8.1 problem does not exist.

Any quick fix for this? Anyone?

Thanks

After upgrade, the MDS and MGR will not start on any of the 3 remaining nodes.

Tried to re-create MGR service and it doesn't work.

Please let me know if I need to start a new topic for this.

Re 64GB disk size error, we will look into this.

Re MDS/MGR : could this be load issues ? do you have correct hardware requirements ? have you solved the earlier network issue ? was cluster healthy before upgrade ? yes it is better to post in the bugs topics

 

Pages: 1 2