viernes, 14 de septiembre de 2012

Virtualization by Davis: “IBM Distributed Overlay Virtual Ethernet (DOVE) networking” plus 5 more

Virtualization by Davis: “IBM Distributed Overlay Virtual Ethernet (DOVE) networking” plus 5 more


IBM Distributed Overlay Virtual Ethernet (DOVE) networking

Posted: 13 Sep 2012 06:42 PM PDT

IBM is developing its own network virtualization to compete with VMware and Big Switch Networks.
One of IBM's values is innovation and Big Blue doesn't want to be left behind with network virtualization programs, therefore IBM is investing in Distributed Overlay Virtual Ethernet (DOVE): a network architecture for building virtual networks infrastructures, that allows to abstract the physical network infrastructure from hypervisor hosts, to make network changes in software rather than hardware, creating endpoints across the underlying network infrastructure.
DOVE current versions works only with vSphere, but apparently there are future plans to expand support for other hypervisors, among the others KVM and Microsoft Hyper-V
The two competitors VMware, now backed up with new acquisition Nicira, developed a network overlay solution using VXLAN tunneling protocol and Big Switch Networks with japanese start-up Midokura are offering a similar solution.
The IBM DOVE architecture is composed by three components: the DOVE controller, the DOVE service appliance and the DOVE switches deployed on the hypervisor hosts. The gateway function like a router, supplying connectivity for data center interconnects.

According to an IBM technical paper research made by Liane Lewin-Eytan, Katherine Barabash, Rami Cohen, Vinit Jain, Anna Levin:

Networking is currently facing important challenges arising from the advent of virtualization and cloud computing. Broad acceptance of these advanced technologies has raised new networking requirements related to the complex configuration, management and control means needed in order to cope with large scale virtual networks of highly dynamic nature supporting multi-tenancy. Coping efficiently with these requirements has brought to the fore the need to virtualize the network by properly decoupling the logical network functionality from the underlying physical infrastructure. An essential method for enabling such a decoupling and achieve a good abstraction of the network is the use of overlays.



Labels: Big Switch, IBM, virtualization, VMware


This posting includes an audio/video/photo media file: Download Now

Technotes: How to Enable SpeedScreen Latency Reduction for NFuse / Web Interface Applications

Posted: 09 Sep 2012 10:22 AM PDT

Technotes: How to Enable SpeedScreen Latency Reduction for NFuse / Web Interface Applications Citrix Systems
Update feed preferences
This article describes how to enable SpeedScreen Latency Reduction for NFuse / Web Interface applications.       (more)

Products & Solutions | Support | Communities | News | Events | My Citrix
(c) 2012 Citrix Systems, Inc. All rights reserved.


Two virtual machine management secrets of VMware Workstation 8

Posted: 12 Sep 2012 01:05 PM PDT

With a little creativity, VMware Workstation 8 can be used to make quick decisions about virtual machine allocation and more.

Add to digg Add to StumbleUpon Add to del.icio.us Add to Google


Back-to-school quiz: VDI storage and backup

Posted: 13 Sep 2012 05:12 AM PDT

A key component of implementing VDI is getting your storage system and backup right. Make sure your storage knowledge is up to snuff with this quiz.

Add to digg Add to StumbleUpon Add to del.icio.us Add to Google


Your 10 Apps + an AppDNA Trial = Application Compatibility Insights

Posted: 13 Sep 2012 07:01 AM PDT

  Did you know you can perform no-charge application compatibility testing for 10 of your own enterprise applications with the Citrix AppDNA application migration software trial?   If you're just starting to plan your Windows XP migration or looking to add a new virtualization technology, trial the AppDNA application migration software to see how your applications will behave on a new OS or virtualization technology.…

Read More


OSD Successresult and abortresult

Posted: 11 Mar 2010 07:57 AM PST

Hi all!

Don't know if this should go in the sequencing forum or the client forum...here I go...

Wondering if anyone been playing around with the successresult and abort result elements in OSD files. I'm having some trouble getting it to run. I'm running App-V 4.6 on RDS on Win2008R2.

I need to run a vbs script before the application starts to check if execution is allowed based on computer names. I'm exiting my script with wscript.quit 0 or wscript.quit 1 but it seems that the app-v client doesn't care about it and go ahead and launch the application anyway or more likely I'm doing something wrong...

This is an excerpt from my OSD file...

<DEPENDENCY>
 <CLIENTVERSION VERSION="4.5.0.0"/>
                <SCRIPT EVENT="LAUNCH" TIMING="PRE" PROTECT="FALSE" WAIT="TRUE" TIMEOUT="0" SUCCESSRESULT="0" ABORTRESULT="1">
                      <HREF>wscript.exe "\\path\script.vbs"</HREF>
                </SCRIPT>
</DEPENDENCY>

the script looks like this...

Set WshShell = WScript.CreateObject("WScript.Shell")
clientName = WshShell.ExpandEnvironmentStrings("%computername%")

if lcase(clientName) = "mycomputer" then
 msgbox "Not allowed on this computer",vbCritical
        wscript.quit 1
End if
wscript.echo "Moving on"
wscript.quit 0

I know the script executes properly since I get the correct msgboxes / echoes.
If I run the script in a *.cmd file and then check %errorlevel% I will see my returncode...

Do I miss something? Could it be that wscript.quit x doesn't return a real exit code but rather an error code? Isn't <href> supported with abortresult / successresult?

I've mostly looked at this article...

http://support.microsoft.com/kb/930973/en-us


This posting includes an audio/video/photo media file: Download Now

No hay comentarios:

Publicar un comentario