AutoCon 0 to 1

It seems like AutoCon 0 (AC0) was just yesterday. We got a little bit of a breather, but things picked up right away. We had to process what we learned from your feedback and our observations on AC0, so we could decide what to do differently for AutoCon 1 (AC1). Let's give you a view of what's been happening since AC0 and changes we've made for AC1.

MOMENTUM FROM AC0

We built some momentum that hit one important milestone with AC0, but it’s continued since then. It hasn’t been quiet. You can see many of our communications on our LinkedIn page; there has been good conversation there. Another of the more interactive ways that momentum has continued has been in the NAF slack workspace.

Slacktivity (sorry, I couldn't help it): there have been a variety of great conversations here (some just plain fun, including the Phil Gervasi-initiated Strategic Meme Reserve), but there are two important workstreams that have been particularly notable:

(1) Autonomicon

• Defining terms is important

• This also serves as a way to get people used to GitHub for documentation - a great, low-risk way to get experience with GitOps

• Still very much a work in progress - you should jump in, check it out, and see what you can contribute

(2) Ryan Shaw’s Network Automation Framework

• NAF is not taking credit for this

• Ryan had ideas and drove it - but he tapped into the NAF community as a sounding board and crowdsourced input

• Ryan Shaw and David Sinn have a great podcast on this with our friends at Packet Pushers

• This Network Automation Framework is a perfect example of the things we want to support via NAF

The question for you, dear reader, is this: What could you do with the collective wisdom of 2000+ network automaniacs putting wind in your sails?

WHAT'S NEW FOR AC1

While all this has been happening, we’ve been planning the AC1 programme.

This has not been a solo effort - we've absorbed lots of your input via the AC0 survey, so many excellent proposals for talks from many of you, the NAF Advisory Board working through all the proposed abstracts, Friends of NAF (FoNzies? Again, I could not resist) helping with venue location ideas and info, sponsor conversations about what’s helpful to them, and more.

Here is how all that work is shaping AC1:

(1) Workshops

• This was a significant piece of feedback from AC0

• We had many proposals for training - and we're grateful for each proposal

• We're happy to help you along your automation journey through these workshops

(2) Fewer Panels

• We appreciate the panel discussions and all who participated in them at AC0

• This made room for additional content, aided by...

(3) A Longer Programme

• AC0 could have been longer - so we added half a day of of additional content

• For AC1, this includes 2 keynotes, 3 days, 6 lightning talks, 9 network automation success stories, 27 speakers, 4 breaks, 1 lunch, and 1 happy hour!

• We are excited for this year’s keynotes from Dinesh Dutt and Peter Boers

(4) More Packet Pushers

• Packet Pushers will be on site at the event again for AC1 to get some of your stories

• As an added benefit this year, Packet Pushers has offered different services at each sponsorship level as incentives - contact us if you'd like more info on this

(5) BoF structure

• We've asked Ivana Duvnjak and Jeff Doyle to organize this for AC1 and put more focus on it

• We see the AC1 BoF meetings as good face-to-face interaction, but the work doesn't stop there; NAF Slack is the place for ongoing work, both before and after AC1

• Discussion on this is happening in our NAF Slack right now - results on the final slate of BoF groups will be coming soon

WHAT'S NEXT

So, what's left for AC1?

• You still need to register for the event! Early Bird ticket price ends on 4/15

• You still need to register for the workshops! We expect these seats to sell out quickly

• Tell your friends and spread the word

• Sponsors: slots are still available. These events don't happen without sponsorship from you - please consider supporting NAF today

Jump on NAF Slack to let us know anything else you'd like to see at AC1 and beyond, or to just be a part of the conversation.

NAF AS A PLACE

We love our favorite analogies that we use for NAF and AutoCon events. We describe NAF as a…

• Salon

• Watering hole

• Pub

All of these describe places where people mingle and seek out refreshment. We see NAF and our AutoCon events as places like these where we can have constructive, useful, enjoyable, and even fun conversations about advancing network automation. There is a seat for everyone involved:

• Implementers making this happen in all sorts of networks (big, small, public, private, shiny and new, squeaky and not so new - you name it)

• Consulting firms walking alongside those implementers

• Training companies getting knowledge and skills out to the community

• Vendors and technology providers bringing tools and tech to the table

• And all the others helping to advance network automation, orchestration, and observability

Everyone has a view - many of those views are complementary, some are in conflict. But in all cases, NAF is a place to find and build constructive ways to advance the cause together. We want to make sure there are seats for everyone and a channel to bring your constructive contributions.

Come to Amsterdam and pull up a seat. Let's have a chat. See you at AutoCon 1!