with the topic
“remove-version-from-setup”.
-- Add a comment to the milestone tag request linking to the review from
step 2.
* Full thread:
http://lists.openstack.org/pipermail/openstack-dev/2015-December/081431.html
Cross-Project Spec Liaisons
===
* Mike Perez
t how you see it
> being implemented.
>
> Other liaisons typically have someone they're reporting to/working
> with directly. For example Oslo Liaisons and the Oslo PTL, release
> liaisons and the release team PTL, etc. It doesn't seem fair to
> ask each spec author to keep up with
-november-20151128/
--
Mike Perez
__
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
o
> understand exactly what they can and should expect in terms of the usage of
> their cloud. Finally, it will also mean that not OpenStack API
> functionality is COMPLETELY dependent on backend device. I know people are
> sick of hearing me say this, so I'll keep it short and say it one more ti
he
> product working group involved as well.
It might make sense to have the cross-project spec liaison [1] to be part of
this discussion?
[1] -
http://lists.openstack.org/pipermail/openstack-dev/2015-December/080869.html
--
Mike Perez
/CrossProjectMeeting#Proposed_agenda
[2] - https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee
[3] -
http://www.openstack.org/blog/2015/12/openstack-developer-mailing-list-digest-20151205/
--
Mike Perez
__
OpenStack Development
Perma Link:
http://www.openstack.org/blog/2015/12/openstack-developer-mailing-list-digest-20151205/
Success Bot Says
* AJaeger: With Juno End-of-Life, Python 2.6 testing has been removed from
OpenStack CI.
* Tell us yours via IRC with a message “#success [insert success]”.
*
Tuesdays at 2100
UTC.
[1] -
https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
Permalink:
http://www.openstack.org/blog/2016/01/openstack-developer-mailing-list-digest-20160108/
SuccessBot Says
===
* russellb: Ported OVS to Python 3.
* notmyname: Removed the beta tag on the swift erasure code docs.
* AJaeger: OpenStack configuration reference has been migrated
meeting will take place at it's usual time Tuesdays at 2100 UTC
when there are agenda items.
[1] - https://wiki.openstack.org/wiki/Meetings/CrossProjectM
--
Mike Perez
__
OpenStack Development Mailing List (not for usage
e rolled out to projects.
[1] - https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?
Perma link:
http://www.openstack.org/blog/2015/12/openstack-developer-mailing-list-digest-20151218/
Success Bot Says
* jroll: Ironic is using the devstack plugin.
* Tell us yours via IRC with a message “#success [insert success]”.
* All: https://wiki.openstack.org/wiki/Successes
Perma link:
http://www.openstack.org/blog/2015/11/openstack-developer-mailing-list-digest-november-20151121/
Success Bot Says
===
* vkmc: We got 7 new interns for the Outreachy program December-March 2015
round.
* bauzas: Reno in place for Nova release notes.
* AJaeger: We now
/2015/crossproject.2015-11-03-21.01.log.html#l-57
[2] -
https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda
[3] -
http://www.openstack.org/blog/2015/11/openstack-developer-mailing-list-digest-november-20151114/
--
Mike Perez
technical knowledge for certain specs.
* Attend the cross-project meeting when it's called for [2].
[1] -
https://review.openstack.org/#/q/project:+openstack/openstack-specs+status:+open,n,z
[2] - https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting
--
Mike Perez
/pipermail/openstack-dev/2015-December/080869.html
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org
penstackci/tree/contrib/README.md
[8] - https://wiki.openstack.org/wiki/Meetings/ThirdParty
[9] - https://wiki.openstack.org/wiki/Ironic/Testing#Questions
[10] - https://review.openstack.org/#/q/project:+openstack-dev/sandbox,n,z
--
Perma Link:
http://www.openstack.org/blog/2015/11/openstack-developer-mailing-list-digest-november-20151107/
New Management Tools and Processes for stable/liberty and Mitaka
* For release management, we used a combination of launchpad
Perma Link:
http://www.openstack.org/blog/2015/11/openstack-developer-mailing-list-digest-november-20151114
Time to Make Some Assertions About Your Projects
===
* The technical committee defined a number of “assert” tags which
allows a project team to to make
sections of that meeting and make sure it gets #info-ed by the
meetbot in the meeting summary.
See you there!
For more details on this meeting, please see:
https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting
[1] - https://review.openstack.org/#/c/266072/
--
Mike Perez
ion. I feel starting that direction with any new project in some open
source space where we want multiple solutions to plug in is just a disaster
waiting to happen.
--
Mike Perez
__
OpenStack Development Mailing Lis
On 23:53 Jun 17, Matthew Treinish wrote:
> On Fri, Jun 17, 2016 at 04:26:49PM -0700, Mike Perez wrote:
> > On 15:12 Jun 14, Matthew Treinish wrote:
> > > I don't think backwards compatibility policies really apply to what what
> > > define
> > > as the
HTML render:
http://www.openstack.org/blog/2016/06/openstack-developer-mailing-list-digest-20160617/
SuccessBot Says
===
* Qiming: Senlin has completed API migration from WADL.
* Mugsie: Kiall Fixed the gate - development can now continue!!!
* notmyname: exactly 6 years ago today,
for reminding me to update that. These are actually approved by the
cross-project spec team now.
http://governance.openstack.org/resolutions/20160414-grant-cross-project-spec-team-voting.html
--
Mike Perez
__
OpenS
esult. How
about we not think the worse of people that are trying to prove our project
being successful and start working with them?
With that said I agree with this strict checking in tests. Deployments need to
stop defining the community defined APIs.
--
Mike Perez
__
stack.org/blog/2016/01/whats-next-for-application-developer-guides/
[11] - https://www.openstack.org/summit/austin-2016/call-for-speakers/
[12] - https://etherpad.openstack.org/p/austin-upstream-dev-track-ideas
[13] - https://review.openstack.org/#/c/262003/
--
M
/project-team-guide/cross-project.html#cross-project-specification-liaisons
[2] -
https://wiki.openstack.org/wiki/CrossProjectLiaisons#Cross-Project_Spec_Liaisons
--
Mike Perez
__
OpenStack Development Mailing List
On 11:24 Jan 14, Mike Perez wrote:
> Hello all!
>
> We've been discussing cross-project spec liaisons on the mailing list [1] and
> cross-project meeting [2][3] for a bit, and we're now stating the official
> responsibilities [4] of the group.
Hey all,
The Project Team Guide fo
/openstack-specs
--
Mike Perez
__
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
* If only a commercial solution can do something exposed in the API, that's
bad. Your API is now dictated by some implementations.
You better believe there's going to be some investment in making OpenCDN work
if gate jobs are depending on it passing. If you want to introduce some shiny
new chec
ocus in the summit attendees needs.
* Every summit ends with a feedback session with the community. Thierry and
I look back on this for improvements when we're planning the next summit.
The team organizing this is the community.
The Foundation staff that helps on the summit side (Thierry and I who d
.org/pipermail/openstack-dev/2016-February/085550.html
[2] -
https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda
[3] - https://review.openstack.org/#/c/242852/
[4] - https://review.openstack.org/#/c/245629/
--
Mike P
I's that use the optional tempest tests
for having the feature available in their driver.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsu
>
> Should we host projects that have no hope of becoming official projects due
> to this sort of criteria? Would we host GPL-only projects under openstack/?
With previous threads complaining about low on infra resources to help with
stable releases, I'd actually say
entation.
>From a QA perspective in gate, if we have to rely on a commercial solution
(even if donated) to test it, then that's bad.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscrib
's about how the
community can test a project. If we have to depend on a commercial entity to do
tests on the main features of a project, I see that as a problem.
I'm with Sean where I see this as not fitting with what the community is trying
to bring in based on what the TC has set in the governance,
Perma link:
http://www.openstack.org/blog/2016/02/openstack-developer-mailing-list-digest-20160212/
SuccessBot Says
===
* dhellmann: [1] is live with release history and upcoming release
schedules.
* ttx: Governance changes are now announced in #openstack-dev, to increase
Tuesdays at 2100
UTC.
[1] -
https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
uld like to add Patrick to the core reviewers for Cinder. Per our
> governance process [1], existing core reviewers please respond with any
> feedback within the next five days. Unless there are no objections, I will
> add Patrick to the group by February 3rd.
+1 good job
at the OpenStack conference in Austin before the first keynote. In this
event, mentees will be able to meet a variety of mentors in a short amount of
time to see who they would like to pair up with. Please check the appropriate
box on the questionnaire form if you’re interested in attending.
--
Mike Perez
On 17:00 Nov 30, Mike Perez wrote:
> On October 28th 2015 at the Ironic Third Party CI summit session [1], there
> was
> consensus by the Ironic core and participating vendors that the set of
> deadlines will be:
>
> * Mitaka-2ː Driver teams will have registered thei
--
Mike Perez
__
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
s.html
[2] - https://specs.openstack.org/openstack/api-wg/
--
Mike Perez
__
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
://wiki.openstack.org/wiki/CrossProjectLiaisons#Cross-Project_Spec_Liaisons
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
in mysql [2]
* Event message format [3]
* Instance auto evacuation [4]
[1] -
https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda
[2] - https://review.openstack.org/#/c/280371/
[3] - https://review.openstack.org/#/c/231382/
[4] - https://review.openstack.org/#/c/257809/
--
Mike
HTML rendered version:
http://www.openstack.org/blog/2016/02/openstack-developer-mailing-list-digest-20160226/
Audience for Release Notes
==
* We have 3 potential audiences for release notes:
- Developers consuming libraries or other code directly.
- Deployers and
On 02/22/2016 07:19 AM, Ian Cordasco wrote:
-Original Message-
From: Mike Perez <thin...@gmail.com>
Reply: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Date: February 19, 2016 at 19:21:13
To: openstack-dev@lists.o
this to be mentioned in the new contributors guide,
after it's improved. I'll make a note about this now.
[1] -
http://lists.openstack.org/pipermail/openstack-dev/2016-January/084133.html
--
Mike Perez
__
OpenStack Developmen
Perma link:
http://www.openstack.org/blog/2016/01/openstack-developer-mailing-list-digest-20160122
Success Bot Says
- mriedem: nova liberty 12.0.1 released [1].
- OpenStack Ansible Kilo 11.2.7 has been released.
- OpenStack-Ansible Liberty 12.0.4 has been released.
- Tell us
for conversion of utf8 to utf8mb4 to support 4
byte unicode in different openstack components.
* Open discussion
[1] - https://review.openstack.org/#/c/245629/
--
Mike Perez
__
OpenStack Development Mailing List (not for usage
a has to also be
dependent on it. I get Infra is already dependent on public cloud
donations, but if we start opening the door to allow projects to bring
in those commercial dependencies, that's not good.
[1] -
http://governance.openstack.org/reference/new-pr
rect me, but
"adopts a test-driven gate in the OpenStack infrastructure for changes"
seems to imply that it would be *in the OpenStack infrastructure*, which
is exactly the problem I'm outlining here.
Read my earlier quote above about commercial dependencies in our
i
t, I would not be satisfied with
us giving up on having functional or integration tests from a project
because of the available implementations. It's reasons like this that
highlight Poppy being different from the rest of OpenStack.
--
eyes on this, so this isn't a surprise to some. The meeting has
been revived significantly, so it's more useful than ever for participation.
[1] - https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting
--
Mike P
OpenStack Operators Midcycle
* Takeaways from the OpenStack Mid-Cycle Ops Meetup: first time’s the charm [1]
* OpenStack Upgrading Tutorial: 11 pitfalls and solutions [2]
“No Open Core” in 2016 (continuing)
===
* Continuing with
liaisons, take note that there is a separate meeting
taking place for cross-project quotas [3].
[1] - https://review.openstack.org/#/c/231382/
[2] - https://review.openstack.org/#/c/257809/
[3] -
http://lists.openstack.org/pipermail/openstack-dev/2016-February/087684.html
--
Mike Perez
://review.openstack.org/#/c/210549/
* Rolling Upgrades (thingee)
- https://review.openstack.org/#/c/290977/1
* Stale Specs (thingee)
- http://lists.openstack.org/pipermail/openstack-dev/2016-March/089115.html
* Open discussion
--
Mike Perez
their specific services. The point here is to agree on the
concept and already existing solutions to solve the problem:
* Rolling Upgrades (Ken Johnston) - https://review.openstack.org/#/c/290977/1
--
Mike Perez
://review.openstack.org/#/c/284454/
[5] - https://wiki.openstack.org/wiki/Boson
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
HTML Render:
http://www.openstack.org/blog/2016/03/openstack-developer-mailing-list-digest-20160311/
SuccessBot Says
===
* Ajaeger: All jobs moved from bare-trusty to ubuntu-trusty.
* Clarkb: Infra is running logstash 2.0 now
* Tell us yours via IRC with a message “#success [insert
all then!
[1] -
https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda
[2] -
https://wiki.openstack.org/wiki/CrossProjectLiaisons#Cross-Project_Spec_Liaisons
--
Mike Perez
__
OpenStack Development
Hi all!
We will be skipping the cross-project meeting since there are no agenda items
to discuss, but someone can add one [1] to call a meeting next time. Thanks!
[1] -
https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda
--
Mike Perez
Hi all!
We will be skipping the cross-project meeting since there are no agenda items
to discuss, but someone can add one [1] to call a meeting next time. Thanks!
[1] -
https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda
--
Mike Perez
(johnthetubaguy)
* Matthew Treinish (mtreinish)
* Mike Perez (thingee)
* Morgan Fainberg (morgan)/(notmorgan)
* Thierry Carrez (ttx)
* Full results [7]
* Full thread:
http://lists.openstack.org/pipermail/openstack-dev/2016-April/thread.html#91702
Cross-Project Session Schedule
enstack-developer-mailing-list-digest-20160311/
[2] - http://lists.openstack.org/pipermail/openstack-dev/2016-March/088558.html
[3] - http://releases.openstack.org/mitaka/schedule.html
--
Mike Perez
__
OpenStack Development Ma
te in elections, that's something we can address. I'll look at
> wording of the existing requirements in the next week or so. If the team has
> a leader, you're all set and I'm happy to support keeping EC2 an official
> team.
Hope this cover things:
ht
work through
> a different arrangement.
>
> Shout-out for this completed ;)
I'd also recommend making announcements in the cross-project meeting [1] during
the horizontal/vertical announcements when needed.
[1] - https://wiki.
specifications? [4]
[1] -
https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda
[2] -
https://wiki.openstack.org/wiki/CrossProjectLiaisons#Cross-Project_Spec_Liaisons
[3] - https://review.openstack.org/#/c/295543/2
[4] - https://review.openstack.org/#/c/295940/
--
Mike
5] - https://review.openstack.org/#/c/295940/
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-b
Hi all!
I Mike Perez aka. thingee, am announcing my candidacy for a position in the
OpenStack Technical Committee. You can find my submitted candidacy which is
still under review here https://review.openstack.org/297748
I am employed by the OpenStack Foundation as a Developer Coordinator to help
sed and not our
support channel. You can request help at our general mailing list [1], or Ask
OpenStack [2].
[1] - http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[2] - https://ask.openstack.org/en/questions/
HTML version:
http://www.openstack.org/blog/2016/03/openstack-developer-mailing-list-digest-20160318-2/
SuccessBot Says
===
* redrobot: The Barbican API guides is now being published. [1]
* jroll: ironic 5.1.0 released as the basis for stable/mitaka.
* ttx: All RC1s up for
ho want anonymous volumes can always hit the API
> directly with curl or whatever SDK.
I suppose it could, however, names are not unique.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Un
ide.rst
[3] - http://www.openstack.org/software/releases/liberty/components/manila
[4] - http://docs.openstack.org/developer/openstack-projects.html
--
Mike Perez
__
OpenStack Development Mailing List (not for usage
e
where it's mentioned directions are changing.
[1] - https://review.openstack.org/#/c/213756/
[2] -
http://lists.openstack.org/pipermail/openstack-docs/2015-December/008062.html
--
Mike Perez
__
OpenStack Development Maili
never fully obtain.
>
> I think it's time to recognize those are different things and separate them.
https://review.openstack.org/#/c/296571/
--
Mike Perez
__
OpenStack Development Mailing List (not for usage ques
t a project has to be
considered by the Defcore group in order to be in the install docs as Lana has
required previously?
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
re rendered
docs from individual projects' repos.
Regardless of what direction people would like to go here, I will be happy to
spearhead this from a cross-project perspective.
--
Mike Perez
__
OpenStack Development Mailin
Hi all!
We will be skipping the cross-project meeting since there are no agenda items
to discuss, but someone can add one [1] to call a meeting next time. Thanks!
[1] -
https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda
--
Mike Perez
HTML version:
http://www.openstack.org/blog/2016/03/openstack-developer-mailing-list-digest-20160304/
SuccessBot Says
===
* Ttx: Mitaka-3 is done.
* Odyssey4me: OpenStack-Ansible Liberty 12.0.7 is released [1].
* johnthetubaguy: Nova is down to four pending blueprints for feature
gestions and feedback are highly appreciated.
The requirements and documentation for starting one are provided here:
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers
Also you can join the third party ci help meeting after going through that
document:
http
HTML version:
http://www.openstack.org/blog/2016/04/openstack-developer-mailing-list-digest-20160401/
SuccessBot Says
===
* Tonyb: Dims fixed the Routes 2.3 API break :)
* pabelanger: migration from devstack-trusty to ubuntu-trusty complete!
* Tell us yours via IRC with a message
On 09:29 Mar 25, Mike Perez wrote:
> Hi all!
>
> I Mike Perez aka. thingee, am announcing my candidacy for a position in the
> OpenStack Technical Committee. You can find my submitted candidacy which is
> still under review here https://review.openstack.org/297748
>
Hi all!
We will be skipping the cross-project meeting since there are no agenda items
to discuss, but someone can add one [1] to call a meeting next time. Thanks!
[1] -
https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda
--
Mike
ially tie it to specific rights or tags we happen to use upstream.
After seeing numerous threads from people in the community being upset by these
parties, I'd be fine with them not continuing.
--
Mike Perez
__
OpenStack Development Mail
ually performs a *move* operation, which isn't a *change* of
> the original resources. Rather, it is a creation of a new set of resources
> (of the new amounts) and a deletion of the old set of resources.
How about extending a volume? A volume is a resource and can be extended in
Cinder to
On 15:25 Apr 23, Jay Pipes wrote:
> On 04/23/2016 03:18 PM, Mike Perez wrote:
> >On 14:54 Apr 18, Jay Pipes wrote:
> >>On 04/16/2016 05:51 PM, Amrith Kumar wrote:
> >>> - update_resource(id or resource, newsize)
> >>
> >>Resizing resources i
d along with the “User Committee”,
> so I think the text actually meant “Technical Committee”. Who can clarify
> this ambiguity?
It is the technical committee. An update to clarify this will be made shortly.
--
Mike Perez
___
Please vote with +1, 0, -1. Also, if the time doesn't work please
> propose 2-3 additional time slots.
>
>
> We can decide later on the tool and I will setup agenda if we have
> enough interest.
+1
--
Mike Perez
made the bad people just
about every time.
Community enforcing or not, I predict this to get out of hand and it's going to
create more community divide regardless.
--
Mike Perez
__
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
two, can you speak more about the interface improvements with working
with all the hardware available. Cinder for example, we deal with block devices
a bit and having to sometimes just dd data from here to there.
[1] - http://magic.io/blog/uvloop-blazing-fast-python-networking/
--
Mike Perez
_
third-party CI movement with a variety of projects. I know this was not
a convenient time for you, but you made sure everyone could get help.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubsc
.openstack.org/
[2] - https://review.openstack.org/#/c/301822/6/doc/source/cross-project.rst
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
On 04:07 May 12, Ildikó Váncsa wrote:
>
>
> > -Original Message-
> > From: Mike Perez [mailto:m...@openstack.org]
> > Sent: May 11, 2016 23:52
> > To: Ildikó Váncsa
> > Cc: 'D'Angelo, Scott <scott.dang...@hpe.com> (scott.dang...@hpe.com)';
-specification-liaisons
[3] -
http://governance.openstack.org/resolutions/20160414-grant-cross-project-spec-team-voting.html
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
HTML render:
http://www.openstack.org/blog/2016/05/openstack-developer-mailing-list-digest-20160513/
SuccessBot Says
===
* Pabelanger: bare-precise has been replaced by ubuntu-precise. Long live DIB
* bknudson: The Keystone CLI is finally gone. Long live openstack CLI.
* Jrichli:
nstack-meeting-cp, assuming this is just multi-attach
efforts and not some on-going cinder and nova api meeting.
[1] - https://review.openstack.org/#/c/317038/
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questi
nd do not care
> where that exists.
Reading this thread, Nikhil who is speaking for the quota team is worried about
the amount of overhead caused by governance, instead of first focusing on
making something actually exist. I see quite a few people in this thread
s
On 16:11 May 10, Matt Riedemann wrote:
> On 5/9/2016 11:30 PM, Mike Perez wrote:
> >Hey all,
> >
> >When we first discussed the future of cross-project meetings at the Tokyo
> >summit, we walked out with the idea of beginning to have ad-hoc meetings
> >instead of
On 16:06 May 14, Nikhil Komawar wrote:
> On 5/14/16 2:35 PM, Mike Perez wrote:
> > Reading this thread, Nikhil who is speaking for the quota team is worried
> > about
> > the amount of overhead caused by governance, instead of first focusing on
> > making something
201 - 300 of 420 matches
Mail list logo
