RE: ceph pv

[James Wilkins]

Out of interest, assuming your using ceph RBD’s – do you hit an issue where by 
the locks don’t correctly ‘move’ when a container migrates?  Historically we’ve 
had to clean up manually with rbd lock list / remove the lock to permit the pod 
to move properly.

Admittedly, we haven’t tested this since 1.2



From: users-boun...@lists.openshift.redhat.com 
[mailto:users-boun...@lists.openshift.redhat.com] On Behalf Of Diego Castro
Sent: 10 January 2017 15:59
To: Philippe Lafoucrière 
Cc: users@lists.openshift.redhat.com
Subject: Re: ceph pv

Hello.
You can use pv without worrying about secrets if you create a keyring file on 
each node at /etc/ceph/ceph.client.openshift.keyring and point the pv object to 
it:

apiVersion: v1
kind: PersistentVolume
metadata:
  name: mypv
  labels:
size: 1024
spec:
  capacity:
storage: 1024
  accessModes:
- "ReadWriteOnce"
  rbd:
monitors:
  - "osm-0:6789"
  - "osm-1:6789"
  - "osm-2:6789"
pool: rbd
image: mypv
user: openshift
keyring: /etc/ceph/ceph.client.openshift.keyring
fsType: ext4
readOnly: false
  persistentVolumeReclaimPolicy: "Retain"

For more information to create a ceph user: 
http://docs.ceph.com/docs/giant/rados/operations/user-management/#managing-users



---
Diego Castro / The CloudFather
GetupCloud.com - Eliminamos a Gravidade

2017-01-09 17:42 GMT-03:00 Philippe Lafoucrière 
>:

On Mon, Jan 9, 2017 at 3:42 AM, James Eckersall 
> wrote:
Our use case would be utilisation of openshift clusters with untrusted clients 
in distinct projects, so we’re trying to ensure they can’t access each/others 
storage.

We are in the same situation, and we generally let our clients access their 
projects without permissions for secrets :)


___
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

Question regarding upgrade of containerised deployment

[James Wilkins]

Hello,



I've noticed on the enterprise documentation page (ref: 
https://docs.openshift.com/enterprise/latest/install_config/upgrading/index.html
 ) that upgrading of containerized versions are supported for 3.1 => 3.2



If I'm using origin - which is currently on 1.3 (alpha1) - is there a method of 
upgrading to alpha2.  For example, do I just follow the manual upgrade steps ( 
https://docs.openshift.org/latest/install_config/upgrading/manual_upgrades.html 
) but instead changing the version numbers in the systemd scripts / 
node-/master config as appropriate?



Any input appreciated.





Cheers,



James






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