yahoo-eng-team team mailing list archive

[Stephen Balukoff <stephen@xxxxxxxxxxxx>]

Public bug reported:

Right now, the Octavia API allows the specification of the project_id on
the create commands for the following objects:

listener
health_monitor
member
pool

However, all of these objects should be inheriting their project_id from
the ancestor load_balancer object. Allowing the specification of
project_id when we create these objects could lead to a situation where
the descendant object's project_id is different from said object's
ancestor load_balancer project_id.

We don't want to break our API's backward compatibility for at least two
release cycles, so for now we should simply ignore this parameter if
specified (and get it from the load_balancer object in the database
directly), and insert TODO notes in the API code to remove the ability
to specify project_id after a certain openstack release.

We should also update the Octavia driver in neutron_lbaas to stop
specifying the project_id on descendant object creation.

This bug is related to https://bugs.launchpad.net/octavia/+bug/1624113

** Affects: neutron
     Importance: Undecided
         Status: New

** Affects: octavia
     Importance: Undecided
         Status: New

** Also affects: neutron
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1624145

Title:
  Octavia should ignore project_id on API create commands (except
  load_balancer)

Status in neutron:
  New
Status in octavia:
  New

Bug description:
  Right now, the Octavia API allows the specification of the project_id
  on the create commands for the following objects:

  listener
  health_monitor
  member
  pool

  However, all of these objects should be inheriting their project_id
  from the ancestor load_balancer object. Allowing the specification of
  project_id when we create these objects could lead to a situation
  where the descendant object's project_id is different from said
  object's ancestor load_balancer project_id.

  We don't want to break our API's backward compatibility for at least
  two release cycles, so for now we should simply ignore this parameter
  if specified (and get it from the load_balancer object in the database
  directly), and insert TODO notes in the API code to remove the ability
  to specify project_id after a certain openstack release.

  We should also update the Octavia driver in neutron_lbaas to stop
  specifying the project_id on descendant object creation.

  This bug is related to https://bugs.launchpad.net/octavia/+bug/1624113

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1624145/+subscriptions