<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Within Reason comments</title>
    <link>http://typo.submonkey.net/</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>I do what I want</description>
    <item>
      <title>"VMware HA?" by Ian Fletcher</title>
      <description>Hi Ceri,

Just come across your comments regards VMware HA and I thought that I'd just explain that HA was designed to be a way of quickly restarting Virtual Machine in the event of the sudden loss of and ESX server (power, hardware etc.)

In addition it offers the option to force the power off of virtual machines in the event of an ESX server becoming isolated on the heartbeat network from the other ESX servers in the cluster. This is where you're certain that loss of connectivity on the heartbeat network will also result in loss of connectivity for VMs on the VM network.

The other option is to leave VMs running and assume that the loss is just of the heartbeat network.

Hence the need to have resilience for the service console network to avoid isolation of an ESX server causing what in effect would be a "false positive" for ESX isolation.

To protect the VM network you should be looking at NIC teaming and for the storage ensuring that you have multi-pathing. HA isn't designed to help you with those network and storage problems.

HA is all about restarting VMs in the event of an ESX failure and also some options in the event of an ESX server being isolated - dependant on the physical equipment being used for the service console and VM networks.
</description>
      <pubDate>Mon, 06 Jul 2009 13:00:22 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:c75b5868-6bb8-420e-a4a0-9a63f0dd589d</guid>
      <link>http://typo.submonkey.net/articles/2009/05/24/vmware-ha#comment-1917</link>
    </item>
    <item>
      <title>"Doubts Even Here: the point of disbelief" by Michael Janke</title>
      <description>Ceri - 

Thanks for the de-hyping. It's a good read. ;)

--Mike
</description>
      <pubDate>Sun, 31 May 2009 01:12:09 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:ed7945e7-00b4-49f4-841c-c20b44b945af</guid>
      <link>http://typo.submonkey.net/articles/2009/05/30/doubts-even-here-the-point-of-disbelief#comment-1765</link>
    </item>
    <item>
      <title>"VMware HA?" by Ceri Davies</title>
      <description>@majinbo,

That's a reasonable idea but unfortunately would cause VMware HA to become even less likely to fail given a network failure.

