[Openstack] [all]Naming the T release of OpenStack -- Poll open
Hi folks, It is time again to cast your vote for the naming of the T Release. As with last time we'll use a public polling option over per user private URLs for voting. This means, everybody should proceed to use the following URL to cast their vote: https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_aac97f1cbb6c61df&akey=b9e448b340787f0e We've selected a public poll to ensure that the whole community, not just gerrit change owners get a vote. Also the size of our community has grown such that we can overwhelm CIVS if using private urls. A public can mean that users behind NAT, proxy servers or firewalls may receive an message saying that your vote has already been lodged, if this happens please try another IP. Because this is a public poll, results will currently be only viewable by myself until the poll closes. Once closed, I'll post the URL making the results viewable to everybody. This was done to avoid everybody seeing the results while the public poll is running. The poll will officially end on 2018-11-08 00:00:00+00:00[1], and results will be posted shortly after. [1] https://governance.openstack.org/tc/reference/release-naming.html --- According to the Release Naming Process, this poll is to determine the community preferences for the name of the T release of OpenStack. It is possible that the top choice is not viable for legal reasons, so the second or later community preference could wind up being the name. Release Name Criteria - Each release name must start with the letter of the ISO basic Latin alphabet following the initial letter of the previous release, starting with the initial release of "Austin". After "Z", the next name should start with "A" again. The name must be composed only of the 26 characters of the ISO basic Latin alphabet. Names which can be transliterated into this character set are also acceptable. The name must refer to the physical or human geography of the region encompassing the location of the OpenStack design summit for the corresponding release. The exact boundaries of the geographic region under consideration must be declared before the opening of nominations, as part of the initiation of the selection process. The name must be a single word with a maximum of 10 characters. Words that describe the feature should not be included, so "Foo City" or "Foo Peak" would both be eligible as "Foo". Names which do not meet these criteria but otherwise sound really cool should be added to a separate section of the wiki page and the TC may make an exception for one or more of them to be considered in the Condorcet poll. The naming official is responsible for presenting the list of exceptional names for consideration to the TC before the poll opens. Exact Geographic Region --- The Geographic Region from where names for the S release will come is Colorado Proposed Names -- * Tarryall * Teakettle * Teller * Telluride * Thomas : the Tank Engine * Thornton * Tiger * Tincup * Timnath * Timber * Tiny Town * Torreys * Trail * Trinidad * Treasure * Troublesome * Trussville * Turret * Tyrone Proposed Names that do not meet the criteria (accepted by the TC) - * Train๐ : Many Attendees of the first Denver PTG have a story to tell about the trains near the PTG hotel. We could celebrate those stories with this name Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [Swift] PUT Object performance problem
Hi clay I just using the command like `swift-ring-builder object.builder set_weight d234 2220`. Then execute `swift-ring-builder object.builder rebalance` and push the rings all object node. Here is more detail information. I/O scheduler : deadline OS : CentOS 7.4 Kernel version : 3.10.0-693.11.1.el7.x86_64 I will try decrease the node_timeout from 3 to 1. (Do you have any recommend value?) On Tue, Oct 30, 2018 at 1:42 AM Clay Gerrard wrote: > Obviously a re-balance will cost some IO, but it's normally perceptible to > the client unless you were already on a razor thin line. > > Two config options seem obvious to think about experimenting with: > > You could decrease the node_timeout and let the proxy try to write more to > handoffs > You could try to use some of the ionice options (or other tuning options) > to make the replicators hammer the disks a little less > > It might having something to do with how you're organizing your ring > weight changes - could you describe how you're managing rings? > Could also be a io scheduling issue - are you using noop/deadline or cfq? > What kernel version? > > -Clay > > > On Mon, Oct 29, 2018 at 9:55 AM SeongSoo Cho wrote: > >> For more information, I use ocata version. >> >> 2018๋ 10์ 29์ผ (์) ์คํ 10:07, SeongSoo Cho ๋์ด ์์ฑ: >> >>> Hello, All >>> >>> I have a terrible problem with object server. >>> Here is the case. >>> 1. User upload an object to proxy-server >>> 2. Proxy server try to connect with object-server >>> 3. If one of object-server is slow to respond, proxy-server is waiting >>> for response. >>> 3.1 While waiting for response, proxy-server can't do anything >>> 4. So, The response of client request will be delayed. >>> >>> In my opinion, this code seems to be a problem >>> ( >>> https://github.com/openstack/swift/blob/stable/rocky/swift/proxy/controllers/obj.py#L1734 >>> ) >>> >>> ``` >>> with ResponseTimeout(node_timeout): >>> resp = conn.getexpect() >>> ``` >>> >>> If node_timeout's value is 3 and object-server respond after 2 seconds, >>> proxy-server wait 2 seconds. >>> >>> Because proxy-server wait for the above response, the execution of the >>> following code is delayed. >>> ( >>> https://github.com/openstack/swift/blob/stable/rocky/swift/proxy/controllers/obj.py#L627 >>> ) >>> >>> ``` >>> for node in nodes: >>> try: >>> putter = self._make_putter(node, part, req, headers) >>> self.app.set_node_timing(node, putter.connect_duration) >>> return putter >>> ``` >>> >>> This problem occurs when i do a ring rebalance. >>> When object-replicator delete a partition directory that are no longer >>> mine, the disk becomes very busy (Because of xfsaild daemon) >>> Because the disk are busy, object-server can't create diskfile during >>> PUT operation. >>> >>> Is there anyone who is having problems like me? >>> How can I solve this problem? >>> >>> I need everyone's help. >>> Thanks. >>> >>> Best Regards >>> SeongSoo Cho >>> >>> -- >>> SeongSoo Cho (South Korea) >>> >>> ___ >> Mailing list: >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> Post to : openstack@lists.openstack.org >> Unsubscribe : >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> > ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] setup private cloud environment
Recommendation: Use the installation tutorials on docs.openstack.org. They start with a two-node cloud, but depending on how you want to use your three boxes, it should be no problem extending the setup to three. This will be a very manual setup, time-consuming but with a great learning effect. There are several automatic or semi-automatic deployment tools that you should evaluate: Packstack (very easy), Kolla and Kolla-Ansible, OpenStack-Ansible. The latter two may require more power than a typical PC delivers. Their advantage: They can set up highly available clouds. Devstack is another solution. I don't know how hard it is to extend a single-node setup to three nodes. Since Devstack's purpose is development and testing, it doesn't really focus on robustness. Triple-O is probably not for you, as it requires servers with IPMI interface. But there are ways to virtualize IPMI, so that you should evaluate this method as well. I am sure there are other methods. One thing to consider: Setting up an OpenStack cloud is not like installing a typical Linux box. There are many (many!) moving parts and many (many!) opportunities to make mistakes. Keep that in mind and don't give up. Bernd Bausch On 10/30/2018 6:53 AM, Najeh Nafti wrote: > Dear Sir/Madam, > > I want to setup my own private cloud using 3 desktop machines with > openstack. > > Could you please give me the steps to build this cloud ? > How can i configure and connect the machines together to build my own > private cloud? > Regards. > Najeh. > > > ___ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack signature.asc Description: OpenPGP digital signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] my ask.openstack.org question has waited for moderator approval for 17 days
If there is a shortage of moderators, I volunteer. On 10/30/2018 8:03 AM, Jacob Burckhardt wrote: > My question on ask.openstack.org says "This post is awaiting moderation". > > It has been like that for 17 days. If you are a moderator, I'd appreciate if > you'd decide whether to publicly post my question: > > https://ask.openstack.org/en/question/116591/is-there-example-of-using-python-zunclient-api/ > > Thanks. > > -Jacob Burckhardt > > ___ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack signature.asc Description: OpenPGP digital signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] my ask.openstack.org question has waited for moderator approval for 17 days
My question on ask.openstack.org says "This post is awaiting moderation". It has been like that for 17 days. If you are a moderator, I'd appreciate if you'd decide whether to publicly post my question: https://ask.openstack.org/en/question/116591/is-there-example-of-using-python-zunclient-api/ Thanks. -Jacob Burckhardt ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] setup private cloud environment
Dear Sir/Madam, I want to setup my own private cloud using 3 desktop machines with openstack. Could you please give me the steps to build this cloud ? How can i configure and connect the machines together to build my own private cloud? Regards. Najeh. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] DHCP not accessible on new compute node.
I'm having the same problem when I delete the DHCP port openstack recreates the port and everything works fine again ...Marcio PradoAnalista de TI - Infraestrutura e RedesFone: +55 (35) 9.9821-3561www.marcioprado.eti.brEm 29/10/2018 17:50, Torin Woltjer escreveu:Recently installed a new compute node, but noticed none of the instances that I put on it will successfully receive network addresses from DHCP. This seems to work on all other compute nodes however. When listening for DHCP requests on the vxlan of the compute node, I notice that while I can see the DHCP requests on the new compute node, I do not see them anywhere else. If I manually assign an address to the interface on the instance I am able to ping in and out. Running dhclient -v on an instance on a working compute node successfully gets a DHCP response, on the new compute node there is no response, I also discovered that the instance on the new compute node cannot ping the DHCP ports at 172.16.1.2 & 172.16.1.3 yet can ping the gateway at 172.16.1.1.The setup is neutron-linuxbridge on Openstack Queens.Torin Woltjerย Grand Dial Communications - A ZK Tech Inc. Companyย 616.776.1066 ext. 2006www.granddial.com ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] DHCP not accessible on new compute node.
Recently installed a new compute node, but noticed none of the instances that I put on it will successfully receive network addresses from DHCP. This seems to work on all other compute nodes however. When listening for DHCP requests on the vxlan of the compute node, I notice that while I can see the DHCP requests on the new compute node, I do not see them anywhere else. If I manually assign an address to the interface on the instance I am able to ping in and out. Running dhclient -v on an instance on a working compute node successfully gets a DHCP response, on the new compute node there is no response, I also discovered that the instance on the new compute node cannot ping the DHCP ports at 172.16.1.2 & 172.16.1.3 yet can ping the gateway at 172.16.1.1. The setup is neutron-linuxbridge on Openstack Queens. Torin Woltjer Grand Dial Communications - A ZK Tech Inc. Company 616.776.1066 ext. 2006 www.granddial.com ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] [user-committee] UC Meeting Reminder
UC meeting in #openstack-uc at 1800UTC -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: (832) 264-2646 ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] Fwd: [openstack-dev] [Openstack-sigs] [all][tc] We're combining the lists! (was: Bringing the community together...)
-- Forwarded message - From: Samuel Cassiba Date: Fri, Sep 21, 2018 at 12:15 AM Subject: Re: [openstack-dev] [Openstack-sigs] [all][tc] We're combining the lists! (was: Bringing the community together...) To: openstack-dev On Thu, Sep 20, 2018 at 2:48 PM Doug Hellmann wrote: > > Excerpts from Jeremy Stanley's message of 2018-09-20 16:32:49 +: > > tl;dr: The openstack, openstack-dev, openstack-sigs and > > openstack-operators mailing lists (to which this is being sent) will > > be replaced by a new openstack-disc...@lists.openstack.org mailing > > list. > > Since last week there was some discussion of including the openstack-tc > mailing list among these lists to eliminate confusion caused by the fact > that the list is not configured to accept messages from all subscribers > (it's meant to be used for us to make sure TC members see meeting > announcements). > > I'm inclined to include it and either use a direct mailing or the > [tc] tag on the new discuss list to reach TC members, but I would > like to hear feedback from TC members and other interested parties > before calling that decision made. Please let me know what you think. > > Doug > +1 including the TC list as a tag makes sense to me and my tangent about intent in online communities. __ 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 -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: (832) 264-2646 ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [all] We're combining the lists! (was: Bringing the community together...)
REMINDER: The openstack, openstack-dev, openstack-sigs and openstack-operators mailing lists (to which this is being sent) will be replaced by a new openstack-disc...@lists.openstack.org mailing list. The new list is open for subscriptions[0] now, but is not yet accepting posts until Monday November 19 and it's strongly recommended to subscribe before that date so as not to miss any messages posted there. The old lists will be configured to no longer accept posts starting on Monday December 3, but in the interim posts to the old lists will also get copied to the new list so it's safe to unsubscribe from them any time after the 19th and not miss any messages. See my previous notice[1] for details. For those wondering, we have 127 subscribers so far on openstack-discuss with 3 weeks to go before it will be put into use (and 5 weeks now before the old lists are closed down for good). [0] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [1] http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html -- Jeremy Stanley signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [Swift] PUT Object performance problem
Obviously a re-balance will cost some IO, but it's normally perceptible to the client unless you were already on a razor thin line. Two config options seem obvious to think about experimenting with: You could decrease the node_timeout and let the proxy try to write more to handoffs You could try to use some of the ionice options (or other tuning options) to make the replicators hammer the disks a little less It might having something to do with how you're organizing your ring weight changes - could you describe how you're managing rings? Could also be a io scheduling issue - are you using noop/deadline or cfq? What kernel version? -Clay On Mon, Oct 29, 2018 at 9:55 AM SeongSoo Cho wrote: > For more information, I use ocata version. > > 2018๋ 10์ 29์ผ (์) ์คํ 10:07, SeongSoo Cho ๋์ด ์์ฑ: > >> Hello, All >> >> I have a terrible problem with object server. >> Here is the case. >> 1. User upload an object to proxy-server >> 2. Proxy server try to connect with object-server >> 3. If one of object-server is slow to respond, proxy-server is waiting >> for response. >> 3.1 While waiting for response, proxy-server can't do anything >> 4. So, The response of client request will be delayed. >> >> In my opinion, this code seems to be a problem >> ( >> https://github.com/openstack/swift/blob/stable/rocky/swift/proxy/controllers/obj.py#L1734 >> ) >> >> ``` >> with ResponseTimeout(node_timeout): >> resp = conn.getexpect() >> ``` >> >> If node_timeout's value is 3 and object-server respond after 2 seconds, >> proxy-server wait 2 seconds. >> >> Because proxy-server wait for the above response, the execution of the >> following code is delayed. >> ( >> https://github.com/openstack/swift/blob/stable/rocky/swift/proxy/controllers/obj.py#L627 >> ) >> >> ``` >> for node in nodes: >> try: >> putter = self._make_putter(node, part, req, headers) >> self.app.set_node_timing(node, putter.connect_duration) >> return putter >> ``` >> >> This problem occurs when i do a ring rebalance. >> When object-replicator delete a partition directory that are no longer >> mine, the disk becomes very busy (Because of xfsaild daemon) >> Because the disk are busy, object-server can't create diskfile during PUT >> operation. >> >> Is there anyone who is having problems like me? >> How can I solve this problem? >> >> I need everyone's help. >> Thanks. >> >> Best Regards >> SeongSoo Cho >> >> -- >> SeongSoo Cho (South Korea) >> >> ___ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [Swift] PUT Object performance problem
For more information, I use ocata version. 2018๋ 10์ 29์ผ (์) ์คํ 10:07, SeongSoo Cho ๋์ด ์์ฑ: > Hello, All > > I have a terrible problem with object server. > Here is the case. > 1. User upload an object to proxy-server > 2. Proxy server try to connect with object-server > 3. If one of object-server is slow to respond, proxy-server is waiting for > response. > 3.1 While waiting for response, proxy-server can't do anything > 4. So, The response of client request will be delayed. > > In my opinion, this code seems to be a problem > ( > https://github.com/openstack/swift/blob/stable/rocky/swift/proxy/controllers/obj.py#L1734 > ) > > ``` > with ResponseTimeout(node_timeout): > resp = conn.getexpect() > ``` > > If node_timeout's value is 3 and object-server respond after 2 seconds, > proxy-server wait 2 seconds. > > Because proxy-server wait for the above response, the execution of the > following code is delayed. > ( > https://github.com/openstack/swift/blob/stable/rocky/swift/proxy/controllers/obj.py#L627 > ) > > ``` > for node in nodes: > try: > putter = self._make_putter(node, part, req, headers) > self.app.set_node_timing(node, putter.connect_duration) > return putter > ``` > > This problem occurs when i do a ring rebalance. > When object-replicator delete a partition directory that are no longer > mine, the disk becomes very busy (Because of xfsaild daemon) > Because the disk are busy, object-server can't create diskfile during PUT > operation. > > Is there anyone who is having problems like me? > How can I solve this problem? > > I need everyone's help. > Thanks. > > Best Regards > SeongSoo Cho > > -- > SeongSoo Cho (South Korea) > > ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] [Swift] PUT Object performance problem
Hello, All I have a terrible problem with object server. Here is the case. 1. User upload an object to proxy-server 2. Proxy server try to connect with object-server 3. If one of object-server is slow to respond, proxy-server is waiting for response. 3.1 While waiting for response, proxy-server can't do anything 4. So, The response of client request will be delayed. In my opinion, this code seems to be a problem ( https://github.com/openstack/swift/blob/stable/rocky/swift/proxy/controllers/obj.py#L1734 ) ``` with ResponseTimeout(node_timeout): resp = conn.getexpect() ``` If node_timeout's value is 3 and object-server respond after 2 seconds, proxy-server wait 2 seconds. Because proxy-server wait for the above response, the execution of the following code is delayed. ( https://github.com/openstack/swift/blob/stable/rocky/swift/proxy/controllers/obj.py#L627 ) ``` for node in nodes: try: putter = self._make_putter(node, part, req, headers) self.app.set_node_timing(node, putter.connect_duration) return putter ``` This problem occurs when i do a ring rebalance. When object-replicator delete a partition directory that are no longer mine, the disk becomes very busy (Because of xfsaild daemon) Because the disk are busy, object-server can't create diskfile during PUT operation. Is there anyone who is having problems like me? How can I solve this problem? I need everyone's help. Thanks. Best Regards SeongSoo Cho -- SeongSoo Cho (South Korea) ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
