build 7bbbddf7 | content blog-content@c8490fa · 338 posts | profiles 20 · corpus 267 | 0 skipped | | format
apiVersion: soultec.ch/v1kind: Solutionmetadata: name: hpe/hpe-greenlake locale: en labels: vendor: HPE GreenLake capability/cloud: 1.94 capability/storage: 2.62 capability/managed-services: 3.23 vendor/hpe: 2.04 annotations: source: src/content/solutions/en/hpe/hpe-greenlake.md route: /en/solutions/hpe/hpe-greenlake/ schema: /nerd/schema/solutions.json markdown: /en/solutions/hpe/hpe-greenlake.mdspec: title: GreenLake tags: [cloud, storage, managed-services] vendors: [hpe] summary: >- Hardware in your own datacentre, billed by what you use. The cloud model without the move to the cloud. photoNeed: >- HPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable stub: false draft: false kind: product addon: false vendorName: HPE GreenLake status: current practice: >- Draft, not yet reviewed. We rarely see GreenLake win on cost. It wins on predictability, because growth stops meaning a procurement project. The contract is the demanding part, and the committed minimum is the number that hurts three years later. practiceReview: true sections: - heading:

What it is

body: | GreenLake puts HPE infrastructure in your datacentre and bills it by consumption. A buffer of capacity sits installed and ready, you pay for what you actually use, and the meter reads monthly. - heading:

What it is for

body: | Data that has to stay in the building for legal or operational reasons, where demand cannot honestly be forecast three years out. The benefit is in the procurement model, not the technology. The hardware is the same hardware. - heading:

What to watch

body: | A consumption model moves capital expenditure into operating expenditure. It does not make it smaller. The arithmetic works when demand genuinely varies. Under a stable, predictable load, buying is often cheaper, and that calculation belongs before the signature.status: corpus: 267 services: - {ref: services/service-for-it-provider, score: 0.51} - {ref: services/backup, score: 0.48} - {ref: services/storage, score: 0.47} - {ref: services/service-desk, score: 0.44} posts: - {ref: posts/raid-controller, score: 0.54} - {ref: posts/how-to-storage-performance-test-mit-vdbench, score: 0.39} - {ref: posts/storage-performance-test-mit-iometer, score: 0.39} - {ref: posts/hci-mit-stormagic, score: 0.39} - {ref: posts/how-to-vsan-witness-9-0, score: 0.35} - {ref: posts/vmware-cloud-foundation-how-to-skip-vsan-hcl-checks-for-esxi-upgrades, score: 0.35} experts: - {ref: experts/matthias-frech, score: 0.50} - {ref: experts/mike-schmid, score: 0.45} - {ref: experts/valentina-cicmak, score: 0.44} neighbours: - {ref: solutions/hpe, score: 0.62} - {ref: solutions/hpe/hpe-dhci, score: 0.50} - {ref: solutions/hpe/hpe-data-management, score: 0.47}
{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "hpe/hpe-greenlake", "locale": "en", "labels": { "vendor": "HPE GreenLake", "capability/cloud": "1.94", "capability/storage": "2.62", "capability/managed-services": "3.23", "vendor/hpe": "2.04" }, "annotations": { "source": "src/content/solutions/en/hpe/hpe-greenlake.md", "route": "/en/solutions/hpe/hpe-greenlake/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/hpe/hpe-greenlake.md" } }, "spec": { "title": "GreenLake", "tags": [ "cloud", "storage", "managed-services" ], "vendors": [ "hpe" ], "summary": "Hardware in your own datacentre, billed by what you use. The cloud model without the move to the cloud.", "photoNeed": "HPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable", "stub": false, "draft": false, "kind": "product", "addon": false, "vendorName": "HPE GreenLake", "status": "current", "practice": "Draft, not yet reviewed. We rarely see GreenLake win on cost. It wins on predictability, because growth stops meaning a procurement project. The contract is the demanding part, and the committed minimum is the number that hurts three years later.\n", "practiceReview": true }, "sections": [ { "heading": "

What it is

",
"body": "GreenLake puts HPE infrastructure in your datacentre and bills it by consumption. A\nbuffer of capacity sits installed and ready, you pay for what you actually use, and the\nmeter reads monthly." }, { "heading": "

What it is for

",
"body": "Data that has to stay in the building for legal or operational reasons, where demand\ncannot honestly be forecast three years out.\n\nThe benefit is in the procurement model, not the technology. The hardware is the same\nhardware." }, { "heading": "

What to watch

",
"body": "A consumption model moves capital expenditure into operating expenditure. It does not\nmake it smaller. The arithmetic works when demand genuinely varies. Under a stable,\npredictable load, buying is often cheaper, and that calculation belongs before the\nsignature." } ], "status": { "corpus": 267, "services": [ { "ref": "services/service-for-it-provider", "score": "0.51" }, { "ref": "services/backup", "score": "0.48" }, { "ref": "services/storage", "score": "0.47" }, { "ref": "services/service-desk", "score": "0.44" } ], "posts": [ { "ref": "posts/raid-controller", "score": "0.54" }, { "ref": "posts/how-to-storage-performance-test-mit-vdbench", "score": "0.39" }, { "ref": "posts/storage-performance-test-mit-iometer", "score": "0.39" }, { "ref": "posts/hci-mit-stormagic", "score": "0.39" }, { "ref": "posts/how-to-vsan-witness-9-0", "score": "0.35" }, { "ref": "posts/vmware-cloud-foundation-how-to-skip-vsan-hcl-checks-for-esxi-upgrades", "score": "0.35" } ], "experts": [ { "ref": "experts/matthias-frech", "score": "0.50" }, { "ref": "experts/mike-schmid", "score": "0.45" }, { "ref": "experts/valentina-cicmak", "score": "0.44" } ], "neighbours": [ { "ref": "solutions/hpe", "score": "0.62" }, { "ref": "solutions/hpe/hpe-dhci", "score": "0.50" }, { "ref": "solutions/hpe/hpe-data-management", "score": "0.47" } ] }}
apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "hpe/hpe-greenlake"locale = "en"[metadata.labels]vendor = "HPE GreenLake""capability/cloud" = "1.94""capability/storage" = "2.62""capability/managed-services" = "3.23""vendor/hpe" = "2.04"[metadata.annotations]source = "src/content/solutions/en/hpe/hpe-greenlake.md"route = "/en/solutions/hpe/hpe-greenlake/"schema = "/nerd/schema/solutions.json"markdown = "/en/solutions/hpe/hpe-greenlake.md"[spec]title = "GreenLake"tags = ["cloud", "storage", "managed-services"]vendors = ["hpe"]summary = "Hardware in your own datacentre, billed by what you use. The cloud model without the move to the cloud."photoNeed = "HPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable"stub = falsedraft = falsekind = "product"addon = falsevendorName = "HPE GreenLake"status = "current"practice = '''Draft, not yet reviewed. We rarely see GreenLake win on cost. It wins on predictability, because growth stops meaning a procurement project. The contract is the demanding part, and the committed minimum is the number that hurts three years later.'''practiceReview = true[[sections]]heading = "

What it is

"
body = '''GreenLake puts HPE infrastructure in your datacentre and bills it by consumption. Abuffer of capacity sits installed and ready, you pay for what you actually use, and themeter reads monthly.'''[[sections]]heading = "

What it is for

"
body = '''Data that has to stay in the building for legal or operational reasons, where demandcannot honestly be forecast three years out.The benefit is in the procurement model, not the technology. The hardware is the samehardware.'''[[sections]]heading = "

What to watch

"
body = '''A consumption model moves capital expenditure into operating expenditure. It does notmake it smaller. The arithmetic works when demand genuinely varies. Under a stable,predictable load, buying is often cheaper, and that calculation belongs before thesignature.'''[status]corpus = 267[[status.services]]ref = "services/service-for-it-provider"score = "0.51"[[status.services]]ref = "services/backup"score = "0.48"[[status.services]]ref = "services/storage"score = "0.47"[[status.services]]ref = "services/service-desk"score = "0.44"[[status.posts]]ref = "posts/raid-controller"score = "0.54"[[status.posts]]ref = "posts/how-to-storage-performance-test-mit-vdbench"score = "0.39"[[status.posts]]ref = "posts/storage-performance-test-mit-iometer"score = "0.39"[[status.posts]]ref = "posts/hci-mit-stormagic"score = "0.39"[[status.posts]]ref = "posts/how-to-vsan-witness-9-0"score = "0.35"[[status.posts]]ref = "posts/vmware-cloud-foundation-how-to-skip-vsan-hcl-checks-for-esxi-upgrades"score = "0.35"[[status.experts]]ref = "experts/matthias-frech"score = "0.50"[[status.experts]]ref = "experts/mike-schmid"score = "0.45"[[status.experts]]ref = "experts/valentina-cicmak"score = "0.44"[[status.neighbours]]ref = "solutions/hpe"score = "0.62"[[status.neighbours]]ref = "solutions/hpe/hpe-dhci"score = "0.50"[[status.neighbours]]ref = "solutions/hpe/hpe-data-management"score = "0.47"
<?xml version="1.0" encoding="UTF-8"?><manifest kind="Solution"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>hpe/hpe-greenlake</name> <locale>en</locale> <labels> <vendor>HPE GreenLake</vendor> <entry key="capability/cloud">1.94</entry> <entry key="capability/storage">2.62</entry> <entry key="capability/managed-services">3.23</entry> <entry key="vendor/hpe">2.04</entry> </labels> <annotations> <source>src/content/solutions/en/hpe/hpe-greenlake.md</source> <route>/en/solutions/hpe/hpe-greenlake/</route> <schema>/nerd/schema/solutions.json</schema> <markdown>/en/solutions/hpe/hpe-greenlake.md</markdown> </annotations> </metadata> <spec> <title>GreenLake</title> <tags> <item>cloud</item> <item>storage</item> <item>managed-services</item> </tags> <vendors> <item>hpe</item> </vendors> <summary>Hardware in your own datacentre, billed by what you use. The cloud model without the move to the cloud.</summary> <photoNeed>HPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable</photoNeed> <stub>false</stub> <draft>false</draft> <kind>product</kind> <addon>false</addon> <vendorName>HPE GreenLake</vendorName> <status>current</status> <practice>Draft, not yet reviewed. We rarely see GreenLake win on cost. It wins on predictability, because growth stops meaning a procurement project. The contract is the demanding part, and the committed minimum is the number that hurts three years later. </practice> <practiceReview>true</practiceReview> </spec> <sections> <section> <heading>

