CI status and sync to Asset.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2017 05:41 AM
Hi,
I have a couple of questions concerning CI status and syncing them to their corresponding Asset.
First of all, which field to us on CI, the general opinion seems to bet that you should use the install_status field on ci's although I can't really get a definitive answer on this.
Next question is concerning custom states on subclasses. For instance, we've introduced custom states to cmdb_ci_computer to match our computer lifecycle. Mappings in the 'Asset-CI install status mapping' module only works for states defined on cmdb level so i can't map the new cmdb_ci_computer values to asset values.
If I were to add the custom states on cmdb level they would be available on all descendant classes and I still can't map them to the desired asset states because there for most there already is a mapping with direction 'both'. The already existing mapping I can't edit (not without altering the ACL anyway) because they are out of the box.
So, I'm wondering how this is all supposed to work, which fields to use and how to deal with custom states on cmdb classes? How is everyone else doing this? The option as I see them:
- create an extra status field to hold the custom states, map them to existing install_status values which in turn map to asset states
- create custom states on cmdb level, also create them on asset level and map those to each other.
None of these seem like great options to me.
Hopefully you can offer some suggestions.
Thx!
- Labels:
-
Enterprise Asset Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2019 07:01 AM
Hello Ben,
I do have similar question as mjl1983. I understand this post is over a year ago. There may have been changes done on the platform to address this issue.
We are using install_status on the CI side. In the Asset-CI Install Status Mappings table, we have added an entry:
CI Install Status = Retired syncs with Asset State = In stock, substate = Pending disposal. Sync direction = Both
From a process perspective, teams will be using Change Management process (via Proposed Change) to retire a CI and prepare the CI for disposal. From the Change ticket perspective, they will be updating the CI install_status to Retired.
I believe there is a known issue and KB article for this ->
