Code Exchange is a great place to start. The About page includes this note about support:   Note: All users should inspect the repository for any usage or contributing process questions. Cisco DevNet is not certifying or maintaining the content of all repositories. If you see an issue or have a question about a project, raise it with the project maintainers. If you see an issue or have a question about Code Exchange itself, please report it by email to askcodeexchange@cisco.com   This blog includes a more in-depth description of Code Exchange, including maintenance and support of the repos with it.   The tile for each repo indicates the person or organization that contributed the repo. Repos are created and maintained by Cisco engineering teams, ecosystem partners, technology and open source communities, and individual developers. In this example, you can see two are from CiscoDevNet and one is from an individual’s GitHub account.     The best way to get all the details on a repo, including the owners, the state of the code, the license, how to contribute, and how to get help, is to select a given repo, click on the “View on GitHub” button on that repo’s Code Exchange page, and review the README and LICENSE files.   In addition to Code Exchange, there is the Open Source Dev Center, containing info about open source projects to which Cisco contributes significantly and uses in its products and solutions. Projects listed here tend to be larger projects with more contributors, users, and supporters both inside and outside of Cisco. ... View more

https://fosdem.org/2019/ FOSDEM is possibly the largest and definitely the best open source conference of the year. It is a weekend event (February 2-3 this year) organized by open source enthusiasts to promote the widespread use of free and open source software. Each year, during the semester break at Université libre de Bruxelles, thousands of developers from all over the world gather to share ideas and collaborate on open source software. FOSDEM is unlike any conference you have ever attended. It is free and open to everyone. Registration is not necessary, nor is it possible. I had my first FOSDEM experience in 2016 and have attended every year since then. Each year, I increase my involvement in the event. After all, FOSDEM is what us volunteers/attendees make it, so jump in and help us make it the best ever. Software Defined Networking devroom This year, I am one of the organizers of the Software Define Networking (SDN) devroom. We have a packed agenda of great talks by experts from many different organizations. Topics include XDP, Cilium, BPF, Virtio, NFV and VNFs, ONOS, VPP and FD.io, Ligato, Kubernetes, DPDK, and OPNFV. Too many acronyms? Don’t worry, you will be familiar with all of them by the end of the day, and we will of course include topics such as network device drivers and filters, flow tables, virtual switching, and much more. You are welcome to drop in for just a few sessions or stay with us the entire day. SDN devroom schedule   Legal and Policy Issues devroom Arguably not as technically stimulating, the Legal and Policy Issues devroom is undeniably a critical component of FOSDEM. Sessions are insightful, extremely relevant to anyone using or contributing to open source software, and covers tough topics in a respectful, constructive, and collaborative environment. The panel discussion in which I am participating, Advocating for FOSS Inside Companies Redux, is just one example. Panelists from different organizations at different stages of their open source journey will share best practices and lessons learned from first-hand experience and real-world situations. Audience participation is encouraged, so join us and bring your burning question and troubling scenarios. Legal and Policy Issues devroom schedule Lightning Talk on TRex Be sure to catch the TRex open source traffic generator lightning talk, Sunday, 14:20-14:35, and hear Hanoch Haim introduce the FOSDEM community to TRex, an open source, low cost, stateful and stateless traffic generator fueled by DPDK. TRex is used by many open source projects, including DPDK, OPNFV, DPDK-OVS, and FD.io/VPP to benchmark SDN/VNF solutions in very high scale. The Dilemma The SDN devroom and the Legal and Policy Issues devroom are just two of  40+ devrooms accepted for FOSDEM this year, not to mention the keynotes and main conference tracks. There are also dozens of Lightning Talks, each providing a taste of a topic and something new to discuss at the bar over a Belgian ale that evening. I proposed a couple lightning talks that are waitlisted in the event space opens up. One is on extending the reach of open source through industry standards. The other is on best practices and lessons learned using GitHub for corporate open source. Please reach out to me at eckelcu@cisco.com or @eckelcu if you want to discuss. With so many great topics and tracks, the unavoidable dilemma is how to allocate your time. Here is a tip, all sessions are recorded and available online within a few weeks. Don’t waste time running all over campus trying to get to every talk on your bucket list. Rather, focus on a few topics, take advantage of the opportunity to make personal connections, and have fun. Helpful Resources The main FOSDEM page has complete and up to date info on the conference. The DevNet Open Source Dev Center highlights open source projects that benefit from significant contributions by Cisco employees and are used in our products and solutions in ways that are relevant to developers. Code Exchange helps you discover, learn, build, and collaborate on curated GitHub projects to jumpstart your work with Cisco platforms, products, APIs, and SDKs. Your contributions are welcome, and we encourage you to submit your open source repos today. Join DevNet. It is free and easy using this link (https://developer.cisco.com/join/fosdem19) created for FOSDEM. ... View more

