[opnfv-tech-discuss] [opnfv-tsc]Notice of intent to participate in OPNFV Danube release(Multisite Project)

[joehuang]

Greetings,
In accordance with the procedure outlined 
here:https://wiki.opnfv.org/display/DEV/Project+Inclusion+in+OPNFV+Release

I am notifying the OPNFV TSC of the intention of the multisite project to 
participate in the OPNFV Danube 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

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

[joehuang]

Hello, Ashish,

Thank you for the BP and doc, see comments in the doc.

Best Regards
Chaoyi Huang (joehuang)

From: Ashish Singh7 [ashish.sin...@tcs.com]
Sent: 26 September 2016 18:28
To: joehuang
Cc: Ashish singh; caizhiyuan (A); Dimitri Mazmanov; Meimei; opnfv-tech-discuss; 
Sama, Malla Reddy; Zhipeng Huang
Subject: RE: [opnfv-tech-discuss][multisite] Secgroup syncing Approach

Hi All,

I have registered a blueprint on "Resouce Syncing" and tied with a supporting 
document.

Blueprint:
https://blueprints.launchpad.net/kingbird/+spec/resource-syncing

Google Docs link
https://docs.google.com/document/d/1N6HFAFUT5BbEp1wbnYjgaKdOlyJanwkXccv-_1zsVQc/edit?usp=sharing


Let us use this to discuss the feature and finalize it.

Regards
Ashish Singh
Tata Consultancy Services
Cell:- 9030419618
Mailto: ashish.sin...@tcs.com
Website: http://www.tcs.com

Experience certainty.IT Services
   Business Solutions
   Consulting





From:joehuang 
To:Ashish singh , opnfv-tech-discuss 
, "caizhiyuan (A)" 
, Meimei , "Sama, Malla Reddy" 
, Zhipeng Huang , "Dimitri 
Mazmanov" , Ashish Singh7 
Date:09/21/2016 02:23 PM
Subject:RE: [opnfv-tech-discuss][multisite] Secgroup syncing Approach




Hello team,

Last year, use case 4 was discussed, some network related requirements were 
identified: 
https://etherpad.opnfv.org/p/multisite_centralized_servic

  *   global view for tenant level IP address / mac address space management
If a tenant has networks in multiple region, and these networks are routable 
(for example, connected with VPN), then, IP address may be duplicated. Need a 
global view for IP address space management
 *   If IP v4 used, this issue needs to be considered. For IPv6, it should 
not be a problem. IR - disagree with this statement. This requirement is 
important not just for prevention of duplicate address.
For security and other reasons it's important to know which IP Addresses (IPv4 
and IPv6) are used in which region.
Can we also extend such requirement to MAC address tracking?
Can we also extend such requirement to mapping for floating and public IP 
Addresses
  *   A service to clone security groups across regions
No appropriate service to security groups across multiple region if the tenant 
has resources distributed, has to set the security groups in different region 
manually.

And during the discussion thread with netready, one more issue identified 
http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2016-July/011499.html:

  *VxLAN pool cross site management for VxLAN segmentation allocation

All these issues needs to be addressed, we can discuss them together.

Tricircle( now Tricircle team is working on the cleaning to make Tricircle 
dedicated for networking automation across Neutron, mentioned below) could be 
the reference, the design blueprint has just been updated for your reference: 
https://docs.google.com/document/d/1zcxwl8xMEpxVCqLTce2-dUOtB-ObmzJTbV1uSQ6qTsY/,
 local network and shared VLAN network and L3 has been implemented in Newton 
release. Of course, in NFV area, L2 networking should be enough in most 
scenario.

And the spec for Tricircle Local Neutron Plugin is in review: 
https://review.openstack.org/#/c/368529/

Best Regards
Chaoyi Huang (joehuang)


From: joehuang
Sent: 09 September 2016 16:59
To: Ashish singh; opnfv-tech-discuss; caizhiyuan (A); Meimei; Sama, Malla 
Reddy; Zhipeng Huang; Dimitri Mazmanov; Ashish Singh7
Subject: RE: [opnfv-tech-discuss][multisite] Secgroup syncing Approach

Hello,  Ashish,

I think sync itself (if excluding the remote sec-group) is not complex, the 
complexity is to ensure the rules set in different region of Neutron will not 
conflict with each other. Otherwise, it'll become mess.

So I agree with you "We must use neutron to perform all our operations as with 
neutron we have total control over it." (Is my understanding correct?)

That's the way of Tricircle(please forgive me to explain a little: Tricircle 
now is only a project about networking automation across Neutron. And the 
Nova/Cinder API-Gateway part will be moved to Trio2o, a new created project: 
https://docs.google.com/presentation/d/1kpVo5rsL6p_rq9TvkuczjommJSsisDiKJiurbhaQg7E/edit),And
 the SEG sync has been implemented in the Tricircle, and we are now doing the 
tricircle splitting and cleaning.

If we implement seg sync in Kingbird, we have to write lots of duplicated code 
which has already done in 

Re: [opnfv-tech-discuss] Notice of intent to participate in OPNFV Danube release (Domino Project)

[David McBride]

Ulas,

Chris Price is requesting that PTLs wait until the TSC has voted to begin
the request to participate phase. We will be discussing tomorrow. Thanks.

David

On Monday, September 26, 2016, Ulas Kozat  wrote:

> Greetings,
>
>
>
> In accordance with the procedure outlined here: https://wiki.opnfv.org/
> display/DEV/Project+Inclusion+in+OPNFV+Release
>
>
>
> I am notifying the OPNFV TSC of the intention of the Domino project to
> participate in the OPNFV Danube release.
>
>
>
> Kind Regards,
>
>
>
> Ulas Kozat
>
> Domino PTL
>
>
>
>
>


-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 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] Notice of intent to participate in OPNFV Danube release (Qtip project)

[Yujun Zhang]

Greetings,

In accordance with the procedure outlined here:
https://wiki.opnfv.org/display/DEV/Project+Inclusion+in+OPNFV+Release

I am notifying the OPNFV TSC of the intention of the Qtip project to
participate in the OPNFV Danube release.

Kind Regards,

--

Yujun Zhang

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

[opnfv-tech-discuss] Notice of intent to participate in OPNFV Danube release (Parser Project)

[Zhipeng Huang]

Hi team,

Based upon the description of the tentative D release agenda, i'm hereby
announcing the intention of Parser to participate in the OPNFV Danube
release and our continuous efforts to make OPNFV better and easier for
general software developers.

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Prooduct Line
Huawei Technologies Co,. Ltd
Email: 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
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [polestar] Polestar Bellevue 9/29 noon-3pm room 407/408

[Ulrich Kleber]

Hi,
I am sorry, I cannot call-in to the Polestar meeting this Thursday. I am in a 
plane back from China at that time.
Cheers,
Uli

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Margaret Chiosi
Sent: Tuesday, 27 September, 2016 02:51
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [polestar] Polestar Bellevue 9/29 noon-3pm room 
407/408



--
Margaret Chiosi

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

[opnfv-tech-discuss] Notice of intent to participate in OPNFV Danube release (Domino Project)

[Ulas Kozat]

Greetings,

In accordance with the procedure outlined here: 
https://wiki.opnfv.org/display/DEV/Project+Inclusion+in+OPNFV+Release

I am notifying the OPNFV TSC of the intention of the Domino project to 
participate in the OPNFV Danube release.

Kind Regards,

Ulas Kozat
Domino PTL


___
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 Packaging CI

[Leif Madsen]

On Sun, Sep 25, 2016 at 01:19:21PM +, Alexandru Avadanii wrote:
> Hi, Luke,
> My experience so far included mostly DEB packages, which fell in 3 categories 
> for Armband:
> 
> -  Backported from newer distro (lots of Ubuntu Xenial arm64 DEBs 
> backported to Trusty)
> 
> -  Patched until upstream pulls our fixes (lshw is a good example, 
> it’s broken in all arm64 Ubuntus  - all distros)
> 
> -  Divergent functionality (we roll our own grub2, based on an Ubuntu 
> pacakge, but with added patches from Fedora and OpenSUSE – it’s hard to fiind 
> a grub2 package that satifies all conditions for integrating with our Cobbler 
> integration approach)
> 
> As for RPMs, we built only 2 custom packages, which I’m sure won’t be 
> upstreamed soon:
> 
> -  qemu-user-static for CentOS7 (implied building some static libs as 
> well, including libc), which is used by Fuel to cross-build images (e.g. 
> arm64 chroots on a x86 machine);
> 
> -  cobbler-grub-aarch64 (contains a single EFI-compatible arm64 
> binary of grub2-efi-arm64 standalone, used by cobbler as the netloader of 
> choice for Armband)
> 
> In my opinion, handlng the above by hand or using obscure external procedures 
> (most Fuel plugins build some DEBs and/or RPMs, each in a different way) is 
> prone to error
> and code duplication over time.
> 
> Also, and maybe I should have started with this, consider the case where the 
> ISO build process is tied to x86 (like Fuel currently is), and the artifacts 
> are expected to contain
> packages for different architectures (AArch64?), which cannot be locally 
> built [easily], in which case fetching some precompiled packages from an 
> OPNFV public repo would be nice.

Do you have a particular method in mind here? I think my biggest
issue would be around building yet another system to build packages. For
example, for RPMs, it would be almost trivial to employ the COPR build
system and host any custom packages in that namespace.

What I would hate to see, would be a set of custom scripts or
applications to build packages, and then host them within the OPNFV
namespace, along with having to maintain that whole pipeline.

I assume there is some sort of DEB equivalent of COPR where those
packages could be hosted, and packages build on a remote service?

-- 
Leif Madsen | Partner Engineer - NFV & CI
NFV Partner Engineering
Red Hat
GPG: (D670F846) BEE0 336E 5406 42BA 6194 6831 B38A 291E D670 F846
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [tech-discuss][fuel] Updated Wiki for the Danube release

[Jonas Bjurel]

I have updated the Fuel@OPNFV WIKI with an placeholder for the Danube release, 
including a few links to etherpads related to what we want to do for the 
release - feel free to fill-in!
BR/Jonas
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii

[Alexandru Avadanii]

Thank you, all!


From: Jonas Bjurel [mailto:jonas.bju...@ericsson.com]
Sent: Monday, September 26, 2016 8:14 PM
To: Gregory Elkinbard; Stefan Berg K
Cc: Daniel Smith; opnfv-tech-discuss@lists.opnfv.org; Alexandru Avadanii
Subject: RE: [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii

This means that we have a majority for Alexandru as an Fuel@OPNFV committer.
I will proceed with needed paper works.
Welcome Alexandru.
BR/Jonas

From: Gregory Elkinbard [mailto:gelkinb...@mirantis.com]
Sent: Friday, September 23, 2016 8:24 PM
To: Stefan Berg K 
>
Cc: Daniel Smith >; 
Jonas Bjurel >; 
opnfv-tech-discuss@lists.opnfv.org; 
Alexandru Avadanii 
>
Subject: Re: [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii

+1

On Fri, Sep 23, 2016 at 3:20 AM, Stefan Berg K 
> wrote:

+1


Från: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 
>
 för Daniel Smith >
Skickat: den 23 september 2016 08:52:47
Till: Jonas Bjurel; 
opnfv-tech-discuss@lists.opnfv.org; 
Alexandru Avadanii
Ämne: Re: [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii

+1

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org]
 On Behalf Of Jonas Bjurel
Sent: Thursday, September 22, 2016 2:36 PM
To: 
opnfv-tech-discuss@lists.opnfv.org; 
Alexandru Avadanii 
>
Subject: [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii

I would like to nominate Alexandru Avadanii (ENEA) as a committer in 
Fuel@OPNFV, I have been in contact
with Alexandru and his willing to take on the role.
Alexandru is one of the main architects/committers in Armband which is a port 
of Fuel@OPNFV to the ARM
Architecture, he has also been very active in Fuel@OPNFV.
This month, Alexandru is the OPNFV committer with the most commits.

OPNFV committers, reply to this mail with your vote (-1, 0, +1).

BR/Jonas

___
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] [fuel] Nominating of Alexandru Avadanii

[Jonas Bjurel]

This means that we have a majority for Alexandru as an Fuel@OPNFV committer.
I will proceed with needed paper works.
Welcome Alexandru.
BR/Jonas

From: Gregory Elkinbard [mailto:gelkinb...@mirantis.com]
Sent: Friday, September 23, 2016 8:24 PM
To: Stefan Berg K 
Cc: Daniel Smith ; Jonas Bjurel 
; opnfv-tech-discuss@lists.opnfv.org; Alexandru 
Avadanii 
Subject: Re: [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii

+1

On Fri, Sep 23, 2016 at 3:20 AM, Stefan Berg K 
> wrote:

+1


Från: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 
>
 för Daniel Smith >
Skickat: den 23 september 2016 08:52:47
Till: Jonas Bjurel; 
opnfv-tech-discuss@lists.opnfv.org; 
Alexandru Avadanii
Ämne: Re: [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii

+1

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org]
 On Behalf Of Jonas Bjurel
Sent: Thursday, September 22, 2016 2:36 PM
To: 
opnfv-tech-discuss@lists.opnfv.org; 
Alexandru Avadanii 
>
Subject: [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii

I would like to nominate Alexandru Avadanii (ENEA) as a committer in 
Fuel@OPNFV, I have been in contact
with Alexandru and his willing to take on the role.
Alexandru is one of the main architects/committers in Armband which is a port 
of Fuel@OPNFV to the ARM
Architecture, he has also been very active in Fuel@OPNFV.
This month, Alexandru is the OPNFV committer with the most commits.

OPNFV committers, reply to this mail with your vote (-1, 0, +1).

BR/Jonas

___
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] [openstack-dev] OPNFV on Github

[HU, BIN]

+1 too, because it is a reasonable way and consistent with the practice of 
other communities, unless there is any legal issue as Heather guided.

BTW, in order for better preparation of  the discussion, there was a suggestion 
to move it to Oct 13. Hope it is ok for everyone who is interested in this 
topic.

Thanks
Bin

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Luke Hinds
Sent: Monday, September 26, 2016 3:49 AM
To: Yujun Zhang 
Cc: Scott Nicholas ; 
openstack-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [openstack-dev] OPNFV on Github

+1 read only is the way to do it, with the hook message pointing them over on 
how to contribute. I think they do the same with the kernel?

I originally got started this way (cloning openstack projects down from github 
and reading / learning the code). After that I learned gerrit and the openstack 
work flow.



On Mon, Sep 26, 2016 at 1:19 AM, Yujun Zhang 
> wrote:
The openstack repos on github seems to be read only. To make contribution, the 
developer will be guided to the gerrit system. See examples[1].

I would vote for a read-only mirror on Github.

[1] https://github.com/openstack/vitrage/pull/4

On Mon, Sep 26, 2016 at 3:10 AM Raymond Paik 
> wrote:
Luke,

"External" repos is something we want to have a discussion on in early/mid 
October (borrowing Bin's Thursday Technical Community Discussion mtg.)

In OpenStack, if someone contributes to the github repo, do some of those 
github contributions also get "moved" to the main OpenStack repo?  If yes, how 
is that done?  My understanding is that you also need a contributor agreement 
in OpenStack 
(https://ask.openstack.org/en/question/89871/does-the-company-need-to-be-a-member-of-the-foundation-in-order-for-employees-to-contribute-code-on-behalf-of-the-company/)

Thanks,

Ray

On Sun, Sep 25, 2016 at 9:54 AM, Luke Hinds 
> wrote:
Hi,

I am sure this might have already been discussed, if so apologies.

Is there any reason we don't mirror our repos to github (similar as happens 
with openstack).

I ask as it could encourage more developers to get involved by increasing 
exposure (especially for independents).

We already have an org in place https://github.com/opnfv

Regards,

Luke

--
Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 
77 45 63 98 84 | t: +44 12 52 36 2483

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

___
openstack-dev mailing list
openstack-...@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/openstack-dev



--
Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 
77 45 63 98 84 | t: +44 12 52 36 2483
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [releng] Nomination of Serena Feng as committer to Releng

[Fatih Degirmenci]

Hi Releng Committers.

I would like to nominate Serena Feng as committer to Releng.

She has been one of the most active Releng contributors during Colorado 
development phase. Apart from being the top contributor to Releng during June, 
she did lots of contributions to improve test result api and the dashboard and 
also fixed security group findings.
https://gerrit.opnfv.org/gerrit/#/q/owner:feng.xiaowei%2540zte.com.cn+project:releng

Please cast your vote on Gerrit: https://gerrit.opnfv.org/gerrit/#/c/22437/

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