from:"joehuang"

Hi, TSC and David,

The purpose of this email is to notify the OPNFV TSC that the Multisite project 
intends to participate in the OPNFV Euphrates release.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite] danube.1.0 tagged

Hello,

Multisite is also tagged with danube.1.0. 
https://git.opnfv.org/multisite/tag/?h=danube.1.0


For Kingbird's Functest has not return to normal yet, once Kingbird's functest 
return to normal, we may release Danube2.0.


Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] VNF to demonstrate VNF high availability across VIM

Hello, Julien,

Welcome to join the PoC demo in OPNFV Beijing Summit, Do you have some 
application to be deployed in the multi-site environment? And may I know which 
company you are working for, so that we can list you in the PoC demo.

Best Regards
Chaoyi Huang (joehuang)

From: Julien [julien...@gmail.com]
Sent: 31 March 2017 18:51
To: joehuang; opnfv-tech-discuss; victor.mora...@intel.com; Meimei
Subject: Re: [opnfv-tech-discuss] VNF to demonstrate VNF high availability 
across VIM

Hi Joehuang,

Thanks for clarification this use case. It is actually very cool and I expect 
to attend the demo in the summit.

BR,
Julien


joehuang mailto:joehu...@huawei.com>>于2017年3月30日周四 
下午3:11写道：
Hello, Julien,

Both should works, you can make one VNF being deployed into two OpenStack 
instances, or make two VNFs work in load-balancing mode.

Currently Tricircle support associating one VIP in two OpenStack instances 
(through allowed address pair), it's up to VNFs how to make use of the enabling 
networking capabilities by Tricircle.

Best Regards
Chaoyi Huang (joehuang)

From: Julien [julien...@gmail.com<mailto:julien...@gmail.com>]
Sent: 30 March 2017 14:58
To: joehuang; opnfv-tech-discuss; 
victor.mora...@intel.com<mailto:victor.mora...@intel.com>; Meimei
Subject: Re: [opnfv-tech-discuss] VNF to demonstrate VNF high availability 
across VIM

Hi Joehuang,

It's amazing.

According to the content "show how a VNF can run in 2 OpenStack instances" and 
the link 
https://git.opnfv.org/multisite/tree/docs/requirements/VNF_high_availability_across_VIM.rst.
 I'm not sure that it is one VNF or two VNFs(active VNF + standby VNF) in the 
Demo.

If it is one VNF, is it possible:
1. Some VMs in active mode are in openstack1, and other VMs in active mode are 
in openstack2;
2. Can VMs working in load balance mode across openstack1 and openstack2?


BR,
Julien


joehuang mailto:joehu...@huawei.com>>于2017年3月16日周四 
上午10:44写道：
Hello,

In multisite, we have one use cases ever discussed:

a VNF (telecom application) should, be able to realize high availability 
deployment across OpenStack instances.
For more detail of such an use cases, you can refer to 
https://git.opnfv.org/multisite/tree/docs/requirements/VNF_high_availability_across_VIM.rst

Now, it's time to bring it into reality.

After Tricircle provides cross OpenStack L2/L3 networking automation capability 
based on VxLAN, we'd like to have a demo in OPNFV Beijing summit to show how a 
VNF can run in 2 OpenStack instances and achieve high availability regardless 
how much nine, planned or unplanned downtime of an OpenStack cloud would be.

The VNF will work in cluster, active/active or active/standby mode, and it was 
deployed into two OpenStack instances, overlay VxLAN network will provide 
network plane for session/or other data replication between VNF parts, and also 
provide the VIP for VNF to provide service, if the VNF is running in 
active/standby, the standby VNF can take over the VIP and continue to provide 
service after the master or the openstack cloud is failed.

If you are interested in such an use case, please join us, help would be 
appreciated:

1. Provide or integrate sample VNF which is able to be deployed into multiple 
OpenStack instances to reach cloud level redundancy/failure escape.
2. Joint demo in Beijing OPNFV summit.
3. Build multi-site general infrastructure in E-release for CI/Functest/3rd 
party service, to provide general multi-region environment for services like 
Tricircle/Kingbird/Domino/Tacker which deal with multi-region functionalities.


Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [multisite] OpenStack Forum Submission on multi-site/distributed clouds

Hi, Curtis,

Thank you very much, this is great.

Best Regards
Chaoyi Huang (joehuang)


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Curtis 
[serverasc...@gmail.com]
Sent: 31 March 2017 0:59
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [multisite] OpenStack Forum Submission on 
multi-site/distributed clouds

Hi All,

I just wanted to let the multi-site OPNFV team know that I have
submitted a request for a forum session on the topic of "The Status
and Future of Multi-site and Distributed Clouds" [1]. There is also a
brainstorming etherpad covering all of NFV [2] which you might already
be aware of. There are only a couple of days left for the forum
submissions.

If you have any questions or comments, just let me know. You can also
add comments to the request page.

Thanks,
Curtis.

[1]: http://forumtopics.openstack.org/cfp/details/58
[2]: https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] VNF to demonstrate VNF high availability across VIM

Do you have some application to be deployed in the multi-site environment?

Best Regards
Chaoyi Huang (joehuang)

From: Julien [julien...@gmail.com]
Sent: 31 March 2017 18:51
To: joehuang; opnfv-tech-discuss; victor.mora...@intel.com; Meimei
Subject: Re: [opnfv-tech-discuss] VNF to demonstrate VNF high availability 
across VIM

Hi Joehuang,

Thanks for clarification this use case. It is actually very cool and I expect 
to attend the demo in the summit.

BR,
Julien

joehuang mailto:joehu...@huawei.com>>于2017年3月30日周四 
下午3:11写道：
Hello, Julien,

Both should works, you can make one VNF being deployed into two OpenStack 
instances, or make two VNFs work in load-balancing mode.

Currently Tricircle support associating one VIP in two OpenStack instances 
(through allowed address pair), it's up to VNFs how to make use of the enabling 
networking capabilities by Tricircle.

Best Regards
Chaoyi Huang (joehuang)

From: Julien [julien...@gmail.com<mailto:julien...@gmail.com>]
Sent: 30 March 2017 14:58
To: joehuang; opnfv-tech-discuss; 
victor.mora...@intel.com<mailto:victor.mora...@intel.com>; Meimei
Subject: Re: [opnfv-tech-discuss] VNF to demonstrate VNF high availability 
across VIM

Hi Joehuang,

It's amazing.

According to the content "show how a VNF can run in 2 OpenStack instances" and 
the link 
https://git.opnfv.org/multisite/tree/docs/requirements/VNF_high_availability_across_VIM.rst.
 I'm not sure that it is one VNF or two VNFs(active VNF + standby VNF) in the 
Demo.

If it is one VNF, is it possible:
1. Some VMs in active mode are in openstack1, and other VMs in active mode are 
in openstack2;
2. Can VMs working in load balance mode across openstack1 and openstack2?

BR,
Julien

joehuang mailto:joehu...@huawei.com>>于2017年3月16日周四 
上午10:44写道：
Hello,

In multisite, we have one use cases ever discussed:

a VNF (telecom application) should, be able to realize high availability 
deployment across OpenStack instances.
For more detail of such an use cases, you can refer to 
https://git.opnfv.org/multisite/tree/docs/requirements/VNF_high_availability_across_VIM.rst

Now, it's time to bring it into reality.

After Tricircle provides cross OpenStack L2/L3 networking automation capability 
based on VxLAN, we'd like to have a demo in OPNFV Beijing summit to show how a 
VNF can run in 2 OpenStack instances and achieve high availability regardless 
how much nine, planned or unplanned downtime of an OpenStack cloud would be.

The VNF will work in cluster, active/active or active/standby mode, and it was 
deployed into two OpenStack instances, overlay VxLAN network will provide 
network plane for session/or other data replication between VNF parts, and also 
provide the VIP for VNF to provide service, if the VNF is running in 
active/standby, the standby VNF can take over the VIP and continue to provide 
service after the master or the openstack cloud is failed.

If you are interested in such an use case, please join us, help would be 
appreciated:

1. Provide or integrate sample VNF which is able to be deployed into multiple 
OpenStack instances to reach cloud level redundancy/failure escape.
2. Joint demo in Beijing OPNFV summit.
3. Build multi-site general infrastructure in E-release for CI/Functest/3rd 
party service, to provide general multi-region environment for services like 
Tricircle/Kingbird/Domino/Tacker which deal with multi-region functionalities.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]minutes of weekly meeting Mar.30

2017-03-30 Thread joehuang

Hello, team,


minutes of weekly meeting Mar.30 is as follows:


Agenda

  *
 *   CMCC multi-site requirements
 *   OPNFV Beijing summit preparation
 *   Contribution to multisite arch guide
 *   Open discussion

Minutes

  *
 *
*

demo environment: Full access to the internet (for package
  installation etc..)  (joehuang, 08:18:05)

*

ACTION: one more baremetal servers  (joehuang, 08:20:55)

*

3 sites, vIMS in two sites, Video conference in 3 sites  (joehuang,
  08:24:14)

*

Contribution to multisite arch guide  (joehuang, 08:46:00)

Link

  *
 *
*   
Minutes:http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-30-08.02.html

*   Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-30-08.02.txt
*   
Log:http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-30-08.02.log.html

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] VNF to demonstrate VNF high availability across VIM

2017-03-30 Thread joehuang

Hello, Julien,

Both should works, you can make one VNF being deployed into two OpenStack 
instances, or make two VNFs work in load-balancing mode.

Currently Tricircle support associating one VIP in two OpenStack instances 
(through allowed address pair), it's up to VNFs how to make use of the enabling 
networking capabilities by Tricircle.

Best Regards
Chaoyi Huang (joehuang)

From: Julien [julien...@gmail.com]
Sent: 30 March 2017 14:58
To: joehuang; opnfv-tech-discuss; victor.mora...@intel.com; Meimei
Subject: Re: [opnfv-tech-discuss] VNF to demonstrate VNF high availability 
across VIM

Hi Joehuang,

It's amazing.

According to the content "show how a VNF can run in 2 OpenStack instances" and 
the link 
https://git.opnfv.org/multisite/tree/docs/requirements/VNF_high_availability_across_VIM.rst.
 I'm not sure that it is one VNF or two VNFs(active VNF + standby VNF) in the 
Demo.

If it is one VNF, is it possible:
1. Some VMs in active mode are in openstack1, and other VMs in active mode are 
in openstack2;
2. Can VMs working in load balance mode across openstack1 and openstack2?


BR,
Julien


joehuang mailto:joehu...@huawei.com>>于2017年3月16日周四 
上午10:44写道：
Hello,

In multisite, we have one use cases ever discussed:

a VNF (telecom application) should, be able to realize high availability 
deployment across OpenStack instances.
For more detail of such an use cases, you can refer to 
https://git.opnfv.org/multisite/tree/docs/requirements/VNF_high_availability_across_VIM.rst

Now, it's time to bring it into reality.

After Tricircle provides cross OpenStack L2/L3 networking automation capability 
based on VxLAN, we'd like to have a demo in OPNFV Beijing summit to show how a 
VNF can run in 2 OpenStack instances and achieve high availability regardless 
how much nine, planned or unplanned downtime of an OpenStack cloud would be.

The VNF will work in cluster, active/active or active/standby mode, and it was 
deployed into two OpenStack instances, overlay VxLAN network will provide 
network plane for session/or other data replication between VNF parts, and also 
provide the VIP for VNF to provide service, if the VNF is running in 
active/standby, the standby VNF can take over the VIP and continue to provide 
service after the master or the openstack cloud is failed.

If you are interested in such an use case, please join us, help would be 
appreciated:

1. Provide or integrate sample VNF which is able to be deployed into multiple 
OpenStack instances to reach cloud level redundancy/failure escape.
2. Joint demo in Beijing OPNFV summit.
3. Build multi-site general infrastructure in E-release for CI/Functest/3rd 
party service, to provide general multi-region environment for services like 
Tricircle/Kingbird/Domino/Tacker which deal with multi-region functionalities.


Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [multisite]weekly meeting of Mar.30

2017-03-29 Thread joehuang

One more topic:

Contribution to multisite arch guide

Best Regards
Chaoyi Huang (joehuang)

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of joehuang 
[joehu...@huawei.com]
Sent: 29 March 2017 16:28
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [multisite]weekly meeting of Mar.30


Hello, team,


Mar.30 2017 Agenda:

* CMCC multi-site requirements discussion(2)

* OPNFV Beijing summit preparation

* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.


Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]weekly meeting of Mar.30

2017-03-29 Thread joehuang

Hello, team,


Mar.30 2017 Agenda:

* CMCC multi-site requirements discussion(2)

* OPNFV Beijing summit preparation

* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.


Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] 答复: VNF to demonstrate VNF high availability across VIM

2017-03-27 Thread joehuang

ence APP is 
planned to be used in the PoC, would you support to deploy clearwater vIMS VMs 
in the PoC environments? After the multi-site PoC environment is ready, it's 
easy to bring a new VNF to the multi-site clouds. We can discuss this in 
multi-site weekly meeting if you are interested in join the PoC.

Best Regards
Chaoyi Huang (joehuang)

From: valentin.bouc...@orange.com [valentin.bouc...@orange.com]
Sent: 27 March 2017 17:45
To: joehuang; Soni, Anand Kumar via opnfv-tech-discuss; Morales, Victor; Meimei
Subject: RE:答复:[opnfv-tech-discuss] VNF to demonstrate VNF high availability 
across VIM

Hi Chaoyi,

Each clearwater vm can have 1 interface (signaling + management) or 2 
interfaces (1 for signaling and 1 for management). See clearwater documentation 
=> 
Link.<http://clearwater.readthedocs.io/en/stable/Multiple_Network_Support.html>

Currently, We have only tested clearwater multisite deployement with 1 
interface per VM. For this configuration, the "North South Networking via 
Multiple External Networks" Tricircle network scenario is interesting. But 
changes would have to be made to bring it closer to the needs.

+-+   +-+
|  RegionOne  |   |  RegionTwo  |
| |   | |
| ext_net1|   | ext_net2|
|   +-+-+ |   |   +-+-+ |
| |   |   | |   |
| |   |   | |   |
|  +--+--+|   |  +--+--+|
|  | || net3  |  | ||
|  | R1  |---| R2  ||
|  | ||   |  | ||
|  +--+--+|   |  +--+--+|
| |   |   | |   |
| |   |   | |   |
| +---+-+-+   |   | +---+-+-+   |
| net1  | |   | net2  | |
|   | |   |   | |
|  ++--+  |   |  ++--+  |
|  | Instance1 |  |   |  | Instance2 |  |
|  +---+  |   |  +---+  |
| |   | |
+-+   +-+

I think the way is to put a network between R1 and R2 instead of instance1 and 
instance2. Thereby, Instance1 can communicate to instance2 with his net1 ip 
trough the net3 network. But, also with the external componants (like sip 
client etc.) with a floating ip on ext_net1 or 2.

BR,
Valentin Boucher

De : joehuang [joehu...@huawei.com]
Envoyé : jeudi 23 mars 2017 14:53
À : BOUCHER Valentin IMT/OLN; Soni, Anand Kumar via opnfv-tech-discuss; 
Morales, Victor; Meimei
Objet : RE: 答复:[opnfv-tech-discuss] VNF to demonstrate VNF high availability 
across VIM

Hi Valentin,

The networking topology is very clear from the picture.

If we want to make vIMS clearwater as close as to the production deployment in 
OpenStack multisite environment, what's the better networking proposal, for 
example, how many interfaces for one VM, i.e, how many network planes, how to 
process the north-south traffic, is SNAT/FIP needed?

Would like to check whether Tricircle networking automation can fulfill the 
demands for vIMS clearwater multi-site deployment.

Tricircle already supports several typical networking topology in 
https://docs.openstack.org/developer/tricircle/networking-guide.html#networking-scenario
 ( please note that VxLAN based bridge network between routers, VxLAN based 
cross OpenStack L2 network will be released in pike-1 by the end of next week )

And one more typical topology is expected to be released in pike-2: L3 
networking to support multiple north-south with east-west enabled: 
https://review.openstack.org/#/c/448359/

Best Regards
Chaoyi Huang (joehuang)

From: valentin.bouc...@orange.com [valentin.bouc...@orange.com]
Sent: 23 March 2017 0:03
To: joehuang; Soni, Anand Kumar via opnfv-tech-discuss; Morales, Victor; Meimei
Subject: RE:答复:[opnfv-tech-discuss] VNF to demonstrate VNF high availability 
across VIM

Hello, Chaoyi,

Oh ok, no problem.

 ~12 VMs with 2 Go and 1 VM with 4 Go per site

VNF networking:

  *   Only one network interface on each VM
  *   Communication between each local site network must be allowed without any 
NAT/PAT or floating ip.
  *   So, Each local VM must be able to communicate with the remote VM with his 
local ip.
  *   For the moment we use a openvpn tunnel to do that and the openvpn vms 
acts as router between local and remote networks (see the picture in 
attachment).

The goal is to replace openvpn tunnel with a better solution like bgp-mpls or 
other thing.

BR,
Valentin


De : joehuang [joehu...@huawei.com]
Envoyé : jeudi 16 mars 2017 14:17
À : BOUCHER Valentin IMT/OLN; Soni, Anand Kumar via opnfv-tech-discuss; 
Morales, Victor; Meimei
Objet : 答复:[opnfv-tech-discuss] VNF to demonstrate VNF high av

Re: [opnfv-tech-discuss] 答复: VNF to demonstrate VNF high availability across VIM

2017-03-23 Thread joehuang

Hi Valentin,

The networking topology is very clear from the picture.

If we want to make vIMS clearwater as close as to the production deployment in 
OpenStack multisite environment, what's the better networking proposal, for 
example, how many interfaces for one VM, i.e, how many network planes, how to 
process the north-south traffic, is SNAT/FIP needed?

Would like to check whether Tricircle networking automation can fulfill the 
demands for vIMS clearwater multi-site deployment.

Tricircle already supports several typical networking topology in 
https://docs.openstack.org/developer/tricircle/networking-guide.html#networking-scenario
 ( please note that VxLAN based bridge network between routers, VxLAN based 
cross OpenStack L2 network will be released in pike-1 by the end of next week )

And one more typical topology is expected to be released in pike-2: L3 
networking to support multiple north-south with east-west enabled: 
https://review.openstack.org/#/c/448359/

Best Regards
Chaoyi Huang (joehuang)

From: valentin.bouc...@orange.com [valentin.bouc...@orange.com]
Sent: 23 March 2017 0:03
To: joehuang; Soni, Anand Kumar via opnfv-tech-discuss; Morales, Victor; Meimei
Subject: RE:答复:[opnfv-tech-discuss] VNF to demonstrate VNF high availability 
across VIM

Hello, Chaoyi,

Oh ok, no problem.

 ~12 VMs with 2 Go and 1 VM with 4 Go per site

VNF networking:

  *   Only one network interface on each VM
  *   Communication between each local site network must be allowed without any 
NAT/PAT or floating ip.
  *   So, Each local VM must be able to communicate with the remote VM with his 
local ip.
  *   For the moment we use a openvpn tunnel to do that and the openvpn vms 
acts as router between local and remote networks (see the picture in 
attachment).

The goal is to replace openvpn tunnel with a better solution like bgp-mpls or 
other thing.

BR,
Valentin


De : joehuang [joehu...@huawei.com]
Envoyé : jeudi 16 mars 2017 14:17
À : BOUCHER Valentin IMT/OLN; Soni, Anand Kumar via opnfv-tech-discuss; 
Morales, Victor; Meimei
Objet : 答复:[opnfv-tech-discuss] VNF to demonstrate VNF high availability across 
VIM

Hello, Valentin,

Very pleased to know the practice,
and very keen to discuss about it in more detail f2f.
But unfortuntealy I am not able to attend the
plugfest in Paris, could you please provide
reference material especial VNF's networking
topology, and then find a way for more detail disucssion.

BR
Chaoyi Huang(joehuang)

Sent from HUAWEI AnyOffice
发件人：valentin.bouc...@orange.com
收件人：黄朝意,Soni, Anand Kumar via opnfv-tech-discuss,Morales, Victor,梅玫
时间：2017-03-16 19:04:22
主题:RE:[opnfv-tech-discuss] VNF to demonstrate VNF high availability across VIM

Hello,

Last summer, In Orange Labs, we implemented vIMS ClearWater on a multi-site 
environment. We used  the single site implementation with Cloudify orchestrator 
and updated this to support multi-site environment. As presented by 
Metaswitch<http://clearwater.readthedocs.io/en/stable/Geographic_redundancy.html>,
 vIMS Clearwater can support currently 2 sites deployment.

However, our implementation only works on 2 separate OpenStack platforms 
because we had no multisite platform at hand. So, the network between those 
sites is based on a OpenVPN tunnel. The multisite mechanism works but It would 
be nice to be able to integrate this on a real multisite platform.

Since OPNFV/Brahmaputra release, the deployment of this vIMS was included in 
functest project but for the moment, it only support one site.

I would attend the next OPNFV/Plugfest in Paris and it could be a great 
opportunity to improve this test-case using your multi-site solution.

Best Regards,
Valentin Boucher



De : opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] de la part de joehuang 
[joehu...@huawei.com]
Envoyé : jeudi 16 mars 2017 03:44
À : opnfv-tech-discuss; victor.mora...@intel.com; Meimei
Objet : [opnfv-tech-discuss] VNF to demonstrate VNF high availability across VIM

Hello,

In multisite, we have one use cases ever discussed:

a VNF (telecom application) should, be able to realize high availability 
deployment across OpenStack instances.
For more detail of such an use cases, you can refer to 
https://git.opnfv.org/multisite/tree/docs/requirements/VNF_high_availability_across_VIM.rst

Now, it's time to bring it into reality.

After Tricircle provides cross OpenStack L2/L3 networking automation capability 
based on VxLAN, we'd like to have a demo in OPNFV Beijing summit to show how a 
VNF can run in 2 OpenStack instances and achieve high availability regardless 
how much nine, planned or unplanned downtime of an OpenStack cloud would be.

The VNF will work in cluster, active/active or active/standby mode, and it was 
deployed into two OpenStack instances, overlay VxLAN network will provide 
network plane

Re: [opnfv-tech-discuss] [multisite] weekly meeting of Mar.23

2017-03-23 Thread joehuang

Hello, Gerald,

Thank you for the mail. Will discuss this in next weekly meeting whether we can 
help.

Before rewriting the multisite part, can the old one still be put in place? The 
update can be done gradually. Someone already complains the missing of this 
guide.

Best Regards
Chaoyi Huang (joehuang)

From: Kunzmann, Gerald [kunzm...@docomolab-euro.com]
Sent: 22 March 2017 23:54
To: joehuang; opnfv-tech-discuss
Cc: openstack-operat...@lists.openstack.org; Heidi Joy Tretheway
Subject: RE: [multisite] weekly meeting of Mar.23

Dear multisite-Team,

FYI, the arch guide [1] in OpenStack is being rewritten, and the multi-site 
docs that were there are no longer there (see archived manuals in [2])
So there are currently no official docs on multi-site/region in OpenStack. In 
the Telco/NFV meeting it was suggested they could use some help writing those.

[1] https://docs.openstack.org/arch-design/
[2] 
https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/arch-design-to-archive/source

It seems the plan is to rewrite the arch guide piece by piece and they just 
haven't gotten to the multisite part yet, and could probably use some help. 
There is also potentially a NFV section to it.

Is there someone from multi-site team interested to work on this? Maybe you 
could discuss this in your meeting tomorrow.

I am not sure who would be the right person to contact, maybe Heidi from 
OpenStack heidi...@openstack.org<mailto:heidi...@openstack.org>?

Best regards,
Gerald


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of joehuang
Sent: Mittwoch, 22. März 2017 06:04
To: opnfv-tech-discuss 
Subject: [opnfv-tech-discuss] [multisite]weekly meeting of Mar.23


Hello, team,



HA PTL FuQiao was invited to talk about multi-site requirements in this weekly 
meeting



Mar.23 2017 Agenda:

* CMCC multi-site requirements

* Functest issue.

* E-Release discussion

* OPNFV Beijing summit preparation

* Open discussion


IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.


Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]weekly meeting minutes of Mar.23

2017-03-23 Thread joehuang

Hello, team,

Weekly meeting minutes is as follows:

  *   Agenda

* CMCC multi-site requirements

* Functest issue.

* E-Release discussion

* OPNFV Beijing summit preparation

* Open discussion

  *   Minutes

  *
 *   CMCC multi-site 
requirements(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-23-08.00.log.html#l-14>,
 08:03:28)
*   3 layer NFV deployment architecture 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-23-08.00.log.html#l-20>,
 08:05:28)
functest 
issue(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-23-08.00.log.html#l-129>,
 08:52:07)
*   functest pass locally 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-23-08.00.log.html#l-145>,
 08:55:24)

  *   Link
 *   
Minutes:http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-23-08.00.html

 *   Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-23-08.00.txt
 *   
Log:http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-23-08.00.log.html

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]weekly meeting of Mar.23

2017-03-21 Thread joehuang

Hello, team,


HA PTL FuQiao was invited to talk about multi-site requirements in this weekly 
meeting


Mar.23 2017 Agenda:

* CMCC multi-site requirements

* Functest issue.

* E-Release discussion

* OPNFV Beijing summit preparation

* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.


Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] 答复: Ray Nugent

2017-03-19 Thread joehuang

Said to know this, really a tragic! My sincere condolences to his family too!

Best Regards
Chaoyi Huang (joehuang)

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Fu Qiao 
[fuq...@chinamobile.com]
Sent: 20 March 2017 11:25
To: Ulrich Kleber; 'TECH-DISCUSS OPNFV'
Subject: [opnfv-tech-discuss] 答复: Ray Nugent

Really sorry to hear this. It is a tragic.
My sincere condolences to his family.

发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Ulrich Kleber
发送时间: 2017年3月17日 17:08
收件人: 'TECH-DISCUSS OPNFV'
主题: [opnfv-tech-discuss] Ray Nugent

Hello,

we just have received the sad news that our former colleague Ray Nugent was 
killed in an automobile accident on Saturday.
Ray has worked in Huawei’s OPNFV team and I am sure many of you remember him 
well, so I wanted to share.
Ray had a very rich experience from many open source projects and used that to 
help OPNFV be what it is today.

Best,
Uli
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] multi-site general infrastructure requirements

2017-03-17 Thread joehuang

Hello, Jack,

OK, will do when things are ready.

Best Regards
Chaoyi Huang (joehuang)

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Jack Morgan 
[jack.mor...@intel.com]
Sent: 16 March 2017 23:55
To: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] multi-site general infrastructure requirements


Huang,

Yes, please bring to Infra WG for discussion. You can add the topic the wiki[1] 
when you are ready. thanks

[1] https://wiki.opnfv.org/display/INF/Infra+Working+Group

On 03/16/2017 04:43 AM, Zhipeng Huang wrote:
Hi Joe,

Maybe we need to bring this up to the Infra team ?

On Thu, Mar 16, 2017 at 5:33 PM, joehuang 
mailto:joehu...@huawei.com>> wrote:
Hello,

Planned to build multi-site general infrastructure in E-release for 
CI/Functest/3rd party service, to provide general multi-region environment for 
services like Tricircle/Kingbird/Domino/Tacker/... which deal with multi-region 
functionalities.

A wiki page was created to collect requirements on multisite infrastructure: 
https://wiki.opnfv.org/display/multisite/Multisite+infrastructure+requirements

Please feel free to add your requirements in the table.

Maybe not all requirements could be implemented in E-release, but we can do it 
step by step.

Best Regards
Chaoyi Huang (joehuang)

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss




--
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Prooduct Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com<mailto:huangzhip...@huawei.com>
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu<mailto:zhipe...@uci.edu>
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado



___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss



--
Jack Morgan
OPNFV Pharos Intel Lab
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] 答复: VNF to demonstrate VNF high availability across VIM

2017-03-16 Thread joehuang

Hello, Valentin,

Very pleased to know the practice,
and very keen to discuss about it in more detail f2f.
But unfortuntealy I am not able to attend the
plugfest in Paris, could you please provide
reference material especial VNF's networking
topology, and then find a way for more detail disucssion.

BR
Chaoyi Huang(joehuang)

Sent from HUAWEI AnyOffice
发件人：valentin.bouc...@orange.com
收件人：黄朝意,Soni, Anand Kumar via opnfv-tech-discuss,Morales, Victor,梅玫
时间：2017-03-16 19:04:22
主题:RE:[opnfv-tech-discuss] VNF to demonstrate VNF high availability across VIM

Hello,

Last summer, In Orange Labs, we implemented vIMS ClearWater on a multi-site
environment. We used the single site implementation with Cloudify orchestrator
and updated this to support multi-site environment. As presented by
Metaswitch<http://clearwater.readthedocs.io/en/stable/Geographic_redundancy.html>,
vIMS Clearwater can support currently 2 sites deployment.

However, our implementation only works on 2 separate OpenStack platforms
because we had no multisite platform at hand. So, the network between those
sites is based on a OpenVPN tunnel. The multisite mechanism works but It would
be nice to be able to integrate this on a real multisite platform.

Since OPNFV/Brahmaputra release, the deployment of this vIMS was included in
functest project but for the moment, it only support one site.

I would attend the next OPNFV/Plugfest in Paris and it could be a great
opportunity to improve this test-case using your multi-site solution.

Best Regards,
Valentin Boucher

De : opnfv-tech-discuss-boun...@lists.opnfv.org
[opnfv-tech-discuss-boun...@lists.opnfv.org] de la part de joehuang
[joehu...@huawei.com]
Envoyé : jeudi 16 mars 2017 03:44
À : opnfv-tech-discuss; victor.mora...@intel.com; Meimei
Objet : [opnfv-tech-discuss] VNF to demonstrate VNF high availability across VIM

Hello,

In multisite, we have one use cases ever discussed:

a VNF (telecom application) should, be able to realize high availability
deployment across OpenStack instances.
For more detail of such an use cases, you can refer to
https://git.opnfv.org/multisite/tree/docs/requirements/VNF_high_availability_across_VIM.rst

Now, it's time to bring it into reality.

After Tricircle provides cross OpenStack L2/L3 networking automation capability
based on VxLAN, we'd like to have a demo in OPNFV Beijing summit to show how a
VNF can run in 2 OpenStack instances and achieve high availability regardless
how much nine, planned or unplanned downtime of an OpenStack cloud would be.

The VNF will work in cluster, active/active or active/standby mode, and it was
deployed into two OpenStack instances, overlay VxLAN network will provide
network plane for session/or other data replication between VNF parts, and also
provide the VIP for VNF to provide service, if the VNF is running in
active/standby, the standby VNF can take over the VIP and continue to provide
service after the master or the openstack cloud is failed.

If you are interested in such an use case, please join us, help would be
appreciated:

1. Provide or integrate sample VNF which is able to be deployed into multiple
OpenStack instances to reach cloud level redundancy/failure escape.
2. Joint demo in Beijing OPNFV summit.
3. Build multi-site general infrastructure in E-release for CI/Functest/3rd
party service, to provide general multi-region environment for services like
Tricircle/Kingbird/Domino/Tacker which deal with multi-region functionalities.

Best Regards
Chaoyi Huang (joehuang)

Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.

This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] multi-site general infrastructure requirements

2017-03-16 Thread joehuang

Hello,

Planned to build multi-site general infrastructure in E-release for 
CI/Functest/3rd party service, to provide general multi-region environment for 
services like Tricircle/Kingbird/Domino/Tacker/... which deal with multi-region 
functionalities.

A wiki page was created to collect requirements on multisite infrastructure: 
https://wiki.opnfv.org/display/multisite/Multisite+infrastructure+requirements

Please feel free to add your requirements in the table.

Maybe not all requirements could be implemented in E-release, but we can do it 
step by step.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [multisite]meeting minutes of Mar.16

2017-03-16 Thread joehuang

Hello, team,


  *   Agenda

* Functest issue.

* E-Release discussion

* OPNFV Beijing summit prepration

* Open discussion

  *   Minutes

  *
 *   "noauth" configuration
 *   
https://github.com/openstack/mistral/blob/master/mistral/context.py#L35 they 
have handled that case 
(pratapagoutham<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017//opnfv-meeting.2017-03-16-08.00.log.html#l-10>,
 08:02:09)
 *   functest issue is still remaining 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017//opnfv-meeting.2017-03-16-08.00.log.html#l-32>,
 08:09:24)
 *   continue to fix functest issue offline 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017//opnfv-meeting.2017-03-16-08.00.log.html#l-103>,
 08:28:35)
 *   E-Release discussion and OPNFV Beijing summit 
prepration(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017//opnfv-meeting.2017-03-16-08.00.log.html#l-104>,
 08:29:23)
 *   ACTION: ping HA team for VNF to run in multisite 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017//opnfv-meeting.2017-03-16-08.00.log.html#l-133>,
 08:43:25)

  *   Link
 *   Minutes: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-16-08.00.html

 *   Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-16-08.00.txt
 *   
Log:http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-16-08.00.log.html

Best Regards
Chaoyi Huang (joehuang)

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of joehuang 
[joehu...@huawei.com]
Sent: 15 March 2017 16:17
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [multisite]weekly meeting of Mar.16


Hello, team,

Mar.16 2017 Agenda:

* Functest issue.

* E-Release discussion

* OPNFV Beijing summit prepration

* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.


Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] VNF to demonstrate VNF high availability across VIM

2017-03-15 Thread joehuang

Hello,

In multisite, we have one use cases ever discussed:

Now, it's time to bring it into reality.

If you are interested in such an use case, please join us, help would be
appreciated:

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]weekly meeting of Mar.16

2017-03-15 Thread joehuang

Hello, team,

Mar.16 2017 Agenda:

* Functest issue.

* E-Release discussion

* OPNFV Beijing summit prepration

* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.


Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]meeting minutes of Mar.9

2017-03-09 Thread joehuang

Hello, team,


Mar.9 2017: Agenda & Minutes

  *   Agenda

* Functest issue.

* D-release branching

* Kingbird feature development.

* Open discussion

  *   Minutes

  *
 *   kingbird run normally in functest environment 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-09-08.11.log.html#l-21>,
 08:17:10)
 *   the stable branch will be created by Aric for OPNFV D release on this 
Friday 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-09-08.11.log.html#l-27>,
 08:20:24)
 *   Release Danube 1.0 on Mar.27 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-09-08.11.log.html#l-34>,
 08:22:06)

  *   Link
 *   Minutes: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-09-08.11.html

 *   Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-09-08.11.txt
 *   
Log:http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-03-09-08.11.log.html

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]weekly meeting of Mar.9

2017-03-08 Thread joehuang

Hello, team,

Agenda of Mar.9 2017

* Functest issue.
* D-release branching
* Kingbird feature development.
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.


Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]weekly meeting of Mar.2

2017-03-01 Thread joehuang

Hello, team,

Agenda of Mar.2 2017

* Functest issue.
* D-release preparation.
* Kingbird feature development.
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.


Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [functest]multisite test executed, but test cases not being execeuted

After kingbird installation in Functest was restored, the multisite test was 
executed, but test cases not being execeuted



https://build.opnfv.org/ci/view/multisite/job/functest-fuel-virtual-suite-master/259/console



2017-02-23 03:07:39,016 - Tempest - INFO - Tempest multisite success_rate is 
0%, is marked as FAIL
2017-02-23 03:07:39,016 - openstack_clean - INFO - Cleaning OpenStack 
resources...
2017-02-23 03:07:39,023 - openstack_utils - INFO - OS_IDENTITY_API_VERSION is 
set in env as '3'
2017-02-23 03:07:47,835 - openstack_utils - ERROR - Error 
[remove_gateway_router(neutron_client, 
'90f89c6f-46f2-46d7-8725-1be7e9630bd0')]: Request Failed: internal server error 
while processing your request.
Neutron server returns request_ids: ['req-4838f98a-5e9d-47ed-ba94-4c957843ed76']
2017-02-23 03:07:47,835 - openstack_clean - ERROR - There has been a problem 
removing the gateway...
2017-02-23 03:07:54,525 - run_tests - INFO - Test execution time: 00:41
2017-02-23 03:07:54,525 - run_tests - ERROR - The test case 'multisite' failed.
2017-02-23 03:07:54,525 - run_tests - INFO - Execution exit value: 
Result.EX_ERROR
2017-02-23 03:07:54,584 - functest_utils - ERROR - The command 'python 
/home/opnfv/repos/functest/functest/ci/run_tests.py  -t 'multisite'' failed

But the tempest test cases for kingbird could be discovered in Functest 
container:

root@d6b3b8fd39e8:~/repos/tempest# testr list-tests | grep kingbird
scenario.quota_management.client_tests.test_quota_management_api.KingbirdQMTestJSON.test_kingbird_delete_all_method
scenario.quota_management.client_tests.test_quota_management_api.KingbirdQMTestJSON.test_kingbird_delete_method
scenario.quota_management.client_tests.test_quota_management_api.KingbirdQMTestJSON.test_kingbird_get_default_method_after_delete
scenario.quota_management.client_tests.test_quota_management_api.KingbirdQMTestJSON.test_kingbird_get_default_method_after_update
scenario.quota_management.client_tests.test_quota_management_api.KingbirdQMTestJSON.test_kingbird_get_method
scenario.quota_management.client_tests.test_quota_management_api.KingbirdQMTestJSON.test_kingbird_put_method
scenario.quota_management.client_tests.test_quota_management_api.KingbirdQMTestJSON.test_kingbird_put_method_wrong_token

It worked before the kingbird installation was commented in Functest image 
build scripts.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [netready] OPNFV Hackfest Paris

Hello,

When we talk about edge cloud, if it's vCPE scenario, then the resource is very 
limited. I am not sure Gluon L3VPN will try to address this scenario or not.

If Gluon L3VPN plans to do so, then where the OpenStack/SDN Controller will be 
deployed? In limited resource edge site? If OpenStack/SDN Controller is not 
deployed into the edge site, then how to address the cross site control plane 
communication?

There are several companies working on lightweight OpenStack (embedded-able 
OpenStack, in one VM) to make it run in edge cloud nodes. For example, this 
company already developed a lightweight embedded OpenStack solution for vCPE: 
http://www.advaoptical.com/~/media/Resources/Application%20Notes/Virtual%20CPE%20White%20Paper.ashx

So I am curious how Gluon L3VPN will be deployed in edge cloud scenario.

Best Regards
Chaoyi Huang (joehuang)

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Prakash Ramchandran 
[prakash.ramchand...@huawei.com]
Sent: 23 February 2017 2:57
To: Georg Kunz; HU, BIN (bh5...@att.com); Tim Irnich; Nikolas Hermanns; 
gergely.csat...@nokia.com; jlin...@cisco.com; Ahmed Elbornou (amaged) 
(ama...@cisco.com); opnfv-tech-discuss@lists.opnfv.org; 
thomas.hamble...@nokia.com
Subject: Re: [opnfv-tech-discuss] [netready] OPNFV Hackfest Paris

George,

Following your drive to add vSwitch HA and other use cases encouraged to find 
if  Gluon L3VPN use case is addressed before I can look at Edge Cloud.

If I missed any review on L3VPN point to me and will follow up.

 If not yet, this  time we can move 
NETREADY-7<https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=99&projectKey=NETREADY&view=planning&selectedIssue=NETREADY-7>
  that to Release-E as potential candidate which points to 
https://en.wikipedia.org/wiki/Cloudlet

Thanks
Prakash


Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@huawei.com>
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






From: Georg Kunz [mailto:georg.k...@ericsson.com]
Sent: Wednesday, February 22, 2017 8:45 AM
To: HU, BIN (bh5...@att.com); Tim Irnich; Nikolas Hermanns; 
gergely.csat...@nokia.com; Prakash Ramchandran; jlin...@cisco.com; Ahmed 
Elbornou (amaged) (ama...@cisco.com); opnfv-tech-discuss@lists.opnfv.org; 
thomas.hamble...@nokia.com
Subject: [opnfv-tech-discuss][netready] OPNFV Hackfest Paris

Hi all,

As promised in the last NetReady meeting, I would like to start a discussion 
about potential topics for the upcoming plugfest and hackfest and bounce them 
with the team.

The plugfest / hackfest will take place in Paris (France) April 24 - 28.

Potential hackfest agenda items for the NetReady team:

· Evolution of the Gluon integration

o   Creation and integration of other protons (APIs)

§  SFC

§  layer-2 networking

§  “exotic networking use case” showcasing Gluon’s flexibility

o   Maintenance of existing scenario

o   Extension of Gluon scenario to other installers

· Potential new use cases

o   Container networking

o   Edge cloud networking

o   Information centric networking

o   …

This is just a starting point. Your feedback is very welcome. Let’s try to 
jointly build a good agenda.

Best regards
Georg
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][danube] MS6 compliance assessment

Hello, David,

The status of multisite is as follows:

Enabling testing for your project in the Functest repo (or other test framework 
repo if you are not using functest)
1) multisite deployments refactoring was finished: 
https://build.opnfv.org/ci/view/multisite/builds
2) kingbird test restoration in Funtest was just merged today: 
https://gerrit.opnfv.org/gerrit/#/c/29003/

Test case implementation in your project repo.
1) All test cases will be embedded into the Functest container image after the 
restoration patch merged: https://gerrit.opnfv.org/gerrit/#/c/29003/
2) the original tempest test cases  are stored in
https://github.com/openstack/kingbird/tree/master/kingbird/tests/tempest/scenario

Please indicate whether the scenarios with which your project is integrated are 
visible on the Functest dashboard.  If not, why?
The feature projects (Kingbird, Tricircle) from multisite have not been 
integrated with installer yet, plan to do the integration in E release. These 
projects are still in development phase in C/D release.
Preliminary Documentation Requirement

  1.  http://artifacts.opnfv.org/multisite/docs/release_installation/index.html
http://artifacts.opnfv.org/multisite/docs/release_overview/index.html
http://artifacts.opnfv.org/multisite/docs/release_userguide/index.html
http://artifacts.opnfv.org/multisite/docs/release_configguide/index.html

There maybe some issues after the Kingbird Functest restoration patch merged, 
after the Kingbird Functest recover to normal, it's ready to do release for 
Multisite. (All test cases are ready and already pass the test locally before 
the Kingbird Functest restoration).

Best Regards
Chaoyi Huang (joehuang)

From: opnfv-project-leads-boun...@lists.opnfv.org 
[opnfv-project-leads-boun...@lists.opnfv.org] on behalf of David McBride 
[dmcbr...@linuxfoundation.org]
Sent: 23 February 2017 4:30
To: opnfv-project-le...@lists.opnfv.org; TECH-DISCUSS OPNFV
Subject: [opnfv-project-leads] [release][danube] MS6 compliance assessment

Team,

I'd like to request that the PTLs for projects participating in Danube respond 
to the following questions, designed to assess compliance with MS6.
Feature Projects

  1.  Please provide a list of commits for the following:
 *   Enabling testing for your project in the Functest repo (or other test 
framework repo if you are not using functest)
 *   Test case implementation in your project repo.
  2.  Please indicate whether the scenarios with which your project is 
integrated are visible on the Functest dashboard.  If not, why?

Test Framework Projects

  1.  Please provide a list of commits for your self-validation tests.

Preliminary Documentation Requirement

  1.  Please provide a link to the preliminary documentation for your project.


Let me know if you have any questions.

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]weekly meeting of Feb.23

Hello, team,

Agenda of Feb.23 2017

* Multisite deployment/functest environment readiness/restoration.
* D-release preparation.
* Kingbird feature development.
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.


Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [functest][multisite] restore kingbird functest

2017-02-17 Thread joehuang

Hello,

Kingbird functest was excluded from Functest due to python client dependency 
conflict. But in Functest container, the kingbird was installed only for 
tempest plugin descovery and execution of tempest test cases. Kingbird is not 
sensitive to the python client version of OpenStack. So it's safe to replace 
kingbird's client's requirements to Functest's requirements in Functest 
container. After the replacement,
all client's requirements will be kept in consistent even after kingbird's
installation in the Functest container.

One patch was prepared to restore the kingbird functest, please help review it 
and make
 it being restored soon.

https://gerrit.opnfv.org/gerrit/#/c/29003/

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [[functest] back of multsite test

2017-02-16 Thread joehuang

Hello,

Kingbird test was removed from Functest due to requirements conflict, and there 
is one suggestion to use venv to install kingbird tempest test cases into 
Functest, for tempest plugin discovery.

https://jira.opnfv.org/browse/FUNCTEST-635

Would like to know whether it's possible to fix it in D release?

The multisite CI environment is ready : build.opnfv.org/ci/view/multisite/

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]meeting minutes of Feb. 16

2017-02-15 Thread joehuang

Hello, team,

Agenda of Feb.16 2017

* Multisite deployment environment.
* (MS6) Test cases implemented, preliminary documentation completed, and stable 
branch open
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite] document review

2017-02-10 Thread joehuang

Hello, team,

Please review the document update for multisite D release.
https://gerrit.opnfv.org/gerrit/#/c/28217/

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]meeting minutes of Feb.9

2017-02-09 Thread joehuang

Hello, team,

The minutes of the weekly meeting is as follows:


Feb.9 2017: Agenda & Minutes

  *   Agenda

  1.
 *   https://jira.opnfv.org/browse/FUNCTEST-721 
(sorantis<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-02-09-08.02.log.html#l-28>,
 08:09:28)
 *   https://review.openstack.org/#/c/416507/ 
(goutham<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-02-09-08.02.log.html#l-36>,
 08:14:10)
 *   adding kbclient to kingbird requirements.txt to see if it succeeds 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-02-09-08.02.log.html#l-54>,
 08:20:19)
 *   https://review.openstack.org/#/c/416507/ 
(goutham<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-02-09-08.02.log.html#l-75>,
 08:27:55)
 *   a new commit of tempest test for the quota management bug fix 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-02-09-08.02.log.html#l-99>,
 08:32:35)

  *   Minutes

  *
 *   Multi Region environment ready soon 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-19-08.02.log.html#l-49>,
 08:19:21)
 *   remove item level quota deletion 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-19-08.02.log.html#l-63>,
 08:24:29)
 *   ACTION: release python-kingbirdclient so that kingbird tempest can use 
it 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-19-08.02.log.html#l-64>,
 08:24:59)

  *   Link
 *   Minutes: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-02-09-08.02.html

 *   Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-02-09-08.02.txt
 *   Log: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-02-09-08.02.log.html

Best Regards
Chaoyi Huang (joehuang)

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of joehuang 
[joehu...@huawei.com]
Sent: 08 February 2017 11:17
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [multisite]Weekly meeting of Feb.9

Hello, team,

Agenda of Feb.9 2017

* (MS6) Test cases implemented, preliminary documentation completed, and stable 
branch open
* Multisite deployment environment.
* Kingbird feature development.
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.


Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]Weekly meeting of Feb.9

2017-02-07 Thread joehuang

Hello, team,

Agenda of Feb.9 2017

* (MS6) Test cases implemented, preliminary documentation completed, and stable 
branch open
* Multisite deployment environment.
* Kingbird feature development.
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.


Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]Weekly meeting of Jan.19

2017-01-18 Thread joehuang

Hello, team,

Agenda of Jan.19 2017

* Multisite deployment environment.
* Kingbird feature development.
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite] Meeting minutes of Jan.12

2017-01-17 Thread joehuang

Hello, team,


Jan.12 2017: Agenda & Minutes

  *   Agenda

* D release discussion

* VNF Geo site disaster recovery

* Kingbird feature development

* Open discussion

  *   Minutes

  *
 *   https://wiki.opnfv.org/display/multisite/Multisite+Release+D+Planning 
(joehuang_, 08:10:34)

  *
 *   https://releases.openstack.org/ocata/schedule.html (joehuang_, 
08:13:48)

  *
 *   stick to the release plan of OPNFV D release and Ocata release. 
Feature freeze Feb.16, branch created on Feb.17 (joehuang, 08:20:34)

  *
 *   VNF Geo site disaster recovery (joehuang, 08:21:52)

  *
 *   multisite requirements documentation update is needed for D release 
(joehuang, 08:43:30)

  *
 *   kingbird feature development (joehuang, 08:47:29)

  *
 *   migrate curl to use client SDK (joehuang, 08:54:17)

  *   Link
 *   Minutes: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-12-08.01.html

 *   Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-12-08.01.txt
 *   Log: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-12-08.01.log.html

Best Regards
Chaoyi Huang (joehuang)

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of joehuang 
[joehu...@huawei.com]
Sent: 11 January 2017 16:39
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [multisite]Weekly meeting of Jan.12

Hello, team,

Agenda of Jan.12 2017

* D release discussion
* VNF Geo site disaster recovery
* Kingbird feature development
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

2017-01-15 Thread joehuang

hello, Goutham,

It's great for your update.

Your patch is good for command line interface. But abstract is needed to work 
as SDK,

for example, for novaclient, you can

from novaclient import client

You can initialize the client

self.nova_client = client.Client(API_VERSION,
session=session,
region_name=region)
and use nova_client to call API provided by Nova:

limits = self.nova_client.limits.get(

tenant_id=project_id).to_dict()

It's same for python-kingbirdclient: not only used for CLI, but also can serve 
as SDK



Best Regards
Chaoyi Huang (joehuang)

From: Goutham Pratapa [goutham.prat...@tcs.com]
Sent: 16 January 2017 3:05
To: joehuang
Cc: caizhiyuan (A); opnfv-tech-discuss; Dimitri Mazmanov
Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hi all,

I have updated the document with the SYNC_JOB structure the table we are going 
to follow for the keypair sync job.

https://docs.google.com/document/d/1fXvhUj1v16TLe72UsWi6CHZxwBmePWckam2_u9fr4Qk/edit#

I have updated the document with ER diagram and brief description. We have to 
act fast to meet our deadline.

So please provide your feedback and comments. Our target is to make the keypair 
syncing an async approach between client and engine.

at least we will give it a try to complete.

In the mean while i will try and convert all the tempest test cases with python 
clients.To help that it will be better if we can get this commit reviewed 
https://review.openstack.org/#/c/418412/

and close the commit soon to complete kingbird sdk as soon as possible. :)

Thanks
Goutham


-Goutham Pratapa/HYD/TCS wrote: -
To: joehuang 
From: Goutham Pratapa/HYD/TCS
Date: 01/13/2017 11:45AM
Cc: "caizhiyuan (A)" , opnfv-tech-discuss 
, "Dimitri Mazmanov" 

Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hi Joe,

I have created a new doc.

https://docs.google.com/document/d/1fXvhUj1v16TLe72UsWi6CHZxwBmePWckam2_u9fr4Qk/edit#

and shared it with respective gmail id's please go through and provide your 
comments.

Thanks
Goutham


-joehuang  wrote: -
To: Goutham Pratapa 
From: joehuang 
Date: 01/13/2017 09:35AM
Cc: Ashish singh , "caizhiyuan (A)" 
, opnfv-tech-discuss 

Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hello, Goutham,

Thank you for the update. But the documentation needs to clean, there are lots 
of comment, and inconsistency in several places. Don't know which updates are 
new one or old one.

Best Regards
Chaoyi Huang (joehuang)

From: Goutham Pratapa [goutham.prat...@tcs.com]
Sent: 13 January 2017 1:12
To: joehuang
Cc: Ashish singh; caizhiyuan (A); opnfv-tech-discuss
Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hi all,

I request you all to go through the document and provide comments..

I have made changes regarding api structure.

Thanks
Goutham


-Goutham Pratapa/HYD/TCS wrote: -
To: joehuang 
From: Goutham Pratapa/HYD/TCS
Date: 01/06/2017 05:40PM
Cc: Ashish singh , "caizhiyuan (A)" 
, opnfv-tech-discuss 

Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hi all,

I have changed the document. based on our discussion to remove User-id from Url 
Path.

Thanks
Goutham


-Goutham Pratapa/HYD/TCS wrote: -
To: joehuang 
From: Goutham Pratapa/HYD/TCS
Date: 12/09/2016 10:29AM
Cc: Ashish singh , "caizhiyuan (A)" 
, opnfv-tech-discuss 

Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hi all,

I changed the document following are the links

https://docs.google.com/document/d/1N6HFAFUT5BbEp1wbnYjgaKdOlyJanwkXccv-_1zsVQc/edit?disco=A03Vdcc

https://docs.google.com/document/d/1N6HFAFUT5BbEp1wbnYjgaKdOlyJanwkXccv-_1zsVQc/edit?disco=A4VEf0U

https://docs.google.com/document/d/1N6HFAFUT5BbEp1wbnYjgaKdOlyJanwkXccv-_1zsVQc/edit?disco=A0y2I0c

Changed the document and Please provide your feedback so that we can keep lock 
on the things to be implemented for now.

and start implementation based upon the locked document.

Thanks
Goutham


-joehuang  wrote: -
To: Goutham Pratapa 
From: joehuang 
Date: 12/09/2016 07:51AM
Cc: Ashish singh , "caizhiyuan (A)" 
, opnfv-tech-discuss 

Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hello, Goutham,

For os-sync API, two suggestions:

1. we need to use POST but not put for this action
2. Even for single resource sync, "ID" should be part of the request body, but 
not as part of the URL path.


Best Regards
Chaoyi Huang (joehuang)

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of joehuang 
[joehu...@huawei.com]
Sent: 07 December 2016 16:32
To: Goutham Pratapa
Cc: Ashish singh; caizhiyuan (A); opnfv-tech-discuss
Subject: Re: [opnfv-tech-discuss] [multisi

Re: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

2017-01-12 Thread joehuang

Hello, Goutham,

Thank you for the update. But the documentation needs to clean, there are lots 
of comment, and inconsistency in several places. Don't know which updates are 
new one or old one.

Best Regards
Chaoyi Huang (joehuang)

From: Goutham Pratapa [goutham.prat...@tcs.com]
Sent: 13 January 2017 1:12
To: joehuang
Cc: Ashish singh; caizhiyuan (A); opnfv-tech-discuss
Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hi all,

I request you all to go through the document and provide comments..

I have made changes regarding api structure.

Thanks
Goutham


-Goutham Pratapa/HYD/TCS wrote: -
To: joehuang 
From: Goutham Pratapa/HYD/TCS
Date: 01/06/2017 05:40PM
Cc: Ashish singh , "caizhiyuan (A)" 
, opnfv-tech-discuss 

Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hi all,

I have changed the document. based on our discussion to remove User-id from Url 
Path.

Thanks
Goutham


-Goutham Pratapa/HYD/TCS wrote: -----
To: joehuang 
From: Goutham Pratapa/HYD/TCS
Date: 12/09/2016 10:29AM
Cc: Ashish singh , "caizhiyuan (A)" 
, opnfv-tech-discuss 

Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hi all,

I changed the document following are the links

https://docs.google.com/document/d/1N6HFAFUT5BbEp1wbnYjgaKdOlyJanwkXccv-_1zsVQc/edit?disco=A03Vdcc

https://docs.google.com/document/d/1N6HFAFUT5BbEp1wbnYjgaKdOlyJanwkXccv-_1zsVQc/edit?disco=A4VEf0U

https://docs.google.com/document/d/1N6HFAFUT5BbEp1wbnYjgaKdOlyJanwkXccv-_1zsVQc/edit?disco=A0y2I0c

Changed the document and Please provide your feedback so that we can keep lock 
on the things to be implemented for now.

and start implementation based upon the locked document.

Thanks
Goutham


-joehuang  wrote: -
To: Goutham Pratapa 
From: joehuang 
Date: 12/09/2016 07:51AM
Cc: Ashish singh , "caizhiyuan (A)" 
, opnfv-tech-discuss 

Subject: RE: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hello, Goutham,

For os-sync API, two suggestions:

1. we need to use POST but not put for this action
2. Even for single resource sync, "ID" should be part of the request body, but 
not as part of the URL path.


Best Regards
Chaoyi Huang (joehuang)

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of joehuang 
[joehu...@huawei.com]
Sent: 07 December 2016 16:32
To: Goutham Pratapa
Cc: Ashish singh; caizhiyuan (A); opnfv-tech-discuss
Subject: Re: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hello, two comments in the doc. Need to discuss this in the weekly meeting.

Best Regards
Chaoyi Huang (joehuang)

From: Goutham Pratapa [goutham.prat...@tcs.com]
Sent: 07 December 2016 14:15
To: joehuang
Cc: Ashish Singh7; Dimitri Mazmanov; Ashish singh; caizhiyuan (A); Meimei; 
opnfv-tech-discuss; Sama, Malla Reddy; Zhipeng Huang; pratapagout...@gmail.com
Subject: RE: [opnfv-tech-discuss][multisite] Secgroup syncing Approach

Hi all,

Made some comments regarding Syncing of multiple keypairs at a time

https://docs.google.com/document/d/1N6HFAFUT5BbEp1wbnYjgaKdOlyJanwkXccv-_1zsVQc/edit?disco=A4VEf0U

as off now we have implemented keypair-sync for a specified keypair or sync all 
keypairs

Ashish and I thought this option will also help.

Please find the link and provide your feedback on this.

Thanks
Goutham


-joehuang  wrote: -
To: Goutham Pratapa 
From: joehuang 
Date: 11/30/2016 06:57PM
Cc: Ashish Singh7 , Dimitri Mazmanov 
, Ashish singh , 
"caizhiyuan (A)" , Meimei , 
opnfv-tech-discuss , "Sama, Malla Reddy" 
, Zhipeng Huang , 
"pratapagout...@gmail.com" 
Subject: RE: [opnfv-tech-discuss][multisite] Secgroup syncing Approach

hello, Goutham,

When I tried to review your update, and click "see new changes", it said you 
have removed the update, I did not find the update yet.

Best Regards
Chaoyi Huang (joehuang)
____
From: Goutham Pratapa [goutham.prat...@tcs.com]
Sent: 29 November 2016 17:09
To: joehuang
Cc: Ashish Singh7; Dimitri Mazmanov; Ashish singh; caizhiyuan (A); Meimei; 
opnfv-tech-discuss; Sama, Malla Reddy; Zhipeng Huang; pratapagout...@gmail.com
Subject: RE: [opnfv-tech-discuss][multisite] Secgroup syncing Approach

Hi all,

I have made some comments regarding the keypair syncing.

which allows user to sync only specified keypair and option for syncing all 
keypairs.

Thanks
Goutham


-joehuang  wrote: -
To: Ashish Singh7 
From: joehuang 
Date: 11/01/2016 01:59PM
Cc: Dimitri Mazmanov , Ashish singh 
, "caizhiyuan (A)" , Meimei 
, opnfv-tech-discuss , 
"Sama, Malla Reddy" , Zhipeng Huang 
, Goutham Pratapa , 
"pratapagout...@gmail.com" 
Subject: RE: [opnfv-tech-discuss][multisite] Secgroup syncing Approach

Just one more comment for t

[opnfv-tech-discuss] [multisite]Weekly meeting of Jan.12

2017-01-11 Thread joehuang

Hello, team,

Agenda of Jan.12 2017

* D release discussion
* VNF Geo site disaster recovery
* Kingbird feature development
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] ETSI NFV Call for Experts on OpenStack vs IFA00[56] gap analyzis

