Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1238622

Summary:	Deployment parameters such as --network-cidr and --floating-ip-start etc should be saved in Tuskar
Product:	Red Hat OpenStack	Reporter:	Udi Kalifon <ukalifon>
Component:	python-rdomanager-oscplugin	Assignee:	Lennart Regebro <lregebro>
Status:	CLOSED NOTABUG	QA Contact:	yeylon <yeylon>
Severity:	high	Docs Contact:
Priority:	medium
Version:	Director	CC:	akrivoka, calfonso, dmatthew, jslagle, lregebro, mburns, rhel-osp-director-maint, srevivo
Target Milestone:	z1	Keywords:	Triaged, ZStream
Target Release:	Director
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-19 18:39:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Udi Kalifon 2015-07-02 10:02:54 UTC

Description of problem:
Currently, in the Tuskar plan, many of the parameters that are supplied in the deployment are missing. As a result, the user must supply them again and again from the command line whenever the deployment is scaled. forgetting to supply the parameters might ruin a deployment.

All parameters must have default values in the plan when Tuskar is initialized, and those values should be used whenever the user doesn't supply anything else. When the user passes other values to those parameters the plan should be updated so that the new values will always be taken in the future.

Example parameters can be seen in the help of the tuskar deploy command:
  --control-flavor
  --compute-flavor
  --ceph-storage-flavor 
  --block-storage-flavor
  --swift-storage-flavor
  --neutron-flat-networks    
  --neutron-physical-bridge  
  --neutron-bridge-mappings  
  --neutron-public-interface 
  --hypervisor-neutron-public-interface 
  --neutron-network-type 
  --neutron-tunnel-types 
  --neutron-disable-tunneling
  --neutron-network-vlan-ranges 
  --overcloud_nameserver 
  --floating-ip-cidr 
  --floating-ip-start 
  --floating-ip-end 
  --bm-network-gateway 
  --network-cidr 
  --libvirt-type
  --ntp-server
  --cinder-lvm
  --tripleo-root

Note that some of the parameters in the example above may not be needed as part of the plan, and other parameters may be needed and are not listed... I just don't understand all these parameter yet.

Comment 3 Dougal Matthews 2015-07-02 10:56:40 UTC

(In reply to Udi from comment #0)
>   --control-flavor
>   --compute-flavor
>   --ceph-storage-flavor 
>   --block-storage-flavor
>   --swift-storage-flavor
>   --neutron-flat-networks    
>   --neutron-physical-bridge  
>   --neutron-bridge-mappings  
>   --neutron-public-interface 
>   --neutron-network-type 
>   --neutron-tunnel-types 
>   --neutron-network-vlan-ranges 
>   --libvirt-type
>   --ntp-server
>   --cinder-lvm

These need to be stored in Tuskar and I believe they all are.


>   --hypervisor-neutron-public-interface 

This isn't used, but should set HypervisorNeutronPublicInterface.


>   --overcloud_nameserver 
>   --floating-ip-cidr 
>   --floating-ip-start 
>   --floating-ip-end 
>   --bm-network-gateway 
>   --network-cidr 
>   --neutron-disable-tunneling

These have nowhere to be saved. They are only used when doing an initial deploy. Tuskar wont save them for us as they are not expected Parameters in the template.


>   --tripleo-root

This doesn't appear to be used anymore and can probably be removed.

Comment 4 Lennart Regebro 2015-07-02 11:16:06 UTC

These parameters are all being saved:

  --control-flavor
  --compute-flavor
  --ceph-storage-flavor 
  --block-storage-flavor
  --swift-storage-flavor
  --neutron-flat-networks    
  --neutron-physical-bridge  
  --neutron-bridge-mappings  
  --neutron-public-interface 
  --neutron-network-type 
  --neutron-tunnel-types 
  --neutron-disable-tunneling
  --neutron-network-vlan-ranges 
  --libvirt-type
  --ntp-server
  --cinder-lvm

The following are only used when initializing the neutron networking, and are not saved, as they are not a part of the Tuskar template. They are not needed when updating the stack. However, should you delete the stack and redeploy it, you will have to pass in the parameters again:

  --overcloud_nameserver 
  --floating-ip-cidr 
  --floating-ip-start 
  --floating-ip-end 
  --bm-network-gateway 
  --network-cidr 


This is a parameter to point at the root directory for tripleo templates. It is currently not being used, but is not a part of the template or deployment and should not be saved. I'm not sure if it's left over from an earlier implementation, or if it's a not yet fully implemented feature. I will check.

  --tripleo-root

This is currently being ignored, and I'm not sure it should be. I will check.

  --hypervisor-neutron-public-interface

Comment 5 Lennart Regebro 2015-07-02 11:21:18 UTC

Actually, I put it back to NEW as we need to discuss this first to decide exactly what is to be done.

Comment 7 Udi Kalifon 2015-07-26 10:28:26 UTC

These parameters don't exist at all any more, is this bug still relevant ?

Comment 8 Lennart Regebro 2015-07-27 07:10:52 UTC

--tripleo-root and --hypervisor-neutron-public-interface both exists, but they are ignored. The others are gone.

So I do believe this bug isn't relevant any more.