Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[WIP] Import/Export Services #131

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

[WIP] Import/Export Services #131

wants to merge 4 commits into from

Conversation

ThomasBuchinger
Copy link
Contributor

This script adds support for importing/exporting Services
At the moment, there are a couple of things wrong/specific to our use case, that I would need to fix, before releasing it to the public, but I wanted to know if you guys would be interested in it at all.

Stuff to fix:

  • it supports renaming certain elements. The feature is pretty handy, but it needs to be implemented differently in a more general setting
  • it is very explicit in the attributes it imports and how it goes about it. There is probably something we can offload to rails
  • Since Services cannot be uniquely identified by name, the script sets a custom attribute with the current service-id to identify already existing Services
  • it doesn't update existing services
  • add any additional associations a service might have (e.g. generic objects)
  • add CLI options to control which parts should be imported

Thomas Buchinger and others added 4 commits September 5, 2018 13:42
@ThomasBuchinger
Add support for service 0bjects
bccb729 
This commit adds support to import/export services (UI > Service >
My Services). It currently has some "features", that we needed in
our usecase, but should be refactored before merging upstream.
* import/export of custom attributes
* import/export of VM relations (using ems_ref)
* import/export of service hierarchy
* depends on an 'Import ID:' custom attribute (defaults to the
service id in the old envrionment)
* rename some stuff
@ThomasBuchinger
fix ems_ref not unique with multiple providers
6bee091 
ems_ref is only unique per provider. Multiple providers can use the same
ems_ref, which leads to collisions. This fix uses the provider hostname
to namespace the ems_ref (because it is more likely to be the same
accross environmentss than the user provided name)
@ThomasBuchinger
fix exception if catalog item is missing
8a8cef5
@ThomasBuchinger
remove transformation for custom_1 attribute
8e5806f 
this transformation is obsolete, because we now have a job that periodically updates the custom_1 attribute (and it should never have been here anyway)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@ThomasBuchinger