Re: [opencontrail-dev] We have a new name!!!

[Gasparakis, Joseph]

So beyond chemical and physical properties (which I agree, Paul’s comments were 
fascinating to me, too), when do we stop calling OpenContrail OpenContrail, and 
we start calling it Tangsten Fabric? Starting from now? Right after ONS? 
Sometime later on?

Thanks

Joseph

From: Dev [mailto:dev-boun...@lists.opencontrail.org] On Behalf Of Valentine 
Sinitsyn
Sent: Saturday, March 3, 2018 7:24 PM
To: CARVER, PAUL 
Cc: annou...@lists.opencontrail.org; dev@lists.opencontrail.org
Subject: Re: [opencontrail-dev] We have a new name!!!

Paul seems to have a strong background in Physics or Material Sciences. :)

Which is very welcome, as mine is also in Solid State Physics and Quantum 
Mechanics.

Valentine

On Mar 3, 2018 17:21, "CARVER, PAUL" > 
wrote:
You’re thinking of polycrystalline tungsten. This is tungsten FABRIC where the 
warp and weft of the fabric allude to the pure single-crystalline form 
(admittedly fabric isn’t body centered cubic, but the name is merely evocative) 
which retains its hardness but is more ductile and malleable. And when combined 
with OpenStack, Tungsten Fabric forms a superalloy 
https://en.wikipedia.org/wiki/Superalloy suitable for ultra-high performance 
applications such as gas turbines and the nozzles of rocket engines.

As with tungsten, Tungsten Fabric is best used in combination with other 
material where it lends it high melting point and tensile strength to the 
complementary properties of the weaker materials with which it is combined.

--
Paul Carver
VoIP: 732-545-7377
Cell: 908-803-1656
E: pcar...@att.com
Q Instant Message
It is difficult to make predictions. Especially about the future.


From: Dev 
[mailto:dev-boun...@lists.opencontrail.org]
 On Behalf Of Harshad Nakil
Sent: Friday, March 02, 2018 19:18
To: Gregory Elkinbard >
Cc: dev@lists.opencontrail.org; 
annou...@lists.opencontrail.org
Subject: Re: [opencontrail-dev] We have a new name!!!

Nice name, hard(inflexible)  and brittle :)

On Mar 2, 2018, at 3:27 PM, Gregory Elkinbard 
> wrote:

We have a name!

Based on input from the community and from trademark counsel, the selected name 
is Tungsten Fabric. We are working with the LF-N governance board to approve 
the project for induction as soon as possible, likely at ONS the last week in 
March.

Stay tuned as we finalize the new branding, website, and social channels for 
Tungsten Fabric, and thanks to everyone who has participated in getting the 
project ready for its migration into the LF-N.

Greg


___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org


___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] [TSC]Update on Edgar's replacement in the TSC

[Gasparakis, Joseph]

Hi all,

Last week I sent out an email calling for candidates to replace Edgar Magana 
who stepped down from the TSC recently.

Towards the end of last week it was brought to my attention that this was not 
necessary, and here is why:

During the 1st OpenContrail summit (aka Reboot) we put together a TSC WG with 
volunteers who were present in the room. With this working group we started 
putting together the processes, charters, role and responsibilities. Some of 
the members of that TSC WG stopped being active after a while, and some other 
members of the community became more active, which is normal for a newly formed 
community.

Right before the 2nd OpenContrail summit, we decided we should confirm who is 
still in the TSC the 5.0 release, and if there are volunteers willing to take 
the place of the TSC members who were not active anymore. At that point of 
time, we had exactly 5 people willing to participate in the OpenContrail TSC:

Joseph Gasparakis - Intel
Paul Carver - AT
Valentine Sinitsyn - Yandex
Masood Ul Amin - Aricent
Edgar Magana - Workday

Aniket Daptari from Juniper at that point of time had mentioned that someone 
from Juniper will also get volunteered, and Sukhdev Kapur started joining our 
TSC calls after a couple of weeks and he was actively contributing and 
connecting the TSC decisions with the Juniper Engineering teams and management, 
and everyone assumed Sukhdev was the volunteer that Aniket had mentioned 
without neglecting the fact that the number of TSC voting members now was 6, 
and not 5 as the charter describes.

Since then TSC calls kept happening and all the (few) decisions were really 
unanimous so we never had to do a proper voting and that clouded everyone's 
memory as to who is a voting member of the TSC and who is not (don't get 
confused by the "few" decisions, a lot of work happened since then, the 
splitting decisions were very few... ;-)).

Coming to last week and having Edgar stepping down probed me as chair to the 
TSC to announce the elections, but then, towards the end all the above started 
surfacing: it seemed like we were about to vote for a 6th member again.

To cut the long story short between some communication between me and the 
candidates for this election and during the TSC call today it was decided 
(unanimously) that we do not need elections since we do have 5 members now, and 
Sukhdev is in fact a voting member of the OpenContrail TSC, so we do not need 
to proceed with elections at this point of time.

In order to avoid the same mistake in the future, the names of the five voting 
TSC members are now published at the top of the Google doc of the TSC minutes 
(https://docs.google.com/document/d/1FIO30YiqDPcXkrJ-oFKPPBoJddHRiFo04T5KRFooT0k/edit#heading=h.btv2h83fc4fi).

We also updated the documents in Juniper/contrail-community-docs 
(https://github.com/Juniper/contrail-community-docs) : I encourage you to 
review and let me or any member of the TSC know if something is currently out 
of order.




For the record the following are the five voting members currently of the 
OpenContrail TSC:


*   Joseph Gasparakis  - Intel

*   Paul Carver - AT

*   Masood Amin - Aricent

*   Sukhdev Kapur  - Juniper

*   Valentin Sinitsyn - Yandex

Before I close this email I would like to thank everyone involved in this 
community and the TSC, and I wanted to let everyone know that for the next two 
Mondays (12/25 & 1/1) we won't have a TSC call. We will resume refreshed on 
Monday 1/8/2018.

Let me know if you have any questions, otherwise enjoy this festive season and 
looking forward to working with you again in 2018!
--
[intel-logo-small]
Joseph Gasparakis
Intel Corporation
Networking Platforms Group
Architecture Division



Regards,

Joseph

--
Joseph Gasparakis
NPG Architecture & Systems Engineering

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

Re: [opencontrail-dev] Call for candidates for the OpenContrail TSC

[Gasparakis, Joseph]

And one more detail to add:

Since the link is shareable to everyone and mistakes like overwriting each 
other's edits can happen (although unlikely), please Reply All to this email 
with a copy of your bio after you have added it in the document, and I will 
make sure the Google Doc has the right content. On Friday 12/15 pm I will make 
the document read-only.

Thanks,

Joseph

From: Dev [mailto:dev-boun...@lists.opencontrail.org] On Behalf Of Gasparakis, 
Joseph
Sent: Tuesday, December 12, 2017 12:45 PM
To: dev@lists.opencontrail.org
Subject: [opencontrail-dev] Call for candidates for the OpenContrail TSC

Hi all,

Since Edgar Magana stepped down from his role in the TSC as a voting member, we 
have an opening to cover his position. If you want to be considered for the 
voting process please add a quick bio (one or two paragraphs) in this document 
by Friday 12/15 17:00 PST:

https://docs.google.com/document/d/1ERO6v2N84a4z-O_96Dv54eoMPvCaHfMn8CL6_Hob2Fs/edit?usp=sharing

As discussed in the last TSC call, next week the voting members of the 
Governance, TSC, ARB and Infrastructure WGs will be voting for Edgar's 
replacement, but just to clarify: this call for candidates is open to *all* 
members of the community.

Regards,

Joseph

--
[intel-logo-small]
Joseph Gasparakis
Intel Corporation
Networking Platforms Group
Architecture Division

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] Call for candidates for the OpenContrail TSC

[Gasparakis, Joseph]

Hi all,

Since Edgar Magana stepped down from his role in the TSC as a voting member, we 
have an opening to cover his position. If you want to be considered for the 
voting process please add a quick bio (one or two paragraphs) in this document 
by Friday 12/15 17:00 PST:

https://docs.google.com/document/d/1ERO6v2N84a4z-O_96Dv54eoMPvCaHfMn8CL6_Hob2Fs/edit?usp=sharing

As discussed in the last TSC call, next week the voting members of the 
Governance, TSC, ARB and Infrastructure WGs will be voting for Edgar's 
replacement, but just to clarify: this call for candidates is open to *all* 
members of the community.

Regards,

Joseph

--
[intel-logo-small]
Joseph Gasparakis
Intel Corporation
Networking Platforms Group
Architecture Division

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] [TSC] TSC calls

