On today's Day Two Cloud we dive into the challenges of adopting and operationalizing a cloud deployment with guest Mark Gossa. We discuss how to incorporate DevOps principles and automation tools into the organization, examine tool options such as Terraform, and chat about going serverless.
The post Day Two Cloud 014: Turning A “Get Us Into Cloud” Order Into Operational Reality appeared first on Packet Pushers.
The Internet Society and AFRINIC collaborated to organize the 3rd Hackathon@AIS in Kampala, Uganda, which took place alongside the 2019 Africa Internet Summit. The event attracted more than one hundred participants who took part in five different tracks at the event. The event has grown from three tracks and 39 participants in 2017 and three tracks with 75 participants in 2018, to five tracks with 100 participants this year. Cisco DevNet has been helping organize the event since the first edition, and this year, they sponsored t-shirts for the Hackathon.
Objectives
The goals of the Hackathon@AIS and other open standards promotion activities in the African region are to identify, encourage, and expose engineers from Africa to open Internet Standards development, so that they can contribute to the work at organizations such as the Internet Engineering Task Force (IETF).
Format
The event ran for two days, organized as follows:
On today’s Heavy Networking, we peer behind the curtain of Intent-Based Networking (IBN) with guest Phil Gervasi, who wrote a pair of white papers for the Packet Pushers' Ignition membership site. We discuss core concepts of IBN, including network abstraction, continuous validation, and automated remediation.
The post Heavy Networking 461: Key Concepts Of Intent-Based Networking appeared first on Packet Pushers.
Ansible became popular largely because we adopted some key principles early, and stuck to them.
The first key principle was simplicity: simple to install, simple to use, simple to find documentation and examples, simple to write playbooks, and simple to make contributions.The second key principle was modularity: Ansible functionality could be easily extended by writing modules, and anyone could write a module and contribute it back to Ansible.
The third key principle was “batteries included”: all of the modules for Ansible would be built-in, so you wouldn’t have to figure out where to get them. They’d just be there.
We’ve come a long way by following these principles, and we intend to stick to them.
Recently though, we’ve been reevaluating how we might better structure Ansible to support these principles. We now find ourselves dealing with problems of scale that are becoming more challenging to solve. Jan-Piet Mens, who has continued to be a close friend to Ansible since our very earliest days, recently described those problems quite succinctly from his perspective as a long-time contributor -- and I think his analysis of the problems we face is quite accurate. Simply, we’ve become victims of our own success.
Success Continue reading
Everyday, I’m in awe of what Ansible has grown to be. The incredible growth of the community and viral adoption of the technology has resulted in a content management challenge for the project.
I don’t want to echo a lot of what’s been said by our dear friend Jan-Piet Mens or our incredible Community team, but give me a moment to take a shot at it.
Our main challenge is rooted in the ability to scale. The volume of pull requests and issues we see day to day severely outweigh the ability of the Ansible community to keep up with that rate of change.
As a result, we are embarking on a journey. This journey is one that we know that the community, both our content creators and content consumers, will be interested in hearing about.
This New World Order (tongue in cheek), as we’ve been calling it, is a model that will allow for us to empower the community of contributors of Ansible content (read: modules, plugins, and roles) to provide their content at their own pace.
To do this, we have made some changes to how Ansible leverages content that is not “shipped” with it. In short, Continue reading
It is hard to say what will happen first: Switching and routing will merge, or an independent networking operating system that can do both will emerge. …
The Switch-Router War Is Over, And Hyperscalers Won was written by Timothy Prickett Morgan at .
The serverless platform was initially developed by IBM but now enters an increasingly complex...
The first phase of CenturyLink’s fiber network expansion traverses more than 3.5 million miles...
One of the new products combines Arrcus’ hardware-agnostic operating system with Broadcom’s...