2017-01-10 Thread joehuang

Ok. If IFA005/IFA006 is not defined as the API interface syntax, just for 
functionality description, I think the gap is not so huge.

So only need to check for each interface defined in IFA005/IFA006 whether this 
interface's function could be supported by OpenStack.

Best Regards
Chaoyi Huang (joehuang)

From: Csatari, Gergely (Nokia - HU/Budapest) [gergely.csat...@nokia.com]
Sent: 10 January 2017 16:09
To: joehuang; opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] ETSI NFV Call for Experts on OpenStack vs 
IFA00[56] gap analyzis

Hi,

Thanks for the quick analyzis.
The target of the current call for experts is only to identify the gaps. We are 
not looking to one-to-one match for each information element and each operation 
of IFA005 and 006 but looking for the same functionality provided by OpenStack.

Br,
Gerg0

From: joehuang [mailto:joehu...@huawei.com]
Sent: Tuesday, January 10, 2017 1:59 AM
To: Csatari, Gergely (Nokia - HU/Budapest) ; 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] ETSI NFV Call for Experts on OpenStack vs 
IFA00[56] gap analyzis

Hello,

I go through the IFA 005 & IFA 006. The difference between API defined in IFA 
005/IFA 006 and OpenStack API is very huge, it seems that there must be some 
wrapper layer above OpenStack API.

Best Regards
Chaoyi Huang (joehuang)

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Csatari, Gergely 
(Nokia - HU/Budapest) [gergely.csat...@nokia.com]
Sent: 10 January 2017 2:41
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: [opnfv-tech-discuss] ETSI NFV Call for Experts on OpenStack vs 
IFA00[56] gap analyzis
Hi,

Now I resend it to correct an actual mistake in my original mail.

The deadline for application is 26th of January.

There is an effort in ETSI NFV to identify the gaps between the specified VIM 
NB API-s and the OpenStack NB API-s (what called TST003). We, who are working 
on this item realized that we need to involve external expertise to have the 
desired progress of the work.
ETSI NFV decided to start a task force and call for external experts. The task 
is to analyze the API-s described in IFA005 and IFA006 and point out the gaps 
compared to the OpenStack API-s (Closing the gaps either on NFV or in OpenStack 
side is not in the scope of the work).
I’m sending this mail to you to draw your attention to this possibility as 
experts in the OPNFV community have the right mix of knowledge for an applicant.

The deadline for application is 2017.01.26. Work starts in March and results 
should be delivered by August.
More details are here: 
https://wiki.opnfv.org/display/meetings/TSC?preview=/2925933/8687963/CL16_3343r1%20Clean%20-%20Call%20for%20Expertise%20-%20Identification%20of%20Gaps%20between%20docx

In case of any questions please mail or irc (csatari on freenode) me.

Br,
Gerg0



___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [multisite] Multisite VNF Geo site disaster recovery

Hello,

If you are interested in this topic, we can discuss it in the weekly meeting, 
but I don't know whether the meeting time works for you or not.

http://webchat.freenode.net/?channels=opnfv-meeting every Thursday, 8:00-9:00 
UTC (During winter time, means CET 9:00 AM).

Best Regards
Chaoyi Huang (joehuang)

From: Klemen Pogacnik [kle...@psi-net.si]
Sent: 09 January 2017 20:57
To: joehuang
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [multisite] Multisite VNF Geo site disaster 
recovery

Thanks for answer. If I understand right, currently there is no work on DR with 
2 or more Openstack clouds. Is it maybe planned for the future?
Kemo

On Mon, Jan 9, 2017 at 7:50 AM, joehuang 
mailto:joehu...@huawei.com>> wrote:
Hello,

Thank you for the mail, please see inline comments:

Best Regards
Chaoyi Huang (joehuang)

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 
[opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>]
 on behalf of Klemen Pogacnik [kle...@psi-net.si<mailto:kle...@psi-net.si>]
Sent: 06 January 2017 22:05
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: [opnfv-tech-discuss] [multisite] Multisite VNF Geo site disaster 
recovery

I'm trying to deploy Multisite VNF Geo site disaster recovery scenario with 
Ceph as a backend for a Cinder service (scenario 3, 3rd way) . Ceph rbd 
mirroring is used for data replication between two sites. Volume created on 
site1 is replicated to site2, but this volume is not visible on Cinder on 
side2. Probably some metadata from Cinder DB must be replicated too. Has 
anybody been thinkink or even working on that?

---> yes, current replication implementation will hide all these information 
from the API level, and the replication fail-over, fail-back are activities 
inside one OpenStack domain. you have to replicate the db to the site2 if you 
want to do DR with different OpenStack cloud. We had discussed with the 
community, whether it's reasonable to expose the volume reference from the 
admin API, community prefer to let the driver to deal with these information.


The second question is, how to make switchover, when site one goes down. On 
open stack there is cinder failover-host command, which is, as I can 
understand, only useful for configuration with one openstack and two ceph 
clusters. Any idea how to make switchover with two openstacks each connected to 
its own ceph cluster.
Thanks a lot for help!

---> This needs to be triggered by GR software, or manually, or via DNS(if 
applicable).

Kemo





___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [multisite] Multisite VNF Geo site disaster recovery

Hello,

If you are interested in this topic, we can discuss it in the weekly meeting, 
but I don't know whether the meeting time works for you or not.

http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM)

Best Regards
Chaoyi Huang (joehuang)

From: Klemen Pogacnik [kle...@psi-net.si]
Sent: 09 January 2017 20:57
To: joehuang
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [multisite] Multisite VNF Geo site disaster 
recovery

Thanks for answer. If I understand right, currently there is no work on DR with 
2 or more Openstack clouds. Is it maybe planned for the future?
Kemo

On Mon, Jan 9, 2017 at 7:50 AM, joehuang 
mailto:joehu...@huawei.com>> wrote:
Hello,

Thank you for the mail, please see inline comments:

Best Regards
Chaoyi Huang (joehuang)

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 
[opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>]
 on behalf of Klemen Pogacnik [kle...@psi-net.si<mailto:kle...@psi-net.si>]
Sent: 06 January 2017 22:05
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: [opnfv-tech-discuss] [multisite] Multisite VNF Geo site disaster 
recovery

I'm trying to deploy Multisite VNF Geo site disaster recovery scenario with 
Ceph as a backend for a Cinder service (scenario 3, 3rd way) . Ceph rbd 
mirroring is used for data replication between two sites. Volume created on 
site1 is replicated to site2, but this volume is not visible on Cinder on 
side2. Probably some metadata from Cinder DB must be replicated too. Has 
anybody been thinkink or even working on that?

---> yes, current replication implementation will hide all these information 
from the API level, and the replication fail-over, fail-back are activities 
inside one OpenStack domain. you have to replicate the db to the site2 if you 
want to do DR with different OpenStack cloud. We had discussed with the 
community, whether it's reasonable to expose the volume reference from the 
admin API, community prefer to let the driver to deal with these information.


The second question is, how to make switchover, when site one goes down. On 
open stack there is cinder failover-host command, which is, as I can 
understand, only useful for configuration with one openstack and two ceph 
clusters. Any idea how to make switchover with two openstacks each connected to 
its own ceph cluster.
Thanks a lot for help!

---> This needs to be triggered by GR software, or manually, or via DNS(if 
applicable).

Kemo





___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] ETSI NFV Call for Experts on OpenStack vs IFA00[56] gap analyzis

Hello,

I go through the IFA 005 & IFA 006. The difference between API defined in IFA 
005/IFA 006 and OpenStack API is very huge, it seems that there must be some 
wrapper layer above OpenStack API.

Best Regards
Chaoyi Huang (joehuang)

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Csatari, Gergely 
(Nokia - HU/Budapest) [gergely.csat...@nokia.com]
Sent: 10 January 2017 2:41
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] ETSI NFV Call for Experts on OpenStack vs 
IFA00[56] gap analyzis

Hi,

Now I resend it to correct an actual mistake in my original mail.

The deadline for application is 26th of January.

There is an effort in ETSI NFV to identify the gaps between the specified VIM 
NB API-s and the OpenStack NB API-s (what called TST003). We, who are working 
on this item realized that we need to involve external expertise to have the 
desired progress of the work.
ETSI NFV decided to start a task force and call for external experts. The task 
is to analyze the API-s described in IFA005 and IFA006 and point out the gaps 
compared to the OpenStack API-s (Closing the gaps either on NFV or in OpenStack 
side is not in the scope of the work).
I’m sending this mail to you to draw your attention to this possibility as 
experts in the OPNFV community have the right mix of knowledge for an applicant.

The deadline for application is 2017.01.26. Work starts in March and results 
should be delivered by August.
More details are here: 
https://wiki.opnfv.org/display/meetings/TSC?preview=/2925933/8687963/CL16_3343r1%20Clean%20-%20Call%20for%20Expertise%20-%20Identification%20of%20Gaps%20between%20docx

In case of any questions please mail or irc (csatari on freenode) me.

Br,
Gerg0



___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] ETSI NFV Call for Experts on OpenStack vs IFA00[56] gap analyzis

Hello, Gerg0,

could you please provide the link of ETSI documents? I want to have a look.

Best Regards
Chaoyi Huang (joehuang)

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Csatari, Gergely 
(Nokia - HU/Budapest) [gergely.csat...@nokia.com]
Sent: 09 January 2017 17:31
To: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] ETSI NFV Call for Experts on OpenStack vs 
IFA00[56] gap analyzis

Hi,

Resending my mail in the hope that it gets into the top of your after holiday 
mail pile.

Br,
GErg0

From: Csatari, Gergely (Nokia - HU/Budapest)
Sent: Wednesday, December 21, 2016 9:53 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: ETSI NFV Call for Experts on OpenStack vs IFA00[56] gap analyzis

Hi,

There is an effort in ETSI NFV to identify the gaps between the specified VIM 
NB API-s and the OpenStack NB API-s (what called TST003). We, who are working 
on this item realized that we need to involve external expertise to have the 
desired progress of the work.
ETSI NFV decided to start a task force and call for external experts. The task 
is to analyze the API-s described in IFA005 and IFA006 and point out the gaps 
compared to the OpenStack API-s (Closing the gaps either on NFV or in OpenStack 
side is not in the scope of the work).
I’m sending this mail to you to draw your attention to this possibility as 
experts in the OPNFV community have the right mix of knowledge for an applicant.

The deadline for application is 2017.01.16. Work starts in March and results 
should be delivered by August.
More details are here: 
https://wiki.opnfv.org/display/meetings/TSC?preview=/2925933/8687963/CL16_3343r1%20Clean%20-%20Call%20for%20Expertise%20-%20Identification%20of%20Gaps%20between%20docx

In case of any questions please mail or irc (csatari on freenode) me.

Br,
Gerg0

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [multisite] Multisite VNF Geo site disaster recovery

2017-01-08 Thread joehuang

Hello,

Thank you for the mail, please see inline comments:

Best Regards
Chaoyi Huang (joehuang)

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Klemen Pogacnik 
[kle...@psi-net.si]
Sent: 06 January 2017 22:05
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [multisite] Multisite VNF Geo site disaster 
recovery

I'm trying to deploy Multisite VNF Geo site disaster recovery scenario with 
Ceph as a backend for a Cinder service (scenario 3, 3rd way) . Ceph rbd 
mirroring is used for data replication between two sites. Volume created on 
site1 is replicated to site2, but this volume is not visible on Cinder on 
side2. Probably some metadata from Cinder DB must be replicated too. Has 
anybody been thinkink or even working on that?

---> yes, current replication implementation will hide all these information 
from the API level, and the replication fail-over, fail-back are activities 
inside one OpenStack domain. you have to replicate the db to the site2 if you 
want to do DR with different OpenStack cloud. We had discussed with the 
community, whether it's reasonable to expose the volume reference from the 
admin API, community prefer to let the driver to deal with these information.


The second question is, how to make switchover, when site one goes down. On 
open stack there is cinder failover-host command, which is, as I can 
understand, only useful for configuration with one openstack and two ceph 
clusters. Any idea how to make switchover with two openstacks each connected to 
its own ceph cluster.
Thanks a lot for help!

---> This needs to be triggered by GR software, or manually, or via DNS(if 
applicable).

Kemo




___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]meeting minutes of Jan.5

2017-01-05 Thread joehuang

Hi, team,

The meeting minutes is as follows:

  *   Agenda

* D release discussion

* Kingbird feature development

* Open discussion

  *   Minutes
 *   https://hastebin.com/utoseyodih.py 
(goutham_pratapa<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-05-08.03.log.html#l-23>,
 08:08:14)
 *   user-id for keypaire obtained from context or from the body 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-05-08.03.log.html#l-35>,
 08:11:40)
 *   http://$kb_ip_addr:8118/v1.0/$admin_tenant_id/os-quota-sets/defaults 
-- this is our curl request for getting the default limits and i tried 
replacing that with some random value and even then it 
worked.(goutham_pratapa<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-05-08.03.log.html#l-42>,
 08:14:07)
 *   https://review.openstack.org/#/c/416186/ -- have you gone through this 
commit.. 
(goutham_pratapa<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-05-08.03.log.html#l-99>,
 08:38:00)
  *   Link
 *   Minutes: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-05-08.03.html

 *   Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-05-08.03.txt
 *   Log: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-01-05-08.03.log.html

Best Regards
Chaoyi Huang (joehuang)

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of joehuang 
[joehu...@huawei.com]
Sent: 04 January 2017 17:06
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [multisite]Weekly meeting of Jan.5

Hello, team,

Welcome to the new year 2017.

Agenda of Jan.5 2017

* D release discussion
* Kingbird feature development
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.

Best Regards
Chaoyi Huang (joehuang)
____
From: joehuang
Sent: 21 December 2016 15:14
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [multisite]Weekly meeting of Dec.22

Hello, team,

As some team members are in Christmas and New Year holiday, we'll have a short 
chat in Dec.22 and Dec.29 meeting.

Agenda of Dec.22 2016

* Kingbird feature development
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]Weekly meeting of Jan.5

2017-01-04 Thread joehuang

Hello, team,

Welcome to the new year 2017.

Agenda of Jan.5 2017

* D release discussion
* Kingbird feature development
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.

Best Regards
Chaoyi Huang (joehuang)

From: joehuang
Sent: 21 December 2016 15:14
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [multisite]Weekly meeting of Dec.22

Hello, team,

As some team members are in Christmas and New Year holiday, we'll have a short 
chat in Dec.22 and Dec.29 meeting.

Agenda of Dec.22 2016

* Kingbird feature development
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]Weekly meeting of Dec.29

2016-12-28 Thread joehuang

Hello, team,

As some team members are in Christmas and New Year holiday, let's continue a 
short chat in Dec.29 meeting.

Agenda of Dec.29 2016

* Kingbird feature development
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.

Best Regards
Chaoyi Huang (joehuang)

From: joehuang
Sent: 21 December 2016 15:14
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [multisite]Weekly meeting of Dec.22

Hello, team,

As some team members are in Christmas and New Year holiday, we'll have a short 
chat in Dec.22 and Dec.29 meeting.

Agenda of Dec.22 2016

* Kingbird feature development
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]Weekly meeting of Dec.22

2016-12-20 Thread joehuang

Hello, team,

As some team members are in Christmas and New Year holiday, we'll have a short 
chat in Dec.22 and Dec.29 meeting.

Agenda of Dec.22 2016

* Kingbird feature development
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [multisite]Meeting minutes of Dec.15

2016-12-16 Thread joehuang

There is no command to get quota usage directly, and it's discussed one year 
ago, but no result, so Horizon have to use the similar way as what did in 
kingbird to calculate the quota usage on network resources.


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of joehuang 
[joehu...@huawei.com]
Sent: 16 December 2016 11:51
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [multisite]Meeting minutes of Dec.15


Hello, team,

The meeting minutes of Dec.15 is as follows:


Dec.15 2016: Agenda & Minutes

  *   Agenda

  *
 *   * Kingbird feature development
 *   * mutli-site deployment
 *   * Revisit Geographical Redundancy
 *   * Open discussion
  *Minutes

  1.
 *   Kingbird feature 
development(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-9>,
 08:02:26)
*   
https://bugs.launchpad.net/kingbird/+bug/1583967(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-21>,
 08:06:31)
*   
https://bugs.launchpad.net/kingbird/+bug/1583965(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-22>,
 08:06:44)
*   
https://review.openstack.org/#/c/314995/(sorantis<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-35>,
 08:13:54)
*   ACTION: update the code in the quota usgae calculation for cinder 
part to enhance the performance 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-40>,
 08:17:23)
*   
https://bugs.launchpad.net/kingbird/+bug/1583967(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-41>,
 08:18:03)
*   ACTION: check to see whether to report the bug for quota usage 
retrievement in the neutron 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-45>,
 08:22:57)
 *   mutli-site 
deployment(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-46>,
 08:23:30)
    *   
https://review.openstack.org/#/c/409653/(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-52>,
 08:27:00)

  *   Link

  *
 *   
Minutes:http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.html
 *   Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-14-15.58.txt
 *   Log: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html

Best Regards
Chaoyi Huang (joehuang)

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of joehuang 
[joehu...@huawei.com]
Sent: 14 December 2016 15:10
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [multisite]Weekly meeting of Dec.15

Hello, team,

Agenda of Dec.15 2016

* Kingbird feature development
* mutli-site deployment
* Revisit Geographical Redundancy
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite]Meeting minutes of Dec.15

2016-12-15 Thread joehuang

Hello, team,

The meeting minutes of Dec.15 is as follows:


Dec.15 2016: Agenda & Minutes

  *   Agenda

  *
 *   * Kingbird feature development
 *   * mutli-site deployment
 *   * Revisit Geographical Redundancy
 *   * Open discussion
  *Minutes

  1.
 *   Kingbird feature 
development(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-9>,
 08:02:26)
*   
https://bugs.launchpad.net/kingbird/+bug/1583967(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-21>,
 08:06:31)
*   
https://bugs.launchpad.net/kingbird/+bug/1583965(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-22>,
 08:06:44)
*   
https://review.openstack.org/#/c/314995/(sorantis<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-35>,
 08:13:54)
*   ACTION: update the code in the quota usgae calculation for cinder 
part to enhance the performance 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-40>,
 08:17:23)
*   
https://bugs.launchpad.net/kingbird/+bug/1583967(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-41>,
 08:18:03)
*   ACTION: check to see whether to report the bug for quota usage 
retrievement in the neutron 
(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-45>,
 08:22:57)
 *   mutli-site 
deployment(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-46>,
 08:23:30)
    *   
https://review.openstack.org/#/c/409653/(joehuang<http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html#l-52>,
 08:27:00)

  *   Link

  *
 *   
Minutes:http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.html
 *   Minutes (text): 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-14-15.58.txt
 *   Log: 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-15-08.01.log.html

Best Regards
Chaoyi Huang (joehuang)

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of joehuang 
[joehu...@huawei.com]
Sent: 14 December 2016 15:10
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [multisite]Weekly meeting of Dec.15

Hello, team,

Agenda of Dec.15 2016

* Kingbird feature development
* mutli-site deployment
* Revisit Geographical Redundancy
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] committer list maintainance

+1000 for this "I never think it is a shame to leave a project,  since it is 
normal that people move on to a new target and didn't have time to say goodbye"

Best Regards
Chaoyi Huang (joehuang)

From: Yujun Zhang [zhangyujun+...@gmail.com]
Sent: 14 December 2016 15:10
To: joehuang; Raymond Paik
Cc: opnfv-tech-discuss
Subject: Re: [opnfv-tech-discuss] committer list maintainance

I think there is no mandatory rule for PTL to attend TSC meeting in order to 
complete the removal process. At least, I never did that before.

On my side, I have tried to contact several inactive committers to ask for 
their willingness and most of them replies politely to explain why. And we have 
a happy ending by putting them in retired list[1].

I did encounter the situation that losing contact to some committer. And we 
just ask TSC to approve the removal and that's it.

