Re: [opencontrail-dev] [Announce] Opinion Please: Help Choose OpenContrail's New Name

Hi Edgar, > In my opinion, these three names sound awful. Completely agree ! Terrible. Why not something very easy like CFabric ? (Oh no it starts with bad letter "c" ;-). > Maybe we could negotiate with Juniper ... Exactly proposed the same few months back (when this all started to surface).

Re: [opencontrail-dev] The Controversy around Renaming OpenContrail

new GUI and analytics engine which are proprietary components to > our product. > > > > > > > > --Randy > > > > Vice President, Technology & Strategy, Cloud Software > > Juniper Networks > > +1 (415) 787-2253 <(415)%20787-2253>

Re: [opencontrail-dev] The Controversy around Renaming OpenContrail

Hi Randy, > To recap, we’re in the process of creating a vehicle that would allow community-led governance > of OpenContrail. That process will result in some kind of entity, besides Juniper, that owns the > governance, codebase, and related trademarks. Let's assume the new name for community

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

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 *Robert > Raszuk > *Sent:* Friday, December 01, 2017 03:

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

e should try to > rename this and create confusion (and dilute brand). > > > > I am not an expert but I see there are many open source projects (like > Docker, Kafka) with commercial version. > > > > Ashish > > > --

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

Hey Nachi, > BTW how about natto? this food seems like a network :P https://en.wikipedia.org/wiki/Natt%C5%8D Do you really want to discourage people from using it :))) ? Cheers, R, ___ Dev mailing list Dev@lists.opencontrail.org

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

ey > lose the benefit of community. > > So I would not be worried about it. > > Regards > -Harshad > > On Sep 26, 2017, at 7:44 AM, Jakub Pavlik <jpav...@mirantis.com> wrote: > > +1 to Robert > > On Mon, Sep 25, 2017 at 8:27 PM, Robert Raszuk <rob

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

Greg, > Can you think of a candidate who can dictate architecture both to Juniper internal engineering and all other community participants? How’s your spare time now-a-days? On Mon, Sep 25, 2017 at 7:51 PM, Gregory Elkinbard wrote: > Harshad, > while in general I

Re: [opencontrail-dev] [TSC] Analytics and web ui on OC 5.0 and beyond

Łukasz, > as a network operator, when looking for moving my datacenter to > SDN solution, I am not going to consider OpenContrail as viable > product on the market if analytics is gone. Well good thing that you are actually not an operator then :) To your comment on analytics it is a mistake to

Re: [opencontrail-dev] OpenContrail and CNI

which is quite important). > However, as this is an OpenSource project we can jointly start to work on > a CNI driver (I looked through the docu and it seems fairly straight > forward). > > Regards, > Michael > > Am 16.06.2016 um 11:05 schrieb Robert Raszuk <rob...@raszuk.ne

Re: [opencontrail-dev] OpenContrail and CNI

What roadmap ? Per Juniper PM during EBC this is not planned formally. We have Pedro's code but it has been shelved officially as just experimental effort. And frankly this is what makes sense the most along with mesos integration. Openstack is not that interesting for vast majority of use

Re: [opencontrail-dev] Flow unsusable over new 1000req/s

> > Do you consider in vrouter soething similiar to megaflows form openflow ? > (example http://networkheresy.com/tag/megaflows/) > It creates wildcard entries in advance. Probably it could help with udp > traffic. Of course there are situations where we can loose some security in > advance of the

Re: [opencontrail-dev] contrail-packages

I’m just asking because you are at least the fourth company I know of that is by now building their own OpenContrail packages, and this doesn’t make too much sense. Best regards Martin ​Hi Martin, While I highly appreciate syseleven work for creating and maintaining packages let's