[openstack-dev] [vitrage] No IRC meeting today

[Afek, Ifat (Nokia - IL/Kfar Sava)]

Hi,

We will not hold the weekly IRC meeting today due to the PTG discussions.
We will meet again next week, March 6th.

BR,
Ifat

__
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] [tacker] tacker project meeting time vote poll

[龚永生]

for more stackers to join tacker project meeting, we are voting new tacker 
project  meeting time at:


https://doodle.com/poll/59dwkpzp84gw9w45


if you are interested in tacker project, please join us. thanks


yong sheng gong


Tacker project team


99cloud__
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] [oslo.db] oslo_db "max_retries" option

[Vitalii Solodilov]

Hi folks! 

I have a question about oslo_db "max_retries" option.
https://github.com/openstack/oslo.db/blob/master/oslo_db/sqlalchemy/engines.py#L381
 
Why only DBConnectionError is considered as a reason for reconnecting here?
Wouldn't it be a good idea to check for more general DBError?
For example, DB host is down at the time of engine creation, but will become 
running some time later.

-- 
Best regards,

Vitalii Solodilov


__
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][PTLs] Community Goals for Rocky: Toggle the debug option at runtime

[ChangBo Guo]

Hi ALL,

TC approved the  goal [0]  a week ago ,  so it's time to finish the work.
we also have a short discussion in oslo meeting  at PTG, find more details
in [1] ,
we use storyboard to check the goal in
https://storyboard.openstack.org/#!/story/2001545.  It's appreciated PTL
set the owner in time .
Feel free to reach me( gcb) in IRC if you have any questions.


[0] https://review.openstack.org/#/c/534605/
[1] https://etherpad.openstack.org/p/oslo-ptg-rocky  From line 175

-- 
ChangBo Guo(gcb)
Community Director @EasyStack
__
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] [neutron][vpnaas] drivers removal

[hoan...@vn.fujitsu.com]

Hi,

Following the announced information by Takashi Yamamoto [1].
I have proposed a patch to remove the following drivers [2]:
- CiscoCsrIPsecDriver
- FedoraStrongSwanDriver
- VyattaIPsecDriver

Those drivers are intended to be removed in Rocky. So, please check it and 
leave comment if you still need those drivers and plan to provide maintaining 
effort to the drivers.

[1] http://lists.openstack.org/pipermail/openstack-dev/2017-July/120264.html 
[2] https://review.openstack.org/#/c/543394/ 

Best regards,
Hoang



__
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] [Zaqar] Nominating yangzhenyu for Zaqar core

[hao wang]

+1, I'm glad to hear this, zhenyu is a great contributor in Zaqar
team. Hope your great work in Rocky as well.

2018-02-27 17:22 GMT+08:00 Xiyuan Wang :
> +1, zhenyu has done  a lot of useful features in Zaqar. Such as delay queue
> and message abstract support. Some others are on the list for Rocky as well.
> Great work.
>
> 2018-02-26 1:38 GMT+00:00 Fei Long Wang :
>>
>> Hi team,
>>
>> I would like to propose adding Zhenyu Yang(yangzhenyu) for the Zaqar core
>> team. He has been an awesome contributor since joining the Zaqar team. And
>> now he is the most active non-core contributor on Zaqar projects for the
>> last 180 days[1]. Zhenyu has great technical expertise and contributed many
>> high quality patches. I'm sure he would be an excellent addition to the
>> team. If no one objects, I'll proceed and add him in a week from now.
>> Thanks.
>>
>> [1] http://stackalytics.com/report/contribution/zaqar-group/180
>>
>> --
>> Cheers & Best regards,
>> Feilong Wang (王飞龙)
>> --
>> Senior Cloud Software Engineer
>> Tel: +64-48032246
>> Email: flw...@catalyst.net.nz
>> Catalyst IT Limited
>> Level 6, Catalyst House, 150 Willis Street, Wellington
>> --
>>
>>
>>
>> __
>> 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 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 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] [FEMDC] no meeting this week

[lebre . adrien]

Hi all, 

Most of us are attending the PTG.  
Next meeting should be held on March, the 14th.

ad_ri3n_

__
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] [qinling] Adding Hunt Xu to qinling core

[Lingxian Kong]

I'd like to add Hunt Xu to the qinling core team.

As you know, Qinling project was just approved as an official openstack
project, it's still very young and doesn't get a ton of activity or review,
but Hunt Xu has been involving in the development and improvement for
comparatively quite a while now:

http://stackalytics.com/report/contribution/qinling/30

He's currently working on improving the tests which is important for
Qinling at this stage (much appreciated!), we also need his vision and
passion for the project which is definitely required to be a core reviewer.

So unless there are objections, I'll plan on adding Hunt Xu to the qinling
group this week.

Cheers,
Lingxian Kong (Larry)
__
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] [qinling] project update - 4

[Lingxian Kong]

This project update email is supposed to be sent regularly, but feel free
to get in touch in #openstack-qinling irc channel anytime. - First, Qinling
was approved as an official project at the end of Queens cycle, and will
start its journey as an official project in Rocky development cycle,
welcome any kind of contributions from the whole community - Qinling
feature and bug tracking have been migrated from launchpad to
StoryBoard[1], which is much more flexible for task tracking across
multiple teams, multiple code repositories, or even multiple branches
within those code repositories. - The Rocky task priorities have been
sorted out, for anyone interested, please refer to
https://storyboard.openstack.org/#!/worklist/251 - More additional Jenkins
jobs were added to the project, such as doc, code coverage, release notes,
etc. As usual, you can easily find previous emails below. [1]:
https://storyboard.openstack.org/#!/project/927

Cheers,
Lingxian Kong (Larry)

-- Forwarded message --
From: Lingxian Kong 
Date: Wed, Jan 24, 2018 at 12:12 AM
Subject: [openstack-dev] [faas] [qinling] project update - 3
To: OpenStack Development Mailing List 


Hi, all

This project update is posted bi-weekly, but feel free to get in touch in
#openstack-qinling anytime.


   - Function package md5 check. This feature allows user specify the md5
   checksum for the code package when creating the function, so the
   function package could be verified after downloading. If CLI is used, the
   md5 checksum will be calculated automatically.
   - Function webhook. The user can expose a function to 3rd party
   service(e.g. GitHub) by creating webhook so that the function can be
   invoked without authentication.
   - [CLI] Support to download function code package.


BTW, maybe some of you already know that Qinling team is applying to become
an OpenStack official project[1], feel free to leave your comments in the
application, any feedback and questions are welcomed.

As usual, you can easily find previous emails below.

[1]: https://review.openstack.org/#/c/533827/

Cheers,
Lingxian Kong (Larry)

-- Forwarded message --
From: Lingxian Kong 
Date: Mon, Jan 8, 2018 at 10:37 AM
Subject: [openstack-dev] [faas] [qinling] project update - 2
To: OpenStack Development Mailing List 


Hi, all

Happy new year!

This project update is posted by-weekly, but feel free to get in touch in
#openstack-qinling anytime.

- Introduce etcd in qinling for distributed locking and storing the
resources that need to be updated frequently.
- Get function workers (admin only)
- Support to detach function from underlying orchestrator (admin only)
- Support positional args in users function
- More unit tests and functional tests added
- Powerful resource query filtering of qinling openstack CLI
- Conveniently delete all executions of one or more functions in CLI

You can find previous emails below.

Have a good day :-)

Cheers,
Lingxian Kong (Larry)

-- Forwarded message --
From: Lingxian Kong 
Date: Tue, Dec 12, 2017 at 10:18 PM
Subject: [openstack-dev] [qinling] [faas] project update
​ - 1​

To: OpenStack Development Mailing List 


Hi, all

Maybe there are aleady some people interested in faas implementation in
openstack, and also deployed other openstack services to be integrated with
(e.g. trigger function by object uploading in swift), Qinling is the thing
you probably don't want to miss out. The main motivation I creatd Qinling
project is from frequent requirements of our public cloud customers.

For people who have not heard about Qinling before, please take a look at
my presentation in Sydney Summit:
https://youtu.be/NmCmOfRBlIU
There is also a simple demo video:
https://youtu.be/K2SiMZllN_A

As the first project update email, I will just list the features
implemented for now:

- Python runtime
- Sync/Async function execution
- Job (invoke function on schedule)
- Function defined in swift object storage service
- Function defined in docker image
- Easy to interact with openstack services in function
- Function autoscaling based on request rate
- RBAC operation
- Function resource limitation
- Simple documentation

I will keep posting the project update by-weekly, but feel free to get in
touch in #openstack-qinling anytime.
__
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] [cinder][nova] Update attachments on replication failover

[Matt Riedemann]

On 2/27/2018 6:34 PM, John Griffith wrote:
​ So replication is set on create of the volume, you could have a rule 
that keeps the two features mutually exclusive, but I'm still not quite 
sure why that would be a requirement here.  ​


Yeah I didn't think of that either, the attachment record has the 
instance uuid in it right? So cinder could just iterate the list of 
attachments for the volume and send multiple requests to nova.


--

Thanks,

Matt

__
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] [congress] no team meeting this week 3/1

[Eric K]

Cancelled for PTG



__
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-dev ][ tripleo ] unplanned outtage in RDO-Cloud

[Wesley Hayutin]

On Fri, Feb 23, 2018 at 8:41 PM, David Moreau Simard 
wrote:

> Please be wary of approving changes since the Third Party CI is out of
> order until this is resolved.
>
> David Moreau Simard
> Senior Software Engineer | OpenStack RDO
>
> dmsimard = [irc, github, twitter]
>
>
> On Fri, Feb 23, 2018 at 5:40 PM, Wesley Hayutin 
> wrote:
> >
> >
> > On Fri, Feb 23, 2018 at 12:09 PM, Wesley Hayutin 
> > wrote:
> >>
> >> Greetings,
> >>
> >> The TripleO CI in RDO-Cloud has experienced an unplanned outage and is
> >> down at this time.  We will update this thread with more information
> >> regarding when the CI will be brought back online as it becomes
> available.
> >>
> >>
> >> Thank you!
> >> Wes Hayutin
> >
> >
> > FYI..
> > The latest estimate for the unplanned outtage to TripleO-CI in RDO-Cloud
> is
> > that it will take a number of business days to resolve the issues.
> >
> > Thank you!
> >
> >
> > 
> __
> > 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 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
>

FYI..

First, thank you for your patience while the CI jobs in RDO Cloud were down.
There are not a lot details to share regarding the outtage at this time,
however services are being restored at this moment and we should see the
3rd party jobs and promotion jobs running shortly with some results rolling
in by the morning.
The effort to restore services involves several teams and takes a bit of
coordination.  I'm happy to report that all the teams involved have very
dedicated engineers and we're making good progress.

Thanks to David Manchado, David Simard and the TripleO CI squad.
__
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][keystone] clusters, trustees and projects

[Ricardo Rocha]

Hi Lance.

On Mon, Feb 26, 2018 at 4:45 PM, Lance Bragstad  wrote:
>
>
> On 02/26/2018 10:17 AM, Ricardo Rocha wrote:
>> Hi.
>>
>> We have an issue on the way Magnum uses keystone trusts.
>>
>> Magnum clusters are created in a given project using HEAT, and require
>> a trust token to communicate back with OpenStack services -  there is
>> also integration with Kubernetes via a cloud provider.
>>
>> This trust belongs to a given user, not the project, so whenever we
>> disable the user's account - for example when a user leaves the
>> organization - the cluster becomes unhealthy as the trust is no longer
>> valid. Given the token is available in the cluster nodes, accessible
>> by users, a trust linked to a service account is also not a viable
>> solution.
>>
>> Is there an existing alternative for this kind of use case? I guess
>> what we might need is a trust that is linked to the project.
> This was proposed in the original application credential specification
> [0] [1]. The problem is that you're sharing an authentication mechanism
> with multiple people when you associate it to the life cycle of a
> project. When a user is deleted or removed from the project, nothing
> would stop them from accessing OpenStack APIs if the application
> credential or trust isn't rotated out. Even if the credential or trust
> were scoped to the project's life cycle, it would need to be rotated out
> and replaced when users come and go for the same reason. So it would
> still be associated to the user life cycle, just indirectly. Otherwise
> you're allowing unauthorized access to something that should be protected.
>
> If you're at the PTG - we will be having a session on application
> credentials tomorrow (Tuesday) afternoon [2] in the identity-integration
> room [3].

Thanks for the reply, i now understand the issue.

I'm not at the PTG. Had a look at the etherpad but it seems app
credentials will have a similar lifecycle so not suitable for the use
case above - for the same reasons you mention.

I wonder what's the alternative to achieve what we need in Magnum?

Cheers,
  Ricardo

> [0] https://review.openstack.org/#/c/450415/
> [1] https://review.openstack.org/#/c/512505/
> [2] https://etherpad.openstack.org/p/application-credentials-rocky-ptg
> [3] http://ptg.openstack.org/ptg.html
>>
>> I believe the same issue would be there using application credentials,
>> as the ownership is similar.
>>
>> Cheers,
>>   Ricardo
>>
>> __
>> 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 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 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] [cinder][nova] Update attachments on replication failover

[John Griffith]

On Tue, Feb 27, 2018 at 9:34 AM, Walter Boring  wrote:

> I think you might be able to get away with just calling os-brick's
> connect_volume again without the need to call disconnect_volume first.
>  calling disconnect_volume wouldn't be good for volumes that are being
> used, just to refresh the connection_info on that volume.
>
​Hmm... but then you'd have an orphaned connection left hanging around for
the old connection no?
​


>
> On Tue, Feb 27, 2018 at 2:56 PM, Matt Riedemann 
> wrote:
>
>> On 2/27/2018 10:02 AM, Matthew Booth wrote:
>>
>>> Sounds like the work Nova will have to do is identical to volume update
>>> (swap volume). i.e. Change where a disk's backing store is without actually
>>> changing the disk.
>>>
>>
>> That's not what I'm hearing. I'm hearing disconnect/reconnect. Only the
>> libvirt driver supports swap volume, but I assume all other virt drivers
>> could support this generically.
>>
>>
>>> Multi-attach! There might be more than 1 instance per volume, and we
>>> can't currently support volume update for multi-attached volumes.
>>>
>> ​Not sure I follow... why not?  It's just refreshing connections, only
difference is you might have to do this "n" times instead of once?​


>
>> Good point - cinder would likely need to reject a request to replicate an
>> in-use multiattach volume if the volume has more than one attachment.
>
> ​So replication is set on create of the volume, you could have a rule that
keeps the two features mutually exclusive, but I'm still not quite sure why
that would be a requirement here.  ​


>
>>
>> --
>>
>> Thanks,
>>
>> Matt
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> 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 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] [charms] queens support release date

[James Page]

Hi All

We're not quite fully baked with Queens testing for the OpenStack charms
for this week so we're going to push back a week to the 8th March to allow
pre-commit functional testing updates to land.

Cheers

James
__
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] [kolla][ptg] Team dinner

[Paul Bourke]

Ok, Thursday seems good for the majority. Venue is 'Against the Grain' 
[0]. You can get the number 16 bus from near the Croke Park hotel, or we 
can just arrange to share a couple of taxis. See you all at the sessions 
tomorrow :)


-Paul

[0] https://goo.gl/maps/pddiUwnr67B2

On 26/02/18 19:39, Paul Bourke wrote:

Hey Kolla,

Hope you're all enjoying Dublin so far :) Some have expressed interest 
in getting together for a team meal, how does Thursday sound? Please 
reply to this with +1/-1 and I can see about booking something.


Cheers,
-Paul

__
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 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] [cyborg]Team Dinner 6:30pm at Croke Park Hotel

[Zhipeng Huang]

Hi Team,

I reserved a table for 8 at Sideline Bar in the Croke Park Hotel for team
dinner . Look forward to meat you guys there :P
__
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] [cinder][nova] Update attachments on replication failover

[Walter Boring]

I think you might be able to get away with just calling os-brick's
connect_volume again without the need to call disconnect_volume first.
 calling disconnect_volume wouldn't be good for volumes that are being
used, just to refresh the connection_info on that volume.

On Tue, Feb 27, 2018 at 2:56 PM, Matt Riedemann  wrote:

> On 2/27/2018 10:02 AM, Matthew Booth wrote:
>
>> Sounds like the work Nova will have to do is identical to volume update
>> (swap volume). i.e. Change where a disk's backing store is without actually
>> changing the disk.
>>
>
> That's not what I'm hearing. I'm hearing disconnect/reconnect. Only the
> libvirt driver supports swap volume, but I assume all other virt drivers
> could support this generically.
>
>
>> Multi-attach! There might be more than 1 instance per volume, and we
>> can't currently support volume update for multi-attached volumes.
>>
>
> Good point - cinder would likely need to reject a request to replicate an
> in-use multiattach volume if the volume has more than one attachment.
>
>
> --
>
> Thanks,
>
> Matt
>
> __
> 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 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] [kolla][ptg] Team dinner

[Gema Gomez]

+1

On 26/02/18 19:39, Paul Bourke wrote:
> Hey Kolla,
> 
> Hope you're all enjoying Dublin so far :) Some have expressed interest
> in getting together for a team meal, how does Thursday sound? Please
> reply to this with +1/-1 and I can see about booking something.
> 
> Cheers,
> -Paul
> 
> __
> 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 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] [cinder][nova] Update attachments on replication failover

[Matt Riedemann]

On 2/27/2018 10:02 AM, Matthew Booth wrote:
Sounds like the work Nova will have to do is identical to volume update 
(swap volume). i.e. Change where a disk's backing store is without 
actually changing the disk.


That's not what I'm hearing. I'm hearing disconnect/reconnect. Only the 
libvirt driver supports swap volume, but I assume all other virt drivers 
could support this generically.




Multi-attach! There might be more than 1 instance per volume, and we 
can't currently support volume update for multi-attached volumes.


Good point - cinder would likely need to reject a request to replicate 
an in-use multiattach volume if the volume has more than one attachment.


--

Thanks,

Matt

__
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][PTG] QA Team photo @12:00-12.10 PM Thursday

[Ghanshyam Mann]

Hi All,

QA team photo slot for PTG is scheduled on Thursday at 12.00. Please
gather @5th floor reception before time, may be good to plan to meet
@11.55 AM.

See you all there!.

-gmann

__
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][PTG] QA Dinner Night

[Ghanshyam Mann]

Hi All,

Based on doodle vote, we finalize the QA Dinner on Wed night. I have
not booked any restaurant yet so please suggest if you know any good
place.

ll put the time and meeting place soon.

-gmann

On Thu, Feb 22, 2018 at 2:11 PM, Ghanshyam Mann  wrote:
> Hi All,
>
> I'd like to propose a QA Dinner night for the people attending QA
> sessions at the Dublin PTG. I initiated a doodle vote [1] to choose
> the appropriate date.
>
> Please vote as per your availability.
>
>  ..1 https://doodle.com/poll/t7phezrq25zrqzz3
>
> -gmann

__
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] [loci] Removing deprecated project-specific Loci repositories

[Chris Hoge]

On October 17, 2017, the Loci team retired the project-specific
Loci repositories in favor of a single repository. This was done to
consolidate development and prevent the anti-pattern of one repository
with duplicated code for every OpenStack project.

After this five month deprecation period, in which we have provided no
support for those repositories, and with all development focused on the
primary Loci repository, we are officially requesting[1] that the project
specific repositories be removed from OpenStack infra hosting.

* Loci has no requirements synching
* The project-specific repositories have no project gating.
* We have zeroed out the project-specific repositories

If you're interested in Loci, the primary repository and project
remains active, and we encourage your use and contributions.[2]

[1] https://review.openstack.org/#/c/548268/
[2] https://git.openstack.org/cgit/openstack/loci/

__
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] [First Contact] [SIG] Rocky PTG Planning

[Kendall Nelson]

REMINDER!

Our team photo is at 4:00 today. You need to be at Registration on Level 5
by 4:00 at the very latest. We will be escorted out to the pitch at that
time and if you are late you will miss the opportunity!

-Kendall (diablo_rojo)

On Sun, Feb 25, 2018 at 2:51 PM Kendall Nelson 
wrote:

> Hello!
>
> Can't wait to see you all tomorrow!
>
> I'm thinking we get started at 9:00? If you want to show up early and hang
> out, the room (Canal Cafe)  is available starting at 8:30 AM.
>
> -Kendall (diablo_rojo)
>
>
> On Tue, 9 Jan 2018, 8:30 pm Kendall Nelson,  wrote:
>
>> 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
>>
>
__
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] [nova][ptg] reminder: cyborg nova-interaction discussion at 2pm this afternoon

[Zhipeng Huang]

THX Melanie ! :)

On Tue, Feb 27, 2018 at 10:34 AM, melanie witt  wrote:

> Howdy everyone,
>
> This is just a reminder that we have some time scheduled to chat with the
> Cyborg team at 2pm this afternoon at the Cyborg room (Suite 665).
>
> From our PTG etherpad agenda[1] :
>
> "Cyborg (previously known as Nomad) is an OpenStack project that aims to
> provide a general purpose management framework for acceleration resources
> (i.e. various types of accelerators such as Crypto cards,GPU, FPGA,
> NVMe/NOF SSDs, ODP, DPDK/SPDK and so on).
> https://wiki.openstack.org/wiki/Cyborg”
>
> If you are interested, please join us!
>
> -melanie
>
> [1] https://etherpad.openstack.org/p/nova-ptg-rocky at L572
> __
> 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
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
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] [cyborg]reminder for team photo

[Zhipeng Huang]

Just a kind reminder for team photo, our slot is 1:40, plz gather around
the reg desk on time :)

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
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] [PTL][SIG][PTG]Team Photos

[Kendall Waters]

Hi Luke and everyone,

Please meet at the registration desk on level 5. Make sure you and your team 
are on time so we can stay on schedule. 

For teams that are less than 20 people, we will be taking the pictures on the 
side of the pitch and for the teams that are over 20 people, the pictures will 
be taken in the stands. As a reminder, NO ONE is allowed on the grass so please 
do not step directly on the pitch when we take the pictures. 

Cheers,
Kendall

> On Feb 27, 2018, at 4:45 AM, Luke Hinds  wrote:
> 
> Hi Kendall,
> 
> Now the day has arrived, could you let us know about logistics..is there 
> somewhere we should go to wait before being collected and heading to the 
> pitch?
> 
> Cheers,
> 
> Luke
> 
> On Wed, Feb 21, 2018 at 11:48 PM, Kendall Nelson  > wrote:
> Hello Everyone!
> 
> I just wanted to remind you all that you have till Monday Feburary 26th to 
> sign up if your team or group is interested in a team photo on the Croke Park 
> pitch! We still have slots available Tuesday afternoon and Thursday morning. 
> 
> -Kendall (diablo_rojo)
> 
> On Thu, Feb 8, 2018 at 10:21 AM Kendall Nelson  > wrote:
> This link might work better for everyone: 
> https://docs.google.com/spreadsheets/d/1J2MRdVQzSyakz9HgTHfwYPe49PaoTypX66eNURsopQY/edit?usp=sharing
>  
> 
>  
> 
> -Kendall (diablo_rojo)
> 
> 
> On Wed, Feb 7, 2018 at 9:15 PM Kendall Nelson  > wrote:
> Hello PTLs and SIG Chairs!
> 
> So here's the deal, we have 50 spots that are first come, first served. We 
> have slots available before and after lunch both Tuesday and Thursday. 
> 
> The google sheet here[1] should be set up so you have access to edit, but if 
> you can't for some reason just reply directly to me and I can add your team 
> to the list (I need team/sig name and contact email). 
> 
> I will be locking the google sheet on Monday February 26th so I need to know 
> if your team is interested by then. 
> 
> See you soon!
> 
> - Kendall Nelson (diablo_rojo)
> 
> [1] 
> https://docs.google.com/spreadsheets/d/1J2MRdVQzSyakz9HgTHfwYPe49PaoTypX66eNURsopQY/edit?usp=sharing
>  
> 
>  
> 
> 
> 
> 
> __
> 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 
> 
> 
> 
> 
> 
> -- 
> Luke Hinds | NFV Partner Engineering | CTO Office | Red Hat
> e: lhi...@redhat.com  | irc: lhinds @freenode | t: 
> +44 12 52 36 2483

__
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] [nova][ptg] team photo Thursday at 11:10 AM

[Matt Riedemann]

On 2/27/2018 10:43 AM, melanie witt wrote:

It will be really cold outside, so be prepared for that.


If you live in California, sure...

--

Thanks,

Matt

__
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] [heat] heat-dashboard is non-free, with broken unit test env

[Thomas Goirand]

On 02/23/2018 09:29 AM, Xinni Ge wrote:
> Hi there,
> 
> We are aware of the javascript embedded issue, and working on it now,
> the patch will be summited later.
> 
> As for the unittest failure, we are still investigating it. We will
> contant you as soon as we find out the cause.
> 
> Sorry to bring troubles to you. We will be grateful if you could wait
> for a little longer.
> 
> Best Regards,
> 
> Xinni

Hi,

Thanks for this message. This lowers the frustration! :)
Let me know if there's any patch I could review.

Cheers,

Thomas Goirand (zigo)

__
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] [PTL][SIG][PTG]Team Photos

[Luke Hinds]

Hi Kendall,

Now the day has arrived, could you let us know about logistics..is there
somewhere we should go to wait before being collected and heading to the
pitch?

Cheers,

Luke

On Wed, Feb 21, 2018 at 11:48 PM, Kendall Nelson 
wrote:

> Hello Everyone!
>
> I just wanted to remind you all that you have till *Monday Feburary 26th*
> to sign up if your team or group is interested in a team photo on the Croke
> Park pitch! We still have slots available Tuesday afternoon and Thursday
> morning.
>
> -Kendall (diablo_rojo)
>
> On Thu, Feb 8, 2018 at 10:21 AM Kendall Nelson 
> wrote:
>
>> This link might work better for everyone:
>> https://docs.google.com/spreadsheets/d/1J2MRdVQzSyakz9HgTHfwYPe49PaoT
>> ypX66eNURsopQY/edit?usp=sharing
>>
>> -Kendall (diablo_rojo)
>>
>>
>> On Wed, Feb 7, 2018 at 9:15 PM Kendall Nelson 
>> wrote:
>>
>>> Hello PTLs and SIG Chairs!
>>>
>>> So here's the deal, we have 50 spots that are first come, first
>>> served. We have slots available before and after lunch both Tuesday and
>>> Thursday.
>>>
>>> The google sheet here[1] should be set up so you have access to edit,
>>> but if you can't for some reason just reply directly to me and I can add
>>> your team to the list (I need team/sig name and contact email).
>>>
>>> I will be locking the google sheet on *Monday February 26th so I need
>>> to know if your team is interested by then. *
>>>
>>> See you soon!
>>>
>>> - Kendall Nelson (diablo_rojo)
>>>
>>> [1] https://docs.google.com/spreadsheets/d/
>>> 1J2MRdVQzSyakz9HgTHfwYPe49PaoTypX66eNURsopQY/edit?usp=sharing
>>>
>>>
>>>
>>>
> __
> 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
>
>