After all, I never think it is a shame to leave a project, since it is normal 
that people move on to a new target and didn't have time to say goodbye.

[1]: 
https://wiki.opnfv.org/display/qtip/Platform+Performance+Benchmarking#PlatformPerformanceBenchmarking-RetiredCommitters

On Wed, Dec 14, 2016 at 2:17 PM joehuang 
mailto:joehu...@huawei.com>> wrote:
In OPNFV we "assume bad faith"? This is not a good assumption.

The less meeting, the better, and usually a TSC meeting will be in the night or 
early morning for me to join. If even need to go to TSC meeting for 5 minutes 
for approval, I would prefer to retain the inactive committer there, just let 
it be.

Best Regards
Chaoyi Huang (joehuang)

From: Raymond Paik [rp...@linuxfoundation.org<mailto:rp...@linuxfoundation.org>]
Sent: 14 December 2016 13:33

To: joehuang
Cc: opnfv-tech-discuss
Subject: Re: [opnfv-tech-discuss] committer list maintainance
Joe,

On the first point, I'm not sure why you are saying you need to be committer to 
submit a patch in OPNFV.  There are plenty of regular contributors who submit 
code/patches to OPNFV.  Let me know if I'm not understanding your point.

On your second point, I can recall a few committers who voluntarily stepped 
down in the past few of months.  One of them was your Board member Wenjing who 
stepped down as a committer for QTIP.  One of the reasons why TSC approval is 
desired for revoking committer status is to prevent PTLs from potentially 
acting in bad faith.  I don't know if there are any PTLs in OPNFV who would act 
in bad faith, but it's good to have checks & balances.  Is it really that 
difficult to send an email to the TSC mailing list and then come to the TSC 
meeting for 5 minutes to get an approval?

Others in the community are welcome to weigh in on this...

Thanks,

Ray

On Tue, Dec 13, 2016 at 9:10 PM, joehuang 
mailto:joehu...@huawei.com>> wrote:
Hello, Raymond,

My suggestion is to update the TSC Charter. Compared to OpenStack core 
reviewer/contributor maintenance, often feel that OPNFV governance brings lots 
of inconvenience:

For example, if one wants to submit a patch, he/she usually has to be a 
committer in OPNFV before he submit a patch. But in OpenStack, anyone is able 
to submit a patch, and core reviewers will make sure this patch should be 
approved or not. If one is nominated as committer to be a core reviewer, and 
pass the voting, then any other core reviewer can add the new one to core 
reviewer list, but in OPNFV, you have to submit a patch or ask help from 
help-desk.

And another example, I seldom find that there is a stepping down notification 
in OPNFV mail-list from committer(yes, I saw some PTL stepping down 
notification), it seems not the fashion in OPNFV. But in OpenStack, a core 
reviewer is quite important role in code review, if he is not able to do the 
core reviewer responsibility, he will send a notification to the OpenStack 
mail-list.

I really don't know the reason why when we find some committer is inactive in 
the past 6 months, we need the approve from TSC?

Best Regards
Chaoyi Huang (joehuang)

From: Raymond Paik [rp...@linuxfoundation.org<mailto:rp...@linuxfoundation.org>]
Sent: 14 December 2016 12:43
To: joehuang
Cc: opnfv-tech-discuss
Subject: Re: [opnfv-tech-discuss] committer list maintainance

Joe,

If there's an inactive committer (for more than 6 months) and the PTL is not 
able to reach that committer for whatever reason, the PTL needs to make a 
request to the TSC to revoke the committer status.  The PTL should not do this 
unilaterally.

Please see the 8th paragraph in the Section 8 of the TSC Charter 
(https://www.opnfv.org/developers/technical-project-governance/tsc-charter)...

Thanks,

Ray

On Tue, Dec 13, 2016 at 6:18 PM, joehuang 
mailto:joehu...@huawei.com>> wrote:
Hello,

In each project's wiki page, we often list committers and contributors, as 
OPNFV's ongoing development, som

[opnfv-tech-discuss] [multisite]Weekly meeting of Dec.15

Hello, team,

Agenda of Dec.15 2016

* Kingbird feature development
* mutli-site deployment
* Revisit Geographical Redundancy
* Open discussion

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] committer list maintainance

In OPNFV we "assume bad faith"? This is not a good assumption.

The less meeting, the better, and usually a TSC meeting will be in the night or 
early morning for me to join. If even need to go to TSC meeting for 5 minutes 
for approval, I would prefer to retain the inactive committer there, just let 
it be.

Best Regards
Chaoyi Huang (joehuang)

From: Raymond Paik [rp...@linuxfoundation.org]
Sent: 14 December 2016 13:33
To: joehuang
Cc: opnfv-tech-discuss
Subject: Re: [opnfv-tech-discuss] committer list maintainance

Joe,

On the first point, I'm not sure why you are saying you need to be committer to 
submit a patch in OPNFV.  There are plenty of regular contributors who submit 
code/patches to OPNFV.  Let me know if I'm not understanding your point.

On your second point, I can recall a few committers who voluntarily stepped 
down in the past few of months.  One of them was your Board member Wenjing who 
stepped down as a committer for QTIP.  One of the reasons why TSC approval is 
desired for revoking committer status is to prevent PTLs from potentially 
acting in bad faith.  I don't know if there are any PTLs in OPNFV who would act 
in bad faith, but it's good to have checks & balances.  Is it really that 
difficult to send an email to the TSC mailing list and then come to the TSC 
meeting for 5 minutes to get an approval?

Others in the community are welcome to weigh in on this...

Thanks,

Ray

On Tue, Dec 13, 2016 at 9:10 PM, joehuang 
mailto:joehu...@huawei.com>> wrote:
Hello, Raymond,

My suggestion is to update the TSC Charter. Compared to OpenStack core 
reviewer/contributor maintenance, often feel that OPNFV governance brings lots 
of inconvenience:

For example, if one wants to submit a patch, he/she usually has to be a 
committer in OPNFV before he submit a patch. But in OpenStack, anyone is able 
to submit a patch, and core reviewers will make sure this patch should be 
approved or not. If one is nominated as committer to be a core reviewer, and 
pass the voting, then any other core reviewer can add the new one to core 
reviewer list, but in OPNFV, you have to submit a patch or ask help from 
help-desk.

And another example, I seldom find that there is a stepping down notification 
in OPNFV mail-list from committer(yes, I saw some PTL stepping down 
notification), it seems not the fashion in OPNFV. But in OpenStack, a core 
reviewer is quite important role in code review, if he is not able to do the 
core reviewer responsibility, he will send a notification to the OpenStack 
mail-list.

I really don't know the reason why when we find some committer is inactive in 
the past 6 months, we need the approve from TSC?

Best Regards
Chaoyi Huang (joehuang)

From: Raymond Paik [rp...@linuxfoundation.org<mailto:rp...@linuxfoundation.org>]
Sent: 14 December 2016 12:43
To: joehuang
Cc: opnfv-tech-discuss
Subject: Re: [opnfv-tech-discuss] committer list maintainance

Joe,

If there's an inactive committer (for more than 6 months) and the PTL is not 
able to reach that committer for whatever reason, the PTL needs to make a 
request to the TSC to revoke the committer status.  The PTL should not do this 
unilaterally.

Please see the 8th paragraph in the Section 8 of the TSC Charter 
(https://www.opnfv.org/developers/technical-project-governance/tsc-charter)...

Thanks,

Ray

On Tue, Dec 13, 2016 at 6:18 PM, joehuang 
mailto:joehu...@huawei.com>> wrote:
Hello,

In each project's wiki page, we often list committers and contributors, as 
OPNFV's ongoing development, some new committers come, some committers grow 
other interesting and put less focus on the old project.

I have one suggestion for the maintenance on committer list: for those who have 
shifted interest, for example, not shown in the weekly meeting and mail-list 
discussion ( all these could be found in the log) in the past 6 months, but 
they forget to send a stepping down notification in the mail-list, PTL should 
be able to move the committer to the contributor list by default, and update 
the list in the git repository too.

It's not good idea ( not polite too :-) ) to send mail to ask "hey, would you 
continue to contribute in the project, if not, I'll remove you from the 
committer list".

Best Regards
Chaoyi Huang (joehuang)

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss



___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] committer list maintainance

Hello, Raymond,

My suggestion is to update the TSC Charter. Compared to OpenStack core 
reviewer/contributor maintenance, often feel that OPNFV governance brings lots 
of inconvenience:

For example, if one wants to submit a patch, he/she usually has to be a 
committer in OPNFV before he submit a patch. But in OpenStack, anyone is able 
to submit a patch, and core reviewers will make sure this patch should be 
approved or not. If one is nominated as committer to be a core reviewer, and 
pass the voting, then any other core reviewer can add the new one to core 
reviewer list, but in OPNFV, you have to submit a patch or ask help from 
help-desk.

And another example, I seldom find that there is a stepping down notification 
in OPNFV mail-list from committer(yes, I saw some PTL stepping down 
notification), it seems not the fashion in OPNFV. But in OpenStack, a core 
reviewer is quite important role in code review, if he is not able to do the 
core reviewer responsibility, he will send a notification to the OpenStack 
mail-list.

I really don't know the reason why when we find some committer is inactive in 
the past 6 months, we need the approve from TSC?

Best Regards
Chaoyi Huang (joehuang)

From: Raymond Paik [rp...@linuxfoundation.org]
Sent: 14 December 2016 12:43
To: joehuang
Cc: opnfv-tech-discuss
Subject: Re: [opnfv-tech-discuss] committer list maintainance

Joe,

If there's an inactive committer (for more than 6 months) and the PTL is not 
able to reach that committer for whatever reason, the PTL needs to make a 
request to the TSC to revoke the committer status.  The PTL should not do this 
unilaterally.

Please see the 8th paragraph in the Section 8 of the TSC Charter 
(https://www.opnfv.org/developers/technical-project-governance/tsc-charter)...

Thanks,

Ray

On Tue, Dec 13, 2016 at 6:18 PM, joehuang 
mailto:joehu...@huawei.com>> wrote:
Hello,

In each project's wiki page, we often list committers and contributors, as 
OPNFV's ongoing development, some new committers come, some committers grow 
other interesting and put less focus on the old project.

I have one suggestion for the maintenance on committer list: for those who have 
shifted interest, for example, not shown in the weekly meeting and mail-list 
discussion ( all these could be found in the log) in the past 6 months, but 
they forget to send a stepping down notification in the mail-list, PTL should 
be able to move the committer to the contributor list by default, and update 
the list in the git repository too.

It's not good idea ( not polite too :-) ) to send mail to ask "hey, would you 
continue to contribute in the project, if not, I'll remove you from the 
committer list".

Best Regards
Chaoyi Huang (joehuang)

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] committer list maintainance

Hello,

In each project's wiki page, we often list committers and contributors, as 
OPNFV's ongoing development, some new committers come, some committers grow 
other interesting and put less focus on the old project.

I have one suggestion for the maintenance on committer list: for those who have 
shifted interest, for example, not shown in the weekly meeting and mail-list 
discussion ( all these could be found in the log) in the past 6 months, but 
they forget to send a stepping down notification in the mail-list, PTL should 
be able to move the committer to the contributor list by default, and update 
the list in the git repository too.

It's not good idea ( not polite too :-) ) to send mail to ask "hey, would you 
continue to contribute in the project, if not, I'll remove you from the 
committer list".

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [multisite] update some related wiki pages