Shulou(Shulou.com)06/02 Report--

Azure Stack is being updated and deployed every month, and in essence, Azure Stack is becoming more and more powerful. So far, it has been updated to ASDK 1904, and the Azure Stack 1904 update build number is 1.1904.0.36. The installation process does not vary much, but the specific changes are as follows:

Improve

1904 the update load includes updates to which host Azure Stack does not include the Azure Stack components of the underlying operating system. This allows some updates to determine their scope. Therefore, the expected time it takes to complete the update in 1904 is less than (about 16 hours, but the exact time varies). At run time this decline is similar to the 1903 update. However, subsequent updates may include the operating system, which means different runtime updates. Future updates will be completed, depending on the expected time required for the payload to include.

Major improvements have been made to the software-defined network (SDN) stack in 1904. These improvements increase the reliability of the overall service and the SDN stack in Azure Stack.

If the currently logged-in user does not have the required permissions to enable the dashboard to load correctly in the administrator portal, add a notification. It also contains links to documents that describe which accounts have the appropriate permissions, depending on the identity provider used during deployment.

Added an improvement in the elapsed time of all Vm in the scenario for VM resiliency and parsing if the storage volume containing the VM profile is offline.

The number of optimized Vm added is simultaneously removed from the host and placed at the upper limit of bandwidth consumption, address VM power outage or blockage when the network load is heavy. This change increases VM uptime when the system is updated.

Improved resource constraints when the system's running strength protects the internal processes from exhausting the platform's resources, resulting in failed operations in the portal.

Improved filtering capabilities to enable operators to apply multiple filters at the same time. You can only sort columns in the new user interface by name.

Process improvements for deleting products / services, plans, quotas, and subscriptions. You can now successfully delete products / services, quotas, schedules, and subscription administrators portal whether the objects you want to delete have no dependencies.

Improved selection of syslog messages with the required severity level of forwarded messages by filtering out unnecessary events and providing configuration parameters. For more information about how to configure severity levels, see Azure Stack data Center Integration-syslog forwarding.

The Azure Stack infrastructure will consume an additional 12 GB + (4 GB number of Azure Stack hosts) from 1904 update and later. This means that the additional capacity consumption of 28 GB (12 GB + 4 GB 4) in the 4-node stamp will be reflected in the capacity screen of the Azure Stack administrator portal. By 1904 the version update should be successful, even if other memory consumption puts the Azure Stack stamp out of capacity. If the Azure Stack stamp is based on memory usage after the update is completed, you will see that it is designed to reflect this state, corrective measures to release some virtual machines with an alert.

Added to the new feature Get-azurestacklog cmdlet by including an additional parameter to-OutputSASUri. You can now collect Azure Stack logs from your environment and store them in the specified Azure storage blob container. For more information, see Azure Stack Diagnostics.

Add a new memory check-in Test-azurestack UpdateReadiness to check to see if there is enough memory available to update groups on the stack that has completed successfully.

Evaluate the health of Service Fabric for improved Test-azurestack.

Improved hardware updates, reducing the time it takes to complete the drive firmware update to 2-4 hours. The update engine dynamically determines which parts of the update need to be performed, based on what is in the package.

To prevent the addition of reliable operations to destructive infrastructure role instance operations that affect availability, pre-check.

An improvement plan for idempotent infrastructure backup operations.

Improvements in Azure Stack log collection. These improvements reduce the time required to retrieve logs. In addition, Get-azurestacklog cmdlet will no longer be able to generate default logs for the OEM role. You must perform an Invoke AzureStackOnDemandLog cmdlet to specify the role of the OEM log to retrieve. For more information, see Azure Stack Diagnostics.

Azure Stack now monitors the data center and integrates with ADFS to provide federated authentication data URL. This will improve reliability during confidential rotation of customer ADFS instances or farms.

Change

Remove the option for the infrastructure role instance in the administrator portal if the Azure Stack operator shuts down. The restart feature ensures a clean shutdown attempt before restarting the infrastructure role instance. For advanced scenarios, API and PowerShell features are still available.

There is no new Marketplace management experience, using a separate Marketplace image and resource provider screen. For now, the resource provider window is empty, but in future versions of the new PaaS service products / services will be displayed and managed in the resource provider window.

Changes to the update experience in the operator portal. There is no new grid updated for the resource provider. The ability to update the resource provider is not yet available.

Changes to the update installation experience in the service provider portal. To help the Azure Stack operator respond appropriately to update problems, the portal now provides more specific suggestions for automatically deriving Test-azurestack and analysis results by running in health-based zoom units. Depending on the result, the operator is notified to perform one of two actions:

The warning alert for "Soft" is displayed in the portal and requires attention to read the latest update. Microsoft recommends that the service request be opened during normal business hours. Test-azurestack is executed, and based on part of the update process, we generate the most appropriate alert on the output. In this case, Test-azurestack has passed.

The "hard" critical alert is displayed in the portal as "the latest update failed. Microsoft recommends that you open the service request as soon as possible. Test-azurestack is executed, and based on the update process, we generate the most appropriate alert on the output. In this case, Test-azurestack also fails."

The updated Azure Linux agent version 2.2.38.0. With this support, customers can maintain a consistent Linux image between Azure and Azure Stack.

Repair item

Fixed where the syslog configuration was not retained through the update loop, causing the syslog client to lose its configuration and to stop forwarding syslog messages. The Syslog configuration will now be retained.

Fixed the issue in the CRP that prevented the unallocated Vm. Previously, if you included multiple large managed disk VM, unallocating VM might have failed with a timeout error.

The problem that has been fixed affects the Windows Defender engine accessed by scaling unit storage.

Fixed user portal issue the access policy window for the blob storage account could not be loaded.

Fixed an error notification in the administrator and user portal that was displayed about the global Azure portal.

Fixed opening in browser tab where selecting a user portal problem feedback tile caused it to be empty.

Fixed static IP address adapters that were attached to the VM instance when changing the IP configuration bound to the network, causing the error message to show portal problems.

The attempt in fixed the user portal problem attaching the network interface to the existing VM through the network window caused the operation to fail and an error message was displayed.

Fixed where Azure Stack does not support attaching more than 4 network interfaces (Nic) to VM instances.

Fixed adding inbound security rules in the portal and selecting the question service tag as the source, showing several options that are not applicable to Azure Stack.

Fixed the problem in which the Network Security Group (Nsg) invalid Azure Stack works in the same way as the global Azure.

Fixed hiding all downloaded products in Marketplace management if registration expired or was deleted.

Fixed command failure and error message invalid shared configuration key in which issuance set AzureRmVirtualNetworkGatewayConnection connected to the existing virtual network gateway in PowerShell.

Fixed a problem that caused the network resource provider (NRP) to synchronize with the network controller, resulting in the synchronization of requested duplicate resources. In some cases, this can cause the parent resource to be in an error state.

Fixed read permissions in which the user participant role was assigned to a subscription but not explicitly provided, if an incorrect problem was generated. The client somelogonaccount@domain.com uses the object ID {GUID} and does not perform the operation. When trying to save changes to a resource.

Fixed images in which the marketplace management screen was empty if the offline federation tool was used to upload images, and any of the files were missing the icon of URI (s).

Fixed an issue that prevented products that were being deleted from marketplace management downloads.

After the installation is complete, log in to the ASDK host as AzureStack\ AzureStackAdmin.

Open PowerShell (not PowerShell ISE) as an administrator.

Run: Enter-PSSession-ComputerName AzS-ERCS01-ConfigurationName PrivilegedEndpoint

Run: Test-AzureStack

At present, there are a lot more testing items than before.

To be continued.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.