p in touch via email, IRC, 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 Ma
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
__
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
+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 the database modeling;
similar vein,
OpenStack Infra has a signing 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&#
fact that it's basically a RedHat project isn't going to
> turn me off...
Contributing to OpenStack is intimidating, if not utterly
discouraging, to people unfamiliar with CLAs and Gerrit. There's a lot
of process that goes into contributing
it seems 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 ado
schedule
> On 3/2/17 9:45 AM, Ian Cordasco wrote:
> > -Original Message-
> > From: Telles Nobrega
> > Reply: OpenStack Development Mailing List (not for usage questions)
> >
> > Date: March 2, 2017 at 08:01:29
> > To: OpenStack Development Mailing Li
. But if we can make a habit of
creating excellent release candidates, we can spend the intermediate
time on documentation. I think that's a good compromise.
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usa
mailing list that the
release team can use to reach PTLs and Release CPLs with
notifications? Would that satisfy it? At that point, it would be up to
each PTL to subscribe, etc., but it also prevents the Release team
from having to generate
f 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
the likely costs.
--
Ian Cordasco
__
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 reviews and
contributions have been very valuable.
--
Ian Cordasco
__
removal, I'd like to propose also removing Mike
Fedosin from the stable-maintenance team for Glance.
--
Ian Cordasco
Glance Stable Branch Liaison
__
OpenStack Development Mailing List (not for usage questions)
Unsub
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 saw in the cold upgrades t
you with the stability of those branches?
> > There are reviewstats tools for seeing the stable review numbers for Heat, I
> > haven't run that though to check against those proposed above, but it's
> > probably something I'd do first before just adding a bun
ter
> at letting go
> of old things.
I agree with the idea of making it easier for new contributors from
outside our walled garden of paid contributors. I won't further derail
this thread with my opinions of how corporations will begin to explo
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 than "making it easy to deploy OpenStack" (via the
> > deployment tools in the tent). Doi
/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/packaging teams, the service
teams will likely be out of a job. People will/can not deploy
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 Cordasco
__
OpenSt
15:54:41.817 | +./stack.sh:exit_trap:502 [[ -z
> /opt/stack/logs ]]
> 2017-02-14 15:54:41.821 | +./stack.sh:exit_trap:505
> /home/stack/devstack/tools/worlddump.py -d /opt/stack/logs
> 2017-02-14 15:54:43.088 | +./stack.sh:exit_trap:511 exit 1
> stack@coritel-VirtualBox:~/devstack$
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 pushing for a transit
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
__
OpenStack Development Mailing
Glance is 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
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 Development Mailing List
aints problem. Whatever version
of gnocchiclient is being installed, the gnocchiclient.utils module
doesn't have "encode_resource_id" present and so the tests fail.
I suspect this is caused by some newer version of gnocchic
that pypa/setuptools recently started hard
depending (instead of vendoring) on its dependencies. Older versions
of pip don't recognize that setuptools' dependencies must be installed
before it is installed.
--
Ian Cordasco
__
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 than the previous version). I
s patches is if you are actively working on this bug.
>
> Have a good week, everyone!
>
> cheers,
> brian
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-re
NED 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.
>
> +3.14
+2.718
--
Ian Cordasco
__
OpenS
suspect and I expect all 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:unsubscr
/pipermail/openstack-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...
deliverables.yaml file in Kolla repository which will allow us to keep
> track of deliverables. Review incoming:)
Is Kolla not using openstack/releases to track deliverables? If so, why
duplicate that information?
--
Ian Cordasco
__
. 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 meeting.
0 concerns on my end.
Good work, Dharini!
--
Ian Cordasco
__
t; slower by default. I know he's working with upstream developers to fix
> > it, but it was problematic for OSA.
>
> /me learns things and also will keep his mouth shut next time :)
You were right that this was part of an effort towards multi-distro
support though!
--
Ian Corda
s etc.
>
> I believe this is more about supporting folks who want to run on
> Centos/RHEL, rather than a step to removing Ubuntu support.
That's also correct. OpenStack-Ansible is attempting to support
multipl
ng 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 it was problematic for OSA.
--
Ian Cordasco
_
t 9:08 AM, Ian Cordasco
> wrote:
>
> > -Original Message-
> > From: Chuck Short
> > Reply: OpenStack Development Mailing List (not for usage questions)
> >
> > Date: January 18, 2017 at 08:01:46
> > To: OpenStack Development Mailing List
>
unchpad.net/glance/+bug/1657459). I suspect what we'll
do for now is blacklist the 1.7.x releases in openstack/requirements.
It seems a bit late in the cycle to bump the minimum version to 1.7.0
so we can safely fix this without having to deal with
incompatibil
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
> implementation of the wrapper to accomm
?
> 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. Let me offer two observations.
> >>
> >> First, Trove has long debated the ideal s
rhaps it's verbose,
but it 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
adoption because it seems 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
upported" which involves
joining the list of projects with the "vulnerability:managed" tag
(https://governance.openstack.org/tc/reference/tags/vulnerability_managed.html).
https://governance.openstack.org/tc/reference/tags/vulnerability_managed.html#requirements
describes the re
on this
list consider "normal" deployments of OpenStack 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
--
is 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
for security, but if
> that exists, 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 sti
]
> 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 secure
solution to deploy. Can Barbican use that as a backend secret store?
--
Ian Cordasco
_
ice as
vulnerabilities are found, disclosed, and fixed in their clouds. If
Barbican is as difficult to deploy as Rob is suggesting (that even
DogTag is difficult to deploy) maybe developers should be focusing on
fixing that instead of haphazardly reimplementing Barbican?
--
Ian Cordasco
__
/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 can confirm this.
--
Ian Cordasco
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 on the project navigator alarming (it looks
> > like some of this information is potentially out of date)?
g/+bug/1656843
>
> https://github.com/OpenStackweb/openstack-org/pull/59
So, if I understand the two links correctly, changes are planned to
make that tag better and until they're made you're going to stop
displaying it using that with projects. Is that co
ll§ion=all
[4]:
http://packages.ubuntu.com/search?keywords=barbican&searchon=names&suite=all§ion=all
[5]:
https://software.opensuse.org/search?utf8=✓&q=barbican&search_devel=false&search_unsupported=false&baseproject=openSUSE:Leap:42.2
Cheers,
--
Ian Cordasco
_
bit short-sighted
and foolish. While these projects 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 Cor
-Original Message-
From: Ian Cordasco
Reply: Ian Cordasco
Date: January 13, 2017 at 08:12:12
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [glance][tempest][api] community images,
tempest tests, and API stability
> And besides &quo
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. We'd really appreciate
cooperation on this.
And besides
-Original Message-
From: Ian Cordasco
Reply: Ian Cordasco
Date: January 11, 2017 at 11:09:11
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] updating to pycryptome from pycrypto
> -Original Message-
> From: Matthew Thode
&
hat
pycryptome has probably inherited), I'd suspect that the best effort
for those of us interested, is to help pysaml2 express the deficits it
has with cryptography so it can move to a better project. If there are
no deficits, then we should focus on helping pysaml2 p
eant to send this to the OpenStack mailing list, but
in case you did, I don't know of a good way of doing that. That said,
there is at least one project that attempts to automate it for you
(openstack-ansible-security). I've CC'd one of the cores to grab their
attention in case they can
here should
allow for shorter, concise, and conclusive discussions in the meetings
(if they're necessary at all).
Cheers!
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: opens
: [openstack-dev] [Release-job-failures] Release of
openstack/glance failed
> On Mon, Dec 12, 2016 at 09:46:54AM -0600, Ian Cordasco wrote:
> >
> >
> > -Original Message-
> > From: Andreas Jaeger
> > Reply: OpenStack Development Mailing List (not for usage quest
d of lines.
>
> -- Ed Leafe
Worth noting, though, that if you are using multiple context managers
in a single 'with' statement that you can't use ()s to split them
across multiple lines, you *must* use \s, otherwise it is
syntactically invalid. (Weird, yes, I know. Guido h
is silly if the tool 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 just my $0.02.
[1]: https://w
#x27;ve chosen (and
yes, you've chosen this) to have a negative assumption about this
contributor's efforts, I've chosen to believe they're looking to fill
a gap. Increasing the productivity of new contributors to OpenStack is
a positive improvem
spirit 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
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:
> > > Hey everyone,
> > >
> > > It seems a contributor has written a script to add CONTRIBUTING.rst
&g
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 there are two better places for this information
> > > that are already standards in OpenStack:
>
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:
> >
> > * README.rst
> > * HACKING.rst
> >
> > Most projects include link
andoned some of the patches. Let's see if we can come to an
agreement about how to improve 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
_
ts?
>
> [1] https://review.openstack.org/#/c/411786/
> [2] https://etherpad.openstack.org/p/zunclient_openstack-client-cli
>
> Best regards,
> Hongbin
> __
> OpenStack Development Mailing List (not for usage qu
re important
than including the people who have chosen to tell us about their experiences.
No one is saying "Michał is evil" or "Michał is a bad person" or "Kolla is a
contributor-hostile project". What we're saying is - Kolla did some things that
excluded collabo
en'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,
though, and respond to their concerns.
--
Ian Cordasco
, 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
__
OpenStack Development Mailing List (not for usag
rg/#/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://bugs.launchpad.net/glance/+bug/1585917
> >
> >
> > Please take a look
> > ==
> 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"
> meetings a week (by inc0's admission). The video meetings seem to replace the
> time that
>
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 way? For example, Glance's projects were
> > missed in the recent liberty end of life work.
& Tony don't have to or is that
something that isn't planned to work through openstack/releases?
Cheers,
--
Ian Cordasco
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
.githubusercontent.com/tbreeds/93cd346c37aa46269456f56649f0a4ac/raw/liberty_eol_data.txt
>
Glance was late to the party, but it should have had its liberty branches EOL'd
as well.
--
Ian Cordasco
__
OpenStack D
ate.
Further, the kolla team seems to think that code submissions sent after a
meeting are sufficient artifacts from the meeting, which there seems to be a
majority who feel otherwise. Based on Jeffrey's descriptions, inc0's emails,
and the rest
+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 can see that he's thorough and
> > comprehensive in
n 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 review and backport yourself:
>
> https://review.openstack.org/409642
rving 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 (no
> 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 actually
> xstatic-angular-boot
e
> ImportError: No module named vine.five
The problem is kombu 4.0.1. We encountered the same problem when 4.0.0
was released and the blacklist for that version was added.
If your project were using constraints, you would not ru
g/periodic-stable/periodic-glance-docs-newton/c304f7c/
> : FAILURE in 4m 19s
> - periodic-glance-python27-db-newton
> http://logs.openstack.org/periodic-stable/periodic-glance-python27-db-newton/7d0750b/
> : SUCCESS in 8m 21s
--
Ian Cordasco
_
l have it mentioned on the agenda)
> - If we remove artificial scarcity, we could discontinue the
> #openstack-meeting-cp channel (which was created to facilitate the
> scheduling of cross-project temporary meetings) and just tell
> cross-project initiatives to
> There is a long conversation in the comments of the review, mainly with
> concerns from cores (purely developer's opinions).
You say that as if developer opinions (the folks who have to
understand and maintain your desired approac
mmunities (like 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
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 that more obvious
>From wh
I don't want it to be merged without appropriate discussion, so I've
-1'd the Workflow.
--
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
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]. And Now we have
> a
> bluep
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 would suggest instead that we try to make
> > this into
> a community goal. We would work with
etely remove reliance on MD5.
Doing this piecemeal via bugs will not be efficient and we'll need community
buy-in.
--
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
stack-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 in #openstack-infra.
Thank y'all for your hard work on this!
--
Ian Cordasco
_
h seems to allow 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 question
ifference 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
identify a specific provider and region and narrow this down to donated
resources. Thanks Tomislav, you've been v
d 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 unique identifier for host:
> hashlib.sha224(projectid + host_name).hexdigest()
I
- 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.
--
Ian Cordasco
__
-Original Message-
From: Ian Cordasco
Reply: Ian Cordasco
Date: November 16, 2016 at 07:06:27
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Stable] Usefulness of Weekly Meeting
> -Original Message-
> From: Tony
cluding me)
> ?state=not_in: 1
> ?state=out: 0
> ?not_state=in: 0
>
> I'd like to finish this poll by EOW so that more folks have the opportunity
> to express their preference.
>
> Cheers,
> milan
>
>
> 2016-11-15 13:50 GMT+01:00 Miles Gould :
>
: [openstack-dev] [Stable] Usefulness of Weekly Meeting
> On Tue, Nov 15, 2016 at 10:25:26AM -0800, Ian Cordasco wrote:
> > Hi all,
> >
> > So the stable-maintenance team (and liaisons to it) have had a meeting
> > scheduled for a while now. Recently, however, we'
other 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.openstac
1 - 100 of 365 matches
Mail list logo
