[openstack-dev] [Zun] Upgrade from 'docker-py' to 'docker'

[Hongbin Lu]

Hi team,

We have recently finished the upgrade from 'docker-py' to 'docker'. If your 
devstack environment run into errors due to the incompatibility between the old 
and new docker python package (such as [1]), you could try the commands below:

  $ sudo pip uninstall docker-py docker-pycreds
  $ sudo pip install -c /opt/stack/requirements/upper-constraints.txt \
  -e /opt/stack/zun
  $ sudo systemctl restart devstack@kuryr*
  $ sudo systemctl restart devstack@zun*

For context, 'docker-py' is the old python-binding library for consuming docker 
REST API. It has been renamed to 'docker' and the old package will be dropped 
eventually. At the last a few days, there are several reports of errors due to 
double installation of both 'docker-py' and 'docker' packages in the 
development environment, so we need to migrate from 'docker-py' to 'docker' to 
resolve the issue.

Right now, all Zun's components and dependencies has finished the upgrade 
[2][3][4], and there is another proposed patch to drop 'docker-py' from global 
requirements [5]. The package conflict issue will be entirely resolved when the 
upgrade is finished globally.

[1] https://bugs.launchpad.net/zun/+bug/1693425
[2] https://review.openstack.org/#/c/475526/
[3] https://review.openstack.org/#/c/475863/
[4] https://review.openstack.org/#/c/475893/
[5] https://review.openstack.org/#/c/475962/

Best regards,
Hongbin
__
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] [Zun] Propose addition of Zun core team and removal notice

[Hongbin Lu]

Hi all,

Thanks for your votes. According to the feedback, I added Shunli to the core 
team [1].

Best regards,
Hongbin

[1] https://review.openstack.org/#/admin/groups/1382,members

> -Original Message-
> From: Shuu Mutou [mailto:shu-mu...@rf.jp.nec.com]
> Sent: June-21-17 8:56 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Cc: Haruhiko Katou
> Subject: Re: [openstack-dev] [Zun] Propose addition of Zun core team
> and removal notice
> 
> +1 to all from me.
> 
> Welcome Shunli! And greate thanks to Dims and Yanyan!!.
> 
> Best regards,
> Shu
> 
> > -Original Message-
> > From: Kumari, Madhuri [mailto:madhuri.kum...@intel.com]
> > Sent: Wednesday, June 21, 2017 12:30 PM
> > To: OpenStack Development Mailing List (not for usage questions)
> > 
> > Subject: Re: [openstack-dev] [Zun] Propose addition of Zun core team
> > and removal notice
> >
> > +1 from me as well.
> >
> >
> >
> > Thanks Dims and Yanyan for you contribution to Zun :)
> >
> >
> >
> > Regards,
> >
> > Madhuri
> >
> >
> >
> > From: Kevin Zhao [mailto:kevin.z...@linaro.org]
> > Sent: Wednesday, June 21, 2017 6:37 AM
> > To: OpenStack Development Mailing List (not for usage questions)
> > 
> > Subject: Re: [openstack-dev] [Zun] Propose addition of Zun core team
> > and removal notice
> >
> >
> >
> > +1 for me.
> >
> > Thx!
> >
> >
> >
> > On 20 June 2017 at 13:50, Pradeep Singh  >  > wrote:
> >
> > +1 from me,
> >
> > Thanks Shunli for your great work :)
> >
> >
> >
> > On Tue, Jun 20, 2017 at 10:02 AM, Hongbin Lu
>  >  > wrote:
> >
> > Hi all,
> >
> >
> >
> > I would like to propose the following change to the Zun
> core team:
> >
> >
> >
> > + Shunli Zhou (shunliz)
> >
> >
> >
> > Shunli has been contributing to Zun for a while and did a
> lot of
> > work. He has completed the BP for supporting resource claim and be
> > closed to finish the filter scheduler BP. He showed a good
> > understanding of the Zun’s code base and expertise on other OpenStack
> > projects. The quantity [1] and quality of his submitted code also
> shows his qualification.
> > Therefore, I think he will be a good addition to the core team.
> >
> >
> >
> > In addition, I have a removal notice. Davanum Srinivas
> > (Dims) and Yanyan Hu requested to be removed from the core team. Dims
> > had been helping us since the inception of the project. I treated him
> > as mentor and his guidance is always helpful for the whole team. As
> > the project becomes mature and stable, I agree with him that it is
> > time to relieve him from the core reviewer responsibility because he
> > has many other important responsibilities for the OpenStack community.
> > Yanyan’s leaving is because he has been relocated and focused on an
> > out-of-OpenStack area. I would like to take this chance to thank Dims
> and Yanyan for their contribution to Zun.
> >
> >
> >
> > Core reviewers, please cast your vote on this proposal.
> >
> >
> >
> > Best regards,
> >
> > Hongbin
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > __
> > 
> > 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 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] [QA][ALL] What tempest tests will go under tempest plugin for a Project?

