2. RE: Zenoss 4 appears to have been axed

@Jane - SourceForge site is in the process of being updated. Older versions (2, 3, etc.) were removed. Working on the uploads today and will post back when the latest ones are up. Meantime the latest version 4 and version 6 of the Community Edition are on this community homepage. Version 6.3 on the horizon.

3. RE: Zenoss 4 appears to have been axed

Also, the spirit of open source is that you do not remove access to code - period. There is a current thread on the forum that is clearly still using Zenoss 3. I would suggest ALL code should be restored.

Obviously this also includes older SUPs, pristine packages, both versions of the zenup code, along with the various Zenoss Core rpms.

The auto-deploy script needs access to the dependencies code (also currently broken):

Original Message:Sent: 11-27-2018 10:50 AMFrom: John BoyleSubject: Zenoss 4 appears to have been axed

@Jane - SourceForge site is in the process of being updated. Older versions (2, 3, etc.) were removed. Working on the uploads today and will post back when the latest ones are up. Meantime the latest version 4 and version 6 of the Community Edition are on this community homepage. Version 6.3 on the horizon.

Also, the spirit of open source is that you do not remove access to code - period. There is a current thread on the forum that is clearly still using Zenoss 3. I would suggest ALL code should be restored.

Obviously this also includes older SUPs, pristine packages, both versions of the zenup code, along with the various Zenoss Core rpms.

The auto-deploy script needs access to the dependencies code (also currently broken):

Original Message:Sent: 11-27-2018 10:50 AMFrom: John BoyleSubject: Zenoss 4 appears to have been axed

@Jane - SourceForge site is in the process of being updated. Older versions (2, 3, etc.) were removed. Working on the uploads today and will post back when the latest ones are up. Meantime the latest version 4 and version 6 of the Community Edition are on this community homepage. Version 6.3 on the horizon.

5. RE: Zenoss 4 appears to have been axed

It is now a week since I reported that source code access has been removed, @John and we still only have SUP743 for Zenoss Core 4, plus the 4 base files for Zenoss 6. Please may we have an update on progress and an ETA for restoration of "open source"?

Also, the spirit of open source is that you do not remove access to code - period. There is a current thread on the forum that is clearly still using Zenoss 3. I would suggest ALL code should be restored.

Obviously this also includes older SUPs, pristine packages, both versions of the zenup code, along with the various Zenoss Core rpms.

The auto-deploy script needs access to the dependencies code (also currently broken):

Original Message:Sent: 11-27-2018 10:50 AMFrom: John BoyleSubject: Zenoss 4 appears to have been axed

@Jane - SourceForge site is in the process of being updated. Older versions (2, 3, etc.) were removed. Working on the uploads today and will post back when the latest ones are up. Meantime the latest version 4 and version 6 of the Community Edition are on this community homepage. Version 6.3 on the horizon.

6. RE: Zenoss 4 appears to have been axed

@Jane - Per previous post...the site is in process of being updated and this was planned for this month. If there is some pressing need for one of the out of maintenance versions please email me directly. Otherwise as previously posted I will post when we have completed posting the versions that will reside there moving forward.

It is now a week since I reported that source code access has been removed, @John and we still only have SUP743 for Zenoss Core 4, plus the 4 base files for Zenoss 6. Please may we have an update on progress and an ETA for restoration of "open source"?

Also, the spirit of open source is that you do not remove access to code - period. There is a current thread on the forum that is clearly still using Zenoss 3. I would suggest ALL code should be restored.

Obviously this also includes older SUPs, pristine packages, both versions of the zenup code, along with the various Zenoss Core rpms.

The auto-deploy script needs access to the dependencies code (also currently broken):

Original Message:Sent: 11-27-2018 10:50 AMFrom: John BoyleSubject: Zenoss 4 appears to have been axed

@Jane - SourceForge site is in the process of being updated. Older versions (2, 3, etc.) were removed. Working on the uploads today and will post back when the latest ones are up. Meantime the latest version 4 and version 6 of the Community Edition are on this community homepage. Version 6.3 on the horizon.

Also, the spirit of open source is that you do not remove access to code - period. There is a current thread on the forum that is clearly still using Zenoss 3. I would suggest ALL code should be restored.

Obviously this also includes older SUPs, pristine packages, both versions of the zenup code, along with the various Zenoss Core rpms.

The auto-deploy script needs access to the dependencies code (also currently broken):

Original Message:Sent: 11-27-2018 10:50 AMFrom: John BoyleSubject: Zenoss 4 appears to have been axed

@Jane - SourceForge site is in the process of being updated. Older versions (2, 3, etc.) were removed. Working on the uploads today and will post back when the latest ones are up. Meantime the latest version 4 and version 6 of the Community Edition are on this community homepage. Version 6.3 on the horizon.

Original Message:Sent: 11-27-2018 10:50 AMFrom: John BoyleSubject: Zenoss 4 appears to have been axed

@Jane - SourceForge site is in the process of being updated. Older versions (2, 3, etc.) were removed. Working on the uploads today and will post back when the latest ones are up. Meantime the latest version 4 and version 6 of the Community Edition are on this community homepage. Version 6.3 on the horizon.

So, it seems Zenoss Inc. has chosen the way to have Zenoss Core (mostly open sourced) community just for a PR.

------------------------------Serge

Original Message:Sent: 11-27-2018 10:50 AMFrom: John BoyleSubject: Zenoss 4 appears to have been axed

@Jane - SourceForge site is in the process of being updated. Older versions (2, 3, etc.) were removed. Working on the uploads today and will post back when the latest ones are up. Meantime the latest version 4 and version 6 of the Community Edition are on this community homepage. Version 6.3 on the horizon.

10. RE: Zenoss 4 appears to have been axed

Although we do now have the Zenoss Core rpm for RedHat 5 and 6, both 32-bit and 64-bit, the download directory at SourceForge has changed so the auto-install script breaks. This I can fix.

However SourceForge does NOT yet have the zenup rpm (ie not the latest SUP but the zenup program itself); neither do we have the pristine install that is required before you can install a SUP update. Please can we have these; otherwise no-one can apply any SUP updates to base Core 4.2.5.

So, it seems Zenoss Inc. has chosen the way to have Zenoss Core (mostly open sourced) community just for a PR.

------------------------------Serge

Original Message:Sent: 11-27-2018 10:50 AMFrom: John BoyleSubject: Zenoss 4 appears to have been axed

@Jane - SourceForge site is in the process of being updated. Older versions (2, 3, etc.) were removed. Working on the uploads today and will post back when the latest ones are up. Meantime the latest version 4 and version 6 of the Community Edition are on this community homepage. Version 6.3 on the horizon.

I am still hoping that Zenoss will supply the zenup and pristine on sourceforge; meanwhile the autodeploy script has a line:

CODEPATH="/home/jane/Zenoss_4.2.5_core-autodeploy"

I have provided the zenup rpm and the pristine file in the pre_req_downloads directory of the git package so, whilst we wait, copy those files from the package to somewhere on your build device and set CODEPATH in the autodeploy script to reflect that.

In addition to installing the latest SUP743, the script also patches Zenoss for an issue introduced in SUP732 to do with setting and pushing the production state of a device. A further issue to do with Notifications, introduced in SUP743 is also patched. Huge thanks to Jay Stanley for diagnosing and patching both of these. See the README for further info.

I have not touched the Ubuntu build in this recent work on the Github package.

Please do provide feedback if you use this autodeploy package. I will update it to get rid of the CODEPATH hack if Zenoss provide the necessary code on SourceForge.

Although we do now have the Zenoss Core rpm for RedHat 5 and 6, both 32-bit and 64-bit, the download directory at SourceForge has changed so the auto-install script breaks. This I can fix.

However SourceForge does NOT yet have the zenup rpm (ie not the latest SUP but the zenup program itself); neither do we have the pristine install that is required before you can install a SUP update. Please can we have these; otherwise no-one can apply any SUP updates to base Core 4.2.5.

So, it seems Zenoss Inc. has chosen the way to have Zenoss Core (mostly open sourced) community just for a PR.

------------------------------Serge

Original Message:Sent: 11-27-2018 10:50 AMFrom: John BoyleSubject: Zenoss 4 appears to have been axed

@Jane - SourceForge site is in the process of being updated. Older versions (2, 3, etc.) were removed. Working on the uploads today and will post back when the latest ones are up. Meantime the latest version 4 and version 6 of the Community Edition are on this community homepage. Version 6.3 on the horizon.

12. RE: Zenoss 4 appears to have been axed

Hello! I've sorted out the issues with the 4.2.5 (and associated ZenUp patching utility) content, it is all currently available. Jane knows per earlier Skype discussion, but I wanted to post here for general awareness. There's one last detail to work out regarding a small file naming detail and the deployment scripts but that will be simple and will not affect the availability of the files needed to install 4.2.5 Core and patch it to the latest RPS.

I am still hoping that Zenoss will supply the zenup and pristine on sourceforge; meanwhile the autodeploy script has a line:

CODEPATH="/home/jane/Zenoss_4.2.5_core-autodeploy"

I have provided the zenup rpm and the pristine file in the pre_req_downloads directory of the git package so, whilst we wait, copy those files from the package to somewhere on your build device and set CODEPATH in the autodeploy script to reflect that.

In addition to installing the latest SUP743, the script also patches Zenoss for an issue introduced in SUP732 to do with setting and pushing the production state of a device. A further issue to do with Notifications, introduced in SUP743 is also patched. Huge thanks to Jay Stanley for diagnosing and patching both of these. See the README for further info.

I have not touched the Ubuntu build in this recent work on the Github package.

Please do provide feedback if you use this autodeploy package. I will update it to get rid of the CODEPATH hack if Zenoss provide the necessary code on SourceForge.

Although we do now have the Zenoss Core rpm for RedHat 5 and 6, both 32-bit and 64-bit, the download directory at SourceForge has changed so the auto-install script breaks. This I can fix.

However SourceForge does NOT yet have the zenup rpm (ie not the latest SUP but the zenup program itself); neither do we have the pristine install that is required before you can install a SUP update. Please can we have these; otherwise no-one can apply any SUP updates to base Core 4.2.5.

So, it seems Zenoss Inc. has chosen the way to have Zenoss Core (mostly open sourced) community just for a PR.

------------------------------Serge

Original Message:Sent: 11-27-2018 10:50 AMFrom: John BoyleSubject: Zenoss 4 appears to have been axed

@Jane - SourceForge site is in the process of being updated. Older versions (2, 3, etc.) were removed. Working on the uploads today and will post back when the latest ones are up. Meantime the latest version 4 and version 6 of the Community Edition are on this community homepage. Version 6.3 on the horizon.

13. RE: Zenoss 4 appears to have been axed

The good news....Zack has done a great job uploading all the right files to SourceForge, with all the consistent names. We have discussed the naming convention and agreed on what is now on SourceForge.

The bad news....The autobuild script won't work as-of today because of the name changes. I need to change it anyway to pick up all the files from SourceForge but, I'm sorry Gals and Guys, it will probably be at least mid next week before I can do this. If anyone needs the script in the next week, please contact me directly and I'll try and guide you through.

Hello! I've sorted out the issues with the 4.2.5 (and associated ZenUp patching utility) content, it is all currently available. Jane knows per earlier Skype discussion, but I wanted to post here for general awareness. There's one last detail to work out regarding a small file naming detail and the deployment scripts but that will be simple and will not affect the availability of the files needed to install 4.2.5 Core and patch it to the latest RPS.Original Message:Sent: 12-31-2018 10:31 AMFrom: Jane CurrySubject: Zenoss 4 appears to have been axed

I am still hoping that Zenoss will supply the zenup and pristine on sourceforge; meanwhile the autodeploy script has a line:

CODEPATH="/home/jane/Zenoss_4.2.5_core-autodeploy"

I have provided the zenup rpm and the pristine file in the pre_req_downloads directory of the git package so, whilst we wait, copy those files from the package to somewhere on your build device and set CODEPATH in the autodeploy script to reflect that.

In addition to installing the latest SUP743, the script also patches Zenoss for an issue introduced in SUP732 to do with setting and pushing the production state of a device. A further issue to do with Notifications, introduced in SUP743 is also patched. Huge thanks to Jay Stanley for diagnosing and patching both of these. See the README for further info.

