Re: [OpenStack-Infra] Puppet Apache Dependency Issues

2015-08-27 Thread Yolanda Robla Mota
Hi Thanks for the explanation. As this is a topic that needs more background, and a deeper discussion, I created an etherpad to work on it. You can access on: https://etherpad.openstack.org/p/puppet-httpd_vs_puppetlabs-apache Best Yolanda El 26/08/15 a las 20:31, Spencer Krum escribió: Hello

Re: [OpenStack-Infra] Puppet Apache Dependency Issues

2015-08-27 Thread Ricardo Carrillo Cruz
I lean towards fixing now by using the new defined type and we write a spec for migrating to puppetlabs-apache (once we merge in upstream infra needs). Regards 2015-08-27 11:07 GMT+02:00 Yolanda Robla Mota : > Hi > Thanks for the explanation. As this is a topic that needs more background, > and

Re: [OpenStack-Infra] [Openstack-i18n] Final plans before translations switch to Zanata

2015-08-27 Thread Andreas Jaeger
Could we also revise languages and language codes? I think we should prefer Country-independent languages over country ones. So, we should prefer German ("de") over German in Germany ("de_DE") and German in Austria ("de_AT"). In case where we have country specific ones - like pl_PL -, can we

Re: [OpenStack-Infra] [Openstack-i18n] Final plans before translations switch to Zanata

2015-08-27 Thread Andreas Jaeger
On 2015-08-27 04:58, Steve Kowalik wrote: [...] The only thing I'm concerned about here is there is currently no support for pulling translations for Horizon or the OpenStack manuals projects, due to having multiple directories with overlapping locales. For example, horizon master has: openst

Re: [OpenStack-Infra] [Openstack-i18n] Final plans before translations switch to Zanata

2015-08-27 Thread Elizabeth K. Joseph
On Thu, Aug 27, 2015 at 3:17 AM, Andreas Jaeger wrote: > Could we also revise languages and language codes? > > I think we should prefer Country-independent languages over country ones. > > So, we should prefer German ("de") over German in Germany ("de_DE") and > German in Austria ("de_AT"). > > I

Re: [OpenStack-Infra] [Openstack-i18n] Final plans before translations switch to Zanata

2015-08-27 Thread Remo Mattei
looks good but there is not US (en_US) in that list. Remo > On Aug 27, 2015, at 09:10, Elizabeth K. Joseph wrote: > > On Thu, Aug 27, 2015 at 3:17 AM, Andreas Jaeger wrote: >> Could we also revise languages and language codes? >> >> I think we should prefer Country-independent languages over

[OpenStack-Infra] Gerrit downtime on Friday 2015-09-11 at 23:00 UTC

2015-08-27 Thread James E. Blair
On Friday, September 11 at 23:00 UTC Gerrit will be unavailable for about 30 minutes while we rename some projects. Existing reviews, project watches, etc, should all be carried over. Currently, we plan on renaming the following projects: stackforge/os-ansible-deployment -> openstack/openstack-

Re: [OpenStack-Infra] [Openstack-i18n] Final plans before translations switch to Zanata

2015-08-27 Thread Andreas Jaeger
On 08/27/2015 06:10 PM, Elizabeth K. Joseph wrote: On Thu, Aug 27, 2015 at 3:17 AM, Andreas Jaeger wrote: Could we also revise languages and language codes? I think we should prefer Country-independent languages over country ones. So, we should prefer German ("de") over German in Germany ("de

Re: [OpenStack-Infra] Puppet Apache Dependency Issues

2015-08-27 Thread Yolanda Robla Mota
I agree with that approach. We are hitting several issues with httpd_mod that should be fixed using a defined type. But I do believe that the way is to consume modules that are trusted by the community, and don't put efforts on maintaining and evolving our own modules if there are good alternati

Re: [OpenStack-Infra] Puppet Apache Dependency Issues

2015-08-27 Thread Spencer Krum
I don't think we should plan to use puppet-apache. I think we should commit to our fork and fix the issues we have. We can build a simple, flexible apache module and stop. Committing to puppetlabs-apache puts us on the roller coaster of updates and bugfixes. The issues we are having are not hard t

Re: [OpenStack-Infra] [Openstack-i18n] Final plans before translations switch to Zanata

2015-08-27 Thread Andreas Jaeger
On 08/27/2015 06:13 PM, Remo Mattei wrote: looks good but there is not US (en_US) in that list. US English is the source language, we do not need it translated We have en in the list as source and that is by convention en_US, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Ident

Re: [OpenStack-Infra] Puppet Apache Dependency Issues

2015-08-27 Thread Yolanda Robla Mota
So... we are already consuming several modules from other providers, relying on it. Is there some problem of trust in the puppetlabs-apache community? Which are the main reasons (apart from the vhost generation) that are preventing us to rely on it, while we rely on others? El 27/08/15 a las 2

[OpenStack-Infra] Stackforge migration on October 17; action required for stackforge projects

2015-08-27 Thread James E. Blair
Hi, In a previous message[1] I described a plan for moving projects in the stackforge/ git namespace into openstack/. We have scheduled this migration for Saturday October 17, 2015. If you are responsible for a stackforge project, please visit the following wiki page as soon as possible and add

Re: [OpenStack-Infra] Puppet Apache Dependency Issues

2015-08-27 Thread Jeremy Stanley
On 2015-08-26 11:31:35 -0700 (-0700), Spencer Krum wrote: [...] > The issue is that the httpd_mod type does not have a baked-in > ordering relationship with the Service['httpd'] resource. [...] This is not the only issue. We also discovered there are places we're installing files into /etc/apache2

[OpenStack-Infra] OpenStack Mailing List question: how to rename a mailing list?

2015-08-27 Thread Ju Lim
Hi. I'm not sure who to contact with my question, but I'm hoping someone on this list can help. We in the OpenStack UX community would like to re-purpose the OpenStack Personas (openstack-perso...@lists.openstack.org) and rename it OpenStack-UX vs. re-creating a brand new OpenStack-UX mailing lis

[OpenStack-Infra] Request for server for developer.openstack.org

2015-08-27 Thread Anne Gentle
Hi all, Sorry I missed the IRC meeting this week, I could've explained there, but did see the request to ask on the list so here we go! In order to serve API reference docs, we need a Pecan server on a cloud server of some sort. I'm guessing this server could be deployed with Puppet but I really d

Re: [OpenStack-Infra] Puppet Apache Dependency Issues

2015-08-27 Thread Paul Belanger
On Wed, Aug 26, 2015 at 11:31:35AM -0700, Spencer Krum wrote: > Hello All, > > At the meeting on August 25th, we discussed an issue with the puppet-httpd > module and a few solutions. The issue is that the httpd_mod type does not > have a baked-in ordering relationship with the Service['httpd'] re

Re: [OpenStack-Infra] Puppet Apache Dependency Issues

2015-08-27 Thread Spencer Krum
I went off list accidentally here. Copying in for the benefit of others. On Thu, Aug 27, 2015 at 5:38 PM, Spencer Krum wrote: > In that case I would recommend either before => Package['httpd'] or before > => Class['httpd::install']. (The second one requires us to create that > class, but this is

Re: [OpenStack-Infra] Puppet Apache Dependency Issues

2015-08-27 Thread Jeremy Stanley
On Thu, Aug 27, 2015 at 5:38 PM, Spencer Krum wrote: [...] > In that case I would recommend either before => Package['httpd'] or before > => Class['httpd::install']. (The second one requires us to create that > class, but this is a pattern used by many modules to expose exactly this > kind of hook

Re: [OpenStack-Infra] Puppet Apache Dependency Issues

2015-08-27 Thread Spencer Krum
> Do you maybe mean "after => Package['httpd']" there? Yes. I mean 'require.' On Thu, Aug 27, 2015 at 6:08 PM, Jeremy Stanley wrote: > On Thu, Aug 27, 2015 at 5:38 PM, Spencer Krum > wrote: > [...] > > In that case I would recommend either before => Package['httpd'] or > before > > => Class['ht

Re: [OpenStack-Infra] Puppet Apache Dependency Issues

2015-08-27 Thread Yolanda Robla Mota
So ... to summarize, we found 3 different issues: 1. Races on httpd_mod -> httpd_mod is a custom type, relying on ruby code. It has a clear race, that is shown on all of our manifests using that. If you use httpd_mod to install new apache modules, they won't be applied until apache is restarted