DE · EN

Call us

build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | built 2026-10-21 12:35 UTC format run

$ soultec get service/orchestration-automation -o yaml$ soultec get service/orchestration-automation -o json$ soultec get service/orchestration-automation -o toml$ soultec get service/orchestration-automation -o xml$ python3 orchestration-automation.pyPS> ./orchestration-automation.ps1$ go run orchestration-automation.go$ node orchestration-automation.js

apiVersion: soultec.ch/v1kind: Servicemetadata: name: orchestration-automation locale: en labels: group: infrastructure capability/automation: 1.81 capability/devops: 3.16 capability/cloud: 1.92 vendor/vmware: 0.98 vendor/morpheus: 3.48 vendor/microsoft: 2.61 annotations: source: src/content/services/en/orchestration-automation.md route: /en/services/orchestration-automation/ schema: /nerd/schema/services.json markdown: /en/services/orchestration-automation.mdspec: title: Orchestration group: infrastructure audience: [enterprise, provider] order: 8 tags: [automation, devops, cloud] vendors: [vmware, morpheus, microsoft] summary: >- Automation is not only worth it for what runs often. The rare procedure is the error-prone one, because nobody has it in their head any more. photoNeed: >- Infrastructure work in progress at a customer site or in our lab: hands on hardware, a rack door open, a screen mid-configuration stub: false draft: false sections: - heading:

The common assumption, and why it is wrong

body: | Many organisations only automate a process once it runs constantly. We see it differently, for a concrete reason. A procedure that happens twice a year is the most error-prone one there is. It needs knowledge nobody has to hand, it gets looked up again every time, and it gets done differently every time. That is where automation returns most: not in time saved, but in repeatability. - heading:

What it covers

body: | Provisioning virtual machines and containers, the processes around operating them, and connections to the usual public clouds: Azure, AWS, Google Cloud, IBM Cloud. That gives one place to manage what otherwise lives in several consoles, keeps cost in view, and turns the question of where a workload runs most cheaply into something you can answer rather than estimate. On top of that comes the part users see: a self-service portal where common and uncommon requests sit as catalogue items. Whoever needs something fills in a form instead of writing a ticket for somebody else to work through by hand. Approvals can be tied to parameters: what stays under a limit is provisioned directly, what exceeds it goes for approval. - heading:

What we build it with

body: | With products that have earned their place in this field: - **Morpheus Data** as a multi-tenant, multi-cloud management platform - **Microsoft MECM** - **VCF Automation** - **Ansible** and Ansible Tower Morpheus ships with more than 80 native integrations. Where those fall short, we go through the APIs that modern software offers anyway. We are happy to show this in a live demo in our lab and work through the use cases you actually have. - heading:

What to watch

body: | Automation encodes the processes you have. Where no rule exists, that shows up during the rollout and the rule has to be written first. Those decisions belong in the operating model and get taken there.status: corpus: 315 solutions: - {ref: solutions/hpe/hpe-morpheus, score: 0.89} - {ref: solutions/vmware/vmware-cloud-foundation/vcf-automation, score: 0.88} - {ref: solutions/vmware/vmware-cloud-foundation, score: 0.61} - {ref: solutions/vmware, score: 0.55} alsoLike: - {ref: posts/my-solution-to-share-powershell-scripts, score: 0.80} - {ref: experts/tobias-waelti, score: 0.75} - {ref: posts/morpheus-cloud-management-plattform, score: 0.68} experts: - {ref: experts/tobias-waelti, score: 0.75} - {ref: experts/louis-kern, score: 0.62} - {ref: experts/mike-schmid, score: 0.39} search: /en/search.json

{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "orchestration-automation", "locale": "en", "labels": { "group": "infrastructure", "capability/automation": 1.81, "capability/devops": 3.16, "capability/cloud": 1.92, "vendor/vmware": 0.98, "vendor/morpheus": 3.48, "vendor/microsoft": 2.61 }, "annotations": { "source": "src/content/services/en/orchestration-automation.md", "route": "/en/services/orchestration-automation/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/orchestration-automation.md" } }, "spec": { "title": "Orchestration", "group": "infrastructure", "audience": [ "enterprise", "provider" ], "order": 8, "tags": [ "automation", "devops", "cloud" ], "vendors": [ "vmware", "morpheus", "microsoft" ], "summary": "Automation is not only worth it for what runs often. The rare procedure is the error-prone one, because nobody has it in their head any more.", "photoNeed": "Infrastructure work in progress at a customer site or in our lab: hands on hardware, a rack door open, a screen mid-configuration", "stub": false, "draft": false, "sections": [ { "heading": "

The common assumption, and why it is wrong

", "body": "Many organisations only automate a process once it runs constantly. We see it differently,\nfor a concrete reason.\n\nA procedure that happens twice a year is the most error-prone one there is. It needs\nknowledge nobody has to hand, it gets looked up again every time, and it gets done\ndifferently every time. That is where automation returns most: not in time saved, but in\nrepeatability." }, { "heading": "

What it covers

", "body": "Provisioning virtual machines and containers, the processes around operating them, and\nconnections to the usual public clouds: Azure, AWS, Google Cloud, IBM Cloud.\n\nThat gives one place to manage what otherwise lives in several consoles, keeps cost in\nview, and turns the question of where a workload runs most cheaply into something you can\nanswer rather than estimate.\n\nOn top of that comes the part users see: a self-service portal where common and uncommon\nrequests sit as catalogue items. Whoever needs something fills in a form instead of\nwriting a ticket for somebody else to work through by hand.\n\nApprovals can be tied to parameters: what stays under a limit is provisioned directly, what\nexceeds it goes for approval." }, { "heading": "

What we build it with

", "body": "With products that have earned their place in this field:\n\n- **Morpheus Data** as a multi-tenant, multi-cloud management platform\n- **Microsoft MECM**\n- **VCF Automation**\n- **Ansible** and Ansible Tower\n\nMorpheus ships with more than 80 native integrations. Where those fall short, we go through\nthe APIs that modern software offers anyway.\n\nWe are happy to show this in a live demo in our lab and work through the use cases you\nactually have." }, { "heading": "

What to watch

", "body": "Automation encodes the processes you have. Where no rule exists, that shows up during the\nrollout and the rule has to be written first. Those decisions belong in the operating model\nand get taken there." } ] }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/hpe/hpe-morpheus", "score": "0.89" }, { "ref": "solutions/vmware/vmware-cloud-foundation/vcf-automation", "score": "0.88" }, { "ref": "solutions/vmware/vmware-cloud-foundation", "score": "0.61" }, { "ref": "solutions/vmware", "score": "0.55" } ], "alsoLike": [ { "ref": "posts/my-solution-to-share-powershell-scripts", "score": "0.80" }, { "ref": "experts/tobias-waelti", "score": "0.75" }, { "ref": "posts/morpheus-cloud-management-plattform", "score": "0.68" } ], "experts": [ { "ref": "experts/tobias-waelti", "score": "0.75" }, { "ref": "experts/louis-kern", "score": "0.62" }, { "ref": "experts/mike-schmid", "score": "0.39" } ], "search": "/en/search.json" }}

apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "orchestration-automation"locale = "en"[metadata.labels]group = "infrastructure""capability/automation" = 1.81"capability/devops" = 3.16"capability/cloud" = 1.92"vendor/vmware" = 0.98"vendor/morpheus" = 3.48"vendor/microsoft" = 2.61[metadata.annotations]source = "src/content/services/en/orchestration-automation.md"route = "/en/services/orchestration-automation/"schema = "/nerd/schema/services.json"markdown = "/en/services/orchestration-automation.md"[spec]title = "Orchestration"group = "infrastructure"audience = ["enterprise", "provider"]order = 8tags = ["automation", "devops", "cloud"]vendors = ["vmware", "morpheus", "microsoft"]summary = "Automation is not only worth it for what runs often. The rare procedure is the error-prone one, because nobody has it in their head any more."photoNeed = "Infrastructure work in progress at a customer site or in our lab: hands on hardware, a rack door open, a screen mid-configuration"stub = falsedraft = false[[spec.sections]]heading = "

