Return to todo.txt CVS log

Up to [Pegasus] / pegasus / vxworks / doc

PEP#: 305
TITLE: VxWorks Port

DESCRIPTION: Ongoing VxWorks porting.

    ============================================================================

    (A) CIMPLE port.

    (A) Disable saving instances of PG_ProviderModule, PG_Provider, and 
        PG_ProviderCapabilities.

    ============================================================================

    (B) Implement emulated dynamic loading in CMPI provider manager.

    (B) Build Linux embedded server pilot implementation.

    (B) Limit memory used by enumerateClasses operation.

    (B) Use exceptions rather than boolean return types to report errors in
        EmbeddedServer interface.

    (X) Provider load/terminate operations.

    (X) Mention "refusal to unload" feature to users.

    (B) SSL porting.
    
    (B) Authentication.

    (B) Memory management.

        (*) Add memory measurement utility.
	
	(*) Memory limits.

        (*) Throttling.

    (B) VxWorks 5.5 port.

    (B) Eliminate configuration files dependencies.

    (X) Control-provider indications (not required).

    (B) Generalize VxWorks-specific code options.

    (B) Message-catalogue localization.

    (X) Logging. - Proposed solution is to move to virtual definition of the 
        log serializer and allow the function to be defined in the embedded 
        system main. This will allow embedded system developer to define
        any output mechanism for logs.

    (B) Shutdown - How do we shutdownt the server? Initial conclusion is that 
        we do it through a signal. We could develop a function in the CIMServer
        main that the embedded system provider that defines the signal to be 
        used as the starting point for shutdown.

    (B) Get rid of PID file.  - I believe that this is already done. ks

    (B) Remove daeminization code.

    (B) Add -c option to cimmofl.

        $ cimmofl -c classnames.txt

    ============================================================================

    (C) Tracing (turned off for now). It appears that this will be the 
        permanent solution.  The alternative is to do the same thing we are 
        going to do with logs, create a callback mechanism whereby the embedded
        system developer can decide what he wants to do with the line output.

    (C) CIM_ComputerSystem provider.

    (C) Class reduction as cimmofl option.

    (C) Remove unused modules.

        (*) Client - Not required

        (*) UserManager 

        (*) Indication Export Server. Not used in any configuriation except HP.

        (*) ProviderRegistrationControlProvider. Not required because no 
            providers registered

        (*) ConfigSettingControlProvider. Not required if we do not have 
            dynamic settings

        (*) UserAuthControlProvider. Can eliminate if there are external 
            means to set user names and providers

        (*) Managed system providers. Does Fujitsu need them or will they 
            write their own.