Hi Brady,

I'll take a look in depth to make sure about the SFC dependencies on NIC's
side and keep you update.

Thanks,

On Mon, Oct 17, 2016 at 4:23 PM, Brady Johnson <bradyallenjohn...@gmail.com>
wrote:

> An,
>
> Thanks for pointing that out.
>
> I didn't know that cardinal, nic, and faas officially depended on sfc. Nic
> and faas mentioned possibly using sfc in the past, but we were never
> notified officially.
>
> The only official dependencies we know about are netvirt and gbp, and they
> both gave us the go ahead.
>
> Since the patch has already been merged, I guess we should go ahead and
> create a weather report.
>
> Regards,
>
> Brady
>
> On Oct 17, 2016 20:04, "An Ho" <an...@huawei.com> wrote:
>
>> Should we open a weather item for tracking purposes since from the
>> dependencies log [1], a few other projects have dependencies on SFC:
>> cardinal, faas, groupbasedpolicy, netvirt, nic?
>>
>> I have CC'ed the other projects to keep them informed of the changes to
>> SFC.
>>
>> Best Regards,
>> An Ho
>>
>> [1] https://logs.opendaylight.org/releng/jenkins092/autorelease-
>> project-report-carbon/10/archives/dependencies.log.gz
>>
>>
>>
>> -----Original Message-----
>> From: release-boun...@lists.opendaylight.org [mailto:
>> release-boun...@lists.opendaylight.org] On Behalf Of Brady Allen Johnson
>> Sent: Monday, October 17, 2016 1:50 AM
>> To: netvirt-...@lists.opendaylight.org; groupbasedpolicy-...@lists.ope
>> ndaylight.org; rele...@lists.opendaylight.org;
>> sfc-dev@lists.opendaylight.org
>> Subject: Re: [release] SFC project changing module artifact versions in
>> maven in Colorado
>>
>> Including sfc-dev email list.
>>
>> Brady
>>
>>
>> On 17/10/16 10:49, Brady Allen Johnson wrote:
>> >
>> > Hello Netvirt and GBP projects,
>> >
>> > I wanted to inform the projects that officially depend on SFC (Netvirt
>> > and GBP) that we will be changing the module artifact versions soon.
>> >
>> > This is as a result of these email threads [0] and [1]. We discussed
>> > the solution in this thread [2].
>> >
>> > I really doubt this will cause problems for your projects. Basically
>> > we'll bump SFC from 0.4.0 to 0.5.0.
>> >
>> > A patch has been created here [3]. We wont merge this until we get the
>> > go ahead from both projects (Netvirt and GBP).
>> >
>> > Regards,
>> >
>> > Brady
>> >
>> > [0]
>> > https://lists.opendaylight.org/pipermail/sfc-dev/2016-Octobe
>> r/003475.html
>> > [1]
>> > https://lists.opendaylight.org/pipermail/sfc-dev/2016-Octobe
>> r/003481.html
>> > [2]
>> > https://lists.opendaylight.org/pipermail/sfc-dev/2016-Octobe
>> r/003485.html
>> > [3] https://git.opendaylight.org/gerrit/#/c/47001/
>> >
>> >
>>
>> _______________________________________________
>> release mailing list
>> rele...@lists.opendaylight.org
>> https://lists.opendaylight.org/mailman/listinfo/release
>> _______________________________________________
>> sfc-dev mailing list
>> sfc-dev@lists.opendaylight.org
>> https://lists.opendaylight.org/mailman/listinfo/sfc-dev
>>
>
> _______________________________________________
> nic-dev mailing list
> nic-...@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/nic-dev
>
>


-- 
*Yrineu Rodrigues*
*OpendayLight NIC PTL/committer*
--

*Linkedin <http://www.linkedin.com/in/yrineu>*
*NIC wiki page*
<https://wiki.opendaylight.org/view/Network_Intent_Composition:Main>
_______________________________________________
sfc-dev mailing list
sfc-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/sfc-dev

Reply via email to