password generated before deployment if user does not set them via constraints.

Bug #1636987 reported by Toure Dunnon on 2016-10-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Medium
Unassigned

Bug Description

Use custom parameter constraint to identify such parameters, allowing the user to add a custom template which can specify that certain parameter that is generated. GUI can use this information too as it is embedded in plan (THT).

Toure Dunnon (toure) on 2016-10-26
tags: added: workflows
description: updated
Toure Dunnon (toure) on 2016-10-27
summary: - password-like parameters are automatically generated before deployment
- if user does not set them
+ password generated before deployment if user does not set them via
+ constraints.
Toure Dunnon (toure) on 2016-10-27
description: updated
Ryan Brady (rbrady) on 2016-11-07
tags: added: tripleo-heat-templates
Dougal Matthews (d0ugal) on 2016-11-07
Changed in tripleo:
status: New → Confirmed
importance: Undecided → Medium
Jiri Tomasek (jtomasek) on 2016-11-08
Changed in tripleo:
status: Confirmed → Triaged
milestone: none → ocata-2
Changed in tripleo:
milestone: ocata-2 → ocata-3
Changed in tripleo:
milestone: ocata-3 → pike-1
Changed in tripleo:
milestone: pike-1 → pike-2
Changed in tripleo:
assignee: nobody → Adriano Petrich (apetrich)
Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
assignee: Adriano Petrich (apetrich) → nobody
Julie Pichon (jpichon) wrote :

I'm a bit confused with the title and short description, this sounds similar to what we already do for passwords at the moment:

https://github.com/openstack/tripleo-common/blob/93d87/tripleo_common/constants.py#L55
https://github.com/openstack/tripleo-common/blob/93d87/tripleo_common/utils/passwords.py#L34

which get auto-generated and then used only if not set in a template/environment.

Is this about moving this to the templates, so that we don't need to keep a hard-coded list anymore? Or about making the system more generic / customisable by the deployer? Thank you.

Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Dougal Matthews (d0ugal) wrote :

I don't think this makes any sense - closing for now. We can reopen if there is an issue somebody can explain.

Changed in tripleo:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints