Orchestration

apiVersion: soultec.ch/v1kind: Servicemetadata: name: orchestration-automation locale: en labels: group: infrastructure capability/automation: 1.78 capability/devops: 3.42 capability/cloud: 1.94 vendor/vmware: 0.88 vendor/morpheus: 3.67 vendor/microsoft: 2.53 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 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. - heading:

What to watch

body: | Automation encodes the processes you have. Where no rule exists it makes the absence visible. That is the uncomfortable part of a rollout and also the most useful: the decisions belong to the operating model, not to the tool.status: corpus: 267 solutions: - {ref: solutions/morpheus, score: 1.00} - {ref: solutions/vmware/vmware-cloud-foundation, score: 0.61} - {ref: solutions/vmware/vmware-cloud-foundation/vcf-automation, score: 0.61} - {ref: solutions/vmware, score: 0.54} alsoLike: - {ref: posts/my-solution-to-share-powershell-scripts, score: 0.81} - {ref: posts/morpheus-cloud-management-plattform, score: 0.66} - {ref: experts/louis-kern, score: 0.63} experts: - {ref: experts/louis-kern, score: 0.63} - {ref: experts/tobias-waelti, score: 0.63} - {ref: experts/christian-schnyder, score: 0.48}

{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "orchestration-automation", "locale": "en", "labels": { "group": "infrastructure", "capability/automation": "1.78", "capability/devops": "3.42", "capability/cloud": "1.94", "vendor/vmware": "0.88", "vendor/morpheus": "3.67", "vendor/microsoft": "2.53" }, "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", "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." }, { "heading": "

What to watch

", "body": "Automation encodes the processes you have. Where no rule exists it makes the absence\nvisible. That is the uncomfortable part of a rollout and also the most useful: the\ndecisions belong to the operating model, not to the tool." } ], "status": { "corpus": 267, "solutions": [ { "ref": "solutions/morpheus", "score": "1.00" }, { "ref": "solutions/vmware/vmware-cloud-foundation", "score": "0.61" }, { "ref": "solutions/vmware/vmware-cloud-foundation/vcf-automation", "score": "0.61" }, { "ref": "solutions/vmware", "score": "0.54" } ], "alsoLike": [ { "ref": "posts/my-solution-to-share-powershell-scripts", "score": "0.81" }, { "ref": "posts/morpheus-cloud-management-plattform", "score": "0.66" }, { "ref": "experts/louis-kern", "score": "0.63" } ], "experts": [ { "ref": "experts/louis-kern", "score": "0.63" }, { "ref": "experts/tobias-waelti", "score": "0.63" }, { "ref": "experts/christian-schnyder", "score": "0.48" } ] }}

apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "orchestration-automation"locale = "en"[metadata.labels]group = "infrastructure""capability/automation" = "1.78""capability/devops" = "3.42""capability/cloud" = "1.94""vendor/vmware" = "0.88""vendor/morpheus" = "3.67""vendor/microsoft" = "2.53"[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"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[[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.'''[[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.'''[[sections]]heading = "

What to watch

"body = '''Automation encodes the processes you have. Where no rule exists it makes the absencevisible. That is the uncomfortable part of a rollout and also the most useful: thedecisions belong to the operating model, not to the tool.'''[status]corpus = 267[[status.solutions]]ref = "solutions/morpheus"score = "1.00"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation"score = "0.61"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation/vcf-automation"score = "0.61"[[status.solutions]]ref = "solutions/vmware"score = "0.54"[[status.alsoLike]]ref = "posts/my-solution-to-share-powershell-scripts"score = "0.81"[[status.alsoLike]]ref = "posts/morpheus-cloud-management-plattform"score = "0.66"[[status.alsoLike]]ref = "experts/louis-kern"score = "0.63"[[status.experts]]ref = "experts/louis-kern"score = "0.63"[[status.experts]]ref = "experts/tobias-waelti"score = "0.63"[[status.experts]]ref = "experts/christian-schnyder"score = "0.48"

<?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.78</entry> <entry key="capability/devops">3.42</entry> <entry key="capability/cloud">1.94</entry> <entry key="vendor/vmware">0.88</entry> <entry key="vendor/morpheus">3.67</entry> <entry key="vendor/microsoft">2.53</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> <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> </spec> <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. </body> </section> <section> <heading>

What to watch

</heading> <body>Automation encodes the processes you have. Where no rule exists it makes the absencevisible. That is the uncomfortable part of a rollout and also the most useful: thedecisions belong to the operating model, not to the tool. </body> </section> </sections> <status> <corpus>267</corpus> <solutions> <item> <ref>solutions/morpheus</ref> <score>1.00</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation</ref> <score>0.61</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/vcf-automation</ref> <score>0.61</score> </item> <item> <ref>solutions/vmware</ref> <score>0.54</score> </item> </solutions> <alsoLike> <item> <ref>posts/my-solution-to-share-powershell-scripts</ref> <score>0.81</score> </item> <item> <ref>posts/morpheus-cloud-management-plattform</ref> <score>0.66</score> </item> <item> <ref>experts/louis-kern</ref> <score>0.63</score> </item> </alsoLike> <experts> <item> <ref>experts/louis-kern</ref> <score>0.63</score> </item> <item> <ref>experts/tobias-waelti</ref> <score>0.63</score> </item> <item> <ref>experts/christian-schnyder</ref> <score>0.48</score> </item> </experts> </status></manifest>

The common assumption, and why it is wrong

What it covers

What to watch

The common assumption, and why it is wrong

What it covers

What to watch

The common assumption, and why it is wrong

What it covers

What to watch

The common assumption, and why it is wrong

What it covers

What to watch

The common assumption, and why it is wrong

What it covers

What to watch

Experts for this

Louis Kern

Tobias Wälti

Christian Schnyder

You might also like

share powershell scripts on-site

Morpheus Cloud Management Platform

Louis Kern