date:20160617

Re: Creating from a template: get parameters from a file

2016-06-17 Thread Clayton Coleman

The -v flag needs to be fixed for sure (splitting flag values is bad).

New-app should support both -f FILE and -p (which you can specify multiple
-p, one for each param).

Do you have any templates that require new lines?

On Jun 17, 2016, at 5:55 PM, Alex Wauck  wrote:

I need to create services from a template that has a lot of parameters.  In
addition to having a lot of parameters, it has parameters with values
containing commas, which does not play well with the -v flag for oc
process.  Is there any way to make oc process get the parameter values from
a file?  I'm currently tediously copy/pasting the values into the web UI,
which is not a good solution.

-- 

Alex Wauck // DevOps Engineer
*E X O S I T E*
*www.exosite.com *
Making Machines More Human.

___
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

Re: Unable to add attributes to user via api

2016-06-17 Thread Clayton Coleman

You have fullName in the metadata object, but it should be in the base object.

On Fri, Jun 17, 2016 at 4:57 PM, Marc Boorshtein  wrote:
> When I create a user by posting to /oapi/v1/users with the following JSON:
>
> {"identites":[],"kind":"User","apiVersion":"v1","metadata":{"name":"testCreateUser","fullName":"Create
> New User"},"details":{},"code":0}
>
> the user gets created by fullName isn't set:
>
> {"kind":"User","apiVersion":"v1","metadata":{"name":"testCreateUser","selfLink":"/oapi/v1/users/testCreateUser","uid":"200ead3d-34cd-11e6-a8db-525400b18ee2","resourceVersion":"1096067","creationTimestamp":"2016-06-17T20:50:29Z"},"identities":null,"groups":null}
>
> Is this the correct behavior?  can only name be set?
>
>
> Thanks
>
> Marc
>
>
> ___
> 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

Re: Hawkular Metrics

2016-06-17 Thread Srinivas Naga Kotaru (skotaru)

Thanks Matt. That is good info 



-- 
Srinivas Kotaru

On 6/17/16, 12:48 PM, "Matt Wringe"  wrote:

>- Original Message -
>> From: "Srinivas Naga Kotaru (skotaru)" 
>> To: users@lists.openshift.redhat.com
>> Sent: Friday, June 17, 2016 2:30:38 PM
>> Subject: Hawkular Metrics
>> 
>> 
>> 
>> Trying to understand how an API can be crafted to get metrics and prepare
>> custom dashboard. My metrics service is up and running, and seeing nice CPU
>> and memory graphs against container metrics tab
>> 
>> 
>> 
>> Few questions around it
>> 
>> 
>> 
>> 1. If I don’t want to use console, can we use an API to get hawkular metrics
>> and prepare custom dashboards?
>
>If you want to use the Hawkular Metrics API directly to read metrics, there is 
>some documentation here for that: 
>https://github.com/openshift/origin-metrics/blob/master/docs/hawkular_metrics.adoc
>
>> 
>> 2. Can I feed hawkular data to any other custom systems to prepare graphs
>> automatically rather we our self create graphs? Like zabbix, cacti or any
>> other graphs generated systems?
>
>From the Hawkular Metrics API call you will get back json data. If you wish to 
>import that into another system you can do so. But we do not provide support 
>for bringing this data into a third party system.
>
>> 
>> 3. Am seeing cpu and memory, any other other metrics it will generate or
>> expose?
>
>Newer versions should have network metrics. We also collect node level metrics 
>as well (but those are not displayed in the console).
>
>In the future we should have support for pods to provide their own custom 
>metrics as well.
>
>> 
>> 4. Finally, what Is the exact API call we can use to get metrics?
>
>Please see the docs: 
>https://github.com/openshift/origin-metrics/blob/master/docs/hawkular_metrics.adoc
>
>> 
>> 
>> 
>> Am using below call and able to see lot of data, but not sure which are
>> interesting fields or right API call
>> 
>> 
>> 
>> curl -H "Authorization: Bearer  -H "Hawkular-tenant: " -X GET
>> https:// /hawkular/metrics/metrics | jq
>> 
>
>That will give you the list of all metrics for that project. From there you 
>will need to narrow it down and select which metrics you are interested in, 
>and over what time period.
>
>> 
>> 
>> 
>> 
>> 
>> --
>> 
>> 
>> Srinivas Kotaru
>> 
>> ___
>> 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

Re: Atomic Centos, can't upgrade

2016-06-17 Thread Philippe Lafoucrière

Thanks Tobias for the detailed help!
I should have thought of running again ansible, I was focused on the error.



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

Re: docker registry image for openshift 3.2?

2016-06-17 Thread Alan Jones

Restarting docker cleared it up.
I think there is something about my install of OS, perhaps it reinstalls
docker.
Thank you!

On Fri, Jun 17, 2016 at 11:19 AM, Clayton Coleman 
wrote:

> Are you trying to pull that from the DockerHub, or do you have an
> --add-registry flag on your daemon?  Because that image only exists on
> the red hat registry.
>
> On Fri, Jun 17, 2016 at 2:12 PM, Alan Jones  wrote:
> > Error syncing pod, skipping: failed to "StartContainer" for "deployment"
> > with ErrImagePull: "Error: image openshift3/ose-deployer:v3.2.0.44 not
> > found"
> >
> > ___
> > 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

Hawkular Metrics

2016-06-17 Thread Srinivas Naga Kotaru (skotaru)

Trying to understand how an API can be crafted to get metrics and prepare 
custom dashboard. My metrics service is up and running, and seeing nice CPU and 
memory graphs against container metrics tab

Few questions around it


1.   If I don’t want to use console, can we use an API to get hawkular 
metrics and prepare custom dashboards?

2.   Can I feed hawkular data to any other custom systems to prepare graphs 
automatically rather we our self create graphs? Like zabbix, cacti or any other 
graphs generated systems?

3.   Am seeing cpu and memory, any other other metrics it will generate or 
expose?

4.   Finally, what Is the exact API call we can use to get metrics?

Am using below call and able to see lot of data, but not sure which are 
interesting fields or right API call

curl -H "Authorization: Bearer  -H "Hawkular-tenant: " -X GET 
https:// /hawkular/metrics/metrics | jq



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

Re: docker registry image for openshift 3.2?

2016-06-17 Thread Clayton Coleman

Are you trying to pull that from the DockerHub, or do you have an
--add-registry flag on your daemon?  Because that image only exists on
the red hat registry.

On Fri, Jun 17, 2016 at 2:12 PM, Alan Jones  wrote:
> Error syncing pod, skipping: failed to "StartContainer" for "deployment"
> with ErrImagePull: "Error: image openshift3/ose-deployer:v3.2.0.44 not
> found"
>
> ___
> 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

docker registry image for openshift 3.2?

2016-06-17 Thread Alan Jones

Error syncing pod, skipping: failed to "StartContainer" for "deployment"
with ErrImagePull: "Error: image openshift3/ose-deployer:v3.2.0.44 not
found"
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Atomic Centos, can't upgrade

2016-06-17 Thread Tobias Florek

Hi,

that's a known problem with known fix, but maybe some publicity around
it might be good.


> We have tried to update our atomic host centos 7, with the
> tree 3c3786d1dd (from the tree e39c28570a), but deployments are all
> failing after the updates on the nodes:
> 
> Error syncing pod, skipping: failed to "SetupNetwork" for "some_deploy"
> with SetupNetworkError: "Failed to setup network for pod
> \"some_deploy(d080f8d4-3498-11e6-8512-005056b1755a)\" using network
> plugins \"redhat/openshift-ovs-subnet\": exit status 1; Skipping pod"


It's a problem that is fixed by either
 * reprovisioning via openshift-ansible, or
 * upgrading to openshift v1.3 (alpha or latest).

The problem is, that due to the docker-current/docker-latest diversion,
/usr/bin/docker is a shell script that needs /etc/sysconfig/docker, but
that is not mounted by the old origin-node systemd unit.

See
 https://github.com/openshift/openshift-ansible/pull/2037
for the fix for origin pre 1.3. Origin v1.3 will run docker chrooted to
the host fs, so the problem does not manifest itself.

Chdeers,
 Tobias Flore

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

Atomic Centos, can't upgrade

2016-06-17 Thread Philippe Lafoucrière

Hi,

We have tried to update our atomic host centos 7, with the tree 3c3786d1dd
(from the tree e39c28570a), but deployments are all failing after the
updates on the nodes:

Error syncing pod, skipping: failed to "SetupNetwork" for "some_deploy"
with SetupNetworkError: "Failed to setup network for pod
\"some_deploy(d080f8d4-3498-11e6-8512-005056b1755a)\" using network plugins
\"redhat/openshift-ovs-subnet\": exit status 1; Skipping pod"
Where can I fill a report for that? Openshift or Atomic host bugtracker
(whereever it is)?

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

All my ipfailover pods are in "Entering MASTER STATE", it's not fair ?

2016-06-17 Thread Stéphane Klein

Hi,

I've:

* one cluster with 2 nodes
* ipfailover replicas=2

I execute:

* oc logs ipfailover-rbx-1-bh3kn
https://gist.github.com/harobed/2ab152ed98f95285d549cbc7af3a#file-oc-logs-ipfailover-rbx-1-bh3kn
* oc logs ipfailover-rbx-1-mmp36
https://gist.github.com/harobed/2ab152ed98f95285d549cbc7af3a#file-oc-logs-ipfailover-rbx-1-mmp36

and I see that all ipfailover pod are in "Entering MASTER STATE".

It's not fair ?

Best regards,
Stéphane
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Use own Dockerhub registry instead of openshift

2016-06-17 Thread Scott Dodson

Sorry, the value needs to be in single quotes otherwise bash tries to
evaluate it.

On Fri, Jun 17, 2016 at 9:47 AM, Den Cowboy  wrote:
> $ oadm router router --replicas=1 \
>
> --credentials='/etc/origin/master/openshift-router.kubeconfig' \
>
> --service-account=router \
>
> --images=docker.io/my-registry/origin-${component}:${latest}
>
>
> dc:
> image: 'docker.io/my-registry/origin-:'
> imagePullPolicy: IfNotPresent
>
> It will work if I use my real image name origin-haproxy and real tag but
> that doesn't seem like a real solution.
>
>
>> Date: Fri, 17 Jun 2016 09:42:34 -0400
>
>> Subject: Re: Use own Dockerhub registry instead of openshift
>> From: sdod...@redhat.com
>> To: dencow...@hotmail.com
>> CC: ccole...@redhat.com; users@lists.openshift.redhat.com
>>
>> You need to add
>> `--images=docker.io/my-registry/origin-${component}:${latest}` to the
>> oadm invocation.
>>
>> On Fri, Jun 17, 2016 at 9:38 AM, Den Cowboy  wrote:
>> > Hi Scott,
>> >
>> > I did the following now:
>> > In master-config.yaml:
>> > my-registry/origin-${component}:${latest}
>> >
>> > In node-config.yaml:
>> > my-registry/origin-${component}:${latest}
>> >
>> > sudo service origin-master restart
>> > sudo service origin-node restart
>> >
>> > Created a router:
>> >
>> > oadm router router --replicas=1 \
>> >
>> > --credentials='/etc/origin/master/openshift-router.kubeconfig' \
>> >
>> > --service-account=router
>> >
>> >
>> > This is in my deploymentconfig:
>> >
>> > image: openshift/origin-haproxy-router:v1.2.0-1-g7386b49
>> > imagePullPolicy: IfNotPresent
>> >
>> >
>> >> Date: Fri, 17 Jun 2016 09:23:56 -0400
>> >
>> >> Subject: Re: Use own Dockerhub registry instead of openshift
>> >> From: sdod...@redhat.com
>> >> To: dencow...@hotmail.com
>> >> CC: ccole...@redhat.com; users@lists.openshift.redhat.com
>> >>
>> >> So in your deployment config it should just be the fully qualified
>> >> image repository, so 'docker.io/registry-name/haproxy-router:v1.2.0'
>> >> not the template. If you didn't re-run the installer you'll also
>> >> want to set imageConfig format in /etc/origin/node/node-config.yaml
>> >> too, and of course after setting these values restart the node
>> >> service.
>> >>
>> >> On Fri, Jun 17, 2016 at 9:14 AM, Den Cowboy 
>> >> wrote:
>> >> > Sorry for the spam but still stuck on this issue.
>> >> > Changing the ansible/hosts file changed the master-config.
>> >> > But deploymentconfig isn't changed.
>> >> >
>> >> > The masterconfig contains
>> >> > docker.io/my-registry/origin-${component}:${latest}
>> >> >
>> >> > So the dc config needs to be:
>> >> > my-registry/origin-${component}:${latest} but it's
>> >> > opensfhit/origin-${component}:
>> >> >
>> >> > So it seems this will only work if you have an own registry which is
>> >> > called
>> >> > something like:
>> >> > https://x:5000/openshift/origin-${component}:${latest}
>> >> >
>> >> > But we are using a registry of docker.io where you can only create
>> >> > something
>> >> > like docker.io/registry-name/origin-... (registry-name can't be
>> >> > openshift
>> >> > because that's the name of the registry of red hat).
>> >> >
>> >> > 
>> >> > From: dencow...@hotmail.com
>> >> > To: sdod...@redhat.com; ccole...@redhat.com
>> >> > Subject: RE: Use own Dockerhub registry instead of openshift
>> >> > Date: Thu, 16 Jun 2016 12:47:05 +
>> >> > CC: users@lists.openshift.redhat.com
>> >> >
>> >> >
>> >> > I edited my playbook.
>> >> > this in my master-config:
>> >> >
>> >> > docker.io/my-registry/origin-${component}:${latest}
>> >> >
>> >> >
>> >> > But this is in the dc config (when I try to start a router).
>> >> > image: openshift/origin-haproxy-router:v1.2.0-1-g7386b49
>> >> >
>> >> > and it fails.
>> >> >
>> >> > 
>> >> > From: dencow...@hotmail.com
>> >> > To: sdod...@redhat.com; ccole...@redhat.com
>> >> > Subject: RE: Use own Dockerhub registry instead of openshift
>> >> > Date: Wed, 15 Jun 2016 17:33:58 +
>> >> > CC: users@lists.openshift.redhat.com
>> >> >
>> >> > https://github.com/openshift/origin/issues/9315 same issue here for
>> >> > the
>> >> > image tag
>> >> >
>> >> > 
>> >> > From: dencow...@hotmail.com
>> >> > To: sdod...@redhat.com; ccole...@redhat.com
>> >> > Subject: RE: Use own Dockerhub registry instead of openshift
>> >> > Date: Wed, 15 Jun 2016 17:00:37 +
>> >> > CC: users@lists.openshift.redhat.com
>> >> >
>> >> > Hi, thanks Scott.
>> >> > I've edited the playbook and reran it:
>> >> >
>> >> > I've a registry with the origin-pod image and the ha-proxy-router
>> >> > image
>> >> > in
>> >> > my registry.
>> >> > I tried to deploy my router
>> >> >
>> >> > Error syncing pod, skipping: failed to "StartContainer" for "POD"
>> >> > with
>> >> > ErrImagePull: "image pull failed for
>> >> > docker.io/my-repo/origin-pod:v1.2.0-1-g7386b49, this may

RE: Use own Dockerhub registry instead of openshift

2016-06-17 Thread Den Cowboy





















$ oadm router router --replicas=1 \
--credentials='/etc/origin/master/openshift-router.kubeconfig' \
--service-account=router \
--images=docker.io/my-registry/origin-${component}:${latest}






dc:
image: 'docker.io/my-registry/origin-:'
imagePullPolicy: IfNotPresent

It will work if I use my real image name origin-haproxy and real tag but that 
doesn't seem like a real solution.


> Date: Fri, 17 Jun 2016 09:42:34 -0400
> Subject: Re: Use own Dockerhub registry instead of openshift
> From: sdod...@redhat.com
> To: dencow...@hotmail.com
> CC: ccole...@redhat.com; users@lists.openshift.redhat.com
> 
> You need to add
> `--images=docker.io/my-registry/origin-${component}:${latest}` to the
> oadm invocation.
> 
> On Fri, Jun 17, 2016 at 9:38 AM, Den Cowboy  wrote:
> > Hi Scott,
> >
> > I did the following now:
> > In master-config.yaml:
> > my-registry/origin-${component}:${latest}
> >
> > In node-config.yaml:
> > my-registry/origin-${component}:${latest}
> >
> > sudo service origin-master restart
> > sudo service origin-node restart
> >
> > Created a router:
> >
> > oadm router router --replicas=1 \
> >
> > --credentials='/etc/origin/master/openshift-router.kubeconfig' \
> >
> > --service-account=router
> >
> >
> > This is in my deploymentconfig:
> >
> > image: openshift/origin-haproxy-router:v1.2.0-1-g7386b49
> > imagePullPolicy: IfNotPresent
> >
> >
> >> Date: Fri, 17 Jun 2016 09:23:56 -0400
> >
> >> Subject: Re: Use own Dockerhub registry instead of openshift
> >> From: sdod...@redhat.com
> >> To: dencow...@hotmail.com
> >> CC: ccole...@redhat.com; users@lists.openshift.redhat.com
> >>
> >> So in your deployment config it should just be the fully qualified
> >> image repository, so 'docker.io/registry-name/haproxy-router:v1.2.0'
> >> not the template. If you didn't re-run the installer you'll also
> >> want to set imageConfig format in /etc/origin/node/node-config.yaml
> >> too, and of course after setting these values restart the node
> >> service.
> >>
> >> On Fri, Jun 17, 2016 at 9:14 AM, Den Cowboy  wrote:
> >> > Sorry for the spam but still stuck on this issue.
> >> > Changing the ansible/hosts file changed the master-config.
> >> > But deploymentconfig isn't changed.
> >> >
> >> > The masterconfig contains
> >> > docker.io/my-registry/origin-${component}:${latest}
> >> >
> >> > So the dc config needs to be:
> >> > my-registry/origin-${component}:${latest} but it's
> >> > opensfhit/origin-${component}:
> >> >
> >> > So it seems this will only work if you have an own registry which is
> >> > called
> >> > something like:
> >> > https://x:5000/openshift/origin-${component}:${latest}
> >> >
> >> > But we are using a registry of docker.io where you can only create
> >> > something
> >> > like docker.io/registry-name/origin-... (registry-name can't be
> >> > openshift
> >> > because that's the name of the registry of red hat).
> >> >
> >> > 
> >> > From: dencow...@hotmail.com
> >> > To: sdod...@redhat.com; ccole...@redhat.com
> >> > Subject: RE: Use own Dockerhub registry instead of openshift
> >> > Date: Thu, 16 Jun 2016 12:47:05 +
> >> > CC: users@lists.openshift.redhat.com
> >> >
> >> >
> >> > I edited my playbook.
> >> > this in my master-config:
> >> >
> >> > docker.io/my-registry/origin-${component}:${latest}
> >> >
> >> >
> >> > But this is in the dc config (when I try to start a router).
> >> > image: openshift/origin-haproxy-router:v1.2.0-1-g7386b49
> >> >
> >> > and it fails.
> >> >
> >> > 
> >> > From: dencow...@hotmail.com
> >> > To: sdod...@redhat.com; ccole...@redhat.com
> >> > Subject: RE: Use own Dockerhub registry instead of openshift
> >> > Date: Wed, 15 Jun 2016 17:33:58 +
> >> > CC: users@lists.openshift.redhat.com
> >> >
> >> > https://github.com/openshift/origin/issues/9315 same issue here for the
> >> > image tag
> >> >
> >> > 
> >> > From: dencow...@hotmail.com
> >> > To: sdod...@redhat.com; ccole...@redhat.com
> >> > Subject: RE: Use own Dockerhub registry instead of openshift
> >> > Date: Wed, 15 Jun 2016 17:00:37 +
> >> > CC: users@lists.openshift.redhat.com
> >> >
> >> > Hi, thanks Scott.
> >> > I've edited the playbook and reran it:
> >> >
> >> > I've a registry with the origin-pod image and the ha-proxy-router image
> >> > in
> >> > my registry.
> >> > I tried to deploy my router
> >> >
> >> > Error syncing pod, skipping: failed to "StartContainer" for "POD" with
> >> > ErrImagePull: "image pull failed for
> >> > docker.io/my-repo/origin-pod:v1.2.0-1-g7386b49, this may be because
> >> > there
> >> > are no credentials on this request. details: (Tag v1.2.0-1-g7386b49 not
> >> > found in repository docker.io/my-repo/origin-pod)"
> >> >
> >> > 2 issues:
> >> > no credentials on this request (it's a public registry so probably no
> >> > issue?)
> >> > tag

Re: Use own Dockerhub registry instead of openshift

2016-06-17 Thread Scott Dodson

You need to add
`--images=docker.io/my-registry/origin-${component}:${latest}` to the
oadm invocation.

On Fri, Jun 17, 2016 at 9:38 AM, Den Cowboy  wrote:
> Hi Scott,
>
> I did the following now:
> In master-config.yaml:
> my-registry/origin-${component}:${latest}
>
> In node-config.yaml:
> my-registry/origin-${component}:${latest}
>
> sudo service origin-master restart
> sudo service origin-node restart
>
> Created a router:
>
> oadm router router --replicas=1 \
>
> --credentials='/etc/origin/master/openshift-router.kubeconfig' \
>
> --service-account=router
>
>
> This is in my deploymentconfig:
>
> image: openshift/origin-haproxy-router:v1.2.0-1-g7386b49
> imagePullPolicy: IfNotPresent
>
>
>> Date: Fri, 17 Jun 2016 09:23:56 -0400
>
>> Subject: Re: Use own Dockerhub registry instead of openshift
>> From: sdod...@redhat.com
>> To: dencow...@hotmail.com
>> CC: ccole...@redhat.com; users@lists.openshift.redhat.com
>>
>> So in your deployment config it should just be the fully qualified
>> image repository, so 'docker.io/registry-name/haproxy-router:v1.2.0'
>> not the template. If you didn't re-run the installer you'll also
>> want to set imageConfig format in /etc/origin/node/node-config.yaml
>> too, and of course after setting these values restart the node
>> service.
>>
>> On Fri, Jun 17, 2016 at 9:14 AM, Den Cowboy  wrote:
>> > Sorry for the spam but still stuck on this issue.
>> > Changing the ansible/hosts file changed the master-config.
>> > But deploymentconfig isn't changed.
>> >
>> > The masterconfig contains
>> > docker.io/my-registry/origin-${component}:${latest}
>> >
>> > So the dc config needs to be:
>> > my-registry/origin-${component}:${latest} but it's
>> > opensfhit/origin-${component}:
>> >
>> > So it seems this will only work if you have an own registry which is
>> > called
>> > something like:
>> > https://x:5000/openshift/origin-${component}:${latest}
>> >
>> > But we are using a registry of docker.io where you can only create
>> > something
>> > like docker.io/registry-name/origin-... (registry-name can't be
>> > openshift
>> > because that's the name of the registry of red hat).
>> >
>> > 
>> > From: dencow...@hotmail.com
>> > To: sdod...@redhat.com; ccole...@redhat.com
>> > Subject: RE: Use own Dockerhub registry instead of openshift
>> > Date: Thu, 16 Jun 2016 12:47:05 +
>> > CC: users@lists.openshift.redhat.com
>> >
>> >
>> > I edited my playbook.
>> > this in my master-config:
>> >
>> > docker.io/my-registry/origin-${component}:${latest}
>> >
>> >
>> > But this is in the dc config (when I try to start a router).
>> > image: openshift/origin-haproxy-router:v1.2.0-1-g7386b49
>> >
>> > and it fails.
>> >
>> > 
>> > From: dencow...@hotmail.com
>> > To: sdod...@redhat.com; ccole...@redhat.com
>> > Subject: RE: Use own Dockerhub registry instead of openshift
>> > Date: Wed, 15 Jun 2016 17:33:58 +
>> > CC: users@lists.openshift.redhat.com
>> >
>> > https://github.com/openshift/origin/issues/9315 same issue here for the
>> > image tag
>> >
>> > 
>> > From: dencow...@hotmail.com
>> > To: sdod...@redhat.com; ccole...@redhat.com
>> > Subject: RE: Use own Dockerhub registry instead of openshift
>> > Date: Wed, 15 Jun 2016 17:00:37 +
>> > CC: users@lists.openshift.redhat.com
>> >
>> > Hi, thanks Scott.
>> > I've edited the playbook and reran it:
>> >
>> > I've a registry with the origin-pod image and the ha-proxy-router image
>> > in
>> > my registry.
>> > I tried to deploy my router
>> >
>> > Error syncing pod, skipping: failed to "StartContainer" for "POD" with
>> > ErrImagePull: "image pull failed for
>> > docker.io/my-repo/origin-pod:v1.2.0-1-g7386b49, this may be because
>> > there
>> > are no credentials on this request. details: (Tag v1.2.0-1-g7386b49 not
>> > found in repository docker.io/my-repo/origin-pod)"
>> >
>> > 2 issues:
>> > no credentials on this request (it's a public registry so probably no
>> > issue?)
>> > tag v1.2.0-1-g7386b49 not found: I have an image with tag v1.2.0 and tag
>> > latest (on the same image). I don't know why it tries to pull an image
>> > with
>> > this tag because this tag doesn't even exist in the OpenShift repo on
>> > Dockerhub:
>> >
>> > ...
>> > v1.3.0-alpha.0
>> > 511 KB
>> > 2 months ago
>> > v1.2.0-rc2
>> > 511 KB
>> > 2 months ago
>> > v1.2.0-rc1
>> > 511 KB
>> > 2 months ago
>> > v1.1.6
>> > 511 KB
>> > 2 months ago
>> > ...
>> >
>> >
>> >
>> >> Date: Wed, 15 Jun 2016 11:55:24 -0400
>> >> Subject: Re: Use own Dockerhub registry instead of openshift
>> >> From: sdod...@redhat.com
>> >> To: dencow...@hotmail.com
>> >> CC: ccole...@redhat.com; users@lists.openshift.redhat.com
>> >>
>> >> Den,
>> >>
>> >> Here's the ansible variable documented in the example inventories. I'd
>> >> suggest fully qualifying it ie:
>> >> 'hub.docker.io/dencowboy/test-${component}:${version}'
>>

RE: Use own Dockerhub registry instead of openshift

2016-06-17 Thread Den Cowboy

Hi Scott,

I did the following now:
In master-config.yaml:
my-registry/origin-${component}:${latest}

In node-config.yaml:
my-registry/origin-${component}:${latest}

sudo service origin-master restart
sudo service origin-node restart

Created a router:




















oadm router router --replicas=1 \
--credentials='/etc/origin/master/openshift-router.kubeconfig' \
--service-account=router






This is in my deploymentconfig: 

image: openshift/origin-haproxy-router:v1.2.0-1-g7386b49
imagePullPolicy: IfNotPresent


> Date: Fri, 17 Jun 2016 09:23:56 -0400
> Subject: Re: Use own Dockerhub registry instead of openshift
> From: sdod...@redhat.com
> To: dencow...@hotmail.com
> CC: ccole...@redhat.com; users@lists.openshift.redhat.com
> 
> So in your deployment config it should just be the fully qualified
> image repository, so 'docker.io/registry-name/haproxy-router:v1.2.0'
> not the template.   If you didn't re-run the installer you'll also
> want to set imageConfig format in /etc/origin/node/node-config.yaml
> too, and of course after setting these values restart the node
> service.
> 
> On Fri, Jun 17, 2016 at 9:14 AM, Den Cowboy  wrote:
> > Sorry for the spam but still stuck on this issue.
> > Changing the ansible/hosts file changed the master-config.
> > But deploymentconfig isn't changed.
> >
> > The masterconfig contains
> > docker.io/my-registry/origin-${component}:${latest}
> >
> > So the dc config needs to be:
> > my-registry/origin-${component}:${latest} but it's
> > opensfhit/origin-${component}:
> >
> > So it seems this will only work if you have an own registry which is called
> > something like:
> > https://x:5000/openshift/origin-${component}:${latest}
> >
> > But we are using a registry of docker.io where you can only create something
> > like docker.io/registry-name/origin-... (registry-name can't be openshift
> > because that's the name of the registry of red hat).
> >
> > 
> > From: dencow...@hotmail.com
> > To: sdod...@redhat.com; ccole...@redhat.com
> > Subject: RE: Use own Dockerhub registry instead of openshift
> > Date: Thu, 16 Jun 2016 12:47:05 +
> > CC: users@lists.openshift.redhat.com
> >
> >
> > I edited my playbook.
> > this in my master-config:
> >
> > docker.io/my-registry/origin-${component}:${latest}
> >
> >
> > But this is in the dc config (when I try to start a router).
> >   image: openshift/origin-haproxy-router:v1.2.0-1-g7386b49
> >
> > and it fails.
> >
> > 
> > From: dencow...@hotmail.com
> > To: sdod...@redhat.com; ccole...@redhat.com
> > Subject: RE: Use own Dockerhub registry instead of openshift
> > Date: Wed, 15 Jun 2016 17:33:58 +
> > CC: users@lists.openshift.redhat.com
> >
> > https://github.com/openshift/origin/issues/9315 same issue here for the
> > image tag
> >
> > 
> > From: dencow...@hotmail.com
> > To: sdod...@redhat.com; ccole...@redhat.com
> > Subject: RE: Use own Dockerhub registry instead of openshift
> > Date: Wed, 15 Jun 2016 17:00:37 +
> > CC: users@lists.openshift.redhat.com
> >
> > Hi, thanks Scott.
> > I've edited the playbook and reran it:
> >
> > I've a registry with the origin-pod image and the ha-proxy-router image in
> > my registry.
> > I tried to deploy my router
> >
> > Error syncing pod, skipping: failed to "StartContainer" for "POD" with
> > ErrImagePull: "image pull failed for
> > docker.io/my-repo/origin-pod:v1.2.0-1-g7386b49, this may be because there
> > are no credentials on this request. details: (Tag v1.2.0-1-g7386b49 not
> > found in repository docker.io/my-repo/origin-pod)"
> >
> > 2 issues:
> > no credentials on this request (it's a public registry so probably no
> > issue?)
> > tag v1.2.0-1-g7386b49 not found: I have an image with tag v1.2.0 and tag
> > latest (on the same image). I don't know why it tries to pull an image with
> > this tag because this tag doesn't even exist in the OpenShift repo on
> > Dockerhub:
> >
> > ...
> > v1.3.0-alpha.0
> > 511 KB
> > 2 months ago
> > v1.2.0-rc2
> > 511 KB
> > 2 months ago
> > v1.2.0-rc1
> > 511 KB
> > 2 months ago
> > v1.1.6
> > 511 KB
> > 2 months ago
> > ...
> >
> >
> >
> >> Date: Wed, 15 Jun 2016 11:55:24 -0400
> >> Subject: Re: Use own Dockerhub registry instead of openshift
> >> From: sdod...@redhat.com
> >> To: dencow...@hotmail.com
> >> CC: ccole...@redhat.com; users@lists.openshift.redhat.com
> >>
> >> Den,
> >>
> >> Here's the ansible variable documented in the example inventories. I'd
> >> suggest fully qualifying it ie:
> >> 'hub.docker.io/dencowboy/test-${component}:${version}'
> >>
> >> https://github.com/openshift/openshift-ansible/blob/master/inventory/byo/hosts.origin.example#L79-L82
> >>
> >> On Wed, Jun 15, 2016 at 11:32 AM, Den Cowboy 
> >> wrote:
> >> > Thanks for the fast reply. Where can we find it in the ansible repo?
> >> > https://github.com/openshift/openshift-ansible
> >> >
> >>

Re: Use own Dockerhub registry instead of openshift

2016-06-17 Thread Scott Dodson

So in your deployment config it should just be the fully qualified
image repository, so 'docker.io/registry-name/haproxy-router:v1.2.0'
not the template.   If you didn't re-run the installer you'll also
want to set imageConfig format in /etc/origin/node/node-config.yaml
too, and of course after setting these values restart the node
service.

On Fri, Jun 17, 2016 at 9:14 AM, Den Cowboy  wrote:
> Sorry for the spam but still stuck on this issue.
> Changing the ansible/hosts file changed the master-config.
> But deploymentconfig isn't changed.
>
> The masterconfig contains
> docker.io/my-registry/origin-${component}:${latest}
>
> So the dc config needs to be:
> my-registry/origin-${component}:${latest} but it's
> opensfhit/origin-${component}:
>
> So it seems this will only work if you have an own registry which is called
> something like:
> https://x:5000/openshift/origin-${component}:${latest}
>
> But we are using a registry of docker.io where you can only create something
> like docker.io/registry-name/origin-... (registry-name can't be openshift
> because that's the name of the registry of red hat).
>
> 
> From: dencow...@hotmail.com
> To: sdod...@redhat.com; ccole...@redhat.com
> Subject: RE: Use own Dockerhub registry instead of openshift
> Date: Thu, 16 Jun 2016 12:47:05 +
> CC: users@lists.openshift.redhat.com
>
>
> I edited my playbook.
> this in my master-config:
>
> docker.io/my-registry/origin-${component}:${latest}
>
>
> But this is in the dc config (when I try to start a router).
>   image: openshift/origin-haproxy-router:v1.2.0-1-g7386b49
>
> and it fails.
>
> 
> From: dencow...@hotmail.com
> To: sdod...@redhat.com; ccole...@redhat.com
> Subject: RE: Use own Dockerhub registry instead of openshift
> Date: Wed, 15 Jun 2016 17:33:58 +
> CC: users@lists.openshift.redhat.com
>
> https://github.com/openshift/origin/issues/9315 same issue here for the
> image tag
>
> 
> From: dencow...@hotmail.com
> To: sdod...@redhat.com; ccole...@redhat.com
> Subject: RE: Use own Dockerhub registry instead of openshift
> Date: Wed, 15 Jun 2016 17:00:37 +
> CC: users@lists.openshift.redhat.com
>
> Hi, thanks Scott.
> I've edited the playbook and reran it:
>
> I've a registry with the origin-pod image and the ha-proxy-router image in
> my registry.
> I tried to deploy my router
>
> Error syncing pod, skipping: failed to "StartContainer" for "POD" with
> ErrImagePull: "image pull failed for
> docker.io/my-repo/origin-pod:v1.2.0-1-g7386b49, this may be because there
> are no credentials on this request. details: (Tag v1.2.0-1-g7386b49 not
> found in repository docker.io/my-repo/origin-pod)"
>
> 2 issues:
> no credentials on this request (it's a public registry so probably no
> issue?)
> tag v1.2.0-1-g7386b49 not found: I have an image with tag v1.2.0 and tag
> latest (on the same image). I don't know why it tries to pull an image with
> this tag because this tag doesn't even exist in the OpenShift repo on
> Dockerhub:
>
> ...
> v1.3.0-alpha.0
> 511 KB
> 2 months ago
> v1.2.0-rc2
> 511 KB
> 2 months ago
> v1.2.0-rc1
> 511 KB
> 2 months ago
> v1.1.6
> 511 KB
> 2 months ago
> ...
>
>
>
>> Date: Wed, 15 Jun 2016 11:55:24 -0400
>> Subject: Re: Use own Dockerhub registry instead of openshift
>> From: sdod...@redhat.com
>> To: dencow...@hotmail.com
>> CC: ccole...@redhat.com; users@lists.openshift.redhat.com
>>
>> Den,
>>
>> Here's the ansible variable documented in the example inventories. I'd
>> suggest fully qualifying it ie:
>> 'hub.docker.io/dencowboy/test-${component}:${version}'
>>
>> https://github.com/openshift/openshift-ansible/blob/master/inventory/byo/hosts.origin.example#L79-L82
>>
>> On Wed, Jun 15, 2016 at 11:32 AM, Den Cowboy 
>> wrote:
>> > Thanks for the fast reply. Where can we find it in the ansible repo?
>> > https://github.com/openshift/openshift-ansible
>> >
>> > Do we also need to change our images of or do we have to create a "test"
>> > project.
>> > For example if we want to push all the images with version 1.1.6 to our
>> > repo
>> > on dockerhub wich is called test:
>> > normally we do this as: test/origin-...:v1.1.6 but than it isn't
>> > inserted in
>> > the "openshift" project probably?
>> > Or do we have to call it: test/openshift/origin-... (if that's possible
>> > on
>> > docker hub)
>> >
>> >> Date: Wed, 15 Jun 2016 09:54:00 -0400
>> >> Subject: Re: Use own Dockerhub registry instead of openshift
>> >> From: ccole...@redhat.com
>> >> To: dencow...@hotmail.com
>> >> CC: users@lists.openshift.redhat.com
>> >>
>> >> You can specify a different image pattern in Ansible (or in the CLI
>> >> tools oadm registry / oadm router) to tell OpenShift where to pull the
>> >> images from. You'll need to match the Origin pattern though
>> >> (registry/namespace/openshift-{same_suffixes_as_origin}) and have a
>> >> consistent tag for all of them.
>>

RE: Use own Dockerhub registry instead of openshift

2016-06-17 Thread Den Cowboy

Sorry for the spam but still stuck on this issue.
Changing the ansible/hosts file changed the master-config. 
But deploymentconfig isn't changed.

The masterconfig contains
docker.io/my-registry/origin-${component}:${latest}

So the dc config needs to be:
my-registry/origin-${component}:${latest} but it's 
opensfhit/origin-${component}:

So it seems this will only work if you have an own registry which is called 
something like:
https://x:5000/openshift/origin-${component}:${latest}

But we are using a registry of docker.io where you can only create something 
like docker.io/registry-name/origin-... (registry-name can't be openshift 
because that's the name of the registry of red hat).

From: dencow...@hotmail.com
To: sdod...@redhat.com; ccole...@redhat.com
Subject: RE: Use own Dockerhub registry instead of openshift
Date: Thu, 16 Jun 2016 12:47:05 +
CC: users@lists.openshift.redhat.com




I edited my playbook.
this in my master-config:

docker.io/my-registry/origin-${component}:${latest}


But this is in the dc config (when I try to start a router).
  image: openshift/origin-haproxy-router:v1.2.0-1-g7386b49

and it fails.

From: dencow...@hotmail.com
To: sdod...@redhat.com; ccole...@redhat.com
Subject: RE: Use own Dockerhub registry instead of openshift
Date: Wed, 15 Jun 2016 17:33:58 +
CC: users@lists.openshift.redhat.com




https://github.com/openshift/origin/issues/9315 same issue here for the image 
tag

From: dencow...@hotmail.com
To: sdod...@redhat.com; ccole...@redhat.com
Subject: RE: Use own Dockerhub registry instead of openshift
Date: Wed, 15 Jun 2016 17:00:37 +
CC: users@lists.openshift.redhat.com




Hi, thanks Scott.
I've edited the playbook and reran it:

I've a registry with the origin-pod image and the ha-proxy-router image in my 
registry.
I tried to deploy my router

Error syncing pod, skipping: failed to "StartContainer" for "POD" with 
ErrImagePull: "image pull failed for 
docker.io/my-repo/origin-pod:v1.2.0-1-g7386b49, this may be because 
there are no credentials on this request.  details: (Tag 
v1.2.0-1-g7386b49 not found in repository docker.io/my-repo/origin-pod)"



2 issues: 
no credentials on this request (it's a public registry so probably no issue?)
tag 
v1.2.0-1-g7386b49 not found: I have an image with tag v1.2.0 and tag latest (on 
the same image). I don't know why it tries to pull an image with this tag 
because this tag doesn't even exist in the OpenShift repo on Dockerhub:

...
v1.3.0-alpha.0511 KB2 months agov1.2.0-rc2511 KB2 months agov1.2.0-rc1511 KB2 
months agov1.1.6511 KB2 months ago
...



> Date: Wed, 15 Jun 2016 11:55:24 -0400
> Subject: Re: Use own Dockerhub registry instead of openshift
> From: sdod...@redhat.com
> To: dencow...@hotmail.com
> CC: ccole...@redhat.com; users@lists.openshift.redhat.com
> 
> Den,
> 
> Here's the ansible variable documented in the example inventories. I'd
> suggest fully qualifying it ie:
> 'hub.docker.io/dencowboy/test-${component}:${version}'
> https://github.com/openshift/openshift-ansible/blob/master/inventory/byo/hosts.origin.example#L79-L82
> 
> On Wed, Jun 15, 2016 at 11:32 AM, Den Cowboy  wrote:
> > Thanks for the fast reply. Where can we find it in the ansible repo?
> > https://github.com/openshift/openshift-ansible
> >
> > Do we also need to change our images of or do we have to create a "test"
> > project.
> > For example if we want to push all the images with version 1.1.6 to our repo
> > on dockerhub wich is called test:
> > normally we do this as: test/origin-...:v1.1.6 but than it isn't inserted in
> > the "openshift" project probably?
> > Or do we have to call it: test/openshift/origin-... (if that's possible on
> > docker hub)
> >
> >> Date: Wed, 15 Jun 2016 09:54:00 -0400
> >> Subject: Re: Use own Dockerhub registry instead of openshift
> >> From: ccole...@redhat.com
> >> To: dencow...@hotmail.com
> >> CC: users@lists.openshift.redhat.com
> >>
> >> You can specify a different image pattern in Ansible (or in the CLI
> >> tools oadm registry / oadm router) to tell OpenShift where to pull the
> >> images from. You'll need to match the Origin pattern though
> >> (registry/namespace/openshift-{same_suffixes_as_origin}) and have a
> >> consistent tag for all of them.
> >>
> >> On Wed, Jun 15, 2016 at 9:16 AM, Den Cowboy  wrote:
> >> > We are setting up a POC for OpenShift Origin.
> >> > We try to use all our own images (so an own docker hub account and reuse
> >> > the
> >> > same images of OpenShift).
> >> > Because we had a big issue some time ago in our POC project because
> >> > OpenShift deleted some images which were older than 1.2.0.
> >> >
> >> > Is it possible to configure something inside openshift so we can pull
> >> > our
> >> > images (for metrics, for registry, for router etc.) from our own
> >> > registry
> >> > and not from the openshift/origin docker hub registry?
> >> >
> >> > Thanks
> >> >
> >> >

Re: openshift and flocker

2016-06-17 Thread aleks


Hi.

Am 17-06-2016 00:01, schrieb Clayton Coleman:

No reason.  Their dependency tree looks small, please open an issue on
GitHub and we'll try to get it added.


Thanks.

Issue opened

https://github.com/openshift/origin/issues/9398

BR Aleks

On Sun, Jun 12, 2016 at 6:59 AM, aleks  
wrote:

Hi.

I haven't found flocker in the list of supported PersistentVolume 
plug-ins


https://docs.openshift.org/latest/architecture/additional_concepts/storage.html#types-of-persistent-volumes

When I take a look into the kubernetes doc is flocker listed


http://kubernetes.io/docs/user-guide/volumes/#flocker

Do you plan to add flocker in the future?

BR Aleks

___
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

Re: Creating from a template: get parameters from a file

Re: Unable to add attributes to user via api

Re: Hawkular Metrics

Re: Atomic Centos, can't upgrade

Re: docker registry image for openshift 3.2?

Hawkular Metrics

Re: docker registry image for openshift 3.2?

docker registry image for openshift 3.2?

Re: Atomic Centos, can't upgrade

Atomic Centos, can't upgrade

All my ipfailover pods are in "Entering MASTER STATE", it's not fair ?

Re: Use own Dockerhub registry instead of openshift

RE: Use own Dockerhub registry instead of openshift

Re: Use own Dockerhub registry instead of openshift

RE: Use own Dockerhub registry instead of openshift

Re: Use own Dockerhub registry instead of openshift

RE: Use own Dockerhub registry instead of openshift

Re: openshift and flocker

18 matches

Site Navigation

Mail list logo

Footer information