Sean's services as Cinder PTL is really appreciable!!
On Sep 12, 2016 7:11 PM, "Sean McGinnis" wrote:
I would like to announce my candidacy to continue as Cinder PTL for the
The Cinder project has made great
Hi Dinesh Bhor,
I could see a lot of projects have used this. Seems interesting.
You can refer Cinder, for example.
I think we should not raise bug for this. For me it's invalid.
You can treat this as improvement(just to reduce test code blocks), it
seems ok to go ahead even without any BP or
Well, I do not belong to core group, but would like to vote for "*man with
micro versions*" tattoo.
Scott well deserves entry to this elite group.. he has always been there in
nova-cinder interactions/discussions, micro versions and many other
valuable additions to cinder component.
>> Thanks for taking the responsibility. Assigned the BP to you. As
>> discussed, please submit a spec for the API design. Feel free to let us
>> know if you need any help.
>> Best regards,
Eli seems strong addition to team, I am happy to have Eli Qiao's expertise
in core team.
+1 from my side.
On Jun 1, 2016 3:09 AM, "Hongbin Lu" wrote:
> Hi team,
> I wrote this email to propose Eli Qiao (taget-9) to be a Higgins core.
I am interested in this.
On Jun 1, 2016 3:53 AM, "Hongbin Lu" wrote:
> Hi team,
> As discussed in the last team meeting, we agreed to define core use cases
> for the API design. I have created a blueprint for that. We
>- Create the service's users and add a password into the databse
>- Sync the service with the database
>- Start the service
If I am right, these are one time activity...during installation stage..
one does not need to create "service users" again and again during service
Dear Eli Qiao,
>I workaround it by naming them as "higgi-api" and "higgi-cond" (seems no
magic in "-i")
>Also, the api-port number as "9517", any comments?
We should update the regex.
s- should be updated to ^s- @
Great compilation, this will help for sure!!
On Fri, May 6, 2016 at 10:38 PM, Sean McGinnis
> At the Design Summit in Austin, the Cinder team met over three days
> to go over a variety of topics. This is a general
Even though I am not a core member, but I would like to vote for Michal as
he truely deserves it...
Huge acceptance from my side..
On Tue, May 3, 2016 at 11:46 PM, Sean McGinnis
> Hey everyone,
> I would like to nominate Michał Dulko
Sure, I will pick for cinder.
On Tue, May 3, 2016 at 6:59 PM, Anne Gentle
> Hi all,
> This patch contains all the RST + YAML for projects to bring over to their
> repos to begin building API reference
Yes, I am ok with it.
On Apr 15, 2016 6:59 AM, "Tang Chen" wrote:
> Hi all,
> In yesterday's meeting, Dean, Richard and I have discussed the meeting
> time issue.
> The following two options work for us.
> E.1 Every two weeks (on
> So should we add what we don't want
to see people -1 for?
This seems right way.. but concern is do everyone follow all docs?
But atleast we should document it somewhere.
On Apr 11, 2016 6:52 AM,
I agree with Thierry Carrez , I think this would help.
Along with this, we need to motivate new joiners to continue with openstack.
Most of them leave earlier or participate less due to some demotivating
factors like coding is easy but getting things reviewed is much difficult.
Thanks for sharing preffered time.
Common votes seems for below time options
E.4 - Thursday at 1600 UTC in #openstack-meeting (IRC webclient)
O.3 - Thursday at 1900 UTC in #openstack-meeting (IRC webclient)
Lets discuss and finalize this time in today's meeting at 1900 UTC in
I just added service for block storage, we have named these
openstack volume service list/enable/disable.
Same protocol is used for nova as well previosly.
Hope this will help.
On Apr 6, 2016 7:54 PM, "Hayes, Graham" wrote:
This is regarding deciding meeting time for OSC team to facilitate
appropriate time for APAC guys.
We are planning to have meeting on alternate weeks for this purpose.
Some of the suggestions are:
*E.1* Every two weeks (on even weeks) on Thursday at 1300 UTC in
Mail list logo