[Rdo-list] Concerning Rabbits
by John Eckersberg
(In the spirit of "Concerning Hobbits")
Ryan O'Hara and I have been investigating RabbitMQ as it pertains to RDO
recently. There has been a lot of discussion on several disparate
threads, so I wanted to try and capture it on the list for the benefit
of everyone.
Ryan has been working on getting RabbitMQ running in a multi-node HA
configuration. I won't steal his thunder, and he can speak to it better
than I can, so I'll defer to him on the details.
As for me, I've been working on el7 support and bug squashing along the
way.
The first bug[1] causes the daemon to load incredibly slow, or outright
fail by timing out. This is due to the SELinux policy disallowing
name_bind on ports lower than 32768. RabbitMQ tries to name_bind to a
port starting at 10000, and increments if it fails. So if you have
SELinux in enforcing mode, you'll get 22768 AVC denials in the log
before it finally starts.
The second bug[2] causes the daemon to intermittently fail to start due
to a race condition in the creation of the erlang cookie file. This
happens only the first time the service starts. Really this is an
Erlang bug, but there's a workaround for the RabbitMQ case.
I've submitted patches for both issues. Until those get merged in, I've
rebuilt[3] RabbitMQ for F20 which includes the fixes.
Beyond bugs, I've also built out RabbitMQ and all the build/runtime
dependencies for el7. I have a yum repo[4] on my fedorapeople page
containing all the bits. This is all the stuff that is presently
missing from EPEL7. In time, I would hope the maintainers build all
this stuff, but for now it'll work for testing. You will also need the
EPEL 7 Beta repository[5] enabled.
As a side note, I built everything using mock with a local override repo
on my workstation. I've not used copr before but it seems relevant to
this sort of thing, so if it's any benefit I'll look to rebuilt the el7
stack there for easier consumption.
Hopefully this helps get the discussion into one place, and provide a
baseline for further investigation by everyone interested in RabbitMQ.
John.
---
[1] Is really two bugzillas, but the same bug:
[1a] https://bugzilla.redhat.com/show_bug.cgi?id=998682
[1b] https://bugzilla.redhat.com/show_bug.cgi?id=1032595
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1059913
[3] http://jeckersb.fedorapeople.org/rabbitmq-server-3.1.5-3.fc20.noarch.rpm
[4] http://jeckersb.fedorapeople.org/rabbitmq-el7/
[5] http://dl.fedoraproject.org/pub/epel/beta/7/x86_64/
10 years, 4 months
[Rdo-list] Open-Source Software Products Users Contacts Release Q1
by Katy Thomas
Hi,
Would you be interested in acquiring our open-source software products users
list with the updated count and verified contacts? The list has been
recently verified in Fourth week of January is ready to use and this
information database can be helpful for your email marketing campaign,
tele-marketing campaign and other marketing campaign initiatives for
unlimited usages.
21st February 2014 Televerified contacts.
Ø Ubuntu users
Ø CentOS users
Ø Debian users
Ø Solaris users
Ø openSUSE users
We have a global reach and can customize your list to offer you a more
targeted approach. Our lists are Tele-verified and guarantee 100% of data
accuracy.
We do provide data cleansing and appending services to resolve this issue.
If interested, let me know your target criteria so that I can get back to
you with relevant information. If interested, let me know your target
criteria so that I can get back to you with relevant information.
Would such detail give you an edge over your competition?
Could we talk more?
Regards,
Katy Thomas,
Demand Generation Manager
eDatalist LLC
List acquisition I Tracked Email campaign I Email/Data Appending I Search
Engine Optimization I Custom Built List I Tele Marketing I Multi Channel
Marketing I Web-site Designing I
If you do not wish to receive future emails from us, please reply as 'leave
out'
11 years
[Rdo-list] VXLAN support
by Gonçalo Borges
Hi Guys...
I would like to send a couple of questions regarding VXLAN support in RDO.
Let me summary the context:
1) The documentation regarding VXLAN is available here:
http://openstack.redhat.com/Using_VXLAN_Tenant_Networks
2) The previous link says that VXLAN will be supported in RDO after
solving the following bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1021778
3) The previous bug seems to be already solved in
openstack-packstack-2013.2.1-0.23.dev979.el6ost.
Now the question:
I have installed openstack-packstack-2013.2.1-0.29.dev956.el6.noarch
(higher than previous fixed version) so VXLAN should be natively
supported. However I do not find any documentation on how to change the
answers file. There are some recipes where you start by deploying a GRE
configuration and that change manually some items to support VXLAN.
However, if VXLAN is already supported in RDO then it should be
configured directly from the answers file. Is there some documentation
on that topic?
TIA
Cheers
Goncalo
11 years
Re: [Rdo-list] [foreman-dev] [OFI] RFC: Dynflow Orchestration. Initial Ideas / User Stories
by Martyn Taylor
Including RDO List
On 25/02/14 15:13, Martyn Taylor wrote:
> All,
>
> We've started pulling together a plan for adding orchestration in the
> OpenStack Foreman Installer.
>
> We have a bunch of User Stories and some implementation notes here:
> http://pad-katello.rhcloud.com/p/ofi-orchestration that we would like
> feedback on.
>
> Please have a read over and let us know if there are any obvious
> issues / gaps. We'll be working from the etherpad, please add
> comments, questions there. Please add <name>: <comment> so we can
> keep track of discussion.
>
> Thank alot
> Martyn
>
> --
> You received this message because you are subscribed to the Google
> Groups "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to foreman-dev+unsubscribe(a)googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
11 years
