Update vagrant nodepool provider #378
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a similar change to the allinone inventory i was just about to push up.... a couple comments
inventory/group_vars/vagrant
Outdated
@@ -27,12 +27,15 @@ nodepool_labels: | |||
nodepool_providers: | |||
- name: cicloud | |||
cloud: cicloud | |||
max-servers: 10 | |||
max-servers: 3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for developers, we should probably keep this to 1 by default just to ease resource usage on the cloud
inventory/group_vars/vagrant
Outdated
@@ -27,12 +27,15 @@ nodepool_labels: | |||
nodepool_providers: | |||
- name: cicloud | |||
cloud: cicloud | |||
max-servers: 10 | |||
max-servers: 3 | |||
images: | |||
- name: ubuntu-xenial | |||
min-ram: 2048 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can bump this down to 512 as well to conserve resources
inventory/group_vars/vagrant
Outdated
images: | ||
- name: ubuntu-xenial | ||
min-ram: 2048 | ||
diskimage: ubuntu-xenial | ||
private-key: /var/lib/nodepool/.ssh/id_rsa | ||
networks: | ||
- name: 'nodepool' | ||
public: False |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dont think we want to encourage devs to boot slaves on our production nodepool environment. We could instead default to the 'internal' network and the slaves should be reachable via fixed ip from the dev env, assuming it to was booted on the internal network.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, tip: we also need user-home and username set on the image so that nodepool, otherwise it defaults to jenkins
Update the nodepool provider defined in the vagrant group vars to work with the current opentechsjc network setup. There are multiple networks, so we must specify one to use. Also reduce the minimum nodes to reduce resource overhead. Signed-off-by: K Jonathan Harker <Jonathan.Harker@ibm.com>
977d1cd
to
36c8d6d
Compare
Update the nodepool provider defined in the vagrant group vars to
work with the current opentechsjc network setup. There are multiple
networks, so we must specify one to use. Also reduce the minimum nodes
to reduce resource overhead.
Signed-off-by: K Jonathan Harker Jonathan.Harker@ibm.com