[Openstack] Openstack Log Errors monitoring

[ron ramos]

Hi,

May i know if anyone is using any tool to monitor ERROR on all openstack
logs and send out alerts?
Thank you.

Regards,
Ron
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] single openstack deployment across datacenters

[ron ramos]

Hi All,

Would just like to know if this is possible, currently i have 2 openstack
deployment at 2 DCs.
I also have ceph cluster at each DC.

I'm looking at changing this deployment with a single Openstack across DCs,
e.g. i will deploy:
2x controller at DC1
3x controller at DC2
8x compute at DC1
8x compute at DC2

DC1 will have an host aggregate labelled AZ1 with 8 compute
DC2 will have an host aggregate labelled AZ2 with 8 compute


then if possible:
use ceph at DC1 as storage_pool_AZ1
use ceph at DC2 as storage_pool_AZ2

1. Is this setup even possible? :D
2. Is there a way i can force a host aggregate to use specific storage pool?
3. will there an issues on vswitch stretched across DC?

i'm looking at this so i can provide users an option to launch an instance
to a specific AZ and distribute their workload between AZ1 and AZ2 for HA.

Regards,
Nhadie
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Production openstack on 5 node

[ron ramos]

i have tried MaaS+juju openstack deployment quite easy to deploy.


On Mon, Jun 26, 2017 at 3:38 AM, Satish Patel  wrote:

> Thank you folks!
>
> I have 5 node so following role i am planning to implement, I am
> little confused related network component, should i use DVR
> (distributed virtual router ) but problem is every single node need
> public IP address in that case, first time building production style
> openstack so don't know what would be the best option?
>
> 1 controller + network
> 4 compute node
>
> On Wed, Jun 21, 2017 at 10:22 PM, Mike Smith 
> wrote:
> > Agree you should definitely check out what is already out there in
> community
> > if you are starting from scratch.  In our specific case, we do our puppet
> > configs manually because 1) we are still on puppet v3 for everything else
> > and 2) we have been doing it this way since Folsom and it’s worked well.
> >
> > We are about to build another new cluster on Ocata and I think for that
> one
> > I will try and leverage more of the community puppet stuff if possible.
> >
> > On Jun 21, 2017, at 1:49 PM, John van Ommen 
> wrote:
> >
> > I couldn't agree more. OpenStack deployment is not a trivial task. Do not
> > reinvent the wheel.
> >
> > John
> >
> > On Jun 21, 2017 12:04 PM, "Erik McCormick" 
> > wrote:
> >>
> >> If you are a Puppet shop you should check out the Puppet community
> >> modules. You will get familiar with all the inner goo as you'll need
> your
> >> own composition layer (in my case a series of hiera files). There's no
> >> reason to reinvent the wheel unless you really want to.
> >>
> >> -Erik
> >>
> >> On Jun 21, 2017 2:19 PM, "Satish Patel"  wrote:
> >>>
> >>> Thank you all of you for your opinion, As mike suggested i am also
> >>> planning to brew home grown puppet module to understand each and every
> >>> component and their role instead of grabbing third party tool, I am
> >>> sure OOO is best for 100 deploying 100 compute node but in my setup we
> >>> have only 5 servers and its not worth it to manage undercloud server.
> >>>
> >>> We are puppet shop so it would be easy to write own code and go from
> >>> there.
> >>>
> >>> On Wed, Jun 21, 2017 at 1:25 AM, Remo Mattei  wrote:
> >>> > I did a deployment with cs9 hp it was pretty bad. I hope the new one
> >>> > does
> >>> > better.
> >>> >
> >>> > Nevertheless I do not see many using hp out there. Maybe different
> >>> > regions
> >>> > like emea do better with that.
> >>> >
> >>> > Inviato da iPhone
> >>> >
> >>> > Il giorno 20 giu 2017, alle ore 21:10, John van Ommen
> >>> >  ha scritto:
> >>> >
> >>> > At HPE we originally used TripleO but switched to a 'flat' model.
> >>> >
> >>> > I personally didn't see any advantage to Triple O. In theory, it
> should
> >>> > be
> >>> > easier to manage and upgrade. In the real world, Helion 3.0 and 4.0
> are
> >>> > superior in every respect.
> >>> >
> >>> > John
> >>> >
> >>> > On Jun 20, 2017 9:02 PM, "Remo Mattei"  wrote:
> >>> >>
> >>> >> I worked for Red Hat and they really want to get ooo going because
> the
> >>> >> installation tools did never work as everyone was hoping. Before Red
> >>> >> Hat I
> >>> >> was at Mirantis and the fuel installation was nice now dead. I know
> >>> >> ooo will
> >>> >> go into containers next couple of release but kolla–Ansible is one
> of
> >>> >> the
> >>> >> emerging solutions now to get it out fast.
> >>> >>
> >>> >> I am doing a project now where I am working on deploying ooo just
> >>> >> finished
> >>> >> the doc for Ocata undercloud.
> >>> >>
> >>> >> Just my two cents to concord with Mike’s statement.
> >>> >>
> >>> >> Remo
> >>> >>
> >>> >> Inviato da iPhone
> >>> >>
> >>> >> Il giorno 20 giu 2017, alle ore 20:51, Mike Smith
> >>> >> 
> >>> >> ha scritto:
> >>> >>
> >>> >> There are definitely 1,001 opinions on what is “best”.  We use RDO
> at
> >>> >> Overstock and we use home-grown puppet modules because we do our own
> >>> >> puppet
> >>> >> modules for everything else we do here.  We based everything around
> >>> >> the
> >>> >> official Openstack install documents and we do it because we want to
> >>> >> *fully*
> >>> >> understand everything we can instead of treating it like a black box
> >>> >> that
> >>> >> knows how to do the magic.
> >>> >>
> >>> >> However, there are lots of options out there - ansible, kolla,
> puppet
> >>> >> plus
> >>> >> vendor-specific options too like those provided by Mirantis.  If
> there
> >>> >> are
> >>> >> config management tools (ansible, puppet, etc) that you already use,
> >>> >> you may
> >>> >> want to check out the Openstack options for those.  You are correct
> >>> >> that
> >>> >> that packstack is more of a ‘all-in-one-server’ installer for a
> quick
> >>> >> POC.
> >>> >> It can to more, but I think RDO recommends “Triple-O” 

Re: [Openstack] controller redundancy

[ron ramos]

hi,

depends on what you mean by inaccessible, your VM is probably still up and
running on the compute node. but you won't be able to access them remotely
as your controller node ( which is hosting neutron ) is down.

regards,
nhadie


On Apr 12, 2017 11:31, "Konstantin Raskoshnyi"  wrote:

> Hi guys,
> I'm new to openstack.
> Installed mirantis os 9,
> If one of controllers goes down - vm machines are not accesible, I though
> openstack supposed to work even if one controller is alive
>
> Any thoughts?
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack