similar to: Fwd: Centos 6 AMI does not support c4-8xlarge

I have done that, but the point of the request is that we would like to have an official upstream AMI that we can use as the basis for our work. I'm guessing that the reason for the blacked out instance type is that early 6.x kernels didn't have the patches necessary to support 36 vCPU's present in the c4.8xlarge instance. John On Wed, Sep 7, 2016 at 10:46 AM, Alvin Starr <alvin

Hi John On 07/09/16 15:50, John Peacock wrote: > I have done that, but the point of the request is that we would like to > have an official upstream AMI that we can use as the basis for our > work. I'm guessing that the reason for the blacked out instance type is > that early 6.x kernels didn't have the patches necessary to support 36 > vCPU's present in the

I have yet to try this but I believe you can take a snapshot of the image after it is first installed. Then attach the snapshot to another VM and copy the data to a new volume. That new volume could then be used to create another AMI that you can deploy as you see fit. On 09/07/2016 10:38 AM, John Peacock wrote: > One of the things suboptimal with Marketplace images is that the >

I asked back in September: https://lists.centos.org/pipermail/centos-virt/2016-September/005219.html and again in November: https://lists.centos.org/pipermail/centos-virt/2016-November/005257.html about getting c4.8xlarge enabled for the official image in AWS Marketplace: https://aws.amazon.com/marketplace/pp/B00NQAYLWO?ref=cns_srchrow Now that the 6.9 release is coming, it would be

On 05/04/17 14:56, John Peacock wrote: > > We want to be able to usethe 10G networking that c4.8xlarge instances > provide and we want to base all of our images directly on the official > Centos6 release AMI. > Can you try ami-500d8546 i us-east-1 and let me know if that works for the c4.8large ? I've asked, a few times, for the CentOS Linux images in AMP to be enabled for

That makes for an interesting problem. I cannot open port 24007 to allow RPC access. On 02/07/2018 11:29 PM, Kotresh Hiremath Ravishankar wrote: > Hi Alvin, > > Yes, geo-replication sync happens via SSH. Ther server port 24007 is > of glusterd. > glusterd will be listening in this port and all volume management > communication > happens via RPC. > > Thanks, >

Ccing glusterd team for information On Thu, Feb 8, 2018 at 10:02 AM, Alvin Starr <alvin at netvel.net> wrote: > That makes for an interesting problem. > > I cannot open port 24007 to allow RPC access. > > On 02/07/2018 11:29 PM, Kotresh Hiremath Ravishankar wrote: > > Hi Alvin, > > Yes, geo-replication sync happens via SSH. Ther server port 24007 is of >

I am running gluster 3.8.9 and trying to setup a geo-replicated volume over ssh, It looks like the volume create command is trying to directly access the server over port 24007. The docs imply that all communications are over ssh. What am I missing? -- Alvin Starr || land: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 alvin at netvel.net

> If you run top what are you seeing on the %Cpu(s) line? %20 On Mon, Feb 8, 2016 at 9:30 PM, Alvin Starr <alvin at netvel.net> wrote: > Slow disks will show up as higher I/Owait times. > If your seeing 99% cpu usage then your likely looking at some other problem. > > If you run top what are you seeing on the %Cpu(s) line? > > > On 02/08/2016 02:20 PM, Gokan Atmaca

Hi Alvin, Yes, geo-replication sync happens via SSH. Ther server port 24007 is of glusterd. glusterd will be listening in this port and all volume management communication happens via RPC. Thanks, Kotresh HR On Wed, Feb 7, 2018 at 8:29 PM, Alvin Starr <alvin at netvel.net> wrote: > I am running gluster 3.8.9 and trying to setup a geo-replicated volume > over ssh, > > It looks

I was sort of hoping that is was something simple like setting the "do_the_right_thing" flag. The libvirtd kicks out 2014-10-31 11:58:57.111+0000: 8741: error : virRegisterNetworkDriver:549 : driver in virRegisterNetworkDriver must not be NULL 2014-10-31 11:59:29.379+0000: 8840: error : virRegisterNetworkDriver:549 : driver in virRegisterNetworkDriver must not be NULL 2014-10-31

This is not abit issue just a minor annoyance. I use Foreman to provision my systems and to keep control I remove all the default *.repo files andkeep away from installing more *.repo files so I can control the content via the foreman(katello) provided redhat.repo. I would argue that the *-release-*.rpm should not contain any setup code but just the stuff in /etc/yum.repos.d. -- Alvin

FIrstly Centos is primarily a RHEL clone. This means that the primary design decisions are to be as RHEL like as possible. After that there are additions and upgrades. Secondly Fedora does not actively support Xen. As a long time Xen and RH/Fedora user I have spent lots of time building/rebuilding broken/missing packages in Fedora. Quite frankly Xen under Fedora is somewhat broken. Libvirt

On 09/08/2015 10:58 AM, Konrad Rzeszutek Wilk wrote: > On Tue, Sep 08, 2015 at 10:50:57AM -0400, Alvin Starr wrote: >> FIrstly Centos is primarily a RHEL clone. >> This means that the primary design decisions are to be as RHEL like as >> possible. >> After that there are additions and upgrades. >> >> Secondly Fedora does not actively support Xen. >

If I reboot a single vm through libvirt/libxl the system reboots normally. If I have several vm's reboot at the same time then The systems go into a paused state and do not reboot. I then have to kill them via xl and restart them. -- Alvin Starr || voice: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 alvin@netvel.net ||

> I'm guessing you're using standard 7,200rpm platter drives? You'll need > to share more information about your environment in order for us to > provide useful feedback. Usually though, the answer is 'caching' and/or > 'faster disks'. Yes , 7.2k rpm disks. 2T mirror (soft). In fact, I had such a preference for slightly more capacity. Unfortunately very

I actually move the default *.repo files and replace them with "". The thing is that Katello turns all the downloaded yum content into a single redhat.repo file and I don't have to install any more *-release-* rpms any more. I would argue that I should not need to install any *-release-* rpms at all to get all the required software. On 03/22/2017 09:34 AM, -=X.L.O.R.D=- wrote:

In general if no MTU is set on interface creation the default value is 1500. On OVS the bridge MTU is automatically set to the smallest port MTU. So you just have to set the MTU of each port of the bridge. Take a look at: https://bugzilla.redhat.com/show_bug.cgi?id=1160897 It is a bit of a pain to read but seems to confirm the statement about the OVS MTU value being set by the MTU of the

Here is info. about the Raid controllers. Doesn't seem to be the culprit. Slow host: Name PERC H710 Mini (Embedded) Firmware Version 21.3.4-0001 Cache Memory Size 512 MB Fast Host: Name PERC H310 Mini (Embedded) Firmware Version 20.12.1-0002 Cache Memory Size 0 MB Slow host: Name PERC H310 Mini (Embedded) Firmware Version 20.13.1-0002 Cache Memory Size 0 MB Slow host: Name PERC H310 Mini

Initial testing shows that AMI to work with c4.8xlarge. We have very few resources in us-east-1, so I'm creating a snapshot then copying that to us-west-2 for further testing. Thanks John On Tue, Apr 11, 2017 at 9:25 PM, Karanbir Singh <mail-lists at karan.org> wrote: > On 05/04/17 14:56, John Peacock wrote: > > > > We want to be able to usethe 10G networking that