Hello Ram,

Due to recent change in Java API all objects that have multiple parents
need to have one of their parents specified explicitly. This is required
even if the parent is ConfigRoot and this information will be later removed
by the server.

Currently FQN of config-root is a list with a single *null* element:
*[null]*.  The FQN of config-root is required when its children compute
their own FQN using the standard convention: My FQN = Parent FQN + My Name.

Thanks,
Daniel

On Mon, Jun 4, 2018 at 9:34 PM, ram yadav <email address hidden> wrote:

> Hi Filip,
> API server remove’s the Config-root when provided as parent as part of
> create.
> So the understanding below is correct.
> What does FQN return today for Config-root without your change? And in
> what case are you querying the FQN for Config-root?
>
> Thanks,
> Ram
>
>
> From: Filip Chmielewski <<email address hidden><mailto:
> <email address hidden>>>
> Date: Friday, June 1, 2018 at 3:09 AM
> To: Ram Yadav <<email address hidden><mailto:<email address hidden>>>
> Cc: Sachchidanand Vaidya <<email address hidden><mailto:<email address hidden>>>,
> Daniel Jasiński <<email address hidden><mailto:<email address hidden>.
> net>>
> Subject: Re: Question related to review https://review.opencontrail.
> org/#/c/43079/1
>
> Hi,
>
> FQN for all objects is defined as [parent's FQN] + [own name].
> All children of config-root (such as Domain) have FQNs that are simply
> 1-element arrays containing their name, which suggests that config-root's
> FQN should be an empty list.
>
> For example, in a hierarchy of  Config Root -> Domain -> Project ->
> Network Policy, we have:
> Network Policy's FQN = [domain-name, project-name, policy-name]
> Project's FQN = [domain-name, project-name]
> Domain's FQN = [domain-name]
> so Config Root's FQN should be [] .
>
> On Wed, May 30, 2018 at 8:51 PM, Sachchidanand Vaidya <
> <email address hidden><mailto:<email address hidden>>> wrote:
> +Filip
>
> From: Ram Yadav <<email address hidden><mailto:<email address hidden>>>
> Date: Wednesday, May 30, 2018 at 11:45 AM
> To: Daniel Jasiński <<email address hidden><mailto:
> <email address hidden>>>
> Cc: Sachchidanand Vaidya <<email address hidden><mailto:<email address hidden>
> >>
> Subject: Question related to review https://review.opencontrail.
> org/#/c/43079/1<https://urldefense.proofpoint.com/v2/
> url?u=https-3A__review.opencontrail.org_-23_c_43079_1&d=DwMFaQ&c=
> HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=5cGBwnyUCiMK2Tm6UX_
> iIiml04qYJeDz4xQzoG2Hi8E&m=FJwZ4I3R0AM9hNxDZpcqZ-
> daRpBLiugIkx5sLH4NC0w&s=gVVK6_ktK37VlqQj8y1iHvvqTZzEkX5L_E66gHcdvnU&e=>
>
> Hi Daniel,
> Can you explain the rationale for returning empty ArrayList as FQN for
> config-root?
>
> Thanks,
> Ram
>
>
> [X]
>
> -------------------------------
> The information in this email is confidential and may be legally
> privileged, it may contain information that is confidential in CodiLime Sp.
> z o. o. It is intended solely for the addressee. Any access to this email
> by third parties is unauthorized. If you are not the intended recipient of
> this message, any disclosure, copying, distribution or any action
> undertaken or neglected in reliance thereon is prohibited and may result in
> your liability for damages.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1765393
>
> Title:
>   vRO API search does not display object description
>
> Status in Juniper Openstack:
>   Fix Committed
> Status in Juniper Openstack r5.0 series:
>   Fix Committed
> Status in Juniper Openstack trunk series:
>   Fix Committed
>
> Bug description:
>   In vRO API explorer object description is not displayed.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juniperopenstack/+bug/1765393/+subscriptions
>

-- 


-------------------------------
The information in this email is 
confidential and may be legally privileged, it may contain information that 
is confidential in CodiLime Sp. z o. o. It is intended solely for the 
addressee. Any access to this email by third parties is unauthorized. If 
you are not the intended recipient of this message, any disclosure, 
copying, distribution or any action undertaken or neglected in reliance 
thereon is prohibited and may result in your liability for damages.