I have not touched the Ubuntu build in this recent work on the Github package.

Please do provide feedback if you use this autodeploy package. I will update it to get rid of the CODEPATH hack if Zenoss provide the necessary code on SourceForge.

Although we do now have the Zenoss Core rpm for RedHat 5 and 6, both 32-bit and 64-bit, the download directory at SourceForge has changed so the auto-install script breaks. This I can fix.

However SourceForge does NOT yet have the zenup rpm (ie not the latest SUP but the zenup program itself); neither do we have the pristine install that is required before you can install a SUP update. Please can we have these; otherwise no-one can apply any SUP updates to base Core 4.2.5.

So, it seems Zenoss Inc. has chosen the way to have Zenoss Core (mostly open sourced) community just for a PR.

------------------------------Serge

Original Message:Sent: 11-27-2018 10:50 AMFrom: John BoyleSubject: Zenoss 4 appears to have been axed

@Jane - SourceForge site is in the process of being updated. Older versions (2, 3, etc.) were removed. Working on the uploads today and will post back when the latest ones are up. Meantime the latest version 4 and version 6 of the Community Edition are on this community homepage. Version 6.3 on the horizon.

14. RE: Zenoss 4 appears to have been axed

Mike had a go with this script on Jan 3rd (before the filename changes) and it largely worked except for the final 2 spot patches. He reports the following:

Jane,

I attempted to use your latest autodeploy script for 4.2.5 on a CentOS6.10 fresh install. It seems to stop at this point. It hangs at the already running list, i eventually had to ctrl + c out.Zenoss will start, but noticed issues with LinuxMonitor / SSH, so tried upgrading and got Python errors below:

I think this has probably installed everything except the two spot patches. I also think the problem with the LinuxMonitor ZenPack is probably unrelated to the build. Mike later reported on IRC:"i think i got it working, blew the DB alway. tried again"

Mike - perhaps you could explain this one a bit more? Which DB did you blow?

If possible, Mike, I suggest we put any more experimentation with the autobuild script on hold for a week until I update it for Zack's work on the SourceForge site. I will also then re-address the failure of those two patches. For reference re those two patches, I have:

