Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restructure config/settings/{stage}.yml data #33

Open
dazza-codes opened this issue Sep 4, 2017 · 0 comments
Open

Restructure config/settings/{stage}.yml data #33

dazza-codes opened this issue Sep 4, 2017 · 0 comments

Comments

@dazza-codes
Copy link
Owner

dazza-codes commented Sep 4, 2017

Allow the services to be an array of services, so that one compute resource (node, network, security group, etc.) can host multiple services. This can allow co-hosting services, like zookeeper and mesos-master services running on the same node.

Consider alternative settings structure (don't use aws as the root key?), e.g.

zookeeper:
  config:
    {general config settings}

kafka:
  {general kafka settings}

spark:
  {general spark settings}

mesos:
  {general mesos settings}

nodes:
  - node_name:
    - {node settings}
    - services:
      - zookeeper
      - mesos-master

network:
  - security_group_name:
    - {security group settings}
      - services:
        - zookeeper
        - mesos-master

Use the keys to find the general settings for each service. The top level key should be the service name. Use the services attribute on compute resources to identify what services to manage (install/configure) for that compute resource (nodes).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant