January 2019 - openstack-discuss - lists.openstack.org

Question about Heat parser
by adjandeye.sylla＠orange.com 23 Jan '19

23 Jan '19

Dear all, In the context of my post-doc research, I'm working with HOT templates and I want to parse them. Instead of developing a new parser, I want to reuse the one that is used by Heat but I don't want to connect to a running OpenStack to do the parsing. Is it possible to use Heat as a standalone parser (i.e. without connecting to a running OpenStack) ? Thank you for your answer. Best regards, Adja SYLLA _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 2

[all] New Automatic SIG (continue discussion)
by Rico Lin 22 Jan '19

22 Jan '19

Dear all To continue the discussion of whether we should have new SIG for autoscaling. I think we already got enough time for this ML [1], and it's time to jump to the next step. As we got a lot of positive feedbacks from ML [1], I think it's definitely considered an action to create a new SIG, do some init works, and finally Here are some things that we can start right now, to come out with the name of SIG, the definition and mission. Here's my draft plan: To create a SIG name `Automatic SIG`, with given initial mission to improve automatic scaling with (but not limited to) OpenStack. As we discussed in forum [2], to have scenario tests and documents will be considered as actions for the initial mission. I gonna assume we will start from scenarios which already provide some basic tests and documents which we can adapt very soon and use them to build a SIG environment. And the long-term mission of this SIG is to make sure we provide good documentation and test coverage for most automatic functionality. I suggest `Automatic SIG` instead of `Autoscaling SIG` to make sure we can provide more value if there are more needs in the future. Just like the example which Adam raised `self-optimizing` from people who are using watcher [3]. Let me know if you got any concerns about this name. And to clarify, there will definitely some cross SIG co-work between this new SIG and Self-Healing SIG (there're some common requirements even across self-healing and autoscaling features.). We also need to make sure we do not provide any duplicated work against self-healing SIG. As a start, let's only focus on autoscaling scenario, and make sure we're doing it right before we move to multiple cases. If no objection, I will create the new SIG before next weekend and plan a short schedule in Denver summit and PTG. [1] http://lists.openstack.org/pipermail/openstack-discuss/2018-November/000284… [2] https://etherpad.openstack.org/p/autoscaling-integration-and-feedback [3] http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000813… -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

6 8

[Cyborg][IRC] The Cyborg IRC meeting will be held Wednesday at 0300 UTC
by Li Liu 22 Jan '19

22 Jan '19

The IRC meeting will be held Wednesday at 0300 UTC, which is 10:00 pm est(Tuesday) / 7:00 pm pst(Tuesday) /11 am Beijing time (Wednesday) This Week's Agenda: 1. Track Status on DB work 2. Plans on pushing for the deadline of Stein(1.5 month to go) a. Nova integration. . b. DB change, device drivers and discovery. -- Thank you Regards Li Liu

1 0

[congress] nominating Akhil Jain for core reviewer
by Eric K 22 Jan '19

22 Jan '19

Hi all, I'm writing to nominate Akhil Jain as a Congress core reviewer. He has been an active and consistent contributor in code, reviews, and community interactions for Rocky and Stein cycles. Some of his key contributions include data source drivers, working with other projects to drive key integrations, thorough code reviews, and many important nuts-and-bolts patches. He has been especially valuable to the project and the community through his technical designs informed by his gathering and understanding of operator requirements. Akhil: I look forward to continuing working together! Eric

2 1

Read Only FS after ceph issue
by Grant Morley 22 Jan '19

22 Jan '19

Hi all, We are in the process of retiring one of our old platforms and last night our ceph cluster went into an "Error" state briefly because 1 of the OSDs went close to full. The data got re-balanced fine and the health of ceph is now "OK" - however we have about 40% of our instances that now have corrupt disks which is a bit odd. Even more strange is that we cannot get them into rescue mode. As soon as we try we the instances seem to hang during the bootup process when they are trying to mount "/dev/vdb1" and we eventually get a kernel timeout error as below: Warning: fsck not present, so skipping root file system [ 5.644526] EXT4-fs (vdb1): INFO: recovery required on readonly filesystem [ 5.645583] EXT4-fs (vdb1): write access will be enabled during recovery [ 240.504873] INFO: task exe:332 blocked for more than 120 seconds. [ 240.506986] Not tainted 4.4.0-66-generic #87-Ubuntu [ 240.508782] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 240.511438] exe D ffff88003714b878 0 332 1 0x00000000 [ 240.513809] ffff88003714b878 ffff88007c18e358 ffffffff81e11500 ffff88007be81c00 [ 240.516665] ffff88003714c000 ffff88007fc16dc0 7fffffffffffffff ffffffff81838cd0 [ 240.519546] ffff88003714b9d0 ffff88003714b890 ffffffff818384d5 0000000000000000 [ 240.522399] Call Trace: I have even tried using a different image for nova rescue and we are getting the same results. Has anyone come across this before? This system is running OpenStack Mitaka with Ceph Jewel. Any help or suggestions will be much appreciated. Regards, -- Grant Morley Cloud Lead Absolute DevOps Ltd Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP www.absolutedevops.io <http://www.absolutedevops.io/> grant(a)absolutedevops.io <mailto:grant@absolutedevops.io> 0845 874 0580

2 2

[manila-ui][queens] cannot create share snapshot
by Ignazio Cassano 22 Jan '19

22 Jan '19

Hello, I installed manila on centos queens but it is not possible creating share snapshot from ui: Danger: An error occurred. Please try again later. It works from command line . Regards Ignazio

2 2

[Diversity] [OffTOPIC] OpenStack Diversity Survey - ends Feb 28
by Amy Marrich 22 Jan '19

22 Jan '19

This is the last time the Diversity and Inclusion WG is asking for your assistance for our current survey in collecting data in regards to diversity. We will be closing the survey on February 28th, 2019 in order to start compiling the data. We revised the Diversity Survey that was originally distributed to the Community in the Fall of 2015 and reached out in August with our new survey. We are looking to update our view of the OpenStack community and it's diversity. We are pleased to be working with members of the CHAOSS project who have signed confidentiality agreements in order to assist us in the following ways: 1) Assistance in analyzing the results 2) And feeding the results into the CHAOSS software and metrics development work so that we can help other Open Source projects Please take the time to fill out the survey and share it with others in the community. The survey can be found at: https://www.surveymonkey.com/r/OpenStackDiversity Thank you for assisting us in this important task! Please feel free to reach out to me via email, in Berlin, or to myself or any WG member in #openstack-diversity! Amy Marrich (spotz) Diversity and Inclusion Working Group Chair

1 0

[tc] [all] Please help verify the role of the TC
by Chris Dent 22 Jan '19

22 Jan '19

Recently Thierry, with the help of other TC members, wrote down the perceived role of the TC [1]. This was inspired by the work on the "Vision for OpenStack Clouds" [2]. If we think we should have that document to help validate and direct our software development, we should have something similar to validate governance. Now we need to make sure the document reflects not just how things are but also how they should be. We (the TC) would like feedback from the community on the following general questions (upon which you should feel free to expand as necessary). * Does the document accurately reflect what you see the TC doing? * What's in the list that shouldn't be? * What's not in the list that should be? * Should something that is listed be done more or less? Discussions like these are sometimes perceived as pointless navel gazing. That's a fair complaint when they result in nothing changing (if it should). In this case however, it is fair to say that the composition of the OpenStack community is changing and we _may_ need some adjustments in governance to effectively adapt. We can't know if any changes should be big or little until we talk about them. We have several weeks before the next TC election, so now seems an appropriate time. Note that the TC was chartered with a mission [3]: The Technical Committee (“TC”) is tasked with providing the technical leadership for OpenStack as a whole (all official projects, as defined below). It enforces OpenStack ideals (Openness, Transparency, Commonality, Integration, Quality…), decides on issues affecting multiple projects, forms an ultimate appeals board for technical decisions, and generally has technical oversight over all of OpenStack. Thanks for your participation and help. [1] https://governance.openstack.org/tc/reference/role-of-the-tc.html [2] https://governance.openstack.org/tc/reference/technical-vision.html [3] https://governance.openstack.org/tc/reference/charter.html#mission -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

15 52

[dev][tc][ptl] Evaluating projects in relation to OpenStack cloud vision
by Julia Kreger 22 Jan '19

22 Jan '19

