----- Meeting Notes (1/4/12 15:45) -----Ask who is or has been using AWS, etc… who is on Visual Studio 2010… etc. etc.
Describe current deployment scenarios. Trying to duplicate and prepare identical environments for development, test, UAT, and production. Multiple deployment configurations. Several points where failure can occur.
Testers, or QA, are often strapped with the extremely difficult task of duplicating environments and deploying software over and over again to determine stability & quality of a release. This is ridiculously difficult.
How are prototypes setup in current environments?Dedicated servers? A few virtual machines on a physical box?
Faster, reliable, and consistent deployments.Configuration or programmatic based systems deployments.Platform based system deployments that remove the operating system as a deployment concern. “Turnkey”
Prototypes need more robust environments, data storage options, and clearer transitions to the next stage.
Test and QA need environments that can be scripted, easily duplicated, rebuilt, and generally thrashed without worry.
…delineate how issues others may have might be resolved by utilizing this prospective tool.
AWS Toolkit which includes the toolkit for Visual Studio & the AWS SDK.
.NET 2.0+ supported for using the AWS SDK. .NET 3.5 SP1+ supported w/ the Toolkit.
The toolkit supports Visual Studio 2008, with the required 3.5 SP1 update, and Visual Studio 2010 as installed.
Do use the tooling for local development, testing, and related activities.Don't use it as an excuse to not build testing, verification, or other insurance into your architecture.Do use the tooling to view, manage, or otherwise manipulate your development environment.Don't use the VS Toolkit to manage or otherwise manipulate your production instances, storage, or otherwise.Do use the toolkit to stay in your primary productive environment, Visual Studio.Don't load the toolkit and never use it!Don't deploy directly from Visual Studio to production.Don't leave integration points until deployment to test.Don't leave yourself without a rollback strategy.Do setup appropriate environmental states; dev, test, prod...Do setup continuous integration.Do setup continuous deployment.Do have monitoring setup in instances, for the architecture, and at any other feasible point.