1 karl 1.1.2.1 Using the CIM/XML Pull Operations
2
3 STATUS
4
|
5 karl 1.1.2.4 <<< The TODO section is being maintained during the review and checkin process
|
6 karl 1.1.2.1 to keep track of problems, errors, notes, etc. Must be deleted before
7 checkin to head of tree. Please feel free to add notes, etc in this
8 section as you review/test.>>>>>>
9
|
10 karl 1.1.2.4 TODO list:
|
11 karl 1.1.2.3 1. Binary operation from OOP. Need to add counter to binary
12 protocol to be able to count objects in response. Generates
13 warnings in things like messageserializer and does not work with
|
14 karl 1.1.2.31 OOP right now. Fixed by converting to XML. Concluded that we do not
15 need to do this. The binary response is not really used often
16 in the current environment So double mapping it is not a major issue.
17 Leave this as FUTURE
|
18 karl 1.1.2.35 2. DONE OpenExecQuery - Code is incomplete in that it does not include the
|
19 karl 1.1.2.31 return from the exec query function to the aggregator yet. Code for Pull
|
20 karl 1.1.2.34 part of OpenQueryInstancesRequest a) should be part of the common
21 CIMOperationRequestDispatcher execCommon code. DONE, not tested. 29 May
|
22 karl 1.1.2.35 30 May tested with simple cli calls.
23 3. DONE The changes to WQLCIMOperationRequestDispatcher and CQL... for handling
|
24 karl 1.1.2.4 pull not completed so we feed the responses back to the EnmerationContext
|
25 karl 1.1.2.35 queues. DONE Not tested 29 May 30 May DONE, some testing done
26 4. Minor TODOs, diagnostics, etc. still in the code. Reduced almost to
27 none now. We are leaving some in as PEGASUS_DEBUG
|
28 karl 1.1.2.31 5. Extension to avoid double move of objects in CIMResponseData (one
|
29 karl 1.1.2.3 into enumerationContext queue and second to new cimResponseData for
30 response. Want to avoid second move by extending Open/Pull response
31 messages to include count and CIMResponse data to count objects out
|
32 karl 1.1.2.23 of queue when converting (avoids the second move). This would mean
33 extending the output writers to allow the count field to be supplied
|
34 karl 1.1.2.30 so they would only create output for up to the count supplied.(Make
|
35 karl 1.1.2.35 this future beyond bug 9676). This is fairly extensive because it
36 extends beyond CIMResponseData to SCMO and XML writers where the
37 XmlWriters used by encodeXmlResponse would have to have counters
38 added. Then instead of copying on getCache we would simply pass the
39 cache and count on and the writer would take and remove.
|
40 karl 1.1.2.31 6. Add more static tests (currently only OpenEnumerateInstances and
|
41 karl 1.1.2.30 OpenEnumerateInstanceNames covered).
|
42 karl 1.1.2.26 Low priority because most of this except exact XML covered in other
|
43 karl 1.1.2.28 tests. note that we can only add very limited tests since a) no
|
44 karl 1.1.2.31 way to test multiple operations in sequence(i.e. open/pull) and
|
45 karl 1.1.2.28 cannot be sure how many responses will come back in all cases even
|
46 karl 1.1.2.35 for open. The only reason for most of these tests is to assure that
47 we do not change XML inadvertendtly in future with change that is
48 compatible to both our server and client but breaks other clients or
49 servers. In any case we can do only minimal tests because most real
50 testing involves both open and pull and the static tests are by their
51 nature single operation.
|
52 karl 1.1.2.32 8. Correct issue between operations and HTTP where we are sending
|
53 karl 1.1.2.31 trailers with exceptions. Modify response mechanisms so that we
54 set non-chunked for all responses where we send error responses to
|
55 karl 1.1.2.35 avoid the trailers. NOTE: There should be now a bug on this in general
56 where we would want to send an initial error without the trailer. Should
57 have always done that.
|
58 karl 1.1.2.32 9. It would be more efficient in dispatcher to always use exception for
|
59 karl 1.1.2.31 rejects and change the _reject functions so that they never return
60 when they reject. This is VERY LOW PRIORITY and primarily saves
61 a few lines of code in the reject functions and their calls. Means we
62 would code.
|
63 karl 1.1.2.35 _rejectIfEnumerationToBroad(...);
64 _rejectIfThisParameterIncorrect(...);
|
65 karl 1.1.2.31
66 instead of
67 if (_rejectIfEnum...)
68 {
69 return true
70 }
71 It would mean that the method trace for the handlers would not return
|
72 karl 1.1.2.35 an exit if we rejected. VERY LOW PRIORITY. Possibly FUTURE. No behavior
73 change, just more compact source code but it messes with the method
74 trace logic.
|
75 karl 1.1.2.34 10. There are still a couple of template functions around the task of
|
76 karl 1.1.2.32 distributing requests to the multiple providers.
77 In fact there are two similiar but different templates for
|
78 karl 1.1.2.31 the associators(i.e. assoc, ref, etc.) functions and the parallel
79 openAssoc functions. It would be nice to consolidate that logic and
80 further to try to create a non-template form for those functions. LOW
|
81 karl 1.1.2.44 PRIORITY and not for bug 9676 ACTION: Define in new bug
82 11. External runtime variables. bug 9676 leaves these variables as
|
83 karl 1.1.2.37 internal to CIMOperationRequestDispatcher.cpp.
84 See bug 9819 for the changes to externalize these variables, both
85 the runtime and buildtime variables. The Work group discussion
86 documents what the variables are and how they tie to statistics info.
87 See the OpenPegasus Wiki, Pull operations work group.
|
88 karl 1.1.2.35 12. Trace functions in CIMResponseData,h & cpp should be PEGASUS_DEBUG.
|
89 karl 1.1.2.37 Same for trace function in EnumerationContext and
90 EnumerationContextTable
91 13.Question. We added trace in CIMRequestOperationDispatcher.cpp if
92 query enum is recevied with no object path. However, since this is
93 a provider problem should we be doing something other than a trace
94 (ex. log) since traces are often not really used and they do generate
95 lots of data whereby something like this could get lost. Also, need
96 to review what level of trace if we keep trace.
|
97 karl 1.1.2.36 14. Note that the build-a-class argument on OpenQueryInstances always
|
98 karl 1.1.2.44 returns error since we do not build the class. We propose to deprecate
99 this in DMTF and not implement in in OpenPegasus. TODO add a bug
100 defining this limitation. This is not a TODO, just a warning for
|
101 karl 1.1.2.37 the future. TODO add bug about this and add to release notes
|
102 karl 1.1.2.38 15. Clarify trace of completion of each enumeration sequence.
103 16. Statistics keeping for open, etc. through cimperf.
104
|
105 karl 1.1.2.26
106 NEXT TASKS:
|
107 karl 1.1.2.37 a. finish 8, 12 above. Test against cimperf since there was a bug
108 in cimperf from before.
|
109 karl 1.1.2.39
|
110 karl 1.1.2.46 14 August 2014
111 1. Issue with the pullop test in some systems causing an HTTP 413 error (
112 too much data). We confirmed that this is probably actually a limit in the
113 client with enumerate instances (the response is simply to big in the case
114 where we are asking it to deliver 100,000 responses instances on some systems)
115 Modified the test for the stress test to be 30,000 instances and added a
116 manual test testSizeLimit to the make file to try to deliver up to 600,000
117 instances to determine limits to the environment.
118
119 Note that this is not actually a failure of the pull operations. In fact
120 where cimcli ei ... fails with 600,000 instances in the response cimcli pei
121 works correctly.
122
123 Update the Client/tests/pullop/Makefile stresstests to hopefully pass the
124 nightly test on more systems.
125
126 2. Eliminated a number of KS_TODOs and code that we had documented out with
127 //// . Note that there are still a number of the KS_TODOs but most of them
128 are really isolated around
129
|
130 karl 1.1.2.47 19 August 2014
|
131 karl 1.1.2.48 1. Mergeout to head of tree. We picked up one issue that for some reason
132 the cvs mergeout was missing, a change to Server/tests/TLS...
133
134 19 August 2014
|
135 karl 1.1.2.47 1. Remove a number of KS_TODO notes either by cleaning them up or by
136 change the keyword to FUTURE if they are things that we might consider
137 for the future
138 2. Some efficiency improvements in dealing with strings primarily get
139 rid of use of String::EMPTY in the new code.
140
141 3. Removed some diagnostic trace output that was used during development.
|
142 karl 1.1.2.46
|
143 karl 1.1.2.45 13 August 2014
144 1. Mergeout to head of tree.
145
|
146 karl 1.1.2.44 11. August 2014
147 1. Correct error in compile in windows (bad reference to sleep(...)
148
|
149 karl 1.1.2.43 29 July 2014
150 1. Cleanup functionality in the unittests for EnumerationContext and
151 its table.
152
|
153 karl 1.1.2.42 23 July 2014
154 1. Mergeout from head of tree to Task branch
155
|
156 karl 1.1.2.41 21 July 2014
157 1. Removed strings.h from pullop.cpp
158 2. Minor cleanup per testing
159
|
160 karl 1.1.2.40 17 July 2014
161 1. Correct error in CIMOperationRequestDispatcher.cpp OpenQueryInstances
162 when PEGASUS_DISABLE_QUERY set.
163 2. Correct issue in diagnostic code in CIMResponseData.cpp that used
164 snprintf function not available in windows.
|
165 karl 1.1.2.41 3. Clean up some miscellaneous code in pullop and Makefile.
|
166 karl 1.1.2.40 4. Minor change to PullErrosrs.
167
|
168 karl 1.1.2.39 2 July 2014
169 1. Corrected error in the new getoopt functions that caused it to fail
170 in build and also in it unit test with the --help option.
171
172 28 June 2014
173 1. Corrected issue where ZOs was getting errors from pullop because we
174 used getopt to parse command line and the linux getopt is not behavior
175 consistent with ZOs. Note that the ZOs getopt matches the posix expect and
176 the linux one has extensions (notably it permutes non option arguments to
177 the end of the arguments array. The easiest and most logical was to move
178 the whole parser to use the internal getoopt which is what we should be
179 using all the time in any case.
|
180 karl 1.1.2.38 18 June 2014
181 1. Correct errors in pullop and CMIMessage.cpp identified by Ji Lee as comments 58,59
182 2. Correct error in Makefile identified by Ji Lee as bug comment 60
|
183 karl 1.1.2.37
184 14 June 2014
185 1. Mergeout from head of tree.
186
|
187 karl 1.1.2.36 12 June 2014
188 1. Implement the basic code for the CIMOperationDispatcher portion of bug 9819
189 Note that the CIMConfig calls are disabled with comments.
190 2. Corrected a number of differences in const declaration and definition for
|
191 karl 1.1.2.37 continueOnError and maxObjectCount in CIMClient. This corrects issue
192 documented in bug 9676 comment 53
|
193 karl 1.1.2.36 3. Corrected some documentation for Pull operations in CIMClient.
194 4. Corrected similar issue In EnumerationContext class. See comment 54
195 5. Removed ExecInfo.h header from Client/tests/PullErrors/PullErrors.cpp
|
196 karl 1.1.2.35
197 30 May 2014
198 1. Correct issue in UintArgs. Modified to use smart pointers, consistent
199 with public interfaces. Tested
200 2. Complete code for OpenQueryInstances and PullInstances so that the complete
201 sequence works for both the server and client (i.e. 2, 3 above done
202 except for more tests in pullop).
203 3. Fix issue in cimcli where the OpenQueryInstances was outputting a path
204 component where there is no path transmitted from the server.
205 4. Moved large block of common code in CQLOperationRequestDispatcher.cpp
206 and WQLOperationRequestDispatcher.cpp to common function
207 handleQueryRequestCommon in CIMOperationRequestDispatcher.cpp. These
208 handlers now reduced to just the parser processing and minimal error
209 checks.
210 5. Cleaned up some code in EnumerationContextTable.CreateContext so only
211 single interface for all requests.
212 6, Commented out a number of PEG_TRACE messages. Note that they are
213 commented with 4 /s at line beginning to be easily identified.
214 //// code
215 There are still a number of KS_TODOs but they are mostly some questsions,
216 some internationalization (note that almost none of this environment is
217 karl 1.1.2.35 completely internationlaized (see the decoders)) and a couple of questions
218 about the existing code or exactly what message should be sent. I argue
219 that the current TODOs should not stop checkin. Will remove after we
220 have tested couple of days and prove that there is no real need.
221 7. Added trace in Query response code if there is no objectPath since that
222 is really an error in the provider
223
|
224 karl 1.1.2.34
225 29 May 2014
226 1. Correct issue in cimcli that was causing rejects of open operations when
227 there were no filters requested. The standard default is WQL in cimcli
228 so we overrode this for the pull operations.
229 2. Clean up OpenQueryInstances in CIMMessage.h and CIMMessage.cpp.
230 3. Modify CIMOperationRequestDispatcher and
231 EnumerationContextTable.CreateContext to pass request rather than request
232 parameters.
233 4. Remove a number of diagnostic messages. Note that there are still some.
234 They are marked KS_TODO with with note to remove before checkin. They are
235 all traces and validations.
236 5. Correct error in inclusion of execinfo.h include in CIMOperationRequestDis.
237 found by Ji Lee.
238 6. Cleaned up execQuery and extended it for OpenQueryInstances. ExecQuery
239 tested but have not tested OpenQueryInstances yet. One more checkin and we
240 should be able to close 2,3 above (OpenQueryInstances).
|
241 karl 1.1.2.32
242 26 May 2014
243 1. Remove a number of diagnostics.
244 2. Make cache size in EnumerationContextTable dynamic and remove function
245 to set default values. MaximumEnums set from Dispatcher on constructor for
246 EnumerationContextTable and table size set to 1/2 of maximum number of
247 open contexts.
248 3. Clean up some statistics in EnumerationContextTable
|
249 karl 1.1.2.33 4. Correct error in query and queryLanguage parameters in cimcli in that
250 the default for queryLanguage is WQL but must be "" for pull operations.
251 If WQL found they set it to "".
|
252 karl 1.1.2.32
|
253 karl 1.1.2.31
254 9 May 2104
255 1. Converted several template functions in CIMOperationRequestDispatcher
256 to real functions
257 2. Added intermediate CIMMessage for CIMPullOperationRequestMessage since
258 all of the pulls have exactly the same data. This allowed us to
259 convert the template function processPullRequest from template to
260 real function
261 3. Added intermediate CIMMessage for CIMOpenOperationRequestMessage betweeh\n
262 all of the Opens and the CIMRequestData message. This will allow
263 common code to test all of these variables in all 6
264 CIMOperationRequestDispatcher handleOpen... functions
265 3. Added variable in CIMOperationRequestDispatcher handleEnqueue to make
266 releasing the original request conditional on return from the handle...
267 for open... and pull... handlers.
268 This allowed us to drop one place where we were creating a new request msg
269 for the delayed response and use the original request. This meant that
270 we could convert the issueOpenOrPullResponse from template function to
271 real function.
272 4. Moved open and pull constructors in CIMMessage.h to CIMMessage.cpp. NOTE:
273 openQueryInstances not moved. Will do when we get this funciton running.
274 karl 1.1.2.31 5. Added test for correct namespace in pull operations. Note that it is
275 never really used but since supplied with request, we test to be sure it is
276 same as open request namespace. added internationalized exception for this.
277 6. We should probably add same test to close just as an input parameter
278 validation.
279 6. Modified processPullRequest to close the enumeration context if
280 incorrect response type received. Before we just returned exception and
281 left context open for next request. Closing is much more logical since the
282 client really did send an erronous request.
283 7. Modified PullErrors to correctly test above changed in behavior.
284 8. Removed a significant number of diagnostic messages.
|
285 karl 1.1.2.33 9. Added query and querylanguage parameters to cimcli.
|
286 karl 1.1.2.31
|
287 karl 1.1.2.23
|
288 karl 1.1.2.30 4 May 2014
289 1. Clean interface with EnumerationContext timeout thread
290 2. Remove more diagnostics
291 3. Correct issue with enumerationContext Release that was causing
292 failures during nightly tests.
293
|
294 karl 1.1.2.29 2 May 2014
295 1. Remove Diagnostics from ResponseData.cpp
296 2. Correct setup and start of EnumerationContextTimerThread
297 3. Change limit on max number of enum contexts to be set from Dispatcher.
298 4. Increase size of hashtable for enum contexts.
299 5. Corrected issue causing failures in removeContext. Now runs through nightly
300 tests most of the time.
|
301 karl 1.1.2.28 1 May 2014
302 1. Cleanup of code and variable names.
303 2. Removed namespace variable from EnumerationContext. It was never used.
304 3. Added test for max number of open enumerations. Right now it is fixed
305 and set about 100. Note that this is tied to the size of hash table
306 so that there is a issue with more dynamic setting of max and the
307 hash table size.
308 4. Removed several unused functions.
309 5. Found one possible issue causing thread conflict but not the core one
310 yet.
311
312 30 April
313 1. Added exception response to dispatcher for Limits exceeded on
314 CreateEnumerationContext. Returns Exceeded server limits CIMException.
315 2. Fixed possible deadlock where we were not unlocking EnumerationContext
316 under error condition
317
318
|
319 karl 1.1.2.27 27 April - mergeout to head of tree
320 1. Mergeout of the code to the head of tree. Documented that mergeout in
321 the bug
322
323 27 April 2014
324 1. Clean up in a number of areas, mostly just code without changing
325 functionality.
326 2. Modified CIMMessage.h slightly to clarify names of the pull intermediate
327 messages (the common open and pull response);
328 3. Removed a number of diagnostics from CIMResponseData
329 4. Added new function to ResponseStressTestProvider to be able to terminate
330 output after a defined number of objects with a CIMException.
331 5. Removed a number of other TODOs
332 6. Corrected a couple of errors in the server message bundle.
333 7. Modified ResponseEncoder to only output the error for pull errors.
334 It was errounously outputting the EndOfSequence, EnumerationContext and
335 the error. This way, only the error is sent which is spec.
336 8. Removed number of TODOs and cleaned up a couple of others.
337 9. Added static tests for OpenEnumerateInstanceNames.
338 10. Modified a number of the temporary diagnostics to be permanent by
339 changing them to PEGASUS_DEBUG_ASSERTs
340 karl 1.1.2.27
|
341 karl 1.1.2.24 22 April 2014
342 1. Clean up some messages.
343 2. Still trying to find issue that randomly keeps messages in timeout
344 queue long after they have been closed and returned.
|
345 karl 1.1.2.25 3. Fixed memory loss error.
|
346 karl 1.1.2.26 4. Added zero reject for OperationTimeout because that effectively disables
347 the whole timeout mechanism so that enumerations could be started, never
348 completed by the client and would just hang around in memory. That
349 would be a significant DDOS attack (start very large enum with no
350 timeout) and never do pulls after open.
|
351 karl 1.1.2.25
|
352 karl 1.1.2.23 21 April 2014
|
353 karl 1.1.2.27 1. Reorganized code in CIMOperationRequestDecoder.cpp ...Iparam classes.
|
354 karl 1.1.2.23 Cleaned up the rejectCIMException code.
355 2. Cleanup some issues in the EnumerationContextTimeout Thread.
356 3. Fixed issue in pullop where it was using zero as default for default
357 operation timeout where it should have been NULL, the DMTF specified
358 default.
359 4. Enabled the test to reject 0 as operation timeout on a request and but
360 controled by a #define in CIMOperationRequestDispatcher.cpp
361 5. Added test for excessive new OperationContext entries in table.
362
363 18 April 2014
364 1. Internationalize remaining messages in CIMOperationRequestDecoder.cpp and
365 clean up the decoders for some of the messages so they use the
366 ...Iparam classes. Note that we did not clean up all of the old message
367 decoders, just the new ones and we did not clean up the Count message
368 since it is deprecated. TODO clean these up so the decoder is really
369 consistent.
370 2. Enabled the EnumerationContext Timer and removed code for alternate
371 non-thread solution.
|
372 karl 1.1.2.16
|
373 karl 1.1.2.21 17 April 2014
374 1. Reorganized the lock/unlock for handling the EnumerationContext because
375 there were thread windows (i.e. using the context after it was released
376 by other thread).
377 2. Modified code for the InteroperationTimerThread and deleted old code that
378 allowed this whole thread to by bypassed.
379 3. Internationalized a number of CIMOperationRequestDispatcher CIMException
380 response messages.
|
381 karl 1.1.2.22 4. Fixed stress tests in Client/tests/pullop that were getting timeout. The
382 issue was not the pull code but that fact that the idle client timeout
383 appears to be measureing to the end of the operation and the operation
384 was taking more than 40 seconds which is the default timeout. The idle
385 timeout takes no account of the fact that chunks are being regularly
386 delivered.
387 5. Several minor code changes.
388 NOTE: At this point the code passes extensive tests of the pull operations
389 both in OOP and none OOP mode (but with lots of diagnostics that may
390 be affecting timing).
|
391 karl 1.1.2.21
|
392 karl 1.1.2.20 10 April 2014
393 1. Fix issues causing failure with repeated pull operations.
394 2. Consolidate some of the CIMOperationRequestDispatcher.cpp template code
395
|
396 karl 1.1.2.19 7 April 2104
397 MergeOut of head of tree.
398
399 7 April 2014
400 1. Permanently fixed issue with getting correct number of objects on response.
401 This was introduced when did a temp fix to the OOP processing, in particular
402 removed the condition variable wait in the CIMOperationDispatcher handle
403 functions for opens and pulls. This moved the functionality to kick off
404 open and pull responses to the provider threads if there are not enough
405 objects when the handle is processed. Also added a variable to allow us to
406 test with either a) responses are required to satisfy the original
407 request size or) b, responses are required only to return some objects.
408 We will add statistics to see which of these works best.
409 2. Modified WsmProcessor EnumerationContext class since the name conflicts
410 with the pull Operation EnumerationContext class.
411 3. Created a new intermediate level of CIMMessage, the CIMPullResponseData
412 Message so that all of the open and Pull responses can use common code
413 since there are only two variables (endOfSequence and EnumerationContext)
414 and they are common across all the open and pull responses.
415 4. Removed a number of diagnostics.
416 5. Cleaned up the Dispcatcher so that the open and pulls have common response
417 karl 1.1.2.19 code and that code can be used from the dispatcher handle functions and
418 the provider response functions.
419
|
420 karl 1.1.2.18 31 March 2014 - Checkin
421 1. Fixed issues in OOP processing of pull operations, in particular
422 issues with cimxml output format when processed through the
423 *InternalXmlEncoder functions.
424 2. Clean up some of the internalXml functionality
425 3. Found issues causing timeout with a particular provider. The issue
426 is that the dispatcher and monitor end up using the same thread so the
427 condition variable in the dispatcher thread stops the monitor. Turned
428 off the conditionVariable in getCache for the moment which means that
429 we get number of responses for open... with 0 objects before the
430 providers can begin to respond. This is only for test.
431 4. Added some statistics for enumerations and display the statistics
432 when we close the server (same as cache statistics)
433
434 12 March 2014 - Mergeout and Mergein
435 1. Mergeout to head of tree for this date and mergein for patch update
436 to bug 9676
437 2. Extensions to pullop tests program and tests.
438 3. Added some diagnostics in looking for OOP issue.
439 4. Removed a number of diagnostics messages and cleaned up code in
440 dispatcher to simplify pull operation processing.
441 karl 1.1.2.18
|
442 karl 1.1.2.17 15 December 2013
443 1. Mergeout and mergein up to 15 December 2013
444 2. Clean up issues from tests documented in bug 9676 last week.
445 3. Clean up some code in dispatcher
446 4. Remove the filter function from ResponseStressc++Provider.
447
|
448 karl 1.1.2.16 21 November 2013
449 1. Mergeout from head of tree to 21 November 2013.
|
450 karl 1.1.2.15
451 18 November 2013
452 1. Cleanup of a bunch of minor errors and completion of all of the code for
453 the openQueryInstances except for the PullInstances in Dispatcher and
454 the aggregator function.
455 2. OpenqueryInstances added to cimcli.
|
456 karl 1.1.2.14
457 13 October 2013 CVS branch update.
458 1. Integrated bug 9786 into the branch. Note that we need to test the
459 generated statistics.
460 2. Mergeout executed to update to head of tree as of 8:00 am 13 October 2013.
461 3. Cleaned up several errors in OOP processing. Note that there is at least
462 one issue left when we to a pull on ManagedElement in at least one of the
463 namespaces.
464 4. Cleaned up some of the outstanding diagnostic code
465 5. Generally passes all tests except for one test of pullop where it is trying
466 to pull enum instances CIM_ManagedElement from a particular namespace.
|
467 karl 1.1.2.12
|
468 karl 1.1.2.16 NOTE: I did not make comments here for changes in October despite the fact
469 that I did 2 mergouts, number of fixes, and a mergein.
470
|
471 karl 1.1.2.12 30 September 2013 - CVS Update
472 Mergeout head of tree up to 29 September 2013.
|
473 karl 1.1.2.10
474 29 September 2013. CVS update.
475 1. Modified calls to statisticalData.cpp to a) directly call with request
476 type, b) incorporate the open, pull, etc. messages. However, since these
477 are not part of the CIM class, we must do something special with them.
|
478 karl 1.1.2.13 See bug 9785 for full solution to this issue.
|
479 karl 1.1.2.10 2. Corrected OOP interface to enable new flag to indicate internal operations
480 and set host, etc.
481 3. Add code to CQLOperationsDispatcher and WQLOperationDispatcher to clean
482 up CIMResponseDataCounter after filtering.
483 4. Modified ProviderAgent to set Host info for some pull operations.
484 5. Added new flag to CIMBinMsgSerializer and Deserializer.
|
485 karl 1.1.2.8
|
486 karl 1.1.2.9 17 September 2013 CVS update (Actually two different updates over 3 days)
487 1. Clean up some issues in CIMMessage.h and CIMMessage.cpp
488 2. Extend OpenExecQuery to WQL and CQL processors but return not complete
489 3. Remove memory leak in EnumerationContext and EnumerationContextTable
490 handling.
491 4. Created template functions for much of the pull operations.
492 5. Reversed order of queryLanguage and query (and changed names to match
493 execQuery) in client and server. Note that these are the execQuery
494 WQL and CQL filters and NOT FQL filters.
495 6. Some code cleanup in dispatcher
496 7. Today, passes all tests in pullop but issue in alltests. For some reason
497 not finding CIMObjectManager instance. Also, leaves enumeration contexts
498 if client terminates since cleanup thread not operating.
|
499 karl 1.1.2.11 8. XML from OOP not correctly processed.
|
500 karl 1.1.2.9
|
501 karl 1.1.2.8 14 September 2013 CVS update
502 Merged out up to 25 August. Cleaned up all operations and standardized code.
503 At this point the non pull operations code is in a set of templates but the
504 pull is not yet.
505 Fixed a significant number of problems so that it appears that the operations
506 except for OpenExecQuery run stably, at least with the pullop test program.
507 Note that there is a problem in that the Interop control provider is not
508 returning its singleton wbemserver object for some reason. Causes a test
509 failure
|
510 karl 1.1.2.7
511 Fixed for 16 June CVS Update
512 1. Cleaned up the enumerationContext and Table release functions and tested
513 to confirm that we do not lose memory in either normal sequences or
514 sequences that close early. Cleaned up pullop and added more tests
|
515 karl 1.1.2.8 Taged Before: PREAUG25UPDATE and after POSTAUG25UPDATE
|
516 karl 1.1.2.4
517 Fixed for 9 June CVS update
518 1. Cleaned up code for OpenQueryInstances. Note that this is incomplete.
519 No support in WQL or CQL Operations
520 2.
521
522 What was fixed for 5 June checkin.
|
523 karl 1.1.2.3 1. Extended ResponseTest MOF for for both CMPI and C++ subclasses
524 2. Fixed issues with pullop.
525 3. Fixed temp issue with CIMResponseData size by putting in mutex. That
526 is not a permanent fix but it gets around issue probably in the control
527 of the move logic that meant counts were off.
528 4. Fixed issues in Dispatcher so that associator code works. Still messy
529 code in the dispatcher.
530 5. Changed name of Enumerationtable.h & cpp to EnumerationContextTable.*
531 6 Changed name of ResponseStressTest module, classes, etc.
532
533 TAG: TASK_PEP317_5JUNE_2013_2
534
|
535 karl 1.1.2.2 2 June 2013
|
536 karl 1.1.2.1
537 Issues - KS
538
|
539 karl 1.1.2.15 - Still way to many TODO and KS comments and KS_TEMPS. Removing bit by bit.
|
540 karl 1.1.2.1
|
541 karl 1.1.2.15 - Runtime variable connection for the config parameters not installed. That
542 has been made into a separate bug (see bug 9819)
|
543 karl 1.1.2.1
544 5. Issue with the threaded timer. For some reason during tests it
545 eventually calls the timer thread with trash for the parm (which is
546 pointer to the EnumerationTable object). Caught because we do a valid
547 test at beginning of the function.
548
|
549 karl 1.1.2.2 6. Still using the templates in CIMOperationRequestDispatcher to simplify
550 the handle... processing.
551
552 7. I think I have a way around the double move of objects in the
553 EnumerationContext so that the outputter will just take a defined number
554 of objects directly from the gathering cache and save the second move.
555
|
556 karl 1.1.2.15 8. Not yet passing all tests but getting closer now. The major test that is
557 causing an error today is the execution of a full enumeration with the
558 forceProviders = true. This causes a client timeout sometimes.
|
559 karl 1.1.2.2
560
561
|
562 karl 1.1.2.1 ===========================================
563
564 OVERVIEW:
565
566 The operation extensions for pull operations defined in the DMTF specification
567 DSP0200 V 1.4 were implemented in Pegasus effective Pegasus version 2.11
568 including Client and Server.
569
570 These operations extend the CIM/XML individual operations to operation
571 sequences where the server must maintain state between operations in a
572 sequence and the client must execute multiple operations to get the full
573 set of instances or instance paths.
574
575 The following new CIM/XML operations as defined in DSP0200 are included;
576
577 -OpenEnumerateInstances
578 -openEnumerateInstancePaths
579 -OpenReferenceInstances
580 -OpenReferenceInstancePaths
581 -OpenAssociatiorInstances
582 -OpenAssociatorInstancePaths
|
583 karl 1.1.2.16 -OpenQueryInstances
|
584 karl 1.1.2.1 -PullInstancesWithPath
585 -PullInstancePaths
|
586 karl 1.1.2.16 -PullInstances
|
587 karl 1.1.2.1 -CloseEnumeration
588 -EnumerationCount
|
589 karl 1.1.2.2 OpenExecQuery
|
590 karl 1.1.2.1
591 The following operations have not been implemented in this version of Pegasus:
592
593 -OpenQueryInstances
594
595 The following limitations on the implementation exist;
596
597 1. The filterQueryLanguage and filterQuery parameters are processed by
598 the Pegasus client but the server returns error if there is any data in
|
599 karl 1.1.2.2 either parameter. This work does not include the development of the
600 query language. Note that a separate effort to extend Pegasus to use
601 the DMTF FQL query language is in process.
|
602 karl 1.1.2.1
603 2. The input parameter continueOnError is processed correctly by the client
604 but the Pegasus server only provides for false since the server does not
605 include logic to continue processing responses after an error is
606 encountered.
607 This is consistent with the statement in the specification that use of
608 this functionality is optional and the fact that the DMTF agrees that all
609 of the issues of continuing after errors have not been clarified.
610
611 3. The operation enumerationCount is not processed by the server today since
612 a) really getting the count would be the same cost as the corresponding
613 enumeration, b) the server does not include a history or estimating
614 mechanism for this to date.
|
615 karl 1.1.2.2 NOTE: After a through review as part of the development of the next version
616 of CMPI we have concluded that this operation is probably not worth the
617 effort. Since it is optional, Pegasus will only return the unknown status
618 at this point
|
619 karl 1.1.2.1
620 Since the concept of sequences of operations linked together (open, pull, close)
621 is a major extension to the original CIM/XML operation concept of completely
622 independent operations several new pieces of functionality are implemented
623 to control interOperationTimeouts, counts of objects to be returned, etc.
624
625 TBD - Review this
626
627 CLIENT
628
629 The new operations follow the same pattern as the APIs for existing operations
630 in that:
631
632 1. All errors are handled as CIMException and Exception
633
634 2. The means of inputting parameters are the same except that there are
635 significantly more input parameters with the open operations and for the
636 first time operations return parameters as well as objects in the
637 response. Specifically the open and pull operations return values for
638 enumerationContext which is the identity for a pull sequence and
639 endOfSequence which is the marker the server sends in open and pull
640 karl 1.1.2.1 responses when it has no more objects to send.
641
642 The significant differences include:
643
644 1. Processing of parameters on responses (i.e. the endOfSequence and
645 enumerationContext parameters are returned for open and pull operations).
646
647 2. Numeric arguments (Uint32 and Uint64 include the option of NULL in some
648 cases so they are packaged inside classes Uint32Arg and Uint64Arg in the
649 client api.
650
651 3. The association and reference operations ONLY process instances. They do
652 not include the capability to return classes like reference and associator
653 do and therefore return CIMInstance rather than CIMObject.
654
655 4. Paths are returned in all cases (i.e OpenEnumerateInstances and
656 PullInstancesWithPath where they were not with EnumeratInstances.
657
658 5. The client must maintain state between operations in a sequence (using
659 the enumerationContext parameter).
660
661 karl 1.1.2.1 TBD- Are there more differences.
662
663
664 SERVER
665
666 The Pegasus server attempts to always deliver the requested number of objects
667 for any open or pull request (the specification allows for the server to
668 deliver less than the requested number of objects and specifically to return
669 zero objects on open). We felt that it was worth any extra cost in processing
670 to provide the client with exactly what it had requested.
671
672 The pegasus server always closes an enumeration sequence upon receipt of any
673 error from the providers, repository, etc. Therefore the server will reject
|
674 karl 1.1.2.2 any request that has continueOnError = true;
675
676 Expansion to allow the continue on error may be added in a future version.
677 In any case, the whole purpose of the continue on error is really to allow
678 input from good providers to be mixed with providers that return errors so
679 that generally this would mean simply changing the logic in the return mechanism
680 to not shutdown when an error is received from any given provider.
681
682 Generally we do not believe that the providers need to do much more in the
683 future to support the continueOnError other than possibly allowing the provider
684 to continue processing after it has received an error.
|
685 karl 1.1.2.1
686 PROVIDERS
687
688 This implementation requires NO changes to the existing providers. The
689 provider APIs operate just as they do with the original operations.
690
691 Because the server processing is different however, there may be some
692 behavior differences primarily because the client now controls the speed of
693 delivery of objects.
694
695 In previous versions of Pegasus, the server attempts to deliver objects as
696 rapidly as then can be put on the network. In the case of HTTP chunked requests
697 they are delivered in chunks of about 100 objects. The primary delay for the
698 providers was the processing of each segment through the server. The server
699 is blocked so that no other segment can proceed through the server until that
700 segment is processed and sent on the network.
701 In the case of non-chunkedresponses, they are completely gathered in the serve
702 and then delivered as one non-chunked response. There were no delays for the
703 providers, just lots of possible memory use in the server.
704
705 The responses from providers (delivered through the deliver(...) interface are
706 karl 1.1.2.1 gathered into segments of about 100 objects and this group of objects is moved
707 through the server to be delivered to the client.
708
709 However with the inclusion of the pull operations, The segments of objects
710 from the providers are cached in the server response path until the
711 maxObjectCount for that request (open or pull) and that number returned in a
712 non-chunked response. Thus, if the client is slow to issue pull requests,
713 the providers might be delayed at some point to reduce memory usage in the
714 server (the delay appears as slow response tothe deliver operation).
715
716 In other words, the time to process large sets of responses from the provider
717 now depends on the speed of handling the client.
718
719 It is important to remember in developing providers that the Pegasus server
720 can most efficiently process responses if they are passed from the provider
721 to the server individually or in small arrays of objects rather than the
722 provider gathering very large arrays of objects and sending them to the
723 server.
724
|
725 karl 1.1.2.2 NEXT GENERATION PROVIDERS
726 KS_TODO
727
|
728 karl 1.1.2.1 CONFIGURATION PARAMETERS
729
730 The server includes several configuration parameters to set limits on the
731 processing of pull operations. All of these configuration parameters are
732 compile time parameters rather than runtime.
733
734 1. Maximum value of minimum interoperation time. This parameter defines the
735 maximum time allowed between the return of an open or pull response and
736 the receipt of the next pull or a close operation before the server may
737 close the enumeration. The specification allows the server to set a
738 maximum interoperation time and refuse open requests that with requested
739 operationTimeout greater than that time.
740 CIM_ERR_INVALID_OPERATION_TIMEOUT
741
742 This value is set with the Pegasus environment variable
743 PEGASUS_PULL....
744
745 2. Maximum objects returned in a single open or pull operation. The server
746 can set a maximum limit on the number of objects that can be returned in
747 a single open or pull oepration with the maxObjectCount parameter.
748
749 karl 1.1.2.1 3. Whether the server allows 0 as an interoperation timeout value. The value
750 zero is s special value for the interoperationTimeout in that it tells the
751 server to not timeout any enumeration sequence.
752
753 With this value for interoperationTimeout, the only way to close an
754 enumeration sequence is to complete all of the pulls or issue the close.
755 If for some reason the sequence is not completed, that enumeration context
756 would remain open indefinitly. Since in Pegasus any open enumeration
757 context uses resources (the context object and any provider resposnes that
758 have not yet been issued in a response) it would appear that most
759 platforms would not want to allow the existence of enumeration contexts
760 that cannot be closed by the server.
761
762 4, maximum consecutive pull requests with 0 maxObjectCount. The use of the
763 pull operation with maxObjectCount set to zero could be used to keep an
764 enumeration context open indefinitly (this tells the server to restart the
765 interoperationTimeout but not send any objects in the response). Therefore the
766 specification allows for the server setting maximum limits on this behavior
767 and returning the error CIM_ERR_SERVER_LIMITS_EXCEEDED if this limit is
768 exceeded.
769 Note that this is maximum CONSECUTIVE pulls so that issuing a pull with
770 karl 1.1.2.1 a non-zero count resets this counter.
771
772 KS-TBD - Is this really logical since we can still block by just issuing
773 lots of zero request and an occansional request for one object.
774
775 Pegaus sets the value of this limit to 1000 and allows the implementer to
776 modify it with the PEGASUS_MAXIMUM_ZERO_OBJECTCOUNT environment variable.
777
778 5. Default operationTimeout -
779
780 The default of this parameter is to refuse operat
781
782 In the current release of Pegasus these are all compile time parameters.
|
783 karl 1.1.2.11
784
785 NOTES On working with task branch.
786
787 Merge out Process
788
789 To keep our TASK branch in sync with the current head of tree we need
790 to do a regular merge out. the TaskMakefile contains the makefile
791 procedures to do this efficiently. NOTE: Following these procedures is
792 important in that you are merging out new material each time you do
793 the merge out. If you were just to repeatedly merge out, you would be
794 merging previously merged changes a second time causing a real mess.
795
796 Start with new directory and put TaskMakefile above pegasus (needed so you
797 have this file for the initial operations.
798
799 make -f TaskMakefile branch_merge_out BNAME=PEP317-pullop ## takes a long time
800
801 This checks out current head, merges it into task branch and sets tags
802 for the mergeout. Note that at the end of this step this work is
803 part of the TASK... branch.
804 karl 1.1.2.11
805 NOW check for conflicts, errors, etc. that resulted from the merge.
806 Look for conflict flags, compare the results (I use linux merge as a
807 good graphic compare tool) and build and test. When you are satisfied
808 that the merge out is clean, you can commit the results to the TASK...
809 branch
810
811 To commit the work to this into Task branch
812
813 make -f mak/TaskMakefile branch_merge_out_commit BNAME=PEP317-pullop
814
815 or manually commit and finish as follows
816
817 cvs commit
818 make -f mak/TaskMakefile branch_merge_out_finish BNAME=PEP317-pullop
819
820 ## This last step is important since it cleans up temporary tags to prepare
821 you for the next checkout
822
823 COMPARE TASKBRANCH WITH HEAD
824
825 karl 1.1.2.11 In a new pegasus work space do same as above for merge out.
826
827 make -f TaskMakefile BNAME=PEP317-pullop
828
829 This produces a result which is all of the head merged into the branch.
830 A diff of this is all the new changes to the head of tree that you will
831 include into the merge.
832
|
Return to
readme.pulloperations
CVS log
Up to [Pegasus] / pegasus