[Gluster-infra] [Bug 1291537] [RFE] Provide mechanism to spin up reproducible test environment for all developers
https://bugzilla.redhat.com/show_bug.cgi?id=1291537 --- Comment #24 from Vijay Bellur --- REVIEW: http://review.gluster.org/14046 (vagrant-test: added more options and centos6 base box) posted (#1) for review on master by Raghavendra Talur (rta...@redhat.com) -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=nx7lZgimHo&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] r.g.o down?
Le jeudi 21 avril 2016 à 14:21 +0200, Michael Scherer a écrit : > Le jeudi 21 avril 2016 à 15:01 +0530, Kaushal M a écrit : > > On Thu, Apr 21, 2016 at 2:58 PM, Michael Scherer wrote: > > > Le jeudi 21 avril 2016 à 14:29 +0530, Kaushal M a écrit : > > >> On Thu, Apr 21, 2016 at 1:14 PM, Michael Scherer wrote: > > >> > Le jeudi 21 avril 2016 à 12:47 +0530, Kaushal M a écrit : > > >> >> I restarted Gerrit that should have fixed it for now. > > >> >> > > >> >> As this has happened several times since the migration, I thought > > >> >> something wasn't done correctly. > > >> >> Turns out the gerrit VM is a really-(really)-low end VM with just 1 > > >> >> CPU core and 2GBs of RAM!! > > >> >> > > >> >> Michael, was this intentional or did you some how overlook this? > > >> > > > >> > I likely overlooked. I reused the same type of VM than the one for > > >> > > > >> >> IIRC, > > >> >> before the migration the VM was running with a dual-core CPU at least > > >> >> and more RAM. > > >> > > > >> > 4G of ram and 2 cpus. So I propose to go to 6G and still 2 cpu for now > > >> > ? > > >> > > >> Fine with me. We always have room to grow if required. > > >> > > >> > > > >> >> The hypervisor has more than enough resources to run a beefier VM. I > > >> >> was thinking of bumping the VM to a 4 Cores and 8 GB of RAM (or more). > > >> >> I'll do this if there are no objections. > > >> > > > >> > This requires a reboot however, is this ok ? > > >> > > >> Doing this shouldn't take longer that ~5minutes. We could do it any time. > > >> It would have been so much easier if libvirt allowed hot-plugging cpu > > >> and ram like disks. > > > > > > Seems to be supported in openstack, and in version we use on RHEL 7. > > > > > > And virsh has a command setvcpus with a --live switch, and the same for > > > the ram. > > > > TIL! I've been trying to do this all the time by editing the VM xml > > config. I believe virt-manager does the same as well, because it fails > > to add cpus live as well. > > so Kaushal tested and this requires a specific setup for that before. > > > > > > > Shall I try later today ? > > > (worst case, it crash and we reboot) > > > > Sure. > > So i am gonna shutdown the VM and increase ressources now. So 5 minutes > of downtime. Of course, things didn't work as planned, since the VM was for some reason still starting on the xen kernel (likely a kernel upgrade). So I did wiped all trace of xen, increased the ram, the cpu, planned for future memory/cpu upgrade if required, and things seems to go well. Until i found that gerrit was not started at boot correctly. So to be fixed later, but for now, this is working fine it seems. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS signature.asc Description: This is a digitally signed message part ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] r.g.o down?
Le jeudi 21 avril 2016 à 15:01 +0530, Kaushal M a écrit : > On Thu, Apr 21, 2016 at 2:58 PM, Michael Scherer wrote: > > Le jeudi 21 avril 2016 à 14:29 +0530, Kaushal M a écrit : > >> On Thu, Apr 21, 2016 at 1:14 PM, Michael Scherer wrote: > >> > Le jeudi 21 avril 2016 à 12:47 +0530, Kaushal M a écrit : > >> >> I restarted Gerrit that should have fixed it for now. > >> >> > >> >> As this has happened several times since the migration, I thought > >> >> something wasn't done correctly. > >> >> Turns out the gerrit VM is a really-(really)-low end VM with just 1 > >> >> CPU core and 2GBs of RAM!! > >> >> > >> >> Michael, was this intentional or did you some how overlook this? > >> > > >> > I likely overlooked. I reused the same type of VM than the one for > >> > > >> >> IIRC, > >> >> before the migration the VM was running with a dual-core CPU at least > >> >> and more RAM. > >> > > >> > 4G of ram and 2 cpus. So I propose to go to 6G and still 2 cpu for now ? > >> > >> Fine with me. We always have room to grow if required. > >> > >> > > >> >> The hypervisor has more than enough resources to run a beefier VM. I > >> >> was thinking of bumping the VM to a 4 Cores and 8 GB of RAM (or more). > >> >> I'll do this if there are no objections. > >> > > >> > This requires a reboot however, is this ok ? > >> > >> Doing this shouldn't take longer that ~5minutes. We could do it any time. > >> It would have been so much easier if libvirt allowed hot-plugging cpu > >> and ram like disks. > > > > Seems to be supported in openstack, and in version we use on RHEL 7. > > > > And virsh has a command setvcpus with a --live switch, and the same for > > the ram. > > TIL! I've been trying to do this all the time by editing the VM xml > config. I believe virt-manager does the same as well, because it fails > to add cpus live as well. so Kaushal tested and this requires a specific setup for that before. > > > > Shall I try later today ? > > (worst case, it crash and we reboot) > > Sure. So i am gonna shutdown the VM and increase ressources now. So 5 minutes of downtime. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] build seems to be hung again
Hi all, Netbsd regression [1] has been running for 3 hrs, but its still building. Seems like there is some issue here. Anyone aware of whats going on here? [1] https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/16000/ regards, Raghavendra ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] gluster blog contents distorted
So as I noted in the #gluster-meeting when this was brought up, this is a WordPress issue in that it sometimes strips formatting, we've seen this a few times. If you're writing posts that are likely to be syndicated, try using inline styling for images instead of relying on your own blog to do so, because once it syndicates to blog.gluster.org, it doesn't update. - amye On Wed, Apr 20, 2016 at 1:06 PM, Saravanakumar Arumugam wrote: > > > On 04/20/2016 08:47 PM, Michael Scherer wrote: > >> Le mercredi 20 avril 2016 à 18:33 +0530, Saravanakumar Arumugam a >> écrit : >> >>> Hi, >>> >>> >>> I can see some of the blogposts content totally distorted. >>> >>> eg: http://blog.gluster.org/2016/03/nos-conf-2016/ >>> >> that's 404 on my side, so did someone changed something ? >> > I think so. > > Its google cache page: > > http://webcache.googleusercontent.com/search?q=cache:dtHqtShjL40J:blog.gluster.org/2016/03/nos-conf-2016/+&cd=2&hl=en&ct=clnk&gl=in > > Anyway, the same issue can be observed in other posts too, just for > reference. > > >> Original blog: >>> https://joelearnsopensource.wordpress.com/2016/03/22/nosconf2016/ >>> >>> We may not be able to get the exact formatting like original one, but at >>> least it should be readable enough. >>> >>> >>> Can you please check and help on this? >>> >>> >>> Thanks, >>> >>> Saravana >>> >>> >>> >>> >>> >>> >>> >>> ___ >>> Gluster-infra mailing list >>> Gluster-infra@gluster.org >>> http://www.gluster.org/mailman/listinfo/gluster-infra >>> >> > ___ > Gluster-infra mailing list > Gluster-infra@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-infra > -- Amye Scavarda | a...@redhat.com | Gluster Community Lead ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] r.g.o down?
On Thu, Apr 21, 2016 at 2:58 PM, Michael Scherer wrote: > Le jeudi 21 avril 2016 à 14:29 +0530, Kaushal M a écrit : >> On Thu, Apr 21, 2016 at 1:14 PM, Michael Scherer wrote: >> > Le jeudi 21 avril 2016 à 12:47 +0530, Kaushal M a écrit : >> >> I restarted Gerrit that should have fixed it for now. >> >> >> >> As this has happened several times since the migration, I thought >> >> something wasn't done correctly. >> >> Turns out the gerrit VM is a really-(really)-low end VM with just 1 >> >> CPU core and 2GBs of RAM!! >> >> >> >> Michael, was this intentional or did you some how overlook this? >> > >> > I likely overlooked. I reused the same type of VM than the one for >> > >> >> IIRC, >> >> before the migration the VM was running with a dual-core CPU at least >> >> and more RAM. >> > >> > 4G of ram and 2 cpus. So I propose to go to 6G and still 2 cpu for now ? >> >> Fine with me. We always have room to grow if required. >> >> > >> >> The hypervisor has more than enough resources to run a beefier VM. I >> >> was thinking of bumping the VM to a 4 Cores and 8 GB of RAM (or more). >> >> I'll do this if there are no objections. >> > >> > This requires a reboot however, is this ok ? >> >> Doing this shouldn't take longer that ~5minutes. We could do it any time. >> It would have been so much easier if libvirt allowed hot-plugging cpu >> and ram like disks. > > Seems to be supported in openstack, and in version we use on RHEL 7. > > And virsh has a command setvcpus with a --live switch, and the same for > the ram. TIL! I've been trying to do this all the time by editing the VM xml config. I believe virt-manager does the same as well, because it fails to add cpus live as well. > > Shall I try later today ? > (worst case, it crash and we reboot) Sure. > -- > Michael Scherer > Sysadmin, Community Infrastructure and Platform, OSAS > > > ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] r.g.o down?
Le jeudi 21 avril 2016 à 14:29 +0530, Kaushal M a écrit : > On Thu, Apr 21, 2016 at 1:14 PM, Michael Scherer wrote: > > Le jeudi 21 avril 2016 à 12:47 +0530, Kaushal M a écrit : > >> I restarted Gerrit that should have fixed it for now. > >> > >> As this has happened several times since the migration, I thought > >> something wasn't done correctly. > >> Turns out the gerrit VM is a really-(really)-low end VM with just 1 > >> CPU core and 2GBs of RAM!! > >> > >> Michael, was this intentional or did you some how overlook this? > > > > I likely overlooked. I reused the same type of VM than the one for > > > >> IIRC, > >> before the migration the VM was running with a dual-core CPU at least > >> and more RAM. > > > > 4G of ram and 2 cpus. So I propose to go to 6G and still 2 cpu for now ? > > Fine with me. We always have room to grow if required. > > > > >> The hypervisor has more than enough resources to run a beefier VM. I > >> was thinking of bumping the VM to a 4 Cores and 8 GB of RAM (or more). > >> I'll do this if there are no objections. > > > > This requires a reboot however, is this ok ? > > Doing this shouldn't take longer that ~5minutes. We could do it any time. > It would have been so much easier if libvirt allowed hot-plugging cpu > and ram like disks. Seems to be supported in openstack, and in version we use on RHEL 7. And virsh has a command setvcpus with a --live switch, and the same for the ram. Shall I try later today ? (worst case, it crash and we reboot) -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] r.g.o down?
On Thu, Apr 21, 2016 at 1:14 PM, Michael Scherer wrote: > Le jeudi 21 avril 2016 à 12:47 +0530, Kaushal M a écrit : >> I restarted Gerrit that should have fixed it for now. >> >> As this has happened several times since the migration, I thought >> something wasn't done correctly. >> Turns out the gerrit VM is a really-(really)-low end VM with just 1 >> CPU core and 2GBs of RAM!! >> >> Michael, was this intentional or did you some how overlook this? > > I likely overlooked. I reused the same type of VM than the one for > >> IIRC, >> before the migration the VM was running with a dual-core CPU at least >> and more RAM. > > 4G of ram and 2 cpus. So I propose to go to 6G and still 2 cpu for now ? Fine with me. We always have room to grow if required. > >> The hypervisor has more than enough resources to run a beefier VM. I >> was thinking of bumping the VM to a 4 Cores and 8 GB of RAM (or more). >> I'll do this if there are no objections. > > This requires a reboot however, is this ok ? Doing this shouldn't take longer that ~5minutes. We could do it any time. It would have been so much easier if libvirt allowed hot-plugging cpu and ram like disks. > -- > Michael Scherer > Sysadmin, Community Infrastructure and Platform, OSAS > > > ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] r.g.o down?
Le jeudi 21 avril 2016 à 09:44 +0200, Michael Scherer a écrit : > Le jeudi 21 avril 2016 à 12:47 +0530, Kaushal M a écrit : > > I restarted Gerrit that should have fixed it for now. > > > > As this has happened several times since the migration, I thought > > something wasn't done correctly. > > Turns out the gerrit VM is a really-(really)-low end VM with just 1 > > CPU core and 2GBs of RAM!! > > > > Michael, was this intentional or did you some how overlook this? > > I likely overlooked. I reused the same type of VM than the one for the one for jenkins builder (my fault for answering mail before breakfast) -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS signature.asc Description: This is a digitally signed message part ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] r.g.o down?
Le jeudi 21 avril 2016 à 12:47 +0530, Kaushal M a écrit : > I restarted Gerrit that should have fixed it for now. > > As this has happened several times since the migration, I thought > something wasn't done correctly. > Turns out the gerrit VM is a really-(really)-low end VM with just 1 > CPU core and 2GBs of RAM!! > > Michael, was this intentional or did you some how overlook this? I likely overlooked. I reused the same type of VM than the one for > IIRC, > before the migration the VM was running with a dual-core CPU at least > and more RAM. 4G of ram and 2 cpus. So I propose to go to 6G and still 2 cpu for now ? > The hypervisor has more than enough resources to run a beefier VM. I > was thinking of bumping the VM to a 4 Cores and 8 GB of RAM (or more). > I'll do this if there are no objections. This requires a reboot however, is this ok ? -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] r.g.o down?
I restarted Gerrit that should have fixed it for now. As this has happened several times since the migration, I thought something wasn't done correctly. Turns out the gerrit VM is a really-(really)-low end VM with just 1 CPU core and 2GBs of RAM!! Michael, was this intentional or did you some how overlook this? IIRC, before the migration the VM was running with a dual-core CPU at least and more RAM. The hypervisor has more than enough resources to run a beefier VM. I was thinking of bumping the VM to a 4 Cores and 8 GB of RAM (or more). I'll do this if there are no objections. ~kaushal On Thu, Apr 21, 2016 at 12:36 PM, Krutika Dhananjay wrote: > Working now. > > -Krutika > > On Thu, Apr 21, 2016 at 12:19 PM, Krutika Dhananjay > wrote: >> >> I get this when i try to access it: 500 Internal server error >> >> -Krutika > > > > ___ > Gluster-infra mailing list > Gluster-infra@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-infra ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] r.g.o down?
Working now. -Krutika On Thu, Apr 21, 2016 at 12:19 PM, Krutika Dhananjay wrote: > I get this when i try to access it: > > *500 Internal server error* > > *-Krutika* > ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra