<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000'>Thanks, Eco!<br><br>Looks like we'll have a planned outage on www.gluster.org later tonight, starting at about 6pm PDT/9pm EDT/01:00 UTC , and should be back online later this evening PDT or early morning EDT.<br><br>The blog and wiki at gluster.org will be inaccessible during this time, but dev services, ie. git, gerritt and jenkins, will run normally throughout. <br><br>Thanks,<br>JM<br><br><br><hr id="zwchr"><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;">
  

    
  
  
    <font face="Cantarell">All,<br>
      <br>
      Here is the proposed outage plan for the Gluster.org server
      upgrade.&nbsp; I plan on sometime after 6PM tomorrow as long as noone
      has any objections to the following:<br>
      <br>
      Upgrade plan for Gluster primary mirror (184.106.200.248)<br>
      <br>
      Pre-work done:<br>
      <br>
      1) Backups of configuration files and non-website specific items
      have been made but not exported off the system yet:<br>
      mkdir -p /var/tmp/upgbax<br>
      cp -a /etc/ /root/ /var/lib/ /var/lib/dpkg
      /var/lib/apt/extended_states /var/lib/aptitude/pkgstates /backup
      /database-backup \<br>
/home/{ab,admin,andyb,avati,backup,bala,caitlin,cole,community.gluster.com,cooking2.gluster.com,cooking.gluster.com,eco,\<br>
freeipmi,glasscanopy,greg,harsha,jjulian,johnm,krishna,mail.gluster.com,mezzanine,paratai,rtadmin,sampath,selvam,sshadmin,\<br>
      support.gluster.com,techniweb,webteam,<a class="moz-txt-link-abbreviated" href="http://www.zresearch.com" target="_blank">www.zresearch.com</a>}
      /var/tmp/upgbax<br>
      <br>
      2) Verified the following per
<a class="moz-txt-link-freetext" href="http://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html" target="_blank">http://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html</a><br>
      - No "splashy" package exists<br>
      - apt-get -s update returns NULL<br>
      - grep -v \# /etc/apt/sources.list <br>
      deb <a class="moz-txt-link-freetext" href="http://ftp.debian.org/debian/" target="_blank">http://ftp.debian.org/debian/</a> squeeze main contrib non-free<br>
      deb <a class="moz-txt-link-freetext" href="http://security.debian.org/" target="_blank">http://security.debian.org/</a> squeeze/updates main contrib
      non-free <br>
      <br>
      3) Verified kernel &gt; 2.6.26<br>
      # uname -r<br>
      2.6.35.4-rscloud<br>
      <br>
      4) Verified low likelihood of issues described in
<a class="moz-txt-link-freetext" href="http://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html" target="_blank">http://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html</a><br>
      <br>
      <br>
      Proposed outage plan:<br>
      <br>
      Phase I - pre-work (15 minutes)<br>
      1) Communicate outage begins<br>
      2) DNS cutover to mirror server<br>
      Phase II - upgrade (unknown)<br>
      3) mount -o remount,rw /<br>
      4) apt-get upgrade<br>
      5) apt-get dist-upgrade<br>
      Phase III (15 minutes<br>
      6)upgrade-from-grub-legacy<br>
      7) Verify site is available via curl<br>
      8) Cut-back DNS<br>
      9) Communicate outage complete<br>
      10) Sit back with a smug grin on my face, resolute in the
      knowledge that this endeavor, like all I undertake, had
      absolutely, positively NOTHING whatsoever go wrong.<br>
    </font>
  

<br>_______________________________________________<br>Gluster-infra mailing list<br>Gluster-infra@gluster.org<br>http://www.gluster.org/cgi-bin/mailman/listinfo/gluster-infra<br></blockquote><br></div></body></html>