[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [tosca] Follow up on the boundary definition section
Hi, I am new to TOSCA & OASIS itself, therefore please excuse me if I am saying something absurd here! Going though Luca’s mail, I was wondering if the boundary definition may(optionally) carry the following. Considering these may be critical for a service functioning. 1)
Security System ( SIEM, IDS, IPS, AV) 2)
Misc Network (GLB, CDN, Latency to a destination) 3)
License Keys (3rd party) 4)
DR (like a dual site/zone) 5)
Billing System integration 6)
Monitoring (CMDB, Event Monitor, Synthetic Transaction, BLA, ITSM entry) 7)
SLA (RPO/RTO, Operation Team, Tier, Dial home, VPN Tunnel) 8)
Compliance (ITAR, HIPPA etc) 9)
External Surround System (Version of a application/component) Cheers Saji
From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org]
On Behalf Of Luca Gioppo I really very much like the proposal of Chris. Usually is better to have a behaviour be esplicitly stated rather than leaving the default implementation of the "null".
If we think instead that specifying nothing "means" abstract that should be the clearly explained in the spec since at the moment is not so clear it could be "orchestrator if you find nothing use the default behaviour".
We should also have clear examples of when some null are legitimate and where no (there could be nodes where is not admitted to have no lifecycle: we need to feed the validator)
Luca > _________________________________________________________________________ > >
> |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]