liquidware-ninjaSecond brain & toolkit
Personal project. Research and learning only. Not for production. No warranty.Not for production
  • Built on my own time for research and learning. Not affiliated with, endorsed by or supported by my employer, Liquidware or Microsoft.
  • Bring your own Liquidware licenses. Don't run any of it in production or against tenants and subscriptions that matter. Test in a dedicated lab first.
  • Provided "as is", without warranty of any kind, under each repository's license. You use it at your own risk and own the Azure charges it incurs.
  • Contributions and forks are welcome and encouraged on public repos. See Contribute.

0003. This repo deploys the Liquidware platform; assessment and design live elsewhere

Context and Problem Statement

The Stratusphere tooling started inside a project that also designed AVD environments from what Stratusphere measured. Deploying the platform, running an assessment engagement, and designing a target environment change at different speeds and serve different people. Where does each belong?

Considered Options

  • This repo deploys and operates the Liquidware platform in Azure; assessment engagements and target-state design are separate projects that consume it
  • One repo for all three

Decision Outcome

Chosen option: "This repo deploys and operates the platform", because the deployment tooling is useful to anyone who runs Stratusphere in Azure, whatever they do with the data afterwards.

Consequences

  • Good, because this repo can be public and stay focused: appliances, the Connector ID Key, the API's behavior, Azure networking and Marketplace.
  • Good, because facts about Liquidware's products live here, and other projects link to them.
  • Neutral, because how an assessment is run or turned into a design isn't recorded here.
Linked from one page