[Gasparakis, Joseph]

Hi all,

This is my regular broadcast to say that anyone interested in joining the 
Technical Steering Committee's call which is scheduled on Mondays at 12 noon 
PST need to let me know and I will add them to the invitee's list.

Also if you wish not to participate anymore please let me know and I will 
remove you from the list.

Regards,

Joseph

--
[intel-logo-small]
Joseph Gasparakis
Intel Corporation
Networking Platforms Group
Architecture Division

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

Re: [opencontrail-dev] We need a new name

[Gasparakis, Joseph]

And I think I changed my mind about buying the domain… ☺

From: Dev [mailto:dev-boun...@lists.opencontrail.org] On Behalf Of Randy Bias
Sent: Thursday, November 30, 2017 12:54 PM
To: EXT - dun...@bluechiptek.com 
Cc: dev@lists.opencontrail.org
Subject: Re: [opencontrail-dev] We need a new name

I think that’s a pretty legitimate concern.

--Randy



*** Sent from mobile, pls forgive tpyoes ***

On Nov 30, 2017, at 12:41, Dave Unger 
> wrote:
I would be concerned about “dikt” being an English homophone of “dicked” 
meaning insulted or mistreated. The potential negative connotation jumped out 
at me pretty immediately.

-DaveU

From: Randy Bias [mailto:rb...@juniper.net]
Sent: Thursday, November 30, 2017 11:32 AM
To: Abhijit Gadgil >; 
Dave Unger >
Cc: dev@lists.opencontrail.org
Subject: Re: [opencontrail-dev] We need a new name

I like this intention (riffing off of kubernetes), but elenktis seems like a 
mouthful.

What about “networking” or similar in Greek?

…

I’ve registered hikoki.io and dikt.io (diktyo 
== network in greek), just in case.

So I’m formally nominating “dikt.io”; it’s good, not great, but 
it’s short and sweet.


Best,


--Randy

Vice President, Technology & Strategy, Cloud Software
Juniper Networks
+1 (415) 787-2253 [Google Voice]
ASSISTANT: Stephanie Concepcion, 
sconcepc...@juniper.net
TWITTER: @randybias
LINKEDIN: linkedin.com/in/randybias



IMPORTANT NOTICE: This message is for the designated recipient only and may 
contain privileged, proprietary, or otherwise private information. If you have 
received this message in error, please notify the sender immediately and delete 
the original message. All pricing and discount information provided in this 
message is for the intended recipient only. All quotes are considered 
proprietary information of Blue Chip Tek, Inc. and are not to be shared outside 
of the recipient’s company. If pricing or discounts are shared outside of the 
recipient’s company pricing may not be honored.

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

Re: [opencontrail-dev] We need a new name

[Gasparakis, Joseph]

Hi all,

I am a Greek native speaker, sorry I was quiet, other than Greek native speaker 
I’ve also been sick so had narrow bandwidth ☹

From Greek native speaker’s perspective the name dikt.io couldn’t be a better 
choice ☺ It incorporates playfully Diktyo (=Network as Randy mentioned) and 
I/O… So I am all for it. Not totally sure however how it resonates with 
non-native Greek speakers which I am guessing will be the majority of the 
users/contributors ☺

Regards,

Joseph

PS: If we don’t go for dikt.io I am now seriously considering buying the 
domain! ☺

From: Dev [mailto:dev-boun...@lists.opencontrail.org] On Behalf Of Randy Bias
Sent: Thursday, November 30, 2017 11:32 AM
To: Abhijit Gadgil ; EXT - dun...@bluechiptek.com 

Cc: dev@lists.opencontrail.org
Subject: Re: [opencontrail-dev] We need a new name

I like this intention (riffing off of kubernetes), but elenktis seems like a 
mouthful.

What about “networking” or similar in Greek?

…

I’ve registered hikoki.io and dikt.io (diktyo == network in greek), just in 
case.

So I’m formally nominating “dikt.io”; it’s good, not great, but it’s short and 
sweet.


Best,


--Randy

Vice President, Technology & Strategy, Cloud Software
Juniper Networks
+1 (415) 787-2253 [Google Voice]
ASSISTANT: Stephanie Concepcion, 
sconcepc...@juniper.net
TWITTER: @randybias
LINKEDIN: linkedin.com/in/randybias


From: Dev 
> 
on behalf of Abhijit Gadgil 
>
Date: Wednesday, November 29, 2017 at 9:03 AM
To: "EXT - dun...@bluechiptek.com" 
>
Cc: "dev@lists.opencontrail.org" 
>
Subject: Re: [opencontrail-dev] We need a new name

elenktis (any native greek speakers here?) Greek word for "Controller" - 
following inspiration from kubernetes -
Does not suffer from 'OpenFoo names'.
-abhijit

On Wed, Nov 29, 2017 at 10:21 PM, Dave Unger 
> wrote:

I suggest "sdnctrl". If I was a sysadmin Googling for an alternate SDN control 
plane, that's pretty close to where I would start. And I've always assumed 
contrail was chosen partially because it sounds similar to control.



-DaveU


From: Dev 
[dev-boun...@lists.opencontrail.org] 
on behalf of Gregory Elkinbard 
[gelkinb...@juniper.net]
Sent: Tuesday, November 28, 2017 12:19 PM
To: dev@lists.opencontrail.org
Subject: Re: [opencontrail-dev] We need a new name
Hey folks,
As you get your creative hats on, please remember that the name will serve to 
advertise our community and attract new users. Ideally, we would want to evoke 
what we do in the name, such as network and security.

Thanks
Greg


From: Dev 
> 
on behalf of Gregory Elkinbard 
>
Date: Tuesday, November 28, 2017 at 12:03 PM
To: "dev@lists.opencontrail.org" 
>
Subject: [opencontrail-dev] We need a new name

Dear Community Members.
Linux Foundation is unable to accept OpenContrail as a trademark to the project 
as Juniper has Contrail product line.
We need to select a different name. Legal team has offered OpenVTrail. But I am 
hoping that folks can come up with something cooler.

Please send in your name proposals, by Dec 4th and lets discuss it during the 
summit.
Requirements for the name. Full name must be unique and not currently 
trademarked.
If the name is a composite, no part of the composite can be trademarked by 
another entity.

Linux foundation can temporarily accept us under the OpenContrail name, but 
will require a new name after a short transition period.

Thanks
Greg



IMPORTANT NOTICE: This message is for the designated recipient only and may 
contain privileged, proprietary, or otherwise private information. If you have 
received this message in error, please notify the sender immediately and delete 
the original message. All pricing and discount information provided in this 
message is for the intended recipient only. All quotes are considered 
proprietary information of Blue Chip Tek, Inc. and are not to be shared outside 
of the recipient’s company. If pricing or discounts are shared outside of the 
recipient’s company pricing may not be honored.


___
Dev mailing list
Dev@lists.opencontrail.org

Re: [opencontrail-dev] Proposed OpenContrail @ KubeCon agenda

[Gasparakis, Joseph]

Sure, we can discuss but more importantly it is better to put together a 
taskforce to get this done:


-  Edward said they have some fixes

-  Valentine during the TSC call also mentioned that probably they can 
contribute their process to build and deploy

-  Paul with the rest of Infrastructure group are also putting the 
CI/CD in place

-  I have mentioned in the past have a way to build OpenContrail (but 
not deploy)

Combining all the above we should be able to fix the issue sooner rather than 
later. I can pull the above people together and start working on this. Output 
will be documentation (worse case) or chef/pupper/ansible manifests at best…

And Yi: I think you are recently started catching with the community up. This 
issue has been identified long ago, we all know about it, people (especially 
Infrastructure committee and other outside) work on a fix. It doesn’t happen 
overnight and it is up to all of us to put “our house in order”. So let’s see 
how we can do our share moving forward ;-)

So, any volunteers to put some sort of OpenContrail installation together 
(single or multi node) to start with please let us know and I will pull 
everyone together next week.

Regards,

Joseph



From: Sukhdev Kapur [mailto:sukh...@juniper.net]
Sent: Wednesday, November 22, 2017 4:58 PM
To: Edward Ting <lti...@lenovo.com>; Yang, Yi Y <yi.y.y...@intel.com>; Gregory 
Elkinbard <gelkinb...@juniper.net>; CARVER, PAUL <pc2...@att.com>; Gasparakis, 
Joseph <joseph.gaspara...@intel.com>; dev@lists.opencontrail.org; Rudra Rugge 
<rru...@juniper.net>
Subject: Re: Proposed OpenContrail @ KubeCon agenda

Edward, Yi, et. all,

I am the newest member of the OpenContrail team and have had my share of issues 
trying to install OpenContrail. Therefore, I do appreciate what you are saying. 
I am all for documenting the issues and solutions so that, as a community, we 
can all leverage from each other’s pain points and solutions.
Having said that, why don’t we come up with a place “OpenContrail User Central” 
(or something like that) where we can start to post these kinds of 
solutions/fixes so that other can leverage from each other’s work.

Joseph, shall we discuss this in our next TSC meeting?

-Sukhdev




From: Edward Ting <lti...@lenovo.com<mailto:lti...@lenovo.com>>
Date: Wednesday, November 22, 2017 at 4:43 PM
To: "Yang, Yi Y" <yi.y.y...@intel.com<mailto:yi.y.y...@intel.com>>, Gregory 
Elkinbard <gelkinb...@juniper.net<mailto:gelkinb...@juniper.net>>, "CARVER, 
PAUL" <pc2...@att.com<mailto:pc2...@att.com>>, Sukhdev Kapur 
<sukh...@juniper.net<mailto:sukh...@juniper.net>>, "Gasparakis, Joseph" 
<joseph.gaspara...@intel.com<mailto:joseph.gaspara...@intel.com>>, 
"dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>" 
<dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>>, Rudra Rugge 
<rru...@juniper.net<mailto:rru...@juniper.net>>
Subject: RE: Proposed OpenContrail @ KubeCon agenda


We have tried contrail-installer (4 different developers) on Ubuntu 16.04 with 
DevStack Ocata (Mitaka is no longer available). It can bring all component 
‘Active’ after try-and-error fixing broken steps, but not fully functional.

We are more than happy to contribute our ‘fixes’ to where we are and work with 
the community together to complete the last missing pieces.

Thanks,

Edward

From: Dev [mailto:dev-boun...@lists.opencontrail.org] On Behalf Of Yang, Yi Y
Sent: Wednesday, November 22, 2017 4:33 PM
To: Gregory Elkinbard; CARVER, PAUL; Sukhdev Kapur; Gasparakis, Joseph; 
dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>; Rudra Rugge
Subject: Re: [opencontrail-dev] Proposed OpenContrail @ KubeCon agenda

Understood, but as an open source community, you Juniper guys are to learn how 
to leverage community resources, I believe many people can contribute to these 
documents or 
https://github.com/Juniper/contrail-installer<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Juniper_contrail-2Dinstaller=DwMGaQ=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI=Y9QaEJ2cs4La8kQDqQ-N2rBJnxrPyFqAIO8efLhSqZ0=UENkYoX6DDteZmRSmfgQUxmxxbuNE1Au8qeoMu_YRiw=zRPvHM2gVJjlmogAMa1v0oPnc_fuoGVVutAlBgTyh0g=>
 if someone of you can provide necessary and quick response about the issues 
developers found. You must make sure people can install and use it first if you 
hope to have more developers and users.

From: Gregory Elkinbard [mailto:gelkinb...@juniper.net]
Sent: Thursday, November 23, 2017 8:23 AM
To: Yang, Yi Y <yi.y.y...@intel.com<mailto:yi.y.y...@intel.com>>; CARVER, PAUL 
<pc2...@att.com<mailto:pc2...@att.com>>; Sukhdev Kapur 
<sukh...@juniper.net<mailto:sukh...@juniper.net>>; Gasparakis, Joseph 
<joseph.gaspara...@intel.com<mailto:joseph.ga

Re: [opencontrail-dev] Proposed OpenContrail @ KubeCon agenda

[Gasparakis, Joseph]

Hence my question ☺

Since we do not have CI/CD in place yet (but even if we had it) if I was to 
develop I would need to have a dev environment where I can easily compile and 
deploy my changes in a single node setup (if I am not mistaken 
contrail-installer does this, but not sure if it is currently fuctional), 
possibly in a VM to make sure what I developed works at small scale before I 
send my patches out.

So it would be great if we could get the steps to do something like that in 
advance (aka pre-work), and then on the day go through few slides on the 
architecture followed by a lot of coding and questions. I am thinking that if 
we don’t have a dev environment we might be limited.

Thanks

Joseph

From: CARVER, PAUL [mailto:pc2...@att.com]
Sent: Wednesday, November 22, 2017 2:21 PM
To: Sukhdev Kapur <sukh...@juniper.net>; Gregory Elkinbard 
<gelkinb...@juniper.net>; Gasparakis, Joseph <joseph.gaspara...@intel.com>; 
dev@lists.opencontrail.org; Rudra Rugge <rru...@juniper.net>
Subject: RE: Proposed OpenContrail @ KubeCon agenda

The more questions the better. The ideal would be no slides and all questions, 
answers and discussions.

No formal pre-work is required, but I would encourage anyone who is 
contemplating any Contrail development to spend a little time thinking about 
what you think your development steps will be and make a list of anything that 
you’re unsure about. The goal of this session is to get developers up to speed, 
so the more specific examples we have of either obstacles or simply things that 
ought to be covered in a getting started guide but aren’t will be helpful.

I’m hoping to create the beginnings of a developer FAQ based on what questions 
people have.

--
Paul Carver
VoIP: 732-545-7377
Cell: 908-803-1656
E: pcar...@att.com<mailto:pcar...@att.com>
Q Instant Message
It is difficult to make predictions. Especially about the future.


From: Dev [mailto:dev-boun...@lists.opencontrail.org] On Behalf Of Sukhdev Kapur
Sent: Wednesday, November 22, 2017 17:09
To: Gregory Elkinbard <gelkinb...@juniper.net<mailto:gelkinb...@juniper.net>>; 
Gasparakis, Joseph 
<joseph.gaspara...@intel.com<mailto:joseph.gaspara...@intel.com>>; 
dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>; Rudra Rugge 
<rru...@juniper.net<mailto:rru...@juniper.net>>
Subject: Re: [opencontrail-dev] Proposed OpenContrail @ KubeCon agenda

Joesph, Greg:

There is not pre-work required. Just come, bring an attitude to learn things, 
and bring your questions.
We have few speakers identified to cover this 4-hour session.

Rudra and I will cover the Overall architecture
We have additional speakers to cover Controller, analytics, and testing areas.

I am working on getting some slides that we will use to cover the architecture.

HTH
-Sukhdev


From: Gregory Elkinbard <gelkinb...@juniper.net<mailto:gelkinb...@juniper.net>>
Date: Wednesday, November 22, 2017 at 1:59 PM
To: "Gasparakis, Joseph" 
<joseph.gaspara...@intel.com<mailto:joseph.gaspara...@intel.com>>, 
"dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>" 
<dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>>, Rudra Rugge 
<rru...@juniper.net<mailto:rru...@juniper.net>>, Sukhdev Kapur 
<sukh...@juniper.net<mailto:sukh...@juniper.net>>
Subject: Re: Proposed OpenContrail @ KubeCon agenda

Rudra, Sukhdev,
You own this session. Can you please respond.
Thanks
Greg


From: "Gasparakis, Joseph" 
<joseph.gaspara...@intel.com<mailto:joseph.gaspara...@intel.com>>
Date: Wednesday, November 22, 2017 at 1:49 PM
To: Gregory Elkinbard <gelkinb...@juniper.net<mailto:gelkinb...@juniper.net>>, 
"dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>" 
<dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>>
Subject: RE: Proposed OpenContrail @ KubeCon agenda

Greg,

For Dec 6th 1:00- 5:00 Developer Track: Is there any pre-work required?

Thanks

Joseph

From: Dev [mailto:dev-boun...@lists.opencontrail.org] On Behalf Of Gregory 
Elkinbard
Sent: Tuesday, November 21, 2017 11:32 AM
To: dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>
Subject: [opencontrail-dev] Proposed OpenContrail @ KubeCon agenda

https://docs.google.com/document/d/1YA0X1GYcAMhcXAhjdSnq_WWmhQKV6pHwkK3PSu9V3e4/edit?usp=sharing<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1YA0X1GYcAMhcXAhjdSnq-5FWWmhQKV6pHwkK3PSu9V3e4_edit-3Fusp-3Dsharing=DwMGaQ=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI=VQrMBvKeploIeBocya36pOwODBVDvmbjFqFgowqJuhs=vEKkTAAAOb3NmoHBAXY0AWuX0eVFStYoTOP-OrZc-8I=3wijA4l3khom5fOwRia9ZvVZy6jmKoDcDFeWzaW3mfE=>
___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

Re: [opencontrail-dev] Stepping Down TSC and Advisory Board

[Gasparakis, Joseph]

Good luck Edgar!

From: Edgar Magana [mailto:edgar.mag...@workday.com]
Sent: Tuesday, November 21, 2017 2:01 PM
To: dev@lists.opencontrail.org; Gregory Elkinbard <gelkinb...@juniper.net>; 
Gasparakis, Joseph <joseph.gaspara...@intel.com>
Subject: [opencontrail-dev] Stepping Down TSC and Advisory Board

Dear Community,

It has been a pleasure to be part of the OpenContrail community for the last 
three years, I would like to continue my involvement but I am about to start 
other projects and I won’t have the bandwidth to make any meaningful 
contributions in OpenContrail.  I wish you the best and I am looking forward to 
working with you all any time soon. My future work is around Public Cloud and 
Kubernetes. So, I am sure they will be some collaborations.

Thanks,

Edgar Magana, PhD
Cloud Operations Architect
Workday, Inc.
___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] Proposed blueprint for OpenContrail 5.0

[Gasparakis, Joseph]

Hi all,

I have created a new blueprint in the OpenContrail launchpad: 
https://blueprints.launchpad.net/opencontrail/+spec/vrouter-dpdk-18.02

Based on the guidelines I am supposed to upload the spec file in 
https://github.com/OpenContrail but since it is not open yet I am attaching for 
the record the spec file in this email.

Regards,

Joseph
--
[intel-logo-small]
Joseph Gasparakis
Intel Corporation
Networking Platforms Group
Architecture Division



vrouter-dpdk-18.02-integration.md
Description: vrouter-dpdk-18.02-integration.md
___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

Re: [opencontrail-dev] New deadline on Blue Print submission for release 5.0

[Gasparakis, Joseph]

Hi Valentine,

Here are my suggestions, but I would like someone from Juniper to confirm this 
is ok:

1. About dev and testing commitment dates just call it out in the document. And 
then we will need to bring this up with the Infrastructure committee that can 
help add the two fields in the drop down
2. About the bug id, I remember in previous discussions in the TSC calls 
someone was saying that bug ids are either unique identifiers to bugs or 
blueprints. So it seems to me like you will need to create a bug id and refer 
to that for your BP.

