[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Exclude broker as hosting gears

+++ Igor Laskovy [10/09/12 23:55 +0300]:
Hi Brenton,

look like erasing broker from rubygem-stickshift-node*,
stickshift-mcollective-agent* and cartridges break something:

Hmm... I was able to reproduce this.  You can run the following to
undo that change:

yum install stickshift-mcollective-agent
service qpidd restart
service mcollective restart
service stickshift-broker restart

It's actually surprising to me that rubygem-stickshift-node has to be
installed on the broker (since it's a dependency of
stickshift-mcollective-agent).  I'm going to file a bug to remind us
to look into that to make sure the RPM dependencies are setup
correctly.  I does make sense that stickshift-mcollective-agent needs
to be installed.

Back to your original question... If you don't want gears to land on
the broker just make sure you don't have any cartridges installed. :)

Also, my day was a little busier than I expected yesterday.  I am
still planning to investigate the district question you had.


[root broker ~]# rhc domain show -l n -d
Password: ***********

Submitting form:
rhlogin: n
debug: true
Contacting https://localhost
Problem reported from server. Response code was 503.
HTTP response from server is <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<title>503 Service Temporarily Unavailable</title>
<h1>Service Temporarily Unavailable</h1>
<p>The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.</p>
<address>Apache/2.2.22 (Fedora) Server at localhost Port 443</address>

Are you have this behavior?

On Mon, Sep 10, 2012 at 5:12 PM, Igor Laskovy <igor laskovy gmail com> wrote:
Great, awaiting if so))

Igor Laskovy
Kiev, Ukraine

On Sep 10, 2012 4:16 PM, "Brenton Leanhardt" <bleanhar redhat com> wrote:

+++ Igor Laskovy [10/09/12 15:48 +0300]:

Thanks Brenton!

I used this guide for starting
http://www.krishnaraman.net/multi-node-openshift-origin-from-scratch/ .

Cool, that doc is still accurate.  We do also have
https://openshift.redhat.com/community/wiki/build-your-own but it is
by definition more involved.

Thanks for reply about removing packages.
But, if, for example, I have two districts, how I can attach/bind user
to one of them only. If this is not main purpose of district, than what

I'm actually trying to figure that out myself.  If I come up with
something today I'll be sure to blog about it.

Igor Laskovy
Kiev, Ukraine
On Sep 10, 2012 3:33 PM, "Brenton Leanhardt" <bleanhar redhat com> wrote:

+++ Igor Laskovy [08/09/12 20:32 +0300]:

Hello from sunny Kiev!

How I can set multihost OpenShift Original to not use broker as host
I suppose that I need to use district somehow, but I can't understand
how to attach user/users domain/users gears to it?

To keep gears from landing on your broker just make sure you don't
have the rubygem-stickshift-node*, stickshift-mcollective-agent* or
any cartridges installed on your broker.

Just curious, what instructions did you follow to setup Origin?  I
know some of the instructions setup a broker+node on the same machine.

* the packages are being renamed in Fedora.  See



Awaiting any advice!

P.S. Sorry for cross posting to the dev and users lists. I am new to
openshift community and not sure which list best represent subject
like that.

I think this would be more appropriate for the users list but it
doesn't really matter right now.  Most of us are on both. :)

Igor Laskovy
Kiev, Ukraine

dev mailing list
dev lists openshift redhat com


Igor Laskovy
Kiev, Ukraine

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]