# Prototype: Cloud Builder Spreadsheet

**URL:** <https://forum.45homelab.com/t/prototype-cloud-builder-spreadsheet/689>\
**Category:** Hardware\
**Created:** [November 20, 2023, 3:13am UTC](https://forum.45homelab.com/t/prototype-cloud-builder-spreadsheet/689 "2023-11-20T03:13:01Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![pcuci](https://forum.45homelab.com/letter_avatar_proxy/v4/letter/p/b2d939/32.png) [@pcuci](https://forum.45homelab.com/u/pcuci)\
**Post date:** [November 28, 2023, 2:15pm UTC](https://forum.45homelab.com/t/prototype-cloud-builder-spreadsheet/689/7 "2023-11-28T14:15:13Z")

</div>

[500 lines of code later…]

> [@Glitch3dPenguin](#):
>
> My sheet are just fans

Hi @Glitch3dPenguin - I remixed your fans list into: [Cloud Builder - Google Sheets](https://docs.google.com/spreadsheets/d/1eLyMbh0iuax6rOilh444H7ivbZ1AmLGtAqWhrUZA-yA/edit#gid=1131537313) (just know that if you change your columns, it’ll break my imports 🤪)

Just for fun, I’m using [your home lab](https://forum.45homelab.com/t/deployed-my-hl15/751) to test this compatibility-checker prototype spreadsheet; which still needs some work to move out of ‘alpha’ 😃

 ![image](https://forum.45homelab.com/uploads/default/original/1X/2d9e69eacbcacfe1225b0120ede8f00b54324008.png)

Your cluster turns out to be too big for my current prototype, and Google Spreadsheets Apps Scripts is too slow—I hit the 30 seconds processing time limit

![image](https://forum.45homelab.com/uploads/default/original/1X/fe3b9fb5bc10b1372465d9e004c322dbfc81b0db.png)

If anyone has ideas what I could optimize, and how, here’s the code (the interesting bits being): [Code.js · main · deposition.cloud / Infrastructure / Compute / Metal · GitLab](https://gitlab.com/deposition.cloud/infra/compute/metal/-/blob/main/Code.js?ref_type=heads#L258-294)

What’s happening is we inflate objects (could be a “Build” or a “Cluster”) with details from related subcomponent sheets (say, “Memory”, “CPU”, or “Motherboard”) if those exist, then we run these compatibility check functions to determine the drop down lists for each sub-component type, i.e.: only list compatible options given all other already selected sub-components.

Speaking of which…

What compatibility checks does everyone here do, that I should definitely not overlook?

Technically, I’m trying to de-risk purchasing incompatible components, whilst planning upgradable paths for this project: [HL15 for intensive compute + memory](https://forum.45homelab.com/t/hl15-for-intensive-compute-memory/228)

> [@SpringerSpaniel](#):
>
> I tend to put everything into [NetBox](https://netbox.dev/)

Great idea to feed the equipment, once purchased, into a DCIM!

---

_[View the full topic](https://forum.45homelab.com/t/prototype-cloud-builder-spreadsheet/689)._