[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-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-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-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
[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-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-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-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
Re: [openstack-dev] [neutron][lbaas][neutron-lbaas][octavia] Announcing the deprecation of neutron-lbaas and neutron-lbaas-dashboard
On 2018-01-31 22:58, Akihiro Motoki wrote:
> I don't think we need to drop translation support NOW (at least for
> neutron-lbaas-dashboard).
> There might be fixes which affects translation and/or there might be
> translation improvements.
> I don't think a deprecation means no translation fix any more. It
> sounds too aggressive.
> Is there any problem to keep translations for them?
Reading the whole FAQ - since bug fixes are planned, translations can
merge back. So, indeed we can keep translation infrastructure set up.
I recommend to translators to remove neutron-lbaas-dashboard from the
priority list,
Andreas
> Akihiro
>
> 2018-02-01 3:28 GMT+09:00 Andreas Jaeger <a...@suse.com>:
>> In that case, I suggest to remove translation jobs for these 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 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 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] how to update published pike docs
On 2018-01-31 18:22, Jeremy Stanley wrote:
> On 2018-01-31 12:07:30 -0500 (-0500), Brian Rosmaita wrote:
> [...]
>> What do we need to do to get the docs.o.o to show the fixed docs? Is
>> it something we need to do on the glance side, or does it have to be
>> fixed somewhere else?
>
> Looks like that commit merged toward the end of September, so
> identifying why the build failed (or never ran) will be tough. I've
> reenqueued the tip of your stable/pike branch into the post
> pipeline, but because that pipeline runs at a low priority it may
> still be a few hours before that completes (commit 06af2eb in the
> status display). Once it does, we should hopefully at least have
> logs detailing the problem though if all goes well you'll have
> properly updated documentation there instead.
That fixed 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] [neutron][lbaas][neutron-lbaas][octavia] Announcing the deprecation of neutron-lbaas and neutron-lbaas-dashboard
In that case, I suggest to remove translation jobs for these 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 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] [infra] how to update published pike docs
On 2018-01-31 18:07, Brian Rosmaita wrote:
> Hello Docs people,
>
> The glance install docs currently published on docs.o.o don't include
> a correction we merged a while back, and I get a few bug reports filed
> on this particular problem every week. (It's great that people are
> willing to file corrections, but the duplicates are really piling up!)
> Anyway, here's what's happening:
>
> published docs:
> https://docs.openstack.org/glance/pike/install/install-debian.html
> (can't see the create db stuff -- you may need to look at the next
> link first to see what I mean)
>
> docs in github:
> https://github.com/openstack/glance/blob/stable/pike/doc/source/install/install-debian.rst
> (can see the create db stuff)
>
> glance stable/pike in the repo:
> http://git.openstack.org/cgit/openstack/glance?h=stable%2Fpike
> You can see stable/pike head is at the fix.
>
> What do we need to do to get the docs.o.o to show the fixed docs? Is
> it something we need to do on the glance side, or does it have to be
> fixed somewhere else?
please check the post job for this, I assume it never run or failed.
If it did not run, just push a new change out.
If it failed, let's fix it first.
Btw. to get logs, see
https://docs.openstack.org/infra/manual/developers.html#post-processing
And docs team has nothing to do here, this is pure infra - so updated tags.
If you have further questions, let's discuss on #openstack-infra,
Andreas
> thanks,
> brian
>
> __
> 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] [devstack] Broken repo on devstack-plugin-container for Fedora
On 2018-01-24 14:14, Daniel Mellado wrote:
> Hi everyone,
>
> Since today, when I try to install devstack-plugin-container plugin over
> fedora. It complains in here [1] about not being able to sync the cache
> for the repo with the following error [2].
>
> This is affecting me on Fedora26+ from different network locations, so I
> was wondering if someone from suse could have a look (it did work for
> Andreas in opensuse... thanks in advance!)
Just a heads up:
So, one problem: The signing key was expired. The key was extended but
not used - now the repo has been published again using the extended key.
So, download works.
AFAIU there's still some problem where dnf is not happy with - Daniel is
investigating,
Andreas
>
> [1]
> https://github.com/openstack/devstack-plugin-container/blob/master/devstack/lib/docker#L164-L170
>
> [2] http://paste.openstack.org/show/652041/
>
> __
> 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][congress] getting requirements updates for congress-dashboard
On 2018-01-24 23:54, Eric K wrote:
> Hi all,
>
> I'm having some trouble getting congress-dashboard to receive requirements
> updates from global-requirements.
>
> The check-requirements job seems to be configured, but does NOT seem to be
> running:
> http://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul.d/pr
> ojects.yaml#n4246
>
> The project is also listed in the requirements repo:
> http://git.openstack.org/cgit/openstack/requirements/tree/projects.txt#n24
>
> Any hints on what may be wrong? Thanks very much!
You can run the requirements update manually on your repository, the
README of requirements explains why. That will allow you to see what fails.
Also, you can check the output of the proposal job yourself, go to:
http://zuul.openstack.org/builds.html?job_name=propose-update-requirements
and look at the log files, you should find:
http://logs.openstack.org/c1/c15d9830375196c9a6c0c111073e1148bf192b4b/post/propose-update-requirements/32b7875/job-output.txt.gz#_2018-01-24_01_50_58_527699
So, remove that obsolete entry and check that the rest of the file is
fine with manually running the update,
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] [cerberus][sticks] Retire openstack/*cerberus* and sticks
On 2017-12-09 15:57, Andreas Jaeger wrote:
> Anthony, Christophe, Gauvin,
>
> The last merge to one of the cerberus repositories was December 2015, I
> propose to retire the repositories to avoid people submitting changes to
> them.
>
> See
> https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project
> on how to retire a project.
>
> If you need help with retiring, please tell me,
FYI, Gauvain started the retirement process and included sticks as well:
https://review.openstack.org/#/c/535660/
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
[openstack-dev] [craton] Retirement of craton and python-cratonclient
Craton development is frozen since around March 2017, I've discussed
with Sulochan and will start the retirement process now,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
__
OpenStack 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][masakari][api] masakari service-type, docs, api-ref and releasenotes
On 2018-01-17 20:23, Monty Taylor wrote:
> Hey everybody,
>
> I noticed today while preparing patches to projects that are using
> openstacksdk that masakari is not listed in service-types-authority. [0]
>
> I pushed up a patch to fix that [1] as well as to add api-ref, docs and
> releasenotes jobs to the masakari repo so that each of those will be
> published appropriately.
>
> As part of doing this, it came up that 'ha' is a pretty broad
> service-type and that perhaps it should be 'compute-ha' or 'instance-ha'.
>
> The service-type is a unique key for identifying a service in the
> catalog, so the same service-type cannot be shared amongst openstack
> services. It is also used for api-ref publication (to
> https://developer.openstack.org/api-ref/{service-type} ) - and in
> openstacksdk as the name used for the service attribute on the
> Connection object. (So the service-type 'ha' would result in having
> conn.ha on an openstack.connection.Connection)
>
> We do support specifying historical aliases. Since masakari has been
> using ha up until now, we'll need to list is in the aliases at the very
> least.
>
> Do we want to change it? What should we change it to?
Yes, I would change it - instance-ha sounds best seeing that the
governance file has:
" service: Instances High Availability Service"
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] [Zuul] requirements-check FAILURE
On 2018-01-17 23:01, Kwan, Louie wrote:
> Would like to add the following module to openstack.masakari project
>
> https://github.com/pytransitions/transitions
>
> Got the following error with zuul requirements-check
>
> Requirement set([Requirement(package=u'transitions', location='',
> specifiers='>=0.6.4', markers=u'', comment='', extras=frozenset([]))]) not in
> openstack/requirements
>
> http://logs.openstack.org/88/534888/3/check/requirements-check/edec7bf/ara/
>
> Any tip or insight to fix it?
Yes, read on how to add it:
https://docs.openstack.org/requirements/latest/
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][docs] Fixing report a bug link for documentation
I noticed that the report-a-bug feature was giving wrong information for
the Neutron api-guide, it missed to give the giturl and SHA of latest
commit.
This comes from not fully initialising the openstackdocstheme.
I fixed this for neutron-lib with change
https://review.openstack.org/534666 .
If you're interested in having correct information, check our setup,
especially for api-ref and api-guide documents, and review the content
of the report a bug link (click on the "Bug" icon in the upper right
corner).
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] [os-api-ref][doc] Adding openstack-doc-core to os-api-ref
On 2018-01-15 16:11, Stephen Finucane wrote:
> On Thu, 2018-01-04 at 15:39 +, Stephen Finucane wrote:
>> I'm not sure what the procedure for this is but here goes.
>>
>> I've noticed that the 'os-api-ref' project seems to have its own group
>> of cores [1], many of whom are no longer working on OpenStack (at
>> least, not full-time), and has a handful of open patches against it
>> [2]. Since the doc team has recently changed its scope from writing
>> documentation to enabling individual projects to maintain their own
>> docs, we've become mainly responsible for projects like 'openstack-doc-
>> theme'. Given that the 'os-api-ref' project is a Sphinx thing required
>> for multiple OpenStack projects, it seems like something that
>> could/should fall into the doc team's remit.
>>
>> I'd like to move this project into the remit of the 'openstack-doc-
>> core' team, by way of removing the 'os-api-ref-core' group or adding
>> 'openstack-doc-core' to the list of included groups. In both cases,
>> existing active cores will be retained. Do any of the existing 'os-api-
>> ref' cores have any objections to this?
>
> It's been two weeks with no -1s, so we've gone ahead and done this.
> Thanks, everyone.
Note that the ownership is already in government repo since May 2016
(https://review.openstack.org/317686),
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,
we can always unretire a repository - it's just a revert of the retire
patches...
So, if you don't hear anything by then, let's retire,
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] [qa][neutron][octavia][horizon][networking-l2gw] Renaming tox_venvlist in Zuul v3 run-tempest
The Zuul v3 tox jobs use "tox_envlist" to name the tox environment to
use, the tempest run-tempest role used "tox_venvlist" with an extra "v"
in it. This lead to some confusion and a wrong fix, so let's be
consistent across these jobs.
I've just pushed changes under the topic tox_envlist to sync these.
To have working jobs, I needed the usual rename dance: Add the new
variable, change the job, remove the old one.
Neutron, octavia, horizon, networking-l2gw team, please review and merge
the first one quickly.
https://review.openstack.org/#/q/topic:tox_envlist
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] [ceilometer] Retiring ceilometerclient
On 2018-01-11 07:48, Thomas Bechtold wrote:
> Hi,
>
> On 11.01.2018 01:18, gordon chung wrote:
>>
>>
>> On 2018-01-10 06:44 PM, Doug Hellmann wrote:
>>>> It's worth pointing out that openstacksdk has ceilometer REST API
>>>> support in it, although it is special-cased since ceilometer was
>>>> retired
>>>> before we even made the service-types-authority:
>>
>> so ceilometer's REST API does not exist anymore. i don't believe it was
>> even packaged in Pike (at least i don't have have an rpm for it in my
>> environment).
>
> It was at lease for openSUSE:
> https://build.opensuse.org/package/show/Cloud:OpenStack:Pike/openstack-ceilometer
Wrong package - statement still true:-)
https://build.opensuse.org/package/show/Cloud:OpenStack:Pike/python-ceilometerclient
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 Evoque Projects
On 2018-01-10 14:00, Sean McGinnis wrote:
> While doing some cleanup, I noticed the Evoque projects (openstack/evoque and
> openstack/evoque-ui) have not had any activity since the beginning of 2016,
> with the team's last official meeting held in December of 2015.
>
> I contacted the core team for this project, and luckily they were very
> responsive in letting me know that this project is indeed no longer active and
> should probably be retired.
>
> Unless I hear otherwise soon, I will be starting the process to retire this
> project and clean up things like its zuul and gerrit configuration.
Thanks, see also
http://lists.openstack.org/pipermail/openstack-dev/2017-December/125352.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] [os-vif]
On 2018-01-09 07:00, Sriharsha Basavapatna wrote:
> Hi,
>
> I've uploaded a patch for review:
> https://review.openstack.org/#/c/531674/
>
> This is the first time I'm submitting a patch on openstack. I'd like
Welcome to OpenStack, Harsha. Please read
https://docs.openstack.org/infra/manual/developers.html if you haven't.
I see that your change fails the basic tests, you can run these locally
as follows to check that your fixes will pass:
tox -e pep8
tox -e py27
Andreas
> to add code reviewers on this patch. I'd appreciate if you could point
> me to any guidelines on how to pick reviewers for a given project
> (os-vif library in this case).
>
> Thanks,
> -Harsha
>
> __
> 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] [os-vif]
On 2018-01-09 07:00, Sriharsha Basavapatna wrote:
> Hi,
>
> I've uploaded a patch for review:
> https://review.openstack.org/#/c/531674/
>
> This is the first time I'm submitting a patch on openstack. I'd like
> to add code reviewers on this patch. I'd appreciate if you could point
> me to any guidelines on how to pick reviewers for a given project
> (os-vif library in this case).
In general, there's no need to add core reviewers to a review. Each of
us have their own dashboards or watch projects that we review and review
as time permits.
Since your change is failing the testsuite: Please fix tests first!
os-vif is part of nova, so if you want to discuss about it, best to join
the #openstack-nova freenode 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] [Release-job-failures][kuryr][release] Tag of openstack/kuryr-kubernetes failed
On 2018-01-03 16:46, Doug Hellmann wrote:
> Excerpts from zuul's message of 2018-01-03 14:46:48 +:
>> Build failed.
>>
>> - publish-openstack-releasenotes
>> http://logs.openstack.org/bf/bfe7b055d19537f2c59125678410b3d25d2cb61d/tag/publish-openstack-releasenotes/1d51c55/
>> : FAILURE in 5m 04s
>>
>
> Based on
> http://logs.openstack.org/bf/bfe7b055d19537f2c59125678410b3d25d2cb61d/tag/publish-openstack-releasenotes/1d51c55/ara/result/43697d56-2d99-457f-b8e8-44d6d7fcba33/
> it looks like the issue is an incomplete list of dependencies:
>
> Running Sphinx v1.6.5
> making output directory...
>
> Exception occurred:
> File "conf.py", line 60, in
> ImportError: No module named kuryr_kubernetes
> The full traceback has been saved in /tmp/sphinx-err-iNXwM7.log, if you want
> to report the issue to the developers.
> Please also report this if it was a user error, so that a better error
> message can be provided next time.
> A bug report can be filed in the tracker at
> <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
Fix is available since End of November:
https://review.openstack.org/#/c/523290/ but not reviewed yet ;(
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] [infra] Retire puppet-apps_site repo
With the retirement of the app-catalog repos and the decommision of
apps.openstack.org, we can retire this repository as well.
I'm proposing a couple of changes with topic:retire-puppet-apps
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] [evoque] Retiring evoque projects
Evoque cores,
The last change merged to the evoque projects was January 2016, I
propose to retire the projects to avoid people commiting to them and
infra updating their jobs needlessly.
See
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project
on how to retire them.
If you need help retiring, 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
[openstack-dev] [cerberus] Retire openstack/*cerberus*
Anthony, Christophe, Gauvin,
The last merge to one of the cerberus repositories was December 2015, I
propose to retire the repositories to avoid people submitting changes to
them.
See
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project
on how to retire a project.
If you need help with retiring, 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
[openstack-dev] [astara] Retire openstack/*astara*
Ryan, Mark,
nothing has merged to the OpenStack astara repos since over a year (last
merge was October 2016).
I suggest to retire the repos completely as explained at
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project
to avoid people to submit patches to it.
Could you do the steps, please?
I'm happy to help you with it, if you prefer,
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] Playbooks need extension, otherwise job will fail
Playbooks in Zuul v3 config files now need the file extension like
".yaml". There are still a few ancient changes for zuul.yaml that do not
have those - and some repos that did not take in Jim's update.
If your jobs are failing with errors that playbooks cannot be found, add
the file extension - or merge the open change. See the list of open
changes on what needs to be done.
Open changes:
https://review.openstack.org/#/q/topic:zuulv3-paths+status:open
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] Changes to releasenotes and docs build jobs
On 11/22/2017 07:39 AM, Monty Taylor wrote:
Hey everybody!
Following recent changes [0] in the PTI [1][2] we're rolling out some
changes to the build-openstack-releasenotes and
build-openstack-sphinx-docs jobs. If you see patches with the topic
'updated-pti' - they are in service of this.
The most important thing to be aware of is that we'll no longer be using
tox for either of them. There are a few reasons for that - the one
that's most important to me is that it allows us to use the exact same
docs and releasenotes build jobs for python, go, javascript or any other
language without needing to add python build tooling to non-python
repos. We'll also align more with how readthedocs does things in the
broader python ecosystem.
It's also worth reminding people that we've NEVER used 'tox -edocs' in
the gate for docs jobs - so anyone who has additional things in their
docs environment has not been having those things run. For folks running
doc8, we recommend adding those checks to your pep8 environment instead.
It's also worth noting that we're adding support for a
doc/requirements.txt file (location chosen for alignment readthedocs) to
express requirements needed for all docs (for both releasenotes and
docs). We'll start off falling back to test-requirements.txt ... but, we
recommend splitting doc related requirements into doc/requirements.txt -
since that will mean not needing to install Sphinx when doing tox
unittests.
Specific info
=
Releasenotes
The patches for releasenotes have been approved and merged.
* We use -W for all releasenotes builds - this means warnings are always
errors for releasenotes. That shouldn't bother anyone, as most of the
releasenotes content is generated by reno anyway.
* We're temporarily installing the project to get version number. Doing
this will be removed as soon as the changes in
topic:releasenotes-version land. Note this only changes the version
number on the front page, not what is shown. topics:releasenotes-version
The majority of the changes for this have merged, let's move forward:
https://review.openstack.org/526850
* Installs dependencies via bindep for doc environment.
* doc/requirements.txt is used for installation of python dependencies.
Things like whereto or openstackdocstheme should go there.
Documentation builds
* We use -W only if setup.cfg sets it
* Installs dependencies via bindep for doc environment. Binary deps,
such as graphviz, should be listed in bindep and marked with a 'doc' tag.
* doc/requirements.txt is used for installation of python dependencies.
Things like whereto or openstackdocstheme should go there.
* tox_install.sh used to install project if it exists. Because of the
current situation with neutron and horizon plugins it's necessary to run
tox_install.sh if it exists as part of setup. We eventually want to make
that go away, but that's a different effort. There are seven repos with
a problematic tox_install.sh - patches will be arriving to fix them, and
we won't land the build-openstack-sphinx-docs changes until they have
all landed.
For many projects, tox_install.sh is not needed at all and can be easily
replaced. Changes are up for those that we can replace easily - and many
are already merged. For open changes, see
https://review.openstack.org/#/q/status:open++topic:rm-tox_install
Please review and merge,
Andreas
We've prepared these with a bunch of depends-on patches across a
collection of projects, so we don't anticipate much in the way of pain
... but life happens, so if you notice anything go south with
releasenotes or sphinx jobs, please let us know and we can help solve
any issues.
Thanks!
Monty
[0] https://review.openstack.org/#/c/509868
[1] https://review.openstack.org/#/c/508694
[2]
https://governance.openstack.org/tc/reference/project-testing-interface.html
__
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] [infra][all] Removal of packages from bindep-fallback
On 2017-11-16 06:59, Ian Wienand wrote:
> Hello,
>
> Some time ago we started the process of moving towards projects being
> more explicit about thier binary dependencies using bindep [1]
>
> To facilitate the transition, we created a "fallback" set of
> dependencies [2] which are installed when a project does not specifiy
> it's own bindep dependencies. This essentially replicated the rather
> ad-hoc environment provided by CI images before we started the
> transition.
>
> This list has acquired a few packages that cause some problems in
> various situations today. Particularly packages that aren't in the
> increasing number of distributions we provide, or packages that come
> from alternative repositories.
>
> To this end, [3,4] proposes the removal of
>
> liberasurecode-*
> mongodb-*
> python-zmq
> redis
> zookeeper
> ruby-*
>
> from the fallback packages. This has a small potential to affect some
> jobs that tacitly rely on these packages.
This has now merged. One fallout I noticed is that pcre-devel is not
installed anymore and thus "pcre.h" is not found when building some
python files. If that hits you, update your bindep.txt file with:
pcre-devel [platform:rpm]
libpcre3-dev [platform:dpkg]
For details about bindep, see
https://docs.openstack.org/infra/manual/drivers.html#package-requirements
Andreas
> NOTE: this does *not* affect devstack jobs (devstack manages it's own
> dependencies outside bindep) and if you want them back, it's just a
> matter of putting them into the bindep file in your project (and as a
> bonus, you have better dependency descriptions for your code).
>
> We should be able to then remove centos-release-openstack-* from our
> centos base images too [5], which will make life easier for projects
> such as triple-o who have to work-around that.
>
> If you have concerns, please reach out either via mail or in
> #openstack-infra
>
> Thank you,
>
> -i
>
> [1] https://docs.openstack.org/infra/bindep/
> [2]
> https://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/data/bindep-fallback.txt
> [3] https://review.openstack.org/519533
> [4] https://review.openstack.org/519534
> [5] https://review.openstack.org/519535
--
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]
On 2017-11-23 09:23, Frank Wang wrote:
> Andreas, Thanks for your quick respose, Currenty, We want to support
> Localization & Internationalization in our environment. Could you give me
> some guidance how to do it? May be I can work on this. By the way, I tried
> to add msgid from neutron-lib to neutron.po, It seems won't work.
There're some docs at https://docs.openstack.org/i18n,
Andreas
> Thanks,
> Frank
>
> At 2017-11-23 15:41:43, "Andreas Jaeger" <a...@suse.com> wrote:
>>On 2017-11-23 08:36, Frank Wang wrote:
>>> *Hello, openstackers,*
>>>
>>> *I'd like to know if neutron-lib support* *Localization &
>>> Internationalization. I found neutron.po for neutron, but no *.po for
>>> neutron-lib. Does anyone have any idea how to support localization for
>>> neutron-lib. I appreciate it. please let me know if I miss something.*
>>
>>It is set up for translation but looking at the translation server, no
>>real work has been done and thus nothing was imported:
>>
>>https://translate.openstack.org/project/view/neutron-lib?dswid=4366
>>
>>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
>
--
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]
On 2017-11-23 08:36, Frank Wang wrote:
> *Hello, openstackers,*
>
> *I'd like to know if neutron-lib support* *Localization &
> Internationalization. I found neutron.po for neutron, but no *.po for
> neutron-lib. Does anyone have any idea how to support localization for
> neutron-lib. I appreciate it. please let me know if I miss something.*
It is set up for translation but looking at the translation server, no
real work has been done and thus nothing was imported:
https://translate.openstack.org/project/view/neutron-lib?dswid=4366
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] "Show all" buttons broken for api-guide
On 2017-11-23 08:06, Gilles Dubreuil wrote:
>
>
> On 23/11/17 18:03, Gilles Dubreuil wrote:
>> Hi,
>>
>> Is that just me?
>>
>> The "Show all" button for any of the
>> "https://developer.openstack.org/api-guide/quick-start/*; pages is
>
> *not*
>
>> working.
>> It normally expands (and collapses with the "Hide all" button) all the
>> resources for the specific guide.
please file a bugreport against os-api-ref, for details see
https://docs.openstack.org/os-api-ref/latest/contributing.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] [all] Changes to releasenotes and docs build jobs
On 2017-11-22 18:26, James E. Blair wrote:
> Monty Taylor <mord...@inaugust.com> writes:
>
>> * We use -W only if setup.cfg sets it
>>
>> * Installs dependencies via bindep for doc environment. Binary deps,
>> such as graphviz, should be listed in bindep and marked with a 'doc'
>> tag.
>>
>> * doc/requirements.txt is used for installation of python dependencies.
>> Things like whereto or openstackdocstheme should go there.
>
> Should we add this info to the infra manual?
>
> Similar to this?
>
> https://docs.openstack.org/infra/manual/drivers.html#package-requirements
Yes, I suggest to update it. The PTI documents doc/requirements.txt but
the link above should be correct and mention it 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
