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] [Tacker] Redundancy VNFFG module in tacker

[Trinh Nguyen]

Hi Hosung,

Here are a couple suggestions you can follow.

1. You can first follow the OpenStack contributor guidelines and set up the
needed accounts [1].
2. After you have the launchpad account,  register a blueprint for your
feature in Tacker's launchpad [2].
3. Clone the Tacker Specs repository to your local dev environment [3].
Write a spec (detail about your feature, implementation plan, etc.) for
your feature. Commit. and then 'git review' to push your spec to Gerrit [4]
for the Tacker team to review and comment.
4. After the spec has been approved by the core reviewers and Tacker's PTL,
you can start working on the implementation the same way when you write the
spec:

   - Clone the needed repositories (tacker, python-tackerclient, or
   tacker-horizon) to your local dev environment
   - Make changes
   - Commit and review
   - Wait for other to comments and refine your changes.

You can join the Tacker's IRC chat channel (#tacker) to talk to other
Tacker developers.

Hope that will help.

[1]
https://docs.openstack.org/contributors/code-and-documentation/index.html
[2] https://blueprints.launchpad.net/tacker
[3] https://github.com/openstack/tacker-specs
[4] http://review.openstack.org

On Fri, Nov 9, 2018 at 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
>


-- 
*Trinh Nguyen*
*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

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

[백호성]

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

[openstack-dev] [Tacker] Cancelling weekly meeting this week.

[Dharmendra Kushwaha]

Dear Tacker members,

We have discussed most of the thing during PTG on Friday, So cancelling weekly 
meeting for this week.
Please focus on discussed specs & code.

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

[openstack-dev] [Tacker] vPTG meetup schedule

[Dharmendra Kushwaha]

Hi all,



We have planned to have our one-day virtual PTG meetup for Stein on below 
schedule.

Please find the meeting details:



Schedule: 21st September, 7:00UTC to 11:00UTC



Meeting Channel: https://bluejeans.com/553456496

Etherpad link:  https://etherpad.openstack.org/p/Tacker-PTG-Stein



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

[openstack-dev] [Tacker] vPTG Topics gathering

[Dharmendra Kushwaha]

Hi all,

We are planning to have our one-day virtual PTG meetup for Stein during 
20th-21th September.
I have created etherpad link [1]  for the same. Please put your discussion 
topics on that. 
Please do it by Saturday, 8th September, so that I will fix the schedule 
accordingly.

[1]: https://etherpad.openstack.org/p/Tacker-PTG-Stein

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

Re: [openstack-dev] [Tacker] Proposing changes in Tacker Core Team

[Kanagaraj Manickam]

+1. Thanks Tacker community for providing the opportunity to server as
committer/active contributor.


On Wed, Aug 22, 2018 at 9:52 AM 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
>
__
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

[Dharmendra Kushwaha]

Thanks all who responded.

Phuoc, welcome to tacker-core team.

Thanks & Regards
Dharmendra Kushwaha

From: Kim Bao, Long [mailto:lon...@vn.fujitsu.com]
Sent: 22 August 2018 17:45
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Tacker] Proposing changes in Tacker Core Team

+1 from me.
First of all, I would like to thank Phuoc for his contribution in Tacker. As I 
know, Phuoc joined in Tacker project for a year, but his contribution in Tacker 
is highly appreciated. Besides, he also is one of active member in  IRC, gerrit 
and bug report.
Hope that he can help Tacker keep growing in his new role.
LongKB

From: Dharmendra Kushwaha [mailto:dharmendra.kushw...@india.nec.com]
Sent: Wednesday, August 22, 2018 11:21 AM
To: openstack-dev 
mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [Tacker] Proposing changes in Tacker Core Team

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

Re: [openstack-dev] [Tacker] Proposing changes in Tacker Core Team

[Kim Bao, Long]

+1 from me.
First of all, I would like to thank Phuoc for his contribution in Tacker. As I 
know, Phuoc joined in Tacker project for a year, but his contribution in Tacker 
is highly appreciated. Besides, he also is one of active member in  IRC, gerrit 
and bug report.
Hope that he can help Tacker keep growing in his new role.
LongKB

From: Dharmendra Kushwaha [mailto:dharmendra.kushw...@india.nec.com]
Sent: Wednesday, August 22, 2018 11:21 AM
To: openstack-dev 
Subject: [openstack-dev] [Tacker] Proposing changes in Tacker Core Team

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

Re: [openstack-dev] [Tacker] Proposing changes in Tacker Core Team

[Hiroyuki JO]

+1

 

--

Hiroyuki JO

Email: jo.hiroy...@lab.ntt.co.jp, TEL(direct) : +81-422-59-7394

NTT Network Service Systems Laboratories

 

From: Dharmendra Kushwaha [mailto:dharmendra.kushw...@india.nec.com] 
Sent: Wednesday, August 22, 2018 1:21 PM
To: openstack-dev
Subject: [openstack-dev] [Tacker] Proposing changes in Tacker Core Team

 

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
odule=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

Re: [openstack-dev] [Tacker] Proposing changes in Tacker Core Team

[Trinh Nguyen]

+1


*Trinh Nguyen *| Founder & Chief Architect



*E:* dangtrin...@gmail.com | *W:* *www.edlab.xyz *



On Wed, Aug 22, 2018 at 2:21 PM 龚永生  wrote:

> +1
>
>
>
>
> --
> *龚永生*
> *九州云信息科技有限公司 99CLOUD Co. Ltd.*
> 邮箱（Email）：gong.yongsh...@99cloud.net 
> 地址：北京市海淀区上地三街嘉华大厦B座806
> Addr : Room 806, Tower B, Jiahua Building, No. 9 Shangdi 3rd Street,
> Haidian District, Beijing, China
> 手机（Mobile)：+86-18618199879
> 公司网址（WebSite）：http://99cloud.net 
>
> 在 2018-08-22 12:21:22，Dharmendra Kushwaha <
> dharmendra.kushw...@india.nec.com> 写道：
>
> 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
>
__
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

[龚永生]

+1




--
龚永生
九州云信息科技有限公司 99CLOUD Co. Ltd.
邮箱（Email）：gong.yongsh...@99cloud.net
地址：北京市海淀区上地三街嘉华大厦B座806
Addr : Room 806, Tower B, Jiahua Building, No. 9 Shangdi 3rd Street, Haidian 
District, Beijing, China
手机（Mobile)：+86-18618199879
公司网址（WebSite）：http://99cloud.net 



在 2018-08-22 12:21:22，Dharmendra Kushwaha  
写道：
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

Re: [openstack-dev] [Tacker] Proposing changes in Tacker Core Team

[hyunsikYang]

+1

*Sent with Shift
*

2018-08-22 13:23 GMT+09:00 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;
>> release=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
>
>


-- 

*---*

*Hyunsik Yang (Ph. D candidate)*

*DCN laboratory / School of Electronic Engineering*

*Soongsil University *

*511 Sangdo-dong Dongjak-gu*

*Seoul, 156-743 Korea*

*TEL : (+82)-2-820-0841 *

*M.P: (+82)-10-9005-7439*

*Sent with Shift
*
__
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

[openstack-dev] [Tacker] Proposing changes in Tacker Core Team

[Dharmendra Kushwaha]

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

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

[龚永生]

William,
tacker is just using network-sfc API, we have tested the ovs driver of it. 




regards,


yong sheng gong




--

龚永生
九州云信息科技有限公司 99CLOUD Co. Ltd.
邮箱（Email）：gong.yongsh...@99cloud.net
地址：北京市海淀区上地三街嘉华大厦B座806
Addr : Room 806, Tower B, Jiahua Building, No. 9 Shangdi 3rd Street, Haidian 
District, Beijing, China
手机（Mobile)：+86-18618199879
公司网址（WebSite）：http://99cloud.net 

At 2018-08-01 02:17:14, "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

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] [Tacker] - TACKER + NETWORKING_SFC + NSH

[william sales]

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-dev] [Tacker] [PTL] [Elections] Candidacy for Tacker PTL (Stein)

[Dharmendra Kushwaha]

Hi all,

I would like to announce my candidacy as Tacker PTL for the upcoming Stein 
cycle.

I am Dharmendra Kushwaha known as dkushwaha on IRC. I member of Tacker 
community since Mitaka release.  During my journey, I was involved in multiple 
features development activities(like Network Service, alarm based monitoring, 
VNFFG-NS etc.), bug triages, fixes and code improvement activities, verifying 
and testing for team.

It is a great experience for me to working in OpenStack/Tacker project with 
very supportive contributors team. Other than community, I was involved in 
couple of NFV related PoCs and to identify the production gaps in Tacker.

As of now Sridhar and Gong sheng Yang have done a great job with a great team 
support, I have learnt many things from them and would like to serve the 
community on those footprints.

During the journey, Tacker comes with multiple rich features and still growing 
in the same direction. Still we have to do lot more and my main goals of Stein 
are as follow:

* Tacker CI/CD Improvement:
- Currently in Tacker more scenarios and proper integration testing is 
lacking on gate, needs to introduce more coverage.
- Focus to introduce more functional and scenario tests for max code 
coverage.
- We have to setup a process where every code should go with proper 
integration test on gate.

* Tacker stability & production ready:
- Identify industries requirements and prioritize their requirements.
- Focus to have more error-handling and significant logging.
- Cross community contribution for features integration.
- Parallel/large node deployment stability.
- More towards NFV-MANO rich features.

* Growing the community with more active core contributors

* More physical gathering of Tacker team in OpenStack conferences.. 

You can find my complete contributions here:
http://stackalytics.com/?release=all_type=all=commits_id=dharmendra-kushwaha

Thanks for reading and consideration my candidacy.

Thanks & Regards
Dharmendra Kushwaha
IRC: dkushwaha

__
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] [tacker] tacker meeting on Mar. 20th 2018 is cancelled

[龚永生]

hi
Because I am on a trip, the Tacker project meeting on Mar. 20th  is cancelled. 
If you guys need to talk, please go to #tacker channel or send me an email.


please go ahead  according to our PTG meeting.
Regards,


yong sheng gong
99cloud__
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] [tacker] tacker rocky vPTG summary

[龚永生]

hi,
tacker team has held a vPTG via zoom, which is recorded at 
https://etherpad.openstack.org/p/Tacker-PTG-Rocky


in summary:
P1 tasks:
1. web studio for vnf resources
2. sfc across k8s with openstack vims
3. make tacker server with monitoring features scaleable
other tasks:
1. policy for placement
2. vnfs from opensource and vender providers
3. cluster features


thanks for all participants.


regards,


gongysh
tacker ptl
99cloud__
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] [tacker][ptg] tacker vPtg will be held tomorrow

[龚永生]

https://etherpad.openstack.org/p/Tacker-PTG-Rocky



gongys
tacker
99cloud__
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] [tacker] tacker project team meeting is changed to GMT 0800 on Tuesdays

[龚永生]

FYI
https://review.openstack.org/#/c/550326/







yong sheng gong
99CLOUD Co. Ltd.
Email：gong.yongsh...@99cloud.net
Addr : Room 806, Tower B, Jiahua Building, No. 9 Shangdi 3rd Street, Haidian 
District, Beijing, China
Mobile：+86-18618199879
http://99cloud.net __
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] [tacker] tacker project meeting time vote poll

[龚永生]

for more stackers to join tacker project meeting, we are voting new tacker 
project  meeting time at:


https://doodle.com/poll/59dwkpzp84gw9w45


if you are interested in tacker project, please join us. thanks


yong sheng gong


Tacker project team


99cloud__
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] [tacker] PTL candidacy from yong sheng gong

[Yongsheng Gong]

This is my self-nomination to continue running as Tacker PTL for the
Rocky cycle.

Lots happened in Takcer Queens cycle. More documents, More features are coming
in. VNFFG is enhanced, Kubernetes vim and container VNF are introduced.
Private Zabbix based application monitoring is done too. Openstack client Tacker
commands are also being developed.


In Rocky cycle, I plan to

- Continue to stablize tacker and make it of production quality.
- Go on with tacker document.
- Enhance container based VNF
- Make a way to connect VM based VNF and container Based VNF
- Introduce more types of VIM, such as public vim, SDN controller vim


Thanks for your consideration.

Yong sheng gong










__
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] [hacking] [requirements] pep8 to pycodestyle

[Swapnil Kulkarni]

On Tue, Dec 12, 2017 at 4:37 AM, Ben Nemec  wrote:
> It's probably worth noting here that this is to reflect an upstream rename
> from pep8 to pycodestyle, not an actual change in the library we use for
> style checking.  It's mentioned in the commit messages, but for anyone just
> scanning the mailing list it may not be obvious.
>
> I left a review on the hacking change.  I think the comments there about
> shadowing the flake8 module name are valid and we should undo/fix that
> before merging.  Otherwise I'm +2.
>
>
> On 12/04/2017 10:19 PM, Swapnil Kulkarni wrote:
>>
>> We have a change [1] out there which will remove pep8 and use
>> pycodestyle in global requirements. For this change to be merged we
>> need all dependent projects to use the same and check if they have any
>> conflicts. We are waiting for [2] for hacking and [3] for tackerclient
>> to be merged so that we can merge [1] into global requirements.
>>
>> Requesting the cores in the hacking and tacker group to have a look
>> into this and help us move further. Feel free to reply or drop by
>> #openstack-requirements if you have any questions. Thanks in advance.
>>
>> [1] https://review.openstack.org/#/c/514663/
>> [2] https://review.openstack.org/#/c/514934/
>> [3] https://review.openstack.org/#/c/517450/
>>
>


Thanks Ben for your review.

__
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] [hacking] [requirements] pep8 to pycodestyle

[Ben Nemec]

It's probably worth noting here that this is to reflect an upstream 
rename from pep8 to pycodestyle, not an actual change in the library we 
use for style checking.  It's mentioned in the commit messages, but for 
anyone just scanning the mailing list it may not be obvious.


I left a review on the hacking change.  I think the comments there about 
shadowing the flake8 module name are valid and we should undo/fix that 
before merging.  Otherwise I'm +2.


On 12/04/2017 10:19 PM, Swapnil Kulkarni wrote:

We have a change [1] out there which will remove pep8 and use
pycodestyle in global requirements. For this change to be merged we
need all dependent projects to use the same and check if they have any
conflicts. We are waiting for [2] for hacking and [3] for tackerclient
to be merged so that we can merge [1] into global requirements.

Requesting the cores in the hacking and tacker group to have a look
into this and help us move further. Feel free to reply or drop by
#openstack-requirements if you have any questions. Thanks in advance.

[1] https://review.openstack.org/#/c/514663/
[2] https://review.openstack.org/#/c/514934/
[3] https://review.openstack.org/#/c/517450/



__
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] [tacker] [hacking] [requirements] pep8 to pycodestyle

[Swapnil Kulkarni]

We have a change [1] out there which will remove pep8 and use
pycodestyle in global requirements. For this change to be merged we
need all dependent projects to use the same and check if they have any
conflicts. We are waiting for [2] for hacking and [3] for tackerclient
to be merged so that we can merge [1] into global requirements.

Requesting the cores in the hacking and tacker group to have a look
into this and help us move further. Feel free to reply or drop by
#openstack-requirements if you have any questions. Thanks in advance.

[1] https://review.openstack.org/#/c/514663/
[2] https://review.openstack.org/#/c/514934/
[3] https://review.openstack.org/#/c/517450/
-- 
Best Regards,
Swapnil Kulkarni
irc : coolsvap

__
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] Virtual Meetup Schedule poll

[Trinath Somanchi]

+1. Updated the poll.


Best Regards,
Trinath Somanchi | NXP | HSDC, INDIA

From: Dharmendra Kushwaha [mailto:dharmendra.kushw...@nectechnologies.in]
Sent: Wednesday, September 06, 2017 11:41 AM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [Tacker] Virtual Meetup Schedule poll

Hi all,

As we agreed to proceed with our virtual PTG meetup for Queens on 14th 
September. I have created 3 timeslots for meetup, Please vote for the time 
slots as per your availability:
https://beta.doodle.com/poll/wkn6phxvnc8r66sv

Please do it by Saturday, 9th September. Please let me know if something wrong 
about timezone in the poll.

Please also keep adding your topics on: 
https://etherpad.openstack.org/p/tacker-queen-grooming

Thanks & Regards
Dharmendra Kushwaha
IRC: dkushwaha

__
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] [Tacker] Virtual Meetup Schedule poll

[Dharmendra Kushwaha]

Hi all,

As we agreed to proceed with our virtual PTG meetup for Queens on 14th 
September. I have created 3 timeslots for meetup, Please vote for the time 
slots as per your availability:
https://beta.doodle.com/poll/wkn6phxvnc8r66sv

Please do it by Saturday, 9th September. Please let me know if something wrong 
about timezone in the poll.

Please also keep adding your topics on: 
https://etherpad.openstack.org/p/tacker-queen-grooming

Thanks & Regards
Dharmendra Kushwaha
IRC: dkushwaha

__
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

[CRISTIAN ARRIBAS GONZALEZ]

Hello! I can´t see any log, because when i go the /opt/logs, any log of
tacker there  is...

2017-08-17 12:54 GMT+02:00 Daniel Mellado :

> On 08/17/2017 12:43 PM, CRISTIAN ARRIBAS GONZALEZ wrote:
> > Hello,
> >
> > my name is Cristian Arribas, i´m getting stated to use Tacker. I
> > installed tacker
> > with devstack. When I want to deploy the ns service with Tosca Template,
> > a one error ocurre:
> >
> > *Error: *Failed to create NS: Request Failed: internal server error
> > while processing your request.
> >
> > ¿What could be the problem?
> >
> > Best regards.
> >
> > --
> > Cristian Arribas González
> > Ingeniería de Telemática
> >
> >
> > 
> __
> > 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
> >
> Hi Christian, welcome aboard! Did you get to check any logs? I'd
> recommend you to first take a look at that in order to narrow the scope.
>
> Best!
>
> Daniel
>
> __
> 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
>



-- 
Cristian Arribas González
Ingeniería de Telemática
__
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

[Daniel Mellado]

On 08/17/2017 12:43 PM, CRISTIAN ARRIBAS GONZALEZ wrote:
> Hello,
> 
> my name is Cristian Arribas, i´m getting stated to use Tacker. I
> installed tacker
> with devstack. When I want to deploy the ns service with Tosca Template,
> a one error ocurre:
> 
> *Error: *Failed to create NS: Request Failed: internal server error
> while processing your request.
> 
> ¿What could be the problem?
> 
> Best regards.
> 
> -- 
> Cristian Arribas González
> Ingeniería de Telemática
> 
> 
> __
> 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
> 
Hi Christian, welcome aboard! Did you get to check any logs? I'd
recommend you to first take a look at that in order to narrow the scope.

Best!

Daniel

__
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

[Trinath Somanchi]

Can you check the tacker logs at /opt/stack/ for exceptions for this error.


Best Regards,
Trinath Somanchi | NXP | HSDC, INDIA

From: CRISTIAN ARRIBAS GONZALEZ [mailto:100304...@alumnos.uc3m.es]
Sent: Thursday, August 17, 2017 4:14 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] Tacker

Hello,

my name is Cristian Arribas, i´m getting stated to use Tacker. I installed 
tacker
with devstack. When I want to deploy the ns service with Tosca Template, a one 
error ocurre:

Error: Failed to create NS: Request Failed: internal server error while 
processing your request.

¿What could be the problem?

Best regards.

--
Cristian Arribas González
Ingeniería de Telemática
__
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] Tacker

[CRISTIAN ARRIBAS GONZALEZ]

Hello,

my name is Cristian Arribas, i´m getting stated to use Tacker. I installed
tacker
with devstack. When I want to deploy the ns service with Tosca Template, a
one error ocurre:

*Error: *Failed to create NS: Request Failed: internal server error while
processing your request.

¿What could be the problem?

Best regards.

-- 
Cristian Arribas González
Ingeniería de Telemática
__
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] [tacker] vim fernet keys HA deployment

[Eduardo Gonzalez]

Hi,

While deploying master multinode realized vim fernet keys are created
locally only in one node unless barbican is used. This causes only be able
to run one tacker-server service simultaneously.

Question: Is there a method in tacker to make HA multinode without barbican
and without shared storage for vim fernet directory.

This is similar to a glance deployment with file based backend.

Regards
__
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] Self-nomination for PTL in Queens

[Eduardo Gonzalez]

Hi Yong,

Kolla already deploy tacker since ocata :)

Regards

On Wed, Aug 9, 2017, 7:30 AM gongys2017  wrote:

> Hi everyone,
>
> This is my self-nomination to continue running as Takcer PTL for the
> Queens cycle.
>
> In Pike cycle, tacker team is focusing on stablebility and scaling. We have
> introtroduced Barbican to keep VIM credentials and Mistral to do VIM
> monitoring and policies. These are great steps to let Tacker to be stable
> and scalable. In addition, the team has been active in promoting tacker.
> We have joined OPNFV meeting, OpenStack days China and OpenStack
> design summit in Boston.  There are some topic sessions which are
> proposed to Syndey Summit by team.
>
> In Queen cycle, I plan to
>
> - Continue to stablize tacker and make it of production quality.
> - Complete tacker document.
> - Provide kolla way to install tacker. I think tacker will be installed in
> kolla which put
>   tacker in containers. The container way will make tacker easier to use,
>   help many guys to use tacker in short way, compared to devstack
> installation.
> - introduce more kinds of VIMs
> - Promote tacker into other community.
>
> Lets make tacker roll together.
>
> Thanks for your consideration.
>
> --
>
> Thanks,
>
> yong sheng gong
> __
> 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] [tacker] Self-nomination for PTL in Queens

[gongys2017]

Hi everyone,

This is my self-nomination to continue running as Takcer PTL for the 
Queens cycle.

In Pike cycle, tacker team is focusing on stablebility and scaling. We 
haveintrotroduced Barbican to keep VIM credentials and Mistral to do 
VIMmonitoring and policies. These are great steps to let Tacker to be stableand 
scalable. In addition, the team has been active in promoting tacker.We have 
joined OPNFV meeting, OpenStack days China and OpenStackdesign summit in 
Boston.  There are some topic sessions which areproposed to Syndey Summit by 
team.

In Queen cycle, I plan to

- Continue to stablize tacker and make it of production quality.
- Complete tacker document.- Provide kolla way to install tacker. I think 
tacker will be installed in kolla which put  tacker in containers. The 
container way will make tacker easier to use,  help many guys to use tacker in 
short way, compared to devstack installation.
- introduce more kinds of VIMs- Promote tacker into other community.

Lets make tacker roll together.
Thanks for your consideration.

-- 

Thanks,

yong sheng gong
__
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] [Tacker] remove Sripriya Seetharam from core reviewer team

[gongys2017]

Hi,   First,  thank Sripriya Seetharam for her great contribution to Tacker 
project. Howeverfor a long time, she cannot be reached via registered email and 
does not join the projectmeeting and has no review activities.
  So I propose to remove Sripriya from tacker core reviewer team. And also hope 
she cancome back to join the project. If she can keep active contribution, the 
team will considerher core reviewer membership again.
Tacker cores, please respond with your opinion. If no reason is given to do
otherwise, I will remove Sripriya from Tacker core group in one week.
Thank Sripriya again.
Yong sheng gong
Tacker PTL
__
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 yanxingan for Tacker core

[Sridhar Ramaswamy]

+2

Thanks Yan for your contribution to Tacker.

On Jul 27, 2017 10:15 AM, "gongys2017"  wrote:


I am proposing we add Yan xingan as a Tacker core.

Yanxingan is woking in china mobile, a telecom company which has big
requirement
on NFV MANO. We are proud of having him on tacker team, and promoting the
usage of
tacker in his company.

In not long time, he has contributed lots on project, such as review, BP
and active in tacker project meeting.
he has also done presentation on tacker to make propaganda of this project.

Tacker cores, please respond with your opinion. If no reason is given to do
otherwise, I will add Yan xingan to the core group in one week.

Thanks,
Yong Sheng Gong


[1] https://review.openstack.org/#/q/owner:yanxingan%2540cmss.
chinamobile.com


__
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] [Tacker] Proposing yanxingan for Tacker core

[gongys2017]

I am proposing we add Yan xingan as a Tacker core.

Yanxingan is woking in china mobile, a telecom company which has big requirement
on NFV MANO. We are proud of having him on tacker team, and promoting the usage 
of
tacker in his company.

In not long time, he has contributed lots on project, such as review, BP and 
active in tacker project meeting.
he has also done presentation on tacker to make propaganda of this project.

Tacker cores, please respond with your opinion. If no reason is given to do
otherwise, I will add Yan xingan to the core group in one week.

Thanks,
Yong Sheng Gong



[1] https://review.openstack.org/#/q/owner:yanxingan%2540cmss.chinamobile.com__
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-dev][Tacker] Not able to run user_data commands on my instance

[yanxingan]

Hi, Vishnu,

  Openwrt mgmt driver is different with user_data shell cmd.

  User_data shell cmds are injected into vm instance during vm's boot 
stage (cloud-init script), via metadata service. Cloud-init script is 
required in image.


  While mgmt_driver is used to configure vm after booting success. 
Openwrt mgmt driver using ssh to configure vm, which is only used for 
openwrt image, can not used for cirros or ubuntu image.


  User_data can be used for any images, if the image has cloud-init script.

To locate this issue, you can execute this cmd in vm:
$ curl http://169.254.169.254/
And check cloud-init is installed in vm.


On 2017/5/23 8:36, Sridhar Ramaswamy wrote:

Hi Vishnu,

Just to rule out any underlying metadata service issue, can you verify 
if a simple heat stack with user_data [1] works fine first? Also, the 
actual TOSCA -> HOT translated template will be available in tacker.log. 
Try creating a heat stack using that HOT template and make sure the 
intended user_data cmds gets executed..


HTH,
Sridhar

[1] 
https://docs.openstack.org/developer/heat/template_guide/software_deployment.html#user-data-boot-scripts-and-cloud-init



On Mon, May 22, 2017 at 5:08 AM, Vishnu Pajjuri 
> wrote:


  Hi,

I'm have installed openstack with tacker by devstack.

I'm able to run OpenWRT vnf and able to configure the firewall
service with openwrt management driver.

And also able to run shell commands in cirros image which is also
using openwrt management driver.


Now I have created one ubuntu image, and able to launch through tacker.

In this instance i want run some shell commands through tacker's
user_data feature.

But no commands are executing.

Is it possible to run commands on custom images unlike cirros/openwrt?

If yes kindly share the procedure to create proper ubuntu image.



Below is tosca configd file


 tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0

 description: Demo with user-data

 metadata:
   template_name: sample-vnfd-userdata

 topology_template:
   node_templates:
 VDU1:
   type: tosca.nodes.nfv.VDU.Tacker
   capabilities:
 nfv_compute:
   properties:
 num_cpus: 1
 mem_size: 1024 MB
 disk_size: 1 GB
   properties:
 image: ubuntu-image
 config: |
   param0: key1
   param1: key2
 mgmt_driver: openwrt
 config_drive: true
 user_data_format: RAW
 user_data: |
   #!/bin/sh
   echo "my hostname is `hostname`" > /tmp/hostname
   date > /tmp/date
   ifconfig > /tmp/ifconfig
   df -h > /tmp/diskinfo
 CP1:
   type: tosca.nodes.nfv.CP.Tacker
   properties:
 management: true
 order: 0
 anti_spoofing_protection: false
   requirements:
 - virtualLink:
 node: VL1
 - virtualBinding:
 node: VDU1

  VL1:
   type: tosca.nodes.nfv.VL
   properties:
 network_name: net_mgmt
 vendor: ACME

Regards,
-Vishnu

__
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] [Openstack-dev][Tacker] Not able to run user_data commands on my instance

[Sridhar Ramaswamy]

Hi Vishnu,

Just to rule out any underlying metadata service issue, can you verify if a
simple heat stack with user_data [1] works fine first? Also, the actual
TOSCA -> HOT translated template will be available in tacker.log. Try
creating a heat stack using that HOT template and make sure the intended
user_data cmds gets executed..

HTH,
Sridhar

[1]
https://docs.openstack.org/developer/heat/template_guide/software_deployment.html#user-data-boot-scripts-and-cloud-init


On Mon, May 22, 2017 at 5:08 AM, Vishnu Pajjuri 
wrote:

>  Hi,
>
>I'm have installed openstack with tacker by devstack.
>
> I'm able to run OpenWRT vnf and able to configure the firewall service
> with openwrt management driver.
>
> And also able to run shell commands in cirros image which is also using
> openwrt management driver.
>
>
> Now I have created one ubuntu image, and able to launch through tacker.
>
> In this instance i want run some shell commands through tacker's user_data
> feature.
>
> But no commands are executing.
>
> Is it possible to run commands on custom images unlike cirros/openwrt?
>
> If yes kindly share the procedure to create proper ubuntu image.
>
>
>
> Below is tosca configd file
>
>
> tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0
>
> description: Demo with user-data
>
> metadata:
>   template_name: sample-vnfd-userdata
>
> topology_template:
>   node_templates:
> VDU1:
>   type: tosca.nodes.nfv.VDU.Tacker
>   capabilities:
> nfv_compute:
>   properties:
> num_cpus: 1
> mem_size: 1024 MB
> disk_size: 1 GB
>   properties:
> image: ubuntu-image
> config: |
>   param0: key1
>   param1: key2
> mgmt_driver: openwrt
> config_drive: true
> user_data_format: RAW
> user_data: |
>   #!/bin/sh
>   echo "my hostname is `hostname`" > /tmp/hostname
>   date > /tmp/date
>   ifconfig > /tmp/ifconfig
>   df -h > /tmp/diskinfo
> CP1:
>   type: tosca.nodes.nfv.CP.Tacker
>   properties:
> management: true
> order: 0
> anti_spoofing_protection: false
>   requirements:
> - virtualLink:
> node: VL1
> - virtualBinding:
> node: VDU1
>
>  VL1:
>   type: tosca.nodes.nfv.VL
>   properties:
> network_name: net_mgmt
> vendor: ACME
>
> Regards,
> -Vishnu
>
> __
> 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] [Openstack-dev][Tacker] Not able to run user_data commands on my instance

[Vishnu Pajjuri]

 Hi,

   I'm have installed openstack with tacker by devstack.

I'm able to run OpenWRT vnf and able to configure the firewall service with
openwrt management driver.

And also able to run shell commands in cirros image which is also using
openwrt management driver.


Now I have created one ubuntu image, and able to launch through tacker.

In this instance i want run some shell commands through tacker's user_data
feature.

But no commands are executing.

Is it possible to run commands on custom images unlike cirros/openwrt?

If yes kindly share the procedure to create proper ubuntu image.



Below is tosca configd file


tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0

description: Demo with user-data

metadata:
  template_name: sample-vnfd-userdata

topology_template:
  node_templates:
VDU1:
  type: tosca.nodes.nfv.VDU.Tacker
  capabilities:
nfv_compute:
  properties:
num_cpus: 1
mem_size: 1024 MB
disk_size: 1 GB
  properties:
image: ubuntu-image
config: |
  param0: key1
  param1: key2
mgmt_driver: openwrt
config_drive: true
user_data_format: RAW
user_data: |
  #!/bin/sh
  echo "my hostname is `hostname`" > /tmp/hostname
  date > /tmp/date
  ifconfig > /tmp/ifconfig
  df -h > /tmp/diskinfo
CP1:
  type: tosca.nodes.nfv.CP.Tacker
  properties:
management: true
order: 0
anti_spoofing_protection: false
  requirements:
- virtualLink:
node: VL1
- virtualBinding:
node: VDU1

 VL1:
  type: tosca.nodes.nfv.VL
  properties:
network_name: net_mgmt
vendor: ACME

Regards,
-Vishnu
__
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] [Openstack-dev][Tacker] How to update vnf with user_data

[Vishnu Pajjuri]

Hi,
   Someone can help me to update vnf with user_data by using noop or
openwrt mgmt_driver.

Below is my tosca-config-user-data.yaml

vdus:
  VDU1:
config:
user_data: |
  #!/bin/sh
  echo "my hostname is `hostname`" > /tmp/hostname
  df -h > /tmp/diskinfo


Regards,
-vishnu
__
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][OSC] Command naming specs

[Jay Pipes]

On 04/17/2017 07:46 PM, Sridhar Ramaswamy wrote:

I like this suggestion. Keyword 'vnf' is the closest to the unit of
things orchestrated by Tacker. Building on that we can have,

openstack vnf create - /create a single VNF based on TOSCA template/
openstack vnf service create - /create a service using a collection of VNFs/
openstack vnf graph create - /create a forwarding graph using a
collection of VNFs/


++ That is concise and easy to understand/read.


It is not an overlap per-se, it is more at a different abstraction
level. The later is a general purpose, lower-level SFC API based on
neutron ports. Former is a higher level YAML (TOSCA) template based
description of a SFC specially geared for NFV use-cases - implemented
using the lower-level networking-sfc APIs. It is analogous to Heat
OS::Nova::Server <-> Nova Compute APIs.


Understood, thanks for the clarification Sridhar!

Best,
-jay

__
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][OSC] Command naming specs

[Sridhar Ramaswamy]

Hi Jay,

See inline ...

On Fri, Apr 14, 2017 at 12:25 PM, Jay Pipes  wrote:

