Re: (Isolation Segments) Question about a Cell with mulitiple "placement_tag"s

Sandy Cash Jr <lhcash@...>

Hi Taniguchi-san,

I don't know what you mean specifically by "not recognized as a valid
compute resource." Perhaps you could share the manifest snippet?

If you have a cell with two placement tags - let's say "segment_one" and
"segment_two" - and each of those corresponds to an existing Isolation
Segment, then an app pushed to either IS could land on that cell. So yes,
a cell can belong to multiple Isolation Segments.

Technically, Diego doesn't actually know about "Isolation Segments" - just
placement tags. When the desiredLRP request is sent from the CC, it
contains the name of the Isolation Segment, which is sent to Diego as a
placement tag. Diego then selects an appropriate cell from among all of
those thus tagged. So there is no exclusion requiring a cell to live in
only one IS or another.



Sandy Cash
Certified Senior IT Architect/Senior SW Engineer
IBM BlueMix
(919) 543-0209

"I skate to where the puck is going to be, not to where it has been.” -
Wayne Gretzky

From: Noburou TANIGUCHI <dev(a)>
To: cf-dev(a)
Date: 03/02/2017 12:41 AM
Subject: [cf-dev] (Isolation Segments) Question about a Cell with
mulitiple "placement_tag"s

Hi team,

Recently I've been trying Isolation Segments for compute tier.

In the official document, it is required to deploy one or more cells with
`diego.rep.placement_tags` to utilize the isolation segment feature.

But I'm wondering why the `diego.rep.placement_tags` is a "single-value
array" [1].

I tried to deploy a cell with two placement tags. The deployment was
successfully finished, but the cell was not recognized as a valid compute

So my questions are:

Q1. Why is the `diego.rep.placement_tags` a "single-value array"?

Q2. A cell with multiple placment tags can be deployed but not recognized
valid. Is this expected behavior for the current implementation?

Q3. Is there any plan to support a cell belonging multiple isolation
segments in the future? If yes, when?


Thanks in advance.

I'm not a ...
View this message in context:

Sent from the CF Dev mailing list archive at

Join { to automatically receive all group messages.