- openstack-discuss - lists.openstack.org

Issue with ceph and vault
by Wouter van Bommel 28 Feb '19

28 Feb '19

Hi, I currently bumped into a situation in a cloud using both ceph and vault. While adding a new node to the cloud all seemed fine, until I noticed that on one node juju failed with the message: hook failed: "secrets-storage-relation-changed" Upon investigation it turned out that this node had a broken network configuration that was not picket up earlier. The problem was, that the vault instance could not be reached. This was fixed, but I could not un-wedge the error. A juju resolve on the node does not seem to have any effect. Using the debug-log option from juju I do see the following lines that do indicate the problem. INFO:vaultlocker.dmcrypt:LUKS formatting /dev/disk/by-dname/osd1-part1 using UUID:4448f9fa-d291-403e-9826-7318e57cf1a4 Cannot format device /dev/disk/by-dname/osd1-part1 which is still in use. vaultlocker: Command '['cryptsetup', '--batch-mode', '--uuid', '4448f9fa-d291-403e-9826-7318e57cf1a4', '--key-file', '-', 'luksFormat', '/dev/disk/by-dname/osd1-part1']' returned non-zero exit status 5 So the disk is in use. Which looks strange to me, as this machine could never complete the hooks as the vault was unreachable. I would like to get some advice on how to proceed. Regrds, Wouter

2 1

[tc][election] campaign question: team approval criteria
by Doug Hellmann 28 Feb '19

28 Feb '19

One of the key responsibilities of the Technical Committee is still evaluating projects and teams that want to become official OpenStack projects. The Foundation Open Infrastructure Project approval process has recently produced a different set of criteria for the Board to use for approving projects [1] than the TC uses for approving teams [2]. What parts, if any, of the OIP approval criteria do you think should apply to OpenStack teams? What other changes, if any, would you propose to the official team approval process or criteria? Are we asking the right questions and setting the minimum requirements high enough? Are there any criteria that are too hard to meet? How would you apply those rule changes to existing teams? [1] http://lists.openstack.org/pipermail/foundation/2019-February/002708.html [2] https://governance.openstack.org/tc/reference/new-projects-requirements.html -- Doug

7 12

Re: [placement][TripleO][infra] zuul job dependencies for greater good?
by Bogdan Dobrelya 28 Feb '19

28 Feb '19

I think we can still consider the middle-ground, where only deprecated multinode jobs, which tripleo infra team is in progress of migrating into standalone jobs, could be made depending on unit and pep8 checks? And some basic jobs will keep being depending on nothing. I expanded that idea in WIP topic [0]. Commit messages explain how the ordering was reworked. PS. I'm sorry I missed the submitted stats for zuul projects posted earlier in this topic, I'll take a look into that. [0] https://review.openstack.org/#/q/topic:ci_pipelines+(status:open+OR+status:… > Bogdan Dobrelya <bdobreli at redhat.com> writes: >> On 26.02.2019 17:53, James E. Blair wrote: >>> Bogdan Dobrelya <bdobreli at redhat.com> writes: >>> >>>> I attempted [0] to do that for tripleo-ci, but zuul was (and still >>>> does) complaining for some weird graphs building things :/ >>>> >>>> See also the related topic [1] from the past. >>>> >>>> [0] https://review.openstack.org/#/c/568543 >>>> [1] http://lists.openstack.org/pipermail/openstack-dev/2018-March/127869.html >>> >>> Thank you for linking to [1]. It's worth re-reading. Especially the >>> part at the end. >>> >>> -Jim >>> >> > > Yes, the part at the end is the best indeed. > I'd amend the time priorities graph though like that: > > CPU-time < a developer time < developers time > > That means burning some CPU and nodes in a pool for a waste might > benefit a developer, but saving some CPU and nodes in a pool would > benefit *developers* in many projects as they'd get the jobs results off > the waiting check queues faster :) -- Best regards, Bogdan Dobrelya, Irc #bogdando

1 2

[ceilometer] radosgw pollster
by Florian Engelmann 28 Feb '19

28 Feb '19

Hi, I failed to poll any usage data from our radosgw. I get 2019-02-22 17:23:57.461 24 INFO ceilometer.polling.manager [-] Polling pollster radosgw.containers.objects in the context of radosgw_300s_pollsters 2019-02-22 17:23:57.462 24 ERROR ceilometer.polling.manager [-] Prevent pollster radosgw.containers.objects from polling [<Project description=, domain_id=xx9d9975088a4d93922e1d73c7217b3b, enabled=True, [...] id=xx90a9b1d4be4d75b4bd08ab8107e4ff, is_domain=False, links={u'self': u'http://keystone-admin.service.xxxxxxx:35357/v3/projects on source radosgw_300s_pollsters anymore!: PollsterPermanentError Configurations like: cat polling.yaml --- sources: - name: radosgw_300s_pollsters interval: 300 meters: - radosgw.usage - radosgw.objects - radosgw.objects.size - radosgw.objects.containers - radosgw.containers.objects - radosgw.containers.objects.size Also tried radosgw.api.requests instead of radowsgw.usage. ceilometer.conf [...] [service_types] radosgw = object-store [rgw_admin_credentials] access_key = xxxxx0Z0xxxxxxxxxxxx secret_key = xxxxxxxxxxxxlRExxcPxxxxxxoNxxxxxxOxxxx [rgw_client] implicit_tenants = true Endpoints: | xxxxxxx | region | swift | object-store | True | admin | http://rgw.service.internalxxx/swift/v1/AUTH_%(tenant_id)s | | xxxxxxx | region | swift | object-store | True | internal | http://rgw.service.internalxxx/swift/v1/AUTH_%(tenant_id)s | | xxxxxxx | region | swift | object-store | True | public | https://s3.somedomain.com/swift/v1/AUTH_%(tenant_id)s | Ceilometer user: { "user_id": "ceilometer", "display_name": "ceilometer", "email": "", "suspended": 0, "max_buckets": 1000, "auid": 0, "subusers": [], "keys": [ { "user": "ceilometer", "access_key": "xxxxxxxxxxxxxxxxxx", "secret_key": "xxxxxxxxxxxxxxxxxxxxxxxxx" } ], "swift_keys": [], "caps": [ { "type": "buckets", "perm": "read" }, { "type": "metadata", "perm": "read" }, { "type": "usage", "perm": "read" }, { "type": "users", "perm": "read" } ], "op_mask": "read, write, delete", "default_placement": "", "placement_tags": [], "bucket_quota": { "enabled": false, "check_on_raw": false, "max_size": -1, "max_size_kb": 0, "max_objects": -1 }, "user_quota": { "enabled": false, "check_on_raw": false, "max_size": -1, "max_size_kb": 0, "max_objects": -1 }, "temp_url_keys": [], "type": "rgw" } radosgw config: [client.rgw.xxxxxxxxxxx] host = somehost rgw frontends = "civetweb port=7480 num_threads=512" rgw num rados handles = 8 rgw thread pool size = 512 rgw cache enabled = true rgw dns name = s3.xxxxxx.xxx rgw enable usage log = true rgw usage log tick interval = 30 rgw realm = public rgw zonegroup = xxx rgw zone = xxxxx rgw resolve cname = False rgw usage log flush threshold = 1024 rgw usage max user shards = 1 rgw usage max shards = 32 rgw_keystone_url = https://keystone.xxxxxxxxxxxxx rgw_keystone_admin_domain = default rgw_keystone_admin_project = service rgw_keystone_admin_user = swift rgw_keystone_admin_password = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx rgw_keystone_accepted_roles = member,_member_,admin rgw_keystone_accepted_admin_roles = admin rgw_keystone_api_version = 3 rgw_keystone_verify_ssl = false rgw_keystone_implicit_tenants = true rgw_keystone_admin_tenant = default rgw_keystone_revocation_interval = 0 rgw_keystone_token_cache_size = 0 rgw_s3_auth_use_keystone = true rgw_max_attr_size = 1024 rgw_max_attrs_num_in_req = 32 rgw_max_attr_name_len = 64 rgw_swift_account_in_url = true rgw_swift_versioning_enabled = true rgw_enable_apis = s3,swift,swift_auth,admin rgw_swift_enforce_content_length = true Any idea whats going on? All the best, Florian

3 7

[nova][dev] Any VMware resource pool and shares kind of feature available in openstack nova?
by Sanjay K 28 Feb '19

28 Feb '19

Hi Matt, I will define/derive priority based on the which sub network the VM belongs to - mostly Production or Development. From this, the Prod VMs will have higher resource allocation criteria than other normal VMs and these can be calculated at runtime when a VM is also rebooted like how VMware resource pools and shares features work. I appreciate any other suggestions. thanks and regards,

4 3

[Openstack-sigs] [publiccloud-wg] Late reminder weekly meeting Public Cloud WG
by Tobias Rydberg 28 Feb '19

28 Feb '19

Hi everyone, Time for a new meeting for PCWG - today (28th) 1400 UTC in #openstack-publiccloud! Agenda found below and at https://etherpad.openstack.org/p/publiccloud-wg Agenda 1. Train goal: Deletion of resources 2. Summit Denver forum topics 3. Followup goals Sorry for the late reminder! Talk to you later today! Cheers, Tobias -- Tobias Rydberg Senior Developer Twitter & IRC: tobberydberg www.citynetwork.eu | www.citycloud.com INNOVATION THROUGH OPEN IT INFRASTRUCTURE ISO 9001, 14001, 27001, 27015 & 27018 CERTIFIED

1 0

[heat] keystone endpoint configuration
by Jonathan Rosser 27 Feb '19

27 Feb '19

In openstack-ansible we are trying to help a number of our end users with their heat deployments, some of them in conjunction with magnum. There is some uncertainty with how the following heat.conf sections should be configured: [clients_keystone] auth_uri = ... [keystone_authtoken] www_authenticate_uri = ... It does not appear to be possible to define a set of internal or external keystone endpoints in heat.conf which allow the following: * The orchestration panels being functional in horizon * Deployers isolating internal openstack from external networks * Deployers using self signed/company cert on the external endpoint * Magnum deployments completing * Heat delivering an external endpoint at [1] * Heat delivering an external endpoint at [2] There are a number of related bugs: https://bugs.launchpad.net/openstack-ansible/+bug/1814909 https://bugs.launchpad.net/openstack-ansible/+bug/1811086 https://storyboard.openstack.org/#!/story/2004808 https://storyboard.openstack.org/#!/story/2004524 Any help we could get from the heat team to try to understand the root cause of these issues would be really helpful. Jon. [1] https://github.com/openstack/heat/blob/master/heat/engine/resources/server_… [2] https://github.com/openstack/heat/blob/master/heat/engine/resources/signal_…

5 7

[kolla] Proposing Michal Nasiadka to the core team
by Eduardo Gonzalez 27 Feb '19

27 Feb '19

Hi, is my pleasure to propose Michal Nasiadka for the core team in kolla-ansible. Michal has been active reviewer in the last relases ( https://www.stackalytics.com/?module=kolla-group&user_id=mnasiadka) has been keeping an eye on the bugs and being active help on IRC. He has also made efforts in community interactions in Rocky and Stein releases, including PTG attendance. His main interest is NFV and Edge clouds and brings valuable couple of years experience as OpenStack/Kolla operator with good knowledge of Kolla code base. Planning to work on extending Kolla CI scenarios, Edge use cases and improving NFV-related functions ease of deployment. Consider this email as my +1 vote. Vote ends in 7 days (22 feb 2019) Regards

6 6

Help with contributing to Storyboard for Outreachy 2019.
by Namrata Jha 27 Feb '19

27 Feb '19

I want to make contributions to the low hanging fruits in the Storyboard project, and want to make changes in the REST API documentation as is required in one of the stories, however, I have no idea how to go about it. I have even commented on the story in concern: https://storyboard.openstack.org/#!/story/298. Any help on this would be greatly appreciated. Moreover, the skills required mentioned on the Outreachy project listings page primarily includes SQL but there are no SQL related bugs to solve on the storyboard. I will contribute to improve the documentations wherever I can but how will that determine my selection as an Outreachy intern. P.S. I'm sorry @Kendall Nelson <kennelson11(a)gmail.com>, I had not intended to personally mail you this issue earlier, I replied to a previous thread and didn't realize that the mailing list wasn't included. Sorry for that. :)

2 1

[nova][keystone] project tags in context for scheduling
by Sam Morrison 27 Feb '19

27 Feb '19

Hi nova and keystone devs, We have a use case where we want to schedule a bunch of projects to specific compute nodes only. The aggregate_multitenancy_isolation isn’t viable because in some cases we will want thousands of projects to go to some hardware and it isn’t manageable/scaleable to do this in nova and aggregates. (Maybe it is and I’m being silly?) The best way I can think of doing this is to tag the keystone projects (or possibly set a custom property) and then write a custom nova scheduler filter to use the tag/property. The only issue I have is that tags/properties aren’t available to nova in it’s RequestContext. Can you think of a better way or a way that would work now? If this does in fact sound like a good way forward does authtoken middleware send this data downwards so nova could consume? If it does I assume it would be then as simple as adding these to the nova RequestContext? Thanks, Sam

3 3