Police: Good evening, are you the host?

Host: No.

Police: We’ve been getting complaints about this party.

Host: About the drugs?

Police: No.

Host: About the guns, then? Is somebody complaining about the guns?

Police: No, the noise.

Host: Oh, the noise. Well that makes sense because there are no guns or drugs here. (An enormous explosion is heard in the background.) Or fireworks. Who’s complaining about the noise? The neighbors?

Police: No, the neighbors fled inland hours ago. Most of the recent complaints have come from Pittsburgh. Do you think you could ask the host to quiet things down?

Host: No Problem. (At this point, a Volkswagen bug with primitive religious symbols drawn on the doors emerges from the living room and roars down the hall, past the police and onto the lawn, where it smashes into a tree. Eight guests tumble out onto the grass, moaning.) See? Things are starting to wind down.

No related posts.

1. the WoW player: «Met a Death Knight with serious blood abilities».
2. the Python guru: «TombException».
3. the Urban Terror player: «Did the lemming thing».
4. the Star Trek fan: «Heghlu’meH QaQ jajvam».
5. the network guru: «TTL expired in transit».
6. the Magic player: «Opponent played Grindstone with Painter’s Servant».
7. the Spaceballs fan: «Out of order? FUCK! Even in heaven, nothing works!».
8. the Matrix fan: «She told me: dodge this!».
9. the NASA fan: «What do you mean “One way mission”?».
10. the Unix guru: «kill -9 -1».

Who said that bad grass never dies?

No related posts.

1. Mouse art — A program that creates nice artwork from your mouse pointer tracking.
2. Jimmy Whales’ theory of failure — Wikipedia founder talks at TED and says: fail, fail, fail.
3. Diagram of secure passwords — How are you choosing your passwords?
4. The number one rule of design — Insightful analysis of the application design process.
5. Printing is getting new life forms, like the Pencil printer and the Paperless printer.

Which is your favourite link of the week? Please share with comments or tweet.

Related posts:

1. Best links of the week 03/2010
2. Best links of the week 04/2010
3. Best links of the week 06/2010

seven: «I’m very busy preparing Linux Day 2010 at the moment.»
geekscrap: «Whoa! it’s in october, isn’t it? You’re taking it early!»
seven: «This year it’s going to be big.»

You’ve been warned.

Related posts:

1. Best links of the week 04/2010
2. Best links of the week 07/2010
3. Best links of the week 03/2010

1. The fact that an enterprise running a mission-critical piece of software can actually survive to bad things(tm) by other means (falling short on their obligations?), doesn’t mean that the mission wasn’t critical, after all. Anyways, mission-critical is just a typical requisite for enterprise applications, not the definition of.
2. If the test is “if installer is next-next-done, then it’s not Enterprise”, it can be easily falsified by examples like Oracle database or Oracle business applications, which are definitely into the Enterprise set but are rather easy to install. Obviously you can achieve complex redundancy setups with Oracle DB or MySQL DB, and both of them require special configuration activities not provided by installer.

Now, I think software quality evaluation for this purpose shouldn’t consider single pieces of software by themselves: CPython is just a component, not a complete solution for any Enterprise task, so any analysis on what’s exactly suitable for a task should take into account at least a group of components that compose a framework for task execution. At most, I can say that some languages foster more software quality than others: for instance, Perl’s CPAN repository shows how difficult it is to achieve a common coding standard with Perl.

IMHO, a definition of Enterprise-grade application should take into account the following features:

1. Processes should respect the ACID principles: wether your application does financial transactions, message delivery or any other kind of workflow, users need to trust on process reliability. This also means that application and protocol modeling should give clear information on what to expect as outcome of a certain operation.
2. Fault tolerance should guarantee that in a closed environment, if prerequisites are respected and maitenance is carried out regularly, the software can accomplish its tasks without interruption, despite technical faults in single components of the underlying hardware.
3. Security best practices (crytography, coding standards, risk management, extensive ACLs, etc.) should be applied to minimize unauthorized access to data and the application should support security features of the underlying system. While everyone claims to be secure today, I think that historical tracking, open-sourceness and quickness of response to threats are good ways to measure safety.
4. System configuration and development practices should follow standards that allow turnover of human resources and market should offer enough qualified personnel and paid support services to guarantee that once the system is up and running, someone exists that can actually keep it running and possibly extend it. Furthermore, market should offer training services and books to save your internal know-how value.
5. New software versions should be released when they’re mature and major releases should keep up with evolution of the market.
6. Software architecture should make performance and TCO grow at most linearly and have an upgrade path that can make your infrastructure serve huge numbers (thousands-to-millions of users) in a modular way (cloud computing is an example of this). Profilation and stress testing should ensure that the application has been engineered to avoid failures under peak usage due to performance hogs. Public independent benchmarks can help estimate processing rate, durability and resources consumption variability.
7. Considering that most Fortune 500 employ Enterprise-grade applications for production management and business management, Enterprise-grade application should offer more complex problem-solving and environment adaptation features than their small-business or consumer counterparts.
8. Documentation and knowledge base should be adequate and up-to-date for most day-to-day needs from users and developers and should match an exact version of the software.
9. Usage data collection and analysis features are an important factor to allow management to plan for resource allocation and to take action upon anomalies.
10. It should be possible to declare in advance a disaster recovery plan to get back on track in a defined timeframe, given a TEOTWAWKI event or subsets of it.

Okay, my definition is really longer than S. Lott’s, but if it was simpler than that, it wouldn’t be Enterprise

At the current state of software industry, products rarely back up their marketing claims of being Enterprise-ready and application obsolescence has become really high-paced, so CIOs approach is more focused on agility than long-term reliability (how many SaaS products never get out of beta these days?). In reality, companies that make profits out of Agile lifestyle are just building on top of strong Enterprise foundations and are avoiding well-known Bad Agile pitfalls. According to Brad Cox’s interview in Masterminds of Programming book (see my review):

Why is computer science not a real science?

Each time you encounter a new piece of of software, you encounter something completely new and unique. How can you have a science where everything is unique?

If you study gold or lead from day to day, you can measure the properties and employ scientific methods to study them. With software, there is none of that.

Enterprise-grade, reausable and reliable components may be one strategy to make software industry a real industry. That’s what Brad Cox thinks and I agree with him. What do you think? Please share your comments.

Related posts:

1. Masterminds of programming
2. What evil lurks in OCFS2
3. Integrate Tornado in Django

Here are the steps to setup multiple uplinks through policy routing on Gentoo:

1. First of all, to access multiple networks, either you have multiple physical NICs or you need to configure your network uplink to let your network ports access multiple VLANs. For more information on VLANs configurations under Gentoo, you can check Gentoo Handbook section on VLANs.
2. On Linux kernel, you need to enable CONFIG_IP_MULTIPLE_TABLES option (in Linux kernel menuconfig, you find it under Networking support => Networking options => IP: policy routing). Recompile and install kernel.
3. Next, you need to install iproute2 package, which allows editing multiple routing tables:

   # emerge -av sys-apps/iproute2

4. Edit /etc/iproute2/rt_tables and add the following route table lines:

   100        T0
   101        T1

