NOC server templates deployment process
•Transferir como KEY, PDF•
0 gostou•670 visualizações
Recomendados
Mais conteúdo relacionado
Destaque
Semelhante a NOC server templates deployment process
Semelhante a NOC server templates deployment process (20)
Mais de John Willis
Mais de John Willis (20)
Último
Último (20)
NOC server templates deployment process
- 1. Before NOC server templates TAR RPM restarts TAR TAR code, EC2 content pupp deploys et RS studio RS deployment devs deployment S3 yum repo Provision-time builds reconfigs TAR EXE TAR AUTO server TOOLS code templates TAR RPM middleware devs platform CONTROL PROVISION RELEASE system admins
- 2. After process apache/php messaging, memcached queuing mysql app middleware 3rd party yum yum winning.c rundeck om code, "D content, te" e plo metas o mo y" "pr job & jo "Re jenkins yum b leas e" builds dev prod
- 3. Infrastructure as SDLC SVN hud agent cfg yum pup son repo pet packages active users run packages directory deck commands nag splunk ios resource model sys cfg right instance create scale events new node Node a log data CONTROL PROVISION RELEASE
- 4. dtosolutions.com John Willis john@dtosolutions
Notas do Editor
- So the team went to the whiteboard to map out the “as is” picture, to follow the strands of spaghetti \n\nThey uncovered several root causes that were undermining the cause:\n-Changes hit all customers at once => Puppet configs in unversioned S3 buckets\n-Buggy node classification causing provisioning problems = > complex/long node classifier script\n-”Dead boxes” after provisioning => rightscript/puppet ordering problems\n-”my box got clobbered!” => puppet, is it supposed to be on or off?\n-new environment setup was taking longer and longer => from days to weeks because of “fooled by false horizons”\n-”is the system ready yet?” => nobody knows what “ready” means\n- scripts crap out on nodes taken out of commission\n-”software works differently” => rightscale driven compile/installs\n
- \n
- Management infrastructure based on “swap-able” sets of integrated tools\n- Organized into three rough categories: Control, Provisioning, Monitoring\n - Control tools support routine and ad hoc procedures executed as commands/scripts\n - Provisioning tools support package delivery and post install customization\n - Monitoring tools actively check health and collect log data\n\nKey integrations:\n- SVN drives everything in the tool chain!\n- Rundeck synchronizes to RS; must be connected to compute service to know what nodes are provisioned and ready\n- All packages come through yum\n\n\n
- 35 Minutes (3 Minutes) \n