Not all of these are required for hybrid/composite cloud, and detail on methods is left out, but as a list of composite cloud capabilities, what say you?
- more than one cloud
- cloud compatibility to allow the same workload to run on any node in he composite cloud without modification
- exposure of node metadata to allow programmatic decision making for auto placement of workloads into the composite
- workloads encapsulated as blueprints to reduce fragility
- one composite catalogue that contains items that can be deployed to composite cloud
- composite-aware network balancing and naming services
- one composite UI/API
- control, monitor and report multiple clouds as one hybrid/composite (ie. composite-aware OSS)
- a metering and billing capability to create a composite bill (ie. composite-aware BSS)
- an optional network path bridging between tenant resources on multiple clouds to create a composite cloud fabric
- recommended that migratory workloads fit a nimble profile, especially with regards to data to mitigate data gravity
- recommended embedding of network and security intelligence into mobile workload blueprint so security and governance travels with the workload
- reconsider centralised command/control view of hybrid into a distributed cloud view
- apply DRS-like method across clouds
- apply FAST-like method across clouds