Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Pebble service manager #588

Merged
merged 1 commit into from
May 6, 2023
Merged

Conversation

dosaboy
Copy link
Member

@dosaboy dosaboy commented Apr 27, 2023

Also extends CLIHelper to support trying more than one binary command. Note that pebble info is not yet supported in sosreport so this functionality is only available when running against a host.

Adapts openstack plugin to fallback to pebble if
systemd services not detected.

Resolves: #584

Copy link
Contributor

@nicolasbock nicolasbock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I run this on a nova-conductor container, I get:

openstack:
  release:
    name: yoga
    days-to-eol: 1463
  failed-parts:
    - agent_exceptions
  features:
    nova:
      main:
        debug: false
        live_migration_permit_auto_converge: false
        live_migration_permit_post_copy: false
    api-ssl: false

while on a nova-cloud-conductor VM:

openstack:                                  
  release:                                   
    name: yoga                                
    days-to-eol: 1463                         
  services:                                                                                    
    systemd:                                                                                   
      enabled:                                                                                 
        - apache2                                                                              
        - haproxy
        - nova-cloud-controller-mysql-router
        - nova-conductor
        - nova-scheduler
      masked:
        - nova-api-os-compute
    ps:
      - apache2 (3)
      - haproxy (2)
      - nova-conductor (3)
      - nova-scheduler (3)
  features:               
    api-ssl: false
  agent-exceptions:                 
    nova:                      
      nova-scheduler:                         
        oslo_db.exception.DBNonExistentTable:
          '2023-04-27': 2                                                                      

The pebbles section is missing from the summary.

I am still investigating why...

@dosaboy
Copy link
Member Author

dosaboy commented Apr 28, 2023

When I run this on a nova-conductor container, I get:

openstack:
  release:
    name: yoga
    days-to-eol: 1463
  failed-parts:
    - agent_exceptions
  features:
    nova:
      main:
        debug: false
        live_migration_permit_auto_converge: false
        live_migration_permit_post_copy: false
    api-ssl: false

while on a nova-cloud-conductor VM:

openstack:                                  
  release:                                   
    name: yoga                                
    days-to-eol: 1463                         
  services:                                                                                    
    systemd:                                                                                   
      enabled:                                                                                 
        - apache2                                                                              
        - haproxy
        - nova-cloud-controller-mysql-router
        - nova-conductor
        - nova-scheduler
      masked:
        - nova-api-os-compute
    ps:
      - apache2 (3)
      - haproxy (2)
      - nova-conductor (3)
      - nova-scheduler (3)
  features:               
    api-ssl: false
  agent-exceptions:                 
    nova:                      
      nova-scheduler:                         
        oslo_db.exception.DBNonExistentTable:
          '2023-04-27': 2                                                                      

The pebbles section is missing from the summary.

I am still investigating why...

hmm ok ill try that out, another thing is that i realise i need to adapt the summary output to s/systemd/pebble/ when the services are in fact coming from pebble.

@dosaboy
Copy link
Member Author

dosaboy commented Apr 28, 2023

i've done a test with the latest code on a neutron-api unit and I get:

openstack:
  release:                  
    name: yoga                       
    days-to-eol: 1462
  services:             
    pebble:                                    
      active:    
        - neutron-server             
    ps:                    
      - neutron-server (1)

@nicolasbock
Copy link
Contributor

This looks much better:

openstack:                                                                                     
  release:                                                                                     
    name: yoga                                                                                 
    days-to-eol: 1457                                                                          
  services:
    pebble:
      active:
        - neutron-server
    ps:
      - neutron-server (1)
  dpkg:
    - keepalived 1:2.0.19-2ubuntu0.2

Also extends CLIHelper to support trying more than
one binary command. Note that pebble info is not yet
supported in sosreport so this functionality is only
available when running against a host.

Adapts openstack plugin to fallback to pebble if
systemd services not detected.

Resolves: canonical#584
@dosaboy dosaboy merged commit 333a4cc into canonical:main May 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

support pebble service manager
2 participants