> On 04/12/2017 03:08 AM, Trinath Somanchi wrote:
>
>> Hi OSC team-
>>
>> While  implementing tacker-cli commands as OSC plugins [1], We are
>> struck in command naming specifications.
>>
>> Tacker being NFVO+VNFM - an NFV component, we have taken ‘nfv’ as the
>> prefix.
>>
>
> It's not *all* of NFV, though.
>

I agree 'nfv' is an umbrella term and it has significance for other
projects as well (like nova).


>
> This problem, by the way, is an indication that Tacker might have too big
> a scope...and a scope that is very much tailored/purpose-built for
> Telcos/NFV. But whatever, I raised this concern during the project
> application as a member of the TC and folks ignored me, so it is what it is
> I guess.


Will stay away from this as we have thrashed this 'scope' question enough
in the TC discussions :)

However, one thing we are forcing ourselves is not use the 'network' as
initial keyword as it clearly belongs in the realm of neutron and its
associated features. What we are looking for is a term like "stack" that
indicates Orchestration (via Heat project) that we slide under.


>
> We were struck in naming the below commands while aligning with the OSC
>> naming specs.
>>
>> For the below commands, for readability, we have added ‘-‘ within the
>> command names.
>>
>> Like,
>>
>>   network-service,  vnf-forwarding-graph, service-function-chain,
>>
>> network-flow-classifier, network-forwarding-path.
>>
>
> I think what Dean and Akihiro were suggesting is to use "vnf" as the first
> "word" in the command list and then use space-delimited commands like so:
>
> openstack vnf network service create
>
> Or just leave off the "network" above, because, well, Tacker doesn't
> create any other type of service..., so:
>
> openstack vnf service create
>


I like this suggestion. Keyword 'vnf' is the closest to the unit of things
orchestrated by Tacker. Building on that we can have,

openstack vnf create - *create a single VNF based on TOSCA template*
openstack vnf service create - *create a service using a collection of VNFs*
openstack vnf graph create - *create a forwarding graph using a collection
of VNFs*
...


>
> and then
>
> openstack vnf forwardinggraph create
>
> and
>
> openstack vnf service function chain create
>
> but then, you'll hit on the obvious overlap with networking-sfc, which
> will bring in the obvious question of "what's the difference between
> Tacker's SFC and networking-sfc's SFC?" which again should lead folks to
> question the scope of Tacker in relation to other OpenStack projects...
>

It is not an overlap per-se, it is more at a different abstraction level.
The later is a general purpose, lower-level SFC API based on neutron ports.
Former is a higher level YAML (TOSCA) template based description of a SFC
specially geared for NFV use-cases - implemented using the lower-level
networking-sfc APIs. It is analogous to Heat OS::Nova::Server <-> Nova
Compute APIs.

- Sridhar


>
> Best,
> -jay
>
>
> __
> 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][OSC] Command naming specs

[Trinath Somanchi]

Agree. Vnffg can be moved as 'vnf forwardinggraph'. Also, we are discussing to 
improve the command readability from an user perspective. 


Thanks,
Trinath Somanchi.

Digital Networking | NXP – Hyderabad – INDIA.
Email: trinath.soman...@nxp.com
Mobile: +91 9866235130 | Off: +91 4033504051


-Original Message-
From: Akihiro Motoki [mailto:amot...@gmail.com] 
Sent: Monday, April 17, 2017 12:32 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [Tacker][OSC] Command naming specs

2017-04-15 12:44 GMT+09:00 Trinath Somanchi <trinath.soman...@nxp.com>:
> Hi Jay-
>
> Thanks for the suggestions, we have improved this to an extent [1].
>
> For  'openstack vnf service function chain create' we agreed to go 
> with, 'openstack nfv chain create' or 'openstack vnf chain create'

I agree with Jay that NFV sounds too broad.
Even though tacker's scope can cover VNF-M and NFV-O, 'nfv' still sound too 
broad to me.
If a command belongs to VNF area, I would suggest to use 'vnf'.
If you have 'nfvo' related commands, you can explore an appropriate word.

VNFM and NFVO are different layers in ETSI and for example I am not sure 'VNF' 
forwarding graph can be called as 'NFV' forwarding graph.

> For ' openstack vnf forwardinggraph create' , you suggestion sounds 
> good. We are thinking on 'openstack vnffg create' in simple terms.

I don't think 'fg' is a common word. It is a bit long but 'forwarding graph' is 
much easier to understand.
'vnffg' is difficult to understand even though I think I know NFV to some 
extent.
Command line completion helps you. You should not think from the developer 
perspective.

Thanks,
Akihiro

> We have come up with a rule for certain commands which conflict with 
> other OpenStack projects,'nfv' is prefixed to differentiate the commands.
>
> The commands that may conflict include ``network-service``, 
> ``classifier``, ``nfp``, ``chain`` and ``event``.
>
> [1]
> https://review.openstack.org/#/c/455188/14/specs/pike/python-openstack
> client.rst
>
> Thanks,
>
> Trinath Somanchi.
>
>
>
> Digital Networking | NXP – Hyderabad – INDIA.
>
> Email: trinath.soman...@nxp.com
>
> Mobile: +91 9866235130 | Off: +91 4033504051
>
>
>
>
>
> -Original Message-
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: Saturday, April 15, 2017 12:55 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Tacker][OSC] Command naming specs
>
>
>
> On 04/12/2017 03:08 AM, Trinath Somanchi wrote:
>
>> Hi OSC team-
>
>>
>
>> While  implementing tacker-cli commands as OSC plugins [1], We are
>
>> struck in command naming specifications.
>
>>
>
>> Tacker being NFVO+VNFM - an NFV component, we have taken ‘nfv’ as the
>
>> prefix.
>
>
>
> It's not *all* of NFV, though.
>
>
>
> This problem, by the way, is an indication that Tacker might have too 
> big a scope...and a scope that is very much tailored/purpose-built for 
> Telcos/NFV.
> But whatever, I raised this concern during the project application as 
> a member of the TC and folks ignored me, so it is what it is I guess.
>
>
>
>> We were struck in naming the below commands while aligning with the
>
>> OSC naming specs.
>
>>
>
>> For the below commands, for readability, we have added ‘-‘ within the
>
>> command names.
>
>>
>
>> Like,
>
>>
>
>>   network-service,  vnf-forwarding-graph,
>
>> service-function-chain,
>
>>
>
>> network-flow-classifier, network-forwarding-path.
>
>
>
> I think what Dean and Akihiro were suggesting is to use "vnf" as the 
> first "word" in the command list and then use space-delimited commands like 
> so:
>
>
>
> openstack vnf network service create
>
>
>
> Or just leave off the "network" above, because, well, Tacker doesn't 
> create any other type of service..., so:
>
>
>
> openstack vnf service create
>
>
>
> and then
>
>
>
> openstack vnf forwardinggraph create
>
>
>
> and
>
>
>
> openstack vnf service function chain create
>
>
>
>
>
> but then, you'll hit on the obvious overlap with networking-sfc, which 
> will bring in the obvious question of "what's the difference between 
> Tacker's SFC and networking-sfc's SFC?" which again should lead folks 
> to question the scope of Tacker in relation to other OpenStack projects...
>
>
>
> Best,
>
> -jay
>
>
>
> ___

Re: [openstack-dev] [Tacker][OSC] Command naming specs

[Akihiro Motoki]

2017-04-15 12:44 GMT+09:00 Trinath Somanchi <trinath.soman...@nxp.com>:
> Hi Jay-
>
> Thanks for the suggestions, we have improved this to an extent [1].
>
> For  'openstack vnf service function chain create' we agreed to go with,
> 'openstack nfv chain create' or 'openstack vnf chain create'

I agree with Jay that NFV sounds too broad.
Even though tacker's scope can cover VNF-M and NFV-O, 'nfv' still
sound too broad to me.
If a command belongs to VNF area, I would suggest to use 'vnf'.
If you have 'nfvo' related commands, you can explore an appropriate word.

VNFM and NFVO are different layers in ETSI and
for example I am not sure 'VNF' forwarding graph can be called as
'NFV' forwarding graph.

> For ' openstack vnf forwardinggraph create' , you suggestion sounds good. We
> are thinking on 'openstack vnffg create' in simple terms.

I don't think 'fg' is a common word. It is a bit long but 'forwarding
graph' is much easier to understand.
'vnffg' is difficult to understand even though I think I know NFV to
some extent.
Command line completion helps you. You should not think from the
developer perspective.

Thanks,
Akihiro

> We have come up with a rule for certain commands which conflict with other
> OpenStack projects,'nfv' is prefixed to differentiate the commands.
>
> The commands that may conflict include ``network-service``, ``classifier``,
> ``nfp``, ``chain`` and ``event``.
>
> [1]
> https://review.openstack.org/#/c/455188/14/specs/pike/python-openstackclient.rst
>
> Thanks,
>
> Trinath Somanchi.
>
>
>
> Digital Networking | NXP – Hyderabad – INDIA.
>
> Email: trinath.soman...@nxp.com
>
> Mobile: +91 9866235130 | Off: +91 4033504051
>
>
>
>
>
> -Original Message-
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: Saturday, April 15, 2017 12:55 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Tacker][OSC] Command naming specs
>
>
>
> On 04/12/2017 03:08 AM, Trinath Somanchi wrote:
>
>> Hi OSC team-
>
>>
>
>> While  implementing tacker-cli commands as OSC plugins [1], We are
>
>> struck in command naming specifications.
>
>>
>
>> Tacker being NFVO+VNFM - an NFV component, we have taken ‘nfv’ as the
>
>> prefix.
>
>
>
> It's not *all* of NFV, though.
>
>
>
> This problem, by the way, is an indication that Tacker might have too big a
> scope...and a scope that is very much tailored/purpose-built for Telcos/NFV.
> But whatever, I raised this concern during the project application as a
> member of the TC and folks ignored me, so it is what it is I guess.
>
>
>
>> We were struck in naming the below commands while aligning with the
>
>> OSC naming specs.
>
>>
>
>> For the below commands, for readability, we have added ‘-‘ within the
>
>> command names.
>
>>
>
>> Like,
>
>>
>
>>   network-service,  vnf-forwarding-graph,
>
>> service-function-chain,
>
>>
>
>> network-flow-classifier, network-forwarding-path.
>
>
>
> I think what Dean and Akihiro were suggesting is to use "vnf" as the first
> "word" in the command list and then use space-delimited commands like so:
>
>
>
> openstack vnf network service create
>
>
>
> Or just leave off the "network" above, because, well, Tacker doesn't create
> any other type of service..., so:
>
>
>
> openstack vnf service create
>
>
>
> and then
>
>
>
> openstack vnf forwardinggraph create
>
>
>
> and
>
>
>
> openstack vnf service function chain create
>
>
>
>
>
> but then, you'll hit on the obvious overlap with networking-sfc, which will
> bring in the obvious question of "what's the difference between Tacker's SFC
> and networking-sfc's SFC?" which again should lead folks to question the
> scope of Tacker in relation to other OpenStack projects...
>
>
>
> Best,
>
> -jay
>
>
>
> __
>
> 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] [Tacker][OSC] Command naming specs

[Trinath Somanchi]

Hi Jay-



Thanks for the suggestions, we have improved this to an extent [1].


For  'openstack vnf service function chain create' we agreed to go with, 
'openstack nfv chain create' or 'openstack vnf chain create'

For ' openstack vnf forwardinggraph create' , you suggestion sounds good. We 
are thinking on 'openstack vnffg create' in simple terms.

We have come up with a rule for certain commands which conflict with other 
OpenStack projects,'nfv' is prefixed to differentiate the commands.
The commands that may conflict include ``network-service``, ``classifier``, 
``nfp``, ``chain`` and ``event``.



[1] 
https://review.openstack.org/#/c/455188/14/specs/pike/python-openstackclient.rst



Thanks,

Trinath Somanchi.



Digital Networking | NXP – Hyderabad – INDIA.

Email: trinath.soman...@nxp.com

Mobile: +91 9866235130 | Off: +91 4033504051





-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Saturday, April 15, 2017 12:55 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Tacker][OSC] Command naming specs



On 04/12/2017 03:08 AM, Trinath Somanchi wrote:

> Hi OSC team-

>

> While  implementing tacker-cli commands as OSC plugins [1], We are

> struck in command naming specifications.

>

> Tacker being NFVO+VNFM - an NFV component, we have taken ‘nfv’ as the

> prefix.



It's not *all* of NFV, though.



This problem, by the way, is an indication that Tacker might have too big a 
scope...and a scope that is very much tailored/purpose-built for Telcos/NFV. 
But whatever, I raised this concern during the project application as a member 
of the TC and folks ignored me, so it is what it is I guess.



> We were struck in naming the below commands while aligning with the

> OSC naming specs.

>

> For the below commands, for readability, we have added ‘-‘ within the

> command names.

>

> Like,

>

>   network-service,  vnf-forwarding-graph,

> service-function-chain,

>

> network-flow-classifier, network-forwarding-path.



I think what Dean and Akihiro were suggesting is to use "vnf" as the first 
"word" in the command list and then use space-delimited commands like so:



openstack vnf network service create



Or just leave off the "network" above, because, well, Tacker doesn't create any 
other type of service..., so:



openstack vnf service create



and then



openstack vnf forwardinggraph create



and



openstack vnf service function chain create





but then, you'll hit on the obvious overlap with networking-sfc, which will 
bring in the obvious question of "what's the difference between Tacker's SFC 
and networking-sfc's SFC?" which again should lead folks to question the scope 
of Tacker in relation to other OpenStack projects...



Best,

-jay



__

OpenStack Development Mailing List (not for usage questions)

Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<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

Re: [openstack-dev] [Tacker][OSC] Command naming specs

[Jay Pipes]

On 04/12/2017 03:08 AM, Trinath Somanchi wrote:

Hi OSC team-

While  implementing tacker-cli commands as OSC plugins [1], We are
struck in command naming specifications.

Tacker being NFVO+VNFM - an NFV component, we have taken ‘nfv’ as the
prefix.


It's not *all* of NFV, though.

This problem, by the way, is an indication that Tacker might have too 
big a scope...and a scope that is very much tailored/purpose-built for 
Telcos/NFV. But whatever, I raised this concern during the project 
application as a member of the TC and folks ignored me, so it is what it 
is I guess.



We were struck in naming the below commands while aligning with the OSC
naming specs.

For the below commands, for readability, we have added ‘-‘ within the
command names.

Like,

  network-service,  vnf-forwarding-graph, service-function-chain,

network-flow-classifier, network-forwarding-path.


I think what Dean and Akihiro were suggesting is to use "vnf" as the 
first "word" in the command list and then use space-delimited commands 
like so:


openstack vnf network service create

Or just leave off the "network" above, because, well, Tacker doesn't 
create any other type of service..., so:


openstack vnf service create

and then

openstack vnf forwardinggraph create

and

openstack vnf service function chain create

but then, you'll hit on the obvious overlap with networking-sfc, which 
will bring in the obvious question of "what's the difference between 
Tacker's SFC and networking-sfc's SFC?" which again should lead folks to 
question the scope of Tacker in relation to other OpenStack projects...


Best,
-jay

__
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][OSC] Command naming specs

[Trinath Somanchi]

Thanks Akihiro for suggestions and comments.
Thanks,
Trinath Somanchi.

Digital Networking | NXP – Hyderabad – INDIA.
Email: trinath.soman...@nxp.com<mailto:trinath.soman...@nxp.com>
Mobile: +91 9866235130 | Off: +91 4033504051


From: Akihiro Motoki [mailto:amot...@gmail.com]
Sent: Thursday, April 13, 2017 8:17 AM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [Tacker][OSC] Command naming specs

networking-sfc has many overlapping areas with tacker and the command names can 
conflict, so I believe it is worth shared in this thread.

networking-sfc team is now implementing OSC commands (as neutronclient OSC 
plugin).
Their command name proposal can be found at 
https://review.openstack.org/#/c/409759/
and command names are like 
https://review.openstack.org/#/c/409759/30/doc/source/usage/osc/v2/networking-sfc.rst

As of now, networking-sfc commands are like:
  openstack sfc port chain create
  openstack sfc port pair group create
  openstack sfc port pair create
  openstack sfc flow classifier create

We would like to use 'sfc' (or 'network sfc') and
hope the tacker team avoid conflicts and confusions between tacker and 
networking-sfc commands.

Personally, 'sfc' is not a well-known abbreviation, but the full spelling 
'service function chaining' looks too long.
I don't think users want to type 'openstack service function chaining port 
chain group create' :-(  It loses usability significantly.

Thanks,
Akihiro

2017-04-13 8:23 GMT+09:00 Trinath Somanchi 
<trinath.soman...@nxp.com<mailto:trinath.soman...@nxp.com>>:
But if we don’t prefix, then we are afraid we might confuse users with command 
names and conflict with other projects.

