Saturday, December 3, 2022
HomeCloud ComputingCloud Networking Sources from Cisco Developer Relations – A Deep Dive

Cloud Networking Sources from Cisco Developer Relations – A Deep Dive


This weblog is a collaboration between lead creator Quinn SnyderDeveloper Advocate, Cisco DevRel and Ravi Balakrishnan, Senior Advertising and marketing Supervisor.


Throughout the Developer Relations ecosystem, plenty of focus (each when it comes to creation, in addition to dialogue with others) is on the content material that enables folks to discover and develop their expertise. Naturally, this tilts outreach (and blogs like these) in the direction of our superb sandboxes and thorough studying labs. Additionally it is fully comprehensible why we might bias ourselves in the direction of these modalities; we’re technical folks, and we like to study and train folks via hands-on exploration, whether or not its guided or self-paced. “See it, study it, code it” has served the group very nicely and it’s one thing we’re pleased with.

Nonetheless, we need to write this weblog rounding out the whole portfolio of labor that helps our infrastructure builders and automation engineers, when the sandboxes and studying labs don’t present all of the solutions to the questions they’ve.

The Developer Facilities

The Developer Facilities (or DevCenters) for brief serve a single supply touchdown web page for all issues programmability associated to a product or instrument. From updates to product APIs, bulletins from the enterprise entity supporting that product, webinars and how-to, and documentation pages – the whole lot wanted by an infrastructure developer may be discovered right here.

As a part of our dedication to developer expertise, these Decenter are saved updated with any newest info or modifications to the APIs to make sure that everybody has entry to the related content material they want, after they want it. We’ve got DevCenters for knowledge heart applied sciences, corresponding to ACI, NX-OS, Nexus Dashboard.  We even have particular DevCenters for Infrastructure as Code, together with one particularly for cloud networking, in addition to for every IaC instrument supported inside the DevNet ecosystem, Ansible and Terraform.  There’s a ton of knowledge that may be gleaned simply from these assets – however that is just the start.

API Documentation

We’ve got touched on this in earlier weblog posts, however nonetheless wish to dive a bit deeper into how we’re improving our API documentation, offering for a greater developer expertise. Each API-enabled product (and the cloud networking product strains aren’t any exception) has an API documentation microsite. This microsite (an instance for ACI is proven beneath) comprises not solely the API information, however background and context concerning the APIs and their design ideas, mannequin references (the place acceptable), and hyperlinks to exterior pages, corresponding to IaC modules/suppliers, sandboxes that can be utilized to discover the APIs, studying labs, and developer group assist boards for questions that will come up throughout API exploration.  These documentation pages additionally assist a number of variations of the API – which means that whatever the model you might be working – you will discover an API reference for it on our portal.

Whereas these pages is probably not as visually “flashy” as our DevCenters, they comprise a wealth of knowledge and supply a lot of exterior hyperlinks to different helpful instruments. A few of our hottest documentation pages embrace:

However proceed to examine again, particularly as new services or products are launched. If it exists – you may be certain now we have API documentation for it!

The CiscoDevNet GitHub Group

Whereas not instantly hosted on our personal web site, lots of our hyperlinks (particularly to assets for Ansible and Terraform) redirect to our Github group for that particular repository. As a result of we wish to follow the ideas that we train to our prospects and companions, our GitHub group is the one supply for all code samples, third get together IaC assets, and pattern tasks inside DevRel. These public-facing repositories may be forked to your personal group, modified, or improved upon, and submitted for merge into the primary upstream department by way of a pull request (PR). To prime it off, it isn’t solely DevRel advocates and engineers inside these repositories, however members of the technical gross sales, engineering, and product administration groups – enabling you to have unfettered entry to the groups which can be growing automation and programmability options.

The opposite added benefit of utilizing our GitHub group is that it permits us to make use of the “Points” web page as a reference for the changelog of our infrastructure as code assets. Whereas TAC does assist the assets, it’s potential to have interaction with our builders to work via enhancements or bugs inside Ansible modules or Terraform suppliers with out opening a direct service request with TAC. These points will likely be aggregated, mounted, and talked about as a part of a given launch of the useful resource and the barrier to opening a difficulty is extremely low – showcasing how utilizing a VCS like GitHub can show invaluable to a developer’s workflow.

Our present record of IaC assets on GitHub are:

However once more – hold checking – as we’re continually including particular actions to these assets, in addition to including new assets on a regular basis!

Code Change and Automation Change

One ultimate (and sometimes neglected) part inside the DevNet web site is the Code Change and Automation Change platforms. Every of those platforms can help you seek for curated content material related to your wants and use-case, every with a distinct bent: Code Change (CE) focuses on easy code samples that can be utilized as a place to begin for creating a bigger resolution, whereas Automation Change (AE) focuses on driving a single use-case via to its automated completion.  Each CE and AE assist builders, each novice and skilled alike, get began on a mission by utilizing different prior work as a supply of inspiration or a constructing block for additional duties. I do know that I’ve been impressed on a number of events to create one thing utilizing another person’s work as a place to begin (with correct attribution to the unique developer, after all). You will discover Code Change and Automation Change by clicking on the embedded hyperlinks of their names.

Placing It All Collectively

From the record above, you’ll be able to see that there’s greater than the spectacular studying and sandbox content material that we create inside DevRel. The whole lot that we do is supposed to drive up the developer expertise, decrease the mean-time-to-API-call (MTTAC, one thing I simply made up), and make sure that our cloud networking infrastructure builders are supported at each step of their journey and in each means potential.

We might love to listen to about your experiences utilizing any of the DevRel assets, not simply those listed above. Good, unhealthy, detached, or in any other case – we’re right here for all of it. You will discover Quinn on Twitter @qsnyder or on LinkedIn and we’d like to have a dialog about what’s working for you, what isn’t, or how we will enhance to drive the perfect developer expertise potential.

 

Share:



RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments