Re: [openstack-dev] [Tacker] Redundancy VNFFG module in tacker

[Nguyễn Trí Hải]

This is the document how to contribute to Tacker:

https://docs.openstack.org/tacker/latest/contributor/index.html

On Fri, Nov 9, 2018, 4:50 PM 백호성  wrote:

> Dear tacker project members,
>
> Hello. I am Hosung Baek and Ph.D.student at Korea Univ.
>
> I am interested in the VNFFG feature in Tacker project, and I want to
> develop the "Redundancy VNFFG module" in tacker.
>
> As far as I know. it is difficult to apply the VNFFG configuration where
> there is low loss requirement such as DetNet and URLLC.
>
> Because there is no module for reliable VNFFG.
>
> The module to be developed is described as follows.
>
> It is a function to construct a disjoint VNFFG by adding redundancy VNFFG
> module to the tacker VNFFG feature and to transmit the data to two disjoint
> paths.
>
> To implement this module, two VNFFGs must be configured for one network
> service and the function to remove redundant packets in two different paths
> is required.
>
> I want to develop this module and contribute this to tacker project.
>
> So could you tell me the contribution process in OpenStack tacker project
> if possible?
>
> Yours sincerely,
>
> Hosung Baek.
>
> __
> 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
>
-- 

*Nguyen Tri Hai  */ Ph.D. Student

ANDA Lab., Soongsil Univ., Seoul, South Korea
__
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][karbor] Please process thepython3-first patches

[Nguyễn Trí Hải]

Hi,

Thanks for reviewing them. Only two patches need to review:
https://review.openstack.org/#/c/594827/
https://review.openstack.org/#/c/594815/ (Depends-On:
https://review.openstack.org/#/c/596289/)


On Fri, Sep 21, 2018 at 10:33 PM jiaopengju 
wrote:

> Thanks for pushing these patches, we will review and merge them ASAP.
>
>
>  原始邮件
> *发件人:* Nguyễn Trí Hải
> *收件人:* OpenStack Development Mailing List (not for usage questions)<
> openstack-dev@lists.openstack.org>
> *抄送:* jiaopengju
> *发送时间:* 2018年9月21日(周五) 20:36
> *主题:* [openstack-dev][goals][python3][karbor] Please process
> thepython3-first patches
>
> Hi Karbor team and Karbor PTL,
>
> As part of the "Run under Python 3 by default" community goal [1] for
> OpenStack in the Stein cycle, I proposed the patches related to
> python3-first goal very long time ago. However, there is no activity for
> those patches.
>
> Please receive those patches and review them. Those patches belong to:
> - openstack/karbor
> - openstack/karbor-dashboard
> - openstack/python-karborclient
>
> Here they are:
> https://review.openstack.org/#/q/project:%255E.*karbor.*+topic:python3-first+status:open
>
> [1] https://governance.openstack.org/tc/goals/stein/python3-first.html
>
> --
>
> Nguyen Tri Hai / Ph.D. Student
>
> ANDA Lab., Soongsil Univ., Seoul, South Korea
>
> <https://www.facebook.com/nguyentrihai>
> <http://linkedin.com/in/nguyentrihai>
> <https://www.facebook.com/nguyentrihai>*[image:
> http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4]
> <http://nguyentrihai.com/>* <https://www.facebook.com/nguyentrihai>
>


-- 

Nguyen Tri Hai / Ph.D. Student

ANDA Lab., Soongsil Univ., Seoul, South Korea

<https://www.facebook.com/nguyentrihai>
<http://linkedin.com/in/nguyentrihai>
<https://www.facebook.com/nguyentrihai>*[image:
http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4]
<http://nguyentrihai.com/>* <https://www.facebook.com/nguyentrihai>
__
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] [goals][python3][karbor] Please process the python3-first patches

[Nguyễn Trí Hải]

Hi Karbor team and Karbor PTL,

As part of the "Run under Python 3 by default" community goal [1] for
OpenStack in the Stein cycle, I proposed the patches related to
python3-first goal very long time ago. However, there is no activity for
those patches.

Please receive those patches and review them. Those patches belong to:
- openstack/karbor
- openstack/karbor-dashboard
- openstack/python-karborclient

Here they are:
https://review.openstack.org/#/q/project:%255E.*karbor.*+topic:python3-first+status:open

[1] https://governance.openstack.org/tc/goals/stein/python3-first.html

-- 

Nguyen Tri Hai / Ph.D. Student

ANDA Lab., Soongsil Univ., Seoul, South Korea



*[image:
http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4]
* 
__
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] [goal][python3] goal champion tools

[Nguyễn Trí Hải]

For dealing with this problem, I turn off all the Timeline events in
Preferences.


On Wed, Aug 29, 2018 at 6:58 AM Doug Hellmann  wrote:

> The story with all of the tasks for tracking the zuul migration has so
> many comments it will no longer display in my browser. So, I've created
> 2 tools to look at the data from the command line.
>
> https://review.openstack.org/597245 has a tool to list the task
> assignments
>
> https://review.openstack.org/597244 has a tool to change the task
> assignment for 1 task
>
> The UX for the assignment tool is terrible, so you have to provide
> your numerical user ID. The easiest way to find that may be to use
> the list tool and copy it from one of the tasks already assigned
> to you.
>
> 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
>


-- 

Nguyen Tri Hai / Ph.D. Student

ANDA Lab., Soongsil Univ., Seoul, South Korea



*[image:
http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4]
* 
__
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] please check with me before submitting any zuul migration patches

[Nguyễn Trí Hải]

Hi,

There is a conflict appearing on karbor projects:
https://review.openstack.org/#/q/project:%255E.*karbor.*+topic:python3-first+status:open

Please check the storyboard to check who is working on the target project
if you want to help.
https://storyboard.openstack.org/#!/story/2002586



On Wed, Aug 22, 2018 at 2:42 PM Nguyễn Trí Hải 
wrote:

> Please add yourself to storyboard to everyone know who is working on the
> project.
>
> https://storyboard.openstack.org/#!/story/2002586
>
> On Wed, Aug 22, 2018 at 3:31 AM Doug Hellmann 
> wrote:
>
>> We have a few folks eager to join in and contribute to the python3 goal
>> by helping with the patches to migrate zuul settings. That's great!
>> However, many of the patches being proposed are incorrect, which means
>> there is either something wrong with the tool or the way it is used.
>>
>> The intent was to have a very small group, 3-4 people, who knew how
>> the tools worked to propose all of those patches.  Having incorrect
>> patches can break the CI for a project, so we need to be especially
>> careful with them.  We do not want every team writing the patches
>> for themselves, and we do not want lots and lots of people who we
>> have to train to use the tools.
>>
>> If you are not one of the people already listed as a goal champion
>> on [1], please PLEASE stop writing patches and get in touch with
>> me personally and directly (via IRC or email) BEFORE doing any more
>> work on the goal.
>>
>> Thanks,
>> Doug
>>
>> [1] https://governance.openstack.org/tc/goals/stein/python3-first.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
>>
>
>
> --
>
> Nguyen Tri Hai / Ph.D. Student
>
> ANDA Lab., Soongsil Univ., Seoul, South Korea
>
> <https://www.facebook.com/nguyentrihai>
> <http://linkedin.com/in/nguyentrihai>
> <https://www.facebook.com/nguyentrihai>*[image:
> http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4]
> <http://nguyentrihai.com/>* <https://www.facebook.com/nguyentrihai>
>


-- 

Nguyen Tri Hai / Ph.D. Student

ANDA Lab., Soongsil Univ., Seoul, South Korea

<https://www.facebook.com/nguyentrihai>
<http://linkedin.com/in/nguyentrihai>
<https://www.facebook.com/nguyentrihai>*[image:
http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4]
<http://nguyentrihai.com/>* <https://www.facebook.com/nguyentrihai>
__
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] [Searchlight] Action plan for Searchlight in Stein

[Nguyễn Trí Hải]

Hi,

The link for Stein's Etherpad is missing.

On Wed, Aug 22, 2018 at 5:58 PM Trinh Nguyen  wrote:

> Dear team,
>
> Here is my proposed action plan for Searchlight in Stein. The ultimate
> goal is to revive Searchlight with a sustainable number of contributors and
> can release as expected.
>
> 1. Migrate Searchlight to Storyboard with the help of Kendall
> 2. Attract more contributors (as well as cores)
> 3. Clean up docs, notes
> 4. Review and clean up patches [1] [2] [3] [4]
> 5. Setting up goals/features for Stein. We will need to have a virtual PTG
> (September 10-14, 2018, Denver) since I cannot attend it this time.
>
> This is our Etherpad for Stein, please feel free to contribute from now on
> until the PTG:
> https://review.openstack.org/#/q/project:openstack/searchlight+status:open
>
> [1]
> https://review.openstack.org/#/q/project:openstack/searchlight+status:open
> [2]
> https://review.openstack.org/#/q/project:openstack/searchlight-ui+status:open
> [3]
> https://review.openstack.org/#/q/project:openstack/python-searchlightclient+status:open
> [4]
> https://review.openstack.org/#/q/project:openstack/searchlight-specs+status:open
>
> If you have any idea or want to contribute, please ping me on IRC:
>
>- IRC Channel: #openstack-searchlight
>- My IRC handler: dangtrinhnt
>
>
> Bests,
>
> *Trinh Nguyen *| Founder & Chief Architect
>
> 
>
> *E:* dangtrin...@gmail.com | *W:* *www.edlab.xyz *
>
> __
> 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
>


-- 

Nguyen Tri Hai / Ph.D. Student

ANDA Lab., Soongsil Univ., Seoul, South Korea



*[image:
http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4]
* 
__
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] [goal][python3] week 2 update

[Nguyễn Trí Hải]

Hi,

The other projects please consider merging the OpenStack Release Bot
patches related to Rocky branch. So that we can propose the patches related
to python3-first goal.

On Tue, Aug 21, 2018 at 8:40 PM Telles Nobrega  wrote:

> Thanks. We merged most of them, there is only one that failed the tests so
> I'm rechecking it.
>
> On Mon, Aug 20, 2018 at 5:43 PM Doug Hellmann 
> wrote:
>
>> Excerpts from Doug Hellmann's message of 2018-08-20 16:34:22 -0400:
>> > Excerpts from Telles Nobrega's message of 2018-08-20 15:07:29 -0300:
>> > > Hi Doug,
>> > >
>> > > I believe Sahara is ready to have those patches worked on.
>> > >
>> > > Do we have to do anything specific to get the env ready?
>> >
>> > Just be ready to do the reviews. I am generating the patches now and
>> > will propose them in a little while when the script finishes.
>>
>> And here they are:
>>
>>
>> +--+-+-+
>> | Subject  | Repo
>> | URL |
>>
>> +--+-+-+
>> | import zuul job settings from project-config |
>> openstack/python-saharaclient   | https://review.openstack.org/593904 |
>> | switch documentation job to new PTI  |
>> openstack/python-saharaclient   | https://review.openstack.org/593905 |
>> | add python 3.6 unit test job |
>> openstack/python-saharaclient   | https://review.openstack.org/593906 |
>> | import zuul job settings from project-config |
>> openstack/python-saharaclient   | https://review.openstack.org/593918 |
>> | import zuul job settings from project-config |
>> openstack/python-saharaclient   | https://review.openstack.org/593923 |
>> | import zuul job settings from project-config |
>> openstack/python-saharaclient   | https://review.openstack.org/593928 |
>> | import zuul job settings from project-config |
>> openstack/python-saharaclient   | https://review.openstack.org/593933 |
>> | import zuul job settings from project-config | openstack/sahara
>> | https://review.openstack.org/593907 |
>> | switch documentation job to new PTI  | openstack/sahara
>> | https://review.openstack.org/593908 |
>> | add python 3.6 unit test job | openstack/sahara
>> | https://review.openstack.org/593909 |
>> | import zuul job settings from project-config | openstack/sahara
>> | https://review.openstack.org/593919 |
>> | import zuul job settings from project-config | openstack/sahara
>> | https://review.openstack.org/593924 |
>> | import zuul job settings from project-config | openstack/sahara
>> | https://review.openstack.org/593929 |
>> | import zuul job settings from project-config | openstack/sahara
>> | https://review.openstack.org/593934 |
>> | import zuul job settings from project-config |
>> openstack/sahara-dashboard  | https://review.openstack.org/593910 |
>> | switch documentation job to new PTI  |
>> openstack/sahara-dashboard  | https://review.openstack.org/593911 |
>> | import zuul job settings from project-config |
>> openstack/sahara-dashboard  | https://review.openstack.org/593920 |
>> | import zuul job settings from project-config |
>> openstack/sahara-dashboard  | https://review.openstack.org/593925 |
>> | import zuul job settings from project-config |
>> openstack/sahara-dashboard  | https://review.openstack.org/593930 |
>> | import zuul job settings from project-config |
>> openstack/sahara-dashboard  | https://review.openstack.org/593935 |
>> | import zuul job settings from project-config | openstack/sahara-extra
>> | https://review.openstack.org/593912 |
>> | import zuul job settings from project-config | openstack/sahara-extra
>> | https://review.openstack.org/593921 |
>> | import zuul job settings from project-config | openstack/sahara-extra
>> | https://review.openstack.org/593926 |
>> | import zuul job settings from project-config | openstack/sahara-extra
>> | https://review.openstack.org/593931 |
>> | import zuul job settings from project-config | openstack/sahara-extra
>> | https://review.openstack.org/593936 |
>> | import zuul job settings from project-config |
>> openstack/sahara-image-elements | https://review.openstack.org/593913 |
>> | import zuul job settings from project-config |
>> openstack/sahara-image-elements | https://review.openstack.org/593922 |
>> | import zuul job settings from project-config |
>> openstack/sahara-image-elements | https://review.openstack.org/593927 |
>> | import zuul job settings from project-config |
>> openstack/sahara-image-elements | https://review.openstack.org/593932 |
>> | import zuul job settings from project-config |
>> openstack/sahara-image-elements | https://review.openstack.org/593937 |
>> | import 

Re: [openstack-dev] [goal][python3] dealing with new jobs failing on old branches

[Nguyễn Trí Hải]

Hi,

I figured out that we also can submit a patch to fix failure job in the old
branches, particularly, the docs job.
However, I still struggle with the failure of py27 or py35 jobs.

On Tue, Aug 21, 2018 at 11:17 PM Doug Hellmann 
wrote:

> Goal champions,
>
> Most of the jobs in the project-templates do not have branch
> specifiers.  That allows us to add a job to a repository and then
> not realize that it doesn't work on an old branch. We're finding
> some of those with this zuul migration (for example,
> https://review.openstack.org/#/c/593012/ and
> https://review.openstack.org/#/c/593016/).
>
> To deal with these, we need to remove that job or template from the
> repository's settings in the project-config repository, and not include
> it in the import patches.
>
> 1. First we want to wait for the team to land as many of the unaltered
>import patches as possible, so those jobs stay on the master branch
>and recent stable branches where they work.
>
> 2. Then, propose a patch to project-config to remove just the problem jobs
>and templates from the repositories where they are a problem.
>
> 3. Then, rebase the patch that removes all of a team's project settings
>on top of the one created in step 2.
>
> 4. Finally, modify the import patch(es) on the older stable branches
>where the jobs fail and remove the jobs or templates that cause
>problems.  Set those patches to depend on the patch created in
>step 2, since they cannot land without the project-config change.
>
> 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
>


-- 

Nguyen Tri Hai / Ph.D. Student

ANDA Lab., Soongsil Univ., Seoul, South Korea



*[image:
http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4]
* 
__
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] please check with me before submitting any zuul migration patches

[Nguyễn Trí Hải]

Please add yourself to storyboard to everyone know who is working on the
project.

https://storyboard.openstack.org/#!/story/2002586

On Wed, Aug 22, 2018 at 3:31 AM Doug Hellmann  wrote:

> We have a few folks eager to join in and contribute to the python3 goal
> by helping with the patches to migrate zuul settings. That's great!
> However, many of the patches being proposed are incorrect, which means
> there is either something wrong with the tool or the way it is used.
>
> The intent was to have a very small group, 3-4 people, who knew how
> the tools worked to propose all of those patches.  Having incorrect
> patches can break the CI for a project, so we need to be especially
> careful with them.  We do not want every team writing the patches
> for themselves, and we do not want lots and lots of people who we
> have to train to use the tools.
>
> If you are not one of the people already listed as a goal champion
> on [1], please PLEASE stop writing patches and get in touch with
> me personally and directly (via IRC or email) BEFORE doing any more
> work on the goal.
>
> Thanks,
> Doug
>
> [1] https://governance.openstack.org/tc/goals/stein/python3-first.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
>


-- 

Nguyen Tri Hai / Ph.D. Student

ANDA Lab., Soongsil Univ., Seoul, South Korea



*[image:
http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4]
* 
__
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] Proposing changes in Tacker Core Team

[Nguyễn Trí Hải]

+1

On Wed, Aug 22, 2018, 1:21 PM Dharmendra Kushwaha <
dharmendra.kushw...@india.nec.com> wrote:

> Hi Tacker members,
>
>
>
> To keep our Tacker project growing with new active members, I would like
>
> to propose to prune +2 ability of our farmer member Kanagaraj Manickam,
>
> and propose Cong Phuoc Hoang (IRC: phuoc) to join the tacker core team.
>
>
>
> Kanagaraj is not been involved since last couple of cycle. You had a great
>
> Contribution in Tacker project like VNF scaling features which are
> milestone
>
> for project. Thanks for your contribution, and wish to see you again.
>
>
>
> Phuoc is contributing actively in Tacker from Pike cycle, and
>
> he has grown into a key member of this project [1]. He delivered multiple
>
> features in each cycle. Additionally tons of other activities like bug
> fixes,
>
> answering actively on bugs. He is also actively contributing in cross
> project
>
> like tosca-parser and heat-translator which is much helpful for Tacker.
>
>
>
> Please vote your +1/-1.
>
>
>
> [1]:
> http://stackalytics.com/?project_type=openstack=all=commits=tacker-group_id=hoangphuoc
>
>
>
> Thanks & Regards
>
> Dharmendra Kushwaha
> __
> 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
>
-- 

*Nguyen Tri Hai  */ Ph.D. Student

ANDA Lab., Soongsil Univ., Seoul, South Korea
__
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] [goal][python3] week 2 update

[Nguyễn Trí Hải]

Hi,

Vitrage team is going to finish the zuul job soon. As I see, only few
patches in the old branches need to be merged.

For the other projects, some patches have problems with different errors.
Please help to fix them.

Thanks for your cooperation.

Nguyen Hai

On Tue, Aug 21, 2018, 12:27 AM Doug Hellmann  wrote:

> This is week 2 of the roll-out of the "Run under Python 3 by default"
> goal (https://governance.openstack.org/tc/goals/stein/python3-first.html).
>
> == What we learned last week ==
>
> As we worked on approving the changes to add the zuul settings to
> a few Oslo repositories, we had trouble with some of the older
> branches because they were running newer versions of the jobs, as
> configured in project-config. To work around this problem, we removed
> those job templates in project-config by submitting separate patches
> (rather than waiting for the full clean-up patch). We used the Oslo
> team repos when we were testing some of the new jobs, so it is
> possible this won't come up for any other teams, but I thought I
> would mention the problem and solution, just in case.
>
> We had at least one question about the order in which the patches
> need to land across the branches. We need the ones with the subject
> "import zuul job settings from project-config" to land before the
> others, but it doesn't make any difference which branches go first.
> Those patches should be basically no-ops, neither adding nor changing
> any of the existing testing. The other follow-up patches change or
> add tests, and are submitted separately specifically so the changes
> they contain can be managed and issues fixed to allow them to land.
>
> Nguyen found a couple of cases where older branches did not work
> with the existing documentation job. The fix may require backporting
> changes to remove tox_install.sh, or other changes that have been
> made in newer stable branches but not backported all the way. Because
> the new documentation job runs through tox we may be able to use
> that in the older branches, as an alternative.
>
> We discovered last night that the version of git on CentOS does not
> support the -C option, so we will need to change our scripts to be
> compatible with the older platform.
>
> == Completed work ==
>
> Congratulations to the Documentation team for approving all of the
> patches to import their zuul job configuration!
>
> == Ongoing work ==
>
> The Oslo team is working on migrating their zuul settings.
>
> The Ironic, Vitrage, Cyborg, Solum, Tacker, Masakari, Congress,
> Designate, Mistral, Watcher, Glance, and Requirements teams have
> started migrating their zuul settings.
>
> The Ironic team has started working on adding functional tests that
> run under Python 3.
>
> Thanks to dtantsur for adding a variant of the python 3.6 jobs that
> installs neutron from source, needed by several networking-related
> projects that integrate tightly with neutron.
> https://review.openstack.org/#/c/593643/
>
> == Next Steps ==
>
> If your team is ready to have your zuul settings migrated, please
> let us know by following up to this email. We will start with the
> volunteers, and then work our way through the other teams.
>
> After the Rocky cycle-trailing projects are released, I will propose
> the change to project-config to change all of the packaging jobs
> to use the new publish-to-pypi-python3 template. We should be able
> to have that change in place before the first milestone for Stein
> so that we have an opportunity to test it.
>
> == How can you help? ==
>
> 1. Choose a patch that has failing tests and help fix it.
>
> https://review.openstack.org/#/q/topic:python3-first+status:open+(+label:Verified-1+OR+label:Verified-2+)
> 2. Review the patches for the zuul changes. Keep in mind that some of
>those patches will be on the stable branches for projects.
> 3. Work on adding functional test jobs that run under Python 3.
>
> == How can you ask for help? ==
>
> If you have any questions, please post them here to the openstack-dev
> list with the topic tag [python3] in the subject line. Posting
> questions to the mailing list will give the widest audience the
> chance to see the answers.
>
> We are using the #openstack-dev IRC channel for discussion as well,
> but I'm not sure how good our timezone coverage is so it's probably
> better to use the mailing list.
>
> == Reference Material ==
>
> Goal description:
> https://governance.openstack.org/tc/goals/stein/python3-first.html
> Open patches needing reviews:
> https://review.openstack.org/#/q/topic:python3-first+is:open
> Storyboard: https://storyboard.openstack.org/#!/board/104
> Zuul migration notes: https://etherpad.openstack.org/p/python3-first
> Zuul migration tracking: https://storyboard.openstack.org/#!/story/2002586
> Python 3 Wiki page: https://wiki.openstack.org/wiki/Python3
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
>