Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://collaborationben.com/feed/

  1. <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
  2. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  3. xmlns:wfw="http://wellformedweb.org/CommentAPI/"
  4. xmlns:dc="http://purl.org/dc/elements/1.1/"
  5. xmlns:atom="http://www.w3.org/2005/Atom"
  6. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  7. xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
  8. xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
  9. >
  10.  
  11. <channel>
  12. <title>collaborationben</title>
  13. <atom:link href="https://collaborationben.com/feed/" rel="self" type="application/rss+xml" />
  14. <link>https://collaborationben.com</link>
  15. <description>A blog on Sametime, Connections, Portal and more</description>
  16. <lastBuildDate>Fri, 21 Jul 2017 13:41:18 +0000</lastBuildDate>
  17. <language>en</language>
  18. <sy:updatePeriod>hourly</sy:updatePeriod>
  19. <sy:updateFrequency>1</sy:updateFrequency>
  20. <generator>http://wordpress.com/</generator>
  21. <cloud domain='collaborationben.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
  22. <image>
  23. <url>https://s2.wp.com/i/buttonw-com.png</url>
  24. <title>collaborationben</title>
  25. <link>https://collaborationben.com</link>
  26. </image>
  27. <atom:link rel="search" type="application/opensearchdescription+xml" href="https://collaborationben.com/osd.xml" title="collaborationben" />
  28. <atom:link rel='hub' href='https://collaborationben.com/?pushpress=hub'/>
  29. <item>
  30. <title>Limiting resources used by IBM Cloud private and Orient Me</title>
  31. <link>https://collaborationben.com/2017/07/04/limiting-resources-used-by-ibm-cloud-private-and-orient-me/</link>
  32. <comments>https://collaborationben.com/2017/07/04/limiting-resources-used-by-ibm-cloud-private-and-orient-me/#comments</comments>
  33. <pubDate>Tue, 04 Jul 2017 15:26:29 +0000</pubDate>
  34. <dc:creator><![CDATA[collaborationben]]></dc:creator>
  35. <category><![CDATA[Uncategorized]]></category>
  36. <category><![CDATA[cfc]]></category>
  37. <category><![CDATA[ibmcnx]]></category>
  38. <category><![CDATA[ibmconnections]]></category>
  39. <category><![CDATA[ICp]]></category>
  40. <category><![CDATA[kubernetes]]></category>
  41. <category><![CDATA[orientme]]></category>
  42. <category><![CDATA[replicasets]]></category>
  43. <category><![CDATA[statefulsets]]></category>
  44.  
  45. <guid isPermaLink="false">http://collaborationben.com/?p=876</guid>
  46. <description><![CDATA[IBM Conductor for Containers has been rebranded IBM Cloud private with version 1.2.0 (https://www.ibm.com/developerworks/community/blogs/fe25b4ef-ea6a-4d86-a629-6f87ccf4649e/entry/IBM_Cloud_private_formerly_IBM_Spectrum_Conductor_for_Containers_version_1_2_0_is_now_available?lang=en) IBM released version 6.0.0.1 of Orient Me and with it added new applications increasing the total amount of pods in play. Each pod requires some resources to run. Recently there has been some frustration for those who work with Connections trying [&#8230;]<img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=876&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
  47. <content:encoded><![CDATA[<p>IBM Conductor for Containers has been rebranded IBM Cloud private with version 1.2.0 (<a href="https://www.ibm.com/developerworks/community/blogs/fe25b4ef-ea6a-4d86-a629-6f87ccf4649e/entry/IBM_Cloud_private_formerly_IBM_Spectrum_Conductor_for_Containers_version_1_2_0_is_now_available?lang=en" rel="nofollow">https://www.ibm.com/developerworks/community/blogs/fe25b4ef-ea6a-4d86-a629-6f87ccf4649e/entry/IBM_Cloud_private_formerly_IBM_Spectrum_Conductor_for_Containers_version_1_2_0_is_now_available?lang=en</a>)</p>
  48. <p>IBM released version 6.0.0.1 of Orient Me and with it added new applications increasing the total amount of pods in play. Each pod requires some resources to run. Recently there has been some frustration for those who work with Connections trying to get Orient Me up and running on smaller servers for testing purposes or for deployment to SMB customers.</p>
  49. <p>I spent some time looking at how to limit the resources consumed by decreasing the number of pods.</p>
  50. <p>Kubernetes allows you to scale up or down your pods. This can be done on the command line or via the UI</p>
  51. <p><a href="https://collaborationben.files.wordpress.com/2017/07/scale.jpg" target="_blank" rel="noopener"><img data-attachment-id="877" data-permalink="https://collaborationben.com/2017/07/04/limiting-resources-used-by-ibm-cloud-private-and-orient-me/scale/#main" data-orig-file="https://collaborationben.files.wordpress.com/2017/07/scale.jpg?w=776" data-orig-size="235,369" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}" data-image-title="scale" data-image-description="" data-medium-file="https://collaborationben.files.wordpress.com/2017/07/scale.jpg?w=776?w=191" data-large-file="https://collaborationben.files.wordpress.com/2017/07/scale.jpg?w=776?w=235" class="alignnone wp-image-877 size-full" src="https://collaborationben.files.wordpress.com/2017/07/scale.jpg?w=776" alt="" srcset="https://collaborationben.files.wordpress.com/2017/07/scale.jpg 235w, https://collaborationben.files.wordpress.com/2017/07/scale.jpg?w=96 96w" sizes="(max-width: 235px) 100vw, 235px"   /></a></p>
  52. <p>Since I prefer the command line here is how you scale an application and it&#8217;s effect on the number of pods. There are two ways in which this is done, by Replica Sets and Stateful Sets. I won&#8217;t go into the difference of both because I&#8217;m not even wholly sure myself but suffice to say that most of OM applications use Replica Sets.</p>
  53. <h3>Replica Sets</h3>
  54. <p>I&#8217;m using analysisservice as an example because it is at the top when commands are run.</p>
  55. <p># kubectl get pods<br />
  56. NAME                                                   READY STATUS RESTARTS AGE<br />
  57. analysisservice-1093785398-31ks2 1/1        Running        0             8m<br />
  58. analysisservice-1093785398-hf90j 1/1        Running        0             8m</p>
  59. <p># kubectl get rs<br />
  60. NAME                                        DESIRED CURRENT READY AGE<br />
  61. analysisservice-1093785398 2                 2                   2            9m</p>
  62. <p>The following command tells K8s to change the number of pods to be 1 that will accept load.</p>
  63. <p># kubectl scale &#8211;replicas=1 rs/analysisservice-1093785398<br />
  64. replicaset &#8220;analysisservice-1093785398&#8221; scaled</p>
  65. <p>Below shows that just the one pod is ready to accept load. Note that the desired number is two. This means that this will be the default value if all the pods are deleted or the OS restarted.</p>
  66. <p># kubectl get rs<br />
  67. NAME                                        DESIRED CURRENT READY AGE<br />
  68. analysisservice-1093785398 2                 2                   1            9m</p>
  69. <p>The pod that is going to not accept load is destroyed and a new one replaces it.</p>
  70. <p># kubectl get pods<br />
  71. NAME                                                   READY STATUS                  RESTARTS AGE<br />
  72. analysisservice-1093785398-31ks2 1/1        Running                  0                   18m<br />
  73. analysisservice-1093785398-4njpn 1/1       Terminating           0                    5m<br />
  74. analysisservice-1093785398-fmnrd 0/1     ContainerCreating 0                   3s</p>
  75. <p>You can see that the new pod is not &#8220;ready&#8221; and thus not accepting any load.</p>
  76. <p># kubectl get pods<br />
  77. NAME                                                   READY STATUS RESTARTS AGE<br />
  78. analysisservice-1093785398-31ks2 1/1        Running 0                   19m<br />
  79. analysisservice-1093785398-fmnrd 0/1      Running 0                   43s</p>
  80. <p>The reverse is true and you can scale the number of pods upwards. ICp can do this with policies based on CPU usage creating more pods and then decreasing them when the load drops.</p>
  81. <p>The above approach does not persist over OS restarts or deletion of all the pods. To persist these changes the following steps need to be followed.</p>
  82. <p># kubectl get deployment<br />
  83. NAME               DESIRED CURRENT UP-TO-DATE AVAILABLE AGE<br />
  84. analysisservice 2                2                   2                        2                      34m</p>
  85. <p>This command amends the deployment configuration which was set in complete.6_0.yaml in the OM binaries.</p>
  86. <p># kubectl edit deployment analysisservice<br />
  87. apiVersion: extensions/v1beta1<br />
  88. kind: Deployment</p>
  89. <p>This will open in vi though you can change your editor if you prefer. Under the spec section you want to amend the number of replicas</p>
  90. <p>spec:<br />
  91. <strong>replicas: 1</strong><br />
  92. selector:<br />
  93. matchLabels:<br />
  94. mService: analysisservice<br />
  95. name: analysisservice<br />
  96. strategy:<br />
  97. rollingUpdate:<br />
  98. maxSurge: 1<br />
  99. maxUnavailable: 1</p>
  100. <p>Ignore the status section. Save and close (:wq)</p>
  101. <p># kubectl get deployment<br />
  102. NAME                    DESIRED CURRENT UP-TO-DATE AVAILABLE AGE<br />
  103. analysisservice      1                   1                   1                      1                       44m</p>
  104. <p>This time the second pod is not listed with a 0/1 ready value. The second pod has been deleted.</p>
  105. <p># kubectl get pods<br />
  106. NAME                                                     READY STATUS RESTARTS AGE<br />
  107. analysisservice-1093785398-kz76m 1/1        Running  0                   17m</p>
  108. <p>You can use the following command to open all application deployments and update using vi all the applications at one time.</p>
  109. <p># kubectl edit deployment</p>
  110. <p>When you save and close the applications will be updated in line the values you set for the replicas.</p>
  111. <p># kubectl get deployment<br />
  112. NAME                                    DESIRED CURRENT UP-TO-DATE AVAILABLE AGE<br />
  113. analysisservice                     1                  1                   1                         1                      55m<br />
  114. haproxy                                 1                  1                   1                         1                      57m<br />
  115. indexingservice                   1                  1                   1                         1                      55m<br />
  116. itm-services                         1                  1                   1                         1                      55m<br />
  117. mail-service                        1                  1                   1                          1                     55m<br />
  118. orient-webclient                1                  1                   1                         1                      55m<br />
  119. people-migrate                  1                  1                   1                         1                      55m<br />
  120. people-relation                  1                  1                   1                         1                      55m<br />
  121. people-scoring                   1                  1                   1                         1                      55m<br />
  122. redis-sentinel                     1                  1                   1                         1                      57m<br />
  123. retrievalservice                  1                  1                   1                         1                      55m<br />
  124. solr1                                     1                  1                   1                         1                      57m<br />
  125. solr2                                    1                  1                   1                         1                      57m<br />
  126. solr3                                    1                  1                   1                         1                      57m<br />
  127. zookeeper-controller-1   1                  1                   1                         1                      57m<br />
  128. zookeeper-controller-2  1                  1                   1                         1                      57m<br />
  129. zookeeper-controller-3  1                  1                   1                         1                      57m</p>
  130. <p>To delete the additional solr and zookeper-controller pods you needs to run the following.</p>
  131. <p># kubectl delete deployment zookeeper-controller-2 zookeeper-controller-3<br />
  132. # kubectl delete deployment solr2 solr3</p>
  133. <p>Running the following shows the number of pods have decreased by quite a lot.</p>
  134. <p># kubectl get pods</p>
  135. <p>Checking the ReplicaSets again shows the values have decreased.</p>
  136. <p># kubectl get rs</p>
  137. <p>Mongo and redis-server do not use Replica Sets, they use StatefulSets.</p>
  138. <h3>StatefulSets</h3>
  139. <p>The following command shows that there are 3 pods for each application.</p>
  140. <p># kubectl get statefulsets<br />
  141. NAME          DESIRED CURRENT AGE<br />
  142. mongo          3                 3                  1h<br />
  143. redis-server 3                 3                  1h</p>
  144. <p>In the same vain as before you edit the replicas decreasing/increasing them as you see fit.</p>
  145. <p># kubectl edit statefulsets<br />
  146. statefulset &#8220;mongo&#8221; edited<br />
  147. statefulset &#8220;redis-server&#8221; edited</p>
  148. <p>The end result is that only the one ReplicaSet is configured.</p>
  149. <p># kubectl get statefulsets<br />
  150. NAME          DESIRED CURRENT AGE<br />
  151. mongo          1                 1                  1h<br />
  152. redis-server 1                 1                  1h</p>
  153. <p>The effect is seen when you list the pods.</p>
  154. <p># kubectl get pods<br />
  155. NAME              READY STATUS RESTARTS AGE<br />
  156. mongo-0          2/2        Running 0                   1h<br />
  157. redis-server-0 1/1         Running 0                   1h</p>
  158. <h3>At install time</h3>
  159. <p>These changes can be made at install time by updating the various .yml files in /microservices/hybridcloud/templates/* and /microservices/hybridcloud/templates/complete.6_0.yaml and then running install.sh.</p>
  160. <h3>Finally</h3>
  161. <p>I have only experimented on the default applications and have not touched those from the kube-system namespace which are the ICp applications and not OM specific.</p>
  162. <p>I haven&#8217;t tried this on a working system yet, purely a detached single node running all roles with hostpath configuration.</p>
  163. <p>Since there is no load on the server my measurements with regards to resources consumed pre and post changes is far from scientific but looking at the UI the amount of CPU and memory is certainly less then previously used.</p>
  164. <p>I have no idea as yet whether this will break OM but I will persist and see whether it does or whether it works swimmingly. If anyone tries this out then please feedback to me.</p>
  165. <p>BTW &#8211; I restarted the OS and had a couple of problems with analysisservice and indexingservice pods not being ready and shown as unhealthy but after deleting haproxy, redis-server-0 and redis-sentinel all my pods are showing as healthy.</p>
  166. <p>IBM, please please provide a relatively simple way (ideally at install time) for us to cut the deployment down to bare bones maybe a small, medium or large deployment as you do with traditional Connections?</p>
  167. <h3>Update 05/07/2017</h3>
  168. <p>Once I integrated the server with a working Connections 6.0 server with latest fixes applied the ITM bar did not work. <a href="https://twitter.com/nmeisenzahl" target="_blank" rel="noopener">Nico Meisenzahl</a> has also been looking into this and we hope to have a working set up soon</p>
  169. <h3>Update 07/07/2017</h3>
  170. <p>Nico created a great <a href="https://meisenzahl.org/2017/07/06/downsizing-orient-me/" target="_blank" rel="noopener">blog </a>updating the yml files to decrease the amount of pods/containers during installation of Orient Me.</p><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/collaborationben.wordpress.com/876/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/collaborationben.wordpress.com/876/" /></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=876&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
  171. <wfw:commentRss>https://collaborationben.com/2017/07/04/limiting-resources-used-by-ibm-cloud-private-and-orient-me/feed/</wfw:commentRss>
  172. <slash:comments>8</slash:comments>
  173. <media:content url="http://1.gravatar.com/avatar/73d65d70497b3486650a324a0d88ecf1?s=96&#38;d=identicon&#38;r=G" medium="image">
  174. <media:title type="html">collaborationben</media:title>
  175. </media:content>
  176.  
  177. <media:content url="http://collaborationben.files.wordpress.com/2017/07/scale.jpg" medium="image" />
  178. </item>
  179. <item>
  180. <title>IBM Connections Files plugin not working within Notes when TLSv1.2 is enforced</title>
  181. <link>https://collaborationben.com/2017/06/19/ibm-connections-files-plugin-not-working-within-notes-when-tlsv1-2-is-enforced/</link>
  182. <comments>https://collaborationben.com/2017/06/19/ibm-connections-files-plugin-not-working-within-notes-when-tlsv1-2-is-enforced/#respond</comments>
  183. <pubDate>Mon, 19 Jun 2017 14:46:44 +0000</pubDate>
  184. <dc:creator><![CDATA[collaborationben]]></dc:creator>
  185. <category><![CDATA[Uncategorized]]></category>
  186. <category><![CDATA[files]]></category>
  187. <category><![CDATA[ibmcnx]]></category>
  188. <category><![CDATA[ibmconnections]]></category>
  189. <category><![CDATA[IBMNotes]]></category>
  190. <category><![CDATA[ihs]]></category>
  191. <category><![CDATA[Notes]]></category>
  192. <category><![CDATA[plugin]]></category>
  193. <category><![CDATA[TLSv1.2]]></category>
  194.  
  195. <guid isPermaLink="false">http://collaborationben.com/?p=866</guid>
  196. <description><![CDATA[After enforcing TLSv1.2 on our internal Connections 5.5 servers the Files plugin would not work. In the IHS logs I would see errors such as [warn] [client 80.229.222.90] [7f9a700a7060] [21173] SSL0222W: SSL Handshake Failed, No ciphers specified (no shared ciphers or no shared protocols). [xx.xx.xx.xx:62899 -&#62; xxx.xxx.xxx.xxx:443] [09:45:11.000102454] 0ms Enabling trace on IHS showed that [&#8230;]<img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=866&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
  197. <content:encoded><![CDATA[<p>After enforcing TLSv1.2 on our internal Connections 5.5 servers the Files plugin would not work.</p>
  198. <p><a href="https://collaborationben.files.wordpress.com/2017/06/files1.jpg" target="_blank" rel="noopener"><img data-attachment-id="867" data-permalink="https://collaborationben.com/2017/06/19/ibm-connections-files-plugin-not-working-within-notes-when-tlsv1-2-is-enforced/files1/#main" data-orig-file="https://collaborationben.files.wordpress.com/2017/06/files1.jpg?w=776" data-orig-size="271,298" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}" data-image-title="files1" data-image-description="" data-medium-file="https://collaborationben.files.wordpress.com/2017/06/files1.jpg?w=776?w=271" data-large-file="https://collaborationben.files.wordpress.com/2017/06/files1.jpg?w=776?w=271" class="alignnone wp-image-867 size-full" src="https://collaborationben.files.wordpress.com/2017/06/files1.jpg?w=776" alt="" srcset="https://collaborationben.files.wordpress.com/2017/06/files1.jpg 271w, https://collaborationben.files.wordpress.com/2017/06/files1.jpg?w=136 136w" sizes="(max-width: 271px) 100vw, 271px"   /></a></p>
  199. <p>In the IHS logs I would see errors such as</p>
  200. <p>[warn] [client 80.229.222.90] [7f9a700a7060] [21173] SSL0222W: SSL Handshake Failed, No ciphers specified (no shared ciphers or no shared protocols). [xx.xx.xx.xx:62899 -&gt; xxx.xxx.xxx.xxx:443] [09:45:11.000102454] 0ms</p>
  201. <p>Enabling trace on IHS showed that the protocol being used was TLSv1.0 which matched Wireshark output. Oddly Status Updates and Activities plugins use TLSv1.2.</p>
  202. <p>&#8220;GET /files/basic/api/library/4a7a7240-8f68-44d8-9447-7410cc2bb467/feed?pageSize=300&amp;acls=true&amp;sI=601 HTTP/1.1&#8221; 200 168770 TLS_RSA_WITH_AES_128_CBC_SHA <strong>TLSV1</strong></p>
  203. <p>I then had to allow TLSv1.0 until I could get an explanation from IBM.</p>
  204. <p>Finally IBM came back with the following two lines to be added to the notes.ini.</p>
  205. <p>SSL_DISABLE_TLS_10<br />
  206. DISABLE_SSLV3=1</p>
  207. <p>Now in access_log I see TLSv1.2 being used.</p>
  208. <p>&#8220;GET /files/basic/api/library/4a7a7240-8f68-44d8-9447-7410cc2bb467/feed?pageSize=300&amp;acls=true&amp;sI=601 HTTP/1.1&#8221; 200 168770 TLS_RSA_WITH_AES_128_GCM_SHA256 <strong>TLSV1.2</strong></p>
  209. <p>IBM also suggested that I check the following was set in plugin_customization.ini, which it was.</p>
  210. <p>com.ibm.documents.connector.service/ENABLE_SSL=true</p>
  211. <p>The notes.ini values have been pushed out to my colleagues via Domino policies.</p><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/collaborationben.wordpress.com/866/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/collaborationben.wordpress.com/866/" /></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=866&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
  212. <wfw:commentRss>https://collaborationben.com/2017/06/19/ibm-connections-files-plugin-not-working-within-notes-when-tlsv1-2-is-enforced/feed/</wfw:commentRss>
  213. <slash:comments>0</slash:comments>
  214. <media:content url="http://1.gravatar.com/avatar/73d65d70497b3486650a324a0d88ecf1?s=96&#38;d=identicon&#38;r=G" medium="image">
  215. <media:title type="html">collaborationben</media:title>
  216. </media:content>
  217.  
  218. <media:content url="http://collaborationben.files.wordpress.com/2017/06/files1.jpg" medium="image" />
  219. </item>
  220. <item>
  221. <title>Touchpoint problem due to no search index</title>
  222. <link>https://collaborationben.com/2017/06/01/touchpoint-problem-due-to-no-search-index/</link>
  223. <comments>https://collaborationben.com/2017/06/01/touchpoint-problem-due-to-no-search-index/#respond</comments>
  224. <pubDate>Thu, 01 Jun 2017 16:39:25 +0000</pubDate>
  225. <dc:creator><![CDATA[collaborationben]]></dc:creator>
  226. <category><![CDATA[Connections]]></category>
  227. <category><![CDATA[ibmcnx]]></category>
  228. <category><![CDATA[ibmconnections]]></category>
  229. <category><![CDATA[Search]]></category>
  230. <category><![CDATA[touchpoint]]></category>
  231.  
  232. <guid isPermaLink="false">http://collaborationben.com/?p=863</guid>
  233. <description><![CDATA[A new Connections customer got in touch with a raft of problems after an upgrade to Connections 6. One of them was a problem with Touchpoint which stopped them from completing the on boarding process which caused them to repeatedly be directed to Touchpoint. What was happening was that they were able to get two [&#8230;]<img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=863&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
  234. <content:encoded><![CDATA[<p>A new Connections customer got in touch with a raft of problems after an upgrade to Connections 6. One of them was a problem with Touchpoint which stopped them from completing the on boarding process which caused them to repeatedly be directed to Touchpoint. What was happening was that they were able to get two or three screens in to &#8220;Add your interests&#8221; and then they couldn&#8217;t go further and had to use &#8220;finish later&#8221; or they were faced with &#8220;Error during prefetching for step profileTags.&#8221;</p>
  235. <p><a href="https://collaborationben.files.wordpress.com/2017/06/tp.jpg" target="_blank" rel="noopener"><img data-attachment-id="864" data-permalink="https://collaborationben.com/2017/06/01/touchpoint-problem-due-to-no-search-index/tp/#main" data-orig-file="https://collaborationben.files.wordpress.com/2017/06/tp.jpg?w=776" data-orig-size="395,187" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}" data-image-title="tp" data-image-description="" data-medium-file="https://collaborationben.files.wordpress.com/2017/06/tp.jpg?w=776?w=300" data-large-file="https://collaborationben.files.wordpress.com/2017/06/tp.jpg?w=776?w=395" class="alignnone wp-image-864 size-full" src="https://collaborationben.files.wordpress.com/2017/06/tp.jpg?w=776" alt="" srcset="https://collaborationben.files.wordpress.com/2017/06/tp.jpg 395w, https://collaborationben.files.wordpress.com/2017/06/tp.jpg?w=150 150w, https://collaborationben.files.wordpress.com/2017/06/tp.jpg?w=300 300w" sizes="(max-width: 395px) 100vw, 395px"   /></a></p>
  236. <p>A quick Google of &#8220;profileTags&#8221; turned up references to search within Connections. I checked the index (which I hadn&#8217;t got around to doing just yet) and I didn&#8217;t find INDEX.READY. The search index had not been created due to LTPAToken exceptions which needed the scheduled tasks to be cleared and all clearScheduler.sql scripts run. Once the search index was created Touchpoint worked.</p><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/collaborationben.wordpress.com/863/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/collaborationben.wordpress.com/863/" /></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=863&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
  237. <wfw:commentRss>https://collaborationben.com/2017/06/01/touchpoint-problem-due-to-no-search-index/feed/</wfw:commentRss>
  238. <slash:comments>0</slash:comments>
  239. <media:content url="http://1.gravatar.com/avatar/73d65d70497b3486650a324a0d88ecf1?s=96&#38;d=identicon&#38;r=G" medium="image">
  240. <media:title type="html">collaborationben</media:title>
  241. </media:content>
  242.  
  243. <media:content url="http://collaborationben.files.wordpress.com/2017/06/tp.jpg" medium="image" />
  244. </item>
  245. <item>
  246. <title>Sametime file transfer not working due to chat logging settings</title>
  247. <link>https://collaborationben.com/2017/04/27/sametime-file-transfer-not-working-due-to-chat-logging-settings/</link>
  248. <comments>https://collaborationben.com/2017/04/27/sametime-file-transfer-not-working-due-to-chat-logging-settings/#respond</comments>
  249. <pubDate>Thu, 27 Apr 2017 07:11:26 +0000</pubDate>
  250. <dc:creator><![CDATA[collaborationben]]></dc:creator>
  251. <category><![CDATA[Sametime]]></category>
  252. <category><![CDATA[file transfer]]></category>
  253. <category><![CDATA[IBM Sametime 9.0.1]]></category>
  254. <category><![CDATA[ibmsametime]]></category>
  255. <category><![CDATA[sametime]]></category>
  256.  
  257. <guid isPermaLink="false">http://collaborationben.com/?p=840</guid>
  258. <description><![CDATA[Internally I transitioned our users over to a new Sametime 9.0.1 Community server with audio and video, meetings, TURN server, the works and it all worked, apart from file transfer. When opening a chat window, the file icon would show but after about 1-2 seconds it would disappear. If you were quick enough you could [&#8230;]<img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=840&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
  259. <content:encoded><![CDATA[<p>Internally I transitioned our users over to a new Sametime 9.0.1 Community server with audio and video, meetings, TURN server, the works and it all worked, apart from file transfer.</p>
  260. <p>When opening a chat window, the file icon would show but after about 1-2 seconds it would disappear. If you were quick enough you could send the recipient a file.</p>
  261. <p>I checked all the policies, I checked policies.user.xml, I updated managed-settings.xml, I enabled trace on the client which showed it was enabled and I tried various configurations and all of which show that file transfer (both direct and via the server) was enabled.</p>
  262. <p>The L3 IBM&#8217;er came back with the following</p>
  263. <blockquote><p>Next I looked at sametime.log and I see ST filetransfer is not staying started and suspect this is why the client can&#8217;t file transfer and they see the file transfer but show up and then go away::<br />
  264. I stplaces 28/Feb/17, 19:27:41 Places is operating in mode RELAX (1)<br />
  265. I stfiletransfer 28/Feb/17, 19:27:41 ChatLoggingMgr::setMode: mode &lt;1&gt;<br />
  266. <span style="color:#ff0000;">E stfiletransfer 28/Feb/17, 19:27:41 Failed to load chatLogging BB or find one of its functions</span><br />
  267. <span style="color:#ff0000;">E stfiletransfer 28/Feb/17, 19:27:41 Logging initialization failed for ChatLog library []</span><br />
  268. I stfiletransfer 28/Feb/17, 19:27:41 Terminated<br />
  269. I stlogger 28/Feb/17, 19:27:41 Initialization completed<br />
  270. I stchatlogging 28/Feb/17, 19:27:41 ChatLoggingMgr::setMode: mode &lt;1&gt;<br />
  271. <span style="color:#ff0000;">E stchatlogging 28/Feb/17, 19:27:41 Failed to load chatLogging BB or find one of its functions</span><br />
  272. <span style="color:#ff0000;">E stchatlogging 28/Feb/17, 19:27:41 Logging initialization failed for ChatLog library []</span><br />
  273. I stchatlogging 28/Feb/17, 19:27:41 Terminated</p>
  274. <p>Chatlogging being enabled when it actually does not exist causes these type of errors and I see in the stconfig.nsf -&gt; Communityservices document,<br />
  275. that yes chat logging is enabled and in relax mode:</p>
  276. <p>But in sametime.ini there is no chatlogging enablement statements:<br />
  277. [ST_BB_NAMES]<br />
  278. <span style="color:#ff0000;">ST_CHAT_LOG=N/A</span><br />
  279. ST_AUTH_TOKEN=notes<br />
  280. [stofflinemessages]</p>
  281. <p>Potential solution<br />
  282. If no chatlogging software then they need to set the setting <span style="color:#ff0000;">Flag: off and Type: 0</span></p></blockquote>
  283. <p><span style="color:#000000;">I updated the values in the SSC which updated the document in stconfig.nsf and after a restart of the Community server file transfer is now available!</span></p>
  284. <p>The default is to set the following value to &#8220;when available&#8221; but setting it to &#8220;never&#8221; worked for me.</p>
  285. <p><a href="https://collaborationben.files.wordpress.com/2017/04/1.jpg" target="_blank" rel="noopener noreferrer"><img data-attachment-id="841" data-permalink="https://collaborationben.com/2017/04/27/sametime-file-transfer-not-working-due-to-chat-logging-settings/1-25/#main" data-orig-file="https://collaborationben.files.wordpress.com/2017/04/1.jpg?w=776" data-orig-size="310,213" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}" data-image-title="1" data-image-description="" data-medium-file="https://collaborationben.files.wordpress.com/2017/04/1.jpg?w=776?w=300" data-large-file="https://collaborationben.files.wordpress.com/2017/04/1.jpg?w=776?w=310" class="alignnone wp-image-841 size-full" src="https://collaborationben.files.wordpress.com/2017/04/1.jpg?w=776" alt="" srcset="https://collaborationben.files.wordpress.com/2017/04/1.jpg 310w, https://collaborationben.files.wordpress.com/2017/04/1.jpg?w=150 150w, https://collaborationben.files.wordpress.com/2017/04/1.jpg?w=300 300w" sizes="(max-width: 310px) 100vw, 310px"   /></a></p>
  286. <p>Update &#8211; 27/04/17</p>
  287. <p>IBM told me that with 9.0.1, out of the box, this option is disabled by default. As this was a 9.0.0.1 server upgraded to 9.0.1 it may have been the case that 9.0.0.1 had this enabled. Or, I may have set it accidentally&#8230;.</p>
  288. <p>Update &#8211; 28/04/17</p>
  289. <p>IBM posted the Technote yesterday &#8211; <a href="https://www-01.ibm.com/support/docview.wss?uid=swg22002683&#038;myns=swglotus&#038;mynp=OCSSKTXQ&#038;mync=E&#038;cm_sp=swglotus-_-OCSSKTXQ-_-E" rel="nofollow">https://www-01.ibm.com/support/docview.wss?uid=swg22002683&#038;myns=swglotus&#038;mynp=OCSSKTXQ&#038;mync=E&#038;cm_sp=swglotus-_-OCSSKTXQ-_-E</a></p><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/collaborationben.wordpress.com/840/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/collaborationben.wordpress.com/840/" /></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=840&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
  290. <wfw:commentRss>https://collaborationben.com/2017/04/27/sametime-file-transfer-not-working-due-to-chat-logging-settings/feed/</wfw:commentRss>
  291. <slash:comments>0</slash:comments>
  292. <media:content url="http://1.gravatar.com/avatar/73d65d70497b3486650a324a0d88ecf1?s=96&#38;d=identicon&#38;r=G" medium="image">
  293. <media:title type="html">collaborationben</media:title>
  294. </media:content>
  295.  
  296. <media:content url="http://collaborationben.files.wordpress.com/2017/04/1.jpg" medium="image" />
  297. </item>
  298. <item>
  299. <title>Orient Me and mongoDB connection failures</title>
  300. <link>https://collaborationben.com/2017/04/20/orient-me-and-mongodb-connection-failures/</link>
  301. <comments>https://collaborationben.com/2017/04/20/orient-me-and-mongodb-connection-failures/#comments</comments>
  302. <pubDate>Thu, 20 Apr 2017 15:16:55 +0000</pubDate>
  303. <dc:creator><![CDATA[collaborationben]]></dc:creator>
  304. <category><![CDATA[Connections]]></category>
  305. <category><![CDATA[ibmconnections]]></category>
  306. <category><![CDATA[kubernetes]]></category>
  307. <category><![CDATA[mongoDB]]></category>
  308. <category><![CDATA[orientme]]></category>
  309. <category><![CDATA[pink]]></category>
  310.  
  311. <guid isPermaLink="false">http://collaborationben.com/?p=837</guid>
  312. <description><![CDATA[I have been banging against a mongoDB wall for a good few days as explained in another post but I&#8217;m slowly getting there. The problem I was facing was that the migration application in the people-migrate container wasn&#8217;t working. # npm run start migrate npm info it worked if it ends with ok npm info [&#8230;]<img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=837&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
  313. <content:encoded><![CDATA[<p>I have been banging against a mongoDB wall for a good few days as explained in another <a href="https://collaborationben.com/2017/04/13/orient-me-and-some-things-ive-come-across-and-wrestled-with/" target="_blank" rel="noopener noreferrer">post </a>but I&#8217;m slowly getting there. The problem I was facing was that the migration application in the people-migrate container wasn&#8217;t working.</p>
  314. <p># npm run start migrate<br />
  315. <em>npm info it worked if it ends with ok</em><br />
  316. <em>npm info using [email protected]</em><br />
  317. <em>npm info using [email protected]</em><br />
  318. <em>npm info lifecycle [email protected]~prestart: [email protected]</em><br />
  319. <em>npm info lifecycle [email protected]~start: [email protected]</em></p>
  320. <p><em>&gt; [email protected] start /usr/src/app</em><br />
  321. <em>&gt; cross-env NODE_ENV=production node lib/server.js &#8220;migrate&#8221;</em></p>
  322. <p><em>2017-04-20T13:19:56.761Z &#8211; info: [migrator] Mongo DB URL: mongodb://mongo-0.mongo:27017,mongo-1.mongo:27017,mongo-2.mongo:27017/relationshipdb?replicaSet=rs0&amp;readPreference=primaryPreferred&amp;wtimeoutMS=2000</em><br />
  323. <em>2017-04-20T13:19:56.766Z &#8211; info: [migrator] Mongo DB URL: mongodb://mongo-0.mongo:27017,mongo-1.mongo:27017,mongo-2.mongo:27017/datamigrationdb?replicaSet=rs0&amp;readPreference=primaryPreferred&amp;wtimeoutMS=2000</em><br />
  324. <em>2017-04-20T13:19:56.767Z &#8211; info: [migrator] Mongo DB URL: mongodb://mongo-0.mongo:27017,mongo-1.mongo:27017,mongo-2.mongo:27017/profiledb?replicaSet=rs0&amp;readPreference=primaryPreferred&amp;wtimeoutMS=2000</em><br />
  325. <em>Connection fails: MongoError: failed to connect to server [mongo-0:27017] on first connect [MongoError: getaddrinfo ENOTFOUND mongo-0 mongo-0:27017]</em><br />
  326. <em>It will be retried for the next request.</em></p>
  327. <p><em>/usr/src/app/node_modules/mongodb/lib/mongo_client.js:338</em><br />
  328. <em>          throw err</em><br />
  329. <em>          ^</em><br />
  330. <em>MongoError: failed to connect to server [mongo-0:27017] on first connect [MongoError: getaddrinfo ENOTFOUND mongo-0 mongo-0:27017]</em><br />
  331. <em>    at Pool.&lt;anonymous&gt; (/usr/src/app/node_modules/mongodb-core/lib/topologies/server.js:327:35)</em><br />
  332. <em>    at emitOne (events.js:96:13)</em><br />
  333. <em>    at Pool.emit (events.js:188:7)</em><br />
  334. <em>    at Connection.&lt;anonymous&gt; (/usr/src/app/node_modules/mongodb-core/lib/connection/pool.js:274:12)</em><br />
  335. <em>    at Connection.g (events.js:291:16)</em><br />
  336. <em>    at emitTwo (events.js:106:13)</em><br />
  337. <em>    at Connection.emit (events.js:191:7)</em><br />
  338. <em>    at Socket.&lt;anonymous&gt; (/usr/src/app/node_modules/mongodb-core/lib/connection/connection.js:177:49)</em><br />
  339. <em>    at Socket.g (events.js:291:16)</em><br />
  340. <em>    at emitOne (events.js:96:13)</em><br />
  341. <em>    at Socket.emit (events.js:188:7)</em><br />
  342. <em>    at connectErrorNT (net.js:1020:8)</em><br />
  343. <em>    at _combinedTickCallback (internal/process/next_tick.js:74:11)</em><br />
  344. <em>    at process._tickCallback (internal/process/next_tick.js:98:9)</em></p>
  345. <p>If I specify the location of migrationConfig I get the same result.</p>
  346. <p># npm run start migrate config:/usr/src/app/migrationConfig</p>
  347. <p>Oddly enough, if I run the above command outside of /usr/src/app/ directory it fails. It doesn&#8217;t actually read the file you specify, it always looks for migrationConfig in relation to the working directory where you are when you issue it. Of course I may have the syntax wrong but if I do not then it&#8217;s a bit sloppy.</p>
  348. <p>On to the problem which seems to be name resolution. The error I was getting was</p>
  349. <p><em>Connection fails: MongoError: failed to connect to server [mongo-0:27017] on first connect [MongoError: getaddrinfo ENOTFOUND mongo-0 mongo-0:27017]</em></p>
  350. <p>It seems to be trying to connect to mongo-0 over 27017.</p>
  351. <p># kubectl exec -it $(kubectl get pods | grep people-migrate | awk &#8216;{print $1}&#8217;) bash</p>
  352. <p># ping mongo-0<br />
  353. <em>ping: mongo-0: Name or service not known</em></p>
  354. <p># ping mongo<br />
  355. <em>PING mongo.default.svc.cluster.local (10.1.67.163) 56(84) bytes of data.</em><br />
  356. <em>64 bytes from 10.1.67.163 (10.1.67.163): icmp_seq=1 ttl=63 time=0.063 ms</em></p>
  357. <p># ping mongo-0.mongo<br />
  358. <em>PING mongo-0.mongo.default.svc.cluster.local (10.1.67.163) 56(84) bytes of data.</em><br />
  359. <em>64 bytes from 10.1.67.163 (10.1.67.163): icmp_seq=1 ttl=63 time=0.087 ms</em></p>
  360. <p>This was the cause, &#8220;mongo-0&#8221; was not resolving for me and this is confirmed by another that there container works the same. To work around this I added an entry to the container&#8217;s host file.</p>
  361. <p># cat /etc/hosts<br />
  362. # Kubernetes-managed hosts file.<br />
  363. 127.0.0.1       localhost<br />
  364. ::1     localhost ip6-localhost ip6-loopback<br />
  365. fe00::0 ip6-localnet<br />
  366. fe00::0 ip6-mcastprefix<br />
  367. fe00::1 ip6-allnodes<br />
  368. fe00::2 ip6-allrouters<br />
  369. 10.1.67.176     people-migrate-4029352936-n8fzl<br />
  370. <strong>10.1.67.163     mongo-0 mongo-0.mongo</strong></p>
  371. <p>Now the migration app works but I also have mongo-sidecar errors which I&#8217;m not clear on as to whether they are supposed to be there.</p>
  372. <h3><strong>Update &#8211; 27/04/17</strong></h3>
  373. <p>This only gets me so far. This allows me to get the data migrated from Connections Profiles in to MongoDB but when the container is torn down and replaced with another the host file entry is gone. Also, there are the following errors in the logs for itm-services containers that I cannot exec to to update the hosts file.</p>
  374. <p><em>Connection fails: MongoError: failed to connect to server [mongo-0:27017] on first connect [MongoError: getaddrinfo ENOTFOUND mongo-0 mongo-0:27017]</em><br />
  375. <em>It will be retried for the next request.</em></p>
  376. <p><em>/usr/src/app/node_modules/mongodb/lib/mongo_client.js:338</em><br />
  377. <em>          throw err</em><br />
  378. <em>          ^</em><br />
  379. <em>MongoError: failed to connect to server [mongo-0:27017] on first connect [MongoError: getaddrinfo ENOTFOUND mongo-0 mongo-0:27017]</em><br />
  380. <em>    at Pool.&lt;anonymous&gt; (/usr/src/app/node_modules/mongodb-core/lib/topologies/server.js:327:35)</em><br />
  381. <em>    at emitOne (events.js:96:13)</em><br />
  382. <em>    at Pool.emit (events.js:188:7)</em><br />
  383. <em>    at Connection.&lt;anonymous&gt; (/usr/src/app/node_modules/mongodb-core/lib/connection/pool.js:274:12)</em><br />
  384. <em>    at Connection.g (events.js:291:16)</em><br />
  385. <em>    at emitTwo (events.js:106:13)</em><br />
  386. <em>    at Connection.emit (events.js:191:7)</em><br />
  387. <em>    at Socket.&lt;anonymous&gt; (/usr/src/app/node_modules/mongodb-core/lib/connection/connection.js:177:49)</em><br />
  388. <em>    at Socket.g (events.js:291:16)</em><br />
  389. <em>    at emitOne (events.js:96:13)</em><br />
  390. <em>    at Socket.emit (events.js:188:7)</em><br />
  391. <em>    at connectErrorNT (net.js:1020:8)</em><br />
  392. <em>    at _combinedTickCallback (internal/process/next_tick.js:74:11)</em><br />
  393. <em>    at process._tickCallback (internal/process/next_tick.js:98:9)</em></p>
  394. <h3>Update 28/04/17</h3>
  395. <p>During the (excellent) Connections Pink Developer Workshop hosted by IBM we were given access to a SoftLayer server running CentOS 7.3 where we installed CfC and Orient Me. The installer worked just fine with no signs of the mongoDB errors above. I have come across two others who have the same errors I have documented above.</p>
  396. <p>I sparked up a CentOS 7.3 server on Bluemix for a few hours and the install with the same binaries worked just fine. I compared what yum has installed and installed all on my local CentOS 7.3 server and the same problem occurred. I changed my NIC device name swapping it from ens192 to match Bluemix and eth0 but the result is the same.</p>
  397. <h3>Update 05/05/17</h3>
  398. <p>This week I was lucky to visit the Dublin labs with a customer discussing Watson Workspace, Watson Work Services, XPages and Pink. I used a couple of hours of those two days to have a chat with <a href="https://twitter.com/davidmcdonagh" target="_blank" rel="noopener noreferrer">David McDonagh</a> and a colleague of his Bruno to look into the problems I was having with Mongo.</p>
  399. <p>The crux of it was that the node I was using as the master, boot, worker and proxy was under a great deal of strain, mainly CPU strain, which seemed to be causing the problem. This would make sense since the differences between my ESXi server and Bluemix are the resources available to it.</p>
  400. <p>I bumped up the resources available to the single node but although the install went OK the problems persisted. It wasn&#8217;t until today that I got it working but not with a single node but rather two nodes. Node 1 ran boot, master and proxy roles whilst node 2 was the worker node. I gave a generous helping of resources to both and the thankfully the installation went smoothly and more importantly the errors above are no more.</p>
  401. <p>I have some further work to see how much I can scale the resources back because it does have an impact on my ESXi host and the other guests on it.</p><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/collaborationben.wordpress.com/837/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/collaborationben.wordpress.com/837/" /></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=837&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
  402. <wfw:commentRss>https://collaborationben.com/2017/04/20/orient-me-and-mongodb-connection-failures/feed/</wfw:commentRss>
  403. <slash:comments>8</slash:comments>
  404. <media:content url="http://1.gravatar.com/avatar/73d65d70497b3486650a324a0d88ecf1?s=96&#38;d=identicon&#38;r=G" medium="image">
  405. <media:title type="html">collaborationben</media:title>
  406. </media:content>
  407. </item>
  408. <item>
  409. <title>Orient Me and some things I&#8217;ve come across and wrestled with</title>
  410. <link>https://collaborationben.com/2017/04/13/orient-me-and-some-things-ive-come-across-and-wrestled-with/</link>
  411. <comments>https://collaborationben.com/2017/04/13/orient-me-and-some-things-ive-come-across-and-wrestled-with/#comments</comments>
  412. <pubDate>Thu, 13 Apr 2017 19:04:31 +0000</pubDate>
  413. <dc:creator><![CDATA[collaborationben]]></dc:creator>
  414. <category><![CDATA[Connections]]></category>
  415. <category><![CDATA[ibm connections]]></category>
  416. <category><![CDATA[ibmcnx]]></category>
  417. <category><![CDATA[ibmconnections]]></category>
  418. <category><![CDATA[orientme]]></category>
  419.  
  420. <guid isPermaLink="false">http://collaborationben.com/?p=833</guid>
  421. <description><![CDATA[Having gained some experience of Docker and CfC (IBM Spectrum Conductor for Containers) before Connections 6.0 was released I thought this would be easy to set up but I must admit I&#8217;m struggling. My setup is 3 CentOS servers for Orient Me with another for DB2/SDI and another for Connections hosting the deployment manager. Here [&#8230;]<img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=833&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
  422. <content:encoded><![CDATA[<p>Having gained some experience of Docker and CfC (IBM Spectrum Conductor for Containers) before Connections 6.0 was released I thought this would be easy to set up but I must admit I&#8217;m struggling.</p>
  423. <p>My setup is 3 CentOS servers for Orient Me with another for DB2/SDI and another for Connections hosting the deployment manager.</p>
  424. <p>Here are some things I have come across which I&#8217;d like to add to as I come across other problems.</p>
  425. <h2>DNS</h2>
  426. <p>Working on a beefy ESXi server running at home I normally manage most things using hosts file which has worked really well, up until now. I won&#8217;t steal from <a href="http://www.robertoboccadoro.com/2017/04/13/orientme-in-a-test-environment-how-to-make-it-work/" target="_blank">Roberto Boccadoro&#8217;s</a> blog post but suffice to say I couldn&#8217;t get it to work using hosts file even after editing nsswitch.conf. I had to rely on spoofing DNS, internally, on my router by updating /jffs/configs/hosts.add to include all my Connections servers.</p>
  427. <p>Even with this I found that the migration script in people-migrate container would fail because so in this case I had to add my host files to /etc/hosts which got me past that step.</p>
  428. <h2>MongoDB</h2>
  429. <p>I had to uninstall and reinstall a couple of times. On reinstall I had problems with the migration application (people-migrate) connecting to mongoDB. I was able to check the databases and connect to them.</p>
  430. <p># kubectl exec -it mongo-0 bash</p>
  431. <p>#mongo</p>
  432. <p>rs0:PRIMARY&gt; show dbs<br />
  433. admin  0.000GB<br />
  434. local  0.000GB</p>
  435. <p>The migration script was failing to connect and I couldn&#8217;t fathom why. I uninstalled again and this time I removed the persistent volumes and recreated them and now the migration script gets further but fails with the following exception.</p>
  436. <p>2017-04-12T12:01:42.751Z &#8211; info: [migrator] Mongo DB URL: mongodb://mongo-0.mongo:27017/relationshipdb?replicaSet=rs&amp;readPreference=primaryPreferred&amp;wtimeoutMS=2000<br />
  437. 2017-04-12T12:01:42.757Z &#8211; info: [migrator] Mongo DB URL: mongodb://mongo-0.mongo:27017/datamigrationdb?replicaSet=rs&amp;readPreference=primaryPreferred&amp;wtimeoutMS=2000<br />
  438. 2017-04-12T12:01:42.758Z &#8211; info: [migrator] Mongo DB URL: mongodb://mongo-0.mongo:27017/profiledb?replicaSet=rs&amp;readPreference=primaryPreferred&amp;wtimeoutMS=2000<br />
  439. 2017-04-12T12:01:54.018Z &#8211; info: [migrator] total request number: 1<br />
  440. 2017-04-12T12:01:54.021Z &#8211; info: [populator] Start to populate URL:<br />
  441. &#8211;&#8220;<a href="https://connections.domain.com/profiles/admin/atom/profiles.do?ps=100&#038;#8221" rel="nofollow">https://connections.domain.com/profiles/admin/atom/profiles.do?ps=100&#038;#8221</a>;</p>
  442. <p>2017-04-12T12:01:59.417Z &#8211; error: [migrator] errors:[{&#8220;profileKey&#8221;:&#8221;16ff2775-2ace-4db8-8e54-56adcc62a5fb&#8221;,&#8221;externalId&#8221;:&#8221;382AB352-F9AE-D6E4-8025-7D2C004A7248&#8243;,&#8221;created&#8221;:1491998514408,&#8221;orgId&#8221;:&#8221;a&#8221;,&#8221;id&#8221;:&#8221;FAKE_ID&#8221;,&#8221;error&#8221;:{}},{&#8220;profileKey&#8221;:&#8221;8af449b4-0357-4bed-a7c7-c0e5285ba826&#8243;,&#8221;externalId&#8221;:&#8221;932ED7B3-988D-9EFC-8625-79E3005B2B62&#8243;,&#8221;created&#8221;:1491998514409,&#8221;orgId&#8221;:&#8221;a&#8221;,&#8221;id&#8221;:&#8221;FAKE_ID&#8221;,&#8221;error&#8221;:{}},{&#8220;profileKey&#8221;:&#8221;a9294f18-ee72-49d0-8a44-cf02abe6d4d2&#8243;,&#8221;externalId&#8221;:&#8221;0873E9A9-7E12-0609-8025-7D38003BFD71&#8243;,&#8221;created&#8221;:1491998514410,&#8221;orgId&#8221;:&#8221;a&#8221;,&#8221;id&#8221;:&#8221;FAKE_ID&#8221;,&#8221;error&#8221;:{}},{&#8220;profileKey&#8221;:&#8221;b6994f86-7525-48b6-92da-900393382e11&#8243;,&#8221;externalId&#8221;:&#8221;0F64A6F8-927B-483C-8625-79E3005AC781&#8243;,&#8221;created&#8221;:1491998514410,&#8221;orgId&#8221;:&#8221;a&#8221;,&#8221;id&#8221;:&#8221;FAKE_ID&#8221;,&#8221;error&#8221;:{}}]<br />
  443. Connection fails: MongoError: failed to connect to server [mongo-0:27017] on first connect [MongoError: connection 4 to mongo-0:27017 timed out]<br />
  444. It will be retried for the next request.<br />
  445. Connection fails: MongoError: failed to connect to server [mongo-0:27017] on first connect [MongoError: connection 5 to mongo-0:27017 timed out]<br />
  446. It will be retried for the next request.</p>
  447. <p>/usr/src/app/node_modules/mongodb/lib/mongo_client.js:338<br />
  448. throw err<br />
  449. ^<br />
  450. MongoError: failed to connect to server [mongo-0:27017] on first connect [MongoError: connection 5 to mongo-0:27017 timed out]<br />
  451. at Pool.&lt;anonymous&gt; (/usr/src/app/node_modules/mongodb-core/lib/topologies/server.js:327:35)<br />
  452. at emitOne (events.js:96:13)<br />
  453. at Pool.emit (events.js:188:7)<br />
  454. at Connection.&lt;anonymous&gt; (/usr/src/app/node_modules/mongodb-core/lib/connection/pool.js:274:12)<br />
  455. at Connection.g (events.js:291:16)<br />
  456. at emitTwo (events.js:106:13)<br />
  457. at Connection.emit (events.js:191:7)<br />
  458. at Socket.&lt;anonymous&gt; (/usr/src/app/node_modules/mongodb-core/lib/connection/connection.js:187:10)<br />
  459. at Socket.g (events.js:291:16)<br />
  460. at emitNone (events.js:86:13)<br />
  461. at Socket.emit (events.js:185:7)<br />
  462. at Socket._onTimeout (net.js:339:8)<br />
  463. at ontimeout (timers.js:365:14)<br />
  464. at tryOnTimeout (timers.js:237:5)<br />
  465. at Timer.listOnTimeout (timers.js:207:5)</p>
  466. <h2>Redis client</h2>
  467. <p>In the knowledge center it alludes as to how to test connecting to Redis from the Connections node. If you want to install the client and try for yourself here are the instructions IBM deemed not necessary to write down for you.</p>
  468. <p># su -c &#8216;rpm -Uvh <a href="http://download.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-9.noarch.rpm&#038;#8217" rel="nofollow">http://download.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-9.noarch.rpm&#038;#8217</a>;<br />
  469. # yum install redis</p>
  470. <p># redis-cli -p 30379<br />
  471. 127.0.0.1:30379&gt; set foo bar<br />
  472. OK<br />
  473. 127.0.0.1:30379&gt; get foo<br />
  474. &#8220;bar&#8221;<br />
  475. 127.0.0.1:30379&gt;</p>
  476. <h2>Odd pod behaviour</h2>
  477. <p>I believe I have an underlying problem with the persistent volumes and over night this happened.</p>
  478. <p># kubectl get pods</p>
  479. <p>zookeeper-controller-3-2528439515-xz702   0/1       OutOfpods   0          13h<br />
  480. zookeeper-controller-3-2528439515-xz79d   0/1       OutOfpods   0          14h<br />
  481. zookeeper-controller-3-2528439515-xzqc9   0/1       OutOfpods   0          13h<br />
  482. zookeeper-controller-3-2528439515-xzzbl   0/1       OutOfpods   0          16h<br />
  483. zookeeper-controller-3-2528439515-z0kwf   0/1       OutOfpods   0          13h<br />
  484. zookeeper-controller-3-2528439515-z13kn   0/1       OutOfpods   0          17h<br />
  485. zookeeper-controller-3-2528439515-z2lsn   0/1       OutOfpods   0          13h<br />
  486. zookeeper-controller-3-2528439515-z6mc5   0/1       OutOfpods   0          14h<br />
  487. zookeeper-controller-3-2528439515-z74nj   0/1       OutOfpods   0          13h<br />
  488. zookeeper-controller-3-2528439515-z97jp   0/1       OutOfpods   0          17h<br />
  489. zookeeper-controller-3-2528439515-zd2js   0/1       OutOfpods   0          4h<br />
  490. zookeeper-controller-3-2528439515-zdc3t   0/1       OutOfpods   0          14h<br />
  491. zookeeper-controller-3-2528439515-zk5bw   0/1       OutOfpods   0          16h</p>
  492. <p># kubectl get pods | wc -l<br />
  493. 2114</p>
  494. <p>There were thousands of pods. I believe they were created faster than they could be garbage collected.</p>
  495. <p>I deleted all the pods in the &#8220;OutOfpods&#8221; status using the following command.</p>
  496. <p># kubectl get pod | cut -d &#8221; &#8221; -f 1 | xargs -n1 -P 10 kubectl delete pod</p>
  497. <h2>Shutdown</h2>
  498. <p>To shutdown my servers I have been running the following to stop all pods.</p>
  499. <p># docker stop $(docker ps -a -q)</p>
  500. <p>I&#8217;m not sure whether I am better off using a different variation of above to stop all pods</p>
  501. <p># kubectl get pod | cut -d &#8221; &#8221; -f 1 | xargs -n1 -P 10 kubectl delete pod</p>
  502. <p>Is there a better prescribed way of doing this?</p>
  503. <h2>Enabling profiles events for Orient Me</h2>
  504. <p>I did what was asked of me in the knowledge center but there is little indication of it having worked. In the documentation it states that I should see &#8220;OrientMe configured properly &#8211; both properties are enabled.&#8221; Where should I see that, in SDI&#8217;s ibmdi.log or in one of the application servers SystemOut.log? I have looked at both and I do not see this written.</p>
  505. <p>Anyway, I&#8217;ll hopefully add  to this as I go. If anyone has come across these problems and found a resolution to them, please get in touch.</p><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/collaborationben.wordpress.com/833/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/collaborationben.wordpress.com/833/" /></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=833&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
  506. <wfw:commentRss>https://collaborationben.com/2017/04/13/orient-me-and-some-things-ive-come-across-and-wrestled-with/feed/</wfw:commentRss>
  507. <slash:comments>9</slash:comments>
  508. <media:content url="http://1.gravatar.com/avatar/73d65d70497b3486650a324a0d88ecf1?s=96&#38;d=identicon&#38;r=G" medium="image">
  509. <media:title type="html">collaborationben</media:title>
  510. </media:content>
  511. </item>
  512. <item>
  513. <title>Old version of Notes Java breaks IBM Connections Files plugin when TLSv1.2 is enforced</title>
  514. <link>https://collaborationben.com/2017/03/29/version-of-notes-java-breaks-ibm-connections-files-plugin-when-tlsv1-2-is-enforced/</link>
  515. <comments>https://collaborationben.com/2017/03/29/version-of-notes-java-breaks-ibm-connections-files-plugin-when-tlsv1-2-is-enforced/#comments</comments>
  516. <pubDate>Wed, 29 Mar 2017 14:39:36 +0000</pubDate>
  517. <dc:creator><![CDATA[collaborationben]]></dc:creator>
  518. <category><![CDATA[Uncategorized]]></category>
  519. <category><![CDATA[Connections]]></category>
  520. <category><![CDATA[ibmcnx]]></category>
  521. <category><![CDATA[ibmconnections]]></category>
  522. <category><![CDATA[IBMNotes]]></category>
  523. <category><![CDATA[Notes]]></category>
  524. <category><![CDATA[TLSv1.2]]></category>
  525.  
  526. <guid isPermaLink="false">http://collaborationben.com/?p=827</guid>
  527. <description><![CDATA[I had to raise a PMR on a problem I and others in my company had with the Notes client. After enforcing TLSv1.2 in Connections 5.5 using the following configuration in httpd.conf the Files plugin would not work but the Activities and Status Updates plugins would. SSLEnable SSLProtocolDisable SSLv2 SSLv3 TLSv11 TLSv10 SSLCipherSpec TLSv12 +TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 [&#8230;]<img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=827&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
  528. <content:encoded><![CDATA[<p>I had to raise a PMR on a problem I and others in my company had with the Notes client. After <a href="https://www.ibm.com/support/knowledgecenter/en/SSYGQH_5.5.0/admin/secure/t_admin_common_forcing_tls.html" target="_blank">enforcing TLSv1.2 in Connections 5.5</a> using the following configuration in httpd.conf the Files plugin would not work but the Activities and Status Updates plugins would.</p>
  529. <h5>SSLEnable<br />
  530. SSLProtocolDisable SSLv2 SSLv3 TLSv11 TLSv10<br />
  531. SSLCipherSpec TLSv12 +TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 +TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 +TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 +TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA +TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 +TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA +TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 +TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 +TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 +TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 +TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA</h5>
  532. <p>I kept seeing the following screen and clicking &#8220;try again using existing options&#8221; did nothing.</p>
  533. <p><a href="https://collaborationben.files.wordpress.com/2017/03/filesplugin.jpg" target="_blank"><img data-attachment-id="828" data-permalink="https://collaborationben.com/2017/03/29/version-of-notes-java-breaks-ibm-connections-files-plugin-when-tlsv1-2-is-enforced/filesplugin/#main" data-orig-file="https://collaborationben.files.wordpress.com/2017/03/filesplugin.jpg?w=776" data-orig-size="272,320" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}" data-image-title="filesplugin" data-image-description="" data-medium-file="https://collaborationben.files.wordpress.com/2017/03/filesplugin.jpg?w=776?w=255" data-large-file="https://collaborationben.files.wordpress.com/2017/03/filesplugin.jpg?w=776?w=272" class="alignnone wp-image-828 size-full" src="https://collaborationben.files.wordpress.com/2017/03/filesplugin.jpg?w=776" alt="" srcset="https://collaborationben.files.wordpress.com/2017/03/filesplugin.jpg 272w, https://collaborationben.files.wordpress.com/2017/03/filesplugin.jpg?w=128 128w" sizes="(max-width: 272px) 100vw, 272px"   /></a></p>
  534. <p>Whilst clicking on &#8220;try again using existing options&#8221; I would see the following in IHS.</p>
  535. <h5>[Wed Mar 29 14:30:41 2017] [warn] [client xxx.xxx.xxx.xx] [7f9a480ec800] [30453] SSL0222W: SSL Handshake Failed, No ciphers specified (no shared ciphers or no shared protocols).  [xxx.xxx.xxx.xx:49296 -&gt; xxx.xxx.xxx.xx:443] [14:30:41.000571168] 0ms</h5>
  536. <p>The SSL certificate is at 4096 bits and I had previously replaced US_export_policy.jar and local_policy.jar with the <a href="https://www-01.ibm.com/marketing/iwm/iwm/web/reg/pick.do?source=jcesdk&amp;lang=en_US" target="_blank">unrestricted policy jars</a> so that was not the problem.</p>
  537. <p>I found, oddly, that if I swapped to the IBM Sametime Meetings plugin first and then changed to Files, my files would load&#8230;. Also, if I ran Fiddler and restarted my Notes client but went directly to Files it would load too. Weird.</p>
  538. <p>I had a screen share with <a href="https://www.linkedin.com/in/lizhecht" target="_blank">Elizabeth Hecht</a> and <a href="https://www.linkedin.com/in/jackie-chewens-b4ba0211" target="_blank">Jacqueline Chewens</a> to show them the odd behaviour and they too were baffled. Liz came across a thought of the version of Java being used may not be allowing connectivity to Files and asked whether I had applied the Java update for FP6? Not having so much focus on Notes and Domino of late I told her I wasn&#8217;t even aware that previously you were supposed to update the version of Java being used by the Notes client.</p>
  539. <p>To test this I updated Notes to FP8, which bundles in the Java update and low and behold the Files plugin started working. Also, there was no need to replace the jars with the unrestricted ones!</p>
  540. <p>The version of Java now in play is as follows.</p>
  541. <h5>c:\Program Files (x86)\IBM\Notes\jvm&gt;java -version<br />
  542. java version &#8220;1.8.0_121&#8221;<br />
  543. Java(TM) SE Runtime Environment (build 1.8.0_121-b13)<br />
  544. Java HotSpot(TM) Client VM (build 25.121-b13, mixed mode, sharing)</h5>
  545. <p>BTW &#8211; if Connections enforces SSL then you need to make sure that <strong>com.ibm.documents.connector.service/ENABLE_SSL=true</strong> is set in the plugin_customization.ini.</p><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/collaborationben.wordpress.com/827/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/collaborationben.wordpress.com/827/" /></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=827&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
  546. <wfw:commentRss>https://collaborationben.com/2017/03/29/version-of-notes-java-breaks-ibm-connections-files-plugin-when-tlsv1-2-is-enforced/feed/</wfw:commentRss>
  547. <slash:comments>2</slash:comments>
  548. <media:content url="http://1.gravatar.com/avatar/73d65d70497b3486650a324a0d88ecf1?s=96&#38;d=identicon&#38;r=G" medium="image">
  549. <media:title type="html">collaborationben</media:title>
  550. </media:content>
  551.  
  552. <media:content url="http://collaborationben.files.wordpress.com/2017/03/filesplugin.jpg" medium="image" />
  553. </item>
  554. <item>
  555. <title>Connections Pink and container orchestration using CfC</title>
  556. <link>https://collaborationben.com/2017/03/16/connections-pink-and-container-orchestration-using-cfc/</link>
  557. <comments>https://collaborationben.com/2017/03/16/connections-pink-and-container-orchestration-using-cfc/#respond</comments>
  558. <pubDate>Thu, 16 Mar 2017 09:16:19 +0000</pubDate>
  559. <dc:creator><![CDATA[collaborationben]]></dc:creator>
  560. <category><![CDATA[Containers]]></category>
  561. <category><![CDATA[cfc]]></category>
  562. <category><![CDATA[Connections]]></category>
  563. <category><![CDATA[docker]]></category>
  564. <category><![CDATA[ibmcnx]]></category>
  565. <category><![CDATA[ibmconnections]]></category>
  566. <category><![CDATA[kubernetes]]></category>
  567. <category><![CDATA[pink]]></category>
  568. <category><![CDATA[spectrum]]></category>
  569.  
  570. <guid isPermaLink="false">http://collaborationben.com/?p=824</guid>
  571. <description><![CDATA[A while ago I started dabbling with Docker after reading some great blogs about ELK by Klaus Bild and Christoph Stoettner thinking I could do with a tool like ELK to analyse log files and to give me something tangible to work with whilst learning about Docker. After a lot of hard learning and some [&#8230;]<img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=824&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
  572. <content:encoded><![CDATA[<p>A while ago I started dabbling with Docker after reading some great blogs about ELK by <a href="https://kbild.ch/2016/08/monitor-websphere-with-elk-and-nagios/" target="_blank">Klaus Bild</a> and <a href="https://www.stoeps.de/better-logstash-filter-to-analyze-systemout-log-and-some-more/#more-13623" target="_blank">Christoph Stoettner</a> thinking I could do with a tool like ELK to analyse log files and to give me something tangible to work with whilst learning about Docker.</p>
  573. <p>After a lot of hard learning and some frustrating hours I got my head around containers and how they could be used to my advantage and got ELK running natively on Ubuntu and then on my work Windows 7 laptop.</p>
  574. <p>A few months before Connect 2017 news was leaking about Connections Pink and its architecture and how the applications will run within containers. Recently <a href="https://www.linkedin.com/in/jasonroygary/" target="_blank">Jason Gary Roy</a> held a webinar (<a href="http://www-01.ibm.com/support/docview.wss?uid=swg27049476" target="_blank">Open Mic Webcast: Think Pink &#8211; The Future of IBM Connections &#8211; 07 March 2017</a>) replaying some of his slides from Connect 2017 and in the video he mentions (briefly) CfC in combination with Docker and containers.</p>
  575. <p>I asked the question in the IBM Connections Community Skype chat and a few people told me that CfC was an IBM product called <a href="https://www.ibm.com/developerworks/community/groups/service/html/communityoverview?communityUuid=fe25b4ef-ea6a-4d86-a629-6f87ccf4649e" target="_blank">IBM Spectrum Conductor for Containers</a>. I looked through the community for CfC and realised how important having an orchestration tool is for running multiple containers and scaling for high availability. This was a long way away from running three containers on my laptop.</p>
  576. <p>Installing CfC was pretty easy and well documented in the CfC <a href="https://www.ibm.com/developerworks/community/groups/service/html/communityoverview?communityUuid=fe25b4ef-ea6a-4d86-a629-6f87ccf4649e" target="_blank">community</a>. Installation wise you need to install on Ubuntu 16.04 or RHEL although I am sure CentOS will work. I&#8217;ll get to that next week.</p>
  577. <p>What you end up with is a rather nice UI which does many of the hard things for you such as networking, setting up persistent storage for your containers, moving applications to other nodes, automatic scaling when demand requires and many more.</p>
  578. <p>What I also liked is that it acts as a private repository for your containers avoiding you needing to push to Docker Hub for storage.</p>
  579. <p>In the latest version you can install on a single node which is great for testing purposes but it also allows you to add and remove worker nodes when you want to branch out.</p>
  580. <p>I asked in the CfC <a href="https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W1559b1be149d_43b0_881e_9783f38faaff/page/Slack%20channel%20(IBM%20Cloud%20technology)%20sign%20up%20page" target="_blank">Slack channel</a> what the future looks like for CfC because if it requires a license then it is another hurdle to overcome when selling in Connections. The response I got was:</p>
  581. <blockquote><p><em>&#8220;We are intending to keep providing a free version that customer can use and deploy as it is a packaging of open-source. Business discussion on what to do beyond that are still ongoing so I can’t comment. Options include providing commercial support or additional add-ons around the open-source for a commercial product. Right now this is a community effort, and we are currently looking  technical feedback  and understanding of what use cases people would like to use CfC for.  Looking forward to  your participation.&#8221;</em></p></blockquote>
  582. <p>Since the product is built on the following open technologies I would hope that a free option remains available going forward.</p>
  583. <p>Another other benefit for using CfC is that IBM are using it for Pink. I assume that most of the documentation referring to orchestration of the containers will reference CfC in some form. Getting to know it now, I hope, will make deploying Pink containers easier.</p>
  584. <p>Thanks to <a href="https://twitter.com/buccarellom" target="_blank">Michele Buccarello</a> for answering my questions.</p>
  585. <h3>CwC has been built with below individual components</h3>
  586. <p>Core component:</p>
  587. <ul>
  588. <li>Kubernetes and Mesosphere API/CLI</li>
  589. <li>GUI</li>
  590. <li>Installer for HA</li>
  591. <li>Authentication through LDAP</li>
  592. <li>An App store</li>
  593. <li>A Private image registry</li>
  594. </ul>
  595. <p>Sample applications:</p>
  596. <ul>
  597. <li>Frontend</li>
  598. <li>Liberty</li>
  599. <li>Nginx</li>
  600. <li>Redis</li>
  601. <li>Tomcat</li>
  602. </ul>
  603. <p>Built in Network</p>
  604. <ul>
  605. <li>Flannel</li>
  606. <li>Calico</li>
  607. </ul>
  608. <p>Built in persistent Storage</p>
  609. <ul>
  610. <li>NFS</li>
  611. <li>Hostpath</li>
  612. <li>GlusterFs</li>
  613. </ul>
  614. <p>Supported CPU Architecture</p>
  615. <ul>
  616. <li>PowerPC LE</li>
  617. <li>x86</li>
  618. </ul>
  619. <p><a href="https://collaborationben.files.wordpress.com/2017/03/cwc_architecture.jpg"><img data-attachment-id="825" data-permalink="https://collaborationben.com/2017/03/16/connections-pink-and-container-orchestration-using-cfc/cwc_architecture/#main" data-orig-file="https://collaborationben.files.wordpress.com/2017/03/cwc_architecture.jpg?w=776" data-orig-size="530,350" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;}" data-image-title="Cwc_Architecture" data-image-description="" data-medium-file="https://collaborationben.files.wordpress.com/2017/03/cwc_architecture.jpg?w=776?w=300" data-large-file="https://collaborationben.files.wordpress.com/2017/03/cwc_architecture.jpg?w=776?w=530" class="alignnone size-full wp-image-825" src="https://collaborationben.files.wordpress.com/2017/03/cwc_architecture.jpg?w=776" alt="" srcset="https://collaborationben.files.wordpress.com/2017/03/cwc_architecture.jpg 530w, https://collaborationben.files.wordpress.com/2017/03/cwc_architecture.jpg?w=150 150w, https://collaborationben.files.wordpress.com/2017/03/cwc_architecture.jpg?w=300 300w" sizes="(max-width: 530px) 100vw, 530px"   /></a></p><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/collaborationben.wordpress.com/824/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/collaborationben.wordpress.com/824/" /></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=824&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
  620. <wfw:commentRss>https://collaborationben.com/2017/03/16/connections-pink-and-container-orchestration-using-cfc/feed/</wfw:commentRss>
  621. <slash:comments>0</slash:comments>
  622. <media:content url="http://1.gravatar.com/avatar/73d65d70497b3486650a324a0d88ecf1?s=96&#38;d=identicon&#38;r=G" medium="image">
  623. <media:title type="html">collaborationben</media:title>
  624. </media:content>
  625.  
  626. <media:content url="http://collaborationben.files.wordpress.com/2017/03/cwc_architecture.jpg" medium="image" />
  627. </item>
  628. <item>
  629. <title>Whiteboard now removed from Sametime meetings</title>
  630. <link>https://collaborationben.com/2017/03/14/whiteboard-now-removed-from-sametime-meetings/</link>
  631. <comments>https://collaborationben.com/2017/03/14/whiteboard-now-removed-from-sametime-meetings/#comments</comments>
  632. <pubDate>Tue, 14 Mar 2017 21:30:51 +0000</pubDate>
  633. <dc:creator><![CDATA[collaborationben]]></dc:creator>
  634. <category><![CDATA[Uncategorized]]></category>
  635. <category><![CDATA[ibmsametime]]></category>
  636. <category><![CDATA[Meetings]]></category>
  637. <category><![CDATA[sametime]]></category>
  638. <category><![CDATA[whiteboard]]></category>
  639.  
  640. <guid isPermaLink="false">http://collaborationben.com/?p=818</guid>
  641. <description><![CDATA[I created Whiteboard in Sametime 9.0.1 after finding that a whiteboard feature was added to meetings some time ago. This morning Andreas Bader got back to the Skype group, IBM Sametime Community Chat after finding that the whiteboard feature had been removed after applying the latest Meeting server patch. Andreas had logged a PMR asking [&#8230;]<img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=818&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
  642. <content:encoded><![CDATA[<p>I created <a href="https://collaborationben.com/2016/05/20/whiteboard-in-sametime-9-0-1/" target="_blank">Whiteboard in Sametime 9.0.1</a> after finding that a whiteboard feature was added to meetings some time ago.</p>
  643. <p>This morning Andreas Bader got back to the Skype group, <a href="https://join.skype.com/o43ARAJCwdHK">IBM Sametime Community Chat</a> after finding that the whiteboard feature had been removed after applying the latest Meeting server patch. Andreas had logged a PMR asking IBM where it had gone. IBM&#8217;s response was;</p>
  644. <p>&#8220;I can confirm The Meetings Whiteboard feature release is being put on hold indefinitely.<br />
  645. The module &#8220;Core Whiteboard Services&#8221; has been removed permanently from the ST Meetings build, the whiteboard was an unsupported proof of concept feature.&#8221;</p>
  646. <p>Cheers IBM. You finally gave us something people wanted for ages and then took it away.</p><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/collaborationben.wordpress.com/818/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/collaborationben.wordpress.com/818/" /></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=818&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
  647. <wfw:commentRss>https://collaborationben.com/2017/03/14/whiteboard-now-removed-from-sametime-meetings/feed/</wfw:commentRss>
  648. <slash:comments>2</slash:comments>
  649. <media:content url="http://1.gravatar.com/avatar/73d65d70497b3486650a324a0d88ecf1?s=96&#38;d=identicon&#38;r=G" medium="image">
  650. <media:title type="html">collaborationben</media:title>
  651. </media:content>
  652. </item>
  653. <item>
  654. <title>Exception when Connections email digests are sent &#8211; LO90678</title>
  655. <link>https://collaborationben.com/2017/03/09/exception-when-connections-email-digests-are-sent-lo90678/</link>
  656. <comments>https://collaborationben.com/2017/03/09/exception-when-connections-email-digests-are-sent-lo90678/#respond</comments>
  657. <pubDate>Thu, 09 Mar 2017 10:03:48 +0000</pubDate>
  658. <dc:creator><![CDATA[collaborationben]]></dc:creator>
  659. <category><![CDATA[Connections]]></category>
  660. <category><![CDATA[database]]></category>
  661. <category><![CDATA[ibmconnections]]></category>
  662. <category><![CDATA[LO90678]]></category>
  663. <category><![CDATA[news]]></category>
  664. <category><![CDATA[notifications]]></category>
  665.  
  666. <guid isPermaLink="false">http://collaborationben.com/?p=816</guid>
  667. <description><![CDATA[I saw the following error in the Infrastructure SystemOut.log each day when the daily or weekly digest is sent on this Connections 5.5 CR2 server. ************************** Weekly Email Digest Report ************************** Tranche ID: tranche_2_5oPldKwZTaR7aAiPFw4L08CyRW Start Time: 7 Mar 2017 23:00:02 GMT -&#62; End Time: 7 Mar 2017 23:00:02 GMT Users Processed: 4, Digest Mails Sent: [&#8230;]<img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=816&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
  668. <content:encoded><![CDATA[<p>I saw the following error in the Infrastructure SystemOut.log each day when the daily or weekly digest is sent on this Connections 5.5 CR2 server.</p>
  669. <p>**************************<br />
  670. Weekly Email Digest Report<br />
  671. **************************<br />
  672. Tranche ID: tranche_2_5oPldKwZTaR7aAiPFw4L08CyRW<br />
  673. Start Time: 7 Mar 2017 23:00:02 GMT -&gt; End Time: 7 Mar 2017 23:00:02 GMT<br />
  674. Users Processed: 4, Digest Mails Sent: 2<br />
  675. **************************<br />
  676. [3/7/17 23:00:04:110 GMT] 00000413 CrudDao       E com.ibm.lconn.hpnews.data.dao.impl.ibatis.CrudDao DELETE Batch &#8211; doInSqlMapClient Exception caught &#8211;<br />
  677. com.ibm.db2.jcc.am.BatchUpdateException: [jcc][t4][102][10040][3.69.66] Batch failure.  The batch was submitted, but at least one exception occurred on an individual member of the batch.<br />
  678. Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null</p>
  679. <p>I thought that there was a problem with data in the database and being a recent migration I thought there was something &#8220;bad&#8221; in there.</p>
  680. <p>db2 &#8220;select PERSON_ID, DISPLAYNAME, EXID from HOMEPAGE.PERSON where PERSON_ID in (select PERSON_ID FROM HOMEPAGE.EMD_EMAIL_PREFS where TRANCHE_ID = &#8216;tranche_1_5oPldKwZTaR7aAiPFw4L08CyRW&#8217;)&#8221;</p>
  681. <p>The above query gave me the users that were in this tranche. I then applied the following trace to see what was being sent</p>
  682. <p>*=info:com.ibm.lotus.connections.core.notify.*=all:com.ibm.lconn.news.*=all:com.ibm.lconn.hpnews.data.dao.impl.ibatis.*=all</p>
  683. <p>This really didn&#8217;t help me too much as the data looked fine. Then I turned to Google and found that <a href="https://www.linkedin.com/in/tedhardenburgh/" target="_blank">Ted Hardenburgh</a> had already come across this problem detailed in <a href="http://dominothoughts.com/DomThoughts/domthoughts.nsf/dx/ibm-connections-5.5-errors-in-systemout.log-cleaning-up-homepage-database.htm" target="_blank">IBM Connections 5.5 &#8211; Errors in SystemOut.log cleaning up HOMEPAGE database</a></p>
  684. <p>I raised a PMR and IBM sent me LO90678 which I applied. Checking the SystemOut.log the next day I still saw the same errors. IBM passed this back to development and they responded with, <em>&#8220;exceptions should go away after expiration period (default 30 days) for stories. News cleanup service should work normally after this period of time.&#8221;</em></p>
  685. <p>I have checked this morning and the exceptions at 23:00 seem to have stopped.</p><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/collaborationben.wordpress.com/816/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/collaborationben.wordpress.com/816/" /></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=collaborationben.com&#038;blog=17920770&#038;post=816&#038;subd=collaborationben&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
  686. <wfw:commentRss>https://collaborationben.com/2017/03/09/exception-when-connections-email-digests-are-sent-lo90678/feed/</wfw:commentRss>
  687. <slash:comments>0</slash:comments>
  688. <media:content url="http://1.gravatar.com/avatar/73d65d70497b3486650a324a0d88ecf1?s=96&#38;d=identicon&#38;r=G" medium="image">
  689. <media:title type="html">collaborationben</media:title>
  690. </media:content>
  691. </item>
  692. </channel>
  693. </rss>
  694.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//collaborationben.com/feed/

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda