Scruffie

That's what we're using Deadline for...

For posterity in case anyone comes across this. Within the default nginx conf file I added a 301 rule location /somepath { return 301 https://linustechtips.com/ ; } now, when I browse to subdomain.domain.com/somepath it will take me to https://linustechtips.com/

long story short, it's for someone else who is paying me. what they want goes, no questions. Second, I'll explain it more thoroughly as I did a poor job before. For example, lets say I have this link: https://static.boredpanda.com/blog/wp-content/uploads/2018/10/cutest-puppy-dog-pictures-coverimage.jpg Well, I don't want to type that link, but I want to redirect it from my own url. Now, I don't have access to the DNS control panel to create a domain forward rule. What I do have however is a subdomain pointing to a linux vm that I'm using. My plan was to use that VM, and Nginx (or apache, whatev) to create a link forward rule. so I was going to forward, or use a 301 return rule to return the above link when someone writes subdomain.domain.com/somepath

Hey guys, so as it says I'm wondering if this is possible.. I have a droplet with DigitalOcean, and an a record pointing to said droplet. Would this be possible subdomain.domain.com/link1 -> route over to droplet with nginx, nginx has a 301 conf that says subdomain.domain.com/link1 will return randomsite.com/somepath I'm not hosting the website on the droplet, just using it to redirect the URL. I can't do it at a DNS level as I don't have access to the domain, so I'm left with routing it through the droplet. Let me know if I can provide further information!

I was tossing so many options around. Currently using DDWRT for stuff, but the router does not support vlans. Was thinking of something like an edgerouter x by ubiquiti and using their UNMS controller, or trying to do a mITX pfsense build? What would you recommend?

Right, so that makes more sense. the subnet mask would only need to increase in size if you needed to support more than 255 devices on a specific vlan? So all three vlans could have a /24? an youre saying for WAN on all three vlans have everything open so theyre able to talk to the web, and all remotely accessible to each other, and then for the lans have all ports closed off on all of them except for ports x, y, and z? and same thing for devices/ips? -> = ping, or interact -|- = unable to ping, or interact If i'm understanding this then I could specify 192.168.1.x -> 192.168.2.x, 192.168.3.x (if my ip was 1.x I could ping/interact with anything on 2.x, and 3.x) and also specify 192.168.2.x, 192.168.3.x -|- 192.168.1.x the .x could be for any number of devices, on any number of ports

For those in here that know, I was wondering if you could help me calculate some subnets and let me know if what I'm thinking of is possible. So, I would like to have 3 separate networks(vlans). N1, N2, N3 I was thinking vlan N1, and N2 would have a subnet mask of 255.255.255.0 (from my limited understanding, this would ensure they do not see other VLANS?) and then vlan N3 would have another subnet to allow it to access both N1, and N2 I would like N1, and N2 to be visible and interactable from N3 (N1, or N2 could not see N3) N1 would be separate from both. It would think it's by itself N2 would be separate from both. It would think it's by itself Is this possible? Would it just be configured via inter-vlan routing? Also what would the subnet be for N3? reason for doing this is to separate N1, and N2 traffic from each other. N3 would be more of a management role, amongst other things. devices on N3 would need to manage devices on either of the other networks

Unfortunately there is hardware differences between the nodes. As certain blocks of the farms were purchased separately. and I'm running windows

Hey guys, how's it going? I've recently been tasked with expanding an animation render farm with multiple nodes connected to it. It is a CPU based render farm (infrastructure is heavily invested is CPU rendering, GPU rendering would require a paradigm shift. Too expensive ATM) with about 25 nodes hooked into it. We currently use AWS's Deadline to manage render provisioning and queuing. The current configuration works quite well actually, however, I'm rapidly running into a management/time bottleneck. If any node needs any sort of software updates it is currently handled manually. Which is fine, on a one off basis. however, if an entire suite needs to be upgraded across the farm this suddenly becomes a massive time sink that will only become worse as the farm expands in size. Is there some sort of management solution out there that can handle this? I understand you can deploy software packages through group policy, however I'm not sure you can deploy software the requires a unique serial number through GP. Basically my wish list would be to have some sort of management console to deploy/update software packages and licensing management and perhaps also manage windows settings on the side (windows updates, IP configuration, etc.) Hoping someone knows of a solution, or can point me in the right direction.

Yeah, was thinking that. Would you recommend I just create the raid array on the host OS, and then install the windows vm (with plex) on the array, and just use the same array for storage?

Planning on it aha. Sorry, haven't really configured software on this level before. I'm still learning Thanks for all of your help, though!

No, I was going to use it to use freeNAS to host plex. However, I could just use Win7 to host plex. My main concer was whether I should create the RAID array in the host OS, or create it in the VM. I've come to the conclusion that creating the array in the host OS and then installing the VM on the array and using that storage would probably be better? Sorry for the confusion!

Why separate software? Isn't with does server capable of forming RAID configurations on its own?

Ah, fair enough. Will look into it! Was just wanting the VM's so I could separate the data without having two separate physical servers. Was trying to take advantage of virtualization

Sorry, I'm not sure you're understanding where the Linux VM will be. The Linux will be under its own, separate VM than FreeNAS. FreeNAS will be used to host/run Plex. Windows server will just be there to host the VMs.