hi, sorry to answer my own question. looking at some of the recent documentation; eg;

http://www.emc.com/collateral/technical-documentation/scaleio-quick-start-guide-for-vmware.pdf

The creation of the template now appears to be part of the main powershell script;

ScaleIOPluginSetup-1.32-402.1.ps1

I think the confusion arose as I was looking at documentation for previous releases which appears to have separate scripts.

Quick question - why is the community forum locked down only to registered users (unregistered/not logged on users should at-least be able to view the posts shouldn't they)? Why are new forum posts moderated or is it just the first post from a poster?

thanks.

HI Megha, I'm afraid I have to disagree with regards to a community.

For a community to flourish information sharing is a requirement - if you look at many of the examples of products in the disruptive space their communities are accessible as read-only to all without logging on/registering- this helps with google crawls and helps to raise visibility and use on their products. e.g. Veeam/ VyOS etc.

Its pretty hard to encourage collaboration when there can be a 24 hour delay or more after posting a comment/update before it is released onto the website.

thanks

Ashley

1. This does not look like ScaleIO OVA: ScaleIOVM_1.32.XXX.X.ova - why?

2. Did they start working on the deployment wizard and then created the SVM template? if that is the case, the deployment wizard must be ran again from the start.

3. Is the DC + datastore: esxtest accessible for the ESX servers? Is it a local DS? they need to supply LOCAL DS for each ESX host...

4. Is the Path to the OVA accessible for the Virgo server and the VC?

5. Using vSphere client, can they see the created template properly?

Hello,

I have the same issue, i used full paths, how i can do to get the list of the svm templates? i get a blank screen.

thanks

Can you check the following:-

  Using vSphere client, can they see the created template properly?
Is the Path to the OVA accessible for the Virgo server and the VC?

Hello, Thanks for your help.

Yes i can see in my case Three templates, because i deployed the ova to three datastores. And yes i can access from the web console or vcenter console the datastores (local) with the template images. the issue is when i need to choose the ova template from the "scaleio deployment" i just see a blank dropdown list. I need to a permission or something?

thanks

Hi,

For the blank drop down list issue, the only time I have seen this in 3 scenarios:

1. The template was added in the middle of the plugin install. The plugin does not automatically refresh in this scenario. Stop and begin the install fresh.

2. The name of the template and folder it exists in do not match what the plugin is looking for. The folder name will be "EMC ScaleIO (Datacenter_Name)", where Datacenter_Name is the name of your datacenter. The name of the template underneath that folder will be "EMC ScaleIO SVM Template (v2.0.13000.211) 1". This is for the 2.0.1.3 template. Also, the notes section for the template must have "2.0.13000.211". These numbers will change with different versions of the template, of course.

3. Not running the install as administrator level user, or administrator itself. If you can, use the actual administrator user.

Check the above and see if any of this matches.

Hello RickH,

Thanks for your suggestions, answering i can answer the following.

1 .I follow all the steps in order, i installed the plugin first, then i uploaded the template using the powercli console, with the provided script.

2. The template for me was created with "EMC ScaleIO c:\Users\path\to\the\ova\file" looks like this could be the issue here, the name of the templates for me had the entire path to the ova file i used when uploaded it. How can i do to avoid the creation of the Full path of the ova file i uploaded?

3. I'm using administrator for all tasks, so i dont think this is the issue here.

Please let me know if the topic 2 could be the issue, and how i can do to upload the ova with the correct name.

Thanks

Go ahead and rename the template itself using the name I gave above. If you have a different version, let me know and I can tell you what the name of the template should be. Also verify the folder it resides under. Make sure it follows the proper naming convention mentioned above as well.

As for why it was named with the path from the OVA itself, we'd have to see what variables were passed to the script when the OVA was uploaded.