Home Lab Hypervisor
-
@Jason said:
@BRRABill said:
@scottalanmiller said:
No major cloud does that. I'm not aware of any that do that, actually. They all (AFAIK) charge as long as the VM exists, powered on or not.
After we discussed that the other day, I found out the Azure does not bill in the stopped (de-allocated) status
Yep azure does lots of cool things. We even have a direct gigabit uplink to Azure.
But it bills exactly the same as AWS. If you stop your VM, you continue to pay. It tells you this in a big warning when you power down a VM. It explains that when you go to power it down so that you don't think you will be saving money.
All of the big clouds work the same. Because you still have the resources allocated until you destroy the instance.
-
@BRRABill said:
@scottalanmiller miller and I were discussing "pay as you go" the other day. I wonder if other cloud providers work the same way.
They all work the same. All major clouds have identical billing models. Someone, somewhere does something differently but none of the real players. Amazon, Google, Microsoft Azure, Digital Ocean, Vultr, Joyent, Rail Yard, Heroku, Rackspace, IBM Softlayer, Verizon, etc. all the same. Different prices, different features but the same model for billing.
-
@scottalanmiller said:
It DEFINITELY bills when stopped. It does NOT bill when deleted. Deleted is obviously stopped, saying stopped implies that it still exists.
Is "Stopped Deallocated" deleted?
-
@BRRABill said:
@scottalanmiller said:
It DEFINITELY bills when stopped. It does NOT bill when deleted. Deleted is obviously stopped, saying stopped implies that it still exists.
Is "Stopped Deallocated" deleted?
I have no idea. Is that a term that someone uses?
Simple question is... can it be turned back on? If so, then no. The ability to turn back on means you didn't stop paying.
-
It has been the state of the machine is in Stopped (Deallocated) means that you have made a shutdown by Web Management Interface Azure ( SHUTDOWN BUTTON ). In this way the cost of virtual machine will not be charged, but the public and internal IP will be deleted.
-
@BRRABill said:
It has been the state of the machine is in Stopped (Deallocated) means that you have made a shutdown by Web Management Interface Azure ( SHUTDOWN BUTTON ). In this way the cost of virtual machine will not be charged, but the public and internal IP will be deleted.
If that is the wording from Azure then it is new. The last time I powered down an instance on there, which was not all that long ago, they stated very clearly that you would be charged in that instance.
-
This implies that you now get free storage? So you could put a 1TB file server up there, power it down and it is free for forever?
-
@scottalanmiller said:
This implies that you now get free storage? So you could put a 1TB file server up there, power it down and it is free for forever?
Seems like perhaps you are indeed still charged for storage.
Though since the plans come with storage I don't know what that means.
-
@scottalanmiller said:
This implies that you now get free storage? So you could put a 1TB file server up there, power it down and it is free for forever?
They give us free storage on Stand by servers. but, I don't think that is normal. I think the normal way is you get billed for storage on shutdown servers.
-
@Jason said:
@scottalanmiller said:
This implies that you now get free storage? So you could put a 1TB file server up there, power it down and it is free for forever?
They give us free storage on Stand by servers. but, I don't think that is normal. I think the normal way is you get billed for storage on shutdown servers.
We always have. But maybe they changed it.
-
Update:
Pulled the trigger and went with this build: http://www.ebay.com/itm/231784944527
It has the H700 raid controller, a fair amount of memory, and an internal SD Card module. I purchased a ~$120 lot of 4 used 1TB disks for storage.
-
Nice. That will be fun.
-
Server arrived early and everything was as expected. I've got XenServer installed and my first VM deployed. So little work required to configure everything. Install from the XenServer iso and most everything is done!
I spun up and configured an OpenVPN server on a CentOS 7 minimal install and had VPN connectivity to my home network in no time!
I must say I like XenCenter on Windows 10. I've previously been using virt-manager (when not using qemu-img and virsh at the console) with the KVM hypervisors I work with, but wow is XenCenter more polished.
As soon as I have time I'm going to sit down and deploy/configure a XenOrchestra VM and compare the functionality between XenCenter and XO firsthand. I also plan to get the backup vm backup script in place and setup. A near-future project may involve configuring an old HP Desktop to function as a BSD-based NAS for storing backups...
Anywho... Thanks again for all of the input, I'm pleased with the outcome thus far.
-
I'm actually setting up an XO VM right now...
Great minds.
From what I saw though, in a future release (coming soon...) they are building in incremental backup functionality to XO.
Which is AWESOME.
