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 Michael Floyd on May 11, 2011
As the discussion in Agile development moves from continuous integration (CI) to continuous deployment, CI servers are doing more to automate the overall build process. Atlassian, which today released Bamboo 3.1, has implemented a new feature called Tasks that the company hopes will aid developers in their continuous deployment efforts.
A Task is basically the instruction or set of instructions being executed as part of a build. For instance a task can be a shell command, script or a Maven goal. Tasks, which now replace Builders in Bamboo 3.0, can be used to configure a job, execute a script, upload files to a server or generate documentation. One advantage Tasks have over Builders is that multiple tasks can run in a single job, allowing each task to access to the same build directory. This makes it easier to, for example, copy files prior to a task being executed.
Tasks are implemented as plugins. Atlassian has ported their available Builders to Tasks, and have completely rewritten their .Net plugin. The plugin supports Visual Studio and MSBuild, Nant, MSTest (runner and parser), MBUnit and NUnit. Atlassian is recommending that developers also convert their custom plugins.
In addition to Tasks, Bamboo has extended its support for global variables to include Plan Variables and added support for parameterized builds. Plan variables are scoped within a Plan, and can be used within either scripts or Tasks in different jobs. One welcomed feature is that unlike Bamboo globals, Plan variables do not require administrator privileges to create them.
In an interview posted today, Jean-Michel Lemieux, Atlassian’s newly appointed VP of Engineering, said:
The engineering teams in Atlassian are already working hard on optimizing our own processes for development velocity and adding features to our products that help others do the same. For example I'm really excited with the recent additions to Bamboo in the area of Continuous Deployment which helps teams streamline their build processes and get software deployed and available to users as quickly as possible.
Bamboo includes several additional enhancements. For example Atlassian has completely revamped the plugin manager, dropping in the Universal Plugin Manager (UPM) already bundled in with the company’s Jira and Confluence products. The UPM allows developers to manage existing plugins, and update all plugins with just a single click.
Other features include improved Windows process handling, new Bitbucket support, extended Github support, Gravatar support, and support for EC2 spot instances for those running Elastic Bamboo.
Deliver quality code quicker with "Go" Agile release management
Continuous Delivery: Anatomy of a Deployment Pipeline
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
Deliver quality code quicker with "Go" Agile release management
Branching & Merging Efficiently: A Guide to Using Process-Based Promotional Patterns
Go: Agile Release Management Solutions. Go enables predictable, defect-free and timely software releases.
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.
No comments
Watch Thread Reply