- openstack-discuss - lists.openstack.org

UC Election - Looking for Election Officials
by Matt Van Winkle 22 Jan '19

22 Jan '19

Hey Stackers, We are getting ready for the Winter 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-feb2019.html <https://governance.openstack.org/uc/reference/uc-election-feb2019.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: January 21 - February 03, 05:59 UTC: Open candidacy for UC positions February 04 - February 10, 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 Joseph

4 4

[Release-job-failures][puppet] Release of openstack/puppet-aodh failed
by Jean-Philippe Evrard 22 Jan '19

22 Jan '19

Hello, puppet-aodh failed [3] to release due to an issue in the upload- puppetforge role, for a permission issue [0]. Maybe a privilege escalation is required in [1], or a deeper analysis needs to be done. The role was changed 5 days ago [2], so I am not sure this code had the chance to be tested in post release pipelines. Could someone have a look, please? Thank you in advance. Jean-Philippe Evrard (evrardjp) [0]: http://logs.openstack.org/61/617ffad84b633618490ca1023f8a31d9694b31a9/relea… [1]: http://git.openstack.org/cgit/openstack-infra/zuul-jobs/tree/roles/upload-p… [2]: https://github.com/openstack-infra/zuul-jobs/commit/fd8ffc6711d6481e2fcd40d… [3]: http://lists.openstack.org/pipermail/release-job-failures/2019-January/0010…

2 2

[nova][ops] Problems disabling notifications on state changes
by Massimo Sgaravatto 22 Jan '19

22 Jan '19

I am disabling ceilometer on my OpenStack Ocata cloud. As fas as I understand, besides stopping the ceilometer services, I can also apply the following changes to nova.conf on the compute nodes: instance_usage_audit = True --> false notify_on_state_change = vm_and_task_state --> None I have a problem with the latter change: # grep ^notify_on_state_change /etc/nova/nova.conf notify_on_state_change=None but in the nova log: 2019-01-21 08:31:48.246 6349 ERROR nova ConfigFileValueError: Value for option notify_on_state_change is not valid: Valid values are [None, vm_state, vm_and_task_state], but found 'None' I have also tried setting notify_on_state_change=<None> but it complains that it is not a valid value I can simply comment that line, but I am afraid there is a problem somewhere Thanks, Massimo

2 2

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

22 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 21 Jan '19

21 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 21 Jan '19

21 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 21 Jan '19

21 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