pegasus/readme.pulloperations - diff

Return to readme.pulloperations CVS log

Up to [Pegasus] / pegasus

Diff for /pegasus/readme.pulloperations between version 1.1.2.16 and 1.1.2.23

version 1.1.2.16, 2013/11/21 17:59:38

version 1.1.2.23, 2014/04/21 13:42:06

Line 12

protocol to be able to count objects in response. Generates

warnings in things like messageserializer and does not work with

OOP right now. Corrected by converting to XML.

2. OpenExecQuery - Code is incorrect in that it does not include the

2. OpenExecQuery - Code is incomplete in that it does not include the

return from the exec query function to the aggregator yet.

3. Code for Pull part of OpenQueryInstancesRequest a) should be part of

the common CIMOperationRequestDispatcher execCommon code.

4. The changes to WQLCIMOperationRequestDispatcher and CQL... for handling

pull not completed so we feed the responses back to the EnmerationContext

queues

3. Lots of minor TODOs, diagnostics, etc.

3. Lots of minor TODOs, diagnostics, etc. still in the code

4. External runtime variables. Proposing that they be fixed for this release

rather than set by configuration. This should be discussed. Am making

this a separate bug. See bug 9819 for the changes to cover this.

5. Decision on EnumerationContext timeout (separate thread or just

5. Consider moving some moreof the code in dispatcher from templates to

checks during other operations). Can we, in fact really keep the

common functions which would mean adding intermediate classes in

enumeration context table and queue under control without monitoring

CIMMessage but would reduce code size. Currently the change that

with a separate thread. We must monitor for:

we should make for this is to create a new message CIMPullRequestData...

a. Client operation that stop requesting (i.e. inter operation time

between CIMRequestDataMessage and the Pull requests since they all

exceeds operationTimeout). Note that if it simply exceeds the time

have exactly the same input and output pararameters (The

the next operation does the cleanup. The issue is those clients that

CIMResponseData hides the response object differences)

simply stop and do not either close or go to completion.

