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
[openstack-dev] [all][release][infra] changing release template publish-to-pypi
Doug recently introduced the template publish-to-pypi-python3 and used
it for all official projects. It only has a minimal python3 usage
(calling setup.py sdist bdist_wheel) that should work with any repo.
Thus, I pushed a a series of changes up - see
https://review.openstack.org/#/q/topic:publish-pypi - to rename
publish-to-pypi-python3 back to publish-to-pypi. Thus, everybody uses
again the same template and testing.
Note that the template publish-to-pypi-python3 contained a test to see
whether the release jobs works, this new job is now run as well. It is
only run if one of the packaging files is updated - and ensures that
uploading to pypi will work fine. If this new job now fails, please fix
the fallout so that you can safely release next time.
The first changes in this series are merging now - if this causes
problems and there is a strong need for an explicit python2 version,
please tell me,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Proposal for a process to keep up with Python releases
On 19/10/2018 18.30, Clark Boylan wrote:
> [...]
Because zuul config is branch specific we could set up every project to use a
`openstack-python3-jobs` template then define that template differently on each
branch. This would mean you only have to update the location where the template
is defined and not need to update every other project after cutting a stable
branch. I would suggest we take advantage of that to reduce churn.
Alternative we have a single "openstack-python3-jobs" template in an
unbranched repo like openstack-zuul-jobs and define different jobs per
branch.
The end result would be the same, each repo uses the same template and
no changes are needed for the repo when branching...
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Release-job-failures] Release of openstack-infra/shade failed
On 19/10/2018 16.19, Sean McGinnis wrote:
This appears to be another in-transit job conflict with the py3 work.
Things should be fine, but we will need to manually propose the
constraint update since it was skipped.
On Fri, Oct 19, 2018, 09:14 <mailto:z...@openstack.org>> wrote:
Build failed.
- release-openstack-python3
http://logs.openstack.org/33/33d839da8acb93a36a45186d158262f269e9bbd6/release/release-openstack-python3/1cb87ba/
: SUCCESS in 2m 44s
- announce-release announce-release : SKIPPED
- propose-update-constraints propose-update-constraints : SKIPPED
- release-openstack-python
http://logs.openstack.org/33/33d839da8acb93a36a45186d158262f269e9bbd6/release/release-openstack-python/3a9339d/
: POST_FAILURE in 2m 40s
We're not using tox venv anymore for the release job, so I think we need
to remove the "fetch-tox-output" role completely:
https://review.openstack.org/611886
Andreas
___
Release-job-failures mailing list
release-job-failu...@lists.openstack.org
<mailto:release-job-failu...@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [requirements][vitrage][infra] SQLAlchemy-Utils version 0.33.6 breaks Vitrage gate
On 18/10/2018 14.15, Ifat Afek wrote:
Hi,
In the last three days Vitrage gate is broken due to the new requirement
of SQLAlchemy-Utils==0.33.6.
We get the following error [1]:
[...] >
Can we move back to version 0.33.5? or is there another solution?
We discussed that on #openstack-infra, and fixed it each day - and then
it appeared again.
https://review.openstack.org/611444 is the proposed fix for that - the
issues comes from the fact that we build wheels if there are none
available and had a race in it.
I hope an admin can delete the broken file again and it works again
tomorrow - if not, best to speak up quickly 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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [astara] Retirement of astara repos?
On 20/08/2018 15.52, Mark McClain wrote:
Yeah. I’ll post the retirement commits this week.
I posted them now - see
https://review.openstack.org/#/q/status:open+++topic:retire-astara
Please abandon also all open reviews:
https://review.openstack.org/#/q/projects:openstack/astara+is:open
If you need help, please speak up,
Andreas
mark
On Aug 18, 2018, at 13:39, Andreas Jaeger wrote:
Mark, shall I start the retirement of astara now? I would appreciate a "go
ahead" - unless you want to do it yourself...
Andreas
On 2018-02-23 14:34, Andreas Jaeger wrote:
On 2018-01-11 22:55, Mark McClain wrote:
Sean, Andreas-
Sorry I missed Andres’ message earlier in December about retiring astara.
Everyone is correct that development stopped a good while ago. We attempted in
Barcelona to find others in the community to take over the day-to-day
management of the project. Unfortunately, nothing sustained resulted from that
session.
I’ve intentionally delayed archiving the repos because of background
conversations around restarting active development for some pieces bubble up
from time-to-time. I’ll contact those I know were interested and try for a
resolution to propose before the PTG.
Mark, any update here?
--
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
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [python3] Enabling py37 unit tests
On 10/10/2018 23.10, Jeremy Stanley wrote:
> I might have only pointed this out on IRC so far, but the
> expectation is that testing 3.5 and 3.6 at the same time was merely
> transitional since official OpenStack projects should be moving
> their testing from Ubuntu Xenial (which provides 3.5) to Ubuntu
> Bionic (which provides 3.6 and, now, 3.7 as well) during the Stein
> cycle and so will drop 3.5 testing on master in the process.
Agreed, this needs some larger communication and explanation on what to do,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [python3] Enabling py37 unit tests
On 10/10/2018 15.42, Corey Bryant wrote:
On Wed, Oct 10, 2018 at 9:26 AM Andreas Jaeger <mailto:a...@suse.com>> wrote:
On 10/10/2018 14.45, Corey Bryant wrote:
> [...]
> == Enabling py37 unit tests ==
>
> Ubuntu Bionic (18.04 LTS) has the 3.7.0 interpreter and I have
reviews
> up to define the py37 zuul job and templates here:
> https://review.openstack.org/#/c/609066
>
> I'd like to start submitting reviews to projects to enable
> openstack-python37-jobs (or variant) for projects that already have
> openstack-python36-jobs in their .zuul.yaml, zuul.yaml,
> .zuul.d/project.yaml.
We have projects testing python 3.5 and 3.6 already. Adding 3.7 to
it is
a lot of wasted VMs. Can we limit testing and not test all three,
please?
Well, I wouldn't call any of them wasted if they're testing against a
supported Python version.
What I mean is that we run too into a situation where we have a large
backlog of CI jobs since we have to many changes and jobs in flight.
So, I'm asking whether there is a good way to not duplicating all jobs
to run on all three interpreters. Do we really need testing of all three
versions? Or is testing with a subset a manageable risk?
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [python3] Enabling py37 unit tests
On 10/10/2018 14.45, Corey Bryant wrote:
[...]
== Enabling py37 unit tests ==
Ubuntu Bionic (18.04 LTS) has the 3.7.0 interpreter and I have reviews
up to define the py37 zuul job and templates here:
https://review.openstack.org/#/c/609066
I'd like to start submitting reviews to projects to enable
openstack-python37-jobs (or variant) for projects that already have
openstack-python36-jobs in their .zuul.yaml, zuul.yaml,
.zuul.d/project.yaml.
We have projects testing python 3.5 and 3.6 already. Adding 3.7 to it is
a lot of wasted VMs. Can we limit testing and not test all three, 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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [docs][charms] Updating Deployment Guides indices of published pages
On 9/27/18 10:04 AM, Frode Nordahl wrote:
Hello docs team,
What would it take to re-generate the indices for Deployment Guides on
the published Queens [0] and Rocky [1] docs pages?
It seems that the charms project has missed the index for those releases
due to some issues which now has been resolved [2]. We would love to
reclaim our space in the list!
0: https://docs.openstack.org/queens/deploy/
1: https://docs.openstack.org/rocky/deploy/
2:
https://review.openstack.org/#/q/topic:enable-openstack-manuals-rocky-latest+(status:open+OR+status:merged)
We found the problem - you updated the build job to use bionic but
nobody updated the publish one. This is fixed now since
https://review.openstack.org/#/c/606147/ is merged.
All should be fine again,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [docs][charms] Updating Deployment Guides indices of published pages
On 27/09/2018 10.04, Frode Nordahl wrote:
Hello docs team,
What would it take to re-generate the indices for Deployment Guides on
the published Queens [0] and Rocky [1] docs pages?
In a nutshell: Patience ;) All looks fine, details below:
They are regenerated as part of each merge to openstack-manuals.
Looking at [0] it was last regenerated on the 11th, might be the post
job was never run for the changes you reference in [2].
It seems that the charms project has missed the index for those releases
due to some issues which now has been resolved [2]. We would love to
reclaim our space in the list!
Right now we have a HUGE backlog of post jobs (70+ hours) due to high
load of CI as mentioned by Clark earlier this month. After the next
merge and post job run, those should be up.
So, please check again once the backlog is worked through and a next
change merged. If the content is then still not there, we need to
investigate the post jobs and why they failed.
Andreas
0: https://docs.openstack.org/queens/deploy/
1: https://docs.openstack.org/rocky/deploy/
2:
https://review.openstack.org/#/q/topic:enable-openstack-manuals-rocky-latest+(status:open+OR+status:merged)
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [goals][python3][nova] starting zuul migration for nova repos
://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [docs] Nominating Ian Y. Choi for openstack-doc-core
On 2018-09-19 20:50, Petr Kovar wrote:
Hi all,
Based on our PTG discussion, I'd like to nominate Ian Y. Choi for
membership in the openstack-doc-core team. I think Ian doesn't need an
introduction, he's been around for a while, recently being deeply involved
in infra work to get us robust support for project team docs translation and
PDF builds.
>
Having Ian on the core team will also strengthen our integration with
the i18n community.
Please let the ML know should you have any objections.
The opposite ;), heartly agree with adding him,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [doc][i18n][infra][tc] plan for PDF and translation builds for documentation
I like the plan, thanks! One suggestion below:
The translated documents are build for releasenotes already in a similar
way as proposed. here we update the index.rst file on the fly to link to
all translated versions, see the bottom of e.g.
https://docs.openstack.org/releasenotes/openstack-manuals/
I suggest that you look also as part of building how to link to PDFs and
translated documents.
For reference, the logic for releasenotes translation is here:
http://git.openstack.org/cgit/openstack-infra/zuul-jobs/tree/roles/build-releasenotes/tasks/main.yaml#n10
I would appreciate if you handle releasenotes the same way as other
documents, so if you want to change releasenotes in the end, please do
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [kolla] Committing proprietary plugins to OpenStack
On 2018-09-12 13:21, Shyam Biradar wrote:
Hi,
We have a proprietary openstack plugin. We want to commit deployment
scripts like containers and heat templates to upstream in tripleo and
kolla project but not actual product code.
Is it possible? Or How can we handle this case? Any thoughts are welcome.
It's first a legal question - is everything you are pushing under the
Apache license as the rest of the project that you push to?
And then a policy of kolla project, so let me tag them
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all][infra] Moving cover job from post to check pipeline
On 2018-09-06 20:10, Andreas Jaeger wrote:
Citing Ian Wienand in [2]
"There was a thread some time ago that suggested coverage jobs weren't
doing much in the "post" pipeline because nobody looks at them and the
change numbers may be difficult to find anyway [1]. This came up again
in a cleanup to add non-voting coverage jobs in
I5c42530d1dda41b8dc8c13cdb10458745bec7bcc.
There really is no consistency across projects; it seems like a couple
of different approaches have been cargo-cult copied as new projects came
in, depending on which random project was used as a template. This
change does a cleanup by moving all post coverage jobs into the check
queue as non-voting jobs."
Correcting: It's a voting job.
Note that I pushed changes - using topic:update-zuul - to projects with
that update and found a few broken cover jobs. Those were run as post
jobs and always failed ;(
Andreas
I've updated Ian's change [2] now and propose to move ahead with it -
and suggest that projects with in-repo coverage job follow it as well.
Let's use the new template [3] openstack-cover-jobs (and it's
-horizon/-neutron variants) for this change.
Andreas
[1]
http://lists.openstack.org/pipermail/openstack-dev/2016-July/099491.html
[2] https://review.openstack.org/#/c/432836/
[3]
https://docs.openstack.org/infra/openstack-zuul-jobs/project-templates.html#project_template-openstack-cover-jobs
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [product] Retiring development-proposals
The product WG is abandoned, so it's time to retire the
development-proposals repository.
The content of the WG is published and thus available for reference:
http://specs.openstack.org/openstack/development-proposals/
I've started the retirement process using topic retire-productwg
following
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project ,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [all][infra] Moving cover job from post to check pipeline
Citing Ian Wienand in [2]
"There was a thread some time ago that suggested coverage jobs weren't
doing much in the "post" pipeline because nobody looks at them and the
change numbers may be difficult to find anyway [1]. This came up again
in a cleanup to add non-voting coverage jobs in
I5c42530d1dda41b8dc8c13cdb10458745bec7bcc.
There really is no consistency across projects; it seems like a couple
of different approaches have been cargo-cult copied as new projects came
in, depending on which random project was used as a template. This
change does a cleanup by moving all post coverage jobs into the check
queue as non-voting jobs."
I've updated Ian's change [2] now and propose to move ahead with it -
and suggest that projects with in-repo coverage job follow it as well.
Let's use the new template [3] openstack-cover-jobs (and it's
-horizon/-neutron variants) for this change.
Andreas
[1] http://lists.openstack.org/pipermail/openstack-dev/2016-July/099491.html
[2] https://review.openstack.org/#/c/432836/
[3]
https://docs.openstack.org/infra/openstack-zuul-jobs/project-templates.html#project_template-openstack-cover-jobs
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [all] Switching docs jobs to new tox-docs for specs repos
I've proposed two changes to change the docs building and publishing of
specs repos to use the new PTI openstack-tox-docs job. This means that
your the docs job will now run "tox -e docs". A quick check shows that
all repos are set up properly - but if suddenly docs building fails for
a specs repo, do the same kind of changes you did for your main repo
when you switched to "publish-openstack-docs-pti" template.
The changes are:
https://review.openstack.org/600457
https://review.openstack.org/600458
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all]-ish : Updates required for readthedocs publishers
On 2018-09-06 14:20, Ilya Shakhat wrote:
What is the process once webhook_id is added to project's zuul.yaml?
Should I propose a change into project-config/zuul.d/projects.yaml or it
will be done automatically?
You need to send to use docs-on-readthedocs template and set the
variable to project-config repo.
BTW (not completely related to this topic, but since I'm touching
zuul.yaml anyway) - what are the best practices for non-official
projects - should zuul configuration stay in project-config or better be
moved to local zuul.yaml?
See
https://docs.openstack.org/infra/manual/creators.html#central-config-exceptions
for what should stay in project-config.
Since the publishing is part of a release, the template needs to stay in
project-config,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Retiring openstack-infra/odsreg and openstack-infra/puppet-odsreg
On 2018-09-05 09:40, Thierry Carrez wrote:
> Andreas Jaeger wrote:
>> Puppet-odsreg is unused nowadays and it seems that odsreg is unused as
>> well. I'll propose changes to retire them with topic "retire-odsreg",
>
> So... we actually still used odsreg until recently for Forum
> submissions. The Berlin Forum is the first one where we won't use it, so
> I feel it's a bit too early to retire that codebase. If the current plan
> (which is to reuse the CFP app from the website) does not work, we'd
> certainly welcome having a plan B.
>
> If you REALLY want it gone NOW I guess we could just push it to GitHub
> and keep it there until we are 100% sure we won't need it anymore, but
> that sounds a bit silly.
>
OK, I'll retire puppet-odsreg only for now - please tell us once odsreg
can be retired as well,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] check-requirements and you
On 2018-09-05 05:20, Matthew Thode wrote:
With the move to per-project requirements (aka divergent requirements)
we started allowing projects to have differing exclusions and minimums.
As long as projects still tested against upper-constraints we were good.
Part of the reason why we use upper-constraints is to ensure that
project A and project B are co-installable. This is especially useful
to distro packagers who can then target upper-constraints for any
package updates they need. Another reason is that we (the requirements
team) reviews new global-requirements for code quality, licencing and
the like, all of which are useful to Openstack as a whole.
If a projects dependencies are compatible with the global list, and the
global list is compatible with the upper-constraints, then the
projects' dependencies are compatible with the upper-constraints.
All the above lets us all work together and use any lib listed in
global-requirements (at the upper-constraints version). This is all
ensured by having the check-requirements job enabled for your project.
It helps ensure co-installability, code quality, python version
compatibility, etc. So please make sure that if you are running
everything in your own zuul config (not project-config) that you have
the check-requirements job as well.
And also set up and run the lower-constraints jobs - you can use the new
template openstack-lower-constraints-jobs for this,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Retiring openstack-infra/odsreg and openstack-infra/puppet-odsreg
Puppet-odsreg is unused nowadays and it seems that odsreg is unused as
well. I'll propose changes to retire them with topic "retire-odsreg",
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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-dev] [goals][python3][adjutant][barbican][chef][cinder][cloudkitty][i18n][infra][loci][nova][charms][rpm][puppet][qa][telemetry][trove] join the bandwagon!
On 2018-08-31 10:49, Tobias Urdin wrote:
Hello Doug,
I've proposed moving all job config from project-config to the repos [1].
I don't know what to do with the periodic job here [2] should that be
left in project-config or moved?
Tobias, I'm sorry to see you doing this - but please abandon! You've
done only part of the work and finishing it will complicate it. Doug has
scripts for these and can easily run that. What Doug asked for was for
an official "go ahead" from the puppet 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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron][python3] Neutron and stadium - python 3 community goal changes coming soon
On 2018-08-30 17:16, Nate Johnston wrote:
On Thu, Aug 30, 2018 at 08:28:40AM -0400, Doug Hellmann wrote:
Excerpts from Michel Peterson's message of 2018-08-30 14:38:00 +0300:
On Thu, Aug 30, 2018 at 12:14 AM, Nate Johnston
wrote:
Progress is also being tracked in a wiki page [4].
[4] https://wiki.openstack.org/wiki/Python3
That wiki page should only track teams or subteams should also be included
there? I'm asking because it seems that some subteams appear there while
the majority doesn't and perhaps we want to standarize that.
It would be great to include information about sub-teams. If there
are several, like in the neutron case, it probably makes sense to
create a separate section of the page with a table for all of them,
just to keep things organized.
Great! I'll do that today.
Nate
P.S. By the way, at the top there is a note encouraging people to join
#openstack-python3, but when I try to do so I get rejected:
11:13 Error(473): #openstack-python3 Cannot join channel (+i) - you
must be invited
I figure either the wiki page or the channel is out of sync, but I am
not sure which one.
wiki page is wrong - the channel is dead. I'll update the wiki page,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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-dev] [infra] Retiring some unused repositories
On 2018-08-29 09:08, Andreas Jaeger wrote:
> On 2018-08-29 06:43, Andreas Jaeger wrote:
>> The infra team plans to retire the following repositories:
>> [...]
>
> One more repository to retire:
>
> openstack-infra/pynotedb
> Part of storyboard effort but unused and no further interest in it.
Further discussion needed for the one above.
I'm adding these two now as well to retire:
openstack-infra/releasestatus
openstack-infra/puppet-releasestatus
releasestatus is not used since December 2015, see
https://review.openstack.org/#/c/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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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-dev] [infra] Retiring some unused repositories
On 2018-08-29 06:43, Andreas Jaeger wrote:
> The infra team plans to retire the following repositories:
> [...]
One more repository to retire:
openstack-infra/pynotedb
Part of storyboard effort but unused and no further interest in 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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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
[openstack-dev] [infra] Retiring some unused repositories
The infra team plans to retire the following repositories:
openstack-infra/activity-board
openstack-infra/beaker-localhost
openstack-infra/beaker-nodepool
openstack-infra/err2d2
openstack-infra/js-afs-blob-store
openstack-infra/js-openstack-registry-hooks
openstack-infra/js-generator-openstack
openstack-infra/pypi-mirror
openstack-infra/trystack-site
openstack-infra/puppet-vinz
openstack-infra/vinz
openstack-infra/vinz-webclient
Explanation:
openstack-infra/activity-board:
Was part of bitergia work with openstack which is no longer done
openstack-infra/beaker-localhost
openstack-infra/beaker-nodepool
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/err2d2
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/js-afs-blob-store
openstack-infra/js-openstack-registry-hooks
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-generator-openstack
Appears to be a cookiecutter like system for openstack js
projects. Maybe we should just use cookiecutter?
openstack-infra/pypi-mirror
Was tooling to make a mirror of a subset of pypi. We moved to
bandersnatch and now just proxy cache pypi.
openstack-infra/trystack-site
Trystack has been retired due to spam and the passport program
is suggested instead.
openstack-infra/puppet-vinz
openstack-infra/vinz
openstack-infra/vinz-webclient
Project to provide alternate Gerrit UI that never got commits.
Process is started with https://review.openstack.org/597370,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all][tc][openstack-helm] On the problem of OSF copyright headers
In this context, there's also the question of copyright headers for
documentation files which we do not require - see
https://wiki.openstack.org/wiki/Documentation/Copyright
This came up recently with:
https://review.openstack.org/#/c/593662/
I'm happy to see a canonical place for this information,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [fuel] time to retire (parts of) fuel?
I see that many repos have not seen any merges for fuel. Do you want to
retire at least parts of it?
We have many bitrot jobs for fuel set up and people proposing jobs
against it that get no reaction - so, I suggest to make it's state clear.
I see some changes in fuel-devops - but the rest looks really dead.
What's your suggestion to move forward?
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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-dev] [astara] Retirement of astara repos?
Mark, shall I start the retirement of astara now? I would appreciate a
"go ahead" - unless you want to do it yourself...
Andreas
On 2018-02-23 14:34, Andreas Jaeger wrote:
On 2018-01-11 22:55, Mark McClain wrote:
Sean, Andreas-
Sorry I missed Andres’ message earlier in December about retiring astara.
Everyone is correct that development stopped a good while ago. We attempted in
Barcelona to find others in the community to take over the day-to-day
management of the project. Unfortunately, nothing sustained resulted from that
session.
I’ve intentionally delayed archiving the repos because of background
conversations around restarting active development for some pieces bubble up
from time-to-time. I’ll contact those I know were interested and try for a
resolution to propose before the PTG.
Mark, any update here?
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [docs] Retire rst2bash
The rst2bash repo is dead and unused. It was created to help us with
Install Guide testing - and this implementation was not finished and the
Install Guide looks completely different now.
I propose to retire it, see
https://review.openstack.org/#/q/topic:retire-rst2bash for changes,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2
On 2018-08-16 07:38, Tony Breeds wrote:
> On Thu, Aug 16, 2018 at 06:27:39AM +0200, Andreas Jaeger wrote:
>
>> Ocata should be retired by now ;) Let's drop it...
>
> *cough* extended maintenance *cough* ;P
Ah, forget about that.
> So we don't need the Ocata docs to be rebuilt with this version?
Ocata uses older sphinx etc. It would be nice - but not sure about the
effort,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2
On 2018-08-15 21:28, Tony Breeds wrote:
On Wed, Aug 15, 2018 at 09:10:18AM -0400, Doug Hellmann wrote:
Excerpts from Andreas Jaeger's message of 2018-08-15 09:28:51 +0200:
On 08/15/2018 07:25 AM, Tony Breeds wrote:
On Tue, Aug 14, 2018 at 04:22:16PM -0400, Doug Hellmann wrote:
Now that https://review.openstack.org/#/c/591671/ has landed, we need
someone to propose the backports of the constraint updates to all of the
existing stable branches.
Done:
https://review.openstack.org/#/q/owner:tonyb+topic:openstackdocstheme+project:openstack/requirements
I'm not entirely convinced such a new release will work on older
branches but I guess that's what CI is for :)
openstackdocsstheme has:
sphinx!=1.6.6,!=1.6.7,>=1.6.2
So, we cannot use it on branches that constraint sphinx to an older version,
Sorry, can't check this right now from where I am,
Andreas
That's a good point. We should give it a try, though. I don't think
pip's constraints resolver takes version specifiers into account, so we
should get the older sphinx and the newer theme. If those do happen to
work together, it should be OK.
If not, we need another solution. We may have to do more work to
backport the theme change into an older version of the library to
make it work in the old branches.
The queens and pike backports have merged but ocata filed with[1]
ContextualVersionConflict: (pbr 1.10.0
(/home/zuul/src/git.openstack.org/openstack/requirements/.tox/py27-check-uc/lib/python2.7/site-packages),
Requirement.parse('pbr!=2.1.0,>=2.0.0'), set(['openstackdocstheme']))
So we can't use the rocky release on ocata. I assume we need to do
something to ensure the docs are generated correctly.
Ocata should be retired by now ;) Let's drop it...
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2
On 2018-08-15 10:33, Tony Breeds wrote:
On Wed, Aug 15, 2018 at 09:28:51AM +0200, Andreas Jaeger wrote:
openstackdocsstheme has:
sphinx!=1.6.6,!=1.6.7,>=1.6.2
So, we cannot use it on branches that constraint sphinx to an older version,
Sorry, can't check this right now from where I am,
Constraints
---
origin/master : Sphinx===1.7.6
origin/stable/newton : Sphinx===1.2.3
origin/stable/ocata : Sphinx===1.3.6
origin/stable/pike: Sphinx===1.6.3
origin/stable/queens : Sphinx===1.6.5
Looks ok to me.
Great, 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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2
On 08/15/2018 07:25 AM, Tony Breeds wrote:
On Tue, Aug 14, 2018 at 04:22:16PM -0400, Doug Hellmann wrote:
Now that https://review.openstack.org/#/c/591671/ has landed, we need
someone to propose the backports of the constraint updates to all of the
existing stable branches.
Done:
https://review.openstack.org/#/q/owner:tonyb+topic:openstackdocstheme+project:openstack/requirements
I'm not entirely convinced such a new release will work on older
branches but I guess that's what CI is for :)
openstackdocsstheme has:
sphinx!=1.6.6,!=1.6.7,>=1.6.2
So, we cannot use it on branches that constraint sphinx to an older version,
Sorry, can't check this right now from where I am,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2
On 2018-08-13 19:16, Andreas Jaeger wrote:
On 2018-08-13 18:40, Petr Kovar wrote:
Hi all,
This is a request for an FFE to release openstackdocstheme 1.21.2.
This mostly fixes usability issues in rendering docs content, so we would
like to update the theme across all project team docs on docs.o.o.
I suggest to release quickly a 1.21.3 with
https://review.openstack.org/#/c/585517/ - and use that one instead.
Release request:
https://review.openstack.org/591485
Andreas
See also the update constraint request at
https://review.openstack.org/#/c/591020/.
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2
On 2018-08-13 18:40, Petr Kovar wrote:
Hi all,
This is a request for an FFE to release openstackdocstheme 1.21.2.
This mostly fixes usability issues in rendering docs content, so we would
like to update the theme across all project team docs on docs.o.o.
I suggest to release quickly a 1.21.3 with
https://review.openstack.org/#/c/585517/ - and use that one instead.
See also the update constraint request at
https://review.openstack.org/#/c/591020/.
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [I18n][all] Translation Imports
On 2018-08-09 10:10, Frank Kloeker wrote:
> Hello,
>
> maybe you missed it, translation import jobs are back today. Please
> merge "Imported Translations from Zanata" as soon as possible so we can
> move fast forward with Rocky translation.
> If you have already branched to stable/rocky please aware that we
> releasenotes translation manage only in master branch.
This means that the import deletes automatically the releasenotes
translations on any stable branch. The file removals you see are fine.
> Special thanks to openstack-infra and the zuul team for the fast error
> handling.
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tripleo] EOL process for newton branches
On 2018-08-07 07:08, Tony Breeds wrote:
> Okay Ian gave me permission to do this. Those repos have been tagged
> newton-eol and had the branches deleted.
Thanks, Tony!
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tripleo] EOL process for newton branches
Tony,
On 2018-07-19 06:59, Tony Breeds wrote:
On Wed, Jul 18, 2018 at 08:08:16PM -0400, Emilien Macchi wrote:
Option 2, EOL everything.
Thanks a lot for your help on this one, Tony.
No problem.
I've created:
https://review.openstack.org/583856
to tag final releases for tripleo deliverables and then mark them as
EOL.
This one has merged now.
Once that merges we can arrange for someone, with appropriate
permissions to run:
# EOL repos belonging to tripleo
eol_branch.sh -- stable/newton newton-eol \
openstack/instack openstack/instack-undercloud \
openstack/os-apply-config openstack/os-collect-config \
openstack/os-net-config openstack/os-refresh-config \
openstack/puppet-tripleo openstack/python-tripleoclient \
openstack/tripleo-common openstack/tripleo-heat-templates \
openstack/tripleo-image-elements \
openstack/tripleo-puppet-elements openstack/tripleo-ui \
openstack/tripleo-validations
Tony, will you coordinate with infra to run this yourself again - or let
them run it for you, please?
Note that we removed the script with retiring release-tools repo, I
propose to readd with https://review.openstack.org/589236 and
https://review.openstack.org/589237 and would love your review on these,
please. I want to be sure that we import the right version...
thanks,
Andreas
Yours Tony.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] autodoc and tox-siblings
On 2018-07-03 06:12, Takashi Yamamoto wrote:
> hi,
>
> - networking-midonet uses autodoc in their doc.
> build-openstack-sphinx-docs runs it.
> - build-openstack-sphinx-docs doesn't use tox-siblings. thus the job
> uses released versions of dependencies. eg. neutron, neutron-XXXaas,
> os-vif, etc
> - released versions of dependencies and networking-midonet master are
> not necessarily compatible
> - a consequence: https://bugs.launchpad.net/networking-midonet/+bug/1779801
> (in this case, neutron-lib and neutron are not compatible)
>
> possible solutions i can think of:
> - stop using autodoc (i suspect i have to do this for now)
> - make intermediate releases of neutron and friends
> - finish neutron-lib work and stop importing neutron etc (ideal but we
> have not reached this stage yet)
> - make doc job use tox-siblings (as it used to do in tox_install era)
>
> any suggestions?
Did you see
http://lists.openstack.org/pipermail/openstack-dev/2018-April/128986.html
- best discuss with Stephen whether that's a better solution,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Release-job-failures][release][horizon] Release of openstack/xstatic-angular-material failed
On 2018-06-25 14:57, Radomir Dopieralski wrote:
> Any idea where it took the 1.1.5.0 version from?
git grep 1.1.5 shows at least:
setup.cfg:description = Angular-Material 1.1.5 (XStatic packaging standard)
xstatic/pkg/angular_material/__init__.py:VERSION = '1.1.5' # version of
the packaged files, please use the upstream
Not sure whether that's the right place, I suggest you build locally and
check the build tarball,
Andreas
> On Mon, Jun 25, 2018 at 2:38 PM, Doug Hellmann <mailto:d...@doughellmann.com>> wrote:
>
> Excerpts from zuul's message of 2018-06-25 12:14:34 +:
> > Build failed.
> >
> > - xstatic-check-version
>
> http://logs.openstack.org/59/592a9d4c90f37cd33c6f861120f41ac8a67d909b/release/xstatic-check-version/a501dba/
>
> <http://logs.openstack.org/59/592a9d4c90f37cd33c6f861120f41ac8a67d909b/release/xstatic-check-version/a501dba/>
> : FAILURE in 1m 31s
> > - release-openstack-python release-openstack-python : SKIPPED
> > - announce-release announce-release : SKIPPED
> > - propose-update-constraints propose-update-constraints : SKIPPED
> >
>
> "git tag version (1.1.5.1) does not match package version (1.1.5.0)"
>
>
> http://logs.openstack.org/59/592a9d4c90f37cd33c6f861120f41ac8a67d909b/release/xstatic-check-version/a501dba/job-output.txt.gz#_2018-06-25_12_14_11_034599
>
> <http://logs.openstack.org/59/592a9d4c90f37cd33c6f861120f41ac8a67d909b/release/xstatic-check-version/a501dba/job-output.txt.gz#_2018-06-25_12_14_11_034599>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [docs][openstack-ansible]
Thanks for your leadership through troubled time!
Hope our ways cross again,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tc][docs] documenting openstack "constellations"
On 05/01/2018 04:08 PM, Doug Hellmann wrote:
The TC has had an item on our backlog for a while (a year?) to
document "constellations" of OpenStack components to make it easier
for deployers and users to understand which parts they need to have
the features they want [1].
John Garbutt has started writing the first such document [2], but
as we talked about the content we agreed the TC governance repository
is not the best home for it, so I have proposed creating a new
repository [3].
In order to set up the publishing jobs for that repo so the content
goes to docs.openstack.org, we need to settle the ownership of the
repository.
I think it makes sense for the documentation team to "own" it, but
I also think it makes sense for it to have its own review team
because it's a bit different from the rest of the docs and we may
be able to recruit folks to help who might not want to commit to
being core reviewers for all of the documentation repositories. The
TC members would also like to be reviewers, to get things going.
So, is the documentation team willing to add the new "constellations"
repository under their umbrella? Or should we keep it as a TC-owned
repository for now?
I'm fine having it as parts of the docs team. The docs PTL should be
part of the review team for sure,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon] Release of openstack/xstatic-angular-vis failed
On 2018-04-23 21:45, Sean McGinnis wrote:
> See below for logs from a failed xstatic release job. It appears something is
> not set up right with this job.
>
> "can't open file 'xstatic_check_version.py': [Errno 2] No such file or
> directory"
>
> I missed it initially, but this release did not actually contain any
> functional
> change, so I think it is fine that it failed. We can just hold off on doing
> anything with it until there are actual changes made that need to be
> delivered.
>
> But it did at least act as a good pipecleaner in that it found this job
> failure. I don't know enough about the release job itself, but please feel
> free
> to reach out in the #openstack-release channel if there is anything the
> release
> team can do to help get this sorted out and ready for when an actual release
> is
> needed.
https://review.openstack.org/563752 should fix it,
Andreas
> Thanks,
> Sean
>
> - Forwarded message from z...@openstack.org -
>
> Date: Mon, 23 Apr 2018 17:03:18 +
> From: z...@openstack.org
> To: release-job-failu...@lists.openstack.org
> Subject: [Release-job-failures] Release of openstack/xstatic-angular-vis
> failed
> Reply-To: openstack-dev@lists.openstack.org
>
> Build failed.
>
> - xstatic-check-version
> http://logs.openstack.org/59/591c61a6bf706434e19de85809f4c37adc612280/release/xstatic-check-version/613f7fc/
> : FAILURE in 2m 23s
> - release-openstack-python release-openstack-python : SKIPPED
> - announce-release announce-release : SKIPPED
> - propose-update-constraints propose-update-constraints : SKIPPED
>
> ___
> Release-job-failures mailing list
> release-job-failu...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures
>
> - End forwarded message -
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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-dev] [docs] When should we say 'run as root' in the docs?
On 2018-04-20 00:11, Matt Riedemann wrote:
> How loose are we with saying things like, "you should run this as root"
> in the docs?
>
> I was triaging this nova bug [1] which is saying that the docs should
> tell you to run nova-status (which implies also nova-manage) as root,
> but isn't running admin-level CLIs implied that you need root, or
> something with access to those commands (sudo)?
>
> I'm not sure how prescriptive we should be with stuff like this in the
> docs because if we did start saying this, I feel like we'd have to say
> it everywhere.
>
> [1] https://bugs.launchpad.net/nova/+bug/1764530
We use in openstack-manuals "# root-command" and "$ non-root command", see:
https://docs.openstack.org/install-guide/common/conventions.html
so, just add the "#" for thse.
But looking at
https://git.openstack.org/cgit/openstack/nova/tree/doc/source/install/verify.rst#n103,
it is there - so, closed invalid IMHO,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [kolla][stable][tc] Kolla deployment guide link is missing on docs.o.o
On 2018-04-16 11:52, Jeffrey Zhang wrote:
> Seems kolla deployment guide doc link is missing here[0]. But it exists
> on pike[1] and ocata[2]
>
> How could we fix this?
See https://docs.openstack.org/doc-contrib-guide/doc-index.html and sent
a patch for openstack-manuals repository,
Andreas
> [0] https://docs.openstack.org/queens/deploy/
> [1] https://docs.openstack.org/pike/deploy/
> [2] https://docs.openstack.org/ocata/deploy/
>
> --
> Regards,
> Jeffrey Zhang
> Blog: http://xcodest.me <http://xcodest.me/>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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
Re: [openstack-dev] [openstack-infra][openstack-zuul-jobs]Questions about playbook copy module
On 2018-04-06 11:20, Xinni Ge wrote:
> Sorry, forgot to reply to the mail list.
>
> On Fri, Apr 6, 2018 at 6:18 PM, Xinni Ge <xinni.ge1...@gmail.com
> <mailto:xinni.ge1...@gmail.com>> wrote:
>
> Hi, Andreas.
>
> Thanks for reply. This is the link of log I am seeing.
>
> http://logs.openstack.org/39/39067dbc1dee99d227f8001595633b5cc98cfc53/release/xstatic-check-version/9172297/ara-report/
>
> <http://logs.openstack.org/39/39067dbc1dee99d227f8001595633b5cc98cfc53/release/xstatic-check-version/9172297/ara-report/>
>
thanks, your analysis is correct, seem we seldom release xstatic packages ;(
fix is at https://review.openstack.org/559300
Once that is merged, an infra-root can rerun the release job - please
ask on #openstack-infra IRC channel,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [openstack-infra][openstack-zuul-jobs]Questions about playbook copy module
On 2018-04-06 10:53, Xinni Ge wrote:
> Hello there,
>
> I have some questions about the value of parameter `dest` of copy module
> in this file.
>
> openstack-zuul-jobs/playbooks/xstatic/check-version.yaml
> Line:6 dest: xstatic_check_version.py
>
> Ansible documents describe `dest` as "Remote absolute path where the
> file should be copied to".
> (http://docs.ansible.com/ansible/devel/modules/copy_module.html#id2)
>
> I am not quite familiar with ansible but maybe it could be `{{
> zuul.executor.log_root
> }}/openstack-zuul-jobs/playbooks/xstatic/check-version.yaml` or
> something similar ?
>
> Actually I ran into the problem trying to release a new xstatic package.
> The release patch was merged but fail to execute the release job. Just
> wondering whether or not it could be the reason of the failure.
Could you share a link to the logs for the job that failed, please?
> I am not sure about how to debug this, or how to re-launch the release job.
> I am very appreciate of it if anybody could kindly help me.
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [requirements][neutron] Depending on pypi versions
On 2018-03-19 14:24, Gary Kotton wrote: > The change will need to be in all of the decomposed projects - > http://codesearch.openstack.org/?q=install_cmd%20-U=nope== > Good catch! Will you do those, please? (once confirmed that this is the right change), Andreas > > On 3/19/18, 3:18 PM, "Gary Kotton" <gkot...@vmware.com> wrote: > > Thanks!! Will check if it now > > On 3/19/18, 3:15 PM, "Andreas Jaeger" <a...@suse.com> wrote: > > On 2018-03-19 14:01, Gary Kotton wrote: > > The issue is that since the change below - > > https://review.openstack.org/553045 - we are not picking up the > latest > > neutron master code. > > I see neutron installed: > > > http://logs.openstack.org/45/553045/1/gate/openstack-tox-pep8/5347981/job-output.txt.gz#_2018-03-15_13_58_12_552258 > > But later it's downgraded - like it's done for the other requirements > you have. So, this uncovered a problem in your install. > > pip install -U breaks it, please double check that this does the right > thing: > > https://review.openstack.org/554222 > > Andreas > > > > > > > *From: *Thomas Morin <thomas.mo...@orange.com> > > *Organization: *Orange S.A. > > *Reply-To: *OpenStack List <openstack-dev@lists.openstack.org> > > *Date: *Monday, March 19, 2018 at 1:46 PM > > *To: *OpenStack List <openstack-dev@lists.openstack.org> > > *Subject: *Re: [openstack-dev] [requirements][neutron] Depending on > pypi > > versions > > > > > > > > Hi Gary, > > > > > > > > See > > > > > http://lists.openstack.org/pipermail/openstack-dev/2018-March/128311.html > > > > > > > >> Note that thanks to the tox-siblings feature, we really continue to > > > >> install neutron and horizon from git - and not use the versions in > > > >> the global-requirements constraints file, > > > > > > > > I think it is worth adding a comment in (test-)requirements.txt > that the > > OpenStack CI is overriding the version and uses git. > > > > > > > > -Thomas > > > > > > > > > > > > Gary Kotton, 2018-03-19 11:25: > > > > Hi, > > > > The change > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_requirements_commit_35653e8c5044bff1059f50a82b6065176eea=DwIGaQ=uilaK90D4TOVoH58JNXRgQ=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw=438_Ni4AJ-nteg3SAstWzssFEcYN8k5BoSslcDtkSEU=nkowIZ6GVGMJAfMtR4XliFZhODdtly2gsBTr8k9wFFY= > > has created some issues with decomposed neutron plugins. Let me > try > > and give an example to explain. > > > > Say for example a patch landed in neutron master that exposed > > feature X. Now if a decomposed plugin wants to consume this it > will > > fail as the decomposed plugin will pull in the latest tag. > > > > Does this mean for each new feature that we wish to consume we > will > > need to update neutron tags? > > > > Please advise. > > > > Thanks > > > > Gary > > > > > __ > > > > OpenStack Development Mailing List (not for usage questions) > > > > Unsubscribe: openstack-dev-requ...@lists.openstack.org > > > <mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe > > > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > > > __ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
Re: [openstack-dev] [requirements][neutron] Depending on pypi versions
On 2018-03-19 14:01, Gary Kotton wrote:
> The issue is that since the change below -
> https://review.openstack.org/553045 - we are not picking up the latest
> neutron master code.
I see neutron installed:
http://logs.openstack.org/45/553045/1/gate/openstack-tox-pep8/5347981/job-output.txt.gz#_2018-03-15_13_58_12_552258
But later it's downgraded - like it's done for the other requirements
you have. So, this uncovered a problem in your install.
pip install -U breaks it, please double check that this does the right
thing:
https://review.openstack.org/554222
Andreas
>
>
> *From: *Thomas Morin <thomas.mo...@orange.com>
> *Organization: *Orange S.A.
> *Reply-To: *OpenStack List <openstack-dev@lists.openstack.org>
> *Date: *Monday, March 19, 2018 at 1:46 PM
> *To: *OpenStack List <openstack-dev@lists.openstack.org>
> *Subject: *Re: [openstack-dev] [requirements][neutron] Depending on pypi
> versions
>
>
>
> Hi Gary,
>
>
>
> See
>
> http://lists.openstack.org/pipermail/openstack-dev/2018-March/128311.html
>
>
>
>> Note that thanks to the tox-siblings feature, we really continue to
>
>> install neutron and horizon from git - and not use the versions in
>
>> the global-requirements constraints file,
>
>
>
> I think it is worth adding a comment in (test-)requirements.txt that the
> OpenStack CI is overriding the version and uses git.
>
>
>
> -Thomas
>
>
>
>
>
> Gary Kotton, 2018-03-19 11:25:
>
> Hi,
>
> The change
>
> https://github.com/openstack/requirements/commit/35653e8c5044bff1059f50a82b6065176eea
> has created some issues with decomposed neutron plugins. Let me try
> and give an example to explain.
>
> Say for example a patch landed in neutron master that exposed
> feature X. Now if a decomposed plugin wants to consume this it will
> fail as the decomposed plugin will pull in the latest tag.
>
> Does this mean for each new feature that we wish to consume we will
> need to update neutron tags?
>
> Please advise.
>
> Thanks
>
> Gary
>
> __
>
> OpenStack Development Mailing List (not for usage questions)
>
> Unsubscribe: openstack-dev-requ...@lists.openstack.org
> <mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe
>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [requirements][neutron] Depending on pypi versions
On 2018-03-19 12:25, Gary Kotton wrote:
> Hi,
>
> The change
> https://github.com/openstack/requirements/commit/35653e8c5044bff1059f50a82b6065176eea
> has created some issues with decomposed neutron plugins. Let me try and
> give an example to explain.
>
> Say for example a patch landed in neutron master that exposed feature X.
> Now if a decomposed plugin wants to consume this it will fail as the
> decomposed plugin will pull in the latest tag.
It will pull in git master if your job lists openstack/neutron in
required-projects.
It will pull in the latest tag if it's not listed.
Most repos are already setup with required-projects set to this - but
please double check.
> Does this mean for each new feature that we wish to consume we will need
> to update neutron tags?
No,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [requirements][kolla] new requirements change on upper-constraints.txt break horizon & neutron
On 2018-03-16 13:22, Jeffrey Zhang wrote:
> kolla install openstack packages through master tarball file on kolla
> master branch[0].
>
> On stable branch, kolla install through neutron tag tarball. But i think
> there will be also
> some issue here. How about i want to install neutron-12.0.1.tar.gz,
> whereas neutron===12.0.0
> exist in the upper-constraints.txt file?
>
> [0] http://tarballs.openstack.org/neutron/neutron-master.tar.gz
I see, thanks.
Let me restore https://review.openstack.org/#/c/553030, it should get us
moving forward here - and then we can figure out whether there are other
options,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][neutron][kolla] tools/tox_install changes - breakage with constraints
On 2018-03-16 11:49, Jeffrey Zhang wrote:
> Now it breaks the kolla's master branch jobs. And have to remove the
> "horizon"
> and "neutron" in the upper-constraints.txt file. check[1][2].
>
> i wanna know what's the correct way to install horizon develop
> branch with upper-constraints.txt file?
>
>
> [1]
> https://review.openstack.org/#/c/549456/4/docker/neutron/neutron-base/Dockerfile.j2
> <https://review.openstack.org/#/c/549456/4/docker/neutron/neutron-base/Dockerfile.j2>
> [2] https://review.openstack.org/#/c/549456/4/docker/horizon/Dockerfile.j2
> <https://review.openstack.org/#/c/549456/4/docker/horizon/Dockerfile.j2>
Sorry, that is too much magic for me to be able to help you.
What are those doing? How do you install today? Please give me some
instructions
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [requirements][kolla] new requirements change on upper-constraints.txt break horizon & neutron
On 2018-03-16 11:42, Thomas Morin wrote:
> This is related to the topic in "[horizon][neutron] tools/tox_install
> changes - breakage with constraints".
>
> proposes to remove these projects from upper-constraints (for a
> different reason)
> https://review.openstack.org/#/c/552865
> <https://review.openstack.org/#/c/552865/> that adds other projects to
> global-requirements, explicitly postpone their addition to
> upper-constraints to a later step
>
> Perhaps neutron and horizon should be removed from upper-constraints for
> now ? (ie restore https://review.openstack.org/#/c/553030 ?)
Yes, that would be one option. but I like to understand whether that
would be a temporary solution - or the end solution.
Jeffrey, how exactly are you installing neutron? From git? From tarballs?
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all][requirements] a plan to stop syncing requirements into projects
thanks for the proposal, Doug. I need an example to understand how
things will work out...
so, let me use a real-life example (version numbers are made up):
openstackdocstheme uses sphinx and needs sphinx 1.6.0 or higher but
knows version 1.6.7 is broken.
So, openstackdocstheme would add to its requirements file:
sphinx>=1.6.0,!=1.6.7
Any project might assume they work with an older version, and have in
their requirements file:
Sphinx>=1.4.0
openstackdocstheme
The global requirements file would just contain:
openstackdocstheme
sphinx!=1.6.7
The upper-constraints file would contain:
sphinx===1.7.1
If we need to block sphinx 1.7.x - as we do right now - , we only update
requirements repo to have in global requirements file:
openstackdocstheme
sphinx!=1.6.7,<1.7.0
and have in upper-constraints:
sphinx===1.6.6
But projects should *not* add the cap to their projects like:
sphinx>=1.6.0,!=1.6.7,<=1.7.0
Is that all correct?
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints
On 2018-03-15 10:05, Thomas Morin wrote:
> Hi Andreas, all,
>
> Andreas Jaeger, 2018-03-14 20:46:
>> Note that thanks to the tox-siblings feature, we really continue to
>> install neutron and horizon from git - and not use the versions in the
>> global-requirements constraints file.
>
> This addresses my main concern, which was that by removing
> tools/tox_install.sh we would end up not pulling master from git.
>
> The fact that we do keep pulling from git wasn't explicit AFAIK in any
> of the commit messages of the changes I had to look at to understand
> what was being modified.
Sorry for not mentioning that.
> I concur with Akihiro's comment, and would go slightly beyond that:
> ideally the solution chosen would not only technical work, but would
> reduce the ahah-there-is-magic-behind-the-scene effect, which is a pain
> I believe for many: people new to the community face a steeper learning
> curve, people inside the community need to spend time adjust, and infra
> folks end up having to document or explain more. In this precise case,
> the magic behind the scene (ie. the tox-siblings role) may lead to
> confusion for packagers (why our CI tests as valid is not what appears
> in requirements.txt) and perhaps people working in external communities
> (e.g. [1]).
The old way - included some magic as well ;(
I agree with Doug - we need to architect our dependencies better to
avoid these problems and hacks,
Andreas
> Best,
>
> -Thomas
>
> [1]
> http://docs.opnfv.org/en/latest/submodules/releng-xci/docs/xci-overview.html#xci-overview
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints
On 2018-03-14 20:46, Andreas Jaeger wrote:
> On 2018-03-14 20:39, Andreas Jaeger wrote:
>> We now have neutron and horizon in global-requirements and do not need
>> to install them anymore with tools/tox_install.sh.
>>
>> This allows to simplify our jobs and testing.
>>
>> Unfortunately, the merging caused now the projects that install neutron
>> and horizon via tools/tox_install to break with constraints.
>>
>> I'm currently pushing up changes for these using topic tox-siblings [1].
>>
>> Please merge those - and if you're pushing up changes yourself, let's
>> use the same topic.
>>
>> Sorry for the breakage ;(
>> Andreas
>>
>> [1] Links
>> https://review.openstack.org/#/q/topic:tox-siblings+(status:open+OR+status:merged)
>>
>
> Note that thanks to the tox-siblings feature, we really continue to
> install neutron and horizon from git - and not use the versions in the
> global-requirements constraints file,
Btw. this work is part of what Monty proposed in
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124676.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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints
On 2018-03-14 20:39, Andreas Jaeger wrote:
> We now have neutron and horizon in global-requirements and do not need
> to install them anymore with tools/tox_install.sh.
>
> This allows to simplify our jobs and testing.
>
> Unfortunately, the merging caused now the projects that install neutron
> and horizon via tools/tox_install to break with constraints.
>
> I'm currently pushing up changes for these using topic tox-siblings [1].
>
> Please merge those - and if you're pushing up changes yourself, let's
> use the same topic.
>
> Sorry for the breakage ;(
> Andreas
>
> [1] Links
> https://review.openstack.org/#/q/topic:tox-siblings+(status:open+OR+status:merged)
>
Note that thanks to the tox-siblings feature, we really continue to
install neutron and horizon from git - and not use the versions in the
global-requirements constraints file,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints
We now have neutron and horizon in global-requirements and do not need
to install them anymore with tools/tox_install.sh.
This allows to simplify our jobs and testing.
Unfortunately, the merging caused now the projects that install neutron
and horizon via tools/tox_install to break with constraints.
I'm currently pushing up changes for these using topic tox-siblings [1].
Please merge those - and if you're pushing up changes yourself, let's
use the same topic.
Sorry for the breakage ;(
Andreas
[1] Links
https://review.openstack.org/#/q/topic:tox-siblings+(status:open+OR+status:merged)
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [cue] Retiring completely
cue has been retired as official project in mid 2016 [1], and talking
with previous PTL, it's time to retire the project completely.
I'm proposing the needed changes now,
Andreas
[1]
http://git.openstack.org/cgit/openstack/governance/tree/reference/legacy.yaml#n110
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [PTG] [Infra] [all] zuulv3 Job Template vs irrelevant files/branch var
On 2018-03-08 02:44, Ghanshyam Mann wrote:
> Hi All,
>
> Before PTG, we were discussing about Job Template and irrelevant files
> issues on multiple mailing thread [1].
>
> Both things does not work as expected and it leads to run the jobs on
> irrelevant files also and on excluded branch.
>
> In Dublin PTG, during infra help hours on Tuesday, we had talk on this
> topic and to find the best approach.
>
> First of all thanks to Jim for explaining the workflow of zuulv3 about
> selecting and integrating the matched jobs. How jobs are being matched
> and how variables like branch and irrelevant-files are being taken
> care between job definition and job template and project's pipeline
> list.
>
> Current issue (explained in ML [1]) is with the integrated-gate job
> template [2] where integrated job like tempest-full are being run.
> Other job template like 'system-required', 'openstack-python-jobs'
> etc.
>
> After discussion, It is found more complicated to solve these issues
> as of now and it might take time for Jim/infra team to come up with
> better way to handle job template and irrelevant_files/branch var etc.
>
> We talked about few possibilities like one way is to supersede the job
> template defined var by project's pipeline list. For example if
> irrelevant_files are defined by both job template and project's
> pipelines then ignore/skip the job template values of that var or all
> var. But this is just idea and not sure how feasible and best it can
> be.
>
> But till the best approach/solution is ready, we need to have some
> workaround as current issue cause running many jobs on unnecessary
> patches and consume lot of infra resources.
>
> We discussed few of the workaround mentioned below and we can go for
> one based on majority of people or infra team like/suggest-
> 1. Do not use integrated-gate template and let each project have the
> jobs in their pipeline list
> 2. Define all the irrelevant files for each projects in job template ?
> 3. Leave as it is.
>
> ..1
> http://lists.openstack.org/pipermail/openstack-dev/2018-February/127349.html
>
> http://lists.openstack.org/pipermail/openstack-dev/2018-February/127347.html
>
> ..2
> https://github.com/openstack-infra/openstack-zuul-jobs/blob/49cd964470c081005f671d6829a14dace2c9ccc2/zuul.d/zuul-legacy-project-templates.yaml#L82
I'm fine with option 2 for those projects that want to do some changes
for now.
Breaking up the integrated-gate will cause more maintenance problems.
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Retirement of astara repos?
On 2018-01-11 22:55, Mark McClain wrote:
> Sean, Andreas-
>
> Sorry I missed Andres’ message earlier in December about retiring astara.
> Everyone is correct that development stopped a good while ago. We attempted
> in Barcelona to find others in the community to take over the day-to-day
> management of the project. Unfortunately, nothing sustained resulted from
> that session.
>
> I’ve intentionally delayed archiving the repos because of background
> conversations around restarting active development for some pieces bubble up
> from time-to-time. I’ll contact those I know were interested and try for a
> resolution to propose before the PTG.
Mark, any update here?
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo.db] [all] please DO NOT IMPORT from oslo_db.tests.* ! projects doing this need to revert ASAP
On 2018-02-19 16:00, Michael Bayer wrote:
> Hi list -
>
> Apparently Cinder was misled by my deprecations within the
> oslo_db.sqlalchemy.test_base package of DbFixture and DbTestCase, and
> in https://review.openstack.org/#/c/522290/ the assumption was made
> that these should be imported from oslo_db.tests.sqlalchemy.This
> is an immense mistake on my part that I did not expect people to go
> looking for the same names elsewhere in private packages and now we
> have a serious downstream issue as these modules are not packaged, as
> well as the possibility that the oslo_db.tests. package is now locked
> in time and I have to add deprecations there also.
>
> If anyone knows of projects (or feels like helping me search) that are
> importing *anything* from oslo_db.tests these must be reverted ASAP.
cinder, glance, ironic,... see
http://codesearch.openstack.org/?q=oslo_db.tests=nope==
;(
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [all][i18n] Accepting translations for Queens
Could everybody import translations, please?
* for master so that you have translated releasenotes
* for stable/queens for the iminent Queens release. Note that this one
removes translated releasenotes, we only translate and publish
releasenotes from master.
Full list of open reviews:
https://review.openstack.org/#/q/status:open+topic:zanata/translations
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [infra] [all] project pipeline definition should stay in project-config or project side ?
On 2018-02-14 01:28, Ghanshyam Mann wrote:
> On Wed, Feb 14, 2018 at 12:06 AM, Paul Belanger <pabelan...@redhat.com> wrote:
>> On Tue, Feb 13, 2018 at 11:05:34PM +0900, gmann wrote:
>>> Hi Infra Team,
>>>
>>> I have 1 quick question on zuulv3 jobs and their migration part. From
>>> zuulv3 doc [1], it is clear about migrating the job definition and use
>>> those among cross repo pipeline etc.
>>>
>>> But I did not find clear recommendation that whether project's
>>> pipeline definition should stay in project-config or we should move
>>> that to project side.
>>>
>>> IMO,
>>> 'template' part(which has system level jobs) can stay in
>>> project-config. For example below part-
>>>
>>> https://github.com/openstack-infra/project-config/blob/e2b82623a4ab60261b37a91e38301927b9b6/zuul.d/projects.yaml#L10507-L10523
>>>
>>> Other pipeline definition- 'check', 'gate', 'experimental' etc should
>>> be move to project repo, mainly this list-
>>> https://github.com/openstack-infra/project-config/blob/master/zuul.d/projects.yaml#L10524-L11019
>>>
>>> If we move those past as mentioned above then, we can have a
>>> consolidated place to control the project pipeline for
>>> 'irrelevant-files', specific branch etc
>>>
>>> ..1 https://docs.openstack.org/infra/manual/zuulv3.html
>>>
>> As it works today, pipeline stanza needs to be in a config project[1]
>> (project-config) repo. So what you are suggestion will not work. This was
>> done
>> to allow zuul admins to control which pipelines are setup / configured.
>>
>> I am mostly curious why a project would need to modify a pipeline
>> configuration
>> or duplicate it into all projects, over having it central located in
>> project-config.
>
> pipeline stanza and configuration stay in project-config. I mean list
> of jobs defined in each pipeline for specific project for example
> here[2]. Now we have list of jobs for each pipeline in 2 places, one
> in project-config [2] and second in project repo[3].
>
> Issue in having it in 2 places:
> - No single place to check what all jobs project will run with what conditions
> - If we need to modify the list of jobs in pipeline or change other
> bits like irrelevant-files etc then it has to be done in
> project-config. So no full control by project side.
This should be explained in:
https://docs.openstack.org/infra/manual/zuulv3.html#what-to-convert
So, the standard templates/jobs - incl. PTI mandated ones - should stay
in project-config, you can move everything else in-tree,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all][infra] Automatically generated Zuul changes (topic: zuulv3-projects)
Please accept these changes so that they don't have to be created for
the stable/queens branch,
Andreas
On 2018-01-31 18:59, James E. Blair wrote:
> Hi,
>
> Occasionally we will make changes to the Zuul configuration language.
> Usually these changes will be backwards compatible, but whether they are
> or not, we still want to move things forward.
>
> Because Zuul's configuration is now spread across many repositories, it
> may take many changes to do this. I'm in the process of making one such
> change now.
>
> Zuul no longer requires the project name in the "project:" stanza for
> in-repo configuration. Removing it makes it easier to fork or rename a
> project.
>
> I am using a script to create and upload these changes. Because changes
> to Zuul's configuration use more resources, I, and the rest of the infra
> team, are carefully monitoring this and pacing changes so as not to
> overwhelm the system. This is a limitation we'd like to address in the
> future, but we have to live with now.
>
> So if you see such a change to your project (the topic will be
> "zuulv3-projects"), please observe the following:
>
> * Go ahead and approve it as soon as possible.
>
> * Don't be strict about backported change ids. These changes are only
> to Zuul config files, the stable backport policy was not intended to
> apply to things like this.
>
> * Don't create your own versions of these changes. My script will
> eventually upload changes to all affected project-branches. It's
> intentionally a slow process, and attempting to speed it up won't
> help. But if there's something wrong with the change I propose, feel
> free to push an update to correct it.
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [CI][Keystone][Requirements][Release] What happened to the gate on Feb 4th?
On 2018-02-05 05:44, Qiming Teng wrote:
> Starting about 24 hours ago, we have been notified CI gate failure
> although we haven't changed anything to our project locally. Before that
> we have spent quite some time making the out-of-tree tempest plugins
> work on gate.
What is *your* project? PLease provide also links to full failure logs,
Andreas
> After checking the log again and again ... we found the following logs
> from Keystone:
>
> Feb 05 03:31:12.609492 ubuntu-xenial-ovh-gra1-0002362092
> devstack@keystone.service[24845]: WARNING keystone.common.wsgi [None
> req-dfcbf106-fbf5-41bd-9012-3c65d1de5f9a None admin] Could not find
> project: service.: ProjectNotFound: Could not find project: service.
>
> Feb 05 03:31:13.845694 ubuntu-xenial-ovh-gra1-0002362092
> devstack@keystone.service[24845]: WARNING keystone.common.wsgi [None
> req-50feed46-7c15-425d-bec7-1b4a7ccf6859 None admin] Could not find
> service: clustering.: ServiceNotFound: Could not find service:
> clustering.
>
> Feb 05 03:31:12.552647 ubuntu-xenial-ovh-gra1-0002362092
> devstack@keystone.service[24845]: WARNING keystone.common.wsgi [None
> req-0a5e660f-dad6-4779-aea4-dd6969c728e6 None admin] Could not find
> domain: Default.: DomainNotFound: Could not find domain: Default.
>
> Feb 05 03:31:12.441128 ubuntu-xenial-ovh-gra1-0002362092
> devstack@keystone.service[24845]: WARNING keystone.common.wsgi [None
> req-7eb9ed90-28fc-40aa-8a41-d560f7a156c9 None admin] Could not find
> user: senlin.: UserNotFound: Could not find user: senlin.
>
> Feb 05 03:31:12.336572 ubuntu-xenial-ovh-gra1-0002362092
> devstack@keystone.service[24845]: WARNING keystone.common.wsgi [None
> req-19e52d02-5471-49a2-8acd-360199d8c6e0 None admin] Could not find
> role: admin.: RoleNotFound: Could not find role: admin.
>
> Feb 05 03:28:33.797665 ubuntu-xenial-ovh-gra1-0002362092
> devstack@keystone.service[24845]: WARNING keystone.common.wsgi [None
> req-544cd822-18a4-4f7b-913d-297716418239 None admin] Could not find
> user: glance.: UserNotFound: Could not find user: glance.
>
> Feb 05 03:28:29.993214 ubuntu-xenial-ovh-gra1-0002362092
> devstack@keystone.service[24845]: WARNING py.warnings [None
> req-dc411d9c-6ab9-44e3-9afb-20e5e7034f12 None admin]
> /usr/local/lib/python2.7/dist-packages/oslo_policy/policy.py:865:
> UserWarning: Policy identity:create_endpoint failed scope check. The
> token used to make the request was project scoped but the policy
> requires ['system'] scope. This behavior may change in the future where
> using the intended scope is required
>
> Feb 05 03:28:29.920892 ubuntu-xenial-ovh-gra1-0002362092
> devstack@keystone.service[24845]: WARNING keystone.common.wsgi [None
> req-32a4a378-d6d3-411e-9842-2178e577af27 None admin] Could not find
> service: compute.: ServiceNotFound: Could not find service: compute.
>
>
>
> --
>
> So I'm wondering what the hack happened? Keystone version bump?
> Devstack changed? Tempest settings changed?
> Why are we merging these changes near the end of a cycle when people are
> focusing on stabilizing things?
>
> Any hints on these are highly appreciated.
--
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [trove] Retiring the trove-integration repository, final call
On 2018-01-26 22:22, Manoj Kumar wrote:
> Initial indication was provided in July last year, that the
> trove-integration repository was going away.
> All the elements have been merged into trove, and are being maintained
> there.
>
> I do not believe anyone spoke up then. If anyone is depending on the
> separate repository, do speak up.
Please remove it completely from the CI system - follow
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project
* abandon these two open reviews:
https://review.openstack.org/#/q/project:openstack/trove-integration+is:open
* Remove the project from project-config
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all][infra] Automatically generated Zuul changes (topic: zuulv3-projects)
On 2018-02-01 05:49, Takashi Yamamoto wrote:
> [...]
>> * Don't create your own versions of these changes. My script will
>> eventually upload changes to all affected project-branches. It's
>> intentionally a slow process, and attempting to speed it up won't
>> help. But if there's something wrong with the change I propose, feel
>> free to push an update to correct it.
> 1. is it ok to create my version of the change when making other
> changes to the file? eg. https://review.openstack.org/#/c/538200/
If you add a *new* zuul.yaml file, do not add the project name stanza.
His scripts will not catch new additions.
If you change an existing file, wait for Jim's change.
> 2. as a reviewer, what should i do to the similar changes which is not yours?
> https://review.openstack.org/#/q/topic:zuulv3-projects+NOT+owner:%22James+E.+Blair+%253Ccorvus%2540inaugust.com%253E%22
I would block any new ones with a reference to the message. There's
really no sense in doing those changes and cause extra work,
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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
