<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 23, 2016 at 4:41 PM, Michael Scherer <span dir="ltr"><<a href="mailto:mscherer@redhat.com" target="_blank">mscherer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">Le mercredi 17 août 2016 à 18:46 +0200, Michael Scherer a écrit :<br>
> Le lundi 08 août 2016 à 15:11 +0200, Michael Scherer a écrit :<br>
> > Le mercredi 03 août 2016 à 14:43 +0200, Michael Scherer a écrit :<br>
> > > Le jeudi 28 juillet 2016 à 10:21 -0700, Amye Scavarda a écrit :<br>
> > > > On Thu, Jul 28, 2016 at 4:05 AM, Niels de Vos <<a href="mailto:ndevos@redhat.com">ndevos@redhat.com</a>> wrote:<br>
> > > ><br>
> > > > > On Thu, Jul 28, 2016 at 06:21:33AM -0400, Kaleb KEITHLEY wrote:<br>
> > > > > > On 07/27/2016 05:18 PM, Amye Scavarda wrote:<br>
> > > > > > ><br>
> > > > > > ><br>
> > > > > > > From the latest updates on the cage list, it looks like we're tracking<br>
> > > > > > > for these moves/downtime for August 8-9? That'll be Monday-Tuesday.<br>
> > > > > > > Any complaints about that schedule?<br>
> > > > > ><br>
> > > > > > 3.8.x releases are scheduled for the 10th of each month. In yesterday's<br>
> > > > > > Community meeting Niels said that 3.8.2 is planned to be released on<br>
> > > > > > schedule.<br>
> > > > > ><br>
> > > > > > If this goes as planned then it shouldn't be a problem, right?<br>
> > > > ><br>
> > > > > We just need to make sure that all patches for 3.8.2 have been tested in<br>
> > > > > the CI before the move. It shortens the development cycle a few days,<br>
> > > > > and it would have been nice to know a little more in advance and<br>
> > > > > mentioned in the community meeting.<br>
> > > > ><br>
> > > > > I do not think there are any critical patches for the release, so I do<br>
> > > > > not expect any problems with the outage either. (Although it really<br>
> > > > > isn't nice to treat 3.8 releases as guinea pig for infrastructure<br>
> > > > > changes.)<br>
> > > > ><br>
> > > > > Niels<br>
> > > > ><br>
> > > > > I brought this up to the community cage group this morning, and we'll look<br>
> > > > to move the VMs after the 3.8.2 release.<br>
> > > > I'll let Michael put in more details around exact timing.<br>
> > ><br>
> > > So we still do not have the exact timing, that's waiting on IT to<br>
> > > configure the network port (and then I have to copy data, and configure<br>
> > > the server for new network, and admin cards, and various stuff).<br>
> ><br>
> > So After coming back from weekend, and dealing with my backlog of mail<br>
> > and expenses, I just received a notification that IT did moved the<br>
> > server (on friday evening) and it does even answer to ping on the admin<br>
> > interface. So I will configure it for internet access later today or<br>
> > tomorow (depending on my capacity to read all mails and doing meetings),<br>
> > and will then plan to the test move once I am confident the server is<br>
> > ok.<br>
> ><br>
><br>
> So, news about the server.<br>
><br>
> I did see there was some weird lvm corruption (that I didn't<br>
> investigate), but couldn't find the exact fix. Turn out that this was<br>
> just removing extranous PV from the VG and that's it. However, since we<br>
> are speaking of moving production workload on it, I will need to<br>
> reformat it to use hardware raid, and so doing that tonight.<br>
<br>
</div></div>Ok so I did reformat and rename the server (with some pain, since the<br>
idrac interface is a bit annoying, and I did hit a few roadblock with<br>
java on linux, with Centos iso, with anaconda partitioning choices) Now,<br>
that's 4 disk in hardware raid 5, and the name is<br>
<a href="http://myrmicinae.rht.gluster.org" rel="noreferrer" target="_blank">myrmicinae.rht.gluster.org</a> (a type of ants).<br>
<br>
I will finish the ansiblization later.<br>
<span class=""><br>
> Then i will start to test the copy of VM once that part is done.<br>
<br>
</span>On that front, seems doing any kind of disk snapshot requires some<br>
downtime, because RHEL do remov^W differenciate features between qemu<br>
for RHEL and qemu for RHEV, so Centos inherit the limitation.<br>
<br>
So I guess we might need a few reboot, which will also permit to get<br>
kernel upgrade, etc. I have no idea of the needed downtime, but since<br>
that's just a reboot, I hope I can do that outside offices hours.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
--<br>
Michael Scherer<br>
Sysadmin, Community Infrastructure and Platform, OSAS<br>
<br></div></div></blockquote><div><br></div><div>Great!</div><div>Thanks for the update here. </div><div>At this point in time, do we have a good timeline for when the reboot can happen? </div><div>In short, is there a light at the end of the tunnel?</div><div>- amye </div><div><br></div></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Amye Scavarda | <a href="mailto:amye@redhat.com" target="_blank">amye@redhat.com</a> | Gluster Community Lead</div></div>
</div></div>