Skip to content
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.

Ansible: generalization of roles, CI, joined effort #1298

Closed
ingvagabund opened this issue Jun 30, 2016 · 5 comments
Closed

Ansible: generalization of roles, CI, joined effort #1298

ingvagabund opened this issue Jun 30, 2016 · 5 comments
Labels
area/ansible lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@ingvagabund
Copy link
Contributor

ingvagabund commented Jun 30, 2016

Decomposition of roles to elevate modularity

As pointed by @stephenrlouie, it makes sense to generalize the roles and make them independent of playbooks [2]. To deploy kubernetes on one node cluster, there is no need for flannel. Sometimes, only kubernetes addons are needed.

Related issues:

Joined effort

Some roles are already shared via Ansible galaxy:

Others can be found for sure. It makes sense to collaborate with individual folks and elevate the effort.

CI

Run various tests on various parts of playbooks to extend the application to various linux distributions. Testing for regressions is important as well. Naming few:

  • smoke tests (testing individual roles on various OSes)
  • unit-tests (testing created facts on various versions of ansible on various OSes)
  • some sort of dashboard with daily digests of run playbooks on various OSes

Both smoke tests and unit-tests can be run over each PR. Daily digest can be taken from periodic jobs run from master HEAD.

Other effort:

Now, sooner or later it is desired to move the entire ansible code under kube-deploy repository:

Make the deployment faster:

[1] http://docs.ansible.com/ansible/galaxy.html
[2] https://github.com/openstack/openstack-ansible

@stephenrlouie
Copy link
Contributor

@danehans

k8s-github-robot pushed a commit that referenced this issue Aug 23, 2016
Automatic merge from submit-queue

Refactor kubernetes roles

Continuing effort [1] of cleaning roles for kubernetes, master and node roles.

TODO:
- [x] clean ``kubernetes`` role
- [x] move ``download_bins.yml`` under ``node`` and ``master`` and enable installation of downloaded binaries for Fedora, CentOS and other OSes.
- [x] extend the installation options with installation of distribution rpm (not just the latest)
- [x] clean and refactor ``node`` role
- [x] clean and refactor ``master`` role
- [x] introduce ``deploy-master.yml`` and ``deploy-node.yml`` playbooks, include them in the top level playbook
- [x] tag relevant tasks and introduce new scripts
- [x] move CPU and Memory accounting under node role (inside ``kubelet-configuration.yml``)

Some items of the TODO (new playbooks, new scripts) can be resolved only once the #967 is merged.

[1] #1298
@jasonbrooks
Copy link
Contributor

@ingvagabund Any activity on this front? I've been wondering about whether we should look at joining efforts with https://github.com/kubernetes-incubator/kubespray or perhaps with https://github.com/openshift/openshift-ansible

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 6, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 9, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/ansible lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

5 participants