On 11/5/18 3:21 AM, Mohammed Naser wrote:
Sent from my iPhone
On Nov 5, 2018, at 10:19 AM, Thierry Carrez wrote:
Monty Taylor wrote:
[...]
What if we added support for serving vendor data files from the root of a
primary URL as-per RFC 5785. Specifically, support deployers adding a json
Folks, I have drafted a few more sections [0] for your /proof reading
and kind review please. Also left some notes for TBD things, either for
the potential co-authors' attention or myself :)
[0]
https://github.com/bogdando/papers-ieee/blob/master/ICFC-2019/LaTeX/position_paper_1570506394.pdf
On Wed, Oct 10, 2018 at 8:45 AM Corey Bryant
wrote:
> Hi All,
>
> I'd like to enable py37 unit tests in the gate.
>
> == Background ==
>
> I work on OpenStack packaging for Ubuntu. During the Rocky release (Ubuntu
> Cosmic) I tried to fix py37 bugs upstream as I came across them. There
> ended
On 11/6/18 3:25 AM, Eyal B wrote:
Hi,
Because of this fix https://review.openstack.org/#/c/611369/ ceilometer
which uses oslo.cache for redis fails to publish to gnocchi
see this log:
Doug,
I have such a list put together (my various installation documents for
getting these clouds working in FIPS mode) but it's hardly ready for
public consumption. I planned on releasing each bit as a code change
and/or bug ticket and letting the community consume it as it figures
some of these
On Tue, Nov 6, 2018 at 9:19 AM Joshua Cornutt wrote:
>
> Another approach would be to make the projects "FIPS aware" where we
> choose the hashing algorithm based on the system's FIPS-enforcing
> state. An example of doing so is what I'm proposing for Django
> (another FIPS-related patch that
The downside of this particular approach is that systems that get
promoted to "FIPS mode" will get into a sticky situation as the code
originally set hashes to use MD5 but then switches to SHA-x after
users may have already used MD5 (and thus have that data stored /
recalled). The best way really
Hey all,
Here is what's on my radar for keystone-specific sessions and talks next
week:
*Tuesday*
- Change ownership of resources [0]
- Keystone Project Update [1]
- OpenStack Policy 101 [2]
- Keystone Project Onboarding [3]
- Gaps between OpenStack and business logic with Adjutant [4]
Just a reminder that we won't be holding a weekly meeting for keystone next
week due to the OpenStack Summit in Berlin.
Meetings will resume on the 20th of November.
Thanks,
Lance
__
OpenStack Development Mailing List (not
Thanks everyone for the suggestions :)
I will try those.
On Wed, Nov 7, 2018 at 8:39 AM Tony Breeds wrote:
> On Tue, Nov 06, 2018 at 06:07:18AM -0800, Julia Kreger wrote:
> > I don't know how the cost structure works for Bluejeans, but I've found
> it
> > works very well for calls with many
On 11/6/2018 5:24 PM, Rochelle Grober wrote:
Maybe the fastest way to get info would be to turn it off and see where the
code barfs in a long run (to catch as many projects as possible)?
There is zero integration testing for lazy translation, so "turning it
off and seeing what breaks"
After hacking on the PoC for awhile [1] I have finally pushed up a spec
[2]. Behold it in all its dark glory!
[1] https://review.openstack.org/#/c/603930/
[2] https://review.openstack.org/#/c/616037/
On 8/22/2018 8:23 PM, Matt Riedemann wrote:
Hi everyone,
I have started an etherpad for
Hi,
Thanks for bringing this up.
On Tue, Nov 06, 2018 at 01:12:55PM +0100, Dr. Jens Harbott (frickler) wrote:
> Dear OpenStackers,
>
> earlier this year Ubuntu released their current LTS version 18.04
> codenamed "Bionic Beaver" and we are now facing the task to migrate
> our devstack-based
On Tue, Nov 6, 2018, at 2:02 PM, Ghanshyam Mann wrote:
> Thanks Jens.
>
> As most of the base jobs are in QA repo, QA team will coordinate this
> migration based on either of the approach mentioned below.
>
> Another point to note - This migration will only target the zuulv3 jobs
> not the
On Wed, 07 Nov 2018 06:51:32 +0900 Slawomir Kaplonski
wrote
> Hi,
>
> > Wiadomość napisana przez Jeremy Stanley w dniu
> > 06.11.2018, o godz. 22:25:
> >
> > On 2018-11-06 22:05:49 +0100 (+0100), Slawek Kaplonski wrote:
> > [...]
> >> also add jobs like
Thanks Jens.
As most of the base jobs are in QA repo, QA team will coordinate this migration
based on either of the approach mentioned below.
Another point to note - This migration will only target the zuulv3 jobs not the
legacy jobs. legacy jobs owner should migrate them to bionic when they
I do intend to respond to all the excellent discussion on this thread,
but right now I just want to offer an update on the code:
I've split the effort apart into multiple changes starting at [1]. A few
of these are ready for review.
One opinion was that a specless blueprint would be appropriate.
Hi Team,
We will have our regular weekly meetings tomorrow at usual time UTC 1400.
Please be aware that North America has just shifted to winter time this
week, which mean it would be 10 pm Beijing time, 6 am PST and 9 am EST. We
probably will adjust the time a little bit starting next week.
The
Team,
We will have a meeting today at 8:00 UTC on openstack-meeting-alt channel.
Alex
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Hi,
> Wiadomość napisana przez Jeremy Stanley w dniu
> 06.11.2018, o godz. 22:25:
>
> On 2018-11-06 22:05:49 +0100 (+0100), Slawek Kaplonski wrote:
> [...]
>> also add jobs like "devstack-xenial" and "tempest-full-xenial"
>> which projects can use still for some time if their job on Bionic
>>
On Wed, 07 Nov 2018 07:07:33 +0900 Clark Boylan
wrote
> On Tue, Nov 6, 2018, at 2:02 PM, Ghanshyam Mann wrote:
> > Thanks Jens.
> >
> > As most of the base jobs are in QA repo, QA team will coordinate this
> > migration based on either of the approach mentioned below.
> >
On Tue, Nov 06, 2018 at 06:07:18AM -0800, Julia Kreger wrote:
> I don't know how the cost structure works for Bluejeans, but I've found it
> works very well for calls with many people on video. I typically have calls
> with 14+ people nearly everyone has their video enabled without a problem.
On 2018-11-06 22:05:49 +0100 (+0100), Slawek Kaplonski wrote:
[...]
> also add jobs like "devstack-xenial" and "tempest-full-xenial"
> which projects can use still for some time if their job on Bionic
> would be broken now?
[...]
That opens the door to piecemeal migration, which (as we similarly
I seem to recall list discussion on this quite a ways back. I think most of it
happened on the Docs ml, though. Maybe Juno/Kilo timeframe? If possible, it
would be good to search over the code bases for places it was called to see its
current footprint. I'm pretty sure it was the docs folks
Ghanshyam Mann writes:
> On Wed, 07 Nov 2018 06:51:32 +0900 Slawomir Kaplonski
> wrote
> > Hi,
> >
> > > Wiadomość napisana przez Jeremy Stanley w dniu
> 06.11.2018, o godz. 22:25:
> > >
> > > On 2018-11-06 22:05:49 +0100 (+0100), Slawek Kaplonski wrote:
> > > [...]
> >
Hello,
You can try Apache OpenMeetings, it's good enough!
Cheers,
Hien.
On Tue, Nov 6, 2018 at 8:36 PM Trinh Nguyen wrote:
> Hi,
>
> I tried several free tools for team meetings, vPTG, and webinars but there
> are always drawbacks ( because it's free, of course). For example:
>
>- Google
On 11/5/18 11:23 PM, Wesley Hayutin wrote:
> Greetings,
>
> Please be aware of the following patch [1]. This updates ansible in
> queens, rocky, and stein.
> This was just pointed out to me, and I didn't see it coming so I
> thought I'd email the group.
>
> That is all, thanks
>
> [1]
Hi All,
TC office hour is started on #openstack-tc channel. Feel free to reach to us
for anything you want discuss/input/feedback/help from TC.
-gmann
__
OpenStack Development Mailing List (not for usage questions)
Hi,
Because of this fix https://review.openstack.org/#/c/611369/ ceilometer
which uses oslo.cache for redis fails to publish to gnocchi
see this log:
Sean McGinnis writes:
> I'm interested in some feedback from the community, particularly those running
> OpenStack deployments, as to whether FIPS compliance [0][1] is something folks
> are looking for.
>
> I've been seeing small changes starting to be proposed here and there for
> things like
Hi,
Kuryr-Kubernetes LBaaSv2 gates are currently broken due to bug [1] in
python-neutronclient. Until commit [2] is merged and a new version of
the client is released I'm proposing to make those gates non-voting
[3].
[1] https://bugs.launchpad.net/python-neutronclient/+bug/1801360
[2]
Dear OpenStackers,
earlier this year Ubuntu released their current LTS version 18.04
codenamed "Bionic Beaver" and we are now facing the task to migrate
our devstack-based jobs to run on Bionic instead of the previous LTS
version 16.04 "Xenial Xerus".
The last time this has happened two years
On Mon, Nov 5, 2018 at 11:02 PM Manuel Sopena Ballesteros
wrote:
>
> Dear Openstack community.
>
>
>
> I am setting up pci passthrough for GPUs using aliases.
>
>
>
> I was wondering the meaning of the fields device_type and numa_policy and how
> should I use them as I could not find much
On Mon, Nov 5, 2018 at 12:50 PM Dmitry Tantsur wrote:
>
>
> On Mon, Nov 5, 2018, 20:07 Julia Kreger wrote:
>
>> *removes all of the hats*
>>
>> *removes years of dust from unrelated event planning hat, and puts it on
>> for a moment*
>>
>> In my experience, events of any nature where convention
On 11/5/2018 10:43 AM, Matt Riedemann wrote:
If you are seeing this error when implementing and running the upgrade
check command in your project:
Traceback (most recent call last):
File
Hi,
I tried several free tools for team meetings, vPTG, and webinars but there
are always drawbacks ( because it's free, of course). For example:
- Google Hangout: only allow a maximum of 10 people to do the video calls
- Zoom: limits about 45m per meeting. So for a webinar or conference
We measured results and would like to shut down check jobs in RDO cloud CI
today. Please let us know if you have objections.
Thanks
On Thu, Nov 1, 2018 at 12:14 AM Wesley Hayutin wrote:
> Greetings,
>
> The TripleO-CI team would like to consider shutting down all the third
> party check jobs
On Tue, Nov 6, 2018 at 5:07 AM Doug Hellmann wrote:
> Sean McGinnis writes:
>
> > I'm interested in some feedback from the community, particularly those
> running
> > OpenStack deployments, as to whether FIPS compliance [0][1] is something
> folks
> > are looking for.
> [trim]
>
> I know we've
I don't know how the cost structure works for Bluejeans, but I've found it
works very well for calls with many people on video. I typically have calls
with 14+ people nearly everyone has their video enabled without a problem.
The limiting factor is really if one participant has limited or somewhat
On Tue, Nov 6, 2018 at 2:04 PM Julia Kreger
wrote:
>
>
> On Tue, Nov 6, 2018 at 5:07 AM Doug Hellmann
> wrote:
>
>> Sean McGinnis writes:
>>
>> > I'm interested in some feedback from the community, particularly those
>> running
>> > OpenStack deployments, as to whether FIPS compliance [0][1]
Luke Hinds writes:
> On Tue, Nov 6, 2018 at 2:04 PM Julia Kreger
> wrote:
>
>>
>>
>> On Tue, Nov 6, 2018 at 5:07 AM Doug Hellmann
>> wrote:
>>
>>> Sean McGinnis writes:
>>>
>>> > I'm interested in some feedback from the community, particularly those
>>> running
>>> > OpenStack deployments, as
Hi all,
I am used to report the os-ken related progress in the neutron team meeting.
After switching to winter time, I am not able to attend the meeting at Tuesday
1400 UTC. I sent out the report in the ML instead. Below is the progress in
last week.
* The os-ken 0.2.0 is released:
Hi Matt,
Thanks for fixing the upgrade checker patch on Searchlight [1]. It works.
[1] https://review.openstack.org/#/c/613789/
On Tue, Nov 6, 2018 at 11:28 PM Matt Riedemann wrote:
> On 11/5/2018 10:43 AM, Matt Riedemann wrote:
> > If you are seeing this error when implementing and running
43 matches
Mail list logo
