Hello, I saw the new wiki page with ovirt blogs and was thinking how I would follow them. Then I thought about how I follow most other blogs and that's through planets (http://planet.{gentoo,debian,centos}.org). What are your opinions on setting up http://planet.ovirt.org? -- With kind regards, Ewoud Kohl van Wijngaarden
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/03/2012 02:31 AM, Ewoud Kohl van Wijngaarden wrote:
Hello,
I saw the new wiki page with ovirt blogs and was thinking how I would follow them. Then I thought about how I follow most other blogs and that's through planets (http://planet.{gentoo,debian,centos}.org). What are your opinions on setting up http://planet.ovirt.org?
+1 I've gotten partially through setting up a Python-based planet tool before, but it can't be that hard, can it? - - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFPLDJf2ZIOBq0ODEERAgSKAKDYub2CuUPQ3Obn/zhD6nJzgjRBHwCfeqF2 ZbWad6TIs4Xln2BOuAzI984= =s5bO -----END PGP SIGNATURE-----
On Fri, Feb 03, 2012 at 11:15:43AM -0800, Karsten 'quaid' Wade wrote:
On 02/03/2012 02:31 AM, Ewoud Kohl van Wijngaarden wrote:
I saw the new wiki page with ovirt blogs and was thinking how I would follow them. Then I thought about how I follow most other blogs and that's through planets (http://planet.{gentoo,debian,centos}.org). What are your opinions on setting up http://planet.ovirt.org?
+1
I've gotten partially through setting up a Python-based planet tool before, but it can't be that hard, can it? I've quickly set up a PoC on http://planet-ovirt.ekohl.nl using venus (which is python-based) with the default template and a minimal config. It seems to be very easy to set up and if you like it I'll see if I can make some simple oVirt theme.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/08/2012 08:45 AM, Ewoud Kohl van Wijngaarden wrote:
On Fri, Feb 03, 2012 at 11:15:43AM -0800, Karsten 'quaid' Wade wrote:
On 02/03/2012 02:31 AM, Ewoud Kohl van Wijngaarden wrote:
I saw the new wiki page with ovirt blogs and was thinking how I would follow them. Then I thought about how I follow most other blogs and that's through planets (http://planet.{gentoo,debian,centos}.org). What are your opinions on setting up http://planet.ovirt.org?
+1
I've gotten partially through setting up a Python-based planet tool before, but it can't be that hard, can it? I've quickly set up a PoC on http://planet-ovirt.ekohl.nl using venus (which is python-based) with the default template and a minimal config. It seems to be very easy to set up and if you like it I'll see if I can make some simple oVirt theme.
That's great! Regarding theme, we can also get some tips from Máirín Duffy; I think she's worked on the Fedora planet theme as well as the oVirt work so far. Although Venus isn't in the EPEL repository, the Fedora Infrastructure team packages it since they use it on planet.fedoraproject.org: http://infrastructure.fedoraproject.org/6/x86_64/venus-bzrrev86-2.el6.noarch... So I want to give you a shell account and sudo access to make this happen on linode01.ovirt.org. How comfortable are you with that? Are you familiar with admining a Fedora/Red Hat-based machine? For example, we need to make a yum repo file for that repository, then do an install of that package, find where the files are, and drop in the work you've done. We can also have you just do the parts you are comfortable with, if you prefer. That may include just handing it off to me to put in place. :) We also don't have a process to pass out ssh+sudo. I've been being a bad example by just giving it to a few @redhat.com people who I have a trust relationship with through mutual employer. My inclination is to trust Ewoud, but I really don't think I should be giving out shell and/or root access without some approval process from this entire team. The best example I know of shared community infrastructure is the Fedora Infrastructure team. It's a 24x7 group with only two Red Hat staffers, infrastructure on donated hosts worldwide, and a great process for bringing people in. They've segmented the work enough that a new person can be given some proving-tasks - mainly to show that they will follow through to get something done. It's OK to not have the skills to start, one has to be willing to learn and be persistent. Thoughts? - - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFPMupi2ZIOBq0ODEERAgqMAJ9iULQxXwyx5jbcOqASlOzuZE1RVwCgj5v+ exZ3tK3msqmcUSuoaXEu8fQ= =9DsL -----END PGP SIGNATURE-----
On Wed, Feb 08, 2012 at 01:34:26PM -0800, Karsten 'quaid' Wade wrote:
That's great! Regarding theme, we can also get some tips from Máirín Duffy; I think she's worked on the Fedora planet theme as well as the oVirt work so far.
That would be nice, I'm not really the graphical hero so to speak ;)
Although Venus isn't in the EPEL repository, the Fedora Infrastructure team packages it since they use it on planet.fedoraproject.org:
http://infrastructure.fedoraproject.org/6/x86_64/venus-bzrrev86-2.el6.noarch...
So I want to give you a shell account and sudo access to make this happen on linode01.ovirt.org. How comfortable are you with that? Are you familiar with admining a Fedora/Red Hat-based machine?
At my daytime job we run CentOS so should be familiar enough.
For example, we need to make a yum repo file for that repository, then do an install of that package, find where the files are, and drop in the work you've done.
We can also have you just do the parts you are comfortable with, if you prefer. That may include just handing it off to me to put in place. :)
We also don't have a process to pass out ssh+sudo. I've been being a bad example by just giving it to a few @redhat.com people who I have a trust relationship with through mutual employer. My inclination is to trust Ewoud, but I really don't think I should be giving out shell and/or root access without some approval process from this entire team.
Since it's all static files generated through a cronjob there's, other than the initial apache configuration, no need for root to maintain it.
The best example I know of shared community infrastructure is the Fedora Infrastructure team. It's a 24x7 group with only two Red Hat staffers, infrastructure on donated hosts worldwide, and a great process for bringing people in. They've segmented the work enough that a new person can be given some proving-tasks - mainly to show that they will follow through to get something done. It's OK to not have the skills to start, one has to be willing to learn and be persistent.
http://fosdem.org/2012/schedule/event/wikimedia_infra was the FOSDEM talk I was quite impressed with. The wikimedia approach: all configuration through puppet, puppet repo is in git and through gerrit code reviews you could suggest infra changes. They have a mixed team as well with a small staff and a community. Now I have no clue how the machine is set up now and keeping things like the HTTPS private key files private might be a challenge, but I think it would fit nicely since there's already gerrit for the other projects. On the other hand, we don't need to fully puppetize the setup to take advantage of it.
On Thu, Feb 09, 2012 at 12:02:14AM +0100, Ewoud Kohl van Wijngaarden wrote:
On Wed, Feb 08, 2012 at 01:34:26PM -0800, Karsten 'quaid' Wade wrote:
For example, we need to make a yum repo file for that repository, then do an install of that package, find where the files are, and drop in the work you've done.
We can also have you just do the parts you are comfortable with, if you prefer. That may include just handing it off to me to put in place. :)
We also don't have a process to pass out ssh+sudo. I've been being a bad example by just giving it to a few @redhat.com people who I have a trust relationship with through mutual employer. My inclination is to trust Ewoud, but I really don't think I should be giving out shell and/or root access without some approval process from this entire team.
Since it's all static files generated through a cronjob there's, other than the initial apache configuration, no need for root to maintain it.
How would you like to move forward with this? I don't mind hosting the planet on a VM on my own hardware either.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/13/2012 07:03 AM, Ewoud Kohl van Wijngaarden wrote:
How would you like to move forward with this? I don't mind hosting the planet on a VM on my own hardware either.
Sorry, lost this email in my inbox. So, we could definitely have you setup a VM and point planet.ovirt.org at that. Are you OK with that bandwidth usage? Want to try it out for a while and move it to other ovirt.org if needed? Alternately, we can configure the www box to be planet.ovirt.org, and get you a shell there to do the work. I'm fine with either way. - - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFPX4I82ZIOBq0ODEERAqkOAKDG9Za1x3GYGxEZJQkR4wIuO2l20wCg0qRs ataUsvWQ4Z1zCt9CmgTBnPo= =7PBq -----END PGP SIGNATURE-----
On Tue, Mar 13, 2012 at 10:22:04AM -0700, Karsten 'quaid' Wade wrote:
On 02/13/2012 07:03 AM, Ewoud Kohl van Wijngaarden wrote:
How would you like to move forward with this? I don't mind hosting the planet on a VM on my own hardware either.
Sorry, lost this email in my inbox.
So, we could definitely have you setup a VM and point planet.ovirt.org at that. Are you OK with that bandwidth usage? Want to try it out for a while and move it to other ovirt.org if needed?
Alternately, we can configure the www box to be planet.ovirt.org, and get you a shell there to do the work. I'm fine with either way.
The benefit or running my own VM would be that I can run debian which packages venus by default. Regarding bandwidth I have no problem since I'll either ask my employer to host it or my personal server where bandwidth is free (as long as it's reasonable and legal, but I doubt that will be an issue). Obvious downside would be that it's my infra and not part of the project. In short term I would prefer hosting it myself and merge it at some point in the future.
participants (2)
-
Ewoud Kohl van Wijngaarden -
Karsten 'quaid' Wade