Re: almost there

[Luke Meyer]

On Mon, Jan 11, 2016 at 1:20 PM, Clayton Coleman 
wrote:

>
> > - I realized that last time I didn't execute the required
> pre-installation
> > steps (which include setting up docker for instance) but this didn't
> seem to
> > pose any problems. Should I scratch everything and start over? One
> worrying
> > aspect is this thing about docker storage, which I don't really get...
>
> Docker storage is a performance thing (the default is incredibly
> slow).  I don't know if you have to scratch it and start over - you
> can selectively apply those steps to each host as you go in most
> cases.
>
>
You don't have to reinstall anything. Just stop docker, follow the
instructions for setting up storage (which includes nuking the ephemeral
contents of /var/lib/docker), and start docker again.
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: almost there

[Clayton Coleman]

On Mon, Jan 11, 2016 at 1:12 PM, Candide Kemmler
 wrote:
>
> Hi,
>
> For the record, I want to field-test using OpenShift Origin together with
> fabric8 for the deployment of a prototype application for a client. I am
> almost fully set up.
>
> I have a few remaining head-scratchers for which I would really appreciate
> some help.
>
> - I couldn't find a way to create a one-server-install with the ansible
> provisioning scripts (which are great); did I miss something?

I don't believe this is an option today.  We typically recommend the
quick install in that path.

>
> both questions below refer to the prerequisites page.
>
> - In the current configuration (one master + 1 node), it looks like all the
> workload will go the node, leaving the master relatively lightweight. Does
> it mean that in a master/node setup, on can reserve less RAM for the master
> then the required 8Gb? In other words, the 8Gb that are mentioned in the
> requirements, do they stand for the minimum total required memory for a
> cluster or is it a -per node requirement?

Masters running 1 node should not require more than 1GB.

>
> - I realized that last time I didn't execute the required pre-installation
> steps (which include setting up docker for instance) but this didn't seem to
> pose any problems. Should I scratch everything and start over? One worrying
> aspect is this thing about docker storage, which I don't really get...

Docker storage is a performance thing (the default is incredibly
slow).  I don't know if you have to scratch it and start over - you
can selectively apply those steps to each host as you go in most
cases.

>
> Thank you for the help so far and looking forward to get some real work done
> soon :-)
>
> Cheers,
>
> Candide
>
> ___
> 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

almost there

[Candide Kemmler]

Hi,

For the record, I want to field-test using OpenShift Origin together with 
fabric8 for the deployment of a prototype application for a client. I am almost 
fully set up.

I have a few remaining head-scratchers for which I would really appreciate some 
help.

- I couldn't find a way to create a one-server-install with the ansible 
provisioning scripts (which are great); did I miss something?

both questions below refer to the prerequisites page 
.

- In the current configuration (one master + 1 node), it looks like all the 
workload will go the node, leaving the master relatively lightweight. Does it 
mean that in a master/node setup, on can reserve less RAM for the master then 
the required 8Gb? In other words, the 8Gb that are mentioned in the 
requirements, do they stand for the minimum total required memory for a cluster 
or is it a -per node requirement?

- I realized that last time I didn't execute the required pre-installation 
steps (which include setting up docker for instance) but this didn't seem to 
pose any problems. Should I scratch everything and start over? One worrying 
aspect is this thing about docker storage, which I don't really get...

Thank you for the help so far and looking forward to get some real work done 
soon :-)

Cheers,

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

Creating a backup of an integrated docker registry

[v]

Hello,

I am using the integrated docker registry and I would like to know whether it 
is possible to create a backup of the registry images. The images of the 
registry are provided via an NFS share, could I just archive the directory and 
restore it in case something goes wrong?

Regards,
v

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

"oadm prune images" throwing error messages

[v]

Hello,

I am getting the following error messages from "oadm prune images"

xxx@xxx ~ # oadm prune images | wc -l
I0111 16:50:18.798414 1039313 imagepruner.go:427] Unable to find image 
"sha256:b2cc0734cef757a1bc1e077ee6544fcf6d0cba4e6f9b0f2724095885ddd0d13d" in 
the graph
I0111 16:50:18.799113 1039313 imagepruner.go:427] Unable to find image 
"sha256:39075341e2189cc940ff7d9b88a032fe8c20e76d6e4ab809b9588830624e5ab2" in 
the graph
I0111 16:50:18.802609 1039313 imagepruner.go:427] Unable to find image 
"sha256:9d81fccf31f87d43badee4d54ec229427cab1e1cefb211d075af7f0302c51de1" in 
the graph
I0111 16:50:18.802661 1039313 imagepruner.go:427] Unable to find image 
"sha256:b2cc0734cef757a1bc1e077ee6544fcf6d0cba4e6f9b0f2724095885ddd0d13d" in 
the graph
I0111 16:50:18.808991 1039313 imagepruner.go:427] Unable to find image 
"sha256:39075341e2189cc940ff7d9b88a032fe8c20e76d6e4ab809b9588830624e5ab2" in 
the graph
I0111 16:50:18.810712 1039313 imagepruner.go:427] Unable to find image 
"sha256:b2cc0734cef757a1bc1e077ee6544fcf6d0cba4e6f9b0f2724095885ddd0d13d" in 
the graph
I0111 16:50:18.811361 1039313 imagepruner.go:427] Unable to find image 
"sha256:39075341e2189cc940ff7d9b88a032fe8c20e76d6e4ab809b9588830624e5ab2" in 
the graph
Dry run enabled - no modifications will be made. Add --confirm to remove images
326

What is it trying to tell me? Could this cause problems with my registry?
Using OS 1.0.6

Regards,
v

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

Re: Job frozen

[Maciej Szulik]

On 01/08/2016 10:17 PM, Philippe Lafoucrière wrote:

On Fri, Jan 8, 2016 at 4:12 PM, David Eads  wrote:


Before you delete again, can you create a gist of job yaml so we can see
what's exploded?



There's ~5000 lines like

- lastProbeTime: 2016-01-08T18:48:51Z
 lastTransitionTime: 2016-01-08T18:48:51Z
 status: "True"
 type: Complete



I'll have a look at status update, maybe we have a bug there.
Anyway thanks pointing us to that!

Maciej



Try `oc delete job/thejob --cascade=false --loglevel=6`.  That should avoid

any reaping waits and provide some debug info if it still doesn't work.
Once that happens, you will be left with cleaning up the rest of what the
job created by hand.



You saved our day :)
The job is gone now.
Thanks David



___
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