&lt;p&gt;Setting the filer IP as the only isolation address (setting das.usedefaultisolationaddress false and das.isolationaddress to the filer's IP) wold protect from filer loss, but not from service console loss and of course does nothing for Fiber Channel users.&lt;/p&gt;

&lt;p&gt;I think that the best mitigation I can currently manage is to put the Service Console on the same physical interfaces as the Virtual Machine networks so that a failure of either will cause a failover.&lt;/p&gt;

&lt;p&gt;As for FC failure, compounded with the complete lack of mirroring, we're just SOL.&lt;p&gt;&lt;/p&gt;&lt;/p&gt;</description>
      <pubDate>Sat, 30 May 2009 19:19:51 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:bdf9558f-cb56-49e9-93d5-e617943e0b86</guid>
      <link>http://typo.submonkey.net/articles/2009/05/24/vmware-ha#comment-1763</link>
    </item>
    <item>
      <title>"VMware HA?" by majinboo</title>
      <description>I think that you could improve the reliability by modifying your setup :
 - use the das.isolationaddress parameter, you can provide a second address by using das.isolationadress2. You can put any IP address that responds to ICMP ping requests. So in you setup, you may use gateway's IP and your filer's IP.
 - configure the isolation response in virtualcenter

If you haven't read it, I suggest you to read this WhitePaper : &lt;a href="http://www.vmware.com/resources/techresources/402"&gt;http://www.vmware.com/resources/techresources/402&lt;/a&gt; . This a good starting point on the subject.

</description>
      <pubDate>Mon, 25 May 2009 10:34:36 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:f11b75d7-52ed-47c3-9f98-821283ff3520</guid>
      <link>http://typo.submonkey.net/articles/2009/05/24/vmware-ha#comment-1762</link>
    </item>
    <item>
      <title>"Check your T5220!" by Alicia</title>
      <description>Im waiting for a more improved version to come out. I dont care how long the wait, because this series kinda sucks to be honest.</description>
      <pubDate>Sun, 17 Feb 2008 08:11:21 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:3d664668-db27-454c-b870-bea8b940e774</guid>
      <link>http://typo.submonkey.net/articles/2008/02/15/check-your-t5220#comment-1516</link>
    </item>
    <item>
      <title>"OpenSolaris as SCSI target" by Ceri</title>
      <description>Hi Ceri,

Yes, it's a little weird :)

These are not my binaries, they're the ones provided by the COMSTAR project and yes, they do work on Solaris 10.  Specifically, it's Solaris 10 update 3 with a reasonable number of patches.

I'm not sure what compiler the COMSTAR team used, but these ones definitely work.

PS I've emailed this response as well.</description>
      <pubDate>Tue, 11 Dec 2007 22:03:06 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:0e0ef845-afdf-454d-978d-b745b7b7c44c</guid>
      <link>http://typo.submonkey.net/articles/2007/11/19/opensolaris-as-scsi-target#comment-920</link>
    </item>
    <item>
      <title>"OpenSolaris as SCSI target" by CeriDavies@Hotmail.com</title>
      <description>Hi, my name is Ceri (Ifor) Davies, I am writing a qlogic target mode driver for solaris 10, and am thinking of switching to Comstar.  Are you recompiling for solaris 10, or are you saying your nevada binaries worked with solaris 10?  That would surprise me, since nevada uses stdio 11 (I think).  The qlogic qlc driver panics on solaris 10 if compiled with studio 11, and has to be compiled with studio 10.

P.S. Your having the same name is weird</description>
      <pubDate>Tue, 11 Dec 2007 21:34:53 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:234fddfb-c147-40bb-87b0-694a8d1e3a28</guid>
      <link>http://typo.submonkey.net/articles/2007/11/19/opensolaris-as-scsi-target#comment-919</link>
    </item>
    <item>
      <title>"message overflow on /dev/log minor #5 -- is syslogd(1M) running?" by joeli</title>
      <description>Me says thank you too! ;)</description>
      <pubDate>Mon, 10 Sep 2007 14:11:28 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:8eb6b022-5f14-4404-a3d2-7f4564bf939b</guid>
      <link>http://typo.submonkey.net/articles/2007/07/23/message-overflow-on-dev-log-minor-5-is-syslogd-1m-running#comment-910</link>
    </item>
    <item>
      <title>"NetBeans on FreeBSD" by Ceri Davies</title>
      <description>Hi Amit,

I hadn't; do you mean the milestones, eg &lt;a href="http://dlc.sun.com/netbeans/download/6.0/milestones/latest/"&gt;http://dlc.sun.com/netbeans/download/6.0/milestones/latest/&lt;/a&gt; ?
&lt;br /&gt;
Not sure why you can't just provide FreeBSD builds to be honest ;-)</description>
      <pubDate>Tue, 04 Sep 2007 09:38:26 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:71ebae5f-10b1-4772-af11-08fa43fc0a18</guid>
      <link>http://typo.submonkey.net/articles/2007/07/13/netbeans-on-freebsd#comment-908</link>
    </item>
    <item>
      <title>"NetBeans on FreeBSD" by Amit</title>
      <description>Hi!

I am Amit, NetBeans Community Docs co-ordinator.

Did you try NetBeans 6 development builds on FeeBSD? If you have not why dont you try it out and may be contribute a small write up to the NetBeans Community Docs.

Looking forward to see your contribution.

Thanks

Amit
</description>
      <pubDate>Mon, 03 Sep 2007 09:47:46 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:970e0a2e-a672-4ebf-b732-bd4b45f629bd</guid>
      <link>http://typo.submonkey.net/articles/2007/07/13/netbeans-on-freebsd#comment-907</link>
    </item>
  </channel>
</rss>
