build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | format run

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

apiVersion: soultec.ch/v1kind: Servicemetadata: name: datacenter-lifecycle locale: en labels: group: consulting capability/architecture: 2.51 capability/migration: 2.82 capability/monitoring: 2.44 vendor/hpe: 1.99 vendor/vmware: 0.98 vendor/lenovo: 4.66 annotations: source: src/content/services/en/datacenter-lifecycle.md route: /en/services/datacenter-lifecycle/ schema: /nerd/schema/services.json markdown: /en/services/datacenter-lifecycle.mdspec: title: Datacenter Lifecycle group: consulting audience: [enterprise, provider] order: 8 tags: [architecture, migration, monitoring] vendors: [hpe, vmware, lenovo] summary: >- Check the state of the infrastructure once or twice a year, validate it against best practice, and implement the recommendations if you want. photoNeed: >- A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table stub: false draft: false sections: - heading:

What the service does

body: | We check the state of your infrastructure and validate it against best practice, including analysis of installed software and firmware levels with update recommendations. The output is a status report with the current state and the recommendations that follow from it. - heading:

Why it recurs

body: | Because a one-off check only says how things stood on one day. The lifecycle service is the proactive part of our operations services and has two pieces. **LifeCycle Service:** once a year an update of the infrastructure, software, firmware and drivers, with a compatibility check beforehand. Plus once a year the installation of a critical patch for VMware, Veeam, HPE, Lenovo, IBM or Scality. **SmartCheck Service:** a monthly check of the systems with a capacity and utilisation check, and we keep the task list with the recommendations. Once a year a technology update on what is new in the products in use. A technical account manager coordinates technical requests around changes and incidents and helps open support tickets with the vendors. It starts with an onboarding: exchange and documentation of contacts, system documentation, IP addresses, passwords and remote access. If we did not build the infrastructure, a health check is part of the onboarding. - heading:

What the service covers

body: | The same six categories as the health check: storage systems, SAN, backup, servers, server virtualization and client virtualization, with the product list that sits there. For the analysis itself we use InfoSight on the HPE side. It evaluates product usage data automatically and checks it against known problems, weaknesses and security gaps. On the VMware by Broadcom side we use VCF Checker, the Health Analyzer and Invar, which the Health Check page describes. For systems at the end of their lifecycle you get an offer for their replacement, matched to the state the analysis showed. - heading:

How this differs from Health Check

