Re: [openstack-dev] [goal][python3] more updates to the goal tools

[super user]

The problem was fixed.

Nguyen Hai

On Fri, Aug 17, 2018 at 11:47 PM Doug Hellmann 
wrote:

> I was not able to reproduce the problem. Please test the fix in
> https://review.openstack.org/#/c/593068/ to see if that helps.
>
> Which version of Python are you using to run the tools? And on which OS?
>
> Excerpts from Doug Hellmann's message of 2018-08-17 10:30:29 -0400:
> > I will work on fixing this today.
> >
> > Has the designate team agreed to go ahead with their migration, or
> > are you still testing the scripts?
> >
> > Doug
> >
> > Excerpts from super user's message of 2018-08-17 15:37:03 +0900:
> > > Hi Doug,
> > >
> > > I'm Nguyen Hai. I proposed the python3-first patch set for
> > > designate projects. However, I have met this error to designate and
> > > designate-dashboard:
> > >
> > > === ../Output/designate/openstack/designate @ master ===
> > >
> > > ./tools/python3-first/do_repo.sh
> ../Output/designate/openstack/designate
> > > master 24292
> > >
> > > ++ cat ../Output/designate/openstack/designate/.gitreview
> > > ++ grep project
> > > ++ cut -f2 -d=
> > > + actual=openstack/designate.git
> > > +++ dirname ../Output/designate/openstack/designate
> > > ++ basename ../Output/designate/openstack
> > > ++ basename ../Output/designate/openstack/designate
> > > + expected=openstack/designate
> > > + '[' openstack/designate.git '!=' openstack/designate -a
> > > openstack/designate.git '!=' openstack/designate.git ']'
> > > + git -C ../Output/designate/openstack/designate review -s
> > > Creating a git remote called 'gerrit' that maps to:
> > > ssh://
> > > nguyentri...@review.openstack.org:29418/openstack/designate.git
> > > ++ basename master
> > > + new_branch=python3-first-master
> > > + git -C ../Output/designate/openstack/designate branch
> > > + grep -q python3-first-master
> > > + echo 'creating python3-first-master'
> > > creating python3-first-master
> > > + git -C ../Output/designate/openstack/designate checkout -- .
> > > + git -C ../Output/designate/openstack/designate clean -f -d
> > > + git -C ../Output/designate/openstack/designate checkout -q
> origin/master
> > > + git -C ../Output/designate/openstack/designate checkout -b
> > > python3-first-master
> > > Switched to a new branch 'python3-first-master'
> > > + python3-first -v --debug jobs update
> > > ../Output/designate/openstack/designate
> > > determining repository name from .gitreview
> > > working on openstack/designate @ master
> > > looking for zuul config in
> > > ../Output/designate/openstack/designate/.zuul.yaml
> > > using zuul config from
> ../Output/designate/openstack/designate/.zuul.yaml
> > > loading project settings from ../project-config/zuul.d/projects.yaml
> > > loading project templates from
> > > ../openstack-zuul-jobs/zuul.d/project-templates.yaml
> > > loading jobs from ../openstack-zuul-jobs/zuul.d/jobs.yaml
> > > looking for settings for openstack/designate
> > > looking at template 'openstack-python-jobs'
> > > looking at template 'openstack-python35-jobs'
> > > looking at template 'publish-openstack-sphinx-docs'
> > > looking at template 'periodic-stable-jobs'
> > > looking at template 'check-requirements'
> > > did not find template definition for 'check-requirements'
> > > looking at template 'translation-jobs-master-stable'
> > > looking at template 'release-notes-jobs'
> > > looking at template 'api-ref-jobs'
> > > looking at template 'install-guide-jobs'
> > > looking at template 'release-openstack-server'
> > > filtering on master
> > > merging templates
> > >   adding openstack-python-jobs
> > >   adding openstack-python35-jobs
> > >   adding publish-openstack-sphinx-docs
> > >   adding periodic-stable-jobs
> > >   adding check-requirements
> > >   adding release-notes-jobs
> > >   adding install-guide-jobs
> > > merging pipeline check
> > > *unhashable type: 'CommentedMap'*
> > > *Traceback (most recent call last):*
> > > *  File
> > >
> "/home/stack/python3-first/goal-tools/.tox/venv/lib/python3.6/site-packages/cliff/app.py",
> > > line 402, in run_subcommand*
> > > *result = cmd.run(parsed_args)*
> > > *  File
> > >
> "/home/stack/python3-first/goal-tools/.tox/venv/lib/python3.6/site-packages/cliff/command.py",
> > > line 184, in run*
> > > *return_code = self.take_action(parsed_args) or 0*
> > > *  File
> > >
> "/home/stack/python3-first/goal-tools/goal_tools/python3_first/jobs.py",
> > > line 531, in take_action*
> > > *entry,*
> > > *  File
> > >
> "/home/stack/python3-first/goal-tools/goal_tools/python3_first/jobs.py",
> > > line 397, in merge_project_settings*
> > > *up.get(pipeline, comments.CommentedMap()),*
> > > *  File
> > >
> "/home/stack/python3-first/goal-tools/goal_tools/python3_first/jobs.py",
> > > line 362, in merge_pipeline*
> > > *if job_name in job_names:*
> > > *TypeError: unhashable type: 'CommentedMap'*
> > > *Traceback (most recent call last):*
> > > *  File
> "/home/stack/python3-first/goal-tools/.tox/venv/bin/python3-first",
> > > line 

Re: [openstack-dev] [goal][python3] more updates to the goal tools

[super user]

Hi Doug,

I'm Nguyen Hai. I proposed the python3-first patch set for
designate projects. However, I have met this error to designate and
designate-dashboard:

=== ../Output/designate/openstack/designate @ master ===

./tools/python3-first/do_repo.sh ../Output/designate/openstack/designate
master 24292

++ cat ../Output/designate/openstack/designate/.gitreview
++ grep project
++ cut -f2 -d=
+ actual=openstack/designate.git
+++ dirname ../Output/designate/openstack/designate
++ basename ../Output/designate/openstack
++ basename ../Output/designate/openstack/designate
+ expected=openstack/designate
+ '[' openstack/designate.git '!=' openstack/designate -a
openstack/designate.git '!=' openstack/designate.git ']'
+ git -C ../Output/designate/openstack/designate review -s
Creating a git remote called 'gerrit' that maps to:
ssh://
nguyentri...@review.openstack.org:29418/openstack/designate.git
++ basename master
+ new_branch=python3-first-master
+ git -C ../Output/designate/openstack/designate branch
+ grep -q python3-first-master
+ echo 'creating python3-first-master'
creating python3-first-master
+ git -C ../Output/designate/openstack/designate checkout -- .
+ git -C ../Output/designate/openstack/designate clean -f -d
+ git -C ../Output/designate/openstack/designate checkout -q origin/master
+ git -C ../Output/designate/openstack/designate checkout -b
python3-first-master
Switched to a new branch 'python3-first-master'
+ python3-first -v --debug jobs update
../Output/designate/openstack/designate
determining repository name from .gitreview
working on openstack/designate @ master
looking for zuul config in
../Output/designate/openstack/designate/.zuul.yaml
using zuul config from ../Output/designate/openstack/designate/.zuul.yaml
loading project settings from ../project-config/zuul.d/projects.yaml
loading project templates from
../openstack-zuul-jobs/zuul.d/project-templates.yaml
loading jobs from ../openstack-zuul-jobs/zuul.d/jobs.yaml
looking for settings for openstack/designate
looking at template 'openstack-python-jobs'
looking at template 'openstack-python35-jobs'
looking at template 'publish-openstack-sphinx-docs'
looking at template 'periodic-stable-jobs'
looking at template 'check-requirements'
did not find template definition for 'check-requirements'
looking at template 'translation-jobs-master-stable'
looking at template 'release-notes-jobs'
looking at template 'api-ref-jobs'
looking at template 'install-guide-jobs'
looking at template 'release-openstack-server'
filtering on master
merging templates
  adding openstack-python-jobs
  adding openstack-python35-jobs
  adding publish-openstack-sphinx-docs
  adding periodic-stable-jobs
  adding check-requirements
  adding release-notes-jobs
  adding install-guide-jobs
