I want to start using the 'Linux Management Services' - feature coming with VMware Studio.
I have created my own linux magement service with the help of eclipse.
My problem is when I import the service in Studio (clicking at "Import Service" button) then the service is imported - well that's what I expect, of course
But: When I have made a newer version of my service (the version number changed of course) I can import it again but Studio do not detect that this is an updated version of my service and place the same service again. Now I have two (and more when adding more) services with different version numbers.
Please see attached screen for an example:
So my question is:
Is that a bug or a feature ?
I can understand when this is an expected behaviour because this can be a really nice feature or even a requirement when trying to build an older appliance version to reproduce something - so the old bounded service is needed, too.
If this is the expected behaviour than it would be necessary to group that somehow. When we have 10 different management services and each of them has over 30 versions the Studio GUI will "explode" or at least be very hard to read.
So when you tell me that services cannot be replaced this way than it is ok for me and I will open a feature request for a 'group feature' at my FR issue discussion, of course
added as FR #028 to the FR list..
My second question is about a line in the Studio developer guide:
You must manually increment the version of an application package if you want it to replace the old package during an appliance update.
What does that mean? And how? Maybe that's only a hint that I need to re-add the newer service version to my Studio profile but I'm not sure..
How are updates handled when I remove the older management service in the profile and add the newer version? Will my appliances receive this as an update or not? and what is to do when not and I want to do that?
As always any help and ideas welcome!