Hello all, Long time ago we talked about mapping put infra and creating something similar to [1]. Ticket [2] So I mapped our infra as well [3]. If I missed something, please send a patch. Enjoy ! [1] https://apps.fedoraproject.org/ [2] https://fedorahosted.org/ovirt/ticket/49 [3] http://monitoring.ovirt.org/ovirt.apps/ - Kiril
Cool! worth adding the link to http://www.ovirt.org/Infrastructure#Our_Architecture as well. if thinking on expanding this, some ideas come to mind: in gerrit subtree, we can add like urls for common searches in gerrit.ovirt.org in jenkins subtree, we can add urls for specific jobs.. i'm sure we'll be able to use it for more consolidation purposes of important links. thanks for bringing this up, Eyal. ----- Original Message -----
From: "Kiril Nesenko" <kiril@redhat.com> To: "infra" <infra@ovirt.org> Sent: Tuesday, October 22, 2013 2:21:40 PM Subject: Mapping oVirt Infra
Hello all,
Long time ago we talked about mapping put infra and creating something similar to [1]. Ticket [2]
So I mapped our infra as well [3]. If I missed something, please send a patch.
Enjoy !
[1] https://apps.fedoraproject.org/ [2] https://fedorahosted.org/ovirt/ticket/49 [3] http://monitoring.ovirt.org/ovirt.apps/
- Kiril _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "Kiril Nesenko" <kiril@redhat.com> Cc: "infra" <infra@ovirt.org> Sent: Tuesday, October 22, 2013 3:08:40 PM Subject: Re: Mapping oVirt Infra
Cool!
worth adding the link to http://www.ovirt.org/Infrastructure#Our_Architecture as well.
Done
if thinking on expanding this, some ideas come to mind:
in gerrit subtree, we can add like urls for common searches in gerrit.ovirt.org in jenkins subtree, we can add urls for specific jobs..
I don't think it the purpose of this site. The main goal is to map all systems and to see what we have. But its possible to add it as well. - Kiril
i'm sure we'll be able to use it for more consolidation purposes of important links.
thanks for bringing this up,
Eyal.
----- Original Message -----
From: "Kiril Nesenko" <kiril@redhat.com> To: "infra" <infra@ovirt.org> Sent: Tuesday, October 22, 2013 2:21:40 PM Subject: Mapping oVirt Infra
Hello all,
Long time ago we talked about mapping put infra and creating something similar to [1]. Ticket [2]
So I mapped our infra as well [3]. If I missed something, please send a patch.
Enjoy !
[1] https://apps.fedoraproject.org/ [2] https://fedorahosted.org/ovirt/ticket/49 [3] http://monitoring.ovirt.org/ovirt.apps/
- Kiril _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On Tue, Oct 22, 2013 at 07:21:40AM -0400, Kiril Nesenko wrote:
Long time ago we talked about mapping put infra and creating something similar to [1]. Ticket [2]
So I mapped our infra as well [3]. If I missed something, please send a patch.
I think this is a great starting point, but we should share this with more people. For one, I know VDSM has its mailing lists at fedorahosted.org and http://www.ovirt.org/Subprojects can be translated into the graph. Some things I should really make a PR for: * move the oVirt instances under For Sysadmins * move children of Usual Usage directly under oVirt Apps or under Community * rename oVirt Trac to Infra ticketing system and move it to Sysadmins * rename all nodes ** For Sysadmins to Infra (because most of our users are also sysadmins) ** For Community to Community ** For Developers to Developers * rename The Mailing lists to Mailing lists
----- Original Message -----
From: "Ewoud Kohl van Wijngaarden" <ewoud+ovirt@kohlvanwijngaarden.nl> To: infra@ovirt.org Sent: Tuesday, October 22, 2013 3:25:18 PM Subject: Re: Mapping oVirt Infra
On Tue, Oct 22, 2013 at 07:21:40AM -0400, Kiril Nesenko wrote:
Long time ago we talked about mapping put infra and creating something similar to [1]. Ticket [2]
So I mapped our infra as well [3]. If I missed something, please send a patch.
I think this is a great starting point, but we should share this with more people. For one, I know VDSM has its mailing lists at fedorahosted.org and http://www.ovirt.org/Subprojects can be translated into the graph.
Some things I should really make a PR for:
* move the oVirt instances under For Sysadmins * move children of Usual Usage directly under oVirt Apps or under Community * rename oVirt Trac to Infra ticketing system and move it to Sysadmins * rename all nodes ** For Sysadmins to Infra (because most of our users are also sysadmins)
Sysadmins - meaning for the infra team members
** For Community to Community ** For Developers to Developers
Why do we need to remove 'For' ?
* rename The Mailing lists to Mailing lists _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
participants (3)
-
Ewoud Kohl van Wijngaarden -
Eyal Edri -
Kiril Nesenko