On 12 January 2015 at 03:17, Tim Penhey tim.pen...@canonical.com wrote:
This is because the EC2 provider tags the machines with the environment
name, and not environment UUID. I think we should change this ASAP.
+1. The environment name should be purely client-local IMHO.
The main thing that
On Sun, Jan 11, 2015 at 8:17 PM, Tim Penhey tim.pen...@canonical.com wrote:
This is because the EC2 provider tags the machines with the environment
name, and not environment UUID. I think we should change this ASAP.
Tim, I'm glad you brought this up. We have followed the lead of the
EC2
On 12/01/15 22:23, roger peppe wrote:
On 12 January 2015 at 03:17, Tim Penhey tim.pen...@canonical.com wrote:
This is because the EC2 provider tags the machines with the environment
name, and not environment UUID. I think we should change this ASAP.
+1. The environment name should be purely
On 13/01/15 04:55, Eric Snow wrote:
On Sun, Jan 11, 2015 at 8:17 PM, Tim Penhey tim.pen...@canonical.com wrote:
This is because the EC2 provider tags the machines with the environment
name, and not environment UUID. I think we should change this ASAP.
Tim, I'm glad you brought this up. We
On Tue, Jan 13, 2015 at 2:15 AM, Kapil Thangavelu
kapil.thangav...@canonical.com wrote:
On Mon, Jan 12, 2015 at 10:03 AM, roger peppe roger.pe...@canonical.com
wrote:
On 12 January 2015 at 15:43, Gustavo Niemeyer gust...@niemeyer.net
wrote:
A few quick notes:
- Having an
On Mon, Jan 12, 2015 at 10:03 AM, roger peppe roger.pe...@canonical.com
wrote:
On 12 January 2015 at 15:43, Gustavo Niemeyer gust...@niemeyer.net
wrote:
A few quick notes:
- Having an understandable name in a resource useful
It's also good to be clear about what a name actually
