Re: [ClusterLabs] Pacemaker documentation license clarification
On 12/13/2015 06:56 PM, Ferenc Wagner wrote: > Ken Gaillotwrites: > >> On 12/11/2015 10:07 AM, Ferenc Wagner wrote: >> >>> [...] the "Legal Notice" >>> section of the generated Publican documentation (for example >>> Pacemaker_Explained/desktop/en-US/index.html) says that the material may >>> only be distributed under GFDL-1.2+. >> >> This is an artifact of how you're building the documentation. Easy to >> miss given the makefile complexity :) > > Especially that I did not study the doc makefiles at all, just issued > make. > >> If you look at the generated versions on clusterlabs.org, they have the >> correct license (CC-BY-SA) > > That's great. > >> However if you do not "make brand" before building the documentation, >> you will get the publican defaults. > > Wouldn't --with-brand=clusterlabs also be needed? Anyway, I can't > really do this because of the sudo step. But specifying --brand_dir > helps indeed. Is there any reason not to use the clusterlabs brand > automatically all the time, without installation? It goes like this: Currently, the brand is specified in each book's publican.cfg (which is generated by configure, and can be edited by "make www-cli"). It works, so realistically it's a low priority to improve it, given everything else on the plate. You're welcome to submit a pull request to change it to use the local brand directory. Be sure to consider that each book comes in multiple formats (and potentially translations, though they're out of date at this point, which is a whole separate discussion worth raising at some point), and add anything generated to .gitignore. > --- a/doc/Makefile.am > +++ b/doc/Makefile.am > @@ -73,16 +73,20 @@ EXTRA_DIST= $(docbook:%=%.xml) > %.html: %.txt > $(AM_V_ASCII)$(ASCIIDOC) --unsafe --backend=xhtml11 $< > > +# publican-clusterlabs/xsl/html-single.xsl imports that of Publican > +# through this link during the build > +../xsl: > + ln -s /usr/share/publican/xsl "$@" > > CFS_TXT=$(wildcard Clusters_from_Scratch/en-US/*.txt) > CFS_XML=$(CFS_TXT:%.txt=%.xml) > > # We have to hardcode the book name > # With '%' the test for 'newness' fails > -Clusters_from_Scratch.build: $(PNGS) $(wildcard > Clusters_from_Scratch/en-US/*.xml) $(CFS_XML) > +Clusters_from_Scratch.build: $(PNGS) $(wildcard > Clusters_from_Scratch/en-US/*.xml) $(CFS_XML) ../xsl > $(PCMK_V) @echo Building $(@:%.build=%) because of $? > rm -rf $(@:%.build=%)/publish/* > - $(AM_V_PUB)cd $(@:%.build=%) && RPM_BUILD_DIR="" $(PUBLICAN) build > --publish --langs=$(DOCBOOK_LANGS) --formats=$(DOCBOOK_FORMATS) $(PCMK_quiet) > + $(AM_V_PUB)cd $(@:%.build=%) && RPM_BUILD_DIR="" $(PUBLICAN) build > --publish --langs=$(DOCBOOK_LANGS) --formats=$(DOCBOOK_FORMATS) $(PCMK_quiet) > --brand_dir=../publican-clusterlabs > rm -rf $(@:%.build=%)/tmp > touch $@ > > [...] > ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[ClusterLabs] Antw: Re: SLES11SP4 (crmsh-2.1.2+git49.g2e3fa0e-1.32): problems parsing nodes
Hi! An update: The fix was to delete the nodes and re-create them. CRM shell was happy then, displaying the node like this: --- node h04 \ utilization utl_cpu=200 utl_ram=1200 attributes standby=off --- But when committing the config I got warnings in syslog like this: pengine[25263]:error: crm_int_helper: Characters left over after parsing 'off': 'off' I feel different parts of the cluster stack have different expectations on the syntax... Regards, Ulrich >>> Ulrich Windl schrieb am 14.12.2015 um 08:22 in Nachricht <566E6E49.49E : 161 : 60728>: Kristoffer Grönlundschrieb am 12.12.2015 um 08:43 in > Nachricht <87io443ydc@krigpad.kri.gs>: > > Ulrich Windl writes: > > > >> Hi! > >> > >> "crm configure edit" displays the nodes section in XML like this: > >> > >> xml \ > >>\ > >> \ > >> \ > >>\ > >>\ > >> \ > >>\ > >> > >> > >> In SLES11 SP3 this was not the case... > >> > >> The rest of the config is not displayed in XML, just the nodes. > > > > Hi, > > > > This may be caused by an unrelated problem with the configuration. crmsh > > tries to verify that the CLI syntax truly matches the XML syntax, and > > will revert to displaying the XML if it thinks the representation > > doesn't match. It can get confused in some cases. > > > > You might get more information using > > > > crm -dR configure show h04 > > Thanks for the hint! Tying it I get some message like these: > DEBUG: node!=node: number of children differ > > In Detail it seems the new software wants to see > inside , and does not want to see: > > value="off"> > > So is it too much to expect for an upgrade to fix the XML syntax it it > changed? > (The output of "cibadmin -Q" does not indicate the XML schema being used) > > > > > In general, for problems upgrading from SLES11SP3 to SLES11SP4 I would > > recommend filing issues with SUSE, not upstream. > > It's not "filing an issue"; it's "make people aware" before they run into > the same problems that I did. > > Regards, > Ulrich > > ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[ClusterLabs] Pacemaker 1.1.14 - Release Candidate 3
The source code for the latest Pacemaker release candidate is available at https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.14-rc3 This is a bugfix release: * When deleting an attribute from a fence device, the entire device would sometimes be deleted. * 0f9a4eb0 introduced a regression preventing crm_mon from being run as a daemon. Everyone is encouraged to download, compile and test the new release. Your feedback is important and appreciated. -- Ken Gaillot___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] Antw: Re: Resources start serial, not parralel
Hi Ulrich, thank you for your answer, what about which limits do you talk? The pacemaker software runs by root user, so limits should be increased for root. There is output from one of my server: -bash-4.1# id uid=0(root) gid=0(root) groups=0(root) -bash-4.1# ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 124801 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 4096 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 10240 cpu time (seconds, -t) unlimited max user processes (-u) 124801 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited -bash-4.1# ps -ef |grep pacemaker root 17947 1 0 Dec11 ?00:00:09 pacemakerd 189 17953 17947 0 Dec11 ?00:00:11 /usr/libexec/pacemaker/cib root 17954 17947 0 Dec11 ?00:00:14 /usr/libexec/pacemaker/stonithd root 17955 17947 0 Dec11 ?00:00:11 /usr/libexec/pacemaker/lrmd 189 17956 17947 0 Dec11 ?00:00:09 /usr/libexec/pacemaker/attrd 189 17957 17947 0 Dec11 ?00:00:09 /usr/libexec/pacemaker/pengine root 17958 17947 0 Dec11 ?00:00:16 /usr/libexec/pacemaker/crmd With settings in pacemaker or system can be changed for start heavy application ( java ) at the same time? 2015-12-14 16:29 GMT+09:00 Ulrich Windl: > Hi! > > There is one feature in Linux that may affect you: If processes block on > I/O (NFS also), the load increases, and the load is the _sum_, and not the > _average_ of all CPUs. So if you have many CPUs, your abservable load will > typically increase. Recently we had a load of 60, but nobody actually > noticed ;-) > > So maybe you just need to adjust the limits for pacemaker... > > Regards, > Ulrich > > >>> Oleg Ilyin schrieb am 13.12.2015 um 15:00 in > Nachricht >