=== anthonyf is now known as Guest70961 | ||
firl | anyone know a way to specify an AMI for a juju deploy? | 01:01 |
---|---|---|
=== Guest97037 is now known as Tm_T | ||
=== mthaddon` is now known as mthaddon | ||
=== jamespag` is now known as jamespage | ||
=== bloodear` is now known as bloodearnest | ||
Muntaner | hey guys | 08:58 |
Muntaner | having a problem with a bootstrap | 08:58 |
Muntaner | http://paste.ubuntu.com/11755548/ | 09:00 |
Muntaner | what can this be? | 09:01 |
Muntaner | what does it means "index file has no data for cloud {etc...} " ? | 09:10 |
=== rbasak_ is now known as rbasak | ||
=== jcsackett_ is now known as jcsackett | ||
=== anthonyf is now known as Guest35024 | ||
=== coreycb` is now known as coreycb | ||
Muntaner | nobody? | 12:32 |
bleepbloop | Hey guys, hopefully simple question, I am using juju to deploy openstack. I have it setup with a dual network setup https://insights.ubuntu.com/wp-content/uploads/226b/split.png the problem is one of the services that is deployed in an lxc container should have a public IP but it is getting one on the internal network. How do I setup juju containers to have | 14:18 |
bleepbloop | an ip on the maas public network? | 14:18 |
bleepbloop | I pretty much want the equivalent of a "floating IP" added to this lxc service, since if I actually go in and manually move it to a different network it will make juju unable to access it | 14:21 |
=== wendar_ is now known as wendar | ||
=== kadams54 is now known as kadams54-away | ||
=== ericsnow__ is now known as ericsnow | ||
=== kadams54-away is now known as kadams54 | ||
=== anthonyf is now known as Guest16072 | ||
=== lukasa is now known as lukasa_away | ||
=== kadams54 is now known as kadams54-away | ||
=== lukasa_away is now known as lukasa | ||
=== anthonyf is now known as Guest26733 | ||
=== kadams54-away is now known as kadams54 | ||
=== kadams54 is now known as kadams54-away | ||
=== bcsaller_ is now known as bcsaller | ||
=== kadams54 is now known as kadams54-away | ||
wolverineav | hi | 21:16 |
wolverineav | quick question, I'm adding a relation between quantum-gateway and rabbitmq-server : juju add-relation quantum-gateway rabbitmq-server | 21:17 |
wolverineav | I get the following error: ERROR ambiguous relation: "quantum-gateway rabbitmq-server" could refer to "quantum-gateway:amqp rabbitmq-server:amqp"; "quantum-gateway:amqp-nova rabbitmq-server:amqp" | 21:17 |
wolverineav | does anyone know on the top of their head which one to choose? pretty sure the openstack documents will have that info somewhere deep :) | 21:18 |
wolverineav | oh, context : setting up openstack using juju and maas. using neutron networking instead of nova-networks | 21:18 |
wolverineav | ah, the next step is 'juju add-relation quantum-gateway nova-cloud-controller' so the nova-amqp would be used there. | 21:34 |
wolverineav | went ahead with juju add-relation quantum-gateway:amqp rabbitmq-server:amqp - no errors. hopefully its the right thing. will find out soon | 21:35 |
=== mup_ is now known as mup | ||
jackweirdy | Hey folks. I'm trying to get Juju working with an openstack instance, and I have no idea what to set as my `region`. I can't find anything about that in horizon, and juju won't bootstrap without a value set. Anyone got any suggestions? Is there a magical default value that makes it work? | 22:25 |
jackweirdy | (to be clear, that's the value of the `region` property in my environments.yaml file) | 22:25 |
marcoceppi | jackweirdy: it's usually "RegionOne" | 23:55 |
jackweirdy | Thanks marcoceppi! | 23:55 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!