OSE ceph examples#4772
OSE ceph examples#4772jeffvance wants to merge 9 commits intoopenshift:masterfrom jeffvance:ose_ceph_doc
Conversation
There was a problem hiding this comment.
this should use the openshift provided mysql image instead, which doesn't require any security changes to work....
https://github.com/openshift/mysql
|
my main concern is it doesn't use our openshift mysql image.
but for a detailed review of the actual steps/instructions, this seems better suited to the storage team.. @markturansky @eparis ? |
|
Two things:
(1a -- Ben, if your team could make a WordPress image that didn't require root/port 80, the WordPress example becomes simpler by removing the security caveats from the readme).
I prefer Jan's approach. I think this ceph example should re-use our WordPress stuff. This PR could add a 3rd volume to the example (NFS was first, Jan added Cinder, this PR can add Ceph). |
|
Also, I know nothing of Ceph, so I leave detailed steps/instructions review to @rootfs who wrote the Ceph plugin and upstream readme. |
|
I will redo the example to fit under the wordpress umbrella. Using Jan's wordpress readme, I'll add a ceph bullet under the "Storage Provisioning" header. |
|
@markturansky shockingly enough, this actually worked: Then connect to the wordpress service via your web browser. you'll need to supply the mysql user/password/dbname/service ip as part of the setup. (the user/pass/dbname generated by the template as env variables) |
|
that's very cool :) On Wed, Sep 23, 2015 at 3:50 PM, Ben Parees notifications@github.com
|
|
@mnagy fyi |
|
@jeffvance Needs to be squashed after the comments are addressed. |
There was a problem hiding this comment.
This is no longer needed with the version of kubernetes that we bundle.
There was a problem hiding this comment.
you can use "mysql" as <mysql-container-ID>, as you set the container name with docker run --name mysql
|
To be honest, I do not like the guide. As pointed out by others,it does not use OpenShift mysql and the structure is confusing.
And.. will be have three different examples (volume directly in a pod, PV+PVC and application template) for all volume plugins? IMo it would make more sense to teach admins just how to create a PV (= one example for each plugin) + one common example how to use them with a PVC or application template? Because the PVC and the template will be always the same, regardless which volume plugin is used. I already started with that in https://github.com/openshift/origin/tree/master/examples/wordpress |
|
Origin Action Required: Pull request cannot be automatically merged, please rebase your branch from latest HEAD and push again |
|
Closing due to age and inactivity. |
I've added several examples using ceph to persist a mysql database.