Forums

Home / Forums

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

PetaSAN v 2.0 released!

Pages: 1 2

Happy to announce the release of PetaSAN v 2.0 which includes the following:

  • Support Ceph Luminous 12.2.2 (latest stable) with Bluestore engine.
  • Allow placing Journal WAL/DB on external faster devices.
  • Enable/Disable real-time data compression using various algorithms.

Note: For users upgrading from earlier versions, please refer to the Release 2.0 Upgrade Guide.

Thanks for the new release guys,

I'm having a problem running the upgrade script. the "upgrade" directory only includes "1.2.0" and "1.2.3". I'm upgrading from 1.5 to 2.0. Here is the error i'm getting:

-bash: /opt/petasan/scripts/upgrade/1.5.0/update_ceph_conf.py: No such file or directory

It looks like you still have the old 1.5 and not the 2.0 package..can you double check you did step 5

apt-get upgrade petasan

Quote from admin on February 12, 2018, 10:31 pm

It looks like you still have the old 1.5 and not the 2.0 package..can you double check you did step 5

apt-get upgrade petasan

Yes. here is the output:

user1@Node1:~# apt-get upgrade petasan
Reading package lists... Done
Building dependency tree
Reading state information... Done
petasan is already the newest version (1.5.0).
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

But when i check the path, it only gives me these two versions:
user1@Node1:~# cd /opt/petasan/scripts/upgrade/
user1@Node1:/opt/petasan/scripts/upgrade# ls
1.2.0 1.2.3

The upgrade output means it is not see-ing the new 2.0 update repository files.

The issue has to do with earlier steps (1 to 4).  Can you please show the output of

 

ls /petasan-2.0-upgrade
cat /etc/apt/sources.list
apt-get update

 

 

We are looking at that folder and only 1.2.0 and 1.2.3 exists.  My theory is ...

We had 1.4 installed fresh, installed 1.5 over 1.4.  I don't think the disk was formatted in between.

Then we are trying the .tar.gz for 2.0.

 

I have another cluster in VM on my machine to test these things, I have a fresh 1.5 from blank and it works until we get to the create_mgr.py scripts,  complains about bad entity name...  Do we need to provide a name after create_mgr.py ?

Ps. In case you haven't figured it out, we're working together in the same lab.

M.

Seeing old v 1.2.0 and 1.2.3 folders in the update directory is not a problem,

The issue relates to a problem setting up the upgrade repository, the output of the 3 commands earlier will help know which step failed. As for the second issue, no you do not need to provide a name for create_mgr. can you post more detail on what you mean by complains about entity name ? please post the full output for both issues.

After completing steps 1-8 on all 3 nodes  (on my VM Cluster, peta15-1, 2, 3 for host names). afrima is using another cluster, bare metal in his case.

 

root@peta15-1:/opt/petasan/scripts# ./create_mgr.py
Error EINVAL: bad entity name

M.

Quote from admin on February 13, 2018, 3:26 pm

The upgrade output means it is not see-ing the new 2.0 update repository files.

The issue has to do with earlier steps (1 to 4).  Can you please show the output of

 

ls /petasan-2.0-upgrade
cat /etc/apt/sources.list
apt-get update

 

 

Here is the output of the above commands:

 

user1@Node1:/# ls /petasan-2.0-upgrade
Packages.gz libradosstriper1_12.2.2-1xenial_amd64.deb python-ndg-httpsclient_0.4.0-3_all.deb
binutils_2.26.1-1ubuntu1~16.04.4_amd64.deb librbd1_12.2.2-1xenial_amd64.deb python-openid_2.2.5-6_all.deb
ca-certificates_20160104ubuntu1_all.deb libreadline5_5.2+dfsg-3build1_amd64.deb python-paste_1.7.5.1-6ubuntu3_all.deb
ceph-base_12.2.2-1xenial_amd64.deb librgw2_12.2.2-1xenial_amd64.deb python-pastedeploy-tpl_1.5.2-1_all.deb
ceph-common_12.2.2-1xenial_amd64.deb libsnappy1v5_1.1.3-2_amd64.deb python-pastedeploy_1.5.2-1_all.deb
ceph-deploy_1.5.38_all.deb libtcmalloc-minimal4_2.4-0ubuntu5.16.04.1_amd64.deb python-pastescript_1.7.5-3build1_all.deb
ceph-mgr_12.2.2-1xenial_amd64.deb libunwind8_1.1-4.1_amd64.deb python-pecan_1.0.2-2ubuntu1_all.deb
ceph-mon_12.2.2-1xenial_amd64.deb libxslt1.1_1.1.28-2.1ubuntu0.1_amd64.deb python-pyinotify_0.9.6-0fakesync1_all.deb
ceph-osd_12.2.2-1xenial_amd64.deb logrotate_3.8.7-2ubuntu2.16.04.2_amd64.deb python-rados_12.2.2-1xenial_amd64.deb
ceph_12.2.2-1xenial_amd64.deb parted_3.2-15_amd64.deb python-rbd_12.2.2-1xenial_amd64.deb
cryptsetup-bin_2%3a1.6.6-5ubuntu2_amd64.deb ps-lrbd-1.0-2.deb python-repoze.lru_0.6-6_all.deb
dh-python_2.20151103ubuntu1.1_all.deb ps-petasan-2.0.0.deb python-requests_2.9.1-3_all.deb
formencode-i18n_1.3.0-0ubuntu5_all.deb ps-python-consul-0.4-7.deb python-rgw_12.2.2-1xenial_amd64.deb
gdisk_1.0.1-1build1_amd64.deb ps-python-dialog-2.14.deb python-routes_2.2-1ubuntu2_all.deb
groff-base_1.22.3-7_amd64.deb ps-python-retry-0.9.2.deb python-scgi_1.13-1.1build1_amd64.deb
javascript-common_11_all.deb ps-python-rtslib-2.2-15.deb python-setuptools_20.7.0-1_all.deb
libbabeltrace-ctf1_1.3.2-1_amd64.deb ps-stats-config-2.0.0.deb python-simplegeneric_0.8.1-1_all.deb
libbabeltrace1_1.3.2-1_amd64.deb ps-targetcli-2.1-9.deb python-singledispatch_3.4.0.3-2_all.deb
libcephfs2_12.2.2-1xenial_amd64.deb python-blinker_1.3.dfsg2-1build1_all.deb python-tempita_0.5.2-1build1_all.deb
libgoogle-perftools4_2.4-0ubuntu5.16.04.1_amd64.deb python-bs4_4.4.1-1_all.deb python-urllib3_1.13.1-2ubuntu0.16.04.1_all.deb
libjs-jquery_1.11.3+dfsg-4_all.deb python-ceph_12.2.2-1xenial_amd64.deb python-waitress_0.8.10-1_all.deb
libjs-sphinxdoc_1.3.6-2ubuntu1.1_all.deb python-cephfs_12.2.2-1xenial_amd64.deb python-webob_1.5.1-1_all.deb
libjs-underscore_1.7.0~dfsg-1ubuntu1_all.deb python-chardet_2.3.0-2_all.deb python-webtest_2.0.18-1ubuntu1_all.deb
libleveldb1v5_1.18-5_amd64.deb python-cherrypy3_3.5.0-2build1_all.deb python-werkzeug_0.10.4+dfsg1-1ubuntu1_all.deb
liblttng-ust-ctl2_2.7.1-1_amd64.deb python-dnspython_1.12.0-1_all.deb python3-minimal_3.5.1-3_amd64.deb
liblttng-ust0_2.7.1-1_amd64.deb python-flask_0.10.1-2build2_all.deb python3-rados_12.2.2-1xenial_amd64.deb
libmpdec2_2.4.2-1_amd64.deb python-formencode_1.3.0-0ubuntu5_all.deb python3-rbd_12.2.2-1xenial_amd64.deb
libparted2_3.2-15_amd64.deb python-html5lib_0.999-4_all.deb python3.5-minimal_3.5.2-2ubuntu0~16.04.1_amd64.deb
libpopt0_1.16-10_amd64.deb python-itsdangerous_0.24+dfsg1-1_all.deb python3.5_3.5.2-2ubuntu0~16.04.1_amd64.deb
libpython3-stdlib_3.5.1-3_amd64.deb python-jinja2_2.8-1_all.deb python3_3.5.1-3_amd64.deb
libpython3.5-minimal_3.5.2-2ubuntu0~16.04.1_amd64.deb python-logutils_0.3.3-5_all.deb rbd-mirror_12.2.2-1xenial_amd64.deb
libpython3.5-stdlib_3.5.2-2ubuntu0~16.04.1_amd64.deb python-lxml_3.5.0-1build1_amd64.deb rbd-nbd_12.2.2-1xenial_amd64.deb
libpython3.5_3.5.2-2ubuntu0~16.04.1_amd64.deb python-mako_1.0.3+ds1-1ubuntu1_all.deb xfsprogs_4.3.0+nmu1ubuntu1_amd64.deb
librados2_12.2.2-1xenial_amd64.deb python-markupsafe_0.23-2build2_amd64.deb

 

user1@Node1:/# cat /etc/apt/sources.list

deb file:/petasan-2.0-upgrade /

user1@Node1:/etc/apt# apt-get update
Get:1 file:/petasan-2.0-upgrade InRelease
Ign:1 file:/petasan-2.0-upgrade InRelease
Get:2 file:/petasan-2.0-upgrade Release
Ign:2 file:/petasan-2.0-upgrade Release
Get:3 file:/petasan-2.0-upgrade Packages
Ign:3 file:/petasan-2.0-upgrade Packages
Get:4 file:/petasan-2.0-upgrade Translation-en
Ign:4 file:/petasan-2.0-upgrade Translation-en
Get:3 file:/petasan-2.0-upgrade Packages
Ign:3 file:/petasan-2.0-upgrade Packages
Get:4 file:/petasan-2.0-upgrade Translation-en
Ign:4 file:/petasan-2.0-upgrade Translation-en
Get:3 file:/petasan-2.0-upgrade Packages
Ign:3 file:/petasan-2.0-upgrade Packages
Get:4 file:/petasan-2.0-upgrade Translation-en
Ign:4 file:/petasan-2.0-upgrade Translation-en
Get:3 file:/petasan-2.0-upgrade Packages [31.7 kB]
Get:4 file:/petasan-2.0-upgrade Translation-en
Ign:4 file:/petasan-2.0-upgrade Translation-en
Get:4 file:/petasan-2.0-upgrade Translation-en
Ign:4 file:/petasan-2.0-upgrade Translation-en
Get:4 file:/petasan-2.0-upgrade Translation-en
Ign:4 file:/petasan-2.0-upgrade Translation-en
Reading package lists... Done
W: The repository 'file:/petasan-2.0-upgrade Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.

 

For the repository issue, the output you posted looks good. the command

apt-get upgrade petasan

should now be able to detect the v 2.0 packages, i really do not know why it is not working in your case. If you do find any clues or if you can reproduce it do let me know.

For the second cluster,  the

Error EINVAL: bad entity name

happens according to   https://github.com/ceph/ceph-ansible/issues/2343  if you create mgr before the new Luminous monitors were restarted. Can you make sure Ceph has been upgraded and you started the upgraded monitors on all 3 nodes.

Pages: 1 2