<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Confluent_1.1_Release_Notes</title><link>https://sourceforge.net/p/xcat/wiki/Confluent_1.1_Release_Notes/</link><description>Recent changes to Confluent_1.1_Release_Notes</description><atom:link href="https://sourceforge.net/p/xcat/wiki/Confluent_1.1_Release_Notes/feed" rel="self"/><language>en</language><lastBuildDate>Wed, 25 Mar 2015 13:53:15 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/xcat/wiki/Confluent_1.1_Release_Notes/feed" rel="self" type="application/rss+xml"/><item><title>Confluent_1.1_Release_Notes modified by Jarrod Johnson</title><link>https://sourceforge.net/p/xcat/wiki/Confluent_1.1_Release_Notes/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v4
+++ v5
@@ -3,12 +3,13 @@
 * Sensor data is now available (/nodes/&amp;lt;node&amp;gt;/sensors/)
 * Noderanges are (mostly) implemented
     * Can do multi-numbered ranges, e.g. 'r1u1-r10u10', which xCAT can not do
-    * Not yet implemented: regex name, regex config match, and strict config match operators
+    * Also added pagination: &amp;lt;n Skips="" 'n'="" nodes="" into="" the="" range,=""&amp;gt;x limits matches to x
     * Implemented in the API tree as '/noderange/' with members that auto-vivify (sort of like automount)
-         * `/noderange/n1-n8/`
-         * `/noderange/n[1-8]/`
-         * `/noderange/compute@rack1/`
-         * `/noderange/rack1,rack2/`
+         * `/noderange/n1-n8/` (n1 through n8)
+         * `/noderange/n[1-8]/` (same as above)
+         * `/noderange/compute@rack1/` (nodes both in compute and rack1)
+         * `/noderange/rack1,rack2/` (rack1 and rack2, multiple groups)
+         * `/noderange/compute&amp;lt;50&amp;gt;25/` (skip first 50, show 25 nodes in compute group)
 * Dynamic nodegroups, members defined as a noderange evaluated on the fly
 * xCAT style commands that go straight to confluent (named so as not to conflict)
     * nodepower (like rpower)
@@ -22,6 +23,7 @@
 * Valid PAM users are no longer allowed unless they *also* have a /users/ entry in confluent.  No password is needed for the entry, password is verified by PAM and not confluent in this mode.
 * stdout/stderr logs now report the source of any data that comes in
 * Set identify LED is implemented
+* node collections are now sorted when enumerated

 ## Fixes
 * Various issues with handling UTF-8 data
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jarrod Johnson</dc:creator><pubDate>Wed, 25 Mar 2015 13:53:15 -0000</pubDate><guid>https://sourceforge.nete019358f4eb55ac3d57699bd6dee94971ac2fdcc</guid></item><item><title>Confluent_1.1_Release_Notes modified by Jarrod Johnson</title><link>https://sourceforge.net/p/xcat/wiki/Confluent_1.1_Release_Notes/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v3
+++ v4
@@ -16,9 +16,9 @@
     * nodeidentify (like rbeacon)
     * nodehealth (new concept, summarize health of nodes)
 * nodesensors offers more powerful tools for gathering data
-  * Can specify interval and data points for controlled data collection
-  * Can specify csv output
-  * Default behavior is similar to 'rvitals'
+    * Can specify interval and data points for controlled data collection
+    * Can specify csv output
+    * Default behavior is similar to 'rvitals'
 * Valid PAM users are no longer allowed unless they *also* have a /users/ entry in confluent.  No password is needed for the entry, password is verified by PAM and not confluent in this mode.
 * stdout/stderr logs now report the source of any data that comes in
 * Set identify LED is implemented
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jarrod Johnson</dc:creator><pubDate>Fri, 20 Mar 2015 20:17:32 -0000</pubDate><guid>https://sourceforge.netc8666a1f80a20d5b781fea013d5609bf29a11036</guid></item><item><title>Confluent_1.1_Release_Notes modified by Jarrod Johnson</title><link>https://sourceforge.net/p/xcat/wiki/Confluent_1.1_Release_Notes/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v2
+++ v3
@@ -11,10 +11,10 @@
          * `/noderange/rack1,rack2/`
 * Dynamic nodegroups, members defined as a noderange evaluated on the fly
 * xCAT style commands that go straight to confluent (named so as not to conflict)
-  * nodepower (like rpower)
-  * nodesetboot (like rsetboot)
-  * nodeidentify (like rbeacon)
-  * nodehealth (new concept, summarize health of nodes)
+    * nodepower (like rpower)
+    * nodesetboot (like rsetboot)
+    * nodeidentify (like rbeacon)
+    * nodehealth (new concept, summarize health of nodes)
 * nodesensors offers more powerful tools for gathering data
   * Can specify interval and data points for controlled data collection
   * Can specify csv output
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jarrod Johnson</dc:creator><pubDate>Fri, 20 Mar 2015 20:17:18 -0000</pubDate><guid>https://sourceforge.net3681f7d6fa2171a54062d6ee52cc9f3e20e00680</guid></item><item><title>Confluent_1.1_Release_Notes modified by Jarrod Johnson</title><link>https://sourceforge.net/p/xcat/wiki/Confluent_1.1_Release_Notes/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v1
+++ v2
@@ -2,13 +2,13 @@
 * CLI clients now stay 'connected' through a server restart (confetty at prompt or running console).
 * Sensor data is now available (/nodes/&amp;lt;node&amp;gt;/sensors/)
 * Noderanges are (mostly) implemented
