If we hot a blade system, we would not be able to 'fit' those drives. Each 
blade can fit 2 drives and they must be 2.5" sas drives.

Sent from my iPhone

On Aug 25, 2012, at 2:03 AM, Ken DeWitt <kendew...@yourfellowtechguy.com> wrote:

> I would like to give a suggestion so that the hardware that everyone has paid 
> for it their current server be added to the vm server meaning their hard 
> drives not the motherboards.  The hard drives can be labelled so the admins 
> know who's drive is who's.  Why I was suggesting this is because I was 
> reading in the email that someone could help the members convert their 
> current servers over to a vm server with their current os, scripts and all 
> the software they worked so hard on and sent so much time on setting up.  
> This will still give the members a system as close to their current systems 
> as possible.  I don't know if this is possible to link the hard drives with 
> the different vm logins for each user.  Something else that would help with 
> adding all the hard drives if the members want to is to sell their current 
> hardware minus the hard drives and put the money or a portion of the money in 
> a put to add hardware raid cards, better motherboard and more ram.  Then all 
> the money they invested in their current servers does not all go to waste.
> 
> Hope that makes sense.
> 
> Any question or comments you can email or call me at any time.
> I will get back to you as fast as I can.
> 
> Thank you and have a nice day!!
> 
> Ken DeWitt
> Your Fellow Tech. Guy
> 
> Phone # : 204-998-3218
> Email: kendew...@yftg.ca
> 
> 
> 
> 
> On Sat, Aug 25, 2012 at 12:02 AM, Mark Jenkins <m...@parit.ca> wrote:
> On 23/08/12 11:53 PM, ayecee wrote:
> Yes, Mark runs a VM server. It runs noisy and hot even when lightly
> loaded, and when your VM stops working, you can't go to the space and
> kick it.
> 
> I'm presently unable to login to my account on it, and some day I'll get
> around to rectifying that.
> 
> Problem solved.
> 
> But, the vm service (vmsrv) in itself was not to blame for ayecee's issue. 
> (hence the subject line)
> http://www.skullspace.ca/wiki/index.php/Vmsrv
> 
> Ayecee has a MUMD account -- which is a service running under vmsrv.
> http://www.skullspace.ca/wiki/index.php/Mumd
> 
> One of the upsides of a mumd account is that you can use it to log into the 
> vmsrv host operating system as well.
> 
> This is documented in the vmsrv wiki page:
> """[vmsrv] Accounts
> 
> Pick one of two ways to get an account:
> 
>   *  Ask the admin team (Mark Jenkins <m...@parit.ca> and Alex Weber[??])
> 
>   *  Use the automated claimid process for mumd at http://192.168.1.28 . mumd 
> accounts are made available to the vmsrv host system via the wonders (and 
> down sides) of LDAP.
> """
> 
> It was the mumd service that was broken, and by no fault of vmsrv.
> 
> Anyone with a plain old fashioned passwd/shadow account on vmsrv (option #1 
> above) would have been fine (able to login and use virtualbox) and unaffected 
> by the ldap issue the mumd service was having recently. (not sure exactly, 
> problem went away when I restarted the mumd slapd).
> 
> 
> vmsrv has been up for the past 64 days.
> 
> 
> I'm going to take three actions to avoid any further MUMD issues hurting the 
> reputation of vmsrv
> 
> 1) Remind all MUMD users of this downside and offer to create regular 
> passwd/shadow accounts on the vmsrv host OS for them.
> 
> 2) Encourage the new vmsrv users who are now coming out of the woodwork to 
> choose a regular passwd/shadow account over the MUMD option
> 
> 3) Install an automated claimid process like MUMD has so that a vmsrv account 
> can be activated automatically by anyone on the Skullspace LAN -- this avoids 
> the hassle of sending me an email to request an account.
> (This program has to escalate to root in order to change /etc/passwd and 
> /etc/shadow, I already have it written from the old pre-vmsrv MUMD days. Much 
> effort went into security considerations in the code, I'll get it up on the 
> Skullspace github to encourage feedback)
> 
> 
> _______________________________________________
> SkullSpace Discuss Mailing List
> Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss
> Archive: https://groups.google.com/group/skullspace-discuss-archive/
> 
> _______________________________________________
> SkullSpace Discuss Mailing List
> Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss
> Archive: https://groups.google.com/group/skullspace-discuss-archive/
_______________________________________________
SkullSpace Discuss Mailing List
Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss
Archive: https://groups.google.com/group/skullspace-discuss-archive/

Reply via email to