Re: [OpenStack-Infra] Multi-Source Publishing on docs.airshipit.org
On 20.04.20 16:37, WALTERS, ANDREW wrote:
> Hello!
>
>
>
> Thank you for giving Airship documentation a home. Having our
> documentation spread across several Read the Docs sites has long been a
> frustration for new Airship users. We are excited to fully embrace the
> site but cannot do so until all of our content is represented there.
> Since we have many source code repositories, our documentation
> originates from several different locations. For example, Treasuremap is
> publishing to docs.airshipit.org; however, Armada documentation [0] is
> not reachable from that page
>
>
>
> The Airship Working Committee has considered how to accomplish hosting
> all of our documentation on the same site while allowing it to live in
> the same repositories as the corresponding source code. Looking at the
> publish job [1], it appears that we could accomplish this by removing
> the final key, adding all of our projects to the “allowed-projects”
> list, and overriding the “publish_site” variable in repository-specific
> jobs. For example, we could create a job in the Armada repository that
No, you're not allowed to override the variable. Instead change it to
have a variable in it like:
publish_site: "airshipit.org/docs/{{ zuul.project.short_name }}"
So, create a new job with the changed variable and use that new job
everywhere,
Andreas
> publishes to “airshipit.org/docs/armada” and link to it from our main
> documentation at docs.airshipit.org.
>
>
>
> Is our approach feasible given our current setup? If so, the Working
> Committee will start submitting the necessary changes.
>
>
>
> Thanks in advance for your help!
>
>
>
> Best regards,
>
>
>
> Drew Walters
>
> Airship Working Committee
>
>
>
> [0] https://airshipit.readthedocs.io/projects/armada/en/latest/
>
> [1]
> https://opendev.org/openstack/project-config/src/branch/master/zuul.d/jobs.yaml#L452
>
>
> _______
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
--
Andreas Jaeger a...@suse.com Twitter: jaegerandi
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg
(HRB 36809, AG Nürnberg) GF: Felix Imendörffer
GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Openstack-documentation publish
On 02.04.20 07:44, mohibtech wrote: > Hi, > I want to publish openstack documentation in my language. Is it > possible. If possible please help me how can i do it. Hi, Best to reach out to the i18n team, see docs.openstack.org/i18n/ Andreas -- Andreas Jaeger a...@suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Can not access the devstack-gate repo.
On 7/25/19 10:18 AM, Xiao Mei GZ Zheng wrote: > Hi Infra, > > Is there any change for the devstack-gate repo? I found this error when > trying to clone the project. > > > + git clone https://git.openstack.org/openstack-infra/devstack-gateCloning > into 'devstack-gate'... > fatal: unable to access 'https://opendev.org/openstack-infra/devstack-gate/': > GnuTLS recv error (-110): The TLS connection was non-properly terminated. > This should fixed now, there was a problem in the cloud provider we run the service, Andreas -- Andreas Jaeger a...@suse.com Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] [rsd-lib] how to sync code from opendev to github
On 7/16/19 11:01 AM, Lei Zhang wrote: > Hi Andreas > > Is there any action to take on github repos outside OpenStack > governance but still under openstack namespace? This is somewhat > confusing for repo consumers as they may not notice this and still use > outdated code. You can work together with the infra team to transfer the repo for that so that redirects exist, Andreas -- Andreas Jaeger a...@suse.com Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [rsd-lib] how to sync code from opendev to github
On 10/07/2019 08.43, Lei Zhang wrote: > Hi guys, > > We have a project named rsd-lib originally was under openstack and CI > takes the charge to push new changes to github repo. Now the project has > been changed from openstack/rsd-lib to > x/rsd-lib(https://opendev.org/x/rsd-lib). The github > repo(https://github.com/openstack/rsd-lib) stops getting newly merged code. > > My question is that is there a way for rsd-lib to continue syncing code > to https://github.com/openstack/rsd-lib, or we have to create another > github repo to mirror the code? You can set this up on your own - but not to openstack/rsd-lib, that name space is only for official OpenStack projects, you need to create your own namespace. For details, read the Infra Manual: https://docs.openstack.org/infra/manual/creators.html#mirroring-projects-to-git-mirrors Andreas -- Andreas Jaeger a...@suse.com Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Zanata broken on Bionic
On 27/04/2019 03.56, Frank Kloeker wrote:
> [...]
> The biggest problem at the moment are pot files. Weblate expects this in
> the source repo which we haven't. But Weblate has it's own local repos.
> It's not clear at the moment how we design the workflow. Zuul can also
> push changes on rst files in the Weblate repo and Weblate can build pot
> files there. It's to think about it.
Pot files are generated files, so there's always an extra step to create
them and keep them in sync.
I see the following options:
* Ensure that users update pot files. That will leads to many conflicts
and rebases, so is out.
* Have a job that writes to gerrit. We're not doing anything like that
in OpenStack by policy.
* Have a separate place that stores pot files.
We use with translate.o.o the third way and store the pot files directly
in translate.o.o. We could generate a special "pot-files repo" that is
used for syncing.
Pushing rst files to Weblate could work as well - but we also have repos
like tripleo-ui that use JSON and not rst,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Zanata broken on Bionic
On 27/04/2019 03.56, Frank Kloeker wrote:
> [...]
> The biggest problem at the moment are pot files. Weblate expects this in
> the source repo which we haven't. But Weblate has it's own local repos.
> It's not clear at the moment how we design the workflow. Zuul can also
> push changes on rst files in the Weblate repo and Weblate can build pot
> files there. It's to think about it.
Pot files are generated files, so there's always an extra step to create
them and keep them in sync.
I see the following options:
* Ensure that users update pot files. That will leads to many conflicts
and rebases, so is out.
* Have a job that writes to gerrit. We're not doing anything like that
in OpenStack by policy.
* Have a separate place that stores pot files.
We use with translate.o.o the third way and store the pot files directly
in translate.o.o. We could generate a special "pot-files repo" that is
used for syncing.
Pushing rst files to Weblate could work as well - but we also have repos
like tripleo-ui that use JSON and not rst,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] openstack/openstack still broken
My changes to update openstack/openstack merged but I still see a problem:
https://opendev.org/openstack/openstack gives still a 500 internal error
I wonder whether github.com/openstack/openstack is correct or got
confused by the org changes as well.
Have a look at project-config as one example...
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Nodepool image building broken after OpenDev change?
On 21/04/2019 19.04, Andreas Jaeger wrote:
> On 21/04/2019 18.53, Andreas Jaeger wrote:
>> Looking at http://nl01.openstack.org/image-list it looks like no new
>> images were build after the OpenDev changes on Friday.
>>
>> No urgency on this for now - but sending it here as discussed on
>> #openstack-infra so that it is not forgotten. Hope somebody picks it up ;)
>
> Hope this fixes it:
> https://review.opendev.org/654257
>
> Please check images once that is in,
I see new images for bionic and others. Hope that the remaining images
build today as well (my change merged too late for all images to get the
new content),
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Nodepool image building broken after OpenDev change?
On 21/04/2019 18.53, Andreas Jaeger wrote:
> Looking at http://nl01.openstack.org/image-list it looks like no new
> images were build after the OpenDev changes on Friday.
>
> No urgency on this for now - but sending it here as discussed on
> #openstack-infra so that it is not forgotten. Hope somebody picks it up ;)
Hope this fixes it:
https://review.opendev.org/654257
Please check images once that is in,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Nodepool image building broken after OpenDev change?
Looking at http://nl01.openstack.org/image-list it looks like no new
images were build after the OpenDev changes on Friday.
No urgency on this for now - but sending it here as discussed on
#openstack-infra so that it is not forgotten. Hope somebody picks it up ;)
Thanks!
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] OpenDev git hosting migration and Gerrit downtime April 19, 2019
On 17/04/2019 02.14, Clark Boylan wrote:
> The infra/OpenDev team continues to make good progress towards this
> transition and plans to perform the transition on April 19, 2019 as
> previously scheduled. We will begin the transition at 15:00UTC and users
> should plan for intermittent Gerrit and git repo outages through the day. We
> expect most of those will be closer to 15:00UTC than 23:00UTC.
>
> Fungi has generated a master list of project renames for the openstack
> namespaces: http://paste.openstack.org/show/749402/. If you have a moment
> please quickly review these planned renames for any obvious errors or issues.
I wonder about these three, are they missing in some governance repo list?
openstack/governance-website -> x/...
openstack/interop-workloads -> x/interop-workloads
openstack/openstack-map -> x/openstack-map
> For the airship, starlingx, and zuul repo renames the repositories listed at
> git.airshipit.org, git.starlingx.io, and git.zuul-ci.org were used placing
> repos in airship/, starlingx/ and zuul/ namespaces. Any repo name prefix
> (like stx- and airship-) is dropped.
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Zanata broken on Bionic
All translation jobs are failing since zanata-cli fails, looking at the
error it looks like Java11 is too new for zanata-cli.
I tested the most recent zanata-cli package 4.6.2 (from last year), and
it failed as well.
Logs:
http://logs.openstack.org/periodic/git.openstack.org/openstack/python-keystoneclient/master/propose-translation-update/8c7d3e8/job-output.txt.gz#_2019-03-15_07_56_38_362424
I see two options:
1) Downgrading java to openjdk8 in the used bionic image
2) Going back to Xenial for the job
Alex Eng is not working on Zanata anymore and was our contact in the
past - I remember another person involved but forgot his name ;( Anybody
remembers or can reach out to Zanata folks for help on fixing this for
good, please?
I've pushed https://review.openstack.org/643539 for going back to
Xenial as temporary workaround. But we should figure out the real fix,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Retiring openstack-infra/puppet-stackalytics (was Retiring openstack-infra/puppet-storyboard)
this is about stackalytics, not storyboard! Please do global search &
replace ;(
So, I will retire puppet-stackalytics,
Andreas
On 18/01/2019 17.11, Andreas Jaeger wrote:
> The repo openstack-infra/puppet-storyboard has been created with the
> intent to host storyboard by the OpenStack Infra team - and this did not
> happen. We will therefore retire the repository,
>
> I'm proposing patches now with topic retire-puppet-storyboard,
>
> Andreas
>
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Retiring openstack-infra/puppet-storyboard
The repo openstack-infra/puppet-storyboard has been created with the
intent to host storyboard by the OpenStack Infra team - and this did not
happen. We will therefore retire the repository,
I'm proposing patches now with topic retire-puppet-storyboard,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] https on eavesdrop.o.o broken
Reviewing a patch that changed http://eavesdrop.o.o to https, I checked
and noticed that the URL gives a misconfiguration error. Should we stop
running Apache on port 443 for eavesdrop - or configure the server
properly with https?
Sending it here so that somebody can clean it up later and we don't
forget it...
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Migrating job configs into infra repositories
On 2018-08-31 20:41, Clark Boylan wrote:
Hello,
OpenStack is currently in the process of migrating project CI job configs into
individual repos. Part of the motivation for this was to remove us (the Infra
team) as a roadblock to getting job config changes merged. This is particular
important for OpenStack as it is trying to update its job configs to be python3
first so there will be a fair bit of job churn over the Stein cycle.
This is great for OpenStack, but the question has come up about whether or not
we (the Infra team) want to do similar for our projects.
My initial thought is that it isn't as urgent for us because infra-core already
manage both the separate repos and the central job config. This means we can
manage the job churn ourselves regardless of the location. Considering the
other items we currently have on our place (namely Winterscale and config
management updates) I'm willing to defer on this for now.
If you think we should make moving job config into our repos a priority please
let me know. More than happy to accommodate this work, but we will likely need
a volunteer to help do it. (I don't expect we'll be able to piggy back off of
the OpenStack work as we have many non standard jobs from OpenStack's
perspective).
Moving the jobs in repo is not that difficult - updating them all to use
python3 will be. The scripts by Doug will help us a lot.
Still, for our 158 repositories, I don't see the benefit at the moment
since it's the same team dealing with it and as Clark said we have some
other things on the plate. We can do this for repos where - and once -
it makes sense one by one over time as we did already,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Retiring some repos?
On 2018-08-29 07:03, Andreas Jaeger wrote:
I digged into the remaining and will investigate whether we can retire
them:
openstack-infra/zuul-packaging
Paul, should we abandon this one as well?
openstack-infra/featuretracker (together with puppet-featuretracker)
these work together with openstack/development-proposals from the
product working group, I'll reach out to them.
the product WG is retired, see
http://lists.openstack.org/pipermail/user-committee/2018-February/002599.html
the URL http://featuretracker.openstack.org/ is also dead.
So, we can retire these two as well,
Andreas
puppet-docker-registry:
See https://review.openstack.org/#/c/399221/ - there's already another
tool which we should use, never any commits merged to it.
pynotedb
I'll reach out to storyboard team.
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Retiring some repos?
On 2018-08-28 23:50, Clark Boylan wrote:
> On Sun, Aug 19, 2018, at 9:47 AM, Andreas Jaeger wrote:
>> A quick search with codesearch suggests that these can be retired since
>> I couldn't find a user:
>>
>[...]
>> openstack-infra/releasestatus (together with puppet-releasestatus, not
>> listed above)
AFAIK we can remove these two as well - looking at:
https://review.openstack.org/254817
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Retiring some repos?
I digged into the remaining and will investigate whether we can retire them:
openstack-infra/zuul-packaging
Paul, should we abandon this one as well?
openstack-infra/featuretracker (together with puppet-featuretracker)
these work together with openstack/development-proposals from the
product working group, I'll reach out to them.
puppet-docker-registry:
See https://review.openstack.org/#/c/399221/ - there's already another
tool which we should use, never any commits merged to it.
pynotedb
I'll reach out to storyboard team.
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Retiring some repos?
On 2018-08-28 23:50, Clark Boylan wrote:
> [...]
I think these repos can definitely be retired:
# Was part of bitergia work with openstack which is no longer done
openstack-infra/activity-board
# These may have been attempts at having puppet beaker testing play nice with
our CI but we hacked around it by pointing the beaker config at localhost.
There are no commits here should be safe to retire.
openstack-infra/beaker-localhost
openstack-infra/beaker-nodepool
# Part of a plan to make our IRC bots errbot driven but more recent spec has us
sticking with supybot fork and plugins.
openstack-infra/err2d2
# Allowed us to mirror npm packages on afs until npm grew too large. I think we
can retire this as we don't mirror npm any longer
openstack-infra/js-afs-blob-store
openstack-infra/js-openstack-registry-hooks
# Appears to be a cookiecutter like system for openstack js projects. Maybe we
should just use cookiecutter?
openstack-infra/js-generator-openstack
# Was tooling to make a mirror of a subset of pypi. We moved to bandersnatch
and now just proxy cache pypi
openstack-infra/pypi-mirror
# Trystack has been retired due to spam and the passport program is suggested
instead
openstack-infra/trystack-site
# Project to provide alternate Gerrit UI that never got commits
openstack-infra/puppet-vinz
openstack-infra/vinz
openstack-infra/vinz-webclient
I've started retiring of these above with
https://review.openstack.org/597370,
thanks for reviewing the list and giving a rationale,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Broken Setup for ATT Airship-CI
fyi, just got an answer that the CI is disabled.
ATT team, if you need help with setup, please read the referenced page
and reach out - having third party CI testing is good ;), just let's do
it so that it's beneficial for everybody,
thanks,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Broken Setup for ATT Airship-CI
Hi ATT Airship-CI contact,
I noticed on https://review.openstack.org/#/c/596433/ (and other
changes) two separate reports from Airship-CI:
1) "Build Failed
https://jenkins-nc.mtn13b1.cci.att.com/job/images/job/airship/job/deckhand/job/deckhand/413/
: FAILURE"
2) "Build Failed
http://10.24.20.18:30081/job/images/job/airship/job/deckhand/job/deckhand/360/
: FAILURE"
Could you update your CI system to follow the CI policy as documented at
https://docs.openstack.org/infra/system-config/third_party.html, please?
Let me cite the following items:
"A third-party system may only leave one comment per patch set (unless
it is retriggered)."
-> yours left two
"All comments from your CI system must contain a link to the wiki page
for your CI system."
-> no such link was left
"Include a public link to all test artifacts to make debugging failed
tests easier (using a dns name over a hardcoded ip is recommended). This
should include:"
-> Neither of the links above is public. Thus your reporting is not
helping the community at large.
Please update your system to follow our policy - and especially those
three items above.
thanks,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] How to display the result of tests on the upper right of a gerrit page
Seeing this is about networking-spp, please review and approve:
https://review.openstack.org/#/c/592656/
https://review.openstack.org/#/c/592664/
Please do not have the pipeline configuration for your own CI in
OpenStack git repos. The job definition is fine but not the pipeline -
it fails now in OpenStack Zuul,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Retiring some repos?
On 2018-08-19 23:04, Akihiro Motoki wrote:
Comments on nose related projects : nose-html-output and openstack-nose
I am not sure that no update means non-used.
Thanks for your insight and comments - so, yes, those two need to stay
around,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Retiring some repos?
Just for the curious ones, of the 1453 repos that I have checked out on
my system, 447 have not seen a change in the last 12 months. Largest
group is fuel with 149 repos.
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Retiring some repos?
-infra/releasestatus
Last update was 2015-06-30T14:27:24+02:00
==
Found old openstack-infra/reviewstats
Last update was 2017-04-19T14:34:43+01:00
==
Found old openstack-infra/trystack-site
Last update was 2016-06-15T18:20:23+00:00
==
Found old openstack-infra/vinz
Last update was 2014-06-12T20:36:19+00:00
==
Found old openstack-infra/vinz-webclient
Last update was 2014-06-12T20:36:45+00:00
==
Found old openstack-infra/zmq-event-publisher
Last update was 2016-04-13T17:24:01-07:00
==
Found old openstack-infra/zuul-packaging
Last update was 2013-11-12T17:27:02-05:00
... done
A quick search with codesearch suggests that these can be retired since
I couldn't find a user:
openstack-infra/activity-board
openstack-infra/beaker-localhost
openstack-infra/beaker-nodepool
openstack-infra/err2d2
openstack-infra/featuretracker (together with puppet-featuretracker, not
listed above)
openstack-infra/js-afs-blob-store
openstack-infra/js-generator-openstack
openstack-infra/js-openstack-registry-hooks
openstack-infra/nose-html-output
openstack-infra/openstackweb
openstack-infra/puppet-docker_registry
openstack-infra/project-config-example
openstack-infra/pynotedb
openstack-infra/pypi-mirror
openstack-infra/releasestatus (together with puppet-releasestatus, not
listed above)
openstack-infra/trystack-site
openstack-infra/vinz
openstack-infra/vinz-webclient
openstack-infra/zuul-packaging
That's 21 repositories.
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Stop supporting bindep-fallback.txt moving forward
On 2018-04-20 16:05, Paul Belanger wrote:
> On Fri, Apr 20, 2018 at 09:07:25AM +0200, Andreas Jaeger wrote:
>> On 2018-04-20 01:15, Paul Belanger wrote:
>>> Greetings,
>>>
>>> I'd like to propose we hard freeze changes to bindep-fallback.txt[1] and
>>> push
>>> projects to start using a local bindep.txt file.
>>>
>>> This would mean, moving forward with ubuntu-bionic, if a project was still
>>> depending on bindep-fallback.txt, their jobs may raise a syntax error.
>>>
>>> In fact, today ubuntu-bionic does seem to pass properly with
>>> bindep-fallback.txt, but perhaps we prime it with a bad package on purpose
>>> to
>>> force the issue. As clarkb points out, the downside to this it does make it
>>> harder for projects to be flipped to ubuntu-bionic. It is possible we could
>>> also prime gerrit patches for projects that are missing bindep.txt to help
>>> push
>>> this effort along.
>>>
>>> Thoughts?
>>>
>>> [1]
>>> http://git.openstack.org/cgit/openstack-infra/project-config/tree/nodepool/elements/bindep-fallback.txt
>>
>> This might break all stable branches as well. Pushing those changes in
>> is a huge effort ;( Is that worth it?
>>
> I wouldn't expect stable branches to be running bionic, unless I am missing
> something obvious.
How do you want to change the set up tox jobs, especially python27,
sphinx-docs, and python35?
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Stop supporting bindep-fallback.txt moving forward
On 2018-04-20 01:15, Paul Belanger wrote:
> Greetings,
>
> I'd like to propose we hard freeze changes to bindep-fallback.txt[1] and push
> projects to start using a local bindep.txt file.
>
> This would mean, moving forward with ubuntu-bionic, if a project was still
> depending on bindep-fallback.txt, their jobs may raise a syntax error.
>
> In fact, today ubuntu-bionic does seem to pass properly with
> bindep-fallback.txt, but perhaps we prime it with a bad package on purpose to
> force the issue. As clarkb points out, the downside to this it does make it
> harder for projects to be flipped to ubuntu-bionic. It is possible we could
> also prime gerrit patches for projects that are missing bindep.txt to help
> push
> this effort along.
>
> Thoughts?
>
> [1]
> http://git.openstack.org/cgit/openstack-infra/project-config/tree/nodepool/elements/bindep-fallback.txt
This might break all stable branches as well. Pushing those changes in
is a huge effort ;( Is that worth it?
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] devstack-plugin-vmax-core
On 2018-01-09 15:59, Okpoyo, Unana wrote:
> Hi there,
>
>
>
> I am trying to create a pike branch for the devstack-plugin-vmax plugin
> but am unable to create branches. Could I be given access to be able to
> do so?
Please sent a patch to update the ACL file, see
https://docs.openstack.org/infra/manual/creators.html#creation-of-branches
for details,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Is our testing of nodepool ok?
With the merge of Zuulv3 branch of nodepool, we need to rethink our
testing of nodepool.
We currently run on openstack-infra/glean and
openstack/diskimage-builder these jobs:
- legacy-dsvm-nodepool-redhat-src
- legacy-dsvm-nodepool-ubuntu-src
- legacy-dsvm-nodepool-opensuse-src
- legacy-dsvm-nodepool-debian-src (experimental)
The jobs check out nodepool and shade as well. Those are python 2 jobs
but isn't nodepool python 3 now? Also, nodepool has devstack file, is that
I just pushed https://review.openstack.org/#/c/536135/ to see whether
the jobs still work - only opensuse succeeded, rest failed but didn't
dig into those.
So, my question: Do we test the right thing with these jobs now that
nodepool v3 branch is merged or are changes needed for the setup? And
could somebody check why those two fail?
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Caching zanata-cli?
On 12/03/2017 11:14 PM, Ian Wienand wrote:
On 12/04/2017 09:54 AM, Andreas Jaeger wrote:
ERROR: Failure downloading
https://search.maven.org/remotecontent?filepath=org/zanata/zanata-cli/3.8.1/zanata-cli-3.8.1-dist.tar.gz,
HTTP Error 503: Service Unavailable: Back-end server is at capacity
Could we cache this, please? Any takers?
There are several ways we could do this
1. Stick it on tarballs.o.o -- which isn't local but may be more reliable
2. Actually mirror via AFS -- a bit of a pain to setup for one file
3. cache via reverse proxy -- possible
4. add to CI images -- easy to do and avoid remote failures.
So I've proposed 4 in [1] and we can discuss further...
-i
[1] https://review.openstack.org/525050
thanks a lot, Ian!
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Caching zanata-cli?
Looking at
http://logs.openstack.org/periodic/git.openstack.org/openstack/aodh/master/propose-translation-update/a2309f6/job-output.txt.gz#_2017-12-02_07_06_43_675230
I see
ERROR: Failure downloading
https://search.maven.org/remotecontent?filepath=org/zanata/zanata-cli/3.8.1/zanata-cli-3.8.1-dist.tar.gz,
HTTP Error 503: Service Unavailable: Back-end server is at capacity
Could we cache this, please? Any takers?
Sorry, without IRC right now...
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Helped needed with playbooks/translation/propose-translation-update.yaml
Looking at
http://logs.openstack.org/periodic/git.openstack.org/openstack/karbor/master/propose-translation-update/d6ffc5e/
, I see that the job failed.
The subunit file is generated - but not uploaded, see
http://logs.openstack.org/periodic/git.openstack.org/openstack/karbor/master/propose-translation-update/d6ffc5e/job-output.txt.gz
Could somebody fix the propose and upstream playbooks to always upload
the subunit file using fetch-translations-stestr-output , please?
thanks,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] npm Zuul jobs - need help
On 2017-11-13 19:47, Paul Belanger wrote:
> On Mon, Nov 13, 2017 at 07:39:08PM +0100, Andreas Jaeger wrote:
>> Hi team,
>>
>> let me summarize the current status and my request for help here.
>>
>> Note: with npm I mean the javascript node tests.
>>
>> I fixed last week the npm test, lint, and docs jobs and converted them
>> to native Zuul v3.
>>
>> But then we noticed the problem that horizon expects chromium and xvfb
>> installed and xvfb started for their tests.
>>
> Do you have an example log of the failure? Can't we use the test-setup role
> and add this into tools/test-setup.sh for now?
The linked bug contains a log
https://bugs.launchpad.net/horizon/+bug/1731421
I didn't look into using. Keep in mind that a few other repos using that
job would need it as well.
Btw. I was not happy that my change only works on Ubuntu and installs
xvfb/chromium using apt.
Andreas
>
>> This let to a reversal (change https://review.openstack.org/#/c/518881/
>> ) so that we continue to use the legacy npm-test job. Now the question
>> is how to fix this properly.
>>
>> Akihiro Motoki and myself proposed
>> https://review.openstack.org/#/c/518879/ and tested that it works in
>> horizon (https://review.openstack.org/518880). Is this the right
>> approach? Or is that so OpenStack specific that we need to move it to
>> openstack-zuul-jobs? I'm also not happy about some changes in there, so
>> would really appreciate if somebody could take this over and do it the
>> right way.
>>
>> A second problem is that the npm-docs automatic conversion was bogus. It
>> converted everything to use the sphinx build jobs. I fixed this with
>> https://review.openstack.org/#/c/518883 for the npm-docs template. Now
>> the missing piece is the publishing part of it - and then we need to
>> design templates for the publishing and review the usage of
>> publish-openstack-sphinx-docs for npm jobs. Have a look at
>> eslint-config-openstack in project-config/zuul.de/projects.yaml, it uses
>> the publish-openstack-sphinx-docs template which adds sphinx building
>> and publishing - we need instead a docs publishing one. I didn't check
>> how many repos have this broken set up.
>>
>> Could anybody tackle these two problems and take over, please? I'm happy
>> to review and learn - but don't have the energy this week to fix it myself,
>>
>> Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] npm Zuul jobs - need help
Hi team,
let me summarize the current status and my request for help here.
Note: with npm I mean the javascript node tests.
I fixed last week the npm test, lint, and docs jobs and converted them
to native Zuul v3.
But then we noticed the problem that horizon expects chromium and xvfb
installed and xvfb started for their tests.
This let to a reversal (change https://review.openstack.org/#/c/518881/
) so that we continue to use the legacy npm-test job. Now the question
is how to fix this properly.
Akihiro Motoki and myself proposed
https://review.openstack.org/#/c/518879/ and tested that it works in
horizon (https://review.openstack.org/518880). Is this the right
approach? Or is that so OpenStack specific that we need to move it to
openstack-zuul-jobs? I'm also not happy about some changes in there, so
would really appreciate if somebody could take this over and do it the
right way.
A second problem is that the npm-docs automatic conversion was bogus. It
converted everything to use the sphinx build jobs. I fixed this with
https://review.openstack.org/#/c/518883 for the npm-docs template. Now
the missing piece is the publishing part of it - and then we need to
design templates for the publishing and review the usage of
publish-openstack-sphinx-docs for npm jobs. Have a look at
eslint-config-openstack in project-config/zuul.de/projects.yaml, it uses
the publish-openstack-sphinx-docs template which adds sphinx building
and publishing - we need instead a docs publishing one. I didn't check
how many repos have this broken set up.
Could anybody tackle these two problems and take over, please? I'm happy
to review and learn - but don't have the energy this week to fix it myself,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Some guidance on job variants
On 2017-10-25 00:51, James E. Blair wrote:
> At the infra meeting today, we discussed how to handle job variants. I
> will try to summarize the discussion and extrapolate some things.
>
> The Zuul v3 migration doc in the infra manual is very clear that some
> project-templates should only be added in project-config, rather than
> in-repo[1].
>
> However, there are some edge cases worth considering:
>
> First: projects may want to alter the behavior of those jobs (e.g., to
> run unit tests on an older node type). In these cases projects should
> leave the template in project-config, and just alter the job by adding a
> project-pipeline variant in-repo.
>
> Theoretically, projects could use this to make their py27 jobs
> non-voting. That would be a TC policy violation, but this system is not
> designed to enforce that policy, only facilitate it.
>
> Second: projects may want to cause those jobs not to run in some
> circumstances.
>
> Zuul's configuration for job variants is additive. Any job variants
> which match a change will be cumulatively applied to the final job
> configuration before it runs. However, once any job or variant for a
> project-pipeline matches a change, that job will run. There is not a
> way to have one variant match a change, and then have a second also
> match it and somehow cause the job not to run. Variants which don't
> match the job simply don't add their own attributes to it.
>
> This means that if a project wants to alter the files or irrelevant
> files list for a job covered by one of those templates, or avoid running
> a job on a particular branch, there is no way to do that if the template
> is applied in project-config.
>
> In these cases, I think the following policy should apply:
>
> 1) If you can use the project-template as-is, then it should be applied
> to the project in project-config.
>
> 2) If you want to improve the files or irrelevant-files matchers on the
> template in such a way that they can apply safely to everyone using the
> template, please do so.
>
> 3) If your project needs a job variant that is incompatible with the
> template, then remove it from project-config and add the individual jobs
> to the project in-repo. The project is still responsible for adhering
> to the PTI.
>
> As you can see, these aren't hard and fast rules, this is more of an
> attempt to gain clarity and be able to make helpful and consistent
> suggestions to folks about how to configure jobs in certain ways.
I'm fine with this and suggest to update the infra manual with the
policy. Also, the explanation about job variants should be in the infra
manual,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Nominating new project-config and zuul job cores
On 2017-10-13 19:01, Jeremy Stanley wrote:
> On 2017-10-13 09:25:52 -0700 (-0700), Clark Boylan wrote:
>> I'd like to nominate a few people to be core on our job related
>> config repos.
> [...]
>
> Count me heartily in favor of all four mentioned additions. They've
> been doing excellent work.
Fully agreed! count me in for these 4,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [openstack-infra][collectd-ceilometer-plugin] renaming project repository
On 2017-08-29 12:23, Foley, Emma L wrote:
> Hi,
>
> Since Ceilometer support was removed from the collectd-ceilometer-plugin[1],
> the repo name is misleading.
> There are other plugins included in the repo, so it shouldn't be deleted,
> however it does need a rename.
>
> I intend to rename the repo to collectd-openstack-plugins.
>
> It looks like there are a number of steps involved in this[2][3], most of
> which I can do myself.
> I believe someone from the infra team will have to migrate the code to the
> new repo, correct?
Yes, as documented at :
https://docs.openstack.org/infra/manual/creators.html#project-renames
Please follow that complete section.
This needs a gerrit downtime and those are costly and will only done a
few times a year,
Andreas
> [1] https://review.openstack.org/#/c/490823/
> [2] https://wiki.openstack.org/wiki/Network/neutron-renaming
> [3] https://review.openstack.org/#/c/329247/7
>
> --
> Intel Research and Development Ireland Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
>
>
>
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Tag stable/mitaka as eol for Monasca Ceilometer
On 2017-08-05 04:25, Joshua Hesketh wrote:
> Howdy,
>
> I have eol'd the mitaka branch for monasca-ceilometer. Please let me
> know if you find any mistakes.
LGTM, thanks,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Tag stable/mitaka as eol for Monasca Ceilometer
On 2017-07-19 20:29, Ashwin Agate wrote:
> Hi,
>
> Can you please delete stable/mitaka branch for openstack/monasca-
> ceilometer project and create a mitaka-eol tag?
>
> Please see https://review.openstack.org/#/c/484494/6 for some
> discussion with Andreas Jaeger on this subject.
Roland, as PTL, can you confirm, please?
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Collected list of repos to retire
On 2017-07-18 14:19, Joshua Hesketh wrote:
> Hey,
>
> I've actioned all of these requests. Thanks again Andreas for putting
> together the list.
>
> The only exception was openstack/astara which had already had
> stable/mitaka retired.
>
> Let me know if there are any more. My apologies for not getting to these
> sooner.
>
Thanks, looks fine!
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Collected list of repos to retire
Here's an updated list - adding openstack-ansible as requested on
openstack-dev. Could an admin handle these, please?
Thanks,
Andreas
openstack/sahara-extra stable/icehousePlease retire
openstack/sahara-extra stable/mitaka Please retire
openstack/packstack stable/kiloPlease retire
openstack/packstack stable/liberty Please retire
openstack/packstack stable/mitaka Please retire
openstack/bareon-ironic stable/mitaka Please retire
openstack/rpm-packaging stable/mitaka Please retire
openstack/training-labs stable/mitaka Please retire
Not done in
https://gist.githubusercontent.com/tbreeds/c99e62bf8da19380e4eb130be8783be7/raw/6d02deb40e07516ce8fc529d2ba8c74af11a5a6b/mitaka_eol_data.txt
openstack/astara stable/mitaka Please retire
Special treatment:
openstack/openstack-ansible stable/mitaka (just delete branch, tag exists)
openstack/training-labs icehouse-eol (just delete branch, tag exists)
openstack/training-labs juno-eol (delete branch, create tag instead)
Note packstack has eol tags already created.
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] review.o.o slow, ask.o.o down
On 2017-07-12 08:44, Andreas Jaeger wrote:
> infra-roots,
>
> currently ask.o.o is down completely - and review.o.o is very slow and
> throws occasional 502s.
>
> Andreas
>
FYI:
Yolanda (thanks!) restarted review.o.o and ask.o.o is up again as well,
Andrea
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] review.o.o slow, ask.o.o down
infra-roots,
currently ask.o.o is down completely - and review.o.o is very slow and
throws occasional 502s.
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Collected list of repos to retire
On 2017-07-11 21:39, David Moreau Simard wrote:
> I don't want to sidetrack the thread but should someone also be taking
> care of cleaning up stale branches in Devstack ?
> It goes all the way back to kilo.
Can we do that without causing harm to projects that haven't eol-ed those?
Let's add QA PTL to chime in and tell us what to do,
Andreas
>
> David Moreau Simard
> Senior Software Engineer | Openstack RDO
>
> dmsimard = [irc, github, twitter]
>
>
> On Mon, Jul 10, 2017 at 11:05 AM, Andreas Jaeger <a...@suse.com> wrote:
>> infra admins, could somebody please retire the following branches from
>> repositories:
>>
>> openstack/sahara-extra stable/icehousePlease retire
>> openstack/sahara-extra stable/mitaka Please retire
>> openstack/packstack stable/kiloPlease retire
>> openstack/packstack stable/liberty Please retire
>> openstack/packstack stable/mitaka Please retire
>> openstack/bareon-ironic stable/mitaka Please retire
>> openstack/rpm-packaging stable/mitaka Please retire
>> openstack/training-labs stable/mitaka Please retire
>>
>> Not done in
>> https://gist.githubusercontent.com/tbreeds/c99e62bf8da19380e4eb130be8783be7/raw/6d02deb40e07516ce8fc529d2ba8c74af11a5a6b/mitaka_eol_data.txt
>>
>> openstack/astara stable/mitaka Please retire
>>
>>
>> Special treatment:
>> openstack/training-labs icehouse-eol (just delete branch, tag exists)
>> openstack/training-labs juno-eol (delete branch, create tag instead)
>>
>> Note that packstack has eol tags already created.
>>
>> thanks,
>> Andreas
>> --
>> Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>>GF: Felix Imendörffer, Jane Smithard, Graham Norton,
>>HRB 21284 (AG Nürnberg)
>> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
>>
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Collected list of repos to retire
infra admins, could somebody please retire the following branches from
repositories:
openstack/sahara-extra stable/icehousePlease retire
openstack/sahara-extra stable/mitaka Please retire
openstack/packstack stable/kiloPlease retire
openstack/packstack stable/liberty Please retire
openstack/packstack stable/mitaka Please retire
openstack/bareon-ironic stable/mitaka Please retire
openstack/rpm-packaging stable/mitaka Please retire
openstack/training-labs stable/mitaka Please retire
Not done in
https://gist.githubusercontent.com/tbreeds/c99e62bf8da19380e4eb130be8783be7/raw/6d02deb40e07516ce8fc529d2ba8c74af11a5a6b/mitaka_eol_data.txt
openstack/astara stable/mitaka Please retire
Special treatment:
openstack/training-labs icehouse-eol (just delete branch, tag exists)
openstack/training-labs juno-eol (delete branch, create tag instead)
Note that packstack has eol tags already created.
thanks,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Removing EOL branches from Packstack
On 2017-07-10 16:36, David Moreau Simard wrote:
> Hi -infra,
>
> We've tagged -eol for stable/kilo, stable/liberty as well as
> stable/mitaka for Packstack.
> We're a bit late! Sorry about that.
>
> The branches can be deleted now.
>
Thanks, adding to my list and now passing on,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Branch close requests for rpm-packaging and training-labs
This includes a request by Dirk Müller on IRC for rpm-packaging:
Please eol (close branch, push eol tag):
openstack/rpm-packaging stable/mitaka
openstack/training-labs stable/mitaka
openstack/training-labs icehouse-eol (just delete branch, tag exists)
openstack/training-labs juno-eol (delete branch, create tag instead)
Thanks,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] There is a problem while fallowing Project creator`s guide
On 2017-05-09 23:18, Jea-Min Lim wrote:
> There is a problem while fallowing Project creator`s guide
>
>
>
> Hi, I`m following Project creator`s guide to create own OpenStack
> related project.
>
> I have problem while following ‘Give OpenStack Permission to Publish
> Releases’ section(URL:
> https://docs.openstack.org/infra/manual/creators.html#give-openstack-permission-to-publish-releases
> <https://docs.openstack.org/infra/manual/creators.html#give-openstack-permission-to-publish-releases>).
>
>
>
> This doc says ‘Once you have PyPI credentials
> visit https://pypi.python.org/pypi?%3Aaction=submit_form
> <https://pypi.python.org/pypi?%3Aaction=submit_form> and fill in only
> the required fields.’
>
>
>
> But I can`t see ‘the required fields.'
>
>
>
> When I click the link
> (https://pypi.python.org/pypi?%3Aaction=submit_form
> <https://pypi.python.org/pypi?%3Aaction=submit_form>) It shows
>
>
>
> 1. Use twine!
>
> 2. Use the setup.py "register" command.
>
> 3. Or upload your PKG-INFO file (generated by distutils) here:
>
>
>
> Am I doing right? or did I miss something?
See:
https://review.openstack.org/#/c/461498/
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Boston 2017 Summit dinner
On 2017-04-29 08:29, Yolanda Robla Mota wrote:
> Unfortunately I won't be coming to the summit this time... Enjoy!
I won't be there either.
Have a great summit,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Problem with OpenStack bot? Vitrage meeting was not recorded
On 2017-04-19 11:07, Afek, Ifat (Nokia - IL/Kfar Sava) wrote:
> Hi,
>
> Vitrage IRC meeting that was held an hour ago on openstack-meeting-4, but was
> not recorded.
> #startmeeting worked, but no other # command worked and the meeting was not
> ended. The full meeting log can be found here:
> http://eavesdrop.openstack.org/irclogs/%23openstack-meeting-4/%23openstack-meeting-4.2017-04-19.log.html
>
>
> Can you please help?
I see it at
http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-04-19-08.03.log.txt
- but no other files like html are generated,
I see quite a few non-ascii characters, did one of them break our html
generation?
Andreas
> Is it possible to copy the meeting content under
> http://eavesdrop.openstack.org/meetings/vitrage/2017/ ?
>
> Thanks,
> Ifat.
>
>
>
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Dell Ironic CI broken
Dell Ironic CI is reporting on unrelated changes like
https://review.openstack.org/449385 - project-config
https://review.openstack.org/#/c/450088/ - trove
It reports in both cases:
"Merge Failed.
This change or one of its cross-repo dependencies was unable to be
automatically merged with the current state of its repository. Please
rebase the change and upload a new patchset."
Please disable our CI immediately - and fix it and test on the
sandbox-ci repo,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Broken zh_TW translations for monasa-ui
See
http://logs.openstack.org/periodic/monasca-ui-propose-translation-update/147e4e4/console.html#_2017-03-16_08_07_24_539792
:
2017-03-16 08:07:24.539792 | ++ msgfmt --statistics -o /dev/null
monitoring/locale/zh_TW/LC_MESSAGES/django.po
2017-03-16 08:07:24.544961 | +
trans='monitoring/locale/zh_TW/LC_MESSAGES/django.po:257: '\''msgid'\''
and '\''msgstr'\'' entries do not both begin with '\''\n'\''
2017-03-16 08:07:24.545011 | msgfmt: found 1 fatal error
2017-03-16 08:07:24.545041 | 48 translated messages, 101 untranslated
messages.'
Could anybody help, please?
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [zuul] Feedback requested for tox job definition
Thanks, Paul.
For me both have their strength and weaknesses:
* If you want to add a new tox job for an existing target like pep8, I
like how simple that is with
https://review.openstack.org/#/c/438281/25/.zuul.yaml
* On the other hand, if you add a new tox job - for a completely new
target, then https://review.openstack.org/#/c/442180/3/.zuul.yaml allows
me to add the job in a single place instead of adding another file like
https://review.openstack.org/#/c/438281/25/playbooks/tox-cover.yaml.
Knowing that most projects do not add their own non-standard jobs, the
more compact setting like 438281 wins for me - and the other way is not
too difficult either.
So, I'm fine with either solution and have a slight preference to 438281.
I fear only time will tell, whether there's really a significant
difference ;)
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] debugging post jobs
On 2017-01-26 08:24, Tom Fifield wrote:
> Hi infra,
>
> I'm debugging a sphinx document change
> (https://review.openstack.org/#/c/424706/ ) that uses a static-*-publish
> job (jenkins/jobs/static-publish-jobs.yaml) in the post pipeline.
>
> I can see the gate passing just fine
> (http://docs-draft.openstack.org/06/424706/2/gate/gate-governance-uc-docs-ubuntu-xenial/c00670c//doc/build/html/
> ), and the change has merged into the repository successfully. However,
> the target site isn't updated after >24 hours.
>
> That indicates to me that the the static-*-publish post job has failed,
> but I'm not sure where to look to find the logs for that. Any hints?
http://docs.openstack.org/infra/manual/developers.html#automated-testing
explains that in the step 1.
BUT:
Yesterday some CI systems needed a restart due to problems caused by one
provider AFAIK and that lost the post queue. So, this might not have run
at all.
If that change is critical, just push a new one up,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] docs.openstack.com excessive INODE consumption
Tony,
we've just disabled publishing to docs.openstack.org.
Tomorrow you can take both developer.openstack.org and
docs.openstack.org sites out of service. Is there anything else that
needs to be done from OpenStack Infra site for this?
Thanks a lot for the service!
Andreas
On 2017-01-10 20:45, Andreas Jaeger wrote:
> Tony,
>
> we've brought up a replacement for docs.openstack.org and
> developer.openstack.org and are in the final steps of switching over
> docs.openstack.org.
>
> Current state is:
> 1) We have switched over the much smaller developer.o.o site and this
> works fine.
>
> 2) Later today, we're switching over the DNS entry of docs.o.o to the
> new site.
> Since this has much more content, we will closely monitor the new server
> and need the old server in case we need to go back to it to fix any
> immediate problems.
>
> Once the new docs.o.o works fine, we can decommission our useage of the
> Cloud Sites servers for docs.o.o and developer.o.o. We hope that we can
> start the decommission phase next week - and somebody from the infra
> team will send an email once we're done,
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [OpenStack-docs] docs.o.o looks great - doesn't it?
On 2017-01-13 20:15, Andreas Jaeger wrote:
> AFAIK everything looks fine with the new docs.o.o site, the server
> handle the workload and the few missing documents have been manually
> copied over.
>
> Thanks for everybody involved with this - thanks to the OpenStack infra
> team for taking over docs.o.o and developer.o.o! Jim did the development
> part, and others helped with the manual steps and reviewed. Thanks
> especially to Jim, Jeremy, Paul, Ian, Yolanda, Anne!
>
> Next steps are stopping publishing of content to the old Cloud Sites
> server [1], marking the spec as implemented [2], and getting https on
> the two sites (Jeremy will do that soon).
>
> We decided in the last infra meeting to evaluate the status again next
> Tuesday and I'll remove the WIP from [1] after the meeting.
>
> Still, if you notice any problems, please speak up,
>
> Andreas
>
> [1] https://review.openstack.org/420135
> [2] https://review.openstack.org/420138
>
No news is good news - I propose to move forward in today's infra meeting,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] docs.o.o looks great - doesn't it?
AFAIK everything looks fine with the new docs.o.o site, the server
handle the workload and the few missing documents have been manually
copied over.
Thanks for everybody involved with this - thanks to the OpenStack infra
team for taking over docs.o.o and developer.o.o! Jim did the development
part, and others helped with the manual steps and reviewed. Thanks
especially to Jim, Jeremy, Paul, Ian, Yolanda, Anne!
Next steps are stopping publishing of content to the old Cloud Sites
server [1], marking the spec as implemented [2], and getting https on
the two sites (Jeremy will do that soon).
We decided in the last infra meeting to evaluate the status again next
Tuesday and I'll remove the WIP from [1] after the meeting.
Still, if you notice any problems, please speak up,
Andreas
[1] https://review.openstack.org/420135
[2] https://review.openstack.org/420138
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server
My spider I found a few directories that were completely missing and
we'll migrate those over later today manually. Once that's done I rerun
the spider and send the result here so that people can fix documents or
file bugs.
I also fixed a few broken links myself.
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server
On 2017-01-03 20:43, Andreas Jaeger wrote:
> we discussed in today's infra meeting to move forward as follows:
>
> 1) update some missing content since a few projects haven't published
>content since we started:
>http://users.suse.com/~aj/missing-docs.tar.bz2 is a copy from
>docs.o.o that needs to be added to our AFS tree.
>
> 2) Merge https://review.openstack.org/400887 to release afs volumes
>and create read-only volumes (jeblair)
>
> 3) Change IP address of docs.openstack.org to point to the new site.
>
> 4) Update 404 handler to not point to archived site anymore
>
> 5) Update archived content so that we can still access any
>content that wasn't published recently:
>a) Resync the mirror at http://files.openstack.org/docs-old/
>
> 6) Check that all links on docs.o.o work correctly
>
> infra-root volunteers for some steps are still needed, this will be
> discussed on #openstack-infra later this week,
Paul just changed DNS, so docs.openstack.org is pointing to the new site.
In case of any problems, please report them as reply to this email or
directly on #openstack-infra.
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] docs.openstack.com excessive INODE consumption
Tony,
we've brought up a replacement for docs.openstack.org and
developer.openstack.org and are in the final steps of switching over
docs.openstack.org.
Current state is:
1) We have switched over the much smaller developer.o.o site and this
works fine.
2) Later today, we're switching over the DNS entry of docs.o.o to the
new site.
Since this has much more content, we will closely monitor the new server
and need the old server in case we need to go back to it to fix any
immediate problems.
Once the new docs.o.o works fine, we can decommission our useage of the
Cloud Sites servers for docs.o.o and developer.o.o. We hope that we can
start the decommission phase next week - and somebody from the infra
team will send an email once we're done,
Andreas
> [...]
> I wanted to bring to your attention a ticket recently created for
> docs.openstack.com and in regards to the large amount of files its
> consuming in the Cloud Sites environment. In the ticket
> 160812-dfw-0001549 there are more details in regards to the issue.
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server
we discussed in today's infra meeting to move forward as follows:
1) update some missing content since a few projects haven't published
content since we started:
http://users.suse.com/~aj/missing-docs.tar.bz2 is a copy from
docs.o.o that needs to be added to our AFS tree.
2) Merge https://review.openstack.org/400887 to release afs volumes
and create read-only volumes (jeblair)
3) Change IP address of docs.openstack.org to point to the new site.
4) Update 404 handler to not point to archived site anymore
5) Update archived content so that we can still access any
content that wasn't published recently:
a) Resync the mirror at http://files.openstack.org/docs-old/
6) Check that all links on docs.o.o work correctly
infra-root volunteers for some steps are still needed, this will be
discussed on #openstack-infra later this week,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server
On 01/03/2017 03:57 PM, Andreas Jaeger wrote:
> On 01/03/2017 03:43 PM, Jeremy Stanley wrote:
>> On 2017-01-03 08:01:42 +0100 (+0100), Andreas Jaeger wrote:
>> [...]
>>> 3) Create docs-archived content so that we can still access any
>>>content that wasn't published recently:
>>>a) Resync the mirror at http://files.openstack.org/docs-old/
>>>b) Serve the content via docs-archived.openstack.org (see
>>> https://review.openstack.org/416148 )
>>>c) Add external IP address
>>>c) Update 404 handler to point to docs-archived.
>> [...]
>>
>> I'm a little unclear on what step "c" is supposed to be there... all
>> our servers already have "external" (globally routable) IP
>> addresses.
>
> Add docs-archived.openstack.org DNS entry.
>
>> As for step "d" that could presumably get confusing if someone
>> requests a page that doesn't exist at either site, since they'll get
>> an error about a missing page at docs-archive.o.o instead of
>> docs.o.o (maybe that's fine, I don't have much insight into reader
>> expectations). Is the longer-term plan to review analytics for page
>> hits against docs-archive to figure out what else should be copied
>> over to docs.o.o manually, or incorporated/reintroduced into
>> documentation builds?
>
> Have a look what happens currently:
> http://docs-beta.openstack.org/bla
>
> Yes, it could be confusing. The idea was to wait for bug reports - and I
> don't really expect any since all links should work (I run a spider on
> docs-beta).
>
> We will not add anything again in documentation builds, this is really
> historic data,
We just discussed this in the infra meeting and since we can rebuild old
documentation if really needed manually (which might be tricky since it
needs older tools and maybe older packages/distro), we do not need
docs-archived. We have all the content on files.openstack.org/docs-old
and can access it there - via anonymous AFS or http,
new plan coming in a minute,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server
On 01/03/2017 03:43 PM, Jeremy Stanley wrote:
> On 2017-01-03 08:01:42 +0100 (+0100), Andreas Jaeger wrote:
> [...]
>> 3) Create docs-archived content so that we can still access any
>>content that wasn't published recently:
>>a) Resync the mirror at http://files.openstack.org/docs-old/
>>b) Serve the content via docs-archived.openstack.org (see
>> https://review.openstack.org/416148 )
>>c) Add external IP address
>>c) Update 404 handler to point to docs-archived.
> [...]
>
> I'm a little unclear on what step "c" is supposed to be there... all
> our servers already have "external" (globally routable) IP
> addresses.
Add docs-archived.openstack.org DNS entry.
> As for step "d" that could presumably get confusing if someone
> requests a page that doesn't exist at either site, since they'll get
> an error about a missing page at docs-archive.o.o instead of
> docs.o.o (maybe that's fine, I don't have much insight into reader
> expectations). Is the longer-term plan to review analytics for page
> hits against docs-archive to figure out what else should be copied
> over to docs.o.o manually, or incorporated/reintroduced into
> documentation builds?
Have a look what happens currently:
http://docs-beta.openstack.org/bla
Yes, it could be confusing. The idea was to wait for bug reports - and I
don't really expect any since all links should work (I run a spider on
docs-beta).
We will not add anything again in documentation builds, this is really
historic data,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server
On 01/02/2017 08:22 PM, Andreas Jaeger wrote:
> [...]
> I've put this topic on the agenda for tomorrow's infra team meeting,
> https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting . Docs team
> members are welcome to join!
In preparation for the meeting, I've updated the plan:
The following needs to be done:
1) update some missing content since a few projects haven't published
content since we started:
http://users.suse.com/~aj/missing-docs.tar.bz2 is a copy from
docs.o.o that needs to be added to our AFS tree.
2) Change IP address of docs.openstack.org to point to the new site.
3) Create docs-archived content so that we can still access any
content that wasn't published recently:
a) Resync the mirror at http://files.openstack.org/docs-old/
b) Serve the content via docs-archived.openstack.org (see
https://review.openstack.org/416148 )
c) Add external IP address
c) Update 404 handler to point to docs-archived.
Later (most can be done independently, so not using numbers):
A) Set up https for docs.openstack.org and developer.openstack.org
B) Stop publishing to CloudDocs site docs-archived but keep site as
is.
Archive all content on it.
Remove docs-archived.openstack.org
C) Stop publishing to old CloudDocs developer.openstack.org page (
https://review.openstack.org/415506 )
D) Remove docs-beta and developer-beta aliases and IP addresses, those
are not needed anymore. (https://review.openstack.org/416149,
https://review.openstack.org/416152)
Note, see our etherpad here as well:
https://etherpad.openstack.org/p/afs-docs
and spec:
http://specs.openstack.org/openstack-infra/infra-specs/specs/doc-publishing.html
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server
On 01/02/2017 07:07 PM, Jeremy Stanley wrote:
> On 2016-12-28 19:09:04 +0100 (+0100), Andreas Jaeger wrote:
> [...]
>> 3) Create docs-archived.openstack.org pointing to the old CloudDocs
>>docs site so that we can still access any content that wasn't
>>published recently. Update 404 handler to point to docs-archived.
> [...]
>
> I don't think this is technically possible with CloudSites, as each
> domain name seems (last time I tried when api.o.o got renamed to
> developer.o.o) to require creating a separate site with its own
> content. I tried to check now to see whether they have a rename
> option at least, but the old credentials I have on record for the
> CloudSites admin portal seem to no longer work and instead claim we
> aren't signed up for the service (maybe I'm trying the wrong account
> and some other Infra sysadmin has the correct credentials on hand?).
>
> What we _can_ do is just not delete it immediately, and then you can
> temporarily override /etc/hosts locally to associate docs.o.o with
> 98.129.229.216 if you need to access it. Also keep in mind though
> that Rackspace is eager to see us delete the content for those sites
> because they're extremely large (at least by their standards), so
> the sooner we can remove them entirely the better.
Looking at previous plans, we have already mirrored once (need to
refresh) http://files.openstack.org/docs-old/, so we can replace that
step with:
a) Resync the mirror
b) Serve the content via docs-archived.openstack.org
I've put this topic on the agenda for tomorrow's infra team meeting,
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting . Docs team
members are welcome to join!
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [OpenStack-docs] [infra][docs] Steps to migrate docs.o.o to new AFS based server
On 12/29/2016 02:29 PM, Anne Gentle wrote:
>
>
> On Wed, Dec 28, 2016 at 12:09 PM, Andreas Jaeger <a...@suse.com
> <mailto:a...@suse.com>> wrote:
>
> [cross-posting to both infra and docs mailing lists]
>
> We're running since several weeks developer.openstack.org
> <http://developer.openstack.org> using the
> OpenStack Infra server and I reviewed what is needed to make the final
> switch. An analysis of missing pages showed that only 4 repos have not
> been published (step 1 below), we need to copy those over.
>
> Once that is done, we can do the switch
>
>
> The following steps need to be done:
>
> 1) update some missing content since a few projects haven't published
>content since we started:
>http://users.suse.com/~aj/missing-docs.tar.bz2
> <http://users.suse.com/~aj/missing-docs.tar.bz2> is a copy from
>docs.o.o that needs to be added to our AFS tree.
>
>
> I looked at the files and seems fine. The project names are: pylockfile,
> python-aodhclient, python-barbicanclient, python-cinderclient, and
> python-manilaclient.
>
>
>
> 2) Change IP address of docs.openstack.org
> <http://docs.openstack.org> to point to the new site.
>
> 3) Create docs-archived.openstack.org
> <http://docs-archived.openstack.org> pointing to the old CloudDocs
>docs site so that we can still access any content that wasn't
>published recently. Update 404 handler to point to docs-archived.
>
>
> This is one step where I'm not sure how it works - but if you know what
> to do it's all good.
Step 3 needs probably login to the CloudSites admin interface - no idea
how that works.
> Do we need to do any notification step to Cloud Sites through a ticket
> to let them know the traffic will change? Might be good to let them know
> proactively.
No idea ;(
they were more concerned with the size of our site (number of files) in
the past.
>
> Later (most can be done independently, so not using numbers), we
> should do:
>
> A) Set up https for docs.openstack.org <http://docs.openstack.org>
> and developer.openstack.org <http://developer.openstack.org>
>
>
>
> B) Stop publishing to CloudDocs site docs-archived but keep site as
>is.
>Archive all content on it.
>
>
> Let me know if you need help with this step - not sure how this is done
> but you can tell me and I'll do the work. :)
This should be similar to 415506 below.
>
>
>Remove docs-archived.openstack.org
> <http://docs-archived.openstack.org>
>
> C) Stop publishing to old CloudDocs developer.openstack.org
> <http://developer.openstack.org> page (
>https://review.openstack.org/415506
> <https://review.openstack.org/415506> )
>
> D) Remove docs-beta and developer-beta aliases and IP addresses, those
>are not needed anymore.
>
> Is anything missing?
>
>
> When the change happens we should probably check the analytics the next
> day to ensure collection is still happening smoothly. Might not be a
> step exactly but it's B.1 and C.1 I suppose.
Yeah, we should keep our eyes open.
>
>
> Otherwise, let's move forward once an infra admin has time. Since we
> continue publishing to both sites for a time, we can always migrate back
> if needed. Infra team, please go ahead if there's no veto - but let's
> not do it this year anymore;)
>
>
> Good thinking and planning! Thanks a bunch.
> Anne
thanks,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] [infra][docs] Steps to migrate docs.o.o to new AFS based server
[cross-posting to both infra and docs mailing lists]
We're running since several weeks developer.openstack.org using the
OpenStack Infra server and I reviewed what is needed to make the final
switch. An analysis of missing pages showed that only 4 repos have not
been published (step 1 below), we need to copy those over.
Once that is done, we can do the switch
The following steps need to be done:
1) update some missing content since a few projects haven't published
content since we started:
http://users.suse.com/~aj/missing-docs.tar.bz2 is a copy from
docs.o.o that needs to be added to our AFS tree.
2) Change IP address of docs.openstack.org to point to the new site.
3) Create docs-archived.openstack.org pointing to the old CloudDocs
docs site so that we can still access any content that wasn't
published recently. Update 404 handler to point to docs-archived.
Later (most can be done independently, so not using numbers), we should do:
A) Set up https for docs.openstack.org and developer.openstack.org
B) Stop publishing to CloudDocs site docs-archived but keep site as
is.
Archive all content on it.
Remove docs-archived.openstack.org
C) Stop publishing to old CloudDocs developer.openstack.org page (
https://review.openstack.org/415506 )
D) Remove docs-beta and developer-beta aliases and IP addresses, those
are not needed anymore.
Is anything missing?
Otherwise, let's move forward once an infra admin has time. Since we
continue publishing to both sites for a time, we can always migrate back
if needed. Infra team, please go ahead if there's no veto - but let's
not do it this year anymore;)
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] ostestr_compat_shim.sh permission denied
On 2016-11-30 23:07, Henry Fourie wrote:
> Help appreciated on periodic-networking-sfc-py35-with-neutron-lib-master
> failure:
>
>
>
> http://logs.openstack.org/periodic/periodic-networking-sfc-py35-with-neutron-lib-master/b911fa2/
>
>
>
>
>
> py35-neutron-lib-master runtests: commands[0] |
> /home/jenkins/workspace/periodic-networking-sfc-py35-with-neutron-lib-master/tools/ostestr_compat_shim.sh
>
> 2016-11-30 06:05:54.237354
> <http://logs.openstack.org/periodic/periodic-networking-sfc-py35-with-neutron-lib-master/b911fa2/console.html#_2016-11-30_06_05_54_237354>|
> ERROR: invocation failed (errno 13), args:
> ['/home/jenkins/workspace/periodic-networking-sfc-py35-with-neutron-lib-master/tools/ostestr_compat_shim.sh'],
> [...]
> 2016-11-30 06:05:54.239932
> <http://logs.openstack.org/periodic/periodic-networking-sfc-py35-with-neutron-lib-master/b911fa2/console.html#_2016-11-30_06_05_54_239932>|
> OSError: [Errno 13] Permission denied
No execute permissions on the file I expect - see
https://review.openstack.org/405140
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Implementation OpenStack
On 2016-11-30 09:57, Björn Stübe wrote:
> Hey Community,
>
> I want to implement an OpenStack infrastructure to make a security audit
> for study purposes. The environment should be close to a productive
> environment. In my university, I'm able to use an server with Windows
> Server 2012 and Hyper-V installed. Is this a hardware environment which
> is usable for me? Do you have other tipps to implement such an
> environment for my purposes?
Bjoern,
best ask on the general openstack mailing list.
This openstack-infra mailing list covers the project infrastructure - to
support OpenStack community - but has nothing to do with how you run
your own,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Gerrit GUI Follow-up button
On 2016-11-28 16:16, Jeremy Stanley wrote:
> On 2016-11-26 18:34:55 + (+), Henry Fourie wrote:
>> There is a description on usage of the Gerrit Web UI Follow-up
>> button.
> [...]
>> Is there a link to this from current openstack review docs, or
>> is there other documentation?
> [...]
>
> https://review.openstack.org/Documentation/user-inline-edit.html
>
> While logged in I can see the Follow-Up button (right after Cherry
> Pick, Rebase and Abandon buttons on an open change) and the Create
> Change button (on the General page for a project), but these may be
> controlled by an ACL and so only visible for me as a member of the
> Administrators group. I take it they're not visible for you?
>
The button is also there for me - and I'm not a gerrit admin,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Initial member for os-xenapi-release
On 2016-11-24 02:44, Bob Ball wrote:
> Hi,
>
> Please could the initial member or owner for os-xenapi-release be set to
> os-xenapi-core so we can modify the members of the group.
>
> Link to group: https://review.openstack.org/#/admin/groups/1650,members
> Review that created group: https://review.openstack.org/#/c/400153/
>
The idea of a release group is to have a smaller subset than the core
group. So, I suggest to set it to just you and you can add additional
members.
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Subject: Re: [openstack-manuals] Create a stable/newton branch for openstack-manuals
On 11/11/2016 12:41 PM, Olena Logvinova wrote:
Thanks Clark!
The HEAD git ref is fine.
FYI, Clark just did this - thanks!
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [openstack-manuals] Create a stable/newton branch for openstack-manuals
On 11/10/2016 11:31 AM, Clark Boylan wrote:
On Thu, Nov 10, 2016, at 04:17 AM, Olena Logvinova wrote:
Hi Infra team!
We need a stable/newton branch to be created for the openstack-manuals
repo, please. The date announced in the mailing list is November, 11
(tomorrow).
Who would be able to do that?
The release team has been handling release related branch management for
projects. If they are unable to do this for you the infra team as Gerrit
admins can sort it out as well.
openstack-manuals has no tags and is not handled by release team - and I
asked the release team in one session in Barcelona about it.
So, it needs an infra-root to do it again, please
thanks,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [OpenStack-I18n] What happens in openstack-manual on Zanata?
On 09/20/2016 09:04 AM, Ian Y. Choi wrote:
It seems that it came from one Andreas's patch
:
http://git.openstack.org/cgit/openstack-infra/project-config/commit/jenkins/scripts?id=1c5f830a40acdd7f9ff666f0154daedcb9f3bdeb
Please see
https://review.openstack.org/#/c/216988/1/jenkins/scripts/common_translation_update.sh
So IMO the previous line #170-175 should be reverted.
Since I am now focusing another thing, it would be much better if
someone fixes :)
Or I will able to manage it after about 7-8 hours later.
Sorry, I broke it.
Fixed hopefully with: https://review.openstack.org/373020
Andreas
With many thanks,
/Ian
Akihiro Motoki wrote on 9/20/2016 3:48 PM:
Hi,
I see many many 'common' in openstack-manual project on Zanata?
https://translate.openstack.org/iteration/view/openstack-manuals/master/documents
'common' in openstack-manuals are linked into individual guides and
they are uploaded by accident.
Is there any change around upstream_translation_update.sh ?
Akihiro
___
OpenStack-I18n mailing list
openstack-i...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] docs.openstack.com excessive INODE consumption
On 08/27/2016 04:59 PM, Tyler Coil wrote:
> Hello Openstack team,
>
>
> I wanted to bring to your attention a ticket recently created for
> docs.openstack.com and in regards to the large amount of files its
> consuming in the Cloud Sites environment. In the
> ticket 160812-dfw-0001549 there are more details in regards to the issue.
>
>
> However, as a brief summary, while auditing our environment the site
> docs.openstack.org came to our attention. At the time of ticket creation
> the site docs.openstack.com was consuming ~594,000 files, since then it
> appears the site has grown to ~605,000 consumed files. This has made
> docs.openstack.com grow to be one of the largest inode consuming sites
> in Cloud Sites. Generally we recommend no single site have over 100,000
> files alone as inodes are a finite resource in the Cloud Sites environment.
I've removed some old content to give all of us some breathing space ;)
Should be more than 50k inodes less now.
Note that the upcoming newton release will add new content again,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Gerritbot can only handle 120 channels but found 121.
On 2016-08-29 14:38, Arie Bregman wrote:
> On Fri, Jun 24, 2016 at 9:00 PM, Andreas Jaeger <a...@suse.com> wrote:
>> On 06/24/2016 03:24 PM, BIN HU wrote:
>>>
>>> Hello,
>>>
>>> I submitted patch for creating a new project "openstack/gluon":
>>> https://review.openstack.org/#/c/333843/
>>>
>>> There is a build error: Gerritbot can only handle 120 channels but found
>>> 121.
>>>
>>> http://logs.openstack.org/43/333843/3/check/gate-project-config-irc-access/1ec2b49/console.html
>>>
>>> Looks like it cannot handle my IRC channel "#openstack-gluon" that I added
>>> in "accessbot/channels.yaml" and "gerritbot/channels.yaml" even if the
>>> access is ok "INFO:checkaccess:openstackinfra access ok on #openstack-gluon"
>>>
>>> Can you help fix it by lifting the limit from 120 to 121? Or how can I fix
>>> it?
>>
>>
>> As mentioend on IRC: This is a hard limit that we cannot change. For now,
>> you just cannot use gerritbot - until somebody volunteers to set up a second
>> bot,
>
> Can you share more details on why this hard limit exists and why it
> can't be changed?
It's a limit by freenode, our IRC network. We've already contacted the
freenode admins and they could not help us,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Unable to add contact information to Gerrit
On 08/01/2016 02:50 PM, Dmitry Dmitriev wrote:
> Hello Infra,
>
> When I try to send my code to review.opwnstack.org I get an error:
>
> $ git review
> fatal: ICLA contributor agreement requires current contact information.
>
> Please review your contact information:
>
> https://review.openstack.org/#/settings/contact
>
>
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> $
>
> If I open the link and try to enter my contact information I see “Server
> error” from Gerrit.
>
> Can you please fix it?
You have to fix it yourself, follow the instructions completely:
This needs your gerrit preferred e-mail address to match a primary
e-mail address for a foundation individual member account.
If you already followed the instructions at
http://docs.openstack.org/infra/manual/developers.html#account-setup
exactly - so no shortcuts - and still get that, see
https://ask.openstack.org/question/56720 for
additional troubleshooting tips.
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Seek help on how to update Contact Information
On 2016-07-14 15:28, vtran wrote:
> Hi,
>
> I'm looking for help . The command "git review" gives me the
> following error:
>
>
> fatal: ICLA contributor agreement requires current contact information.
>
> Please review your contact information:
>
> https://review.openstack.org/#/settings/contact
>
>
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
>
> In my understanding, I need to update the section "Contact Information"
> in page https://review.openstack.org/#/settings/contact. However i got
> the following error:
>
> Code Review - Error
> Server Error
> Cannot store contact information
>
> I think I have filled out all other info in https://review.openstack.or
> g/#/settings/contact.
>
> Could you please point me to what I should do to get pass this issue?
This needs your gerrit preferred e-mail address to match a primary
e-mail address for a foundation individual member account.
If you already followed *all* the instructions at
http://docs.openstack.org/infra/manual/developers.html#account-setup
and still get that, see https://ask.openstack.org/question/56720 for
additional troubleshooting tips,
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Barcelona summit talk ideas
On 07/08/2016 01:46 AM, Elizabeth K. Joseph wrote:
> On Tue, Jun 14, 2016 at 7:07 AM, Paul Belanger <pabelan...@redhat.com> wrote:
>> Greetings,
>>
>> I wanted to start another etherpad[1] for collaboration on summit talk ideas
>> related to openstack-infra. I think it worked well for Austin and see no
>> reason
>> not to do it again.
>>
>> I've already outlined a few ideas of what interests me (and hopefully
>> others),
>> please take a moment to review and add your own ideas.
>>
>> We have until July 13 to submit talks[2]:
>>
>> JULY 13, 2016 AT 11:59PM PDT (JULY 14 6:59 UTC) IS THE DEADLINE TO SUBMIT A
>> TALK.
>>
>> [1] https://etherpad.openstack.org/p/barcelona-upstream-openstack-infa
>> [2] https://www.openstack.org/summit-login/login
>
> Talks seem to be coming together, which is good since the deadline is
> less than a week away :)
>
> We have a lightning talks section of the Etherpad. In case anyone
> missed it, thingee mentioned at our meeting this week and has sent an
> email about how to participate in the upstream lightning talks he's
> hosting again
> (http://lists.openstack.org/pipermail/openstack-dev/2016-July/098945.html)
> so we probably want to firm up our talk plans for that too.
do we collect ideas - or answer directly to thingee and let him choose?
I put one idea up on the etherpad now,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Gerritbot can only handle 120 channels but found 121.
On 06/24/2016 03:24 PM, BIN HU wrote:
Hello,
I submitted patch for creating a new project "openstack/gluon":
https://review.openstack.org/#/c/333843/
There is a build error: Gerritbot can only handle 120 channels but found 121.
http://logs.openstack.org/43/333843/3/check/gate-project-config-irc-access/1ec2b49/console.html
Looks like it cannot handle my IRC channel "#openstack-gluon" that I added in
"accessbot/channels.yaml" and "gerritbot/channels.yaml" even if the access is ok
"INFO:checkaccess:openstackinfra access ok on #openstack-gluon"
Can you help fix it by lifting the limit from 120 to 121? Or how can I fix it?
As mentioend on IRC: This is a hard limit that we cannot change. For
now, you just cannot use gerritbot - until somebody volunteers to set up
a second bot,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [Infra] Job failure notifications
On 06/16/2016 05:31 PM, Ivan Kolodyazhny wrote:
> Hi team,
>
> Is any way to subscribe to notifications to any failure on gate job? I'm
> maintainer of gate-tempest-dsvm-full-bdd-nv job in Cinder and would
> like to know when it is failed.
Use the OpenStack health to see yourself, for example:
http://status.openstack.org/openstack-health/#/g/build_queue/post?groupKey=build_queue=translation
There's only a mailing list for periodic jobs, no generic one,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Request help for ICLA error
On 06/15/2016 12:58 PM, Soffie Huang wrote:
> Hello Infra Team,
>
> I am trying to push the code changes for sanbox. But while initiating the
> review I am getting the following Error.
>
> ---
> fatal: ICLA contributor agreement requires current contact information.
> Please review your contact information:
> https://review.openstack.org/#/settings/contact
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> -
>
>
> I have signed the ICLA by providing my email address and also I tried to
> update my contact details at the link given above. While updating the
> details I am getting server error.
>
> Could you help me with this issue?
It needs your gerrit preferred e-mail address to match a primary
e-mail address for a foundation individual member account.
If you already followed the instructions at
http://docs.openstack.org/infra/manual/developers.html#account-setup
and still get that, see https://ask.openstack.org/question/56720 for
additional troubleshooting tips,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Error with 'git review'
On 06/15/2016 12:21 PM, zhaolihuisky wrote:
> Hi, all
>
> I commit the code using 'git review' command, but error happened.
>
> """
> $ git review
> fatal: remote error:
> ICLA contributor agreement requires current contact information.
>
> Please review your contact information:
>
> https://review.openstack.org/#/settings/contact
> """
>
> Then visit https://review.openstack.org/#/settings/contact
> and add my mailing address, country, phone number, fax number,
> but error:
>
> """
> "Code Review - Error
> Server Error
> Cannot store contact information"
> """
>
> Is there any suggestion?
It needs your gerrit preferred e-mail address to match a primary
e-mail address for a foundation individual member account.
If you already followed the instructions at
http://docs.openstack.org/infra/manual/developers.html#account-setup
and still get that, see https://ask.openstack.org/question/56720 for
additional troubleshooting tips,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Retire stable/kilo of openstack-manuals
On 2016-05-12 21:45, Paul Belanger wrote:
> On Thu, May 12, 2016 at 09:20:23PM +0200, Andreas Jaeger wrote:
>> The docs team has frozen the stable/kilo branch of openstack-manuals.
>> Whenever it's convenient, could you delete the branch and add a kilo-eol
>> tag, please?
>>
> I'm happy to learn how to do this, let me ping another infra-root or look for
> some documentation on the process.
This has not been done so far - could you try pinging again, please? ;)
Thanks,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [infra][all] Jobs failing : "No matching distribution found for "
Note that there's no sense in rechecking right now. The infra team is
trying to workaround this problem currently (thanks Joshua!)
Once everything is fine, we change the IRC topic and send a note here,
Andreas
On 2016-05-11 06:07, Ian Wienand wrote:
> So it seems the just released pip 8.1.2 has brought in a new version
> of setuptools with it, which creates canonical names per [1] by
> replacing "." with "-".
>
> The upshot is that pip is now looking for the wrong name on our local
> mirrors. e.g.
>
> ---
> $ pip --version
> pip 8.1.2 from /tmp/foo/lib/python2.7/site-packages (python 2.7)
> $ pip --verbose install --trusted-host mirror.ord.rax.openstack.org -i
> http://mirror.ord.rax.openstack.org/pypi/simple 'oslo.config>=3.9.0'
> Collecting oslo.config>=3.9.0
> 1 location(s) to search for versions of oslo.config:
> * http://mirror.ord.rax.openstack.org/pypi/simple/oslo-config/
> Getting page http://mirror.ord.rax.openstack.org/pypi/simple/oslo-config/
> Starting new HTTP connection (1): mirror.ord.rax.openstack.org
> "GET /pypi/simple/oslo-config/ HTTP/1.1" 404 222
> Could not fetch URL
> http://mirror.ord.rax.openstack.org/pypi/simple/oslo-config/: 404 Client
> Error: Not Found for url:
> http://mirror.ord.rax.openstack.org/pypi/simple/oslo-config/ - skipping
> Could not find a version that satisfies the requirement oslo.config>=3.9.0
> (from versions: )
> ---
>
> (note olso-config, not oslo.config). Compare to
>
> ---
> $ pip --verbose install --trusted-host mirror.ord.rax.openstack.org -i
> http://mirror.ord.rax.openstack.org/pypi/simple 'oslo.config>=3.9.0'
> You are using pip version 6.0.8, however version 8.1.2 is available.
> You should consider upgrading via the 'pip install --upgrade pip' command.
> Collecting oslo.config>=3.9.0
> Getting page http://mirror.ord.rax.openstack.org/pypi/simple/oslo.config/
> Starting new HTTP connection (1): mirror.ord.rax.openstack.org
> "GET /pypi/simple/oslo.config/ HTTP/1.1" 200 2491
> ---
>
> I think infra jobs that run on bare-precise are hitting this
> currently, because that image was just built. Other jobs *might* be
> isolated from this for a bit, until the new pip gets out there on
> images, but "winter is coming", as they say...
>
> There is [2] available to make bandersnatch use the new names.
> However, I wonder if this might have the effect of breaking the
> mirrors for old versions of pip that ask for the "."?
>
> pypi proper does not seem affected, just our mirrors.
>
> I think probably working with bandersnatch to get a fixed version ASAP
> is probably the best way forward, rather than us trying to pin to old
> pip versions.
>
> -i
>
> [1] https://www.python.org/dev/peps/pep-0503/
> [2]
> https://bitbucket.org/pypa/bandersnatch/pull-requests/20/fully-implement-pep-503-normalization/
>
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] binary package install - plan of attack
On 05/09/2016 11:11 AM, Robert Collins wrote:
> [...]
> Testing only dependencies should be in the test profile.
>
> We may want to have a source or similar named profile for
> building-from-source of things, but I'd start with just the default
> profile for the always-needed deps and test for CI test run
> dependencies.
John and myself just had a discussion on #openstack-swift about what are
test dependencies and what not - see also
https://review.openstack.org/#/c/298313/6/other-requirements.txt
John pointed out that all the requirements are needed for both testing
and actual usage, so my marking of test is wrong in the change.
So, I'll remove the test again on that one - do you agree, Robert?
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] binary package install - plan of attack
On 2016-05-09 19:47, Robert Collins wrote:
>
> On 9 May 2016 9:20 PM, "Andreas Jaeger" <a...@suse.com
> <mailto:a...@suse.com>> wrote:
>
>>
>> And then invoke "bindep test" and that would install both packages,
> correct?
>
> Yes.
Great! Thanks for the explanations!
I've created some patches now.
>> In that case our three steps here would be:
>> * Mark in the reviews some of the dependencies as [test]
https://review.openstack.org/#/c/298313/
>> * Invoke "bindep test" instead of "bindep" in infra scripts
https://review.openstack.org/#/c/314571/
https://review.openstack.org/#/c/314574/
>> * Fix the bug (not a blocking issue)
Robert, will you work on this, please?
Thanks,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] binary package install - plan of attack
On 05/03/2016 09:45 PM, James E. Blair wrote:
Andreas Jaeger <a...@suse.com> writes:
Goals:
1. bindep-fallback.txt should be minimal and handle packages that the
majority of projects need.
Isn't the goal to remove bindep-fallback.txt completely?
I wasn't sure whether we want to go that far - but that's also why I
stated the goals so that we can all be on the same page ;).
I hope so -- I think it should be -- otherwise we are saying projects
should explicitly declare their binary dependencies, except for some
arbitrary set.
I understand we may iterate a bit before we get there, and 'minimal' can
be a step on the way to 'removed'.
Yes, this would be the first step in this direction. But if we want to
remove it, the messaging around it will be different ;)
Thanks for the write up!
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] binary package install - plan of attack
Paul and myself discussed this morning how to move forward with binary
package installation - the bindep-fallback.txt/other-requirements.txt story.
I wrote up what we discussed and hope I didn't forgot anything here.
Please review and comment - and sign up if you want to help.
Andreas - who will board his plane to Washington in a few minutes
Goals:
1. bindep-fallback.txt should be minimal and handle packages that the
majority of projects need.
2. Projects can use other-requirements to document their binary
requirements.
3. There are no apt-get/yum install commands in jenkins/jobs/
Proposal:
1. Resolve with lifeless how the other-requirements.txt file should
look like, see:
nova: https://review.openstack.org/#/c/200672/
swift: https://review.openstack.org/#/c/298313/
2. Document how to use other-requirements.txt.
3. Review list of packages in bindep-fallback.txt and write up
packages that are not in the minimal set. Review apt-get/yum
install lists.
First iteration for apt-get/yum install (just jobs/macros):
* npm-install
* xvfb-install
* firefox-install
* chrome-install
* diskimage-builder-install
* puppet-prepare-node - this might be tricky since it removes
packages as well, so might be the only exception.
* chef-bundler-prep
* elasticsearch-install
* gate-anvil-rpms-dsvm-{node}
* periodic-package-afs-centos7 - might need to stay as is.
First iteration of extra packages to remove for
bindep-fallback.txt (let's not discuss specific packages here yet
but instead the broader principle (see goal 1 and how to refine that
one using this first proposal):
* asciidoc
* docbook-style-xsl [platform:rpm]
* docbook-xml [platform:dpkg]
* docbook-xsl [platform:dpkg]
* docbook5-schemas [platform:rpm]
* docbook5-style-xsl [platform:rpm]
* docbook5-xml [platform:dpkg]
* firefox [!platform:debian]
* fonts-nanum [platform:dpkg]
* fonts-takao [platform:dpkg]
* iceweasel [platform:debian]
* liberasurecode-dev [platform:dpkg]
* liberasurecode-devel [platform:rpm]
* libevent-dev [platform:dpkg]
* libevent-devel [platform:rpm]
* libffi-dev [platform:dpkg]
* libffi-devel [platform:rpm]
* libjerasure-dev [platform:ubuntu-trusty]
* libjpeg-dev [platform:dpkg]
* libjpeg-turbo-devel [platform:rpm]
* libldap2-dev [platform:dpkg]
* libpcap-dev [platform:dpkg]
* libpcap-devel [platform:rpm]
* libpq-dev [platform:dpkg]
* librrd-dev [platform:dpkg]
* libvirt-dev [platform:dpkg]
* libvirt-devel [platform:rpm]
* libvirt-python [platform:rpm]
* libxml2-dev [platform:dpkg]
* libxml2-devel [platform:rpm]
* libxml2-utils [platform:dpkg]
* libxslt-devel [platform:rpm]
* libxslt1-dev [platform:dpkg]
* mariadb [platform:rpm]
* mariadb-devel [platform:rpm]
* mariadb-server [platform:rpm]
* memcached
* mongodb [platform:dpkg]
* mongodb-server [platform:rpm]
* mysql-server [platform:dpkg]
* php-cli [platform:rpm]
* php5-cli [platform:dpkg]
* php5-mcrypt [platform:dpkg]
* postgresql
* postgresql-devel [platform:rpm]
* postgresql-server [platform:rpm]
* python-zmq
* redis [platform:rpm]
* redis-server [platform:dpkg]
* rrdtool-devel [platform:rpm]
* swig
* xorg-x11-server-Xvfb [platform:rpm]
* xsltproc [platform:dpkg]
* xvfb [platform:dpkg]
* zookeeperd [platform:dpkg]
4. Send email to openstack-dev to inform projects that
other-requirements.txt can be used - and in which cases it has to
be used. Explain:
* that we will remove all apt-get/yum install usage from
jenkins/jobs by specific date X.
* infra will send other-requirements.txt files to projects with
current default package list to projects that currently use
apt-get/yum install. Projects should merge these and then remove
packages that they do not need. If this is not merged by day X,
the projects will break.
* which packages will be removed from bindep-fallback.txt
5. Review extra package installs. Send other-requirements.txt changes
for projects who's jobs are affected.
6. Review how integration jobs can be done. For example
gate-bandit-integration-{target-project} in jenkins/jobs/bandit.yaml
could be changed to:
1) checkout bandit and the integration repository
2) Install other-requirements/bindep-fallback for *both*
repositories. In this case installing packages for bandit is
enough since tox is run from bandit. But for others it might be
different.
3) Run tests
7. By day X: Remove all extra package installs from jenkins/ and
remove these packages from bindep-fallback.txt.
8. Party!
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Re: [OpenStack-Infra] [openstack] "https://www.openstack.org/marketplace/drivers" not updated
On 2016-03-31 08:59, Mohan Kumar wrote:
> Hi Team ,
>
> we have added driver details to driverlog project few month before
>
> *https://github.com/openstack/driverlog/blob/master/etc/default_data.json#L3680-L3697
> *
> and the UI is also got updated
>
> *http://stackalytics.com/report/driverlog?project_id=openstack%2Fneutron=Open%20Networking%20Laboratory=liberty*
>
> But this details not *got updated at "
> https://www.openstack.org/marketplace/drivers/; website *. Could
> anyone shed some light on it ? any point of contact ?
That web site is not maintained by the Infra team. Sorry, we cannot help
you further.
Instead report bugs here:
https://bugs.launchpad.net/openstack-org
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] nova-docs, nova-branch-tarball post jobs are broken due to constraints
On 02/27/2016 05:54 PM, Andreas Jaeger wrote:
> Some post-jobs like nova-docs and nova-branch-tarball (similar for every
> other project that switched to using constraints unconditionally) are
> broken now.
>
> The problem is that we run these using "tox -evenv" - and the standard
> virtual environment for nova uses constraints. But since this is a post
> job, we have not setup the constraints file at all.
>
> Example log files:
> http://logs.openstack.org/77/77e6866feff4000926695ae0ef06f89864c320cf/post/nova-docs/b2bb877/console.html
> http://logs.openstack.org/77/77e6866feff4000926695ae0ef06f89864c320cf/post/nova-branch-tarball/c077cd3/console.html
>
> Has anybody an idea how to fix this?
I suggest we remove constraints from the venv tox environment for now:
https://review.openstack.org/285826
https://review.openstack.org/285827
Please review - and feel free to propose a better solution as alternative,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] nova-docs, nova-branch-tarball post jobs are broken due to constraints
Some post-jobs like nova-docs and nova-branch-tarball (similar for every
other project that switched to using constraints unconditionally) are
broken now.
The problem is that we run these using "tox -evenv" - and the standard
virtual environment for nova uses constraints. But since this is a post
job, we have not setup the constraints file at all.
Example log files:
http://logs.openstack.org/77/77e6866feff4000926695ae0ef06f89864c320cf/post/nova-docs/b2bb877/console.html
http://logs.openstack.org/77/77e6866feff4000926695ae0ef06f89864c320cf/post/nova-branch-tarball/c077cd3/console.html
Has anybody an idea how to fix this?
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Translation scripts: Next steps?
Thanks to great help by Akihiro, the translation spec [1] has
implemented the first steps (1-4) and all the python projects as well as
django projects with one module use this setup just fine!
Now it's time to decide how to continue with repositories that have more
than one module.
We currently only translate a single repository with more than one
module - horizon - and special case it. We can continue doing it this way.
But there're a few more repositories that want translations in the
future and have multiple modules, so let's discuss how to continue - or
whether to wait until those are ready.
Looking at repositories, here's a list in the form "repository =>
modules" that Akihiro compiled:
* horizon => horizon, openstack_dashboard (both django modules)
* vitrage-dashboard => vitrageentities, vitragealarms,
vitragedashboard (all django modules)
* astara-horizon : astara_horizon (namespace package),
astara_horizon.astara_openstack_dashboard (django)
* networking-sfc : networking_sfc (python), sfc_dashboard (django)
Akihiro has proposed one change [2] that can be used for horizon and
also vitrage-dashboard. Or we ask vitrage-dashboard to use a single module.
The other two repositories have both a python and a django repository
which needs special casing, like step 6 of the spec [1]. But those are
not asking yet for translation.
What do you suggest to do with these options:
1) Keep status quo for now?
2) Merge [2] to simplify scripts for horizon and vitrage
3) Implement step 6 - even if no repo currently uses it
4) Anything else?
Andreas
[1]
http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_setup.html
[2] https://review.openstack.org/#/c/280711/
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] problems on periodic-neutron
On 02/09/2016 02:22 AM, fumihiko kakuma wrote:
On Tue, 09 Feb 2016 09:11:22 +0900
fumihiko kakuma <kak...@valinux.co.jp> wrote:
On Mon, 8 Feb 2016 14:20:45 -0500
Matthew Treinish <mtrein...@kortar.org> wrote:
There is nothing wrong with openstack-health it's behaving as currently
expected. There is a known limitation with the dashboard right now where
results aren't counted if the job failure occurs before devstack starts. If your
jobs are running but never even getting to devstack openstack-health (well
really the subunit2sql db) will not have any data on those runs. Once you fix
these jobs to actually start running devstack (or anything else which generates
a subunit stream in the expected place) it'll appear on the dashboard.
I wrote a brief blog post a little while ago on how openstack-health works and
some of the features it has:
http://blog.kortar.org/?p=279
The current limitations section explains this issue in a bit more detail.
-Matt Treinish
Thank you for reply.
OK, it explains the issue for periodic-neutron pipeline.
But how about periodic pipeline? It also does not seem to work.
http://status.openstack.org/openstack-health/#/g/build_queue/periodic
Currently my jobs are required to use periodic pipeline.
So I want to know whether it works on periodic pipeline.
https://review.openstack.org/#/c/276317/
Thanks,
Sorry, I did not check the details of jobs on periodic pipeline.
They do not seems to run devstack.
So openstack-health dashboard will not display a graph for periodic
pipeline.
Is that correct?
Yes, health dashboard currently covers only devstack,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] juno-eol for openstack-manual
On 2015-12-12 11:22, Andreas Jaeger wrote:
> Hi infra-root,
>
> We have merged the last changes for juno and are ready to end-of-life
> openstack-manuals. Please do whenever convenient,
A friendly reminder that this has not happened yet..
Note that we have no ACLs setup for tagging ourselves, so need infra
help on it,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Translation check website
Who will be cores for this repo? The groups are not setup yet:
https://review.openstack.org/#/admin/groups/1266,members
https://review.openstack.org/#/admin/groups/1267,members
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Translation check website
>
> https://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/scripts
>
> > 3. How to get a machine to set up the website ?
>
> Once the puppet module is complete, you'll contact one of us on the
> infra team (probably me) and I'll launch the server.
>
> A couple notes:
>
> 1. We'll want to refresh this instance regularly (weekly?), so you'll
> want a cron job to run unstack.sh weekly or so and then recreate the
> devstack instance. We'll also want to keep an eye on how this goes,
> since unstack.sh is not a perfect script and we may need to recreate
> the instance from scratch now and then.
>
> 2. We also want to pull the translations regularly (daily?), so you'll
> want a cron job to run the zanata-cli script for the translations in
> Horizon
>
> > 4. How to get a domain name ? for example:
> translation-test.openstack.org ?
>
> This will be created when I bring up the server in step 3. We don't
> have a name for it yet, but should probably update the spec when we
> decide upon one.
>
> --
> Elizabeth Krumbach Joseph || Lyz || pleia2
>
>
>
>
>
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Translation setup challenges
On 12/30/2015 07:22 PM, Akihiro Motoki wrote:
Thanks for initiating this effort.
2015-12-29 6:28 GMT+09:00 Andreas Jaeger <a...@suse.com>:
Reading some IRC backlog and an incoming review with a new suggestion on how
to do translations in the project, I decided to write some problems our
current scripts have, together with questions and proposals. With the
growing big tent and the automatic way to setup translations, we get more
repos requesting translations - and more support requests.
Please read the description below and tell me what's wrong,what's missing,
where you disagree - and how to move forward.
thanks,
Andreas
Setting up translations for new projects currently has the following
challenges:
a) For "python" repositories, we expect that the locale file is
located at $repo/locale/$repo.pot - without any change possible.
This leads to python-novaclient/locale/python-novaclient.pot and
oslo.log/locale/oslo.log.i18n - in both cases the python module has
a different name, novaclient and oslo_log.
Currently everybody makes it wrong and we have to help them using
the proper file names.
Proposal:
* Simplify location to use $modulename/locale/$modulename
Can we determine modulename easily from the name in setup.cfg like
in jenkins/scripts/pypi-extract-name.py?
IMO it is better to keep a domain name. The domain name means a filename.
The domain name is specified in oslo.i18n wrapper and setup.cfg.
Changing the directory name helps a lot, but changing the basename helps little.
My proposal is $modulename/locale/$reponame, but either of them is okay to me.
Isn't the domainname the same as modulename? I just checked
python-novaclient and it uses as domainname novaclient.
b) For dashboard repos, there's no common entry point yet and some are
even setup like "python" repositories (designate-dashboard).
It is a good idea to add some common entry point (tox target).
There's also no naming pattern on how to name files and everybody
does it differently.
Currently the django component is called djangjo.pot, the
javascript one djangojs.pot.
Question: Do we really need to do it this way or can we change it?
We should have a single entrypoint for projects and a standard way
to call them.
Proposal: Define standard tox environement "extractmessages", it
places translation files in (if django/djangojs are really the best
names, I prefer to change them):
* $modulename/locale/django.pot
* $modulename/locale/djangojs.pot
Can we determine modulename easily from the name in setup.cfg like
in jenkins/scripts/pypi-extract-name.py? At least
django_openstack_auth is setup differently..
As far as I know it is not easy to change.
Looking at
https://docs.djangoproject.com/en/1.9/topics/i18n/translation/#specialties-of-django-translation,
The django framework expects django and djangojs as a domain name.
Message catalogs should be placed in 'locale' directory under each
django application path,
i.e. $modulename/locale/. It works most dashboard repository, but
'horizon' repo is special.
Horizon repo uses two django applications, openstack_dashboard and
horizon and this means
we need horizon/locale and openstack_dashboard/locale.
If we forces $modulename/locale/, it breaks Horizon implementation.
Ok, we need to make an exception here. Let me update my draft spec for this.
# Horizon team explored to split openstack_dashboard and horizon, but
there seems no much value
# at the moment and the effort is now stopped (or abandoned).
c) Projects currently need to add the pot file initially, our scripts
fail if the directory does not exist.
Proposal: Make scripts robust so that they work even without
initial pot file.
It sounds a good idea.
If 'translate' tag is specified in project-config/gerrit/projects.yaml,
it would be nice that POT file is generated automatically.
Exactly.
thanks for your comments,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
