"EMI-1 Release Elements"

The majority of plans are part of the technical work plan of the security area available at the project-wide deliverable page.

Nevertheless, some news have been also collected with respect to the development and test plan :

"UNICORE Security PT"

I assume that to include something in this release, its development must be finished to the end of this year.

> * The list of development/feature additions/general updating of
> components.
> - The estimated timeline for these works.

There is one concrete feature addition which should be included in release 1: Argus callout for UNICORE/X. Timeline - M8. UNICORE/X is maintained by other PT (UNICORE Service hosting) but this development is changing "XACML Entity" which is maintained by my PT.

There will be a lot of open developments but (looking at workplan) none of them shall be fully finished and therefore included in the release.

> * Planned interactions with other components. Both within and outside of
> the security area.
>
> - The interfaces (standard or other) that will be used.
> - Will the interface need to be changed?
I assume you mean "new, not yet existing interactions".

So obviously interaction between UNICORE/X whose XACML entity (as it is named in the project) will be able to contact Argus. The current Argus interface shall be used, hopefully without changes. But this is theoretical statement now - part of work is to verify this.

-- MorrisRiedel - 15-Oct-2010

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2010-10-15 - MorrisRiedelExCern
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback