Uniform metadata in IM and Dashboard about im HOT 6 OPEN

Hi @EGI-ILM,

I will try to address some of these features separately.
But I want first to address the interoperability issues that you are suffering, as it must not happen.

If you use the same OpenStack credentials in both applications, it must work in the same way in both.

We can try to debug this issue.

from im.

Thanks. I will contact you privately.

from im.

Hi @EGI-ILM,

We have implemented most of this functionality.
You can test it in the IM devel instance.

In case that you create an infrastructure with the im-client tool, you can add a "infra_name" in the metadata of the TOSCA to set the name that will appear in the Dashboard.

tosca_definitions_version: tosca_simple_yaml_1_0

metadata:
  infra_name: some name

and you can use the filter option in the im-client to get the infrastructure with a particular name:

./im_client.py list "infra_name: some name"

Please test it in the IM devel instance, and let me know if it works as expected.

from im.

Site and VO and Operability comments above have not been addressed, so I only tested the name functionality:

• IM CLI creates the name, and it is visible from the Dashboard
• I created two infrastructures with name "lethe-datalake-1". They can be queried:

$ im_client.py list "infra_name: lethe-datalake-1"
Infrastructure IDs: 
  359f9e64-7f87-11ed-a52b-ba0fc5d95973
  e5674fdc-7f86-11ed-bed1-ba0fc5d95973

$ im_client.py list "infra_name: lethe-datalake"
Infrastructure IDs: 
  359f9e64-7f87-11ed-a52b-ba0fc5d95973
  e5674fdc-7f86-11ed-bed1-ba0fc5d95973

$ im_client.py list "infra_name: lethe"
Infrastructure IDs: 
  359f9e64-7f87-11ed-a52b-ba0fc5d95973
  e5674fdc-7f86-11ed-bed1-ba0fc5d95973

$ im_client.py list "infra_name: letheX"
No Infrastructures.

What does not seem to work or can be improved

• The name is not shown in the IM CLI list, so it is still difficult to identify infrastructures:

$ im_client.py list
Infrastructure IDs: 
  359f9e64-7f87-11ed-a52b-ba0fc5d95973
  e5674fdc-7f86-11ed-bed1-ba0fc5d95973

• The CLI does not seem to provide renaming (just a comment, as I am not sure if this is desired, but the functionality exists in Dashboard).
• Using the Dashboard, I rename one of the infrastructures to "lethe-datalake-2". It seems that the CLI filter does not work anymore (do CLI and DSHB use a different data source for names?).

$ im_client.py list "infra_name: lethe-datalake-2"
No Infrastructures.
$ im_client.py list "infra_name: lethe-datalake-1"
Infrastructure IDs: 
  359f9e64-7f87-11ed-a52b-ba0fc5d95973
  e5674fdc-7f86-11ed-bed1-ba0fc5d95973

• Additionally, it might be good to have a shortcut (e.g, -n "some name") for "infra_name: some name".

During the testing I also had an error I will send privately.

from im.

By the way, related to this naming functionality maybe it can be used also as a prefix for:

• OpenStack VM
• OpenStack volumes
• OpenStack Security Groups

I know OpenStack VM names can be configured in a TOSCA template. I do not know how the other two could be renamed, but it is helpful to have this option, which makes resources easily identifiable without having to check the Infrastructure ID every time.

from im.

HI @EGI-ILM,

I have added new -n option in the im-client:
https://imdocs.readthedocs.io/en/latest/client.html#cmdoption-im-client-n-name

For example you can do:

$ im_client.py getstate -n "lethe-datalake-1"

You can test it using the im-client master branch.

from im.