Opened 51 years ago

Last modified 10 years ago

#879 new task

IZ529: The component state is not defined in the spec

Reported by: rhierlmeier Owned by:
Priority: normal Milestone:
Component: hedeby Version: 1.0
Severity: Keywords: Sun doc


[Imported from gridengine issuezilla]

        Issue #:      529          Platform:     Sun         Reporter: rhierlmeier (rhierlmeier)
       Component:     hedeby          OS:        All
     Subcomponent:    doc          Version:      1.0            CC:    None defined
        Status:       NEW          Priority:     P3
      Resolution:                 Issue type:    TASK
                               Target milestone: 1.0u5next
      Assigned to:    adoerr (adoerr)
      QA Contact:     adoerr
       * Summary:     The component state is not defined in the spec
   Status whiteboard:

     Issue 529 blocks:
   Votes for issue 529:                                     Vote for this issue

   Opened: Tue Jul 29 00:24:00 -0700 2008 


   We have no clear definition of the component state in the spec. The only hint
   can be found in the jdocs of class ComponentState.


   During the manual test for the 1.0 release we found out that the GE Adapter does
   not behave in the correct way on some error conditions. During the discussion
   inside of the engineering we found out that we have not a clear definition of
   the component state.

   Suggested Fix / Work Around:

   Introduce a new section in chapter 1 "Common Concept" describing what a
   component is and what the state of a component means.



   How to test:

   With test we should ensure that the component behaves correctly. Check the
   component states of executor, resource_provider, spare_pool, ge_adapter and jvm.
   With issue 234 a testsuite test for reloading the configuration of the
   components will be implemented. The defined test scenarios handles most of
   error conditions. However for the ge_adapter some test cases are missing
   (invalid password for keystore, invalid password for username).
   I added additional comments to the test.


    2PD  including the code analysis how the component state is interpreted in
         in the component implementations.
         without implementation of the tests which are part of issue 234
               ------- Additional comments from rhierlmeier Tue Jul 29 00:24:45 -0700 2008 -------
   Dependency to issue 234 added
               ------- Additional comments from adoerr Mon Aug 18 05:50:33 -0700 2008 -------
   Changed issue type to TASK and updated target milestone.
               ------- Additional comments from easymf Thu Dec 18 07:26:53 -0700 2008 -------
   the task has to be aligned with work done in IZ#595
               ------- Additional comments from torsten Fri Nov 27 00:40:09 -0700 2009 -------
   changed milestone to 1.0u5next

Change History (0)

Note: See TracTickets for help on using tickets.