Re: [Openstack-operators] UC Election - Looking for Election Officials

[Amy Marrich]

And for those curious... our officials are.

Ed Leafe, Chandan Kumar and then Mohamed Elsakhawy


Thanks,
Amy (spotz)
(Who's claiming lack of sleep for not including the names earlier)

On Tue, Jul 24, 2018 at 11:39 AM, Amy Marrich  wrote:

> Just wanted to say THANK you as we now have 3 officials! Please
> participate in the User Committee elections as a candidate and perhaps most
> importantly by voting!
>
> Thanks,
>
> Amy (spotz)
>
> On Tue, Jul 24, 2018 at 10:05 AM, Amy Marrich  wrote:
>
>> Hey Stackers,
>>
>>
>> We are getting ready for the Summer UC election and we need to have at
>> least two Election Officials. I was wondering if you would like to help us
>> on that process. You can find all the details of the election at
>> https://governance.openstack.org/uc/reference/uc-election-aug2018.html.
>>
>>
>> I do want to point out to those who are new that Election Officials are
>> unable to run in the election itself but can of course vote.
>>
>>
>>
>> The election dates will be:
>>
>> August 6 - August 17, 05:59 UTC: Open candidacy for UC positions
>>
>> August 20 - August 24, 11:59 UTC: UC elections (voting)
>>
>>
>>
>> Please, reach out to any of the current UC members or simple reply to
>> this email if you can help us in this community process.
>>
>>
>>
>> Thanks,
>>
>>
>>
>> OpenStack User Committee
>>
>> Amy, Leong, Matt, Melvin, and Saverio
>>
>>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] UC Election - Looking for Election Officials

[Amy Marrich]

Just wanted to say THANK you as we now have 3 officials! Please participate
in the User Committee elections as a candidate and perhaps most importantly
by voting!

Thanks,

Amy (spotz)

On Tue, Jul 24, 2018 at 10:05 AM, Amy Marrich  wrote:

> Hey Stackers,
>
>
> We are getting ready for the Summer UC election and we need to have at
> least two Election Officials. I was wondering if you would like to help us
> on that process. You can find all the details of the election at
> https://governance.openstack.org/uc/reference/uc-election-aug2018.html.
>
>
> I do want to point out to those who are new that Election Officials are
> unable to run in the election itself but can of course vote.
>
>
>
> The election dates will be:
>
> August 6 - August 17, 05:59 UTC: Open candidacy for UC positions
>
> August 20 - August 24, 11:59 UTC: UC elections (voting)
>
>
>
> Please, reach out to any of the current UC members or simple reply to this
> email if you can help us in this community process.
>
>
>
> Thanks,
>
>
>
> OpenStack User Committee
>
> Amy, Leong, Matt, Melvin, and Saverio
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] UC Election - Looking for Election Officials

[Amy Marrich]

Hey Stackers,


We are getting ready for the Summer UC election and we need to have at
least two Election Officials. I was wondering if you would like to help us
on that process. You can find all the details of the election at
https://governance.openstack.org/uc/reference/uc-election-aug2018.html.


I do want to point out to those who are new that Election Officials are
unable to run in the election itself but can of course vote.



The election dates will be:

August 6 - August 17, 05:59 UTC: Open candidacy for UC positions

August 20 - August 24, 11:59 UTC: UC elections (voting)



Please, reach out to any of the current UC members or simple reply to this
email if you can help us in this community process.



Thanks,



OpenStack User Committee

Amy, Leong, Matt, Melvin, and Saverio
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [nova] Couple of CellsV2 questions

[Jonathan Mills]

Thanks, Matt.  Those are all good suggestions, and we will incorporate
your feedback into our plans.