merging pipeline check
*unhashable type: 'CommentedMap'*
*Traceback (most recent call last):*
*  File
"/home/stack/python3-first/goal-tools/.tox/venv/lib/python3.6/site-packages/cliff/app.py",
line 402, in run_subcommand*
*result = cmd.run(parsed_args)*
*  File
"/home/stack/python3-first/goal-tools/.tox/venv/lib/python3.6/site-packages/cliff/command.py",
line 184, in run*
*return_code = self.take_action(parsed_args) or 0*
*  File
"/home/stack/python3-first/goal-tools/goal_tools/python3_first/jobs.py",
line 531, in take_action*
*entry,*
*  File
"/home/stack/python3-first/goal-tools/goal_tools/python3_first/jobs.py",
line 397, in merge_project_settings*
*up.get(pipeline, comments.CommentedMap()),*
*  File
"/home/stack/python3-first/goal-tools/goal_tools/python3_first/jobs.py",
line 362, in merge_pipeline*
*if job_name in job_names:*
*TypeError: unhashable type: 'CommentedMap'*
*Traceback (most recent call last):*
*  File "/home/stack/python3-first/goal-tools/.tox/venv/bin/python3-first",
line 10, in *
*sys.exit(main())*
*  File
"/home/stack/python3-first/goal-tools/goal_tools/python3_first/main.py",
line 42, in main*
*return Python3First().run(argv)*
*  File
"/home/stack/python3-first/goal-tools/.tox/venv/lib/python3.6/site-packages/cliff/app.py",
line 281, in run*
*result = self.run_subcommand(remainder)*
*  File
"/home/stack/python3-first/goal-tools/.tox/venv/lib/python3.6/site-packages/cliff/app.py",
line 402, in run_subcommand*
*result = cmd.run(parsed_args)*
*  File
"/home/stack/python3-first/goal-tools/.tox/venv/lib/python3.6/site-packages/cliff/command.py",
line 184, in run*
*return_code = self.take_action(parsed_args) or 0*
*  File
"/home/stack/python3-first/goal-tools/goal_tools/python3_first/jobs.py",
line 531, in take_action*
*entry,*
*  File
"/home/stack/python3-first/goal-tools/goal_tools/python3_first/jobs.py",
line 397, in merge_project_settings*
*up.get(pipeline, comments.CommentedMap()),*
*  File
"/home/stack/python3-first/goal-tools/goal_tools/python3_first/jobs.py",
line 362, in merge_pipeline*
*if job_name in job_names:*
*TypeError: unhashable type: 'CommentedMap'*
*+ echo 'No changes'*
*No changes*
*+ exit 1*

On 

Re: [openstack-dev] [goal][python3] more updates to the goal tools

[super user]

Got it.

Nguyen Hai

On Wed, Aug 8, 2018 at 7:58 AM Doug Hellmann  wrote:

> Champions,
>
> I have made quite a few changes to the tools for generating the zuul
> migration patches today. If you have any patches you generated locally
> for testing, please check out the latest version of the tool (when all
> of the changes merge) and regenerate them.
>
> Doug
>
> __
> 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

Re: [openstack-dev] [Tacker] - TACKER + NETWORKING_SFC + NSH

[super user]

Currently, Tacker does not support NSH.

This feature will implement in the future.

On Wed, Aug 1, 2018 at 3:17 AM william sales 
wrote:

> Hello guys,
>
> is there any version of Tacker that allows the use of networking_sfc with
> NSH?
>
> Thankful.
>
> William Sales
> __
> 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

[openstack-dev] [devstack-dev][swift] Limitations of Erasure Coding in Swift

[super user]

Hello everybody,

I would like to ask about the limitations of Erasure Coding in Swift right
now. What can we do to overcome these limitations?

Thank you.
__
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] [oslo][osc][cliff][tacker] New release of cmd2 break cliff and tacker client

[super user]

Hi everyone,

New release of cmd2 0.9.0 seems to break cliff and python-tackerclient.

The cmd2 library changed the way it handles parsing input commands. It now
uses a different library, which means the values passed to the commands are
no longer PyParsing objects and are instead Statement objects. These
objects do not have a “parsed” property, so the receiving code needs to
work with them differently.

The patch https://review.openstack.org/571524 tries to fix this in the
places within cliff where it was failing in interactive mode.

Please consider reviewing this patch and have a new release for cliff so
that the python-tackerclient pass the py35 tests.

Thank you,
Nguyen Hai
__
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] [Designate] Plan for OSM

[super user]

I thought it is Open Source MANO.

On Thu, May 3, 2018, 4:45 PM duon...@vn.fujitsu.com 
wrote:

> Hi Ben,
>
> >>On 04/25/2018 11:31 PM, daidv at vn.fujitsu.com wrote:
> >> Hi forks,
> >>
> >> We tested and completed our process with OVO migration in Queens cycle.
> >> Now, we can continue with OSM implementation for Designate.
> >> Actually, we have pushed some patches related to OSM[1] and it's ready
> to review.
>
> > Out of curiosity, what does OSM stand for?  Based on the patches it
> > seems related to rolling upgrades, but a quick glance at them doesn't
> > make it obvious to me what's going on.  Thanks.
>
> OSM stands for Online Schema Migration, which means that we can migrate
> database schema without
> downtime for service.
>
> > -Ben
>
> Best regards,
>
> Ha Quang Duong (Mr.)
> PODC - Fujitsu Vietnam Ltd.
>
>
> __
> 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

Re: [openstack-dev] [all][requirements] a plan to stop syncing requirements into projects

[super user]

I will help to update some.

On Fri, Apr 6, 2018 at 8:42 PM, Doug Hellmann  wrote:

> Excerpts from super user's message of 2018-04-06 17:10:32 +0900:
> > Hope you fix this soon, there are many patches depend on the 'match the
> > minimum version' problem which causes requirements-check fail.
>
> The problem is with *those patches* and not the check.
>
> I've been trying to update some, but my time has been limited this week
> for personal reasons. I encourage project teams to run the script I
> provided or edit their lower-constraints.txt file by hand to fix the
> issues.
>
> Doug
>
> __
> 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

Re: [openstack-dev] [all][requirements] a plan to stop syncing requirements into projects

[super user]

Hope you fix this soon, there are many patches depend on the 'match the
minimum version' problem which causes requirements-check fail.

On Wed, Apr 4, 2018 at 10:58 PM, Doug Hellmann 
wrote:

> Excerpts from Doug Hellmann's message of 2018-03-28 18:53:03 -0400:
> >
> > Because we had some communication issues and did a few steps out
> > of order, when this patch lands projects that have approved
> > bot-proposed requirements updates may find that their requirements
> > and lower-constraints files no longer match, which may lead to job
> > failures. It should be easy enough to fix the problems by making
> > the values in the constraints files match the values in the
> > requirements files (by editing either set of files, depending on
> > what is appropriate). I apologize for any inconvenience this causes.
>
> In part because of this, and in part because of some issues calculating
> the initial set of lower-constraints, we have several projects where
> their lower-constraints don't match the lower bounds in the requirements
> file(s). Now that the check job has been updated with the new rules,
> this is preventing us from landing the patches to add the
> lower-constraints test job (so those rules are working!).
>
> I've prepared a script to help fix up the lower-constraints.txt
> based on values in requirements.txt and test-requirements.txt.
> That's not everything, but it should make it easier to fix the rest.
>
> See https://review.openstack.org/#/c/558610/ for the script. I'll work
> on those pep8 errors later today so we can hopefully land it soon, but
> in the mean time you'll need to check out that commit and follow the
> instructions for setting up a virtualenv to run the script.
>
> Doug
>
> __
> 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