<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>My Blog &#187; Work</title>
	<atom:link href="http://blog.wianecki.com/category/work/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wianecki.com</link>
	<description>my own personal blog</description>
	<lastBuildDate>Thu, 09 Feb 2012 15:39:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Solaris provisioning errors &#8216;FAILED: Timed out while waiting for OS Provisioning agent&#8217;</title>
		<link>http://blog.wianecki.com/2009/11/24/solaris-provisioning-errors-failed-timed-out-while-waiting-for-os-provisioning-agent/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=solaris-provisioning-errors-failed-timed-out-while-waiting-for-os-provisioning-agent</link>
		<comments>http://blog.wianecki.com/2009/11/24/solaris-provisioning-errors-failed-timed-out-while-waiting-for-os-provisioning-agent/#comments</comments>
		<pubDate>Tue, 24 Nov 2009 16:53:28 +0000</pubDate>
		<dc:creator>cw</dc:creator>
				<category><![CDATA[Opsware SAS]]></category>
		<category><![CDATA[Opsware]]></category>
		<category><![CDATA[SA]]></category>
		<category><![CDATA[SAS]]></category>

		<guid isPermaLink="false">http://blog.wianecki.com/?p=4127</guid>
		<description><![CDATA[<p>Posted in <a href="http://blog.wianecki.com/category/work/frb/opsware-sas/" title="Opsware SAS">Opsware SAS</a></p>Technical document information Title: Solaris provisioning errors &#039;FAILED: Timed out while waiting for OS Provisioning agent&#039; Document ID: KM719530 Product: Server Automation Version: Updated: 2009-Apr-24 Problem Fix]]></description>
		<wfw:commentRss>http://blog.wianecki.com/2009/11/24/solaris-provisioning-errors-failed-timed-out-while-waiting-for-os-provisioning-agent/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Opsware Core unable to communicate to agent running on Symantec PureDisk SuSE server.</title>
		<link>http://blog.wianecki.com/2009/08/12/opsware-core-unable-to-communicate-to-agent-running-on-symantec-puredisk-suse-server/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=opsware-core-unable-to-communicate-to-agent-running-on-symantec-puredisk-suse-server</link>
		<comments>http://blog.wianecki.com/2009/08/12/opsware-core-unable-to-communicate-to-agent-running-on-symantec-puredisk-suse-server/#comments</comments>
		<pubDate>Wed, 12 Aug 2009 13:39:44 +0000</pubDate>
		<dc:creator>cw</dc:creator>
				<category><![CDATA[Opsware SAS]]></category>
		<category><![CDATA[Opsware]]></category>
		<category><![CDATA[PD]]></category>
		<category><![CDATA[puredisk]]></category>
		<category><![CDATA[SA]]></category>
		<category><![CDATA[SAS]]></category>
		<category><![CDATA[server automation]]></category>
		<category><![CDATA[symantec]]></category>

		<guid isPermaLink="false">http://blog.wianecki.com/?p=3782</guid>
		<description><![CDATA[<p>Posted in <a href="http://blog.wianecki.com/category/work/frb/opsware-sas/" title="Opsware SAS">Opsware SAS</a></p>Having issue to talk back to Symantec PureDisk SuSE server, port 1002 is closed on PD firewall (iptables). To add this as an exception do the following 1)login to PD server 2) cp -p /etc/puredisk/custom_iptables_rules /etc/puredisk/custom_iptables_rules.orig 3) vi /etc/puredisk/custom_iptables_rules 4) add the following entry # protocol (tcp,udp,tcmp,all) source[/mask] port tcp 10.10.10.1 1002 # where 10.10.10.1 [...]]]></description>
		<wfw:commentRss>http://blog.wianecki.com/2009/08/12/opsware-core-unable-to-communicate-to-agent-running-on-symantec-puredisk-suse-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How do I keep my Red Hat Linux servers up to date with HP Server Automation</title>
		<link>http://blog.wianecki.com/2009/07/25/how-do-i-keep-my-red-hat-linux-servers-up-to-date-with-hp-server-automation/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=how-do-i-keep-my-red-hat-linux-servers-up-to-date-with-hp-server-automation</link>
		<comments>http://blog.wianecki.com/2009/07/25/how-do-i-keep-my-red-hat-linux-servers-up-to-date-with-hp-server-automation/#comments</comments>
		<pubDate>Sat, 25 Jul 2009 13:30:46 +0000</pubDate>
		<dc:creator>cw</dc:creator>
				<category><![CDATA[Opsware SAS]]></category>
		<category><![CDATA[HP]]></category>
		<category><![CDATA[Opsware]]></category>
		<category><![CDATA[SAS]]></category>
		<category><![CDATA[server automation]]></category>

		<guid isPermaLink="false">http://blog.wianecki.com/?p=3691</guid>
		<description><![CDATA[<p>Posted in <a href="http://blog.wianecki.com/category/work/frb/opsware-sas/" title="Opsware SAS">Opsware SAS</a></p>Technical document information Title: How do I keep my Red Hat Linux servers up to date with HP Server Automation Document ID: KM740084 Product: Server Automation Version: Updated: 2009-May-18 HP Server Automation(SA) has a feature that allows integration with your Red Hat Network(RHN) account to allow you to import content from RHN into your SA [...]]]></description>
		<wfw:commentRss>http://blog.wianecki.com/2009/07/25/how-do-i-keep-my-red-hat-linux-servers-up-to-date-with-hp-server-automation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>virtual server on my rhel 5 not starting</title>
		<link>http://blog.wianecki.com/2009/07/25/virtual-server-on-my-rhel-5-not-starting/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=virtual-server-on-my-rhel-5-not-starting</link>
		<comments>http://blog.wianecki.com/2009/07/25/virtual-server-on-my-rhel-5-not-starting/#comments</comments>
		<pubDate>Sat, 25 Jul 2009 13:27:54 +0000</pubDate>
		<dc:creator>cw</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Opsware SAS]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[virtual server]]></category>
		<category><![CDATA[virtualization]]></category>
		<category><![CDATA[vm]]></category>
		<category><![CDATA[xen]]></category>

		<guid isPermaLink="false">http://blog.wianecki.com/?p=3689</guid>
		<description><![CDATA[<p>Posted in <a href="http://blog.wianecki.com/category/unix/os/linux/" title="Linux">Linux</a><a href="http://blog.wianecki.com/category/work/frb/opsware-sas/" title="Opsware SAS">Opsware SAS</a><a href="http://blog.wianecki.com/category/unix/os/" title="OS">OS</a></p>Sometime ago installed my RedHat 5 with xen. Then I needed to create a virtual server running RedHat 4 in it, all needed to be 64 bit because Opsware required 64 bit RHEL AS4, so had to come up with an inexpensive solution. Got Intel Quad from Dell for $400 with 8gb ram, inexpensive desktop, [...]]]></description>
		<wfw:commentRss>http://blog.wianecki.com/2009/07/25/virtual-server-on-my-rhel-5-not-starting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Server Automation: Gateway name resolution error &#8211; gateway.proxyError</title>
		<link>http://blog.wianecki.com/2009/07/21/server-automation-gateway-name-resolution-error-gateway-proxyerror/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=server-automation-gateway-name-resolution-error-gateway-proxyerror</link>
		<comments>http://blog.wianecki.com/2009/07/21/server-automation-gateway-name-resolution-error-gateway-proxyerror/#comments</comments>
		<pubDate>Wed, 22 Jul 2009 01:35:22 +0000</pubDate>
		<dc:creator>cw</dc:creator>
				<category><![CDATA[Opsware SAS]]></category>
		<category><![CDATA[Gateway name resolution error - gateway.proxyError]]></category>
		<category><![CDATA[gateway.proxyError]]></category>
		<category><![CDATA[HP]]></category>
		<category><![CDATA[Opsware]]></category>
		<category><![CDATA[SA]]></category>
		<category><![CDATA[SAS]]></category>

		<guid isPermaLink="false">http://blog.wianecki.com/?p=3595</guid>
		<description><![CDATA[<p>Posted in <a href="http://blog.wianecki.com/category/work/frb/opsware-sas/" title="Opsware SAS">Opsware SAS</a></p>]]></description>
		<wfw:commentRss>http://blog.wianecki.com/2009/07/21/server-automation-gateway-name-resolution-error-gateway-proxyerror/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>how to import cert from opsware into your browser</title>
		<link>http://blog.wianecki.com/2009/07/20/how-to-import-cert-from-opsware-into-your-browser/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=how-to-import-cert-from-opsware-into-your-browser</link>
		<comments>http://blog.wianecki.com/2009/07/20/how-to-import-cert-from-opsware-into-your-browser/#comments</comments>
		<pubDate>Mon, 20 Jul 2009 20:46:24 +0000</pubDate>
		<dc:creator>cw</dc:creator>
				<category><![CDATA[Opsware SAS]]></category>
		<category><![CDATA[HP]]></category>
		<category><![CDATA[Opsware]]></category>
		<category><![CDATA[server automation]]></category>

		<guid isPermaLink="false">http://blog.wianecki.com/?p=3512</guid>
		<description><![CDATA[<p>Posted in <a href="http://blog.wianecki.com/category/work/frb/opsware-sas/" title="Opsware SAS">Opsware SAS</a></p>Recently I needed to connect my browser to my opsware port 1004 but I got problems with certificate. This is where I needed to connect to: opsware:1004/ but I was getting nowhere as certificates were not installed for it. Solution is simple. I had to go to my opsware core server to the following directory: [...]]]></description>
		<wfw:commentRss>http://blog.wianecki.com/2009/07/20/how-to-import-cert-from-opsware-into-your-browser/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Opswsshd Jail fail to start</title>
		<link>http://blog.wianecki.com/2009/07/01/opswsshd-jail-fail-to-start/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=opswsshd-jail-fail-to-start</link>
		<comments>http://blog.wianecki.com/2009/07/01/opswsshd-jail-fail-to-start/#comments</comments>
		<pubDate>Wed, 01 Jul 2009 15:33:47 +0000</pubDate>
		<dc:creator>cw</dc:creator>
				<category><![CDATA[Opsware SAS]]></category>
		<category><![CDATA[HP]]></category>
		<category><![CDATA[Opsware]]></category>
		<category><![CDATA[SA]]></category>
		<category><![CDATA[SAS]]></category>
		<category><![CDATA[server automation]]></category>

		<guid isPermaLink="false">http://blog.wianecki.com/2009/07/01/opswsshd-jail-fail-to-start/</guid>
		<description><![CDATA[<p>Posted in <a href="http://blog.wianecki.com/category/work/frb/opsware-sas/" title="Opsware SAS">Opsware SAS</a></p>Technical document information Title: Opswsshd Jail fail to start Document ID: KM743112 Product: Server Automation Version: Updated: 2009-Jun-01 Problem Fix]]></description>
		<wfw:commentRss>http://blog.wianecki.com/2009/07/01/opswsshd-jail-fail-to-start/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Minimum permissions required to change &#8220;Server Use&#8221; or &#8220;Deployment Stage&#8221;</title>
		<link>http://blog.wianecki.com/2009/06/01/minimum-permissions-required-to-change-server-use-or-deployment-stage-2/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=minimum-permissions-required-to-change-server-use-or-deployment-stage-2</link>
		<comments>http://blog.wianecki.com/2009/06/01/minimum-permissions-required-to-change-server-use-or-deployment-stage-2/#comments</comments>
		<pubDate>Mon, 01 Jun 2009 16:27:40 +0000</pubDate>
		<dc:creator>cw</dc:creator>
				<category><![CDATA[Opsware SAS]]></category>
		<category><![CDATA[HP]]></category>
		<category><![CDATA[Opsware]]></category>
		<category><![CDATA[SA]]></category>
		<category><![CDATA[SAS]]></category>
		<category><![CDATA[server automation]]></category>

		<guid isPermaLink="false">http://blog.wianecki.com/?p=3712</guid>
		<description><![CDATA[<p>Posted in <a href="http://blog.wianecki.com/category/work/frb/opsware-sas/" title="Opsware SAS">Opsware SAS</a></p>Technical document information Title: Minimum permissions required to change &#034;Server Use&#034; or &#034;Deployment Stage&#034; Document ID: KM743283 Product: Server Automation Version: Updated: 2009-Jun-01 You&#8217;re setting up a user group and want to give only the minimum permissions required for the task at hand.&#160; The task includes being able to change Server Use and/or Deployment Stage [...]]]></description>
		<wfw:commentRss>http://blog.wianecki.com/2009/06/01/minimum-permissions-required-to-change-server-use-or-deployment-stage-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>dumping session from opsware</title>
		<link>http://blog.wianecki.com/2009/04/21/dumping-session-from-opsware/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=dumping-session-from-opsware</link>
		<comments>http://blog.wianecki.com/2009/04/21/dumping-session-from-opsware/#comments</comments>
		<pubDate>Tue, 21 Apr 2009 14:05:18 +0000</pubDate>
		<dc:creator>cw</dc:creator>
				<category><![CDATA[FRB]]></category>
		<category><![CDATA[Opsware SAS]]></category>
		<category><![CDATA[Work]]></category>
		<category><![CDATA[dump_session.pyc]]></category>
		<category><![CDATA[Opsware]]></category>
		<category><![CDATA[PYTHONPATH]]></category>

		<guid isPermaLink="false">http://blog.wianecki.com/?p=1520</guid>
		<description><![CDATA[<p>Posted in <a href="http://blog.wianecki.com/category/work/frb/" title="FRB">FRB</a><a href="http://blog.wianecki.com/category/work/frb/opsware-sas/" title="Opsware SAS">Opsware SAS</a><a href="http://blog.wianecki.com/category/work/" title="Work">Work</a></p>Sometimes I need to dump session which did not work and send to support, here is quick how to do it. I am just putting this for myself for me to find it easily as I do it with this rest of my blog, so if you find this useful then its great if not [...]]]></description>
		<wfw:commentRss>http://blog.wianecki.com/2009/04/21/dumping-session-from-opsware/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Server Automation / opsware Inventory Model</title>
		<link>http://blog.wianecki.com/2009/04/01/server-automation-opsware-inventory-model/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=server-automation-opsware-inventory-model</link>
		<comments>http://blog.wianecki.com/2009/04/01/server-automation-opsware-inventory-model/#comments</comments>
		<pubDate>Wed, 01 Apr 2009 12:41:17 +0000</pubDate>
		<dc:creator>cw</dc:creator>
				<category><![CDATA[Opsware SAS]]></category>
		<category><![CDATA[Opsware]]></category>
		<category><![CDATA[SA]]></category>
		<category><![CDATA[SAS]]></category>
		<category><![CDATA[twister]]></category>

		<guid isPermaLink="false">http://blog.wianecki.com/?p=1189</guid>
		<description><![CDATA[<p>Posted in <a href="http://blog.wianecki.com/category/work/frb/opsware-sas/" title="Opsware SAS">Opsware SAS</a></p>If you would like to connect to the API documentation that describes the SA Plataform API, you should do the following: 1. You must copy to your local system the certificate (p12 file) available in your SA Core under /var/opt/opsware/crypto/spin/ directory. 2. When importing the certificate, it requires the password provided in the response file [...]]]></description>
		<wfw:commentRss>http://blog.wianecki.com/2009/04/01/server-automation-opsware-inventory-model/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

