Hi everyone !!!. I study project Neutron in Openstack. I see Neutron use 5
use case and i set up Juno follow use case Per-tentant router with private
network so Can I combine 2 use case are Multiple flat network and
Per-tentant ? If yes, how to config file Neutron ?
Thanks...
__
Hi all,
I guess there are two issues here: one is the definition of the model
(the parameters, tags or whatever that you want to track), and the other
one is to which extent it can be computed automatically, or needs human
intervention (or human interpretation).
For the first one, in other cases
Problem solved.
In this test/lab cloud, we're using vmware to host the network node.
Putting the esx's virtual switch in promiscuous mode did the trick.
On Tue, May 5, 2015 at 3:54 PM, Gustavo Randich
wrote:
> Hi everybody,
>
> I've just configuerd DVR in Kilo. Everything is fine, except that
There is a summit session in Vancouver with some ideas in
https://etherpad.openstack.org/p/YVR-ops-tags.
I have added the links there as reference material. Building on a previous
work from other communities would be an interesting possibility.
We donĀ¹t need to wait till then so comments on the e
Hi everybody,
I've just configuerd DVR in Kilo. Everything is fine, except that instances
with no floating-ip cannot reach external network.
NETWORKS
neutron net-create ext-net1 --router:external --provider:physical_network
external --provider:network_type flat
neutron subnet-create ext-net1 10.1
I think since PHL many of us have been just waiting for info on how we can
participate and proceed. Happy to discuss further in YVR or just start
tagging...
-dave
On Tue, May 5, 2015 at 12:31 PM, Stefano Maffulli
wrote:
> Hello folks,
>
> in PHL meeting the discussion on project tags[1] highlig
Hello folks,
in PHL meeting the discussion on project tags[1] highlighted that
operators are looking for answers to questions like:
* Are fixes backported? Or Consumes Master to get fixes?
* Is it packaged?
* Is it stable? Mature?
* is it tested in Tempest/Rally/whatever so I can test
Hello there!
We - that is David Lyle, Stefano Maffulli, and I - would like to invite you
to fill out a short survey on the user interfaces you deploy for your
openstack clouds. Specifically, we're curious about your Horizon/Openstack
Dashboard usage, and how you've customized, modified, or replace
On Tue, May 5, 2015 at 11:33 AM, Curtis wrote:
> Do people have any comments or strategies on dealing with Galera
> replication across the WAN using regions? Seems like something to try
> to avoid if possible, though might not be possible. Any thoughts on
> that?
>
We're doing this with good luc
We do it with some of our databases (horizon, designate, and keystone) and
we run a arbitrator process (garbd) in a 3rd DC. We have lots of low
latency bandwidth which you have to be careful with. My recommendation
would be that you need to know your network well and have good monitoring
in place.
Do people have any comments or strategies on dealing with Galera
replication across the WAN using regions? Seems like something to try
to avoid if possible, though might not be possible. Any thoughts on
that?
Thanks,
Curtis.
On Mon, May 4, 2015 at 3:11 PM, Jesse Keating wrote:
> I agree with Sub
Hi,
I am trying to setup the policies for nova. Can you please have a look if thats
correct?
nova/policy.json
"context_is_admin": "role:admin",
"admin_or_owner": "is_admin:True or project_id:%(project_id)s",
"owner": "user_id:%(user_id)s",
"admin_or_user": "
On Mon, May 4, 2015 at 9:42 PM, Tom Fifield wrote:
> Do you need users to be able to see it as one cloud, with a single API
> endpoint?
Define need :)
As many of you know my cloud is a University system and researchers
are nothing if not lazy, in the best possible sense of course :) So
having
Second installation, IMHO. Everything else would make it less robust.
On 05/04/2015 11:40 PM, Jonathan Proulx wrote:
Hi All,
We're about to expand our OpenStack Cloud to a second datacenter.
Anyone one have opinions they'd like to share as to what I would and
should be worrying about or how to
14 matches
Mail list logo