What it is

</heading>
<body>GreenLake puts HPE infrastructure in your datacentre and bills it by consumption. Abuffer of capacity sits installed and ready, you pay for what you actually use, and themeter reads monthly. </body> </section> <section> <heading>

What it is for

</heading>
<body>Data that has to stay in the building for legal or operational reasons, where demandcannot honestly be forecast three years out.The benefit is in the procurement model, not the technology. The hardware is the samehardware. </body> </section> <section> <heading>

What to watch

</heading>
<body>A consumption model moves capital expenditure into operating expenditure. It does notmake it smaller. The arithmetic works when demand genuinely varies. Under a stable,predictable load, buying is often cheaper, and that calculation belongs before thesignature. </body> </section> </sections> <status> <corpus>267</corpus> <services> <item> <ref>services/service-for-it-provider</ref> <score>0.51</score> </item> <item> <ref>services/backup</ref> <score>0.48</score> </item> <item> <ref>services/storage</ref> <score>0.47</score> </item> <item> <ref>services/service-desk</ref> <score>0.44</score> </item> </services> <posts> <item> <ref>posts/raid-controller</ref> <score>0.54</score> </item> <item> <ref>posts/how-to-storage-performance-test-mit-vdbench</ref> <score>0.39</score> </item> <item> <ref>posts/storage-performance-test-mit-iometer</ref> <score>0.39</score> </item> <item> <ref>posts/hci-mit-stormagic</ref> <score>0.39</score> </item> <item> <ref>posts/how-to-vsan-witness-9-0</ref> <score>0.35</score> </item> <item> <ref>posts/vmware-cloud-foundation-how-to-skip-vsan-hcl-checks-for-esxi-upgrades</ref> <score>0.35</score> </item> </posts> <experts> <item> <ref>experts/matthias-frech</ref> <score>0.50</score> </item> <item> <ref>experts/mike-schmid</ref> <score>0.45</score> </item> <item> <ref>experts/valentina-cicmak</ref> <score>0.44</score> </item> </experts> <neighbours> <item> <ref>solutions/hpe</ref> <score>0.62</score> </item> <item> <ref>solutions/hpe/hpe-dhci</ref> <score>0.50</score> </item> <item> <ref>solutions/hpe/hpe-data-management</ref> <score>0.47</score> </item> </neighbours> </status></manifest>
Solution · HPE

GreenLake

HPE GreenLake

The vendor calls it: HPE GreenLake

Hardware in your own datacentre, billed by what you use. The cloud model without the move to the cloud.

HPE Gold Partner

Topics Cloud 1.94 Storage 2.62 Managed Services 3.23
Vendors HPE 2.04
04Services
06Posts
03Capabilities
267Corpus

What it is

GreenLake puts HPE infrastructure in your datacentre and bills it by consumption. A buffer of capacity sits installed and ready, you pay for what you actually use, and the meter reads monthly.

What it is for

Data that has to stay in the building for legal or operational reasons, where demand cannot honestly be forecast three years out.

The benefit is in the procurement model, not the technology. The hardware is the same hardware.

What to watch

A consumption model moves capital expenditure into operating expenditure. It does not make it smaller. The arithmetic works when demand genuinely varies. Under a stable, predictable load, buying is often cheaper, and that calculation belongs before the signature.

What we do with it

Draft, unreviewed

Draft, not yet reviewed. We rarely see GreenLake win on cost. It wins on predictability, because growth stops meaning a procurement project. The contract is the demanding part, and the committed minimum is the number that hurts three years later.

This paragraph is a draft and nobody at soulTec has confirmed it yet. Everything above it describes the product and is checkable against the vendor.

Posts about it

Who works with it

Do you work with this? Take a look at our open roles.