[Openstack] creating a mailinglist for packaging specific topics?
Hello together. I think it's a good idea to create a mailinglist for packaging specific topics. This list here is IMO not the right place for discussions on such topics, because a lot of people have to read (or at least they have to filter those mails into /dev/null) them and this will waste a huge amount of time, which could be spend more useful topics. The target of this list would be to coordinate the work of packagers of the different distributions to reach more and (hopefully) identical quality and to provide packages just in time with new releases/milestones. Also to have a single point of contact for upcoming packagers and maybe to provide similar sets of packages (for example same naming convention, same versions and so on). Here a few examples I want to discuss in more detail. * what is stability in the point of view of a distributor/packager (the discussion triggered yesterday on the OSDEM on the FOSDEM 2012). I think it's necessary that we have the same point of view to not have a very different "stability" on different distributions * is it possible (and how) to share efforts between the packaging for different distributions (for example I'm pretty sure that it's possible to create nearly the same SPECs for OpenSUSE/SLES and FedoraCore/RHEL) * is it useful to host all package definitions (SPECs and so on) at a central place (for example at Github in a project openstack/packages or somethink like that) so that everybody can commit to those definitions in an easy and defined way (using gerrit for reviews..)? * should there only be one package set for one distribution or is it better to have different package sets? (for example at the moment SUSE and we (B1) are providing packages on the OpenSUSE Build Service) Bye, Christian. -- Christian Berendt Linux / Unix Consultant & Developer Mail: bere...@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] creating a mailinglist for packaging specific topics?
On 02/05/2012 12:27 PM, Christian Berendt wrote: > Hello together. > > I think it's a good idea to create a mailinglist for packaging specific > topics. This list here is IMO not the right place for discussions on > such topics, because a lot of people have to read (or at least they > have to filter those mails into /dev/null) them and this will waste a > huge amount of time, which could be spend more useful topics. I don't think the amount of traffic on cross-distribution packaging related collaboration would be that high to really be a problem on this list. I'd rather not have to sign up for yet another mailing list. -- Russell Bryant ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] creating a mailinglist for packaging specific topics?
On 02/05/2012 06:38 AM, Russell Bryant wrote: On 02/05/2012 12:27 PM, Christian Berendt wrote: Hello together. I think it's a good idea to create a mailinglist for packaging specific topics. This list here is IMO not the right place for discussions on such topics, because a lot of people have to read (or at least they have to filter those mails into /dev/null) them and this will waste a huge amount of time, which could be spend more useful topics. I don't think the amount of traffic on cross-distribution packaging related collaboration would be that high to really be a problem on this list. I'd rather not have to sign up for yet another mailing list. Hi Christian! So, the topic of multiple mailing lists has come up before and we've even tried topical mailing lists before, but the amount of traffic on them tends to be too low for it to be worth the extra ML subscription. I've also made the argument before that with a general mailing list (this one), you get a wider audience and people that may not always get excited about distribution specifics may be exposed to important discussions, learn something new, and in general just be made aware of the state of a particular subcommunity by scanning/skimming emails. After all, it's easy enough to just delete/archive emails that you really don't care about -- or create filters. When posting distribution-specific topics to the main mailing list, just use the convention "[TOPIC] Discussion subject" as your email subject. So, something like: [DISTRO] Common place to house RPM-based distro artifacts That way, it's easy for folks to ignore if they don't wish to follow the conversation. All the best, -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Swift S3 with Keystone anyone?
On Thu, 2 Feb 2012 19:03:54 +0900 Akira Yoshiyama wrote: > I modified the wiki: > http://wiki.openstack.org/Keystone-BP-S3Token > > I added authtoken in main pipeline just now. I was unable to find the official configuration for "authtoken". Since it's only a name of convention, I cannot even guess what module is meant here. Some people seem to use authtoken like this: [filter:authtoken] paste.filter_factory = keystone.middleware.auth_token:filter_factory service_protocol = http service_host = 127.0.0.1 service_port = 5000 auth_host = 127.0.0.1 auth_port = 35357 auth_protocol = http auth_uri = http://127.0.0.1:5000/ admin_token = 999888777666 ;Uncomment next line and check ip:port to use memcached to cache token requests ;memcache_hosts = 127.0.0.1:11211 Is it what you meant? If yes, what does it do in case of S3? The diagram in the wiki does not mention it. -- Pete ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
