text:
Hello, everybody! After a successful three season run in its first year of existence, the need for a second Madden league here on CAG was proven to be true. Comprised mainly of players who felt they were still learning the game, the "JV League" was born.
Throughout those three seasons, members shared tips, discussed strategies, and helped each other improve their skills. When all was said and done, most of us felt that we had taken great strides in our understanding of the game, and weren't so overmatched against more experienced Madden players.
This year, I'd like to build off of that. While this will definitely still be a place for people who feel like they're still learning the game, the bigger emphasis will be on sportsmanship, communication, and sharing tips to help each other improve. In that spirit, I made a joke about changing the name from the "JV League" to the "Gentlemen's League", and ya know what...I'm going to run with it (however, choosing a stripper name that starts with the same letter as your team name to represent yourself is entirely optional, lol).
I'd like the league to be as self sustaining as possible: no nonsense, no constant reminders to play right, few warnings given, a non-negotiable expectation to keep up with the thread, being responsive to PM's, etc. And if people show any difficulty sticking to that, they're gone. What I'd like to avoid is the whole mentality of caring more about winning than caring about playing right. Also, having so and so's friend's, brother's, uncle who likes Madden, but has no idea what this thread is or even what CAG is can be a hinderance more often than not. If you want to be a part of the league, be a part of the league.
I've also been mulling a few settings changes in an effort to make the games as fair as possible. All of these things will be discussed in the thread though before anything is set in stone. So, definitely, anybody who thinks the Gentlemen's League would be a good fit for them, feel free to voice your interest, introduce yourself, weigh in on league policies, bounce around some ideas, etc. I'm excited about the growth that we could see this year, and look forward to us all enjoying some good, friendly, competitive, productive football together.
League Website
Releasing a Player From the Website
1. Log in
2. Click on "My Team"
3. Find the player you want to cut
4. Click on him to flip the card over
5. Click "View Profile"
6. Use the drop down box in the top right corner to select "Release Player"
League Settings
League Rules and Policies
Two Point Conversions
Scrambling QBs
Moving Players to Different Positions
Onside Kicks
Squib Kicks
Big Lead in the 4th Quarter
Games Against the CPU
Free Agency
Contract Length
Restructuring Contracts
Strike Policy
League News
9/4/12 - Disconnect Issue and League Policy
8/28/12 - Launch Day! Proposed Settings and Rules
8/24/12 - CAG League Sports: Madden 13 Gentlemen's League Team Selection Order
8/5/12 - Team Selection Criteria
Team | CAG Name (click to send private message) | XBL Gamertag | Time Zone | Availability
Any team listed as *OPEN* may be taken by a new member
Buffalo Bills X | GpNinja | GpNinja | CST | I can play from about 5pm to midnight Except Wend,Thursday,Saturdays
Miami Dolphins | Matt Young | X Matt Young X | PST | ???
New England Patriots | AllenScribe | XboxChromosome | CST | Generally on around 7 p.m. through the week, and all weekend. Pretty flexible with hours as I work from home most days
New York Jets | dr0ppinL0adz | Z stepano Z | CST | Weekday Evenings (except when NFL is on Monday Night Football and Thursday Night Football) / Saturday Afternoons
Baltimore Ravens | Konfusion | KTrainThomas | ??? | ???
Cincinnati Bengals | DVO21 | DVO21 | CST | monday- thurs 6 pm till 9 pm, friday 6 pm till midnight saturday-sunday whenever usually works until about midnight
Cleveland Browns | Ultimate Matt X | Ultimate Matt X | EST | ???
Pittsburgh Steelers | HooRox | DarkSabreFury | ??? | ???
Houston Texans | docb9110 | docb9110 | CST | ???
Indianapolis Colts | *OPEN*
Jacksonville Jaguars | DarkTower80 | DarkTower80 | MST | Eveniings
Tennessee Titans | n8rockerasu | n8rocker82 | CST | Sun - 11AM-9PM CST, Mon-Thu - 5-9PM CST, Fri - 5PM-2AM CST, Sat - anytime
Denver Broncos | DarkRider | BrownWing | EST | ???
Kansas City Chiefs | sicsonic | sicsonic | ??? | usually 2pm-2am everyday except most Fridays and Saturdays
Oakland Raiders | Flyersfan | PsychedelicRock | ??? | ???
San Diego Chargers | Zolor23 | Zolor23 | EST | Basically any day, nights
Dallas Cowboys | njrockpd | Harrybodyshots | ??? | ???
New York Giants | jbake_11 | bakenator11 | EST | Nights and Weekends
Philadelphia Eagles | scrub0bk | xscrubo | EST | weeknights from 7-10, some weekends during the day as well
Washington Redskins | JoelyPoley | FattyMcSweaty | EST | Mon-Fri anytime after 7pm eastern, Generally anytime on Saturday and Sunday
Chicago Bears | pitfallharry219 | pitfallharry219 | EST | ???
Detroit Lions X | perdition(troy | the joy of troy | CST | Weekdays 4:30pm-10:00pm, Weekends anytime before 5:00pm
Green Bay Packers | *OPEN*
Minnesota Vikings | KasterDB | KasterDB | EST | Mon, Tues, Fri - between 3:30-11 PM, Wed - between 2-10 PM, Thur - between 5-11 PM, Sat/Sun - 10 AM to 10 PM
Atlanta Falcons | slofton | IceBoundToast | EST | 8am to 10am everyish day. After 7pm on my weekens. Just contact me for info.
Carolina Panthers | staticz | staticzv2 | CST | ???
New Orleans Saints X | Superstar | sgmsuperstar | ??? | ???
Tampa Bay Buccaneers | GamerDude316 | Cydoniac | EST | Sun: flexible during the day till about 10:30 PM EST. Mon-Thurs: 5:30-10:30 EST. Fri: Anytime after 5:30 EST. Saturday: Generally flexible (but please PM to set up a specific time as thats usually when I make plans with the girlfriend or the family).
Arizona Cardinals | billymcdugal | BillyMcDugal86 | EST | Mon and Thurs: 9a-10a. Tues and Wed: 9a-10:30a. Fri: 9a-11a, Sat: nights are generally good. Sun: any time
San Francisco 49ers X | yo soy el tiger | yo soy el tiger | ??? | ???
Seattle Seahawks | Lexxon | Gumbill | EST | Weekdays after 4PM, Weekends vary but generally afternoon or nights
St. Louis Rams | *OPEN*
*X = Strike
Waiting List
Past Champions
Madden 13
Season 1 - Miami Dolphins (Chetty12)
Season 2 - Detroit Lions (perdition(troy)
Madden 12
Season 1 - Green Bay Packers (pitfallharry219)
Season 2 - Green Bay Packers (pitfallharry219)
Season 3 - New York Giants (lvpatriots)
Edited by CAGLeagueSports, 17 June 2013 - 07:02 PM.


text: Sadly, today is LFMF's last update has come FAILers. Please enjoy these last batch of embarrassing tips, and remember that all your previous helpful LFMF lessons are staying here on this site. There's a burning in our eyes, but we're going to pretend it's just from cutting up jalapeños earlier. Thank you all.

subset: commoncrawl


text:
In the first week of the single-stream recycling program, Durango collected about three times the amount of recyclables compared to an average week in its previous source-separated program, or 70 bales of recyclables compared to about 25 bales, said Mary Beth Miles, the citys sustainability director.
Figures on volume or weight of the recyclables were not available Monday because the recyclables wont be measured or weighed until shipped to a broker in Murray, Utah, later this week for resale as a commodity.
Single stream is so popular that 200 residents are on a waiting list to get a new single-stream container next month because the city has run out of the first of batch of 2,000 containers. Residents need the new containers to participate in single stream.
While the response has been enthusiastic, Miles said residents are still learning the program, making mistakes such as putting glass bottles and jars into the single-stream container or bagging their recyclables in plastic.
Glass cannot be accepted because it will shatter and contaminate the rest of the recyclables, bringing down their commodity value.
Instead, glass must be taken to one of the four drop-off sites around town: Wagon Wheel Liquor, north City Market, Fort Lewis College or the Durango Recycle Center on Tech Center Drive.
Plastic bags are not accepted because they are not recyclable and can cause problems during the processing, such as getting caught inside the baling equipment.
Unlike garbage, theres really no need to bag the recyclables, Miles said.
If residents still prefer to bag their recyclables, she suggested they use paper bags but emphasized that the city cannot take other paper products such as paper towels, tissues or dirty paper plates.
Residents who put the wrong materials in their containers could get a flier explaining how the system works. Wrong materials in the containers also add to the workload and hurt the efficiency of the program, Miles said.
Durango has converted its drop-off site to new single-stream containers as well as containers still designated for glass and cardboard.
In a few months, however, when improvements are completed at the recycle center, the single-stream containers will be removed from the other drop-off sites around town.
Noncity residents will be charged $1 per 60-gallon container of material they take to the Durango Recycling Center. City residents wont be charged for dropping off their materials there because all city households will be charged a $3 monthly service fee for single-stream beginning in April.
Apartment and condominium residents might appreciate the citys updated trash and recycling ordinance, which requires all multi-family residences of eight dwelling units or more to provide residents with the opportunity to recycle single-stream material and glass.


text:
NEW YORK (AP) — They are the self-proclaimed "Most Hated Band in the World," and now they're bringing their own theater of the absurd to the Fuse Network with the aptly titled "Insane Clown Posse Theater."
For 24 years, Joseph Bruce and Joseph Utsler have taken on the persona of wicked clowns, transforming themselves into their alter egos, Violent J and Shaggy 2 Dope.
On their weekly forum, the Detroit-area rappers critique all things pop culture, claiming to bring an outsider's perspective "as people not involved with pop culture." A good part of the show has the guys critiquing music videos, much like Beavis and Butthead from a generation ago.
"Maybe this is conceited, but I don't care," Bruce said. "This is what we believe right here. Nobody is qualified to do something like this as ICP because ICP is the only group in the position in the history of rock 'n' roll that ever sold as many millions of records as we had and had as much success as we've had and it's still considered a joke. It's still considered the most hated band in the world."
With a sardonic smile, he added: "We love to be hated."
Perhaps that's just when it comes to their music because both want the show to go beyond their infamous Juggalo fan base. Throughout their long career, what the duo had lacked in terms of a mainstream audience was overshadowed by their dedicated, clown-faced fan base known as Juggalos.
A portion of this vast subculture has come under attack in recent years, and at one point the FBI had classified them as a "gang threat." The band filed a lawsuit that was eventually settled, saying that a majority of Juggalos are law-abiding folks who are simply misunderstood.
"Calling them a gang is people who fear what they don't understand," Bruce said.
Utsler added: "It's a huge body of people. In any group that large you're going to have people that aren't the most fantastic people in the world. You're going to have awesome people. So how can you say just because, like, there is a group of kids that happen to be Juggalos that are in a gang that you can say like, little Jimmy Beaver from Iowa in the cornfields is a gang member because he's a Juggalo? That's ridiculous. It's stupid."
The band started to gather this fan base in the mid-1990s with the song "The Juggla," and started calling people around them Juggalos. The name stuck and the fan base grew.
As for "Insane Clown Posse Theater," the guys have poked fun at videos by Miley Cyrus, D'Angelo, Macklemore & Ryan Lewis, and Christina Aguilera. Besides watching music videos, they have a different guest star each week, make fun of red carpet photos and poke fun at different trends. One thing that they won't do is talk about news.
"I don't care about a royal baby," Utsler said. "I don't care about Detroit going bankrupt. I'm just living. And I don't know all the details. I don't know politics, who caused it or why it's caused? I'm just dumb like that because I don't care."
Insane Clown Posse feels qualified to do FUSE show
NEW YORK (AP) — They are the self-proclaimed "Most Hated Band in the World," and now they're bringing their own theater of the absurd to the Fuse Network with the aptly titled "Insane Clown Posse Theater."


text:
|Attention: DocWiki has reached EOL and will be decommissioned January 25, 2019.
OpenStack Grizzly Release: High-Availability Automated Deployment Guide
From DocWiki
There are two common ways of installing OpenStack, either manually or by using automation tools such as the Cisco OpenStack Installer (Cisco OSI). This guide providers users step-by-step instructions for using Cisco OSI to automate the installation, configuration and deployment of a highly-available OpenStack Grizzly environment. The OpenStack deployment covers the following software components:
- Keystone (Identity Service)
- Glance (Image Service)
- Nova (Compute Service)
- Horizon (OpenStack Dashboard Web User Interface)
- Quantum (Network Service)
- Cinder (Block Storage Service)
- Swift (Object Storage Service)
In addition to highly-available OpenStack services, the system will also enable basic monitoring functionality based on Nagios, Collectd, and Graphite.
In Cisco OSI, an initial build server outside of the OpenStack cluster is used to manage and automate the OpenStack software deployment. This build server primarily functions as a Puppet Master for software deployment and configuration management of the OpenStack cluster, as well as a Cobbler server for managing the bare-metal installation of the Ubuntu Operating System. Once the build server is installed and configured, it is used as an out-of-band automation and management workstation to manage the OpenStack nodes. It also functions as a monitoring server to collect statistics about the health and performance of the OpenStack deployment, as well as to monitor the availability of the machines and services.
You can find bugs, release milestones, and other information on Launchpad. You can find release notes for the most recent release here.
High-Availability Introduction
Most OpenStack deployments are maturing from evaluation-level environments to highly available and highly scalable environments to support production applications and services. The architecture consists of the following components used to provide high-availability to OpenStack services:
- MySQL Galera provides synchronous multi-master clustering to the MySQL/InnoDB databases.
- RabbitMQ Clustering and RabbitMQ Mirrored Queues provide active/active and highly scalable message queuing for OpenStack services.
- HAProxy and Keepalived provide load-balancing between clients and OpenStack API Endpoints.
- The Multiple Quantum L3 and DHCP Agents Blueprint allows multiple Quantum Layer-3 and DHCP Agents to be deployed for high-availability and scalability purposes. At this time (Grizzly release), multiple DHCP Agents can service a Quantum network, however, only a single L3 Agent can service one Quantum network at a time. Therefore, the L3 Agent is a single point of failure and is not included in the Cisco High-Availability Deployment Guide. Quantum Provider Network Extensions are used to map physical data center networks to Quantum networks. In this deployment model, Quantum relies on the physical data center to provide Layer-3 high-availability instead of the L3 Agent.
- Glance uses Swift as the back-end to store OpenStack images. Just as with the rest of the OpenStack API's, HAProxy and Keepalived provide high-availability to the Glance API and Registry endpoints.
- Swift: Multiple Swift proxies are used to provide high-availability for the Swift proxy service. Replication provides high-availability to data stored within a Swift object-storage system. The replication processes compare local data with each remote copy to ensure they all contain the latest version. Object replication uses a hash list to quickly compare subsections of each partition, and container and account replication use a combination of hashes and shared high water marks.
For more details about the high-availability architecture, please refer to the manual deployment guide
Critical Reminders
The most common OpenStack HA deployment issues are either incorrect site.pp file settings or not deploying the nodes in the proper order. To save you from future troubleshooting steps, ENSURE that you deploy the nodes in the order described within the document and verify the accuracy of files. You will likely be using your own IP addressing, passwords and node names in your setup and it is critical to ensure any variations from this guide are fully understood.
Do not configure RAID on the hard disks of Swift Storage Nodes. Swift performs better without RAID and disk redundancy is unneeded since Swift protects the data through replication. Therefore, if a RAID Controller manages the hard disks, ensure you present each of the hard disks independently. Our example uses disk /dev/sda for the Operating System installation and disks /dev/sdb-/dev/sdf for Swift storage. Please remember to modify these definitions within the site.pp example file based on your specific deployment environment. Additional Swift considerations and tuning information can be found here.
The passwords used in our example site.pp file are insecure, so it's highly recommended to change them.
Operating System
The operating system used for this installation is Ubuntu 12.04 LTS (Precise).
Server Requirements
Our deployment uses 12 Cisco UCS C-series servers to serve the roles of Controller, Compute, Load-Balancer and Swift Proxy/Storage. The environment scales linearly, therefore individual nodes can be added to increase capacity for any particular OpenStack service. The five distinct node types used in this document are:
- 3 Controller Nodes- Runs Nova API, Nova Conductor, Nova Consoleauth, Nova Novncproxy, Nova Scheduler, NoVNC, Quantum Server, Quantum OVS Plugin/Agent, Quantum DHCP Agent, Glance API/Registry, Keystone, Cinder API, Cinder Scheduler, OpenStack Dashboard, RabbitMQ Server, MySQL Server WSREP and Galera.
- Provides management functionality of the OpenStack environment.
- 2 Compute Nodes- Runs Nova Compute, Quantum OVS Agent and Cinder Volume services.
- Provides the hypervisor role for running Nova instances (Virtual Machines) and presents LVM volumes for Cinder block storage.
- 2 Load-Balancer Nodes- Runs HAProxy and Keepalived to load-balance traffic across Controller and Swift Proxy clusters.
- 2 Swift Proxy Nodes- The Proxy Node is responsible for tying together users and their data within the the Swift object storage system. For each request, it will look up the location of the account, container or object in the Swift ring and route the request accordingly. The public API is also exposed by Proxy Node.
- 3 Swift Storage Nodes- Each Storage Nodes contains Swift object, container, and account services. At a very high-level, these are the servers that contain the user data and perform replication among one another to keep the system in a consistent state.
Networking Requirements
The OpenStack HA environment uses five separate networks. Three of the five networks are used by Tenants. Three tenant networks are being used as an example, and thus the tenant networks can be increased or decreased based on your deployment needs. Connectivity within Tenants uses Quantum with the Open vSwitch (OVS) plugin and Provider Network Extensions. Provider Network Extensions allow cloud administrators to create OpenStack networks that map directly to physical networks in the data center and support local, VLAN and GRE deployment models. Our example uses the Provider VLAN networking model. The network details are as follows:
- 1 Management Network
- This network is used to perform management functions against the node. For example, SSH'ing to the nodes to change a configuration setting. The network is also used for lights-out management using the CIMC interface of the UCS servers. Lastly, OpenStack API's and the Horizon web dashboard is associated to this network.
- An IP address for each node is required for this network. If using lights-out management such as CIMC, each node will require 2 addresses from this network.
- This network typically employs private (RFC1918).
- 3 Tenant Networks
- These networks are used to provide connectivity to Instances. Since Quantum Provider Networking Extensions are being used, it is common to give tenants direct access to a "public" network that can be used to reach the Internet.
- Compute and Controller Nodes will have an interface attached to this network. Since the Compute/Controller Node interfaces that attach to this network are managed by OVS, the interface should NOT contain an IP address.
- This network typically employs publicly routable IP addressing if external NAT'ing is not used upstream towards the Internet edge (this document uses all private addressing).
- 1 Storage Network
- This network is used for providing separate connectivity between Swift Proxy and Storage Nodes. This ensures storage traffic is not interfering with Instance traffic.
- This network typically employs private (RFC1918) IP addressing.
Figure 1 is used to help visualize the network deployment and to act as a reference for configuration steps within the document. It is highly recommend to print the diagram so it can easily be referenced throughout the installation process.
Figure 1: OpenStack HA Network Design Details
- Physical Network Switches: Each node in the reference deployment is physically connected to two Cisco Nexus switches that are configured for layer 2 only. eth0 of each node connects to Nexus switch 1 and eth1 of each node is connected to Nexus switch 2. Trunking is configured on each interface connecting to the eth0 and eth1 NICs of each node. Trunking is also configured between the switches and to the upstream physical routers.
- Physical Network Routers: Each Nexus switch is connected to a pair of upstream ASR 9000 routers. The routers provide layer 3 functionality, including first-hop redundancy (using VRRP) for all OpenStack networks. Keep in mind that the HA architecture uses Quantum Provider Networking Extensions, so tenant networks will also use ASR 9000 VRRP addresses as gateways.
The installation of the nodes should be in the following order:
- Build Node- build-server
- Load-Balancer Nodes- slb01 and slb02
- Swift Storage Nodes- swift01, swift02 and swift03
- Swift Proxy Nodes- swiftproxy01 and swiftproxy02
- Controller Nodes- control01, control02 and control03
- Compute Nodes- compute01, compute02 and compute03
Build Node Installation
Ensure you have reviewed the Critical Reminders section before proceeding. The build node is named build-server in our reference deployment. This server has relatively modest hardware requirements: 2 GB RAM, 20 GB storage, Internet connectivity, and a network interface on the same network as the management interfaces (CIMC and eth0 in our reference deployment) of the OpenStack nodes.
Install Ubuntu 12.04 LTS. A minimal install with openssh-server is sufficient. Configure the network interface on the OpenStack cluster management segment with a static IP. Also, when partitioning the storage, choose a partitioning scheme which provides at least 15 GB free space under /var, as installation packages and ISO images used to deploy OpenStack will eventually be cached there. Use the Build Node Deployment Guide for step-by-step instructions for installing the Build Node. When the installation finishes, log in and become root:
sudo -H bash
NOTE: Please read the following if you have proxy'ed Internet access or no Internet access :
If you require a proxy server to access the Internet, be aware that proxy users have occasionally reported problems during the phases of the installation process that download and install software packages. A common symptom of proxy trouble is that apt will complain about hash mismatches or file corruptions when verifying downloaded files. A few known scenarios and workarounds include:
- If the apt-get process reports a "HASH mismatch", you may be facing an issue with a caching engine. If it's possible to do so, bypassing the caching engine may resolve the problem.
- If you do have a proxy, you will want, at a minimum, to export the two types of proxies needed in your root shell when running fetch commands, as noted in the relevant sections.
- You will also want to change the $proxy setting in site.pp to reflect your local proxy.
Another possible change is if you don't have "public" Internet accessible IPs for all of your machines (build, control, compute, etc.) and are building this in a controlled environment. If this is the case, ensure that $default_gateway is *not* set in site.pp and all of the files required for installing the control and compute nodes will be fetched from the boot server.
IMPORTANT: If you have proxies, and you set your proxy information in either your .profile or in a file like /etc/environment, you will need to set both http_proxy and https_proxy. You will also need to set a no_proxy command at least for the build node. An example might look like:
http_proxy=http://your-proxy.address.com:80/ https_proxy=https://your-https-proxy.address.com:443/ no_proxy=your-build-node-name,*yourbuild.domain.name,127.0.0.1,127.0.1.1,localhost
You have two choices for configuring up the build node. You can follow the manual steps below, or you can run a one line script that tries to automate this process. In either case, you should end up with the puppet modules installed, and a set of template site manifests in /etc/puppet/manifests.
Option 1: Run the Script
To run the install script, copy and paste the following on your command line (as root with your proxy set if necessary as above):
curl -s -k -B https://raw.github.com/CiscoSystems/grizzly-manifests/multi-node/install_os_puppet | /bin/bash
With a proxy, use:
https_proxy=http://proxy.example.com:80/ curl -s -k -B https://raw.github.com/CiscoSystems/grizzly-manifests/multi-node/install_os_puppet > install_os_puppet chmod +x install_os_puppet ./install_os_puppet -p http://proxy.example.com:80/
You can now jump to "Customizing your build server". Otherwise, follow along with the steps below.
Option 2: Run the Commands Manually
All should now install any pending security updates:
apt-get update && apt-get dist-upgrade -y && apt-get install -y puppet git ipmitool
Reboot the system:
reboot now
Get the Cisco OSI example manifests. Under the grizzly-manifests GitHub repository:
git clone -b multi-node https://github.com/CiscoSystems/grizzly-manifests ~/cisco-grizzly-manifests/ cd ~/cisco-grizzly-manifests git checkout -q g.2
With a proxy:
https_proxy=http://proxy.example.com:80 git clone -b multi-node https://github.com/CiscoSystems/grizzly-manifests ~/cisco-grizzly-manifests/ cd ~/cisco-grizzly-manifests https_proxy=http://proxy.example.com:80 git checkout multi-node
Copy the puppet manifests from ~/cisco-grizzly-manifests/manifests/ to /etc/puppet/manifests/
cp ~/cisco-grizzly-manifests/manifests/* /etc/puppet/manifests
Copy the puppet templates from ~cisco-grizzly-manifests/templates/ to /etc/puppet/templates/
cp ~/cisco-grizzly-manifests/templates/* /etc/puppet/templates
Then get the Cisco Edition puppet modules from Cisco's GitHub repository:
(cd /etc/puppet/manifests; python /etc/puppet/manifests/puppet_modules.py)
With a proxy:
(cd /etc/puppet/manifests; http_proxy=http://proxy.example.com:80 https_proxy=http://proxy.example.com:80 python /etc/puppet/manifests/puppet-modules.py)
Build Node Configuration
In the /etc/puppet/manifests directory you will find these files:
clean_node.sh cobbler-node.pp core.pp modules.list puppet-modules.py reset_nodes.sh site.pp.example site.pp.ha.example
At a high level, cobbler-node.pp manages the deployment of cobbler to support booting of additional servers into your environment. The core.pp manifest defines the core definitions for OpenStack service deployment. The site.pp.example manifest captures the configuration components that can be modified by end-users ""for a non-HA deployment"". The site.pp.ha.example manifest captures the configuration components that can be modified by end-users ""for a HA deployment"". clean_node.sh is a shell script provided as a convenience to deployment users; it wraps several cobbler and puppet commands for ease of use when building and rebuilding the nodes of the OpenStack cluster. reset_nodes.sh is a wrapper around clean_node.sh to rebuild your entire cluster quickly with one command.
IMPORTANT! You must copy site.pp.ha.example to site.pp and then edit it as appropriate for your installation. It is internally documented.
cp /etc/puppet/manifests/site.pp.ha.example /etc/puppet/manifests/site.pp vi /etc/puppet/manifests/site.pp
Then, use the 'puppet apply' command to activate the manifest:
puppet apply -v /etc/puppet/manifests/site.pp
When the puppet apply command runs, the puppet agent on the build node will follow the instructions in the site.pp and cobbler-node.pp manifests and will configure several services on the build server:
- ntpd -- a time synchronization server used on all OpenStack cluster nodes to ensure time throughout the cluster is correct
- tftpd-hpa -- a TFTP server used as part of the PXE boot process when OpenStack nodes boot up
- dnsmasq -- a DNS and DHCP server used as part of the PXE boot process when OpenStack nodes boot up
- cobbler -- an installation and boot management daemon which manages the installation and booting of OpenStack nodes
- apt-cacher-ng -- a caching proxy for package installations, used to speed up package installation on the OpenStack nodes
- nagios -- a infrastructure monitoring application, used to monitor the servers and processes of the OpenStack cluster
- collectd --a statistics collection application, used to gather performance and other metrics from the components of the OpenStack cluster
- graphite and carbon -- a real-time graphing system for parsing and displaying metrics and statistics about OpenStack
- apache -- a web server hosting sites to implement graphite, nagios, and puppet web services
The initial puppet configuration of the build node will take several minutes to complete as it downloads, installs, and configures all the software needed for these applications.
Once the site manifest has been applied to your system, you need to stage puppet plugins so they can be accessed by the managed nodes:
puppet plugin download
After the build node is configured, the systems listed in site.pp should be defined in cobbler on the build server:
cobbler system list slb01 slb02 control01 control02 control03 swiftproxy01 swiftproxy02 swift01 swift02 swift03 compute01 compute02
Load-Balancer Node Deployment
Now that the OpenStack nodes are being managed by the Build Node, deploying a node should be as simple as calling the clean_node.sh script with the node name:
. /etc/puppet/manifests/clean_node.sh {node_name}
NOTE: Replace node_name with the name of your controller.
Example: /etc/puppet/manifests/clean_node.sh slb01 /etc/puppet/manifests/clean_node.sh slb02
clean_node.sh is a script which does several things:
- Configures Cobbler to PXE boot the specified node with appropriate PXE options to do an automated install of Ubuntu
- Uses Cobbler to power-cycle the node
- Removes any existing client registrations for the node from Puppet, so Puppet will treat it as a new install
- Removes any existing key entries for the node from the SSH known hosts database
You can watch the automated Ubuntu installation progress by using the Virtual KVM from the UCS CIMC. Once the installation finishes, nodes reboot and then automatically run the puppet agent. By now you should be able to SSH to the node(s):
ssh localadmin@<MGT_IP>
On each node, the Puppet agent automatically retrieves and applies the configuration associated to its name within the site manifest. This step will take several minutes, as puppet downloads, installs, and configures the various OpenStack components and associated services. Observe the progress of the puppet deployment process by tail'ing syslog:
tail -f /var/log/syslog
Once OpenStack nodes complete the build process, run puppet on the build node a second time:
puppet agent -t
This second puppet run will gather information about the individual OpenStack nodes collected by Puppet when they were being built, and use that information to set up status monitoring of the OpenStack cluster on the build server.
Verify the Load-Balancer Node Installation
After the load-balancer nodes complete the automated deployment process, use the following steps to verify proper functionality:
Make sure puppet agent runs clean:
puppet agent -t -d
Note: If you are unable to complete a clean puppet agent run, then do not proceed with the deployment. Send a support request email to email@example.com with a copy of the puppet error.
Verify that the haproxy service is running:
service haproxy status haproxy is running.
Verify that the virtual IP address for the Controller cluster is bound to node slb01:
ip addr list 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether f8:72:ea:00:1c:4d brd ff:ff:ff:ff:ff:ff inet 192.168.220.81/24 brd 192.168.220.255 scope global eth0 ""inet 192.168.220.40/32 scope global eth0"" inet6 fe80::fa72:eaff:fe00:1c4d/64 scope link valid_lft forever preferred_lft forever
Verify that the virtual IP address for the swift proxy cluster is bound to node slb02:
ip addr list 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether f8:72:ea:00:1c:4d brd ff:ff:ff:ff:ff:ff inet 192.168.220.82/24 brd 192.168.220.255 scope global eth0 ""inet 192.168.220.60/32 scope global eth0"" inet6 fe80::fa72:eaff:fe00:1c4d/64 scope link valid_lft forever preferred_lft forever
Controller Node Deployment
Now that the OpenStack nodes are being managed by the Build Node, deploying the controller nodes should be as simple as calling the clean_node.sh script with the node name. It is IMPORTANT to deploy the controller nodes one at a time starting with control01, then control02 and lastly control03
/etc/puppet/manifests/clean_node.sh {node_name}
Note: Replace node_name with the name of your first controller node.
Example: /etc/puppet/manifests/clean_node.sh control01
Once control01 completes the build process, run puppet on the build node a second time:
puppet agent -t
This second puppet run will gather information about the individual OpenStack nodes collected by puppet when they were being built, and use that information to set up status monitoring of the OpenStack cluster on the build server.
Verify the Controller Node Installation
After the controller nodes complete the automated deployment process, use the following steps to verify proper functionality:
Make sure puppet agent runs clean:
puppet agent -t -d
""Note:"" If you are unable to complete a clean puppet agent run, then do not proceed with the deployment. Send a support request email to email@example.com with a copy of the puppet run error.
From each of the load-balancer nodes, verify that the MySQL Galera monitoring service is functioning:
telnet 192.168.220.41 9200 Trying 192.168.220.41... Connected to 192.168.220.41. Escape character is '^]'. HTTP/1.1 200 OK Content-Type: text/html Content-Length: 43 <html><body>MySQL is running.</body></html> Connection closed by foreign host.
Verify that the RabbitMQ service is running:
service rabbitmq-server status
Verify that the OpenStack services are running:
service keystone status service glance-api status service glance-registry status service nova-api status service nova-conductor status service nova-scheduler status service nova-consoleauth status service quantum-server status service quantum-dhcp-agent status service quantum-plugin-openvswitch status service cinder-api status service cinder-scheduler status
Verify that you can obtain a token from Keystone:
keystone token-get
Make sure to complete the same verification steps on the other two controller nodes.


text:
We are certified with the most recognized trust mark in the Nordic countries, Trygg e-handel, which is managed by the Swedish Digital Commerce association.
All our parcels are shipped with TNT (or DHL in Germany). The shipping charge is 7,90 € for orders of less than 100 €. We cover the cost of shipping for orders exceeding 100 €.
Hööks is happy to refund any items within 60 days, sale items 14 days. Please contact customer service if you would like to return an item.
Free shipping for order over 100 €
Remember to use a back harness when driving in order to allow correct braking.


text:
Do you know a Delaware student who is working to make a difference for the environment?
Do you know a Delaware student who is working to make a difference for the environment? The Delaware Department of Natural Resources and Environmental Control is encouraging teachers, classmates, parents, club or group leaders, and others to nominate these students for the 2013 Young Environmentalist of the Year Awards.
Nominations must be based on actions or projects that have taken place between July 1, 2012 and June 30, 2013.
Nominations will be accepted by DNREC between May 1 and June 14. A winner will be chosen from each of the following categories: elementary school for students in grades 1-4, middle school for students in grades 5-8, and high school for students in grades 9-12.
The Young Environmentalist program honors Delaware students whose actions have resulted in the protection, restoration, or enhancement of Delaware's natural resources through one or more of the following means: demonstrating environmental stewardship, initiating an innovative project, increasing public awareness, and demonstrating environmental ethics.
A gift card and a Delaware State Parks prize pack will be awarded to each category winner in recognition of his or her contribution to the community. Winners will be honored in a special ceremony on Governor's Day at the 2013 Delaware State Fair on July 25.
For more information, including nomination forms, call Joanna Wilson at (302) 739-9902 or visit www.dnrec.delaware.gov.


text:
Chevy Truck Vin Decoder above is part of popular Chevy Truck Vin Decoder collection which uploaded by p1kpak in Chevrolet inventory. We believe this image will be good for your reference
We have attached another great Chevrolet below. You can save as your references. Bookmark our site now to get more amazing wallpaper by share it to your Facebook, Twitter, Pinterest, Google Plus or your other social media account.
This though-provoking article about Chevy Truck Vin Decoder will give you fresh inspiration. We hope you enjoyed it.
This cool image, is other parts of Chevrolet has dimension 367 x 800, You can save and obtain the Chevy Truck Vin Decoder images by right click on the clicking the right mouse to get the high-res version.


text:
Word of the Day
wayfarer WEY-fair-er noun; a traveler, especially on foot. � Dictionary.com
Website of the Day
The Wayfarers Association Hillwalking Club
With over 300 members, the Wayfarers Association Hillwalking Club explores walking and hiking in the Wicklow/Dublin mountains area, as well as regular trips to other parts of Ireland.
Number to Know
6.6: In 2013, a 6.6-magnitude earthquake hit Lushan County, Ya�an, in China�s Sichuan province, killing more than 150 people and injuring thousands.
This Day in History
April 20, 1999: Columbine High School massacre: Eric Harris and Dylan Klebold killed 13 people and injure 24 others before committing suicide at Columbine High School in Columbine, Colo.
Today�s Featured Birthday
Jessica Lange, American actress, 65
Daily Quote
�For me, nothing has ever taken precedence over being a mother and having a family and a home.� � Jessica Lange
Morning Minutes, April 20
Word of the Day


text:
KROGER PHARMACY #34374 pharmacy / drugstore is located in the wonderful city of HOUSTON, in the state of TX. If you need to fill a prescription, this is a perfect place to start. It can be found at 8550 HWY 6 N WEST RD HOUSTON TX 77095.
The LabDraw Pharmacy Directory is available to assists patients with finding a reliable pharmacy. It is also a reporting mechanism used to provide valuable feedback to the doctors, insurance companies, and laboratory service providers. By allowing the patients to comment freely about their experiences at a pharmacy or locating a particular facility we are assisting with opening up the doors to better healthcare.
If you have any comments to make regarding the service you have received at this pharmacy, or other information about what is provided here, feel free to add it to the comments section located below. Your comments will be immediately made available to others viewing this page.


text:
Wendell Barnhouse is a nationally-known and respected columnist who has spent over 20 years covering collegiate athletics. He has reported from 25 Final Fours and more than three dozen bowl games and has written about the Big 12 and its schools since the conference's beginning. Barnhouse will be updating the Big 12 Insider on happenings and behind-the-scenes information about the conference.
The Executive Committee is the highest governance body in the NCAA and is composed of institutional chief executive officers that oversee Association-wide issues. The committee is charged with ensuring that each division operates consistently with the basic purposes, fundamental policies and general principles of the Association.
"President Schulz's support and passion for intercollegiate athletics will be invaluable to the Executive Committee," Emmert said. "He will bring the proud traditions of both the Big 12 Conference and Kansas State to the highest governing body in the NCAA. I look forward to working with him to improve the experience for our student-athletes."
Schulz has served on the Division I NCAA Board of Directors, which is made up of presidents or chancellors from institutions in each of the association's 11 conferences, and will continue to fulfill his current four-year term in this role, ending in August 2016.
"President Schulz has proven himself as an outstanding educator and a talented leader," said Big 12 Commissioner Bob Bowlsby. "These capabilities are regularly demonstrated in our Big 12 meetings and the NCAA has quickly recognized what an asset he will be on the Board. We are proud of President Schulz and grateful for his willingness to service at the national level."
The board of directors is charged with responsibilities like electing institutions to Division I membership, overseeing the Academic Progress Rate and Academic Performance Census, and assuring gender and ethnic diversity in the leadership structure.
"President Schulz has provided terrific leadership for Kansas State University and the Big 12 Conference while also making an immediate impact during his first year as a member of the NCAA Division I Board of Directors," K-State Director of Athletics John Currie said. "Strengthening the interconnectivity between intercollegiate athletics and campus communities through his role on the NCAA Board and Executive Committee is a key component to K-State to becoming a Top 50 public research university by 2025."


text:
Archives 2013
28 December 2013
Sepang, 28 December 2013 - Fifteen (15) children from Rumah Charis, Kuala Lumpur had their wishes granted at KL International Airport when they each received the gift they wished for courtesy of Malaysia Airports and...
Read More
19 December 2013
Sepang, 19 December 2013 - Warga kerja Malaysia Airports bakal menerima faedah yang lebih baik setelah Malaysia Airports menandatangani Perjanjian Bersama ke-7 (CA7) dengan kesatuan-kesatuan sekerjanya hari ini. ...
Read More
14 November 2013
Sepang, 14 November 2013 - Two more airports under Malaysia Airports' management have received Aerodrome Certification and another six certified airports received the Safety Management System (SMS) certifications today...
Read More
31 October 2013
Sepang, 31 October 2013 - Malaysia Airports Holdings Berhad ("MAHB") recorded a revenue of RM2,978.1 million for the nine months ended 30 September 2013 ("9M13"), representing a growth of 34.2% compared to RM2,219.8...
Read More
28 October 2013
Sepang, 28 October 2013 - Malaysia Airports held its KLIA awards presentation to honour partners with exceptional performance for the year 2012. The prestigious KLIA Awards is the ideal platform for Malaysia Airports to...
Read More
25 October 2013
Sepang, 25 October 2013 - We are proud to announce that Malaysia Airports Holdings Berhad was conferred the Silver Award in the Employer of Choice award category in the Malaysia HR Award 2013 on 24October 2013 at a...
Read More
16 October 2013
Sepang, 16 October 2013 - Barely a week after the successful trial landing at Runway 3, klia2 continues to gain momentum towards its opening in May next year when Malaysia Airports Holdings Berhad (Malaysia Airports)...
Read More
07 October 2013
Sepang, 7 October 2013 - KUB Malaysia Berhad (KUB), a main board listed investment arm company today announced the completion of a third runway project at the world's largest purpose-built terminal dedicated for...
Read More
04 October 2013
Sepang, 4 October 2013 - Malaysia Airports telah melancarkan Tabung Pahlawan 2013 di Lapangan Terbang Antarabangsa KL (KLIA) ke arah menyokong usaha Kementerian Pertahanan dan Persatuan Bekas Tentera Malaysia untuk...
Read More
30 September 2013
Sepang, 30 September 2013 - Bonus came early this year for 21 travelers -- thanks to Malaysia Airports' Indulge Till You Fly (ITUF) Campaign! The travelers, all of whom participated in Malaysia Airports'...
Read More


text:
French telecommunications regulator Arcep has launched an investigation into the French version of Skype to answer that question.
The news is significant because if Arcep decides Skype is a telco, a host of regulatory and fiscal requirements will apply, which could create headaches for Microsoft and cut down on Steve Ballmer's smiley icons for a spell.
Arcep seems to have lost patience with Skype France (which is actually based in neighboring francophone Luxembourg) for failing to register as a telecom operator, despite its continual requests. In its official announcement of the probe, Arcep said that under local laws, Skype has certain obligations that include the routing of emergency calls and implementing the means required to perform legally ordered interceptions (wiretaps) if it is a telco.
[ British Telecom, Verizon and others are gearing up to compete with Amazon in IaaS. Read more at Amazon, Telcos Will Battle For Cloud Customers. ]
Arcep's statement points out that "the service allows Internet users located in France to call fixed and mobile numbers in France and around the world, using their computer or smartphone" and that a provider doesn't have to a get administrative approval to become an electronic communications operator in France. However, it must declare it will operate as such before it sets out its stall in the Republic. "A failure to comply with this obligation does, however, constitute a criminal offence," the statement concludes.
At least one press report says Arcep has been trying to get Skype locally to file the appropriate paperwork since April 2012.
Arcep's chairman has "apprised the Parisian public prosecutor of these facts," and that office will now decide if an offence has been in fact committed.
Arcep's move has drawn interest from around the world. According to a recent New York Times article, the news raises the question of "what constitutes a telephone company in the age of Internet-based communications." The Times pointed out that the action comes at a tricky time for Microsoft, which has come under pressure from digital rights groups over how user data collected from Skype is shared with advertisers and law enforcement agencies.
Microsoft told the Times that it had communicated with Arcep its view that Skype is in fact not a provider of electronic communications services under French law, and that it would "continue to work with Arcep in a constructive fashion."
Arcep's muscle-flexing may be part of a wider shift of France more closely policing -- and taxing -- U.S.-based Internet firms -- and, for example, starting to levy revenue charges on the collection of citizen data.
Attend Interop Las Vegas May 6-10 and learn the emerging trends in information risk management and security. Use Priority Code MPIWK by March 22 to save an additional $200 off the early bird discount on All Access and Conference Passes. Join us in Las Vegas for access to 125+ workshops and conference classes, 300+ exhibiting companies, and the latest technology. Register today!


text: Providing a Citywide System of Single Point Access to Domestic Violence Information, Resources, and Referrals to a Diverse Population: An Evaluation of the City of Chicago Domestic Violence Help Line, 2004-2005 (ICPSR 33970) Version Date: Oct 23, 2012 View help for published Cite this Study | Share this study Share on Twitter Share on Facebook Share on LinkedIn × Citation Fugate, Michelle, George, Christine, Haber, Natalie, and Stawiski, Sarah. Providing a Citywide System of Single Point Access to Domestic Violence Information, Resources, and Referrals to a Diverse Population: An Evaluation of the City of Chicago Domestic Violence Help Line, 2004-2005. Ann Arbor, MI: Inter-university Consortium for Political and Social Research [distributor], 2012-10-23. https://doi.org/10.3886/ICPSR33970.v1 Export Citation: RIS (generic format for RefWorks, EndNote, etc.) EndNote Principal Investigator(s): View help for Principal Investigator(s) Michelle Fugate, City of Chicago; Christine George, Loyola University-Chicago; Natalie Haber, Loyola University-Chicago; Sarah Stawiski, Loyola University-Chicago https://doi.org/10.3886/ICPSR33970.v1 Version V1 Analyze Online Slide tabs to view more At A Glance Data & Documentation Variables Publications Export Metadata Staff Project Description Summary View help for Summary This study was a 2-year evaluation of the City of Chicago Domestic Violence Help Line. The Help Line was a unique telephone service functioning as a clearinghouse for all domestic violence victim services in the Chicago metropolitan area. The service was toll-free, multi-lingual, confidential, and operated 24-hours, 7 days a week. The purpose of the Help Line was to connect domestic violence victims to specialized services through direct referrals and three-way phone linkages. In order to conduct a comprehensive evaluation, the perspective of a broad range of users of the Help Line was sought. Telephone interviews were conducted with domestic violence victim callers to the Help Line over the course of one year (Part 1 - Victims Data). Telephone interviews were also conducted with domestic violence service providers (Part 2 - Providers Data). As the largest referral source into the Help Line, Chicago Police Officers completed a written survey about their experiences with the Help Line (Part 3 - Police Data). Finally, to explore the general awareness of the Help Line, members of the District Advisory Committees across the city were surveyed (Part 4 - District Advisory Committee (DAC) Data). The Part 1 (Victims Data) data file contains 399 cases and 277 variables. The Part 2 (Providers Data) data file contains 74 cases and 137 variables. The Part 3 (Police Data) data file contains 1,205 cases and 128 variables. The Part 4 (District Advisory Committee (DAC) Data) data file contains 357 cases and 105 variables. Citation View help for Citation Fugate, Michelle, George, Christine, Haber, Natalie, and Stawiski, Sarah. Providing a Citywide System of Single Point Access to Domestic Violence Information, Resources, and Referrals to a Diverse Population: An Evaluation of the City of Chicago Domestic Violence Help Line, 2004-2005. Ann Arbor, MI: Inter-university Consortium for Political and Social Research [distributor], 2012-10-23. https://doi.org/10.3886/ICPSR33970.v1 Export Citation: RIS (generic format for RefWorks, EndNote, etc.) EndNote Funding View help for Funding United States Department of Justice. Office of Justice Programs. National Institute of Justice (2003-WG-BX-1008) Subject Terms View help for Subject Terms abuse advocacy domestic violence victim safety victim services violence violence against women womens shelters Geographic Coverage View help for Geographic Coverage United States Chicago Illinois Restrictions View help for Restrictions A downloadable version of data for this study is available however, certain identifying information in the downloadable version may have been masked or edited to protect respondent privacy. Additional data not included in the downloadable version are available in a restricted version of this data collection. For more information about the differences between the downloadable data and the restricted data for this study, please refer to the codebook notes section of the PDF codebook. Users interested in obtaining restricted data must complete and sign a Restricted Data Use Agreement, describe the research project and data protection plan, and obtain IRB approval or notice of exemption for their research. Distributor(s) View help for Distributor(s) Inter-university Consortium for Political and Social Research Scope of Project Time Period(s) View help for Time Period(s) 2004-07 -- 2005-08 (Part 1), 2005-04 -- 2005-08 (Part 2), 2005-03 (Part 3), 2004-05 -- 2004-09 (Part 4) Date of Collection View help for Date of Collection 2004-07 -- 2005-08 (Part 1), 2005-04 -- 2005-08 (Part 2), 2005-03 (Part 3), 2004-05 -- 2004-09 (Part 4) Data Collection Notes View help for Data Collection Notes The final report for this study mentions that there were 1,202 interviews with police officers (Part 3 - Police Data) while the data file has 1,205 cases. ICPSR was unable to determine the reason for this discrepancy. The final report mentions that qualitative data were collected from focus groups with Victim Information and Referral Advocates (VIRAs) but these data were not made available to ICPSR. Methodology Study Purpose View help for Study Purpose The 3 primary goals of the study were: (1) to assess the effectiveness of the Help Line's operation in serving domestic violence victims from Chicago's diverse populations; (2) to learn about the differing needs of diverse populations and their experiences utilizing the information, referrals, and linkages; and (3) to provide information to other municipalities interested in establishing such public-private programs, collaborations, and policies. Study Design View help for Study Design Part 1 (Victims Data) During the course of each call to the Help Line, Victim Information and Referral Advocates (VIRAs) recorded general non-identifying information about the victim and basic information about the victim's service needs. Brief telephone interviews were conducted with a representative sample of a subset of victim callers to the Help Line. The phone interviews were designed to take place apart from and subsequent to the Help Line call. This decision was made for a variety of methodological and safety reasons. The time lag allowed respondents to have some time to assess her or his experience and to have had the possibility of using the information and therefore gauging its usefulness, providing for a more valid assessment of their experience. Phone interviews were conducted between July 2004 and August 2005 with victims who called the Help Line. The brief interviews ranged from 5 to 45 minutes, averaging about 10 minutes. The interviews were conducted on an average within 11 days from the victim's call to the Help line, thus allowing researchers to ascertain both the victim's assessment of her or his interaction with the Help Line and how she or he subsequently used the information/linkage/referral from the Help Line. The vast majority of the completed interviews was the result of calls originating from the researchers, with a small number of calls originating from a call to an 800 number. All the VIRAs recruited victims to the study during the course of their staffing of the Help Line. During a Help Line call, if the VIRA determined that the victim met the criteria to be included in the study, the VIRA proceeded to ask the victim to participate in a later telephone interview. If the victim agreed, a safe phone number, name and time for a return call were gathered, if available. If a safe number was not available, the caller was provided with a toll-free phone number to call in order to participate in the interview. Each week the Mayor's Office on Domestic Violence (MODV) transmitted by computer disk to the research team selected information on all those individuals who had been asked to participate in the study for the preceding week and their responses. The researchers then proceeded to call recruited victims. A Spanish-speaking researcher called all Spanish-speaking victims and conducted those interviews. In the calling procedure, there were steps that the interviewer followed to maintain safety of the respondent. First, in order to approach each call safely, the interviewer checked the transmitted MODV Help Line data prior to calling. Second, to ensure safety of the potential participants of the study, researchers set a time limit for attempted calls at 3 weeks. Third, upon reaching the client, interviewers prompted the respondent about the study itself (using the name "City Health Survey") and only continued the call if the respondent remembered the survey. Fourth, no voice mail messages were left and all calls originated from specific phone stations at the research center that were dedicated to the study. Finally, researchers designed the interview to be as unobtrusive as possible. Part 2 (Providers Data) A telephone interview was conducted with 74 respondents from 55 Chicago-area agencies. Some of the organizations had multiple geographic locations or "sites" and therefore, sometimes more than one respondent was interviewed from one agency. The organizations interviewed fell into 2 types. One type existed specifically to provide domestic violence services. The other type was a domestic violence program within a larger multi-purpose agency. A very thorough recruitment effort was instituted to ensure a high level of participation and to identify the appropriate staff at each agency site who interacted with the Help Line. Telephone interviews were conducted from April to August 2005. Part 3 (Police Data) The Chicago Police Department (CPD) administered the survey to all CPD officers in every one of the Police Districts at each shift roll call on March 16, 2005, providing an accessible environment for distribution of the survey. Completion of the survey was voluntary and confidential. No record was kept of individual survey completion in order to mitigate the possible coercive effect of supervisors' administration of surveys. This resulted in 1,205 completed surveys. Part 4 (District Advisory Committee (DAC) Data) In May through September of 2004, researchers surveyed a total of 357 Chicago residents attending one of the monthly Police District DAC meetings. The DAC's geographic districts encompassed the whole city and thus their members provided a convenient sample of active community residents, representatives from social service agencies, community and faith organizations and business leaders. The surveys were conducted during a regularly scheduled monthly DAC meeting and were administered by the researchers. Survey administration was incorporated into each meeting's agenda, which facilitated completion of the survey. Sample View help for Sample Part 1 (Victims Data) Originally, every caller stratified by race was selected. When prompted by the computer, the Victim Information and Referral Advocate (VIRA) attempted recruitment and then recorded the results of that attempt. If the VIRA determined that the victim was in current crisis or a dangerous or unsafe location, recruitment did not occur. During the project's development researchers had determined that a sample size of 367 completed interviews was needed to achieve a representative sample at the 95 percent confidence level with a confidence interval of 5. Researchers developed the sampling frame that identified 4 times that number for recruitment. Researchers believed quadrupling would account for the drop off due to refusals to participate, failure to contact, and disconnected phone numbers. Researchers anticipated that some victims would not have access to private phones and therefore installed a toll-free number for these victims to be able to call and participate in the study. During the 13 weeks in which the systematic stratified sampling frame was in effect, 2,054 victims called the domestic violence Help Line, 532 (26 percent) were recruited, 189 (36 percent) agreed to participate in an interview, 103 gave contact information and 39 interviews were completed. At this rate, researchers would not achieve a representative sample by the end of the data collection time period. Researchers tested a variety of strategies to increase take-up rates both at the recruitment end and the interview end. Several steps were taken: the time length of the recruitment script was decreased, discussions occurred with and between VIRAs on successful recruitment techniques, meetings were held with Help Line supervisors on successful recruitment, a list of tips was created for VIRAs to use, and the interval in the selection frame was decreased. To increase completion rates, during recruitment the VIRAs asked whether the phone number the victim supplied was a cell phone and when the phone was likely to be on. Researchers also began making evening and weekend phone calls to victims to conduct the interview. More than half of the victim callers, while agreeing to participate in the study, could not give researchers a phone number where they could be reached. Researchers had not expected to rely on the victim calling back to the toll-free phone number for over half of the calls. Given the experiences of other studies using 800 numbers, researchers knew the fall off rate was extremely high. To increase completion through victim call back to the toll-free 800 number, researchers tested different call back times, included evening times, and asked victims to specify the time/day they were likely to call back. Additionally, all shelters agreed to post a reminder flyer next to the communal telephone (where there was no communal phone, the shelter reminded during intake) to remind victims who agreed to participate to place the call. While these changes increased the take up and completion rates slightly, researchers would still not achieve a representative sample by the conclusion of the recruitment period. For the remainder of the project, from October 21, 2004 through August 10, 2005, every victim caller meeting the criteria (over 18, not in current crisis, not a family of origin relationship) was invited to participate in an interview. Part 2 (Providers Data) The list of all possible agencies was compiled by the Mayor's Office on Domestic Violence (MODV) and the Help Line Director. Agencies that only served sexual assault victims or those that only provided abuser treatment services were excluded. Further, all agencies in the city were included, but agencies located in the suburbs were included only if a referral had been made there in the past year. Five were not included because of the small number of referrals; four agencies had fewer than six referrals in the previous year. Part 3 (Police Data) The Chicago Police Department (CPD) administered the survey to all CPD officers in every one of the Police Districts at each shift roll call on March 16, 2005. Part 4 (District Advisory Committee (DAC) Data) While it was beyond the capacity of this study to survey a representative sample of community residents, researchers were able to survey a convenience sample of Chicago residents who attended monthly Police District Advisory meetings in each of the police districts. In May through September of 2004, researchers surveyed Chicago residents attending one of the monthly Police District DAC meetings. Time Method View help for Time Method Cross-sectional Universe View help for Universe Part 1 (Victims Data): Individuals who called the Chicago Domestic Violence Help Line from July 22, 2004 through August 10, 2005. Part 2 (Providers Data): Chicago-area domestic violence agencies in operation between April and August, 2005. Part 3 (Police Data): All Chicago Police Department officers in every one of the Police Districts at each shift roll call on March 16, 2005. Part 4 (District Advisory Committee (DAC) Data): Chicago residents who attended one of the monthly Police District - District Advisory Council (DAC) meetings between May and September of 2004. Unit(s) of Observation View help for Unit(s) of Observation Parts 1, 3, and 4: individual, Part 2: agency Data Type(s) View help for Data Type(s) administrative records data, survey data Mode of Data Collection View help for Mode of Data Collection record abstracts self-enumerated questionnaire telephone interview Description of Variables View help for Description of Variables Part 1 (Victims Data) Several questions covered what kinds of information (both general information and specific referrals and linkages) clients were seeking, how useful they found the interactions with the Help Line in getting that information, and what they did with the information that they received. Usefulness on these dimensions and others was measured on a Likert scale with a five-value range. Questions were included that measured the accessibility of certain features of the Help Line. There were also questions to measure the impact of the Help Line call on the victims and questions to see how victims accessed that system of services and what gaps and challenges they encountered during that process. The Mayor's Office on Domestic Violence (MODV) provided the research team with each caller's demographic information, as well as information on the abuser and type of abuse. These data included demographic information such as victim's sex, age, race/ethnicity, children and living circumstances. Other data included language used in the call, how the caller learned about the Help Line, and the types of services the caller requested. There was some additional demographic information that was covered in the interview including the living situation of the respondents and their employment status. Part 2 (Providers Data) Information in this data file includes program type, services provided, number of staff, and the number of referrals. In addition, there are questions related to barriers the agency may have faced in relation to specific victim populations such as mentally disabled, elderly, or substance abusers. Part 3 (Police Data) The survey included questions about the officers' use of the Help Line and their experiences with and victims' reactions to the Help Line, including barriers encountered in serving victims from various racial, ethnic, linguistic, or life style groups. Part 4 (District Advisory Committee (DAC) Data) The survey gathered information in 4 major areas: (1) individuals' understanding and knowledge of domestic violence and domestic violence services in their community; (2) their knowledge of the Help Line and its components; (3) their use of the Help Line; and (4) their assessment of the Help Line. Response Rates View help for Response Rates Part 1 (Victims Data) Of 6,974 victims of domestic violence, the Victim Information and Referral Advocates (VIRAs) made an attempt to recruit 3,138 victims to participate in a later interview. Of the 3,138 recruited, 51 percent (1,597) agreed to participate in the evaluation interview. Eight hundred twenty-three victims with phone numbers were contacted for the study. Of those called, 47 percent (389) were interviewed. In addition, 728 victims were recruited for interviews but were not able to give phone numbers. Either they did not have access to a phone, or they did not have a "safe phone". Eight of those called the 800 number and were interviewed and 2 additional interviews from the pilot period were included in the analysis, resulting in a total of 399 interviews. Part 2 (Providers Data) The response rate was 83 percent, with 55 out of a possible 66 agencies participating. Part 3 (Police Data) For security reasons, the Chicago Police Department could not report the exact number of patrol officers in the city, the number scheduled, or the number who appeared at roll call on the day the survey was administered. Therefore, it was not possible to directly ascertain the response rate. Part 4 (District Advisory Committee (DAC) Data) The research team achieved an 89 percent participation rate by surveying 357 DAC members out of the 403 surveys distributed. Presence of Common Scales View help for Presence of Common Scales Several Likert-type scales were used in Parts 1 (Victims Data), 2 (Providers Data), and 3 (Police Data). Version(s) Original Release Date View help for Original Release Date 2012-10-23 Version History View help for Version History 2018-02-15 The citation of this study may have changed due to the new version control system that has been implemented. The previous citation was: Fugate, Michelle, Christine George, Natalie Haber, and Sarah Stawiski. Providing a Citywide System of Single Point Access to Domestic Violence Information, Resources, and Referrals to a Diverse Population: An Evaluation of the City of Chicago Domestic Violence Help Line, 2004-2005. ICPSR33970-v1. Ann Arbor, MI: Inter-university Consortium for Political and Social Research [distributor], 2012-10-23. http://doi.org/10.3886/ICPSR33970.v1 2012-10-23 ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major statistical software formats as well as standard codebooks to accompany the data. In addition to these procedures, ICPSR performed the following processing steps for this data collection:Created variable labels and/or value labels.Standardized missing values.Checked for undocumented or out-of-range codes. Notes The public-use data files in this collection are available for access by the general public. Access does not require affiliation with an ICPSR member institution. One or more files in this data collection have special restrictions. Restricted data files are not available for direct download from the website; click on the Restricted Data button to learn more. The citation of this study may have changed due to the new version control system that has been implemented. This dataset is maintained and distributed by the National Archive of Criminal Justice Data (NACJD), the criminal justice archive within ICPSR. NACJD is primarily sponsored by three agencies within the U.S. Department of Justice: the Bureau of Justice Statistics, the National Institute of Justice, and the Office of Juvenile Justice and Delinquency Prevention.


text:
0 Members and 1 Lonely Barbarian are spying on this topic.
But if it is a song that never ends it has no verses and when i say rock i mean tifany and cindi lauper and kenni g and others
I feel like chicken tonight, like chicken tonight, like chicken tonight.
... Crazy. I was crazy once. They put me in a box. The box had worms. I hate worms. Worms make me crazy. Crazy. I was crazy once ...
Page created in 0.275 seconds with 28 queries.