I know the OpenStack summit is on today and it might be difficult but I am 
hoping someone from Juniper can verify or not.

Regards,

Joseph

-Original Message-
From: Valentine Sinitsyn [mailto:valentine.sinit...@gmail.com] 
Sent: Monday, November 6, 2017 8:35 AM
To: Gasparakis, Joseph <joseph.gaspara...@intel.com>; dev@lists.opencontrail.org
Subject: Re: [opencontrail-dev] New deadline on Blue Print submission for 
release 5.0

Moreover, I get -2 for Zuul as specs sent has no Bug-Id.
If I recall correctly, there was no Bug-Id requirement for blueprints, and the 
guidelines don't mention it either.

Is it safe to ignore this -2 or should I create a stub bug report in the 
Launchpad?

Thanks,
Valentine

On 06.11.2017 20:27, Valentine Sinitsyn wrote:
> Hi all,
> 
> Another Launchpad-related question here. Guidelines doc says we need 
> to fill in the Milestone target field - but currently there is nothing 
> to choose in the drop-down, or at least I don't have an access to the options.
> 
> How should I fix this?
> 
> Thanks,
> Valentine
> 
> On 02.11.2017 00:38, Gasparakis, Joseph wrote:
>> Hi all,
>>
>> There has been an extension in the Blue Print submission deadline: we 
>> can now submit Blue Prints for the 5.0 release cycle by November 
>> 10^th . Please consult the Process and Guidelines for Blue Print 
>> submissions document (WIP) here 
>> <https://docs.google.com/document/d/1hYhaPmQEN4V4ZeLxruloIshnQ6yd05vN
>> kcKqhRqCnIw/edit> for more details. As per that document one needs to 
>> submit a feature or enhancement proposal in the OpenContrail 
>> launchpad <https://blueprints.launchpad.net/juniperopenstack> and 
>> then a full specification in https://review.opencontrail.org 
>> <https://review.opencontrail.org/#/q/status:open>. Both submissions 
>> need to be in Markdown format (.md). Please see the document for more 
>> details.
>>
>> Regards,
>>
>> Joseph
>>
>> --
>>
>> intel-logo-small
>>
>> Joseph Gasparakis
>>
>> Intel Corporation
>>
>> Networking Platforms Group
>>
>> Architecture Division
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@lists.opencontrail.org
>> http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail
>> .org
>>
> 
___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] New deadline on Blue Print submission for release 5.0

[Gasparakis, Joseph]

Hi all,

There has been an extension in the Blue Print submission deadline: we can now 
submit Blue Prints for the 5.0 release cycle by November 10th. Please consult 
the Process and Guidelines for Blue Print submissions document (WIP) 
here
 for more details. As per that document one needs to submit a feature or 
enhancement proposal in the OpenContrail 
launchpad and then a full 
specification in 
https://review.opencontrail.org.
 Both submissions need to be in Markdown format (.md). Please see the document 
for more details.

Regards,

Joseph

--
[intel-logo-small]
Joseph Gasparakis
Intel Corporation
Networking Platforms Group
Architecture Division

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

Re: [opencontrail-dev] [TSC] Request for bios for the ARB

[Gasparakis, Joseph]

Bio for Joseph Gasparakis, I would also like to be considered for being member 
of the ARB.

Joseph is an SDN/NFV architect working for Intel in Oregon. He has a strong 
packet processing and linux networking background coupled with an understanding 
of higher level software stacks in the SDN/NFV area. He implemented the 
enablement for network card offloads for overlay networks in the linux kernel 
network stack and he has worked closely with DPDK teams inside Intel on various 
DPDK usecases and features.

He has been for two years the architect behind Intel's Open Networking 
Platform, an SDN/NFV Reference Architecture with software components such as 
DPDK based OvS, OpenStack and ODL. Since last year he has been working with 
OpenContrail focusing on integration and data plane performance issues.

Regards,

Joseph

From: Dev [mailto:dev-boun...@lists.opencontrail.org] On Behalf Of Gasparakis, 
Joseph
Sent: Monday, September 25, 2017 2:49 PM
To: dev <dev@lists.opencontrail.org>
Subject: [opencontrail-dev] [TSC] Request for bios for the ARB

Hi all,

As discussed in the OpenContrail summit we are looking to create an 
Architectural Review Board in order to review submitted blueprints, which are 
architectural change proposals. During today's TSC call we defined the 
qualifications for the candidates:

Qualifications for being part of ARB

  *   Members with strong technical background. As an example an architect, a 
CTO, a technical director with tech
  *   Understanding on the OpenContrail architecture
  *   Understanding of SDN/NFV and their use cases

Good to have:

  *   Understanding how Open Source operates (blueprint reviews etc)
  *   Understanding the code of the specific component and related third party 
libraries that is being reviewed
  *   Understanding of the full system view, but either be an expert in system 
level or be an expert in a specific area but with some level of understanding 
in the system.

Please Reply All with your bio if you want to be considered for a seat in the 
ARB by the end of the week (10/1 - I am including the weekend in case that 
helps folks to find time to do it). Please keep it to no more than a page.

Regards,

Joseph


--
[intel-logo-small]
Joseph Gasparakis
Intel Corporation
Networking Platforms Group
Architecture Division

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] [TSC] Request for bios for the ARB

[Gasparakis, Joseph]

Hi all,

As discussed in the OpenContrail summit we are looking to create an 
Architectural Review Board in order to review submitted blueprints, which are 
architectural change proposals. During today's TSC call we defined the 
qualifications for the candidates:

Qualifications for being part of ARB

  *   Members with strong technical background. As an example an architect, a 
CTO, a technical director with tech
  *   Understanding on the OpenContrail architecture
  *   Understanding of SDN/NFV and their use cases

Good to have:

  *   Understanding how Open Source operates (blueprint reviews etc)
  *   Understanding the code of the specific component and related third party 
libraries that is being reviewed
  *   Understanding of the full system view, but either be an expert in system 
level or be an expert in a specific area but with some level of understanding 
in the system.

Please Reply All with your bio if you want to be considered for a seat in the 
ARB by the end of the week (10/1 - I am including the weekend in case that 
helps folks to find time to do it). Please keep it to no more than a page.

Regards,

Joseph


--
[intel-logo-small]
Joseph Gasparakis
Intel Corporation
Networking Platforms Group
Architecture Division

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] [TSC] [RFC] About the OpenContrail ARB

[Gasparakis, Joseph]

Hi all,

As we all know we are planning to have an ARB at least for the first public 
release.
We had a discussion in the TSC call today and it seems we came up with two 
options: ARB being part of TSC and ARB not being part of the TSC.

Here is the compare and contrast as described in 
https://docs.google.com/document/d/1dxTTU9a6P9wdu4Vd1tkonHp-D4xRbW_DyoDMZ0WDD1M/edit

ARB part of TSC:

  *   ARB is standing subcommittee of TSC and PTLs with delegates or elected 
members of one of these bodies constituting ARB.
  *   TSC explicitly delegates ARB charter and provides oversight to ARB
  *   Clear separation of powers would be necessary to avoid bogging down TSC. 
For example TSC controls release schedule, use cases, definition of release, 
schedule, high level quality requirements. While ARB controls all API's 
(external and inter components), overall product architecture, reviews 
individual blueprints, and can selectively review (and -2) critical code 
segments.

ARB not part of TSC:

  *   Works under an independent charter. Members are elected at large they do 
not have to be members of the TSC or PTL body.
  *   At least one core member from the project should be part of ARB review
  *   TSC and ARB operate under separate charters, but division of 
responsibilities is similar to the proposal above. For example TSC controls 
release schedule, use cases, definition of release, schedule, high level 
quality requirements. While ARB controls all API's (external and inter 
components), overall product architecture, reviews individual blueprints, and 
can selectively review (and -2) critical code segments

At the point I am polling for any other options to put on the table. Please 
reply all to this thread if you have a 3rd or 4th option that you would like to 
propose by end of Wednesday 9/27. I will be consolidating any new options and 
send out a voting poll on Thursday, hoping to close this decision by end of the 
week.

Regards,

Joseph


--
[intel-logo-small]
Joseph Gasparakis
Intel Corporation
Networking Platforms Group
Architecture Division

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

Re: [opencontrail-dev] [TSC WG] Transitioning to open source - PLEASE VOTE

[Gasparakis, Joseph]

Hi Harshad,

Although I agree with you that the Benevolent Dictator model works very well, 
it requires this Benevolent Dictator to be extremely knowledgeable with the 
code and architecture, and at the same time doing this job full time (in some 
cases more than just full time). We had this discussion in the 1st OpenContrail 
summit and it doesn’t seem like we have someone like that.

On the other hand, the designs (blueprints) are done by individuals or small 
teams of individuals. The ARB or TSC will be only reviewing those blueprints. 
Again, this has been discussed in the TSC WG calls which are public and open. 
At the 2nd Summit last week we agreed to move forward this way for the first 
open OpenContrail release and then we will adjust based on the learning.

Regards,

Joseph

From: Harshad Nakil [mailto:hna...@gmail.com]
Sent: Sunday, September 24, 2017 7:49 PM
To: Gasparakis, Joseph <joseph.gaspara...@intel.com>
Cc: gu...@certusnet.com.cn; dev <dev@lists.opencontrail.org>
Subject: Re: [opencontrail-dev] [TSC WG] Transitioning to open source - PLEASE 
VOTE

IMHO architecture board does not work and design by committee does not work.
You really need a benevolent dictator.
Regards
-Harshad


On Sep 24, 2017, at 7:34 PM, Gasparakis, Joseph 
<joseph.gaspara...@intel.com<mailto:joseph.gaspara...@intel.com>> wrote:
 Thank you all. Clearly option is the winner, and this is the direction we take 
moving forward, thank you all for your voting. Voting is now closed.

Regards,

Joseph


 Original message 
From: gu...@certusnet.com.cn<mailto:gu...@certusnet.com.cn>
Date: 9/23/17 03:17 (GMT-08:00)
To: "Gasparakis, Joseph" 
<joseph.gaspara...@intel.com<mailto:joseph.gaspara...@intel.com>>, dev 
<dev@lists.opencontrail.org<mailto:dev@lists.opencontrail.org>>
Subject: Re: [opencontrail-dev] [TSC WG] Transitioning to open source - PLEASE 
VOTE

Hi,
     Support option #2.

Regards
Gengliang Guo

From: Gasparakis, Joseph<mailto:joseph.gaspara...@intel.com>
Date: 2017-09-20 03:34
To: 'dev@lists.opencontrail.org'<mailto:dev@lists.opencontrail.org>
Subject: [opencontrail-dev] [TSC WG] Transitioning to open source - PLEASE VOTE
Hi all,

Transitioning into an open source model it makes sense for Juniper to have for 
the first public release more control than others since they have all the 
knowledge and it makes sense for them to be able to prevent radical 
architectural changes.

In the last TSC WG call we came up with a few proposals:


1.   Allow someone in Juniper have veto powers to reject a proposed change

2.   Create an  Architectural Review Board (ARB as defined in 
https://docs.google.com/document/d/1zNIVEOY3XsnUdYKy1ddwgjJoOV-Iwx1pHU_8ViYlTFs/edit)
 that will be reviewing in order to accept or reject architectural proposals, 
and Juniper to have the majority of the seats so they can control by the power 
of majority what goes in and what not.

If we decide for 2, we can choose at a later stage if we will have an ARB 
ongoing or only for this first release.

Please vote one of the two options and for the sake of openness and 
transparency REPLY ALL so your vote is visible to the whole list. If I receive 
any private votes I will be forwarding them to this list.

Also please vote by end of day today as we would like to have this decision 
made during the summit tomorrow.

Regards,

Joseph

--
<image002(09-23-18-15-40).png>
Joseph Gasparakis
Intel Corporation
Networking Platforms Group
Architecture Division

___
Dev mailing list
Dev@lists.opencontrail.org<mailto:Dev@lists.opencontrail.org>
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] [TSC] Polling for interest in TSC calls

[Gasparakis, Joseph]

Hi all,

This is to broadcast a reminder that the OpenContrail TSC is holding regular 
weekly meetings on Mondays. These meetings are open to the community so if you 
would like to participate please let me know and I will add you as participant.

Regards,

Joseph

--
[intel-logo-small]
Joseph Gasparakis
Intel Corporation
Networking Platforms Group
Architecture Division

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] [TSC WG] Transitioning to open source - PLEASE VOTE

[Gasparakis, Joseph]

Hi all,

Transitioning into an open source model it makes sense for Juniper to have for 
the first public release more control than others since they have all the 
knowledge and it makes sense for them to be able to prevent radical 
architectural changes.

In the last TSC WG call we came up with a few proposals:


1.   Allow someone in Juniper have veto powers to reject a proposed change

2.   Create an  Architectural Review Board (ARB as defined in 
https://docs.google.com/document/d/1zNIVEOY3XsnUdYKy1ddwgjJoOV-Iwx1pHU_8ViYlTFs/edit)
 that will be reviewing in order to accept or reject architectural proposals, 
and Juniper to have the majority of the seats so they can control by the power 
of majority what goes in and what not.

If we decide for 2, we can choose at a later stage if we will have an ARB 
ongoing or only for this first release.

Please vote one of the two options and for the sake of openness and 
transparency REPLY ALL so your vote is visible to the whole list. If I receive 
any private votes I will be forwarding them to this list.

Also please vote by end of day today as we would like to have this decision 
made during the summit tomorrow.

Regards,

Joseph

--
[intel-logo-small]
Joseph Gasparakis
Intel Corporation
Networking Platforms Group
Architecture Division

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

Re: [opencontrail-dev] [TSC WG] CALL TO ACTION: Subprojects for OpenContrail

[Gasparakis, Joseph]

Hi all,

I got 2 replies so far on this call to action (and thank you for your review!) 
, if there is anyone else out there who would like to contribute it would be 
great if you raise your hand and comment some more in the Google document below.

Thanks!

Joseph

From: Dev [mailto:dev-boun...@lists.opencontrail.org] On Behalf Of Gasparakis, 
Joseph
Sent: Friday, September 1, 2017 4:11 PM
To: 'dev@lists.opencontrail.org' <dev@lists.opencontrail.org>
Cc: adapt...@juniper.net; ashbhal...@gmail.com
Subject: [opencontrail-dev] [TSC WG] CALL TO ACTION: Subprojects for 
OpenContrail

Hi all,

As discussed a few weeks back we have this document that starts the discussion 
on possibly restructuring the git repo and create subprojects:

https://docs.google.com/document/d/1rUr7b3-mJ3WXRtUcUHFxPENl2kPL-F_5Oc1xm3G0Nxs/edit

The TSC WG decided in the last meeting that we need folks with hands on 
development experience in order to move to the next level of decomposition, so 
I would like to ask these type of folks (I assume it will be mostly Juniper 
developers) to volunteer by reviewing the document and propose further changes. 
I will be happy to support this activity, and am sure so will other members of 
the TSC WG.

Those who are interested please reply, I am hoping to get the prework started 
asap and complete the document update before the OpenContrail Summit on the 
20th of September.

Regards,

Joseph

--
[intel-logo-small]
Joseph Gasparakis
Intel Corporation
Networking Platforms Group
Architecture Division

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] [TSC WG] CALL TO ACTION: Subprojects for OpenContrail

[Gasparakis, Joseph]

Hi all,

As discussed a few weeks back we have this document that starts the discussion 
on possibly restructuring the git repo and create subprojects:

https://docs.google.com/document/d/1rUr7b3-mJ3WXRtUcUHFxPENl2kPL-F_5Oc1xm3G0Nxs/edit

The TSC WG decided in the last meeting that we need folks with hands on 
development experience in order to move to the next level of decomposition, so 
I would like to ask these type of folks (I assume it will be mostly Juniper 
developers) to volunteer by reviewing the document and propose further changes. 
I will be happy to support this activity, and am sure so will other members of 
the TSC WG.

Those who are interested please reply, I am hoping to get the prework started 
asap and complete the document update before the OpenContrail Summit on the 
20th of September.

Regards,

Joseph

--
[intel-logo-small]
Joseph Gasparakis
Intel Corporation
Networking Platforms Group
Architecture Division

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] [TSC WG] Proposal for TSC charter and processes complete

[Gasparakis, Joseph]

Hi all,

I would like to inform the mailing list that during this week's TSC WG we 
reviewed the document that describes the proposed OpenContrail TSC charter and 
processes found here: 
https://docs.google.com/document/d/188rzOJF2i6-WOOqJOHCaSy9DOGyPiCoLHIFTBSWaDnA

We would like to welcome any other comments, otherwise we are satisfied a 
proposal.

Regards,

Joseph

--
Joseph Gasparakis
NPG Architecture & Systems Engineering

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

Re: [opencontrail-dev] [TSC]Proposed set of sub-projects/components along with mapping of existing repos

[Gasparakis, Joseph]

Hi Valentine,

Thanks for the additions in the list of dependencies.
Your suggestions to make a clear separation of OpenContrail and OpenStack makes 
sense. In fact maybe we need to define some guidelines on what will be 
submitted as OpenStack blueprints and what will stay within the OpenContrail 
github moving forward. Similarly, are there any plans to interface OpenContrail 
with container engines, such as Kubernetes? I assume making the guidelines 
wider and generic could cover something like that too?

Anybody any other thoughts on this topic?

Joseph

-Original Message-
From: Valentine Sinitsyn [mailto:valentine.sinit...@gmail.com] 
Sent: Monday, July 10, 2017 4:10 AM
To: Gasparakis, Joseph <joseph.gaspara...@intel.com>; dev@lists.opencontrail.org
Cc: ashbhal...@gmail.com; adapt...@juniper.net
Subject: Re: [opencontrail-dev] [TSC]Proposed set of sub-projects/components 
along with mapping of existing repos

Hi all,

On 10.07.2017 13:05, Gasparakis, Joseph wrote:
> Hi all,
> 
> These are the items for this topic:
> 
> -What do we have?  Where is it?  Do we use it?  Who owns it?
> 
> -Project wide structure and subcomponent structure. (TSC/PTL like)
> 
> Trying to kick off the discussion, here are some (scattered) thoughts 
> I have, please add your thoughts:
> 
> *_What do we have?  Where is it?  Do we use it?  Who owns it?_*
> 
> Here is a list of what I have seen in my (pretty brief exposure to
> OpenContrail)
> 
> -Dependencies:
> 
> oPackages from Ubuntu or RedHat (about 50 packages)
> 
> ohttp://downloads.datastax.com (Cassandra driver + dev package, libuv)
> 
> ohttp://ubuntu-cloud.archive.canonical.com (liburcu + dev package)
Plus Kafka (and librdkafka) and Redis for analytics/web ui.

> 
> -Repo and build package in https://github.com/Juniper/contrail-vnc 
> (why called contrail-vnc?) - Pulls from repos
> 
> ocontrail-controller
> 
> ocontrail-generateDS
> 
> ovijava
> 
> ocontrail-java-api
> 
> ocontrail-vrouter-java-api
> 
> ocontrail-vcenter-plugin
> 
> ocontrail-build
> 
> ocontrail-vrouter
> 
> ocontrail-third-party
This fetches a whole bunch of third-party stuff including BIND and DPDK, and 
patches most of it.

> 
> ocontrail-sandesh
> 
> ocontrail-packages
> 
> ocontrail-nova-vif-driver
> 
> ocontrail-nova-extensions
> 
> ocontrail-neutron-plugin
> 
> ocontrail-heat
> 
> ocontrail-web-controller
> 
> ocontrail-web-core
> 
> ocontrail-webui-third-party
> 
> ocontrail-web-storage
> 
> ocontrail-web-server-manager

Plus contrail-dpdk for contrail-vrouter-dpdk.

> 
> Is any other github/Juniper project needed?
> 
> I do not know who the owners of the above are…
> 
> *_Project wide structure and subcomponent structure. (TSC/PTL like)_*
> 
> As embarrassing as it might seem, I do not recall what exactly this 
> refers to… Anybody who attended the OpenContrail reboot Summit?
Wasn't it about deciding which [separable] subprojects the OpenContrail project 
should be built of? Each project might have a separate PTL body, so a committer 
in web ui isn't necessarily one in contrail-vrouter.

Some thought to kick off the discussion:

- A clear OpenStack separation. This is the top of my personal list. It should 
be straightforward to see which bits are generic and which bits are OSS 
integration. May require some changes to source code IIRC.

