<?xml version="1.0" encoding="UTF-8"?>
<otherdata xmlns="http://linux.duke.edu/metadata/other" packages="8">
<package pkgid="a7853f6363bc20f1474dafb2ab3d81cdc58935393674bccfb38d93d16e25d5a7" name="caasp-container-manifests" arch="noarch">
  <version epoch="0" ver="0.0.0+git_r151_1190d13" rel="2.1"/>
  <changelog author="containers-bugowner@suse.de" date="1498219200">- Commit 1f5680c by Rafael Fernández López ereslibre@ereslibre.es
  Mount `salt-master` and `salt-minion-ca` caches from the host
  This way we ensure that the mine information and other cached information
  survives reboots.
  Fixes: bsc#1045368</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498478400">- Commit d5a5ccc by Graham Hayes graham.hayes@suse.com
  bsc#1043592 Add pre-generation of minion keys
  Generates 2 salt keys (ca and admin) and places them in the correct
  directories.
  This allows us to remove *auto_accept* from the master config file and select
  the rest of the members of the cluster.
  The admin key is writen out to */etc/salt/pki/minion/minion.(pub|pem)* The ca
  key is written out the same path in the container.
  bsc#1043592</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498564800">- Commit 09c947b by Jordi Massaguer Pla jmassaguerpla@suse.de
  add the admin-node-setup script and service to the package
  This is the 3rd step to fix bsc#1045378 - activate.sh was not reran after
  admin node upgrade
  Commit 81a7983 by Jordi Massaguer Pla jmassaguerpla@suse.de
  add admin-node-setup service
  This is the second step to fix bsc#1045378 - activate.sh was not reran after
  admin node upgrade
  We create a service that will run the admin-node-setup.sh on every reboot
  (thus on every update)
  Enable this in the activate.sh
  Commit 68926c0 by Jordi Massaguer Pla jmassaguerpla@suse.de
  split activate into 2
  This is the first step to fix bsc#1045378 - activate.sh was not reran after
  admin node upgrade.
  We need to split the script in 2:
  - activate.sh: run only once after the installation
  - admin-node-setup.sh: run on every reboot (thus in every update)</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498564801">- Commit 2ab0646 by Thorsten Kukuk kukuk@thkukuk.de
  Fix ordner number of velum.conf for issue.d (we use only two digit numbers)</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498564802">- Commit bf6b0f0 by Graham Hayes graham.hayes@suse.com
  bsc#1043592 Use mktemp to create tmp directories
  Use `mktemp` to ensure that directory has a random name</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498651200">- Commit b738430 by Graham Hayes graham.hayes@suse.com
  bsc#1045350 Accept salt keys that have been pre-generated
  Currently the admin nodes salt minion starts before the container that
  generates and accepts keys is ran.
  This means that the salt minion is started with a key that is not accepted,
  and goes to a pending state.
  This checks if the key is pre-generated, and if we have accepted a key from
  this minion before. If the key has been generated, but not accepted, we
  accept the key and continue.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498651201">- Commit 0ea70ff by Kiall Mac Innes kiall@macinnes.ie
  Remove unnecessary code from activate.sh
  See SR#135010, SR#134883, SR#134572</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498651202">- Commit aa1a388 by Alvaro Saurin alvaro.saurin@gmail.com
  Minor: some comments</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498651203">- Commit 6714137 by Kiall Mac Innes kiall@macinnes.ie
  Clear TX update grains on admin node boot bsc#1045379
  Clear the tx_update_{reboot_needed,failed} grains upon boot. This ensures the
  UI doesn't continue to show an admin node upgrade after we've upgraded.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498737600">- Commit f9ee78a by Rafael Fernández López ereslibre@ereslibre.es
  Add gen-certs script
  This script will generate a CA and both certificates for services that
  require to start with TLS enabled: `velum` and `salt-api`.
  Thanks to Robert Roland (@robdaemon) for providing the original script.
  Fixes: bsc#1043570 Fixes: bsc#1043589</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498824000">- Commit ab71633 by Jordi Massaguer Pla jmassaguerpla@suse.de
  fix requirements for the docker images
  This is needed to fix bsc#1046378
  Signed-off-by: Jordi Massaguer Pla &lt;jmassaguerpla@suse.de&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498824001">- Commit 7ae4dac by Rafael Fernández López ereslibre@ereslibre.es
  Rename `velum-dashboard-autoyast` to `velum-autoyast`
  We have a lot of processes in the development, e2e-tests and debugging
  environments that use `velum-dashboard`. Renaming the autoyast serving to
  `velum-autoyast` will make them still only match one container, the one they
  expect (actually both of them are practically the same thing, but to keep
  things as they were).</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499169600">- Commit c685e59 by Kiall Mac Innes kiall@macinnes.ie
  Match up TLS cert generation to genca.sh
  * Remove critical constraints
  * Add nonRepudiation and digitalSignature key usages
  * Include only the keyid Authority Identifier
  bsc#1046708
  Commit eb05991 by Kiall Mac Innes kiall@macinnes.ie
  Include a UUID in the CA's Subject field
  Including a random UUID in the CA's subject fields ensures that browsers do
  not cache certs from older deployments, preventing access to replacement
  deployments.
  bsc#1046881
  Commit ee9d3ab by Kiall Mac Innes kiall@macinnes.ie
  Include x509 Subject and Authority IDs in certs
  e.g:
  X509v3 extensions:
  X509v3 Subject Key Identifier:
  15:5F:91:F5:63:EA:85:B6:91:AB:8C:A9:9E:C2:36:F0:FD:11:B8:2E
  X509v3 Authority Key Identifier:
  keyid:F2:AA:7D:21:48:9D:45:00:FA:0C:94:40:48:81:B7:92:33:B5:27:12
  bsc#1046881
  Commit 69a738d by Kiall Mac Innes kiall@macinnes.ie
  End entity TLS certs should not be CA certs
  Use different extentions when self signing the CA cert, and when signing end
  entity certs.
  bsc#1047177
  Commit 0c4bbd7 by Kiall Mac Innes kiall@macinnes.ie
  CA: Add some logging to more easily identify the steps</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499342400">- Commit 2a2a6af by Kiall Mac Innes kiall@macinnes.ie
  Reinstate critical flag on x509 extensions
  Reinstate the critiical flag on two x509 extenstions:
  * X509v3 Basic Constraints (CA=False)
  * X509v3 Key Usage (Digital Signature, Non Repudiation, Key Encipherment)
  bsc#1046708</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499774400">- Commit 1e3ef9e by Kiall Mac Innes kiall@macinnes.ie
  Add Jenkinsfile
  The Jenkinsfile in each repo, if we adopt Jenkins in the end, will be very
  thin, including just a single library load, and a single method call. This
  prevents us from needing to keep each projects Jenkinsfile in sync as CI
  changes are made.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500033600">- Commit 1e3ef9e by Kiall Mac Innes kiall@macinnes.ie
  Add Jenkinsfile
  The Jenkinsfile in each repo, if we adopt Jenkins in the end, will be very
  thin, including just a single library load, and a single method call. This
  prevents us from needing to keep each projects Jenkinsfile in sync as CI
  changes are made.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500033601">- Commit 001ac9f by Maximilian Meister mmeister@suse.de
  make branch safe by transforming slashes to dashes
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  (cherry picked from commit d376008e7402a94592885caf07755ea0e86ba577)
  Commit d6f5250 by Maximilian Meister mmeister@suse.de
  packaging: make branch configurable
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  (cherry picked from commit 4cfa01c0e5eeadbd4e3927881d8b43662a265adb)</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500638400">- Commit c436fd9 by Rafael Fernández López ereslibre@ereslibre.es
  Add fingerprints to the velum issue
  By adding SHA1 and SHA256 fingerprints to the Velum issue, we can ensure that
  the instance we are accessing is the right one, and we are not mistaken
  (several clusters) or to reject a MITM, since the certificates chain of trust
  does not exist (the CA is autogenerated), and the customer has no way to
  import the CA as trusted for now.
  Fixes: bsc#1048135</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500897600">- Commit 20fef89 by Rafael Fernández López ereslibre@ereslibre.es
  Cache the grains on the `ca` container
  Rendering grains on the `ca` takes a fair amount of time if they are not
  cached, as lots of grains are falling back to other cases, making other calls
  like `publish.publish` timeout (timeouts by default after 5 seconds).
  Forcing the grains cache will be slow only the first time, when the grains
  get populated, and will get cached, making future uses faster.
  Fixes: bsc#1049886</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500984000">- Commit 42e94d3 by Flavio Castelli fcastelli@suse.com
  Improve comment about how to access velum
  Be explicit about using `https://`, some users tried to access velum using
  `http://velum-ip:443`.
  Fixes bsc#1047310
  (cherry picked from commit 16553956d341321e7733eab36679b88b631dd4b2)</changelog>
</package>
<package pkgid="415753f4402687c798b45b1dd3aa06060ba9396cede5fa86d105f594d397f834" name="caasp-container-manifests" arch="src">
  <version epoch="0" ver="0.0.0+git_r151_1190d13" rel="2.1"/>
  <changelog author="containers-bugowner@suse.de" date="1498219200">- Commit 1f5680c by Rafael Fernández López ereslibre@ereslibre.es
  Mount `salt-master` and `salt-minion-ca` caches from the host
  This way we ensure that the mine information and other cached information
  survives reboots.
  Fixes: bsc#1045368</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498478400">- Commit d5a5ccc by Graham Hayes graham.hayes@suse.com
  bsc#1043592 Add pre-generation of minion keys
  Generates 2 salt keys (ca and admin) and places them in the correct
  directories.
  This allows us to remove *auto_accept* from the master config file and select
  the rest of the members of the cluster.
  The admin key is writen out to */etc/salt/pki/minion/minion.(pub|pem)* The ca
  key is written out the same path in the container.
  bsc#1043592</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498564800">- Commit 09c947b by Jordi Massaguer Pla jmassaguerpla@suse.de
  add the admin-node-setup script and service to the package
  This is the 3rd step to fix bsc#1045378 - activate.sh was not reran after
  admin node upgrade
  Commit 81a7983 by Jordi Massaguer Pla jmassaguerpla@suse.de
  add admin-node-setup service
  This is the second step to fix bsc#1045378 - activate.sh was not reran after
  admin node upgrade
  We create a service that will run the admin-node-setup.sh on every reboot
  (thus on every update)
  Enable this in the activate.sh
  Commit 68926c0 by Jordi Massaguer Pla jmassaguerpla@suse.de
  split activate into 2
  This is the first step to fix bsc#1045378 - activate.sh was not reran after
  admin node upgrade.
  We need to split the script in 2:
  - activate.sh: run only once after the installation
  - admin-node-setup.sh: run on every reboot (thus in every update)</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498564801">- Commit 2ab0646 by Thorsten Kukuk kukuk@thkukuk.de
  Fix ordner number of velum.conf for issue.d (we use only two digit numbers)</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498564802">- Commit bf6b0f0 by Graham Hayes graham.hayes@suse.com
  bsc#1043592 Use mktemp to create tmp directories
  Use `mktemp` to ensure that directory has a random name</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498651200">- Commit b738430 by Graham Hayes graham.hayes@suse.com
  bsc#1045350 Accept salt keys that have been pre-generated
  Currently the admin nodes salt minion starts before the container that
  generates and accepts keys is ran.
  This means that the salt minion is started with a key that is not accepted,
  and goes to a pending state.
  This checks if the key is pre-generated, and if we have accepted a key from
  this minion before. If the key has been generated, but not accepted, we
  accept the key and continue.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498651201">- Commit 0ea70ff by Kiall Mac Innes kiall@macinnes.ie
  Remove unnecessary code from activate.sh
  See SR#135010, SR#134883, SR#134572</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498651202">- Commit aa1a388 by Alvaro Saurin alvaro.saurin@gmail.com
  Minor: some comments</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498651203">- Commit 6714137 by Kiall Mac Innes kiall@macinnes.ie
  Clear TX update grains on admin node boot bsc#1045379
  Clear the tx_update_{reboot_needed,failed} grains upon boot. This ensures the
  UI doesn't continue to show an admin node upgrade after we've upgraded.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498737600">- Commit f9ee78a by Rafael Fernández López ereslibre@ereslibre.es
  Add gen-certs script
  This script will generate a CA and both certificates for services that
  require to start with TLS enabled: `velum` and `salt-api`.
  Thanks to Robert Roland (@robdaemon) for providing the original script.
  Fixes: bsc#1043570 Fixes: bsc#1043589</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498824000">- Commit ab71633 by Jordi Massaguer Pla jmassaguerpla@suse.de
  fix requirements for the docker images
  This is needed to fix bsc#1046378
  Signed-off-by: Jordi Massaguer Pla &lt;jmassaguerpla@suse.de&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498824001">- Commit 7ae4dac by Rafael Fernández López ereslibre@ereslibre.es
  Rename `velum-dashboard-autoyast` to `velum-autoyast`
  We have a lot of processes in the development, e2e-tests and debugging
  environments that use `velum-dashboard`. Renaming the autoyast serving to
  `velum-autoyast` will make them still only match one container, the one they
  expect (actually both of them are practically the same thing, but to keep
  things as they were).</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499169600">- Commit c685e59 by Kiall Mac Innes kiall@macinnes.ie
  Match up TLS cert generation to genca.sh
  * Remove critical constraints
  * Add nonRepudiation and digitalSignature key usages
  * Include only the keyid Authority Identifier
  bsc#1046708
  Commit eb05991 by Kiall Mac Innes kiall@macinnes.ie
  Include a UUID in the CA's Subject field
  Including a random UUID in the CA's subject fields ensures that browsers do
  not cache certs from older deployments, preventing access to replacement
  deployments.
  bsc#1046881
  Commit ee9d3ab by Kiall Mac Innes kiall@macinnes.ie
  Include x509 Subject and Authority IDs in certs
  e.g:
  X509v3 extensions:
  X509v3 Subject Key Identifier:
  15:5F:91:F5:63:EA:85:B6:91:AB:8C:A9:9E:C2:36:F0:FD:11:B8:2E
  X509v3 Authority Key Identifier:
  keyid:F2:AA:7D:21:48:9D:45:00:FA:0C:94:40:48:81:B7:92:33:B5:27:12
  bsc#1046881
  Commit 69a738d by Kiall Mac Innes kiall@macinnes.ie
  End entity TLS certs should not be CA certs
  Use different extentions when self signing the CA cert, and when signing end
  entity certs.
  bsc#1047177
  Commit 0c4bbd7 by Kiall Mac Innes kiall@macinnes.ie
  CA: Add some logging to more easily identify the steps</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499342400">- Commit 2a2a6af by Kiall Mac Innes kiall@macinnes.ie
  Reinstate critical flag on x509 extensions
  Reinstate the critiical flag on two x509 extenstions:
  * X509v3 Basic Constraints (CA=False)
  * X509v3 Key Usage (Digital Signature, Non Repudiation, Key Encipherment)
  bsc#1046708</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499774400">- Commit 1e3ef9e by Kiall Mac Innes kiall@macinnes.ie
  Add Jenkinsfile
  The Jenkinsfile in each repo, if we adopt Jenkins in the end, will be very
  thin, including just a single library load, and a single method call. This
  prevents us from needing to keep each projects Jenkinsfile in sync as CI
  changes are made.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500033600">- Commit 1e3ef9e by Kiall Mac Innes kiall@macinnes.ie
  Add Jenkinsfile
  The Jenkinsfile in each repo, if we adopt Jenkins in the end, will be very
  thin, including just a single library load, and a single method call. This
  prevents us from needing to keep each projects Jenkinsfile in sync as CI
  changes are made.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500033601">- Commit 001ac9f by Maximilian Meister mmeister@suse.de
  make branch safe by transforming slashes to dashes
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  (cherry picked from commit d376008e7402a94592885caf07755ea0e86ba577)
  Commit d6f5250 by Maximilian Meister mmeister@suse.de
  packaging: make branch configurable
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  (cherry picked from commit 4cfa01c0e5eeadbd4e3927881d8b43662a265adb)</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500638400">- Commit c436fd9 by Rafael Fernández López ereslibre@ereslibre.es
  Add fingerprints to the velum issue
  By adding SHA1 and SHA256 fingerprints to the Velum issue, we can ensure that
  the instance we are accessing is the right one, and we are not mistaken
  (several clusters) or to reject a MITM, since the certificates chain of trust
  does not exist (the CA is autogenerated), and the customer has no way to
  import the CA as trusted for now.
  Fixes: bsc#1048135</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500897600">- Commit 20fef89 by Rafael Fernández López ereslibre@ereslibre.es
  Cache the grains on the `ca` container
  Rendering grains on the `ca` takes a fair amount of time if they are not
  cached, as lots of grains are falling back to other cases, making other calls
  like `publish.publish` timeout (timeouts by default after 5 seconds).
  Forcing the grains cache will be slow only the first time, when the grains
  get populated, and will get cached, making future uses faster.
  Fixes: bsc#1049886</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500984000">- Commit 42e94d3 by Flavio Castelli fcastelli@suse.com
  Improve comment about how to access velum
  Be explicit about using `https://`, some users tried to access velum using
  `http://velum-ip:443`.
  Fixes bsc#1047310
  (cherry picked from commit 16553956d341321e7733eab36679b88b631dd4b2)</changelog>
</package>
<package pkgid="c009e4fe19ff72b9ebe203fdc3c9f77d2275bcd887b98351d65e90744ef1398e" name="kubernetes-salt" arch="noarch">
  <version epoch="0" ver="1.5.3+git_r334_96ad63d" rel="2.1"/>
  <changelog author="containers-bugowner@suse.de" date="1499342400">- Commit 2bd42f5 by Rafael Fernández López ereslibre@ereslibre.es
  Add prerequisite for key to be present on `cert` sls
  Add a specific dependency for the key to be present when generating the
  certificate for the minion.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428800">- Commit 871a9dc by Michal Jura mjura@suse.com
  Fix JINJA escaping for docker_opts in docker state module</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428801">- Commit ce45c56 by Rafael Fernández López ereslibre@ereslibre.es
  Remove unneeded signing policies
  These signing policies were used when the CA wasn't containerized, when we
  containerized it, they were moved to `caasp-container-manifests`, and the CA
  container is mounting it from there.
  If we uncontainerize the CA in the future we can move it back if needed, but
  let's keep this clean so it's not misleading.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428802">- Commit d2df0ed by Rafael Fernández López ereslibre@ereslibre.es
  When generating the certificate use the pillar path
  Since we added the minion certificate location to the pillar, also take the
  public key location from the pillar, or the certificate generation will fail
  if the pillar value changes.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499688000">- Commit de22c66 by Miquel Sabaté Solà msabate@suse.com
  Set MySQL as the job cache for the Salt master
  First of all, we can specify an external job cache. If we don't do that, then
  the `keep_jobs` option only applies to the local cache. This means that Salt
  will not clean up jobs, events and returns older than the specified
  `keep_jobs` value (default: 24h) for the MySQL returner that we have already
  configured.
  Moreover, since we'd already be using MySQL as a job cache, we don't have to
  use the local system (/var/cache/salt/master/jobs/) as a cache
  (note that Salt would still be using this directory to avoid JID collisions).
  The documentation also says that the local cache can be a burden for large
  deployments.
  See bsc#1044133
  Signed-off-by: Miquel Sabaté Solà &lt;msabate@suse.com&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499688001">- Commit 08a0960 by Kiall Mac Innes kiall@macinnes.ie
  Revert "Set MySQL as the job cache for the Salt master"
  This reverts commit de22c660a99bc1425295c86be7d7dc3e79089845.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499774400">- Commit e3c9c21 by Kiall Mac Innes kiall@macinnes.ie
  Add Jenkinsfile
  The Jenkinsfile in each repo, if we adopt Jenkins in the end, will be very
  thin, including just a single library load, and a single method call. This
  prevents us from needing to keep each projects Jenkinsfile in sync as CI
  changes are made.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499774401">- Commit fcbfd6b by Michal Jura mjura@suse.com
  Make log level configurable for dockerd service, bsc#1046407
  Set the logging level for dockerd, possible values are:
  [ debug, info, warn, error, fatal ]</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499774402">- Commit 31ad98d by Michal Jura mjura@suse.com
  Don't duplicate log level argument for k8s services, bsc#1046407</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499774403">- Commit 88e9ff9 by Rafael Fernández López ereslibre@ereslibre.es
  Keep `job_cache: True` as it's discouraged to disable it
  Our deployment is also failing probably due to the fact that we were
  disabling the salt `job_cache`.
  Commit b0547af by Miquel Sabaté Solà msabate@suse.com
  Set MySQL as the job cache for the Salt master
  First of all, we can specify an external job cache. If we don't do that, then
  the `keep_jobs` option only applies to the local cache. This means that Salt
  will not clean up jobs, events and returns older than the specified
  `keep_jobs` value (default: 24h) for the MySQL returner that we have already
  configured.
  Moreover, since we'd already be using MySQL as a job cache, we don't have to
  use the local system (/var/cache/salt/master/jobs/) as a cache
  (note that Salt would still be using this directory to avoid JID collisions).
  The documentation also says that the local cache can be a burden for large
  deployments.
  See bsc#1044133
  Signed-off-by: Miquel Sabaté Solà &lt;msabate@suse.com&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499947200">- Commit b6281ae by Kiall Mac Innes kiall@macinnes.ie
  Ensure grains are always refreshed periodically
  Salt's grains_refresh_every configuration param does not quite do what we
  need it to, it's failing to refresh grains from the `grains` file - leading
  to updates going undetected.
  This change adds a slightly modified version of what this config param
  internally does, adding the force_refresh: True argument, ensuring we
  correctly refresh.
  bsc#1048583</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500033600">- Commit c59070d by Rafael Fernández López ereslibre@ereslibre.es
  Fix `ca` key path
  This was a leftover from the previous implementation. Now the ca key is
  present under `/etc/pki/private` in the ca container too (as it mounts
  `/etc/pki`)</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500033601">- Commit e8e5675 by Maximilian Meister mmeister@suse.de
  make branch safe by transforming slashes to dashes
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  (cherry picked from commit 6b146d53a70df907251dee51c56e37cc4e495e8d)
  Commit 661407b by Maximilian Meister mmeister@suse.de
  packaging: make branch configurable
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  (cherry picked from commit 588b834d55ea07000d34afb2940f5d5294566a25)</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500292800">- Commit 6a027e2 by Alvaro Saurin alvaro.saurin@gmail.com
  Add some extra naames to the AIP server certificate (bsc#1033671)</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500292801">- Commit 344ad40 by Kiall Mac Innes kiall@macinnes.ie
  Upgrade: Wait longer for minions to reboot
  Wait 1200 seconds (20 minutes) for minions to reboot, instead of the default
  300 seconds (5 minutes). We increase this to cover off cases where slower to
  boot physical hardware is used.
  20 minutes was chosen as, I've seen physical hardware take 10-12 minutes in
  the past, and someone likely has something that is slower to reboot.
  bsc#1048683</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500379200">- Commit a47bafc by Rafael Fernández López ereslibre@ereslibre.es
  Explicitly refresh the mine on all minions after the `ca` has published the
  `ca.crt`
  We will explicitly force all minions to refresh the mine after the `ca`
  minion has published the `ca.crt` certificate on the mine, to avoid rendering
  problems with later SLS being executed. It might happen that a minion was
  missing this information on its mine, so the rendering of the SLS failed,
  effectively stopping the whole orchestration process.
  Fixes: bsc#1048548</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500465600">- Commit 5923b46 by Kiall Mac Innes kiall@macinnes.ie
  Don't wait for minion responses when rebooting
  When we instruct a minion to reboot, we can't reliably wait for the response
  from salt-minion letting us know that the "systemctl reboot" command
  succeeded, as systemd may choose to shutdown the salt-minion service before
  it can sent out the "Yes, that worked" response.
  Salt does not make any attempt to finish in progress tasks when it receives a
  SIGTERM, leaving us with few other viable choices for this.
  Fixes bsc#1049200</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500465601">- Commit 457f484 by Kiall Mac Innes kiall@macinnes.ie
  Add extra requisites to the update orchestration
  These additional requisites enforce a stricter ordering of tasks during the
  upgrade. In some case, "-set-update-grain" would not execute in the right
  place, potentially leading to a failed upgrade.
  bsc#1045381</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500552000">- Commit 817f2c4 by Rafael Fernández López ereslibre@ereslibre.es
  Do not publish the `ca.crt` from the `ca` SLS, use `mine_functions`
  We will be publishing this contents when the `ca` minion starts, so there's
  no need to do this during the orchestration.
  `mine.send` is not reliable enough since we cannot confirm that the contents
  are there yet, and waiting a random amount of time is not appropriate as we
  are just hiding the real problem. In the near future we can do an active wait
  for the content to be there using `retry`, but for now we just publish the
  contents of the `ca.crt` using
  `mine_functions`, so it is sent when the `ca` minion starts.
  There's no need to refresh the mine, as this was just hiding the real problem
  when we were publishing this contents during the orchestration phase.
  Fixes: bsc#1049137 Fixes: bsc#1048548</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500552001">- Commit dc4f2bb by Kiall Mac Innes kiall@macinnes.ie
  Delay reboots during upgrade by 15 seconds
  Even with backgrounding the call, salt-minion sometimes still does not have
  enough time to respond before systemd shuts down salt-minion on some
  environments. By adding a 15 second delay, we give salt-minion much more time
  than it should need in a healthy cluster to respond.
  Additionally, switch from the deprecated syntax for supplying bg=True, to the
  newer syntax which no longer logs a warning.
  Followup up fix for bsc#1049200</changelog>
</package>
<package pkgid="7bd516c7ce7696541991f3bccbb75dae51dfe88cd0595b3cdcdc9782f0553d96" name="kubernetes-salt" arch="src">
  <version epoch="0" ver="1.5.3+git_r334_96ad63d" rel="2.1"/>
  <changelog author="containers-bugowner@suse.de" date="1499342400">- Commit 2bd42f5 by Rafael Fernández López ereslibre@ereslibre.es
  Add prerequisite for key to be present on `cert` sls
  Add a specific dependency for the key to be present when generating the
  certificate for the minion.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428800">- Commit 871a9dc by Michal Jura mjura@suse.com
  Fix JINJA escaping for docker_opts in docker state module</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428801">- Commit ce45c56 by Rafael Fernández López ereslibre@ereslibre.es
  Remove unneeded signing policies
  These signing policies were used when the CA wasn't containerized, when we
  containerized it, they were moved to `caasp-container-manifests`, and the CA
  container is mounting it from there.
  If we uncontainerize the CA in the future we can move it back if needed, but
  let's keep this clean so it's not misleading.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428802">- Commit d2df0ed by Rafael Fernández López ereslibre@ereslibre.es
  When generating the certificate use the pillar path
  Since we added the minion certificate location to the pillar, also take the
  public key location from the pillar, or the certificate generation will fail
  if the pillar value changes.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499688000">- Commit de22c66 by Miquel Sabaté Solà msabate@suse.com
  Set MySQL as the job cache for the Salt master
  First of all, we can specify an external job cache. If we don't do that, then
  the `keep_jobs` option only applies to the local cache. This means that Salt
  will not clean up jobs, events and returns older than the specified
  `keep_jobs` value (default: 24h) for the MySQL returner that we have already
  configured.
  Moreover, since we'd already be using MySQL as a job cache, we don't have to
  use the local system (/var/cache/salt/master/jobs/) as a cache
  (note that Salt would still be using this directory to avoid JID collisions).
  The documentation also says that the local cache can be a burden for large
  deployments.
  See bsc#1044133
  Signed-off-by: Miquel Sabaté Solà &lt;msabate@suse.com&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499688001">- Commit 08a0960 by Kiall Mac Innes kiall@macinnes.ie
  Revert "Set MySQL as the job cache for the Salt master"
  This reverts commit de22c660a99bc1425295c86be7d7dc3e79089845.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499774400">- Commit e3c9c21 by Kiall Mac Innes kiall@macinnes.ie
  Add Jenkinsfile
  The Jenkinsfile in each repo, if we adopt Jenkins in the end, will be very
  thin, including just a single library load, and a single method call. This
  prevents us from needing to keep each projects Jenkinsfile in sync as CI
  changes are made.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499774401">- Commit fcbfd6b by Michal Jura mjura@suse.com
  Make log level configurable for dockerd service, bsc#1046407
  Set the logging level for dockerd, possible values are:
  [ debug, info, warn, error, fatal ]</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499774402">- Commit 31ad98d by Michal Jura mjura@suse.com
  Don't duplicate log level argument for k8s services, bsc#1046407</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499774403">- Commit 88e9ff9 by Rafael Fernández López ereslibre@ereslibre.es
  Keep `job_cache: True` as it's discouraged to disable it
  Our deployment is also failing probably due to the fact that we were
  disabling the salt `job_cache`.
  Commit b0547af by Miquel Sabaté Solà msabate@suse.com
  Set MySQL as the job cache for the Salt master
  First of all, we can specify an external job cache. If we don't do that, then
  the `keep_jobs` option only applies to the local cache. This means that Salt
  will not clean up jobs, events and returns older than the specified
  `keep_jobs` value (default: 24h) for the MySQL returner that we have already
  configured.
  Moreover, since we'd already be using MySQL as a job cache, we don't have to
  use the local system (/var/cache/salt/master/jobs/) as a cache
  (note that Salt would still be using this directory to avoid JID collisions).
  The documentation also says that the local cache can be a burden for large
  deployments.
  See bsc#1044133
  Signed-off-by: Miquel Sabaté Solà &lt;msabate@suse.com&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499947200">- Commit b6281ae by Kiall Mac Innes kiall@macinnes.ie
  Ensure grains are always refreshed periodically
  Salt's grains_refresh_every configuration param does not quite do what we
  need it to, it's failing to refresh grains from the `grains` file - leading
  to updates going undetected.
  This change adds a slightly modified version of what this config param
  internally does, adding the force_refresh: True argument, ensuring we
  correctly refresh.
  bsc#1048583</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500033600">- Commit c59070d by Rafael Fernández López ereslibre@ereslibre.es
  Fix `ca` key path
  This was a leftover from the previous implementation. Now the ca key is
  present under `/etc/pki/private` in the ca container too (as it mounts
  `/etc/pki`)</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500033601">- Commit e8e5675 by Maximilian Meister mmeister@suse.de
  make branch safe by transforming slashes to dashes
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  (cherry picked from commit 6b146d53a70df907251dee51c56e37cc4e495e8d)
  Commit 661407b by Maximilian Meister mmeister@suse.de
  packaging: make branch configurable
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  (cherry picked from commit 588b834d55ea07000d34afb2940f5d5294566a25)</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500292800">- Commit 6a027e2 by Alvaro Saurin alvaro.saurin@gmail.com
  Add some extra naames to the AIP server certificate (bsc#1033671)</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500292801">- Commit 344ad40 by Kiall Mac Innes kiall@macinnes.ie
  Upgrade: Wait longer for minions to reboot
  Wait 1200 seconds (20 minutes) for minions to reboot, instead of the default
  300 seconds (5 minutes). We increase this to cover off cases where slower to
  boot physical hardware is used.
  20 minutes was chosen as, I've seen physical hardware take 10-12 minutes in
  the past, and someone likely has something that is slower to reboot.
  bsc#1048683</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500379200">- Commit a47bafc by Rafael Fernández López ereslibre@ereslibre.es
  Explicitly refresh the mine on all minions after the `ca` has published the
  `ca.crt`
  We will explicitly force all minions to refresh the mine after the `ca`
  minion has published the `ca.crt` certificate on the mine, to avoid rendering
  problems with later SLS being executed. It might happen that a minion was
  missing this information on its mine, so the rendering of the SLS failed,
  effectively stopping the whole orchestration process.
  Fixes: bsc#1048548</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500465600">- Commit 5923b46 by Kiall Mac Innes kiall@macinnes.ie
  Don't wait for minion responses when rebooting
  When we instruct a minion to reboot, we can't reliably wait for the response
  from salt-minion letting us know that the "systemctl reboot" command
  succeeded, as systemd may choose to shutdown the salt-minion service before
  it can sent out the "Yes, that worked" response.
  Salt does not make any attempt to finish in progress tasks when it receives a
  SIGTERM, leaving us with few other viable choices for this.
  Fixes bsc#1049200</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500465601">- Commit 457f484 by Kiall Mac Innes kiall@macinnes.ie
  Add extra requisites to the update orchestration
  These additional requisites enforce a stricter ordering of tasks during the
  upgrade. In some case, "-set-update-grain" would not execute in the right
  place, potentially leading to a failed upgrade.
  bsc#1045381</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500552000">- Commit 817f2c4 by Rafael Fernández López ereslibre@ereslibre.es
  Do not publish the `ca.crt` from the `ca` SLS, use `mine_functions`
  We will be publishing this contents when the `ca` minion starts, so there's
  no need to do this during the orchestration.
  `mine.send` is not reliable enough since we cannot confirm that the contents
  are there yet, and waiting a random amount of time is not appropriate as we
  are just hiding the real problem. In the near future we can do an active wait
  for the content to be there using `retry`, but for now we just publish the
  contents of the `ca.crt` using
  `mine_functions`, so it is sent when the `ca` minion starts.
  There's no need to refresh the mine, as this was just hiding the real problem
  when we were publishing this contents during the orchestration phase.
  Fixes: bsc#1049137 Fixes: bsc#1048548</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500552001">- Commit dc4f2bb by Kiall Mac Innes kiall@macinnes.ie
  Delay reboots during upgrade by 15 seconds
  Even with backgrounding the call, salt-minion sometimes still does not have
  enough time to respond before systemd shuts down salt-minion on some
  environments. By adding a 15 second delay, we give salt-minion much more time
  than it should need in a healthy cluster to respond.
  Additionally, switch from the deprecated syntax for supplying bg=True, to the
  newer syntax which no longer logs a warning.
  Followup up fix for bsc#1049200</changelog>
</package>
<package pkgid="009d85c0838fcf5a84bebd4bc5d676d540b2ec7d25c608424d4cceaa59e7dd0d" name="kubernetes-terraform" arch="noarch">
  <version epoch="0" ver="1.5.3+20170714.2dd9780" rel="4.1"/>
  <changelog author="containers-bugowner@suse.de" date="1494936000">- Default `DASHBOARD_HOST` if empty and `SKIP_DASHBOARD` is provided</changelog>
  <changelog author="containers-bugowner@suse.de" date="1495454400">- Commit f897733 by Alvaro Saurin alvaro.saurin@gmail.com
- Updated docs</changelog>
  <changelog author="containers-bugowner@suse.de" date="1495713600">- Commit c4bb80a by Graham Hayes graham.hayes@suse.com
- Revert "contrib/libvirt.sh: suppress wget output once again"
-
- This reverts commit d66d186c7ddfdab2c8bd1896dbe458f955219d6d.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1496750400">- Commit 77d7342 by Kiall Mac Innes kiall@macinnes.ie
  Use the new staging images for CaaSP</changelog>
  <changelog author="containers-bugowner@suse.de" date="1497441600">- Commit 301d421 by Kiall Mac Innes kiall@macinnes.ie
  Pass terraform exit code through</changelog>
  <changelog author="containers-bugowner@suse.de" date="1497441601">- Commit 2984c1f by Kiall Mac Innes kiall@macinnes.ie
  Revert "Pass terraform exit code through"
  This reverts commit 301d42164821f2b0a7940c0b9cb179c7abb1e4b1.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1497441602">- Commit 8fc9e1a by Kiall Mac Innes kiall@macinnes.ie
  Set TF parallelism to 1</changelog>
  <changelog author="containers-bugowner@suse.de" date="1497614400">- Commit b52d64c by Flavio Castelli fcastelli@suse.com
  libvirt: add graph card back
  Add the graph card back, this is needed to interact with the machines using
  virt-manager's console.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498046400">- Commit 3a8f327 by Kiall Mac Innes kiall@macinnes.ie
  Allow selection of release/staging/devel images
  The STAGING variable, and it's values, match those used in caasp-devenv</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498132800">- Commit ce6b1e2 by Graham Hayes graham.hayes@suse.com
  Add 'grains_refresh_every' config to dev env</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498564800">- Commit fdd30a6 by Maximilian Meister mmeister@suse.de
  contrib/libvirt.sh: enable additional wget flags via ENV
  we need to have a way to set the verbosity otherwise in some scenarios (like
  CI) it's too much noise
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498824000">- Commit 7115743 by Michal Jura mjura@suse.com
  Accept salt keys before orchestration will start
  After change, bsc#1043592 Add support for accepting nodes all salt keys for
  nodes have to be accepted, we don't auto accept them any more.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499256000">- Commit ea3a829 by Michal Jura mjura@suse.com
  Generate certificates for salt-api and velum
  Call gen-certs.sh before containers will be launched on Admin Dashboard. This
  will certificates for salt-api and velum, normally on Admin Dashboard this
  script is called by activate.sh sctipt, which is not run on by this
  deployment.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499256001">- Commit 137dac9 by Alvaro Saurin alvaro.saurin@gmail.com
  Wait for the database and do not try to set it up here</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499342400">- Commit 1f677f4 by Kiall Mac Innes kiall@macinnes.ie
  Add Jenkinsfile
  The Jenkinsfile in each repo, if we adopt Jenkins in the end, will be very
  thin, including just a single library load, and a single method call. This
  prevents us from needing to keep each projects Jenkinsfile in sync as CI
  changes are made.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428800">- Commit 2c7e0ca by Kiall Mac Innes kiall@macinnes.ie
  Include FQDN and count as domain metadata
  This makes it easier to parse some data out of the terraform state file for
  CI purposes.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499688000">- Commit 924d247 by Graham Hayes graham.hayes@suse.com
  Allow NO_COLOR env var
  Commit 24c195e by Flavio Castelli fcastelli@suse.com
  Make colored output optional
  Disable colored output by passing the "--no-color" flag.
  Signed-off-by: Flavio Castelli &lt;fcastelli@suse.com&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499860800">- Commit dbd2575 by Victor Palade vpalade@suse.com
  small improvements: set the default of MINIONS_SIZE=3
  * since it became mandatory, in velum, for a bootstrap to have at least 3
  nodes, one master and 2 nodes, change the default value to 3.
  * add *.log to gitignore to avoid adding the crash logs to git.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499947200">- Commit 32657db by Graham Hayes graham.hayes@suse.com
  Generate environment.json file</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500033600">- Commit 013646d by Maximilian Meister mmeister@suse.de
  make branch safe by transforming slashes to dashes
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  (cherry picked from commit ff46d0e21da567a8281f3892277f7e002d4073ce)
  Commit a1733a0 by Maximilian Meister mmeister@suse.de
  packaging: make branch configurable
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  (cherry picked from commit e2339f07ed4bd07a4907002c2a11eefbb6eae4b2)</changelog>
</package>
<package pkgid="690b3a063e306e301800c175c7d17ea6d62254005dd4159e479c704a3d8abee5" name="kubernetes-terraform" arch="src">
  <version epoch="0" ver="1.5.3+20170714.2dd9780" rel="4.1"/>
  <changelog author="containers-bugowner@suse.de" date="1494936000">- Default `DASHBOARD_HOST` if empty and `SKIP_DASHBOARD` is provided</changelog>
  <changelog author="containers-bugowner@suse.de" date="1495454400">- Commit f897733 by Alvaro Saurin alvaro.saurin@gmail.com
- Updated docs</changelog>
  <changelog author="containers-bugowner@suse.de" date="1495713600">- Commit c4bb80a by Graham Hayes graham.hayes@suse.com
- Revert "contrib/libvirt.sh: suppress wget output once again"
-
- This reverts commit d66d186c7ddfdab2c8bd1896dbe458f955219d6d.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1496750400">- Commit 77d7342 by Kiall Mac Innes kiall@macinnes.ie
  Use the new staging images for CaaSP</changelog>
  <changelog author="containers-bugowner@suse.de" date="1497441600">- Commit 301d421 by Kiall Mac Innes kiall@macinnes.ie
  Pass terraform exit code through</changelog>
  <changelog author="containers-bugowner@suse.de" date="1497441601">- Commit 2984c1f by Kiall Mac Innes kiall@macinnes.ie
  Revert "Pass terraform exit code through"
  This reverts commit 301d42164821f2b0a7940c0b9cb179c7abb1e4b1.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1497441602">- Commit 8fc9e1a by Kiall Mac Innes kiall@macinnes.ie
  Set TF parallelism to 1</changelog>
  <changelog author="containers-bugowner@suse.de" date="1497614400">- Commit b52d64c by Flavio Castelli fcastelli@suse.com
  libvirt: add graph card back
  Add the graph card back, this is needed to interact with the machines using
  virt-manager's console.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498046400">- Commit 3a8f327 by Kiall Mac Innes kiall@macinnes.ie
  Allow selection of release/staging/devel images
  The STAGING variable, and it's values, match those used in caasp-devenv</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498132800">- Commit ce6b1e2 by Graham Hayes graham.hayes@suse.com
  Add 'grains_refresh_every' config to dev env</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498564800">- Commit fdd30a6 by Maximilian Meister mmeister@suse.de
  contrib/libvirt.sh: enable additional wget flags via ENV
  we need to have a way to set the verbosity otherwise in some scenarios (like
  CI) it's too much noise
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1498824000">- Commit 7115743 by Michal Jura mjura@suse.com
  Accept salt keys before orchestration will start
  After change, bsc#1043592 Add support for accepting nodes all salt keys for
  nodes have to be accepted, we don't auto accept them any more.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499256000">- Commit ea3a829 by Michal Jura mjura@suse.com
  Generate certificates for salt-api and velum
  Call gen-certs.sh before containers will be launched on Admin Dashboard. This
  will certificates for salt-api and velum, normally on Admin Dashboard this
  script is called by activate.sh sctipt, which is not run on by this
  deployment.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499256001">- Commit 137dac9 by Alvaro Saurin alvaro.saurin@gmail.com
  Wait for the database and do not try to set it up here</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499342400">- Commit 1f677f4 by Kiall Mac Innes kiall@macinnes.ie
  Add Jenkinsfile
  The Jenkinsfile in each repo, if we adopt Jenkins in the end, will be very
  thin, including just a single library load, and a single method call. This
  prevents us from needing to keep each projects Jenkinsfile in sync as CI
  changes are made.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428800">- Commit 2c7e0ca by Kiall Mac Innes kiall@macinnes.ie
  Include FQDN and count as domain metadata
  This makes it easier to parse some data out of the terraform state file for
  CI purposes.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499688000">- Commit 924d247 by Graham Hayes graham.hayes@suse.com
  Allow NO_COLOR env var
  Commit 24c195e by Flavio Castelli fcastelli@suse.com
  Make colored output optional
  Disable colored output by passing the "--no-color" flag.
  Signed-off-by: Flavio Castelli &lt;fcastelli@suse.com&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499860800">- Commit dbd2575 by Victor Palade vpalade@suse.com
  small improvements: set the default of MINIONS_SIZE=3
  * since it became mandatory, in velum, for a bootstrap to have at least 3
  nodes, one master and 2 nodes, change the default value to 3.
  * add *.log to gitignore to avoid adding the crash logs to git.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499947200">- Commit 32657db by Graham Hayes graham.hayes@suse.com
  Generate environment.json file</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500033600">- Commit 013646d by Maximilian Meister mmeister@suse.de
  make branch safe by transforming slashes to dashes
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  (cherry picked from commit ff46d0e21da567a8281f3892277f7e002d4073ce)
  Commit a1733a0 by Maximilian Meister mmeister@suse.de
  packaging: make branch configurable
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  (cherry picked from commit e2339f07ed4bd07a4907002c2a11eefbb6eae4b2)</changelog>
</package>
<package pkgid="81861d781ceab458e66654ca12e2f858cc7e45e3c8d44ed855dc338d98235429" name="velum" arch="src">
  <version epoch="0" ver="1.0.0+git_r447_5cdaee560571557fa4ba7146e07e94af8af03535" rel="3.1"/>
  <changelog author="containers-bugowner@suse.de" date="1499256000">- Commit 125fb16 by Rafael Fernández López ereslibre@ereslibre.es
  Make travis load the required phantomjs version
  Also improve caching for faster builds.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499342400">- Commit 2211633 by PI-Victor palade.ionut@gmail.com
  views: remove lore ipsum dead code from worker_bootstrap.html.slim</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499342401">- Commit b898f75 by Rafael Fernández López ereslibre@ereslibre.es
  Download the kubectl client certificate and key from the new location
  Fixes: bsc#1046963</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499342402">- Commit 67308fb by Flavio Castelli fcastelli@suse.com
  Improve the style of "db is initializing" page [bsc#1047305]
  Try to use the same style as the main velum web application.
  Signed-off-by: Flavio Castelli &lt;fcastelli@suse.com&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428800">- Commit 7f8256d by Maximilian Meister mmeister@suse.de
  change dark to light font color in the dark background
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  Commit 68927b8 by Maximilian Meister mmeister@suse.de
  public: style the other static pages as well
  follow up of #237
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428801">- Commit f34180e by Flavio Castelli fcastelli@suse.com
  Serve "db is not ready" page over https [bsc#1047203]
  Ensure the "db is not yet ready" is served over https too. This fixes
  bsc#1047203.
  Signed-off-by: Flavio Castelli &lt;fcastelli@suse.com&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428802">- Commit 53f71da by Rafael Fernández López ereslibre@ereslibre.es
  Before checking all nodes, make sure we are waiting for them
  When using the `check-all` box, make sure that all expected nodes are present
  on the page, so we select all the nodes that we intend to, instead of only a
  subset of them.
  This should help remove flaky tests.
  Commit bab4226 by Miquel Sabaté Solà msabate@suse.com
  Improved the reliability of some tests
  There's a flaky test that has been marked as `pending` since:
  1. It's already tested as an end-to-end test. 2. We've wasted too much time
  on it already and we have more pressing
  issues.
  Besides that, we've applied best practices and tests should run faster
  overall.
  This commit has been done with the help of @vitoravelino and @ereslibre.
  Signed-off-by: Miquel Sabaté Solà &lt;msabate@suse.com&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428803">- Commit 054e21c by Rafael Fernández López ereslibre@ereslibre.es
  Take orchestration result into consideration when bootstrapping
  When bootstrapping, if the orchestration fails, depending in what stage it
  failed, we might never retrieve individual highstate returns from minions, so
  they will be in `pending` status forever.
  With this change, we also listen for the overall bootstrap orchestration
  result (`orch.kubernetes` for now), so we will mark all pending nodes as
  failed.
  Fixes: bsc#1046706</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428804">- Commit c28c294 by Flavio Castelli fcastelli@suse.com
  db not ready page: return http 503
  The "db is not ready" page now returns a http 503 status instead of a 200.
  Signed-off-by: Flavio Castelli &lt;fcastelli@suse.com&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499774400">- Commit a40ed8a by Kiall Mac Innes kiall@macinnes.ie
  Add Jenkinsfile
  The Jenkinsfile in each repo, if we adopt Jenkins in the end, will be very
  thin, including just a single library load, and a single method call. This
  prevents us from needing to keep each projects Jenkinsfile in sync as CI
  changes are made.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499860800">- Commit 55895e9 by Rafael Fernández López ereslibre@ereslibre.es
  Add missing indexes for `salt_events` table
  Fix some slow queries that we were having due to missing indexes.
  Increase batch job size.
  Fixes: bsc#1046862</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499860801">- Commit 79cccb5 by Rafael Fernández López ereslibre@ereslibre.es
  `force_ssl` is documented to be executed from the class context
  Not all redirections to `https` were properly handled. By making this
  change we manually redirect to `https` as a `before_action` as before,
  but handling a `redirect_to` in the chain (effectively stopping the
  chain and in the expected order).
  The reason behind this is that `force_ssl` called from our own filter:
  https://github.com/rails/rails/blob/03925dc26a747075ff37660d1f0a060a8178bf66/actionpack/lib/action_controller/metal/force_ssl.rb#L62-L68
  installs a `before_action`, but it's already too late for that very
  request (we are already in the `before_actions` for that request).
  Also, with the current implementation the filter gets installed after
  our other `before_action` filters, what implies that the redirection
  to `https` is not the very first filter in the chain, as it should
  be.
  By calling to the method itself:
  https://github.com/rails/rails/blob/03925dc26a747075ff37660d1f0a060a8178bf66/actionpack/lib/action_controller/metal/force_ssl.rb#L76-L96
  from our filter, we ensure all requests are redirected to TLS.
  Fixes: bsc#1048134</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499860802">- Commit 4ae4648 by Jordi Massaguer Pla jmassaguerpla@suse.de
  [packaging] rebase schema patch because of the changes introduced in 7e2e454
  Signed-off-by: Jordi Massaguer Pla &lt;jmassaguerpla@suse.de&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499947200">- Commit aed8918 by Rafael Fernández López ereslibre@ereslibre.es
  Detect orchestration results when `mods` has been provided as argument
  We usually run the orchestrations manually as:
  `salt-run state.orchestrate orch.kubernetes`
  And this case was detected properly. This change adds support for also
  detecting the orchestration result when the orchestration is called using the
  `salt-api` on Velum (the general case):
  `salt-run state.orchestrate mods=orch.kubernetes`
  With this change we support both return results.
  Fixes: bsc#1046706</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500033600">- Commit aed8918 by Rafael Fernández López ereslibre@ereslibre.es
  Detect orchestration results when `mods` has been provided as argument
  We usually run the orchestrations manually as:
  `salt-run state.orchestrate orch.kubernetes`
  And this case was detected properly. This change adds support for also
  detecting the orchestration result when the orchestration is called using the
  `salt-api` on Velum (the general case):
  `salt-run state.orchestrate mods=orch.kubernetes`
  With this change we support both return results.
  Fixes: bsc#1046706</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500033601">- Commit a285f00 by Maximilian Meister mmeister@suse.de
  make branch safe by transforming slashes to dashes
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  (cherry picked from commit 49ab27251e452026bee834eb56709180c781a783)
  Commit 7e861b6 by Maximilian Meister mmeister@suse.de
  packaging: make branch configurable
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  (cherry picked from commit b0d65b5acc4beea1052e748120fbbf42a8715fc4)</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500379200">- Commit d8db7e0 by Kiall Mac Innes kiall@macinnes.ie
  Handle failues of the update orchestration
  Handle the failure of an update orchestration in the same way we handle a
  failure for a bootstrap orchestration.
  bsc#1047895</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500379201">- Commit 466f6cb by Maximilian Meister mmeister@suse.de
  increase workers (bsc#1048533)
  this allows for more concurrent api requests
  a worker spawns a copy of the velum process
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500638400">- Commit 0d7fe16 by Vítor Avelino contact@vitoravelino.me
  bsc#1049165 : avoid orchestration action from ui while updating/adding node
  - When an admin node update is available, do not allow users to press "update
  all nodes". The admin node should be updated first.
  - Never allow both a workers update and an admin update to be started at the
  same time.
  - Velum should not allow add node while a bootstrap/upgrade/etc is in
  progress
- Commit fa31b18 by Vítor Avelino contact@vitoravelino.me
  bsc#1045734: fix show/hide update link based on update/highstate
  - Update all nodes link should be shown if all nodes are in applied
  state and there's an update available/retryable. If for some reason
  a node goes to a different state than "applied" or there's no update,
  link becomes unavailable.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500984000">- Commit f4c1056 by Kiall Mac Innes kiall@macinnes.ie
  Set VERSION to 1.0.0
  Fixes bsc#1050396</changelog>
</package>
<package pkgid="e0bad5cd547dd66929db2da635893f53df81934f13da5f9b3501856ea097e8bc" name="velum" arch="x86_64">
  <version epoch="0" ver="1.0.0+git_r447_5cdaee560571557fa4ba7146e07e94af8af03535" rel="3.1"/>
  <changelog author="containers-bugowner@suse.de" date="1499256000">- Commit 125fb16 by Rafael Fernández López ereslibre@ereslibre.es
  Make travis load the required phantomjs version
  Also improve caching for faster builds.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499342400">- Commit 2211633 by PI-Victor palade.ionut@gmail.com
  views: remove lore ipsum dead code from worker_bootstrap.html.slim</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499342401">- Commit b898f75 by Rafael Fernández López ereslibre@ereslibre.es
  Download the kubectl client certificate and key from the new location
  Fixes: bsc#1046963</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499342402">- Commit 67308fb by Flavio Castelli fcastelli@suse.com
  Improve the style of "db is initializing" page [bsc#1047305]
  Try to use the same style as the main velum web application.
  Signed-off-by: Flavio Castelli &lt;fcastelli@suse.com&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428800">- Commit 7f8256d by Maximilian Meister mmeister@suse.de
  change dark to light font color in the dark background
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  Commit 68927b8 by Maximilian Meister mmeister@suse.de
  public: style the other static pages as well
  follow up of #237
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428801">- Commit f34180e by Flavio Castelli fcastelli@suse.com
  Serve "db is not ready" page over https [bsc#1047203]
  Ensure the "db is not yet ready" is served over https too. This fixes
  bsc#1047203.
  Signed-off-by: Flavio Castelli &lt;fcastelli@suse.com&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428802">- Commit 53f71da by Rafael Fernández López ereslibre@ereslibre.es
  Before checking all nodes, make sure we are waiting for them
  When using the `check-all` box, make sure that all expected nodes are present
  on the page, so we select all the nodes that we intend to, instead of only a
  subset of them.
  This should help remove flaky tests.
  Commit bab4226 by Miquel Sabaté Solà msabate@suse.com
  Improved the reliability of some tests
  There's a flaky test that has been marked as `pending` since:
  1. It's already tested as an end-to-end test. 2. We've wasted too much time
  on it already and we have more pressing
  issues.
  Besides that, we've applied best practices and tests should run faster
  overall.
  This commit has been done with the help of @vitoravelino and @ereslibre.
  Signed-off-by: Miquel Sabaté Solà &lt;msabate@suse.com&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428803">- Commit 054e21c by Rafael Fernández López ereslibre@ereslibre.es
  Take orchestration result into consideration when bootstrapping
  When bootstrapping, if the orchestration fails, depending in what stage it
  failed, we might never retrieve individual highstate returns from minions, so
  they will be in `pending` status forever.
  With this change, we also listen for the overall bootstrap orchestration
  result (`orch.kubernetes` for now), so we will mark all pending nodes as
  failed.
  Fixes: bsc#1046706</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499428804">- Commit c28c294 by Flavio Castelli fcastelli@suse.com
  db not ready page: return http 503
  The "db is not ready" page now returns a http 503 status instead of a 200.
  Signed-off-by: Flavio Castelli &lt;fcastelli@suse.com&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499774400">- Commit a40ed8a by Kiall Mac Innes kiall@macinnes.ie
  Add Jenkinsfile
  The Jenkinsfile in each repo, if we adopt Jenkins in the end, will be very
  thin, including just a single library load, and a single method call. This
  prevents us from needing to keep each projects Jenkinsfile in sync as CI
  changes are made.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499860800">- Commit 55895e9 by Rafael Fernández López ereslibre@ereslibre.es
  Add missing indexes for `salt_events` table
  Fix some slow queries that we were having due to missing indexes.
  Increase batch job size.
  Fixes: bsc#1046862</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499860801">- Commit 79cccb5 by Rafael Fernández López ereslibre@ereslibre.es
  `force_ssl` is documented to be executed from the class context
  Not all redirections to `https` were properly handled. By making this
  change we manually redirect to `https` as a `before_action` as before,
  but handling a `redirect_to` in the chain (effectively stopping the
  chain and in the expected order).
  The reason behind this is that `force_ssl` called from our own filter:
  https://github.com/rails/rails/blob/03925dc26a747075ff37660d1f0a060a8178bf66/actionpack/lib/action_controller/metal/force_ssl.rb#L62-L68
  installs a `before_action`, but it's already too late for that very
  request (we are already in the `before_actions` for that request).
  Also, with the current implementation the filter gets installed after
  our other `before_action` filters, what implies that the redirection
  to `https` is not the very first filter in the chain, as it should
  be.
  By calling to the method itself:
  https://github.com/rails/rails/blob/03925dc26a747075ff37660d1f0a060a8178bf66/actionpack/lib/action_controller/metal/force_ssl.rb#L76-L96
  from our filter, we ensure all requests are redirected to TLS.
  Fixes: bsc#1048134</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499860802">- Commit 4ae4648 by Jordi Massaguer Pla jmassaguerpla@suse.de
  [packaging] rebase schema patch because of the changes introduced in 7e2e454
  Signed-off-by: Jordi Massaguer Pla &lt;jmassaguerpla@suse.de&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1499947200">- Commit aed8918 by Rafael Fernández López ereslibre@ereslibre.es
  Detect orchestration results when `mods` has been provided as argument
  We usually run the orchestrations manually as:
  `salt-run state.orchestrate orch.kubernetes`
  And this case was detected properly. This change adds support for also
  detecting the orchestration result when the orchestration is called using the
  `salt-api` on Velum (the general case):
  `salt-run state.orchestrate mods=orch.kubernetes`
  With this change we support both return results.
  Fixes: bsc#1046706</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500033600">- Commit aed8918 by Rafael Fernández López ereslibre@ereslibre.es
  Detect orchestration results when `mods` has been provided as argument
  We usually run the orchestrations manually as:
  `salt-run state.orchestrate orch.kubernetes`
  And this case was detected properly. This change adds support for also
  detecting the orchestration result when the orchestration is called using the
  `salt-api` on Velum (the general case):
  `salt-run state.orchestrate mods=orch.kubernetes`
  With this change we support both return results.
  Fixes: bsc#1046706</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500033601">- Commit a285f00 by Maximilian Meister mmeister@suse.de
  make branch safe by transforming slashes to dashes
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  (cherry picked from commit 49ab27251e452026bee834eb56709180c781a783)
  Commit 7e861b6 by Maximilian Meister mmeister@suse.de
  packaging: make branch configurable
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;
  (cherry picked from commit b0d65b5acc4beea1052e748120fbbf42a8715fc4)</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500379200">- Commit d8db7e0 by Kiall Mac Innes kiall@macinnes.ie
  Handle failues of the update orchestration
  Handle the failure of an update orchestration in the same way we handle a
  failure for a bootstrap orchestration.
  bsc#1047895</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500379201">- Commit 466f6cb by Maximilian Meister mmeister@suse.de
  increase workers (bsc#1048533)
  this allows for more concurrent api requests
  a worker spawns a copy of the velum process
  Signed-off-by: Maximilian Meister &lt;mmeister@suse.de&gt;</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500638400">- Commit 0d7fe16 by Vítor Avelino contact@vitoravelino.me
  bsc#1049165 : avoid orchestration action from ui while updating/adding node
  - When an admin node update is available, do not allow users to press "update
  all nodes". The admin node should be updated first.
  - Never allow both a workers update and an admin update to be started at the
  same time.
  - Velum should not allow add node while a bootstrap/upgrade/etc is in
  progress
- Commit fa31b18 by Vítor Avelino contact@vitoravelino.me
  bsc#1045734: fix show/hide update link based on update/highstate
  - Update all nodes link should be shown if all nodes are in applied
  state and there's an update available/retryable. If for some reason
  a node goes to a different state than "applied" or there's no update,
  link becomes unavailable.</changelog>
  <changelog author="containers-bugowner@suse.de" date="1500984000">- Commit f4c1056 by Kiall Mac Innes kiall@macinnes.ie
  Set VERSION to 1.0.0
  Fixes bsc#1050396</changelog>
</package>
</otherdata>