Hi Grant,,
Somehow missed this email, so sorry for the delay on that one.
Are you setting up the installation with SSL Certs for the public IP only,
or internal as well?
You should be able to setup the endpoint VIP address instead of an IP -
which would mean the certificate matches the endpoint.
Hi Eugene,
sorry its taken me a while to get to the bottom of this error, running the
> op-venv-script manually helped me eventually find the issue. We run the
> install in a limited internet environment, I had overridden the
> pip_install_options to specify our python cache and wheel indices and
Hi Eugene,
You're right that error doesn't give us much.
My best advice for a next step would be to manually run "bash
/opt/op-venv-script.sh" from inside the repo container:
dc2-controller-01_repo_container-7ce807b6.
I've had similar issues, which is usually a constraints issue (we're
working way
Hi Eugene,
With just that error it's a bit difficult to see exactly why it's failing.
Could you use paste.openstack.org (or similar) to paste a more detailed log
of the error/output?
I'd also suggest jumping into #openstack-ansible on the Freenode irc
server, there are usually some people about
Hi Amit,
Sending it again to include the ML!
On 2 March 2017 at 11:01, Amit Kumar wrote:
> Hi All,
>
> I have deployed Openstack using Openstack-Ansible. I am using Newton
> release from tag 14.0.8. My test environment is containing only Compute
> Node and Controller Node (Infra Node).
> When u
Hi Lawrence,
(Copying my response from the dev list! as a note, if you add
[openstack-ansible] in the title it allows filters to filter it a bit
better)
Thanks for raising this.
The 10.255.255.x range is used by lxcbr0 on the host, to assign the eth0
address to the containers.
In essence this won'
On 28 February 2017 at 09:59, Grant Morley wrote:
> Hi All,
>
> We have an OSA Mitaka deployment and for some reason all of the end points
> ( keystone, neutron, glance etc.. ) are all reporting as HTTP rather than
> HTTPS. The only thing that seems to have worked with HTTPS is Horizon ( I
> know
Hi Andreas,
The way you're doing it at the end looks correct - the docs are not quite
right on that one.
The nfs_shares file will only get templated on the cinder_volumes hosts, as
will the nfs_shares_config option - so in essence it shouldn't matter that
the var isn't limited to volume hosts.
T
Hi Salman,
Thanks for pointing that out - I'll file a fix for that now (
https://review.openstack.org/427950 )
If you find any more it'd be great if you could file a bug in launchpad:
https://bugs.launchpad.net/openstack-ansible
We triage bugs once a week (on Tuesdays), so we usually pick them u
Hi Fabrice,
Firstly, I've moved this over to the ops mailing list (dev in bcc - just so
anybody following along knows where it's gone!) - I think it's more of an
operational issue than a dev one.
That does seem weird - so the error is:
> 2017-01-25 11:03:58.475 113231 ERROR nova.virt.libvirt.dr
>
>
> I have been looking for a Community Goal [1] that would directly help
> Operators and I found the "run API via WSGI" useful.
> So I've decided to propose this one as a goal for Pike but I'll stay
> open to postpone it to Queen if our community thinks we already have
> too much goals for Pike.
Hi Akshay,
If I understand correctly, you're looking to deploy the services on metal
hosts (rather than in containers) - in that case you would need to adjust
the env.d/*.yml (service files) to set the property "is_metal: True".
The second query regarding multiple VLans - if you are using pre-exis
12 matches
Mail list logo