- Each sub-project defines a technology stack and a set of skills needed for 
contribute. Roughly, we have REST APIs and config node services which are 
mostly Python, control plane services (plus collector and query engine from 
analytics) which are C++, and low-level vRouter part, not to mention Node-based 
web ui. Maybe it makes sense to manage these separately, so that someone 
interested to contribute to e.g. config API can commit and test their changes 
with little or no interaction with control plane services. Makes multiproject 
features more challenging though.

Best,
Valentine

> 
> Thank you in advance,
> 
> Joseph
> 
> --
> 
> Joseph Gasparakis
> 
> Intel Corporation
> 
> NPG Architecture & Systems Engineering
> 
> 
> 
> ___
> Dev mailing list
> Dev@lists.opencontrail.org
> http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.
> org
> 
___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] [TCS] Proposed technical governance structure including model

[Gasparakis, Joseph]

Hi all,

These are the items for this topic:


-  Model and rationale for it

-  Diagram/workflow (this is important)

-  Process for revising technical processes (3-4 weeks)

Trying to kick off the discussion, here are some (scattered) thoughts I have, 
please add your thoughts:


Model and rationale for it

-  This needs to be in accordance with the foundation that OpenContrail 
will get under

-  We need to consider the following:

o   How will the decisions in the TSC be decided? Will there be cases where a 
unanimous decision is needed, and when? Will most of the decision require 
majority or a specific percentage of the votes?

o   Only one representative in the TSC from each organization?

o   What are the focus areas of the TSC?

?  Make architectural proposal and decisions for OpenContrail?

?  Make contact with other Open Source projects (and their perspective TSCs)  
that OpenContrail will need to interface with? (like OpenStack)

?  Prioritize and define usacases? Where do these usecases come from? Do we 
need something like "marketing committee"?

?  Election of committers and new TSC members? What is the process for 
something like this?

?  Review of operations? Does CI/CD systems do what they are supposed to do? 
Opens?

?  What else?

Diagram/workflow


-  When we have some more clarity on the model and rationale we can 
start putting some diagrams in place and we can continue the discussions based 
on these diagrams

-  What is the repository for these diagrams? What format should be 
used?

Process for revising technical processes

I supposed the technical processes need to be defined first so here is an 
attempt to start the list (some already discussed in Model and rationale for it)

-  Decision on election of committers, contributors and TSC members

-  Decisions on networking and hardware technologies to be supported in 
contrail and making sure they are abstracted in a way that most hardware 
vendors are covered.

-  CD/CI - Additions, updates, removal of unnecessary processes. Does 
CD/CI caters for the above networking and hardware technologies?

-  What else?

Thanks

Joseph

--
Joseph Gasparakis
Intel Corporation
NPG Architecture & Systems Engineering

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] [TSC]Proposed set of sub-projects/components along with mapping of existing repos

[Gasparakis, Joseph]

Hi all,

These are the items for this topic:


-What do we have?  Where is it?  Do we use it?  Who owns it?

-Project wide structure and subcomponent structure. (TSC/PTL like)

Trying to kick off the discussion, here are some (scattered) thoughts I have, 
please add your thoughts:


What do we have?  Where is it?  Do we use it?  Who owns it?
Here is a list of what I have seen in my (pretty brief exposure to OpenContrail)

-Dependencies:

o   Packages from Ubuntu or RedHat (about 50 packages)

o   http://downloads.datastax.com (Cassandra driver + dev package, libuv)

o   http://ubuntu-cloud.archive.canonical.com (liburcu + dev package)

-Repo and build package in https://github.com/Juniper/contrail-vnc (why 
called contrail-vnc?) - Pulls from repos

o   contrail-controller

o   contrail-generateDS

o   vijava

o   contrail-java-api

o   contrail-vrouter-java-api

o   contrail-vcenter-plugin

o   contrail-build

o   contrail-vrouter

o   contrail-third-party

o   contrail-sandesh

o   contrail-packages

o   contrail-nova-vif-driver

o   contrail-nova-extensions

o   contrail-neutron-plugin

o   contrail-heat

o   contrail-web-controller

o   contrail-web-core

o   contrail-webui-third-party

o   contrail-web-storage

o   contrail-web-server-manager

Is any other github/Juniper project needed?
I do not know who the owners of the above are...


Project wide structure and subcomponent structure. (TSC/PTL like)
As embarrassing as it might seem, I do not recall what exactly this refers 
to... Anybody who attended the OpenContrail reboot Summit?

Thank you in advance,

Joseph
--
Joseph Gasparakis
Intel Corporation
NPG Architecture & Systems Engineering

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] [TCS] Kicking off discussion and meetings

[Gasparakis, Joseph]

Hi all,

I am planning to setup a conference call to discuss the following as part of 
the TSC WG. The items we need to help form are the following based on 
https://docs.google.com/document/d/1Rhu2YrX594WRut4IRu8Rkvsy2cXvcPyOKA1i8EGZc0U/edit#heading=h.yb76auno7he2
 :


*   Proposed technical governance structure including model

o   Rationale for this model

o   Diagram/workflow (this is important)

o   Process for revising technical processes (3-4 weeks)

*   Proposed set of sub-projects/components along with mapping of existing 
repos (4 weeks)

o   What do we have?  Where is it?  Do we use it?  Who owns it?

o   Project wide structure and subcomponent structure. (TSC/PTL like)

*   Establish guidelines for proposing and approving feature scope, 
documentation, design, development, CI/CD configuration and release management

*   Proposed set of guidelines for coding, architecture, and accepting code

*   Recommend release cadence

*   What are the artifacts that the OpenContrail community is responsible 
for?  Packages?  Ansible scripts?  Containers?  Recommend.

I propose we start the discussion over email and focus it on the two first big 
ticket items:


*   Proposed technical governance structure including model

*   Proposed set of sub-projects/components along with mapping of existing 
repos

I am about to start a separate email thread for each of those where we can 
start sharing thoughts, and then make them a bit more concrete during the call.
Please contribute your thoughts.

Also please let me know if you want to be added to the call. I will invite the 
members who volunteered for this working group and this mailing list. I am 
planning to use Skype for this call - I have not invited a mailing list before 
in a Skype call, so maybe it would be better if you let me know in advance that 
you are interested and I will I add your email address explicitly.

Thank you in advance,

Joseph
--
Joseph Gasparakis
Intel Corporation
NPG Architecture & Systems Engineering

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org

[opencontrail-dev] [TSC] Getting started

[Gasparakis, Joseph]

Hi all,

I would like to start the discussion (other than the one proposed for the TSC 
to discuss with Alex in another thread) and kick off meetings with the people 
in the TSC.
These I believe are the people involved, I managed to get some of the email 
address but not all. Please let me know your email address if I don't have it 
and I will schedule our first call early next week.


*   Ash Bhalgat (Mellanox) - ???

*   Masood Amin (Aricent) - 
masood.a...@aricent.com

*   Edgar Magana (Workday) - 
edgar.mag...@workday.com

*   Aniket Daptari (Juniper) - ???

Thank you,

Joseph
--
Joseph Gasparakis
Intel Corporation
NPG Architecture & Systems Engineering

___
Dev mailing list
Dev@lists.opencontrail.org
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org