Connecting Cloud Innovators: Building Community at .NEXT 2024
You can create intelligent applications to run on the Service Domain infrastructure or the cloud where you have pushed collected data. You can implement application YAML files to use as a template, where you can customize the template by passing existing Categories associated with a Service Domain to it.You need to create a project with at least one user to create an app. Creating an Application:Create a Kubernetes application that you can associate with a project. Before you begin To complete this task, log on to the cloud management console. If your app requires a service, make sure you enable it in the associated project. Application YAML files can also be a template where you can customize the template by passing existing Categories associated with a Service Domain to it. See also Configure Service Domain Environment Variables to set and use environment variables in your app. Nutanix recommends that you do not reuse application names after creating and then deleting (removing) an a
Objective:Create a virtual/physical separation between different kinds of CVM traffic. Each type of traffic can be on different vLANs (virtual) or a completely different physical switch. Different type of CVM traffic are:Management: Prism, SSH, Rsyslog, SNMP, PE-PC etc. Any communication that requires the default gateway. Backplane: Mainly CVM CVM communication that happens between cluster services. Host Host and Host CVM traffic also comes under this category. Service: This is a user defined traffic type where-in he can choose a particular AOS feature to be separated out of other traffic types. RDMA: This is a type of Service traffic but only limited to Stargate service.Solution Summary:The way to achieve these separations is by creating a new interface (vNIC) on CVMs for each traffic type. By default all the traffic types happen over management interface (eth0) and user can decide to segment other traffic types to new CVM interfaces one at a time. RDMA is a special segmentation ty
Citrix Diagnostic Facility (CDF)CDF collects and traces the messages generated by various Citrix services running on the Delivery Controller. CDF helps discover and debug the root cause and related issues. Configure and Use CDFDownload the tool in a ZIP file from: http://support.citrix.com/article/CTX111961 Extract the ZIP file and run the extracted CDFControl.exe file. Go to Tools > Options and ensure that Enable real-time viewing while capturing trace is selected. This allows you to view the real time logs while the scripts run. Go to Tools → Options → Trace File Path and set the path for log collection. Check the following modules to enable plugin specific log collection. BrokerHostingManagementBrokerHostingPluginHostServiceHCLHostServiceLogHostServiceLoggingHostSnapInMachineCreationLogMachineCreationLoggingMachineCreationServiceHCLMachineCreationSnapIn Before running the script, click Start Tracing. It will start capturing the traces while PoSH script executes.Once you encounter
Sometimes Kubernetes clusters are not listed when we try to open Karbon console from Karbon management GUI on Prism Central. This is due to Karbon (karbon_core & karbon_ui) containers being in an unhealthy state. This can be due to various reasons, one of them being docker containers are unable to get the proper resources or docker is unable to establish a connection with Karbon containers. Below is a screenshot of what one would notice when one would go to the Karbon console and no Kubernetes clusters are listed. Symptoms are container is unhealthy and here is the simple fix to try as a first step: The Karbon container karbon_core is unhealthy. The Karbon container karbon_core is unhealthy.nutanix@NTNX-10-X-X-X-A-PCVM:~$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 3cf0cb9a9dee karbon-core:v1.0.1 "/start.sh" 5 months ago Up 5 months (unhealthy)
What is NSX-T ?NSX-T provides customers a way to run software-defined networking infrastructure. NSX-T data center provides networking, security and automation for cloud-native applications, bare metal workloads, multi-hypervisor environments, public clouds, and multiple clouds. NSX-T is designed to address the needs of these emerging application frameworks and architectures with heterogeneous endpoints and technology stacks. NSX-T allows IT and development teams to choose the technologies best suited for their particular applications.Logical overview of vSphere Switching Components, where NSX-T fits and how the Nutanix platform interacts with them NOTE: NSX-T support is only available from AOS 5.16.1/5.10.9 and above. For more details please review below KB: https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000CsyzCAC
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.