[yocto] Yocto for NFS/SDN networking product

[Khem Raj]

Generally individual components wrote there own component build
systems using gmake, cmake, autotools etc. then they let the distros bundle
it using their meta builders like rpm, dpkg etc.

Yocto however is providing a mechanism to roll your own distro
so many large projects now a days deploy it as the default build
infrastructure for the project and build a "just enough OS" for
their projects to work. I havent looked in detail into OpenSwitch
but I believe its a single component and then it has external dependencies
it relies on.

With yocto projects layer structure it also lets you choose only
relevant layers into the project build system which might be relevant in
openswitch case.

Therefore, if you are building a full platform build around openswitch, you
have to use some platform build system and it
could well be yocto. if you are just build a single component
from openswitch and dont care where it gets packaged and distributed, then
you could just get it going on your linux machine
you have and build/debug/test natively.

On Mon, Jun 5, 2017 at 6:06 AM, Kosta Zertsekel <kzertsekel at mrv.com> wrote:

> Khem,
>
>
> Fully agree that Yocto has is good, 'cause it supports cross-build, has a
> wide
>
> industry support and actually it has **the version** (meaning, all the
> packages
>
> are taken with specific git commit id unlike debian/ubuntu binaries).
>
>
> But then, I'm confused in the other respect...
>
>
> I'm looking at the OpenSwitch build system (part of Open Compute project
>
> under Linux Foundation) and I see that is uses yocto as a subsystem. It's
> really
>
> confusing because yocto is supposed to have "meta-XYZ" for OpenSwitch
>
> support.
>
>
> So, when choosing a build system for OpenSwitch-based products - do one
>
> still has to use yocto or just go with the build system provided
> by OpenSwitch?
>
>
> Thanks,
>
> --- KostaZ
>
> ------------------------------
> *From:* Khem Raj <raj.khem at gmail.com>
> *Sent:* Sunday, January 31, 2016 5:56 PM
> *To:* Kosta Zertsekel
> *Cc:* yocto at yoctoproject.org; Ran Wainstein
> *Subject:* Re: [yocto] Yocto for NFS/SDN networking product
>
> Kosta
>
> Yocto project is developed by many volunteers and people sponsored by
> corporations,
> all development happens in opensource. The community supports the project.
> There
> are also lot of commercial OS vendors which use Yocto project to build
> their products,
> so you can always go to them if you are looking for commercial support.
>
> For advantages, it can build a small footprint since it builds bottom up.
> So you can really get only needed
> packages for your custom image. It will create a source based distribution
> for you where you have control
> over every part of the OSS stack. You can really tailor your solution to
> your needs.
>
> It builds in cross-build environment, supports many CPU architectures and
> machines
>
> The community is very welcoming and helpful. You can easily contribute to
> the project
> and fulfill your needs by doing so. The learning curve might be a bit
> steeper. But then
> you do have trainings available offerred by professionals.
>
> Thanks
> -Khem
> On Sun, Jan 31, 2016 at 4:22 AM, Kosta Zertsekel <kzertsekel at mrv.com>
> wrote:
>
>> Hi dear Yocto community,
>>
>>
>> I'm trying to evaluate Yocto as the candidate to create Linux distro
>>
>> for NFS/SDN networking product. Through Google I get an impression
>>
>> that there is a race between Yocto, CentOS (RedHat) and 6WIND
>>
>> Linux distributions to get most of NFV/SDN Linux distro market.
>>
>>
>> Can you please help to find cons and pros of using Yocto for
>>
>> NFV/SDN networking product?
>>
>>
>> I google over NFV/SDN part of www.etsi.org but couldn't make up
>>
>> my mind what specific distro got the traction.
>>
>>
>> I see that Yocto has NFV/SDN layers (reference
>> <http://events.linuxfoundation.org/sites/events/files/slides/YP_and_OpenStack_LinuxCon2014.pdf>
>> ):
>>
>> ```
>> git clone git://git.yoctoproject.org/meta-cloud-services
>> git clone git://git.openembedded.org/meta-openembedded
>> git clone --branch icehouse git://git.yoctoproject.org/
>> meta-virtualization
>> git clone git://git.openembedded.org/openembedded-core oe-core
>> ```
>>
>> Are these layers officially supported by Intel?
>>
>> Does Intel provide the NFV/SDN support?
>>
>>
>> Thanks,
>>
>> --- KostaZ
>> [image: E-Banner] <http://www.mrv.com/blog>
>>
>>
>> MRV Communications is a global supplier of packet and optical solutions
>> that power the world’s largest networks. Our products combine innovative
>> hardware with intelligent software to make networks smarter, faster and
>> more efficient.
>>
>>
>> The contents of this message, together with any attachments, are intended
>> only for the use of the person(s) to whom they are addressed and may
>> contain confidential and/or privileged information. If you are not the
>> intended recipient, immediately advise the sender, delete this message and
>> any attachments and note that any distribution, or copying of this message,
>> or any attachment, is prohibited.
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
> <https://goo.gl/0NNSWr>
>
>
> MRV Communications is a global supplier of packet and optical solutions
> that power the world’s largest networks. Our products combine innovative
> hardware with intelligent software to make networks smarter, faster and
> more efficient.
>
>
> The contents of this message, together with any attachments, are intended
> only for the use of the person(s) to whom they are addressed and may
> contain confidential and/or privileged information. If you are not the
> intended recipient, immediately advise the sender, delete this message and
> any attachments and note that any distribution, or copying of this message,
> or any attachment, is prohibited.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170606/870550f8/attachment.html>