Hi,
Architecture wise, I'm in favor of the traffic ops sending the specific
configuration to the cache.
Main reason is taking features like "DS *individual *automatic deployment"
into account, where we would like to be able to control "which server get
which configuration and when" - e.g. edge cac
Hi,
IIRC, when tenancy was added, the plan was that a user of an inactive
tenant cannot do anything.
A user of its active parent can manipulate the inactive tenant resources.
I thought it was even covered by a UT, but anyhow, as I see it, any other
current behavior should be fixed.
See [NS] inline
Hi,
I'm with Jeremy on that.
The "use_tenancy" flag came to allow simple transition to the tenanted
world:
On the transition, the TC owner should adjust all tenancies, most
importantly create a "root tenant" admin, and only then put the use_tenancy
flag on.
For 3.0 I believe that tenancy should be
+1:)
On Sun, May 20, 2018 at 5:04 AM, John Rushford wrote:
> +1
>
> > On May 19, 2018, at 10:15 AM, Jeremy Mitchell
> wrote:
> >
> > +1
> >
> > On Fri, May 18, 2018 at 7:57 PM, Hank Beatty wrote:
> >
> >> +1
> >>
> >>
> >> On 05/18/2018 11:06 AM, Eric Friedrich wrote:
> >>
> >>> Hey-
> >>> B
