search

dougmcclure / ILA-Open-Beta

Expiriments with ILA and DevOps, IT Operations and Automation Tools
1 stars 1 forks source link

Determine improved naming standards to improve project comprehension. #11

Open c835722 opened 11 years ago

c835722 commented 11 years ago

Doug said .. Can you think of anything we should rename, relocate, etc. I'd like a good naming scheme for the provisioning scripts that shows their function - order - role in a scenario, etc. Same for directories holding stuff unique to one box or scenario.

c835722 said .. I think the script names should reflect the generalisation of the deployment unit they pertain to rather than the product name. The product names (which keep changing) defeat people trying to understand what the "solution" provides. So my suggestion would be to refactor the provisioning scripts around how the deployment unit participates. eg. syslog-server, application-server. These terms the vast majority of the public understand whereas SCAA and ILA not so much.

Further, this is part of ongoing project refactoring to continuously improve the readability and thus simplicity of the project

dougmcclure commented 11 years ago

Would this make sense for provisioning script naming?

targetsystem_purpose_version

box1_prereqs_v1 : download & store (or install) prereqs box1_installdriver_v1 : install the driver box1_exportLFA_v1 : extract the LFA from the driver box1_installscenario1_v1 : install the scenario1 updates box1_installscenario2_v1 box2_prereqs_v1 : download & store (or install) prereqs box2_installLFA_v1 : install the LFA box2_installscenario1_v1 : install WebSphere Liberty, sample app, LFA configurations box2_installscenario2_v1 box2_installscenario3_v1 box3_prereqs_v1 : download & store (or install) prereqs box3_installsyslog_v1 box3_installscenario3v1 box4

c835722 commented 11 years ago

Some random thoughts. Prefer no version suffixes at the end of scripts. Let git look after versions. Prefer fewer scripts to more. Like box* prefix. Need to determine if we can either find or build a base box that has all the pre-reqs built in. That way, scripting is easier going forward and the user experience less complicated (I wonder whether there is a public vagrant base box binary repo somewhere. Alternatively would IBM sponsor some download bandwidth from an ftp server). If we assume a custom base box then the custom scripting might be better off moved to a chef/puppet. (Hmm, perhaps a thought to far ATM)

dougmcclure commented 11 years ago

I'll be happy to host a custom base box on my personal servers, we'd just need to build it.

What's the lowdown on RedHat boxes and licensing, etc. Can they be built and hosted and whomever uses them needs to get support/license/redhat network subscription on their own?

Doug

On Sun, Apr 28, 2013 at 10:24 PM, c835722 notifications@github.com wrote:

Some random thoughts. Prefer no version suffixes at the end of scripts. Let git look after versions. Prefer fewer scripts to more. Like box* prefix. Need to determine if we can either find or build a base box that has all the pre-reqs built in. That way, scripting is easier going forward and the user experience less complicated (I wonder whether there is a public vagrant base box binary repo somewhere. Alternatively would IBM sponsor some download bandwidth from an ftp server). If we assume a custom base box then the custom scripting might be better off moved to a chef/puppet. (Hmm, perhaps a thought to far ATM)

— Reply to this email directly or view it on GitHubhttps://github.com/dougmcclure/ILA-Open-Beta/issues/11#issuecomment-17147782 .

c835722 commented 11 years ago

If this were to occur (downloaded from a personal server non-commercial non-IBM) I think the CentOS / redhat-releases hack you have in place currently suffices. Further, could an enhancement request be made for support of SCAA on CentOS I wonder? WRT to building the box, well essentially thats already done. That is, it would just be uploading the current customised CentOS64 virtual-instance-image and then changing the Vagrantfile to source from the new download server. Flip side on that personal server of yours, who pays for the bandwidth? is it bandwidth limited? etc.