Contributors to Github repos that have been submitted in Code Exchange are welcome and encouraged to add the "DevNet published" badge to these repos.     The way I do this is as follows.   1) Log in to Code Exchange and go to your Dashboard: https://developer.cisco.com/codeexchange/dashboard   2) Click on any of your projects to enter the admin interface for that project, e.g., https://developer.cisco.com/codeexchange/github/repo/CiscoDevNet/iotvizconf#edit   Note, the link above is for one of my projects so it likely will not render for you. You will need to select one of the projects you have submitted in order to have access to its admin interface. However, the format of the URL for the admin interface of all projects is similar (i.e., https://developer.cisco.com/codeexchange/github/repo/<repo org>/<repo name>#edit )   On the right hand side you will see the helpful “Add this badge” info that you can copy/paste at the top of your README.   Admin interface for repo in Code Exchange 3) The end result in GitHub: https://github.com/CiscoDevNet/iotvizconf README.md in GitHub For additional info on Code Exchange, how to submit a repo, and how to get it approved and published, check out Curated Code Repos Get Your Integration Project Done Faster, Better. ... View more

Having a hard time getting started on your next big integration with Cisco products? Found the platform and API docs on DevNet but need help turning this into running code? Check out Code Exchange, one more way DevNet makes it easy for developers to be successful with Cisco products and platforms.   Code Exchange is an online, curated set of code repositories that help you develop applications with/on Cisco platforms and APIs. Inside Code Exchange, you will find hundreds of code repositories – code created and maintained by Cisco engineering teams, ecosystem partners, technology and open source communities, and individual developers. Anyone can use this code to jumpstart their app development with Cisco platforms, products, application programming interfaces (APIs), and software development kits (SDKs).   For more information, see this post in the Cisco blogs. Feel free to share any comments or questions there or he in this space. ... View more

The IETF 102 Hackathon is less than two weeks away. We will have a prep call Wednesday, 11 July, at 7am PDT. Webex info is included below. IETF Hackathons encourage developers to collaborate and develop utilities, ideas, sample code and solutions that show practical implementations of IETF standards. IETF Hackathons aim to: Advance the pace and relevance of IETF standards activities by bringing the speed and collaborative spirit of open source development into the IETF Bring developers and young people into IETF and get them exposed to and interested in IETF IETF Hackathons are free to attend and open to everyone. They are collaborative events, not competitions. Past IETF Hackathons have covered a range of topics including; DNS, HTTP 2.0, NETVC, OpenDaylight, ONOS, VPP/FD.io, RiOT, SFC, TLS 1.3, WebRTC, YANG/NETCONF/RESTCONF. New technologies are always encouraged. The next IETF Hackathon will be held in Montreal July 14 and 15, 2018. The call is optional and will be recorded for those who cannot make it. Anyone is welcome to join; however, the call is meant primarily for first time hackathon participants and champions to learn what to expect and get answers to any questions. If you have not already registered for the hackathon , please do so asap. Registration is free but is required and is independent of registering for the IETF 102 meeting. https://www.ietf.org/registration/ietf102/ hackathon registration.py If you would like to champion a project, please add it the wiki asap and send an email to this list ( hackathon @ietf.org ) and other relevant communities to let people know about your project. https://trac.ietf.org/trac/ietf/meeting/wiki/102 hackathon Cheers, Charles IETF 102 Hackathon prep call Wednesday, July 11, 2018 7:00 am  |  Pacific Daylight Time (San Francisco, GMT-07:00)  |  1 hr Meeting number (access code): 208 342 455 Meeting password: hackathon (42252846 from phones) Add to Calendar When it's time, join the meeting . Join from a video system or application Dial 208342455@cisco.webex.com You can also dial 173.243.2.68 and enter your meeting number. From the Cisco internal network, dial *267* and the 9-digit meeting number. If you are the host, enter your PIN when prompted. Join by phone +1-866-432-9903 Call-in toll-free number (US/Canada) +1-408-525-6800 Call-in toll number (US/Canada) Global call-in numbers   |  Toll-free calling restrictions Can't join the meeting? IMPORTANT NOTICE: Please note that this WebEx service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session. ... View more