body: | The Health Check ends with the report. With the lifecycle service the annual update and the monthly check are part of it: our engineers make sure that the findings which would sit in a health check report actually get worked off. Not all of it can be done by an external engineer. Some tasks depend on access, on approvals or on decisions that have to be taken inside your organisation, and we name those as such. What is in our hands, we take on. That difference sounds small and is the decisive one in practice: reports nobody works through accumulate, and the estate degrades anyway.status: corpus: 315 solutions: - {ref: solutions/hpe/hpe-server, score: 0.49} - {ref: solutions/hpe/hpe-server/hpe-synergy, score: 0.49} - {ref: solutions/vmware/vmware-cloud-foundation/addon/business-operations, score: 0.48} - {ref: solutions/hpe/hpe-zerto, score: 0.47} alsoLike: - {ref: services/health-check, score: 0.75} - {ref: services/engineering, score: 0.71} - {ref: posts/broadcom-support-portal, score: 0.55} experts: - {ref: experts/dario-doerflinger, score: 0.49} - {ref: experts/matthias-grasmueck, score: 0.40} - {ref: experts/marco-mattei, score: 0.37} search: /en/search.json
{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "datacenter-lifecycle", "locale": "en", "labels": { "group": "consulting", "capability/architecture": 2.51, "capability/migration": 2.82, "capability/monitoring": 2.44, "vendor/hpe": 1.99, "vendor/vmware": 0.98, "vendor/lenovo": 4.66 }, "annotations": { "source": "src/content/services/en/datacenter-lifecycle.md", "route": "/en/services/datacenter-lifecycle/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/datacenter-lifecycle.md" } }, "spec": { "title": "Datacenter Lifecycle", "group": "consulting", "audience": [ "enterprise", "provider" ], "order": 8, "tags": [ "architecture", "migration", "monitoring" ], "vendors": [ "hpe", "vmware", "lenovo" ], "summary": "Check the state of the infrastructure once or twice a year, validate it against best practice, and implement the recommendations if you want.", "photoNeed": "A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table", "stub": false, "draft": false, "sections": [ { "heading": "

What the service does

",
"body": "We check the state of your infrastructure and validate it against best practice, including\nanalysis of installed software and firmware levels with update recommendations. The output\nis a status report with the current state and the recommendations that follow from it." }, { "heading": "

Why it recurs

",
"body": "Because a one-off check only says how things stood on one day. The lifecycle service is the\nproactive part of our operations services and has two pieces.\n\n**LifeCycle Service:** once a year an update of the infrastructure, software, firmware and\ndrivers, with a compatibility check beforehand. Plus once a year the installation of a\ncritical patch for VMware, Veeam, HPE, Lenovo, IBM or Scality.\n\n**SmartCheck Service:** a monthly check of the systems with a capacity and utilisation\ncheck, and we keep the task list with the recommendations. Once a year a technology update\non what is new in the products in use. A technical account manager coordinates technical\nrequests around changes and incidents and helps open support tickets with the vendors.\n\nIt starts with an onboarding: exchange and documentation of contacts, system documentation,\nIP addresses, passwords and remote access. If we did not build the infrastructure, a health\ncheck is part of the onboarding." }, { "heading": "

What the service covers

",
"body": "The same six categories as the health check: storage systems, SAN, backup, servers, server\nvirtualization and client virtualization, with the product list that sits there.\n\nFor the analysis itself we use InfoSight on the HPE side. It evaluates product usage data\nautomatically and checks it against known problems, weaknesses and security gaps. On the\nVMware by Broadcom side we use VCF Checker, the Health Analyzer and Invar, which the Health\nCheck page describes.\n\nFor systems at the end of their lifecycle you get an offer for their replacement, matched to\nthe state the analysis showed." }, { "heading": "

How this differs from Health Check

",
"body": "The Health Check ends with the report. With the lifecycle service the annual update and the\nmonthly check are part of it: our engineers make sure that the findings which would sit in a\nhealth check report actually get worked off.\n\nNot all of it can be done by an external engineer. Some tasks depend on access, on approvals\nor on decisions that have to be taken inside your organisation, and we name those as such.\nWhat is in our hands, we take on.\n\nThat difference sounds small and is the decisive one in practice: reports nobody works\nthrough accumulate, and the estate degrades anyway." } ] }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/hpe/hpe-server", "score": "0.49" }, { "ref": "solutions/hpe/hpe-server/hpe-synergy", "score": "0.49" }, { "ref": "solutions/vmware/vmware-cloud-foundation/addon/business-operations", "score": "0.48" }, { "ref": "solutions/hpe/hpe-zerto", "score": "0.47" } ], "alsoLike": [ { "ref": "services/health-check", "score": "0.75" }, { "ref": "services/engineering", "score": "0.71" }, { "ref": "posts/broadcom-support-portal", "score": "0.55" } ], "experts": [ { "ref": "experts/dario-doerflinger", "score": "0.49" }, { "ref": "experts/matthias-grasmueck", "score": "0.40" }, { "ref": "experts/marco-mattei", "score": "0.37" } ], "search": "/en/search.json" }}
apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "datacenter-lifecycle"locale = "en"[metadata.labels]group = "consulting""capability/architecture" = 2.51"capability/migration" = 2.82"capability/monitoring" = 2.44"vendor/hpe" = 1.99"vendor/vmware" = 0.98"vendor/lenovo" = 4.66[metadata.annotations]source = "src/content/services/en/datacenter-lifecycle.md"route = "/en/services/datacenter-lifecycle/"schema = "/nerd/schema/services.json"markdown = "/en/services/datacenter-lifecycle.md"[spec]title = "Datacenter Lifecycle"group = "consulting"audience = ["enterprise", "provider"]order = 8tags = ["architecture", "migration", "monitoring"]vendors = ["hpe", "vmware", "lenovo"]summary = "Check the state of the infrastructure once or twice a year, validate it against best practice, and implement the recommendations if you want."photoNeed = "A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table"stub = falsedraft = false[[spec.sections]]heading = "

What the service does

"
body = '''We check the state of your infrastructure and validate it against best practice, includinganalysis of installed software and firmware levels with update recommendations. The outputis a status report with the current state and the recommendations that follow from it.'''[[spec.sections]]heading = "

Why it recurs

