August 2019 - openstack-discuss - lists.openstack.org

[uc] Less than 4 days left to nominate for the UC!
by Ed Leafe 20 Aug '19

20 Aug '19

A week has gone by since nominations opened, and we have yet to receive a single nomination! Now I’m sure everyone’s waiting until the last minute in order to make a dramatic moment, but don’t put it off for *too* long! If you missed the initial announcement [0], here’s the information you need: Any individual member of the Foundation who is an Active User Contributor (AUC) can propose their candidacy (except the three sitting UC members elected in the previous election). Self-nomination is common, no third party nomination is required. They do so by sending an email to the user-committee(a)lists.openstack.orgmailing-list, with the subject: “UC candidacy” by August 16, 05:59 UTC. The email can include a description of the candidate platform. The candidacy is then confirmed by one of the election officials, after verification of the electorate status of the candidate. -- Ed Leafe [0] http://lists.openstack.org/pipermail/user-committee/2019-August/002864.html

3 4

Update / change user_id from server / VM
by Pawel Konczalski 20 Aug '19

20 Aug '19

Hi all, is it possible to update / change the user_id of a OpenStack server (VM) if the user no more exists? # openstack server show 8cf8164a-6f55-4435-9f4e-621617d7951f -c user_id +---------+----------------------------------+ | Field | Value | +---------+----------------------------------+ | user_id | ebfd5b2bf26a4f4381a290948cb3ce8b | +---------+----------------------------------+ # openstack user show ebfd5b2bf26a4f4381a290948cb3ce8b No user with a name or ID of 'ebfd5b2bf26a4f4381a290948cb3ce8b' exists. BR Pawel

1 0

ops meetup team meeting 2019-8-20
by Chris Morgan 20 Aug '19

20 Aug '19

Minutes for the openstack ops meetups team meeting today are linked below. Here are some notes: - Attendance at the upcoming NYC meetup (hosted at Bloomberg) is up to 40 and still growing - Hoping to arrange a social event on the evening of day 1, a sponsor for that is still being sought - easiest way to get updates is to follow https://twitter.com/osopsmeetup - one of the sessions will propose bringing more ceph content to these meetups or starting a new similar dedicated ceph operators meetup series <https://twitter.com/osopsmeetup> Meeting ended Tue Aug 20 14:37:20 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 10:37 AM Minutes: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_tea… 10:37 AM Minutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_tea… 10:37 AM Log: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_tea… Cheers, Chris -- Chris Morgan <mihalis68(a)gmail.com>

1 0

[all][infra] Changes to docs publishing (promote pipeline)
by Andreas Jaeger 20 Aug '19

20 Aug '19

We have set up in Zuul a new way of publishing artifacts and are beginning to use that now for documentation jobs [1]: The documents built in the gate queue are published as is with just copying over to our webserver in the promote pipeline. The jobs for building are still the same name (small implementation change), only the publish job has changed: It's now in the promote pipeline. There's no need for you to do anything. This work has been done for openstack-tox-docs (used by most OpenStack projects), api-ref and api-guide jobs, and for openstack-manuals and friends. To iterate the old way was: 1) Build docs in gate pipeline 2) Merge 3) Build docs in post pipeline (same git tree!) 4) Publish Now we do: 1) Build docs in gate pipeline 2) Merge 3) Take logs from gate pipeline and publish them You will notice a changed behaviour: The promote pipeline reports to gerrit - unlike the post one. So, you see that in the review and also get notified via email. Note that changes currently in gate pipeline might have used the previous openstack-tox-docs implemention and will fail since the promote job needs the changed implementation. The next publish will work. If you have any questions, please ask on #openstack-infra IRC channel. [1] https://review.opendev.org/677009 -- Andreas Jaeger aj(a)suse.com Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 0

How are we managing quotas, flavors, projects and more across large org Openstack deployments?
by Robert Lennie 20 Aug '19

20 Aug '19

Hi, I am a complete neophyte to this forum so I may have missed any earlier discussions on this topic if there have been any? I am currently working on a proprietary legacy (Django based) "OpenStack Operations Manager" dashboard system that attempts to manage quotas, flavors, clusters and more across a very large distributed OpenStack deployment for multiple customers. There are a number of potential shortcomings with our current dashboard system and I was wondering how other teams in other organizations with similar large Openstack deployments are handling these types of system management issues? The issues addressed are likely common to other large environments. In particular what tools might exist upstream that allow system (particularly quota and flavor) management across large distributed Openstack environments? I welcome any feedback, comments, suggestions and any other information regarding the tools that currently exist or may be planned for this purpose? Regards, Robert Lennie Principal Software Engineer Verizon Media

5 5

Re: [masakari] how to install masakari on centos 7 (Vu Tan)
by Devharakar, Shilpa 20 Aug '19

20 Aug '19

Hi Vu Tan, Sorry for the attachment, instead please refer [1] Here are the steps we verified for Masakari installation on Ubuntu Distribution with openstack installed via devstack. [1]: http://paste.openstack.org/show/760303/ > Hi Vu Tan, > > Sorry for late reply. > Here are the steps we verified on Ubuntu Distribution, installed openstack via devstack. > > PFA 'detailed_steps_to_install_masakari.txt' > Do not refer '/masakari/etc/Masakari.conf' sample file, instead generate it using 'tox -egenconfig' after 'git clone' Thanks with Regards, Shilpa Shivaji Devharakar| Software Development Supervisor | NTT DATA Services| w. 91-020- 67095703 | Shilpa.Devharakar(a)nttdata.com | Learn more at nttdata.com/americas -----Original Message----- From: openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Sent: Monday, August 19, 2019 10:42 PM To: openstack-discuss(a)lists.openstack.org Subject: openstack-discuss Digest, Vol 10, Issue 95 Send openstack-discuss mailing list submissions to openstack-discuss(a)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(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)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: [all] [tc] [docs] [release] [ptls] Docs as SIG: Ownership of docs.openstack.org (Doug Hellmann) 2. Re: [openstack-dev] Dropping lazy translation support (Shengjing Zhu) 3. [neutron] Bug Deputy Report August 12 - August 19 (Ryan Tidwell) 4. Re: [masakari] how to install masakari on centos 7 (Vu Tan) (Devharakar, Shilpa) ---------------------------------------------------------------------- Message: 1 Date: Mon, 19 Aug 2019 12:59:32 -0400 From: Doug Hellmann <doug(a)doughellmann.com> To: Sean McGinnis <sean.mcginnis(a)gmx.com> Cc: Alexandra Settle <a.settle(a)outlook.com>, OpenStack Discuss <openstack-discuss(a)lists.openstack.org> Subject: Re: [all] [tc] [docs] [release] [ptls] Docs as SIG: Ownership of docs.openstack.org Message-ID: <9DABCC6E-1E61-45A6-8370-4F086428B3B6(a)doughellmann.com> Content-Type: text/plain;charset=utf-8 > On Aug 19, 2019, at 11:41 AM, Sean McGinnis <sean.mcginnis(a)gmx.com> wrote: > >> >> Quick recap: The documentation team is set to disband as an official >> project, and make the leap to becoming a SIG (Special Interest Group). >> >> >> The remaining individuals working on the docs team are sorting >> through what's left and where it is best placed. In [1], Doug has >> rightfully pointed out that whilst the documentation team as it >> stands today is no longer "integral", the docs.openstack.org web site >> is. An owner is required. >> > > Unless things have changed, SIGs can be owners of a resource published > via docs.openstack.org (and I am assuming that means be extension, > docs.o.o itself). Is there a reason the Docs SIG would not still be > able to own the site? > >> The suggestion is for the Release Management team is the "least worst" >> (thanks, tonyb) place for the website manaagement to land. As Tony >> points out, this requires learning new tools and processes but the >> individuals working on the docs team currently have no intention to >> leave, and are around to help manage this from the SIG. >> > > I'm personally fine with the release team taking this on, but it does > seem like an odd fit. I think it would make a lot more sense for the > Docs SIG to own the docs site than the release team. Thierry has always drawn (one of) the distinction(s) between teams and SIGs as being that teams own tasks that are “part of” the thing we produce that we call OpenStack, while SIGs are less formally part of that input to that production process. Updating the docs site every time we have a new release felt like it should be part of the formal process, and definitely not something we should leave to chance. The cadence made me think the release team could be a good home. It’s 95% automated now, for what that’s worth. I imagine someone could automate the step of adding the new series pages, although I’m not sure what the trigger would be. We could also look at other ways to build the site that don’t require any action each cycle, of course, including not updating it at all and only publishing docs out of master. That’s especially appealing if we don’t have anyone in the community willing and able to pick up the work. > >> Open to discussion and suggestions, but to summarise the proposal here: >> >> docs.openstack.org ownership is to transition to be the >> responsibility of the Release Management team officially provided >> there are no strong objections. >> >> Thanks, >> >> Alex >> IRC: asettle >> >> [1] https://review.opendev.org/#/c/657142/ >> [2] https://review.opendev.org/#/c/657141/ > ------------------------------ Message: 2 Date: Mon, 19 Aug 2019 20:46:05 +0800 From: Shengjing Zhu <zsj950618(a)gmail.com> To: openstack-discuss(a)lists.openstack.org Cc: mriedemos(a)gmail.com Subject: Re: [openstack-dev] Dropping lazy translation support Message-ID: <CAG+qr1F8BcOvw3YyQg9CUptkSxDAsW_125aSCDydTGjWQHfLiw(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Sorry for replying the old mail, and please cc me when reply. Matt Riedemann <mriedemos at gmail.com> writes: > This is a follow up to a dev ML email [1] where I noticed that some > implementations of the upgrade-checkers goal were failing because some > projects still use the oslo_i18n.enable_lazy() hook for lazy log > message translation (and maybe API responses?). > > The very old blueprints related to this can be found here [2][3][4]. > > If memory serves me correctly from my time working at IBM on this, > this was needed to: > > 1. Generate logs translated in other languages. > > 2. Return REST API responses if the "Accept-Language" header was used > and a suitable translation existed for that language. > > #1 is a dead horse since I think at least the Ocata summit when we > agreed to no longer translate logs since no one used them. > > #2 is probably something no one knows about. I can't find end-user > documentation about it anywhere. It's not tested and therefore I have > no idea if it actually works anymore. > > I would like to (1) deprecate the oslo_i18n.enable_lazy() function so > new projects don't use it and (2) start removing the enable_lazy() > usage from existing projects like keystone, glance and cinder. > > Are there any users, deployments or vendor distributions that still > rely on this feature? If so, please speak up now. I was pointed to this discussion when I tried to fix this feature in keystone, https://review.opendev.org/677117 For #2 translated API response, this feature probably hasn't been working for some time, but it's still a valid user case. Has the decision been settled? -- Regards, Shengjing Zhu ------------------------------ Message: 3 Date: Mon, 19 Aug 2019 11:32:23 -0500 From: Ryan Tidwell <rktidwell85(a)gmail.com> To: openstack-discuss(a)lists.openstack.org Subject: [neutron] Bug Deputy Report August 12 - August 19 Message-ID: <CAKe2JbjhPpg0AjwX8yXj+iTtuYCVe=PoGOgcK0DdoNyLFRckFw(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hello Neutron Team, Here is my bug deputy report for August 12 - August 19: Medium: -[OVS agent] Physical bridges can't be initialized if there is no connectivity to rabbitmq https://bugs.launchpad.net/neutron/+bug/1840443 The fix for this has been merged and a number of backports have merged as well. It appears to have been handled by the team. - excessive number of dvrs where vm got a fixed ip on floating network https://bugs.launchpad.net/bugs/1840579 https://review.opendev.org/#/c/677092/ has been proposed and is being worked on. This appears to be related to how we determine whether to instantiate a DVR local router on a compute node. It looks like there is a case where we create a local router when it's not necessary, thereby consuming too many IP's on the floating IP network at scale. Undecided: - network/subnet resources cannot be read and written separated https://bugs.launchpad.net/neutron/+bug/1840638 https://review.opendev.org/#/c/677166/ has been proposed. This was just reported just a few hours ago and still needs some triage to confirm severity of the issue. RFE's: - [RFE] Add new config option to enable IGMP snooping in ovs https://bugs.launchpad.net/bugs/1840136 Regards, Ryan Tidwell -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190819…> ------------------------------ Message: 4 Date: Mon, 19 Aug 2019 16:33:40 +0000 From: "Devharakar, Shilpa" <Shilpa.Devharakar(a)nttdata.com> To: "openstack-discuss(a)lists.openstack.org" <openstack-discuss(a)lists.openstack.org> Subject: Re: [masakari] how to install masakari on centos 7 (Vu Tan) Message-ID: <CH2PR12MB4072BC1B71DAFAF0B8E3021CFFA80(a)CH2PR12MB4072.namprd12.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Hi Vu Tan, Sorry for late reply. Here are the steps we verified on Ubuntu Distribution, installed openstack via devstack. PFA 'detailed_steps_to_install_masakari.txt' Do not refer '/masakari/etc/Masakari.conf' sample file, instead generate it using 'tox -egenconfig' after 'git clone' > Hi Patil, > May I know how is it going ? > >> On Tue, Jul 23, 2019 at 10:18 PM Vu Tan <vungoctan252(a)gmail.com> wrote: >> >> Hi Patil, >> Thank you for your reply, please instruct me if you successfully >> install it. Thanks a lot >> >> On Tue, Jul 23, 2019 at 8:12 PM Patil, Tushar > > <Tushar.Patil(a)nttdata.com> >> wrote: >> >> Hi Vu Tan, >> >> I'm trying to install Masakari using source code to reproduce the issue. >> If I hit the same issue as yours, I will troubleshoot this issue and >> let you know the solution or will update you what steps I have >> followed to bring up Masakari services successfully. >> >> Regards, >> Tushar Patil >> >> ________________________________________ >> From: Vu Tan <vungoctan252(a)gmail.com> >> Sent: Monday, July 22, 2019 12:33 PM >> To: Gaëtan Trellu >> Cc: Patil, Tushar; openstack-discuss(a)lists.openstack.org >> Subject: Re: [masakari] how to install masakari on centos 7 >> >> Hi Patil, >> May I know when the proper document for masakari is released ? I have >> configured conf file in controller and compute node, it seems running >> but it is not running as it should be, a lots of error in logs, here >> is a sample log: >> >> 2.7/site-packages/oslo_config/cfg.py:3024 >> 2019-07-19 10:25:26.360 7745 DEBUG oslo_service.service [-] bindir >> = /usr/local/bin log_opt_values /usr/lib/ >> python2.7/site-packages/oslo_config/cfg.py:3024 >> 2019-07-19 18:46:21.291 7770 ERROR masakari File >> "/usr/lib/python2.7/site-packages/oslo_service/service.py", line 65, >> in _is_daemo n >> 2019-07-19 18:46:21.291 7770 ERROR masakari is_daemon = os.getpgrp() >> != os.tcgetpgrp(sys.stdout.fileno()) >> 2019-07-19 18:46:21.291 7770 ERROR masakari OSError: [Errno 5] >> Input/output error >> 2019-07-19 18:46:21.291 7770 ERROR masakari >> 2019-07-19 18:46:21.300 7745 CRITICAL masakari [-] Unhandled error: >> OSError: [Errno 5] Input/output error >> 2019-07-19 18:46:21.300 7745 ERROR masakari Traceback (most recent >> call >> last): >> 2019-07-19 18:46:21.300 7745 ERROR masakari File >> "/usr/bin/masakari-api", line 10, in <module> >> >> I dont know if it is missing package or wrong configuration >> >> >> On Thu, Jul 11, 2019 at 6:14 PM Gaëtan Trellu < >> gaetan.trellu(a)incloudus.com<mailto:gaetan.trellu@incloudus.com>> wrote: >> You will have to enable the debit, debug = true and check the APi log. >> >> Did you try to use the openstack CLi ? >> >> Gaetan >> >> On Jul 11, 2019 12:32 AM, Vu Tan <vungoctan252(a)gmail.com<mailto: >> vungoctan252(a)gmail.com>> wrote: >> I know it's just a warning, just take a look at this image: >> [image.png] >> it's just hang there forever, and in the log show what I have shown >> to you >> >> On Wed, Jul 10, 2019 at 8:07 PM Gaëtan Trellu < >> gaetan.trellu(a)incloudus.com<mailto:gaetan.trellu@incloudus.com>> wrote: >> This is just a warning, not an error. >> >> On Jul 10, 2019 3:12 AM, Vu Tan <vungoctan252(a)gmail.com<mailto: >> vungoctan252(a)gmail.com>> wrote: >> Hi Gaetan, >> I follow you the guide you gave me, but the problem still persist, >> can you please take a look at my configuration to see what is wrong >> or what is missing in my config ? >> the error: >> 2019-07-10 14:08:46.876 17292 WARNING >> keystonemiddleware._common.config [-] The option "__file__" in conf >> is not known to auth_token >> 2019-07-10 14:08:46.876 17292 WARNING >> keystonemiddleware._common.config [-] The option "here" in conf is >> not known to auth_token >> 2019-07-10 14:08:46.882 17292 WARNING keystonemiddleware.auth_token >> [-] AuthToken middleware is set with keystone_authtoken.service_ >> >> the config: >> >> [DEFAULT] >> enabled_apis = masakari_api >> log_dir = /var/log/kolla/masakari >> state_path = /var/lib/masakari >> os_user_domain_name = default >> os_project_domain_name = default >> os_privileged_user_tenant = service >> os_privileged_user_auth_url = http://controller:5000/v3 >> os_privileged_user_name = nova os_privileged_user_password = P@ssword >> masakari_api_listen = controller masakari_api_listen_port = 15868 >> debug = False auth_strategy=keystone >> >> [wsgi] >> # The paste configuration file path >> api_paste_config = /etc/masakari/api-paste.ini >> >> [keystone_authtoken] >> www_authenticate_uri = http://controller:5000 auth_url = >> http://controller:5000 auth_type = password project_domain_id = >> default project_domain_name = default user_domain_name = default >> user_domain_id = default project_name = service username = masakari >> password = P@ssword region_name = RegionOne >> >> [oslo_middleware] >> enable_proxy_headers_parsing = True >> >> [database] >> connection = mysql+pymysql://masakari:P@ssword@controller/masakari >> >> >> >> On Tue, Jul 9, 2019 at 10:25 PM Vu Tan <vungoctan252(a)gmail.com<mailto: >> vungoctan252(a)gmail.com>> wrote: >> Thank Patil Tushar, I hope it will be available soon >> >> On Tue, Jul 9, 2019 at 8:18 AM Patil, Tushar >> <Tushar.Patil(a)nttdata.com <mailto:Tushar.Patil@nttdata.com>> wrote: >> Hi Vu and Gaetan, >> >> Gaetan, thank you for helping out Vu in setting up masakari-monitors >> service. >> >> As a masakari team ,we have noticed there is a need to add proper >> documentation to help the community run Masakari services in their >> environment. We are working on adding proper documentation in this 'Train' >> cycle. >> >> Will send an email on this mailing list once the patches are uploaded >> on the gerrit so that you can give your feedback on the same. >> >> If you have any trouble in setting up Masakari, please let us know on >> this mailing list or join the bi-weekly IRC Masakari meeting on the >> #openstack-meeting IRC channel. The next meeting will be held on 16th >> July >> 2019 @0400 UTC. >> >> Regards, >> Tushar Patil >> >> ________________________________________ >> From: Vu Tan <vungoctan252(a)gmail.com<mailto:vungoctan252@gmail.com>> >> Sent: Monday, July 8, 2019 11:21:16 PM >> To: Gaëtan Trellu >> Cc: openstack-discuss(a)lists.openstack.org<mailto: >> openstack-discuss(a)lists.openstack.org> >> Subject: Re: [masakari] how to install masakari on centos 7 >> >> Hi Gaetan, >> Thanks for pinpoint this out, silly me that did not notice the simple >> "error InterpreterNotFound: python3". Thanks a lot, I appreciate it >> >> On Mon, Jul 8, 2019 at 9:15 PM <gaetan.trellu(a)incloudus.com<mailto: >> gaetan.trellu(a)incloudus.com><mailto:gaetan.trellu@incloudus.com<mailto: >> gaetan.trellu(a)incloudus.com>>> wrote: >> Vu Tan, >> >> About "auth_token" error, you need "os_privileged_user_*" options >> into your masakari.conf for the API. >> As mentioned previously please have a look here to have an example of >> configuration working (for me at least): >> >> - masakari.conf: >> >> https://review.opendev.org/#/c/615715/42/ansible/roles/masakari/templ >> ates/masakari.conf.j2 >> - masakari-monitor.conf: >> >> https://review.opendev.org/#/c/615715/42/ansible/roles/masakari/templ >> ates/masakari-monitors.conf.j2 >> >> About your tox issue make sure you have Python3 installed. >> >> Gaëtan >> >> On 2019-07-08 06:08, Vu Tan wrote: >> >> > Hi Gaetan, >> > I try to generate config file by using this command tox -egenconfig >> > on top level of masakari but the output is error, is this masakari >> > still in beta version ? >> > [root@compute1 masakari-monitors]# tox -egenconfig genconfig >> > create: /root/masakari-monitors/.tox/genconfig >> > ERROR: InterpreterNotFound: python3 >> > _____________________________________________________________ >> > summary >> > ______________________________________________________________ >> > ERROR: genconfig: InterpreterNotFound: python3 >> > >> > On Mon, Jul 8, 2019 at 3:24 PM Vu Tan <vungoctan252(a)gmail.com<mailto: >> vungoctan252(a)gmail.com><mailto:vungoctan252@gmail.com<mailto: >> vungoctan252(a)gmail.com>>> wrote: >> > Hi, >> > Thanks a lot for your reply, I install pacemaker/corosync, >> > masakari-api, maskari-engine on controller node, and I run >> > masakari-api with this command: masakari-api, but I dont know >> > whether the process is running like that or is it just hang there, >> > here is what it shows when I run the command, I leave it there for >> > a while but it does not change anything : >> > [root@controller masakari]# masakari-api >> > 2019-07-08 15:21:09.946 30250 INFO masakari.api.openstack [-] >> > Loaded >> > extensions: ['extensions', 'notifications', 'os-hosts', 'segments', >> > 'versions'] >> > 2019-07-08 15:21:09.955 30250 WARNING >> > keystonemiddleware._common.config [-] The option "__file__" in conf >> > is not known to auth_token >> > 2019-07-08 15:21:09.955 30250 WARNING >> > keystonemiddleware._common.config [-] The option "here" in conf is >> > not known to auth_token >> > 2019-07-08 15:21:09.960 30250 WARNING keystonemiddleware.auth_token >> > [-] AuthToken middleware is set with >> > keystone_authtoken.service_token_roles_required set to False. This >> > is backwards compatible but deprecated behaviour. Please set this to True. >> > 2019-07-08 15:21:09.974 30250 INFO masakari.wsgi [-] masakari_api >> > listening on 127.0.0.1:15868<http://127.0.0.1:15868>< >> http://127.0.0.1:15868> >> > 2019-07-08 15:21:09.975 30250 INFO oslo_service.service [-] >> > Starting 4 workers >> > 2019-07-08 15:21:09.984 30274 INFO >> > masakari.masakari_api.wsgi.server [-] (30274) wsgi starting up on >> > http://127.0.0.1:15868 >> > 2019-07-08 15:21:09.985 30275 INFO >> > masakari.masakari_api.wsgi.server [-] (30275) wsgi starting up on >> > http://127.0.0.1:15868 >> > 2019-07-08 15:21:09.992 30277 INFO >> > masakari.masakari_api.wsgi.server [-] (30277) wsgi starting up on >> > http://127.0.0.1:15868 >> > 2019-07-08 15:21:09.994 30276 INFO >> > masakari.masakari_api.wsgi.server [-] (30276) wsgi starting up on >> > http://127.0.0.1:15868 >> > >> > On Sun, Jul 7, 2019 at 7:37 PM Gaëtan Trellu >> ><gaetan.trellu(a)incloudus.com<mailto:gaetan.trellu@incloudus.com >> ><mailto:gaetan.trellu@incloudus.com<mailto:gaetan.trellu@incloudus.c >> >om>>> >> wrote: >> > >> > Hi Vu Tan, >> > >> > Masakari documentation doesn't really exist... I had to figured >> > some stuff by myself to make it works into Kolla project. >> > >> > On controller nodes you need: >> > >> > - pacemaker >> > - corosync >> > - masakari-api (openstack/masakari repository) >> > - masakari- engine (openstack/masakari repository) >> > >> > On compute nodes you need: >> > >> > - pacemaker-remote (integrated to pacemaker cluster as a resource) >> > - masakari- hostmonitor (openstack/masakari-monitor repository) >> > - masakari-instancemonitor (openstack/masakari-monitor repository) >> > - masakari-processmonitor (openstack/masakari-monitor repository) >> > >> > For masakari-hostmonitor, the service needs to have access to >> > systemctl command (make sure you are not using sysvinit). >> > >> > For masakari-monitor, the masakari-monitor.conf is a bit different, >> > you will have to configure the [api] section properly. >> > >> > RabbitMQ needs to be configured (as transport_url) on masakari-api >> > and masakari-engine too. >> > >> > Please check this review[1], you will have masakari.conf and >> > masakari-monitor.conf configuration examples. >> > >> > [1] https://review.opendev.org/#/c/615715 >> > >> > Gaëtan >> > >> > On Jul 7, 2019 12:08 AM, Vu Tan <vungoctan252(a)gmail.com<mailto: >> vungoctan252(a)gmail.com><mailto:vungoctan252@gmail.com<mailto: >> vungoctan252(a)gmail.com>>> wrote: >> > >> > VU TAN <VUNGOCTAN252(a)GMAIL.COM<mailto:VUNGOCTAN252@GMAIL.COM><mailto: >> VUNGOCTAN252(a)GMAIL.COM<mailto:VUNGOCTAN252@GMAIL.COM>>> >> > >> > 10:30 AM (35 minutes ago) >> > >> > to openstack-discuss >> > >> > Sorry, I resend this email because I realized that I lacked of >> > prefix on this email's subject >> > >> > Hi, >> > >> > I would like to use Masakari and I'm having trouble finding a step >> > by step or other documentation to get started with. Which part >> > should be installed on controller, which is should be on compute, >> > and what is the prerequisite to install masakari, I have installed >> > corosync and pacemaker on compute and controller nodes, , what else >> > do I need to do ? step I have done so far: >> > - installed corosync/pacemaker >> > - install masakari on compute node on this github repo: >> > https://github.com/openstack/masakari >> > - add masakari in to mariadb >> > here is my configuration file of masakari.conf, do you mind to take >> > a look at it, if I have misconfigured anything? >> > >> > [DEFAULT] >> > enabled_apis = masakari_api >> > >> > # Enable to specify listening IP other than default >> > masakari_api_listen = controller # Enable to specify port other >> > than default masakari_api_listen_port = 15868 debug = False >> > auth_strategy=keystone >> > >> > [wsgi] >> > # The paste configuration file path api_paste_config = >> > /etc/masakari/api-paste.ini >> > >> > [keystone_authtoken] >> > www_authenticate_uri = http://controller:5000 auth_url = >> > http://controller:5000 auth_type = password project_domain_id = >> > default user_domain_id = default project_name = service username = >> > masakari password = P@ssword >> > >> > [database] >> > connection = mysql+pymysql://masakari:P@ssword@controller/masakari >> 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. >> >> >> 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. >> > Thanks with Regards, Shilpa Shivaji Devharakar| Software Development Supervisor | NTT DATA Services| w. 91-020- 67095703 | Shilpa.Devharakar(a)nttdata.com | Learn more at nttdata.com/americas -----Original Message----- From: openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Sent: Sunday, August 4, 2019 12:42 AM To: openstack-discuss(a)lists.openstack.org Subject: openstack-discuss Digest, Vol 10, Issue 13 Send openstack-discuss mailing list submissions to openstack-discuss(a)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(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)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: [nova][ops] Documenting nova tunables at scale (Joe Robinson) 2. Re: [masakari] how to install masakari on centos 7 (Vu Tan) ---------------------------------------------------------------------- Message: 1 Date: Sat, 3 Aug 2019 10:40:11 +1000 From: Joe Robinson <joseph.r.email(a)gmail.com> To: Matt Riedemann <mriedemos(a)gmail.com> Cc: openstack-discuss(a)lists.openstack.org Subject: Re: [nova][ops] Documenting nova tunables at scale Message-ID: <CAOvR4Gx1K+7+Thyz-qv57D-vNx-OZQFtxhxk+X6hCQT3QiGpug(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi Matt, My name is Joe - docs person from years back - this looks like a good initiative and I would be up for documenting these settings at scale. Next step I can see is gathering more Info about this pain point (already started :)) and then I can draft something together for feedback. On Sat, 3 Aug. 2019, 6:25 am Matt Riedemann, <mriedemos(a)gmail.com> wrote: > I wanted to send this to get other people's feedback if they have > particular nova configurations once they hit a certain scale (hundreds > or thousands of nodes). Every once in awhile in IRC I'll be chatting > with someone about configuration changes they've made running at large > scale to avoid, for example, hammering the control plane. I don't know > how many times I've thought, "it would be nice if we had a doc > highlighting some of these things so a new operator could come along > and see, oh I've never tried changing that value before". > > I haven't started that doc, but I've started a bug report for people > to dump some of their settings. The most common ones could go into a > simple admin doc to start. > > I know there is more I've thought about in the past that I don't have > in here but this is just a starting point so I don't make the mistake > of not taking action on this again. > > https://bugs.launchpad.net/nova/+bug/1838819 > > -- > > Thanks, > > Matt > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190803…> ------------------------------ Message: 2 Date: Thu, 1 Aug 2019 11:43:13 +0700 From: Vu Tan <vungoctan252(a)gmail.com> To: "Patil, Tushar" <Tushar.Patil(a)nttdata.com> Cc: Gaëtan Trellu <gaetan.trellu(a)incloudus.com>, "openstack-discuss(a)lists.openstack.org" <openstack-discuss(a)lists.openstack.org> Subject: Re: [masakari] how to install masakari on centos 7 Message-ID: <CACnQ=ZGFkWQ3G5rxYRCmqLQB-FvbaPutHXVb4AZrHCKp09LRsA(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi Patil, May I know how is it going ? On Tue, Jul 23, 2019 at 10:18 PM Vu Tan <vungoctan252(a)gmail.com> wrote: > Hi Patil, > Thank you for your reply, please instruct me if you successfully > install it. Thanks a lot > > On Tue, Jul 23, 2019 at 8:12 PM Patil, Tushar > <Tushar.Patil(a)nttdata.com> > wrote: > >> Hi Vu Tan, >> >> I'm trying to install Masakari using source code to reproduce the issue. >> If I hit the same issue as yours, I will troubleshoot this issue and >> let you know the solution or will update you what steps I have >> followed to bring up Masakari services successfully. >> >> Regards, >> Tushar Patil >> >> ________________________________________ >> From: Vu Tan <vungoctan252(a)gmail.com> >> Sent: Monday, July 22, 2019 12:33 PM >> To: Gaëtan Trellu >> Cc: Patil, Tushar; openstack-discuss(a)lists.openstack.org >> Subject: Re: [masakari] how to install masakari on centos 7 >> >> Hi Patil, >> May I know when the proper document for masakari is released ? I have >> configured conf file in controller and compute node, it seems running >> but it is not running as it should be, a lots of error in logs, here >> is a sample log: >> >> 2.7/site-packages/oslo_config/cfg.py:3024 >> 2019-07-19 10:25:26.360 7745 DEBUG oslo_service.service [-] bindir >> = /usr/local/bin log_opt_values /usr/lib/ >> python2.7/site-packages/oslo_config/cfg.py:3024 >> 2019-07-19 18:46:21.291 7770 ERROR masakari File >> "/usr/lib/python2.7/site-packages/oslo_service/service.py", line 65, >> in _is_daemo n >> 2019-07-19 18:46:21.291 7770 ERROR masakari is_daemon = os.getpgrp() >> != os.tcgetpgrp(sys.stdout.fileno()) >> 2019-07-19 18:46:21.291 7770 ERROR masakari OSError: [Errno 5] >> Input/output error >> 2019-07-19 18:46:21.291 7770 ERROR masakari >> 2019-07-19 18:46:21.300 7745 CRITICAL masakari [-] Unhandled error: >> OSError: [Errno 5] Input/output error >> 2019-07-19 18:46:21.300 7745 ERROR masakari Traceback (most recent >> call >> last): >> 2019-07-19 18:46:21.300 7745 ERROR masakari File >> "/usr/bin/masakari-api", line 10, in <module> >> >> I dont know if it is missing package or wrong configuration >> >> >> On Thu, Jul 11, 2019 at 6:14 PM Gaëtan Trellu < >> gaetan.trellu(a)incloudus.com<mailto:gaetan.trellu@incloudus.com>> wrote: >> You will have to enable the debit, debug = true and check the APi log. >> >> Did you try to use the openstack CLi ? >> >> Gaetan >> >> On Jul 11, 2019 12:32 AM, Vu Tan <vungoctan252(a)gmail.com<mailto: >> vungoctan252(a)gmail.com>> wrote: >> I know it's just a warning, just take a look at this image: >> [image.png] >> it's just hang there forever, and in the log show what I have shown >> to you >> >> On Wed, Jul 10, 2019 at 8:07 PM Gaëtan Trellu < >> gaetan.trellu(a)incloudus.com<mailto:gaetan.trellu@incloudus.com>> wrote: >> This is just a warning, not an error. >> >> On Jul 10, 2019 3:12 AM, Vu Tan <vungoctan252(a)gmail.com<mailto: >> vungoctan252(a)gmail.com>> wrote: >> Hi Gaetan, >> I follow you the guide you gave me, but the problem still persist, >> can you please take a look at my configuration to see what is wrong >> or what is missing in my config ? >> the error: >> 2019-07-10 14:08:46.876 17292 WARNING >> keystonemiddleware._common.config [-] The option "__file__" in conf >> is not known to auth_token >> 2019-07-10 14:08:46.876 17292 WARNING >> keystonemiddleware._common.config [-] The option "here" in conf is >> not known to auth_token >> 2019-07-10 14:08:46.882 17292 WARNING keystonemiddleware.auth_token >> [-] AuthToken middleware is set with keystone_authtoken.service_ >> >> the config: >> >> [DEFAULT] >> enabled_apis = masakari_api >> log_dir = /var/log/kolla/masakari >> state_path = /var/lib/masakari >> os_user_domain_name = default >> os_project_domain_name = default >> os_privileged_user_tenant = service >> os_privileged_user_auth_url = http://controller:5000/v3 >> os_privileged_user_name = nova os_privileged_user_password = P@ssword >> masakari_api_listen = controller masakari_api_listen_port = 15868 >> debug = False auth_strategy=keystone >> >> [wsgi] >> # The paste configuration file path >> api_paste_config = /etc/masakari/api-paste.ini >> >> [keystone_authtoken] >> www_authenticate_uri = http://controller:5000 auth_url = >> http://controller:5000 auth_type = password project_domain_id = >> default project_domain_name = default user_domain_name = default >> user_domain_id = default project_name = service username = masakari >> password = P@ssword region_name = RegionOne >> >> [oslo_middleware] >> enable_proxy_headers_parsing = True >> >> [database] >> connection = mysql+pymysql://masakari:P@ssword@controller/masakari >> >> >> >> On Tue, Jul 9, 2019 at 10:25 PM Vu Tan <vungoctan252(a)gmail.com<mailto: >> vungoctan252(a)gmail.com>> wrote: >> Thank Patil Tushar, I hope it will be available soon >> >> On Tue, Jul 9, 2019 at 8:18 AM Patil, Tushar >> <Tushar.Patil(a)nttdata.com <mailto:Tushar.Patil@nttdata.com>> wrote: >> Hi Vu and Gaetan, >> >> Gaetan, thank you for helping out Vu in setting up masakari-monitors >> service. >> >> As a masakari team ,we have noticed there is a need to add proper >> documentation to help the community run Masakari services in their >> environment. We are working on adding proper documentation in this 'Train' >> cycle. >> >> Will send an email on this mailing list once the patches are uploaded >> on the gerrit so that you can give your feedback on the same. >> >> If you have any trouble in setting up Masakari, please let us know on >> this mailing list or join the bi-weekly IRC Masakari meeting on the >> #openstack-meeting IRC channel. The next meeting will be held on 16th >> July >> 2019 @0400 UTC. >> >> Regards, >> Tushar Patil >> >> ________________________________________ >> From: Vu Tan <vungoctan252(a)gmail.com<mailto:vungoctan252@gmail.com>> >> Sent: Monday, July 8, 2019 11:21:16 PM >> To: Gaëtan Trellu >> Cc: openstack-discuss(a)lists.openstack.org<mailto: >> openstack-discuss(a)lists.openstack.org> >> Subject: Re: [masakari] how to install masakari on centos 7 >> >> Hi Gaetan, >> Thanks for pinpoint this out, silly me that did not notice the simple >> "error InterpreterNotFound: python3". Thanks a lot, I appreciate it >> >> On Mon, Jul 8, 2019 at 9:15 PM <gaetan.trellu(a)incloudus.com<mailto: >> gaetan.trellu(a)incloudus.com><mailto:gaetan.trellu@incloudus.com<mailto: >> gaetan.trellu(a)incloudus.com>>> wrote: >> Vu Tan, >> >> About "auth_token" error, you need "os_privileged_user_*" options >> into your masakari.conf for the API. >> As mentioned previously please have a look here to have an example of >> configuration working (for me at least): >> >> - masakari.conf: >> >> https://review.opendev.org/#/c/615715/42/ansible/roles/masakari/templ >> ates/masakari.conf.j2 >> - masakari-monitor.conf: >> >> https://review.opendev.org/#/c/615715/42/ansible/roles/masakari/templ >> ates/masakari-monitors.conf.j2 >> >> About your tox issue make sure you have Python3 installed. >> >> Gaëtan >> >> On 2019-07-08 06:08, Vu Tan wrote: >> >> > Hi Gaetan, >> > I try to generate config file by using this command tox -egenconfig >> > on top level of masakari but the output is error, is this masakari >> > still in beta version ? >> > [root@compute1 masakari-monitors]# tox -egenconfig genconfig >> > create: /root/masakari-monitors/.tox/genconfig >> > ERROR: InterpreterNotFound: python3 >> > _____________________________________________________________ >> > summary >> > ______________________________________________________________ >> > ERROR: genconfig: InterpreterNotFound: python3 >> > >> > On Mon, Jul 8, 2019 at 3:24 PM Vu Tan <vungoctan252(a)gmail.com<mailto: >> vungoctan252(a)gmail.com><mailto:vungoctan252@gmail.com<mailto: >> vungoctan252(a)gmail.com>>> wrote: >> > Hi, >> > Thanks a lot for your reply, I install pacemaker/corosync, >> > masakari-api, maskari-engine on controller node, and I run >> > masakari-api with this command: masakari-api, but I dont know >> > whether the process is running like that or is it just hang there, >> > here is what it shows when I run the command, I leave it there for >> > a while but it does not change anything : >> > [root@controller masakari]# masakari-api >> > 2019-07-08 15:21:09.946 30250 INFO masakari.api.openstack [-] >> > Loaded >> > extensions: ['extensions', 'notifications', 'os-hosts', 'segments', >> > 'versions'] >> > 2019-07-08 15:21:09.955 30250 WARNING >> > keystonemiddleware._common.config [-] The option "__file__" in conf >> > is not known to auth_token >> > 2019-07-08 15:21:09.955 30250 WARNING >> > keystonemiddleware._common.config [-] The option "here" in conf is >> > not known to auth_token >> > 2019-07-08 15:21:09.960 30250 WARNING keystonemiddleware.auth_token >> > [-] AuthToken middleware is set with >> > keystone_authtoken.service_token_roles_required set to False. This >> > is backwards compatible but deprecated behaviour. Please set this to True. >> > 2019-07-08 15:21:09.974 30250 INFO masakari.wsgi [-] masakari_api >> > listening on 127.0.0.1:15868<http://127.0.0.1:15868>< >> http://127.0.0.1:15868> >> > 2019-07-08 15:21:09.975 30250 INFO oslo_service.service [-] >> > Starting 4 workers >> > 2019-07-08 15:21:09.984 30274 INFO >> > masakari.masakari_api.wsgi.server [-] (30274) wsgi starting up on >> > http://127.0.0.1:15868 >> > 2019-07-08 15:21:09.985 30275 INFO >> > masakari.masakari_api.wsgi.server [-] (30275) wsgi starting up on >> > http://127.0.0.1:15868 >> > 2019-07-08 15:21:09.992 30277 INFO >> > masakari.masakari_api.wsgi.server [-] (30277) wsgi starting up on >> > http://127.0.0.1:15868 >> > 2019-07-08 15:21:09.994 30276 INFO >> > masakari.masakari_api.wsgi.server [-] (30276) wsgi starting up on >> > http://127.0.0.1:15868 >> > >> > On Sun, Jul 7, 2019 at 7:37 PM Gaëtan Trellu >> ><gaetan.trellu(a)incloudus.com<mailto:gaetan.trellu@incloudus.com >> ><mailto:gaetan.trellu@incloudus.com<mailto:gaetan.trellu@incloudus.c >> >om>>> >> wrote: >> > >> > Hi Vu Tan, >> > >> > Masakari documentation doesn't really exist... I had to figured >> > some stuff by myself to make it works into Kolla project. >> > >> > On controller nodes you need: >> > >> > - pacemaker >> > - corosync >> > - masakari-api (openstack/masakari repository) >> > - masakari- engine (openstack/masakari repository) >> > >> > On compute nodes you need: >> > >> > - pacemaker-remote (integrated to pacemaker cluster as a resource) >> > - masakari- hostmonitor (openstack/masakari-monitor repository) >> > - masakari-instancemonitor (openstack/masakari-monitor repository) >> > - masakari-processmonitor (openstack/masakari-monitor repository) >> > >> > For masakari-hostmonitor, the service needs to have access to >> > systemctl command (make sure you are not using sysvinit). >> > >> > For masakari-monitor, the masakari-monitor.conf is a bit different, >> > you will have to configure the [api] section properly. >> > >> > RabbitMQ needs to be configured (as transport_url) on masakari-api >> > and masakari-engine too. >> > >> > Please check this review[1], you will have masakari.conf and >> > masakari-monitor.conf configuration examples. >> > >> > [1] https://review.opendev.org/#/c/615715 >> > >> > Gaëtan >> > >> > On Jul 7, 2019 12:08 AM, Vu Tan <vungoctan252(a)gmail.com<mailto: >> vungoctan252(a)gmail.com><mailto:vungoctan252@gmail.com<mailto: >> vungoctan252(a)gmail.com>>> wrote: >> > >> > VU TAN <VUNGOCTAN252(a)GMAIL.COM<mailto:VUNGOCTAN252@GMAIL.COM><mailto: >> VUNGOCTAN252(a)GMAIL.COM<mailto:VUNGOCTAN252@GMAIL.COM>>> >> > >> > 10:30 AM (35 minutes ago) >> > >> > to openstack-discuss >> > >> > Sorry, I resend this email because I realized that I lacked of >> > prefix on this email's subject >> > >> > Hi, >> > >> > I would like to use Masakari and I'm having trouble finding a step >> > by step or other documentation to get started with. Which part >> > should be installed on controller, which is should be on compute, >> > and what is the prerequisite to install masakari, I have installed >> > corosync and pacemaker on compute and controller nodes, , what else >> > do I need to do ? step I have done so far: >> > - installed corosync/pacemaker >> > - install masakari on compute node on this github repo: >> > https://github.com/openstack/masakari >> > - add masakari in to mariadb >> > here is my configuration file of masakari.conf, do you mind to take >> > a look at it, if I have misconfigured anything? >> > >> > [DEFAULT] >> > enabled_apis = masakari_api >> > >> > # Enable to specify listening IP other than default >> > masakari_api_listen = controller # Enable to specify port other >> > than default masakari_api_listen_port = 15868 debug = False >> > auth_strategy=keystone >> > >> > [wsgi] >> > # The paste configuration file path api_paste_config = >> > /etc/masakari/api-paste.ini >> > >> > [keystone_authtoken] >> > www_authenticate_uri = http://controller:5000 auth_url = >> > http://controller:5000 auth_type = password project_domain_id = >> > default user_domain_id = default project_name = service username = >> > masakari password = P@ssword >> > >> > [database] >> > connection = mysql+pymysql://masakari:P@ssword@controller/masakari >> 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. >> >> >> 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 -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190801…> ------------------------------ Subject: Digest Footer _______________________________________________ openstack-discuss mailing list openstack-discuss(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss ------------------------------ End of openstack-discuss Digest, Vol 10, Issue 13 ************************************************* 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 -------------- An embedded and charset-unspecified text was scrubbed... Name: detailed_steps_to_install_masakari.txt URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190819…> ------------------------------ Subject: Digest Footer _______________________________________________ openstack-discuss mailing list openstack-discuss(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss ------------------------------ End of openstack-discuss Digest, Vol 10, Issue 95 ************************************************* 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.

