To be honest, most companies I've worked at have moved to amazon, where the networking stack has APIs. I've also seen folks who use CI/CD pipelines to generate configuration files for devices that don't directly support automation.
On Wed, Aug 9, 2017 at 7:16 PM, Joe Hamelin <j...@nethead.com> wrote: > We've been using this tool since we're a LEAN company, but it actually is a > good way to assign tasks/projects and delegate tasks so everyone can see > what is going on. Managers can move cards to your active lane or ask why a > task/project has stalled. > > I'm not sure what exactly you are looking for but as a team management > tool, this has mostly worked for us for the last 3-4 years. YMMV. > > https://kanbanize.com/ > > > > -- > Joe Hamelin, W7COM, Tulalip, WA, +1 (360) 474-7474 > > On Wed, Aug 9, 2017 at 5:52 PM, Kasper Adel <karim.a...@gmail.com> wrote: > > > We are pretty new to those new-age network orchestrators and automation, > > > > I am curious to ask what everyone is the community is doing? sorry for > such > > a long and broad question. > > > > What is your workflow? What tools are your teams using? What is working > > what is not? What do you really like and what do you need to improve? How > > mature do you think your process is? etc etc > > > > Wanted to ask and see what approaches the many different teams here are > > taking! > > > > We are going to start working from a GitLab based workflow. > > > > Projects are created, issues entered and developed with a gitflow > branching > > strategy. > > > > GitLab CI pipelines run package loadings and run tests inside a lab. > > > > Tests are usually python unit tests that are run to do both functional > and > > service creation, modification and removal tests. > > > > For unit testing we typically use python libraries to open transactions > to > > do the service modifications (along with functional tests) against > physical > > lab devices. > > > > For our prod deployment we leverage 'push on green' and gating to push > > package changes to prod devices. > > > > Thanks > > >
