Jump to content

SchoolBusDriver

Members
  • Content Count

    204
  • Joined

  • Last visited

Community Reputation

0 Neutral

About SchoolBusDriver

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. HTPC Manager unRAID Plugin The old HTPC Manager Project died but Styxit and others have picked it back. They have made 770 commits already and are still working on it daily. New HTPC Manager Website Main Screen from one of my unRAID Boxes CouchPotato SABnzdb sabNZDB Stats NOTES: If you want to make HTPC Manager (or Maraschino) your default program when going to your unRAID server address. Edit the go file on the unRAID USB Stick nano /boot/config/go Change the unRAID emhttp line from this... /usr/local/sbin/emhttp & To this (-p defines what port emhttp will listen too) /usr/local/sbin/emhttp -p 5000 & Restart unRAID for it to take effect. After you restart and access unRAID with the new HTTP port Go to the Settings Tab and change either HTPC Manager or Maraschino to port 80. You MUST run them as user root or else it will not work. Make your life easy and add unRAID to the Applications Module in either HTPC Manager or Maraschino. Missing Package for Stats to work (PhAzE will eventually add it to his GitHub or elsewhere) I had to compile a missing package for the stats page to work. I do not have a place to store it where the plugin will automatically download it during install. HTPC Manager will work fine without it but the stats tab will not. Until PhAzE has a chance to convert this plugin, if you want to use the stats page: Download Link ---> psutil-2.1.1-i486-1.tgz to /boot/packages on your unRAID USB Flash Drive and install it. installpkg /boot/packages/psutil-2.1.1-i486-1.tgz You will need to stop / restart the HTPC Manager after you install the package. Once PhAzE adds it to his Github and updates the plugin, everything will be automated. Stats Configuration Page Ignore the directions on the HTPC Manager Configuration Page and do not put a comma between different entries (filesystems, mount points, etc). My Ignore Mountpoint (notice I put spaces and not commas like it tells you too /mnt/disk1 /mnt/disk2 /mnt/disk3 /mnt/user /var/log /proc/fs/nfs HTPC Manager Plugin htpcmanager.plg <---- Download link
  2. I agree. Nano as a plugin is crazy considering the size of it, what it is and pretty much any documentation / blogs / guides a Linux noob will see on the Web will use nano over VIM. Personally... I am not writing a guide or posting a VM Appliance until the next beta (which will have nano in it). Like it or not, for users to do a lot of the Xen / VM Appliance stuff it requires editing some cfg files. If that isn't isn't hard enough... Imagine writing a guide and having to explain to a novice how to use VIM on top of that... Hit "a", then add what you want, hit "esc" and move there to delete, hit "d", then "del" until it's gone, then hit "esc", then ":", then "w" and then "q", etc. Screw that noise! The dorks that get off on VIM can continue to use it and impress their dork friends on how "cool" they are. The rest of us will use nano. What were you thinking? Any ideas / suggestions on how to do this?
  3. Wow! This is one of the best guides on here. You really knocked it out of the park with this one. From the nice VM Appliance all the way through the documentation. Keep up the great work and put a donate button on this!
  4. That isn't my call to make. I am making suggestions to Tom from his point of view with everyone in mind. I haven't tried running Xen with iommu=1 on a motherboard / bios that doesn't support / do IOMMU to see what happens (good, bad, nothing). If I was Tom, I would leave it out. When someone wants to do PCI Passthrough they will follow a guide and have to add the PCI Device IDs to syslinux.cfg anyway. Adding iommu=1 at the same time shouldn't be an issue. Plus, I suspect that the people who do need / use PCI Passthrough will be small compared to those who do not.
  5. I suggested the following and Tom has said they are going into the next release: 1. Do not assign a set amount of memory to Dom0 and make syslinux.cfg look like this: label Xen 4.3.1 / unRAID OS kernel /syslinux/mboot.c32 append /xen dom0_max_vcpus=1 dom0_vcpus_pin --- /bzimage --- /bzroot label Xen 4.3.1 / unRAID OS Safe Mode (no plugins) kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot unraidsafemode Since a lot of people use a Cache Directories (a memory hog), let Dom0 get assigned all the memory. That way if memory runs low, the VM has the issues / crash (as a previous user a few posts up experienced) and not unRAID. Even with all the memory assigned to Dom0 (unRAID), the VMs can still use / grab it but unRAID has the priority and will take back what it needs. Note - By default, this how most Linux Distros handle it. 2. You will probably want to dedicate at least one CPU to Dom0 by default. label Xen 4.3.1 / unRAID OS kernel /syslinux/mboot.c32 append /xen dom0_max_vcpus=1 dom0_vcpus_pin --- /bzimage --- /bzroot label Xen 4.3.1 / unRAID OS Safe Mode (no plugins) kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot unraidsafemode a) Dedicating a CPU core only for dom0 makes sure dom0 always has free CPU time to process the IO requests for the domUs. b) When dom0 has a dedicated core there are less CPU context switches to do, giving better performance. c) Assigning more than one isn't going to make Dom0, write files faster to unRAID or make the VMs run any faster.
  6. We aren't reinventing the wheel or blazing new trails in Virtualization. Businesses / Enterprises have been virtualizing MILLIONs of Servers which run very complex multi-million apps like ERP, Video Conferencing, etc. for over a decade. There are PLENTY of users here in the unRAID forum who use Plexx in a VM in either XenServer or ESXi. Not to mention the MILLIONS of home users who run ESXi / XenServer with Plex in a VM (who don't use unRAID and posts in other forums). Simply put... You won't notice any difference with your Plex App running in a VM with Paravirtualized Drivers compared to bare metal.
  7. Here you go... wget http://ftp.lip6.fr/pub/linux/distributions/slackware/slackware64-14.1/slackware64/a/usbutils-007-x86_64-1.txz installpkg usbutils-007-x86_64-1.txz
  8. You have 4 options... Option A Shrink / Expand Ironics image. Issues: 1. You can't do it in unRAID. You have to do it in a regular Linux Distro. 2. It's very COMPLICATED and not noob friendly. Option B 1. Create a 25GB, 50GB, 100GB, etc. whatever image file ("data drive"). 2. Format your "data drive" with ext4. 3. Add this "data drive" to your VM Appliance cfg file. Example: 4. Start your VM Appliance and login as root. 5. Create a data folder in the root. 6. Change ownership and permissions 7. Edit fstab and mount the "data drive" to /data Example of what to add: 8. Users will configure Plex, sabnzbd, Sickbeard, Transmission, etc. to use /data in the VM for where they store Plex stuff. Plus where they download, unrar, etc. stuff before it's moved to unRAID. Option C Ironic post several images of various sizes (5GB,10GB, 50GB, 100GB, etc.) for his All In One VM Appliance. (or add this to page one on how to create a "data drive" in a VM) Option D Ironic has a Plex, XBMC, Usenet Indexer, Owncloud, etc. VM Appliance of various sizes (5GB, 10GB, 50GB, 100GB, etc.) or use Option B above. (or add this to page one on how to create a "data drive" in a VM) Issues: I mentioned separating things like Plex and creating a Plex VM Appliance (like you would an XBMC one) but Ironic doesn't want to create / support more than one VM Appliance and he did not think it was a good idea for running several VM Appliances either. He prefers an All In One approach. Typically XenServer and ESXi people have Usenet Indexers, MakeMKV (converting, ripping, etc. Blurays / DVDs / Video Files), Plex, XBMC, etc. running in their own VM Appliance. Why do we do that? 1. Some Applications are more memory, CPU, network, database, etc. intensive than others. It's best you separate those if you can and have more "control" over the VM and the resources you assign to them. 2. With Plex, Usenet Indexers, MakeMKV, XBMC, sabnzb, sickbeard all running at once along with copying / moving files to unRAID via Samba / NFS, etc... EVERYTHING is going through ONE NIC and you have no option to split that traffic between multiple NICs. (See: Networking inside Xen) 3. Usenet Indexers, XBMC, Plex, owncloud, etc. can / do have their own database that you run in Mysql (Mariadb) and many of us do not want every app all in one Mysql instance but prefer separate ones. Usenet Indexer would be a great example of this. The data is HUGE and where everything is stored. It also makes backing up your MySQL database easier too. 4. When you update / upgrade the underlying Linux Distro or complex programs like Usenet Indexers, XBMC, Plex, etc. you could break one App, several or all of them. What is the point of being able to run multiple VMs and keep your unRAID "clean" but duplicate the orginal problem and put all your eggs (all your apps) into one VM Appliance. If it breaks, has issues, etc... You lose one, several or all the Apps that you run in an All In One. Hopefully others will post VM Appliances in the near future... Some we could use are: pfSense XBMC Usenet Indexer Owncloud unTangled Tvheadend VDR A Hardened / Secured VM Appliance where users can have it sit outside their Firewall and add Apps they want to have access from the Web. Etc.
  9. Surprised Ironic did install this in his VM or nobody else suggested it... Webmin. You can manage your VM all from a WebGUI. Right now it's flagged out of date on Arch but I bet it works and will be updated shortly. There are also a lot of plugins / skins for it. The OpenVPN add-on is in AUR.
  10. Believe it or not, we actually agree on something. Informative and good post.
  11. Actually when you install apps / services / sockets / targets / slices / tools / libraries / etc all the systemd files are installed in the following directory: /usr/lib/systemd/system That is where you will find things like xbmc, nfs, samba, mysql and all kinds of various things linux uses / needs during start up. There will be 175+ (Mine has 230) systemd files in that directory. When you run the above command.. It creates a symbolic link from /usr/lib/systemd/system to /etc/systemd/system and depending on the app / socket / service / slice / target it can either be in system or multiuser. Usually multiuser for 90% of things users will run into.
  12. I agree. Hopefully in time either Tom or a user develops a Plugin or WebGUI that is point and click. You are right. Tom has said he adding it in the next release. 1. Nobody said crap comments about Joe. 2. Joe did get pissed, he demanded the guy remove it from his GUI all of those are true / facts. 3. Neither Speeding Ant or Joe was bad just a difference of opinion. 4. Preclear is open source. If Speeding Ant or I want to take to preclear, use it as in another product, modify it, add it to a GUI for unRAID or FreeNAS... Anyone can do it and there is NOTHING wrong with it.
  13. 1. Why? 2. The users will not be able to do it in unRAID 6.0. The img file has a partition and multipath and various Linux tools you need to mount it are not enabled / installed in unRAID. 3. Assuming multipath was enabled / installed... A user would have to extend the image file, extend the partition and then extend the file system. That isn't easy. 1. Your "job" is to provide VM Appliances that users install and configure / customize to their liking and keep your repo up to date. 2. You need to have a bunch of VM Appliances not a all encompassing ONE. Otherwise you are going to make your life / the users life hell. People who run ESXi and XenServer have SEVERAL VM Appliances not just ONE. Why would you do anything different? 3. Why would a user need to continue to download your image, install it over their old one when Sickbeard has an update? The user would do the following instead: pacman -Syyu The user should only have to install VM Appliances once and keep it updated not continue to install image after image. Option A It's easier to have multiple versions of the same VM Appliance but have different sizes of it available for download (if you / they do not like Option B below). Option B 1. Provide instructions on how to create a 25, 50, 100GB, etc. whatever image file ("data drive") and how to format it with ext4. 2. Provide instructions on how to add this "data drive" to the cfg file. Example: Within your image, create a data folder in the root. In the /etc/fstab have a commented out mount for it and provide instructions on how to uncomment it out. Example: Going forward the users will configure sabnzbd, Sickbeard, Transmission, etc. to use /data in the VM for where they download, unrar, etc. stuff before it's moved to unRAID. A few other things you need to consider 1. Create several Vanilla Arch VM Appliances (of various sizes or option B above) and provide instructions for installing the apps. If I install you vanilla image and I only want / use Sabnzbd, Sickbeard, Couchpotato, Headphones... All I have to do is: pacman -S sabnzbd sickbeard couchpotato headphones To enable start on boot (or you could edit your packages to do it for them): systemctl enable sabnzbd systemctl enable sickbeard systemctl enable couchpotato systemctl enable headphones 2. Create separate dedicated VM Appliances for complex things like Plex, XBMC, Usenet Indexers, etc. This is how everyone does it now if they have a ESXi or XenServer... So you should do it too. 3. All in one solution with all those apps installed running in one VM is a receipt for disaster and you are going to have 945 versions of it and you still want make everyone happy. It sort of defeats the purpose of running VMs in the first place. I would have several different VM Appliances. For example: VM Appliance - sabnzbd, sickbeard, couchpotato, headphones, media front end and torrents VM Appliance - Plex VM Appliance - XBMC VM Appliance - Owncloud This is a VM Appliance / App people will probably want outside their firewall. If so, they are going to want to secure / harden this VM Appliance (might want to consider something other than Arch). VM Appliance - Vanilla Arch (with instructions on how to install the various apps of their choice)
  14. My preference is the same as yours... WebGUIs / Plugins that work 100% of the time and do not crash the server. Reality... Neither exist today and there isn't anyone interested or volunteering to write / develop the WebGUIs and Plugins we will need. I'm willing to chip in some money to see if we can get this done. Are you? If so, how much are willing to donate?