The common assumption, and why it is wrong

"body = '''Many organisations only automate a process once it runs constantly. We see it differently,for a concrete reason.A procedure that happens twice a year is the most error-prone one there is. It needsknowledge nobody has to hand, it gets looked up again every time, and it gets donedifferently every time. That is where automation returns most: not in time saved, but inrepeatability.'''[[spec.sections]]heading = "

What it covers

"body = '''Provisioning virtual machines and containers, the processes around operating them, andconnections to the usual public clouds: Azure, AWS, Google Cloud, IBM Cloud.That gives one place to manage what otherwise lives in several consoles, keeps cost inview, and turns the question of where a workload runs most cheaply into something you cananswer rather than estimate.On top of that comes the part users see: a self-service portal where common and uncommonrequests sit as catalogue items. Whoever needs something fills in a form instead ofwriting a ticket for somebody else to work through by hand.Approvals can be tied to parameters: what stays under a limit is provisioned directly, whatexceeds it goes for approval.'''[[spec.sections]]heading = "

What we build it with

"body = '''With products that have earned their place in this field:- **Morpheus Data** as a multi-tenant, multi-cloud management platform- **Microsoft MECM**- **VCF Automation**- **Ansible** and Ansible TowerMorpheus ships with more than 80 native integrations. Where those fall short, we go throughthe APIs that modern software offers anyway.We are happy to show this in a live demo in our lab and work through the use cases youactually have.'''[[spec.sections]]heading = "

What to watch

"body = '''Automation encodes the processes you have. Where no rule exists, that shows up during therollout and the rule has to be written first. Those decisions belong in the operating modeland get taken there.'''[status]corpus = 315search = "/en/search.json"[[status.solutions]]ref = "solutions/hpe/hpe-morpheus"score = "0.89"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation/vcf-automation"score = "0.88"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation"score = "0.61"[[status.solutions]]ref = "solutions/vmware"score = "0.55"[[status.alsoLike]]ref = "posts/my-solution-to-share-powershell-scripts"score = "0.80"[[status.alsoLike]]ref = "experts/tobias-waelti"score = "0.75"[[status.alsoLike]]ref = "posts/morpheus-cloud-management-plattform"score = "0.68"[[status.experts]]ref = "experts/tobias-waelti"score = "0.75"[[status.experts]]ref = "experts/louis-kern"score = "0.62"[[status.experts]]ref = "experts/mike-schmid"score = "0.39"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Service"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>orchestration-automation</name> <locale>en</locale> <labels> <group>infrastructure</group> <entry key="capability/automation">1.81</entry> <entry key="capability/devops">3.16</entry> <entry key="capability/cloud">1.92</entry> <entry key="vendor/vmware">0.98</entry> <entry key="vendor/morpheus">3.48</entry> <entry key="vendor/microsoft">2.61</entry> </labels> <annotations> <source>src/content/services/en/orchestration-automation.md</source> <route>/en/services/orchestration-automation/</route> <schema>/nerd/schema/services.json</schema> <markdown>/en/services/orchestration-automation.md</markdown> </annotations> </metadata> <spec> <title>Orchestration</title> <group>infrastructure</group> <audience> <item>enterprise</item> <item>provider</item> </audience> <order>8</order> <tags> <item>automation</item> <item>devops</item> <item>cloud</item> </tags> <vendors> <item>vmware</item> <item>morpheus</item> <item>microsoft</item> </vendors> <summary>Automation is not only worth it for what runs often. The rare procedure is the error-prone one, because nobody has it in their head any more.</summary> <photoNeed>Infrastructure work in progress at a customer site or in our lab: hands on hardware, a rack door open, a screen mid-configuration</photoNeed> <stub>false</stub> <draft>false</draft> <sections> <section> <heading>

The common assumption, and why it is wrong

