Re: [openstack-dev] [tripleo] puppet5 has broken the master gate
Hello Alex, On Tue, Nov 13, 2018 at 9:53 AM Alex Schultz wrote: > > Just a heads up but we recently updated to puppet5 in the master > dependencies. It appears that this has completely hosed the master > scenarios and containers-multinode jobs. Please do recheck/approve > anything until we get this resolved. > > See https://bugs.launchpad.net/tripleo/+bug/1803024 > > I have a possible fix (https://review.openstack.org/#/c/617441/) but > it's probably a better idea to roll back the puppet package if > possible. > In RDO, we have reverted Revert "Stein: push puppet 5.5.6" -> https://review.rdoproject.org/r/#/c/17333/1 Thanks for the heads up! Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [tripleo][openstack-ansible] Updates on collaboration on os_tempest role
Hello, During the starting of Denver 2018 PTG [1]., We started collaborating towards using the openstack-ansible-os_tempest role [2] as a unified tempest role in TripleO and openstack-ansible project within OpenStack community. It will help us to improve the testing strategies between two projects which can be further expanded to other OpenStack deployment tools. We will be sharing bi-weekly updates through mailing lists. We are tracking/planning all the work here: Proposal doc: https://etherpad.openstack.org/p/ansible-tempest-role Work item collaboration doc: https://etherpad.openstack.org/p/openstack-ansible-tempest Here is the update till now: openstack-ansible-os_tempest project: * Enable stackviz support - https://review.openstack.org/603100 * Added support for installing tempest from distro - https://review.openstack.org/591424 * Fixed missing ; from if statement in tempest_run - https://review.openstack.org/614521 * Added task to list tempest plugins - https://review.openstack.org/615837 * Remove apt_package_pinning dependency from os_tempest role - https://review.openstack.org/609992 * Enable python-tempestconf support - https://review.openstack.org/612968 Support added to openstack/rpm-packaging project (will be consumed in os_tempest role): * Added spec file for stackviz - https://review.openstack.org/609337 * Add initial spec for python-tempestconf - https://review.openstack.org/598143 Upcoming improvements: * Finish the integration of python-tempestconf in os_tempest role. Have queries, Feel free to ping us on #tripleo or #openstack-ansible channel. Links: [1.] http://lists.openstack.org/pipermail/openstack-dev/2018-August/133119.html [2.] http://git.openstack.org/cgit/openstack/openstack-ansible-os_tempest Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tripleo][ui][tempest][oooq] Refreshing plugins from git
Hello Honza, On Thu, Oct 18, 2018 at 6:15 PM Bogdan Dobrelya wrote: > > On 10/18/18 2:17 AM, Honza Pokorny wrote: > > Hello folks, > > > > I'm working on the automated ui testing blueprint[1], and I think we > > need to change the way we ship our tempest tests. > > > > Here is where things stand at the moment: > > > > * We have a kolla image for tempest > > * This image contains the tempest rpm, and the openstack-tempest-all rpm > > * The openstack-tempest-all package in turn contains all of the > >openstack tempest plugins > > * Each of the plugins is shipped as an rpm > > > > So, in order for a new test in tempest-tripleo-ui to appear in CI we > > have to go through at least the following tests: > > > > * New tempest-tripleo-ui rpm > > * New openstack-tempest-all rpm > > * New tempest kolla image > > > > This could easily take a week, if not more. > > > > What I would like to build is something like the following: > > > > * Add an option to the tempest-setup.sh script in tripleo-quickstart to > >refresh all tempest plugins from git before running any tests > > * Optionally specify a zuul change for any of the plugins being > >refreshed > > * Hook up the test job to patches in tripleo-ui (which tests in > >tempest-tripleo-ui are testing) so that I can run a fix and its test > >in a single CI job I have added a patch in TripleO Quickstart extras Validate-tempest role: https://review.openstack.org/#/c/612377/ to install any tempest plugin from git and zuul will pick the specific change in the gates. Here is the patch on how to test it with FS: https://review.openstack.org/612386 Basically in any FS, we can add following lines tempest_format: venv tempest_plugins_git: - 'https://git.openstack.org/openstack/tempest-tripleo-ui.git' the respective FS related job will install the tempest plugin and we can also use test_white_regex: to trigger the tempest tests. I think it will solve the problem. Thanks Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [TripleO] Regarding dropping Ocata related jobs from TripleO
Hello, As Ocata release is already EOL on 27-08-2018 [1]. In TripleO, we are running Ocata jobs in TripleO CI and in promotion pipelines. Can we drop it all the jobs related to Ocata or do we need to keep some jobs to support upgrades in CI? Links: [1.] https://releases.openstack.org/ Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [TripleO][kolla-ansible][DevStack][Tempest][openstack-ansible] Collaborate towards creating a unified ansible tempest role in openstack-ansible project
Hello, Few days back, Alex initiated the conversation about sharing ansible roles [1] across different projects. It is a nice idea and it brings a lot of collaboration among different projects with in OpenStack Community. Since Tempest provides the Integration test suite for validating any deployed OpenStack cloud. We uses ansible roles for installing/configuring/running Tempest starting from DevStack Tempest Zuul based CI jobs to TripleO, OpenStack-ansible spanning to kolla-ansible projects. Across all these deployments tools have their own roles for installing/configuring/running Tempest but doing similar tasks. I think it's a good opportunity for us to collaborate towards creating an unified ansible role in openstack-ansible project by re-using and modifying the stuff and then aggregating into openstack-ansible-os_tempest [2] project. I have summarized the problem statement and requirements on this etherpad [3]. Feel free to add your requirements and questions for the same on the etherpad so that we can shape the unified ansible role in a better way. Links: 1. http://lists.openstack.org/pipermail/openstack-dev/2018-August/133119.html 2. https://github.com/openstack/openstack-ansible-os_tempest 3. https://etherpad.openstack.org/p/ansible-tempest-role Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [openstack-ansible][kolla-ansible][tripleo] ansible roles: where they live and what do they do
the os_nova role and pass in
> > > like install: false, service: false, config_dir:
> > > /my/special/location/, config_data: {...} and it spit out the configs.
> > > Then my roles would actually leverage these via containers/etc. Of
> > > course most of this goes away if we had a unified (not file based)
> > > configuration method across all services (openstack and non-openstack)
> > > but we don't. :D
> > >
> >
> > I like your idea here Alex.
> > So having a role for each of these steps is too much management I agree,
> > however
> > establishing a pattern of using tasks for each step may be a really good
> > way to cleanly handle this.
> >
> > Are you saying something like the following?
> >
> > openstack-nova-role/
> > * * /tasks/
> > * * /tasks/install.yml
> > * * /tasks/service.yml
> > * */tasks/config.yml
> > * */taks/main.yml
> > ---
> > # main.yml
> >
> > include: install.yml
> > when: nova_install|bool
> >
> > include: service.yml
> > when: nova_service|bool
> >
> > include: config.yml
> > when: nova_config.yml
> > ----------
> >
> > Interested in anything other than tags :)
> > Thanks
> >
> This is basically what I do with roles i write, allow the user to decide to
> step
> over specific tasks. For example, I have created nodepool_task_manager
> variable
> with the following:
>
>
> http://git.openstack.org/cgit/openstack/ansible-role-nodepool/tree/defaults/main.yaml#n16
>
> http://git.openstack.org/cgit/openstack/ansible-role-nodepool/tree/tasks/main.yaml
>
> Been using it for a few years now, works much better then tags for me. The
> phases are pre, install, configure, service right now.
Thanks Alex for starting the conversation.
There are few other ansible roles for tempest and it's friends (stackviz)
https://github.com/redhat-openstack/infrared/tree/master/plugins/tempest
https://github.com/openstack/tempest/tree/master/roles
It would be a great idea to improve ansible-role-os_tempest role and
modify it such a way that it can be re-used by anyone.
I will start working on this.
Thanks,
Chandan Kumar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Summit][qa] Vancouver Summit 2018 QA Recap
in QA and we all agreed on below points: > - QA will keep doing the same number of stable branches support as it is > doing now. Means support till "Maintained" phase branches. EM branch will > not be in scope of guaranteed support of QA. > - As Tempest is branchless, it should work for EM phase branches also but if > anything new changes break EM branch testing then we stopped testing master > Tempest on EM branches. > Matt has already pushed the patch to document the above agreement [3]. Thanks > for doing good documentation always :), > > Eris > === > Spec- https://review.openstack.org/#/c/443504/ > It came up in feedback sessions also and people really want to see some > progress on this. We have spec under review for that and need more volunteer > to drive this forward. I will also check with SamP on this. Other than that > there was not much discussion/progress on this in summit. > > ACTION ITEM: gmann to push the spec review in QA team and more follow up > about progress. > > > [1] https://etherpad.openstack.org/p/YVR-rocky-default-roles > [2] https://etherpad.openstack.org/p/YVR-extended-maintenance > [3] https://review.openstack.org/#/c/570620/ Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [qa] Office Hours Report 2018-02-01
Hello, Thanks everyone for attending QA office hour. Since It's the starting of the year so attendance is low. We managed to triaged some bugs opened/changed in last 14 days. The IRC report [0] and full log [1] are available through meetbot. bug 1745871 in Patrole "RBAC tests for group type specs" https://bugs.launchpad.net/patrole/+bug/1745871 Status: confirmed Related Review: https://review.openstack.org/#/c/525589/ 1743688 in congress "Tempest unable to detect service availability properly, causing congress tests to fail" https://bugs.launchpad.net/devstack/+bug/1743688 Status: In Progress bug 1744096 in devstack "CentOS install fails with 'python3: command not found'" https://bugs.launchpad.net/devstack/+bug/1744096 status: In Progress bug 1746687 in tempest "tempest plugins should be loaded though configuration" https://bugs.launchpad.net/tempest/+bug/1746687 Status: Invalid Above bug leads to interesting discussion on how to ship tempest plugins with kolla tempest containers Below are the remarks: * Bundle all the plugins in a single containers. * User service_available config params to enable or disable a plugin while using it * In tempest we have blacklist or whitelist test params to play with tests. bug 1745322 in tempest "stackviz folder does not show up in logs on zuulv3 native jobs" https://bugs.launchpad.net/tempest/+bug/1745322 Status: Fix committed Review: https://review.openstack.org/#/c/539146/ bug 1745307 in tempest "Group related cases would fail if driver has group spec check" https://bugs.launchpad.net/tempest/+bug/1745307 Status: in-progress Review: https://review.openstack.org/537784 https://bugs.launchpad.net/tempest/+bug/1660612 bug 1660612 in neutron "Tempest full jobs time out on execution" status: New Comments: related fix https://review.openstack.org/#/c/536598/ is not ok. it changes existing tox envs which has an impact on existing jobs it make it all scenario to run parallel, but tempest full deos not run scenario tests. Links: [0]. http://eavesdrop.openstack.org/meetings/qa_office_hour/2018/qa_office_hour.2018-02-01-09.05.txt [1]. http://eavesdrop.openstack.org/meetings/qa_office_hour/2018/qa_office_hour.2018-02-01-09.05.log.html Thanks for reading. Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [qa][all] QA Office Hours on 01st Feb, 2018
Hello All, a kind reminder that tomorrow at 9:00 UTC we'll start office hours for the QA team in the #openstack-qa channel. Please join us with any question/comment you may have related to tempest plugin split community goal, tempest and others QA tools. We'll triage bugs for QA projects from the past 7 days and then extend the time frame if there is time left. Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [qa][all] QA Office Hours on 18th Jan, 2018
Hello All, A kind reminder that tomorrow at 9:00 UTC we'll start office hours for the QA team in the #openstack-qa channel. Please join us with any question/comment you may have related to tempest plugin split community goal, tempest and others QA tools. We'll triage bugs for QA projects from the past 7 days and then extend the time frame if there is time left. Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] [tc] Community Goals for Rocky
Hello Em On Tue, Jan 16, 2018 at 9:59 PM, Emilien Macchi <emil...@redhat.com> wrote: > Here's an update so we can hopefully, as a community, take a decision > in the next days or so. > > > * Migration to StoryBoard > > Champion: Kendall Nelson > https://review.openstack.org/#/c/513875/ > Some projects already migrated, some projects will migrate soon but > there is still a gap of things that prevents some projects to not > migrate. > See > https://storyboard.openstack.org/#!/search?tags=blocking-storyboard-migration > For that reason, we are postponing this goal to later but work needs > to keep going to make that happen one day. > > > * Remove mox > > Champion: Sean McGinnis (unless someone else steps up) > https://review.openstack.org/#/c/532361/ > This goal is to clean some technical debt in the code. > It remains a good candidate for Queens. > May I step up for this goal for Rocky release? I am currently involved with Tempest plugin split goal in Queens Release. I wanted to help on this one. Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [infra][tempest][devstack][congress] tempest.config.CONF.service_available changed on Jan 2/3?
Hello Eric, On Sat, Jan 6, 2018 at 4:46 AM, Eric K <ekcs.openst...@gmail.com> wrote: > Seems that sometime between 1/2 and 1/3 this year, > tempest.config.CONF.service_available.aodh_plugin as well as > ..service_available.mistral became unavailable in congress dsvm check/gate > job. [1][2] > > I've checked the changes that went in to congress, tempest, devstack, > devstack-gate, aodh, and mistral during that period but don't see obvious > causes. Any suggestions on where to look next to fix the issue? Thanks > very much! > The aodh tempest plugin [https://review.openstack.org/#/c/526299/] is moved to telemetry-tempest-plugin [https://github.com/openstack/telemetry-tempest-plugin]. I have sent a patch to Congress project to fix the issue: https://review.openstack.org/#/c/531534/ The mistral bundled intree tempest plugin [https://review.openstack.org/#/c/526918/] is also moved to mistral-tempest-plugin repo [https://github.com/openstack/mistral-tempest-plugin] Tests are moved to a new repo as a part of Tempest Plugin Split goal [https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html]. Feel free to consume the new tempest plugin and let me know if you need any more help. Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [qa] Office Hours Report 2018-01-04
Hello, Thanks everyone for attending QA office hour. Since It's the starting of the year so attendance is low. We managed to triaged some bugs opened/changed in last 14 days. The IRC report [0] and full log [1] are available through meetbot. **Bug Traiged Summary** * Bug #1740194 in devstack: "Apache2 unable to start as 2 MPM modules enabled on Fedora 27" Status: Confirmed, Related Review: https://review.openstack.org/#/c/527048/ https://bugs.launchpad.net/devstack/+bug/1740194 * Bug #1740480 in devstack: "502 Proxy Error" Status: New, Action: Need help in traiging https://bugs.launchpad.net/devstack/+bug/1740480 * Bug #1740920 in devstack: "stable/newton branch does not work because keystone does not have stable/newton branch" Status: Invalid https://bugs.launchpad.net/devstack/+bug/1740920 * Bug #1741097 in devstack: "Installing pip fails on RHEL 7.4 with SSL error" status: In Progress, Related Review: https://review.openstack.org/#/c/530991/ https://bugs.launchpad.net/devstack/+bug/1741097 * Bug #1740544 in tempest: "Volume retype fails when migration occurs" Status: confirmed https://bugs.launchpad.net/tempest/+bug/1740544 * Bug #1739829 in tempest: "tempest-full job failing in stable/pike with 404 from keystone during tempest verify-config" Status: Confirmed, Related Review: https://review.openstack.org/#/c/530915/ (Needs to be backported for stable branches) https://bugs.launchpad.net/tempest/+bug/1739829 * Bug #1740258 in tempest: "[scenario]/img_dir is deprecated but required" Status: Undecided, Action: Needs discussion https://bugs.launchpad.net/tempest/+bug/1740258 Links: [0]. http://eavesdrop.openstack.org/meetings/qa_office_hours/2018/qa_office_hours.2018-01-04-09.02.html [1]. http://eavesdrop.openstack.org/meetings/qa_office_hours/2018/qa_office_hours.2018-01-04-09.02.log.html Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [qa][all] QA Office Hours on 04th Jan, 2018
Hello All, a kind reminder that tomorrow at 9:00 UTC we'll start office hours for the QA team in the #openstack-qa channel. Please join us with any question/comment you may have related to tempest plugin split community goal, tempest and others QA tools. We'll triage bugs for QA projects from the past 7 days and then extend the time frame if there is time left. Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [qa] Office Hours Report 2017-12-21
Hello, Thanks everyone for attending QA office hour. The IRC report [0] and full log [1] are available through meetbot. We have triaged 3 bugs and talks about some reviews, As below is the report. * Bug #1736988 in devstack: "using long-deprecated keystonemiddleware options" https://bugs.launchpad.net/devstack/+bug/1736988 Status: Invalid, transferred to Keystone * Bug #1738938 in devstack: ""[: ==: unary operator expected" when running unstack.sh" https://bugs.launchpad.net/devstack/+bug/1738938 Status: Fixed in progress. *Bug #1737634 in tempest: "ImagesTestJSON.test_delete_saving_image can wait for image status SAVING when the snapshot is already ACTIVE" https://bugs.launchpad.net/tempest/+bug/1737634 Status: Confirmed, Tagged as low-hanging-fruit Discussions on review: * Remove jobs from tempest-lib as repo is deprecated: https://review.openstack.org/#/c/529524/ * Add profiler support into Tempest - https://review.openstack.org/#/c/523935/ Links: [0] http://eavesdrop.openstack.org/meetings/office_hours/2017/office_hours.2017-12-21-09.01.html [1] http://eavesdrop.openstack.org/meetings/office_hours/2017/office_hours.2017-12-21-09.01.log.html Thanks for reading, Happy Holidays, see ya next year :-) Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [qa][all] QA Office Hours on 21st Dec, 2017
Hello All, a kind reminder that tomorrow at 9:00 UTC we'll start office hours for the QA team in the #openstack-qa channel. Please join us with any question/comment you may have related to tempest plugin split community goal, tempest and others QA tools. We'll triage bugs for QA projects from the past 7 days and then extend the time frame if there is time left. Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [QA] Office Hours report 2017-12-07
Hello, Thanks everyone for attending QA office hour. The IRC report [0] and full log [1] are available through meetbot. Below is the list of 10 bugs traiged and discussed during office hour, opened in last 14 days. * Bug #1735667 in StackViz: "Use stestr instead of testrepository" https://bugs.launchpad.net/stackviz/+bug/1735667 * Bug #1733983 in os-testr: "Tempest reports 'missing Worker 1!'" https://bugs.launchpad.net/os-testr/+bug/1733983 * Bug #1736385 in grenade: "placement is not being properly restarted in grenade (pike to master)" https://bugs.launchpad.net/grenade/+bug/1736385 * Bug #1734510 in devstack: "devstack pike: Error: No sql_connection parameter is established" https://bugs.launchpad.net/devstack/+bug/1734510 * Bug #1735097 in devstack: "Devstack depends on running mysql on ubuntu 16.04" https://bugs.launchpad.net/devstack/+bug/1735097 * Bug #1736385 in devstack: "placement is not being properly restarted in grenade (pike to master)" https://bugs.launchpad.net/devstack/+bug/1736385 * Bug #1736776 in devstack: "DevStack in DevStack" https://bugs.launchpad.net/devstack/+bug/1736776 * Bug #1506215 in tempest: "--regex and --blacklist_file does not work together" https://bugs.launchpad.net/tempest/+bug/1506215 * Bug #1734636 in tempest: "test_get_service_by_volume_host_name failed with "cinder-volume not found on host #DEFAULT" error" https://bugs.launchpad.net/tempest/+bug/1734636 * Bug #1734776 in tempest: "Tempest volume tests hardcoded for tenant isolation" https://bugs.launchpad.net/tempest/+bug/1734776 Links: [0] http://eavesdrop.openstack.org/meetings/office_hours/2017/office_hours.2017-12-07-09.00.html [1] http://eavesdrop.openstack.org/meetings/office_hours/2017/office_hours.2017-12-07-09.00.log.html Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [qa][all] QA Office Hours on 07th Dec, 2017
Hello All, a kind reminder that tomorrow at 9:00 UTC we'll start office hours for the QA team in the #openstack-qa channel. Please join us with any question/comment you may have related to tempest plugin split community goal, tempest and others QA tools. We'll triage bugs for QA projects from the past 7 days and then extend the time frame if there is time left. Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [all] [tc] Tempest Plugin Split Goal Queens-2 Update
Hello, As Queens Milestone 2 approaches its end, here is the second iteration of updates on Queens Tempest Plugin Split community goal [1]. **Not Started** Congress ec2-api freezer mistral monasca senlin tacker Telemetry Trove Vitrage ** In Progress ** Cinder Heat Ironic magnum manila Neutron murano networking-l2gw octavia ** Completed ** Barbican CloudKitty Designate Horizon Keystone Kuryr Sahara Solum Tripleo Watcher Winstackers Zaqar Zun Here is the list of open reviews: https://review.openstack.org/#/q/topic:goal-split-tempest-plugins+status:open Here is the detailed report on Tempest Plugin split goal status for different projects: https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html#project-teams If you are willing to help on the **not started**, that would be great help. Links: [1]. https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Openstack-sigs] [Openstack-operators] [QA] Proposal for a QA SIG
Hello, On Sun, Nov 19, 2017 at 7:44 PM, Ghanshyam Mann <ghanshyamm...@gmail.com> wrote: > On Sat, Nov 18, 2017 at 12:41 AM, Andrea Frittoli > <andrea.fritt...@gmail.com> wrote: >> >> >> On Fri, Nov 17, 2017 at 12:33 PM Thierry Carrez <thie...@openstack.org> >> wrote: >>> >>> Andrea Frittoli wrote: >>> > [...] >>> > during the last summit in Sydney we discussed the possibility of >>> > creating an >>> > OpenStack quality assurance special interest group (OpenStack QA SIG). >>> > The proposal was discussed during the QA feedback session [0] and it >>> > received >>> > positive feedback there; I would like to bring now the proposal to a >>> > larger >>> > audience via the SIG, dev and operators mailing lists. >>> > [...] > > Yea, This will greatly help QA team to get more interest from > downstream QA teams and sharing > of QA practice, scenarios & tools. I am happy to volunteer for this effort. > >>> >>> I think this goes with the current trends of re-centering upstream >>> "project teams" on the production of software, while using SIGs as >>> communities of practice (beyond the governance boundaries), even if they >>> happen to produce (some) software as the result of their work. >>> >>> 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 ? >> >> >> That is a possibility indeed, but I think co-existance will be the case for >> a >> bit at least - we may decide to drop the QA program eventually depending >> on how the experience with the SIG goes. > > Yea, we can think of merging both based on progress and how this SIG > provide us the practical benefits. Probably this idea might solve less > contributors issue where more people from downstream start > participating in QA but as of now I cannot say anything on this. > > In current situation, it will be difficult to not have QA project > team. QA has around 15 projects > and few of active projects like Tempest, Devstack, Grenade, Patrole, > O-H need dedicated team to > maintain and implement them. Grouping them under single SIG will be > another challenge to get a dedicated > attention to them. > > Currently I see the proposed QA SIG as a common platform for different > entity like OpenStack upstream, downstream QA and > other community like opnfv etc. to share best practice, tooling etc. > For example, opnfv shown much interest in on-ongoing OpenStack > "extreme testing" and this SIG can play important role to > shape this project in good/efficient direction. But we need a > dedicated set of people to lead/implement it. > > Another point/idea is to consider and run this QA SIG as one of the > effort under QA program along with project team which can be lead by > common leader(QA PTL) to make sure both > effort goes in smooth and syncing way. > Thanks Andreaf for starting it. I am happy to help. It is a great idea to bring more people under QA as well as help to share best practices and tools with in OpenStack community. I have one query, Are we also planning to collaborate with other communities like Ansible, K8s and others for the same? Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Tripleo] Containerizing tempest
Hello, I am planning to containerizing tempest for Tripleo. Kolla project provides tempest kolla image [1.]. On a containerized Tripleo deployment, the Kolla tempest image will be available on undercloud and the end user should able to run tempest from there using tempest cli. I need some help on how to proceed: [1.] Where to make changes in Tripleo in order to make Kolla Tempest image available on undercloud? [2.] Since Tempest is not a service but an application, how to expose tempest cli without tempest cli on undercloud without entering into tempest kolla image? Links: [1.] https://github.com/openstack/kolla/tree/master/docker/tempest Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [all]Tempest plugin split community goals status update
Hello, Since one month is about to pass after Denver PTG. Here is the status update on the Tempest Plugin split community goals: List of projects which have already completed the goal: - Barbican - Designate - Horizon - Keystone - Kuryr - Os-win - Sahara - Solum - Watcher List of projects which are working on the goal: - Aodh - Cinder - Magnum - Manila - Murano - Neutron - Neutron L2GW - Octavia - Senlin - Zaqar - Zun Here is the detailed report on Tempest Plugin split goal status for different projects: https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html#project-teams Here is the list of open reviews: https://review.openstack.org/#/q/topic:goal-split-tempest-plugins+status:open Feel free to take a look. If you have any queries related to the goal, Free to ping me on #openstack-qa channel. Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [all] Queens Goal for Tempest Plugin Split
Hello, Since Tempest Plugin Split[0] is added as Queen Goal and most of the projects have already started the work. It is just a heads up. If you are going to Denver PTG. Andreaf is doing a walkthrough on migrating a plugin from in-tree to own repo [1]. Do not forget to attend this. The OpenStack-QA team will be also hosting sprints in order to help on splitting tempest plugins. If you are volunteering for the same, take some time to participate in that. If you have any queries or any help you need on this, I will be available on #openstack-qa channel, Feel free to ping me. My IRC nick is chandankumar. After PTG, I will start sneaking in project's weekly meeting to help the project team to achieve this goal. One last thing, if you are volunteering for this goal, don't forgot to update the tempest plugin split wiki page[2]. Links: [0]. https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html [1]. https://etherpad.openstack.org/p/qa-queens-ptg [2]. https://wiki.openstack.org/wiki/Tempest_plugin_split_status Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [rpm-packaging][karbor]
Hello Chen, On Mon, Jul 17, 2017 at 12:41 PM, Chen Ying <chenyin...@gmail.com> wrote: > Hi Chandan, > >Thank your work about packaging abclient . > Both the packages are now available in cbs. https://review.rdoproject.org/r/#/c/7711/ got merged in RDO. Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [rpm-packaging][karbor]
On Fri, Jul 14, 2017 at 12:10 PM, Chandan kumar <chkumar...@gmail.com> wrote: > Hello Jiong, > > Thank you for packaging karbor. > > On Fri, Jul 14, 2017 at 11:49 AM, Jiong Liu <liuji...@gohighsec.com> wrote: >> Hello rpm-packaging team and folks, >> >> >> >> I got trouble with packaging OpenStack project(karbor), which depends on two >> packages: icalendar and abclient. >> >> icalendar has pip package and RPM package, but RPM package can not be found >> by RDO CI. > > python-icalender is available in fedora: > https://koji.fedoraproject.org/koji/packageinfo?packageID=10783 > We can pull it soon in RDO. > >> >> While abclient only has pip package but no RPM package. >> > > abclient is not available in Fedora or RDO. I am packaging it. It will > be soon available in RDO. I have filed a python-abclient package review for Fedora : https://bugzilla.redhat.com/show_bug.cgi?id=1470980 Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [rpm-packaging][karbor]
Hello Jiong, Thank you for packaging karbor. On Fri, Jul 14, 2017 at 11:49 AM, Jiong Liu <liuji...@gohighsec.com> wrote: > Hello rpm-packaging team and folks, > > > > I got trouble with packaging OpenStack project(karbor), which depends on two > packages: icalendar and abclient. > > icalendar has pip package and RPM package, but RPM package can not be found > by RDO CI. python-icalender is available in fedora: https://koji.fedoraproject.org/koji/packageinfo?packageID=10783 We can pull it soon in RDO. > > While abclient only has pip package but no RPM package. > abclient is not available in Fedora or RDO. I am packaging it. It will be soon available in RDO. > > > So in this case, what should I do to make sure these two packages can be > installed via RPM when packaing karbor? > > > > My patch is uploaded to rpm-package review list, as you can find here > https://review.openstack.org/#/c/480806/ > Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tc][all][ptl] Most Supported Queens Goals and Improving Goal Completion
On Fri, Jun 30, 2017 at 3:08 PM, Thierry Carrez <thie...@openstack.org> wrote: > Mike Perez wrote: >> [...] >> What do people think before we bikeshed on the name? Would having a >> champion volunteer to each goal to help? > > It feels like most agree that having champions would help. Do we have > any volunteer for the currently-proposed Pike goals ? As a reminder, > those are: > > * Split Tempest plugins into separate repos/projects [1] I would like to volunteer for Split Tempest plugins into separate repos/projects . > * Move policy and policy docs into code [2] > > [1] > https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html > [2] https://review.openstack.org/#/c/469954/ > Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [QA][ALL] What tempest tests will go under tempest plugin for a Project?
++ openstack-dev On Tue, Jun 27, 2017 at 3:57 PM, Ghanshyam Mann <ghanshyamm...@gmail.com> wrote: > On Tue, Jun 27, 2017 at 3:52 PM, Chandan kumar <chkumar...@gmail.com> wrote: >> Hello Ghanshyam, >> >> On Sat, Jun 24, 2017 at 3:48 PM, Ghanshyam Mann <ghanshyamm...@gmail.com> >> wrote: >>> On Fri, Jun 23, 2017 at 4:51 PM, Chandan kumar <chkumar...@gmail.com> wrote: >>>> Hello, >>>> >>>> In Queen OpenStack release, We have a community goal to split In-Tree >>>> tempest plugin to a separate repo[1.]. >>>> >>>> I have a couple question regarding the tempest tests movement within >>>> tempest plugins. >>>> >>>> [1.] Since some of the core OpenStack projects like Nova, Glance and >>>> Swift does have tempest plugin currently. >>>> Their Tempest tests reside under tempest project repo. >>>> are we going to create tempest plugin for the same? >>>> If yes, what are the tempest tests (API/Scenario) tests moving >>>> under tempest plugins? >>>> >>>> [2.] And, like other core projects like neutron and cinder have their >>>> in-tree tempest plugins also. >>>> And those are also moving to a separate repo and currently, their >>>> tests also resides under tempest repo. >>>> How can we avoid the duplication of the tempest tests? >>> >>> Its same answer for 1 and 2. Tempest is a place to have integration >>> tests and future tests also falls in same scope. >>> Yes, we do have API tests negative as well as positive which are there >>> because of defcore. Defcore need those for interop certification. >>> Those will reside in Tempest as of now and so new tests can be added >>> in Tempest if defcore require them. >>> >>> New or existing Tempest plugin for 6 core projects whose tests are >>> present in Tempest, will target their functional/API/negative testing >>> etc which are/should be out of scope of Tempest. >>> >>> Regarding the duplication of tests, we do take care of those while >>> review of new tests addition. If there is any new tests proposed in >>> Tempest, reviewers need to check whether same coverage is there on >>> project side or not (either functional tests or in tempest plugin). >>> Also if those are more appropriate to reside on project side. We will >>> be continuing with the same process to avoid duplicate tests. >>> >> >> Thanks got it, So basically if any tests needed by DefCore as well as >> integration tests >> needed for Core Projects will go under Tempest. >> >>> >>>> >>>> [3.] For other projects while moving tests to a separate repo how we >>>> are going to collaborate together to avoid >>>> duplication and move common tests to Tempest? >>> >>> You mean tests in projects tree as functional tests etc and their >>> tempest plugin ? >> >> Yes, For example, Swift have lots of functional tests with in tests >> folder of swift project tree. >> Does it go under tempest plugin? >> This part i am confused. > > That depends on project to project. If they want to implement tempest > like tests and does not fall under Tempest scope, then those tests > goes in tempest plugin like done by Cinder. But it does not mean that > all existing functional tests of projects needs to be moved/converted > to tempest like tests. > That's all depends on project team decision. > > -gmann > >> Thanks, I got all the answers. Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [QA][ALL] What tempest tests will go under tempest plugin for a Project?
Hello Ghanshyam, On Sat, Jun 24, 2017 at 3:48 PM, Ghanshyam Mann <ghanshyamm...@gmail.com> wrote: > On Fri, Jun 23, 2017 at 4:51 PM, Chandan kumar <chkumar...@gmail.com> wrote: >> Hello, >> >> In Queen OpenStack release, We have a community goal to split In-Tree >> tempest plugin to a separate repo[1.]. >> >> I have a couple question regarding the tempest tests movement within >> tempest plugins. >> >> [1.] Since some of the core OpenStack projects like Nova, Glance and >> Swift does have tempest plugin currently. >> Their Tempest tests reside under tempest project repo. >> are we going to create tempest plugin for the same? >> If yes, what are the tempest tests (API/Scenario) tests moving >> under tempest plugins? >> >> [2.] And, like other core projects like neutron and cinder have their >> in-tree tempest plugins also. >> And those are also moving to a separate repo and currently, their >> tests also resides under tempest repo. >> How can we avoid the duplication of the tempest tests? > > Its same answer for 1 and 2. Tempest is a place to have integration > tests and future tests also falls in same scope. > Yes, we do have API tests negative as well as positive which are there > because of defcore. Defcore need those for interop certification. > Those will reside in Tempest as of now and so new tests can be added > in Tempest if defcore require them. > > New or existing Tempest plugin for 6 core projects whose tests are > present in Tempest, will target their functional/API/negative testing > etc which are/should be out of scope of Tempest. > > Regarding the duplication of tests, we do take care of those while > review of new tests addition. If there is any new tests proposed in > Tempest, reviewers need to check whether same coverage is there on > project side or not (either functional tests or in tempest plugin). > Also if those are more appropriate to reside on project side. We will > be continuing with the same process to avoid duplicate tests. > Thanks got it, So basically if any tests needed by DefCore as well as integration tests needed for Core Projects will go under Tempest. > >> >> [3.] For other projects while moving tests to a separate repo how we >> are going to collaborate together to avoid >> duplication and move common tests to Tempest? > > You mean tests in projects tree as functional tests etc and their > tempest plugin ? Yes, For example, Swift have lots of functional tests with in tests folder of swift project tree. Does it go under tempest plugin? This part i am confused. > If so, then same process as done in Tempest. When > adding new tests in tempest plugin, reviewers need to check the > duplicate coverage of those tests. > Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [QA][ALL] What tempest tests will go under tempest plugin for a Project?
Hello, In Queen OpenStack release, We have a community goal to split In-Tree tempest plugin to a separate repo[1.]. I have a couple question regarding the tempest tests movement within tempest plugins. [1.] Since some of the core OpenStack projects like Nova, Glance and Swift does have tempest plugin currently. Their Tempest tests reside under tempest project repo. are we going to create tempest plugin for the same? If yes, what are the tempest tests (API/Scenario) tests moving under tempest plugins? [2.] And, like other core projects like neutron and cinder have their in-tree tempest plugins also. And those are also moving to a separate repo and currently, their tests also resides under tempest repo. How can we avoid the duplication of the tempest tests? [3.] For other projects while moving tests to a separate repo how we are going to collaborate together to avoid duplication and move common tests to Tempest? Links: [1.] https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [QA] Proposed changes to the team meeting time
On Thu, Jun 8, 2017 at 4:04 PM, Andrea Frittoli <andrea.fritt...@gmail.com> wrote: > I proposed a change to irc-meetings [1] to move the meeting to 8:00 UTC. > The first 8:00 UTC meeting will be next week June 15th. > > [1] https://review.openstack.org/472194 > It will be helpful. Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [puppet] [tempest] L2GW not standard Tempest Plugin. How to get tests into CI?
On Mon, May 22, 2017 at 6:41 PM, Ghanshyam Mann <ghanshyamm...@gmail.com> wrote: > On Mon, May 22, 2017 at 9:42 PM, Kevin Benton <ke...@benton.pub> wrote: >> Can you file a patch to adjust tox.ini of l2gw to make it the same as the >> others? > > Actually it is not just tox, if we need to setup l2gw tests as Tempest > plugin, it needs some of the tests and config options refactoring. I > have not gone deep into those tests but from first look it should be > easy one. > >> >> On May 22, 2017 7:35 AM, "Ricardo Noriega De Soto" <rnori...@redhat.com> >> wrote: >>> >>> Hello guys, >>> >>> I'm trying to enable some tempest tests into puppet-openstack-integration >>> project. I basically did the same procedure as with other Neutron drivers >>> but tests were not being executed: >>> >>> https://review.openstack.org/#/c/460080/ >>> >>> If you check the puppet-tempest patch, I enable the "l2gw" driver in >>> tempest.conf under the service_avaiblable section: >>> >>> https://review.openstack.org/#/c/459712/ >>> >>> However, the way these tests are called slightly different: >>> >>> >>> https://github.com/openstack/networking-l2gw/tree/master/networking_l2gw/tests >>> >>> https://github.com/openstack/networking-l2gw/blob/master/tox.ini#L50-L53 > > Yes, as you mentioned l2gw tests are not setup as tempest plugin but > that should not matter here. Test is being skipped because, > 'l2-gateway' extension is not enabled on tempest config [1] in your > patch. > > This tests depends on 2 conditions to run [2] > 1. 'l2-gateway' extension to be enabled. > 2. len(CONF.L2GW.l2gw_switch) < 0 This seems not to be in tempest conf [3]. > > If you make these 2 options configured correctly then test should run. > I was searching example of those config in openstack/networking-l2gw > jobs but seems like those tests does not run there. Anywhere we run > those tests? > > Currently tests depends Tempest + some extra config options. This way > makes l2gw tests hard to configure and run. To make it simple, I > recommend to make l2gw tests as tempest plugin if they can be. It > should be simple though. We have nice doc for setting up the Plugin > [4], but if you need help QA team will be happy to help in that. > I have added a patch upstream which implements tempest plugin for networking-l2gw : https://review.openstack.org/#/c/466728/ Feel free to take it forward. Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tripleo] pingtest vs tempest
On Thu, May 4, 2017 at 5:34 PM, Arx Cruz <arxc...@redhat.com> wrote: > > > On Wed, May 3, 2017 at 11:53 PM, Emilien Macchi <emil...@redhat.com> wrote: >> >> (cross-posting) >> >> I've seen a bunch of interesting thoughts here. >> The most relevant feedback I've seen so far: >> >> - TripleO folks want to keep testing fast and efficient. >> - Tempest folks understand this problematic and is willing to collaborate. >> >> I propose that we move forward and experiment the usage of Tempest in >> TripleO CI for one job that could be experimental or non-voting to >> start. >> Instead of running the Pingtest, we would execute a Tempest Scenario >> that boot an instance from volume (like Pingstest is already doing) >> and see how it goes (in term of coverage and runtime). >> I volunteer to kick-off the work with someone more expert than I am >> with quickstart (Arx maybe?). >> > > Sure, let's work on that :) @Arx, @EmilienM, If you need any helping hand on this please let me know Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Magnum] Liberty RPMs for RDO
Hello Mathieu, On Mon, Nov 30, 2015 at 4:48 PM, Alan Pevec <ape...@gmail.com> wrote: > Hi Mathieu, > > 2015-11-30 10:54 GMT+01:00 Mathieu Velten <mathieu.vel...@cern.ch>: > > Hi, > > > > Let me first introduce myself : I am currently working at CERN to help > > evaluate and deploy Magnum. > > > > In this regard Ricardo recently sends an email regarding Puppet > > modules, this one is about RPMs of Magnum for CentOS with RDO. > > Nice, looking forward to review it! > > > You can find here a repository containing the source and binary RPMs > > for magnum and python-magnumclient. > > http://linuxsoft.cern.ch/internal/repos/magnum7-testing/ > > This one is 403 ? > > > The version 1.0.0.0b2.dev4 is the Magnum Liberty release and the > > 1.1.0.0-5 version is the Mitaka M1 release using Liberty dependencies > > (one client commit regarding keystone auth and one server commit > > regarding oslo.config have been reverted). > > > > Let me know how I can contribute the spec files to somewhere more > > suitable. > > Let's discuss this on rdo-list (CCed) > > I had also created a rdo package review for python-magnumclient. https://bugzilla.redhat.com/show_bug.cgi?id=1286772 Where can i find you irc channel? or you can ping me on #rdo channel. My irc nick is chandankumar. So that we can get magnum packaged for RDO. Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Removing unused dependencies like:'discover' module from all projects
Hello, I am packaging 'discover' module https://bugzilla.redhat.com/show_bug.cgi?id=1251951 for RDO. Since, this module is not maintained yet as per this http://code.google.com/p/unittest-ext/ and this module is used as a test-dependencies in all the projects as per 'openstack-requirements' module https://github.com/openstack/requirements/blob/master/global-requirements.txt#L246 and i have a discussion with lifeless regarding that https://github.com/testing-cabal/unittest-ext/issues/96 and he has proposed a fix on that: https://review.openstack.org/#/c/217046/ Can someone confirms whether it is obsolete or not? if it is obsolete, can we remove if it does not break any project? so that i can create a bug to track it. Needs input on that. Thanks, Chandan Kumar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Stackalytics 0.4 released!
Hello , On Thu, Dec 12, 2013 at 10:11 PM, Monty Taylor mord...@inaugust.com wrote: On 12/12/2013 04:49 PM, Ilya Shakhat wrote: Hello everyone! Stackalytics team is happy to announce the release of version 0.4. This release is completely dedicated to different types of reports. We added highly demanded top reviewers chart acknowledged as an essential tool for finding most active reviewers (ex. http://stackalytics.com/report/reviews/neutron-group/30). Open reviews report to help core engineers with tracking the backlog and reviews that stay for too long (http://stackalytics.com/report/reviews/nova/open). And activity report, the one to show all work done by engineer and another by company. Also this report includes nice punch-card and the one can find that there are really world-wide never-sleeping contributors like http://stackalytics.com/report/companies/red%20hat :) Nice work. On the activity chart, it shows an activity graph of time and day. What timezone are those hours shown in? In details, total changes are: * Added review stats report http://stackalytics.com/report/reviews/neutron-group/30 that shows top reviewers with breakdown by marks and disagreement ratio against core's decision * Added open reviews report http://stackalytics.com/report/reviews/nova/open that shows top longest reviews and backlog summary * Added activity report http://stackalytics.com/report/users/boris-42 with engineer's activity log and punch-card of usual online hours (in UTC). The same report is available for companies * Fixed review stats calculation, now Approve marks are counted separately * Fixed commit date calculation, now it is date of merge, not commit * Minor improvements in filter selectors * Incorporated 21 updates to user and company profiles in default data The next Stackalytics meeting will be on Monday, Dec 16 at 15:00 UTC in #openstack-meeting. Come and join us, we have somemore things for the next release. Thanks, Ilya Thank you Ilya for bringing lots of changes in the stackalytics. I would like to help in the development of stackalytics. Last time i have missed. This time i will not. Thanks, Chandan Kumar ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] While booting an instance each time, getting Status = ERROR.
Hello, I have deployed Devstack in a VM RAM= 2 GB, CPU-2 using Fedora 18. It is my localrc file.: http://fpaste.org/39848/33990213/ I have created image of fedora 17 using glance. By using that image, I am trying to boot an instance using nova client. During Booting after the end of Build state, The Instance gives Status ERROR. Below is the output of all the operations that i have done during booting an instance. http://fpaste.org/39851/13793402/ I have tried to deploy the devstack in a bare metal, there also i have got the same Status Error during boot the instance. For finding the reason of Status = Error, i have checked logs directory. But there are lots of files available for different screen. Please tell me which file to look to file error Log? Here is the log link: http://fpaste.org/39855/37934048/ here is the output of nova-manage service list: http://fpaste.org/39857/40640137/ from there i found that all nova services are enabled. But why on each time booting the instance it gives error? Thanks, Chandan Kumar ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
