, or some other method. At the very
least, I'll see y'all
around PyCon, the larger F/OSS world, etc.
--
Ian Cordasco
IRC/Git{Hub,Lab}/Twitter: sigmavirus24
__
OpenStack Development Mailing List (not for usage questions
le system to share a vault key with Zuul.
> I don't think that has come up as a suggestion yet, but seems like it
> would work.
I suppose Barbican doesn't meet those requirements either, then, yes?
--
Ian Cordasco
__
+1. Welcome to the team, Thomas
On Mar 21, 2017 3:43 PM, "Jim Baker" wrote:
> *I nominate Thomas Maddox as a core reviewer for the Craton project.*
>
> Thomas has shown extensive knowledge of Craton, working across a range of
> issues in the core service, including down to
ning key for each release cycle that Gnocchi
is likely currently signed with when tarballs are released. You may
receive complaints that new releases aren't verifiable in the same
way, but that and needing a decent MANIFEST.in (assuming you're also
dropping your usage of PBR) will probably b
a lot
of process that goes into contributing. Moving this to a friendlier
(if not inferior) developer platform makes sense if there is interest
from companies not interested in participating in the OpenStack
community.
--
Ian Cordasco
___
ems like Murano relies on a lot of
unstable OpenStack infrastructure. While lots of people have
contributed time, energy, sweat, and tears to the project there are
still plenty of things that make Murano less than desirable. Perhaps
that's why the project has found so few adopters. I'm sure there ar
t;openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [docs][release][ptl] Adding docs to the
release schedule
> On 3/2/17 9:45 AM, Ian Cordasco wrote:
> > -Original Message-
> > From: Telles Nobrega
> > Reply: OpenStack Development Mailing List (not for usage
t
reviewing all of our documentation.
I know projects go sideways all the time. I think this was Glance's
first cycle like this in a few cycles. But if we can make a habit of
creating excellent release candidates, we can spend the intermediate
time on documentation. I thi
the Release team
from having to generate N emails where N is the number of
"business-only" lists.
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.open
st. Core project teams already occasionally bicker over changes
being approved that one half wouldn't have approved. This will
introduce yet another place for subjective reasoning between trusted
members of the community.
I'm not sure there's a great deal of value in those lists considering
effective immediately.
>
> Thank you to all of you in the community that I've worked with in IRC, at
> summits in Austin
> and Barcelona and to all of you who gave your time to review and improve my
> contributions.
Thank you for all your work on OSA Travis! Your r
; again as Glance contributors:
> - Kairat Kushaev
> - Mike Fedosin
> - Louis Taylor
On the heels of this removal, I'd like to propose also removing Mike
Fedosin from the stable-maintenance team for Glance.
--
Ia
In openstack/releases in the deliverables directory, e.g.,
https://github.com/openstack/releases/blob/master/deliverables/ocata/glance.yaml
Please excuse my top-posting and brevity as I am sending this from my phone
On Feb 20, 2017 5:01 PM, "Kenny Johnston" wrote:
> I
of people.
>
> I appreciate your guidance and input, but shouldn't we decide our
> stable maintainers, the same way we decide cores? The current list
> contains at least one person that doesn't contribute anymore, so it's
> not like it's super curated.
This is how every othe
ead with my opinions of how corporations will begin to exploit
that and invest less directly in OpenStack's development though.
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-de
t;openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [chef] Making the Kitchen Great Again: A
Retrospective on OpenStack & Chef
> On Thu, Feb 16, 2017 at 7:54 AM, Ian Cordasco wrote:
> > It seems like a lot of people view "developing OpenStack" as more
> > attractive
ankly. If we put our tooling
in repo, we'll likely then start collecting RPM/Debian/etc. packaging
in repo as well.
I think what would help improve willing bidirectional communication
between service and deployment/packaging teams would be an
understanding that without the deployment/pa
stone
is the implementation "Identity" is the thing it does and what you're
looking for from a service that is not Keystone.
Same goes for clouds that swap out RadosGW for Swift. They're looking
for an OpenStack Object Store API. They're not fuzzy matching on
project name.
--
Ian Cord
exit_trap:511 exit 1
> stack@coritel-VirtualBox:~/devstack$ sudo gedit
> /opt/stack/requirements/.venv/local/lib/python2.7/site-
> packages/pip/_vendor/requests/packages/__init__.py
Hi Carmine,
It looks like your virtualenv needs to be recreated. The version of
pip inside of it seems to be thor
ance team is a good chance to try something new
> > and interesting, and of course gain new experience.
> >
>
> I support you in your attempt to have a natural evolution. I think
> it's going to be harder and harder the longer you're developing Glare's
> features without pushi
rough an API. Our trademark
> interoperability requirements may even guarantee the presence of one
> already in any compliant deployment; I'll have to check... ;)
Well it's a storage service, so I hope the name doesn't start with "S". ;D
--
Ian Cordasco
___
s working on the image-import specifications to make v2
more interoperable.
That said, I'm convinced neither Glare nor Glance have learned the
scaling issues from the current designs. At best, the last I looked,
Glare has learned not to inherit Glance's caching design which has
been fre
On Feb 7, 2017 5:47 PM, "Joshua Harlow" wrote:
Likely just never pulled the trigger.
Seems like we should pull it though.
Will have to wait until Pike given the library release freeze
__
OpenStack
sed by some newer version of gnocchiclient being
used than is actually supported for stable/newton.
Cheers!
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
ndencies must be installed
before it is installed.
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/c
I love it!
Top-posting from my phone
On Jan 28, 2017 3:08 PM, "Brian Rosmaita"
wrote:
> Hello Glancers,
>
> Attached is the new draft logo of the Glance mascot. It looks to me
> like this draft captures the key features we requested (and is much more
> personable
; Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage questions)
g>
Subject: Re: [openstack-dev] [openstack-ansible] Proposing Amy Marrich for core
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 01/27/2017 08:29 AM, Alexandra Settle wrote:
> > I would like to propose Amy Marrich for the core team for OpenStack-Ansible
of Glance's cores to be a bit more
careful.
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org
-dev/2017-January/110617.html
--
Ian Cordasco
Your Friendly, But Stern, Neighborhood Release CPL
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
w incoming:)
Is Kolla not using openstack/releases to track deliverables? If so, why
duplicate that information?
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openst
Plus, she's
> willing to argue with me (and the other cores) about points of software
> engineering. She will be a great addition to the Glance core reviewers
> team.
>
> If you have any concerns, please let me know. I plan to add Dharini to
> the core list after this week's Glance mee
g>
Subject: Re: [openstack-dev] [openstack-ansible] Ocata deployed on CentOS 7!
> On 01/19/2017 10:14 AM, Ian Cordasco wrote:
> > -Original Message-
> > From: Adam Heczko
> > Reply: OpenStack Development Mailing List (not for usage questions)
> >
> > D
e is attempting to support
multiple distros at the same time. =)
--
Ian Cordasco
__
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
more details in this
> regard, point to Ubuntu specific bugs etc.
> Thanks.
I think Major may be referring to some serious performance regressions
found in Ubuntu 16.04. The default system Python is significantly
slower by default. I know he's working with upstream developers to fix
it, but
t;openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [keystone] webob 1.7
> On Wed, Jan 18, 2017 at 9:08 AM, Ian Cordasco
> wrote:
>
> > -Original Message-
> > From: Chuck Short
> > Reply: OpenStack Development Mailing List (not for usage question
o 1.7.0
so we can safely fix this without having to deal with
incompatibilities between versions.
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.or
ly be the sort of thing that
> would qualify for a backport, so it might take quite a while to see a
> real release.
>
> As you point out, the final version of the upstream API may be
> different. With a wrapper in place, we ought to be able to modify the
> imple
g>
Subject: Re: [openstack-dev] [all] [barbican] [security] Why are
projects trying to avoid Barbican, still?
> On 01/17/2017 07:57 AM, Ian Cordasco wrote:
> > On Mon, Jan 16, 2017 at 6:20 PM, Amrith Kumar wrote:
> >> Ian,
> >>
> >> This is a fascinating conversation.
is verbose for good reason. OpenStack's handling of embargoed
issues is pretty much as good as it gets for a project the size of
OpenStack. It benefits deployers and users by making the issue AND the
fix known at the same time which gives deployers the ability to
immediately consume the fix.
a worthwhile
goal. Yes Barbican can improve, so can Cinder. So let's keep these
discussions constructive, okay?
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-
es the requirements to attain that tag.
Cheers,
--
Ian Cordasco
__
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
against the increasing
demand to be able to deploy OpenStack on a FIPS compliant kernel, so
now we should all be designing our cryptographic based features in
ways that can satisfy both or have fallbacks in the case of FIPS.
Cheers
--
Ian Cordasco
___
right for their
> need, whether that is in the OpenStack community or not, it doesn't really
> matter (maybe at one point it did).
As long as they're using something secure, that's fine by me. Instead
these projects all want to reimplement the same functionality o
xists, it shall be better to use another algorithms, in terms of
> security.
>
> What do people think about it?
I think people should work on the Python patches *first*. Once they're
merged, *then* we should potentially create a wrapper (if it's still
necessary at that point) to do this.
er-project secret stores, has a solution been
> developed that solves both of these?
>
>
> [1]
> http://docs.openstack.org/project-install-guide/key-manager/draft/barbican-
> backend.html
So there seems to be a consensus that Vault is a good easy and secur
e focusing on
fixing that instead of haphazardly reimplementing Barbican?
--
Ian Cordasco
__
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
f deploying multi-site HSMs.
>
> * Vault supports HSM deployments also
>
> [1] http://docs.openstack.org/developer/castellan/
> [2] https://www.vaultproject.io/
The last I checked, Rob, they also support DogTag IPA which is purely
a Software based HSM. Hopefully the Barbican team
t;openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [all] [barbican] [security] Why are
projects trying to avoid Barbican, still?
> On 16/01/2017 13:38, Ian Cordasco wrote:
> > Is the problem perhaps that no one is aware of other projects using
> > Barbican? Is the status
ck.org>
Subject: Re: [openstack-dev] [barbican] Project Navigator Out of Date?
> On 16/01/17 21:55, Ian Cordasco wrote:
> >
> > Third, "Existence and quality of packages for this project in popular
> > distributions." it seems Fedora [2], Debian [3], Ubuntu [4],
ll
[5]:
https://software.opensuse.org/search?utf8=✓=barbican_devel=false_unsupported=false=openSUSE:Leap:42.2
Cheers,
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-re
are making themselves easier to
deploy, if not done properly they are potentially endangering their
users and that seems like a bigger problem than deploying Barbican to
me.
--
Ian Cordasco
Glance, Hacking, Bandit, and Craton core reviewer
-Original Message-
From: Ian Cordasco <sigmaviru...@gmail.com>
Reply: Ian Cordasco <sigmaviru...@gmail.com>
Date: January 13, 2017 at 08:12:12
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev
ot more work to fix
for large clouds than fixing some API interactions.
In short, the Glance team is ready, willing, and able to own the
responsibility for any breakage this causes users and any
interoperability problems this will pose.
-Original Message-
From: Ian Cordasco <sigmaviru...@gmail.com>
Reply: Ian Cordasco <sigmaviru...@gmail.com>
Date: January 11, 2017 at 11:09:11
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [opens
y so it can move to a better project. If there are
no deficits, then we should focus on helping pysaml2 port to
cryptography.
[1]: I'm verifying this with some people who know better
Cheers,
--
Ian Cordasco
__
OpenSta
openstack-ansible-security). I've CC'd one of the cores to grab their
attention in case they can help you.
Cheers,
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstac
tag should be watched by
the OSSP and having the lion's share of the conversation here should
allow for shorter, concise, and conclusive discussions in the meetings
(if they're necessary at all).
Cheers!
--
Ian Cordasco
__
December 14, 2016 at 00:18:38
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [Release-job-failures] Release of
openstack/glance failed
> On Mon, Dec 12, 2016 at 09:46:54AM -0600, Ian Cordasco wrote:
> &
(Weird, yes, I know. Guido has refused to make
this consistent on python-dev several times iirc.)
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.o
ool allows it
(or as is usually the case in OpenStack, is configured to allow it).
At that point it's subjective and a bit of a waste of people's time to
argue over it. From a perspective of personal preference, I prefer ()s
but that's jus
ovement for our community. It may not fix a bug or add
a feature, but it helps ramp up the people who will do that.
So please, let's keep this productive. If you want to discuss ways of
ratelimiting patchset contributions or some other nonsense, please
start a new thread.
Cheers,
--
Ian Co
of our last specification, I've put all
our options into one place and once we've started to reject them we
can move them to the Alternatives section with explanations.
Cheers,
--
Ian Cordasco
__
OpenStack Development Mailing
t;openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [all] Adding CONTRIBUTING.rst files to projects
> Hi stackers!
>
> On Wed, Dec 21, 2016 at 5:33 PM, Emilien Macchi wrote:
>
> > On Wed, Dec 21, 2016 at 10:22 AM, Ian Cordasco
> > wrote:
> > > H
t;openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [all] Adding CONTRIBUTING.rst files to projects
> On Wed, Dec 21, 2016 at 5:46 PM, Andreas Jaeger wrote:
>
> > On 2016-12-21 16:22, Ian Cordasco wrote:
> > > [...]
> > > That said, I think
t;openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [all] Adding CONTRIBUTING.rst files to projects
> On 2016-12-21 16:22, Ian Cordasco wrote:
> > [...]
> > That said, I think there are two better places for this information
> > that are already standards in OpenStack:
the experience for people finding our
projects and wanting to collaborate with us.
[1]:
https://review.openstack.org/#/q/owner:zhouyunfeng%40inspur.com+topic:addCONTRIBUTING.rst
--
Ian Cordasco
__
OpenStack Development Mailing
> 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
>
--
Ian Cordasco
__
a has received feedback about those things. And
Kolla should work to address that feedback. Unfortunately, all that's happened
is that Kolla is defending its practices and stating rather adamantly that it
intends to continue these exclusionary practices. Whatever the Kolla team's
intenti
Well I think we all agree that Google Hangouts aren't acceptable as they
exclude residents of an entire nation.
I don't think anyone's against teams using impromptu video calls to help
resolve conversations. I think each team needs to listen to its members,
thou
for 20
minutes, we decided on this because of reasons a, b, and c. Review:
https://review.openstack.org/:review_id has the final code details. Feel free
to ping us on irc or the review with further questions."
--
Ian Cordasco
_
to enable better request-id tracking:
> > https://review.openstack.org/#/c/352892/
> > This will be nice for operators, let's get it reviewed and merged!
> >
> > (6) Request for some insights and opinions for bug
> > https:
t;openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [kolla][tc] Video Meetings - input requested
> On Dec 14, 2016, at 7:45 AM, Ian Cordasco wrote:
> >
> > Taking you to the extreme of your statement, it seems there are several of
> > these "ad hoc"
> meeti
t;openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [release][ptl][all] self-service branch management
> On 2016-12-14 08:51:29 -0500 (-0500), Ian Cordasco wrote:
> [...]
> > I do have one question, will creating the branch's end-of-life
> > eventually work the same
ts were
missed in the recent liberty end of life work. Could we submit a
review to do that work so Josh & Tony don't have to or is that
something that isn't planned to work through openstack/releases?
Cheers,
--
Ian Cordasco
_
abandoned.
>
> Please let me know if there are any mistakes or latecomers to the list.
>
> Cheers,
> Josh
>
> [0]
> https://gist.githubusercontent.com/tbreeds/93cd346c37aa46269456f56649f0a4ac/raw/liberty_eol_data.txt
>
Glance was late to the party, but it shoul
inc0's emails,
and the rest of this thread, it seems quite clear that kolla isn't obeying one
of the 4 opens.
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-
+2 from me as well
On Dec 14, 2016 3:16 AM, "Erno Kuvaja" wrote:
> On Tue, Dec 13, 2016 at 10:05 PM, Brian Rosmaita
> wrote:
> > I'd like to propose Steve Lewis (stevelle on IRC) for Glance core. Take
> > a look at any of his reviews, and you
wer" than general nodepool nodes?
> >
> > glance does not use constraints in venv environment.
> >
> > It can be used since a few months. I'll send a change for master,
>
> I expect this needs backporting to stable branches - stable or glance
> team, please revie
New Years on 2017
Jan 2 (meaning people will still be on vacation).
The next meeting will be 2017 Jan 9.
Happy New Year and Happy Holidays!
--
Ian Cordasco
Craton Core Reviewer
__
OpenStack Development Mailing List
> On Dec 9, 2016, at 4:47 PM, Richard Jones wrote:
>
> Hi folks,
>
> We in Horizon land are looking to update to a new version of one of
> our dependencies, Angular Bootstrap version 2.2.0. We do this through
> xstatic packaging, so the release we'll be making is
g constraints, you would not run into this
problem. As such, what you need to do is wait for the blacklist to
pass master and be backported to the stable/mitaka branch in
openstack/requirements. The master patch has been approved and is
gating as I type this.
--
Ian Cordasco
__
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
-glance-python27-db-mitaka/404cb23/
> : SUCCESS in 6m 30s
> - periodic-glance-docs-newton
> http://logs.openstack.org/periodic-stable/periodic-glance-docs-newton/c304f7c/
> : FAILURE in 4m 19s
> - periodic-glance-python27-db-newton
> http://logs.openstack.org/periodic-stabl
tings) and just tell
> cross-project initiatives to use the regular channels
I think there's still value in #openstack-meeting-cp, but I don't feel strongly
enough to argue against its removal.
--
Ian Cordasco
hat's not the case.
> Please help me to bring it to life ;)
Please give us more detail and convince us to help you. :)
[1]: https://theagileadmin.com/what-is-devops/
--
Ian Cordasco
__
OpenStack Development Mailing List (not for
we used to)
and providing them with clear, unambiguous, narrowly defined use cases
that will convince them of the benefits of our feature requests.
Cheers,
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage
On Dec 2, 2016 3:07 AM, "Thierry Carrez" wrote:
>
> Doug Hellmann wrote:
> > Release team, please take a look at the attached logo and let me know
> > what you think.
>
> It's not immediately obvious to me it's a shepherd dog, but then I don't
> exactly know how to make
ttps://review.openstack.org/403775 which does this and adds an
upgrade release note to document the change.
I don't want it to be merged without appropriate discussion, so I've
-1'd the Workflow.
--
Ian Cordasco
__
Op
File beat is maintained be elastic and a part of their product line just
like ELK. It's a fantastic tool and quite flexible given its age and size
of codebase
On Nov 26, 2016 11:59 PM, "Jeffrey Zhang" wrote:
> Heka is marked deprecated in Kolla during Newton cycle[0].
any know cases of this happening? If so, can those be
> publicly documented to quantify how much this issue is hurting
> deployments?
I too would be very interested in learning about these.
>
> On Fri, Nov 18, 2016 at 9:57 AM, Ian Cordasco wrote:
> > Also, instead of creating bugs, I
of MD5 and have a goal for a cycle or two later to
completely remove reliance on MD5.
Doing this piecemeal via bugs will not be efficient and we'll need community
buy-in.
--
Ian Cordasco
__
OpenStack Development
loser to the date.
> >
> > If you have any questions, feel free to reply or use #openstack-infra on
> > freenode.
> >
> Greetings all,
>
> We have just approved this change and it will be live shortly. Again, if you
> are
> having problems, please join us
for squashing a previous cycle's migrations at
the start of a cycle.
Help and opinions are appreciated,
--
Ian Cordasco
Glance Release Liaison
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
n upstream version - just cannot reproduce.
> Although, the only difference which I see is that my machine is a bit slower,
> plus it uses only 2 workers.
Okay, we'll start keeping track of where these tests fail. We might be able to
i
formed like: {base URL}/{host_name}
> - Project should have a project specific link to external tool when querying
> via Nova servers API. This might be: {base URL}/project/{hostId}.
> hostId is exposed to project as it do not tell exact host, but otherwise as
> a u
; Which would result in log entry; if not - please ignore this idea)
Thanks for the help though, Tomislav! Did you look for the hash seed that tox
was using and try running the tests that way? I've been swamped with other
responsibilities this week so I haven't had time to investigate this myself
-Original Message-
From: Ian Cordasco <sigmaviru...@gmail.com>
Reply: Ian Cordasco <sigmaviru...@gmail.com>
Date: November 16, 2016 at 07:06:27
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [open
heers,
> milan
>
>
> 2016-11-15 13:50 GMT+01:00 Miles Gould :
>
> > On 14/11/16 20:52, Ian Cordasco wrote:
> >
> >> not_in is nice and explicit while nin and out are a bit, more clever. I
> >> think we should avoid trying to be clever.
Date: November 15, 2016 at 16:55:36
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [Stable] Usefulness of Weekly Meeting
> On Tue, Nov 15, 2016 at 10:25:26AM -0800, Ian Cordasco wrote:
> > Hi all,
week) and if we need to reschedule them to better serve
those who plan to attend.
Cheers,
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
1 - 100 of 355 matches
Mail list logo