[Ghanshyam Mann]

On Fri, Jun 23, 2017 at 4:51 PM, Chandan kumar  wrote:
> Hello,
>
> In Queen OpenStack release, We have a community goal to split In-Tree
> tempest plugin to a separate repo[1.].
>
> I have a couple question regarding the tempest tests movement within
> tempest plugins.
>
> [1.] Since some of the core OpenStack projects like Nova, Glance and
> Swift does have tempest plugin currently.
>  Their Tempest tests reside under tempest project repo.
>  are we going to create tempest plugin for the same?
>  If yes, what are the tempest tests (API/Scenario) tests moving
> under tempest plugins?
>
> [2.] And, like other core projects like neutron and cinder have their
> in-tree tempest plugins also.
>  And those are also moving to a separate repo and currently, their
> tests also resides under tempest repo.
>  How can we avoid the duplication of the tempest tests?

Its same answer for 1 and 2. Tempest is a place to have integration
tests and future tests also falls in same scope.
Yes, we do have API tests negative as well as positive which are there
because of defcore. Defcore need those for interop certification.
Those will reside in Tempest as of now and so new tests can be added
in Tempest if defcore require them.

New or existing Tempest plugin for 6 core projects whose tests are
present in Tempest, will target their functional/API/negative testing
etc which are/should be out of scope of Tempest.

Regarding the duplication of tests, we do take care of those while
review of new tests addition. If there is any new tests proposed in
Tempest, reviewers need to check whether same coverage is there on
project side or not (either functional tests or in tempest plugin).
Also if those are more appropriate to reside on project side. We will
be continuing with the same process to avoid duplicate tests.


>
> [3.] For other projects while moving tests to a separate repo how we
> are going to collaborate together to avoid
>  duplication and move common tests to Tempest?

You mean tests in projects tree as functional tests etc and their
tempest plugin ? If so, then same process as done in Tempest. When
adding new tests in tempest plugin, reviewers need to check the
duplicate coverage of those tests.

-gmann

>
> Links:
> [1.] 
> https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html
>
> Thanks,
>
> Chandan Kumar
>
> __
> 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] [nova] Need volunteer(s) to help migrate project docs

[Zhenyu Zheng]

I will help

On Sat, Jun 24, 2017 at 12:23 AM, Matt Riedemann 
wrote:

> The spec [1] with the plan to migrate project-specific docs from
> docs.openstack.org to each project has merged.
>
> There are a number of steps outlined in there which need people from the
> project teams, e.g. nova, to do for their project. Some of it we're already
> doing, like building a config reference, API reference, using the
> openstackdocstheme, etc. But there are other things like moving the install
> guide for compute into the nova repo.
>
> Is anyone interested in owning this work? There are enough tasks that it
> could probably be a couple of people coordinating. It also needs to be done
> by the end of the Pike release, so time is a factor.
>
> [1] https://review.openstack.org/#/c/472275/
>
> --
>
> Thanks,
>
> Matt
>
> __
> 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