commit velum for openSUSE:Factory
Hello community, here is the log from the commit of package velum for openSUSE:Factory checked in at 2018-04-27 16:10:11 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/velum (Old) and /work/SRC/openSUSE:Factory/.velum.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Package is "velum" Fri Apr 27 16:10:11 2018 rev:24 rq:601890 version:3.0.0+dev+git_r738_10fcaf450fd1ac030569f55335e6ba1f31662c8e Changes: -------- --- /work/SRC/openSUSE:Factory/velum/velum.changes 2018-04-22 14:40:40.882705992 +0200 +++ /work/SRC/openSUSE:Factory/.velum.new/velum.changes 2018-04-27 16:10:13.572301791 +0200 @@ -1,0 +2,33 @@ +Fri Apr 27 12:05:14 UTC 2018 - containers-bugowner@suse.de + +- Commit 162c0d0 by Liam Proven lproven@suse.com + Reword force-removal warning as per IRC #docker discussion + + +------------------------------------------------------------------- +Fri Apr 27 09:08:40 UTC 2018 - containers-bugowner@suse.de + +- Commit 01fe462 by MalloZup dmaiocchi@suse.com + change link to actual one + + +------------------------------------------------------------------- +Thu Apr 26 10:02:52 UTC 2018 - containers-bugowner@suse.de + +- Commit 310d614 by Vítor Avelino vavelino@suse.com + node removal: improved way of showing removal links + + 'Remove' and 'Force remove' links were being shown at the same time so far. + But 'Force remove' only makes sense to be shown when a previous removal has + failed. + + With this we are showing only one link at a time. When the highstate of a + minion is fine, we show 'Remove'. Whenever it comes 'removal_failed', we show + 'Force remove'. + + enhancemente#node-removal + + Signed-off-by: Vítor Avelino <vavelino@suse.com> + + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ velum.spec ++++++ --- /var/tmp/diff_new_pack.1YXFj6/_old 2018-04-27 16:10:14.428270399 +0200 +++ /var/tmp/diff_new_pack.1YXFj6/_new 2018-04-27 16:10:14.428270399 +0200 @@ -23,7 +23,7 @@ # Version: 1.0.0 # %%define branch 1.0.0 -Version: 3.0.0+dev+git_r734_f7dc070fb3c2fa61475e52ed2fb91ca204727921 +Version: 3.0.0+dev+git_r738_10fcaf450fd1ac030569f55335e6ba1f31662c8e Release: 0 %define branch master Summary: Dashboard for CaasP @@ -96,7 +96,7 @@ %description velum is the dashboard for CaasP to manage and deploy kubernetes clusters on top of MicroOS -This package has been built with commit f7dc070fb3c2fa61475e52ed2fb91ca204727921 from branch master on date Fri, 20 Apr 2018 11:31:38 +0000 +This package has been built with commit 10fcaf450fd1ac030569f55335e6ba1f31662c8e from branch master on date Fri, 27 Apr 2018 12:04:35 +0000 %prep %setup -q -n velum-%{branch} ++++++ master.tar.gz ++++++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/velum-master/README.md new/velum-master/README.md --- old/velum-master/README.md 2018-04-20 13:31:45.000000000 +0200 +++ new/velum-master/README.md 2018-04-27 14:05:40.000000000 +0200 @@ -39,7 +39,7 @@ ## Development -You can start a Velum development environment by following the instructions in [caasp-devenv](https://github.com/kubic-project/caasp-devenv). +You can start a Velum development environment by following the instructions in [caasp-devenv](https://github.com/kubic-project/automation#caasp-devenv). ## Licensing diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/velum-master/app/views/dashboard/modals/_warn_node_force_removal_modal.html.slim new/velum-master/app/views/dashboard/modals/_warn_node_force_removal_modal.html.slim --- old/velum-master/app/views/dashboard/modals/_warn_node_force_removal_modal.html.slim 2018-04-20 13:31:45.000000000 +0200 +++ new/velum-master/app/views/dashboard/modals/_warn_node_force_removal_modal.html.slim 2018-04-27 14:05:40.000000000 +0200 @@ -8,10 +8,16 @@ h4#modal-label.modal-title | Forced node removal .modal-body - p You are about to force remove a node from the cluster. This means that... (more info here) - p Only proceed with this operation if you really know what you are doing. + p You are about to forcibly remove a node from the cluster. This action cannot be reversed. + p Any data on this node will be lost and the machine must be re-installed before it can be + p added back. + p + p The operation will perform some basic tasks to maintain the coherence of the cluster, but + p it may not function normally afterwards. + p + p Only proceed with this operation if you are certain it is essential to do so. .modal-footer button.btn.btn-default data-dismiss="modal" type="button" | Cancel button.btn.btn-primary.force-remove-anyway type="button" - | Proceed anyway \ No newline at end of file + | Proceed with forcible removal
participants (1)
-
root@hilbert.suse.de