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