Controversial posts made by travisdh1

The idea behind CALs, great. The implementation of it, horrible.

@Mike-Davis said in Vendor Mistake - VMware Infrastructure Decisions:

I haven't found a case where the cost of vSAN made sense with so many other options out there. I think with 3 hosts and 2 CPUs each he would be in the neighborhood of $14,000 for the vSAN licenses. Has anyone found a good use case for vSAN?

Really? Geesh, nevermind, XS7 + gluster.

@JaredBusch said in 2600hz.org - Open Source VoIP:

@RojoLoco said in 2600hz.org - Open Source VoIP:

@JaredBusch said in 2600hz.org - Open Source VoIP:

@RojoLoco said in 2600hz.org - Open Source VoIP:

@scottalanmiller said in 2600hz.org - Open Source VoIP:

2600Hz is the vendor here. Kazoo is the actual product name, which is better as 2600Hz is a bizarre name for a project.

2600Hz is a bizarre name for anything... should be 26kHz.

@scottalanmiller & @RojoLoco it most certainly is not a strange name for a telephony project.

https://en.wikipedia.org/wiki/2600_hertz

Yeah, not a name to get market share or branding wiht, but it is a peffectly logical name for telephony.

Ah. Learned something new. But as an audio guy, my point was that it would be 26k vs. 2600. Didn't realize that was a significant frequency in telephony.

26k is upper bound of hearing right?

Most people's hearing falls off around 19k. Teenagers and children can hear up to a possible 20k. 2600 was probably chosen because people can't hear it (the dog, cat, or ferret tho..)

@stacksofplates said in XenServer Disable Root:

@travisdh1 said in XenServer Disable Root:

@stacksofplates said in XenServer Disable Root:

@travisdh1 said in XenServer Disable Root:

@stacksofplates said in XenServer Disable Root:

@travisdh1 said in XenServer Disable Root:

Why is the management interface even on the standard network instead of on a VLAN or dedicated management network?

Well it's on our server VLAN, but as I don't control the network I can't see what has access to what. Plus even if that's considered local console access, users created on the system have root access through that console. So if I log in as jhooks through XenCenter, I'm given the root console. So I can't hand off any access to anyone else to just control the VMs.

So someone else HAS to be responsible for that portion. Inform the boss of the requirements, and that it's beyond your assigned duties. Not your problem.

I'm responsible for our systems meeting our security requirements. If I can't stop things like that from happening, I'll have to use something else. We have

So you can't do you're job. You need to communicate this to management, and get that network information. You literally CAN NOT do even basic security without that very basic information!

Sorry I meant I if I can't stop other people running VMs from having root access on this system I'll need to use something else. That's kind of crazy that if I connect to a host with XenCenter as a non privileged user, I still get the root console. I don't understand that.

I know what you mean. I'm sorry, I don't know how to state this another way so you could maybe understand. This is why you need to know how the network is configured. It's right in the configuration documentation for XenServer. The management interface goes on a private network, period, end of story.

@Dashrender said in LastPass Replacement?:

@scottalanmiller said in LastPass Replacement?:

@dafyre said in LastPass Replacement?:

Because they got bought out by LMI(Log Me In), I think... and in some circles, LMI has a horrid reputation.

That and they are not free. But mostly the LMI buy out.

For the cloud auto sync options, I'm totally fine paying $12/yr. But the LMI thing does bug me.

Yeah, call this a preemptive action on my part. I don't want LMI getting any $$ from me.