LectureRechercheRadarCadre d'investissement
Connexion / Inscription
ToutTechnologieProduitsInvestissementBourseAutres

Lecture

2026-11-224 publications

Actualiser

Inference chip company Positron AI executive: Inference now drives two-thirds of AI workloads, shifting deployment to modular data centers

Matériel
2026-11-22 02:28 GMT+8

Cameron McCaskill, head of sales and business development at Positron AI Inc., stated at the SC26 supercomputing conference that inference workloads now account for approximately two-thirds of the traffic running through AI infrastructures, compared to one-third for training. This represents a significant reversal from 2023, when the split was roughly 85% training and 15% inference. According to McCaskill, this shift is driving the economic decisions behind how companies build out their AI infrastructure.

To capture this market change, Positron AI designs its inference appliances around commodity memory rather than High Bandwidth Memory (HBM), which is scarce and expensive. The company’s first-generation Atlas server runs on programmable chips, with plans to tape out its own silicon early next year for the Titan server. Oracle Corp. is bringing about 340 Atlas servers live in its cloud this quarter, and a neocloud provider has also signed on for Atlas and committed to Titan.

The design choice to skip HBM keeps power consumption low enough for air-cooled rooms. A single Positron server draws about 4,500 watts, and a full rack of Titan servers fits within 40 kilowatts. This footprint suits sites where operators can find a few megawatts of cheap power without heavy regulatory hurdles. McCaskill noted a rise in demand from modular data center operators who have half-megawatt to 2.5-megawatt capacity and aim to go from land and power to monetizable tokens within 90 to 120 days.

Sources :SiliconANGLE

Recherche

Adding Your Firewall's CA Won't Fix Azure Hosted Agent Timeouts

Matériel
2026-11-22 02:12 GMT+8

When a financial services team moves hosted agents into its own virtual network with public access disabled, TLS-inspecting firewalls on all outbound traffic, and private endpoints for Cosmos DB and Storage, the deployment succeeds but the Agents page spins and times out. The team's first instinct is to register the firewall's CA certificate with Private CA trust, a public preview feature that lets agents call internal services using corporate certificates. That fix does not work, and Muzz Imam, Principal Product Manager on the Microsoft Foundry team, explains why in a November 21, 2026 blog post.

The reason is a scope limitation: Private CA trust does not apply to the platform's own Microsoft Entra ID and managed identity traffic from the agent subnet. When the agent infrastructure signs in to Entra ID before calling your resources, that traffic is still being inspected and re-signed by the firewall. Adding the firewall's CA to the trust store changes nothing because the platform's sign-in path is excluded from the trust mechanism entirely. Imam reproduced this in a test subscription by routing the agent subnet's Entra traffic through a decrypting proxy; registering the proxy's CA made no difference, and a no-decrypt rule for the Entra hosts fixed it.

The actual fix has two parts. First, exclude three specific host patterns from TLS inspection: login.microsoftonline.com, {region}.login.microsoft.com, and control-{region}.identity.azure.net. Second, allow those hosts on the firewall plus the managed identity FQDNs from the Azure Container Apps firewall guidance or the AzureActiveDirectory service tag. If an NSG sits on the agent subnet, it needs a matching outbound rule for the same service tag. Private CA trust remains useful for what it was built for: letting tools, model gateways and agent code call internal services that use the company's own certificates.