On 07/23/2018 05:57 PM, Matt Riedemann wrote:
> I'll try to help a bit inline. Also cross-posting to openstack-dev and
> tagging with [nova] to highlight it.
> 
> On 7/23/2018 10:43 AM, Jonathan Mills wrote:
>> I am looking at implementing CellsV2 with multiple cells, and there's
>> a few things I'm seeking clarification on:
>>
>> 1) How does a superconductor know that it is a superconductor?  Is its
>> operation different in any fundamental way?  Is there any explicit
>> configuration or a setting in the database required? Or does it simply
>> not care one way or another?
> 
> It's a topology term, not really anything in config or the database that
> distinguishes the "super" conductor. I assume you've gone over the
> service layout in the docs:
> 
> https://docs.openstack.org/nova/latest/user/cellsv2-layout.html#service-layout
> 
> 
> There are also some summit talks from Dan about the topology linked here:
> 
> https://docs.openstack.org/nova/latest/user/cells.html#cells-v2
> 
> The superconductor is the conductor service at the "top" of the tree
> which interacts with the API and scheduler (controller) services and
> routes operations to the cell. Then once in a cell, the operation should
> ideally be confined there. So, for example, reschedules during a build
> would be confined to the cell. The cell conductor doesn't go back "up"
> to the scheduler to get a new set of hosts for scheduling. This of
> course depends on which release you're using and your configuration, see
> the caveats section in the cellsv2-layout doc.
> 
>>
>> 2) When I ran the command "nova-manage cell_v2 create_cell
>> --name=cell1 --verbose", the entry created for cell1 in the api
>> database includes only one rabbitmq server, but I have three of them
>> as an HA cluster.  Does it only support talking to one rabbitmq server
>> in this configuration? Or can I just update the cell1 transport_url in
>> the database to point to all three? Is that a supported configuration?
> 
> First, don't update stuff directly in the database if you don't have to.
> :) What you set on the transport_url should be whatever oslo.messaging
> can handle:
> 
> https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.transport_url
> 
> 
> There is at least one reported bug for this but I'm not sure I fully
> grok it or what its status is at this point:
> 
> https://bugs.launchpad.net/nova/+bug/1717915
> 
>>
>> 3) Is there anything wrong with having one cell share the amqp bus
>> with your control plane, while having additional cells use their own
>> amqp buses? Certainly I realize that the point of CellsV2 is to shard
>> the amqp bus for greater horizontal scalability.  But in my case, my
>> first cell is on the smaller side, and happens to be colocated with
>> the control plane hardware (whereas other cells will be in other parts
>> of the datacenter, or in other datacenters with high-speed links).  I
>> was thinking of just pointing that first cell back at the same
>> rabbitmq servers used by the control plane, but perhaps directing them
>> at their own rabbitmq vhost. Is that a terrible idea?
> 
> Would need to get input from operators and/or Dan Smith's opinion on
> this one, but I'd say it's no worse than having a flat single cell
> deployment. However, if you're going to do multi-cell long-term anyway,
> then it would be best to get in the mindset and discipline of not
> relying on shared MQ between the controller services and the cells. In
> other words, just do the right thing from the start rather than have to
> worry about maybe changing the deployment / configuration for that one
> cell down the road when it's harder.
> 

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] OpenStack Summit Berlin - Community Voting Open

[Ashlee Ferguson]

Hi everyone,

Session voting is now open for the November 2018 OpenStack Summit in Berlin!

VOTE HERE 

Hurry, voting closes Thursday, July 26 at 11:59pm Pacific Time (Friday, July 27 
at 6:59 UTC).

The Programming Committees will ultimately determine the final schedule. 
Community votes are meant to help inform the decision, but are not considered 
to be the deciding factor. The Programming Committee members exercise judgment 
in their area of expertise and help ensure diversity. View full details of the 
session selection process here.

Continue to visit https://www.openstack.org/summit/berlin-2018 
 for all Summit-related 
information.

REGISTER
Register for the Summit  
before prices increase in late August!

VISA APPLICATION PROCESS
Make sure to secure your Visa soon. More information 
 about the 
Visa application process.

TRAVEL SUPPORT PROGRAM
August 30 is the last day to submit applications. Please submit your 
applications 
 by 
11:59pm Pacific Time (August 31 at 6:59am UTC).

If you have any questions, please email sum...@openstack.org 
.

Cheers,
Ashlee


Ashlee Ferguson
OpenStack Foundation
ash...@openstack.org




___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [publiccloud-wg]New Meeting Time Starting This Week

[Zhipeng Huang]

Hi Folks,

As indicated in https://review.openstack.org/#/c/584389/, PCWG is moving
towards a tick-tock meeting arrangements to better accommodate participants
along the globe.

For even weeks starting this Wed, we will have a new meeting time on
UTC0700. For odd weeks we will remain for the UTC1400 time slot.

Look forward to meet you all at #openstack-publiccloud on Wed !

-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators