Lixivial

namespace Tools
{
    using System.IO
    using Perforce.P4;

    public class PerforceCopy
    {
        private static void Copy()
        {
            const string serverString   = "10.10.0.151:1666";

Lixivial

var exclusionList = new List<string>(new string[] { "projects-403", 
								 "projects-547", 
								 "projects-561", 
								 "projects-562", 
								 "projects-961", 
								 "projects-645", 
								 "projects-897", 
								 "projects-643", 
								 "projects-517",
								 "projects-518",

Lixivial

15:33:29	→ miniLixi (~Jesse@71-10-86-62.dhcp.roch.mn.charter.com) has entered the channel.
15:33:55	<@Lixivial> miniLixi: qstat 75.126.234.42:26000
15:33:57	<miniLixi> Galt's Gulch - CTF - TX, USA 20 24 pushmectf mshade.org:26000 \n
15:33:58	<miniLixi> 75 *A*Blackmushroom -666\n
15:33:58	<miniLixi> 64 12 Angry Men -666\n
15:33:58	<miniLixi> 82 MossDemos -666\n
15:33:59	<miniLixi> 27 [+]death/angel -666\n
15:33:59	<miniLixi> 50 <.< -666\n
15:34:00	<miniLixi> 91 neurocide -666\n
15:34:02	<miniLixi> 97 [o]SoulBringer 0\n

Lixivial

22:24:51    <@Lixi|away> miniLixi: qstat -c masters -g nexuizm -m
22:25:01    <miniLixi> Here are lixi|away's results:
22:25:01    <miniLixi> MASTER    dpmaster.deathmask.net:27950
22:25:01    <miniLixi> [Nexuiz Ninjaz] Race - Washington DC, US - GigE   0   16  streetrace  208.43.251.170:26004
22:25:02    <miniLixi> +++NEX CTF DesertCastles Server /MI/USA+++    0   10  desertcastles6  72.52.190.155:26004
22:25:02    <miniLixi> !BAF!MINSTAGATOR (minsta, hook)   7   32  farewell_laserfun   69.9.46.110:26000
22:25:02    <miniLixi> 30    Stevibo     3
22:25:04    <miniLixi> 85    !BAF!Will Riker     2
22:25:06    <miniLixi> 86    [GT]ColdVodka   7
22:25:08    <miniLixi> 128   Big Ron     2

Lixivial

#!/bin/bash
# old_logs.sh -- A simple import script to import old tarball logs into a new awstats site config.
# by Lixivial (Jesse Pearson) 
# contact: jesall@gmail.com
# or irc.quakenet.org/#prae.nexuiz
#
# Script arguments:
#
# config -- awstats config name sans .conf
# access_log -- the path to the access log with wildcards

Lixivial

#!/bin/bash
# Daily Backup Confluence Bridge
# jesse pearson
#
# Purpose:
# Used to send the Amanda backup logs into a Confluence page and
# attach a PDF output summary to the given page.
#
# Dependencies:
# cadaver

Lixivial

Basic document management deployment.

eapp and isms both use inforouter for document management facilities; the front-ends for these are scaled 
independent of the UI front-ends. The only bottleneck and single point of failure is the metadata db, 
which by Inforouter's definition must be a single database.

The inforouter fs cluster is still slightly undefined at the moment. I'm hoping we can use any standard filesystem 
providers. If we were to use s3, we may need an arbitration subsystem to act as a gatekeeper and translate inforouter calls
into HTTP REST calls.

Lixivial

iSMS Production Diagram

This diagram is a fairly straightforward load balanced web tier with a clustered database tier scenario. Since our usage expectations can be modeled and predicted there is little need for a distinct hardware load balancer resident between web and database tiers. I think we can generally trust the SQL Server controller node(s) to sufficiently route db traffic to the correct partitioned cluster. Since elasticity is not a primary concern, session coherence will be managed with sticky sesssions on the load balancers. The prevailing requirement on the web, database (and likely domain controller) servers is that it'll be running Windows. The mail relays may be Linux-based running sendmail or postfix.

All connections to public-facing infrastructure -- whether they be over HTTPS or LDAPS -- are restricted to Scholarship America public IP addresses. This can be achieved either at each constituent endpoint (web and backup domain controller) or directly via the VPN box. Our eapp environment cur

Lixivial

SA Auth Environment
  
The purpose of this environment is to take internal directory services and expose them to constituent
environments in a secure and scalable way. 

On the internal side (designated SA LAN), we have our domain controller forest. This is represented by 
two domain controllers at the moment whose sync process is not outlined in this diagram.

For the external auth environment, we have n-number of backend authentication storage providers. Backend
providers could include:

Lixivial

Code migration and deployment procedures

Outlined below is how code is migrated from branches to trunk with flagged notes outlining where the target 
environments actually are.

It also outlines various scenarios, and base term definitions can be found below the diagram.

Diagram                                                       
                                                     
       +--------------------------------+