#153: design, deploy and document Fedora OpenShift Playground (FOSP) --------------------+--------------------- Reporter: goern | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting --------------------+--------------------- This ticket is to coordinate the activities to design, deploy and document the Fedora OpenShift Playground (FOSP).
Technical work is conducted by puiterwijk and misc, help is offered by scollier and goern
jzb to create a wiki page describing the SLA of FOSP
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+--------------------- Reporter: goern | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+---------------------
Comment (by scollier):
kickoff email from misc on this:
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/...
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+--------------------- Reporter: goern | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+---------------------
Comment (by goern):
see also https://fedoraproject.org/wiki/Cloud/OpenShift_Origin_Testbed
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+--------------------- Reporter: goern | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+---------------------
Comment (by misc):
Also: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
We can discuss this on the cloud-wg list, or on the infra list, I took the infra because I kinda expect this would be more suitable, but since this discussion is about the requirement an the outcome, maybe a ticket would have been better.
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+----------------------- Reporter: goern | Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+----------------------- Changes (by jzb):
* owner: => jberkus * status: new => assigned
Comment:
Per discussion in today's meeting. Josh Berkus (jberkus) has agreed take point on this as single point of contact.
Assigning ticket to him. We should revisit before Flock, but probably not right after Summit.
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+----------------------- Reporter: goern | Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+-----------------------
Comment (by jberkus):
This is currently in a holding pattern around hosting.
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+----------------------- Reporter: goern | Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+-----------------------
Comment (by jberkus):
Still waiting on availability of CNCF hosting.
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+----------------------- Reporter: goern | Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+-----------------------
Comment (by scollier):
Misc and I are meeting next week to flush out the architecture a bit more and maybe even kick off an install to kick the tires on.
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+----------------------- Reporter: goern | Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+-----------------------
Comment (by jberkus):
When? I'd like to join.
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+----------------------- Reporter: goern | Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+-----------------------
Comment (by scollier):
Replying to [comment:8 jberkus]:
When? I'd like to join.
Next Friday. I added you.
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+----------------------- Reporter: goern | Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+-----------------------
Comment (by misc):
So, after the meeting, we did finished with:
1 repo (https://github.com/fedora-cloud/fosp-playbooks)
2 action items: - see for the DNS, ie get a domain name, and a wildcard to point to the server we allocated - discuss the authentication we want. So far, we wanted to use openid connect, see if that's doable with ipsilon as deployed by Fedora
The TODO list is to create a playbook that deploy the bastion host, ie deploy ansible, openshift ansible and run the deployment based on the host file from the git repo linked earlier.
We did select 3 masters, 2 applications nodes and 2 infras nodes for now in the Fedora cloud.
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+----------------------- Reporter: goern | Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+-----------------------
Comment (by misc):
Periodic update time. The dns related issue have been fixed (with dnsmasq and hosts), and now, we bumped into https://github.com/openshift /openshift-ansible/issues/2294
I am a bit unsure on the way to bypass it, between "patching openshift- ansible", and "carrying a fixed version of seboolean".
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+----------------------- Reporter: goern | Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+-----------------------
Comment (by jdetiber):
Why fork, I have no issues carrying the patched seboolean module in openshift-ansible until we can require a version of ansible that has the fix.
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+----------------------- Reporter: goern | Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+-----------------------
Comment (by jberkus):
Next work session is Sept. 23
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+----------------------- Reporter: goern | Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+-----------------------
Comment (by scollier):
moved works session to Oct 3rd.
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+----------------------- Reporter: goern | Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+-----------------------
Comment (by scollier):
moved working session out a couple of weeks due to the seboolean issue. That gives time for the patch to get rolled in and for misc to test those packages.
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+----------------------- Reporter: goern | Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+-----------------------
Comment (by misc):
So good new. The deploy did finished fine. I stumbled on 2 issues, 1 with me doing wrong cut and paste (resulting in utf8 fun), and one doing wrong cut and paste (ie, taking config that didn't correspond to the VM).
So now, we just need to figure the last bit, ie having the bastion to do proper proxying to the cluster. (and me to push last commit, and basic doc)
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+----------------------- Reporter: goern | Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+-----------------------
Comment (by scollier):
Replying to [comment:16 misc]:
Finished with openshift-sdn enabked or disabled?
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+----------------------- Reporter: goern | Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+-----------------------
Comment (by misc):
Flannel is running and I do not remember activating openshift-sdn. I found why flannel was failing (wrong cut and paste), but I can reprovision with openshift-sdn later. I will likely do the deployment again just to verify I didn't do some hotfixes that I forgot, or that it did work by luck after enough bruteforce fixes.
#153: design, deploy and document Fedora OpenShift Playground (FOSP) ---------------------+----------------------- Reporter: goern | Owner: jberkus Type: task | Status: assigned Priority: normal | Milestone: Future Component: --- | Resolution: Keywords: meeting | ---------------------+-----------------------
Comment (by scollier):
share your ansible hosts file please?
-
Fedora Cloud Trac Tickets