Talk:OpenStack: Difference between revisions

From Alliance Doc
Jump to navigation Jump to search
No edit summary
No edit summary
 
(13 intermediate revisions by 4 users not shown)
Line 1: Line 1:
CERN docs on OpenStack, might be helpful [https://clouddocs.web.cern.ch/clouddocs/ https://clouddocs.web.cern.ch/clouddocs/]


==New combined CLI tool installation==
Add a section about re-sizing volumes, mention alternatives, e.g. ZFS +zpools+adding new volumes
{{command|sudo apt-get install python-dev python-pip}}
{{command|pip install python-openstackclient}}
see [[http://docs.openstack.org/cli-reference/common/cli_install_openstack_command_line_clients.html http://docs.openstack.org/cli-reference/common/cli_install_openstack_command_line_clients.html]]


To install on a machine (ACENET specifically without admin privileges) use:{{command| pip install --user python-openstackclient}}
[[User:Cgeroux|Chris Geroux]] ([[User talk:Cgeroux|talk]]) 17:37, 17 December 2018 (UTC)
which installs to ~/.local/lib/pythonX.Y/site-packages/ so by adding <code>export PYTHONPATH=${HOME}/.local/lib/python2.7/site-packages/:${PYTHONPATH}</code> to your <code>.bashrc</code> file if you are using Python major version X=2, and minor version Y=7.
----


It seems that the new openstack command line client, works more interactively? If I run the command
[http://www.example.com link title]This page states:
{{Command|openstack}}
 
starts up an interactive prompt and get get a list of available commands by typing <code>help</code> at the openstack prompt. Useful user accessible commands are {{Command| openstack server}} {{Command| openstack volume}} {{Command| openstack container}} {{Command| openstack object}} {{Command| openstack network}} {{Command| openstack security}} {{Command| openstack image}}
: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." Edit: The reason I point this out is I don't want users believing that virtualization is inherently slow (or has performance ramifications), such is the case in emulation (in general).
--[[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)
 
CERN docs on OpenStack, might be helpful [https://clouddocs.web.cern.ch/clouddocs/ https://clouddocs.web.cern.ch/clouddocs/]<br/>
Add a section about CloudInit? [http://cloudinit.readthedocs.io/en/latest/ 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:  {{command| curl -s http://169.254.169.254/openstack/latest/user_data}}  
from the particular VM in question.
 
traduction ː 2018-04-15, cross-pollination between OpenStack, Creating a VM under Linux, Creating a VM under Windows / need to review comments from ChrisGeroux on Slack

Latest revision as of 17:37, 17 December 2018

Add a section about re-sizing volumes, mention alternatives, e.g. ZFS +zpools+adding new volumes

Chris Geroux (talk) 17:37, 17 December 2018 (UTC)


link titleThis 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." Edit: The reason I point this out is I don't want users believing that virtualization is inherently slow (or has performance ramifications), such is the case in emulation (in general). --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:

Question.png
[name@server ~]$  curl -s http://169.254.169.254/openstack/latest/user_data

from the particular VM in question.

traduction ː 2018-04-15, cross-pollination between OpenStack, Creating a VM under Linux, Creating a VM under Windows / need to review comments from ChrisGeroux on Slack