Reading Time: 14 minutes

This is an article realized for StarWind blog and focused on the design and implementation of a ROBO infrastructure. See also the original post.

Introduction

The fabric of SAN (means Storage Area Network) with Fibre Channel solutions have always been a dedicated network, with dedicated components (like FC switches).

But, starting with iSCSI and FCoE protocols, the storage fabric could now be shared with the traditional network infrastructure, because at least level 1 and 2 have a common Ethernet layer (for iSCSI also layer 3 and 4 are the same of TCP/IP networks).

continue reading…

Reading Time: 3 minutes

In response to issues identified by external researchers, Intel has performed an in-depth comprehensive security review of our Intel® Management Engine (ME), Intel® Server Platform Services (SPS), and Intel® Trusted Execution Engine (TXE) with the objective of enhancing firmware resilience.

As a result on 20th Nov 2017, Intel has identified security vulnerabilities that could potentially place impacted platforms at risk.

In response to issues identified by external researchers, Intel has performed an in-depth comprehensive security review of its Intel® Management Engine (ME), Intel® Trusted Execution Engine (TXE), and Intel® Server Platform Services (SPS) with the objective of enhancing firmware resilience.

continue reading…

Reading Time: 2 minutes

Starting with vSphere 6.5 you have some limitations with OVF format. For example you cannot export in OVA format anymore.

Note that you can still import in OVF or OVA. But you may have also some issues in OVF import.

continue reading…

Reading Time: 2 minutes

Microsoft ufficializza un nuovo servizio (al momento in preview) su Azure che risponde al binomio VMware e Amazon (relativo all’offerta VMware Cloud on AWS).

La soluzione si chiama VMware in Azure, e si tratta di un ambiente vSphere installato bare-metal all’interno dei datacenter Azure. Non ci sono dettagli architetturali, come ad esempio il numero di host minimi (su VMware Cloud on AWS è 4), il tipo di storage utilizzato (si utilizzerà la Cloud Foundation e quindi vSAN?). L’unica certezza è che l’intero servizio è implementato tramite partner VMware e non direttamente tramite VMware.

continue reading…

Reading Time: 2 minutes

VMware has recently released the new verion of vRealize Network Insight (vRNI) 3.6 that adds key capabilities that enhance network and security visibility in customers’ SDDC and AWS environments, and that enable customers to confidently deploy, manage and scale their VMware NSX deployments.

VMware vRealize Network Insight delivers intelligent operations for software-defined networking and security and helps customers build an optimized, highly-available and secure network infrastructure across multi-cloud environments. Also it can accelerates micro-segmentation planning and deployment, enables visibility across virtual and physical networks and provides operational views to manage and scale VMware NSX deployments.

continue reading…

Reading Time: < 1 minute

Finally, one year after Broadcom announced the intention acquire Brocade the deal is completed: Broadcom Limited announced that it has completed its acquisition of Brocade. With the close of this transaction, Brocade’s storage area networking (SAN) business is now a highly strategic part of Broadcom’s enterprise storage portfolio.

This is also an important milestone toward Broadcom completing the proposed divestiture of Brocade’s Ruckus Wired (ICX) and Wireless business to ARRIS International PLC (“ARRIS”). ARRIS has stated that it expects to close its acquisition once final regulatory approvals are complete.

continue reading…

Reading Time: 3 minutes

Nell’ambito della virtualizzazione server, i principali hypervisor di tipo 1 (o bare-metal) sono: VMware ESXi, Microsoft Hyper-V, e, per il mondo Linux, Xen e KVM.

Per quanto riguarda il public cloud, in particolare i servizi di tipo IaaS, al momento i più usati sono Xen (poiché AWS ne utilizza una versione customizzata) e Hyper-V (visto che è alla base di Azure). Cambia tutto nell’e infrastrutture on-prem poché ESXi (e vSphere) rimane la soluzione più utilizzata, con Hyper-V e KVM che seguono, ma ancora da lontano.

Notare che sia Xen che KVM rappresentano in realtà una famiglia (o una tecnologia), non un prodotto specifico: ogni distribuzione o ogni vendor ha la sua “versione” do uno o dell’altro. Se invece parliamo di XenServer allora ci si riferisce al prodotto specifico di Citrix basato su Xen (Citrix aveva acquitato il brand Xen commerciale tanti anni fa), oppure se parliamo di RHEV allora ci si riferisce all’implementazione di RedHat basata su KVM (RedHat è stata tra le prime a “sponsorizzare” KVM a discapito di Xen).

continue reading…

© 2025-2011 vInfrastructure Blog | Disclaimer & Copyright