I got in and for a while it said the conference was over, then it started. But no audio Phones aren't working here so can't dial in as we have that flapping router on the island so everyone gets new IPs down here every ten seconds or so, so even signing into a lot of websites is hard.
@Dashrender Thanks for the feedback. The training will include some leave-behind materials to help you recall any specifics. Additionally, there is always the user's guide to refresh your memory, or you can always call our support number for 24/7 assistance.
@Kelly The available virtual cores you can assign to a particular VM match the number of logical threads(for hyperthreading) on the nodes. If you have identically spec'd nodes there will be no restrictions put in place beyond that for the number of virtual CPUs you can assign to a particular VM.
The limit of number of virtual cores to the smallest amount of logical threads is specifically to prevent issues with over-provisioning so there are automatic limits put in place to prevent issues that would cause VMs to not be stable.
I'm really glad to hear you are purchasing a cluster and we look forward to working with you.
A common option for small environments would be to simply include the driver package on a Windows SMB file share in a centrally accessible, read only folder that can be seen from each VM. Then just log into each VM and double click to update! Easy Peasy.
For larger environments, Group Policy will be the most common approach.
@Dashrender yes, I was thinking of agentless solutions like Veeam. So if it has KVM support it will work with Scale?
I wish I could help you with this. No place that I've worked at has needed something that big
I came really close - I just missed the Scale boat. 3 years ago when looking at a replacement EHR I posted about some ridiculous needs. Many conversations with Scott - and Scale never came up. Looking back, I have to assume that Scale wasn't something we knew about quite yet. Instead I was looking at a $100K two server setup with something like 20 disks each (mainly for IOPs - this was pre acceptable SSD pricing). Management went with another solution (one they hate today) because the startup costs where so high.
It started life on a bare metal 2003 R2 server in late 2007. Lived there until last year, when with the help of a friend who used to work for the now gobbled and displaced EHR company, he helped me migrate the entire thing to a Windows 2012 R2 VM. This VM is 750 GB total storage assigned, using around 640 GB. It's not growing anymore, pretty sure it's thin provisioned (it is, but it's expanded itself out to 716 GB).
This VM host has 1.1 TB of RAID 10 (8 drives 10K 300 GB).
Will end-users be able to grow slowly? IE: Grow from one node to 2... and then eventually buy a third?
or would it be a jump straight from 1 node to 3 nodes?
Unfortunately at this time there is no means of growing from one to two. The jump is from one to three and one node at a time from then on. This is because of the need of a witness to avoid split brain of the cluster. One node avoids this by not having high availabilty, three and more nodes handle this by always having a witness. At two nodes there are complications that do not exist otherwise. So at this time, there is no two node option.
Except, of course, if you were in a situation where two nodes was useful through replication. That works with two nodes.
Looks like your connection to MangoLassi was lost, please wait while we try to reconnect.