From egle.sigler at rackspace.com Thu Mar 1 12:20:31 2018 From: egle.sigler at rackspace.com (Egle Sigler) Date: Thu, 1 Mar 2018 12:20:31 +0000 Subject: [Interop-wg] Meeting cadence Message-ID: <05053234-BF15-4DB3-A9B4-B22DE1659601@rackspace.com> Hello Everyone, During the PTG we have discussed changing the meeting frequency to every two weeks. Our next meeting will be on March 7th, followed by the meeting on March 21st. Thank you! Egle -------------- next part -------------- An HTML attachment was scrubbed... URL: From mvoelker at vmware.com Fri Mar 2 14:04:19 2018 From: mvoelker at vmware.com (Mark Voelker) Date: Fri, 2 Mar 2018 14:04:19 +0000 Subject: [Interop-wg] PTG Photos Available Message-ID: https://www.dropbox.com/sh/dtei3ovfi7z74vo/AABhBfvHCzSGxjdCqHhGK3pZa/Refstack?dl=0 At Your Service, Mark T. Voelker OpenStack Architect From egle.sigler at rackspace.com Tue Mar 6 20:21:51 2018 From: egle.sigler at rackspace.com (Egle Sigler) Date: Tue, 6 Mar 2018 20:21:51 +0000 Subject: [Interop-wg] Interop Meeting Invite Wed. 10:00 AM CST/ 16:00 UTC Message-ID: Hello Everyone, Etherpad for Wednesday’s meeting: https://etherpad.openstack.org/p/InteropWhistler.8 Please add items to the agenda. Note the meeting location: #openstack-meeting-3. If you can’t join us at this time, you can still contribute by sending email to the mailing list (or just to me or Mark), or joining us in the #openstack-interop IRC channel later. Patches and patch reviews are always welcome! https://review.openstack.org/#/q/status:open+project:openstack/interop,n,z Info on OpenStack IRC: https://wiki.openstack.org/wiki/IRC Web IRC link if you are not using IRC client: http://webchat.freenode.net/?channels=openstack-meeting-3 Meetbot quick reference guide: http://meetbot.debian.net/Manual.html#user-reference Thank you, Egle -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2620 bytes Desc: not available URL: From gmann at ghanshyammann.com Wed Mar 7 12:40:25 2018 From: gmann at ghanshyammann.com (Ghanshyam Mann) Date: Wed, 7 Mar 2018 21:40:25 +0900 Subject: [Interop-wg] [openstack-dev] [QA] [PTG] [Interop] [Designate] [Heat] [TC]: QA PTG Summary- Interop test for adds-on project Message-ID: Hi All, QA had discussion in Dublin PTG about interop adds-on tests location. First of all thanks all (specially markvoelker, dhellmann, mugsie) for joining the sessions. and I am glad we conclude the things and agreed on solution. Discussion was carry forward from the ML discussion [1] and to get the agreement about interop adds-on program tests location. Till now only 2 projects (heat and designate) are in list of adds-on program from interop side. After discussion and points from all stack holders, QA team agreed to host these 2 projects interop tests. Tests from both projects are not much as of now and QA team can accommodate to host their interop tests. Along with that agreement we had few more technical points to consider while moving designate and heat interop tests in Tempest repo. All the interop tests going to be added in Tempest must to be Tempest like tests. Tempest like tests here means tests written using Tempest interfaces and guidelines. For example, heat has their tests in heat-tempest-plugin based on gabbi and to move heat interop tests to Tempest those have to be written as Tempest like test. This is because if we accept non-tempest like tests in Tempest then, it will be too difficult to maintain by Tempest team. Projects (designate and heat) and QA team will work closely to move interop tests to Tempest repo which might needs some extra work of standardizing their tests and interface used by them like service clients etc. In future, if there are more new interop adds-on program proposal then, we need to analyse the situation again regarding QA team bandwidth. TC or QA or interop team needs to raise the resource requirement to Board of Directors before any more new adds-on program is being proposed. If QA team has less resource and less review bandwitdh then we cannot accept the more interop programs till QA get more resource to maintain new interop tests. Overall Summary: - QA team agreed to host the interop tests for heat and designate in Tempest repo. - Existing TC resolution needs to be adjust about the QA team resource bandwidth requirement. If there is going to be more adds-on program proposal then, QA team will not accept the new interop tests if QA team bandwidth issue still exist that time also. - Tempest will document the clear process about interop tests addition and other more care items etc. - Projects team to make their tests and interface as Tempest like tests and stable interfaces standards. Tempest team will closely work and help Designate and Heat on this. Action Items: - mugsie to abandon https://review.openstack.org/#/c/521602 with quick summary of discussion here at PTG - markvoelker to write up clarification to InteropWG process stating that tests should be moved into Tempest before being proposed to the BoD - markvoelker to work with gmann before next InteropWG+BoD discussion to frame up a note about resourcing testing for add-on/vertical programs - dhellmann to adjust the TC resolution for resource requirement in QA when new adds-on program is being proposed - project teams to convert interop test and framework as per tempest like tests and propose to add to tempest repo. - gmann to define process in QA about interop tests addition and maintainance We have added this as one of the monitoring/helping item for QA to make sure it is done without delay. Let's work together to finish this activity. Discussion Details: https://etherpad.openstack.org/p/qa-rocky-ptg-Interop-test-for-adds-on-project ..1 http://lists.openstack.org/pipermail/openstack-dev/2018-January/126146.html -gmann -------------- next part -------------- An HTML attachment was scrubbed... URL: From cdent+os at anticdent.org Wed Mar 7 13:07:33 2018 From: cdent+os at anticdent.org (Chris Dent) Date: Wed, 7 Mar 2018 13:07:33 +0000 (GMT) Subject: [Interop-wg] [openstack-dev] [QA] [PTG] [Interop] [Designate] [Heat] [TC]: QA PTG Summary- Interop test for adds-on project In-Reply-To: References: Message-ID: On Wed, 7 Mar 2018, Rabi Mishra wrote: >> Projects (designate and heat) and QA team will work closely to move >> interop tests to Tempest repo which might needs some extra work of >> standardizing their tests and interface used by them like service clients >> etc. >> > > Though I've not been part of any of these discussions, this seems to be > exactly opposite to what I've been made to understand by the team i.e. Heat > is not rewriting the gabbi api tests used by Trademark program, but would > create a new tempest plugin (new repo > 'orchestration-trademark-tempest-plugin') to host the heat related tests > that are currently candidates for Trademark program? There was additional discussion on Friday with people from the TC, trademark program, heat and QA that resulted in the plan you describe, which is being codified at: https://review.openstack.org/#/c/521602/ -- Chris Dent (⊙＿⊙') https://anticdent.org/ freenode: cdent tw: @anticdent From andrea.frittoli at gmail.com Wed Mar 7 13:15:20 2018 From: andrea.frittoli at gmail.com (Andrea Frittoli) Date: Wed, 07 Mar 2018 13:15:20 +0000 Subject: [Interop-wg] [openstack-dev] [QA] [PTG] [Interop] [Designate] [Heat] [TC]: QA PTG Summary- Interop test for adds-on project In-Reply-To: References: Message-ID: On Wed, Mar 7, 2018 at 12:42 PM Ghanshyam Mann wrote: > Hi All, > > QA had discussion in Dublin PTG about interop adds-on tests location. > First of all thanks all (specially markvoelker, dhellmann, mugsie) for > joining the sessions. and I am glad we conclude the things and agreed on > solution. > > Discussion was carry forward from the ML discussion [1] and to get the > agreement about interop adds-on program tests location. > > Till now only 2 projects (heat and designate) are in list of adds-on > program from interop side. After discussion and points from all stack > holders, QA team agreed to host these 2 projects interop tests. Tests from > both projects are not much as of now and QA team can accommodate to host > their interop tests. > > Along with that agreement we had few more technical points to consider > while moving designate and heat interop tests in Tempest repo. All the > interop tests going to be added in Tempest must to be Tempest like tests. > Tempest like tests here means tests written using Tempest interfaces and > guidelines. For example, heat has their tests in heat-tempest-plugin based > on gabbi and to move heat interop tests to Tempest those have to be written > as Tempest like test. This is because if we accept non-tempest like tests > in Tempest then, it will be too difficult to maintain by Tempest team. > > Projects (designate and heat) and QA team will work closely to move > interop tests to Tempest repo which might needs some extra work of > standardizing their tests and interface used by them like service clients > etc. > > In future, if there are more new interop adds-on program proposal then, we > need to analyse the situation again regarding QA team bandwidth. TC or QA > or interop team needs to raise the resource requirement to Board of > Directors before any more new adds-on program is being proposed. If QA team > has less resource and less review bandwitdh then we cannot accept the more > interop programs till QA get more resource to maintain new interop tests. > > Overall Summary: > - QA team agreed to host the interop tests for heat and designate in > Tempest repo. > - Existing TC resolution needs to be adjust about the QA team resource > bandwidth requirement. If there is going to be more adds-on program > proposal then, QA team will not accept the new interop tests if QA team > bandwidth issue still exist that time also. > - Tempest will document the clear process about interop tests addition and > other more care items etc. > - Projects team to make their tests and interface as Tempest like tests > and stable interfaces standards. Tempest team will closely work and help > Designate and Heat on this. > > Thanks for the summary Ghanshyam! We had some follow up discussion on Friday about this, after the Heat team expressed their concern about proceeding with the plan we discussed during the session on Wednesday. A group of representatives of the Heat, Designate and Interop teams met with the TC and agreed on reviving the resolution started by mugsie in https://review.openstack.org/#/c/521602 to add an alternative to hosting tests in the Tempest repo. Unfortunately I was only there for the last few minutes of the meeting, but I understand that the proposal drafted there was to allow team to have interop-specific Tempest plugins co-owned by QA/Interop/add-on project team. mugsie has updated the resolution accordingly and I think the discussion on that can continue in gerrit directly. Just to clarify, nothing has been decided yet, but at least the new proposal was received positively by all parties involved in the discussion on Friday. Action Items: > - mugsie to abandon https://review.openstack.org/#/c/521602 with quick > summary of discussion here at PTG > This is not valid anymore, we should discuss this further and hopefully reach an agreement. > - markvoelker to write up clarification to InteropWG process stating that > tests should be moved into Tempest before being proposed to the BoD > - markvoelker to work with gmann before next InteropWG+BoD discussion to > frame up a note about resourcing testing for add-on/vertical programs > - dhellmann to adjust the TC resolution for resource requirement in QA > when new adds-on program is being proposed > - project teams to convert interop test and framework as per tempest > like tests and propose to add to tempest repo. > If the new resolution is agreed on, this will become one of the options. > - gmann to define process in QA about interop tests addition and > maintainance > This is still an option so you may still want to do it. Andrea Frittoli (andreaf) > > We have added this as one of the monitoring/helping item for QA to make > sure it is done without delay. Let's work together to finish this > activity. > > Discussion Details: > https://etherpad.openstack.org/p/qa-rocky-ptg-Interop-test-for-adds-on-project > > ..1 > http://lists.openstack.org/pipermail/openstack-dev/2018-January/126146.html > > > -gmann > _______________________________________________ > Interop-wg mailing list > Interop-wg at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/interop-wg > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ramishra at redhat.com Wed Mar 7 13:01:05 2018 From: ramishra at redhat.com (Rabi Mishra) Date: Wed, 7 Mar 2018 18:31:05 +0530 Subject: [Interop-wg] [openstack-dev] [QA] [PTG] [Interop] [Designate] [Heat] [TC]: QA PTG Summary- Interop test for adds-on project In-Reply-To: References: Message-ID: On Wed, Mar 7, 2018 at 6:10 PM, Ghanshyam Mann wrote: > Hi All, > > QA had discussion in Dublin PTG about interop adds-on tests location. > First of all thanks all (specially markvoelker, dhellmann, mugsie) for > joining the sessions. and I am glad we conclude the things and agreed on > solution. > > Discussion was carry forward from the ML discussion [1] and to get the > agreement about interop adds-on program tests location. > > Till now only 2 projects (heat and designate) are in list of adds-on > program from interop side. After discussion and points from all stack > holders, QA team agreed to host these 2 projects interop tests. Tests from > both projects are not much as of now and QA team can accommodate to host > their interop tests. > > Along with that agreement we had few more technical points to consider > while moving designate and heat interop tests in Tempest repo. All the > interop tests going to be added in Tempest must to be Tempest like tests. > Tempest like tests here means tests written using Tempest interfaces and > guidelines. For example, heat has their tests in heat-tempest-plugin based > on gabbi and to move heat interop tests to Tempest those have to be written > as Tempest like test. This is because if we accept non-tempest like tests > in Tempest then, it will be too difficult to maintain by Tempest team. > > Projects (designate and heat) and QA team will work closely to move > interop tests to Tempest repo which might needs some extra work of > standardizing their tests and interface used by them like service clients > etc. > Though I've not been part of any of these discussions, this seems to be exactly opposite to what I've been made to understand by the team i.e. Heat is not rewriting the gabbi api tests used by Trademark program, but would create a new tempest plugin (new repo 'orchestration-trademark-tempest-plugin') to host the heat related tests that are currently candidates for Trademark program? > > In future, if there are more new interop adds-on program proposal then, we > need to analyse the situation again regarding QA team bandwidth. TC or QA > or interop team needs to raise the resource requirement to Board of > Directors before any more new adds-on program is being proposed. If QA team > has less resource and less review bandwitdh then we cannot accept the more > interop programs till QA get more resource to maintain new interop tests. > > Overall Summary: > - QA team agreed to host the interop tests for heat and designate in > Tempest repo. > - Existing TC resolution needs to be adjust about the QA team resource > bandwidth requirement. If there is going to be more adds-on program > proposal then, QA team will not accept the new interop tests if QA team > bandwidth issue still exist that time also. > - Tempest will document the clear process about interop tests addition and > other more care items etc. > - Projects team to make their tests and interface as Tempest like tests > and stable interfaces standards. Tempest team will closely work and help > Designate and Heat on this. > > Action Items: > - mugsie to abandon https://review.openstack.org/#/c/521602 with quick > summary of discussion here at PTG > - markvoelker to write up clarification to InteropWG process stating that > tests should be moved into Tempest before being proposed to the BoD > - markvoelker to work with gmann before next InteropWG+BoD discussion to > frame up a note about resourcing testing for add-on/vertical programs > - dhellmann to adjust the TC resolution for resource requirement in QA > when new adds-on program is being proposed > - project teams to convert interop test and framework as per tempest > like tests and propose to add to tempest repo. > - gmann to define process in QA about interop tests addition and > maintainance > > We have added this as one of the monitoring/helping item for QA to make > sure it is done without delay. Let's work together to finish this > activity. > > Discussion Details: https://etherpad.openstack.org/p/qa-rocky-ptg-Interop- > test-for-adds-on-project > > ..1 http://lists.openstack.org/pipermail/openstack-dev/2018- > January/126146.html > > -gmann > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Regards, Rabi Mishra -------------- next part -------------- An HTML attachment was scrubbed... URL: From egle.sigler at rackspace.com Tue Mar 20 18:48:12 2018 From: egle.sigler at rackspace.com (Egle Sigler) Date: Tue, 20 Mar 2018 18:48:12 +0000 Subject: [Interop-wg] Interop Meeting Invite Wed. 11:00 AM CDT/ 16:00 UTC Message-ID: Hello Everyone, Etherpad for Wednesday’s meeting: https://etherpad.openstack.org/p/InteropWhistler.9 Please add items to the agenda. Meetings will be held every other week. Time is adjusted for daylight savings. Note the meeting location: #openstack-meeting-3. If you can’t join us at this time, you can still contribute by sending email to the mailing list (or just to me or Mark), or joining us in the #openstack-interop IRC channel later. Patches and patch reviews are always welcome! https://review.openstack.org/#/q/status:open+project:openstack/interop,n,z Info on OpenStack IRC: https://wiki.openstack.org/wiki/IRC Web IRC link if you are not using IRC client: http://webchat.freenode.net/?channels=openstack-meeting-3 Meetbot quick reference guide: http://meetbot.debian.net/Manual.html#user-reference Thank you, Egle -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2716 bytes Desc: not available URL: