From aspiers at suse.com Thu Jan 4 00:59:23 2018 From: aspiers at suse.com (Adam Spiers) Date: Thu, 4 Jan 2018 00:59:23 +0000 Subject: [Openstack-sigs] [self-healing] now tracking SIG actions in StoryBoard Message-ID: <20180104005923.gsq3vyfa3qycjbep@pacific.linksys.moosehall> Hi all, and happy 2018! After a chaotic holiday season, one of my first orders of business is to take care of various administravia relating to the new Self-Healing SIG. One piece of related news is that we now have a git repository: https://git.openstack.org/cgit/openstack/self-healing-sig/summary https://github.com/openstack/self-healing-sig Although we have no immediate plans to populate this with anything (yet, at least), it allows us to use Storyboard to track actions related to self-healing. Consequently I have started to file stories and tasks for these: https://storyboard.openstack.org/#!/project/917 Contributions / feedback welcome on any of those. I'll be sending out individual mails on some of those topics over the coming days and weeks. Regards, Adam From aspiers at suse.com Thu Jan 4 01:09:22 2018 From: aspiers at suse.com (Adam Spiers) Date: Thu, 4 Jan 2018 01:09:22 +0000 Subject: [Openstack-sigs] [self-healing] URGENT RFC: length of PTG session for self-healing SIG In-Reply-To: <20180104005923.gsq3vyfa3qycjbep@pacific.linksys.moosehall> References: <20180104005923.gsq3vyfa3qycjbep@pacific.linksys.moosehall> Message-ID: <20180104010922.gvmd3szqfda7hbe6@pacific.linksys.moosehall> Adam Spiers wrote: >Hi all, and happy 2018! > >After a chaotic holiday season, one of my first orders of business is >to take care of various administravia relating to the new Self-Healing >SIG. [snipped] > https://storyboard.openstack.org/#!/project/917 > >Contributions / feedback welcome on any of those. I'll be sending out >individual mails on some of those topics over the coming days and >weeks. The most urgent of these actions is to figure out the amount of time we need for a SIG session at the Dublin PTG, because Kendall is planning the PTG schedule and needs to know by next Monday (8th): https://storyboard.openstack.org/#!/story/2001429 Apparently the smallest session duration we can pick is half a day. My feeling is that at this early stage of the PTG, that should be more than enough. The main agenda items I can think of are: - Introduce more people into the SIG and promote its mission. - Gather more feedback on operator requirements and experiences. - Gather info from projects on existing integration points. - Start documenting self-healing capabilities which already exist. It would be easy to spend a whole week on these alone, but obviously most people will need to attend other sessions at the PTG so I don't want to create an uncomfortable clash by claiming too long a session for this SIG. Any other opinions on this before Monday deadline? Thanks! Adam From aspiers at suse.com Thu Jan 4 12:01:08 2018 From: aspiers at suse.com (Adam Spiers) Date: Thu, 4 Jan 2018 12:01:08 +0000 Subject: [Openstack-sigs] [self-healing] new #openstack-self-healing IRC channel In-Reply-To: <20180104005923.gsq3vyfa3qycjbep@pacific.linksys.moosehall> References: <20180104005923.gsq3vyfa3qycjbep@pacific.linksys.moosehall> Message-ID: <20180104120108.l5jjci5prt2oevzd@pacific.linksys.moosehall> Adam Spiers wrote: >Hi all, and happy 2018! > >After a chaotic holiday season, one of my first orders of business is >to take care of various administravia relating to the new Self-Healing >SIG. [snipped] I've just done the necessary ChanServ voodoo on FreeNode and submitted a couple of reviews to set up a new #openstack-self-healing IRC channel: https://review.openstack.org/#/c/531135/ https://review.openstack.org/#/c/531136/ since this was agreed worthwhile in both Denver and Sydney. I felt that #openstack-self-healing-sig was a bit long-winded I'm not religious about it; feel free to add your opinions via those reviews. Thanks! From tobias at citynetwork.se Fri Jan 5 14:01:41 2018 From: tobias at citynetwork.se (Tobias Rydberg) Date: Fri, 5 Jan 2018 15:01:41 +0100 Subject: [Openstack-sigs] [publiccloud-wg] Missing features work session Message-ID: Hi everyone, During our last meeting we decided to get together at IRC for a work session dedicated to get the "Missing features list" up to date, and take the fist steps converting items into a more official list at launchpad - where we have a project [1]. Would be awesome to see as many of you as possible joining this. Where: #openstack-publiccloud When: Wednesday 10th January 1400 UTC Agenda: https://etherpad.openstack.org/p/publiccloud-wg This first effort of its kind is as you can see at the same time as bi-weekly meetings. Please send feedback of that, I'm happy to setup another session just like this - at a time that suites you better! Hope to see you there! Regards, Tobias Rydberg Chair Public Cloud WG [1] https://launchpad.net/openstack-publiccloud-wg -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3945 bytes Desc: S/MIME Cryptographic Signature URL: From gr at ham.ie Mon Jan 8 15:18:07 2018 From: gr at ham.ie (Graham Hayes) Date: Mon, 8 Jan 2018 15:18:07 +0000 Subject: [Openstack-sigs] [self-healing][api] Common Healthcheck middleware Message-ID: Hi all, In Sydney in one of the Cloud Native sessions we talked about adding a common healthcheck to OpenStack services. I took a stab at writing up what we talked about, and what was covered later on in a different session, and have a spec up [1] to start the design work. If anyone who is interested could take a look and give feedback, I would appreciate it. I would like us to start prototyping this out as soon as we could. Thanks, - Graham 1 - https://review.openstack.org/#/c/531456/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: OpenPGP digital signature URL: From zhipengh512 at gmail.com Mon Jan 8 17:26:21 2018 From: zhipengh512 at gmail.com (Zhipeng Huang) Date: Tue, 9 Jan 2018 01:26:21 +0800 Subject: [Openstack-sigs] [ResMgmt SIG]Proposal to form Resource Management SIG Message-ID: Hi all, With the maturing of resource provider/placement feature landing in OpenStack in recent release, and also in light of Kubernetes community increasing attention to the similar effort, I want to propose to form a Resource Management SIG as a contact point for OpenStack community to communicate with Kubernetes Resource Management WG[0] and other related SIGs. The formation of the SIG is to provide a gathering of similar interested parties and establish an official channel. Currently we have already OpenStack developers actively participating in kubernetes discussion (e.g. [1]), we would hope the ResMgmt SIG could further help such activities and better align the resource mgmt mechanism, especially the data modeling between the two communities (or even more communities with similar desire). I have floated the idea with Jay Pipes and Chris Dent and received positive feedback. The SIG will have a co-lead structure so that people could spearheading in the area they are most interested in. For example for me as Cyborg dev, I will mostly lead in the area of acceleration[2]. If you are also interested please reply to this thread, and let's find a efficient way to form this SIG. Efficient means no extra unnecessary meetings and other undue burdens. [0] https://docs.google.com/document/d/1j3vrG6BgE0hUDs2e-1ZUegKN4W4Adb1B6oJ6j-4kyPU/edit?usp=sharing [1] https://github.com/kubernetes/community/pull/782 [2] https://github.com/kubernetes/kubernetes/labels/area%2Fhw-accelerators -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email: huangzhipeng at huawei.com Office: Huawei Industrial Base, Longgang, Shenzhen (Previous) Research Assistant Mobile Ad-Hoc Network Lab, Calit2 University of California, Irvine Email: zhipengh at uci.edu Office: Calit2 Building Room 2402 OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado -------------- next part -------------- An HTML attachment was scrubbed... URL: From ekcs.openstack at gmail.com Tue Jan 9 00:21:29 2018 From: ekcs.openstack at gmail.com (Eric K) Date: Mon, 08 Jan 2018 16:21:29 -0800 Subject: [Openstack-sigs] [self-healing] URGENT RFC: length of PTG session for self-healing SIG In-Reply-To: <20180104010922.gvmd3szqfda7hbe6@pacific.linksys.moosehall> References: <20180104005923.gsq3vyfa3qycjbep@pacific.linksys.moosehall> <20180104010922.gvmd3szqfda7hbe6@pacific.linksys.moosehall> Message-ID: Thanks Adam for helping us get organized in the new year. I agree that half a day is a good length at this stage. There would always be more to talk about, but a lot of it can happen in less centralized channels. Eric On 1/3/18, 5:09 PM, "Adam Spiers" wrote: >Adam Spiers wrote: >>Hi all, and happy 2018! >> >>After a chaotic holiday season, one of my first orders of business is >>to take care of various administravia relating to the new Self-Healing >>SIG. > >[snipped] > >> https://storyboard.openstack.org/#!/project/917 >> >>Contributions / feedback welcome on any of those. I'll be sending out >>individual mails on some of those topics over the coming days and >>weeks. > >The most urgent of these actions is to figure out the amount of time >we need for a SIG session at the Dublin PTG, because Kendall is >planning the PTG schedule and needs to know by next Monday (8th): > > https://storyboard.openstack.org/#!/story/2001429 > >Apparently the smallest session duration we can pick is half a day. >My feeling is that at this early stage of the PTG, that should be more >than enough. The main agenda items I can think of are: > >- Introduce more people into the SIG and promote its mission. > >- Gather more feedback on operator requirements and experiences. > >- Gather info from projects on existing integration points. > >- Start documenting self-healing capabilities which already exist. > >It would be easy to spend a whole week on these alone, but obviously >most people will need to attend other sessions at the PTG so I don't >want to create an uncomfortable clash by claiming too long a session >for this SIG. > >Any other opinions on this before Monday deadline? > >Thanks! >Adam > >_______________________________________________ >openstack-sigs mailing list >openstack-sigs at lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs From thierry at openstack.org Tue Jan 9 10:23:02 2018 From: thierry at openstack.org (Thierry Carrez) Date: Tue, 9 Jan 2018 11:23:02 +0100 Subject: [Openstack-sigs] [openstack-dev] [ResMgmt SIG]Proposal to form Resource Management SIG In-Reply-To: References: Message-ID: <466b3ca5-af1c-89aa-d040-e9ac8385a9ae@openstack.org> Zhipeng Huang wrote: > [...] > With the maturing of resource provider/placement feature landing in > OpenStack in recent release, and also in light of Kubernetes community > increasing attention to the similar effort, I want to propose to form a > Resource Management SIG as a contact point for OpenStack community to > communicate with Kubernetes Resource Management WG[0] and other related > SIGs. > [...] When ready, please propose a change to the governance-sigs repository, adding the proposed SIG to the sigs.yaml file: https://git.openstack.org/cgit/openstack/governance-sigs/tree/sigs.yaml -- Thierry Carrez (ttx) From zhipengh512 at gmail.com Tue Jan 9 16:50:41 2018 From: zhipengh512 at gmail.com (Zhipeng Huang) Date: Wed, 10 Jan 2018 00:50:41 +0800 Subject: [Openstack-sigs] [openstack-dev] [ResMgmt SIG]Proposal to form Resource Management SIG In-Reply-To: <466b3ca5-af1c-89aa-d040-e9ac8385a9ae@openstack.org> References: <466b3ca5-af1c-89aa-d040-e9ac8385a9ae@openstack.org> Message-ID: THX Thierry, will keep this in mind :) On Tue, Jan 9, 2018 at 6:23 PM, Thierry Carrez wrote: > Zhipeng Huang wrote: > > [...] > > With the maturing of resource provider/placement feature landing in > > OpenStack in recent release, and also in light of Kubernetes community > > increasing attention to the similar effort, I want to propose to form a > > Resource Management SIG as a contact point for OpenStack community to > > communicate with Kubernetes Resource Management WG[0] and other related > > SIGs. > > [...] > > When ready, please propose a change to the governance-sigs repository, > adding the proposed SIG to the sigs.yaml file: > > https://git.openstack.org/cgit/openstack/governance-sigs/tree/sigs.yaml > > -- > Thierry Carrez (ttx) > > _______________________________________________ > openstack-sigs mailing list > openstack-sigs at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs > -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email: huangzhipeng at huawei.com Office: Huawei Industrial Base, Longgang, Shenzhen (Previous) Research Assistant Mobile Ad-Hoc Network Lab, Calit2 University of California, Irvine Email: zhipengh at uci.edu Office: Calit2 Building Room 2402 OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado -------------- next part -------------- An HTML attachment was scrubbed... URL: From stig.openstack at telfer.org Tue Jan 9 19:45:52 2018 From: stig.openstack at telfer.org (Stig Telfer) Date: Tue, 9 Jan 2018 19:45:52 +0000 Subject: [Openstack-sigs] [scientific] IRC meeting today: SGX security and Ironic, RCUK cloud workshop Message-ID: <9D5DF709-B703-4D64-B0C7-A49C06A30566@telfer.org> Hello All - We have an IRC meeting in channel #openstack-meeting at 2100 UTC today (just over an hour’s time). All are welcome. Today’s agenda is here: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_January_9th_2018 We have Andrey Brito from the Federal University of Campina Grande discussing some of his work using Intel SGX for strengthening the security of Ironic compute instances. We also have a roundup of yesterday’s RCUK Cloud Workshop in London. Plus, inevitably, a roundup of people’s experiences of the impact of the Spectre/Meltdown remediations. Cheers, Stig -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Tue Jan 9 20:30:06 2018 From: kennelson11 at gmail.com (Kendall Nelson) Date: Tue, 09 Jan 2018 20:30:06 +0000 Subject: [Openstack-sigs] [First Contact] [SIG] Rocky PTG Planning Message-ID: Hello Everyone :) I put us down for one day at the PTG and wanted to get a jump start on discussion planning. I created an etherpad[1] and wrote down some topics to get the ball rolling. Please feel free to expand on them if there are other details you feel we need to talk about or add new ones as you see fit. Also, please add your name to the 'Planned Attendance' section if you are thinking of attending. Thanks! -Kendall (diablo_rojo) [1] https://etherpad.openstack.org/p/FC_SIG_Rocky_PTG -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengh512 at gmail.com Thu Jan 11 07:31:05 2018 From: zhipengh512 at gmail.com (Zhipeng Huang) Date: Thu, 11 Jan 2018 15:31:05 +0800 Subject: [Openstack-sigs] [publiccloud-wg]Public Cloud Feature List Hackathon Day 2 Message-ID: Hi Folks, Today we are gonna continue to comb through the public cloud feature list[0] as we did yesterday. Please join the discussion at #openstack-publiccloud starting from UTC1400. [0]https://docs.google.com/spreadsheets/d/1Mf8OAyTzZxCKzYHMgBl-QK_2- XSycSkOjqCyMTIedkA/edit?usp=sharing -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email: huangzhipeng at huawei.com Office: Huawei Industrial Base, Longgang, Shenzhen (Previous) Research Assistant Mobile Ad-Hoc Network Lab, Calit2 University of California, Irvine Email: zhipengh at uci.edu Office: Calit2 Building Room 2402 OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengh512 at gmail.com Thu Jan 11 08:38:34 2018 From: zhipengh512 at gmail.com (Zhipeng Huang) Date: Thu, 11 Jan 2018 16:38:34 +0800 Subject: [Openstack-sigs] [publiccloud-wg]Rocky PTG Planning Etherpad Message-ID: Hi Team, I drafted an initial framework of the etherpad we could use for Rocky PTG in Dublin. You are more than welcomed to provide input: https://etherpad.openstack.org/p/publiccloud-wg-ptg-rocky -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email: huangzhipeng at huawei.com Office: Huawei Industrial Base, Longgang, Shenzhen (Previous) Research Assistant Mobile Ad-Hoc Network Lab, Calit2 University of California, Irvine Email: zhipengh at uci.edu Office: Calit2 Building Room 2402 OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado -------------- next part -------------- An HTML attachment was scrubbed... URL: From cdent+os at anticdent.org Thu Jan 11 17:29:26 2018 From: cdent+os at anticdent.org (Chris Dent) Date: Thu, 11 Jan 2018 17:29:26 +0000 (GMT) Subject: [Openstack-sigs] [all][api] POST /api-sig/news Message-ID: Greetings OpenStack community, Wide-ranging conversations in the API-SIG meeting today [7]. We started out discussing techniques for driving the adoption of the guidelines published by the group. Two ideas received most of the attention: * Provide guidance on the tools available to make it easier to align new API projects with the guidelines, from the outset. The idea of an example or cookbook project was mooted, but the number of options, variables, and opinions that such an effort would face killed this idea. Better, perhaps, are recommend tools for addressing common problems. * Making use of the OpenStack-wide goals [8] process to encourage working towards consistency. Monty has made a proposal [9] based on the rfc5988 link guidance newly listed below. Then we talked about work in progress to establish a common health check system across the OpenStack services. There's an oslo-spec [10] in progress. The API-SIG's involvement is to help make sure the HTTP side of things is handled well. As always if you're interested in helping out, in addition to coming to the meetings, there's also: * The list of bugs [5] indicates several missing or incomplete guidelines. * The existing guidelines [2] always need refreshing to account for changes over time. If you find something that's not quite right, submit a patch [6] to fix it. * Have you done something for which you think guidance would have made things easier but couldn't find any? Submit a patch and help others [6]. # Newly Published Guidelines None this week. # API Guidelines Proposed for Freeze Guidelines that are ready for wider review by the whole community. * Expand note about rfc5988 link header https://review.openstack.org/#/c/531914/ # Guidelines Currently Under Review [3] * Add guideline on exposing microversions in SDKs https://review.openstack.org/#/c/532814/ * 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 * WIP: Add API-schema guide (still being defined) https://review.openstack.org/#/c/524467/ # Highlighting your API impacting issues If you seek further review and insight from the API SIG about APIs that you are developing or changing, 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 SIG mission and the work we do, see our wiki page [4] and guidelines [2]. Thanks for reading and see you next week! # References [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://wiki.openstack.org/wiki/API_SIG [5] https://bugs.launchpad.net/openstack-api-wg [6] https://git.openstack.org/cgit/openstack/api-wg [7] http://eavesdrop.openstack.org/meetings/api_sig/2018/api_sig.2018-01-11-15.59.html [8] https://governance.openstack.org/tc/goals/index.html [9] https://review.openstack.org/#/c/532627/ [10] https://review.openstack.org/#/c/531456/ Meeting Agenda https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda Past Meeting Records http://eavesdrop.openstack.org/meetings/api_sig/ Open Bugs https://bugs.launchpad.net/openstack-api-wg -- Chris Dent (⊙_⊙') https://anticdent.org/ freenode: cdent tw: @anticdent From stig.openstack at telfer.org Tue Jan 16 23:06:22 2018 From: stig.openstack at telfer.org (Stig Telfer) Date: Tue, 16 Jan 2018 23:06:22 +0000 Subject: [Openstack-sigs] [scientific] IRC meeting Wednesday 1100UTC: Bare metal Magnum Message-ID: Hi All - We have an IRC meeting on Wednesday at 1100 UTC in channel #openstack-meeting. Everyone is welcome. Agenda is here: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_January_17th_2018 This week we have two main items on the agenda: Our guest is Spyros Trigazis from CERN, who will be discussing latest improvements in Magnum’s support for research computing use cases, and in particular bare metal use cases. We’d also like to kick off some discussion around PTG planning. Cheers, Stig -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry at openstack.org Thu Jan 18 10:26:00 2018 From: thierry at openstack.org (Thierry Carrez) Date: Thu, 18 Jan 2018 11:26:00 +0100 Subject: [Openstack-sigs] [all] Dublin PTG proposed track layout Message-ID: <056b20b3-ded0-5ef5-e4a7-8b9bf370f9a8@openstack.org> Hi SIGs, The proposed track layout for the PTG was posted. Please see this message to openstack-dev: http://lists.openstack.org/pipermail/openstack-dev/2018-January/126335.html A number of SIGs will meet in Dublin. The proposed allocation takes into account the estimated group size and number of days that was communicated to Kendall and I by the SIG leads. We'd like to publish this schedule on the event website ASAP, so please check that it still matches your needs (number of days, room size vs. expected attendance) and does not create too many conflicts. There are lots of constraints, so we can't promise we'll accommodate your remarks, but we'll do our best. Cheers, -- Thierry Carrez (ttx) From aspiers at suse.com Fri Jan 19 10:13:47 2018 From: aspiers at suse.com (Adam Spiers) Date: Fri, 19 Jan 2018 10:13:47 +0000 Subject: [Openstack-sigs] [all] Dublin PTG proposed track layout In-Reply-To: <056b20b3-ded0-5ef5-e4a7-8b9bf370f9a8@openstack.org> References: <056b20b3-ded0-5ef5-e4a7-8b9bf370f9a8@openstack.org> Message-ID: <20180119101347.f5qplouv4xyqqcrv@pacific.linksys.moosehall> Thierry Carrez wrote: >Hi SIGs, > >The proposed track layout for the PTG was posted. Please see this >message to openstack-dev: > >http://lists.openstack.org/pipermail/openstack-dev/2018-January/126335.html > >A number of SIGs will meet in Dublin. The proposed allocation takes into >account the estimated group size and number of days that was >communicated to Kendall and I by the SIG leads. We'd like to publish >this schedule on the event website ASAP, so please check that it still >matches your needs (number of days, room size vs. expected attendance) >and does not create too many conflicts. There are lots of constraints, >so we can't promise we'll accommodate your remarks, but we'll do our best. Looks fine from my side. Thanks Kendall and Thierry! From andrea.frittoli at gmail.com Fri Jan 19 17:17:22 2018 From: andrea.frittoli at gmail.com (Andrea Frittoli) Date: Fri, 19 Jan 2018 17:17:22 +0000 Subject: [Openstack-sigs] [Openstack-operators] [QA] Proposal for a QA SIG In-Reply-To: References: <0873dec8-624d-b32a-5608-74cc74c02005@openstack.org> Message-ID: Hello everyone, After a long holiday break I would like to resume work on bringing the QA SIG to life. I proposed a QA SIG session [0] for the next PTG, but I'm not sure the right audience will be in Dublin. Could you please reply if you are interested but won't be in Dublin or add your name to the etherpad if you plan to be there and attend? If we have enough attendance in Dublin we can kick off there - otherwise I will setup a meeting with all interested parties (IRC meeting probably, but other options are possible). Thank you! Andrea Frittoli (andreaf) [0] https://etherpad.openstack.org/p/qa-rocky-ptg On Mon, Nov 20, 2017 at 9:15 AM Thierry Carrez wrote: > Rochelle Grober wrote: > > Thierry Carrez wrote: > >> One question I have is whether we'd need to keep the "QA" project team > at > >> all. Personally I think it would create confusion to keep it around, > for no gain. > >> SIGs code contributors get voting rights for the TC anyway, and SIGs > are free > >> to ask for space at the PTG... so there is really no reason (imho) to > keep a > >> "QA" project team in parallel to the SIG ? > > > > Well, you can get rid of the "QA Project Team" but you would then need > to replace it with something like the Tempest Project, or perhaps the Test > Project. You still need a PTL and cores to write, review and merge tempest > fixes and upgrades, along with some of the tests. The Interop Guideline > tests are part of Tempest because being there provides oversight on the > style and quality of the code of those tests. We still need that. > > SIGs can totally produce some code (and have review teams), but I agree > that in this case this code is basically a part of "the product" (rather > than a tool produced by guild of practitioners) and therefore makes > sense to be kept in an upstream project team. Let's keep things the way > they are, while we work out other changes that may trigger other > organizational shuffles (like reusing our project infrastructure beyond > just OpenStack). > > I wonder if we should not call the SIG under a different name to reduce > the confusion between QA-the-project-team and QA-the-SIG. Collaborative > Testing SIG? > > -- > Thierry Carrez (ttx) > > _______________________________________________ > openstack-sigs mailing list > openstack-sigs at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stig.openstack at telfer.org Tue Jan 23 17:59:05 2018 From: stig.openstack at telfer.org (Stig Telfer) Date: Tue, 23 Jan 2018 17:59:05 +0000 Subject: [Openstack-sigs] [scientific] IRC meeting today 2100UTC: PTG and Summit Message-ID: <274ED39E-675C-4FE3-83B1-EB40E3C76CF8@telfer.org> Hi All - We have an IRC meeting today at 2100UTC (about 3 hours time) in channel #openstack-meeting. Everyone is welcome. The agenda items for today focus on planning SIG activities for upcoming events - PTG and Summit. Full agenda is here: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_January_23rd_2018 Cheers, Stig -------------- next part -------------- An HTML attachment was scrubbed... URL: From Arkady.Kanevsky at dell.com Mon Jan 29 21:36:21 2018 From: Arkady.Kanevsky at dell.com (Arkady.Kanevsky at dell.com) Date: Mon, 29 Jan 2018 21:36:21 +0000 Subject: [Openstack-sigs] PWG at IRC Message-ID: I am at IRC in case we want to discuss things. If not we can cancel them all and discuss at PTG in Dublin Arkady Kanevsky, Ph.D. Director of SW Development Dell EMC Service Provider BU Dell Inc. One Dell Way, MS PS2-91 Round Rock, TX 78682, USA Phone: 512 723 5264 -------------- next part -------------- An HTML attachment was scrubbed... URL: From stig.openstack at telfer.org Tue Jan 30 22:42:12 2018 From: stig.openstack at telfer.org (Stig Telfer) Date: Tue, 30 Jan 2018 22:42:12 +0000 Subject: [Openstack-sigs] [scientific] IRC meeting: preemptible instances and upcoming events Message-ID: <304614B7-A3FC-45EC-9BCD-2EFAE1288B72@telfer.org> Hi All - We have a Scientific SIG IRC meeting on Wednesday at 1100 UTC in channel #openstack-meeting. Everyone is welcome. This week’s agenda includes an update on recent work towards preemptible “spot” instances. We also have a few events on the calendar to discuss and plan for. Full agenda is here: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_January_31st_2018 Best wishes Stig -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Sayers at sib.swiss Wed Jan 31 12:48:41 2018 From: Kevin.Sayers at sib.swiss (Kevin Sayers) Date: Wed, 31 Jan 2018 13:48:41 +0100 Subject: [Openstack-sigs] [scientific] federation of multi-site workflow Message-ID: <155711dec1d0e89c7ba9e766d5a67feb@bell.isb-sib.ch> I am working to develop strategies for scientific edge computing. OpenStack federation seems like a possible approach. I am interested if anyone has experiences they are willing to share regarding setting up a federation across HPC clusters/private clouds at different universities for execution of scientific workflows. Best, Kevin -- Kevin Sayers Workflow Developer SPHN Data Coordination Centre +41 61 633 29 68 kevin.sayers at sib.swiss https://dcc.sib.swiss From jm6819 at att.com Wed Jan 31 23:00:56 2018 From: jm6819 at att.com (MCCABE, JAMEY A) Date: Wed, 31 Jan 2018 23:00:56 +0000 Subject: [Openstack-sigs] [LCOO][RBAC] Topical session 2/1 1200 UTC Message-ID: <6146864A3C560F4BBA6764F9A4188941548010DD@MOSTLS1MSGUSRFA.ITServices.sbc.com> A topical session on Multi-cloud Security will be at 1200 UTC on Thursday 2/1. This is a type of LCOO working group discussion forum we conduct on a monthly basis. Agenda and logistics to join can be found at https://openstack-lcoo.atlassian.net/wiki/spaces/LCOO/pages/65175564/ -------------- next part -------------- An HTML attachment was scrubbed... URL: