fenneh

<!- .... ->
<log4net>    
    <appender name="RollingLogFileAppenderLogstash" type="log4net.Appender.RollingFileAppender">
      <encoding value="utf-8" />
      <!--该目录必需有 IIS用户 写权限-->
      <file value="X:/var/log/[app_name]/logfile.log" />
      <appendToFile value="true" />
      <rollingStyle value="Date" />
      <lockingModel type="log4net.Appender.FileAppender+MinimalLock" />

fenneh

## Consumer Throughput: Single consumer thread, no compression
## Consumer Throughput: 3 consumer thread, no compression

bin/kafka-consumer-perf-test.sh --topic benchmark-3-3-none \
--zookeeper kafka-zk-1:2181,kafka-zk-2:2181,kafka-zk-3:2181 \
--messages 15000000 \
--threads 1

fenneh

Producer

Setup
bin/kafka-topics.sh --zookeeper esv4-hcl197.grid.linkedin.com:2181 --create --topic test-rep-one --partitions 6 --replication-factor 1
bin/kafka-topics.sh --zookeeper esv4-hcl197.grid.linkedin.com:2181 --create --topic test --partitions 6 --replication-factor 3

Single thread, no replication

bin/kafka-run-class.sh org.apache.kafka.clients.tools.ProducerPerformance test7 50000000 100 -1 acks=1 bootstrap.servers=esv4-hcl198.grid.linkedin.com:9092 buffer.memory=67108864 batch.size=8196

fenneh

If you are adventurous, here the process to have Hipchat working in your favourite IRC client:

• First, you need to install the IRSSI XMPP plugin. You can find this package in your distribution, but I advice you to use the latest version possible if you don't want this segfault errors everywhere: http://gna.org/bugs/?20487

• The first version released after the patch fix is the 0.52-2 that you can download here: https://launchpad.net/ubuntu/+archive/primary/+files/irssi-plugin-xmpp_0.52-2_amd64.deb (No dependencies so it should work in any Debian distributions)

• Once it's done. You have to configure IRSSI. Either via command line, either manually in the ~/.irssi/config file. I followed this thread: http://cybione.org/lists/irssi-xmpp-list/msg00339.html and it was pretty successful.

• You can find your XMPP access on your HipChat account on this page: https://boxuk.hipchat.com/account/xmpp. Everything has a XMPP account id. Even the Rooms name. So you have to use these instead of the real names for your I

fenneh

<#
.Synopsis
   Updates the Step Templates used on Deployment Processes to the latest versions
.DESCRIPTION
   Step templates can be updated from the library on Octopus, but that doesnt mean that the Deployment processes using that template will start using the latest version right away. Normally, the user would have to update the step template on each deployment process manually. This script takes care of that.
.EXAMPLE
   Update-StepTemplatesOnDeploymentProcesses -ActionTemplateID "ActionTemplates-3" -OctopusURI "http://localhost" -APIKey "API-RLMWLZBPMX5DRPLCRNZETFS4HA"
.EXAMPLE
   Update-StepTemplatesOnDeploymentProcesses -AllActionTemplates -OctopusURI "http://Octopusdeploy.MyCompany.com" -APIKey "API-TSET42BPMX5DRPLCRNZETFS4HA"
.LINK

fenneh

#
# Assumptions
#
# 1. If you have a Octopus release deployed, say 1.0.0.73, there is a git
#    tag set for that commit in GitHub that is "v1.0.0.73".
#
# 2. You have TeamCity label each successful build in GitHub with the format
#    "v{build number}. Sidenote: it appears that TeamCity only labels the
#    default branch, but not feature branches.
#

fenneh

Set-Alias MSBuild (Join-Path -Path (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\MSBuild\ToolsVersions\2.0").MSBuildToolsPath -ChildPath "MSBuild.exe")

Set-Alias MSBuild (Join-Path -Path (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\MSBuild\ToolsVersions\3.5").MSBuildToolsPath -ChildPath "MSBuild.exe")

Set-Alias MSBuild (Join-Path -Path (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0").MSBuildToolsPath -ChildPath "MSBuild.exe")

fenneh

param
(
  [string] $EnvironmentName,
	[string] $Version,
	[string] $ProjectName,
	[string] $OctopusApiKey,
	[string] $OctopusServerUrl,
	[string] $ReleaseNotes
)

fenneh

<Project DefaultTargets="CopyOutputs;DeployService" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="4.0">

  <!-- These settings control what the service's name, description etc appear in services.msc task panel. -->
	<PropertyGroup Label="ServiceMetaData">
		<ServiceName>ShinyNewService</ServiceName>
		<ServiceDisplayName>Shiny New Service</ServiceDisplayName>
		<ServiceDescription>A shiny new service, that changes the world for the greater good.</ServiceDescription>
	</PropertyGroup>

	<Choose>

fenneh

Set-StrictMode -Version Latest

$libPath = (Split-Path -Parent $MyInvocation.MyCommand.Definition)
Import-Module $libPath\SecurityLib.psm1

function New-WindowsService {
  param
	(
		[Parameter(Mandatory=$True,Position=0,HelpMessage="The name of the Windows Service")]
		[string]$serviceName,