On Tue, Jul 4, 2017, at 07:17 PM, Kevin Fenzi wrote:
On 07/04/2017 04:22 AM, Brian Exelbierd wrote:
>
>
> On Mon, Jul 3, 2017, at 11:05 PM, Jeremy Cline wrote:
>> On 07/03/2017 01:51 PM, Kevin Fenzi wrote:> The next steps are:
>>>
>>> * Make sure our plan for managing apps/routers/etc will work.
>>> Basically> >>> we thought we would check in .json configs in
ansible and then
>>> have it> >>> run os commands loading those. We need a app using
that method to> >>> confirm it works as we expect. I think relrod was going to
try
>>> and do> >>> that with waverdb or modernpaste, but we should
confirm, he might
>>> have> >>> been working on the non config part of this. ;)
>>
>> I'm ready to move the-new-hotness over. Is the expectation that I
>> deliver a JSON file that defines my project as part of a
>> request for> >> resources ticket?
>>
>> Are we going to disable editing in the web UI and only let
>> changes get> >> applied by hand-editing the JSON and pushing that with
Ansible?
>> I'm not> >> necessarily objecting to that approach, I'm just
curious.
>>
>> Would it be better for us to have web editing privileges and
>> use the> >> staging instance to tune our configurations in an
OpenShift
>> configured> >> the same way the production instance will be, then
export those for> >> production, or are we better off all having development
OpenShift
>> instances for that? We'll need to all be careful to run the same
>> version> >> as stg/production since it sounds like this JSON isn't
particularly> >> well-documented, nor is there any schema or validation tools.
>
> Have we checked with how the RH IT and RH OpenShift Online teams do> > this?
>
> They may have an answer for us.
Yes, and we could ask again now, but when we talked to folks at the
hackfest in RDU pretty much the answer was that it was up in
the air and> some of them were using oc commands in ansible to make apps, etc...
I didnt jnow know how well the operational side of that team was
represented at the hackfest.
Regards,
bex
kevin
_______________________________________________
infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org> To unsubscribe
send an email to
infrastructure-leave(a)lists.fedoraproject.org
Email had 1 attachment:
+ signature.asc
1k (application/pgp-signature)