fishnix

16:03:11,723 INFO  [[/testapp]] Warning: no min runtimes specified.
16:03:11,725 INFO  [[/testapp]] Warning: no max runtimes specified.
16:03:11,728 INFO  [[/testapp]] An exception happened during JRuby-Rack startup
method 'to_yaml' not defined in Object
--- System
jruby 1.6.5 (ruby-1.9.2-p136) (2011-10-25 9dcd388) (Java HotSpot(TM) 64-Bit Server VM 1.6.0_29) [darwin-x86_64-java]
Time: 2011-11-14 16:03:11 -0500
Server: JBoss Web/2.1.11.GA
jruby.home: classpath:/META-INF/jruby.home

fishnix

Summary:

 rvm use 1.9.2
 brew install libxml2 libxslt libiconv
 brew link libxml2 libxslt libiconv
 gem install nokogiri 
 gem install knife-rackspace

===================
Scratch:

fishnix

knife ec2 server create -I ami-41814f28 -d fedora13-gems -f m1.large -Z us-east-1a -x ec2-user

knife rackspace server create -S s2.example.com -N s2.example.com -f 1 -I 118 -d centos6-fishnix -r "role[generic],role[lamp],recipe[users::sysadmins]"

fishnix

## iRule to select pool and persistence method when all Exchange Client
## Access HTTP-based services are accessed through the same BIG-IP virtual
## server. This iRule will use an HTTP header inserted by a BIG-IP Edge
## Gateway for persistence (if that header is present); otherwise it will
## set persistence according to traditional methods.


## Although it is possible to send all connections to the same pool,
## advanced health monitors generally check only a specific connection
## service. In this example iRule, we send each service to its own pool;

fishnix

when RULE_INIT {
  # Use a local array to configure SNAT addresses.
  # These addresses do not need to be defined in a SNAT pool or elsewhere;
  # they simply need to be free IP addresses LTM can use to as a source
  # for server-side connections, and are typically on the same subnet as
  # the pool members. In this example, we use three addresses. Replace
  # these with free IP addresses appropriate to your network topology.
  # Follow the pattern of the existing addresses to add more than three.
  set static::snat_ips(0) 10.0.0.1
  set static::snat_ips(1) 10.0.0.2

fishnix

when HTTP_REQUEST priority 100 {
  switch -glob -- [string tolower [HTTP::path]] { 
    "/ews*" {
      if { [HTTP::header exists "User-Agent"] } {
          log local0. "EWS traffic,[IP::client_addr],[HTTP::header User-Agent]"
      } else {
          log local0. "EWS traffic,[IP::client_addr],No User-Agent"
      }
      if { [HTTP::header exists "Authorization"] } {
          log local0. "EWS traffic,[IP::client_addr],Authorization Header"

fishnix

ltm rule foobar.example.com_deployment_guide_persist {
  ## iRule to select pool and persistence method when all Exchange Client
  ## Access HTTP-based services are accessed through the same BIG-IP virtual
  ## server. This iRule will use an HTTP header inserted by a BIG-IP Edge
  ## Gateway for persistence (if that header is present); otherwise it will
  ## set persistence according to traditional methods.


  ## Although it is possible to send all connections to the same pool,
  ## advanced health monitors generally check only a specific connection

fishnix

git clone [email protected]:fishnix/Serendipity.git -b 1.6
cd Serendipity
git checkout -b upstream/1.6
git remote add upstream https://github.com/s9y/Serendipity.git
git pull upstream 1.6
git checkout 1.6 
git merge upstream/1.6
git push

fishnix

dhcp-128-36-182-202:yale-master-feature fish$ mvn install
[INFO] Scanning for projects...
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building yale-master-feature feature 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] >>> features-maven-plugin:2.2.5:generate-features-xml (generate-features-xml) @ yale-master-feature >>>
[INFO] 
[INFO] <<< features-maven-plugin:2.2.5:generate-features-xml (generate-features-xml) @ yale-master-feature <<<

fishnix

[INFO] 
[INFO] --- features-maven-plugin:2.2.5:generate-features-xml (generate-features-xml) @ yale-master-feature ---
[INFO] Step 1: Building list of provided bundle exports
[INFO] ...done!
[INFO] Step 2 : No Bundle file supplied for building list of exports
[INFO] ...done!
[INFO] Step 3 : Discovering bundles in Maven dependencies
[INFO]   Discovered org.apache.karaf:org.apache.karaf.main:jar:2.2.2-fuse-04-06:compile
[INFO]   Discovered org.apache.karaf:org.apache.karaf.client:jar:2.2.2-fuse-04-06:compile
[INFO]   Discovered org.apache.aries.testsupport:org.apache.aries.testsupport.unit:jar:0.3:compile