5. Edit your /etc/conf.d/net file to enable network startup configuration. First add the following lines, modifying addresses and interface names to suit your needs:

   config_eth0=( "192.168.0.100/24" )
   routes_eth0=(
       "192.168.0.0/24 src 192.168.0.100 table T0"
       "default via 192.168.0.1 table T0"
       "default nexthop via 192.168.0.1 weight 1"
   )
   rules_eth1=("from 192.168.1.1/32 table T0 priority 100" )
    
   config_eth1=( "192.168.1.200/24" )
   routes_eth0=(
       "192.168.1.0/24 src 192.168.1.200 table T1"
       "default via 192.168.1.1 table T1"
       "default nexthop via 192.168.0.1 weight 1"
   )
   rules_eth1=("from 192.168.1.100/32 table T1 priority 101" )

   Then uncomment the following functions (if you copied your /etc/conf.d/net from /etc/conf.d/net.example, they should be already there in comments):

   postup() {
          local x="rules_${IFVAR}[@]"
          local -a rules=( "${!x}" )
          if [[ -n ${rules} ]] ; then
                  einfo "Adding IP policy routing rules"
                  eindent
                  # Ensure that the kernel supports policy routing
                  if ! ip rule list | grep -q "^" ; then
                          eerror "You need to enable IP Policy Routing (CONFIG_IP_MULTIPLE_TABLES)"
                          eerror "in your kernel to use ip rules"
                  else
                          for x in "${rules[@]}" ; do
                                  ebegin "${x}"
                                  ip rule add ${x} dev "${IFACE}"
                                  eend $?
                          done
                  fi
                  eoutdent
                  # Flush the cache
                  ip route flush cache dev "${IFACE}"
          fi
   }
    
   postdown() {
          # Automatically erase any ip rules created in the example postup above
          if interface_exists "${IFACE}" ; then
                  # Remove any rules for this interface
                  local rule
                  ip rule list | grep " iif ${IFACE}[ ]*" | {
                          while read rule ; do
                                  rule="${rule#*:}"
                                  ip rule del ${rule}
                          done
                  }
                  # Flush the route cache
                  ip route flush cache dev "${IFACE}"
          fi
    
          # Return 0 always
          return 0
   }

6. Finally, reboot with your new kernel. My advice is to proceed with this step while you can access your machine locally, just in case anything goes wrong.

Some in-depth on what I described above: with policy routing you can insert additional routing tables and configure your system to use a set of rules to decide which table to apply for each IP packet. So if you create T0 and T1 tables, you can set your host to respond to requests from each interface back to the same interface and load balance routes going to outer network by giving the same weight to both gateways in generic route table.

If you use this setup to publish your server on multiple public networks, you will probably need to configure multiple DNS A records in round-robin over your IPs.

If you’re interested in more Gentoo tips, just subscribe to my feed or follow me on Twitter.

Related posts:

1. Exim ldap lookup multiple DNs
2. Linux RAID disk wipeout
3. Gentooize Part 1: colorize console

Related posts:

1. Linux RAID disk wipeout
2. Using screen as your login shell
3. Gentooize Part 1: colorize console

Here’s the top feeds you should be subscribed to (CVE tags are reported in brackets):

1. NIST Vulnerability Database.
2. US Cert Technical Security Alerts [CERT].
3. SecurityFocus Vulnerabilities [SF-INCIDENTS].
4. Open Source Vulnerability Database [OSVDB].
5. IBM Internet Security Systems Threats [ISS].
6. Vupen Security Advisories [VUPEN].
7. Secunia Latest Security Advisories (Unofficial) [SECUNIA].
8. eEye Security Advisories [EEYE].

The above list is also available as OPML file you can import into your feed reader.

Furthermore, you should subscribe to Operating Systems product-centric vulnerability feeds to ensure you receive timely information regarding updated packages and suggested workarounds for your infrastructure. Here’s a comprehensive list, sorted alphabetically:

1. Apple Security Announce (Mac OS X, iPhone, etc) [APPLE].
2. Checkpoint’s SmartDefense Service [CHECKPOINT].
3. Cisco’s Product & Service Security Advisories [CISCO].
4. Debian Security Advisories [DEBIAN].
5. Fedora Security Updates [FEDORA].
6. FreeBSD Security Advisories [FREEBSD].
7. Gentoo Linux Security Advisories (GLSA) [GENTOO].
8. Mandriva Security Advisories [MANDRIVA].
9. Microsoft’s Security Notification Service Comprehensive Edition [MS].
10. NetBSD Security Advisories [NETBSD].
11. OpenPKG Security Advisories [OPENPKG].
12. OpenBSD Errata [OPENBSD].
13. Red Hat Security Advisories [REDHAT].
14. Slackware Linux Security Advisories [SLACKWARE].
15. Solaris SunSolve Alerts [SUNALERT].
16. SUSE Linux Enterprise Security Advisories (also contains OpenSUSE advisories) [SUSE].
17. Ubuntu Security Notices [UBUNTU].

OS security advisory feeds are available as OPML file as well.

Have I missed anything? Please report if you find some advisory feed I accidentally missed. Also, if you’re into an Operating System security team and you don’t offer a security announcement feed, please consider making it available.

Related posts:

1. Windows back-to-the-future bug
2. Security through obscurity
3. Process management roundup/1

1. USIM card with an embedded Wi-Fi radio — Next generation phone SIM will run local hotspots.
2. European Credit and debit card security broken — You’d better use old signature-based cards.
3. Infineon TPM hacked — It eventually happened. No gory details though.
4. 21st century life in transition — What happens when you apply digital rules in analog world.
5. Twitter History — A nice video with developers from Twitter.

If you have a little more time, you may enjoy this 20-minutes video by Jamie Oliver at TED 2010 on food education. He must have read Ned Batchelder’s tips on presentation: entertain, educate, practice.

Related posts:

1. Best links of the week 04/2010
2. Best links of the week 07/2010
3. Best links of the week 03/2010

Being a Django monkey, I’d like to share some tips on how to make Wordpress and Django live together:

URL mapping

To make Wordpress and Django co-exist, they should map to different parts of the url space: you can simply configure them to respond on different virtual hosts, or just map Wordpress to a specific path. For instance, if your webserver is Apache and you’re serving Django through mod_wsgi, you can use a config snippet like this:

<VirtualHost *:80>
ServerName somehost.com
ServerAdmin hostmaster@somehost.com
ErrorLog /path/to/somehost.com/log/error.log
CustomLog /path/to/somehost.com/log/access.log combined
DirectoryIndex index.html
DocumentRoot /var/empty
WSGIScriptAlias / /path/to/somehost.com/parts/wsgi/wsgi
WSGIDaemonProcess somehost.com user=www group=www threads=25
WSGIProcessGroup somehost.com
Alias /blog/ /path/to/somehost.com/wordpress/
Alias /media/ /path/to/somehost.com/project/media/

<Directory /path/to/somehost.com/wordpress/>
Order allow,deny
Allow from all
</Directory>

<Directory /path/to/somehost.com/media/>
Order allow,deny
Allow from all
</Directory>
</VirtualHost>

Accessing data

To share data between your Wordpress blog and your Django instance, you have two three main options:

1. Save your Wordpress tables and your Django models in the same database and configure your Django models accordingly.
   Pros: this approach is very straightforward and you don’t need to learn Wordpress API. You can use Django admin interface to edit your Wordpress database.
   Cons: sharing a database between two applications can have an impact on maintenance issues. For example, to rehash your Django application, you can’t just drop database, re-create it and populate with syncdb. Wordpress database schema can change in new releases and make your ORM mapping obsolete.
2. Use Python’s xmlrpclib in Django to access Wordpress XML-RPC interface.
   Pros: API changes won’t possibly break compatibility with previous releases. XML-RPC adds more logic, which means more consistency checks and more behind-the-curtain processing.
   Cons: XML-RPC calls are not as performant as direct access to MySQL.
3. UPDATE: Doug pointed me to another method: adding a PHP template loader to Django. An useful video tutorial is also available.

To setup method 1, you can use models.py from django-wordpress-admin project, which was built around inspectdb output with some custom manager enhancements. On GitHub there’s another project named django-wordpress, with the same approach and a step-by-step tutorial is published at uswaretech.com.

If you found Django-Wordpress integration tips useful, please drop a note in the comment box below to say how you used it, or just stay in touch with Twitter or RSS Feed for more Django stories.

Related posts:

1. Integrate Tornado in Django
2. Django dynamic template paths
3. Django and mysql names