Hello community, here is the log from the commit of package kubernetes-salt for openSUSE:Factory checked in at 2018-04-24 15:34:11 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/kubernetes-salt (Old) and /work/SRC/openSUSE:Factory/.kubernetes-salt.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "kubernetes-salt" Tue Apr 24 15:34:11 2018 rev:14 rq:600111 version:3.0.0+git_r727_68280fa Changes: -------- --- /work/SRC/openSUSE:Factory/kubernetes-salt/kubernetes-salt.changes 2018-04-16 12:48:51.829385650 +0200 +++ /work/SRC/openSUSE:Factory/.kubernetes-salt.new/kubernetes-salt.changes 2018-04-24 15:34:13.207854421 +0200 @@ -1,0 +2,256 @@ +Mon Apr 23 12:03:59 UTC 2018 - [email protected] + +- Commit 44798f4 by Rafael Fernández López [email protected] + Use `expr_form` instead of `tgt_type` until we update salt + + This is producing an error on our current salt version: + + `Rendering SLS 'base:cleanup.remove-post-orchestration' failed: Jinja + error: get() + got an unexpected keyword argument 'tgt_type'` + + Go back to using `expr_form` until we update. + + feature#deployment-stability + + +------------------------------------------------------------------- +Mon Apr 23 10:16:50 UTC 2018 - [email protected] + +- Commit 352e4f5 by Rafael Fernández López [email protected] + Always remove the "we are removing a machine" grain from the cluster + + Even if the `removal` orchestration has failed, we want to remove this grain + from the cluster, or the subsequent `etc-hosts` orchestrations won't be + executed if a removal failed. + + feature#deployment-stability + + +------------------------------------------------------------------- +Mon Apr 23 07:43:54 UTC 2018 - [email protected] + +- Commit f2190ca by Alvaro Saurin [email protected] + Instead of running things on the forced-removal orchestration, move actions + to SLS files (so they can be shared with the regular removal orchestration). + + feature#node_removal + + +------------------------------------------------------------------- +Sat Apr 21 10:16:14 UTC 2018 - [email protected] + +- Commit 6d5dcda by Federico Ceratto [email protected] + Stop using __opts__ and os_data() + + bsc#1087115 + + +------------------------------------------------------------------- +Fri Apr 20 08:47:24 UTC 2018 - [email protected] + +- Commit ec9c37c by Flavio Castelli [email protected] + Introduce feature-gates pillar + + Allow feature gates to be toggled via a dedicated pillar. + + feature#feature-gates + + +------------------------------------------------------------------- +Thu Apr 19 09:00:00 UTC 2018 - [email protected] + +- Commit 165baf2 by Federico Ceratto [email protected] + Switch caasp_nodename to using __opts__ + bsc#1087115 + +------------------------------------------------------------------- +Wed Apr 18 15:23:47 UTC 2018 - [email protected] + +- Commit 52b61c2 by Flavio Castelli [email protected] + crio: fix upgrade orchestration + + Ensure everything is fine on the admin node + + feature#crio + + Signed-off-by: Flavio Castelli <[email protected]> + + Commit 33256f0 by Flavio Castelli [email protected] + crio: cleanup code + + Several changes to reflect the feedback got on the pull request. + + feature#crio + + Signed-off-by: Flavio Castelli <[email protected]> + + Commit f62aaec by Flavio Castelli [email protected] + Do not rely on salt virtual_subtype grain + + The `virtual_subtype` grain cannot be used to identify salt minions that are + running inside of containers started by kubernetes. + + The salt core code sets this grain to `Docker` by looking at the cgroup + hierarchy of PID 1 on the minion. + + On regular docker container (not managed by kubernetes!) the cgroup hierarchy + includes a `docker` slice. However all the containers started by kubelet are + placed under the `kubepods` slice. + + Right now the only salt minion running inside of a container is the `ca` one, + which can be easily identified by looking at its roles. + + This commit changes our salt states to use roles instead of the unreliable + `virtual_subtype` grain. + + feature#crio + + Signed-off-by: Flavio Castelli <[email protected]> + + Commit 569c9aa by Flavio Castelli [email protected] + Extend motd + + Show information about the container runtime used on the node. + + feature#crio + + Signed-off-by: Flavio Castelli <[email protected]> + + Commit 1bae9eb by Flavio Castelli [email protected] + Remove unused cri abstractions + + cri-o doesn't have yet a way to copy files from the host into its running + containers. Fortunately this feature is required only on the admin node, + which is still using docker. + + This commit removes some of the abstractions introduced to be able to copy + files into running containers. + + We will revert this commit later on, once we migrate the admin node to use + cri-o. + + feature#crio + + Signed-off-by: Flavio Castelli <[email protected]> + + Commit 0c7a2b2 by Flavio Castelli [email protected] + Fix issue caused by velum pillar override + + Pillars set by velum are going to override what is set via the + `salt/pillars` files. + + That caused all the nodes to be using cri-o. The following code enforces + 'docker' to be used for all the nodes with a certain role (eg: the admin and + the ca ones). + + feature#crio + + Signed-off-by: Flavio Castelli <[email protected]> + + Commit 72e93b8 by Flavio Castelli [email protected] + Full support of cri-o + + Allow to deploy new SUSE CaaS Platform clusters using cri-o as a container + runtime instead of docker. + + The cluster will keep using docker on the admin node, while all the other + nodes are going to use cri-o. + + It's not possible to have mixed environments, all nodes have to use the same + container runtime. + + The CRI can be chosen by setting the value of the `cri:name` pillar, which is + defined inside of the `pillar/cri.sls` file. By default `docker` is being + used. + + feature#crio + + Signed-off-by: Flavio Castelli <[email protected]> + + Commit 8bc9d1b by Flavio Castelli [email protected] + Remove e2e image puller manifest + + This is no longer used. + + Commit e4b586a by Alvaro Saurin [email protected] + Added support for the CRIO containers runtime + + +------------------------------------------------------------------- +Wed Apr 18 08:17:13 UTC 2018 - [email protected] + +- Commit 902cc67 by Kiall Mac Innes [email protected] + Ensure salt master and api configs are complete + + This moves the external_auth section over to 50-master.conf, as this is + needed by the salt-master process, and duplicates `user: root` from + 50-master.conf to 50-api.conf - which allows salt-api to start and function + without it reading 50-master.conf + + +------------------------------------------------------------------- +Wed Apr 18 08:12:11 UTC 2018 - [email protected] + +- Commit 24835c2 by Alvaro Saurin [email protected] + Fix: always remove the "we-are-removing-a-node" cluster-wide grain. Make sure + we flush the mine (for the target) after removing the target's key. ++++ 59 more lines (skipped) ++++ between /work/SRC/openSUSE:Factory/kubernetes-salt/kubernetes-salt.changes ++++ and /work/SRC/openSUSE:Factory/.kubernetes-salt.new/kubernetes-salt.changes ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ kubernetes-salt.spec ++++++ --- /var/tmp/diff_new_pack.dKDTJ3/_old 2018-04-24 15:34:14.343813322 +0200 +++ /var/tmp/diff_new_pack.dKDTJ3/_new 2018-04-24 15:34:14.351813033 +0200 @@ -25,14 +25,14 @@ %endif %if 0%{?is_opensuse} && 0%{?suse_version} > 1500 - %define _base_image tumbleweed + %define _base_image kubic %endif %{!?tmpfiles_create:%global tmpfiles_create systemd-tmpfiles --create} Name: kubernetes-salt %define gitrepo salt -Version: 3.0.0+git_r688_ac25f0d +Version: 3.0.0+git_r727_68280fa Release: 0 BuildArch: noarch Summary: Production-Grade Container Scheduling and Management @@ -41,9 +41,18 @@ Url: https://github.com/kubic-project/salt Source: master.tar.gz BuildRequires: systemd-rpm-macros +Requires: salt +%if 0%{?suse_version} >= 1500 +Requires: python3-M2Crypto +Requires: python3-etcd +Requires: python3-pyOpenSSL +Requires: python3-pyroute2 +%else +Requires: python-etcd Requires: python-m2crypto Requires: python-pyOpenSSL -Requires: salt +Requires: python-pyroute2 +%endif %description Salt scripts for deploying a Kubernetes cluster ++++++ master.tar.gz ++++++ ++++ 1682 lines of diff (skipped)
