-----Original Message-----
From: rdo-list-bounces(a)redhat.com [mailto:rdo-list-bounces@redhat.com] On
Behalf Of Kaul, Yaniv
Sent: Thursday, February 26, 2015 8:07 PM
To: Tal Kammer
Cc: rdo-list(a)redhat.com
Subject: Re: [Rdo-list] What RH Tempest is best to be used against Kilo?
> -----Original Message-----
> From: Tal Kammer [mailto:tkammer@redhat.com]
> Sent: Thursday, February 26, 2015 7:24 PM
> To: Kaul, Yaniv
> Cc: rdo-list(a)redhat.com; Yaniv Eylon
> Subject: Re: [Rdo-list] What RH Tempest is best to be used against Kilo?
>
>
>
> ----- Original Message -----
> > ----- Original Message -----
> >
> > > Is master or Juno more updated?
> > > I’m afraid both are not updated to remove the XML tests which are
> > > already gone in upstream.
> >
> > Yaniv, I believe you have an outdated local branch..
Every test pulls from github, I don't maintain them here.
https://github.com/redhat-
openstack/tempest/tree/juno/tempest/services/volume/xml certainly has XML
- and that's Juno branch.
So I assume the answer is 'master'. OK - will try and use that. I already see
failures there - that worked in the Juno branch... :(
Thanks,
Y.
Changes (intended?)
- config_tempest doesn't create a [volume] section, as it used to. That means my
'sed' (instead of openstack-config) was not working, moved to 'echo'.
- 'Backups' become 'backups' in volume-feature-enabled in
etc/tempest.conf. I'm removing it, as I don't test backup in Cinder.
- I can't seem to NOT run the backup test
(tempest.api.volume.admin.test_volumes_backup.VolumesBackupsV1Test.test_volume_backup_create_get_detailed_list_restore_delete[gate,smoke])
although:
[root@lg528 ~]# grep -ci backup tempest/etc/tempest.conf
0
The rest is fine.
Y.
> >
> > tkammer@tkammer redhat-tempest$ git status # On branch master #
> > Untracked files:
> > # (use "git add <file>..." to include in what will be
committed)
> > nothing added to commit but untracked files present (use "git add"
> > to
> > track)
> >
> > tkammer@tkammer redhat-tempest$ git log | grep 'removes the xml' -C6
> > commit e5e7a50909d3e91e5e98e851ae764fe897eca648
> > Author: Matthew Treinish <mtreinish(a)kortar.org>
> > Date: Wed Nov 26 11:00:10 2014 -0500
> >
> > Remove unused xml config options
> >
> > This patch removes the xml configuration options from tempest. Since
> > the xml testing has all been removed from tempest these options no
> > longer do anything, so let's just remove them from config.
> >
> > Change-Id: I5b3e221d942e09134024b82acaf179dc869357e0
>
> Sorry, just noticed I've quoted the wrong commit :) tkammer@tkammer
> redhat-tempest$ git log | grep 'remove xml_utils and all things that
> depend on it' -C6
>
> commit e4119b664dca51f0d055553fcf540921b90186ae
> Merge: d354961 fc07254
> Author: Jenkins <jenkins(a)review.openstack.org>
> Date: Wed Nov 26 17:23:17 2014 +0000
>
> Merge "remove xml_utils and all things that depend on it"
>
> commit d354961d1c427f0690a7571998ac4121449da280
> Merge: 2d01ff3 f3c7591
> Author: Jenkins <jenkins(a)review.openstack.org>
> Date: Wed Nov 26 17:23:06 2014 +0000
>
> --
> Merge "Unified interface for ScenarioTest and NetworkScenarioTest"
>
> commit fc072542073b3e3611854aad41364c08b03c5e83
> Author: Sean Dague <sean(a)dague.net>
> Date: Mon Nov 24 11:50:25 2014 -0500
>
> remove xml_utils and all things that depend on it
>
> This rips out xml_utils, and all the things that depend on it, which takes
> out a huge amount of the xml infrastructure in the process.
>
> Change-Id: I9d40f3065e007a531985da1ed56ef4f2e245912e
>
>
> >
> > If you prefer the GUI version (for example), you can see this also
> > on github that the XML is not part of the master branch anymore:
> >
https://github.com/redhat-openstack/tempest/tree/master/tempest/serv
> > ic
> > es/identity/v3
> >
https://github.com/redhat-openstack/tempest/tree/juno/tempest/servic
> > es
> > /identity/v3
> >
> > > Are there any plans to contribute tempest-config upstream?
> > > (probably the only reason I still use RH’s fork?).
> > > Y.
> >
> > Yes, David Kranz initiated a push of the tool upstream.
> > In any case, we have implemented an automation system around the
> > sync with upstream branch.
> > As of about two weeks ago, our master branch will always be in sync
> > with upstream master (maybe a couple of days behind as we still in
> > the process of deciding if the update should happen daily/weekly/etc).
> >
> > > _______________________________________________
> > > Rdo-list mailing list
> > > Rdo-list(a)redhat.com
> > >
https://www.redhat.com/mailman/listinfo/rdo-list
> >
> > > To unsubscribe: rdo-list-unsubscribe(a)redhat.com
> > --
> >
> > --
> > Tal Kammer
> > Automation and infra Team Lead, Openstack platform.
> > Red Hat Israel
> >
> > _______________________________________________
> > Rdo-list mailing list
> > Rdo-list(a)redhat.com
> >
https://www.redhat.com/mailman/listinfo/rdo-list
> >
> > To unsubscribe: rdo-list-unsubscribe(a)redhat.com
>
> --
> Tal Kammer
> Automation and infra Team Lead, Openstack platform.
> Red Hat Israel
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com