1 0

Re: [keystone][horizon] Integration with GuardianKey
by Paulo Angelo 20 Aug '19

20 Aug '19

> > > > We are trying to integrate OpenStack (Horizon or Keystone) with > > > GuardianKey. However, we have doubts related to the best way to do > this > > > and the best point in the code for this integration. > > > > > > > > > GuardianKey is a solution to protect systems against authentication > > > attacks. It uses Machine Learning and analyses the user's behavior, > > > threat intelligence and psychometrics (or behavioral biometrics). The > > > protected system (in the concrete case, OpenStack admin interface) > must > > > send an event via REST for the GuardianKey on each login attempt. More > > > info at https://guardiankey.io <https://guardiankey.io>. > > > > > > The best way to integrate would be on having a hook in the procedure > > > that process the user credentials submission in OpenStack (the script > > > that receives the POST), something such as: > > > > > > > > > if(<POST IN AUTH FORM>) { > > > boolean loginFailed = checkLogin(); > > > GuardianKeyEvent event = > createEventForGuardianKey(username,loginFailed); > > > boolean GuardianKeyValidation = checkGuardianKeyViaREST(event); > > > if(GuardianKeyValidation){ > > > // Allow access > > > } else { > > > // Deny access > > > } > > > } > > > > > > Where is the best place to create this integration? Horizon or > Keystone? > > > Is there a way to create a hook for this purpose? Should we create an > > > extension? > > Keystone would be the best place for this. Horizon is only one way a user > can log in to OpenStack, so hooking into Horizon would not cover your > attack vector. Keystone has a built-in auditing system specifically for > this, using CADF notifications to emit events when a user logs in: > > https://docs.openstack.org/keystone/latest/admin/event_notifications.html > > All you need to do is create a consumer for those notifications. > > Colleen > Thank you, Colleen, for your message. These days, I spent some time on it to understand better about the OpenStack events. As I could see, the authentication event does not have the user login name and other useful user information, such as e-mail. Is there a way to retrieve this information using the OpenStack resources? Or the best way is to access directly the database? Another question: We will need to deny the access if GuardianKey identifies a high attack risk. In this case, is there an easy way to drop a user session using the Keystone API or resources (and the information in the event)? Finally, you mentioned about the consumer. Is this a consumer for a RabbitMQ queue or an OpenStack API consumer? In the last case, is there example code for this? Thank you in advance. Regards, Paulo Angelo

1 0

Heat Template
by mesut aygün 19 Aug '19

19 Aug '19

Hi everyone; I am writing the template for cluster but i cant inject the cloud-init data. How can I inject the password data for vm? heat_template_version: 2014-10-16 new_instance: type: OS::Nova::Server properties: key_name: { get_param: key_name } image: { get_param: image_id } flavor: bir name: str_replace: template: master-$NONCE-dmind params: $NONCE: { get_resource: name_nonce } user_data: | #!/bin/bash #cloud-config password: 724365 echo "Running boot script" >> /home/ubuntu/test sudo sed -i "/^[^#]*PasswordAuthentication[[:space:]]no/c\PasswordAuthentication yes" /etc/ssh/sshd_config sudo useradd -d /home/mesut -m mesut sudo usermod --password 724365 ubuntu /etc/init.d/ssh restart

2 1

[neutron] Bug Deputy Report August 12-19
by Ryan Tidwell 19 Aug '19

19 Aug '19

Hello Neutron Team, Here is my bug deputy report for August 12 - August 19: Medium: -[OVS agent] Physical bridges can't be initialized if there is no connectivity to rabbitmq https://bugs.launchpad.net/neutron/+bug/1840443 The fix for this has been merged and a number of backports have merged as well. It appears to have been handled by the team. - excessive number of dvrs where vm got a fixed ip on floating network https://bugs.launchpad.net/bugs/1840579 https://review.opendev.org/#/c/677092/ has been proposed and is being worked on. This appears to be related to how we determine whether to instantiate a DVR local router on a compute node. It looks like there is a case where we create a local router when it's not necessary, thereby consuming too many IP's on the floating IP network at scale. Undecided: - network/subnet resources cannot be read and written separated https://bugs.launchpad.net/neutron/+bug/1840638 https://review.opendev.org/#/c/677166/ has been proposed. This was just reported just a few hours ago and still needs some triage to confirm severity of the issue. RFE's: - [RFE] Add new config option to enable IGMP snooping in ovs https://bugs.launchpad.net/bugs/1840136 Regards, Ryan Tidwell

1 0

[neutron] Bug Deputy Report August 12 - August 19
by Ryan Tidwell 19 Aug '19

19 Aug '19

Hello Neutron Team, Here is my bug deputy report for August 12 - August 19: Medium: -[OVS agent] Physical bridges can't be initialized if there is no connectivity to rabbitmq https://bugs.launchpad.net/neutron/+bug/1840443 The fix for this has been merged and a number of backports have merged as well. It appears to have been handled by the team. - excessive number of dvrs where vm got a fixed ip on floating network https://bugs.launchpad.net/bugs/1840579 https://review.opendev.org/#/c/677092/ has been proposed and is being worked on. This appears to be related to how we determine whether to instantiate a DVR local router on a compute node. It looks like there is a case where we create a local router when it's not necessary, thereby consuming too many IP's on the floating IP network at scale. Undecided: - network/subnet resources cannot be read and written separated https://bugs.launchpad.net/neutron/+bug/1840638 https://review.opendev.org/#/c/677166/ has been proposed. This was just reported just a few hours ago and still needs some triage to confirm severity of the issue. RFE's: - [RFE] Add new config option to enable IGMP snooping in ovs https://bugs.launchpad.net/neutron/+bug/1840136 Regards, Ryan Tidwell

1 0