As some of you may or may not have heard, recently the Technical Committee approved a technical vision document [1]. The goal of the technical vision document is to try to provide a reference point for cloud infrastructure software in an ideal universe. It is naturally recognized that not all items will apply to all projects. With that in mind, we want to encourage projects to leverage the vision by performing a realistic self-evaluation to determine how their individual project compares to the technical vision: What gaps exist in the project that could be closed to be more in alignment with the vision? Are there aspects of the vision which are inappropriate for the project to such a degree that the vision itself should change, not the project? We envision the results of the evaluation to be added to each project's primary contributor documentation tree (/doc/source/contributor/vision-reflection.rst) as a list of bullet points detailing areas where a project feels they need adjustment to better align with the technical vision, and if the project already has visibility into a path forward, that as well. As with all things of this nature, we anticipate projects to treat the document as a living document and update it as each project's contributors feel necessary. If an individual project community feels something in the overall OpenStack community technical vision does not apply, that is okay. If the project community feels that something in the vision is wrong for the whole of OpenStack, please feel free to submit a revision to gerrit in order to start that discussion. Once projects have performed a realistic self-evaluation, we ask each project to then consider those items they identified in their future planning as areas that could use the attention of contributors. To be very explicit about this, the intent is to help enable projects to identify areas for improved alignment with the rest of OpenStack using a short, concise, easily consumable list that can be referenced in planning, or even by drive-by contributors if they are intrigued by a specific problem. Thanks, Julia Kreger & Chris Dent [1] https://governance.openstack.org/tc/reference/technical-vision.html

3 4

[heystone][nova][cinder] netapp queens trust scoped token
by Ignazio Cassano 22 Jan '19

22 Jan '19

Hello Everyone, I am using a client for backupping openstack virtual machine. The crux of the problem is the client uses trust based authentication for scheduling backup jobs on behalf of user. When a trust scoped token is passed to cinder client to take a snapshot, I expect the client use the token to authenticate and perform the operation which cinder client does. However cinder volume service invokes novaclient as part of cinder nfs backend snapshot operation and novaclient tries to re-authenticate. Since keystone does not allow re-authentication using trust based tokens, cinder snapshot operation fails. So I get the following error: 2018-12-12 04:07:14.759 2859 ERROR cinder.volume.drivers. remotefs [req-61d977c1-eef3-4309-ac02-aaa0eb880925 ab1bdb5dadc54312891f3a6410fef04d 6d1bffb04e3b4cdda30dc17aa96bfffc - default default] Call to Nova to create snapshot failed: Forbidden: You are not authorized to perform the requested action: Using trust-scoped token to create another token. Create a new trust-scoped token instead. (HTTP 403) (Request-ID: req-f55b682a-001b-4952-bfb1-abf4dd6bf459) > 2018-12-12 04:07:14.759 2859 ERROR cinder.volume.drivers. remotefs Traceback (most recent call last): > 2018-12-12 04:07:14.759 2859 ERROR cinder.volume.drivers. remotefs File "/usr/lib/python2.7/site-packages/cinder/volume/drivers/ remotefs.py", line 1452, in _create_snapshot_online > 2018-12-12 04:07:14.759 2859 ERROR cinder.volume.drivers. remotefs connection_info) > 2018-12-12 04:07:14.759 2859 ERROR cinder.volume.drivers. remotefs File "/usr/lib/python2.7/site-packages/cinder/compute/nova.py", line 188, in create_volume_snapshot > 2018-12-12 04:07:14.759 2859 ERROR cinder.volume.drivers. remotefs create_info=create_info) > 2018-12-12 04:07:14.759 2859 ERROR cinder.volume.drivers. remotefs File "/usr/lib/python2.7/site-packages/novaclient/v2/assisted_volume_snapshots.py", line 43, in create > 2018-12-12 04:07:14.759 2859 ERROR cinder.volume.drivers. remotefs return self._create('/os-assisted-volume-snapshots', body, 'snapshot') > 2018-12-12 04:07:14.759 2859 ERROR cinder.volume.drivers. remotefs File "/usr/lib/python2.7/site-packages/novaclient/base.py", line 361, in _create > 2018-12-12 04:07:14.759 2859 ERROR cinder.volume.drivers. remotefs resp, body = self.api.client.post(url, body=body) > 2018-12-12 04:07:14.759 2859 ERROR cinder.volume.drivers. remotefs File "/usr/lib/python2.7/site-packages/keystoneauth1/adapter.py", line 310, in post > 2018-12-12 04:07:14.759 2859 ERROR cinder.volume.drivers. remotefs return self.request(url, 'POST', **kwargs) My cinder volume are non netapp fas8040 via nfs. Anyone can help me ? Regards Ignazio

2 4