-
Notifications
You must be signed in to change notification settings - Fork 0
Configuration Management Plan
Documents for the project VMAT are located on the github project wiki, located at https://github.com/tiger12506/VMAT/wiki/Configuration-Management-Plan
All documents relating to the project, including binary documents such as pictures will be placed in this repository by using git access. Any minor documentation, such as code comments and the like will most likely remain with the source, and may or may not be duplicated in the wiki repository, depending on the relevancy of the documentation as deemed by team Virtual.
This method of storing documents allow for public access by all, which makes design decisions/readme material available to anyone who may wish to contribute in the future.
We are using a repository stored on GitHub. It is a public repository, which was approved by our client; however, we do not anticipate there being a large demand to fork our code base.
The decision to use Git instead of a version control system we were more familiar with like Subversion was based on experiences with other projects. Git is a distributed system, so it handles local changes a lot better than Subversion, which requires you to post changes directly to the master repository.
Branching in Git also makes experimental changes easier. We can use the master branch to control our stable version, and every time we want to make major changes we create a new branch and merge it all together when it is working correctly. This will make adding and managing new changes much simpler because we will not have a period of downtime where a commit breaks the program and we have the fix the repository before the program works again.
The project repository is kept separate from our wiki repository, which is used for all of the project's documentation. The only documentation in the project repository will be a README file which describes how to operate the program, either as a quick start-up guide or for testing and debugging purposes.
Due to the technical and configurational challenges of creating virtual machines within a virtual machine, team Virtual has procured a physical machine from the client which will run Windows 2008 R2. Installed upon the machine will be VMware Server 2.0 and HyperV both, to minimize the risk of the targeted platform changing.
Physical machine specifications: 250 GB HDD 1 GB RAM
Also, there resides a VM at vmat.csse.rose-hulman.edu which can be used also, as it currently has 2008 R2 running on it with VMware Server 2.0 installed. Though HyperV will not install upon this machine, it would appear that VMware was successful and it will be possible to use it.
These machines will be used to test development of the VMAT project, as an environment is needed where virtual machines can be cloned, initialized with hostname/ip address/etc., and verified for correctness.
More details will be added here when they are discovered.
The end result of this project will be a stable version of VMAT software, written in ASP.NET available in a public repository on github. The client will undoubtedly prefer to maintain ownership of the repository, so it will be transferred to him at time of deployment.
The client will likely use the software by installing it upon their current Windows 2008 R2 server where the VMs are currently managed. The web server will then be available to their employees, who can then request new VM project servers of our software.
Client has machines running IE 6.0, Firefox 3.6 for compatibility testing. Expect machines with XP and 7 to access application with more modern browsers.