for the files in /opt/zenoss/Products/ZenModel - I think the nomenclature is self-evident? Mike, be interesting to know what size your Device.py and actions.py are?? (note these are my copies of the files - under /opt/zenoss, the files should be owned by zenoss:zenoss.

The good news....Zack has done a great job uploading all the right files to SourceForge, with all the consistent names. We have discussed the naming convention and agreed on what is now on SourceForge.

The bad news....The autobuild script won't work as-of today because of the name changes. I need to change it anyway to pick up all the files from SourceForge but, I'm sorry Gals and Guys, it will probably be at least mid next week before I can do this. If anyone needs the script in the next week, please contact me directly and I'll try and guide you through.

Hello! I've sorted out the issues with the 4.2.5 (and associated ZenUp patching utility) content, it is all currently available. Jane knows per earlier Skype discussion, but I wanted to post here for general awareness. There's one last detail to work out regarding a small file naming detail and the deployment scripts but that will be simple and will not affect the availability of the files needed to install 4.2.5 Core and patch it to the latest RPS.Original Message:Sent: 12-31-2018 10:31 AMFrom: Jane CurrySubject: Zenoss 4 appears to have been axed

I am still hoping that Zenoss will supply the zenup and pristine on sourceforge; meanwhile the autodeploy script has a line:

CODEPATH="/home/jane/Zenoss_4.2.5_core-autodeploy"

I have provided the zenup rpm and the pristine file in the pre_req_downloads directory of the git package so, whilst we wait, copy those files from the package to somewhere on your build device and set CODEPATH in the autodeploy script to reflect that.

In addition to installing the latest SUP743, the script also patches Zenoss for an issue introduced in SUP732 to do with setting and pushing the production state of a device. A further issue to do with Notifications, introduced in SUP743 is also patched. Huge thanks to Jay Stanley for diagnosing and patching both of these. See the README for further info.

I have not touched the Ubuntu build in this recent work on the Github package.

Please do provide feedback if you use this autodeploy package. I will update it to get rid of the CODEPATH hack if Zenoss provide the necessary code on SourceForge.

Although we do now have the Zenoss Core rpm for RedHat 5 and 6, both 32-bit and 64-bit, the download directory at SourceForge has changed so the auto-install script breaks. This I can fix.

However SourceForge does NOT yet have the zenup rpm (ie not the latest SUP but the zenup program itself); neither do we have the pristine install that is required before you can install a SUP update. Please can we have these; otherwise no-one can apply any SUP updates to base Core 4.2.5.

So, it seems Zenoss Inc. has chosen the way to have Zenoss Core (mostly open sourced) community just for a PR.

------------------------------Serge

Original Message:Sent: 11-27-2018 10:50 AMFrom: John BoyleSubject: Zenoss 4 appears to have been axed

@Jane - SourceForge site is in the process of being updated. Older versions (2, 3, etc.) were removed. Working on the uploads today and will post back when the latest ones are up. Meantime the latest version 4 and version 6 of the Community Edition are on this community homepage. Version 6.3 on the horizon.

15. RE: Zenoss 4 appears to have been axed

I have updated the autodeploy script again today (Jan 10th, 2019) with the correct filenames on SourceForge and retested. I have also done some cleaning up, especially around the two little patches at the end of the script.

The good news....Zack has done a great job uploading all the right files to SourceForge, with all the consistent names. We have discussed the naming convention and agreed on what is now on SourceForge.

The bad news....The autobuild script won't work as-of today because of the name changes. I need to change it anyway to pick up all the files from SourceForge but, I'm sorry Gals and Guys, it will probably be at least mid next week before I can do this. If anyone needs the script in the next week, please contact me directly and I'll try and guide you through.

Hello! I've sorted out the issues with the 4.2.5 (and associated ZenUp patching utility) content, it is all currently available. Jane knows per earlier Skype discussion, but I wanted to post here for general awareness. There's one last detail to work out regarding a small file naming detail and the deployment scripts but that will be simple and will not affect the availability of the files needed to install 4.2.5 Core and patch it to the latest RPS.Original Message:Sent: 12-31-2018 10:31 AMFrom: Jane CurrySubject: Zenoss 4 appears to have been axed

I am still hoping that Zenoss will supply the zenup and pristine on sourceforge; meanwhile the autodeploy script has a line:

CODEPATH="/home/jane/Zenoss_4.2.5_core-autodeploy"

I have provided the zenup rpm and the pristine file in the pre_req_downloads directory of the git package so, whilst we wait, copy those files from the package to somewhere on your build device and set CODEPATH in the autodeploy script to reflect that.

In addition to installing the latest SUP743, the script also patches Zenoss for an issue introduced in SUP732 to do with setting and pushing the production state of a device. A further issue to do with Notifications, introduced in SUP743 is also patched. Huge thanks to Jay Stanley for diagnosing and patching both of these. See the README for further info.

I have not touched the Ubuntu build in this recent work on the Github package.

Please do provide feedback if you use this autodeploy package. I will update it to get rid of the CODEPATH hack if Zenoss provide the necessary code on SourceForge.

Although we do now have the Zenoss Core rpm for RedHat 5 and 6, both 32-bit and 64-bit, the download directory at SourceForge has changed so the auto-install script breaks. This I can fix.

However SourceForge does NOT yet have the zenup rpm (ie not the latest SUP but the zenup program itself); neither do we have the pristine install that is required before you can install a SUP update. Please can we have these; otherwise no-one can apply any SUP updates to base Core 4.2.5.

So, it seems Zenoss Inc. has chosen the way to have Zenoss Core (mostly open sourced) community just for a PR.

------------------------------Serge

Original Message:Sent: 11-27-2018 10:50 AMFrom: John BoyleSubject: Zenoss 4 appears to have been axed

@Jane - SourceForge site is in the process of being updated. Older versions (2, 3, etc.) were removed. Working on the uploads today and will post back when the latest ones are up. Meantime the latest version 4 and version 6 of the Community Edition are on this community homepage. Version 6.3 on the horizon.