Hi Jeremy, Please see inline ..
On Mon, Jun 13, 2016 at 4:53 PM, <jeremy.huylebro...@orange.com> wrote: > Thanks Rajat. > Much appreciated you share this with the list. > > Allow me a few questions. > Sorry if they are out of scope since I don't know all the context. > > - How large can be the deployments of a CBW? > > >>>> Large as in per site OR # of sites (multi site L2 / L3 VPNs etc) ? Regardless, the scale of the deployments is really based on traffic dimensioning and other factors , hard to provide a generic answer ; as such there should not be any hard / artificial limits . > > - What operating system you choose for the switches? > > >>>>>> The Switches have choice of any NOS ; AFAIK, currently there is support for ONL, Cumulus and maybe Ubuntu Snappy (Ubuntu folks can confirm availability) ; Going forward We (OCP+Benu) are focusing on tooling and instrumentation as well as dynamic network topology management of 10s of thousands of such campus/branches. > > - Is the network team developer enough in its mindset to program some > advanced rules/automation or handle the Linux CLI? > > >>> Yea.. centrally managed IFTTT style automation for multiple branches from a CBW manager in the Data Center. > > - Do you mass update the entire fleet of switches? Do you have a > Dev/Test pipeline in place for such changes? > > >>> Yea, from initial fullfilment, FSOL (First sign of Life) to DevOPs , it is a drone/manager architecture where the OCP whitebox branch APs and switches are Ansible (will change to Salt-SSH) drones and the Manager is a Data Center workload for command and control > > - Was the architecture and hardware sort of over-provisioned for > future use cases (ex: x86 CPU, more memory, more ports, bigger ports, > fiber)? > > >>>>> CBW H/W is always price sensitive and hence compute / storage constraint. In the current state, you can assume a dual core ARM SoC as a compute engine in the White Box APs and Switches. Flash any where from 256 MB to a few GBs, DRAM from 128 MBs to 1 GB ; From compute perspective, the CBW switches prolly would can run containerized workloads, but it is tough to do it on the APs, though we are using LXC on the openWRT NOS on APs. The benefit of running containerized workloads on the CBW gear is to facilitate automated dark launches w/o destabilizing the networking topology. > Looking at your web site, I understand you may have a lot of small/mid > size deployments, all independent of each other, using the broadband > connection only for management purpose to your datacenter and not for > workload traffic. > >>>> True to a point, unless there is a policy to provide virtualized cloud services e.g. cloud security ; in that case the traffic selectors, to policy based traffic steering to service chain the traffic via virtualized appliances in the Regional cloud or edge cloud (former in most cases) > Please correct me if I am wrong. > > Thanks again > > > From: Rajat Ghai <rg...@benunets.com> > Date: Friday, June 10, 2016 at 7:56 PM > To: Jeremy Huylebroeck <jeremy.huylebro...@orange.com> > Cc: "opencompute-networking@lists.opencompute.org" < > opencompute-networking@lists.opencompute.org> > Subject: Re: [Opencompute-networking] example of using OCP gear for > enterprise/campus networks? > > Hi Jeremy, > > We have design what we called an "Open Branch" ; An open open branch > constitutes of such OCP CBW PoE switches and one or more OCP CBW Wi-Fi APs. > The WI-Fi APs are wired to the branch switches while more devices are > directly plugged to the PoE switch or connect wirelessly via OCP CBW Wi-Fi > units. Further, there may be multiple such sites in a campus environment. > OCP Wi-FI units are capable of broadcasting multiple virtual SSIDs and > each SSID is mapped to a different VLAN. > > A branch network controller in the cloud, provisions each of such VLANs > and provides policies such that certain VLANs terminate in the site itself > , while some are terminated to the data center using L2 overlays like GRE. > > Some VLANs are Open Flow controlled by the network controller and some are > not. > > An overall topology is shown below. > > > > > > On Thu, Jun 9, 2016 at 1:33 PM, <jeremy.huylebro...@orange.com> wrote: > >> >> Anybody using OCP networking gear for wired enterprise/campus networks? >> (desk/phones+connection between buildings) >> >> I would be interested in the approaches that were taken to transition >> from a legacy system to a new one based on open technologies, taking also >> into consideration future applications. >> >> Thanks. >> >> >> [image: Description: cid:image001.png@01CB81AA.3037FC70] >> >> *Jérémy Huylebroeck* >> >> Principal Cloud Architect >> >> >> *Orange Silicon Valley – SG/OSV *+1 (415) 243-1541 >> jeremy.huylebro...@orange.com >> >> _________________________________________________________________________________________________________________________ >> >> Ce message et ses pieces jointes peuvent contenir des informations >> confidentielles ou privilegiees et ne doivent donc >> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu >> ce message par erreur, veuillez le signaler >> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages >> electroniques etant susceptibles d'alteration, >> Orange decline toute responsabilite si ce message a ete altere, deforme ou >> falsifie. Merci. >> >> This message and its attachments may contain confidential or privileged >> information that may be protected by law; >> they should not be distributed, used or copied without authorisation. >> If you have received this email in error, please notify the sender and >> delete this message and its attachments. >> As emails may be altered, Orange is not liable for messages that have been >> modified, changed or falsified. >> Thank you. >> >> >> _______________________________________________ >> opencompute-networking mailing list >> Unsubscribe: >> http://lists.opencompute.org/mailman/options/opencompute-networking >> >> opencompute-networking@lists.opencompute.org >> http://lists.opencompute.org/mailman/listinfo/opencompute-networking >> >> > > > -- > Best Regards > Rajat Ghai > CTO > Benu Networks (www.benunets.com) > > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > > _______________________________________________ > opencompute-networking mailing list > Unsubscribe: > http://lists.opencompute.org/mailman/options/opencompute-networking > > opencompute-networking@lists.opencompute.org > http://lists.opencompute.org/mailman/listinfo/opencompute-networking > >
_______________________________________________ opencompute-networking mailing list Unsubscribe: http://lists.opencompute.org/mailman/options/opencompute-networking opencompute-networking@lists.opencompute.org http://lists.opencompute.org/mailman/listinfo/opencompute-networking
