I don't understand the meaning of the sentence above:Local storage datacenter name is an internal nameand currently will not be shown in engine's admin UI.It's just an internal label. I think we can just remove that question always using the default value and nothing will change.
How is the chosen "she_datacenter" name related with the "Default" datacenter where the hypervisor is put in? Do I have to manually create it (I don't see this se_datacenter in webadmin portal)?Also, I know there is open bugBut it seems I'm not able to to import the storage domain...In events, when I import, I have the sequenceStorage Domain she_sdomain was added by admin@internalVDSM ovc71.localdomain.local command failed: Cannot acquire host id: (u'9f1ec45d-0c32-4bfc-8b67-372d6f204fd1', SanlockException(22, 'Sanlock lockspace add failure', 'Invalid argument'))Failed to attach Storage Domains to Data Center Default. (User: admin@internal)Failed to attach Storage Domain she_sdomain to Data Center Default. (User: admin@internal)What should be the flow to compensate the bug? Do I have actually to attache it to "Default" datacenter or what? Is it expected to be fixed before 3.6?Postponing to 3.6.1 not being identified as a blocker.
You can try to add the first additional storage domain for other VMs.The datacenter should came up and at that point you try importing the hosted-engine storage domain.You cannot add other VMs to that storage domain neither you'll can when the auto-import will work.