Example, ‘network-service’ if we follow the existing way, then

$> openstack network service create

might confuse the user in context that it’s a neutron/networking command. Is 
that not True?

Also, for some other commands, like sfc, we might end up conflict with 
networking-sfc.

Like, $> openstack  sfc show  (or) openstack service function chain show

With some of the other commands, there are abbreviations like

$> openstack vnffgd create

If the above command must be split to words, it spells like,

$> openstack virtual network function forwarding graph descriptor create  


If we elaborate this way the command itself will be a lengthy string where user 
has a very lengthy command.

Any suggestions for these?
Thanks,
Trinath Somanchi.

Digital Networking | NXP – Hyderabad – INDIA.
Email: trinath.soman...@nxp.com<mailto:trinath.soman...@nxp.com>
Mobile: +91 9866235130<tel:+91%2098662%2035130> | Off: +91 
4033504051<tel:+91%2040%203350%204051>


From: Dean Troyer [mailto:dtro...@gmail.com<mailto:dtro...@gmail.com>]
Sent: Wednesday, April 12, 2017 10:17 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Tacker][OSC] Command naming specs

On Wed, Apr 12, 2017 at 2:08 AM, Trinath Somanchi 
<trinath.soman...@nxp.com<mailto:trinath.soman...@nxp.com>> wrote:
Tacker being NFVO+VNFM - an NFV component, we have taken ‘nfv’ as the prefix.

Note that OSC itself does not use 'command prefixes', it names resources with 
enough specificity to make them unique.  Sometimes that looks like a proefix, 
but it is not.


For the below commands, for readability, we have added ‘-‘ within the command 
names.
Like,
  network-service,  vnf-forwarding-graph, service-function-chain,
network-flow-classifier, network-forwarding-path.

But the existing OSC commands don’t have a ‘-‘ in between the command names.

The OSC command structure specifically does not use dashes or underscores as 
separators, it uses spaces.  We want commands to be words.  Dashes are only 
used in option names due to option parsing rules.

Specifically in networking there are a large number of resources that are hard 
to concisely name.  Plugins are of course free to do what they want but we 
encourage them to use the OSC guidelines, and we know that users _really_ 
appreciate staying consistent.

There are places where you may feel forced to use abbreviations ('vnf' in your 
example above).  Those are discouraged, but we also recognize that they are 
often the most common usage ('IP' in IP address for example) and where that 
usage is common is fine.  Again, networking is an area where many things are 
commonly known only by their abbreviation, and this usage is in fact expected 
by users.  In the end, picking commands that are what users would expect to 
search for is what they appreciate the most.

dt

--

Dean Troyer
dtro...@gmail.com<mailto:dtro...@gmail.com>

__
OpenStack Development Mailing List (not for usage q

Re: [openstack-dev] [Tacker][OSC] Command naming specs

[Akihiro Motoki]

networking-sfc has many overlapping areas with tacker and the command names
can conflict, so I believe it is worth shared in this thread.

networking-sfc team is now implementing OSC commands (as neutronclient OSC
plugin).
Their command name proposal can be found at
https://review.openstack.org/#/c/409759/
and command names are like
https://review.openstack.org/#/c/409759/30/doc/source/usage/osc/v2/networking-sfc.rst

As of now, networking-sfc commands are like:
  openstack sfc port chain create
  openstack sfc port pair group create
  openstack sfc port pair create
  openstack sfc flow classifier create

We would like to use 'sfc' (or 'network sfc') and
hope the tacker team avoid conflicts and confusions between tacker and
networking-sfc commands.

Personally, 'sfc' is not a well-known abbreviation, but the full spelling
'service function chaining' looks too long.
I don't think users want to type 'openstack service function chaining port
chain group create' :-(  It loses usability significantly.

Thanks,
Akihiro

2017-04-13 8:23 GMT+09:00 Trinath Somanchi <trinath.soman...@nxp.com>:

> But if we don’t prefix, then we are afraid we might confuse users with
> command names and conflict with other projects.
>
>
>
> Example, ‘network-service’ if we follow the existing way, then
>
>
>
> $> openstack network service create
>
>
>
> might confuse the user in context that it’s a neutron/networking command.
> Is that not True?
>
>
>
> Also, for some other commands, like sfc, we might end up conflict with
> networking-sfc.
>
>
>
> Like, $> openstack  sfc show  (or) openstack service function chain show
>
>
>
> With some of the other commands, there are abbreviations like
>
>
>
> $> openstack vnffgd create
>
>
>
> If the above command must be split to words, it spells like,
>
>
>
> $> openstack virtual network function forwarding graph descriptor create
>  
>
>
>
> If we elaborate this way the command itself will be a lengthy string where
> user has a very lengthy command.
>
>
>
> Any suggestions for these?
>
> Thanks,
>
> *Trinath Somanchi.*
>
>
>
> Digital Networking | NXP – Hyderabad – INDIA.
>
> Email: *trinath.soman...@nxp.com <trinath.soman...@nxp.com>*
>
> Mobile: +91 9866235130 <+91%2098662%2035130> | Off: +91 4033504051
> <+91%2040%203350%204051>
>
> [image: cid:image001.png@01D28854.B7934C80]
>
>
>
> *From:* Dean Troyer [mailto:dtro...@gmail.com]
> *Sent:* Wednesday, April 12, 2017 10:17 PM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [Tacker][OSC] Command naming specs
>
>
>
> On Wed, Apr 12, 2017 at 2:08 AM, Trinath Somanchi <
> trinath.soman...@nxp.com> wrote:
>
> Tacker being NFVO+VNFM - an NFV component, we have taken ‘nfv’ as the
> prefix.
>
>
>
> Note that OSC itself does not use 'command prefixes', it names resources
> with enough specificity to make them unique.  Sometimes that looks like a
> proefix, but it is not.
>
>
>
>
>
> For the below commands, for readability, we have added ‘-‘ within the
> command names.
>
> Like,
>
>   network-service,  vnf-forwarding-graph, service-function-chain,
>
> network-flow-classifier, network-forwarding-path.
>
>
>
> But the existing OSC commands don’t have a ‘-‘ in between the command
> names.
>
>
>
> The OSC command structure specifically does not use dashes or underscores
> as separators, it uses spaces.  We want commands to be words.  Dashes are
> only used in option names due to option parsing rules.
>
>
>
> Specifically in networking there are a large number of resources that are
> hard to concisely name.  Plugins are of course free to do what they want
> but we encourage them to use the OSC guidelines, and we know that users
> _really_ appreciate staying consistent.
>
>
>
> There are places where you may feel forced to use abbreviations ('vnf' in
> your example above).  Those are discouraged, but we also recognize that
> they are often the most common usage ('IP' in IP address for example) and
> where that usage is common is fine.  Again, networking is an area where
> many things are commonly known only by their abbreviation, and this usage
> is in fact expected by users.  In the end, picking commands that are what
> users would expect to search for is what they appreciate the most.
>
>
>
> dt
>
>
>
> --
>
>
> Dean Troyer
> dtro...@gmail.com
>
> __
> 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][OSC] Command naming specs

[Trinath Somanchi]

But if we don’t prefix, then we are afraid we might confuse users with command 
names and conflict with other projects.

Example, ‘network-service’ if we follow the existing way, then

$> openstack network service create

might confuse the user in context that it’s a neutron/networking command. Is 
that not True?

Also, for some other commands, like sfc, we might end up conflict with 
networking-sfc.

Like, $> openstack  sfc show  (or) openstack service function chain show

With some of the other commands, there are abbreviations like

$> openstack vnffgd create

If the above command must be split to words, it spells like,

$> openstack virtual network function forwarding graph descriptor create  


If we elaborate this way the command itself will be a lengthy string where user 
has a very lengthy command.

Any suggestions for these?
Thanks,
Trinath Somanchi.

Digital Networking | NXP – Hyderabad – INDIA.
Email: trinath.soman...@nxp.com<mailto:trinath.soman...@nxp.com>
Mobile: +91 9866235130 | Off: +91 4033504051


From: Dean Troyer [mailto:dtro...@gmail.com]
Sent: Wednesday, April 12, 2017 10:17 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [Tacker][OSC] Command naming specs

On Wed, Apr 12, 2017 at 2:08 AM, Trinath Somanchi 
<trinath.soman...@nxp.com<mailto:trinath.soman...@nxp.com>> wrote:
Tacker being NFVO+VNFM - an NFV component, we have taken ‘nfv’ as the prefix.

Note that OSC itself does not use 'command prefixes', it names resources with 
enough specificity to make them unique.  Sometimes that looks like a proefix, 
but it is not.


For the below commands, for readability, we have added ‘-‘ within the command 
names.
Like,
  network-service,  vnf-forwarding-graph, service-function-chain,
network-flow-classifier, network-forwarding-path.

But the existing OSC commands don’t have a ‘-‘ in between the command names.

The OSC command structure specifically does not use dashes or underscores as 
separators, it uses spaces.  We want commands to be words.  Dashes are only 
used in option names due to option parsing rules.

Specifically in networking there are a large number of resources that are hard 
to concisely name.  Plugins are of course free to do what they want but we 
encourage them to use the OSC guidelines, and we know that users _really_ 
appreciate staying consistent.

There are places where you may feel forced to use abbreviations ('vnf' in your 
example above).  Those are discouraged, but we also recognize that they are 
often the most common usage ('IP' in IP address for example) and where that 
usage is common is fine.  Again, networking is an area where many things are 
commonly known only by their abbreviation, and this usage is in fact expected 
by users.  In the end, picking commands that are what users would expect to 
search for is what they appreciate the most.

dt

--

Dean Troyer
dtro...@gmail.com<mailto:dtro...@gmail.com>
__
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][OSC] Command naming specs

[Dean Troyer]

On Wed, Apr 12, 2017 at 2:08 AM, Trinath Somanchi 
wrote:

> Tacker being NFVO+VNFM - an NFV component, we have taken ‘nfv’ as the
> prefix.
>

Note that OSC itself does not use 'command prefixes', it names resources
with enough specificity to make them unique.  Sometimes that looks like a
proefix, but it is not.

For the below commands, for readability, we have added ‘-‘ within the
> command names.
>
> Like,
>
>   network-service,  vnf-forwarding-graph, service-function-chain,
>
> network-flow-classifier, network-forwarding-path.
>
>
>
> But the existing OSC commands don’t have a ‘-‘ in between the command
> names.
>

The OSC command structure specifically does not use dashes or underscores
as separators, it uses spaces.  We want commands to be words.  Dashes are
only used in option names due to option parsing rules.

Specifically in networking there are a large number of resources that are
hard to concisely name.  Plugins are of course free to do what they want
but we encourage them to use the OSC guidelines, and we know that users
_really_ appreciate staying consistent.

There are places where you may feel forced to use abbreviations ('vnf' in
your example above).  Those are discouraged, but we also recognize that
they are often the most common usage ('IP' in IP address for example) and
where that usage is common is fine.  Again, networking is an area where
many things are commonly known only by their abbreviation, and this usage
is in fact expected by users.  In the end, picking commands that are what
users would expect to search for is what they appreciate the most.

dt

-- 

Dean Troyer
dtro...@gmail.com
__
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] [Tacker][OSC] Command naming specs

[Trinath Somanchi]

Hi OSC team-

While  implementing tacker-cli commands as OSC plugins [1], We are struck in 
command naming specifications.

Tacker being NFVO+VNFM - an NFV component, we have taken 'nfv' as the prefix.

We were struck in naming the below commands while aligning with the OSC naming 
specs.

For the below commands, for readability, we have added '-' within the command 
names.
Like,
  network-service,  vnf-forwarding-graph, service-function-chain,
network-flow-classifier, network-forwarding-path.

But the existing OSC commands don't have a '-' in between the command names.

We want to know what is best fit options to rename the commands.
Kindly help us in improving the command names.
[1] https://review.openstack.org/#/c/455188
Thanking you.
/ Trinath Somanchi.

Trinath Somanchi.
Hyderabad Software Development Center (HSDC), GSD , DN,
NXP India Pvt Limited, 1st Floor, Block 3, DLF Cyber City, Gachibowli,
Hyderabad, Telangana, 500032, India

Email: trinath.soman...@nxp.com  | Mobile: +91 
9866235130 | Off: +91 4033504051
[cid:image002.png@01D28854.B7934C80]




__
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] [tacker] VNF Configuration injection issue

[Vishnu Pajjuri]

Hi,
   I'm running tacker and able to launch vnf through VNF manager. But the
configuration of the VNF is not getting injected to VNF.
Kindly help me in debugging of injection of configuration


Please find below tosca config file

tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0

description: OpenWRT with firewall services

metadata:
  template_name: APM

topology_template:
  node_templates:
VDU1:
  type: tosca.nodes.nfv.VDU.Tacker
  capabilities:
nfv_compute:
  properties:
num_cpus: 1
mem_size: 1024 MB
disk_size: 1 GB
  properties:
image: openWRT-image2
config:
  firewall: |
package firewall

config defaults
option syn_flood '1'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'REJECT'

config zone
option name 'lan'
list network 'lan'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'REJECT'

config zone
option name 'wan'
list network 'wan'
list network 'wan6'
option input 'REJECT'
option output 'ACCEPT'
option forward 'REJECT'
option masq '1'
option mtu_fix '1'

config forwarding
option src 'lan'
option dest 'wan'

config rule
option name 'Allow-DHCP-Renew'
option src 'wan'
option proto 'udp'
option dest_port '68'
option target 'ACCEPT'
option family 'ipv4'

config rule
option name 'Allow-Ping'
option src 'wan'
option proto 'icmp'
option icmp_type 'echo-request'
option family 'ipv4'
option target 'REJECT'
mgmt_driver: openwrt
monitoring_policy:
  name: ping
  parameters:
count: 3
interval: 10
  actions:
failure: respawn

CP1:
  type: tosca.nodes.nfv.CP.Tacker
  properties:
management: true
anti_spoofing_protection: false
  requirements:
- virtualLink:
node: VL1
- virtualBinding:
node: VDU1

VL1:
  type: tosca.nodes.nfv.VL
  properties:
network_name: net_mgmt
vendor: Tacker



Note: haven't seen any ssh connection formed to VNF from host during and
after installation.


Thanks && Regards,
-Vishnu
__
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] [tacker] Final mascot files

[Sridhar Ramaswamy]

Hi Tackers,

We got the "final" version of Tacker logo from Openstack marketing team.
Please take a look at the dropbox link below:





*I’m excited to finally be able to share final project logo files with you.
Inside this folder, you’ll find full-color and one-color versions of the
logo, plus a mascot-only version, in EPS, JPG and PNG formats. You can use
them on presentations and wherever else you’d like to add some team flair.
https://www.dropbox.com/sh/yyt1lazllah7ccf/AACkW8LkIiG32OXLYBqeP-RJa?dl=0
At
the PWG, we’ll have stickers for your team of the mascot, plus signage on
your room. I’m especially excited for the project teams to see all of the
logos together as one group, because they work beautifully together
stylistically while making each project’s mark distinctive.*

- Sridhar
__
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] [tacker] Virtual PTG Meetup - Wed Feb 22

[Sridhar Ramaswamy]

Folks -

Tacker team will meet virtually for upcoming Pike PTG. Given the
global audience, we will do one 5 - 6 hour conference call starting
Wednesday, February 22, 2017 -  05:00:00 UTC [1]. Please mark your
calendars.

Here is the PTG etherpad [2]. Feel free to add topics and candidate
pike tasks in the etherpad.

- Sridhar

[1] 
https://www.timeanddate.com/worldclock/meetingtime.html?iso=20170222=283=33=235=176
[2] https://etherpad.openstack.org/p/tacker-pike-grooming

__
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] [Tacker] Tacker upgrade vnf

[lương hữu tuấn]

Hi Tacker folks,

I have my own consideration about vnf upgrade. Please correct me if i am
wrong.

As i saw that tacker supports the vnf update when vnfd and vnfd_id do not
change. What about the situation of upgrading vnf, for instance, i would
like to upgrade my vnf which is deployed with one virtual machine to the
new version which has a cluster of virtual machine, or new flavor, or new
resource model of heat stack. My question is such a this process is called
SCALE in tacker?

Br,

Nokia/Tuan
__
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] [tacker] Tacker Mascot

[Sridhar Ramaswamy]

Tackers,

I received a draft version of our project logo, using the mascot we
selected together. A final version will be ready for us before the Project
Team Gathering in February. Before they make our logo final, they want to
be sure we're happy with our mascot.

Let me know if anyone have suggestions to change. We can briefly discuss
this in our meeting today.

- Sridhar
__
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] [tacker] Cancelling today's weekly meeting

[Sridhar Ramaswamy]

I'm cancelling today's meeting. We have a light agenda and our
contributors from China are off due to holiday week there. Please use
the extra time to continue to wrap up remaining Ocata items,

- VNFC support
- VNF inline templates
- Pending NSD work (api-ref, samples, etc)
- other pending items listed in your respectives BPs [1]

I'll be available in the #tacker channel for any questions or issues.

thanks,
Sridhar

[1] https://blueprints.launchpad.net/tacker/ocata

__
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] Core team changes / proposing Dharmendra Kushwaha

[Sridhar Ramaswamy]

Thanks for those who responded.

Dharmendra - welcome to the tacker-core team!

- Sridhar

On Tue, Jan 24, 2017 at 4:58 PM, Sridhar Ramaswamy  wrote:
> Tackers,
>
> I'd like to propose following changes to the Tacker core team.
>
> Stephen Wong
>
> After being associated with Tacker project from its genesis, Stephen
> Wong (irc: s3wong) has decided to step down from the core-team. I
> would like to thank Stephen for his contribution to Tacker,
> particularly for his help navigating the initial days splitting off
> Neutron and in re-launching this project in Vancouver summit for
> TOSCA-based NFV Orchestration. His recent effort in writing the SFC
> driver to support VNF Forwarding Graph is much appreciated. Thanks
> Stephen!
>
> Dharmendra Kushwaha
>
> It gives me great pleasure to propose Dharmendra (irc:  dkushwaha) to
> join the Tacker core team. Dharmendra's contributions to tacker
> started in Jan 2016. He is an active contributor across the board [1]
> in bug fixes, code cleanups and, most recently, as a lead author of
> the Network Services Descriptor blueprint.
>
> Also, Dharmendra recently stepped up to take care of bug triage for
> Tacker. There is an uptick in deployment issues reported through LP
> [2] and in irc - which itself is a good healthy thing. Now we need to
> respond by fixing the issues reported promptly. Dharmendra’s help will
> be immensely valuable here.
>
> Existing cores - please vote +1 / -1.
>
> thanks,
> Sridhar
>
> [1] 
> http://stackalytics.com/?module=tacker-group_id=dharmendra-kushwaha=marks
> [2] https://answers.launchpad.net/tacker

__
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 PTL Non-candidacy

[Sahdev P Zala]

Hi Sridhar, 

Thanks for your leadership in Tacker for last two years!! Great years for 
the project. I am glad that you will be continuing contributing to the 
project. I look forward to work with you for further collaboration between 
Tacker and TOSCA translator projects.

Regards, 
Sahdev Zala




From:   Sridhar Ramaswamy <sric...@gmail.com>
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Date:   01/18/2017 06:11 PM
Subject:    [openstack-dev] [tacker] Tacker PTL Non-candidacy



As I announced in the last Tacker weekly meeting, I'm not planning to run 
for Pike PTL position. Having served in this role for the last three 
cycles (including for the periods before it was a big-tent project), I 
think it is time for someone else to step in and take this forward. I'll 
continue to contribute as a core-team member. I'll be available to help 
the new PTL in any ways needed.

Personally, it has been a such a rewarding experience. I would like to 
thank all the contributors - cores and non-core members - who supported 
this project and me. We had an incredible amount of cross-project 
collaboration in tacker, with the likes of tosca-parser / heat-translator, 
neutron networking-sfc, senlin, and mistral - my sincere thanks to all the 
PTLs and the members of those projects. 

Now going forward, we have tons to do in Tacker - towards making it a 
leading, community built TOSCA Orchestrator service. And that, not just 
for the current focus area of NFV but also expand into Enterprise and 
Container use-cases. Fun times!

thanks,
Sridhar
irc: sridhar_ram
__
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] Core team changes / proposing Dharmendra Kushwaha

[Sripriya Seetharam]

+1 to Dharmendra, great addition.

Thank you very much Stephen for your contributions.

-Sripriya

On 1/24/17, 4:58 PM, "Sridhar Ramaswamy"  wrote:

Tackers,

I'd like to propose following changes to the Tacker core team.

Stephen Wong

After being associated with Tacker project from its genesis, Stephen
Wong (irc: s3wong) has decided to step down from the core-team. I
would like to thank Stephen for his contribution to Tacker,
particularly for his help navigating the initial days splitting off
Neutron and in re-launching this project in Vancouver summit for
TOSCA-based NFV Orchestration. His recent effort in writing the SFC
driver to support VNF Forwarding Graph is much appreciated. Thanks
Stephen!

Dharmendra Kushwaha

It gives me great pleasure to propose Dharmendra (irc:  dkushwaha) to
join the Tacker core team. Dharmendra's contributions to tacker
started in Jan 2016. He is an active contributor across the board [1]
in bug fixes, code cleanups and, most recently, as a lead author of
the Network Services Descriptor blueprint.

Also, Dharmendra recently stepped up to take care of bug triage for
Tacker. There is an uptick in deployment issues reported through LP
[2] and in irc - which itself is a good healthy thing. Now we need to
respond by fixing the issues reported promptly. Dharmendra’s help will
be immensely valuable here.

Existing cores - please vote +1 / -1.

thanks,
Sridhar

[1] 
https://urldefense.proofpoint.com/v2/url?u=http-3A__stackalytics.com_-3Fmodule-3Dtacker-2Dgroup-26user-5Fid-3Ddharmendra-2Dkushwaha-26metric-3Dmarks=DwIGaQ=IL_XqQWOjubgfqINi2jTzg=hROKXYYshyJWhFmsb7PFSLyhefOI0B-5pQmhOlAcwa8=2xUWkN09oB2b_eRh3Chk_UTkxfU9_RWz1pMhIbO6-ks=pER-09wTI4Zp_jj4e1nSkn8IZjkOpM5TEdEzR5NHeDY=
 
[2] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__answers.launchpad.net_tacker=DwIGaQ=IL_XqQWOjubgfqINi2jTzg=hROKXYYshyJWhFmsb7PFSLyhefOI0B-5pQmhOlAcwa8=2xUWkN09oB2b_eRh3Chk_UTkxfU9_RWz1pMhIbO6-ks=DfUsLy7WZx96tbMnvhC4VG4wZv6wRbc2GQviZzcucaA=
 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev=DwIGaQ=IL_XqQWOjubgfqINi2jTzg=hROKXYYshyJWhFmsb7PFSLyhefOI0B-5pQmhOlAcwa8=2xUWkN09oB2b_eRh3Chk_UTkxfU9_RWz1pMhIbO6-ks=ct4qjMgrzhDQIOMQJN2pFyHPbTWH2F0UciX8DVmPn5M=
 


__
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] Core team changes / proposing Dharmendra Kushwaha

[Bharath Thiruveedula]

+1 for both.

Regards

Bharath T
Imaginea Technologies Inc.

On Wed, Jan 25, 2017 at 8:19 PM, HADDLETON, Robert W (Bob) <
bob.haddle...@nokia.com> wrote:

> +1
>
> Thanks Stephen!  And welcome aboard Dharmendra!
>
> Bob
>
>
> On 1/24/2017 6:58 PM, Sridhar Ramaswamy wrote:
>
>> Tackers,
>>
>> I'd like to propose following changes to the Tacker core team.
>>
>> Stephen Wong
>>
>> After being associated with Tacker project from its genesis, Stephen
>> Wong (irc: s3wong) has decided to step down from the core-team. I
>> would like to thank Stephen for his contribution to Tacker,
>> particularly for his help navigating the initial days splitting off
>> Neutron and in re-launching this project in Vancouver summit for
>> TOSCA-based NFV Orchestration. His recent effort in writing the SFC
>> driver to support VNF Forwarding Graph is much appreciated. Thanks
>> Stephen!
>>
>> Dharmendra Kushwaha
>>
>> It gives me great pleasure to propose Dharmendra (irc:  dkushwaha) to
>> join the Tacker core team. Dharmendra's contributions to tacker
>> started in Jan 2016. He is an active contributor across the board [1]
>> in bug fixes, code cleanups and, most recently, as a lead author of
>> the Network Services Descriptor blueprint.
>>
>> Also, Dharmendra recently stepped up to take care of bug triage for
>> Tacker. There is an uptick in deployment issues reported through LP
>> [2] and in irc - which itself is a good healthy thing. Now we need to
>> respond by fixing the issues reported promptly. Dharmendra’s help will
>> be immensely valuable here.
>>
>> Existing cores - please vote +1 / -1.
>>
>> thanks,
>> Sridhar
>>
>> [1] http://stackalytics.com/?module=tacker-group_id=dharmen
>> dra-kushwaha=marks
>> [2] https://answers.launchpad.net/tacker
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> 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] [tacker] Core team changes / proposing Dharmendra Kushwaha

[HADDLETON, Robert W (Bob)]

+1

Thanks Stephen!  And welcome aboard Dharmendra!

Bob

On 1/24/2017 6:58 PM, Sridhar Ramaswamy wrote:

Tackers,

I'd like to propose following changes to the Tacker core team.

Stephen Wong

After being associated with Tacker project from its genesis, Stephen
Wong (irc: s3wong) has decided to step down from the core-team. I
would like to thank Stephen for his contribution to Tacker,
particularly for his help navigating the initial days splitting off
Neutron and in re-launching this project in Vancouver summit for
TOSCA-based NFV Orchestration. His recent effort in writing the SFC
driver to support VNF Forwarding Graph is much appreciated. Thanks
Stephen!

Dharmendra Kushwaha

It gives me great pleasure to propose Dharmendra (irc:  dkushwaha) to
join the Tacker core team. Dharmendra's contributions to tacker
started in Jan 2016. He is an active contributor across the board [1]
in bug fixes, code cleanups and, most recently, as a lead author of
the Network Services Descriptor blueprint.

Also, Dharmendra recently stepped up to take care of bug triage for
Tacker. There is an uptick in deployment issues reported through LP
[2] and in irc - which itself is a good healthy thing. Now we need to
respond by fixing the issues reported promptly. Dharmendra’s help will
be immensely valuable here.

Existing cores - please vote +1 / -1.

thanks,
Sridhar

[1] 
http://stackalytics.com/?module=tacker-group_id=dharmendra-kushwaha=marks
[2] https://answers.launchpad.net/tacker

__
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] [tacker] Core team changes / proposing Dharmendra Kushwaha

[Sridhar Ramaswamy]

Tackers,

I'd like to propose following changes to the Tacker core team.

Stephen Wong

After being associated with Tacker project from its genesis, Stephen
Wong (irc: s3wong) has decided to step down from the core-team. I
would like to thank Stephen for his contribution to Tacker,
particularly for his help navigating the initial days splitting off
Neutron and in re-launching this project in Vancouver summit for
TOSCA-based NFV Orchestration. His recent effort in writing the SFC
driver to support VNF Forwarding Graph is much appreciated. Thanks
Stephen!

Dharmendra Kushwaha

It gives me great pleasure to propose Dharmendra (irc:  dkushwaha) to
join the Tacker core team. Dharmendra's contributions to tacker
started in Jan 2016. He is an active contributor across the board [1]
in bug fixes, code cleanups and, most recently, as a lead author of
the Network Services Descriptor blueprint.

Also, Dharmendra recently stepped up to take care of bug triage for
Tacker. There is an uptick in deployment issues reported through LP
[2] and in irc - which itself is a good healthy thing. Now we need to
respond by fixing the issues reported promptly. Dharmendra’s help will
be immensely valuable here.

Existing cores - please vote +1 / -1.

thanks,
Sridhar

[1] 
http://stackalytics.com/?module=tacker-group_id=dharmendra-kushwaha=marks
[2] https://answers.launchpad.net/tacker

__
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] [Tacker] Announcing my candidacy for PTL of the Pike cycle

[gongys2017]

Hi All,
Sridhar Ramaswamy and our team have done great work during last several cycles.
Many thanks to the team and Sridhar Ramaswamy.

With this email, I'm announcing my PTL candidacy of the Tacker team for the
Pike release cycle.

First let me briefly introduce myself. I joined the OpenStack community
development in 2012, then became the core member of Neutron team and served
the project for a few cycles. Currently, I'm contributing to Tacker project
as a core member.

Following are my contribution activities:
* Review:  http://stackalytics.com/?release=all=marks_id=gongysh
* Commit:  http://stackalytics.com/?release=all=commits_id=gongysh

As a major leader of 99cloud (active Gold Member of OpenStack Foundation)
I have led 99cloud teams actively participating the upstream activities.
In addition, I introduced Tacker projects to many Chinese companies and
motivated some contributors to join Tacker and related projects.

Here are some ideas I propose the team to focus on in new cycles:
* Documentation - Tacker teams have done fairly well in this area. We should
continue this effort. Nice documentation for new users, especially developers,
will definitely help the project develop.

* Robust architecture – Tacker needs some refactoring in order to be used for
a more robust environment. For example, monitoring feature, VIM feature etc.
We can split some features into components and make them distributed. New API
framework is also one part of this architecture.

* Testing - Tacker originally derived from Neutron, the original testing
framework needs reorganization to fit the Tacker codes. After that, we need to
drive stronger principles to demand better unit and functional test coverage.

* New features - In order for Tacker to become a leading community-built
TOSCA-based Orchestrator service (Inherited from Sridhar, thanks!) in OpenStack,
Tacker need introduce more features, such as TOSCA UI tools, workflows etc.
Of course, the VNF(D), NS(D), VNFFG(D) in MANO via Tacker TOSCA Orchestrator
service will get matured in new cycles.

* Getting more stackers to join - To finish the tons of tasks, we need tons of
contributors. To involve and motivate stackers into Tacker team will be one of
my major tasks.

SDN and NFV is getting hotter and the deployments are accelerating. I would
like to make sure Tacker is getting ready to catch the rising big wave.

Many Thanks to Sridhar and all the dear developers again.

Thank you for your kind consideration of my candidacy.__
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] [tacker] Tacker PTL Non-candidacy

[Sridhar Ramaswamy]

As I announced in the last Tacker weekly meeting, I'm not planning to run
for Pike PTL position. Having served in this role for the last three cycles
(including for the periods before it was a big-tent project), I think it is
time for someone else to step in and take this forward. I'll continue to
contribute as a core-team member. I'll be available to help the new PTL in
any ways needed.

Personally, it has been a such a rewarding experience. I would like to
thank all the contributors - cores and non-core members - who supported
this project and me. We had an incredible amount of cross-project
collaboration in tacker, with the likes of tosca-parser / heat-translator,
neutron networking-sfc, senlin, and mistral - my sincere thanks to all the
PTLs and the members of those projects.

Now going forward, we have tons to do in Tacker - towards making it a
leading, community built TOSCA Orchestrator service. And that, not just for
the current focus area of NFV but also expand into Enterprise and Container
use-cases. Fun times!

thanks,
Sridhar
irc: sridhar_ram
__
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] December 28th weekly meeting cancelled

[Kanagaraj Manickam]

Happy christmas & new year 2017.

Thanks & Regards
Kanagaraj M

On Dec 21, 2016 1:18 PM, "Sridhar Ramaswamy"  wrote:

We are skipping next week's Tacker meeting, on Dec 28th [1]. We will resume
on Jan 4th.

Happy Holidays!!

[1] http://eavesdrop.openstack.org/meetings/tacker/
2016/tacker.2016-12-21-05.30.log.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
__
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] [tacker] December 28th weekly meeting cancelled

[Sridhar Ramaswamy]

We are skipping next week's Tacker meeting, on Dec 28th [1]. We will resume
on Jan 4th.

Happy Holidays!!

[1]
http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-12-21-05.30.log.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

[openstack-dev] [tacker] Weekly meeting agenda - Dec 14, 2016

[Sridhar Ramaswamy]

Here is the agenda for today's tacker weekly meeting,

https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_Dec_14th.2C_2016


   - Announcements
   - Spec-less blueprints rundown
  -
  
https://blueprints.launchpad.net/tacker/+spec/deprecate-legacy-template-dsl
(need
  owner)
  - https://blueprints.launchpad.net/tacker/+spec/switch-to-keystoneauth
  - https://blueprints.launchpad.net/tacker/+spec/vnffgd-param-support
  - https://blueprints.launchpad.net/tacker/+spec/hot-template-support
   - Refactor openstack driver (Haiwei) -
   https://review.openstack.org/405276
   - Tacker-Senlin integration spec (Haiwei / Xuan) -
   https://review.openstack.org/#/c/352943/



*Again, please note the new meeting time,*

*Dec 14th, Wednesday 05:30 UTC @ #openstack-meeting.*

- Sridhar
__
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] Weekly meeting time slot - doodle poll

[Trinath Somanchi]

Thanks a lot Sridhar.

/ Trinath

From: Sridhar Ramaswamy [mailto:sric...@gmail.com]
Sent: Saturday, December 03, 2016 4:37 AM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Cc: Dharmendra Kushwaha <dharmendra.kushw...@gmail.com>; 
<bharath_...@hotmail.com> <bharath_...@hotmail.com>; Tung Doan 
<doantungbk@gmail.com>; Tung Doan <tungd...@dcn.ssu.ac.kr>; 龚永生 
<gong.yongsh...@99cloud.net>
Subject: Re: [openstack-dev] [tacker] Weekly meeting time slot - doodle poll

Thanks for the all those who responded. There is an overwhelming response to go 
with an early UTC time. I'm picking the following slot,

Wednesdays 0530 UTC

I've pushed a request to switch to new this time effective Dec 14th [1]. We 
will continue with use the existing Tuesdays 1600UTC slot for one more week 
(Dec 6th).

[1] https://review.openstack.org/406390

On Tue, Nov 29, 2016 at 10:17 PM, Sridhar Ramaswamy 
<sric...@gmail.com<mailto:sric...@gmail.com>> wrote:
Given the natural changes in the mix of our active members and the recent 
daylight savings time change, I'm opening a doodle poll to find the best slot 
for our weekly meeting with max coverage. Please respond to the doodle poll 
below,

http://doodle.com/poll/ee9p34kfhskd2ucc

Note, this is the same poll shared in today's weekly meeting, though I've added 
more timeslots to pick from. If you've already responded, please log back one 
more time and select all possible slots.

thanks,
Sridhar

__
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] Weekly meeting time slot - doodle poll

[Sridhar Ramaswamy]

Thanks for the all those who responded. There is an overwhelming response
to go with an early UTC time. I'm picking the following slot,

Wednesdays 0530 UTC

I've pushed a request to switch to new this time effective Dec 14th [1]. We
will continue with use the existing Tuesdays 1600UTC slot for one more week
(Dec 6th).

[1] https://review.openstack.org/406390

On Tue, Nov 29, 2016 at 10:17 PM, Sridhar Ramaswamy 
wrote:

> Given the natural changes in the mix of our active members and the recent
> daylight savings time change, I'm opening a doodle poll to find the best
> slot for our weekly meeting with max coverage. Please respond to the doodle
> poll below,
>
> http://doodle.com/poll/ee9p34kfhskd2ucc
>
> Note, this is the same poll shared in today's weekly meeting, though I've
> added more timeslots to pick from. If you've already responded, please log
> back one more time and select all possible slots.
>
> thanks,
> Sridhar
>
__
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] [tacker] Weekly meeting time slot - doodle poll

[Sridhar Ramaswamy]

Given the natural changes in the mix of our active members and the recent
daylight savings time change, I'm opening a doodle poll to find the best
slot for our weekly meeting with max coverage. Please respond to the doodle
poll below,

http://doodle.com/poll/ee9p34kfhskd2ucc

Note, this is the same poll shared in today's weekly meeting, though I've
added more timeslots to pick from. If you've already responded, please log
back one more time and select all possible slots.

thanks,
Sridhar
__
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] Unable to assign IP address to connection points.

[HADDLETON, Robert W (Bob)]

Hi Prasad:
The first two things to check are:

1 - Check the VM instance in Horizon to confirm that there are three IP 
addresses assigned to it.  If there is only one IP address assigned to 
the VM, check the subnet configuration for the vnf_private and private 
networks and make sure they have DHCP enabled.


2 - Verify that the image you are using is configured to enable DHCP on 
eth1 and eth2 or their equivalent network interfaces.


If there ARE three IP addresses assigned to the VM from step 1 then it 
is likely that the image is not configured to support DHCP on eth1 and eth2.
You would need to either modify the image to enabled DHCP on eth1 and 
eth2 and then save the modified image, or find a new image that has DHCP 
enabled on those ports.


Hope this helps

Bob


On 11/16/2016 4:11 AM, prasad kokkula wrote:

Hi All,

[Tacker]   I have tried to launch the vnf Instance using Tacker. vnf 
is launched succesfully and able to do SSH.


I have faced the issue, the connection points (CP2, CP3) are not 
getting ip addreess except managament CP (CP1). Could you please let 
me know is this Tacker issue or any configuration mismatch.


I have installed openstack newton release on Centos 7. Please let me 
know if you need any other configuration.




=
Below are the net-list ip's

[root@localhost (keystone_admin)]# neutron net-list
+--+-+---+
| id   | name| subnets 
  |

+--+-+---+
| 55077c0e-8291-4730-99b4-f280967cb69e | public  | 
39256aad-d075-4c38-bf2c-14613df2252e 172.24.4.224/28 
  |
| 73bbaf70-9bdd-4359-a3a2-09dbd5734341 | private | 
09b9018c-ca3b-46ee-9a4e-507e5124139f 10.0.0.0/24 
  |
| d0560ee9-9ab0-4df8-a0d2-14064950a17c | vnf_mgmt  | 
01d2b67c-ee28-4875-92e0-a8e51fdf8401 192.168.200.0/24 
 |
| f98f38b8-8b6c-4adb-b0e9-a265ce969acf | vnf_private | 
61d39f59-2ff7-4292-afd9-536f007fd30c 192.168.201.0/24 
 |

+--+-+---+
[root@localhost (keystone_admin)]#

Tosca file used for vnf creation.


[root@localhost (keystone_admin)]# cat sample-vnfd.yaml

tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0

description: Demo vCPE example

metadata:
  template_name: sample-tosca-vnfd

topology_template:
  node_templates:
VDU1:
  type: tosca.nodes.nfv.VDU.Tacker
  capabilities:
nfv_compute:
  properties:
num_cpus: 1
mem_size: 512 MB
disk_size: 1 GB
  properties:
image: cirros1
availability_zone: nova
mgmt_driver: noop
user_data_format: RAW
config: |
  param0: key1
  param1: key2

CP1:
  type: tosca.nodes.nfv.CP.Tacker
  properties:
management: true
  requirements:
- virtualLink:
node: VL1
- virtualBinding:
node: VDU1

CP2:
  type: tosca.nodes.nfv.CP.Tacker
  properties:
anti_spoofing_protection: false
  requirements:
- virtualLink:
node: VL2
- virtualBinding:
node: VDU1

CP3:
  type: tosca.nodes.nfv.CP.Tacker
  properties:
anti_spoofing_protection: false
  requirements:
- virtualLink:
node: VL3
- virtualBinding:
node: VDU1

VL1:
  type: tosca.nodes.nfv.VL
  properties:
network_name: vnf_mgmt
vendor: Tacker

VL2:
  type: tosca.nodes.nfv.VL
  properties:
network_name: vnf_private
vendor: Tacker

VL3:
  type: tosca.nodes.nfv.VL
  properties:
network_name: private
vendor: Tacker

===


__
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] [Tacker] Unable to assign IP address to connection points.

[prasad kokkula]

Hi All,

[Tacker]   I have tried to launch the vnf Instance using Tacker. vnf is
launched succesfully and able to do SSH.

I have faced the issue, the connection points (CP2, CP3) are not getting ip
addreess except managament CP (CP1). Could you please let me know is this
Tacker issue or any configuration mismatch.

I have installed openstack newton release on Centos 7. Please let me know
if you need any other configuration.




=
Below are the net-list ip's

[root@localhost (keystone_admin)]# neutron net-list
+--+-+--
-+
| id   | name| subnets
  |
+--+-+--
-+
| 55077c0e-8291-4730-99b4-f280967cb69e | public  |
39256aad-d075-4c38-bf2c-14613df2252e 172.24.4.224/28  |
| 73bbaf70-9bdd-4359-a3a2-09dbd5734341 | private |
09b9018c-ca3b-46ee-9a4e-507e5124139f 10.0.0.0/24  |
| d0560ee9-9ab0-4df8-a0d2-14064950a17c | vnf_mgmt|
01d2b67c-ee28-4875-92e0-a8e51fdf8401 192.168.200.0/24 |
| f98f38b8-8b6c-4adb-b0e9-a265ce969acf | vnf_private |
61d39f59-2ff7-4292-afd9-536f007fd30c 192.168.201.0/24 |
+--+-+--
-+
[root@localhost (keystone_admin)]#

Tosca file used for vnf creation.


[root@localhost (keystone_admin)]# cat sample-vnfd.yaml

tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0

description: Demo vCPE example

metadata:
  template_name: sample-tosca-vnfd

topology_template:
  node_templates:
VDU1:
  type: tosca.nodes.nfv.VDU.Tacker
  capabilities:
nfv_compute:
  properties:
num_cpus: 1
mem_size: 512 MB
disk_size: 1 GB
  properties:
image: cirros1
availability_zone: nova
mgmt_driver: noop
user_data_format: RAW
config: |
  param0: key1
  param1: key2

CP1:
  type: tosca.nodes.nfv.CP.Tacker
  properties:
management: true
  requirements:
- virtualLink:
node: VL1
- virtualBinding:
node: VDU1

CP2:
  type: tosca.nodes.nfv.CP.Tacker
  properties:
anti_spoofing_protection: false
  requirements:
- virtualLink:
node: VL2
- virtualBinding:
node: VDU1

CP3:
  type: tosca.nodes.nfv.CP.Tacker
  properties:
anti_spoofing_protection: false
  requirements:
- virtualLink:
node: VL3
- virtualBinding:
node: VDU1

VL1:
  type: tosca.nodes.nfv.VL
  properties:
network_name: vnf_mgmt
vendor: Tacker

VL2:
  type: tosca.nodes.nfv.VL
  properties:
network_name: vnf_private
vendor: Tacker

VL3:
  type: tosca.nodes.nfv.VL
  properties:
network_name: private
vendor: Tacker


===
__
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] [tacker] No Tacker weekly meeting today

[Sripriya Seetharam]

Hi Tackers,

There will be no weekly meeting today as there are no agenda items from the 
team. We will meet next week on Nov 22nd 2016. Please feel free to add your 
agenda items in meeting wiki link [1].

[1] https://wiki.openstack.org/wiki/Meetings/Tacker#Agenda


Thanks,
Sripriya
__
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] [tacker] Tacker design sessions summary

[Sripriya Seetharam]

Hello Tackers,

Here is a high level summary (delayed!) of the Tacker design sessions [1] at 
the summit. Please feel free to add/comment on the notes in case I have missed 
any.

Fishbowl session:

Topic-1: VMware / vCloud, Public Cloud
There is a need for supporting VIMs beyond OpenStack in Tacker. It was 
suggested that native VMware deployment using vcloud is typical in customer 
deployments. There was also discussion on VMware integrated OpenStack as a 
deployment choice. Both options were explored and the general agreement was to 
use the vCloud api to talk to VMware VIM. The open vCloud API is able to 
support complex resource requests from Tacker with a rich set of REST APIs. 
Action items include revisiting the current VIM API that will allow any VIM to 
be registered in Tacker and reference OpenStack driver be part of VIM module, 
drivers including VMware will reside outside Tacker project. CI options - 3rd 
party CI testing similar to Nova VMware driver tests needs to be integrated in 
Tacker. Tacker feature compatibility such as - scaling, monitoring, mgmt 
driver, auto network, auto flavor creation need to be evaluated and implemented 
specific to vCloud API.

Topic 2: Containerized VNFs
The topic was around exploring the current options for launching VNFs as 
containers. Zun project provides API for containers life cycle management. 
There are still questions around how to consume zun's REST APIs and its
interaction with container networking project such as Kuryr. Also, the role of 
VIM in container management such as OpenStack using Zun, VMware vCloud using 
photon was discussed to identify the support required by VIM for container 
management. It was agreed that a spec needs to be created to come with a plan 
for 1st iteration of container support in Tacker.

Work sessions:

Topic 1: NSD - Mistral Integration
The role of workflow composer such as mistral was discussed to implement the 
NSD feature. Given, NSD template describes a complex network service, there are 
benefits in bringing mistral to process the template with dependency 
requirements or to initiate resource requests in parallel. Also, any error 
scenarios or forking sub tasks on certain matching VNF criteria can be handled 
with mistral support, especially for forwarding graphs. The action items 
identified was to build a basic translator that can map simple NSD TOSCA 
templates to Mistral workflow files in the 1st iteration for Ocata cycle. This 
can later be evolved to handle more complex requirements of NSD.

Topic 2: EM Interface Evolution
The discussion was around defining the API interactions between Tacker and 
external EM interface for VNF management. It was agreed that there is no 
standard way to define and implement this feature. The orchestrator and 
framework should implement a basic version of this interaction and later evolve 
it as more requirements are gathered. There needs to be a feedback loop from EM 
interface to Tacker to drive the policies and performance SLAs of VNFs. The 
orchestrator needs to provide the calls to EM interface for VNF configuration 
management. Also, VNF change notifications should be monitored by the EM 
interface and the data sent as a loopback to Tacker to trigger action requests.

Topic 3: Senlin Integration:
Senlin team provided a good overview of the project and described cluster 
management for scaling and HA policies in Tacker. Heat-translator provides 
supports for senlin resources. Also, senlin integration generates multiple 
templates including profiles and clusters that will have to be handled and 
managed within Tacker. There needs to be support for specifying target set of 
nodes/VDUs that needs to be scaled out/scaled in by senlin. There are 
challenges in translating tosca scaling policies and vnf properties to senlin 
resource types such as profile, cluster and policy as there is no 1:1 mapping 
of these resources between tosca template and senlin heat templates. It was 
agreed that an initial support can be brought in as an alternative to heat auto 
scaling if senlin is deployed on the system.

Cross project discussions
Topic: 4 tosca-parser/heat-translator:
The TP/HT folks updated the team on the 2 features that are brought in for 
Ocata cycle. 1. nested-templates which is required for target VDU scaling and 
2.substitution mappings required for NSD implementation. The team discussed on 
supporting forwarding graph in NSD in tosca-parser project. The action item 
identified was to find the gaps between the NSD spec in tosca profile and 
tosca-parser support and TP team will correspondingly follow up with the 
required fixes.

Topic 5: networking-sfc:
Tacker is now using networking-sfc to implement forwarding graphs. The ask was 
to rely on a stable branch of networking-sfc to bring in the functional tests 
for forwarding graphs in Tacker. The networking-sfc team will create newton 
release in December and will follow the regular release schedule going forward 
from 

[openstack-dev] [tacker] Weekly meeting cancelled for Oct 25th 2016 and Nov 1st 2016

[Sripriya Seetharam]

Hi Tackers,

Tacker weekly meeting is cancelled for the following 2 weeks i.e., Oct 25th 
2016 and Nov 1st 2016 in lieu of the summit and folks travelling back. We will 
resume on Nov 8th 2016.

Have a great summit and safe travels!

-Sripriya

__
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] [Tacker] Ocata design summit topics

[Sripriya Seetharam]

Hi Tackers,

We have the Ocata design summit topics and initial agenda items captured in the 
below etherpad link:

https://etherpad.openstack.org/p/tacker-ocata-summit

The OpenStack design summit schedule page has also been updated to reflect 
these topics in the fishbowl and working sessions.

Feel free to add your inputs/thoughts on the topics. See you all at the summit!

Thanks,
Sripriya
__
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] Presence at PTG Atlanta

[Sripriya Seetharam]

Hi,

Based on team’s decision in tacker weekly meeting [1], Tacker team has decided 
to have a virtual developer meetup and not have PTG presence in Atlanta. Given, 
most of our contributors are geographically spread out, it was decided that the 
virtual midcycle format would be more appropriate in getting the maximum number 
of contributors together to conduct the design meetup.

Thanks,
Sripriya

[1] 
http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-10-11-16.00.html


From: Sripriya Seetharam <ssee...@brocade.com>
Date: Monday, October 10, 2016 at 12:05 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Subject: [openstack-dev][Tacker] Presence at PTG Atlanta

Hi Tackers,

As you all know, the first PTG meetup (Pike cycle) is happening at Atlanta, Feb 
20-24, 2017. This is as per the new format starting after Barcelona conference, 
where design summit happens in between two OpenStack conferences. Please read 
[1] for more details. I believe our traditional virtual mid cycle meetups have 
been effective for project scoping and discussions and we could have something 
similar for design summit. We can discuss in the upcoming Tacker weekly meeting 
and also in mailing list to provide our decision.

Thanks,
Sripriya

[1] https://www.openstack.org/ptg/
__
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] [Tacker] Presence at PTG Atlanta

[Sripriya Seetharam]

Hi Tackers,

As you all know, the first PTG meetup (Pike cycle) is happening at Atlanta, Feb 
20-24, 2017. This is as per the new format starting after Barcelona conference, 
where design summit happens in between two OpenStack conferences. Please read 
[1] for more details. I believe our traditional virtual mid cycle meetups have 
been effective for project scoping and discussions and we could have something 
similar for design summit. We can discuss in the upcoming Tacker weekly meeting 
and also in mailing list to provide our decision.

Thanks,
Sripriya

[1] https://www.openstack.org/ptg/
__
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] [networking-sfc] Removing required port-id from classifier

[Tim Rozet]

Thanks Igor! Anil and I can help test out real NSH support when we have the 
networking-odl driver finished.  That would be a good way to exercise that side 
of networking-sfc code.  Will look at these patches.

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Duarte Cardoso, Igor" <igor.duarte.card...@intel.com>
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>, "Cathy Zhang" <cathy.h.zh...@huawei.com>
Sent: Wednesday, October 5, 2016 6:06:02 AM
Subject: Re: [openstack-dev] [tacker] [networking-sfc] Removing required 
port-idfrom classifier

Hi Tim,

Just about the second part of your email:

> how are IETF SFC/NSH related API/plugin changes going?  
I'm essentially finished with NSH encap support [1], just have to fix a few 
bugs and write the tests. Then I will work on connecting port-chains together 
so we can have SFC graphs, kind of like IETF's branching/reclassification "SFC 
Encapsulation" chains (described with higher detail in the NSH draft).

> Can we expect to have attributes like path-id, encap type soon?  
The NSH patch I mentioned above will allow NSH encap to be specified for both 
port-chains and port-pairs and, if port-pairs do not support the port-chain's 
encapsulation, it's up to the driver to SFC-Proxy the traffic accordingly (OVS 
will install SFC-proxy flows, just like it does today by default, for MPLS). 
Regarding the path-id, I was working on a patch to facilitate that [2], but we 
ended up merging one focused only on enabling the path-id ("chain_id") [3]. So 
we have both attributes now.

[1] https://review.openstack.org/#/c/373465
[2] https://review.openstack.org/#/c/346175
[3] https://review.openstack.org/#/c/355336

Best regards,
Igor.

-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com] 
Sent: Tuesday, October 4, 2016 6:07 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>; Cathy Zhang <cathy.h.zh...@huawei.com>
Subject: [openstack-dev] [tacker] [networking-sfc] Removing required port-id 
from classifier

Hi Cathy,
I recall a while back discussing removing the required neutron port-id from the 
classifier.  We just finished up implementing VNFFG in Tacker and are hitting 
this while testing.  What is the plan to remove this requirement?  Also, how 
are IETF SFC/NSH related API/plugin changes going?  Can we expect to have 
attributes like path-id, encap type soon?  

Thanks,

Tim Rozet
Red Hat SDN Team

__
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] [tacker] [networking-sfc] Removing required port-id from classifier

[Duarte Cardoso, Igor]

Hi Tim,

Just about the second part of your email:

> how are IETF SFC/NSH related API/plugin changes going?  
I'm essentially finished with NSH encap support [1], just have to fix a few 
bugs and write the tests. Then I will work on connecting port-chains together 
so we can have SFC graphs, kind of like IETF's branching/reclassification "SFC 
Encapsulation" chains (described with higher detail in the NSH draft).

> Can we expect to have attributes like path-id, encap type soon?  
The NSH patch I mentioned above will allow NSH encap to be specified for both 
port-chains and port-pairs and, if port-pairs do not support the port-chain's 
encapsulation, it's up to the driver to SFC-Proxy the traffic accordingly (OVS 
will install SFC-proxy flows, just like it does today by default, for MPLS). 
Regarding the path-id, I was working on a patch to facilitate that [2], but we 
ended up merging one focused only on enabling the path-id ("chain_id") [3]. So 
we have both attributes now.

[1] https://review.openstack.org/#/c/373465
[2] https://review.openstack.org/#/c/346175
[3] https://review.openstack.org/#/c/355336

Best regards,
Igor.

-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com] 
Sent: Tuesday, October 4, 2016 6:07 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>; Cathy Zhang <cathy.h.zh...@huawei.com>
Subject: [openstack-dev] [tacker] [networking-sfc] Removing required port-id 
from classifier

Hi Cathy,
I recall a while back discussing removing the required neutron port-id from the 
classifier.  We just finished up implementing VNFFG in Tacker and are hitting 
this while testing.  What is the plan to remove this requirement?  Also, how 
are IETF SFC/NSH related API/plugin changes going?  Can we expect to have 
attributes like path-id, encap type soon?  

Thanks,

Tim Rozet
Red Hat SDN Team

__
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] [tacker] Newton retrospective - notes

[Sridhar Ramaswamy]

Tackers -

I've captured the notes from newton retrospective topic from last week's
meeting,

https://etherpad.openstack.org/p/tacker-newton-retrospective

Let's make Ocata dev cycle even better!
__
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] [tacker] [networking-sfc] Removing required port-id from classifier

[Tim Rozet]

Hi Cathy,
I recall a while back discussing removing the required neutron port-id from the 
classifier.  We just finished up implementing VNFFG in Tacker and are hitting 
this while testing.  What is the plan to remove this requirement?  Also, how 
are IETF SFC/NSH related API/plugin changes going?  Can we expect to have 
attributes like path-id, encap type soon?  

Thanks,

Tim Rozet
Red Hat SDN Team

__
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][ptl] Leave of Absence

[Doug Hellmann]

Excerpts from Sridhar Ramaswamy's message of 2016-10-03 23:26:16 -0700:
> Tackers,
> 
> I'd like to inform I'll be away from work / the community for about 4 - 6
> weeks to attend to an urgent medical need.  This also means I won't be able
> to attend the upcoming Barcelona summit. I'll terribly miss the event,
> particularly meeting some of the new faces in the Tacker community.
> 
> I'm happy that the Newton release is behind us, and Ocata summit planning
> is well underway [1]. I'd like to nominate tacker core Sripriya Seetharam
> (irc: sripriya) as the acting PTL to continue the work forward in my
> absence .
> 
> thanks,
> Sridhar
> 
> [1] https://etherpad.openstack.org/p/tacker-ocata-summit

Thank you for ensuring there is someone filling the PTL role in your
absence, Sridhar, and good luck with your medical situation. I'm sure
the whole team wishes you a quick recovery.

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-dev] [tacker][ptl] Leave of Absence

[Sridhar Ramaswamy]

Tackers,

I'd like to inform I'll be away from work / the community for about 4 - 6
weeks to attend to an urgent medical need.  This also means I won't be able
to attend the upcoming Barcelona summit. I'll terribly miss the event,
particularly meeting some of the new faces in the Tacker community.

I'm happy that the Newton release is behind us, and Ocata summit planning
is well underway [1]. I'd like to nominate tacker core Sripriya Seetharam
(irc: sripriya) as the acting PTL to continue the work forward in my
absence .

thanks,
Sridhar

[1] https://etherpad.openstack.org/p/tacker-ocata-summit
__
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] PTL candidacy

[Janki Chhatbar]

+1

On 17-Sep-2016 10:30 am, "Trinath Somanchi" <trinath.soman...@nxp.com>
wrote:

> +1
> --
> *From:* Sridhar Ramaswamy <sric...@gmail.com>
> *Sent:* Saturday, September 17, 2016 3:40:18 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* [openstack-dev] [tacker] PTL candidacy
>
> Hi Tackers,
>
> I would like to announce my candidacy to continue as Tacker PTL for the
> Ocata
> dev cycle.
>
> I'm a member of the Tacker community right from its Neutron ServiceVM days.
> I actively participated in its transition into NFV Orchestration area and
> its
> graduation into big-tent. Since becoming an official project our developer
> community has grown and has more diverse [1].
>
> Newton was a packed cycle for us with many stellar achievements from the
> community: VNF Scaling, Audit Events, VNF Forwarding Graph using Neutron
> Networking-SFC (we are almost there!) and External Alarm-based Monitoring
> using Ceilometer. As usual tons of refactoring work happened to continue
> to shed the "Neutronisms" in the project.
>
> Along the way, we have become a better openstack citizen following best
> practices like Reno release-notes, better release processes, and better
> python3 support. We also expanded our core-team with three new members.
>
> My vision for Tacker Ocata is along the following workstreams identified
> in the recent weekly meeting.
>
> * Decomposed VIM drivers:
> We need to enable a healthy ecosystem of VIM drivers beyond the current
> default openstack VIM driver. Our user community has mixed hypervisor/cloud
> technology in their deployments - with some existing pre-openstack systems
> (a.la, VMware), some OpenStack based clouds, and, forward looking into
> Containers and public clouds. All this needs an easy to add VIM driver to
> bolt underneath Tacker. Luckily our architecture is designed with this in
> mind right from day one. We just need to make it easy (a) for developers to
> bring in new VIM drivers and (b) for deployers to quickly add new VIM
> capabilities without requiring a fork-lift upgrade of Tacker for every new
> VIM type.
>
> As part of this workstream, I'd work towards bringing in a Container VIM
> type interfacing with Magnum / Zun.
>
> Lifecycle Features:
> * Finish left over Newton features - VNFC and NSD
> * Better integration with external EM / FCAPS systems
> * Enable support for VNFs leveraging Neutron's latest VLAN aware VM
> feature
>
> Project maintenance:
>  * Doc: API reference guide
>  * Pecan API framework
>  * OSC support
>  * Finish python3x TC goal
>
> Tons of fun things to do! However, Ocata is going to be a short cycle.
> So, over next few weeks, I'll help to continue to groom these topics and
> zoom in on those that are implementable in one dev cycle and clearly
> identify some tracks that would carry over to the next cycle.
>
> In Ocata, given an opportunity to serve as your PTL, I'll continue my role
> as the "chief enabler" for this amazing community of developers that I'm so
> proud to lead over the last two cycles.
>
> - Sridhar Ramaswamy (irc: sridhar_ram)
>
> [1] http://stackalytics.com/?module=tacker-group=commits
>
>
> __
> 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] PTL candidacy

[Trinath Somanchi]

+1


From: Sridhar Ramaswamy <sric...@gmail.com>
Sent: Saturday, September 17, 2016 3:40:18 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [tacker] PTL candidacy

Hi Tackers,

I would like to announce my candidacy to continue as Tacker PTL for the Ocata
dev cycle.

I'm a member of the Tacker community right from its Neutron ServiceVM days.
I actively participated in its transition into NFV Orchestration area and its
graduation into big-tent. Since becoming an official project our developer
community has grown and has more diverse [1].

Newton was a packed cycle for us with many stellar achievements from the
community: VNF Scaling, Audit Events, VNF Forwarding Graph using Neutron
Networking-SFC (we are almost there!) and External Alarm-based Monitoring
using Ceilometer. As usual tons of refactoring work happened to continue
to shed the "Neutronisms" in the project.

Along the way, we have become a better openstack citizen following best
practices like Reno release-notes, better release processes, and better
python3 support. We also expanded our core-team with three new members.

My vision for Tacker Ocata is along the following workstreams identified
in the recent weekly meeting.

* Decomposed VIM drivers:
We need to enable a healthy ecosystem of VIM drivers beyond the current
default openstack VIM driver. Our user community has mixed hypervisor/cloud
technology in their deployments - with some existing pre-openstack systems
(a.la<http://a.la>, VMware), some OpenStack based clouds, and, forward looking 
into
Containers and public clouds. All this needs an easy to add VIM driver to
bolt underneath Tacker. Luckily our architecture is designed with this in
mind right from day one. We just need to make it easy (a) for developers to
bring in new VIM drivers and (b) for deployers to quickly add new VIM
capabilities without requiring a fork-lift upgrade of Tacker for every new
VIM type.

As part of this workstream, I'd work towards bringing in a Container VIM
type interfacing with Magnum / Zun.

Lifecycle Features:
* Finish left over Newton features - VNFC and NSD
* Better integration with external EM / FCAPS systems
* Enable support for VNFs leveraging Neutron's latest VLAN aware VM feature

Project maintenance:
 * Doc: API reference guide
 * Pecan API framework
 * OSC support
 * Finish python3x TC goal

Tons of fun things to do! However, Ocata is going to be a short cycle.
So, over next few weeks, I'll help to continue to groom these topics and
zoom in on those that are implementable in one dev cycle and clearly
identify some tracks that would carry over to the next cycle.

In Ocata, given an opportunity to serve as your PTL, I'll continue my role
as the "chief enabler" for this amazing community of developers that I'm so
proud to lead over the last two cycles.

- Sridhar Ramaswamy (irc: sridhar_ram)

[1] http://stackalytics.com/?module=tacker-group=commits

__
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] PTL candidacy

[Henry Fourie]

+1

From: Sridhar Ramaswamy [mailto:sric...@gmail.com]
Sent: Friday, September 16, 2016 3:10 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [tacker] PTL candidacy

Hi Tackers,

I would like to announce my candidacy to continue as Tacker PTL for the Ocata
dev cycle.

I'm a member of the Tacker community right from its Neutron ServiceVM days.
I actively participated in its transition into NFV Orchestration area and its
graduation into big-tent. Since becoming an official project our developer
community has grown and has more diverse [1].

Newton was a packed cycle for us with many stellar achievements from the
community: VNF Scaling, Audit Events, VNF Forwarding Graph using Neutron
Networking-SFC (we are almost there!) and External Alarm-based Monitoring
using Ceilometer. As usual tons of refactoring work happened to continue
to shed the "Neutronisms" in the project.

Along the way, we have become a better openstack citizen following best
practices like Reno release-notes, better release processes, and better
python3 support. We also expanded our core-team with three new members.

My vision for Tacker Ocata is along the following workstreams identified
in the recent weekly meeting.

* Decomposed VIM drivers:
We need to enable a healthy ecosystem of VIM drivers beyond the current
default openstack VIM driver. Our user community has mixed hypervisor/cloud
technology in their deployments - with some existing pre-openstack systems
(a.la<http://a.la>, VMware), some OpenStack based clouds, and, forward looking 
into
Containers and public clouds. All this needs an easy to add VIM driver to
bolt underneath Tacker. Luckily our architecture is designed with this in
mind right from day one. We just need to make it easy (a) for developers to
bring in new VIM drivers and (b) for deployers to quickly add new VIM
capabilities without requiring a fork-lift upgrade of Tacker for every new
VIM type.

As part of this workstream, I'd work towards bringing in a Container VIM
type interfacing with Magnum / Zun.

Lifecycle Features:
* Finish left over Newton features - VNFC and NSD
* Better integration with external EM / FCAPS systems
* Enable support for VNFs leveraging Neutron's latest VLAN aware VM feature

Project maintenance:
 * Doc: API reference guide
 * Pecan API framework
 * OSC support
 * Finish python3x TC goal

Tons of fun things to do! However, Ocata is going to be a short cycle.
So, over next few weeks, I'll help to continue to groom these topics and
zoom in on those that are implementable in one dev cycle and clearly
identify some tracks that would carry over to the next cycle.

In Ocata, given an opportunity to serve as your PTL, I'll continue my role
as the "chief enabler" for this amazing community of developers that I'm so
proud to lead over the last two cycles.

- Sridhar Ramaswamy (irc: sridhar_ram)

[1] http://stackalytics.com/?module=tacker-group=commits

__
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] [tacker] PTL candidacy

[Sridhar Ramaswamy]

Hi Tackers,

I would like to announce my candidacy to continue as Tacker PTL for the
Ocata
dev cycle.

I'm a member of the Tacker community right from its Neutron ServiceVM days.
I actively participated in its transition into NFV Orchestration area and
its
graduation into big-tent. Since becoming an official project our developer
community has grown and has more diverse [1].

Newton was a packed cycle for us with many stellar achievements from the
community: VNF Scaling, Audit Events, VNF Forwarding Graph using Neutron
Networking-SFC (we are almost there!) and External Alarm-based Monitoring
using Ceilometer. As usual tons of refactoring work happened to continue
to shed the "Neutronisms" in the project.

Along the way, we have become a better openstack citizen following best
practices like Reno release-notes, better release processes, and better
python3 support. We also expanded our core-team with three new members.

My vision for Tacker Ocata is along the following workstreams identified
in the recent weekly meeting.

* Decomposed VIM drivers:
We need to enable a healthy ecosystem of VIM drivers beyond the current
default openstack VIM driver. Our user community has mixed hypervisor/cloud
technology in their deployments - with some existing pre-openstack systems
(a.la, VMware), some OpenStack based clouds, and, forward looking into
Containers and public clouds. All this needs an easy to add VIM driver to
bolt underneath Tacker. Luckily our architecture is designed with this in
mind right from day one. We just need to make it easy (a) for developers to
bring in new VIM drivers and (b) for deployers to quickly add new VIM
capabilities without requiring a fork-lift upgrade of Tacker for every new
VIM type.

As part of this workstream, I'd work towards bringing in a Container VIM
type interfacing with Magnum / Zun.

Lifecycle Features:
* Finish left over Newton features - VNFC and NSD
* Better integration with external EM / FCAPS systems
* Enable support for VNFs leveraging Neutron's latest VLAN aware VM feature

Project maintenance:
 * Doc: API reference guide
 * Pecan API framework
 * OSC support
 * Finish python3x TC goal

Tons of fun things to do! However, Ocata is going to be a short cycle.
So, over next few weeks, I'll help to continue to groom these topics and
zoom in on those that are implementable in one dev cycle and clearly
identify some tracks that would carry over to the next cycle.

In Ocata, given an opportunity to serve as your PTL, I'll continue my role
as the "chief enabler" for this amazing community of developers that I'm so
proud to lead over the last two cycles.

- Sridhar Ramaswamy (irc: sridhar_ram)

[1] http://stackalytics.com/?module=tacker-group=commits
__
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] [Tacker] Abstract interface for VNFC

[bharath thiruveedula]

Hi Tackers,
As per this week meeting logs, regarding VNFC BP, I came to know that we need 
to add abstract interface which is invoked  by infra_driver. But as we decided 
to go with SoftwareDeployment option  in this cycle, most of the heat template 
changes are done by heat translator [1]. I couldn't understand the exact usage 
of VNFC abstract interface in this case. I think we have two options if we want 
to have abstract interface with SoftwareDeployment option.
1)Remove the VNFC part from tosca and give the rest as input to heat-translator 
and create the heat stack. In the "SoftwareDeployment" driver which implements 
the abstract interface we can add the corresponding heat resources for VNFC to 
the heat template and update the stack.
2)Just add the abstract interface as a place holder in this cycle. And 
implement it in the further cycles(which may not sounds good)
Let me know your suggestion.
[1] https://review.openstack.org/#/c/358321/

RegardsBharath T  __
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 vnf-create is not bringing upalltheinterfaces

[Sridhar Ramaswamy]

Both OpenWRT or Cirros images just brings up their first interface (eth0)
to automatically do DHCP (client). Either case, please reach out to us in
the #tacker IRC channel to get some help resolving this issue.

On Mon, Aug 29, 2016 at 5:27 AM, Abhilash Goyal <abhilashgoy...@gmail.com>
wrote:

> Default cirros that is added at the time of installation.
> On 29 Aug 2016 16:25, "Zhi Chang" <chang...@unitedstack.com> wrote:
>
>> My cirros image works ok. What version about your cirros image?
>>
>>
>> -- Original --
>> *From: * "Abhilash Goyal"<abhilashgoy...@gmail.com>;
>> *Date: * Mon, Aug 29, 2016 06:43 PM
>> *To: * "OpenStack Development Mailing List (not for usage questions)"<
>> openstack-dev@lists.openstack.org>;
>> *Subject: * Re: [openstack-dev] tacker vnf-create is not bringing
>> upalltheinterfaces
>>
>> Hello Chang,
>> thanks a lot, this image worked. Could you guide me the same for cirros
>> image.
>>
>>
>> On Mon, Aug 29, 2016 at 2:54 PM, Zhi Chang <chang...@unitedstack.com>
>> wrote:
>>
>>> OpenWRT image should be enabled first nic's DHCP.
>>>
>>>
>>> -- Original --
>>> *From: * "Abhilash Goyal"<abhilashgoy...@gmail.com>;
>>> *Date: * Mon, Aug 29, 2016 05:35 PM
>>> *To: * "OpenStack Development Mailing List (not for usage questions)"<
>>> openstack-dev@lists.openstack.org>;
>>> *Subject: * Re: [openstack-dev] tacker vnf-create is not bringing up
>>> alltheinterfaces
>>>
>>> Hi Chang,
>>>
>>> I am using https://downloads.openwrt.org/chaos_calmer/15.05/x86/k
>>> vm_guest/openwrt-15.05-x86-kvm_guest-combined-ext4.img.gz image of
>>> openWRT.
>>> This feature is not working for Cirros either.
>>>
>>> On Mon, Aug 29, 2016 at 2:25 PM, Zhi Chang <chang...@unitedstack.com>
>>> wrote:
>>>
>>>> Hi, Goyal.
>>>>
>>>> What version about your OpenWRT image? You can get OpenWRT image
>>>> from  this: https://drive.google.com/open?id=0B-ruQ8Tx46wSMktKV3J
>>>> LRWhnLTA
>>>>
>>>>
>>>> Thanks
>>>> Zhi Chang
>>>>
>>>> -- Original --
>>>> *From: * "Abhilash Goyal"<abhilashgoy...@gmail.com>;
>>>> *Date: * Mon, Aug 29, 2016 05:18 PM
>>>> *To: * "openstack-dev"<openstack-dev@lists.openstack.org>;
>>>> *Subject: * [openstack-dev] tacker vnf-create is not bringing up all
>>>> theinterfaces
>>>>
>>>> [Tacker]
>>>> Hello team,
>>>> I am trying to make an OpenWRT VNF through tacker using this vnf-d
>>>> <https://github.com/openstack/tacker/blob/master/samples/tosca-templates/vnfd/tosca-vnfd-openwrt.yaml>.
>>>> VNF is spawning successfully, but expected VNF should have 3 connecting
>>>> points with first one in management network, but this is not happening. It
>>>> is getting up with default network configuration because of this, IPs are
>>>> not getting assigned to it automatically.
>>>> Guidance would be appreciated.
>>>>
>>>> --
>>>> Abhilash Goyal
>>>>
>>>>
>>>> 
>>>> __
>>>> OpenStack Development Mailing List (not for usage questions)
>>>> Unsubscribe: openstack-dev-requ...@lists.op
>>>> enstack.org?subject:unsubscribe
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Abhilash Goyal
>>>
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>> Abhilash Goyal
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> 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] tacker vnf-create is not bringing upalltheinterfaces

[Abhilash Goyal]

Default cirros that is added at the time of installation.
On 29 Aug 2016 16:25, "Zhi Chang" <chang...@unitedstack.com> wrote:

> My cirros image works ok. What version about your cirros image?
>
>
> -- Original --
> *From: * "Abhilash Goyal"<abhilashgoy...@gmail.com>;
> *Date: * Mon, Aug 29, 2016 06:43 PM
> *To: * "OpenStack Development Mailing List (not for usage questions)"<
> openstack-dev@lists.openstack.org>;
> *Subject: * Re: [openstack-dev] tacker vnf-create is not bringing
> upalltheinterfaces
>
> Hello Chang,
> thanks a lot, this image worked. Could you guide me the same for cirros
> image.
>
>
> On Mon, Aug 29, 2016 at 2:54 PM, Zhi Chang <chang...@unitedstack.com>
> wrote:
>
>> OpenWRT image should be enabled first nic's DHCP.
>>
>>
>> -- Original --
>> *From: * "Abhilash Goyal"<abhilashgoy...@gmail.com>;
>> *Date: * Mon, Aug 29, 2016 05:35 PM
>> *To: * "OpenStack Development Mailing List (not for usage questions)"<
>> openstack-dev@lists.openstack.org>;
>> *Subject: * Re: [openstack-dev] tacker vnf-create is not bringing up
>> alltheinterfaces
>>
>> Hi Chang,
>>
>> I am using https://downloads.openwrt.org/chaos_calmer/15.05/x86/
>> kvm_guest/openwrt-15.05-x86-kvm_guest-combined-ext4.img.gz image of
>> openWRT.
>> This feature is not working for Cirros either.
>>
>> On Mon, Aug 29, 2016 at 2:25 PM, Zhi Chang <chang...@unitedstack.com>
>> wrote:
>>
>>> Hi, Goyal.
>>>
>>> What version about your OpenWRT image? You can get OpenWRT image
>>> from  this: https://drive.google.com/open?id=0B-ruQ8Tx46wSMktKV3J
>>> LRWhnLTA
>>>
>>>
>>> Thanks
>>> Zhi Chang
>>>
>>> -- Original --
>>> *From: * "Abhilash Goyal"<abhilashgoy...@gmail.com>;
>>> *Date: * Mon, Aug 29, 2016 05:18 PM
>>> *To: * "openstack-dev"<openstack-dev@lists.openstack.org>;
>>> *Subject: * [openstack-dev] tacker vnf-create is not bringing up all
>>> theinterfaces
>>>
>>> [Tacker]
>>> Hello team,
>>> I am trying to make an OpenWRT VNF through tacker using this vnf-d
>>> <https://github.com/openstack/tacker/blob/master/samples/tosca-templates/vnfd/tosca-vnfd-openwrt.yaml>.
>>> VNF is spawning successfully, but expected VNF should have 3 connecting
>>> points with first one in management network, but this is not happening. It
>>> is getting up with default network configuration because of this, IPs are
>>> not getting assigned to it automatically.
>>> Guidance would be appreciated.
>>>
>>> --
>>> Abhilash Goyal
>>>
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>> Abhilash Goyal
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Abhilash Goyal
>
>
> __
> 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] Proposing Yong Sheng Gong for Tacker core team

[Kanagaraj Manickam]

+1.

Congrats yong.

Thanks & Regards
Kanagaraj M

On Aug 27, 2016 2:12 AM, "Sridhar Ramaswamy"  wrote:

We have enough votes to proceed.

Yong - welcome to the Tacker core team!

- Sridhar

On Tue, Aug 23, 2016 at 12:06 PM, Stephen Wong 
wrote:

> +1
>
> On Tue, Aug 23, 2016 at 8:55 AM, Sridhar Ramaswamy 
> wrote:
>
>> Tackers,
>>
>> I'd like to propose Yong Sheng Gong to join the Tacker core team. Yong is
>> a seasoned OpenStacker and has been contributing to Tacker project since
>> Nov 2015 (early Mitaka). He has been the major force in helping Tacker to
>> shed its *Neutronisms*. He has low tolerance on unevenness in the code
>> base and he fixes them as he goes. Yong also participated in the Enhanced
>> Placement Awareness (EPA) blueprint in the Mitaka cycle. For Newton he took
>> up himself cleaning up the DB schema and in numerous reviews to keep the
>> project going. He has been a dependable member of the Tacker community [1].
>>
>> Please chime in with your +1 / -1 votes.
>>
>> thanks,
>> Sridhar
>>
>> [1] http://stackalytics.com/report/contribution/tacker/90
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> 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] tacker vnf-create is not bringing upalltheinterfaces

[Zhi Chang]

My cirros image works ok. What version about your cirros image? 
 
 
-- Original --
From:  "Abhilash Goyal"<abhilashgoy...@gmail.com>;
Date:  Mon, Aug 29, 2016 06:43 PM
To:  "OpenStack Development Mailing List (not for usage 
questions)"<openstack-dev@lists.openstack.org>; 

Subject:  Re: [openstack-dev] tacker vnf-create is not bringing 
upalltheinterfaces

 
Hello Chang, thanks a lot, this image worked. Could you guide me the same for 
cirros image.




On Mon, Aug 29, 2016 at 2:54 PM, Zhi Chang <chang...@unitedstack.com> wrote:
OpenWRT image should be enabled first nic's DHCP. 
 
 
-- Original --
From:  "Abhilash Goyal"<abhilashgoy...@gmail.com>;
Date:  Mon, Aug 29, 2016 05:35 PM
To:  "OpenStack Development Mailing List (not for usage 
questions)"<openstack-dev@lists.openstack.org>; 

Subject:  Re: [openstack-dev] tacker vnf-create is not bringing up 
alltheinterfaces

 
Hi Chang,

I am using 
https://downloads.openwrt.org/chaos_calmer/15.05/x86/kvm_guest/openwrt-15.05-x86-kvm_guest-combined-ext4.img.gz
 image of openWRT. 
This feature is not working for Cirros either.


On Mon, Aug 29, 2016 at 2:25 PM, Zhi Chang <chang...@unitedstack.com> wrote:
Hi, Goyal.


What version about your OpenWRT image? You can get OpenWRT image from  
this: https://drive.google.com/open?id=0B-ruQ8Tx46wSMktKV3JLRWhnLTA
 


Thanks
Zhi Chang
 
-- Original --
From:  "Abhilash Goyal"<abhilashgoy...@gmail.com>;
Date:  Mon, Aug 29, 2016 05:18 PM
To:  "openstack-dev"<openstack-dev@lists.openstack.org>; 

Subject:  [openstack-dev] tacker vnf-create is not bringing up all theinterfaces

 
[Tacker]Hello team,
I am trying to make an OpenWRT VNF through tacker using this vnf-d. VNF is 
spawning successfully, but expected VNF should have 3 connecting points with 
first one in management network, but this is not happening. It is getting up 
with default network configuration because of this, IPs are not getting 
assigned to it automatically. 
Guidance would be appreciated.


-- 
Abhilash Goyal




 
 




__
 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
 





-- 
Abhilash Goyal




 
 




__
 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
 





-- 
Abhilash Goyal__
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 vnf-create is not bringing up alltheinterfaces

[Abhilash Goyal]

Hello Chang,
thanks a lot, this image worked. Could you guide me the same for cirros
image.


On Mon, Aug 29, 2016 at 2:54 PM, Zhi Chang <chang...@unitedstack.com> wrote:

> OpenWRT image should be enabled first nic's DHCP.
>
>
> -- Original --
> *From: * "Abhilash Goyal"<abhilashgoy...@gmail.com>;
> *Date: * Mon, Aug 29, 2016 05:35 PM
> *To: * "OpenStack Development Mailing List (not for usage questions)"<
> openstack-dev@lists.openstack.org>;
> *Subject: * Re: [openstack-dev] tacker vnf-create is not bringing up
> alltheinterfaces
>
> Hi Chang,
>
> I am using https://downloads.openwrt.org/chaos_calmer/15.
> 05/x86/kvm_guest/openwrt-15.05-x86-kvm_guest-combined-ext4.img.gz image
> of openWRT.
> This feature is not working for Cirros either.
>
> On Mon, Aug 29, 2016 at 2:25 PM, Zhi Chang <chang...@unitedstack.com>
> wrote:
>
>> Hi, Goyal.
>>
>> What version about your OpenWRT image? You can get OpenWRT image from
>>  this: https://drive.google.com/open?id=0B-ruQ8Tx46wSMktKV3JLRWhnLTA
>>
>>
>> Thanks
>> Zhi Chang
>>
>> -- Original --
>> *From: * "Abhilash Goyal"<abhilashgoy...@gmail.com>;
>> *Date: * Mon, Aug 29, 2016 05:18 PM
>> *To: * "openstack-dev"<openstack-dev@lists.openstack.org>;
>> *Subject: * [openstack-dev] tacker vnf-create is not bringing up all
>> theinterfaces
>>
>> [Tacker]
>> Hello team,
>> I am trying to make an OpenWRT VNF through tacker using this vnf-d
>> <https://github.com/openstack/tacker/blob/master/samples/tosca-templates/vnfd/tosca-vnfd-openwrt.yaml>.
>> VNF is spawning successfully, but expected VNF should have 3 connecting
>> points with first one in management network, but this is not happening. It
>> is getting up with default network configuration because of this, IPs are
>> not getting assigned to it automatically.
>> Guidance would be appreciated.
>>
>> --
>> Abhilash Goyal
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Abhilash Goyal
>
>
> __
> 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
>
>


-- 
Abhilash Goyal
__
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 vnf-create is not bringing up alltheinterfaces

[Zhi Chang]

OpenWRT image should be enabled first nic's DHCP. 
 
 
-- Original --
From:  "Abhilash Goyal"<abhilashgoy...@gmail.com>;
Date:  Mon, Aug 29, 2016 05:35 PM
To:  "OpenStack Development Mailing List (not for usage 
questions)"<openstack-dev@lists.openstack.org>; 

Subject:  Re: [openstack-dev] tacker vnf-create is not bringing up 
alltheinterfaces

 
Hi Chang,

I am using 
https://downloads.openwrt.org/chaos_calmer/15.05/x86/kvm_guest/openwrt-15.05-x86-kvm_guest-combined-ext4.img.gz
 image of openWRT. 
This feature is not working for Cirros either.


On Mon, Aug 29, 2016 at 2:25 PM, Zhi Chang <chang...@unitedstack.com> wrote:
Hi, Goyal.


What version about your OpenWRT image? You can get OpenWRT image from  
this: https://drive.google.com/open?id=0B-ruQ8Tx46wSMktKV3JLRWhnLTA
 


Thanks
Zhi Chang
 
-- Original --
From:  "Abhilash Goyal"<abhilashgoy...@gmail.com>;
Date:  Mon, Aug 29, 2016 05:18 PM
To:  "openstack-dev"<openstack-dev@lists.openstack.org>; 

Subject:  [openstack-dev] tacker vnf-create is not bringing up all theinterfaces

 
[Tacker]Hello team,
I am trying to make an OpenWRT VNF through tacker using this vnf-d. VNF is 
spawning successfully, but expected VNF should have 3 connecting points with 
first one in management network, but this is not happening. It is getting up 
with default network configuration because of this, IPs are not getting 
assigned to it automatically. 
Guidance would be appreciated.


-- 
Abhilash Goyal




 
 




__
 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
 





-- 
Abhilash Goyal__
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