-- 
Luke Hinds | NFV Partner Engineering | CTO Office | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | t: +44 12 52 36 2483
__
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] [nova][ptg] team photo Thursday at 11:10 AM

[melanie witt]

Hey everyone,

We have time scheduled on Thursday morning 11:10-11:20 AM for a team photo at 
the PTG. For those in the Nova room (Davin Suite), we’ll walk together to the 
registration area before 11:10 AM to meet before we’ll be escorted down to the 
pitch (sports field) to take the photo. If you won’t be in the Nova room on 
Thursday morning, just meet us at the registration area at 11:10 AM. It will be 
really cold outside, so be prepared for that.

Cheers,
-melanie
__
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] [nova][ptg] reminder: cyborg nova-interaction discussion at 2pm this afternoon

[melanie witt]

Howdy everyone,

This is just a reminder that we have some time scheduled to chat with the 
Cyborg team at 2pm this afternoon at the Cyborg room (Suite 665).

From our PTG etherpad agenda[1] :

"Cyborg (previously known as Nomad) is an OpenStack project that aims to 
provide a general purpose management framework for acceleration resources (i.e. 
various types of accelerators such as Crypto cards,GPU, FPGA, NVMe/NOF SSDs, 
ODP, DPDK/SPDK and so on).
https://wiki.openstack.org/wiki/Cyborg”

If you are interested, please join us!

-melanie

[1] https://etherpad.openstack.org/p/nova-ptg-rocky at L572
__
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] Zanata upgrade to version 4

[Frank Kloeker]

Hello,

the translation phase for Queens is just over. Many thanks for all that 
work during the cycle and translations in different OpenStack projects.
We will take the chance now to upgrade our translation platform to a new 
version. We don't expect bigger issues because we tested the upgrade 
process anyway on translate-dev.openstack.org. Nevertheless the platform 
could be not available this week. So please note the hint.


kind regards

Frank
(PTL I18n)

__
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] [cinder][ptg] Team Photo Rescheduled!!!

[Jay S Bryant]

Team,

Some people had conflicts with the 12:50 time for our Team Photo due to 
lunch and presentations so I have decided to reschedule the photo.


We are going to squeeze it in before the Nova/Cinder cross project 
meeting at 9:00 am on Thursday 3/1.  So, be punctual to get to the pitch 
on Thursday morning and bring a smile!


Jay


__
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] [cinder][nova] Update attachments on replication failover

[Matthew Booth]

Couple of thoughts:

Sounds like the work Nova will have to do is identical to volume update
(swap volume). i.e. Change where a disk's backing store is without actually
changing the disk.

Multi-attach! There might be more than 1 instance per volume, and we can't
currently support volume update for multi-attached volumes.

Matt

On 27 February 2018 at 09:45, Matt Riedemann  wrote:

> On 2/26/2018 9:52 PM, John Griffith wrote:
>
>> ​Yeah, it seems like this would be pretty handy with what's there.  So
>> are folks good with that?  Wanted to make sure there's nothing contentious
>> there before I propose a spec on the Nova and Cinder sides. If you think it
>> seems at least worth proposing I'll work on it and get something ready as a
>> welcome home from Dublin gift for everyone :)
>>
>
> I'll put it on the nova/cinder PTG etherpad agenda for Thursday morning.
> This seems like simple plumbing on the nova side, so not any major problems
> from me.
>
> --
>
> Thanks,
>
> Matt
>
> __
> 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
>



-- 
Matthew Booth
Red Hat OpenStack Engineer, Compute DFG

Phone: +442070094448 (UK)
__
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] [cinder][nova] Update attachments on replication failover

[Matt Riedemann]

On 2/26/2018 9:52 PM, John Griffith wrote:
​Yeah, it seems like this would be pretty handy with what's there.  So 
are folks good with that?  Wanted to make sure there's nothing 
contentious there before I propose a spec on the Nova and Cinder sides. 
If you think it seems at least worth proposing I'll work on it and get 
something ready as a welcome home from Dublin gift for everyone :)


I'll put it on the nova/cinder PTG etherpad agenda for Thursday morning. 
This seems like simple plumbing on the nova side, so not any major 
problems from me.


--

Thanks,

Matt

__
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] [Zaqar] Nominating yangzhenyu for Zaqar core

[Zhang Fan]

Big +1 for Zhenyu Yang. Although I am not a contributor of zaqar, but as his 
former colleague, I do know that he's definitely an excellent developer.

Best wishes.
Fan Zhang

 Original Message
Sender: Xiyuan Wang
Recipient: OpenStack Development Mailing List (not for usage 
questions)
Date: Tuesday, Feb 27, 2018 17:22
Subject: Re: [openstack-dev] [Zaqar] Nominating yangzhenyu for Zaqar core

+1, zhenyu has done  a lot of useful features in Zaqar. Such as delay queue and 
message abstract support. Some others are on the list for Rocky as well.
Great work.

2018-02-26 1:38 GMT+00:00 Fei Long Wang 
>:
Hi team,

I would like to propose adding Zhenyu Yang(yangzhenyu) for the Zaqar core team. 
He has been an awesome contributor since joining the Zaqar team. And now he is 
the most active non-core contributor on Zaqar projects for the last 180 
days[1]. Zhenyu has great technical expertise and contributed many high quality 
patches. I'm sure he would be an excellent addition to the team. If no one 
objects, I'll proceed and add him in a week from now. Thanks.

[1] http://stackalytics.com/report/contribution/zaqar-group/180

--
Cheers & Best regards,
Feilong Wang (王飞龙)
--
Senior Cloud Software Engineer
Tel: +64-48032246
Email: flw...@catalyst.net.nz
Catalyst IT Limited
Level 6, Catalyst House, 150 Willis Street, Wellington
--



__
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 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] [Zaqar] Nominating yangzhenyu for Zaqar core

[Xiyuan Wang]

+1, zhenyu has done  a lot of useful features in Zaqar. Such as delay queue
and message abstract support. Some others are on the list for Rocky as well.
Great work.

2018-02-26 1:38 GMT+00:00 Fei Long Wang :

> Hi team,
>
> I would like to propose adding Zhenyu Yang(yangzhenyu) for the Zaqar core
> team. He has been an awesome contributor since joining the Zaqar team. And
> now he is the most active non-core contributor on Zaqar projects for the
> last 180 days[1]. Zhenyu has great technical expertise and contributed many
> high quality patches. I'm sure he would be an excellent addition to the
> team. If no one objects, I'll proceed and add him in a week from now.
> Thanks.
>
> [1] http://stackalytics.com/report/contribution/zaqar-group/180
>
> --
> Cheers & Best regards,
> Feilong Wang (王飞龙)
> --
> Senior Cloud Software Engineer
> Tel: +64-48032246
> Email: flw...@catalyst.net.nz
> Catalyst IT Limited
> Level 6, Catalyst House, 150 Willis Street, Wellington
> --
>
>
>
> __
> 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 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] [refstack] Full list of API Tests versus 'OpenStack Powered' Tests

[Mark Voelker]

Hi Greg,

Only the tests listed in the Guidelines are required to pass to get an 
OpenStack Powered logo and trademark usage license from the OpenStack 
Foundation (you must also use the designated sections of upstream code 
specified in the Guideline documents).  However vendors are strongly encouraged 
to run all the tests.  Doing so provides some data to the Interop Working Group 
about how many products support capabilities that aren’t on the required list 
today, but might be considered in the future.  If you have any questions about 
the process, please contact inte...@openstack.org and the Foundation staff will 
be happy to help!

At Your Service,

Mark T. Voelker



> On Feb 26, 2018, at 11:22 PM, Waines, Greg  wrote:
> 
>  
> · I have a commercial OpenStack product that I would like to claim 
> compliancy with RefStack
> · Is it sufficient to claim compliance with only the “OpenStack 
> Powered Platform” TESTS ?
> oi.e. https://refstack.openstack.org/#/guidelines
> oi.e. the ~350-ish compute + object-storage tests
> · OR
> · Should I be using the COMPLETE API Test Set ?
> oi.e. the > 1,000 tests from various domains that get run if you do not 
> specify a test-list
>  
> Greg.
>  
>  
> __
> 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 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