Kasper

I know that many are embarrassed to share their overly manual processes and
or others are keeping their solutions private. It sounds like you have a
solution for your needs. I would add some transparency to the process in
the form of a dashboard or summary of status for support staff, security,
QA, etc to understand that a particular release was tested, approved and
deployed "days" prior to the customer having an issue vs "minutes".
Inter-organization communication and socialization for the win!

Maybe a poll on workflow would be fun:
1. Break Fix workflow - aka ASAP
2. Whale customer requests only
3. Budget constrained projects only
4. Everything is awesome we get to test all the things AND have single
button rollback
5. All of the above depending on the team and department.

:)

On Wed, Aug 9, 2017 at 7: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
>



-- 
- Andrew "lathama" Latham lath...@gmail.com http://lathama.com
<http://lathama.org> -

Reply via email to