[Openstack] [fuel] fuel cli question
Federico Michele Facca
federico.facca at create-net.org
Thu Oct 22 13:04:04 UTC 2015
hi adam,
to get inspiration, you can also define a complex deployment environment
through the GUI and then download it.
federico
Br,
Federico
--
Future Internet is closer than you think!
http://www.fiware.org
Official Mirantis partner for OpenStack Training
https://www.create-net.org/community/openstack-training
--
Dr. Federico M. Facca
CREATE-NET
Via alla Cascata 56/D
38123 Povo Trento (Italy)
P +39 0461 312471
M +39 334 6049758
E federico.facca at create-net.org
T @chicco785
W www.create-net.org
On Thu, Oct 22, 2015 at 2:49 PM, Fabrizio Soppelsa <fsoppelsa at mirantis.com>
wrote:
> Adam,
> I suppose you're asking for Fuel 7.0, in case just query the `fuel`
> command from CLI with --help [1].
> Also, we deprecate GRE in 7.0+ in favor of VxLAN, even if you can force
> the command and use it, as I explain below.
>
> You can create your described env with this procedure:
>
> 1) Create env
> `fuel release`
> id | name | state | operating_system | version
> ---|------------------------|-------------|------------------|-------------
> 2 | Kilo on Ubuntu 14.04.1 | available | Ubuntu | 2015.1.0-7.0
> 1 | Kilo on CentOS 6.5 | unavailable | CentOS | 2015.1.0-7.0
> `fuel env create --name MyEnv --release 2 --mode ha --net neutron --nst
> gre`
>
> 2) To specify to use Ceph, download the settings file:
> `fuel env | grep MyEnv`
> 5 | new | MyEnv | ha_compact | 2 | None
> `fuel --env 5 settings download`
>
> 3) Edit this file:
> `$EDITOR settings_5.yaml`
> Find the Ceph options under key 'storage' and setup as desired. To enable
> Ceph, just turn the option value to 'true'. For example, set true in
> 'volumes_ceph'.
>
> 4) Upload this new yaml file:
> `fuel --env 5 settings upload`
>
> Best regards,
> Fabrizio
>
>
> [1]
> [root at fuel ~]# fuel env create --help
> usage: fuel environment [-h] [--env ENV]
> [--list | --set | --delete | --create | --update]
> [--release RELEASE] [--force] [--name NAME]
> [--mode {multinode,ha}] [--net {nova,neutron}]
> [--nst {gre,vlan,tun}] [--deployment-tasks]
> [--attributes] [--download | --upload] [--dir DIR]
>
> optional arguments:
> -h, --help show this help message and exit
> --env ENV, --env-id ENV
> environment id
> --list, -l List all available environments
> --set, -s Set environment parameters (e.g name, deployment
> mode)
> --delete Delete environment with specific env or name
> --create, -c, --env-create
> Create a new environment with specific release id
> and name
> --update, --env-update
> Update OS to specified release id for given env
> --release RELEASE, --rel RELEASE
> Release id
> --force, -f Do it anyway
> --name NAME, --env-name NAME
> Environment name
> --mode {multinode,ha}, -m {multinode,ha}, --deployment-mode
> {multinode,ha}
> Set deployment mode for specific environment
> --net {nova,neutron}, -n {nova,neutron}, --network-mode {nova,neutron}
> Set network mode for specific environment
> --nst {gre,vlan,tun}, --net-segment-type {gre,vlan,tun}
> Set network segment type
> --deployment-tasks Environment tasks configuration
> --attributes Environment attributes
> --download, -d Download configuration of specific cluster
> --upload, -u Upload configuration to specific cluster
> --dir DIR Select directory to which download release
> attributes
>
> Examples:
>
> To change environment name, mode or network mode:
> fuel --env 1 env set --name NewEnvName --mode ha_compact
>
> To create an environment with name MyEnv and release id=1 run:
> fuel env create --name MyEnv --rel 1
>
> By default, it creates environment with ha_compact mode and
> neutron with VLAN network segmentation as network provider
> (WARNING: nova-network is deprecated since 6.1 release).
> To specify other modes add optional arguments:
> fuel env create --name MyEnv --rel 1 \
> --mode ha --network-mode neutron
>
> Update environment to given OS release:
> fuel env --env 1 --update --release 1
>
> Print all available environments:
> fuel env
>
> Modify deployment_tasks for environment:
> fuel env --env 1 --deployment-tasks --download
> fuel env --env 1 --deployment-tasks --upload
>
> To delete the environment:
> fuel --env 1 env --force delete
>
> Modify attributes of the environment:
> fuel env --env 1 --attributes --download
> fuel env --env 1 --attributes --upload
>
>
>
>
> On 10/22/2015 12:09 AM, Adam Lawson wrote:
>
> I'm being asked how to create a new environment using fuel cli. I need to
> know how to define KVM, neutron/GRE with Ceph back-end for everything. The
> docs gives examples but don't go into specifics.
>
> * Adam Lawson*
>
> AQORN, Inc.
> 427 North Tatnall Street
> Ste. 58461
> Wilmington, Delaware 19801-2230
> Toll-free: (844) 4-AQORN-NOW ext. 101
> International: +1 302-387-4660
> Direct: +1 916-246-2072
>
>
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
>
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack at lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20151022/3fcfa6b0/attachment.html>
More information about the Openstack
mailing list