Zenoss on RHEL
|
![]() ![]() |
John, Further to our conversation at Splash, I'm keen to distribute our Zenoss RPM stack via RHEL on a commercial basis. By that, I mean that the brand recognition and sales and marketing machine of Red Hat will get Zenoss (Inc.) and my business much further than I can do so myself - and of course, you'll benefit from RHEL licence sales. I guess it's our challence to discover how to make this possible ... Firstly, the SRPM's I need to build are at http://build.last-bastion.net/RPMBuilders/10/SRPMS/BastionLinux. ; There are ~650 SRPM's here, of which around half are necessary for Zope/Zenoss, a quarter for Plone (which would promote my Plone4Zenoss initiative within the Zenoss community), and the other quarter my proprietry Project/Programme management and Small Business financial accounting portal software. I would think that there will be up to 800 RPM's generated and necessary to deploy the Zope/Zenoss/Plone stack. This is fantastic because clearly this represents enough complexity for an organisation to invest in RHEL/Zenoss (and commercial Plone). Note that presently this software is built against BastionLinux core which is simply a local recompile of Fedora Core 10 (the provenance of everything is quite obvious via the above URL) and will trivially build against an RHEL koji/hive environment. My target outcome for this is essentially what I have on BastionLinux: subscribing to http://linux.last-bastion.net/LBN/up2date/plope/10 and http://linux.last-bastion.net/LBN/up2date/monitor/10 channels get's you a hardened enterprise Zenoss installation (and at price-points set by us). BTW, these BastionLinux channels understand up2date/yum/rug/Red Carpet/zypper. The million dollar question is exactly how do we get there? |
|
![]() ![]() |
No serious interest from vendor |
|
![]() ![]() |
||
![]() ![]() |
Yeah... That subject line is no joke |
|
![]() ![]() |
Purchase all the watche5 you wanted to buy at super discounted prices |