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.14 OOP right now. Corrected by converting to XML.
|
15 karl 1.1.2.23 2. OpenExecQuery - Code is incomplete in that it does not include the
|
16 karl 1.1.2.15 return from the exec query function to the aggregator yet.
|
17 karl 1.1.2.4 3. Code for Pull part of OpenQueryInstancesRequest a) should be part of
18 the common CIMOperationRequestDispatcher execCommon code.
19 4. The changes to WQLCIMOperationRequestDispatcher and CQL... for handling
20 pull not completed so we feed the responses back to the EnmerationContext
21 queues
|
22 karl 1.1.2.27 3. Minor TODOs, diagnostics, etc. still in the code
|
23 karl 1.1.2.14 4. External runtime variables. Proposing that they be fixed for this release
|
24 karl 1.1.2.15 rather than set by configuration. This should be discussed. Am making
|
25 karl 1.1.2.16 this a separate bug. See bug 9819 for the changes to cover this.
|
26 karl 1.1.2.24 5. Consider moving some more of the code in dispatcher from templates to
|
27 karl 1.1.2.23 common functions which would mean adding intermediate classes in
28 CIMMessage but would reduce code size. Currently the change that
29 we should make for this is to create a new message CIMPullRequestData...
30 between CIMRequestDataMessage and the Pull requests since they all
31 have exactly the same input and output pararameters (The
32 CIMResponseData hides the response object differences)
33 6. Extension to avoid double move of objects in CIMResponseData (one
|
34 karl 1.1.2.3 into enumerationContext queue and second to new cimResponseData for
35 response. Want to avoid second move by extending Open/Pull response
36 messages to include count and CIMResponse data to count objects out
|
37 karl 1.1.2.23 of queue when converting (avoids the second move). This would mean
38 extending the output writers to allow the count field to be supplied
39 so they would only create output for up to the count supplied.
|
40 karl 1.1.2.28 9. Add more static tests (currently only OpenEnumerateInstances and
41 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 way to test multiple opertions in sequence(i.e. open/pull) and
45 cannot be sure how many responses will come back in all cases even
46 for open.
|
47 karl 1.1.2.26 10. Could clean up the CIMOperationRequestDecoder.cpp rejectCIMException
|
48 karl 1.1.2.23 further since there is some overlap. That is low priority.
|
49 karl 1.1.2.28 11. Correct issue between operations and HTTP where we are sending
|
50 karl 1.1.2.26 trailers with exceptions. Also correct issue where we are
51 sending endOfSequence and EnumerationContext in response when
|
52 karl 1.1.2.28 we send CIMException. DONE Except that we really need to get
53 rid of the trailers completely for pull operations. Need to
54 have flag to send as non trailer (probably non_chunked flag)
|
55 karl 1.1.2.26
56 NEXT TASKS:
|
57 karl 1.1.2.23 b. Finish and test the OpenQueryInstances
|
58 karl 1.1.2.16 c. Clean up TODOs
|
59 karl 1.1.2.23 d. Find issue that is causing occasional failures under load. It
60 is probably a threading issue between the 3 possible threads
61 that use the EnumerationContext (request thread, provider thread,
|
62 karl 1.1.2.24 timeout thread) and a place where not mutuxed, primarily the
63 timeout thread.
|
64 karl 1.1.2.23
|
65 karl 1.1.2.28 1 May 2014
66 1. Cleanup of code and variable names.
67 2. Removed namespace variable from EnumerationContext. It was never used.
68 3. Added test for max number of open enumerations. Right now it is fixed
69 and set about 100. Note that this is tied to the size of hash table
70 so that there is a issue with more dynamic setting of max and the
71 hash table size.
72 4. Removed several unused functions.
73 5. Found one possible issue causing thread conflict but not the core one
74 yet.
75
76 30 April
77 1. Added exception response to dispatcher for Limits exceeded on
78 CreateEnumerationContext. Returns Exceeded server limits CIMException.
79 2. Fixed possible deadlock where we were not unlocking EnumerationContext
80 under error condition
81
82
|
83 karl 1.1.2.27 27 April - mergeout to head of tree
84 1. Mergeout of the code to the head of tree. Documented that mergeout in
85 the bug
86
87 27 April 2014
88 1. Clean up in a number of areas, mostly just code without changing
89 functionality.
90 2. Modified CIMMessage.h slightly to clarify names of the pull intermediate
91 messages (the common open and pull response);
92 3. Removed a number of diagnostics from CIMResponseData
93 4. Added new function to ResponseStressTestProvider to be able to terminate
94 output after a defined number of objects with a CIMException.
95 5. Removed a number of other TODOs
96 6. Corrected a couple of errors in the server message bundle.
97 7. Modified ResponseEncoder to only output the error for pull errors.
98 It was errounously outputting the EndOfSequence, EnumerationContext and
99 the error. This way, only the error is sent which is spec.
100 8. Removed number of TODOs and cleaned up a couple of others.
101 9. Added static tests for OpenEnumerateInstanceNames.
102 10. Modified a number of the temporary diagnostics to be permanent by
103 changing them to PEGASUS_DEBUG_ASSERTs
104 karl 1.1.2.27
|
105 karl 1.1.2.24 22 April 2014
106 1. Clean up some messages.
107 2. Still trying to find issue that randomly keeps messages in timeout
108 queue long after they have been closed and returned.
|
109 karl 1.1.2.25 3. Fixed memory loss error.
|
110 karl 1.1.2.26 4. Added zero reject for OperationTimeout because that effectively disables
111 the whole timeout mechanism so that enumerations could be started, never
112 completed by the client and would just hang around in memory. That
113 would be a significant DDOS attack (start very large enum with no
114 timeout) and never do pulls after open.
|
115 karl 1.1.2.25
|
116 karl 1.1.2.23 21 April 2014
|
117 karl 1.1.2.27 1. Reorganized code in CIMOperationRequestDecoder.cpp ...Iparam classes.
|
118 karl 1.1.2.23 Cleaned up the rejectCIMException code.
119 2. Cleanup some issues in the EnumerationContextTimeout Thread.
120 3. Fixed issue in pullop where it was using zero as default for default
121 operation timeout where it should have been NULL, the DMTF specified
122 default.
123 4. Enabled the test to reject 0 as operation timeout on a request and but
124 controled by a #define in CIMOperationRequestDispatcher.cpp
125 5. Added test for excessive new OperationContext entries in table.
126
127 18 April 2014
128 1. Internationalize remaining messages in CIMOperationRequestDecoder.cpp and
129 clean up the decoders for some of the messages so they use the
130 ...Iparam classes. Note that we did not clean up all of the old message
131 decoders, just the new ones and we did not clean up the Count message
132 since it is deprecated. TODO clean these up so the decoder is really
133 consistent.
134 2. Enabled the EnumerationContext Timer and removed code for alternate
135 non-thread solution.
|
136 karl 1.1.2.16
|
137 karl 1.1.2.21 17 April 2014
138 1. Reorganized the lock/unlock for handling the EnumerationContext because
139 there were thread windows (i.e. using the context after it was released
140 by other thread).
141 2. Modified code for the InteroperationTimerThread and deleted old code that
142 allowed this whole thread to by bypassed.
143 3. Internationalized a number of CIMOperationRequestDispatcher CIMException
144 response messages.
|
145 karl 1.1.2.22 4. Fixed stress tests in Client/tests/pullop that were getting timeout. The
146 issue was not the pull code but that fact that the idle client timeout
147 appears to be measureing to the end of the operation and the operation
148 was taking more than 40 seconds which is the default timeout. The idle
149 timeout takes no account of the fact that chunks are being regularly
150 delivered.
151 5. Several minor code changes.
152 NOTE: At this point the code passes extensive tests of the pull operations
153 both in OOP and none OOP mode (but with lots of diagnostics that may
154 be affecting timing).
|
155 karl 1.1.2.21
|
156 karl 1.1.2.20 10 April 2014
157 1. Fix issues causing failure with repeated pull operations.
158 2. Consolidate some of the CIMOperationRequestDispatcher.cpp template code
159
|
160 karl 1.1.2.19 7 April 2104
161 MergeOut of head of tree.
162
163 7 April 2014
164 1. Permanently fixed issue with getting correct number of objects on response.
165 This was introduced when did a temp fix to the OOP processing, in particular
166 removed the condition variable wait in the CIMOperationDispatcher handle
167 functions for opens and pulls. This moved the functionality to kick off
168 open and pull responses to the provider threads if there are not enough
169 objects when the handle is processed. Also added a variable to allow us to
170 test with either a) responses are required to satisfy the original
171 request size or) b, responses are required only to return some objects.
172 We will add statistics to see which of these works best.
173 2. Modified WsmProcessor EnumerationContext class since the name conflicts
174 with the pull Operation EnumerationContext class.
175 3. Created a new intermediate level of CIMMessage, the CIMPullResponseData
176 Message so that all of the open and Pull responses can use common code
177 since there are only two variables (endOfSequence and EnumerationContext)
178 and they are common across all the open and pull responses.
179 4. Removed a number of diagnostics.
180 5. Cleaned up the Dispcatcher so that the open and pulls have common response
181 karl 1.1.2.19 code and that code can be used from the dispatcher handle functions and
182 the provider response functions.
183
|
184 karl 1.1.2.18 31 March 2014 - Checkin
185 1. Fixed issues in OOP processing of pull operations, in particular
186 issues with cimxml output format when processed through the
187 *InternalXmlEncoder functions.
188 2. Clean up some of the internalXml functionality
189 3. Found issues causing timeout with a particular provider. The issue
190 is that the dispatcher and monitor end up using the same thread so the
191 condition variable in the dispatcher thread stops the monitor. Turned
192 off the conditionVariable in getCache for the moment which means that
193 we get number of responses for open... with 0 objects before the
194 providers can begin to respond. This is only for test.
195 4. Added some statistics for enumerations and display the statistics
196 when we close the server (same as cache statistics)
197
198 12 March 2014 - Mergeout and Mergein
199 1. Mergeout to head of tree for this date and mergein for patch update
200 to bug 9676
201 2. Extensions to pullop tests program and tests.
202 3. Added some diagnostics in looking for OOP issue.
203 4. Removed a number of diagnostics messages and cleaned up code in
204 dispatcher to simplify pull operation processing.
205 karl 1.1.2.18
|
206 karl 1.1.2.17 15 December 2013
207 1. Mergeout and mergein up to 15 December 2013
208 2. Clean up issues from tests documented in bug 9676 last week.
209 3. Clean up some code in dispatcher
210 4. Remove the filter function from ResponseStressc++Provider.
211
|
212 karl 1.1.2.16 21 November 2013
213 1. Mergeout from head of tree to 21 November 2013.
|
214 karl 1.1.2.15
215 18 November 2013
216 1. Cleanup of a bunch of minor errors and completion of all of the code for
217 the openQueryInstances except for the PullInstances in Dispatcher and
218 the aggregator function.
219 2. OpenqueryInstances added to cimcli.
|
220 karl 1.1.2.14
221 13 October 2013 CVS branch update.
222 1. Integrated bug 9786 into the branch. Note that we need to test the
223 generated statistics.
224 2. Mergeout executed to update to head of tree as of 8:00 am 13 October 2013.
225 3. Cleaned up several errors in OOP processing. Note that there is at least
226 one issue left when we to a pull on ManagedElement in at least one of the
227 namespaces.
228 4. Cleaned up some of the outstanding diagnostic code
229 5. Generally passes all tests except for one test of pullop where it is trying
230 to pull enum instances CIM_ManagedElement from a particular namespace.
|
231 karl 1.1.2.12
|
232 karl 1.1.2.16 NOTE: I did not make comments here for changes in October despite the fact
233 that I did 2 mergouts, number of fixes, and a mergein.
234
|
235 karl 1.1.2.12 30 September 2013 - CVS Update
236 Mergeout head of tree up to 29 September 2013.
|
237 karl 1.1.2.10
238 29 September 2013. CVS update.
239 1. Modified calls to statisticalData.cpp to a) directly call with request
240 type, b) incorporate the open, pull, etc. messages. However, since these
241 are not part of the CIM class, we must do something special with them.
|
242 karl 1.1.2.13 See bug 9785 for full solution to this issue.
|
243 karl 1.1.2.10 2. Corrected OOP interface to enable new flag to indicate internal operations
244 and set host, etc.
245 3. Add code to CQLOperationsDispatcher and WQLOperationDispatcher to clean
246 up CIMResponseDataCounter after filtering.
247 4. Modified ProviderAgent to set Host info for some pull operations.
248 5. Added new flag to CIMBinMsgSerializer and Deserializer.
|
249 karl 1.1.2.8
|
250 karl 1.1.2.9 17 September 2013 CVS update (Actually two different updates over 3 days)
251 1. Clean up some issues in CIMMessage.h and CIMMessage.cpp
252 2. Extend OpenExecQuery to WQL and CQL processors but return not complete
253 3. Remove memory leak in EnumerationContext and EnumerationContextTable
254 handling.
255 4. Created template functions for much of the pull operations.
256 5. Reversed order of queryLanguage and query (and changed names to match
257 execQuery) in client and server. Note that these are the execQuery
258 WQL and CQL filters and NOT FQL filters.
259 6. Some code cleanup in dispatcher
260 7. Today, passes all tests in pullop but issue in alltests. For some reason
261 not finding CIMObjectManager instance. Also, leaves enumeration contexts
262 if client terminates since cleanup thread not operating.
|
263 karl 1.1.2.11 8. XML from OOP not correctly processed.
|
264 karl 1.1.2.9
|
265 karl 1.1.2.8 14 September 2013 CVS update
266 Merged out up to 25 August. Cleaned up all operations and standardized code.
267 At this point the non pull operations code is in a set of templates but the
268 pull is not yet.
269 Fixed a significant number of problems so that it appears that the operations
270 except for OpenExecQuery run stably, at least with the pullop test program.
271 Note that there is a problem in that the Interop control provider is not
272 returning its singleton wbemserver object for some reason. Causes a test
273 failure
|
274 karl 1.1.2.7
275 Fixed for 16 June CVS Update
276 1. Cleaned up the enumerationContext and Table release functions and tested
277 to confirm that we do not lose memory in either normal sequences or
278 sequences that close early. Cleaned up pullop and added more tests
|
279 karl 1.1.2.8 Taged Before: PREAUG25UPDATE and after POSTAUG25UPDATE
|
280 karl 1.1.2.4
281 Fixed for 9 June CVS update
282 1. Cleaned up code for OpenQueryInstances. Note that this is incomplete.
283 No support in WQL or CQL Operations
284 2.
285
286 What was fixed for 5 June checkin.
|
287 karl 1.1.2.3 1. Extended ResponseTest MOF for for both CMPI and C++ subclasses
288 2. Fixed issues with pullop.
289 3. Fixed temp issue with CIMResponseData size by putting in mutex. That
290 is not a permanent fix but it gets around issue probably in the control
291 of the move logic that meant counts were off.
292 4. Fixed issues in Dispatcher so that associator code works. Still messy
293 code in the dispatcher.
294 5. Changed name of Enumerationtable.h & cpp to EnumerationContextTable.*
295 6 Changed name of ResponseStressTest module, classes, etc.
296
297 TAG: TASK_PEP317_5JUNE_2013_2
298
|
299 karl 1.1.2.2 2 June 2013
|
300 karl 1.1.2.1
301 Issues - KS
302
|
303 karl 1.1.2.15 - Still way to many TODO and KS comments and KS_TEMPS. Removing bit by bit.
|
304 karl 1.1.2.1
|
305 karl 1.1.2.15 - Runtime variable connection for the config parameters not installed. That
306 has been made into a separate bug (see bug 9819)
|
307 karl 1.1.2.1
308 5. Issue with the threaded timer. For some reason during tests it
309 eventually calls the timer thread with trash for the parm (which is
310 pointer to the EnumerationTable object). Caught because we do a valid
311 test at beginning of the function.
312
|
313 karl 1.1.2.2 6. Still using the templates in CIMOperationRequestDispatcher to simplify
314 the handle... processing.
315
316 7. I think I have a way around the double move of objects in the
317 EnumerationContext so that the outputter will just take a defined number
318 of objects directly from the gathering cache and save the second move.
319
|
320 karl 1.1.2.15 8. Not yet passing all tests but getting closer now. The major test that is
321 causing an error today is the execution of a full enumeration with the
322 forceProviders = true. This causes a client timeout sometimes.
|
323 karl 1.1.2.2
324
325
|
326 karl 1.1.2.1 ===========================================
327
328 OVERVIEW:
329
330 The operation extensions for pull operations defined in the DMTF specification
331 DSP0200 V 1.4 were implemented in Pegasus effective Pegasus version 2.11
332 including Client and Server.
333
334 These operations extend the CIM/XML individual operations to operation
335 sequences where the server must maintain state between operations in a
336 sequence and the client must execute multiple operations to get the full
337 set of instances or instance paths.
338
339 The following new CIM/XML operations as defined in DSP0200 are included;
340
341 -OpenEnumerateInstances
342 -openEnumerateInstancePaths
343 -OpenReferenceInstances
344 -OpenReferenceInstancePaths
345 -OpenAssociatiorInstances
346 -OpenAssociatorInstancePaths
|
347 karl 1.1.2.16 -OpenQueryInstances
|
348 karl 1.1.2.1 -PullInstancesWithPath
349 -PullInstancePaths
|
350 karl 1.1.2.16 -PullInstances
|
351 karl 1.1.2.1 -CloseEnumeration
352 -EnumerationCount
|
353 karl 1.1.2.2 OpenExecQuery
|
354 karl 1.1.2.1
355 The following operations have not been implemented in this version of Pegasus:
356
357 -OpenQueryInstances
358
359 The following limitations on the implementation exist;
360
361 1. The filterQueryLanguage and filterQuery parameters are processed by
362 the Pegasus client but the server returns error if there is any data in
|
363 karl 1.1.2.2 either parameter. This work does not include the development of the
364 query language. Note that a separate effort to extend Pegasus to use
365 the DMTF FQL query language is in process.
|
366 karl 1.1.2.1
367 2. The input parameter continueOnError is processed correctly by the client
368 but the Pegasus server only provides for false since the server does not
369 include logic to continue processing responses after an error is
370 encountered.
371 This is consistent with the statement in the specification that use of
372 this functionality is optional and the fact that the DMTF agrees that all
373 of the issues of continuing after errors have not been clarified.
374
375 3. The operation enumerationCount is not processed by the server today since
376 a) really getting the count would be the same cost as the corresponding
377 enumeration, b) the server does not include a history or estimating
378 mechanism for this to date.
|
379 karl 1.1.2.2 NOTE: After a through review as part of the development of the next version
380 of CMPI we have concluded that this operation is probably not worth the
381 effort. Since it is optional, Pegasus will only return the unknown status
382 at this point
|
383 karl 1.1.2.1
384 Since the concept of sequences of operations linked together (open, pull, close)
385 is a major extension to the original CIM/XML operation concept of completely
386 independent operations several new pieces of functionality are implemented
387 to control interOperationTimeouts, counts of objects to be returned, etc.
388
389 TBD - Review this
390
391 CLIENT
392
393 The new operations follow the same pattern as the APIs for existing operations
394 in that:
395
396 1. All errors are handled as CIMException and Exception
397
398 2. The means of inputting parameters are the same except that there are
399 significantly more input parameters with the open operations and for the
400 first time operations return parameters as well as objects in the
401 response. Specifically the open and pull operations return values for
402 enumerationContext which is the identity for a pull sequence and
403 endOfSequence which is the marker the server sends in open and pull
404 karl 1.1.2.1 responses when it has no more objects to send.
405
406 The significant differences include:
407
408 1. Processing of parameters on responses (i.e. the endOfSequence and
409 enumerationContext parameters are returned for open and pull operations).
410
411 2. Numeric arguments (Uint32 and Uint64 include the option of NULL in some
412 cases so they are packaged inside classes Uint32Arg and Uint64Arg in the
413 client api.
414
415 3. The association and reference operations ONLY process instances. They do
416 not include the capability to return classes like reference and associator
417 do and therefore return CIMInstance rather than CIMObject.
418
419 4. Paths are returned in all cases (i.e OpenEnumerateInstances and
420 PullInstancesWithPath where they were not with EnumeratInstances.
421
422 5. The client must maintain state between operations in a sequence (using
423 the enumerationContext parameter).
424
425 karl 1.1.2.1 TBD- Are there more differences.
426
427
428 SERVER
429
430 The Pegasus server attempts to always deliver the requested number of objects
431 for any open or pull request (the specification allows for the server to
432 deliver less than the requested number of objects and specifically to return
433 zero objects on open). We felt that it was worth any extra cost in processing
434 to provide the client with exactly what it had requested.
435
436 The pegasus server always closes an enumeration sequence upon receipt of any
437 error from the providers, repository, etc. Therefore the server will reject
|
438 karl 1.1.2.2 any request that has continueOnError = true;
439
440 Expansion to allow the continue on error may be added in a future version.
441 In any case, the whole purpose of the continue on error is really to allow
442 input from good providers to be mixed with providers that return errors so
443 that generally this would mean simply changing the logic in the return mechanism
444 to not shutdown when an error is received from any given provider.
445
446 Generally we do not believe that the providers need to do much more in the
447 future to support the continueOnError other than possibly allowing the provider
448 to continue processing after it has received an error.
|
449 karl 1.1.2.1
450 PROVIDERS
451
452 This implementation requires NO changes to the existing providers. The
453 provider APIs operate just as they do with the original operations.
454
455 Because the server processing is different however, there may be some
456 behavior differences primarily because the client now controls the speed of
457 delivery of objects.
458
459 In previous versions of Pegasus, the server attempts to deliver objects as
460 rapidly as then can be put on the network. In the case of HTTP chunked requests
461 they are delivered in chunks of about 100 objects. The primary delay for the
462 providers was the processing of each segment through the server. The server
463 is blocked so that no other segment can proceed through the server until that
464 segment is processed and sent on the network.
465 In the case of non-chunkedresponses, they are completely gathered in the serve
466 and then delivered as one non-chunked response. There were no delays for the
467 providers, just lots of possible memory use in the server.
468
469 The responses from providers (delivered through the deliver(...) interface are
470 karl 1.1.2.1 gathered into segments of about 100 objects and this group of objects is moved
471 through the server to be delivered to the client.
472
473 However with the inclusion of the pull operations, The segments of objects
474 from the providers are cached in the server response path until the
475 maxObjectCount for that request (open or pull) and that number returned in a
476 non-chunked response. Thus, if the client is slow to issue pull requests,
477 the providers might be delayed at some point to reduce memory usage in the
478 server (the delay appears as slow response tothe deliver operation).
479
480 In other words, the time to process large sets of responses from the provider
481 now depends on the speed of handling the client.
482
483 It is important to remember in developing providers that the Pegasus server
484 can most efficiently process responses if they are passed from the provider
485 to the server individually or in small arrays of objects rather than the
486 provider gathering very large arrays of objects and sending them to the
487 server.
488
|
489 karl 1.1.2.2 NEXT GENERATION PROVIDERS
490 KS_TODO
491
|
492 karl 1.1.2.1 CONFIGURATION PARAMETERS
493
494 The server includes several configuration parameters to set limits on the
495 processing of pull operations. All of these configuration parameters are
496 compile time parameters rather than runtime.
497
498 1. Maximum value of minimum interoperation time. This parameter defines the
499 maximum time allowed between the return of an open or pull response and
500 the receipt of the next pull or a close operation before the server may
501 close the enumeration. The specification allows the server to set a
502 maximum interoperation time and refuse open requests that with requested
503 operationTimeout greater than that time.
504 CIM_ERR_INVALID_OPERATION_TIMEOUT
505
506 This value is set with the Pegasus environment variable
507 PEGASUS_PULL....
508
509 2. Maximum objects returned in a single open or pull operation. The server
510 can set a maximum limit on the number of objects that can be returned in
511 a single open or pull oepration with the maxObjectCount parameter.
512
513 karl 1.1.2.1 3. Whether the server allows 0 as an interoperation timeout value. The value
514 zero is s special value for the interoperationTimeout in that it tells the
515 server to not timeout any enumeration sequence.
516
517 With this value for interoperationTimeout, the only way to close an
518 enumeration sequence is to complete all of the pulls or issue the close.
519 If for some reason the sequence is not completed, that enumeration context
520 would remain open indefinitly. Since in Pegasus any open enumeration
521 context uses resources (the context object and any provider resposnes that
522 have not yet been issued in a response) it would appear that most
523 platforms would not want to allow the existence of enumeration contexts
524 that cannot be closed by the server.
525
526 4, maximum consecutive pull requests with 0 maxObjectCount. The use of the
527 pull operation with maxObjectCount set to zero could be used to keep an
528 enumeration context open indefinitly (this tells the server to restart the
529 interoperationTimeout but not send any objects in the response). Therefore the
530 specification allows for the server setting maximum limits on this behavior
531 and returning the error CIM_ERR_SERVER_LIMITS_EXCEEDED if this limit is
532 exceeded.
533 Note that this is maximum CONSECUTIVE pulls so that issuing a pull with
534 karl 1.1.2.1 a non-zero count resets this counter.
535
536 KS-TBD - Is this really logical since we can still block by just issuing
537 lots of zero request and an occansional request for one object.
538
539 Pegaus sets the value of this limit to 1000 and allows the implementer to
540 modify it with the PEGASUS_MAXIMUM_ZERO_OBJECTCOUNT environment variable.
541
542 5. Default operationTimeout -
543
544 The default of this parameter is to refuse operat
545
546 In the current release of Pegasus these are all compile time parameters.
|
547 karl 1.1.2.11
548
549 NOTES On working with task branch.
550
551 Merge out Process
552
553 To keep our TASK branch in sync with the current head of tree we need
554 to do a regular merge out. the TaskMakefile contains the makefile
555 procedures to do this efficiently. NOTE: Following these procedures is
556 important in that you are merging out new material each time you do
557 the merge out. If you were just to repeatedly merge out, you would be
558 merging previously merged changes a second time causing a real mess.
559
560 Start with new directory and put TaskMakefile above pegasus (needed so you
561 have this file for the initial operations.
562
563 make -f TaskMakefile branch_merge_out BNAME=PEP317-pullop ## takes a long time
564
565 This checks out current head, merges it into task branch and sets tags
566 for the mergeout. Note that at the end of this step this work is
567 part of the TASK... branch.
568 karl 1.1.2.11
569 NOW check for conflicts, errors, etc. that resulted from the merge.
570 Look for conflict flags, compare the results (I use linux merge as a
571 good graphic compare tool) and build and test. When you are satisfied
572 that the merge out is clean, you can commit the results to the TASK...
573 branch
574
575 To commit the work to this into Task branch
576
577 make -f mak/TaskMakefile branch_merge_out_commit BNAME=PEP317-pullop
578
579 or manually commit and finish as follows
580
581 cvs commit
582 make -f mak/TaskMakefile branch_merge_out_finish BNAME=PEP317-pullop
583
584 ## This last step is important since it cleans up temporary tags to prepare
585 you for the next checkout
586
587 COMPARE TASKBRANCH WITH HEAD
588
589 karl 1.1.2.11 In a new pegasus work space do same as above for merge out.
590
591 make -f TaskMakefile BNAME=PEP317-pullop
592
593 This produces a result which is all of the head merged into the branch.
594 A diff of this is all the new changes to the head of tree that you will
595 include into the merge.
596
|
Return to
readme.pulloperations
CVS log
Up to [Pegasus] / pegasus