Now that you have created your shiny new Jekyll site it’s time to move past the local server hosting on http://127.0.0.1:4000
Assuming you have a LUN that has been provisioned to your server, containing a physical volume, volume group and one or more logical volumes that is currently mounted and in use on your server. You can follow these steps to increase the size of that resource.
At this point I am assuming that you have properly configured your fibre channel adapters/HBA’s, provisioned the ports on the switch, configured proper zoning, and configured multipathing. Possibly I will add that config to a separate post. Assuming all of this, after you have created a LUN on your storage device and presented it to your server, you can follow these steps to create a functional device using LVM commands.
IMPORTANT: This tutorial is not complete. if you scroll to the bottom you will see that there is a bug with mod_wsgi that I have not been able to fix as of yet.
Or an alternate title for this post could be… “LSI, the raid controller I won’t purchase again”… or “MPIO, piss off”
For the purposes of this demonstration i’m going to assume you have Django already installed.
So you have started up a shiny new Django project and probably gone through the getting started tutorial. Somewhere along that line you are shown how to get the “free” functionality of the Django admin pages, along with authentication into the admin section. The next logical step is to say “wow, that’s great I should add some authentication to the views I have created”. A quick Google search will inform you, good. fucking. luck.
Upon starting a recent Django project I quickly ran into an issue where a model I created was intended to hold username/passwords for ssh authentications to various servers. But by default by just calling the admin.site.register(Server) method resulted in the password being displayed in plane text. So lets start jumping through some rings of fire to get a pretty little password field in it’s place.
I have been trying to install the CUDA SDK and related components under Ubuntu 10.10 following the examples on the nVidia website in the following PDF http://developer.download.nvidia.com/compute/cuda/3_2_prod/docs/Getting_Started_Linux.pdf
So this was a major pain in the ass, having to wait 10+ seconds every time I press “ . “ for the content assist window to popup and then another load of time upon typing set,get or anything else.