The article frames this as one of five checks teams should run when the Agents page times out. The others cover subnet delegation (the agent subnet must be delegated to Microsoft.App/environments, use an RFC 1918 range, and belong to one Foundry resource only), DNS zone linking (the privatelink.documents.azure.com zone must be linked to the VNet holding the agent subnet, not just a peered hub), peered hub VNets (system routes handle connectivity but DNS follows the agent subnet's linked zones), and the DelegatedSubnetInUse error that blocks subnet reuse after soft-deleting a Foundry account. Each check has specific Azure CLI commands to verify the state.

The broader lesson for anyone deploying AI agents in enterprise networks is that the obvious fix for a TLS-related timeout is not always the correct one. The platform's authentication infrastructure operates outside the trust boundary that administrators control. When a timeout persists after adding your CA, the question shifts from "does my certificate chain validate?" to "is the platform's own sign-in traffic being intercepted?" — and the answer requires a firewall rule change, not a trust-store change.

Sources :Microsoft Foundry Blog

Recherche

Trump Proposes Ban or Tax on US Companies Building Data Centers Overseas

Structurel
2026-11-21

US President Donald Trump has stated that he wants to prevent US companies from building data centers in other countries, or impose a "tremendous tax" if they proceed with overseas plans. The proposal comes as a surprise, as Trump noted he has not yet discussed the policy with his cabinet and advisors, according to Axios.

One possible reason for this consideration is that Chinese AI labs have been exploiting a loophole in US law. This technicality allows them to export data to overseas data centers that use AI chips banned for export to China, such as Nvidia's Blackwell and upcoming Vera Rubin chips. "We're not allowing data centers to go into other countries because China will take all of them, and we're not allowing that to happen," Trump said.

The US House of Representatives passed the Remote Access Security Act (RASA) in January 2026 to close this workaround, but the bill has been in limbo in the Senate since then. The US Bureau of Industry and Security (BIS) is also taking steps to prevent this, with Nvidia warning its clients that their customers should be at least 51% not from China to avoid legal exposure.

However, implementing a "tremendous tax" faces significant hurdles. Congress is the only federal body with the constitutional power to impose taxes, and with the opposing party controlling both the House and the Senate, it would be difficult for the White House to implement its legislative priorities without serious concessions. Additionally, there are issues of data sovereignty and latency; US companies build data centers abroad partly because some governments demand that their data remain within their territory. A ban could cause American tech companies to lose these markets and result in longer latency for global customers.

Sources :Tom's Hardware

Recherche

UN CCW Review Conference Ends Without Mandate for Binding Ban on Lethal Autonomous Weapons

Structurel
2026-11-22 00:28 GMT+8

The seventh review conference of the United Nations Convention on Certain Conventional Weapons (CCW) concluded in Geneva early Saturday morning with only a minimal consensus. Instead of establishing a clear path toward a legally binding prohibition on fully autonomous weapon systems, the 128 States Parties agreed merely to continue discussions over the next two years to develop new regulations. Whether these talks will ever result in a binding international treaty remains uncertain given the history of previous negotiations.

Prior to and during the one-week conference, 98 countries and numerous non-governmental organizations called for rapid and binding restrictions on so-called "killer robots." Recently, 163 countries supported a resolution advocating for binding legal rules on the use of autonomous systems in conflicts. However, decisions within the CCW framework require consensus, meaning opposition from a small group of states was sufficient to block more ambitious steps. Russia primarily opposed binding requirements, which effectively acted as a veto. The United States, the United Kingdom, Israel, and Belarus also expressed reservations about committing to a legally binding instrument.

The German government had previously advocated for a ban on fully autonomous weapons but signaled willingness to compromise during the deliberations to avoid jeopardizing a consensus. Human rights organizations and experts reacted with sharp criticism to the outcome after a total of 13 years of international debate. Thomas Küchenmeister, spokesperson for the Stop Killer Robots campaign in Germany, criticized the "wishy-washy mandate," stating it showed no ambition to promptly ban and comprehensively regulate autonomous weapons. He fears that the arms race in military artificial intelligence will continue unchecked.

Nicole van Rooijen, Executive Director of Stop Killer Robots, pointed out that autonomous technologies, including AI systems in target acquisition processes, are already being used on battlefields. She warned that any further delay in binding rules endangers civilians and humanity. Verity Coyle from Human Rights Watch lamented that the result creates legal uncertainty at a time when clarity is urgently needed due to rapid technological development. Observers also criticized the lack of transparency at the conference, noting that much of the deliberation took place behind closed doors without civil society participation.

Sources :heise online

Recherche

Vous êtes à jour dans cette vue

Connexion / Inscription
LectureRechercheRadarCadre d'investissement