Hello,
seems like that manual intervention (log on and evacuate node) is the price we
have to pay if we don't want our master to wreak havoc in our cluster when it
has connectivity problems.
Maybe this whole mechanism could be built in a more defensive way. What is
missing for us is an option
One of the biggest problems we have with our current infrastructure/process
(and which we are trying to address with Openshift) is multiple teams
fighting for shared environments (test, uat, stage, prod). This led to a
terrible "deployment train" anti-pattern with 4 big releases a year to
promote a
Hi,
I think that it could be interesting that we involve within this discussion
what Middleware team has developed as we propose within the pipelines
scripts such possibility to move a "project" between different namespaces
(dev -> test -> prod) including also approving or rejecting (
https://gith
On Wed, Oct 12, 2016 at 10:04 PM, Lionel Orellana
wrote:
> May I ask in relation to this, how do you define an "environment" at the
> moment? My first instinct was to create a project for one app and configure
> different service/deployments referencing different image tags (e.g. dev,
> test, etc
May I ask in relation to this, how do you define an "environment" at the
moment? My first instinct was to create a project for one app and configure
different service/deployments referencing different image tags (e.g. dev,
test, etc). Given that all services within a project are automatically
injec
Never mind me. It's all in the customer portal.
On 12 October 2016 at 21:57, Lionel Orellana wrote:
> Hi
>
> Is there any doco on Red Hat's JBoss images? With Wildfly I can go to
> github to see how the image is built. Looking at the Dockerfile is very
> useful too to understand what's going on.
Hey Ricardo,
I believe that your problem can be solved by using a message queue such as
RabbitMQ with persistent storage.
So instead of sending your messages directly to the Mainframe you should
deliver it your MQ. Afterwards you will need to open a transaction with the
MQ for reading the message a
We manage most of our systems with Salt, and this includes our OpenShift
cluster. We create nodes with salt-cloud and lay the groundwork (e.g.
admin user accounts, install various useful packages) using Salt, and then
we do the actual OpenShift installation using openshift-ansible (which Rich
Megg
Yeah, if you make this change you'll be responsible for triggering
evacuation of down nodes. You can do that via "oadm manage-node NODE_NAME
--evacuate"
On Mon, Oct 10, 2016 at 8:06 AM, v wrote:
> Hello Clayton,
>
> thank you for replying!
> I'm not sure whether changing the node failure detect
On 10/12/2016 03:15 AM, Stéphane Klein wrote:
Hi,
I use OpenShift with success but I search a good practice to:
* keep all object config history (deployment config history, image
stream creation/delete, project creation/delete…)
* I use OpenShift template system, sometime I need to update this
>From a security perspective we recommend rotating frequently, but it's up
to your judgement. If someone compromised your master cert you would want
to rotate it quickly, so just keep that in mind.
On Oct 12, 2016, at 8:37 AM, Mario Rosic wrote:
Hello,
thank you, the playbook seems to work wel
Hello,
thank you, the playbook seems to work well.
However, I don't want to keep track of cert expiry dates and since those certs
are self-signed I'm going to modify the playbook to issue the certs for 30
years (which should exceed the life of the cluster).
To me it seems like there is no rea
Hi
Is there any doco on Red Hat's JBoss images? With Wildfly I can go to
github to see how the image is built. Looking at the Dockerfile is very
useful too to understand what's going on. Red Hat's registry ( registry
.access.redhat.com) doesn't give any useful info. Is there a correlation
between
Hi,
I use OpenShift with success but I search a good practice to:
* keep all object config history (deployment config history, image
stream creation/delete, project creation/delete…)
* I use OpenShift template system, sometime I need to update this
template but I need to update manually all proje
14 matches
Mail list logo
