Hi All,
I've created an etherpad for Fault Management/Monitoring for
NFV/Edge/5G/IoT. It'll take place on Tuesday, May 22, 4:40pm-6:10pm @
Room 221-222. If you have any usecase/idea/challenge for FM at these new
area, could you join this forum and add any topic/comment to etherpad.
On 18-05-17 13:51:06, Tony Breeds wrote:
> On Wed, May 16, 2018 at 04:14:36PM -0500, Matthew Thode wrote:
> > On 18-05-16 17:07:09, Doug Hellmann wrote:
> > > Excerpts from Matthew Thode's message of 2018-05-16 15:59:47 -0500:
> > > > Sphinx has breaking changes (yet again) and we need to figure
On Wed, May 16, 2018 at 04:14:36PM -0500, Matthew Thode wrote:
> On 18-05-16 17:07:09, Doug Hellmann wrote:
> > Excerpts from Matthew Thode's message of 2018-05-16 15:59:47 -0500:
> > > Sphinx has breaking changes (yet again) and we need to figure out how to
> > > deal with it. I think the fix
The Octavia project had other breakage due to sphinx > 1.7 but we have
already resolved those issues.
Back story: the way arguments are handled for apidoc changed.
An example patch for the fix would be: https://review.openstack.org/#/c/568383/
Michael (johnsom)
On Wed, May 16, 2018 at 1:59 PM,
On Wed, May 16, 2018 at 7:02 PM, James E. Blair wrote:
> Hongbin Lu writes:
>
> > The goal of those patches is to move the job definitions and playbooks
> from
> > openstack/zun to openstack/zun-tempest-plugin. The advantages of such
> > change are as
2018-05-17 1:24 GMT+08:00 Jay Pipes :
> On 05/16/2018 01:01 PM, Nadathur, Sundar wrote:
>
>> Hi,
>> The Cyborg quota spec [1] proposes to implement a quota (maximum
>> usage) for accelerators on a per-project basis, to prevent one project
>> (tenant) from over-using some
Yo Nova Gurus :-),
We here at GoDaddy are getting hot and heavy into Cells V2 these days and would
like to propose an enhancement or maybe see if something like this is already
in the works.
Need:
To be able to “synchronize” cells from a specified file (git controlled, or
inventory
Hi All,
I've created the below etherpad for the QA feedback sessions[1] which
is schedule on Monday, May 21, 1:30 pm. This contains the basic
agenda and feedback items we are planning to discuss in this sessions.
If you have any additional items to add or modify, please feel free to do that.
Team,
We discussed having a team dinner like we have done in the past during
today's team meeting. It sounded like most people would be available
Tuesday evening, so that is the evening I am planning for.
If you are able to attend please add your name to the etherpad [1] by
Sunday 5/20 so
Hongbin Lu writes:
> The goal of those patches is to move the job definitions and playbooks from
> openstack/zun to openstack/zun-tempest-plugin. The advantages of such
> change are as following:
>
> * Make job definitions closer to tempest test cases so that it is optimal
Hi all,
I have a series of patches for moving gate jobs from openstack/zun to
openstack/zun-tempest-plugin:
https://review.openstack.org/#/q/topic:relocate-zun-jobs+(status:open+OR+status:merged)
Moving forward those patches will incur a period of time that our gate will
have no tempest tests
Thanks for your reply, @Doug and @Jim
Cheers,
Lingxian Kong
On Thu, May 17, 2018 at 2:23 AM Jim Rollenhagen
wrote:
> On Wed, May 16, 2018 at 9:55 AM, Doug Hellmann
> wrote:
>
>> Excerpts from Lingxian Kong's message of 2018-05-16 11:12:01
On 18-05-16 17:07:09, Doug Hellmann wrote:
> Excerpts from Matthew Thode's message of 2018-05-16 15:59:47 -0500:
> > Sphinx has breaking changes (yet again) and we need to figure out how to
> > deal with it. I think the fix will be simple for affected projects, but
> > we should probably move
Excerpts from Matthew Thode's message of 2018-05-16 15:59:47 -0500:
> Sphinx has breaking changes (yet again) and we need to figure out how to
> deal with it. I think the fix will be simple for affected projects, but
> we should probably move forward on this. The error people are getting
> seems
Sphinx has breaking changes (yet again) and we need to figure out how to
deal with it. I think the fix will be simple for affected projects, but
we should probably move forward on this. The error people are getting
seems to be 'Field list ends without a blank line; unexpected unindent.'
I'd
On 2018-05-16 17:42:09 + (+), Jeremy Stanley wrote:
[...]
> Unfortunately, I'm unable to find any follow-up summary on the
> mailing list from the aforementioned session, but recollection from
> those who were present (I had a schedule conflict at that time) was
> that a
Some of the team will be attending the OpenStack summit in Vancouver,
so I am cancelling the weekly IRC meeting for the 23rd.
We will resume our normal schedule on the 30th.
Michael
__
OpenStack Development Mailing List
On Wed, May 16, 2018 at 1:07 PM, Alex Schultz wrote:
> Since the summit is coming up, there will likely be very low
> attendance. We'll carry any open items until the following week.
>
No Weekly Owl as well, but be patient for the next Edition special Summit.
--
Emilien
Since the summit is coming up, there will likely be very low
attendance. We'll carry any open items until the following week.
Thanks,
-Alex
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On Wed, May 16, 2018 at 2:51 PM, Wesley Hayutin wrote:
>
>
> On Wed, May 16, 2018 at 2:41 PM Doug Hellmann wrote:
>>
>> Excerpts from Petr Kovar's message of 2018-05-16 17:39:14 +0200:
>> > Hi all,
>> >
>> > In the past few years, we've seen several
On Wed, May 16, 2018 at 1:04 PM, Doug Hellmann wrote:
> Excerpts from Wesley Hayutin's message of 2018-05-16 12:51:25 -0600:
>> On Wed, May 16, 2018 at 2:41 PM Doug Hellmann wrote:
>>
>> > Excerpts from Petr Kovar's message of 2018-05-16 17:39:14
On Wed, May 16, 2018 at 3:05 PM Doug Hellmann wrote:
> Excerpts from Wesley Hayutin's message of 2018-05-16 12:51:25 -0600:
> > On Wed, May 16, 2018 at 2:41 PM Doug Hellmann
> wrote:
> >
> > > Excerpts from Petr Kovar's message of 2018-05-16
On 5/16/2018 12:24 PM, Jay Pipes wrote:
Quota checks happen before Nova's scheduler gets involved, so having a
scheduler filter handle quota usage checking is pretty much a non-starter.
For server resources yeah, for things like instances quota, CPU and RAM,
etc.
Nova does an up-front quota
Excerpts from Wesley Hayutin's message of 2018-05-16 12:51:25 -0600:
> On Wed, May 16, 2018 at 2:41 PM Doug Hellmann wrote:
>
> > Excerpts from Petr Kovar's message of 2018-05-16 17:39:14 +0200:
> > > Hi all,
> > >
> > > In the past few years, we've seen several efforts
Excerpts from Jeremy Stanley's message of 2018-05-16 17:42:09 +:
> On 2018-05-16 13:16:09 +0200 (+0200), Dmitry Tantsur wrote:
> > On 05/15/2018 09:19 PM, Juan Antonio Osorio wrote:
> > > As part of the work from the Security Squad, we added the
> > > ability for the containerized undercloud
Hi Dear Neutron Team,
Our team dinner will take place at Al Porto Ristorante, which is located
half a mile from the Summit venue:
321 Water St, Vancouver, BC V6B 1B8
Phone: +1 604-683-8376
http://www.alporto.ca
https://goo.gl/8q5Qy2
Our reservation is at 7pm, under mi name: "Miguel Lavalle"
On Wed, May 16, 2018 at 2:41 PM Doug Hellmann wrote:
> Excerpts from Petr Kovar's message of 2018-05-16 17:39:14 +0200:
> > Hi all,
> >
> > In the past few years, we've seen several efforts aimed at automating
> > procedural documentation, mostly centered around the
Excerpts from Petr Kovar's message of 2018-05-16 17:39:14 +0200:
> Hi all,
>
> In the past few years, we've seen several efforts aimed at automating
> procedural documentation, mostly centered around the OpenStack
> installation guide. This idea to automatically produce and verify
> installation
On 2018-05-16 13:16:09 +0200 (+0200), Dmitry Tantsur wrote:
> On 05/15/2018 09:19 PM, Juan Antonio Osorio wrote:
> > As part of the work from the Security Squad, we added the
> > ability for the containerized undercloud to encrypt the
> > overcloud plans. This is done by enabling Swift's encrypted
On 05/16/2018 01:01 PM, Nadathur, Sundar wrote:
Hi,
The Cyborg quota spec [1] proposes to implement a quota (maximum
usage) for accelerators on a per-project basis, to prevent one project
(tenant) from over-using some resources and starving other tenants.
There are separate resource
On 05/16/2018 10:39 AM, Petr Kovar wrote:
Hi all,
In the past few years, we've seen several efforts aimed at automating
procedural documentation, mostly centered around the OpenStack
installation guide. This idea to automatically produce and verify
installation steps or similar procedures was
On 2018-05-16 18:24:45 +0200 (+0200), Petr Kovar wrote:
[...]
> I'd like to propose replacing the reference to the IBM Style Guide
> with a reference to the developerWorks editorial style guide
> (https://www.ibm.com/developerworks/library/styleguidelines/).
> This lightweight version comes from
Hi,
The Cyborg quota spec [1] proposes to implement a quota (maximum
usage) for accelerators on a per-project basis, to prevent one project
(tenant) from over-using some resources and starving other tenants.
There are separate resource classes for different accelerator types
(GPUs, FPGAs,
Hi all,
For OpenStack documentation contributors, we provide a basic style guide
that describes most important guidelines for writing, user interface
guidelines, and RST conventions:
https://docs.openstack.org/doc-contrib-guide/writing-style.html
Hi all,
Due to OpenStack Vancouver Summit, we canceled the weekly team meeting
at 2018-05-22. Updated Meeting schedule can be found at
https://wiki.openstack.org/wiki/Zun#Meetings .
Best regards,
Hongbin
__
OpenStack
Hi all,
In the past few years, we've seen several efforts aimed at automating
procedural documentation, mostly centered around the OpenStack
installation guide. This idea to automatically produce and verify
installation steps or similar procedures was mentioned again at the last
Summit
On 8/31/2017 2:14 PM, Matt Riedemann wrote:
The change to deprecate the monkey_patch and monkey_patch_modules option
was deprecated in Queens, so they wouldn't be removed until the Rocky
release at the earliest. We don't backport changes which deprecate things.
My recommendation to you is
Thanks for the reminder. We replaced the pycrypto code in Barbican but
forgot to remove the dependency in requirements.txt. A review has
been added to do this.
https://review.openstack.org/568879
On Sun, 2018-05-13 at 12:22 -0500, Matthew Thode wrote:
> This is a reminder to the projects
Hi Dear Neutron Team,
Due to the OpenStack Summit in Vancouver next week, we will cancel the
drivers meeting scheduled on May 24th at 1500UTC. We will resume our
meetings on May 31st at 1500UTC
Best regards
__
OpenStack
Hi Dear Neutron Team,
Due to the OpenStack Summit in Vancouver next week, we will cancel the
drivers meeting scheduled on May 25th at 1400UTC. We will resume our
meetings on June 1st at 1400UTC
Best regards
Miguel
__
On 2018-05-16 15:17:52 +0200 (+0200), Bogdan Dobrelya wrote:
[...]
> My understanding, I may be totally wrong, is that unlike to
> packages and repos (do not count OSTree [0]), containers use
> layers and can be exported into tarballs with built-in
> de-duplication. This makes idea of tossing
Hi Dear Neutron Team,
Due to the OpenStack Summit in Vancouver next week, we will cancel the team
meeting scheduled on May 22nd at 1400UTC. We will resume our meetings on
May 28th at 2100UTC
Best regards
Miguel
__
OpenStack
s/#edge-computing-irc/#edge-computing-group
Sorry for the typo.
The meeting starts now.
ad_ri3n_
- Mail original -
> De: "Dimitri Pertin"
> À: openstack-dev@lists.openstack.org
> Cc: openstack-s...@lists.openstack.org, edge-comput...@lists.openstack.org
>
On Wed, May 16, 2018 at 9:55 AM, Doug Hellmann
wrote:
> Excerpts from Lingxian Kong's message of 2018-05-16 11:12:01 +1200:
> > Hi,
> >
> > Maybe I missed the original discussion, I found the 'mutable'
> configuration
> > implementation relies on oslo.service, but is there
Excerpts from Lingxian Kong's message of 2018-05-16 11:12:01 +1200:
> Hi,
>
> Maybe I missed the original discussion, I found the 'mutable' configuration
> implementation relies on oslo.service, but is there any guide for the
> projects using cotyledon instead?
oslo.service implements the signal
On 5/16/18 2:17 PM, Jeremy Stanley wrote:
On 2018-05-16 11:31:30 +0200 (+0200), Bogdan Dobrelya wrote:
[...]
I'm pretty sure though with broader containers adoption, openstack
infra will catch up eventually, so we all could benefit our
upstream CI jobs with affinity based and co-located data
Hi all,
The docs meeting will continue today at 16:00 UTC in
#openstack-doc, as scheduled. For more details, see the meeting page:
https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
Cheers,
pk
__
OpenStack Development
Friendly reminder that the "early bird" pricing for the next PTG in
Denver in September is ending at 6:59 UTC Friday (which translates to
Thursday, 23:59 Pacific time).
If you are concerned with pricing increase and want to snatch the $199
ticket deal before the price jumps to $399, act now !
On 2018-05-16 11:31:30 +0200 (+0200), Bogdan Dobrelya wrote:
[...]
> I'm pretty sure though with broader containers adoption, openstack
> infra will catch up eventually, so we all could benefit our
> upstream CI jobs with affinity based and co-located data available
> around for consequent build
Hi,
On 05/15/2018 09:19 PM, Juan Antonio Osorio wrote:
Hello!
As part of the work from the Security Squad, we added the ability for the
containerized undercloud to encrypt the overcloud plans. This is done by
enabling Swift's encrypted volumes, which require barbican. Right now it's
turned
Good morning,
just a quick note when packing the suitcase: We have a Docs/I18n Forum
session on Monday 21th, 13:30, direct after lunch [1]. Take the chance
to discuss topics about project onboarding with translation or
documentation, usage of translated documents or tools. Or just come to
Hi,
As there is summit in next week, neutron QoS meeting from 22.05 is cancelled.
Next meeting will be normally on 05.06.2018
—
Slawek Kaplonski
Senior software engineer
Red Hat
__
OpenStack Development Mailing List (not
Hi,
As there is summit in next week, neutron CI meeting from 22.05 is cancelled.
Next meeting will be normally on 29.05
—
Slawek Kaplonski
Senior software engineer
Red Hat
__
OpenStack Development Mailing List (not for
I thought it is Open Source MANO.
On Thu, May 3, 2018, 4:45 PM duon...@vn.fujitsu.com
wrote:
> Hi Ben,
>
> >>On 04/25/2018 11:31 PM, daidv at vn.fujitsu.com wrote:
> >> Hi forks,
> >>
> >> We tested and completed our process with OVO migration in Queens cycle.
> >> Now,
Hi team,
As usual we will have our weekly meeting starting UTC1400 at
#openstack-cyborg, initial agenda as follows:
1. summit prep
2. sub team report
3. critical rocky spec review
4. open patches
--
Zhipeng (Howard) Huang
Standard Engineer
IT Standard & Patent/IT Product Line
Huawei
- Original Message -
> This is a reminder to the projects called out that they are using old,
> unmaintained and probably insecure libraries (it's been dead since
> 2014). Please migrate off to use the cryptography library. We'd like
> to drop pycrypto from requirements for rocky.
>
>
On 5/15/18 10:31 PM, Wesley Hayutin wrote:
On Tue, May 15, 2018 at 1:29 PM James E. Blair > wrote:
Jeremy Stanley > writes:
> On 2018-05-15 09:40:28 -0700 (-0700), James E. Blair wrote:
Graham Hayes wrote:
Any additional background on why we allowed LCOO to operate like this
would help a lot.
We can't prevent any group of organizations to work in any way they
prefer -- we can, however, deny them the right to be called an OpenStack
workgroup if they fail at openly
Thanks for the reminder
we updated the code to 1.1.1 , and current info can be found
https://pypi.org/project/zVMCloudConnector/#description
detailed code can be found here , you can see no block for webob anymore
https://github.com/mfcloud/python-zvm-sdk/blob/master/requirements.txt#L7
please
Bump the last time
Hi all,
As we keep adding more info to the migration guideline [1], you might like
to take a look again.
And do hope it will make things easier for you. If not, please find me in
irc or mail.
[1] https://etherpad.openstack.org/p/Heat-StoryBoard-Migration-Info
2018-05-10
60 matches
Mail list logo