Re: What is our technical debt?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 26 Jun 2020 at 10:34, David Kirwan <dkirwan@xxxxxxxxxx> wrote:
>
> Hi all,
>
> If we are moving towards openshift/kubernetes backed services, we should probably be sticking with containers rather than Vagrant. We can use CRC [1] (Code Ready Containers) or minikube [2] for most local dev work.
>

The only problem with that is not everything runs in containers. For
example the new AAA service is backed by FreeIPA and that does not run
in a container. Everything will run in a virtual machine given that
enough care has been put into creating the VM. I don't think the same
can be said for containers.

> I'd be very much in favour of having an Infra managed Prometheus instance (+ grafana and alertmanager on Openshift), its something I hoped to work on within CPE sustaining infact.
>
>
> - [1] https://github.com/code-ready/crc
> - [2] https://minikube.sigs.k8s.io/docs/
>
>
>
> On Fri, 26 Jun 2020 at 10:23, Luca BRUNO <lucab@xxxxxxxxxx> wrote:
>>
>> On Thu, 25 Jun 2020 15:59:44 -0700
>> Kevin Fenzi <kevin@xxxxxxxxx> wrote:
>>
>> > > What else would we want in there?
>> >
>> > Monitoring - we will likely get our nagios setup again soon just
>> > because it's mostly easy, but it's also not ideal.
>>
>> On this one (or more broadly "observability") I'd still like to see an
>> infra-managed Prometheus to internally cover and sanity-check the
>> "openshift-apps" services.
>> I remember this was on the "backlog" dashboard at Flock'19 but I don't
>> know if it got translated to an actual action item/ticket in the end.
>>
>> Ciao, Luca
>> _______________________________________________
>> infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
>> To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
>> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
>
>
>
> --
> David Kirwan
> Software Engineer
>
> Community Platform Engineering @ Red Hat
>
> T: +(353) 86-8624108     IM: @dkirwan
>
> _______________________________________________
> infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx



-- 
Stephen Coady
Software Engineer
Red Hat
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux