[openstack-dev] [Openstack] Tokyo Summit Survey: Experience Deploying CloudFoundry in OpenStack
Hi, OpenStack users and developers, In our continued commitment to make CF the ONE true cross-cloud PaaS, we have been wondering what your experience was when deploying CF onto OpenStack using BOSH. We created this short survey: https://www.surveymonkey.com/r/VQQZ5ZP to aggregate your experience. This is a short survey that will take 5 minutes (or less) of your time to fill it out. After a week, we will share the results with the community. Our goal is to learn the most common pain point and hopefully help fix these in both the CF and OpenStack communities. Our session is scheduled on Wednesday, October 28 4:40pm - 5:20pm: http://openstacksummitoctober2015tokyo.sched.org/event/31161b1a3c03e3ac8a968d5623ef9dfc#.Vh2sJxOqqko. please feel free to join this discussion with us. :-) Best regards, CF BOSH team and contributors -Zhang Hua (Edward), Xing Zhou (Tom), Dr. Max __ 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
Re: [openstack-dev] Paul Luse added to Swift Core
Paul, congratulations! :-) John Dickinson To 2014-07-31 上午 "OpenStack Development Mailing List 08:57 (not for usage questions)" cc Please respond to "OpenStack Subject Development[openstack-dev] Paul Luse added to Mailing ListSwift Core \(not for usage questions\)" I'm happy to share that Paul Luse has join Swift's core reviewer team. Paul has provided a ton of leadership, insight, and code during the past year. He was instrumental in getting storage policies written, and he's actively involved in the current work around erasure code support. Welcome, Paul! --John (See attached file: signature.asc) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev signature.asc Description: Binary data ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [swift] Use FQDN in Ring files instead of "ip"
Hi, Here's a patch to allow hostname in Ring which is under developing you might be interested in. https://review.openstack.org/#/c/80421/ -Edward Zhang "Matsuda, Kenichiro" "openstack-dev@lists.openstack.org" 2014-07-23 上午cc 10:47 Subject [openstack-dev] [swift] Use FQDN in Please respond to Ring files instead of "ip" "OpenStack Development Mailing List \(not for usage questions\)" Hi, I want to use FQDN in Ring files instead of "ip". I tried the following Swift APIs with using FQDN and it succeeded. (I used swift1.13.1.) - PUT Container - PUT Object In some documents there is no info for using FQDN in Ring files. - swift 1.13.1 documentation The Rings > List of Devices http://docs.openstack.org/developer/swift/1.13.1/overview_ring.html#list-of-devices - The IP address of the server containing the device. - - swift-ring-builder's USAGE - swift-ring-builder add [--region ] --zone --ip --port --replication-ip --replication-port --device --meta --weight - I would like to know whether FQDN in Ring files supports and/or how to evaluate to support FQDN in Ring files. Could you please advise me for it? Best Regards, Kenichiro Matsuda. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Swift 2.0.0 has been released and includes support for storage policies
Cheers! This is the most exciting moment for Swift users and developers. Proud of you and the community! :-) -Edward Zhang John Dickinson To 2014-07-08 下午 "OpenStack Development Mailing List 09:24 (not for usage questions)" , Please respond to openstack-announce@lists.openstack. "OpenStack org Development cc Mailing List \(not for usage Subject questions\)"[openstack-dev] Swift 2.0.0 has I'm happy to announce that Swift 2.0.0 has been officially released! You can get the tarball at http://tarballs.openstack.org/swift/swift-2.0.0.tar.gz. This release is a huge milestone in the history of Swift. This release includes storage policies, a set of features I've often said is the most important thing to happen to Swift since it was open-sourced. What are storage policies, and why are they so significant? Storage policies allow you to set up your cluster to exactly match your use case. From a technical perspective, storage policies allow you to have more than one object ring in your cluster. Practically, this means that you can can do some very important things. First, given the global set of hardware for your Swift deployment, you can choose which set of hardware your data is stored on. For example, this could be performance-based, like with flash vs spinning drives, or geography-based, like Europe vs North America. Second, once you've chosen the subset of hardware for your data, storage policies allow you to choose how the data is stored across that set of hardware. You can choose the replication factor independently for each policy. For example, you can have a "reduced redundancy tier", a "3x replication tier", and also a tier with a replica in every geographic region in the world. Combined with the ability to choose the set of hardware, this gives you a huge amount of control over how your data is stored. Looking forward, storage policies is the foundation upon we are building support for non-replicated storage. With this release, we are able to focus on building support for an erasure code storage policy, thus giving the ability to more efficiently store large data sets. For more information, start with the developer docs for storage policies at http://swift.openstack.org/overview_policies.html. I gave a talk on storage policies at the Atlanta summit last April. https://www.youtube.com/watch?v=mLC1qasklQo The full changelog for this release is at https://github.com/openstack/swift/blob/master/CHANGELOG. --John (See attached file: signature.asc) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev signature.asc Description: Binary data ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Swift] storage policies merge plan
John, Do it make sense to support storage policy work in devstack so that it can be more easily tested? -Edward Zhang John Dickinson To 2014-05-24 上午 "OpenStack Development Mailing List 06:27 (not for usage questions)" , Please respond to openstack-operators@lists.openstack "OpenStack .org Development cc Mailing List \(not for usage Subject questions\)"[openstack-dev] [Swift] storage We've been working for a long time on the feature/ec branch in the swift repo. It's now "done" and needs to be merged into master to be generally available. Here's how the integration is going to work: 1) The feature/ec branch will be refactored into a series of dependent reviewable patches 2) The patch chain will be proposed to master, and master will enter a freeze until the storage policy patches land 3) The first patch in the chain will be marked as -2 to "plug" the chain 4) The Swift community will review and approve all patches in the chain. 5) When all patches in the chain are approved, the first -2 will be removed and the whole chain will be sent to the CI system There are two things that I'll ask of you during this time. First, please commit time to reviewing the storage policy patches. Second, please do not deploy a version of Swift that is midway through the storage policy patch chain. I don't expect it to break anything, but it's a complicating factor best to be avoided. I will send out another email when the patch chain has been proposed to master and to announce the freeze. --John (See attached file: signature.asc) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev signature.asc Description: Binary data ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] OpenStack Beijing Meetup on May 24th
Hi ALL, The 2nd OpenStack Beijing meetup is opened for registration. Welcome to join us! Title: OpenStack Beijing Meetup on May 24th http://www.meetup.com/China-OpenStack-User-Group/events/182091162/ Theme：OpenStack Atlanta Summit Guests: Jeffrey Yang, Jian Hua Geng, Edward Zhang, Vincent Hou from IBM Jouston Huang, Xin Xu from UnitedStack Overview: OpenStack Atalanta Summit was just concluded. During this meet up, we invite guests, who has attended Atlanta Summit, to share their feelings and thoughts about Atlanta Summit with people who were not able to attend this summit. Our guests will share their feel gained from summit, specifically Docker, Juniper OpenContrail, Ceph, and Ubuntu Juju network weakness, and etc. They will share their experiences and lessons learned in their speeches and design sessions in the summit too. Agenda: 2:00-2:15 Sign in 2:15-3:15 Round table sharing：Summit briefing（By all guests） 3:15-3:30 Tea break 3:30-4:00 Small talk：How to make a speech in OpenStack Summit 4:00-4:30 Small talk：Lessons learned while leading a OpenStack design session（By: Edward Zhang, Vincent Hou） 4:30-5:00 Social time___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Swift] Request's Round trip time
Sumit, I'm working on profiling middleware and tools for Swift debugging on performance issue. This tool is powerful to get understanding how is code running at the function level by collecting metrics in statistical way. I think you maybe try this tool and see if you can get RTT at proxy server side. Remember to get the RTT information via query on the function __call__ of ./swift/proxy/server.py. Here's the patch. https://review.openstack.org/#/c/53270/24 I'm also thinking of proposing another tool to trace the request process path and tie the timing information together in order to give you a full picture in hierarchical way so that you can understand how well each Swift server component behaves for a specific request. Any feedback is welcomed. -Edward Zhang Sumit Gaur To "OpenStack Development Mailing List 2014-03-31 下午 (not for usage questions)" 01:52 cc Please respond to Subject "OpenStack [openstack-dev] [Swift] Request's DevelopmentRound trip time Mailing List \(not for usage questions\)" Hi I want to see the Round Trip Time for swift request in proxy log. I am able to see RTT for failures and timeouts and no RTT for normal requests. Do I need to set and config param. Thanks sumit___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <><><>___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Swift] Profiling issue, need help!
Hi Stackers,
I'm working on the patch 53270 for Swift profiling middleware and was
blocked by a very annoying problem of the python eventlet profile which
inherits from python standard profiler. It sometimes raised AssertionError
of 'bad call' or 'bad return' in trace_dispatch_call and
trace_dispatch_return hooked function. The eventlet profiler extend the
return calls of standard profiler at line 116. This problem will be gone if
I change it back to python standard profile. So I guess it is specific to
eventlet profile. It may not correctly handle some special cases.
The 2 places in the code of standard profiler that complains:
1) https://github.com/python-git/python/blob/master/Lib/profile.py#L299
assert rframe.f_back is frame.f_back, ("Bad call", rfn, rframe,
rframe.f_back, frame, frame.f_back)
2) https://github.com/python-git/python/blob/master/Lib/profile.py#L330
assert frame is self.cur[-2].f_back, ("Bad return", self.cur[-3])
I don't understand why to use assert there. What does it mean if it happens
unexpected?
The profiler crashed and profiling results can't be used because of you
have an unexpected call? (based on the practice of using assert
statement to check your call contract)
The results still can be used but not precise any more. you may need to
catch the AssertionError.
It is actually a bug need to be fixed here?
When I look into the eventlet profile, I'm also very curious about two
line of code in eventlet profile module. It doesn't make sense to me since
they are not reachable in any case. anybody can explain why?
https://github.com/eventlet/eventlet/blob/master/eventlet/green/profile.py#L103
https://github.com/eventlet/eventlet/blob/master/eventlet/green/profile.py#L110
Here's an example of stack trace:
---
Traceback (most recent call last):
File "/opt/stack/swift/bin/swift-proxy-server", line 23, in
sys.exit(run_wsgi(conf_file, 'proxy-server', default_port=8080,
**options))
File "/opt/stack/swift/swift/common/wsgi.py", line 407, in run_wsgi
run_server(conf, logger, sock)
File "/opt/stack/swift/swift/common/wsgi.py", line 335, in run_server
wsgi.server(sock, app, NullLogger(), custom_pool=pool)
File "/usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py", line 693,
in server
client_socket = sock.accept()
File "/usr/local/lib/python2.7/dist-packages/eventlet/greenio.py", line
183, in accept
timeout_exc=socket.timeout("timed out"))
File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/__init__.py",
line 155, in trampoline
return hub.switch()
File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line
187, in switch
return self.greenlet.switch()
File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line
236, in run
self.wait(sleep_time)
File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/poll.py", line
113, in wait
self.block_detect_post()
File "/usr/lib/python2.7/profile.py", line 211, in trace_dispatch
if self.dispatch[event](self, frame,t):
File "/opt/stack/swift/swift/common/middleware/profile.py", line 239, in
trace_dispatch_return_extend_back
return self.trace_dispatch_return(frame, t);
File "/usr/lib/python2.7/profile.py", line 312, in trace_dispatch_return
assert frame is self.cur[-2].f_back, ("Bad return", frame.f_code,
self.cur[-2].f_back.f_code)
AssertionError: ('Bad return', ,
)
---
Another paste example of stack trace is here.
-Edward Zhang___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Openstack-dev][swift] profiling middleware blueprint status
hi John, I've been working on Swift profiling middleware blueprint since HK design summit. I found the status of direction needs approval and series goal is not defined yet. Would you please help to check if we need to change it? BTW, the code is ready for review. :-) -Edward Zhang___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Swift] Metadata Search API
Hi, I added two comments about enhancement of sorting and location based query at the discussion wiki page. https://wiki.openstack.org/wiki/Talk:MetadataSearchAPI#Metadata_Search_API_Discussion_page Best Regards, Edward Zhang(张华) Advisory Software Engineer Open Standards and Cloud Emerging Technology Institute(ETI) IBM China Software Development Lab "Thomas, Lincoln (HP Storage R&D)" "openstack-dev@lists.openstack.org" 2014-01-11 上午cc 10:00 Subject [openstack-dev] [Swift] Metadata Please respond to Search API "OpenStack Development Mailing List \(not for usage questions\)" Rebooting this thread now that I've reorg'd the Wiki page. The proposed REST API spec for searching system and custom metadata in Swift, across accounts, containers, and objects, is now posted at: https://wiki.openstack.org/wiki/MetadataSearchAPI I've also made the first modification to the API since the Icehouse design summit where I introduced this project: adding "metadata:" per conversation with Paula Ta-Shma's team at IBM Storage Research. The home page for this project remains at: https://wiki.openstack.org/wiki/MetadataSearch See that home page for further details, and the history of this email thread. Feel free to edit the Wiki as described on the home page! As Brian Cline (SoftLayer) said so eloquently in this thread: > Today, about the best one can do is iterate through everything and inspect metadata > along the way - obviously an infinitely expensive (and hilariously insane) > operation. > If there are any others who have implemented search in Swift, please speak up and > help shape this. We both want to get community consensus on a standard search API, > then get a pluggable reference implementation into Swift. > This is all work-in-progress stuff, but we'd welcome any feedback, concerns, > literal jumps for joy, etc. in this thread, both on the API and on a reference > architecture. Thanks in advance, Lincoln Thomas (IRC lincolnt) System/Software Engineer, HP Storage R&D Portland, OR, USA, +1 (503) 757-6274 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <><><><>___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Openstack] [keystone][ssl] Help for configure keystone with ssl.
Qing Long, Here's a document in keystone FYI. https://github.com/openstack/keystone/blob/master/doc/source/apache-httpd.rst Meanwhile, I'm submitting a patch into devstack to enable apache and ssl for keystone service: https://review.openstack.org/#/c/36474/ Please help me to test it if you want. :-) Best Regards, Edward Zhang(张华) "Qinglong.Meng" To openst...@lists.openstack.org, 08/21/2013 06:13 "openstack-dev@lists.openstack.org" PM , cc Subject [Openstack] [keystone][ssl] Help for configure keystone with ssl. Hi All, Os: ubuntu 12.04 LTS keystone version: stable/grizzly Ｉ hava seen "keystone-manage ssl_setup" in keystone tag 2013.2.b1. but I can't use it in my version. So I want to know: * how to configure ssl with keystone manual? * how to test configure is ok? Tks for you help. Best Regards, -- Lawrency Meng mail: mengql112...@gmail.com ___ Mailing list: https://launchpad.net/~openstack Post to : openst...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openst...@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack <><><><>___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