Mark your calendars and book your travel now, the Open Source Summit North America will be in Los Angeles, CA September 11-14. The summit is essentially the combination of what were previously LinuxCon, ContainerCon, CloudOpen, and the Open Community Conference. You no longer need to pick and choose and travel the globe; rather, we all benefit from coming together under one roof for a fantastic learning and networking experience. But there is a catch. Yes, there is always a catch. You are now left with the difficult task of selecting from a packed schedule of fantastic presentations and hands on workshops. While daunting at first, this is actually a good problem to have with multiple options that all make good use of your time. Since I have the pen, let me take this opportunity to selfishly plug the three sessions in which I am speaking. Get Hands on with Containerized Deployment of OpenStack - Charles Eckel, Cisco DevNet Monday September 11, 4:00-4:40pm http://sched.co/BDpl Hearing a lot about OpenStack and want to check it out for yourself? See how quick and easy it is to install and start using OpenStack using containers that run within a VM on your laptop or within a sandbox. OpenStack Kolla provides production ready tools to deploy OpenStack services as Docker containers that can be managed and upgraded easily. To help you explore Kolla and OpenStack, we provide access to a VM with a containerized deployment of OpenStack Mitaka and step by step instructions. Acquaint yourself with the environment. Learn your way around Horizon (GUI) and the CLI to view and operate your OpenStack cloud. Best of all, take what you learn with you and experiment on your own to discover all OpenStack offers you. OpenDaylight as a Platform for Network Programmability - Charles Eckel, Cisco DevNet Thursday September 14, 2:45-3:25pm http://sched.co/BEN0 Software Defined Networking (SDN) may have started as the separation of the control plane and the data plane, but the true power lies in the ability to communicate with the network through well-defined and interfaces using standard protocols. This session provides a brief intro to SDN in general, and more specifically to OpenDaylight, an open source platform for programmable SDN. Next, we dive into network programmability, including why we need it and the role of NETCONF, YANG, and RESTCONF. Then we put the theory into practice as we install OpenDaylight as use it a platform for programming a sample network. (Really!) Outside the Box: Cisco’s Open Source Journey - Panel Discussion Wednesday September 13, 4:00-4:40pm http://sched.co/Bocc Not used to hearing Cisco and “open” used in the same sentence? Wondering why Cisco is investing as heavily as it is in open source technologies? If you answered yes to either of those questions, this panel is for you. Join moderator and Linux luminary Ed Warnicke along with panelists Serpil Bayraktar, Rohit Agarwalla, Anne McCormick, and Charles Eckel as they discuss the various areas of Cisco’s involvement in the open source ecosystem. They’ll be covering Cisco’s involvement in and contributions to FD.io/VPP, SNAS.io, OpenStack, Kubernetes/Cloud Native, and much more. The panel will also discuss how Cisco’s contributions and involvement in open source technologies are key components in its future strategy. You’ll also have the opportunity to learn about Cisco DevNet (developer.cisco.com), Cisco’s developer resource hub that offers learning labs, forums, sandboxes, API and code libraries, hackathons, and much, much more. The future is open and Cisco is moving forward to embrace it with (you knew it was coming) open arms. You can view the entire Open Source Summit schedule here. Register now, then follow the links above to start building your personal schedule. I look forward to seeing you at the summit. In the meantime, feel free to add any comments or questions here, on twitter @eckelcu, via email  eckelcu@cisco.com, or better yet, by clicking on the icon below to be become a new member of DevNet! ... View more