"
body = '''Because a one-off check only says how things stood on one day. The lifecycle service is theproactive part of our operations services and has two pieces.**LifeCycle Service:** once a year an update of the infrastructure, software, firmware anddrivers, with a compatibility check beforehand. Plus once a year the installation of acritical patch for VMware, Veeam, HPE, Lenovo, IBM or Scality.**SmartCheck Service:** a monthly check of the systems with a capacity and utilisationcheck, and we keep the task list with the recommendations. Once a year a technology updateon what is new in the products in use. A technical account manager coordinates technicalrequests around changes and incidents and helps open support tickets with the vendors.It starts with an onboarding: exchange and documentation of contacts, system documentation,IP addresses, passwords and remote access. If we did not build the infrastructure, a healthcheck is part of the onboarding.'''[[spec.sections]]heading = "

What the service covers

"
body = '''The same six categories as the health check: storage systems, SAN, backup, servers, servervirtualization and client virtualization, with the product list that sits there.For the analysis itself we use InfoSight on the HPE side. It evaluates product usage dataautomatically and checks it against known problems, weaknesses and security gaps. On theVMware by Broadcom side we use VCF Checker, the Health Analyzer and Invar, which the HealthCheck page describes.For systems at the end of their lifecycle you get an offer for their replacement, matched tothe state the analysis showed.'''[[spec.sections]]heading = "

How this differs from Health Check

"
body = '''The Health Check ends with the report. With the lifecycle service the annual update and themonthly check are part of it: our engineers make sure that the findings which would sit in ahealth check report actually get worked off.Not all of it can be done by an external engineer. Some tasks depend on access, on approvalsor on decisions that have to be taken inside your organisation, and we name those as such.What is in our hands, we take on.That difference sounds small and is the decisive one in practice: reports nobody worksthrough accumulate, and the estate degrades anyway.'''[status]corpus = 315search = "/en/search.json"[[status.solutions]]ref = "solutions/hpe/hpe-server"score = "0.49"[[status.solutions]]ref = "solutions/hpe/hpe-server/hpe-synergy"score = "0.49"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation/addon/business-operations"score = "0.48"[[status.solutions]]ref = "solutions/hpe/hpe-zerto"score = "0.47"[[status.alsoLike]]ref = "services/health-check"score = "0.75"[[status.alsoLike]]ref = "services/engineering"score = "0.71"[[status.alsoLike]]ref = "posts/broadcom-support-portal"score = "0.55"[[status.experts]]ref = "experts/dario-doerflinger"score = "0.49"[[status.experts]]ref = "experts/matthias-grasmueck"score = "0.40"[[status.experts]]ref = "experts/marco-mattei"score = "0.37"
<?xml version="1.0" encoding="UTF-8"?><manifest kind="Service"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>datacenter-lifecycle</name> <locale>en</locale> <labels> <group>consulting</group> <entry key="capability/architecture">2.51</entry> <entry key="capability/migration">2.82</entry> <entry key="capability/monitoring">2.44</entry> <entry key="vendor/hpe">1.99</entry> <entry key="vendor/vmware">0.98</entry> <entry key="vendor/lenovo">4.66</entry> </labels> <annotations> <source>src/content/services/en/datacenter-lifecycle.md</source> <route>/en/services/datacenter-lifecycle/</route> <schema>/nerd/schema/services.json</schema> <markdown>/en/services/datacenter-lifecycle.md</markdown> </annotations> </metadata> <spec> <title>Datacenter Lifecycle</title> <group>consulting</group> <audience> <item>enterprise</item> <item>provider</item> </audience> <order>8</order> <tags> <item>architecture</item> <item>migration</item> <item>monitoring</item> </tags> <vendors> <item>hpe</item> <item>vmware</item> <item>lenovo</item> </vendors> <summary>Check the state of the infrastructure once or twice a year, validate it against best practice, and implement the recommendations if you want.</summary> <photoNeed>A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table</photoNeed> <stub>false</stub> <draft>false</draft> <sections> <section> <heading>

What the service does

</heading>
<body>We check the state of your infrastructure and validate it against best practice, includinganalysis of installed software and firmware levels with update recommendations. The outputis a status report with the current state and the recommendations that follow from it. </body> </section> <section> <heading>

Why it recurs

</heading>
<body>Because a one-off check only says how things stood on one day. The lifecycle service is theproactive part of our operations services and has two pieces.**LifeCycle Service:** once a year an update of the infrastructure, software, firmware anddrivers, with a compatibility check beforehand. Plus once a year the installation of acritical patch for VMware, Veeam, HPE, Lenovo, IBM or Scality.**SmartCheck Service:** a monthly check of the systems with a capacity and utilisationcheck, and we keep the task list with the recommendations. Once a year a technology updateon what is new in the products in use. A technical account manager coordinates technicalrequests around changes and incidents and helps open support tickets with the vendors.It starts with an onboarding: exchange and documentation of contacts, system documentation,IP addresses, passwords and remote access. If we did not build the infrastructure, a healthcheck is part of the onboarding. </body> </section> <section> <heading>

What the service covers

</heading>
<body>The same six categories as the health check: storage systems, SAN, backup, servers, servervirtualization and client virtualization, with the product list that sits there.For the analysis itself we use InfoSight on the HPE side. It evaluates product usage dataautomatically and checks it against known problems, weaknesses and security gaps. On theVMware by Broadcom side we use VCF Checker, the Health Analyzer and Invar, which the HealthCheck page describes.For systems at the end of their lifecycle you get an offer for their replacement, matched tothe state the analysis showed. </body> </section> <section> <heading>

How this differs from Health Check

</heading>
<body>The Health Check ends with the report. With the lifecycle service the annual update and themonthly check are part of it: our engineers make sure that the findings which would sit in ahealth check report actually get worked off.Not all of it can be done by an external engineer. Some tasks depend on access, on approvalsor on decisions that have to be taken inside your organisation, and we name those as such.What is in our hands, we take on.That difference sounds small and is the decisive one in practice: reports nobody worksthrough accumulate, and the estate degrades anyway. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <solutions> <item> <ref>solutions/hpe/hpe-server</ref> <score>0.49</score> </item> <item> <ref>solutions/hpe/hpe-server/hpe-synergy</ref> <score>0.49</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/addon/business-operations</ref> <score>0.48</score> </item> <item> <ref>solutions/hpe/hpe-zerto</ref> <score>0.47</score> </item> </solutions> <alsoLike> <item> <ref>services/health-check</ref> <score>0.75</score> </item> <item> <ref>services/engineering</ref> <score>0.71</score> </item> <item> <ref>posts/broadcom-support-portal</ref> <score>0.55</score> </item> </alsoLike> <experts> <item> <ref>experts/dario-doerflinger</ref> <score>0.49</score> </item> <item> <ref>experts/matthias-grasmueck</ref> <score>0.40</score> </item> <item> <ref>experts/marco-mattei</ref> <score>0.37</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": "datacenter-lifecycle", "locale": "en", "labels": { "group": "consulting", "capability/architecture": 2.51, "capability/migration": 2.82, "capability/monitoring": 2.44, "vendor/hpe": 1.99, "vendor/vmware": 0.98, "vendor/lenovo": 4.66, }, "annotations": { "source": "src/content/services/en/datacenter-lifecycle.md", "route": "/en/services/datacenter-lifecycle/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/datacenter-lifecycle.md", }, }, "spec": { "title": "Datacenter Lifecycle", "group": "consulting", "audience": ["enterprise", "provider"], "order": 8, "tags": ["architecture", "migration", "monitoring"], "vendors": ["hpe", "vmware", "lenovo"], "summary": "Check the state of the infrastructure once or twice a year, validate it against best practice, and implement the recommendations if you want.", "photoNeed": "A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table", "stub": False, "draft": False, "sections": [ { "heading": "

What the service does

",
"body": ( "We check the state of your infrastructure and validate it against best practice, including\n" "analysis of installed software and firmware levels with update recommendations. The output\n" "is a status report with the current state and the recommendations that follow from it." ), }, { "heading": "

Why it recurs

",
"body": ( "Because a one-off check only says how things stood on one day. The lifecycle service is the\n" "proactive part of our operations services and has two pieces.\n" "\n" "**LifeCycle Service:** once a year an update of the infrastructure, software, firmware and\n" "drivers, with a compatibility check beforehand. Plus once a year the installation of a\n" "critical patch for VMware, Veeam, HPE, Lenovo, IBM or Scality.\n" "\n" "**SmartCheck Service:** a monthly check of the systems with a capacity and utilisation\n" "check, and we keep the task list with the recommendations. Once a year a technology update\n" "on what is new in the products in use. A technical account manager coordinates technical\n" "requests around changes and incidents and helps open support tickets with the vendors.\n" "\n" "It starts with an onboarding: exchange and documentation of contacts, system documentation,\n" "IP addresses, passwords and remote access. If we did not build the infrastructure, a health\n" "check is part of the onboarding." ), }, { "heading": "

What the service covers

",
"body": ( "The same six categories as the health check: storage systems, SAN, backup, servers, server\n" "virtualization and client virtualization, with the product list that sits there.\n" "\n" "For the analysis itself we use InfoSight on the HPE side. It evaluates product usage data\n" "automatically and checks it against known problems, weaknesses and security gaps. On the\n" "VMware by Broadcom side we use VCF Checker, the Health Analyzer and Invar, which the Health\n" "Check page describes.\n" "\n" "For systems at the end of their lifecycle you get an offer for their replacement, matched to\n" "the state the analysis showed." ), }, { "heading": "

How this differs from Health Check

",
"body": ( "The Health Check ends with the report. With the lifecycle service the annual update and the\n" "monthly check are part of it: our engineers make sure that the findings which would sit in a\n" "health check report actually get worked off.\n" "\n" "Not all of it can be done by an external engineer. Some tasks depend on access, on approvals\n" "or on decisions that have to be taken inside your organisation, and we name those as such.\n" "What is in our hands, we take on.\n" "\n" "That difference sounds small and is the decisive one in practice: reports nobody works\n" "through accumulate, and the estate degrades anyway." ), }, ], }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/hpe/hpe-server", "score": "0.49", }, { "ref": "solutions/hpe/hpe-server/hpe-synergy", "score": "0.49", }, { "ref": "solutions/vmware/vmware-cloud-foundation/addon/business-operations", "score": "0.48", }, { "ref": "solutions/hpe/hpe-zerto", "score": "0.47", }, ], "alsoLike": [ { "ref": "services/health-check", "score": "0.75", }, { "ref": "services/engineering", "score": "0.71", }, { "ref": "posts/broadcom-support-portal", "score": "0.55", }, ], "experts": [ { "ref": "experts/dario-doerflinger", "score": "0.49", }, { "ref": "experts/matthias-grasmueck", "score": "0.40", }, { "ref": "experts/marco-mattei", "score": "0.37", }, ], "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 = 'datacenter-lifecycle' locale = 'en' labels = [ordered]@{ group = 'consulting' 'capability/architecture' = 2.51 'capability/migration' = 2.82 'capability/monitoring' = 2.44 'vendor/hpe' = 1.99 'vendor/vmware' = 0.98 'vendor/lenovo' = 4.66 } annotations = [ordered]@{ source = 'src/content/services/en/datacenter-lifecycle.md' route = '/en/services/datacenter-lifecycle/' schema = '/nerd/schema/services.json' markdown = '/en/services/datacenter-lifecycle.md' } } spec = [ordered]@{ title = 'Datacenter Lifecycle' group = 'consulting' audience = @('enterprise', 'provider') order = 8 tags = @('architecture', 'migration', 'monitoring') vendors = @('hpe', 'vmware', 'lenovo') summary = 'Check the state of the infrastructure once or twice a year, validate it against best practice, and implement the recommendations if you want.' photoNeed = 'A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table' stub = $false draft = $false sections = @( [ordered]@{ heading = '

What the service does

'
body = @'We check the state of your infrastructure and validate it against best practice, includinganalysis of installed software and firmware levels with update recommendations. The outputis a status report with the current state and the recommendations that follow from it.'@ } [ordered]@{ heading = '

Why it recurs

'
body = @'Because a one-off check only says how things stood on one day. The lifecycle service is theproactive part of our operations services and has two pieces.**LifeCycle Service:** once a year an update of the infrastructure, software, firmware anddrivers, with a compatibility check beforehand. Plus once a year the installation of acritical patch for VMware, Veeam, HPE, Lenovo, IBM or Scality.**SmartCheck Service:** a monthly check of the systems with a capacity and utilisationcheck, and we keep the task list with the recommendations. Once a year a technology updateon what is new in the products in use. A technical account manager coordinates technicalrequests around changes and incidents and helps open support tickets with the vendors.It starts with an onboarding: exchange and documentation of contacts, system documentation,IP addresses, passwords and remote access. If we did not build the infrastructure, a healthcheck is part of the onboarding.'@ } [ordered]@{ heading = '

What the service covers

'
body = @'The same six categories as the health check: storage systems, SAN, backup, servers, servervirtualization and client virtualization, with the product list that sits there.For the analysis itself we use InfoSight on the HPE side. It evaluates product usage dataautomatically and checks it against known problems, weaknesses and security gaps. On theVMware by Broadcom side we use VCF Checker, the Health Analyzer and Invar, which the HealthCheck page describes.For systems at the end of their lifecycle you get an offer for their replacement, matched tothe state the analysis showed.'@ } [ordered]@{ heading = '

How this differs from Health Check

'
body = @'The Health Check ends with the report. With the lifecycle service the annual update and themonthly check are part of it: our engineers make sure that the findings which would sit in ahealth check report actually get worked off.Not all of it can be done by an external engineer. Some tasks depend on access, on approvalsor on decisions that have to be taken inside your organisation, and we name those as such.What is in our hands, we take on.That difference sounds small and is the decisive one in practice: reports nobody worksthrough accumulate, and the estate degrades anyway.'@ } ) } status = [ordered]@{ corpus = 315 solutions = @( [ordered]@{ ref = 'solutions/hpe/hpe-server' score = '0.49' } [ordered]@{ ref = 'solutions/hpe/hpe-server/hpe-synergy' score = '0.49' } [ordered]@{ ref = 'solutions/vmware/vmware-cloud-foundation/addon/business-operations' score = '0.48' } [ordered]@{ ref = 'solutions/hpe/hpe-zerto' score = '0.47' } ) alsoLike = @( [ordered]@{ ref = 'services/health-check' score = '0.75' } [ordered]@{ ref = 'services/engineering' score = '0.71' } [ordered]@{ ref = 'posts/broadcom-support-portal' score = '0.55' } ) experts = @( [ordered]@{ ref = 'experts/dario-doerflinger' score = '0.49' } [ordered]@{ ref = 'experts/matthias-grasmueck' score = '0.40' } [ordered]@{ ref = 'experts/marco-mattei' score = '0.37' } ) 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": "datacenter-lifecycle", "locale": "en", "labels": map[string]any{ "group": "consulting", "capability/architecture": 2.51, "capability/migration": 2.82, "capability/monitoring": 2.44, "vendor/hpe": 1.99, "vendor/vmware": 0.98, "vendor/lenovo": 4.66, }, "annotations": map[string]any{ "source": "src/content/services/en/datacenter-lifecycle.md", "route": "/en/services/datacenter-lifecycle/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/datacenter-lifecycle.md", }, }, "spec": map[string]any{ "title": "Datacenter Lifecycle", "group": "consulting", "audience": []any{"enterprise", "provider"}, "order": 8, "tags": []any{"architecture", "migration", "monitoring"}, "vendors": []any{"hpe", "vmware", "lenovo"}, "summary": "Check the state of the infrastructure once or twice a year, validate it against best practice, and implement the recommendations if you want.", "photoNeed": "A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table", "stub": false, "draft": false, "sections": []any{ map[string]any{ "heading": "

What the service does

",
"body": "We check the state of your infrastructure and validate it against best practice, including\n" + "analysis of installed software and firmware levels with update recommendations. The output\n" + "is a status report with the current state and the recommendations that follow from it.", }, map[string]any{ "heading": "

Why it recurs

",
"body": "Because a one-off check only says how things stood on one day. The lifecycle service is the\n" + "proactive part of our operations services and has two pieces.\n" + "\n" + "**LifeCycle Service:** once a year an update of the infrastructure, software, firmware and\n" + "drivers, with a compatibility check beforehand. Plus once a year the installation of a\n" + "critical patch for VMware, Veeam, HPE, Lenovo, IBM or Scality.\n" + "\n" + "**SmartCheck Service:** a monthly check of the systems with a capacity and utilisation\n" + "check, and we keep the task list with the recommendations. Once a year a technology update\n" + "on what is new in the products in use. A technical account manager coordinates technical\n" + "requests around changes and incidents and helps open support tickets with the vendors.\n" + "\n" + "It starts with an onboarding: exchange and documentation of contacts, system documentation,\n" + "IP addresses, passwords and remote access. If we did not build the infrastructure, a health\n" + "check is part of the onboarding.", }, map[string]any{ "heading": "

What the service covers

",
"body": "The same six categories as the health check: storage systems, SAN, backup, servers, server\n" + "virtualization and client virtualization, with the product list that sits there.\n" + "\n" + "For the analysis itself we use InfoSight on the HPE side. It evaluates product usage data\n" + "automatically and checks it against known problems, weaknesses and security gaps. On the\n" + "VMware by Broadcom side we use VCF Checker, the Health Analyzer and Invar, which the Health\n" + "Check page describes.\n" + "\n" + "For systems at the end of their lifecycle you get an offer for their replacement, matched to\n" + "the state the analysis showed.", }, map[string]any{ "heading": "

How this differs from Health Check

",
"body": "The Health Check ends with the report. With the lifecycle service the annual update and the\n" + "monthly check are part of it: our engineers make sure that the findings which would sit in a\n" + "health check report actually get worked off.\n" + "\n" + "Not all of it can be done by an external engineer. Some tasks depend on access, on approvals\n" + "or on decisions that have to be taken inside your organisation, and we name those as such.\n" + "What is in our hands, we take on.\n" + "\n" + "That difference sounds small and is the decisive one in practice: reports nobody works\n" + "through accumulate, and the estate degrades anyway.", }, }, }, "status": map[string]any{ "corpus": 315, "solutions": []any{ map[string]any{ "ref": "solutions/hpe/hpe-server", "score": "0.49", }, map[string]any{ "ref": "solutions/hpe/hpe-server/hpe-synergy", "score": "0.49", }, map[string]any{ "ref": "solutions/vmware/vmware-cloud-foundation/addon/business-operations", "score": "0.48", }, map[string]any{ "ref": "solutions/hpe/hpe-zerto", "score": "0.47", }, }, "alsoLike": []any{ map[string]any{ "ref": "services/health-check", "score": "0.75", }, map[string]any{ "ref": "services/engineering", "score": "0.71", }, map[string]any{ "ref": "posts/broadcom-support-portal", "score": "0.55", }, }, "experts": []any{ map[string]any{ "ref": "experts/dario-doerflinger", "score": "0.49", }, map[string]any{ "ref": "experts/matthias-grasmueck", "score": "0.40", }, map[string]any{ "ref": "experts/marco-mattei", "score": "0.37", }, }, "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: "datacenter-lifecycle", locale: "en", labels: { group: "consulting", "capability/architecture": 2.51, "capability/migration": 2.82, "capability/monitoring": 2.44, "vendor/hpe": 1.99, "vendor/vmware": 0.98, "vendor/lenovo": 4.66, }, annotations: { source: "src/content/services/en/datacenter-lifecycle.md", route: "/en/services/datacenter-lifecycle/", schema: "/nerd/schema/services.json", markdown: "/en/services/datacenter-lifecycle.md", }, }, spec: { title: "Datacenter Lifecycle", group: "consulting", audience: ["enterprise", "provider"], order: 8, tags: ["architecture", "migration", "monitoring"], vendors: ["hpe", "vmware", "lenovo"], summary: "Check the state of the infrastructure once or twice a year, validate it against best practice, and implement the recommendations if you want.", photoNeed: "A working session with a customer: a whiteboard with a real diagram, or two people over a laptop across a table", stub: false, draft: false, sections: [ { heading: "

What the service does

",
body: "We check the state of your infrastructure and validate it against best practice, including\n" + "analysis of installed software and firmware levels with update recommendations. The output\n" + "is a status report with the current state and the recommendations that follow from it.", }, { heading: "

Why it recurs

",
body: "Because a one-off check only says how things stood on one day. The lifecycle service is the\n" + "proactive part of our operations services and has two pieces.\n" + "\n" + "**LifeCycle Service:** once a year an update of the infrastructure, software, firmware and\n" + "drivers, with a compatibility check beforehand. Plus once a year the installation of a\n" + "critical patch for VMware, Veeam, HPE, Lenovo, IBM or Scality.\n" + "\n" + "**SmartCheck Service:** a monthly check of the systems with a capacity and utilisation\n" + "check, and we keep the task list with the recommendations. Once a year a technology update\n" + "on what is new in the products in use. A technical account manager coordinates technical\n" + "requests around changes and incidents and helps open support tickets with the vendors.\n" + "\n" + "It starts with an onboarding: exchange and documentation of contacts, system documentation,\n" + "IP addresses, passwords and remote access. If we did not build the infrastructure, a health\n" + "check is part of the onboarding.", }, { heading: "

What the service covers

",
body: "The same six categories as the health check: storage systems, SAN, backup, servers, server\n" + "virtualization and client virtualization, with the product list that sits there.\n" + "\n" + "For the analysis itself we use InfoSight on the HPE side. It evaluates product usage data\n" + "automatically and checks it against known problems, weaknesses and security gaps. On the\n" + "VMware by Broadcom side we use VCF Checker, the Health Analyzer and Invar, which the Health\n" + "Check page describes.\n" + "\n" + "For systems at the end of their lifecycle you get an offer for their replacement, matched to\n" + "the state the analysis showed.", }, { heading: "

How this differs from Health Check

",
body: "The Health Check ends with the report. With the lifecycle service the annual update and the\n" + "monthly check are part of it: our engineers make sure that the findings which would sit in a\n" + "health check report actually get worked off.\n" + "\n" + "Not all of it can be done by an external engineer. Some tasks depend on access, on approvals\n" + "or on decisions that have to be taken inside your organisation, and we name those as such.\n" + "What is in our hands, we take on.\n" + "\n" + "That difference sounds small and is the decisive one in practice: reports nobody works\n" + "through accumulate, and the estate degrades anyway.", }, ], }, status: { corpus: 315, solutions: [ { ref: "solutions/hpe/hpe-server", score: "0.49", }, { ref: "solutions/hpe/hpe-server/hpe-synergy", score: "0.49", }, { ref: "solutions/vmware/vmware-cloud-foundation/addon/business-operations", score: "0.48", }, { ref: "solutions/hpe/hpe-zerto", score: "0.47", }, ], alsoLike: [ { ref: "services/health-check", score: "0.75", }, { ref: "services/engineering", score: "0.71", }, { ref: "posts/broadcom-support-portal", score: "0.55", }, ], experts: [ { ref: "experts/dario-doerflinger", score: "0.49", }, { ref: "experts/matthias-grasmueck", score: "0.40", }, { ref: "experts/marco-mattei", score: "0.37", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 96 lines · YAML · validated at build# 114 lines · JSON · validated at build# 135 lines · TOML · validated at build# 156 lines · XML · validated at build# 151 lines · Python · read back at build, equals the JSON record# 148 lines · PowerShell · read back at build, equals the JSON record# 155 lines · Go · read back at build, equals the JSON record# 140 lines · JavaScript · read back at build, equals the JSON record · served at /en/services/datacenter-lifecycle.md

Service · consulting

Datacenter Lifecycle

Check the state of the infrastructure once or twice a year, validate it against best practice, and implement the recommendations if you want.

Vendors HPE 1.99 VMware 0.98 Lenovo 4.66
04Solutions
03Capabilities
03Vendors
315Corpus

What the service does

We check the state of your infrastructure and validate it against best practice, including analysis of installed software and firmware levels with update recommendations. The output is a status report with the current state and the recommendations that follow from it.

Why it recurs

Because a one-off check only says how things stood on one day. The lifecycle service is the proactive part of our operations services and has two pieces.

LifeCycle Service: once a year an update of the infrastructure, software, firmware and drivers, with a compatibility check beforehand. Plus once a year the installation of a critical patch for VMware, Veeam, HPE, Lenovo, IBM or Scality.

SmartCheck Service: a monthly check of the systems with a capacity and utilisation check, and we keep the task list with the recommendations. Once a year a technology update on what is new in the products in use. A technical account manager coordinates technical requests around changes and incidents and helps open support tickets with the vendors.

It starts with an onboarding: exchange and documentation of contacts, system documentation, IP addresses, passwords and remote access. If we did not build the infrastructure, a health check is part of the onboarding.

What the service covers

The same six categories as the health check: storage systems, SAN, backup, servers, server virtualization and client virtualization, with the product list that sits there.

For the analysis itself we use InfoSight on the HPE side. It evaluates product usage data automatically and checks it against known problems, weaknesses and security gaps. On the VMware by Broadcom side we use VCF Checker, the Health Analyzer and Invar, which the Health Check page describes.

For systems at the end of their lifecycle you get an offer for their replacement, matched to the state the analysis showed.

How this differs from Health Check

The Health Check ends with the report. With the lifecycle service the annual update and the monthly check are part of it: our engineers make sure that the findings which would sit in a health check report actually get worked off.

Not all of it can be done by an external engineer. Some tasks depend on access, on approvals or on decisions that have to be taken inside your organisation, and we name those as such. What is in our hands, we take on.

That difference sounds small and is the decisive one in practice: reports nobody works through accumulate, and the estate degrades anyway.

Experts for this

Maybe you? Take a look at our open roles.

You might also like