Re: [aperi-dev] Full support for Solaris?

[Khan M Tasinga <kmtasing@xxxxxxxxxx>]

Hey Dale,

It's nice to hear from another person
interested in Aperi! Here are some initial notes / thoughts related to
what it'd take to get everything up and running on Solaris:

* Platform-specific native code... As
you've already noticed, Aperi has plenty. Browsing the Aperi/bin/linux-ix86
folder in CVS will give you a good sense of the native binaries / libraries
Aperi depends upon to function. Unfortunately, producing native binaries
/ libraries for Solaris isn't as simple as putting together appropriate
Makefiles and building the code in CVS. Why? Some of the Solaris platform-specific
code isn't available. A few examples immediately come to mind:

        -
If you look in the Aperi/data/c/T-Storm folder, you'll see ProbeLinux.c
and ProbeWin32.c files. There needs to be a ProbeSolaris.c, containing
the code required to obtain disk and filesystem information from a Solaris
server.

        -
If you look in the Aperi/device folder, you'll see a Linux folder with
AttributeScanner, EventScanner and TopologyScanner subfolders, all containing
code specific to the Linux Aperi Fabric Agent. A Solaris folder, containing
code for the fabric attribute, event and topology scanners is required.

        -
CCLOG, a C-based logging / tracing toolkit used by Aperi's native code.
Currently, the Solaris version is not available in CVS.

When we (IBM) made our initial contribution
to Eclipse, we only made sure to include all of the platform-specific code
required to make everything work on Windows and Linux (for both, the 32-bit
x86 flavors). Platform-specific code for Solaris does exist. It would just
need to be made available.

* Platform-specific Java code... Just
as with the native code, there are instances where Solaris-specific Java
code was not included with the initial IBM contribution. Example? The ProbeWin32
class (in the org.eclipse.aperi.agent.probe package) is tied to the code
in ProbeWin32.c. Just as ProbeSolaris.c doesn't exist, there is no ProbeSolaris
class.

* Server side functionality... The initial
IBM contribution was based on code from the IBM TotalStorage Productivity
Center (TPC). On the server side, TPC supports AIX, Linux and Windows.
Solaris is not officially supported. Off-top, I can't see any real reason
why the Aperi servers (Data / Filesystem, Device and Report) wouldn't work
on Solaris. But as it stands, it's relatively uncharted territory.

* SPARC vs. x86... Any Solaris-specific
code obtained from IBM would assume the SPARC architecture. I'm not enough
of a Solaris expert to know whether or not that would present any significant
problems.

I hope that helps. Anyone else have
some relevent input?

Regards,
Khan Tasinga
IBM Tivoli Software Engineer (Storage Management Development)

Dale Ghent <daleg@xxxxxxxxxxxxx>
Sent by: aperi-dev-bounces@xxxxxxxxxxx

08/28/2007 02:47 PM

Please respond to
Aperi Development <aperi-dev@xxxxxxxxxxx>

To	aperi-dev@xxxxxxxxxxx
cc
Subject	[aperi-dev] Full support for Solaris?

Hey all, I'm pretty new to Aperi but as a SAN admin I'm very  
interested in it and have been watching it for the past several months.

I run a mostly Sun (Solaris 10) shop, and so my options for  
installing the agent, reporting server, and so on are limited to that  
platform.

 From what I can tell, the only platform-specific code in Aperi are  
the shared libs, which seem to be readily compilable/available for  
Linux and Win32. Are there any hidden gotchas to keep in mind when  
porting to a new platform? Solaris 10 offers HBAAPI (in fact, I've  
written some of my on utilities using it), and after rummaging  
through the C source that was the only major dependency I could find.

Anything else I should watch out for?

/dale
_______________________________________________
aperi-dev mailing list
aperi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aperi-dev