Nah, I had that error previously, and added the keymgr section.
Just seeing a bunch of 404s when horizon tries to get the "project Id"
using the /tenant URL.
On Friday, February 5, 2016, Matt Fischer wrote:
> Are you seeing the cinder Volume limit error?
>
> If that's the
On 05/02/16 18:19, Ned Rhudy (BLOOMBERG/ 731 LEX) wrote:
> Hello operators,
>
> We're continuing to investigate different cloud networking technologies
> as part of our project to migrate from nova-network to Neutron, and one
> that's come up frequently is Project Calico
>
Hello operators,
We're continuing to investigate different cloud networking technologies as part
of our project to migrate from nova-network to Neutron, and one that's come up
frequently is Project Calico (http://www.projectcalico.org/). However, we can't
actually find anything in the way of
Hi ,
I have openstack setup with 1 controller node and 2 compute node. There is
no separate network node, controller node is configured to also act as
network node.
I want to test the number of tenant networks i can create, before some
problems come up and figure out what problems come up. I also
I meant in a general sense of the networking technology that you're using for
instance networking, not in the sense of per-tenant networks, though my wording
was ambiguous. Part of our larger question centers around the viability of
tying instances directly to a provider network. Being that we
Actually, "identity:get_project" : "" seems ok, there's plenty of other actions
with that lack of restriction.
get_auth_catalog, get_auth_domains, get_region.
> On Feb 5, 2016, at 2:55 PM, Abel Lopez wrote:
>
> After digging around and switching my distribution to RDO (I
Clint Byrum writes:
>
> I also think you should share this on openstack-dev, as the developers
> may also be aware of other efforts that may conflict with or complement
> Romana.
Your mission seems to be very close to that of Project Calico.
Are you seeing the cinder Volume limit error?
If that's the issue the work around is here in the bug description.
https://bugs.launchpad.net/tripleo/+bug/1521639
On Feb 4, 2016 10:31 PM, "Abel Lopez" wrote:
> Hey everyone,
> In my liberty testing, I've got keystone v3
On 02/05/2016 08:17 AM, Chris Marino wrote:
Hi Tomas, functionally, that is pretty accurate, but operationally they
are quite different. All the L3 approaches have fundamentally the same
point of view. I'd add OpenContrail and Nuage and what CloudScaling did
to the list of similar approaches as
Hi Tomas, functionally, that is pretty accurate, but operationally they are
quite different. All the L3 approaches have fundamentally the same point of
view. I'd add OpenContrail and Nuage and what CloudScaling did to the list
of similar approaches as well.
More info here if you interested.
Hi Jay, yes we do.
Besides the obvious ML2 driver, we've probably done more with the new IPAM
API than anyone. We submitted a proposal for the Summit to talk about our
experiences.
Also, we want Romana to work on whatever underlay OpenStack is running and
that's going to require further work so
Hello,
Does anyone have users RAID'ing or striping multiple block storage volumes
from within an instance?
If so, what was the experience? Good, bad, possible but with caveats?
Thanks,
Joe
___
OpenStack-operators mailing list
This week we had a really great meeting, including some folks from the
Horizon team stepping in to help make the Horizon plugin better. We
discussed some of the work relating to the UI piece, and adding tests
to app-catalog-ui to ensure future changes are tested properly against
Horizon.
We also
SuccessBot Says
===
- odyssey4me: OpenStack Ansible Liberty 12.0.5 released.
- stevemar: Devstack now defaults to v3 for Keystone.
- boris-42: osprofiler functional job passed [1].
- dulled: Conference between Nova and Cinder mid-cycles worked!
- odyssey4me: OpenStack Ansible Kilo
14 matches
Mail list logo