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
://review.openstack.org/#/c/284454/
[5] - https://wiki.openstack.org/wiki/Boson
--
Mike Perez
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
://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
://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
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
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
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
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
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
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
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
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
e.
[1] - https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting
[2] -
http://eavesdrop.openstack.org/meetings/containers/2015/containers.2015-11-03-16.01.log.html#l-150
--
Mike Perez
___
OpenStack-operators mailing list
OpenStack-operators@lists.op
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
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
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
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.
--
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
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
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
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
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
* 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,
SuccessBot Says
===
- odyssey4me: OpenStack Ansible Liberty 12.0.5 released.
- stevemar: Devstack now defaults to v3 for Keystone.
- boris-42: osprofiler functional job passed [1].
- dulled: Conference between Nova and Cinder mid-cycles worked!
- odyssey4me: OpenStack Ansible Kilo
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
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
://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
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
then seek
mentoring from the OpenStack mentoring program. To be clear though, their
program is debuting at the OpenStack conference and is only doing face 2 face
at this point as well.
--
Mike Perez
___
OpenStack-operators mailing list
OpenStack-
--
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
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
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
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
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
riginally in the newsletter, and then
people at the summit approached me about making it more visible, so it's now
a separate thing and emailed to the dev and operators list weekly.
http://lists.openstack.org/pipermail/openstack-operators/2016-January/009335.html
--
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
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
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
/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
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
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
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
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
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?
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
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
/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]”.
*
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]”.
*
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
-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
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
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
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-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
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
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-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
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
-oct-31-nov-6/#dev-digest
--
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
On 18:51 Oct 28, Mike Perez wrote:
> On 12:35 Oct 28, JJ Asghar wrote:
> > On 10/28/15 10:35 AM, Mike Perez wrote:
> > > On 14:09 Oct 16, hittang wrote:
> > >> Hello,everynoe. Can anybody help me for installing magnum? I have an
> > >> openstack inst
be spearheading some Tooz integration work:
https://review.openstack.org/#/c/185646/
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subj
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
--
Mike Perez
On 12:35 Oct 28, JJ Asghar wrote:
> On 10/28/15 10:35 AM, Mike Perez wrote:
> > On 14:09 Oct 16, hittang wrote:
> >> Hello,everynoe. Can anybody help me for installing magnum? I have an
> >> openstack installtion,which has one controller node, one network node, and
>
penstack.org/wiki/Magnum
--
Mike Perez
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
On Oct 25, 2015, at 18:19, Mike Perez <thin...@gmail.com> wrote:
>> On Oct 25, 2015, at 10:48, Mike Perez <thin...@gmail.com> wrote:
>>
>> On 15:54 Oct 21, Jay S. Bryant wrote:
>>
>>
>>
>>> Not sure where the evening will
> On Oct 25, 2015, at 10:48, Mike Perez <thin...@gmail.com> wrote:
>
> On 15:54 Oct 21, Jay S. Bryant wrote:
>
>
>
>> Not sure where the evening will take us, but we are planning to meet
>> by registration at the Convention Center. Looking at the map, if I
mmit. We're especially looking for Nova, Cinder, and Keystone
> developers to attend and give feedback.
I will definitely be there for the Cinder side.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questio
ps/umqvsjPag3S2
I delegate someone to make reservations for 15 people.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:u
content. The attempt here was to enable others
to have somewhere to start, to continue quality documentation with
continued developments.
Please help me to do more positive work in this project. It would be an
honor to be member of your technical committee.
Thank you,
Mike Perez
Official
on to rush and suffer quality for the sake of vendors
wanting the latest and greatest feature. We're more mature than that.
Things like replication I'd rather see adopted in the next release. Otherwise,
if I can use you're own word, you're "cramming" features in a release.
[1] - https:/
on this meeting, please see:
https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
the user story owner to user story mapping
> is 1:1.
+1
Before I got to Shamail's email, I was also thinking this sounds exactly what
the product working group is doing.
--
Mike Perez
__
OpenStack Deve
we kept everything to the spec on gerrit, and had the product
working group bringing needed attention to specs, we could eliminate the cross
project meeting.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage q
://thing.ee/cinder/active_contribs.png
[5] - https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#Key_New_Features_7
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
-
http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-07-28-21.03.log.html#l-239
[3] - http://lists.openstack.org/pipermail/openstack-dev/2015-August/071993.html
--
Mike Perez
__
OpenStack Develop
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
--
Mike Perez
__
OpenStack Development Mailing
Propose your topics:
https://etherpad.openstack.org/p/cinder-mitaka-summit-topics
Next Cinder meeting, we'll discuss them:
https://wiki.openstack.org/wiki/CinderMeetings
--
Mike Perez
__
OpenStack Development Mailing List
://lists.openstack.org/pipermail/third-party-announce/2015-July/000249.html
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
others won't
be able to do anything with it until the M release anyways.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
between Cinder and
Nova os-brick having the ability to inform libvirt of the size change.
The only caveat that we need Nova to agree on is this would only work with
Libvirt. This is planned for the M release.
[1] - https://etherpad.openstack.org/p/cinder-meetup-summer-2015
--
Mike Perez
On 12:13 Aug 13, Mike Perez wrote:
It gives me great pleasure to nominate Gorka Eguileor for Cinder core.
Gorka's contributions to Cinder core have been much apprecated:
https://review.openstack.org/#/q/owner:%22Gorka+Eguileor%22+project:openstack/cinder,p,0035b6410002dd11
60/90 day
201 - 300 of 503 matches
Mail list logo
