Re: Order of Deploy/Template Configuration

2016-05-25 Thread Clayton Coleman 
The mechanism to do that would be a deployment pre-hook or a pod
precondition (via init container, coming in the next release.

On May 25, 2016, at 6:55 PM, Skarbek, John  wrote:

Good Morning,

Is there some concept of parenting, or timing, or simply ordering of items
when building a template configuration? Specifically around first time
deploys.

I’ve got a multi service application, where the head honcho service
requires prior services to be up and running. Thus far, I’ve modified the
start script for the images to simply do a check and wait then repeat for a
long time. I worry as I continue this, it’ll end up hurting us in the long
run.

I’m wondering if I can tell the template that app B depends on app A, such
that it’ll wait to deploy app B until after the deploy and readiness checks
are complete on app A.



-- 
John Skarbek

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Order of Deploy/Template Configuration

2016-05-25 Thread Skarbek, John 
Good Morning,

Is there some concept of parenting, or timing, or simply ordering of items when 
building a template configuration? Specifically around first time deploys.

I’ve got a multi service application, where the head honcho service requires 
prior services to be up and running. Thus far, I’ve modified the start script 
for the images to simply do a check and wait then repeat for a long time. I 
worry as I continue this, it’ll end up hurting us in the long run.

I’m wondering if I can tell the template that app B depends on app A, such that 
it’ll wait to deploy app B until after the deploy and readiness checks are 
complete on app A.


--
John Skarbek
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: "could not create user" error

2016-05-25 Thread Jordan Liggitt 
The users you are trying to log in as are likely already mapped to
identities from another identity provider. You can see whether that's the
case by doing `oc describe user your-username`. If so, the "claim"
mappingMethod will refuse to map the htpasswd identity to the user.

If you want the htpasswd identities to automatically map to the
correspondingly named user even if that user already has an associated
identity, set mappingMethod to "add"



On May 25, 2016, at 11:39 AM, Candide Kemmler 
wrote:

I'm trying to configure htpasswd-based authentication but getting:

"Could not create user." error

my configuration is as follows:

oauthConfig:
 assetPublicURL: https://paas.intrinsic.world:8443/console/
 grantConfig:
   method: auto
 identityProviders:
 - challenge: true
   login: true
   mappingMethod: claim
   name: my_htpasswd_provider
   provider:
 apiVersion: v1
 kind: HTPasswdPasswordIdentityProvider
 file: /etc/origin/master/users.htpasswd
 masterCA: ca.crt
 masterPublicURL: https://paas.intrinsic.world:8443
 masterURL: https://paas.intrinsic.world:8443
 sessionConfig:
   sessionMaxAgeSeconds: 3600
   sessionName: ssn
   sessionSecretsFile: /etc/origin/master/session-secrets.yaml
 tokenConfig:
   accessTokenMaxAgeSeconds: 86400
   authorizeTokenMaxAgeSeconds: 500

___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

"could not create user" error

2016-05-25 Thread Candide Kemmler 
I'm trying to configure htpasswd-based authentication but getting:

"Could not create user." error

my configuration is as follows:

oauthConfig:
 assetPublicURL: https://paas.intrinsic.world:8443/console/ 

 grantConfig:
   method: auto
 identityProviders:
 - challenge: true
   login: true
   mappingMethod: claim
   name: my_htpasswd_provider
   provider:
 apiVersion: v1
 kind: HTPasswdPasswordIdentityProvider
 file: /etc/origin/master/users.htpasswd
 masterCA: ca.crt
 masterPublicURL: https://paas.intrinsic.world:8443 

 masterURL: https://paas.intrinsic.world:8443 

 sessionConfig:
   sessionMaxAgeSeconds: 3600
   sessionName: ssn
   sessionSecretsFile: /etc/origin/master/session-secrets.yaml
 tokenConfig:
   accessTokenMaxAgeSeconds: 86400
   authorizeTokenMaxAgeSeconds: 500___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Limiting scaling of a pod

2016-05-25 Thread Philippe Lafoucrière 
On Sun, May 22, 2016 at 7:05 PM, Clayton Coleman 
wrote:

> What are you trying to defend against?  The more concrete examples you
> can provide (where the app would be broken if there is >1 copy) the
> more we can do to ensure the use case is solved.
>

We have a legacy Resque Scheduler pod running. If this pod is running more
than once at a time, jobs are schedule (queued) more than once, and it
leads to other issues.
This pod doesn't have any PV, so we can't use a ReadWriteOnce PV to ensure
that.
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users