version 1.1, 2007/05/30 22:24:21
|
version 1.2, 2007/06/01 16:58:05
|
|
|
it is checked into the pegasus supported directories as a starting | it is checked into the pegasus supported directories as a starting |
point. | point. |
| |
There is a PEP covering this implementation. |
PEP 285 defines the basics of this implemenation. |
|
|
|
Generally this code implements the required functionality of ws-man as |
|
defined by the DMTF specifications DSP0226, DSP0227, and DSP0228. |
|
|
|
It implements all of the required operations. However, it does not |
|
implement the fragment operations. |
|
|
|
Some of the Server limitations today include: |
|
|
|
1. Provides no support for indications. |
|
2. Does not allow use of SSL on connections. |
|
3. Single threaded. |
|
4. Some limitations in the implementation such as limit to one object on |
|
each pull response simple because that was easier for the demonstation. |
|
5. Includes a number of tests but does not do rigid response testing for the |
|
operation responses. |
|
6. Operates as a standalone server and uses the Pegasus client apis to |
|
communicate with the Pegasus server. Note that this code does not have a |
|
daemon mode. |
|
|
|
This work includes two types of client code: |
|
|
|
1. test clients for the ws-man operations (ex. wsmget, wsmenumerate, ...) |
|
2. An extension to the Pegasus Client so that the Pegasus client APIs can be |
|
used to communicate with a ws-management server. This set of functionality |
|
is addressed in a separate PEP ( PEP 298 ). |
| |
30 may 2007 | 30 may 2007 |
| |