</heading> <body>Many organisations only automate a process once it runs constantly. We see it differently,for a concrete reason.A procedure that happens twice a year is the most error-prone one there is. It needsknowledge nobody has to hand, it gets looked up again every time, and it gets donedifferently every time. That is where automation returns most: not in time saved, but inrepeatability. </body> </section> <section> <heading>

What it covers

</heading> <body>Provisioning virtual machines and containers, the processes around operating them, andconnections to the usual public clouds: Azure, AWS, Google Cloud, IBM Cloud.That gives one place to manage what otherwise lives in several consoles, keeps cost inview, and turns the question of where a workload runs most cheaply into something you cananswer rather than estimate.On top of that comes the part users see: a self-service portal where common and uncommonrequests sit as catalogue items. Whoever needs something fills in a form instead ofwriting a ticket for somebody else to work through by hand.Approvals can be tied to parameters: what stays under a limit is provisioned directly, whatexceeds it goes for approval. </body> </section> <section> <heading>

What we build it with

</heading> <body>With products that have earned their place in this field:- **Morpheus Data** as a multi-tenant, multi-cloud management platform- **Microsoft MECM**- **VCF Automation**- **Ansible** and Ansible TowerMorpheus ships with more than 80 native integrations. Where those fall short, we go throughthe APIs that modern software offers anyway.We are happy to show this in a live demo in our lab and work through the use cases youactually have. </body> </section> <section> <heading>

What to watch

</heading> <body>Automation encodes the processes you have. Where no rule exists, that shows up during therollout and the rule has to be written first. Those decisions belong in the operating modeland get taken there. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <solutions> <item> <ref>solutions/hpe/hpe-morpheus</ref> <score>0.89</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/vcf-automation</ref> <score>0.88</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation</ref> <score>0.61</score> </item> <item> <ref>solutions/vmware</ref> <score>0.55</score> </item> </solutions> <alsoLike> <item> <ref>posts/my-solution-to-share-powershell-scripts</ref> <score>0.80</score> </item> <item> <ref>experts/tobias-waelti</ref> <score>0.75</score> </item> <item> <ref>posts/morpheus-cloud-management-plattform</ref> <score>0.68</score> </item> </alsoLike> <experts> <item> <ref>experts/tobias-waelti</ref> <score>0.75</score> </item> <item> <ref>experts/louis-kern</ref> <score>0.62</score> </item> <item> <ref>experts/mike-schmid</ref> <score>0.39</score> </item> </experts> <search>/en/search.json</search> </status></manifest>

# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "orchestration-automation", "locale": "en", "labels": { "group": "infrastructure", "capability/automation": 1.81, "capability/devops": 3.16, "capability/cloud": 1.92, "vendor/vmware": 0.98, "vendor/morpheus": 3.48, "vendor/microsoft": 2.61, }, "annotations": { "source": "src/content/services/en/orchestration-automation.md", "route": "/en/services/orchestration-automation/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/orchestration-automation.md", }, }, "spec": { "title": "Orchestration", "group": "infrastructure", "audience": ["enterprise", "provider"], "order": 8, "tags": ["automation", "devops", "cloud"], "vendors": ["vmware", "morpheus", "microsoft"], "summary": "Automation is not only worth it for what runs often. The rare procedure is the error-prone one, because nobody has it in their head any more.", "photoNeed": "Infrastructure work in progress at a customer site or in our lab: hands on hardware, a rack door open, a screen mid-configuration", "stub": False, "draft": False, "sections": [ { "heading": "

The common assumption, and why it is wrong

", "body": ( "Many organisations only automate a process once it runs constantly. We see it differently,\n" "for a concrete reason.\n" "\n" "A procedure that happens twice a year is the most error-prone one there is. It needs\n" "knowledge nobody has to hand, it gets looked up again every time, and it gets done\n" "differently every time. That is where automation returns most: not in time saved, but in\n" "repeatability." ), }, { "heading": "

What it covers