Where are the new kingmakers? They are at the IETF hackathon, or at least they were last weekend. The best and brightest internet technologists from around the planet gathered in Prague this week for IETF 99. The first order of business was the IETF hackathon, aimed at invigorating the standards process, enhancing the speed and relevance of emerging standards, and growing the community of people working with and contributing to the IETF. Restoring Balance The Internet Engineering Task Force (IETF) is a standards organization whose mission is to make the Internet work better by producing high quality, relevant technical documents that influence the way people design, use, and manage the Internet. From its inception in 1986, the IETF has held “rough consensus and running code” as its motto and mode of operation. However, the reality slowly shifted over time until the majority of the structure, effort, and activities revolved around discussions, documents, and long email threads dedicated to forming rough consensus with very little emphasis on running code. The first hackathon, held in March of 2015 at IETF 92, was an attempt to restore the balance. The 8 th hackathon at IETF 99 in Prague was a strong indication the strategy is working. Prague is a beautiful city, with fantastic architecture, picturesque bridges and canals, and terrific food and beer all at very affordable prices. Despite all that, a record 199 hackathon participants opted to spend their weekend in a crowded room collaborating with fellow subject matter experts and developers working on the latest algorithms and ideas around internet protocols, transports, and security. For nearly half the participants, this was their first IETF hackathon, and for 45 participants, this hackathon was their first time at any IETF event. With over 25 different projects from which to choose, newcomers and seasoned IETF veterans alike had an easy time finding one of more areas of common interest and expertise to which they could contribute. This collaborative and constructive atmosphere turns out to be a great way to get started with the IETF, its community, and its work items. Not Your Typical Hackathon The IETF Hackathon is not a typical hackathon. Participants are motivated by a desire to improve the internet rather than prize money. The spirit is collaborative rather than competitive. Participation is free and attending the IETF meeting that follows is not required. Individuals volunteer to “champion” projects related to IETF work, and teams form around these champions. The list of projects for this hackathon where as follows: ACME STAR Authenticated Received Chain (ARC) COSE in the network: Secure Wake-on-Radio (SWORN) DNS, DNSSEC, DNS Privacy DOTS HTTP error code 451 Interface to Network Security Functions (I2NSF) Framework Loss-Latency tradeoff MILE MPTCP Multicast over SPRING Multiple Provisioning Domains (mPvD) and Captive Portal detection NEAT/TAPS OpenWSN QUIC RIOT SACM SCHC implementation and test SCTP SCTP SDN Apps for management of microwave radio link via IETF YANG Data Model Secure IoT bootstrapping for Noobs with EAP-NOOB SysRepo - Segment Routing v6 TCPINC YANG/NETCONF/RESTCONF Additional information about each project is available in the hackathon wiki . One of the ways the hackathon increases the pace and relevance of IETF work is through running code. Implementing evolving standards and producing running code validates the standards and highlights things that may be missing, wrong, or ambiguous in draft versions of these standards. Better still is if the code is open source, in which case viewing and sharing the source code aids in understanding the standards, makes them easier to use, and promotes adoption. The doors to the hackathon opened at 8am Saturday morning for project champions to setup their tables and development environments. By 9am, the room was mostly full with eager participants exploring the options and opportunities with various champions. At 9:30am we had the official kickoff to welcome everyone, review logistics, and answer any questions. Then the real work began. Teams dug in and worked past the official closing time at 9pm. Of course, we had fun all along the way, taking time to get to know each other, and in many cases, help or be helped by people from other teams. Having people from various standards organizations, open source communities and universities exchange contact info and ideas provides benefits that reach far beyond the course of the weekend. By 9:30pm, the last remaining hackathoners grudgingly packed up for the night. The doors officially reopened at 9am Sunday, but the room was already half full by 8:30am. Work continued until early afternoon at which time teams prepared and delivered  presentations summarizing what they achieved, lessons learned along the way, and what would be fed back into IETF working groups to accelerate their standardization efforts. These presentations were delivered to a panel of judges from the IETF community. In the name of friendly competition, winners are selected based on the following criteria: Advance pace and relevance of IETF standards Bring speed and collaborative spirit of open source software into the IETF Flush out ideas, feed into WG session Produce sample code/reference implementations, utilities Attract developers, young people to IETF Match young, skillful developers with IETF veterans University engagement around hackathon projects The award categories and winners from this hackathon were as follows: Best New Work - HTTP error code 451 Best University Work - Interface to Network Security Functions (I2NSF) Framework “NEAT”est Work - NEAT/TAPS Best Interop Work – Best Continuing Work - SCHC implementation and test SCTP Best Name - Waiting for go-dots Best Overall - SDN Apps for management of microwave radio link via IETF YANG Data Model Other teams had fantastic achievements as well. All project presentations are available here . One pervasive theme was collaboration across standards efforts and open source communities, with a particularly good example being the work done by the team working on RIOT. Cenk Gündoğan, RIOT maintainer, had this to say: RIOT powers the Internet of Things like Linux powers the Internet. RIOT is a free, open source operating system developed by a grassroots community gathering companies, academia, and hobbyists, distributed all around the world. RIOT supports most low-power IoT devices and microcontroller architectures (32-bit, 16-bit and 8-bit) and implements all relevant open standards supporting an Internet of Things that is connected, secure, durable, and privacy-friendly. The IETF99 Hackathon provides an excellent opportunity to connect with hackers around the world and share experiences about their implementations as well as interoperability. Visit us at: https://github.com/RIOT-OS/RIOT https://riot-os.org/ Effort and Benefit Continue The hackathon ended officially on Sunday afternoon, at which time the general IETF meeting gets underway. Fortunately, collaboration on running code that progresses IETF standards forward continued throughout the week. A portion of the IETF Lounge was designated as Hackathon Corner to make it easy for people to congregate, collaborate, and code. New for this IETF meeting was the opportunity to access the Hacklab, a rack of servers and network gear, including a full DOCSIS network with half a dozen simulated home networks accessible via a cable modem and built-in WiFi. Running code is a critical aspect to the history and evolution of the Internet.  Hacklab is an extension of the Hackathon that takes place during each IETF meeting throughout the year.  Hacklab is an ideal environment where engineers from around the globe, that participate in the IETF, can work side by side implementing the protocols that they develop under the IETF umbrella. - John Jason Brzozowski, Comcast Fellow and Chief IPv6 Architect Demos to IETF Community One of the perks of participating in the hackathon is the ability to show off what you did at the Thursday night social event known as Bits-n-Bites. A record number of teams took advantage of this, and more would have if we had space to accommodate them. Hackathon teams polished and enhanced their projects throughout the week, then put them on display for whoever was interested to learn more. Turns out this was most to the people at the IETF meeting. Of course, great local food and beverages helped attract a crowd as well. Below is a summary slide for each demo,followed by a few photos from the gathering. What is Next? The next IETF Hackathon is at IETF 100 in Singapore, November 11-12, 2017. As always, participation is free and open to everyone. The IETF hackathon offers an excellent opportunity to experience firsthand the critical work the IETF does and the people that make it happen. It is an event that invites open source communities, other standards organizations, universities, and people from the local community to join the IETF to improve the functionality, security, and durability of the internet we all know and love. To get more information on all things related to past, present, and future hackathons, including the opening of registration for the IETF 100 Hackathon, visit https://www.ietf.org/hackathon/ . You are also encouraged to subscribe to hackathon@ietf.org to get the latest breaking news and announcements. eckelcu@cisco.com @eckelcu - Credit to Stephen O'Grady’s book for the phrase, “The New Kingmakers”. - Credit to Richard Stonehouse of Stonehouse Photographic for photos ... View more