openstack team mailing list archive

[Jorge Luiz Corrêa <correajl@xxxxxxxxx>]

Hi! 

Continuing the tests, I've found the cause of some problems. 

1) In my nova.conf I had the --multi_host=T flag. This was the problem. Removing that the secrules became active. Secrules from Juju samples are working fine now. 

2) Pointing the host running juju to use the dnsmasq from nova-network is a solution. It's working. From where is it recommended to run juju? From an external host? The problem is that when I run juju it tries to connect to a name like server-12, server-13 … these names just make sense inside the cloud. So, for that, I presume juju must be ran from a host inside the cloud. Or not? Making automatic assign of floating ip makes juju connect to the external IP?

Thanks a bunch! Juju is amazing! 

On May 3, 2012, at 3:20 PM, Adam Gandelman wrote:

> On 05/03/2012 06:04 AM, Jorge Luiz Correa wrote:
>> 
>> Hi list!
>> 
>> I would like to know if someone has tested juju with Essex. I've installed OpenStack using Ubuntu 12.04 and its packages (Essex). The nova components are working fine. I can create and destroy instances. So I'm using Juju from a 11.10 Oneiric. I've made some modifications in my environment.yaml configuration file to work with keystone. In my first tests I could bootstrap, creating a new instance. However, some problems that I'm having now:
> 
> I'd recommend using the latest Juju version, either from the Juju PPA [1] on oneiric or the version shipped with precise.  
> 
>> 
>> 1) Juju and nova aren't creating secgroup-rules in the right way. I can see new secgroup-rules, like juju-sample, juju-sample-0 and so on. But, when I list the rules, there are NO rules. The immediately impact is that when running 'juju status' the host is not able to access the instances created by juju. If I go to dashboard and add access with the right ports, so juju gets working. 
> 
> This should be working fine.  We fixed some bugs in nova around security groups during Essex that I uncovered trying to get Juju working against it, but since then its been working nicely.  I've just bootstrapped against an Essex/12.04 and get a functioning security group rule set.  This may look a bit different depending on what you've named the environment, but should be similar: http://paste.ubuntu.com/965169/
> 
>> 
>> 2) The host running juju 'should' know how to resolve the instance names, like server-8, server-10 to address from cloud network. How we need to deal with it? Host running juju has to use the same DNS that serves the cloud? I've changed the dhcp configuration in juju host to add the address of nova network that runs a dnsmasq and knows how to resolve these names. Is this the right way? Recommendations? 
>> 
> 
> This is mostly a Nova config thing. By default, new instances' public hostnames are the same as their private hostnames.    If you want to be able to reach instances via their private hostname, you'd need to do some DNS magic outside of Juju like you are doing, or perhaps there is a documented way of achieving this in Nova itself.      The best solution is to instead add '--auto_assign_floating_ip' to nova.conf.  This will ensure a public floating IP is associated with new instances and allow Juju to reach its nodes that way instead.   This matches the behavior of EC2.
> 
> 
> Adam
> 
> [1] Juju PPA - ppa:juju/pkgs
> 
>> Thanks!
>> 
>> -- 
>> - MSc. Correa, J.L.
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp