Talk:OpenStack: Difference between revisions
No edit summary |
(Correction) |
||
| Line 1: | Line 1: | ||
This page states: | |||
:It allows the creation and management of virtual machines ("VMs", or "instances"), which act like separate individual machines, by emulation in software. | |||
I think that saying this is emulation really downplays the technology behind this nowadays you would be hugely wasteful to emulate AMD64. Virtualization is better as a term but if you are concerned about circular logic with that you can say "virtualization, similar to emulation but using hardware acceleration." | |||
--[[User:Bk12fy|Brad Kennedy]] ([[User talk:Bk12fy|talk]]) 17:08, 21 July 2017 (UTC) | |||
---- | |||
TODO: add a section about uploading images (note, very important to specify image format) | TODO: add a section about uploading images (note, very important to specify image format) | ||
Revision as of 17:08, 21 July 2017
This page states:
- It allows the creation and management of virtual machines ("VMs", or "instances"), which act like separate individual machines, by emulation in software.
I think that saying this is emulation really downplays the technology behind this nowadays you would be hugely wasteful to emulate AMD64. Virtualization is better as a term but if you are concerned about circular logic with that you can say "virtualization, similar to emulation but using hardware acceleration." --Brad Kennedy (talk) 17:08, 21 July 2017 (UTC)
TODO: add a section about uploading images (note, very important to specify image format)
CERN docs on OpenStack, might be helpful https://clouddocs.web.cern.ch/clouddocs/
Add a section about CloudInit? http://cloudinit.readthedocs.io/en/latest/
Want some clarity about the differences between an image, a snapshot, and a bootable volume, as well as "Boot from image (creates new volume)" and "Boot from volume snapshot (creates new volume)".
Note about cloud init, if you are dynamically creating your cloud init file, say through heat, then you can see the result that the particular VM sees by going to:
[name@server ~]$ curl -s http://169.254.169.254/openstack/latest/user_data
from the particular VM in question.