Relate a DevOps with Changes - how ?

[JK1]

Hello guys,

it was really nice on the SNUG BG event and i hope we can make this group as good as possible. Seems I am the first to ask something

As it is fancy to use DevOps and agile methodologies today, of course in our company we use it as well. But I have a struggle to align the DevOps way of work with ITSM, especially with changes. For example, a new code is created and have to be deployed on few environments and platforms, and several config actions required and 10 micro services are to be deployed - per environment. And we will need a single change per single one of these activities, so we end up with 50 or more changes. Of course we cant ask the developers or DevOps team to do that as this will take more time than the actual work (not to mention they see it as a single action that needs to be tracked - Bamboo does it that way ). So we ended up with master (or parent) change which spawns as many as needed child changes -   so the developers will have to open only one change, and select from there what is needed.

But I want to ask for your experience on this hot topic. Have anyone done such thing, between changes and devops ? And if yes, how did you do it ? Any experience and ideas are very much welcome!

Thanks in advance!

Joro

[mitzaka]

jorro - by the way, I just ran into some info from Perspectum (they are a ServiceNow partner from one of the founders) who obviously have a built integration SNOW <> JIRA. They will present it at their boot at K17 (if I remember correctly you were going?). If so, we might sync up and go and check it together, as I will be in Orlando also next week. And I am interested to see their solution, as we also have our own SNOW <> JIRA integration, I am curios to compare:)

Not a tool - see our Jira integrated solution live at K17

[JK1]

Hey,

that   would be great! I should be there, yes (if plane doesnt crash, burn, etc. ) . So let sync up - I should be there on 6th so,lest catch up on the net. My Skype is voflik79 - feel free to ping me.

Cheers,

Joro

[JK1]

Hello experts!

I think we made that in very wrong way. Devops is very far from the regular operations and ITSM. Hence you need to use Plans, Deployments and so on.

Also the mentioned from SNow, new change type ticket, is good option as well (it is named CH Continuous or simply CH C). It is more in the Agile/Lean type of work and you can relate to the jobs devops is doing and especially their CI/CD.

Any one done it that way already?

What are the biggest challenges ?

Cheers,

Joro

[Lyubomir1]

Hey Joro,

I don't know anyone who has already done it, but a few days ago I came across this cool article about ITSMs place in the world of DevOps and Continuous Delivery. You might get some ideas from it.

https://medium.com/@JonHall_/on-the-false-equivalence-of-devops-and-itils-standard-change-and-why-it...

You might also check out some of Jon's other articles.

Cheers,

Lyubo