Hi Ops,
For the last few Design Summits, I've run a docs session in the Ops track, to
focus on the Ops Guide (and, to a lesser extent, the Architecture Guide). Is
there interest in doing this again? If so, can I please grab a slot?
Thanks,
Lana (Docs PTL)
--
Lana Brindley
Technical Writer
We run completely separate clusters. I’m sure vhosts give you acceptable
security but it means also sharing disk and ram which means if something went
awry and generated lots of messages etc. it could take your whole rabbit
cluster down.
Sam
> On 17 Sep 2016, at 3:34 PM, Joe Topjian
+1 This was our concern also with Trove. If a tenant DoSes Trove we
probably don't all get fired. The rest of rabbit is just too important to
risk sharing.
On Sun, Sep 18, 2016 at 6:53 PM, Sam Morrison wrote:
> We run completely separate clusters. I’m sure vhosts give you
Hi everyone,
The Ops/Arch Guides specialty team meeting time has changed to biweekly on
Monday 2100 UTC in IRC #openstackmeeting3. Tomorrow we will discuss the docs
session at the ops midcycle
(https://etherpad.openstack.org/p/NYC-ops-Documentation) and the direction of
the Ops Guide.
Feel
I'd love to see your results on this . Very interesting stuff.
On Sep 17, 2016 1:37 AM, "Joe Topjian" wrote:
> Hi all,
>
> We're planning to deploy Murano to one of our OpenStack clouds and I'm
> debating the RabbitMQ setup.
>
> For background: the Murano agent that runs on
Good call.
I think Matt bringing up Trove is worthwhile, too. If we were to consider
deploying Trove in the future, and now that I've learned it also has an
agent/rabbit setup, there's definitely more weight behind a second
agent-only Rabbit cluster.
On Sun, Sep 18, 2016 at 9:15 PM, Sam Morrison
Hi Shiva.
I think you shoud have a try with OpenvSwitch mirror port or
Tap-as-a-service
2016-09-17 1:45 GMT+07:00 shiva m :
> Hi,
>
>
> I have lauched an IPS (intrusion prevention system, l2 device) instance on
> devstack. I want to examine traffic hitting br-int and pass
Thanks for everyone's input. I think I'm going to go with a single Rabbit
cluster and separate by vhosts. Our environment is nowhere as large as
NeCTAR or TWC, so I can definitely understand concern about Rabbit blowing
the cloud up. We can be a little bit more flexible.
As a precaution, though,