Upcoming changes in 1.19

[Andrew Wilkins]

On Wed, Apr 2, 2014 at 9:19 PM, Kapil Thangavelu <
kapil.thangavelu at canonical.com> wrote:

>
> On Wed, Apr 2, 2014 at 2:32 AM, Andrew Wilkins <
> andrew.wilkins at canonical.com> wrote:
>
>> I'm going to start landing my Azure-related changes on trunk, now that
>> we've branched for 1.18.
>>
>> I've just approved a change that will cause "juju ssh" and related
>> commands (scp, debug-hooks, debug-log) to connect to internal addresses,
>> proxying via the API server. This is enabled for all newly bootstrapped
>> environments, except for the local provider. If you see weirdness with
>> these commands, this could be why.
>>
>
>
> Sounds cool, but what's the reasoning on it? we're moving to multiple
> machines in a service for azure i assume. It also sounds like it would help
> for containers in public clouds with private but not public addresses.
>

Yes, Azure is the driver behind this. To support high availability of
deployed services, units must reside within the same "Cloud Service". Each
Cloud Service has a single public address, but each VM inside it has its
own internal address.

Once some of the other things are ready, I'll land the changes to
>> provider/azure that require gwacl to be updated. If you see problems
>> building against gwacl, you'll need to update using godeps.
>>
>>
> thanks for the heads up.
>
> cheers,
>
> Kapil
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140402/69fd4c49/attachment.html>