Here's how we currently handle subordinate package dependencies in charm-nova-compute. See commit 32ef5b4c and 280c0d7d. For this bug I think we can fix it in this code with our current approach but it's clearly a bit awkward to handle subordinate dependencies in nova-compute. I'd like to also open another bug to see if we can figure out a better way to tell subordinates they need to upgrade and allow them to upgrade their own packages.
def determine_packages()
...
if cmp_release >= 'rocky':
packages = [p for p in packages if not p.startswith('python-')] packages.extend(PY3_PACKAGES)
if filter_missing_packages(['python-ceilometer']): packages.append('python3-ceilometer')
if filter_missing_packages(['python-neutron']): packages.append('python3-neutron')
if filter_missing_packages(['python-neutron-fwaas']): # to be added for this bug packages.append('python3-neutron-fwaas') # to be added for this bug
if virt_type == 'lxd': packages.append('python3-nova-lxd')
Here's how we currently handle subordinate package dependencies in charm-nova-compute. See commit 32ef5b4c and 280c0d7d. For this bug I think we can fix it in this code with our current approach but it's clearly a bit awkward to handle subordinate dependencies in nova-compute. I'd like to also open another bug to see if we can figure out a better way to tell subordinates they need to upgrade and allow them to upgrade their own packages.
def determine_ packages( ) 'python- ')]
packages. extend( PY3_PACKAGES) missing_ packages( ['python- ceilometer' ]):
packages. append( 'python3- ceilometer' ) missing_ packages( ['python- neutron' ]):
packages. append( 'python3- neutron' ) missing_ packages( ['python- neutron- fwaas'] ): # to be added for this bug
packages. append( 'python3- neutron- fwaas') # to be added for this bug
packages. append( 'python3- nova-lxd' )
...
if cmp_release >= 'rocky':
packages = [p for p in packages if not p.startswith(
if filter_
if filter_
if filter_
if virt_type == 'lxd':
return packages