>
>While I installed dnsmasq 2.63 manually, they used Ubuntu 14.04 to get
>around the problem. Is it maybe time to upgrade the base for the dev env
>to 14.04, or would that cause many other problems? Have you tried that
>out? If you have a pointer to an appropriate 14.04 image I can configure
>in
I¹m seeing similar. Instances launch, they show as having Ips in
`neutron list` but I cannot access them via IP.
Other thing I¹ve notices is that doing a `neutron agent-list` gives me an
empty list, I would assume it should at least show the dhcp agent ?
On 7/1/14, 12:00 PM, "Kyle Mestery"
Has anyone had any success with running devstack and neutron in a vagrant
machine where the floating Ips are accessible from outside of the vagrant box (
I.e. From the host ).
I’ve spent a few hours trying to get it working without any real success.
_
Based on this feedback I have removed the docker portions of the review to
devstack
But have kept in the changes that make it easier for a nova drivers to add
their own
Files to the nova rootwrap.d directory.
On 4/11/14 10:47 AM, "Russell Bryant" wrote:
>On 04/11/2014 11:28 AM, Pa
I would rather see the devstack support be integrated in devstack's repo
itself. There's a review
Outstanding for devstack[1] that adds this support in and also adds in
some pieces to make
it easier to utilize external nova drivers.
If that fails out then I'm all for merging in your review to t
There is a bug in the default docker registry. Set this is your localrc
and it should work
DOCKER_REGISTRY_IMAGE=samalba/docker-registry
On 3/12/14 1:35 AM, "urgensherpa" wrote:
>hello there,i setup using devstack ..below is my docker version output
>--
I'm also a +1 for #2.However as discussed on IRC, we should clearly
spell out that the JSON blob should never be treated in a SQL-like manner.
The moment somebody says 'I want to make that item in the json
searchable' is the time to discuss adding it as part of the SQL schema.
On 2/13/14 4:
On 2/12/14 5:16 PM, "Roshan Agrawal" wrote:
>
>> -Original Message-
>> From: devdatta kulkarni [mailto:devdatta.kulka...@rackspace.com]
>> Sent: Wednesday, February 12, 2014 3:26 PM
>> To: OpenStack Development Mailing List (not for usage questions)
>> Subject: [openstack-dev] [Solum] Q
Works for me.
On 2/4/14 11:07 AM, "devdatta kulkarni"
wrote:
>Sounds good to me.
>
>- Devdatta
>
>-Original Message-
>From: "Clayton Coleman"
>Sent: Monday, February 3, 2014 12:10pm
>To: "OpenStack Development Mailing List (not for usage questions)"
>
>Subject: Re: [openstack-dev] [Solu
If you're running on a machine with devstack these dependencies *should*
already be met.
If you like to work on VMs on your local box I have build a Vagrant dev
environment that should take care of your dependencies here -
https://github.com/rackerlabs/vagrant-solum-dev
I think it's documented
I have a box with a newer version of pip ( 1.5 ) and it refuses to install
netaddr >= 0.7.6 as it's an external/insecure pip package.This may cause
issues for devs that are running newer versions of pip than standard system
packages. There maybe other packages in the larger global-requirem
On 12/4/13 3:06 PM, "Adrian Otto" wrote:
>
>On Dec 4, 2013, at 12:32 PM, Monty Taylor wrote:
>
>> On 12/04/2013 03:25 PM, Clint Byrum wrote:
>>> Excerpts from Paul Montgomery's message of 2013-12-04 12:04:06 -0800:
TLDR: Should Solum log a warning if operators do not use the InnoDB
s
12 matches
Mail list logo
