GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Using Spreadsheets

Using Spreadsheets

Jump to bottom
Joe Kaiser edited this page Jan 25, 2018 · 5 revisions

Using Spreadsheets

We use spreadsheets - CSV spreadsheets to be specific.

You're laughing it up fuzzball.

Let's imagine an almost universal, easy to understand, easy to use, relatively compact, explicitly structured way to represent data about all the stuff we have and how it should be configured that even the marketing idiot in the cubicle on A2 could create or load if we trusted him that much. (We actually don't trust him, that's an example of hyperbole.) What comes to mind?

Yeah, CSV - that's why we use spreadsheets.

Stacki loads and unloads data in spreadsheets for hosts, networks, storage controllers, and storage partitions. It allows you to do all the preparation to automate the deployment of a data center.

And it's not YAML.

There are examples and details in:

  • Configure Additional Networks
  • Configure Partitioning
  • Configure Storage Controller
  • Adding Hosts

Using a spreadsheet for specifying host, network, controller, and disk configuration is considered a Stacki best practice. You might hate them (I don't, I like commas.) but loading spreadsheets:

  • Makes you explicitly define your configuration.
  • Validates the configuration.
  • Saves it in RCS (yeah, we're that old) so you can roll back or blame someone.
  • Syncs the database and the configuration, which saves time, steps, and potential human errors versus the command line.

Use a spreadsheet.

Checkout our Google Group or our Slack Team for any support or other questions.

Want to contribute to this Wiki? Fork it and send a pull request.

Stacki Documentation

  • Getting Started
  • Overview
  • Definitions
  • Stacki Cheat Sheet
  • Installation
    • Quickstart
    • Frontend Install - Basics
    • Frontend Install - New
    • Frontend Install - Existing
    • Frontend Install - Cluster Up
    • Backend Install - Basics
    • Backend Install - Discovery
    • Backend Install - Spreadsheet
    • Backend Reinstall
    • Amazon Web Services
    • Creating Jumbo Pallets
  • Upgrading
    • Upgrading Frontends
  • Customization
    • Carts
      • Adding Packages
      • Adding Files
      • Adding Install Scripts
    • Pallets
      • Adding OS Pallets
      • Adding Software Pallets
    • Boxes
    • Appliances
    • Stacki Universal XML
  • Configuration
    • Using Attributes
    • Using Spreadsheets
    • Network Configuration - Frontend
    • Network Configuration - Backends
    • Partioning Configuration
    • Storage Configuration
    • Switch Configuration
    • UEFI
    • Firmware Configuration
    • Firmware Configuration - Mellanox
    • Firmware Configuration - Dell
  • Interacting With Your Cluster
    • Command line
    • Stacki Web Service
  • FAQ/Shooting Your Foot
    • Order of Intallation
    • Carts vs Pallets
    • Using the %include Directive
    • Setting Cart Order
    • Use frontend for backend public access
    • Changing Private Network Deprecated
  • Developer
    • Core Development
    • Building From Source
    • Building For AWS
    • Adding new packages to Stacki
    • Test Framework
  • Reference
    • CLI Reference
    • Example CSV Files
  • Release Notes
    • Release Notes for 5.3
    • Release Notes for 5.2
    • Release Notes for 5.1
    • Release Notes for 5.0
    • Diffs from Stacki 4.0
  • Licenses
    • Overview Licenses
    • Rocks License
    • Stacki License

Clone this wiki locally

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.