Tuesday 15 February 2011

bash - Inter-Gear Communication for Openshift? -



bash - Inter-Gear Communication for Openshift? -

i'm trying create app such gear 2 according model can accessed gear 3,4...n when using --scaling option.

the thought beingness construction head of chain of relays. i'm trying find relevant info next gears have same behavior. this:

i've found no documentation describes how reach gear 2 (the primary dnas) url (internal/external ip:port) or otherwise, i'm little lost how allow app scale properly.

i should mention far i've used bash scripting, i'm not worried starting programme in other languages, long follows construction in openshift i'm not worried.

the end result create scalable instance of shoutcast on openshift.

to clear:

i'm developing cartridge, not using diy, understand of openshift in guide of course of study i'm limited because i'm new.

i'm stuck trying figure out how have cartridge handle having additional gears utilize first gear relay. not confused how openshift routes requests externally gears , load balances them. i'm not lost how utilize port-forwarding connect app, goal design cartridge wouldn't requirement @ all, utilize external routes.

the problem described above additional gears need configuration, need available source (what improve first gear?). in fact solution issue might somehow set cartridge bypass haproxy external route goes first gear.

github interested, pass around, it'll remain public. works standalone, scaling (what i'd fix) causes issues. i've been working on long myself, have @ :)

there's great kb article explains how routing works on openshift gears here https://help.openshift.com/hc/en-us/articles/203263674-what-external-ports-are-available-on-openshift-.

on scalable application, haproxy handles traffic routing gears. way access gears through ports mentioned in article above. rhc provide port-forwading alternative allow access things mysql straight local machine.

please note: don't allow arbitrary binding of ports on externally accessible ip address.

it possible bind internal ip port range: 15000 - 35530. other ports reserved specific processes avoid conflicts. since we're binding internal ip, need utilize port forwarding access it: https://openshift.redhat.com/community/blogs/getting-started-with-port-forwarding-on-openshift

bash openshift scaling

No comments:

Post a Comment