Skip to content

Define different port ranges #37

@russellshackleford

Description

@russellshackleford

I'm using oscar-stack for multiple dev environments. If I run plain vagrant up, with the same roles/vms.yaml, I can rely on a consistent spinup order, which means I can rely on a consistent port mapping order and thus can set aliases and config in .ssh/config. This immediately breaks with more than one stack unless every stack is started up in the same order all the time. This hits a wall on system resources, however, if I have a lot of stacks, even if I can power down the unneeded ones after starting them all so that the last one has a predictable port. Obviously if I pass an incomplete list of hosts (or a list sorted differently than vms.yaml) this will also break, but something that allows a bare up to use ports X to Y would minimize the friction considerably.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions