> Hi
>
> With keystone, we recently came across an issue in terms of the assumptions
> that the openstack client is making about the
> entities it can show - namely that is assumes all entries have a ‘name’
> attribute (which is how the "openstack show"
> command works). Turns out, that not all
> On Aug 26, 2015, at 4:45 AM, Henry Nash wrote:
>
> > Hi
> >
> > With keystone, we recently came across an issue in terms of the assumptions
> > that the openstack client is making about the
> entities it can show - namely that is assumes all entries have a 'name'
> attribute (which is how the
Chen, Wei D would like to recall the message, "[openstack-dev]
[api][keystone][openstackclient] Standards for object name attributes and
filtering".
__
OpenStack Development Mailing List (not for usage questions)
Unsubscrib
> > Hi
> >
> > With keystone, we recently came across an issue in terms of the assumptions
> > that the openstack client is making about the
> > entities it can show - namely that is assumes all entries have a ‘name’
> > attribute (which is how the "openstack show"
> > command works). Turns out,
Hi Stanislaw,
I also faced similar issue.Reason might be that from inside master
instance openstack heat service is not reachable.
Please check /var/log/cloud-init-log for any connectivity related
error message and if found try manually whichever command has failed
with correct url.
If this is
Hi,
I've been running against openstack-dev (master branch) using the
stackforge/networking-ovs-dpdk master branch (OVS GIT TAG
1e77bbe565bbf5ae7f4c47f481a4097d666d3d68), using the single-node local.conf
file on Ubuntu 15.04. I've had to patch a few things to get past ERRORs during
start:
- di
Thanks everyone for the feedback!
There weren't any comments about options (1) and (4), I'm interpreting
it as a consensus that we're not doing a "future" branch, and as a sign
that nobody wants to even think about CI for external forks (which I'm
sure will come back to haunt us, so don't count o
Let's get these details into the QuickStart doc so anyone else hitting this can
be clued in.
--
Adrian
On Aug 27, 2015, at 9:38 PM, Vikas Choudhary
mailto:choudharyvika...@gmail.com>> wrote:
Hi Stanislaw,
I also faced similar issue.Reason might be that from inside master instance
openstack
Hi all,
I have two points.
a. For the problem in this thread, my suggestion is to introduce new
concepts to replace the existing firewall and SG.
Perhaps you have found the overlap between firewall and SG. It's trouble
for user to select.
So the new concepts are edge-firewall for N/S traffic and D
101 - 109 of 109 matches
Mail list logo