-  * Can do multi-numbered ranges, e.g. 'r1u1-r10u10', which xCAT can not do
-  * Not yet implemented: regex name, regex config match, and strict config match operators
-  * Implemented in the API tree as '/noderange/' with members that auto-vivify (sort of like automount)
-     * `/noderange/n1-n8/`
-     * `/noderange/n[1-8]/`
-     * `/noderange/compute@rack1/`
-     * `/noderange/rack1,rack2/`
+    * Can do multi-numbered ranges, e.g. 'r1u1-r10u10', which xCAT can not do
+    * Not yet implemented: regex name, regex config match, and strict config match operators
+    * Implemented in the API tree as '/noderange/' with members that auto-vivify (sort of like automount)
+         * `/noderange/n1-n8/`
+         * `/noderange/n[1-8]/`
+         * `/noderange/compute@rack1/`
+         * `/noderange/rack1,rack2/`
 * Dynamic nodegroups, members defined as a noderange evaluated on the fly
 * xCAT style commands that go straight to confluent (named so as not to conflict)
   * nodepower (like rpower)
@@ -35,4 +35,3 @@
 * More specifically indicate a remote system 'timeout' condition to client
 * HTTP API now tolerates invalid cookies that may leak in from another site in the same domain
 * Configuration change handlers could induce errors to clients that aren't trying to care about the handlers.  This is addressed by redirecting those errors to the trace log.
-* 
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jarrod Johnson</dc:creator><pubDate>Fri, 20 Mar 2015 20:16:57 -0000</pubDate><guid>https://sourceforge.netf3bed43fdf23a40d0f1316c3a4b603e9a135983f</guid></item><item><title>Confluent_1.1_Release_Notes modified by Jarrod Johnson</title><link>https://sourceforge.net/p/xcat/wiki/Confluent_1.1_Release_Notes/</link><description>&lt;div class="markdown_content"&gt;&lt;h2 id="new-featuresmodified-behavior"&gt;New features/Modified behavior&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;CLI clients now stay 'connected' through a server restart (confetty at prompt or running console).&lt;/li&gt;
&lt;li&gt;Sensor data is now available (/nodes/&amp;lt;node&amp;gt;/sensors/)&lt;/li&gt;
&lt;li&gt;Noderanges are (mostly) implemented&lt;/li&gt;
&lt;li&gt;Can do multi-numbered ranges, e.g. 'r1u1-r10u10', which xCAT can not do&lt;/li&gt;
&lt;li&gt;Not yet implemented: regex name, regex config match, and strict config match operators&lt;/li&gt;
&lt;li&gt;Implemented in the API tree as '/noderange/' with members that auto-vivify (sort of like automount)&lt;ul&gt;
&lt;li&gt;&lt;code&gt;/noderange/n1-n8/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;/noderange/n[1-8]/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;/noderange/compute@rack1/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;/noderange/rack1,rack2/&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Dynamic nodegroups, members defined as a noderange evaluated on the fly&lt;/li&gt;
&lt;li&gt;xCAT style commands that go straight to confluent (named so as not to conflict)&lt;/li&gt;
&lt;li&gt;nodepower (like rpower)&lt;/li&gt;
&lt;li&gt;nodesetboot (like rsetboot)&lt;/li&gt;
&lt;li&gt;nodeidentify (like rbeacon)&lt;/li&gt;
&lt;li&gt;nodehealth (new concept, summarize health of nodes)&lt;/li&gt;
&lt;li&gt;nodesensors offers more powerful tools for gathering data&lt;/li&gt;
&lt;li&gt;Can specify interval and data points for controlled data collection&lt;/li&gt;
&lt;li&gt;Can specify csv output&lt;/li&gt;
&lt;li&gt;Default behavior is similar to 'rvitals'&lt;/li&gt;
&lt;li&gt;Valid PAM users are no longer allowed unless they &lt;em&gt;also&lt;/em&gt; have a /users/ entry in confluent.  No password is needed for the entry, password is verified by PAM and not confluent in this mode.&lt;/li&gt;
&lt;li&gt;stdout/stderr logs now report the source of any data that comes in&lt;/li&gt;
&lt;li&gt;Set identify LED is implemented&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="fixes"&gt;Fixes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Various issues with handling UTF-8 data&lt;/li&gt;
&lt;li&gt;More robust handling of shellmodule plugins&lt;/li&gt;
&lt;li&gt;Address some errors that were logged but no failure sent to client&lt;/li&gt;
&lt;li&gt;nodegroup requests without trailing '/' no longer fail&lt;/li&gt;
&lt;li&gt;Improved handling of console plugin exceptions&lt;/li&gt;
&lt;li&gt;Connected client count no longer goes negative&lt;/li&gt;
&lt;li&gt;Fix confetty behavior when not outputting straight to terminal&lt;/li&gt;
&lt;li&gt;Confluent no longer fails to work on ppc64&lt;/li&gt;
&lt;li&gt;More specifically indicate a remote system 'timeout' condition to client&lt;/li&gt;
&lt;li&gt;HTTP API now tolerates invalid cookies that may leak in from another site in the same domain&lt;/li&gt;
&lt;li&gt;Configuration change handlers could induce errors to clients that aren't trying to care about the handlers.  This is addressed by redirecting those errors to the trace log.&lt;/li&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jarrod Johnson</dc:creator><pubDate>Fri, 20 Mar 2015 20:14:25 -0000</pubDate><guid>https://sourceforge.neta7f3f6660ccc4002c6a88084d37e0761d7481099</guid></item></channel></rss>