Find nutanix version details using API - nutanix

I am trying to get the below details from nutanix cluster using API.
lcm version
ahv version
prism central version
I tried the API explorer but could not find any solution. Please suggest.

Related

Azure MobileServiceClient can InsertAsync but not ReadAsync

I can create a MobileServiceClient and GetTable<Model>() to InsertAsync, and see how my model gets inserted in the Easy Table table in Azure. But when I ReadAsync() from the table I get the following error:
Microsoft.WindowsAzure.MobileSerices.MobileServiceInvalidOperation: The server did not provide a response with the expected content.
This is when I mobileServiceClient.GetTable<Model>.ReadAsync()
What could be the problem?
This was when running from an MsTest project with no Microsoft.WindowsAzure.MobileServices.CurrentPlatform.Init(); call. The read worked when running the app
I had the same problem.
According to GitHub Issue:
As #elamalani pointed out above, we don't support .Net Core 2.1 in the SDK today. Unfortunately, we don't have a workaround today and like Ela said, the we don't have an ETA for a new release or other SDK to use for .Net Core 2.1 compatibility yet, so your only workaround is to stick with .Net Core 2.0 for now.
And I was also had SDK version 2.1
After changing SDK to version 2.0 all going to work fine. Please try to making the same, hope it will help you

Documentation for newest google speech api in c#

yesterday I installed the Google.Apis.Speech.v1beta1 Client Library using the package manager in visual studio as indicated in https://www.nuget.org/packages/Google.Apis.Speech.v1beta1/1.32.2.1132, I get there from https://developers.google.com/api-client-library/dotnet/get_started, but all documentation and samples I've found so far are for Google.Cloud.Speech.V1 anyone can point to documentation or samples for the new library? Thanks for your attention.

Getting Error "Cannot perform a single-role upgrade using different versions of the SDK"

This is my first post so please let me know if I post under wrong subject heading.
I have upgraded my Azure SDK version from 2.4 to 2.7 and build the package for updating Web role. During the update I am getting the error
"Cannot perform a single-role upgrade using different versions of the SDK".
I have checked in all settings and versions of Azure reference in my project and found all updated to 2.7. My understanding was Azure itself handles the roles SDK version based on the package.
I am not sure how to resolve this issue as I don't find any configuration settings in Web role to upgrade SDK version.
Please let me know if anyone faced such issue in passed. Any help in this regard is highly appreciated.
Thanks
If your deployment only has a single role you might try selecting All for the Role option instead of explicitly specifying the individual role when updating.

Jobs from an earlier version of the Azure WebJobs SDK have been detected

I'm using web-jobs SDK pre-release version and from few minutes ago Im getting this warning message:
Jobs from an earlier version of the Azure WebJobs SDK have been detected. Please upgrade the jobs to the latest version in order to see their status in the dashboard. Please visit this article for more information about the Azure WebJobs SDK.
I would be thankful if you help me with this.
Later edit: the link should work now
The page for that link is not yet live. It will be published soon, sorry for the inconvenience.
Meanwhile, to upgrade, get the latest WebJobs SDK packages (notice the package names changed so you might want to remove the old ones):
http://www.nuget.org/packages/Microsoft.Azure.Jobs/0.3.0-beta
http://www.nuget.org/packages/Microsoft.Azure.Jobs.Core/0.3.0-beta
Also notice that some attribute names changed:
Where are Azure WebJob's BlobInput and BlobOutput classes?

Migrating from Azure SDK 2.0 to Azure SDK 2.3

We have critical project partly deployed in azure that uses queues, blobs and table storage.
Now we using SDK 2.0 and thinking about moving to latest SDK 2.3 but it will cost us some resources especially for load testing with a new Azure SDK.
Is there a strong point to update SDK version like critical bug fix, performance issue or maybe useful new feature?
Sure, I read release notes but haven't found enough information about it.
In general we recommend that you always take the latest storage client from Nuget directly. If you look at Nuget you will see we are actually on 4.0.1 version of the .NET client vs the 2.0 version of the storage client that I believe is what shipped with SDK 2.0. As you can imagine there are a very large list of improvements between client 2.0 and 4.0. A couple of quick examples include: CORS Support, large improvements to Tables including JSON support and a highly optimized table service layer.
Here are some blogs with some more information:
http://blogs.msdn.com/b/windowsazurestorage/archive/2014/05/14/what-s-new-for-microsoft-azure-storage-at-teched-2014.aspx
http://blogs.msdn.com/b/windowsazurestorage/archive/2013/12/05/windows-azure-tables-introducing-json.aspx
There are also a lot of performance related improvements that have been made as well:
http://blogs.msdn.com/b/windowsazurestorage/archive/2013/09/07/announcing-storage-client-library-2-1-rtm.aspx
Hope this helps.
Jason
The latest Storage SDK version is now v12, which you can find in the Azure SDK repos:
Java
.NET
Python
JS/TS
You can also find migration guides in the repos which detail the migration benefits. The SDK has now split into separate ones like Storage Blob, Storage Queue, etc. The following are migration guides for Storage Blob. You can find the guides for the others in the repos as well:
Java
.NET
Finally, there are Changelogs for the new SDKs in the repos as well, which you can reference to see what fixes/changes are done. The following are Changelogs for Storage Blob. You can find the logs for Queue, Datalake, etc. in the repos as well:
Java
.NET
Python
JS/TS
It is recommended that you use the latest SDKs since those are the ones getting the new features as well as bug and critical fixes whereas the older libraries will only be getting bug and critical fixes. Read more about Azure SDK lifecycle and support policy

Resources