osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

openstack-discuss Digest, Vol 10, Issue 59


Hi Ralf Teckelmann,

> Hello,
>
> Utilizing openstack-ansible we successfully installed all the masakari services. Besides masakari-hostmonitor all are running fine.
> For the hostmonitor a pacemaker cluster is missing.
>
> Can anyone give me an overview how the pacemaker cluster setup would look like?
> Which (pacemaker) services is running where (compute nodes, something on any other node,...), etc?
>
> Best regards,
>
> Ralf Teckelmann

Sorry for the late answer...

Masakari team is in process of 'adding devstack support to install host-monitor', please refer community patch [1].
You can refer 'devstack/plugin.sh', please note it has IPMI Hardware support dependency.

Also PFA 'detailed_steps_on_ubuntu_for_pacemaker_verification.txt' for verification of same carried out on Ubuntu distribution (installed openstack using devstack with Masakari enabled).

[1]: https://review.opendev.org/#/c/671200/ Add devstack support to install host-monitor

Thanks with Regards,
Shilpa Shivaji Devharakar| Software Development Supervisor | NTT DATA Services| w. 91-020- 67095703 | Shilpa.Devharakar at nttdata.com | Learn more at nttdata.com/americas

-----Original Message-----
From: openstack-discuss-request at lists.openstack.org <openstack-discuss-request at lists.openstack.org>
Sent: Monday, August 12, 2019 6:30 PM
To: openstack-discuss at lists.openstack.org
Subject: openstack-discuss Digest, Vol 10, Issue 59

Send openstack-discuss mailing list submissions to
openstack-discuss at lists.openstack.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
or, via email, send a message with subject or body 'help' to
openstack-discuss-request at lists.openstack.org

You can reach the person managing the list at
openstack-discuss-owner at lists.openstack.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..."


Today's Topics:

   1. Re: [tripleo][openstack-ansible] Integrating
      ansible-role-collect-logs in OSA (Arx Cruz)
   2. [swauth][swift] Retiring swauth (Ondrej Novy)
   3. [ironic] Resuming having weekly meetings (Julia Kreger)
   4. [masakari] pacemaker-remote Setup Overview
      (Teckelmann, Ralf, NMU-OIP)


----------------------------------------------------------------------

Message: 1
Date: Mon, 12 Aug 2019 12:32:34 +0200
From: Arx Cruz <arxcruz at redhat.com>
To: Jean-Philippe Evrard <jean-philippe at evrard.me>
Cc: openstack-discuss at lists.openstack.org
Subject: Re: [tripleo][openstack-ansible] Integrating
ansible-role-collect-logs in OSA
Message-ID:
<CAB27Hy1tB0TjEwsvrgeBUF1NFCzDadE58-VR68Qt_=3RKY+fVw at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hello,

I've started to split the logs collection tasks in small tasks [1] in order to allow other users to choose what exactly they want to collect.
For example, if you don't need the openstack information, or if you don't care about networking, etc.

Please take a look.

I'll also add it on the OSA agenda for tomorrow's meeting.

Kind regards,

1 - https://review.opendev.org/#/c/675858/

On Mon, Jul 22, 2019 at 8:44 AM Jean-Philippe Evrard < jean-philippe at evrard.me> wrote:

> Sorry for the late answer...
>
> On Wed, 2019-07-10 at 12:12 -0600, Wesley Hayutin wrote:
> >
> > These are of course just passed in as extra-config.  I think each
> > project would want to define their own list of files and maintain it
> > in their own project.  WDYT?
>
> Looks good. We can either clean up the defaults, or OSA can just
> override the defaults, and it would be good enough. I would say that
> this can still be improved later, after OSA has started using the role
> too.
>
> > It simple enough. But I am happy to see a different approach.
>
> Simple is good!
>
> > Any thoughts on additional work that I am not seeing?
>
> None :)
>
> >
> > Thanks for responding! I know our team is very excited about the
> > continued collaboration with other upstream projects, so thanks!!
> >
>
> Likewise. Let's reduce tech debt/maintain more code together!
>
> Regards,
> Jean-Philippe Evrard (evrardjp)
>
>
>
>
>

--

Arx Cruz

Software Engineer

Red Hat EMEA <https://www.redhat.com>

arxcruz at redhat.com
@RedHat <https://twitter.com/redhat>   Red Hat
<https://www.linkedin.com/company/red-hat>  Red Hat <https://www.facebook.com/RedHatInc>
<https://www.redhat.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190812/f8492593/attachment-0001.html>

------------------------------

Message: 2
Date: Mon, 12 Aug 2019 12:56:15 +0200
From: Ondrej Novy <novy at ondrej.org>
To: openstack-discuss at lists.openstack.org
Subject: [swauth][swift] Retiring swauth
Message-ID:
<CAOO6c=wgDZDRpQboo=_0qZ=fHrfu0rO0w=PaUat9bJduwFiVXw at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi,

because swauth is not compatible with current Swift, doesn't support Python 3, I don't have time to maintain it and my employer is not interested in swauth, I'm going to retire swauth project.

If nobody take over it, I will start removing swauth from opendev on 08/24.

Thanks.

--
Best regards
 OndÅ?ej Nový
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190812/28f563f9/attachment-0001.html>

------------------------------

Message: 3
Date: Mon, 12 Aug 2019 07:55:07 -0400
From: Julia Kreger <juliaashleykreger at gmail.com>
To: openstack-discuss <openstack-discuss at lists.openstack.org>
Subject: [ironic] Resuming having weekly meetings
Message-ID:
<CAF7gwdhSWcUbYu0S2QfvjO44Q_5vJr6KTUQE3TRu3UYirqFGmQ at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

All,

I meant to send this specific email last week, but got distracted and $life.

I believe we need to go back to having weekly meetings. The couple times I floated this in the past two weeks, there hasn't seemed to be any objections, but I also did not perceive any real thoughts on the subject. While the concept and use of office hours has seemingly helped bring some more activity to our IRC channel, we don't have a check-point/sync-up mechanism without an explicit meeting.

With that being said, I'm going to start the meeting today and if we have quorum, try to proceed with it today.

-Julia



------------------------------

Message: 4
Date: Mon, 12 Aug 2019 12:59:20 +0000
From: "Teckelmann, Ralf, NMU-OIP" <ralf.teckelmann at bertelsmann.de>
To: "openstack-discuss at lists.openstack.org"
<openstack-discuss at lists.openstack.org>
Subject: [masakari] pacemaker-remote Setup Overview
Message-ID:
<AM6PR04MB47112DF6617442709662B43389D30 at AM6PR04MB4711.eurprd04.prod.outlook.com>

Content-Type: text/plain; charset="utf-8"

Hello,

Utilizing openstack-ansible we successfully installed all the masakari services. Besides masakari-hostmonitor all are running fine.
For the hostmonitor a pacemaker cluster is missing.

Can anyone give me an overview how the pacemaker cluster setup would look like?
Which (pacemaker) services is running where (compute nodes, something on any other node,...), etc?

Best regards,

Ralf Teckelmann

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190812/e0e36e53/attachment.html>

------------------------------

Subject: Digest Footer

_______________________________________________
openstack-discuss mailing list
openstack-discuss at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss


------------------------------

End of openstack-discuss Digest, Vol 10, Issue 59
*************************************************
Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: detailed_steps_on_ubuntu_for_pacemaker_verification
Type: application/octet-stream
Size: 3262 bytes
Desc: detailed_steps_on_ubuntu_for_pacemaker_verification
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190819/b55c0101/attachment.obj>