Hi Zhiyuan, Thank you very much, I'll join the next meeting!
Meher Message: 3 Date: Thu, 17 Aug 2017 12:26:06 +0000 From: Vega Cai <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: Re: [openstack-dev] [tricircle-Service Function Chaining] Message-ID: <CAN33iACT-=gko2kxnspqw_pszhdmt6el9tznd9dintwhp9y...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi Meher, The document structure of networking-sfc has been changed so the link in the guide is not accurate. Since you have already deployed Tricircle and would like to enable service function chaining feature, I think you can refer to these guides[1, 2] to setup local Neutron server. The configuration for local Neutron server is /etc/neutron/neutron.conf and /etc/neutron/plugins/ml2/ml2_conf.ini for the DevStack setup. And /etc/neutron/neutron.conf.0 is the configuration file for central Neutron server. BTW, would you like to join our weekly meeting? The current time(9:00 am UTC+8 on Wednesday) may not be suitable for you, but we can figure out a proper time and rearrange the meeting. [1] https://docs.openstack.org/networking-sfc/latest/install/install.html [2] https://docs.openstack.org/networking-sfc/latest/install/configuration.html BR Zhiyuan On Thu, 17 Aug 2017 at 18:10 <[email protected]> wrote: > Hello to all the community of Tricircle, > > > > I deployed Tricircle according to the architecture proposed by "Multi-pod > Installation with DevStack". Now I'm trying to apply the "Networking Guide" > tutorial and more specifically "Service Function Chaining Guide". Indeed, I > find that the configuration is somewhat ambiguous with regard to the > configuration of local neutron. > > > > I thank you in advance for helping me on this by a more detailed > explanation. Have a great day! > > > > Best regards, > > > > Meher > > > > [image: Logo Orange] <http://www.orange.com/> > > > > *Meher Hihi * > Intern > ORANGE/IMT/OLN/WTC/CMA/MAX > > Fixe : +33 2 96 07 03 71 > <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33296070371> > Mobile : +33 7 58 38 68 87 > <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33758386887> > [email protected] > > > > > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- BR Zhiyuan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170817/cc9fbc13/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 605 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170817/cc9fbc13/attachment-0002.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 605 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170817/cc9fbc13/attachment-0003.png> ------------------------------ Message: 4 Date: Thu, 17 Aug 2017 14:40:20 +0200 From: Thierry Carrez <[email protected]> To: [email protected] Subject: Re: [openstack-dev] [oslo][oslo.config][ansible][tripleo][kolla][ptg] Pluggable drivers and protect plaintext secrets Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8 Raildo Mascena de Sousa Filho wrote: > Hi all, > > Should we reserve a room in the extra session ethercalc [0 > <%20https://ethercalc.openstack.org/Queens-PTG-Discussion-Rooms%20>] or > we already have a time slot scheduled for that discussion? > > [0] https://ethercalc.openstack.org/Queens-PTG-Discussion-Rooms It feels like this discussion could be scheduled in the Oslo room as well. I guess it depends whether you need extra room :) -- Thierry Carrez (ttx) ------------------------------ Message: 5 Date: Thu, 17 Aug 2017 15:08:58 +0200 From: Markus Zoeller <[email protected]> To: [email protected] Subject: Re: [openstack-dev] [tripleo] Proposal to require bugs for tech debt Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8 On 16.08.2017 18:40, Alex Schultz wrote: > On Wed, Aug 16, 2017 at 8:24 AM, Markus Zoeller > <[email protected]> wrote: >> On 16.08.2017 02:59, Emilien Macchi wrote: >>> On Tue, Aug 15, 2017 at 5:46 PM, Alex Schultz <[email protected]> wrote: >>>> Hey folks, >>>> >>>> I'm proposing that in order to track tech debt that we're adding in as >>>> part of development that we create a way to track these items and not >>>> approve them without a bug (and a reference to said bug)[0]. Please >>>> take a moment to review the proposed policy and comment. I would like >>>> to start this for the queens cycle. >>> >>> I also think we should frequently review the status of these bugs. >>> Maybe unofficially from time to time and officially during milestone-3 >>> of each cycle. >>> >>> I like the proposal so far, thanks. >>> >> >> FWIW, for another (in-house) project, I create a page called "technical >> debt" in the normal docs directory of the project. That way, I can add >> the "reminder" with the same commit which introduced the technical debt >> in the code. Similar to what OpenStack already does with the >> release-notes. The list of technical debt items is then always visible >> in the docs and not a query in the bug-tracker with tags (or something >> like that). >> Just an idea, maybe it applicable here. >> > > Yea that would a good choice if we only had a single or a low number > of projects under the tripleo umbrella. The problem is we have many > different components which contribute to tech debt so storing it in > each repo would be hard to track. I proposed bugs because it would be > a singular place for reporting. For projects with fewer deliverable > storing it like release notes is a good option. > > Thanks, > -Alex > No biggie. A single project was my implicit assumption, that's true. Wish you good luck. -- Regards, Markus Zoeller (markus_z) >> -- >> Regards, Markus Zoeller (markus_z) >> >>>> A real world example of where this would beneficial would be the >>>> workaround we had for buggy ssh[1]. This patch was merged 6 months ago >>>> to work around an issue in ssh that was recently fixed. However we >>>> would most likely never have remembered to revert this. It was only >>>> because someone[2] spotted it and mentioned it that it is being >>>> reverted now. >>>> >>>> Thanks, >>>> -Alex >>>> >>>> [0] https://review.openstack.org/#/c/494044/ >>>> [1] >>>> https://review.openstack.org/#/q/6e8e27488da31b3b282fe1ce5e07939b3fa11b2f,n,z >>>> [2] Thanks pabelanger >>>> ------------------------------ Message: 6 Date: Mon, 14 Aug 2017 09:34:51 +0300 (EET) From: Gökhan IŞIK (BİLGEM BTE) <[email protected]> To: Julien Danjou <[email protected]> Cc: [email protected] Subject: Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Hi Julien, We developed the monitor dashboard to use it on our private cloud in the first place. We have Mitaka release and we use MongoDB with Ceilometer. But you are right, we can update the api to use Gnocchi. This release currently supports one day monitoring, when we add Gnocchi api support we can add weekly and monthly monitoring options. Thanks. ----- Orijinal Mesaj ----- Kimden: "Julien Danjou" <[email protected]> Kime: "Gökhan IŞIK (BİLGEM BTE)" <[email protected]> Kk: [email protected] Gönderilenler: 11 Ağustos Cuma 2017 15:29:17 Konu: Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon On Tue, Aug 01 2017, Gökhan IŞIK (BİLGEM BTE) wrote: Hi, > We are happy to share with you that we developed an AngularJS based usage > monitoring panel for Horizon. > The panel visualizes the collected utilization data by Ceilometer. > > Source code is now available on github [1]. > > The plugin consists of 3 panels; a monitoring panel for users, a project > monitoring panel and a hypervisor monitoring panel for admins. > > A user can display utilization charts for the current project's instances, > export the metrics in csv format and launch alarms using the dashboard. > We have another service to capture these alarms and send notification e-mails > to the cloud users which is also available on github.com/b3lab. > An admin can display projects' utilization charts, export the metrics in csv > format in Project Monitor panel. And the Hypervisor Monitor panel is to > visualize SNMP based metrics collected from hypervisors. > > We are currently improving some features. > > Some screenshots published at our website [2]. We also uploaded two videos > showing some features of the plugin [3][4]. > > All comments and ideas are welcome! Did you build all of this against the deprecated Ceilometer API rather than Gnocchi? :( -- Julien Danjou ;; Free Software hacker ;; https://julien.danjou.info -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170814/4dd2fd36/attachment-0003.html> ------------------------------ Message: 7 Date: Wed, 16 Aug 2017 16:57:25 +0300 (EET) From: Gökhan IŞIK (BİLGEM BTE) <[email protected]> To: Julien Danjou <[email protected]> Cc: [email protected] Subject: Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Hi Julien, We developed the monitor dashboard to use it on our private cloud in the first place. We have Mitaka release and we use MongoDB with Ceilometer. But you are right, we can update the api to use Gnocchi. This release currently supports one day monitoring, when we add Gnocchi api support we can add weekly and monthly monitoring options. Thanks. ----- Orijinal Mesaj ----- Kimden: "Gökhan IŞIK (BİLGEM BTE)" <[email protected]> Kime: "Julien Danjou" <[email protected]> Kk: [email protected] Gönderilenler: 14 Ağustos Pazartesi 2017 9:34:51 Konu: Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon Hi Julien, We developed the monitor dashboard to use it on our private cloud in the first place. We have Mitaka release and we use MongoDB with Ceilometer. But you are right, we can update the api to use Gnocchi. This release currently supports one day monitoring, when we add Gnocchi api support we can add weekly and monthly monitoring options. Thanks. ----- Orijinal Mesaj ----- Kimden: "Julien Danjou" <[email protected]> Kime: "Gökhan IŞIK (BİLGEM BTE)" <[email protected]> Kk: [email protected] Gönderilenler: 11 Ağustos Cuma 2017 15:29:17 Konu: Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon On Tue, Aug 01 2017, Gökhan IŞIK (BİLGEM BTE) wrote: Hi, > We are happy to share with you that we developed an AngularJS based usage > monitoring panel for Horizon. > The panel visualizes the collected utilization data by Ceilometer. > > Source code is now available on github [1]. > > The plugin consists of 3 panels; a monitoring panel for users, a project > monitoring panel and a hypervisor monitoring panel for admins. > > A user can display utilization charts for the current project's instances, > export the metrics in csv format and launch alarms using the dashboard. > We have another service to capture these alarms and send notification e-mails > to the cloud users which is also available on github.com/b3lab. > An admin can display projects' utilization charts, export the metrics in csv > format in Project Monitor panel. And the Hypervisor Monitor panel is to > visualize SNMP based metrics collected from hypervisors. > > We are currently improving some features. > > Some screenshots published at our website [2]. We also uploaded two videos > showing some features of the plugin [3][4]. > > All comments and ideas are welcome! Did you build all of this against the deprecated Ceilometer API rather than Gnocchi? :( -- Julien Danjou ;; Free Software hacker ;; https://julien.danjou.info -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170816/c3874471/attachment-0006.html> ------------------------------ Message: 8 Date: Tue, 1 Aug 2017 16:10:04 +0300 (EET) From: Gökhan IŞIK (BİLGEM BTE) <[email protected]> To: [email protected] Cc: Esra Celik <[email protected]> Subject: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Hi all, We are happy to share with you that we developed an AngularJS based usage monitoring panel for Horizon. The panel visualizes the collected utilization data by Ceilometer. Source code is now available on github [1]. The plugin consists of 3 panels; a monitoring panel for users, a project monitoring panel and a hypervisor monitoring panel for admins. A user can display utilization charts for the current project's instances, export the metrics in csv format and launch alarms using the dashboard. We have another service to capture these alarms and send notification e-mails to the cloud users which is also available on github.com/b3lab. An admin can display projects' utilization charts, export the metrics in csv format in Project Monitor panel. And the Hypervisor Monitor panel is to visualize SNMP based metrics collected from hypervisors. We are currently improving some features. Some screenshots published at our website [2]. We also uploaded two videos showing some features of the plugin [3][4]. All comments and ideas are welcome! [1] https://github.com/b3lab/safir_monitor_dashboard [2] https://www.b3lab.org/safir-monitor-dashboard-github-uzerinde-yayinlandi/ [3] https://www.youtube.com/watch?v=mAKU20b65Ug [4] https://www.youtube.com/watch?v=kllf4s2qutg Gökhan Işık TÜBİTAK BİLGEM B3LAB -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170801/0fb6c3c8/attachment-0003.html> ------------------------------ Message: 9 Date: Wed, 16 Aug 2017 16:57:25 +0300 (EET) From: Gökhan IŞIK (BİLGEM BTE) <[email protected]> To: Julien Danjou <[email protected]> Cc: [email protected] Subject: Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Hi Julien, We developed the monitor dashboard to use it on our private cloud in the first place. We have Mitaka release and we use MongoDB with Ceilometer. But you are right, we can update the api to use Gnocchi. This release currently supports one day monitoring, when we add Gnocchi api support we can add weekly and monthly monitoring options. Thanks. ----- Orijinal Mesaj ----- Kimden: "Gökhan IŞIK (BİLGEM BTE)" <[email protected]> Kime: "Julien Danjou" <[email protected]> Kk: [email protected] Gönderilenler: 14 Ağustos Pazartesi 2017 9:34:51 Konu: Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon Hi Julien, We developed the monitor dashboard to use it on our private cloud in the first place. We have Mitaka release and we use MongoDB with Ceilometer. But you are right, we can update the api to use Gnocchi. This release currently supports one day monitoring, when we add Gnocchi api support we can add weekly and monthly monitoring options. Thanks. ----- Orijinal Mesaj ----- Kimden: "Julien Danjou" <[email protected]> Kime: "Gökhan IŞIK (BİLGEM BTE)" <[email protected]> Kk: [email protected] Gönderilenler: 11 Ağustos Cuma 2017 15:29:17 Konu: Re: [openstack-dev] [horizon] A Monitoring panel plugin for Horizon On Tue, Aug 01 2017, Gökhan IŞIK (BİLGEM BTE) wrote: Hi, > We are happy to share with you that we developed an AngularJS based usage > monitoring panel for Horizon. > The panel visualizes the collected utilization data by Ceilometer. > > Source code is now available on github [1]. > > The plugin consists of 3 panels; a monitoring panel for users, a project > monitoring panel and a hypervisor monitoring panel for admins. > > A user can display utilization charts for the current project's instances, > export the metrics in csv format and launch alarms using the dashboard. > We have another service to capture these alarms and send notification e-mails > to the cloud users which is also available on github.com/b3lab. > An admin can display projects' utilization charts, export the metrics in csv > format in Project Monitor panel. And the Hypervisor Monitor panel is to > visualize SNMP based metrics collected from hypervisors. > > We are currently improving some features. > > Some screenshots published at our website [2]. We also uploaded two videos > showing some features of the plugin [3][4]. > > All comments and ideas are welcome! Did you build all of this against the deprecated Ceilometer API rather than Gnocchi? :( -- Julien Danjou ;; Free Software hacker ;; https://julien.danjou.info -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170816/c3874471/attachment-0007.html> ------------------------------ Message: 10 Date: Thu, 17 Aug 2017 14:09:02 +0000 From: Raildo Mascena de Sousa Filho <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: Re: [openstack-dev] [oslo][oslo.config][ansible][tripleo][kolla][ptg] Pluggable drivers and protect plaintext secrets Message-ID: <CANSb5mZ8XxTDknQapvoJKLhbzXyB2jzG4=hlgqixoginvhq...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Well, it was the first option but unfortunately, Doug doesn't have any free time slot on those days, so we have to postpone that discussion to the end of the week. On Thu, Aug 17, 2017 at 9:41 AM Thierry Carrez <[email protected]> wrote: > Raildo Mascena de Sousa Filho wrote: > > Hi all, > > > > Should we reserve a room in the extra session ethercalc [0 > > <%20https://ethercalc.openstack.org/Queens-PTG-Discussion-Rooms%20>] or > > we already have a time slot scheduled for that discussion? > > > > [0] https://ethercalc.openstack.org/Queens-PTG-Discussion-Rooms > > It feels like this discussion could be scheduled in the Oslo room as > well. I guess it depends whether you need extra room :) > > -- > Thierry Carrez (ttx) > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Raildo mascena Software Engineer, Identity Managment Red Hat <https://www.redhat.com> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170817/53bcfd74/attachment-0001.html> ------------------------------ Message: 11 Date: Thu, 17 Aug 2017 07:30:27 -0700 From: Emilien Macchi <[email protected]> To: OpenStack Development Mailing List <[email protected]> Subject: [openstack-dev] [kolla] [tripleo] [openstack-ansible] [deployment] Collaboration at PTG Message-ID: <CACu=hytF2CcEFJV0xP=ZiDPRjJ_7HS=7oik++jhjlhyokae...@mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hey folks, As usual, we'll meet in Denver and I hope we can spend some time together (in a meeting room first) to have face to face discussions on the recent topics that we had. Right now, TripleO sessions are not scheduled in our agenda, so we're pretty flexible: https://etherpad.openstack.org/p/tripleo-ptg-queens I would like to propose one topic (happy to coordinate the discussion) on some efforts regarding doing configuration management with Ansible, and k8s integration as well. Flavio made some progress [1] - I really hope we can make progress here. [1] http://lists.openstack.org/pipermail/openstack-dev/2017-July/119696.html If you're working on Kolla / OpenStack-Ansible - please let us know if you have specific constraints on the schedule, so we can maybe block a timeslot in the agenda from now. We'll have a "Packaging" room which is reserved for all topics related to OpenStack deployments, so we can use this one. Looking forward to meeting you at PTG! Thanks, -- Emilien Macchi ------------------------------ Message: 12 Date: Thu, 17 Aug 2017 23:56:31 +0900 From: Akihiro Motoki <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: Re: [openstack-dev] [all] Secrets of edit-constraints Message-ID: <calhu9tk_c1k7g3e8duzecdf7lhlkmqh8ar-j0t3um8s9pd7...@mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Thanks Tony for the confirmation. We have various variants of tox_install.sh. I just wondered we need to fix it globally or it depends on someone's development environment. Anyway we can improve tox_install.sh for more general way :) Thanks, Akihiro 2017-08-16 18:14 GMT+09:00 Tony Breeds <[email protected]>: > On Mon, Aug 14, 2017 at 08:36:33AM +0000, Csatari, Gergely (Nokia - > HU/Budapest) wrote: >> Hi, >> >> I have an interesting situation with the parametrization of edit-constraints >> in tools/tox_install.sh. This happens at the moment in neutron-lib, but as >> amotoki pointed out in [1] the same should happen in any projects (and >> actually was happening with me in Vitrage and Mistral). >> >> Here is what I experience: >> With the current parameters of edit-constraints (edit-constraints $localfile >> -- $LIB_NAME "-e file://$PWD#egg=$LIB_NAME") the library itself (neutron-lib >> in this case) is added to upper-constraints.txt and the installation fails >> with "Could not satisfy constraints for 'neutron-lib': installation from >> path or url cannot be constrained to a version". >> If I modify the parameters of edit-constraints in a way that it removes the >> library (neutron-lib in this case) instead of adding (edit-constraints >> $localfile $LIB_NAME --) it my build succeeds (as I'm playing with api-ref I >> use tox -r -e api-ref, but the same also happens with tox -r -e pep8). >> >> Is this happening with only me? > > No using edit-constraints to remove an item from the constrained set so > you can use the current developement (git SHA) is the right things to > do. > > Many of the project in the scenario you're describing do just that. > > Yours Tony. > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ------------------------------ Message: 13 Date: Thu, 17 Aug 2017 07:58:37 -0700 From: Emilien Macchi <[email protected]> To: OpenStack Development Mailing List <[email protected]> Subject: Re: [openstack-dev] [tripleo] pike-3 released - now focusing on pike-rc1 Message-ID: <CACu=hyvrhg4oxnjrzgpegyfcouvdevt5waelhzkc75+xmpo...@mail.gmail.com> Content-Type: text/plain; charset="UTF-8" On Mon, Jul 31, 2017 at 7:26 AM, Emilien Macchi <[email protected]> wrote: > ## This week until August 28th > Preparing RC & final releases. > Feature & CI freeze just started. > During this time, folks should focus on upgrades from Ocata to Pike, > fixing bugs [1]. > Please do the FFE (including CI changes) requests on openstack-dev [tripleo]. We'll tag TripleO Pike RC1 on R+O during the week of Aug 28 - Sep 01. We still have some patches that we need in master and the CI efforts are still ongoing to validate Pike release, so it doesn't make sense for us to branch now. We'll probably tag final Pike 2 weeks. If there is any thought or question, please let us know. -- Emilien Macchi ------------------------------ Message: 14 Date: Thu, 17 Aug 2017 17:04:01 +0200 From: Flavio Percoco <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: Re: [openstack-dev] [kolla] [tripleo] [openstack-ansible] [deployment] Collaboration at PTG Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8"; Format="flowed" On 17/08/17 07:30 -0700, Emilien Macchi wrote: >Hey folks, > >As usual, we'll meet in Denver and I hope we can spend some time >together (in a meeting room first) to have face to face discussions on >the recent topics that we had. >Right now, TripleO sessions are not scheduled in our agenda, so we're >pretty flexible: https://etherpad.openstack.org/p/tripleo-ptg-queens > >I would like to propose one topic (happy to coordinate the discussion) >on some efforts regarding doing configuration management with Ansible, >and k8s integration as well. >Flavio made some progress [1] - I really hope we can make progress here. > >[1] http://lists.openstack.org/pipermail/openstack-dev/2017-July/119696.html > >If you're working on Kolla / OpenStack-Ansible - please let us know if >you have specific constraints on the schedule, so we can maybe block a >timeslot in the agenda from now. >We'll have a "Packaging" room which is reserved for all topics related >to OpenStack deployments, so we can use this one. > >Looking forward to meeting you at PTG! >Thanks, Just want to raise my hand to help driving some of these conversations. I'd love to see some sessions around collaborating with other teams. Some ideas that we've discussed in the past could use some more discussions. For example: - Configuration management - Sharing playbooks with kolla - Kubernetes based jobs - What's there? - What can be shared? Going to add these points to the etherpad, Flavio -- @flaper87 Flavio Percoco -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 862 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170817/c92ce8ad/attachment-0001.sig> ------------------------------ Message: 15 Date: Thu, 17 Aug 2017 10:24:13 -0500 From: Major Hayden <[email protected]> To: [email protected] Subject: Re: [openstack-dev] [kolla] [tripleo] [openstack-ansible] [deployment] Collaboration at PTG Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8 On 08/17/2017 09:30 AM, Emilien Macchi wrote: > If you're working on Kolla / OpenStack-Ansible - please let us know if > you have specific constraints on the schedule, so we can maybe block a > timeslot in the agenda from now. > We'll have a "Packaging" room which is reserved for all topics related > to OpenStack deployments, so we can use this one. I don't have any constraints (that I'm aware of), but I'd be interested in participating! Performance in the gate jobs has been one of my tasks lately and I'd like to see if we can collaborate there to make improvements without ruining infra's day. ;) As long as you can put up with a few Dad jokes, I'll be there. -- Major Hayden ------------------------------ Message: 16 Date: Thu, 17 Aug 2017 10:32:22 -0500 From: Sean McGinnis <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: Re: [openstack-dev] [all][elections] Project Team Lead Election Conclusion and Results Message-ID: <20170817153220.GA20230@sm-xps> Content-Type: text/plain; charset=us-ascii > > Elections: > * Documentation: > http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_d5d9fb5a2354e2a0 > * Ironic: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_0fb06bb4edfd3d08 > Election process details and results are also available here: > https://governance.openstack.org/election/ > > Thank you to all involved in the PTL election process, > > - Kendall Nelson(diablo_rojo) Thank you to our election officials for running a smooth election! ------------------------------ Message: 17 Date: Thu, 17 Aug 2017 12:36:12 -0400 From: Brian Rosmaita <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: [openstack-dev] [glance] priorities for THURSDAY (17 aug) and FRIDAY (18 aug) Message-ID: <cafnespr8mu_oisinqys5mjxtovoynes-cmxfpvpunlgftg5...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Glancers (and other people interested in the Pike release of Glance), We need a RC-2, and the sooner we can release it, the better. So we really need a review push today and tomorrow. Glance cores: please direct your attention to the patches listed on this etherpad: https://etherpad.openstack.org/p/glance-pike-RC-critical They are mostly related to the new interoperable image import functionality. Abhishek and I can only +2 each others work, and Erno is on a well-deserved vacation, so we need some more eyes on those patches. Even if you're not a glance core, your careful review on these patches will be helpful. thanks, brian -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170817/5b785e8d/attachment-0001.html> ------------------------------ Message: 18 Date: Thu, 17 Aug 2017 18:36:25 +0200 From: Jiří Stránský <[email protected]> To: [email protected] Subject: Re: [openstack-dev] [tripleo] critical situation with CI / upgrade jobs Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8; format=flowed On 17.8.2017 00:47, Emilien Macchi wrote: > Here's an update on the situation. > > On Tue, Aug 15, 2017 at 6:33 PM, Emilien Macchi <[email protected]> wrote: >> Problem #1: Upgrade jobs timeout from Newton to Ocata >> https://bugs.launchpad.net/tripleo/+bug/1702955 > [...] > > - revert distgit patch in RDO: https://review.rdoproject.org/r/8575 > - push https://review.openstack.org/#/c/494334/ as a temporary solution > - we need https://review.openstack.org/#/c/489874/ landed ASAP. > - once https://review.openstack.org/#/c/489874/ is landed, we need to > revert https://review.openstack.org/#/c/494334 ASAP. > > We still need some help to find out why upgrade jobs timeout so much > in stable/ocata. > >> Problem #2: from Ocata to Pike (containerized) missing container upload step >> https://bugs.launchpad.net/tripleo/+bug/1710938 >> Wes has a patch (thanks!) that is currently in the gate: >> https://review.openstack.org/#/c/493972 > [...] > > The patch worked and helped! We've got a successful job running today: > http://logs.openstack.org/00/461000/32/check/gate-tripleo-ci-centos-7-containers-multinode-upgrades-nv/2f13627/console.html#_2017-08-16_01_31_32_009061 > > We're now pushing to the next step: testing the upgrade with pingtest. > See https://review.openstack.org/#/c/494268/ and the Depends-On: on > https://review.openstack.org/#/c/461000/. > > If pingtest proves to work, it would be a good news and prove that we > have a basic workflow in place on which we can iterate. > > The next iterations afterward would be to work on the 4 scenarios that > are also going to be upgrades from Ocata to pike (001 to 004). > For that, we'll need Problem #1 and #2 resolved before we want to make > any progress here, to not hit the same issues that before. > >> Problem #3: from Ocata to Pike: all container images are >> uploaded/specified, even for services not deployed >> https://bugs.launchpad.net/tripleo/+bug/1710992 >> The CI jobs are timeouting during the upgrade process because >> downloading + uploading _all_ containers in local cache takes more >> than 20 minutes. >> So this is where we are now, upgrade jobs timeout on that. Steve Baker >> is currently looking at it but we'll probably offer some help. > > Steve is still working on it: https://review.openstack.org/#/c/448328/ > Steve, if you need any help (reviewing or coding) - please let us > know, as we consider this thing important to have and probably good to > have in Pike. Independent, but related issue is that the job doesn't make use of CI-local registry mirrors. I seem to recall we already had mirror usage implemented at some point, but we must have lost it somehow. Fix is here: https://review.openstack.org/#/c/494525/ Jirka > > Thanks, > ------------------------------ Message: 19 Date: Thu, 17 Aug 2017 17:53:52 +0100 From: Luke Hinds <[email protected]> To: Raildo Mascena de Sousa Filho <[email protected]> Cc: "OpenStack Development Mailing List \(not for usage questions\)" <[email protected]> Subject: Re: [openstack-dev] [barbican] [security] custodia @ PTG Message-ID: <cakrsgqta4ayco7piean595eu3xmfg7ygr4wx7esdcdbncrf...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi Raildo, That's great news. Are you around next Thursday to jump on #openstack-meeting-alt at 17:00 UTC? we can then go over some topics. @Dave, unless you prefer to use the Barbican meeting that is (possible synergies to barbican)? Regards, Luke On Thu, Aug 17, 2017 at 1:10 PM, Raildo Mascena de Sousa Filho < [email protected]> wrote: > Hi Luke, > > I'll definitely be there, sounds like a great idea, so we can clarify a > lot of topics and make progress in the community together. > > Cheers, > > > On Thu, Aug 17, 2017 at 5:52 AM Luke Hinds <[email protected]> wrote: > >> Hi Raildo, >> >> Both Barbican and Security have an interest in custodia and we have it >> marked down as a topic / discussion point for the PTG [1] >> >> Would you be interested / willing to join the Barbican room on Thurs / >> Fri and propose a walk through / overview etc? >> >> [1] https://etherpad.openstack.org/p/barbican-ptg-queens >> >> >> Regards, >> >> Luke >> > -- > > Raildo mascena > > Software Engineer, Identity Managment > > Red Hat > > <https://www.redhat.com> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > -- Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat e: [email protected] | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44 12 52 36 2483 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170817/46de313d/attachment-0001.html> ------------------------------ Message: 20 Date: Thu, 17 Aug 2017 22:25:17 +0530 From: Anil Venkata <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: Re: [openstack-dev] [neutron] Call for help with in-tree tempest scenario test failures Message-ID: <CAP7mkkAN2KrNrpeaNx+gN5cR5Y7Q2MkSVhmXg6U90rqBt-=-d...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" I will work on DVR+HA migration jobs. Thanks Anilvenkata On Fri, Aug 11, 2017 at 2:40 AM, Sławek Kapłoński <[email protected]> wrote: > Hello, > > I’m still checking this QoS scenario test and I found something strange > IMHO. > For example, almost all failed tests from last 2 days were executed on > nodes with names like: > * ubuntu-xenial-2-node-citycloud-YYY-XXXX - on those nodes almost (or > even all) all scenario tests was failed due to failed SSH connection to > instance, > * ubuntu-xenial-2-node-rax-iad-XXXX - on those nodes QoS test was failed > because of timeout during reading data > > I’m noob in gate tests and how it’s exactly working so my conclusions can > be completely wrong but maybe those issues are related somehow to some > cloud providers which provides infrastructure for tests? > Maybe someone more experienced could take a look on that and help me? Thx > in advance. > > — > Best regards > Slawek Kaplonski > [email protected] > > > > > > Wiadomość napisana przez Ihar Hrachyshka <[email protected]> w dniu > 03.08.2017, o godz. 23:40: > > > > Thanks for those who stepped in (Armando and Slawek). > > > > We still have quite some failures that would benefit from initial log > > triage and fixes. If you feel like in this feature freeze time you > > have less things to do, helping with those scenario failures would be > > a good way to contribute to the project. > > > > Thanks, > > Ihar > > > > On Fri, Jul 28, 2017 at 6:02 AM, Sławek Kapłoński <[email protected]> > wrote: > >> Hello, > >> > >> I will try to check QoS tests in this job. > >> > >> — > >> Best regards > >> Slawek Kaplonski > >> [email protected] > >> > >> > >> > >> > >>> Wiadomość napisana przez Jakub Libosvar <[email protected]> w dniu > 28.07.2017, o godz. 14:49: > >>> > >>> Hi all, > >>> > >>> as sending out a call for help with our precious jobs was very > >>> successful last time and we swept all Python 3 functional from Neutron > >>> pretty fast (kudos the the team!), here comes a new round of failures. > >>> > >>> This time I'm asking for your help <imagine Uncle Sam "We want you" > >>> poster here> with gate-tempest-dsvm-neutron-dvr-multinode-scenario > >>> non-voting job. This job has been part of check queue for a while and > is > >>> very very unstable. Such job covers scenarios like router dvr/ha/legacy > >>> migrations, qos, trunk and dvr. I went through current failures and > >>> created an etherpad [1] with categorized failures and logstash queries > >>> that give you latest failures with given particular tests. > >>> > >>> If you feel like doing troubleshooting and sending fixes for gates, > >>> please pick one test and write down your name to the test. > >>> > >>> Thanks to all who are willing to participate. > >>> > >>> Have a great weekend. > >>> Jakub > >>> > >>> > >>> [1] > >>> https://etherpad.openstack.org/p/neutron-dvr-multinode- > scenario-gate-failures > >>> > >>> > >>> ____________________________________________________________ > ______________ > >>> OpenStack Development Mailing List (not for usage questions) > >>> Unsubscribe: [email protected]?subject: > unsubscribe > >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >> > >> > >> ____________________________________________________________ > ______________ > >> OpenStack Development Mailing List (not for usage questions) > >> Unsubscribe: [email protected]?subject: > unsubscribe > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >> > > > > ____________________________________________________________ > ______________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: [email protected]?subject: > unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170817/1ff883a2/attachment-0001.html> ------------------------------ Message: 21 Date: Thu, 17 Aug 2017 13:13:40 -0400 From: Julia Kreger <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: [openstack-dev] [ironic] pike release Message-ID: <caf7gwdicrqz5hnfgt0f8xxuzfrs9h2o9jndq10xms7m7hwu...@mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Greetings everyone! As some of you may have noticed, we released ironic 9.0.0 today. But wait! There is more! We triggered this release due to a number of issues, one of which was that we learned that we needed the stable/pike branch for our grenade jobs to execute properly. This was not done previously because Ironic’s release model is incompatible with making release candidate releases. Once we’ve confirmed that our grenade testing is passing, we will back port patches we had previously approved, but that had not landed, from master to stable/pike. As a result, please anticipate Ironic’s official Pike release for this cycle to be 9.1.0, if the stars, gates, and job timeouts align with us. If there are any questions, please feel free to stop by #openstack-ironic. We have also been keeping our general purpose whiteboard[1] up to date, you can see our notes regarding our current plan starting at line 120, and notes regarding gate failures and issues starting at line 37. Thanks! -Julia [1]: https://etherpad.openstack.org/p/IronicWhiteBoard ------------------------------ Message: 22 Date: Thu, 17 Aug 2017 13:25:24 -0400 From: michael mccune <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: [openstack-dev] [all][api] POST /api-sig/news Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8; format=flowed Greetings OpenStack community, This week's meeting centered around two main topics; the Guided Review Process[0] and the inclusion of guidance to discourage extension usage[4]. As the working group has now become a Special Interest Group, we have begun the work of changing the documentation and infra services over to use the new naming (with many thanks to Ed Leafe). The Guided Review Process document has been accepted by the SIG as a document describing an activity that we will be hosting at PTG events, and also as requested by teams. Emails will be sent out this week to all the project PTLs with instructions about the review process and how they can be prepared to participate at the Queens PTG. If you have not seen this document yet, you can find it in the review[0], or on the API-SIG specs site[2] once it is redeployed. Work on the guidance to discourage extension usage[4] continues and there have been some comments by members of the community to help drive this process along. This topic continues to be a tricky discussion, but the SIG is making progress in defining a guideline that will be ready for community approval. As with last week, we still haven't fully decided how these issues will be explained, but we are getting closer and continue to hold the ideal that extension URIs are not helpful for creating interoperable APIs. On the topic of the PTG, there was some minor discussion about what we will be talking about beyond guided reviews but this is still in the nascent stages. Stay tuned for more information about the API-SIG PTG events. # Newly Published Guidelines None this week. # API Guidelines Proposed for Freeze Guidelines that are ready for wider review by the whole community. None this week # Guidelines Currently Under Review [3] * Explain, simply, why extensions are bad https://review.openstack.org/#/c/491611/ * A (shrinking) suite of several documents about doing version and service discovery Start at https://review.openstack.org/#/c/459405/ * WIP: microversion architecture archival doc (very early; not yet ready for review) https://review.openstack.org/444892 # Highlighting your API impacting issues If you seek further review and insight from the API WG, please address your concerns in an email to the OpenStack developer mailing list[1] with the tag "[api]" in the subject. In your email, you should include any relevant reviews, links, and comments to help guide the discussion of the specific challenge you are facing. To learn more about the API WG mission and the work we do, see OpenStack API Working Group [2]. Thanks for reading and see you next week! # References [0] https://review.openstack.org/#/c/487847/ [1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev [2] http://specs.openstack.org/openstack/api-wg/ [3] https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z [4] https://review.openstack.org/#/c/491611/ Meeting Agenda https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda Past Meeting Records http://eavesdrop.openstack.org/meetings/api_wg/ Open Bugs https://bugs.launchpad.net/openstack-api-wg ------------------------------ Message: 23 Date: Thu, 17 Aug 2017 19:20:24 +0100 (BST) From: Chris Dent <[email protected]> To: [email protected] Subject: [openstack-dev] [all] purplerbot briefly broken Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8"; Format="flowed" If you don't know what purplerbot is, you can stop reading if you don't care. If you do see: https://anticdent.org/purple-irc-bot.html Because I was lazy, I never registered the purplerbot nick with freenode. Sometime in the recent past freenode made it so that you had to be a registered nick in order to be able to send private messages to at least some and maybe all users. This meant that commands like `p!spy openstack-nova` (that and additional commands explained in the link above) would result in no output, no error message, nothing. The bot's server side error log clued me in and it is now fixed. If you've now read this and the blog posting and think "hey, I want purplerbot in my channel", please let me know. -- Chris Dent (⊙＿⊙') https://anticdent.org/ freenode: cdent tw: @anticdent ------------------------------ Message: 24 Date: Thu, 17 Aug 2017 15:33:48 -0600 From: Kevin Benton <[email protected]> To: [email protected] Subject: [openstack-dev] No drivers meeting today Message-ID: <CAO_F6JOwioq=yeDPkDvzwL3Pru71Qp=TFWO6Uju=eb4-ak5...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi everyone, I'm canceling the drivers meeting today to allow everyone to focus on fixes for Pike. Let me or Armando know right away if you have have any fixes that need to go into RC2 since he has prepared the RC2 release patch already. Cheers, Kevin Benton -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170817/076d13b7/attachment-0001.html> ------------------------------ Message: 25 Date: Thu, 17 Aug 2017 16:47:14 -0500 From: Matthew Thode <[email protected]> To: [email protected] Subject: [openstack-dev] [requirements] Unfreezing of the requirements repo Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Hi all, It's time to unfreeze the requirements repo. For projects that have branched (most everyone at this point) this won't be a change. For projects that have yet to branch, you will need to look out for and block global requirements bot updates until you've branched. You will also need to look out for test failures in your gating as you mau be pulling in master (queens) upper-constraints instead of pike. The workaround for this is to change your tox.ini temporarilly to target the pike branch for fetching the upper-constraints.txt file. It'd be better to just branch if you can though. If you have questions, feel free to reach out to me on irc (prometheanfire on freenode, #openstack-requirements for the channel) or email. -- Matthew Thode (prometheanfire) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170817/582c07ed/attachment-0001.sig> ------------------------------ Message: 26 Date: Fri, 18 Aug 2017 07:55:29 +1000 From: Tony Breeds <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: Re: [openstack-dev] [requirements] Unfreezing of the requirements repo Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" On Thu, Aug 17, 2017 at 04:47:14PM -0500, Matthew Thode wrote: > Hi all, > > It's time to unfreeze the requirements repo. > > For projects that have branched (most everyone at this point) this > won't be a change. > > For projects that have yet to branch, you will need to look out for > and block global requirements bot updates until you've branched. > You will also need to look out for test failures in your gating as you > mau be pulling in master (queens) upper-constraints instead of pike. > The workaround for this is to change your tox.ini temporarilly to target > the pike branch for fetching the upper-constraints.txt file. It'd be > better to just branch if you can though. That won't work. As the gate doesn't use that URL is copy's the file from the requirements repo from the same branch into the projects workspace. See the various run-*.sh scripts like: http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/scripts/run-tox.sh#n119 So if a constraints update on master breaks your prep for pike please reach out quickly to the requirements team. Yours Tony. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170818/7b5309f7/attachment-0001.sig> ------------------------------ Message: 27 Date: Thu, 17 Aug 2017 22:57:22 +0100 From: Jean-Philippe Evrard <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: Re: [openstack-dev] [kolla] [tripleo] [openstack-ansible] [deployment] Collaboration at PTG Message-ID: <CAEhFLkTatBuT7PiEQ1=s3hr6rqr3hxw+lmivd6fow6iz18f...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" I'd be happy to join. I don't think we have constraints on the schedule yet, and we can indeed book slot(s). Best regards, JP. On Thu, Aug 17, 2017 at 3:30 PM, Emilien Macchi <[email protected]> wrote: > Hey folks, > > As usual, we'll meet in Denver and I hope we can spend some time > together (in a meeting room first) to have face to face discussions on > the recent topics that we had. > Right now, TripleO sessions are not scheduled in our agenda, so we're > pretty flexible: https://etherpad.openstack.org/p/tripleo-ptg-queens > > I would like to propose one topic (happy to coordinate the discussion) > on some efforts regarding doing configuration management with Ansible, > and k8s integration as well. > Flavio made some progress [1] - I really hope we can make progress here. > > [1] http://lists.openstack.org/pipermail/openstack-dev/2017- > July/119696.html > > If you're working on Kolla / OpenStack-Ansible - please let us know if > you have specific constraints on the schedule, so we can maybe block a > timeslot in the agenda from now. > We'll have a "Packaging" room which is reserved for all topics related > to OpenStack deployments, so we can use this one. > > Looking forward to meeting you at PTG! > Thanks, > -- > Emilien Macchi > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170817/e270036f/attachment-0001.html> ------------------------------ Message: 28 Date: Thu, 17 Aug 2017 19:48:43 -0400 From: David Moreau Simard <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: Re: [openstack-dev] [kolla] [tripleo] [openstack-ansible] [deployment] Collaboration at PTG Message-ID: <cah7c+po80y9yuxloncgzkjddgb98ka7w6r1o4+1xtih4k+i...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Happy to join in case my perspective from infra and RDO can be useful! David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] On Aug 17, 2017 10:32 AM, "Emilien Macchi" <[email protected]> wrote: > Hey folks, > > As usual, we'll meet in Denver and I hope we can spend some time > together (in a meeting room first) to have face to face discussions on > the recent topics that we had. > Right now, TripleO sessions are not scheduled in our agenda, so we're > pretty flexible: https://etherpad.openstack.org/p/tripleo-ptg-queens > > I would like to propose one topic (happy to coordinate the discussion) > on some efforts regarding doing configuration management with Ansible, > and k8s integration as well. > Flavio made some progress [1] - I really hope we can make progress here. > > [1] http://lists.openstack.org/pipermail/openstack-dev/2017- > July/119696.html > > If you're working on Kolla / OpenStack-Ansible - please let us know if > you have specific constraints on the schedule, so we can maybe block a > timeslot in the agenda from now. > We'll have a "Packaging" room which is reserved for all topics related > to OpenStack deployments, so we can use this one. > > Looking forward to meeting you at PTG! > Thanks, > -- > Emilien Macchi > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170817/6f94341a/attachment-0001.html> ------------------------------ Message: 29 Date: Fri, 18 Aug 2017 12:18:41 +1200 From: Lingxian Kong <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: Re: [openstack-dev] [horizon] Multi-region support in shared Keystone service deployment Message-ID: <caljnaz38ecm+n0b-fxmhkbiw-rxinceangj7vwojemw2_y1...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Thanks, Rob, blueprint is proposed here: https://blueprints.launchpad.net/horizon/+spec/horizon-multi-region-support Cheers, Lingxian Kong (Larry) On Thu, Aug 17, 2017 at 11:05 PM, Rob Cresswell (rcresswe) < [email protected]> wrote: > As I mentioned the last time you asked :), we use blueprints, and the > template is here: https://blueprints.launchpad.net/horizon/+spec/template > > Please register a blueprint for discussion / tracking. The change looks > sensible, although I’d prefer we use a setting name like > https://docs.openstack.org/horizon/latest/configuration/settings.html# > openstack-keystone-domain-choices. It’s a bit less ambiguous. > > Rob > > > > On 16 Aug 2017, at 23:03, Lingxian Kong <[email protected]> wrote: > > Hi, Horizon developers, > > In our OpenStack based public cloud(Catalyst Cloud), Keystone is a shared > identity service across 3 regions, our customers have been asking for the > feature that they could select their preferred region when they log in > Horizon, rather than switching region each time after login. > > Unfortunately, the existing 'AVAILABLE_REGIONS' only works with > multi-keystone, multi-region environment, so for backward compatibility and > getting rid of potential confusion, a new config option named > 'AVAILABLE_SERVICE_REGIONS' was introduced in my patch[1][2], the setting > is supposed to be configured by the cloud operators and the > 'AVAILABLE_REGIONS' setting will take precedence over > 'AVAILABLE_SERVICE_REGIONS'. > > I am sending this email to ask for more feedback, and do I need to propose > a feature spec before the code is actually being reviewed? > > [1]: https://review.openstack.org/#/c/494083/ > [2]: https://review.openstack.org/#/c/494059/ > > Cheers, > Lingxian Kong (Larry) > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170818/ecc1ddab/attachment-0001.html> ------------------------------ Message: 30 Date: Fri, 18 Aug 2017 00:47:02 +0000 From: joehuang <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: [openstack-dev] [releases]pike release notes missing in Tricircle Message-ID: <5e7a3d1bf5fd014e86e5f971cf446eff564ad...@dggeml501-mbx.china.huawei.com> Content-Type: text/plain; charset="iso-8859-1" Hello, The patch to update the reno( https://review.openstack.org/#/c/494565/ ) has been merged after Tricircle stable/pike branch is created, and the gate-tricircle-releasenotes<http://docs-draft.openstack.org/65/494565/1/check/gate-tricircle-releasenotes/088a2a1//releasenotes/build/html/> also worked fine, but the pike release notes is missing in https://docs.openstack.org/releasenotes/tricircle/ I found that pike release notes are visible both in Nova/Cinder project (https://docs.openstack.org/releasenotes/cinder/ https://docs.openstack.org/releasenotes/nova/) Is there something need to do to make pike release notes appearing in the site? Best Regards Chaoyi Huang (joehuang) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170818/ef063ea0/attachment-0001.html> ------------------------------ Message: 31 Date: Fri, 18 Aug 2017 02:41:23 +0000 From: "Xiong, Huan" <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: Re: [openstack-dev] [horizon] Admin dashboard instances index page generated duplicate Glance requests Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" > This may be a bug; I recall it was patched recently and perhaps the same logic > needs to be applied to the Admin view. It sounds like an oversight. Thanks, Rob. I filed 1711486. What you mentioned is probably df194c8b. It added code in Admin dashboard instance index view class to retrieve image objects, but didn't use them to set instances' image attribute. Thanks, Ray > > Rob > > > On 14 Aug 2017, at 03:46, Xiong, Huan <[email protected]> > wrote: > > > > Hi, > > > > I observed accessing Admin dashboard's instance index page generated > lots of duplicate requests to Glance for converting instance image id to name, > but accessing Project dashboard's instance index page didn't (my system > runs Newton, but from what I can tell, Ocata and Pike code seem to have > same issue). > > > > I looked at the code and found the reason. In Project dashboard's instance > index view class, it first calls Glance's API to get a list of image objects, > then > iterates through instance objects and sets each instance's image attribute to > corresponding image object. As a result, when instance object's > image_name() is called later, it gets name from image object. In Admin > dashboard's instance index view class, however, it doesn't do this and hence > needs to send request to Glance everytime image_name() is called. > > > > I wonder why Admin dashboard's instance index view class doesn't use the > same approach as Project dashboard? Is it intended? > > > > Thanks, > > Ray > > > > > > > > This email is intended only for the named addressee. It may contain > information that is confidential/private, legally privileged, or copyright- > protected, and you should handle it accordingly. If you are not the intended > recipient, you do not have legal rights to retain, copy, or distribute this > email > or its contents, and should promptly delete the email and all electronic > copies > in your system; do not retain copies in any media. If you have received this > email in error, please notify the sender promptly. Thank you. > > > > > > > > > __________________________________________________________ > ____________ > > ____ OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > > [email protected]?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > __________________________________________________________ > ________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev- > [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev This email is intended only for the named addressee. It may contain information that is confidential/private, legally privileged, or copyright-protected, and you should handle it accordingly. If you are not the intended recipient, you do not have legal rights to retain, copy, or distribute this email or its contents, and should promptly delete the email and all electronic copies in your system; do not retain copies in any media. If you have received this email in error, please notify the sender promptly. Thank you. ------------------------------ Message: 32 Date: Fri, 18 Aug 2017 03:13:07 +0000 From: joehuang <[email protected]> To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Subject: Re: [openstack-dev] [releases]pike release notes missing in Tricircle Message-ID: <5e7a3d1bf5fd014e86e5f971cf446eff564ae...@dggeml501-mbx.china.huawei.com> Content-Type: text/plain; charset="iso-8859-1" Not an issue. Just found that the patch needs to be approved by reviewer(s), it's not merged automatically. Best Regards Chaoyi Huang (joehuang) ________________________________ From: joehuang Sent: 18 August 2017 8:47 To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev][releases]pike release notes missing in Tricircle Hello, The patch to update the reno( https://review.openstack.org/#/c/494565/ ) has been merged after Tricircle stable/pike branch is created, and the gate-tricircle-releasenotes<http://docs-draft.openstack.org/65/494565/1/check/gate-tricircle-releasenotes/088a2a1//releasenotes/build/html/> also worked fine, but the pike release notes is missing in https://docs.openstack.org/releasenotes/tricircle/ I found that pike release notes are visible both in Nova/Cinder project (https://docs.openstack.org/releasenotes/cinder/ https://docs.openstack.org/releasenotes/nova/) Is there something need to do to make pike release notes appearing in the site? Best Regards Chaoyi Huang (joehuang) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170818/8b63630c/attachment-0001.html> ------------------------------ Message: 33 From: [email protected] To: [email protected] Subject: [openstack-dev] [octavia] octavia 1.0.0.0rc2 (pike) Message-ID: <[email protected]> Hello everyone, A new release candidate for octavia for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/octavia/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Pike release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/pike release branch at: http://git.openstack.org/cgit/openstack/octavia/log/?h=stable/pike Release notes for octavia can be found at: http://docs.openstack.org/releasenotes/octavia/ ------------------------------ Message: 34 From: [email protected] To: [email protected] Subject: [openstack-dev] [keystone] keystone 12.0.0.0rc2 (pike) Message-ID: <[email protected]> Hello everyone, A new release candidate for keystone for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/keystone/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Pike release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/pike release branch at: http://git.openstack.org/cgit/openstack/keystone/log/?h=stable/pike Release notes for keystone can be found at: http://docs.openstack.org/releasenotes/keystone/ ------------------------------ Message: 35 Date: Fri, 18 Aug 2017 10:28:16 +0200 From: Thierry Carrez <[email protected]> To: openstack-dev <[email protected]> Subject: [openstack-dev] [release] Release countdown for week R-1, August 18-25 Message-ID: <[email protected]> Content-Type: text/plain; charset=windows-1252 Welcome to our regular release countdown email! Development Focus ----------------- We are entering the last week before release week. Focus should be on producing the last Pike release candidates and intermediary releases, including updated translations and requirements updates. If your team attends the PTG in Denver, you should also be actively preparing the topics for discussion at the event. Actions ---------- For *cycle-with-intermediary* deliverables, the Pike release will be the last-released version. If you need to release a newer version, you need to do it before August 24. After that date we can't guarantee inclusion in the Pike release, and will fall back to the last-released version. The following deliverables still did not have /any/ release during the Pike cycle and urgently need to make one (and ask for the stable/pike branch to be cut from it). If we don't have anything by the deadline, the release team will have to either force a release, or remove the deliverable from Pike: - ceilometer, panko - magnum, magnum-ui - senlin-dashboard - tacker As a reminder, asking for a release and corresponding stable/pike branch is done by modifying the deliverable Pike release file in the openstack/releases repository and adding: ... - projects: - hash: YOURHASH repo: openstack/YOURPROJECT version: YOUR.NEW.VERSION branches: - location: YOUR.NEW.VERSION name: stable/pike The following deliverables do have an intermediary release in Pike but still haven't asked for a stable/pike branch to be cut. If we don't have a stable/pike branch by the deadline, the release team will branch from the last-available intermediary release: - aodh - instack-undercloud - kuryr-kubernetes - manila-ui - neutron-fwaas-dashboard - swift - tacker-horizon As a reminder, asking for the stable/pike branch to be cut from an already-released Pike version is done by modifying the deliverable Pike release file in the openstack/releases repository and adding: ... branches: - location: YOUR.LAST.PIKEVERSION name: stable/pike For *cycle-with-milestones* deliverables, early next week you should make sure to merge the latest translations patches[1] and latest requirements patches[2], and ask for a last release candidate before the Pike release. As a reminder, asking for a new RC is done by modifying the deliverable Pike release file in the openstack/releases repository and adding: ... - projects: - hash: YOURHASH repo: openstack/YOURPROJECT version: YOURVERSION.0.0.0rc2 [1] https://review.openstack.org/#/q/status:open+branch:stable/pike+topic:zanata/translations [2] https://review.openstack.org/#/q/status:open+branch:stable/pike+topic:openstack/requirements Upcoming Deadlines & Dates -------------------------- Deadline for last release candidates / intermediary releases: August 24 Final Pike release: August 30 Queens PTG in Denver: Sept 11-15 As usual come find us on #openstack-release IRC channel if you have any questions or concerns. -- Thierry Carrez (ttx) ------------------------------ Message: 36 Date: Fri, 18 Aug 2017 09:02:25 +0000 From: Alexandra Settle <[email protected]> To: openstack-docs <[email protected]>, "OpenStack Development Mailing List (not for usage questions)" <[email protected]> Cc: Petr Kovar <[email protected]> Subject: [openstack-dev] [docs][ptg] Doc team attendance Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Hi everyone, I’ve updated the docs PTG etherpad with a few details: https://etherpad.openstack.org/p/denver-doc-PTG All those attending, could you please put your names/availability on the etherpad. Also – to those interested who cannot attend on the Mon-Tues for Queens planning sessions, please note that I have booked Wednesday morning in Colorado Ballroom C for migration-specific discussions. See: https://ethercalc.openstack.org/Queens-PTG-Discussion-Rooms If you wish to attend *these* sessions, please put your name in the Wednesday slot in the etherpad. Cheers, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170818/9e835bce/attachment-0001.html> ------------------------------ Message: 37 Date: Fri, 18 Aug 2017 09:08:51 +0000 From: <[email protected]> To: "[email protected]" <[email protected]> Subject: Re: [openstack-dev] [Vitrage] Template raise host cpu alarm on the instance and change state Message-ID: <30930_1503047333_5996AEA5_30930_412_1_B80AC817DD579B46B64BE775A4F83B6F9760F2@OPEXCLILM24.corporate.adroot.infra.ftgroup> Content-Type: text/plain; charset="utf-8" Hi All, I want to make this use case [cid:[email protected]] So I have used this Nagios config "/etc/vitrage/nagios_conf.yaml" nagios: - nagios_host: myhost type: nova.host name: hjtg2132-HP-ProDesk-600-G2-MT And I have used this template "host_high_cpu_load_to_instance_cpu_suboptimal.yaml" metadata: name: host_high_cpu_load_to_instance_cpu_suboptimal description: when there is high cpu on the host, show implications on the instances definitions: entities: - entity: category: ALARM type: host_high_cpu_load template_id: host_alarm # some string - entity: category: ALARM type: instance_cpu_performance_problem template_id: instance_alarm - entity: category: RESOURCE type: nova.host template_id: host - entity: category: RESOURCE type: nova.instance template_id: instance relationships: - relationship: source: host_alarm # source and target from entities section target: host relationship_type: on template_id : alarm_on_host - relationship: source: instance_alarm target: instance relationship_type: on template_id : alarm_on_instance - relationship: source: host target: instance relationship_type: contains template_id : host_contains_instance scenarios: - scenario: condition: alarm_on_host actions: - action: action_type: set_state action_target: target: host properties: state: ERROR - scenario: condition: alarm_on_host and host_contains_instance actions: - action: action_type: raise_alarm action_target: target: instance properties: alarm_name: Instance cpu Consumption is suboptimal severity: critical - action: action_type: set_state action_target: target: instance properties: state: ERROR - scenario: condition: alarm_on_host and host_contains_instance and alarm_on_instance actions: - action: action_type: add_causal_relationship action_target: source: host_alarm target: instance_alarm I can see the alarm from Nagios on the host. But I don't see the state changes and I don't see the alarms rises on instances so I don't see the root cause schema. Please find attached pictures showing that. I would appreciate if you can help me to solve this. Thanking you + best regards, Bader _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170818/32f204c8/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 14021 bytes Desc: image001.jpg URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170818/32f204c8/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: Images.zip Type: application/x-zip-compressed Size: 946729 bytes Desc: Images.zip URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170818/32f204c8/attachment.bin> ------------------------------ Subject: Digest Footer _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ------------------------------ End of OpenStack-dev Digest, Vol 64, Issue 31 ********************************************* _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