", "body": ( "Provisioning virtual machines and containers, the processes around operating them, and\n" "connections to the usual public clouds: Azure, AWS, Google Cloud, IBM Cloud.\n" "\n" "That gives one place to manage what otherwise lives in several consoles, keeps cost in\n" "view, and turns the question of where a workload runs most cheaply into something you can\n" "answer rather than estimate.\n" "\n" "On top of that comes the part users see: a self-service portal where common and uncommon\n" "requests sit as catalogue items. Whoever needs something fills in a form instead of\n" "writing a ticket for somebody else to work through by hand.\n" "\n" "Approvals can be tied to parameters: what stays under a limit is provisioned directly, what\n" "exceeds it goes for approval." ), }, { "heading": "

What we build it with

", "body": ( "With products that have earned their place in this field:\n" "\n" "- **Morpheus Data** as a multi-tenant, multi-cloud management platform\n" "- **Microsoft MECM**\n" "- **VCF Automation**\n" "- **Ansible** and Ansible Tower\n" "\n" "Morpheus ships with more than 80 native integrations. Where those fall short, we go through\n" "the APIs that modern software offers anyway.\n" "\n" "We are happy to show this in a live demo in our lab and work through the use cases you\n" "actually have." ), }, { "heading": "

What to watch

", "body": ( "Automation encodes the processes you have. Where no rule exists, that shows up during the\n" "rollout and the rule has to be written first. Those decisions belong in the operating model\n" "and get taken there." ), }, ], }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/hpe/hpe-morpheus", "score": "0.89", }, { "ref": "solutions/vmware/vmware-cloud-foundation/vcf-automation", "score": "0.88", }, { "ref": "solutions/vmware/vmware-cloud-foundation", "score": "0.61", }, { "ref": "solutions/vmware", "score": "0.55", }, ], "alsoLike": [ { "ref": "posts/my-solution-to-share-powershell-scripts", "score": "0.80", }, { "ref": "experts/tobias-waelti", "score": "0.75", }, { "ref": "posts/morpheus-cloud-management-plattform", "score": "0.68", }, ], "experts": [ { "ref": "experts/tobias-waelti", "score": "0.75", }, { "ref": "experts/louis-kern", "score": "0.62", }, { "ref": "experts/mike-schmid", "score": "0.39", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))

# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Service' metadata = [ordered]@{ name = 'orchestration-automation' locale = 'en' labels = [ordered]@{ group = 'infrastructure' 'capability/automation' = 1.81 'capability/devops' = 3.16 'capability/cloud' = 1.92 'vendor/vmware' = 0.98 'vendor/morpheus' = 3.48 'vendor/microsoft' = 2.61 } annotations = [ordered]@{ source = 'src/content/services/en/orchestration-automation.md' route = '/en/services/orchestration-automation/' schema = '/nerd/schema/services.json' markdown = '/en/services/orchestration-automation.md' } } spec = [ordered]@{ title = 'Orchestration' group = 'infrastructure' audience = @('enterprise', 'provider') order = 8 tags = @('automation', 'devops', 'cloud') vendors = @('vmware', 'morpheus', 'microsoft') summary = 'Automation is not only worth it for what runs often. The rare procedure is the error-prone one, because nobody has it in their head any more.' photoNeed = 'Infrastructure work in progress at a customer site or in our lab: hands on hardware, a rack door open, a screen mid-configuration' stub = $false draft = $false sections = @( [ordered]@{ heading = '

The common assumption, and why it is wrong

' body = @'Many organisations only automate a process once it runs constantly. We see it differently,for a concrete reason.A procedure that happens twice a year is the most error-prone one there is. It needsknowledge nobody has to hand, it gets looked up again every time, and it gets donedifferently every time. That is where automation returns most: not in time saved, but inrepeatability.'@ } [ordered]@{ heading = '

What it covers

' body = @'Provisioning virtual machines and containers, the processes around operating them, andconnections to the usual public clouds: Azure, AWS, Google Cloud, IBM Cloud.That gives one place to manage what otherwise lives in several consoles, keeps cost inview, and turns the question of where a workload runs most cheaply into something you cananswer rather than estimate.On top of that comes the part users see: a self-service portal where common and uncommonrequests sit as catalogue items. Whoever needs something fills in a form instead ofwriting a ticket for somebody else to work through by hand.Approvals can be tied to parameters: what stays under a limit is provisioned directly, whatexceeds it goes for approval.'@ } [ordered]@{ heading = '

What we build it with

' body = @'With products that have earned their place in this field:- **Morpheus Data** as a multi-tenant, multi-cloud management platform- **Microsoft MECM**- **VCF Automation**- **Ansible** and Ansible TowerMorpheus ships with more than 80 native integrations. Where those fall short, we go throughthe APIs that modern software offers anyway.We are happy to show this in a live demo in our lab and work through the use cases youactually have.'@ } [ordered]@{ heading = '

What to watch

' body = @'Automation encodes the processes you have. Where no rule exists, that shows up during therollout and the rule has to be written first. Those decisions belong in the operating modeland get taken there.'@ } ) } status = [ordered]@{ corpus = 315 solutions = @( [ordered]@{ ref = 'solutions/hpe/hpe-morpheus' score = '0.89' } [ordered]@{ ref = 'solutions/vmware/vmware-cloud-foundation/vcf-automation' score = '0.88' } [ordered]@{ ref = 'solutions/vmware/vmware-cloud-foundation' score = '0.61' } [ordered]@{ ref = 'solutions/vmware' score = '0.55' } ) alsoLike = @( [ordered]@{ ref = 'posts/my-solution-to-share-powershell-scripts' score = '0.80' } [ordered]@{ ref = 'experts/tobias-waelti' score = '0.75' } [ordered]@{ ref = 'posts/morpheus-cloud-management-plattform' score = '0.68' } ) experts = @( [ordered]@{ ref = 'experts/tobias-waelti' score = '0.75' } [ordered]@{ ref = 'experts/louis-kern' score = '0.62' } [ordered]@{ ref = 'experts/mike-schmid' score = '0.39' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32

// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": map[string]any{ "name": "orchestration-automation", "locale": "en", "labels": map[string]any{ "group": "infrastructure", "capability/automation": 1.81, "capability/devops": 3.16, "capability/cloud": 1.92, "vendor/vmware": 0.98, "vendor/morpheus": 3.48, "vendor/microsoft": 2.61, }, "annotations": map[string]any{ "source": "src/content/services/en/orchestration-automation.md", "route": "/en/services/orchestration-automation/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/orchestration-automation.md", }, }, "spec": map[string]any{ "title": "Orchestration", "group": "infrastructure", "audience": []any{"enterprise", "provider"}, "order": 8, "tags": []any{"automation", "devops", "cloud"}, "vendors": []any{"vmware", "morpheus", "microsoft"}, "summary": "Automation is not only worth it for what runs often. The rare procedure is the error-prone one, because nobody has it in their head any more.", "photoNeed": "Infrastructure work in progress at a customer site or in our lab: hands on hardware, a rack door open, a screen mid-configuration", "stub": false, "draft": false, "sections": []any{ map[string]any{ "heading": "

The common assumption, and why it is wrong

", "body": "Many organisations only automate a process once it runs constantly. We see it differently,\n" + "for a concrete reason.\n" + "\n" + "A procedure that happens twice a year is the most error-prone one there is. It needs\n" + "knowledge nobody has to hand, it gets looked up again every time, and it gets done\n" + "differently every time. That is where automation returns most: not in time saved, but in\n" + "repeatability.", }, map[string]any{ "heading": "

What it covers

", "body": "Provisioning virtual machines and containers, the processes around operating them, and\n" + "connections to the usual public clouds: Azure, AWS, Google Cloud, IBM Cloud.\n" + "\n" + "That gives one place to manage what otherwise lives in several consoles, keeps cost in\n" + "view, and turns the question of where a workload runs most cheaply into something you can\n" + "answer rather than estimate.\n" + "\n" + "On top of that comes the part users see: a self-service portal where common and uncommon\n" + "requests sit as catalogue items. Whoever needs something fills in a form instead of\n" + "writing a ticket for somebody else to work through by hand.\n" + "\n" + "Approvals can be tied to parameters: what stays under a limit is provisioned directly, what\n" + "exceeds it goes for approval.", }, map[string]any{ "heading": "

What we build it with

", "body": "With products that have earned their place in this field:\n" + "\n" + "- **Morpheus Data** as a multi-tenant, multi-cloud management platform\n" + "- **Microsoft MECM**\n" + "- **VCF Automation**\n" + "- **Ansible** and Ansible Tower\n" + "\n" + "Morpheus ships with more than 80 native integrations. Where those fall short, we go through\n" + "the APIs that modern software offers anyway.\n" + "\n" + "We are happy to show this in a live demo in our lab and work through the use cases you\n" + "actually have.", }, map[string]any{ "heading": "

What to watch

", "body": "Automation encodes the processes you have. Where no rule exists, that shows up during the\n" + "rollout and the rule has to be written first. Those decisions belong in the operating model\n" + "and get taken there.", }, }, }, "status": map[string]any{ "corpus": 315, "solutions": []any{ map[string]any{ "ref": "solutions/hpe/hpe-morpheus", "score": "0.89", }, map[string]any{ "ref": "solutions/vmware/vmware-cloud-foundation/vcf-automation", "score": "0.88", }, map[string]any{ "ref": "solutions/vmware/vmware-cloud-foundation", "score": "0.61", }, map[string]any{ "ref": "solutions/vmware", "score": "0.55", }, }, "alsoLike": []any{ map[string]any{ "ref": "posts/my-solution-to-share-powershell-scripts", "score": "0.80", }, map[string]any{ "ref": "experts/tobias-waelti", "score": "0.75", }, map[string]any{ "ref": "posts/morpheus-cloud-management-plattform", "score": "0.68", }, }, "experts": []any{ map[string]any{ "ref": "experts/tobias-waelti", "score": "0.75", }, map[string]any{ "ref": "experts/louis-kern", "score": "0.62", }, map[string]any{ "ref": "experts/mike-schmid", "score": "0.39", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}

// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Service", metadata: { name: "orchestration-automation", locale: "en", labels: { group: "infrastructure", "capability/automation": 1.81, "capability/devops": 3.16, "capability/cloud": 1.92, "vendor/vmware": 0.98, "vendor/morpheus": 3.48, "vendor/microsoft": 2.61, }, annotations: { source: "src/content/services/en/orchestration-automation.md", route: "/en/services/orchestration-automation/", schema: "/nerd/schema/services.json", markdown: "/en/services/orchestration-automation.md", }, }, spec: { title: "Orchestration", group: "infrastructure", audience: ["enterprise", "provider"], order: 8, tags: ["automation", "devops", "cloud"], vendors: ["vmware", "morpheus", "microsoft"], summary: "Automation is not only worth it for what runs often. The rare procedure is the error-prone one, because nobody has it in their head any more.", photoNeed: "Infrastructure work in progress at a customer site or in our lab: hands on hardware, a rack door open, a screen mid-configuration", stub: false, draft: false, sections: [ { heading: "

The common assumption, and why it is wrong

", body: "Many organisations only automate a process once it runs constantly. We see it differently,\n" + "for a concrete reason.\n" + "\n" + "A procedure that happens twice a year is the most error-prone one there is. It needs\n" + "knowledge nobody has to hand, it gets looked up again every time, and it gets done\n" + "differently every time. That is where automation returns most: not in time saved, but in\n" + "repeatability.", }, { heading: "

What it covers

", body: "Provisioning virtual machines and containers, the processes around operating them, and\n" + "connections to the usual public clouds: Azure, AWS, Google Cloud, IBM Cloud.\n" + "\n" + "That gives one place to manage what otherwise lives in several consoles, keeps cost in\n" + "view, and turns the question of where a workload runs most cheaply into something you can\n" + "answer rather than estimate.\n" + "\n" + "On top of that comes the part users see: a self-service portal where common and uncommon\n" + "requests sit as catalogue items. Whoever needs something fills in a form instead of\n" + "writing a ticket for somebody else to work through by hand.\n" + "\n" + "Approvals can be tied to parameters: what stays under a limit is provisioned directly, what\n" + "exceeds it goes for approval.", }, { heading: "

What we build it with

", body: "With products that have earned their place in this field:\n" + "\n" + "- **Morpheus Data** as a multi-tenant, multi-cloud management platform\n" + "- **Microsoft MECM**\n" + "- **VCF Automation**\n" + "- **Ansible** and Ansible Tower\n" + "\n" + "Morpheus ships with more than 80 native integrations. Where those fall short, we go through\n" + "the APIs that modern software offers anyway.\n" + "\n" + "We are happy to show this in a live demo in our lab and work through the use cases you\n" + "actually have.", }, { heading: "

What to watch

", body: "Automation encodes the processes you have. Where no rule exists, that shows up during the\n" + "rollout and the rule has to be written first. Those decisions belong in the operating model\n" + "and get taken there.", }, ], }, status: { corpus: 315, solutions: [ { ref: "solutions/hpe/hpe-morpheus", score: "0.89", }, { ref: "solutions/vmware/vmware-cloud-foundation/vcf-automation", score: "0.88", }, { ref: "solutions/vmware/vmware-cloud-foundation", score: "0.61", }, { ref: "solutions/vmware", score: "0.55", }, ], alsoLike: [ { ref: "posts/my-solution-to-share-powershell-scripts", score: "0.80", }, { ref: "experts/tobias-waelti", score: "0.75", }, { ref: "posts/morpheus-cloud-management-plattform", score: "0.68", }, ], experts: [ { ref: "experts/tobias-waelti", score: "0.75", }, { ref: "experts/louis-kern", score: "0.62", }, { ref: "experts/mike-schmid", score: "0.39", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 93 lines · YAML · validated at build# 114 lines · JSON · validated at build# 132 lines · TOML · validated at build# 153 lines · XML · validated at build# 148 lines · Python · read back at build, equals the JSON record# 145 lines · PowerShell · read back at build, equals the JSON record# 152 lines · Go · read back at build, equals the JSON record# 137 lines · JavaScript · read back at build, equals the JSON record · served at /en/services/orchestration-automation.md

Service · infrastructure

Orchestration

Automation is not only worth it for what runs often. The rare procedure is the error-prone one, because nobody has it in their head any more.

Topics Automation 1.81 DevOps 3.16 Cloud 1.92

Vendors VMware 0.98 Morpheus 3.48 Microsoft 2.61

04Solutions

03Capabilities

03Vendors

315Corpus

photograph wantedInfrastructure work in progress at a customer site or in our lab: hands on hardware, a rack door open, a screen mid-configuration

The common assumption, and why it is wrong

Many organisations only automate a process once it runs constantly. We see it differently, for a concrete reason.

A procedure that happens twice a year is the most error-prone one there is. It needs knowledge nobody has to hand, it gets looked up again every time, and it gets done differently every time. That is where automation returns most: not in time saved, but in repeatability.

What it covers

Provisioning virtual machines and containers, the processes around operating them, and connections to the usual public clouds: Azure, AWS, Google Cloud, IBM Cloud.

That gives one place to manage what otherwise lives in several consoles, keeps cost in view, and turns the question of where a workload runs most cheaply into something you can answer rather than estimate.

On top of that comes the part users see: a self-service portal where common and uncommon requests sit as catalogue items. Whoever needs something fills in a form instead of writing a ticket for somebody else to work through by hand.

Approvals can be tied to parameters: what stays under a limit is provisioned directly, what exceeds it goes for approval.

What we build it with

With products that have earned their place in this field:

Morpheus Data as a multi-tenant, multi-cloud management platform
Microsoft MECM
VCF Automation
Ansible and Ansible Tower

Morpheus ships with more than 80 native integrations. Where those fall short, we go through the APIs that modern software offers anyway.

We are happy to show this in a live demo in our lab and work through the use cases you actually have.

What to watch

Automation encodes the processes you have. Where no rule exists, that shows up during the rollout and the rule has to be written first. Those decisions belong in the operating model and get taken there.