Talk:OpenStack: Difference between revisions

From Alliance Doc
Jump to navigation Jump to search
No edit summary
No edit summary
 
(11 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/]


==Combined OpenStack CLI tool==
Add a section about re-sizing volumes, mention alternatives, e.g. ZFS +zpools+adding new volumes
===Installation===
{{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)
provided that pip is install 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 python can then load those modules. Further adding <code>export PATH=${HOME}/.local/bin:${PATH}</code> to your .bashrc will allow you to run the openstack commands directly.
----


===Executing commands===
[http://www.example.com link title]This page states:
The combined CLI tool can be used interactively by running
{{Command|openstack}}
and then issuing commands at the prompt. Alternatively the commands can be issued as one-offs by a preceding the command with <code>openstack</code>, for example
{{Command|openstack server list}}
When running in interactive mode a list of available commands can be seen by typing <code>help</code> at the openstack prompt. The available commands are categorized by groups, many of the most commonly used are listed below (e.g. <code>server</code> command group. More information on a particular command group can be obtained by typing <code>help <command group></code> where <code><command group></code> is the particular command group e.g. <code>server</code>. To get help on a particular command (e.g. options and arguments) one can type <code>help <command group> <command></code>. Note that many of the available commands are available only to OpenStack administrators and will show some meaningless error message if a non-administrator tries using it. For this reason a list of available commands grouped by command group is provided below to allow one to easily identify commands available to the average user.


To execute a command type {{Command|openstack <command group> <command>}}
:It allows the creation and management of virtual machines ("VMs", or "instances"), which act like separate individual machines, by emulation in software.


====<code>server</code> command group====
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)
| <code>add security group</code>  || <code>migrate</code> || <code>resume</code> || <code>unlock</code>
----
|-
| <code>add volume</code> || <code>pause</code> || <code>set</code> || <code>unpause</code>
|-
| <code>create</code> || <code>reboot</code> || <code>shelve</code> || <code>unrescue</code>
|-
| <code>delete</code> || <code>rebuild</code> || <code>show</code> || <code>unset</code>
|-
| <code>dump create</code> || <code>remove security group</code> || <code>ssh</code> || <code>unshelve</code>
|-
| <code>image create</code> || <code>remove volume</code>        || <code>start</code> ||
|-
| <code>list</code> || <code>rescue</code>  || <code>stop</code>
|-
| <code>lock</code> || <code>resize</code> || <code>suspend</code>
|}


====<code>volume</code> command group====
TODO: add a section about uploading images (note, very important to specify image format)
{|-
|<code>create</code>||<code>set</code>
|-
|<code>delete</code>||<code>show</code>
|-
|<code>list</code>||<code>unset</code>
|}


====<code>console</code> command group====
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/]
|<code>log show</code>||<code>url show</code>
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)".
|}
====<code>image</code> command group====
{|-
|<code>create</code>||<code>save</code>|
|-
|<code>delete</code>||<code>set</code>|
|-
|<code>list</code>||<code>show</code>|
|}
====<code>ip</code> command group====
{|-
|<code>fixed add</code>||<code>floating list</code>
|-
|<code>fixed remove</code>||<code>floating pool list</code>
|-
|<code>floating add</code>||<code>floating remove</code>
|-
|<code>floating create</code>||<code>floating show</code>
|-
|<code>floating delete</code>
|}


====<code>keypair</code> command group====
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.
|<code>create</code>||<code>list</code>
|-
|<code>delete</code>||<code>show</code>
|}
====<code>network</code> command group====
{|-
|<code>create</code>||<code>set</code>
|-
|<code>delete</code>||<code>show</code>
|-
|<code>list</code>||
|}


====<code>snapshot</code> command group====
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
{|-
|<code>create</code>||<code>set</code>
|-
|<code>delete</code>||<code>show</code>
|-
|<code>list</code>||<code>unset</code>
|}
 
====<code>security group</code> command group====
{|-
|<code>create</code>||<code>rule list</code>
|-
|<code>delete</code>||<code>rule show</code>
|-
|<code>list</code>||<code>set</code>
|-
|<code>rule create</code>||<code>show</code>
|-
|<code>rule delete</code>||
|}
 
====<code>limits show</code>====
 
 
<!--These two (container and object) are not widely publicized
====container====
{|-
|<code>create</code>||<code>set</code>
|-
|<code>delete</code>||<code>show</code>
|-
|<code>list</code>||<code>unset</code>
|-
|<code>save</code>
|}
====object====
{|-
|<code>create</code>||<code>show</code>
|-
|<code>delete</code>||<code>store account set</code>
|-
|<code>list</code>||<code>store account show</code>
|-
|<code>save</code>||<code>store account unset</code>
|-
|<code>set</code>||<code>unset</code>
|}
-->

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

Retrieved from "https://docs.alliancecan.ca/mediawiki/index.php?title=Talk:OpenStack&oldid=64991"