6. Extension to avoid double move of objects in CIMResponseData (one

b. We should protect against providers that no not every finish delivering

or take to long between deliveries. This does not exist in Pegasus

today

6. Consider moving some of the code in dispatcher from templates to common

functions which would mean adding intermediate classes in CIMMessage but

would reduce code size.

7. Extension to avoid double move of objects in CIMResponseData (one

into enumerationContext queue and second to new cimResponseData for

response. Want to avoid second move by extending Open/Pull response

messages to include count and CIMResponse data to count objects out

of queue when converting (avoids the second move). Big issue here

of queue when converting (avoids the second move). This would mean

with binary data since need to extend format to count it.

extending the output writers to allow the count field to be supplied

8. NEXT TASKS:

so they would only create output for up to the count supplied.

a. test the enumeration timeout thread

7. Add test for the 0 operationtimeout in PullErrors.

b. finish and test the OpenQueryInstances

8. Add more static tests (currently only OpenEnumerateInstances is covered).

9. Could clean up the CIMOperationRequestDecoder.cpp rejectCIMException

further since there is some overlap. That is low priority.

10.Add exception for to many entries in EnumerationContextTable. The

test exists but is ignored right now.

7. NEXT TASKS:

b. Finish and test the OpenQueryInstances

c. Clean up TODOs

d. Find issue when we run makepoststarttests in pullop client with

d. Find issue that is causing occasional failures under load. It

forceProviderProcesses = true. This causes an operation like

is probably a threading issue between the 3 possible threads

cimcli pei CIM_ManagedElement to not complete (client timeout)

that use the EnumerationContext (request thread, provider thread,

sometimes.

timeout thread) and a place where not mutuxed.

21 April 2014

1. Reorganizzed code in CIMOperationRequestDecoder.cpp ...Iparam classes.

Cleaned up the rejectCIMException code.

2. Cleanup some issues in the EnumerationContextTimeout Thread.

3. Fixed issue in pullop where it was using zero as default for default

operation timeout where it should have been NULL, the DMTF specified

default.

4. Enabled the test to reject 0 as operation timeout on a request and but

controled by a #define in CIMOperationRequestDispatcher.cpp

5. Added test for excessive new OperationContext entries in table.

18 April 2014

1. Internationalize remaining messages in CIMOperationRequestDecoder.cpp and

clean up the decoders for some of the messages so they use the

...Iparam classes. Note that we did not clean up all of the old message

decoders, just the new ones and we did not clean up the Count message

since it is deprecated. TODO clean these up so the decoder is really

consistent.

2. Enabled the EnumerationContext Timer and removed code for alternate

non-thread solution.

17 April 2014

1. Reorganized the lock/unlock for handling the EnumerationContext because

there were thread windows (i.e. using the context after it was released

by other thread).

2. Modified code for the InteroperationTimerThread and deleted old code that

allowed this whole thread to by bypassed.

3. Internationalized a number of CIMOperationRequestDispatcher CIMException

response messages.

4. Fixed stress tests in Client/tests/pullop that were getting timeout. The

issue was not the pull code but that fact that the idle client timeout

appears to be measureing to the end of the operation and the operation

was taking more than 40 seconds which is the default timeout. The idle

timeout takes no account of the fact that chunks are being regularly

delivered.

5. Several minor code changes.

NOTE: At this point the code passes extensive tests of the pull operations

both in OOP and none OOP mode (but with lots of diagnostics that may

be affecting timing).

10 April 2014

1. Fix issues causing failure with repeated pull operations.

2. Consolidate some of the CIMOperationRequestDispatcher.cpp template code

7 April 2104

MergeOut of head of tree.

7 April 2014

1. Permanently fixed issue with getting correct number of objects on response.

This was introduced when did a temp fix to the OOP processing, in particular

removed the condition variable wait in the CIMOperationDispatcher handle

functions for opens and pulls. This moved the functionality to kick off

open and pull responses to the provider threads if there are not enough

objects when the handle is processed. Also added a variable to allow us to

test with either a) responses are required to satisfy the original

request size or) b, responses are required only to return some objects.

We will add statistics to see which of these works best.

2. Modified WsmProcessor EnumerationContext class since the name conflicts

with the pull Operation EnumerationContext class.

3. Created a new intermediate level of CIMMessage, the CIMPullResponseData

Message so that all of the open and Pull responses can use common code

since there are only two variables (endOfSequence and EnumerationContext)

and they are common across all the open and pull responses.

4. Removed a number of diagnostics.

5. Cleaned up the Dispcatcher so that the open and pulls have common response

code and that code can be used from the dispatcher handle functions and

the provider response functions.

31 March 2014 - Checkin

1. Fixed issues in OOP processing of pull operations, in particular

issues with cimxml output format when processed through the

*InternalXmlEncoder functions.

2. Clean up some of the internalXml functionality

3. Found issues causing timeout with a particular provider. The issue

is that the dispatcher and monitor end up using the same thread so the

condition variable in the dispatcher thread stops the monitor. Turned

off the conditionVariable in getCache for the moment which means that

we get number of responses for open... with 0 objects before the

providers can begin to respond. This is only for test.

4. Added some statistics for enumerations and display the statistics

when we close the server (same as cache statistics)

12 March 2014 - Mergeout and Mergein

1. Mergeout to head of tree for this date and mergein for patch update

to bug 9676

2. Extensions to pullop tests program and tests.

3. Added some diagnostics in looking for OOP issue.

4. Removed a number of diagnostics messages and cleaned up code in

dispatcher to simplify pull operation processing.

15 December 2013

1. Mergeout and mergein up to 15 December 2013

2. Clean up issues from tests documented in bug 9676 last week.

3. Clean up some code in dispatcher

4. Remove the filter function from ResponseStressc++Provider.

21 November 2013

1. Mergeout from head of tree to 21 November 2013.

Legend:

Removed from v.1.1.2.16
changed lines
	Added in v.1.1.2.23

No CVS admin address has been configured