From: rmccabe@sourceware.org <rmccabe@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] conga ./clustermon.spec.in.in ./conga.spec.in. ...
Date: 25 Oct 2006 18:47:17 -0000 [thread overview]
Message-ID: <20061025184717.18064.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: conga
Changes by: rmccabe at sourceware.org 2006-10-25 18:47:16
Modified files:
. : clustermon.spec.in.in conga.spec.in.in
luci/storage : form-macros
make : version.in
ricci/common : utils.cpp
ricci/modules/service: ServiceManager.cpp
Log message:
sync up changes from the -RHEL5 branch
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/clustermon.spec.in.in.diff?cvsroot=cluster&r1=1.18&r2=1.19
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/conga.spec.in.in.diff?cvsroot=cluster&r1=1.46&r2=1.47
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/luci/storage/form-macros.diff?cvsroot=cluster&r1=1.17&r2=1.18
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/make/version.in.diff?cvsroot=cluster&r1=1.22&r2=1.23
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/ricci/common/utils.cpp.diff?cvsroot=cluster&r1=1.7&r2=1.8
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/ricci/modules/service/ServiceManager.cpp.diff?cvsroot=cluster&r1=1.6&r2=1.7
--- conga/clustermon.spec.in.in 2006/10/16 21:01:40 1.18
+++ conga/clustermon.spec.in.in 2006/10/25 18:47:16 1.19
@@ -194,6 +194,9 @@
%changelog
+* Wed Oct 25 2006 Stanko Kupcevic <kupcevic@redhat.com> 0.8-21
+- 211942: Xenvm moniker must be eradicated
+
* Wed Oct 16 2006 Stanko Kupcevic <kupcevic@redhat.com> 0.8-20
- cluster module: mark services as being xenvms, in status report
--- conga/conga.spec.in.in 2006/10/24 21:54:29 1.46
+++ conga/conga.spec.in.in 2006/10/25 18:47:16 1.47
@@ -282,6 +282,14 @@
%changelog
+* Wed Oct 25 2006 Stanko Kupcevic <kupcevic@redhat.com> 0.8-21
+- 211564: ricci allocates huge memory chunk, causing long swapping
+- 211345: cluster_adapters is missing import of Xenvm module
+- 211191: SELinux issues tracking bug
+- 211370: retrieving log from node fails
+- 211942: Xenvm moniker must be eradicated from UI
+- 211375: unable to reliably create a cluster
+- 211373: reboot node fails from storage tab
* Wed Oct 16 2006 Stanko Kupcevic <kupcevic@redhat.com> 0.8-20
- Minor GUI nits
--- conga/luci/storage/form-macros 2006/10/16 20:57:13 1.17
+++ conga/luci/storage/form-macros 2006/10/25 18:47:16 1.18
@@ -445,17 +445,12 @@
<div metal:use-macro="here/form-macros/macros/single-visible-span"/>
<div metal:use-macro="here/form-macros/macros/form-scripts"/>
- <a tal:define="main_log_URL context/cluster/index_html/absolute_url"
- tal:attributes="href python:main_log_URL + '?nodename=' + storagename + '&pagetype=17'"
+ <a tal:define="main_log_URL context/logs/index_html/absolute_url"
+ tal:attributes="href python:main_log_URL + '?nodename=' + storagename"
onClick="return popup_log(this, 'notes')">
View recent log activity
</a>
<br/>
- <a tal:define="main_reboot_URL python:'./?storagename=' + storagename + '&pagetype=44'"
- tal:attributes="href main_reboot_URL">
- Reboot this machine
- </a>
- <br/>
<br/>
<span tal:omit-tag=""
--- conga/make/version.in 2006/10/24 21:54:29 1.22
+++ conga/make/version.in 2006/10/25 18:47:16 1.23
@@ -1,11 +1,2 @@
-#VERSION=0.9
-#RELEASE=0_TMP_BUILD___WILL_BE_1
-
-# RELEASE has such a strange format just to make sure
-# people notice that version is not completed
-#
-# after version is ready, replace with real release number
-#
-
VERSION=0.8
-RELEASE=20.4
+RELEASE=21
--- conga/ricci/common/utils.cpp 2006/10/23 18:43:35 1.7
+++ conga/ricci/common/utils.cpp 2006/10/25 18:47:16 1.8
@@ -27,6 +27,8 @@
#include <openssl/md5.h>
#include <stdlib.h>
+//#include <iostream>
+
using namespace std;
--- conga/ricci/modules/service/ServiceManager.cpp 2006/10/23 18:43:36 1.6
+++ conga/ricci/modules/service/ServiceManager.cpp 2006/10/25 18:47:16 1.7
@@ -677,7 +677,8 @@
release.find("6") != release.npos)
// TODO: detect FC6
FC6 = true;
- // TODO: detect RHEL5
+ else if (release.find("Tikanga") != release.npos)
+ RHEL5 = true;
release_set = true;
}
next reply other threads:[~2006-10-25 18:47 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 18:47 rmccabe [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-29 19:47 [Cluster-devel] conga ./clustermon.spec.in.in ./conga.spec.in. rmccabe
2008-07-28 17:49 rmccabe
2008-05-12 15:13 rmccabe
2008-04-18 3:31 rmccabe
2008-04-11 6:54 rmccabe
2008-04-11 6:48 rmccabe
2008-04-07 20:11 rmccabe
2008-02-12 17:40 rmccabe
2008-01-29 22:02 rmccabe
2007-08-20 16:23 rmccabe
2007-08-13 19:06 rmccabe
2007-08-09 22:02 rmccabe
2007-08-08 21:24 rmccabe
2007-06-27 7:43 rmccabe
2007-05-01 15:57 rmccabe
2007-04-11 20:15 rmccabe
2007-04-11 19:23 rmccabe
2007-03-20 20:52 kupcevic
2007-02-07 1:36 kupcevic
2007-02-05 22:01 kupcevic
2007-02-05 20:08 rmccabe
2007-02-05 12:12 kupcevic
2007-01-23 22:34 kupcevic
2007-01-17 16:36 kupcevic
2007-01-17 14:57 kupcevic
2007-01-17 14:32 kupcevic
2006-12-13 19:21 kupcevic
2006-12-12 13:53 kupcevic
2006-11-17 20:46 kupcevic
2006-11-17 0:59 kupcevic
2006-11-16 19:35 kupcevic
2006-11-02 0:46 rmccabe
2006-11-01 23:11 kupcevic
2006-11-01 20:43 rmccabe
2006-10-31 20:34 kupcevic
2006-10-25 16:35 kupcevic
2006-10-16 21:01 kupcevic
2006-10-16 15:56 kupcevic
2006-10-04 16:32 kupcevic
2006-09-26 5:21 kupcevic
2006-08-22 23:01 kupcevic
2006-08-22 20:12 kupcevic
2006-08-16 6:34 kupcevic
2006-08-15 4:15 kupcevic
2006-08-09 21:13 kupcevic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061025184717.18064.qmail@sourceware.org \
--to=rmccabe@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).