Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Jenni Konrad on Apr 20, 2011
Visual Studio Lab Management 2010 is a highly integrated virtualization, development, and testing tool. It combines Visual Studio 2010, the virtualization server Hyper-V 2008, and System Center Virtual Machine Manager (SCVMM). Microsoft initially released Lab Management as a standalone product, but has now integrated it into Visual Studio 2010 Ultimate with MSDN and Visual Studio Test Professional with MSDN.
The inability to reproduce bugs has always been a headache for developers. Lab Management helps streamline this process via rich bug reporting. When testers encounter an error, they can create a snapshot of the virtual environment at that moment: not just a screenshot, but the current state of the application or website and all the servers involved. When a developer receives the bug report, they see the bug in its original state, along with the collected diagnostic information.
The virtual lab environment makes it easier to provision virtual servers, configure complex scenarios, and dispose of them when they’re no longer needed. It’s not even necessary to maintain each configuration during the entire testing process, since checkpoints are attached to bugs; when the developer views the bug, the environment is restored to the point at which the error occurred.
Microsoft introduced this tool to significantly reduce the time and money spent on hardware, server administration, and the development/testing lifecycle. Lab Management is completely integrated into the Visual Studio Team System, making it simpler to configure virtual test labs and delete them when the process is complete. Hyper-V Server’s network isolation eliminates the need to manually configure routing and DNS addressing. Testers can create both manual and automatic test plans, and execute them in multiple virtual environments. With checkpoints, developers no longer have to spend time attempting to reproduce an error, and IntelliTrace logs provide more information than traditional error logging methods.
Lab Management can also be used in physical environments or with different virtualization solutions, such as VMWare. However, features like automatic build deployment and virtual server configuration and templates will not be available on non-Hyper-V platforms.
Troubleshoot Java/.NET performance while getting full visibility in production
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
RDBMS to NoSQL: Managing the Transition
Want to know how software releases can be stress-free and happen with one click? Try Go free!
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
Go: Agile Release Management Solutions. Go enables predictable, defect-free and timely software releases.
This sounds like vaporware. Is the captured application working in a vacuum? Unless it's a standalone thing, you won't be able to capture the state of the entire system, e.g. think web services. Sounds like a product for a niche, a bit like intellitrace.
Eh. It *could* be good. If we had "graceful enhancement" (the opposite of graceful degradation), so we could start w/a simple screenshot (say), get the stack trace(s), get the logs, get the configuration, get the d/b data that was read, and finally, if all else fails, get the entire farking environment; WITHOUT having to go the whole 9 yards from the start.
Also, I wonder what the Java equivalent is?
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
2 comments
Watch Thread Reply