5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
@Jon Thank you for getting back. So, I tried reverse proxying the PC and after initial hiccups with nginx caching, path-based reverse proxying and web sockets reverse proxying causing login failures and VM console access issues, I’ve finally had it working with the following config: location / { proxy_pass https://cloudconsole; proxy_intercept_errors on; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } cloudconsole refers to the upstream PC URL.Didn’t find anything broken so far when accessing the PC via the reverse proxy.
Thank you @aluciani
@Balram This is a good requirement. We have this need too as we just rolled out Self-Service and want to allow some developers use the REST API to provision VMs from catalog items. However, I don’t find any mention of catalog items in the API. We were told that there’s a REST API call made available for everything that we do in UI, but that’s certainly not the case.
@Riddhima.singh I’m using AOS 5.15.4 and Prism Central pc.2021.1.0.1 and I’m experiencing the same problem as @etr.eric reported. I’ve asked the same question here. Have you been able to get this to work and if yes, what versions of PE/PC are you running?
@Jon one possible answer to your curiosity about a reverse proxy in front of PC is for a better UX with Self-Service. For example, we’re using Prism Central Self-Service for our developers to provision VMs. We don’t want to give them a URL with port 9440 and we want to publish some FAQs. We tried to reverse proxy PC with nginx, but we had issues (path based reverse proxying and nginx caching). So, we ended up with a landing page with links to PC and FAQs. (1) Is this expected behavior with reverse proxying PC? Anybody has this working?(2) Can PC be configured to listen on 443? The last I checked, the answer was “no”.
Around 7 years ago, @shuguet asked this question. i.e. PD at container level so that every VM deployed in a container may be backed up by default. The last post in this thread ( @DavidTeague ) around a year ago mentions that it’s still not possible. I’m looking for this same feature in March 2021 and it only makes sense to want such a feature. Based on the documentation and looking at PE, I see that this is still not possible. Granted, with Protection Policies on Prism Central, you could assign all VMs to a category with a Protection Policy assigned to that category. However, it would be nice to have the PD feature with PE at a storage container level. Nutanix Folks, any rationale for not doing this?
Well, found the permission. It’s “View_Marketplace_Item”. This is non-intuitive for a customer who hasn’t bought CALM as the concept of “Marketplace” doesn’t exist without CALM. Also, the message refers to “VM templates”. Are all these permissions documented?
Just to add context to the above for RBAC, permissions granularity is possible via APIs (which we’re working on), but when certain operations are provided via the PC UI, it’s fair to expect them to be comprehensive enough to build out a solution for deployment to end users. The dead links and CALM stuff are still poor UX for a customer who hasn’t purchased CALM.
Even if our VM templates and Disk images are UEFI-enabled, when provisioning a VM via the Self-Service Prism Central UI, the user is prompted to select a Boot Configuration with options listed as:Legacy BIOS UEFIWe don’t want our users to have to select UEFI for every VM. I was told that we cannot change the default selection to UEFI and that does not provide a good UX.
@BlakeRobertsNBL I have an ansible role at https://galaxy.ansible.com/cybergavin/nutanix_vm_create which provisions many VMs with the option of mounting/enabling NGT on the VMs. For NGT operations, I had to use Prism Element as there are no relevant APIs for AHV on Prism Central. This may assist you in creating a playbook specifically for NGT.
@Alona Yes, I’m aware that we’ve got to convert VM templates to VMs and migrate them (should have made that clearer). I’ll just create new images as they’d be the foundation for future workloads on AHV.
I’ve just created an ansible role (https://galaxy.ansible.com/cybergavin/nutanix_vm_create) for bulk creation of VMs using different images and in different subnets. It also mounts and enables NGT.
Thank you @Alona . Of course, that timeline is not official (my brain fade!).
Ok @Alona , that’s comforting to know. I was concerned due to the recommendation to migrate from v1 to v2.0 at https://www.nutanix.dev/reference/prism_element/v2/
@Aleksander P This worked for me too. I got a clue from this CALM script and then came across your post. Thank you. However, I do not have CALM and the bulk installation suggested by @Alona does not meet my requirement as I am enabling NGT using the API using a cloud-init script during Self-Service VM provisioning.@Alona I am concerned that these NGT API calls are only available in v1 and not v2. Will NGT management via APIs be deprecated?
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
