Windows

OGC supports provisioning Windows instances, however, it does make a couple of assumptions:

• OpenSSH Server is running on the Windows Machine
• Rsync is installed and available
• Passwordless ssh is setup

Fortunately, we provide you with a Packer setup that will let you quickly build an AWS AMI to meet those requirements.

Warning

If using OGC contributed packer build, only AWS is supported at this time.

Build AMI

The configurations are located in contrib/, to get started run:

$ git clone https://github.com/adam-stokes/ogc
$ cd ogc/contrib

Alert

If using these Packer configs, please note the default user to use is: ogc

Windows 2019

To build a Windows 2019 Server instance run:

ogc/contrib> $ packer build windows2019.json

Once complete, grab the AMI ID, as this will be used in the layout specification of OGC.

Usage

To provision and deploy a Windows machine, the following example spec will work:

Create a file windows.py:

from ogc.deployer import init
from ogc.log import get_logger
from ogc.fs import expand_path

log = get_logger("ogc")

deployment = init(
    layout_model=dict(
        instance_size="c5.2xlarge",
        name="ubuntu-ogc",
        provider="aws",
        remote_path="ogc-src",
        runs_on="ami-0587bd602f1da2f1d",
        scale=1,
        scripts="fixtures/ex_deploy_windows",
        username="ogc",
        ssh_private_key=expand_path("~/.ssh/id_rsa_libcloud"),
        ssh_public_key=expand_path("~/.ssh/id_rsa_libcloud.pub"),
        ports=["22:22", "80:80", "443:443", "5601:5601"],
        tags=[],
        labels=dict(
            division="engineering", org="obs", team="observability", project="perf"
        ),
    ),
)

Once defined, simply running:

$ ogc windows up -v

Will get you a provisioned Windows machine!

Scripting

Powershell a good choice, works out of the box on Windows, however, if you want to use a different programming language the choice is yours. All the templating, database, and context is available.

For example, to print out the current node information, edit a file 01-powershell:

powershell echo "${node.instance_name}:${node.public_ip}" > ${node.instance_name}.txt

This is a simple example, for a more advanced deployment it may be best to create your ps1 files and then reference them through powershell interpreter.