oslc-automation message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: OSLC Automation "Integration Patterns" (applies in part to Systems Engineering & HIgh Availability work)
- From: Martin P Pain <martinpain@uk.ibm.com>
- To: oslc-automation@lists.oasis-open.org
- Date: Mon, 20 Oct 2014 11:34:48 +0100
I have started throwing together a list
of the ways that I am aware of in which systems can be integrated using
OSLC Automation: https://wiki.oasis-open.org/oslc-automation/IntegrationPatterns
On thinking about it, there seem to
be multiple "sequences" that the systems can follow (what high-level
actions are taken & in what order), and for each of them there are
different ways that the systems can connect ("topologies") to
achieve those actions.
I think it's important to document these
(non-standards track) to help implementors and people applying domain to
specific domains (e.g. Systems Engineering, High Availability) to
know their options, and the different patterns that other implementations
might be coding for.
Please have a quick read (I've listed
3 "sequences" and 4 "topologies" for one of those sequences
so far - I haven't gone into detail yet) and let me know if (1) what I'm
trying to communicate makes sense (2) what your implementations/thoughts
use and (3) if you have any suggestions for improved terminology.
I hope to discuss this at the meeting
tomorrow, along with other things on the agenda regarding the plan for
Automation 3.0: https://wiki.oasis-open.org/oslc-automation/Meetings/Telecon2014.10.21
Thanks,
Martin
OSLC Automation TC Chair
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]